Method and apparatus for triggering non-unicast service operation, and network functions

Abstract

To provide a method and apparatus for triggering a non-unicast service operation, and network functions.SOLUTION: A method comprises: acquiring non-unicast session information or non-unicast service information; and executing a first operation according to the non-unicast session information or the non-unicast service information, wherein the first operation comprises at least one of the following: sending a first non-unicast session operation instruction to a second network function, and sending a second non-unicast session operation instruction or a non-unicast session context operation instruction to a third network function; and the first non-unicast session operation instruction comprises at least one of the following: a non-unicast session shared resource operation instruction, a non-unicast service operation instruction, the non-unicast session information, information of a first network function, non-unicast quality of service (QoS) stream information, and a non-unicast session operation type.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] (CROSS REFERENCE TO RELATED APPLICATIONS) This application claims priority to Chinese Patent Application No. 202110070319.1 filed in China on January 19, 2021, Chinese Patent Application No. 202110129381.3 filed in China on January 29, 2021, and Chinese Patent Application No. 202110158954.5 filed in China on February 4, 2021, the entire contents of which are incorporated herein by reference.

[0002] The present application relates to the field of communication technology, and specifically to a method, device and network function for triggering non-unicast service operations. [Background technology]

[0003] In a communication system, for example, a fifth-generation mobile communication technology (5th-Generation, 5G) system, a multicast service can have two transmission methods. 1) Shared: A transmission channel shared by multiple terminals is used between a core network and a wireless access network (RAN), and only a portion of data is transmitted to multiple terminals for reception. 2) Unicast: A transmission channel related to terminals is used between a core network and a RAN, and this channel may include a shared channel between some user plane functions of the core network. In one multicast service, the two transmission methods may coexist. However, currently, when a multicast service operation is triggered, only the shared transmission method is considered, thereby affecting the multicast service. Therefore, how to trigger a non-unicast service operation when the shared transmission method and the unicast transmission method are considered at the same time is a problem that must be solved urgently. Summary of the Invention [Problem to be solved by the invention]

[0004] The embodiments of the present application provide a method, device and network function for triggering a non-unicast task operation, which can trigger a non-unicast task operation when a shared transmission mode and a unicast transmission mode are simultaneously considered. [Means for solving the problem]

[0005] According to a first aspect, there is provided a method for triggering a non-unicast business operation to be performed by a first network function, the method comprising: Obtaining non-unicast session information or non-unicast service information; performing a first operation based on the non-unicast session information or the non-unicast service information; wherein the first operation includes at least one of sending a first non-unicast session operation instruction to a second network function, and sending a second non-unicast session operation instruction or a non-unicast session context operation instruction to a third network function; wherein the first non-unicast session operation instruction is at least one of a non-unicast session shared resource operation instruction, a non-unicast task operation instruction, non-unicast session information, information of the first network function, non-unicast quality of service (QoS) flow information, and a non-unicast session operation type; wherein the second non-unicast session operation instruction is: at least one of a non-unicast session shared resource operation instruction, a non-unicast task operation instruction, a non-unicast session unicast resource operation instruction, non-unicast session information, information of the first network function, non-unicast QoS flow information, and a non-unicast session operation type; Wherein, the non-unicast session context operation instruction is at least one of a non-unicast session shared resource operation instruction, a non-unicast task operation instruction, a non-unicast session unicast resource operation instruction, and a non-unicast session connection operation instruction; Here, the non-unicast session shared resource operation instruction is: at least one of a non-unicast session shared resource operation type, a non-unicast task operation instruction, non-unicast session information, information of the first network function, non-unicast QoS flow information, and a non-unicast session operation type; Wherein, the non-unicast session unicast resource operation instruction is: At least one of a non-unicast session unicast resource operation type, a non-unicast task operation instruction, non-unicast session information, information of the first network function, unicast QoS flow information, a non-unicast session operation type, and unicast session information; Here, the non-unicast includes at least one of a multicast and a broadcast.

[0006] According to a second aspect, there is provided a method for triggering a non-unicast business operation performed by a second network function, the method comprising: performing a second operation based on at least one of the non-unicast capability of the first RAN node and the first indication received from the first network function; Here, the second operation is at least one of: sending a single paging message to the first RAN node; sending a non-unicast session shared resource operation instruction to the first RAN node; suspending sending of the non-unicast session shared resource operation instruction; sending a non-unicast session unicast resource operation instruction to the first RAN node; suspending sending of the non-unicast session unicast resource operation instruction; and sending a group paging message to the first RAN node; The first indication information is used to indicate at least one of non-unicast resource operation type information, no need for paging, and need for paging; The non-unicast includes at least one of a multicast and a broadcast.

[0007] According to a third aspect, there is provided a method for triggering a non-unicast business operation performed by a third network function, the method comprising: information on the third network function; and sending at least one of user information, terminal information, and unicast session information to a tenth network function; The unicast session information includes: It includes at least one of a session management context identifier and a PDU session identifier.

[0008] According to a fourth aspect, there is provided a method for triggering a non-unicast service operation performed by an access network side device, the method comprising: Obtaining a non-unicast session unicast resource operation instruction; Instructing a core network function that a node is joining and / or that a node is leaving.

[0009] According to a fifth aspect, there is provided a method for managing a multicast tree for a non-unicast service executed by a fourth network function, the method comprising: a non-unicast session connection operation instruction received from a fifth network function; RAN capabilities; managing the multicast tree according to at least one of the following: a non-unicast session or a RAN node capability of serving the non-unicast service; Here, the multicast tree is The multicast tree includes at least one of a control plane multicast tree and a user plane multicast tree.

[0010] According to a sixth aspect, there is provided a method for managing a multicast tree for a non-unicast service performed by a fifth network function, the method comprising: sending a non-unicast session connection operation indication to a fourth network function according to the first information; Here, the first information is A user plane function controlled by the fifth network function transmits data to a first terminal using a non-unicast session unicast resource; stopping a user plane function controlled by the fifth network function from transmitting data to a final terminal using non-unicast session unicast resources; the fifth network function providing a service for a first terminal or user; and ceasing the fifth network function from providing service for the last terminal or user.

[0011] According to a seventh aspect, there is provided a method for associating a non-unicast task executed by a sixth network function with a unicast session, the method comprising: sending a first operation instruction to a seventh network function according to at least one of the RAN capability, the RAN node capability to serve a non-unicast service or session, the first binding instruction from the seventh network function, and the second binding instruction from the eighth network function; Wherein, the first binding instruction includes unicast session information, and at least one of a non-unicast service operation instruction, non-unicast session information, a non-unicast service operation type, a non-unicast session operation type, and a non-unicast instruction; Here, the second binding instruction is: including at least one of: user already joined, user not left, user already left, user not joined, business already started, business not started, business already stopped, business not stopped, not allowing user to join, allowing user to join, not binding, binding, unbinding, and not unbinding; Here, the first operation instruction is: The instruction includes at least one of an association instruction, a disassociation instruction, a non-association instruction, and a maintenance of association instruction.

[0012] According to an eighth aspect, there is provided a method for associating a non-unicast task executed by a seventh network function with a unicast session, the method comprising: obtaining a first operation instruction for a sixth network function or a second operation instruction for an eighth network function; According to the first operation instruction or the second operation instruction, performing at least one of associating the unicast session with a non-unicast session, associating the unicast session with a non-unicast function, disassociating the unicast session with the non-unicast session, and disassociating the unicast session with the non-unicast function; Here, the first operation instruction includes at least one of an association instruction, an association cancellation instruction, a non-association instruction, and an association maintenance instruction, The second operation instruction includes at least one of an associating instruction, an unassociating instruction, a non-associating instruction, and an association maintaining instruction.

[0013] According to a ninth aspect, there is provided a method for associating a non-unicast task executed by an eighth network function with a unicast session, the method comprising: A terminal or user has a bound non-unicast session or service; and sending a second operation instruction to a seventh network function according to at least one of: the terminal or the user having no bound non-unicast sessions or no bound non-unicast services; Here, the second operation instruction includes at least one of an associating instruction, an unassociating instruction, a non-associating instruction, and an association maintaining instruction.

[0014] According to a tenth aspect, there is provided a method for authenticating or authorizing a non-unicast task performed by a ninth network function, the method comprising: Obtaining non-unicast indication information; sending an authentication or authorization message to an application server; Here, the non-unicast instruction information includes at least one of unicast session information, a non-unicast service operation instruction, a non-unicast session information, a non-unicast service operation type, a non-unicast session operation type, and a non-unicast instruction.

[0015] According to an eleventh aspect, there is provided a non-unicast task operation triggering device for use in a first network function, the device comprising: A first acquisition module for acquiring non-unicast session information or non-unicast service information; a first execution module for executing a first operation based on the non-unicast session information or the non-unicast service information; wherein the first operation includes at least one of sending a first non-unicast session operation instruction to a second network function, and sending a second non-unicast session operation instruction or a non-unicast session context operation instruction to a third network function; wherein the first non-unicast session operation instruction is at least one of a non-unicast session shared resource operation instruction, a non-unicast task operation instruction, non-unicast session information, information of the first network function, non-unicast quality of service (QoS) flow information, and a non-unicast session operation type; wherein the second non-unicast session operation instruction is: at least one of a non-unicast session shared resource operation instruction, a non-unicast task operation instruction, a non-unicast session unicast resource operation instruction, non-unicast session information, information of the first network function, non-unicast QoS flow information, and a non-unicast session operation type; Wherein, the non-unicast session context operation instruction is at least one of a non-unicast session shared resource operation instruction, a non-unicast task operation instruction, a non-unicast session unicast resource operation instruction, and a non-unicast session connection operation instruction; Here, the non-unicast session shared resource operation instruction is: at least one of a non-unicast session shared resource operation type, a non-unicast task operation instruction, non-unicast session information, information of the first network function, non-unicast QoS flow information, and a non-unicast session operation type; Wherein, the non-unicast session unicast resource operation instruction is: At least one of a non-unicast session unicast resource operation type, a non-unicast task operation instruction, non-unicast session information, information of the first network function, unicast QoS flow information, a non-unicast session operation type, and unicast session information; Here, the non-unicast includes at least one of a multicast and a broadcast.

[0016] According to a twelfth aspect, there is provided a triggering device for a non-unicast task operation for use in a second network function, the device comprising: a second execution module for performing a second operation based on at least one of the non-unicast capability of the first RAN node and the first indication information received from the first network function; Here, the second operation is at least one of: sending a single paging message to the first RAN node; sending a non-unicast session shared resource operation instruction to the first RAN node; suspending sending of the non-unicast session shared resource operation instruction; sending a non-unicast session unicast resource operation instruction to the first RAN node; suspending sending of the non-unicast session unicast resource operation instruction; and sending a group paging message to the first RAN node; The first indication information is used to indicate at least one of non-unicast resource operation type information, no need for paging, and need for paging; The non-unicast includes at least one of a multicast and a broadcast.

[0017] According to a thirteenth aspect, there is provided a trigger device for a non-unicast task operation for use in a third network function, the device comprising: information on the third network function; and a third sending module for sending at least one of the user information, the terminal information, and the unicast session information to a tenth network function; The unicast session information includes: It includes at least one of a session management context identifier and a PDU session identifier.

[0018] According to a fourteenth aspect, there is provided a trigger device for a non-unicast service operation for use in an access network side device, the device comprising: a fifth obtaining module for obtaining a non-unicast session unicast resource operation instruction; and a fourth execution module for instructing a core network function that a node is joining and / or that a node is leaving.

[0019] According to a fifteenth aspect, there is provided a management device for a non-unicast service multicast tree used in a fourth network function, the management device comprising: a non-unicast session connection operation instruction received from a fifth network function; RAN capabilities; a first management module for managing the multicast tree according to at least one of a non-unicast session or a RAN node capability of serving a non-unicast service; Here, the multicast tree is The multicast tree includes at least one of a control plane multicast tree and a user plane multicast tree.

[0020] According to a sixteenth aspect, there is provided a management device for a non-unicast service multicast tree used in a fifth network function, the management device comprising: a first sending module for sending a non-unicast session connection operation indication to a fourth network function according to the first information; Here, the first information is A user plane function controlled by the fifth network function transmits data to a first terminal using a non-unicast session unicast resource; stopping a user plane function controlled by the fifth network function from transmitting data to a final terminal using non-unicast session unicast resources; the fifth network function providing a service for a first terminal or user; and ceasing the fifth network function from providing service for the last terminal or user.

[0021] According to a seventeenth aspect, there is provided an apparatus for associating a non-unicast service with a unicast session for use in a sixth network function, the apparatus comprising: a second sending module for sending a first operation instruction to the seventh network function according to at least one of the RAN capability, the RAN node capability serving the non-unicast service or the non-unicast session, the first binding instruction from the seventh network function, and the second binding instruction from the eighth network function; Wherein, the first binding instruction includes unicast session information, and at least one of a non-unicast service operation instruction, non-unicast session information, a non-unicast service operation type, a non-unicast session operation type, and a non-unicast instruction; Here, the second binding instruction is: including at least one of: user already joined, user not left, user already left, user not joined, business already started, business not started, business already stopped, business not stopped, not allowing user to join, allowing user to join, not binding, binding, unbinding, and not unbinding; Here, the first operation instruction is: The instruction includes at least one of an association instruction, a disassociation instruction, a non-association instruction, and a maintenance of association instruction.

[0022] According to an eighteenth aspect, there is provided an apparatus for associating a non-unicast service with a unicast session for use in a seventh network function, the apparatus comprising: a fourth acquisition module for acquiring a first operation instruction of a sixth network function or a second operation instruction of an eighth network function; According to the first operation instruction or the second operation instruction, a third execution module for performing at least one of associating the unicast session with the non-unicast session, associating the unicast session with the non-unicast function, disassociating the unicast session with the non-unicast session, and disassociating the unicast session with the non-unicast function; Here, the first operation instruction includes at least one of an association instruction, an association cancellation instruction, a non-association instruction, and an association maintenance instruction, The second operation instruction includes at least one of an associating instruction, an unassociating instruction, a non-associating instruction, and an association maintaining instruction.

[0023] According to a nineteenth aspect, there is provided an apparatus for associating a non-unicast service with a unicast session for use in an eighth network function, the apparatus comprising: A terminal or user has a bound non-unicast session or service; a fourth sending module for sending a second operation instruction to a seventh network function according to at least one of: the terminal or the user having no bound non-unicast session or no non-unicast service; Here, the second operation instruction includes at least one of an associating instruction, an unassociating instruction, a non-associating instruction, and an association maintaining instruction.

[0024] According to a twentieth aspect, there is provided an authentication or authorization device for a non-unicast service for use in a ninth network function, the device comprising: a fifth acquiring module for acquiring non-unicast indication information; and a fifth sending module for sending an authentication or authorization message to the application server; Here, the non-unicast instruction information includes at least one of unicast session information, a non-unicast service operation instruction, a non-unicast session information, a non-unicast service operation type, a non-unicast session operation type, and a non-unicast instruction.

[0025] According to a twenty-first aspect, there is provided a network function comprising a processor, a memory, and a program or instructions stored in the memory and operable to run on the processor, the program or instructions, when executed by the processor, implementing the steps of the method described above.

[0026] According to a twenty-second aspect, there is provided a readable storage medium having a program or instructions stored thereon, the program or instructions implementing the steps of the method described above when executed by a processor.

[0027] According to a twenty-third aspect, there is provided a chip, the chip including a processor and a communication interface, the communication interface coupled to the processor, the processor running a program or instructions and used to implement the method described above.

[0028] According to a twenty-fourth aspect, an embodiment of the present application provides a computer program product, the computer program product being stored in a non-volatile storage medium, the program product being executed by at least one processor to realize the steps of the methods described above.

[0029] According to a twenty-fifth aspect, an embodiment of the present application provides a network function, the network function being configured to perform the steps of the method described above. Effect of the Invention

[0030] It is easy to understand that the method for triggering a non-unicast business operation in the embodiment of the present application can realize triggering of a non-unicast business operation when the shared transmission method and the unicast transmission method are simultaneously considered by executing a first operation based on the acquired non-unicast session information or non-unicast business information. [Brief description of the drawings]

[0031] [Figure 1] 1 is a block diagram of a wireless communication system to which an embodiment of the present application can be applied. [Diagram 2] 2 is a flowchart of a method for triggering a non-unicast business operation in an embodiment of the present application; [Diagram 3] 4 is a flowchart of another non-unicast business operation triggering method in an embodiment of the present application; [Figure 4] 4 is a flowchart of another non-unicast business operation triggering method in an embodiment of the present application; [Diagram 5]4 is a flowchart of another non-unicast business operation triggering method in an embodiment of the present application; [Figure 6] 2 is a flowchart of a method for managing a multicast tree for a non-unicast service in an embodiment of the present application; [Figure 7] 4 is a flowchart of another non-unicast service multicast tree management method in an embodiment of the present application; [Figure 8] 2 is a flowchart of a method for associating a non-unicast task with a unicast session in an embodiment of the present application; [Figure 9] 4 is a flowchart of another method for associating a non-unicast task with a unicast session in an embodiment of the present application; [Figure 10] 4 is a flowchart of another method for associating a non-unicast task with a unicast session in an embodiment of the present application; [Figure 11] 4 is a flowchart of an authentication or authorization method for a non-unicast service in an embodiment of the present application; [Figure 12] 1 is a flowchart of a related business operation process in Example 1 of the present application. [Figure 13] 1 is a flowchart of a related business operation process in Example 2 of the present application. [Figure 14] 1 is a flowchart of a related business operation process in Example 3 of the present application. [Figure 15] 1 is a flowchart of a related business operation process in Example 4 of the present application. [Figure 16] FIG. 2 is a block diagram of a trigger device for non-unicast business operations in an embodiment of the present application; [Figure 17] FIG. 11 is a block diagram of another non-unicast business operation trigger device of an embodiment of the present application; [Figure 18] FIG. 11 is a block diagram of another non-unicast business operation trigger device of an embodiment of the present application; [Figure 19] FIG. 11 is a block diagram of another non-unicast business operation trigger device of an embodiment of the present application; [Figure 20]FIG. 2 is a block diagram of a management device for a non-unicast service multicast tree according to an embodiment of the present application; [Figure 21] FIG. 11 is a block diagram of another non-unicast service multicast tree management device in an embodiment of the present application; [Figure 22] FIG. 2 is a block diagram of an apparatus for associating a non-unicast task with a unicast session according to an embodiment of the present application; [Diagram 23] FIG. 2 is a block diagram of another non-unicast service and unicast session association device according to an embodiment of the present application; [Figure 24] FIG. 2 is a block diagram of another non-unicast service and unicast session association device according to an embodiment of the present application; [Diagram 25] FIG. 2 is a block diagram of an authentication or authorization device for a non-unicast service according to an embodiment of the present application; [Figure 26] FIG. 2 is a block diagram of a network function of an embodiment of the present application. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0032] The following clearly and completely describes the technical solutions in the embodiments of the present application in conjunction with the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained based on the embodiments of the present application without the need for creative efforts by those skilled in the art are within the scope of protection of the present application.

[0033] The terms "first," "second," etc. in the specification and claims of the present application are intended to distinguish between similar objects and are not intended to describe a particular order or sequence. It is to be understood that terms so used are interchangeable, where appropriate, such that the embodiments of the present application may be performed in other orders than those shown or described herein, and that the objects distinguished by "first" and "second" are generally of the same type and do not limit the number of objects, e.g., the first object may be one or more. It is to be noted that "and / or" in the specification and claims refers to at least one of the objects connected, and the character " / " generally refers to an "or" relationship between the related objects.

[0034] It should be noted that the techniques described in the embodiments of the present application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be applied to other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" in the embodiments of the present application are always used interchangeably, and the techniques described may be used in the above-mentioned systems and radio technologies, or in other systems and radio technologies. Although the following description describes a New Radio (NR) system for illustrative purposes and uses NR terminology in most of the following description, these technologies may also be used in applications other than NR system applications, such as sixth generation (6G) systems.th This may be applied to a 6G (6th Generation) communication system.

[0035] FIG. 1 shows a block diagram of a wireless communication system to which the embodiment of the present application can be applied. The wireless communication system includes a terminal 11 and a network side device 12. Here, the terminal 11 may be called a terminal device or a user terminal (User Equipment, UE), and the terminal 11 may be a terminal side device such as a mobile phone, a tablet personal computer, a laptop computer (or called a notebook computer), a personal digital assistant (PDA), a palmtop computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile Internet device (MID), a wearable device, a vehicle user equipment (VUE), a pedestrian user equipment (PUE), etc., and the wearable device includes a bracelet, an earphone, glasses, etc. It should be noted that the specific type of the terminal 11 in the embodiment of the present application is not limited.The network side equipment 12 may be a base station or a core network, where the base station may be called an access point, a base transceiver station (BTS), a radio base station, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a B node, an evolved B node (eNB), a home B node, a home evolved B node, a wireless local area network (WLAN) access point, a WiFi node, a transmitting receiving point (TRP), or any other suitable term in the art, and as long as the same technical effect is achieved, the base station is not limited to a specific technical term, and it should be explained that in the embodiments of this application, only a base station in an NR system is taken as an example, but the specific type of the base station is not limited.

[0036] In an embodiment of the present application, the network function may be, for example, a first network function, a second network function, a third network function, a fourth network function, etc., and may be referred to as a network function entity.

[0037] In an embodiment of the present application, the network function may selectively include one of an Access Mobility Management Function (AMF), a Session Management Function (SMF), an Intermediate SMF (I-SMF), a User Plane Function (UPF), an Intermediate UPF (I-UPF), a Multicast and Broadcast Session Management Function (MB-SMF), a Multicast and Broadcast User Plane Function (MB-UPF), a Unified Data Management (UDM), a Unified Data Repository (UDR), a Home Subscriber Server (HSS), an Application Function (AF), a Network Exposure Function (NEF), an Unstructured Data Storage Function (UDSF), and the like, but is not limited thereto.

[0038] Alternatively, the information of the network functions may be referred to as network function information. For example, the information of the first network function may be referred to as first network function information, the information of the second network function may be referred to as second network function information, the information of the third network function may be referred to as third network function information, etc.

[0039] In the embodiment of the present application, decouple shared channel operation and individual channel operation are two kinds of operations.

[0040] Optionally, the following embodiments may incorporate any combination of MB-SMF, SMF, MB-UPF, UPF, I-SMF, I-UPF, etc.

[0041] Optionally, in the following embodiments, the interaction between MB-SMF and AMF is a non-unicast session operation instruction, which may include a non-unicast session shared resource operation instruction, a non-unicast business operation instruction, etc.

[0042] Optionally, in the following embodiments, the interaction between the MB-SMF and the SMF / I-SMF is a non-unicast session context operation instruction, which may include a non-unicast session unicast resource operation instruction, a non-unicast session connection operation instruction, a non-unicast business operation instruction, a non-unicast session shared resource operation instruction, etc.

[0043] Optionally, in the following embodiments, the interaction between SMF / I-SMF and AMF is a non-unicast session operation instruction, which may include a non-unicast session unicast resource operation instruction, a non-unicast session shared resource operation instruction, a non-unicast business operation instruction, etc.

[0044] Optionally, in the following embodiments, the interaction between the AMF and the RAN node is a non-unicast session shared resource operation instruction and / or a non-unicast session unicast resource operation instruction.

[0045] Optionally, in the following embodiments, the interaction between the AF and the MB-SMF or between the UE and the AMF is a non-unicast service operation indication.

[0046] Optionally, the non-unicast includes at least one of a multicast and a broadcast.

[0047] In the embodiment of the present application, the shared resource is used by a core network element to transmit some data to a base station, and the base station transmits the some data to a non-specific number of terminals.

[0048] In an embodiment of the present application, a unicast resource is used by a core network element to transmit a portion of data to a terminal, and the unicast resource may include any one of a resource used to transmit non-unicast data and a resource prepared for transmitting non-unicast data.

[0049] In an embodiment of the present application, for the MB-SMF, it can request the authorization information of the terminal / user from the UDM, where the authorization information is related to operator information and non-unicast function, or related to operator information and non-unicast service, or related to operator information and non-unicast session, and then the MB-SMF judges based on the authorization information whether to allow the user / terminal to perform the non-unicast function / non-unicast service / non-unicast session in the corresponding operator, and if yes, performs the subsequent operation, and if not, does not perform the subsequent operation.

[0050] The following describes in detail the method for non-unicast service according to the embodiment of the present application through specific embodiments and application scenarios thereof in conjunction with the drawings.

[0051] Referring to Figure 2, Figure 2 is a flowchart of a method for triggering a non-unicast service operation according to an embodiment of the present application, the method being performed by a first network function, which may include, but is not limited to, any one of MB-SMF (in the example shown in Figure 12), SMF / I-SMF (in the example shown in Figure 13), AMF (in the examples shown in Figures 14 and 15), etc. As shown in Figure 2, the method includes the following steps:

[0052] Step 21: Obtain non-unicast session information or non-unicast service information.

[0053] In this embodiment, the non-unicast includes at least one of a multicast and a broadcast.

[0054] Step 22: Perform a first operation based on the non-unicast session information or the non-unicast service information.

[0055] Optionally, the first operation may include at least one of sending a first non-unicast session operation instruction to a second network function and sending a second non-unicast session operation instruction or a non-unicast session context operation instruction to a third network function.

[0056] In one embodiment, the second network function is optionally an AMF when the first network function is an MB-SMF or an SMF / I-SMF, as in the examples shown in Figures 12 and 13. Or, the second network function is optionally an MB-SMF when the first network function is an AMF, as in the examples shown in Figures 14 and 15.

[0057] In another embodiment, when the first network function is a MB-SMF, the third network function is selectively an SMF or an I-SMF, as in the example shown in Figure 12. Or when the first network function is a SMF / I-SMF, the third network function is selectively an AMF, as in the example shown in Figure 13. Or when the first network function is an AMF, the third network function is selectively an SMF or an I-SMF, as in the examples shown in Figures 14 and 15. Or when the first network function is a NEF or MBSF, the third network function is selectively an MB-SMF, as in the examples shown in Figures 12 and 13.

[0058] Optionally, the first non-unicast session operation instruction comprises: The information may include at least one of a non-unicast session shared resource operation instruction, a non-unicast service operation instruction, non-unicast session information, information of the first network function, non-unicast Quality of Service (QoS) flow information, and a non-unicast session operation type.

[0059] Optionally, the second non-unicast session operation instruction comprises: The information may include at least one of a non-unicast session shared resource operation instruction, a non-unicast service operation instruction, a non-unicast session unicast resource operation instruction, non-unicast session information, information of the first network function, non-unicast QoS flow information, and a non-unicast session operation type.

[0060] In one alternative embodiment, the unicast resources may include, but are not limited to, Protocol Data Unit (PDU) Session resources and connection resources, which may include transmission resources between the MB-UPF and the UPF / I-UPF.

[0061] Optionally, the non-unicast session context manipulation indication may include: The command may include at least one of a non-unicast session shared resource operation instruction, a non-unicast task operation instruction, a non-unicast session unicast resource operation instruction, and a non-unicast session connection operation instruction.

[0062] Optionally, the non-unicast session shared resource operation instruction includes: The information may include at least one of a non-unicast session shared resource operation type, a non-unicast task operation instruction, non-unicast session information, information of the first network function, non-unicast QoS flow information, and a non-unicast session operation type.

[0063] Optionally, the non-unicast session unicast resource operation instruction includes: The information may include at least one of a non-unicast session unicast resource operation type, a non-unicast task operation instruction, non-unicast session information, information of the first network function, unicast QoS flow information, a non-unicast session operation type, and unicast session information.

[0064] In one embodiment, a first network function can perform a first operation upon receiving a report that data has arrived.

[0065] It is easy to understand that the method for triggering a non-unicast business operation in the embodiment of the present application can realize triggering of a non-unicast business operation when the shared transmission method and the unicast transmission method are simultaneously considered by executing a first operation based on the acquired non-unicast session information or non-unicast business information.

[0066] In an embodiment of the present application, optionally, the non-unicast session connection operation instruction is: indicating that a user plane node is to join; indicating that the user plane node is leaving; indicating that the user plane node is to hold; indicating that the user plane node is not joining; and indicating that the user plane node is not to leave; not instructing a user plane node to join; not instructing the user plane node to leave; The user plane node does not indicate that it holds the The user plane node does not indicate not to join; and Not instructing the user plane node to stay put; indicating that a control plane node is to join; indicating that the control plane node is leaving; and indicating that the control plane node is to hold; indicating that the control plane node is not joining; and indicating that the control plane node is not to leave; and The control plane node does not indicate the joining; and The control plane node does not indicate that it is leaving; The control plane node does not indicate that it is to hold The control plane node does not indicate not to join; and and not instructing the control plane node to stay put.

[0067] Optionally, performing the first operation, as described above, may include performing the first operation based on RAN capabilities.

[0068] Optionally, step 22 above further comprises: performing a first operation based on non-unicast session context information corresponding to the non-unicast session information; and performing a first operation based on context information of the non-unicast service corresponding to the non-unicast service information.

[0069] Optionally, performing the first operation above further comprises: When both RAN nodes support a non-unicast function, sending a first non-unicast session operation indication to a second network function; sending a first non-unicast session operation indication to a second network function when all RAN nodes serving the non-unicast service or the non-unicast session support a non-unicast function; sending a first non-unicast session operation indication to a second network function when the context information of the non-unicast task or the non-unicast session does not include third network function information; sending a first non-unicast session operation instruction to a second network function when the context information of the non-unicast task or the non-unicast session includes information of the second network function; and sending a first non-unicast session operation instruction to a third network function when the context information of the non-unicast task or session includes information of the second network function.

[0070] It should be noted that in this embodiment, the non-unicast service corresponds to the acquired non-unicast service information, and the non-unicast session corresponds to the acquired non-unicast session information.

[0071] Optionally, performing the first operation above further comprises: sending a second non-unicast session operation indication or a non-unicast session context operation indication to a third network function when none of the RAN nodes support the non-unicast function; sending a second non-unicast session operation indication or a non-unicast session context operation indication to a third network function when none of the RAN nodes serving the non-unicast service or the non-unicast session supports the non-unicast function; When none of the RAN nodes supports the non-unicast function, sending a second non-unicast session operation indication or a non-unicast session context operation indication to a third network function; sending a second non-unicast session operation indication or a non-unicast session context operation indication to a third network function when none of the RAN nodes serving the non-unicast service or the non-unicast session supports the non-unicast function; sending a second non-unicast session operation instruction or a non-unicast session context operation instruction to the third network function when the third network function information is included in the context information of the non-unicast task or the non-unicast session; sending a second non-unicast session operation instruction or a non-unicast session context operation instruction to a third network function when the second network function information is not included in the context information of the non-unicast task or the non-unicast session; sending a second non-unicast session operation instruction or a non-unicast session context operation instruction to the third network function when the context information of the non-unicast task or the non-unicast session includes information of the third network function; and performing at least one of sending a second non-unicast session operation instruction or a non-unicast session context operation instruction to a third network function when the second network function information is not included in the context information of the non-unicast task or the non-unicast session.

[0072] Further, the method in this embodiment includes: The method may further include sending the first non-unicast session operation instruction to a second network function or performing sending the first non-unicast session operation instruction to the second network function.

[0073] Optionally, before performing the first operation, the method in this embodiment further comprises: This may further include obtaining user information or terminal information.

[0074] Furthermore, performing the above-mentioned first operation may include performing the first operation based on user context information corresponding to the user information, or performing the first operation based on terminal context information corresponding to the terminal information.

[0075] Optionally, before performing the first operation, the method in this embodiment further comprises: This may further include obtaining user information or terminal information.

[0076] Furthermore, performing the first operation as described above includes: When a user or terminal does not have a unicast session (e.g., a PDU Session) associated with the non-unicast function, sending a first non-unicast session operation indication to the second network function; When a user or terminal does not have a unicast session (e.g., a PDU Session) related to a non-unicast task, sending a first non-unicast session operation indication to the second network function; and executing a first non-unicast session operation instruction to the second network function when the user or terminal does not have a unicast session (e.g., a PDU Session) associated with the non-unicast session.

[0077] It should be noted that the user corresponds to the obtained user information, and the terminal corresponds to the obtained terminal information.

[0078] Optionally, before performing the first operation, the method in this embodiment further comprises: This may further include obtaining user information or terminal information.

[0079] Furthermore, performing the first operation as described above includes: performing, when the user or terminal has a unicast session associated with the non-unicast function, sending a second non-unicast session operation indication or a non-unicast session context operation indication to a third network function; performing, when the user or terminal has a unicast session related to a non-unicast task, sending a second non-unicast session operation indication or a non-unicast session context operation indication to a third network function; and performing, when the user or terminal has a unicast session associated with the non-unicast session, sending a second non-unicast session manipulation indication or a non-unicast session context manipulation indication to a third network function. Here, the user corresponds to the user information, and the terminal corresponds to the terminal information, The non-unicast service corresponds to the non-unicast service information, and the non-unicast session corresponds to the non-unicast session information.

[0080] Further, the method in this embodiment includes: The method may further include performing sending a first non-unicast session operation indication to the second network function.

[0081] Optionally, the first non-unicast session operation instruction comprises: The information may further include at least one of user information, user list information, terminal information, terminal list information, first instruction information, RAN node information, RAN node list information, and unicast session information; Wherein, the first indication information is used to indicate at least one of non-unicast resource operation type information, no need for paging, and need for paging; The non-unicast resource operation type information includes: The resource operations include at least one of a shared resource operation and a unicast resource operation.

[0082] Optionally, the second non-unicast session operation instruction further comprises: may include at least one of user information, user list information, terminal information, terminal list information, second instruction information, and unicast session information; Wherein, the second indication information is used to indicate at least one of non-unicast resource operation type information, no need for paging, and need for paging; The non-unicast resource operation type information includes: The resource operations include at least one of a shared resource operation and a unicast resource operation.

[0083] Optionally, the non-unicast service operation instruction may include any one of a non-unicast start instruction, a non-unicast update instruction, a non-unicast stop instruction, a non-unicast join instruction, and a non-unicast leave instruction.

[0084] In an embodiment of the present application, before performing the first operation, in this embodiment, the method includes: The method may further include obtaining first authorization information, the first authorization information including at least one of user non-unicast function authorization information associated with the operator information, user non-unicast service authorization information associated with the operator information, and user non-unicast session authorization information associated with the operator information; The above-mentioned executing the first operation includes executing the first operation based on the first permission information.

[0085] Further, the method in this embodiment includes: The method may further include obtaining information of the third network function and unicast session information from a tenth network function according to user information and / or terminal information; The unicast session information includes: It includes at least one of a session management context identifier and a PDU session identifier.

[0086] Furthermore, before performing the first operation, the method in this embodiment further comprises: The method may further include obtaining user information and / or terminal information from a tenth network function according to the identifier information; Here, the identifier information is At least one of an IP address, a MAC address, a user identifier, and a terminal identifier is included; It should be noted that in this embodiment, the MB-SMF can request the authorization information of the terminal / user from the UDM, where the authorization information is related to operator information and non-unicast function, or related to operator information and non-unicast service, or related to operator information and non-unicast session. Then, the MB-SMF judges based on the authorization information whether the user / terminal is allowed to perform the non-unicast function / non-unicast service / non-unicast session in the corresponding operator, and if allowed, performs the subsequent operation; if not, does not perform the subsequent operation.

[0087] Referring to Figure 3, Figure 3 is a flowchart of a method for triggering a non-unicast service operation according to an embodiment of the present application, the method being performed by a second network function, which includes but is not limited to any one of AMF (in the examples shown in Figures 12 and 13), MB-SMF (in the examples shown in Figures 14 and 15), etc. As shown in Figure 3, the method includes the following steps:

[0088] Step 31: Perform a second operation based on at least one of the non-unicast capability of the first RAN node and the first indication information received from the first network function.

[0089] In one embodiment, the second network function is optionally an AMF when the first network function is an MB-SMF or an SMF / I-SMF, as in the examples shown in Figures 12 and 13. Or, the second network function is optionally an MB-SMF when the first network function is an AMF, as in the examples shown in Figures 14 and 15.

[0090] In this embodiment, the second operation is: The method may include at least one of sending a single paging message to the first RAN node, sending a non-unicast session shared resource operation instruction to the first RAN node, suspending sending of the non-unicast session shared resource operation instruction, sending a non-unicast session unicast resource operation instruction to the first RAN node, suspending sending of the non-unicast session unicast resource operation instruction, and sending a group paging message to the first RAN node.

[0091] Optionally, the first indication information is used to indicate at least one of non-unicast resource operation type information, no need for paging, and a need for paging.

[0092] Optionally, after receiving a failure indication sent by the first RAN node or a response time of the first RAN node times out, the method in this embodiment includes: The method may further include sending at least one of a non-unicast session shared resource operation instruction and a non-unicast session unicast resource operation instruction to a second RAN node.

[0093] Optionally, the method in this embodiment further comprises: The method may further include obtaining non-unicast capability information of the RAN node by receiving non-unicast related information from the RAN node to determine the non-unicast capability of the RAN node.

[0094] It is easy to understand that in this embodiment, the second operation performed by the second network function can realize triggering of a non-unicast business operation when the shared transmission mode and the unicast transmission mode are considered simultaneously.

[0095] Referring to Figure 4, Figure 4 is a flowchart of a method for triggering a non-unicast service operation according to an embodiment of the present application, the method being performed by a third network function, which includes but is not limited to any one of SMF or I-SMF (in the examples shown in Figures 12 to 15). As shown in Figure 4, the method includes the following steps:

[0096] Step 41: Information of the third network function, and Sending at least one of the user information, the terminal information, and the unicast session information to a tenth network function; The unicast session information includes: It includes at least one of a session management context identifier and a PDU session identifier.

[0097] Referring to Figure 5, Figure 5 is a flowchart of a method for triggering a non-unicast service operation according to an embodiment of the present application, the method being performed by an access side network equipment, the access side network equipment including but not limited to any one of a RAN node, an NR node (gNB, i.e., a 5G base station), etc. As shown in Figure 5, the method includes the following steps:

[0098] Step 51: Obtain a non-unicast session unicast resource operation instruction.

[0099] Step 52: Instruct a core network function that a node is joining and / or a node is leaving.

[0100] In the prior art, for non-unicast services, there is a possibility that the shared transmission method and the unicast transmission method coexist. In such a case, how to manage the multicast tree is a problem that needs to be solved urgently.

[0101] Referring to Figure 6, Figure 6 is a flowchart of a method for managing a non-unicast service multicast tree according to an embodiment of the present application, the method being performed by a fourth network function, which may include, but is not limited to, any one of MB-SMF (in the example shown in Figure 12), SMF / I-SMF (in the example shown in Figure 13), AMF (in the examples shown in Figures 14 and 15), etc. As shown in Figure 6, the method includes the following steps:

[0102] Step 61: Manage the multicast tree according to at least one of the non-unicast session connection operation instructions, the RAN capabilities, and the RAN node capabilities serving the non-unicast sessions or the non-unicast services.

[0103] Optionally, the non-unicast session connection operation indication is received from a fifth network function.

[0104] In one embodiment, when the fourth network function is a MB-SMF, the fifth network function is selectively an SMF or an I-SMF, as in the example shown in Figure 12. Or, when the fourth network function is a SMF / I-SMF, the fifth network function is selectively an AMF, as in the example shown in Figure 13. Or, when the fourth network function is an AMF, the fifth network function is selectively an SMF or an I-SMF, as in the examples shown in Figures 14 and 15.

[0105] Optionally, the multicast tree includes at least one of a control plane multicast tree and a user plane multicast tree.

[0106] It should be noted that the multicast tree adopts a tree-like structure, and each node in the multicast tree is used to manage a multicast transaction / service.

[0107] As can be seen, this embodiment can realize management of a multicast tree when considering a shared transmission mode and a unicast transmission mode simultaneously according to a non-unicast session connection operation instruction, a RAN capability, and / or a RAN node capability serving a non-unicast session or a non-unicast service.

[0108] In an embodiment of the present application, the non-unicast session connection operation instruction is: The indication may include at least one of a user plane node management indication and a control plane node management indication.

[0109] Optionally, the user plane node management instruction further comprises: indicating that a user plane node is to join; indicating that the user plane node is leaving; indicating that the user plane node is to hold; indicating that the user plane node is not joining; and indicating that the user plane node is not to leave; not instructing a user plane node to join; not instructing the user plane node to leave; The user plane node does not indicate that it holds the The user plane node does not indicate not to join; and Not instructing the user plane node to stay put; A non-unicast session shared resource operation instruction; and a non-unicast session unicast resource manipulation instruction.

[0110] Optionally, the control plane node management instruction comprises: indicating that a control plane node is to join; indicating that the control plane node is leaving; and indicating that the control plane node is to hold; indicating that the control plane node is not joining; and indicating that the control plane node is not to leave; and The control plane node does not indicate the joining; and The control plane node does not indicate that it is leaving; The control plane node does not indicate that it is to hold The control plane node does not indicate not to join; and The control plane node does not indicate that it will leave; A non-unicast session shared resource operation instruction; a non-unicast session unicast resource operation instruction;

[0111] Optionally, the method in this embodiment may further include acquiring RAN node information. The above-mentioned managing the multicast tree includes managing a control plane multicast tree. The managing of the control plane multicast tree includes: Subscribing RAN node information to a control plane multicast tree; and removing the RAN node information from the control plane multicast tree.

[0112] Optionally, the method in this embodiment may further include obtaining transmission endpoint information. The above-mentioned managing the multicast tree includes managing a user plane multicast tree. The managing of the user plane multicast tree includes: Subscribing transmission endpoint information to a user plane multicast tree; and removing the transmission endpoint information from the user plane multicast tree.

[0113] Here, the transmission endpoint information includes at least one of an IP address, a port, tunnel information, and node information.

[0114] In an embodiment of the present application, optionally, the above-mentioned managing the multicast tree may include managing a user plane multicast tree. The managing of the user plane multicast tree may include: Increasing a count of user plane nodes; and decreasing the count of user plane nodes.

[0115] Optionally, managing the multicast tree may include managing a control plane multicast tree. The managing of the control plane multicast tree may include: Increasing the count of control plane nodes; and decreasing the count of control plane nodes.

[0116] Optionally, the method in this embodiment further comprises: managing a user plane multicast tree according to user plane node management instructions; managing a control plane multicast tree according to user plane node management instructions; managing a control plane multicast tree according to control plane node management instructions; and managing the user plane multicast tree according to the control plane node management instructions.

[0117] Optionally, managing the multicast tree may include managing a control plane multicast tree. The managing of the control plane multicast tree may include: Subscribing the fifth network function information to a control plane multicast tree; and removing the fifth network function information from the control plane multicast tree.

[0118] Optionally, the method in this embodiment further comprises: managing a control plane multicast tree according to control plane node management instructions and information of a fifth network function; The method may further include at least one of: managing a control plane multicast tree according to a user plane node management instruction and information of a fifth network function.

[0119] Optionally, the method in this embodiment further comprises: controlling a user plane function to initiate data transmission; and controlling a user plane function to stop data transmission.

[0120] Optionally, the method in this embodiment further comprises: Controlling a user plane function to initiate data transmission when a first node joins a user plane multicast tree; and controlling a user plane function to stop data transmission when the last node leaves the user plane multicast tree.

[0121] Referring to Figure 7, Figure 7 is a flowchart of a method for managing a non-unicast service multicast tree according to an embodiment of the present application, the method being performed by a fifth network function, which includes but is not limited to any one of SMF / I-SMF (in the examples shown in Figures 12, 13 and 14), AMF (in the example shown in Figure 13), etc. As shown in Figure 7, the method includes the following steps:

[0122] Step 71: Send a non-unicast session connection operation instruction to a fourth network function according to the first information.

[0123] Here, the first information is a user plane function controlled by a fifth network function transmitting data to the first terminal using the non-unicast session unicast resources; stopping a user plane function controlled by a fifth network function from transmitting data to an end terminal using non-unicast session unicast resources; a fifth network function providing a service for the first terminal or user; and c) causing the fifth network function to cease providing service for the last terminal or user.

[0124] Optionally, the non-unicast session connection operation instruction further comprises: The instruction includes at least one of a user plane node management instruction and a control plane node management instruction.

[0125] For a detailed description of the user plane node management command and the control plane node management command, please refer to the embodiment of FIG. 6. No further description will be given here.

[0126] Thereby, by sending a non-unicast session connection operation instruction to the fourth network function, the fourth network function can realize management for the multicast tree.

[0127] Referring to Figure 8, Figure 8 is a flowchart of a method for associating a non-unicast service with a unicast session according to an embodiment of the present application, which is performed by a sixth network function, which may include, but is not limited to, any one of MB-SMF (in the example shown in Figure 12), SMF / I-SMF (in the example shown in Figure 13), AMF (in the examples shown in Figures 14 and 15), etc. As shown in Figure 8, the method includes the following steps:

[0128] Step 81: Send a first operation instruction to the seventh network function according to at least one of the RAN capability, the RAN node capability to serve the non-unicast service or non-unicast session, the first binding instruction from the seventh network function, and the second binding instruction from the eighth network function.

[0129] In one embodiment, the seventh network function is optionally an AMF when the sixth network function is an MB-SMF or an SMF / I-SMF, as in the examples shown in Figures 12 and 13. Or, the seventh network function is optionally an MB-SMF when the sixth network function is an AMF, as in the examples shown in Figures 14 and 15.

[0130] In another embodiment, when the sixth network function is a MB-SMF, the eighth network function is alternatively an SMF or an I-SMF, as in the example shown in Figure 12. Or, when the sixth network function is a SMF / I-SMF, the eighth network function is alternatively an AMF, as in the example shown in Figure 13. Or, when the sixth network function is an AMF, the eighth network function is alternatively an SMF or an I-SMF, as in the examples shown in Figures 14 and 15.

[0131] Optionally, the first binding indication comprises unicast session information; and The information includes at least one of a non-unicast service operation instruction, non-unicast session information, a non-unicast service operation type, a non-unicast session operation type, and a non-unicast instruction.

[0132] Furthermore, the first binding instruction includes: The information may further include at least one of user information and terminal information.

[0133] Optionally, the second binding instruction comprises: The first operation instruction includes at least one of: the user has already joined, the user has not left, the user has already left, the user has not joined, the operation has already started, the operation has not started, the operation has already stopped, the operation has not stopped, not allowing the user to join, allowing the user to join, not binding, binding, unbinding, and not unbinding. Optionally, the first operation instruction includes: The instruction includes at least one of an association instruction, a disassociation instruction, a non-association instruction, and a maintenance of association instruction.

[0134] Optionally, the method in this embodiment further comprises: The method may further include sending at least one of a non-unicast session unicast resource operation instruction, non-unicast session information, non-unicast business information, a non-unicast session shared resource operation instruction, a non-unicast session operation type, unicast session information, user information, and terminal information to the eighth network function.

[0135] Optionally, the step of transmitting the first operation instruction to the seventh network function includes: Any RAN node supports non-unicast or any RAN node serving a non-unicast service or session supports non-unicast; and This may include sending a not binding instruction to the seventh network function in accordance with at least one of a second binding instruction of the eighth network function, which is at least one of: a user has already joined, a user has not left, business has not started, business has already stopped, not allowing user joining, not binding, and unbinding.

[0136] Optionally, the step of transmitting the first operation instruction to the seventh network function includes: None of the RAN nodes support non-unicast, none of the RAN nodes serving the non-unicast service or non-unicast session support non-unicast, none of the RAN nodes support non-unicast, none of the RAN nodes serving the non-unicast service or non-unicast session support non-unicast, and This may include sending a binding instruction to the seventh network function in accordance with at least one of second binding instructions of the eighth network function, which are at least one of: user not joining, user already leaving, business already started, business not stopped, allowing user joining, binding, and not unbinding.

[0137] It is not difficult to understand that this embodiment makes it possible to associate a non-unicast task with a unicast session.

[0138] Referring to Figure 9, Figure 9 is a flowchart of a method for triggering a non-unicast service operation according to an embodiment of the present application, the method being performed by a seventh network function, which includes but is not limited to any one of AMF (in the examples shown in Figures 12 and 13), MB-SMF (in the examples shown in Figures 14 and 15), etc. As shown in Figure 9, the method includes the following steps:

[0139] Step 91: Obtain a first operation instruction for the sixth network function or a second operation instruction for the eighth network function.

[0140] Optionally, the first operation instruction is: The instruction includes at least one of an association instruction, a disassociation instruction, a non-association instruction, and a maintenance of association instruction.

[0141] Optionally, the second operation instruction is: The instruction includes at least one of an association instruction, a disassociation instruction, a non-association instruction, and a maintenance of association instruction.

[0142] Step 92: According to the first operation instruction or the second operation instruction, at least one of associating a unicast session with a non-unicast session, associating a unicast session with a non-unicast function, disassociating the unicast session with the non-unicast session, and disassociating the unicast session with the non-unicast function is performed.

[0143] Optionally, the method in this embodiment further comprises: may further include sending a first binding indication to the sixth network function based on at least one of a terminal capability, a RAN capability, and a RAN capability for serving a non-unicast service or a non-unicast session; Wherein, the first binding instruction includes unicast session information, and The information includes at least one of a non-unicast service operation instruction, non-unicast session information, a non-unicast service operation type, a non-unicast session operation type, and a non-unicast instruction.

[0144] Optionally, the method in this embodiment further comprises: Obtaining capability information of a terminal; and obtaining capability information of the RAN node.

[0145] In this way, the association operation between the non-unicast service and the unicast session can be performed rationally via the terminal capability information and / or the RAN node capability information.

[0146] Optionally, the method in this embodiment further comprises: sending a first binding indication to the sixth network function when the terminal does not support non-unicast; sending a first binding indication to the sixth network function when none of the RAN nodes support non-unicast, when none of the RAN nodes serving the non-unicast service or the non-unicast session support non-unicast, when none of the RAN nodes support non-unicast, or when none of the RAN nodes serving the non-unicast service or the non-unicast session support non-unicast; Wherein, the first binding instruction includes unicast session information, and The information includes at least one of a non-unicast service operation instruction, non-unicast session information, a non-unicast service operation type, a non-unicast session operation type, and a non-unicast instruction.

[0147] It is not difficult to understand that this embodiment makes it possible to associate a non-unicast task with a unicast session.

[0148] Referring to Figure 10, Figure 10 is a flowchart of a method for managing a non-unicast service multicast tree according to an embodiment of the present application, the method being performed by an eighth network function, which includes but is not limited to any one of SMF / I-SMF (in the examples shown in Figures 12, 13 and 14), AMF (in the example shown in Figure 15), etc. As shown in Figure 10, the method includes the following steps:

[0149] Step 101: Send a second operation instruction to a seventh network function according to at least one of: a terminal or user has a bound non-unicast session or a non-unicast service; and a terminal or user does not have a bound non-unicast session or a non-unicast service.

[0150] Optionally, the second operation instruction includes at least one of an association instruction, an unassociation instruction, a non-association instruction, and an association maintenance instruction.

[0151] Optionally, the method in this embodiment further comprises: obtaining a third binding indication of a sixth network function; and and managing a non-unicast service or a non-unicast session of the terminal according to the third binding instruction, or managing a non-unicast service or a non-unicast session of the user according to the third binding instruction. Here, the third binding instruction includes at least one of: the user has not joined; the user has already left; the service has already started; the service has not stopped; allowing the user to join; binding; and not unbinding.

[0152] It is not difficult to understand that this embodiment makes it possible to associate a non-unicast task with a unicast session.

[0153] Referring to Figure 11, Figure 11 is a flowchart of an authentication or authorization method for a non-unicast service according to an embodiment of the present application, the method being performed by a ninth network function, which includes but is not limited to any one of SMF / I-SMF (in the examples shown in Figures 14 and 15), MB-SMF (in the examples shown in Figures 14 and 15), etc. As shown in Figure 11, the method includes the following steps:

[0154] Step 111: Obtain non-unicast indication information.

[0155] In this embodiment, the non-unicast instruction information includes at least one of unicast session information, a non-unicast service operation instruction, a non-unicast session information, a non-unicast service operation type, a non-unicast session operation type, and a non-unicast instruction.

[0156] Step 112: Send an authentication or authorization message to the application server.

[0157] Optionally, the non-unicast indication information further includes at least one of user information, terminal information, and application server information; wherein the application server information is associated with the application server; The server ID includes at least one of an IP address and an application server identifier.

[0158] Optionally, the method in this embodiment further comprises: obtaining an authentication permission indication from a tenth network function according to the non-unicast indication information; The method may further include performing, in accordance with the authentication and authorization instruction, sending an authentication or authorization message to the application server.

[0159] Optionally, the method in this embodiment further comprises: The method may further include forwarding an authentication or authorization message between the application server and a terminal; Here, the terminal is associated with the user information or corresponds to the terminal information.

[0160] The present application will be described in detail below with reference to specific examples.

[0161] Example 1 In this embodiment 1, as shown in FIG. 12, the corresponding non-unicast business operation process may include the following steps:

[0162] Before executing the following steps, the SMF / I-SMF must obtain information about the SMF / I-SMF (e.g., identifier, IP address, IP address and port number, etc.) and At least one of user information (e.g., a user identifier), terminal information (e.g., a terminal identifier), a PDU session identifier, and a session management context identifier may be stored in a core network function.

[0163] The SMF / I-SMF may store the above information in the NEF / MBSF or UDM, or may store it in the UDR via the NEF.

[0164] Step 1: [Optionally] A content server sends a non-unicast service operation instruction to an MB-SMF for a certain non-unicast service, e.g., an MB Service request, which may include a start, restart, stop, and / or update request, and which may be sent to the MB-SMF via a NEF (MBSF). The request may include identifier information(s), e.g., an IP address, a MAC address, a user identifier, a terminal identifier, etc. The destination NEF or MBSF or MB-SMF can obtain user information and / or terminal information (which may be different from the user identifier provided by the content server) from the home NEF according to the identifier information, and the home NEF can obtain the user information and / or terminal information from the UDR and then send it to the destination NEF or MBSF or MB-SMF.

[0165] Step 2: [Optionally] The MB-UPF detects that data from the content server has arrived or that data is absent, for example, groupcast data Multicast Data.

[0166] Step 3: [Optionally] the MB-UPF reports data arrival or no data to the MB-SMF. A report of data arrival is considered as the non-unicast session being (re)started, a report of no data is considered as the non-unicast session being stopped.

[0167] Alternatively, to prevent the UE from entering connected state because it received a (re)initiation notification early, but then re-entering idle state because it has not received data, the MB-SMF may perform subsequent steps when it receives a report that data has arrived after receiving a (re)initiation request.

[0168] Step 4: [Optionally] the MB-SMF performs one or any combination of the following operations: - If this non-unicast service already has a subscribed member, when all RAN nodes support multicast function, or when all RAN nodes serving this non-unicast service or non-unicast session support non-unicast function, or when the non-unicast context information of the MB-SMF does not include SMF / I-SMF information (e.g., SMF ID, IP address), or when AMF information (e.g., AMF ID, IP address), or when this SMF / I-SMF information is not included, or when this AMF information is not included, the MB-SMF obtains the member information, e.g., stored in itself, or obtained from UDSF, or obtained from NEF. The MB-SMF obtains the serving AMF information of the member, e.g., obtained from UDM. The MB-SMF is used to send non-unicast session operation instructions to the AMF for members, e.g., sending Namf_Communication_N1N2MessageTransfer / Namf_Communication_NonUeN2MessageTransfer, send a multicast establishment instruction, e.g., for a (re)start operation, manage (e.g., establish) non-unicast session shared resources and / or convey a non-unicast service operation instruction, where the non-unicast session operation instruction includes one or a combination of non-unicast session information (e.g., identifier, non-unicast address), MB-SMF information (e.g., identifier, IP address), non-unicast QoS flow information (e.g., stream identifier, quality of service requirement, standard quality of service index), non-unicast service operation instruction (e.g., start or re-start), and non-unicast session operation type (e.g., establish / modify (update) / release), and may further include user information (e.g., SUPI, GPSI, GUTI), terminal information (e.g., IMEI), first instruction information, etc. The first indication is used to indicate AMF operation type information (e.g., a unicast resource association operation, a non-unicast resource association operation, or both), or to indicate that paging is not required or that paging is required.

[0169] -The MB-SMF sends a non-unicast session operation indication to the AMF, for example, a non-unicast session modification indication for a non-unicast service update operation, which is used to manage (e.g., modify) a non-unicast session shared resource and / or convey a non-unicast service operation indication, and the non-unicast session operation indication includes one or a combination of non-unicast session information, MB-SMF information, non-unicast QoS flow information, non-unicast service operation indication (e.g., update / start / stop), and non-unicast session operation type, and may further include first indication information, RAN node or RAN node list information, etc. The first indication information is used to indicate a type of AMF update operation (e.g., a unicast resource association operation, a non-unicast resource association operation, or both), or to indicate that paging is not required or that paging is required.

[0170] The MB-SMF sends a non-unicast session operation instruction to the AMF, for example, for a non-unicast service stop operation, a non-unicast release instruction is sent, which is used to manage (e.g., release) non-unicast session shared resources and / or convey a non-unicast service operation instruction, where the non-unicast session operation instruction includes one or a combination of non-unicast session information, MB-SMF information, a non-unicast service operation instruction, and a non-unicast session operation type, and may further include RAN node or RAN node list information, etc.

[0171] Step 5: [Optionally] if none of the RAN nodes support the non-unicast function, or none of the RAN nodes serving this non-unicast service or non-unicast session support the non-unicast function, or none of the RAN nodes support the non-unicast function, or none of the RAN nodes serving this non-unicast service or non-unicast session support the non-unicast function, or the non-unicast context information of the MB-SMF includes SMF / I-SMF information, or does not include AMF information, or includes information of this SMF / I-SMF, or does not include information of this AMF, the MB-SMF obtains an SMF / I-SMF serving the non-unicast session, for example from the non-unicast context information stored locally in the MB-SMF, or obtains one or any combination of SMF / I-SMF information corresponding to the user information and / or terminal information and a PDU session identifier, a session management context identifier by UDM or NEF, and performs one or any combination of the following operations (MB-SMF and SMF may be combined) for each SMF: - if it already has a subscribed member, sending a non-unicast context operation indication to the SMF or I-SMF, e.g. for a (re)start operation, a non-unicast context establishment indication is used to manage (e.g. establish) a non-unicast session context, the non-unicast context operation indication including one or a combination of non-unicast session information, MB-SMF information, non-unicast QoS flow information, non-unicast service operation indication, non-unicast session shared resource operation indication, non-unicast session unicast resource operation indication, non-unicast session operation type, and may further include first indication information, etc. The non-unicast session shared resource is used to transmit non-unicast data in a shared manner (the core network transmits some data to the base station, and the base station transmits the some data to a non-specific number of terminals, e.g., zero, one, or more than one), and the non-unicast session unicast resource is used to transmit non-unicast data in an exclusive manner (the core network transmits some data to one terminal, and the transmission path passes through the base station), and the non-unicast session unicast resource may be used to transmit non-unicast data or may be prepared to transmit non-unicast data. The non-unicast context operation indication may further include one or any combination of a session management context identifier, a PDU session identifier, user information, and terminal information.

[0172] - Send a non-unicast context operation indication to the SMF or I-SMF, for example for an update operation, to send a non-unicast context modification indication, which is used to manage (e.g., modify) a non-unicast session context, and the non-unicast context operation indication may include one or a combination of non-unicast session information, MB-SMF information, non-unicast QoS flow information, non-unicast service operation indication, and non-unicast session operation type, and may further include first indication information, etc. When the update operation is to add / delete users or terminals for a non-unicast service and establish / release media resources for these users or terminals, the non-unicast context operation indication may further include one or any combination of a session management context identifier, a PDU session identifier, user information, and terminal information.

[0173] - Send a non-unicast context operation indication to the SMF or I-SMF, for example, for a stop operation of a non-unicast service, send a non-unicast context release operation, and manage (e.g., release) a non-unicast session context, where the non-unicast context operation indication includes one or a combination of non-unicast session information, MB-SMF information, non-unicast QoS flow information, non-unicast service operation indication, non-unicast session shared resource operation indication, non-unicast session unicast resource operation indication, and non-unicast session operation type, and may further include first indication information, etc. The non-unicast context operation indication may further include one or any combination of a session management context identifier, a PDU session identifier, user information, and terminal information.

[0174] Step 6: [Optionally] The SMF / I-SMF obtains unicast session information (e.g., PDU session identifier, PDU session identifier, and user identifier) ​​related to the non-unicast session. The SMF generates unicast QoS flow information based on the non-unicast QoS flow information, e.g., when generating the unicast QoS flow information, the unicast session additionally supports the service of the data stream indicated for the non-unicast QoS flow information, or does not additionally support the service capability of the data stream indicated for the non-unicast QoS flow information.

[0175] Optionally, the SMF / I-SMF is used to send a non-unicast session operation indication to the AMF for each unicast session or user associated with the unicast session to manage (e.g., establish / release) the non-unicast session unicast resource, where the non-unicast session operation indication includes one or a combination of a non-unicast session unicast resource operation indication and a non-unicast session operation type, and may further include user information, terminal information, unicast session information, unicast QoS flow information, first indication information, etc. For example, for a (re)start operation of a non-unicast service, the first indication information may indicate an AMF paging user.

[0176] Optionally, the SMF / I-SMF may further send a non-unicast session operation instruction to the AMF for each user, for example, for a (re)start operation of a non-unicast service, a non-unicast session establishment instruction is sent to manage (e.g., establish) a non-unicast session shared resource and / or convey a non-unicast service operation instruction, where the non-unicast session operation instruction includes one or a combination of non-unicast session information, MB-SMF information, non-unicast QoS flow information, non-unicast session shared resource operation instruction, non-unicast service operation instruction, and non-unicast session operation type, and may further include user information, terminal information, first instruction information, etc. The non-unicast session operation instruction may be sent to the AMF in one call or message, and at this time, the non-unicast session shared resource operation instruction and the non-unicast session unicast resource operation instruction may be integrated into one non-unicast session resource operation instruction (e.g., Namf_Communication_N1N2Message Transfer).

[0177] Step 7a and Step 7b: [Optionally] When the UE is in an idle state, the AMF sends a paging message to the RAN node, and the RAN node pages the UE. The AMF can perform a sending operation of the paging message based on the first indication information.

[0178] Alternatively, the AMF may know the non-unicast capability of each RAN node through various non-unicast business operation processes, for example, know that the RAN node supports or does not support the non-unicast capability in steps 13 / 14 / 15 / 16, and perform a paging message sending operation based on the non-unicast capability of the RAN node, for example, depending on whether it receives non-unicast session related information (e.g., non-unicast session information, MB-SMF information). The AMF may further determine whether to send or not send a paging message based on the non-unicast capability information of the UE.

[0179] Step 8: The AMF performs one or any combination of the following operations on the non-unicast session operation indication: The AMF sends a non-unicast session shared resource operation instruction to a RAN node or a RAN node list corresponding to the RAN node information or the RAN node list information included in the non-unicast session operation instruction. The AMF can decide whether to send or not to send a non-unicast session shared resource operation instruction based on the first instruction. The AMF can decide whether to send or not to send a non-unicast session shared resource operation instruction, or to send a group paging message (i.e., to page a group of UEs or to page a group), or to use a paging policy (e.g., if the RAN node returns a failure indication or the waiting response times out, the AMF can send a non-unicast session shared resource operation instruction or a group paging message to other RAN nodes) based on the non-unicast capability of the RAN node and / or the first instruction.

[0180] The AMF sends a non-unicast session unicast resource operation instruction for the terminal UE corresponding to the terminal information or user information included in the non-unicast session operation instruction to the RAN node. The AMF can determine whether to send or not send a non-unicast session unicast resource operation instruction, or to send a group paging message or a single paging message (i.e., paging one UE), or to use a paging policy (e.g., if the RAN node returns a failure indication or the waiting response times out, the AMF can send a non-unicast session unicast resource operation instruction, a group paging message, or a single paging message to another RAN node) based on the non-unicast capability and / or the first instruction of the RAN node, and can determine the above action based on the UE state (e.g., idle state, connected state), for example, when in an idle state, send a group paging or a single paging, or when in a connected state, send a non-unicast session unicast resource operation instruction.

[0181] Step 9: [Optionally] The RAN node sends a non-unicast operation notification over the air interface, e.g., for a non-unicast session shared resource establishment indication, a non-unicast start notification, for a non-unicast session shared resource release indication, a non-unicast stop notification, and for a paging message, a paging indication.

[0182] Step 10: [Optionally] If the UE is in an idle state and receives a non-unicast operation notification, the UE can enter a connected state to receive non-unicast resource allocation, e.g., send a Service Request message; and if a paging indication is received, the UE enters a connected state to receive a non-unicast resource allocation, e.g., send a Service Request message.

[0183] Step 11: [Optionally] If the UE is in (or has entered) a connected state, the AMF associates a non-unicast session unicast resource with the UE by sending a non-unicast session unicast resource operation indication to the RAN node serving the UE. If the non-unicast session shared resource operation indication was not sent in step 8, the AMF further sends a non-unicast session shared resource operation indication to the RAN node.

[0184] Step 12: The RAN node performs one or any combination of the following operations: The RAN node configures air interface non-unicast transmission resources, for example by receiving a non-unicast session shared resource establishment indication, establishing air interface non-unicast transmission resources, receiving a non-unicast session shared resource update indication, updating the air interface non-unicast transmission resources, receiving a non-unicast session shared resource release indication, and removing the transmission resources associated with the non-unicast service.

[0185] The RAN node configures air interface unicast transmission resources, for example, receives a non-unicast session unicast resource operation instruction and performs a corresponding operation.

[0186] Step 13: [Optionally] The RAN node sends a non-unicast session shared resource operation response instruction to the MB-SMF via the AMF in response to the non-unicast session shared resource operation instruction, where the response instruction may include user information, terminal information, MB-SMF information, non-unicast session information, RAN node information, and transmission endpoint information (IP address, IP address and tunnel identifier, or tunnel identifier).

[0187] Step 14: [Optionally] the AMF forwards the non-unicast session shared resource operation response indication to the MB-SMF. The MB-SMF records the RAN node information and / or the transmission endpoint information in the non-unicast session context and / or increases the count of the user plane non-unicast tree path (e.g., increases by 1) used to manage the user plane non-unicast tree (i.e., the above information is the user plane non-unicast tree information in the context), or deletes the RAN node information and / or the transmission endpoint information from the non-unicast session context and / or decreases the count of the user plane non-unicast tree path (e.g., decreases by 1). The MB-SMF can perform the above operation based on the response indication, for example, records if the response indication is a response indication to establish an indication for a non-unicast session shared resource, and deletes if the response indication is a response indication to release an indication for a non-unicast session shared resource.

[0188] Step 15: [Optionally] If the non-unicast session unicast resource operation indication is received, the RAN node sends a non-unicast session unicast resource operation response indication to the AMF, and may include non-unicast session information, for example when the RAN node supports non-unicast functionality, the non-unicast session information may include an indication for a node to join or an indication for a node to leave, which may be used to indicate a user plane node to join or an indication for a user plane node to leave in the non-unicast session connection operation indication.

[0189] Step 16: [Optionally] The AMF forwards the non-unicast session unicast resource operation response indication to the SMF / I-SMF.

[0190] Step 17: [Optionally] When a non-unicast session unicast resource operation response instruction is received, if the response instruction includes non-unicast session information, it is determined that the non-unicast data is to be transmitted using the shared transmission method, and if not, it is determined that the non-unicast data is to be transmitted using the unicast method.

[0191] Optionally, the SMF / I-SMF sends a non-unicast context operation response indication or a non-unicast context operation indication, such as a non-unicast context update response indication, a non-unicast context release response indication, or a non-unicast context establishment indication, to the MB-SMF, and may include non-unicast session information, a non-unicast session connection operation indication, etc. The non-unicast session connection operation indication is used to manage connection operations of core network nodes serving the non-unicast session.

[0192] Furthermore, the SMF may send a non-unicast context operation response indication or a non-unicast context operation indication to the MB-SMF when it has not received a non-unicast session sharing / unicast resource operation response indication sent by the AMF, or may send a non-unicast context operation response indication or a non-unicast context operation indication after receiving a non-unicast session unicast resource operation response indication for all or part of the unicast sessions used to transmit non-unicast data. The non-unicast session connection operation indication may or may not indicate a user plane node to join / leave / keep / not join / not leave, and is used to manage the non-unicast tree of the user plane, i.e., the connection with the MB-UPF controlled by the MB-SMF, and may or may not indicate a control plane node to join / leave / keep / not join / not leave, and is used to manage the non-unicast tree management of the control plane, i.e., the connection with the MB-SMF. It may also be used to represent a non-unicast session connection operation indication without including specific information.

[0193] For example, if this UE is the first terminal using a unicast mode served by a UPF / I-UPF controlled by an SMF / I-SMF, the non-unicast session connection operation instruction may instruct the user plane to join; if this UE is the last terminal using a unicast mode served by a UPF / I-UPF controlled by an SMF / I-SMF, the non-unicast session connection operation instruction may instruct the user plane to leave; if this UE is the last terminal associated with a non-unicast session unicast resource managed by an SMF / I-SMF, the non-unicast session connection operation instruction may instruct the control plane to leave, or may not instruct the control plane to leave in order to reserve some context information for use in re-starting non-unicast business operations.

[0194] Step 18: [Optionally] The MB-SMF configures the MB-UPF to manage transmission resources for non-unicast data, e.g., for a (re)start operation, establish transmission resources and turn on data transmission, for a stop operation, release transmission resources and stop data transmission, and for an update operation, update the transmission resources.

[0195] Steps 19a, 19b, 19c, 19d: [Optionally] upon receiving non-unicast data, the MB-UPF forwards the non-unicast data via shared resources and / or unicast resources.

[0196] Step 20: The RAN node selects an air interface non-unicast transmission resource and / or an air interface unicast transmission resource to forward the non-unicast data.

[0197] Step 21: The RAN node forwards the non-unicast data through the selected air interface resource.

[0198] Example 2 In this embodiment 2, as shown in FIG. 13, the corresponding non-unicast business operation process may include the following steps:

[0199] Before executing the following steps, the SMF / I-SMF must obtain information about the SMF / I-SMF (e.g., identifier, IP address, IP address and port number, etc.) and At least one of user information, terminal information, a PDU session identifier, and a session management context identifier may be stored in a core network function.

[0200] The SMF / I-SMF may store the above information in the NEF / MBSF or UDM, or may store it in the UDR via the NEF.

[0201] Step 1: A content server sends a non-unicast service operation instruction to an MB-SMF for a certain non-unicast service, for example, an MB Service request, for example, a session update request, including member information, thereby requesting to update / establish / remove resources for the member, and this request may be sent to the MB-SMF via a NEF or MBSF. The request may include identifier information(s), for example, an IP address, a MAC address, a user identifier, a terminal identifier, etc. The destination NEF or MBSF or MB-SMF can obtain user information and / or terminal information (which may be different from the user identifier provided by the content server) to a home NEF according to the identifier information, and the home NEF can obtain the user information and / or terminal information from the UDR and then send it to the destination NEF or MBSF or MB-SMF.

[0202] Step 2: [Optionally] When all RAN nodes support non-unicast function, the MB-SMF is used to obtain AMF information serving users, e.g., from UDM, and send non-unicast session operation instructions (e.g., establish / release) to the AMF for each user, manage non-unicast session shared resources (e.g., establish / update / release) and / or convey non-unicast service operation instructions, where the non-unicast session operation instructions include one or a combination of non-unicast session information, MB-SMF information, non-unicast QoS flow information, non-unicast service operation instructions, and non-unicast session operation type, and may further include user information, terminal information, first instruction information, etc.

[0203] Step 3: [Optionally] If none of the RAN nodes support the non-unicast function, or if none of the RAN nodes support the non-unicast function, the MB-SMF obtains the SMF serving the user, for example based on the information obtained from the UDM, or obtained locally, or both (for example, the UDM obtains SMF1, and if there is SMF1 locally, selects SMF1, or if there are SMF2 and SMF1 locally and SMF2 is related to SMF1, selects SMF2), or obtains SMF / I-SMF information and PDU session identifier, session management context corresponding to the user information and / or terminal information by the UDM or NEF. The MB-SMF may obtain one or any combination of the identifiers and send (e.g., establish / update) a non-unicast context operation indication to each SMF for managing the non-unicast session context, the non-unicast context operation indication including one or a combination of non-unicast session information, MB-SMF information, non-unicast QoS flow information, non-unicast service operation indication, non-unicast session shared resource operation indication, non-unicast session unicast resource operation indication, and non-unicast session operation type, and may further include user information, user list information, session management context identifier, PDU session identifier, first indication information, etc. The MB-SMF may send a non-unicast context operation indication for each user to the SMF serving this user, and the non-unicast context operation indication includes one or a combination of non-unicast session information, MB-SMF information, non-unicast QoS flow information, non-unicast service operation indication, non-unicast session shared resource operation indication, non-unicast session unicast resource operation indication, and non-unicast session operation type, and may further include user information, first indication information, etc.

[0204] Step 4: [Optionally] the SMF obtains unicast session information related to the non-unicast session and user information. The SMF generates unicast QoS flow information based on the non-unicast QoS flow information, e.g., when generating the unicast QoS flow information, the unicast session further supports a service of a data stream indicated for the non-unicast QoS flow information, or does not further support a service capability of a data stream indicated for the non-unicast QoS flow information.

[0205] Optionally, the SMF / I-SMF sends a non-unicast session operation indication to the AMF for each unicast session or user associated with the unicast session, used to manage the non-unicast session unicast resources, where the non-unicast session operation indication includes one or a combination of a non-unicast session unicast resource operation indication and a non-unicast session operation type, and may further include user information, unicast session information, unicast QoS flow information, first indication information, etc. For example, for a (re)start operation of a non-unicast service, the first indication information may indicate an AMF paging user.

[0206] Optionally, the SMF / I-SMF may further send a non-unicast session operation instruction (e.g., Nsmf_Communication_N1N2MessageTransfer) to the AMF for each user, which is used to manage (e.g., establish) non-unicast session shared resources and / or convey a non-unicast service operation instruction, where the non-unicast session operation instruction includes one or a combination of non-unicast session information, MB-SMF information, non-unicast QoS flow information, non-unicast session shared resource operation instruction, non-unicast service operation instruction, and non-unicast session operation type, and may further include user information, terminal information, user list information, terminal list information, first instruction information, etc.

[0207] Step 5: [Optionally] When the UE is in an idle state, the AMF may wait for the UE to enter a connected state, or may page the UE to cause it to enter a connected state.

[0208] Step 6: When the UE is in a connected state (or enters a connected state), the AMF sends a non-unicast session shared resource operation indication for members (e.g., a Multicast Release request) to the RAN node serving the UE.

[0209] Step 7: [Optionally] When the UE is in (or enters) a connected state, the AMF manages (e.g., establishes / updates / releases) non-unicast session unicast resource operation indications (e.g., N2 session request) to the RAN node serving the UE.

[0210] Step 8: When the UE is in a connected state, the AMF instructs the UE to establish or release a non-unicast.

[0211] Step 9: [Optionally] The RAN node allocates air interface transmission resources according to the non-unicast session shared resource operation instruction or the non-unicast session unicast resource operation instruction.

[0212] Step 10: [Optionally] The RAN node instructs the AMF to send a non-unicast session shared resource operation response indication (e.g., Multicast Release response), which may include MB-SMF information, non-unicast session information, RAN node information, transmission endpoint information, etc.

[0213] Step 11: [Optionally] the AMF sends a non-unicast session shared resource operation response indication (e.g., Nsmf_MBSession_ReleaseSMContext) to the MB-SMF. The MB-SMF records the RAN node information and / or the transmission endpoint information in the non-unicast session context and / or increases (e.g., increases by 1) the count of the path used to manage the user plane non-unicast tree (i.e., the above information is the user plane non-unicast tree information in the context), or deletes the RAN node information and / or the transmission endpoint information from the non-unicast session context and / or decreases (e.g., decreases by 1) the count of the path. The MB-SMF can perform the above operation based on the response indication, for example, record if the response indication is a response indication to establish an indication for a non-unicast session shared resource, and delete if the response indication is a response indication to release an indication for a non-unicast session shared resource.

[0214] Step 12: [Optionally] The RAN node sends a non-unicast session unicast resource operation response indication (e.g., N2 Session Response) to the AMF, which may include unicast session information, non-unicast session information, etc. If the RAN node supports non-unicast capability, the non-unicast session information may be included, and the AMF may record the capability of the RAN node. The non-unicast session information may include an indication that a node is joining or an indication that a node is leaving, which may be used to indicate that a user plane node has joined or that a user plane node is leaving in the non-unicast session connection operation indication.

[0215] Step 13: [Optionally] The AMF sends a non-unicast session unicast resource operation response indication to the SMF, for example sending Nsmf_PDUSession_UpdateSMContext.

[0216] Step 14: [Optionally] The SMF sends a non-unicast session context operation response indication (e.g., Nsmf_MBSession_Release response) to the MB-SMF, such as a non-unicast context update response indication, a non-unicast context release response indication, etc., and may include non-unicast session information, a non-unicast session connection operation indication, etc. The non-unicast session connection operation indication is used to manage the connection operation of the core network node serving the non-unicast session. The SMF may send a non-unicast context operation response indication or a non-unicast context operation indication to the MB-SMF when it has not received a non-unicast session sharing / unicast resource operation response indication sent by the AMF, or may send a non-unicast context operation response indication or a non-unicast context operation indication after receiving a non-unicast session unicast resource operation response indication for all or part of the unicast sessions used to transmit non-unicast data. The non-unicast session connection operation instruction may or may not instruct the user plane to join / leave / retain / not join / not leave, and is used to manage the non-unicast tree of the user plane, i.e., the connection with the MB-UPF controlled by the MB-SMF, and may or may not instruct the control plane to join / leave / retain / not join / not leave, and is used to manage the non-unicast tree management of the control plane, i.e., the connection with the MB-SMF.

[0217] For example, if this UE is the first terminal using a unicast mode served by a UPF / I-UPF controlled by an SMF / I-SMF, the non-unicast session connection operation instruction may instruct the user plane to join; if this UE is the last terminal using a unicast mode served by a UPF / I-UPF controlled by an SMF / I-SMF, the non-unicast session connection operation instruction may instruct the user plane to leave; if this UE is the last terminal associated with a non-unicast session unicast resource managed by an SMF / I-SMF, the non-unicast session connection operation instruction may instruct the control plane to leave, or may not instruct the control plane to leave in order to reserve some context information for use in re-starting non-unicast business operations.

[0218] Step 15: [Optionally] Based on the above response instruction, the MB-SMF sends an N4 session modification instruction (i.e., N4 session modification) to the MB-UPF, configuring the MB-UPF to stop transmitting data to the corresponding UPF (and ultimately to the UE via the PDU session), where this stop operation may be based on a non-unicast session connection operation instruction.

[0219] Example 3 In this embodiment 3, as shown in FIG. 14, the corresponding non-unicast business operation process may include the following steps:

[0220] Step 1: The UE sends a non-unicast service operation instruction, for example, a non-unicast service join (e.g., MBS Session Join) / leave instruction, which may include non-unicast session information and non-unicast capability. The non-unicast capability may be sent by the UE to the AMF through a registration process or an activation process, for example, through a Registration Request or Service Request message.

[0221] Step 2: The AMF selects a PDU session that can be associated with the multicast operation, and the selection may be based on whether the UE already has an associated PDU session or does not have an associated PDU session, e.g., if so, select the associated PDU session, and if not, select one from the UE's PDU sessions. Note that the AMF may further select a PDU session to associate with the multicast operation based on whether the RAN node serving the non-unicast service or the RAN node serving the multicast service both support the multicast function, either none of them support the multicast function, or neither of them support the multicast function.

[0222] The AMF may decide whether to perform step 3 or step 4 based on whether the UE already has an associated PDU session, e.g., perform step 3 if the UE does not have an associated PDU session, or perform step 3 if the UE has an associated PDU session.

[0223] Step 3: [Optionally] The AMF may select one of the PDU sessions of the UE as a unicast session associated with the non-unicast. The AMF may further select based on whether the RAN node serving the non-unicast service or the RAN node serving the non-unicast service all support the non-unicast function, or none of them support the non-unicast function, or none of them support the non-unicast function. The AMF selects an MB-SMF, for example, selects an MB-SMF serving the non-unicast session, and sends to it a non-unicast session operation indication including second indication information (can be the second indication information even if it does not include specific information), where the second indication information is used to instruct binding / unbinding between the unicast session and the non-unicast session, and includes one or a combination of unicast session information, non-unicast service operation indication, non-unicast session information, non-unicast service operation type (e.g., join / leave), non-unicast session operation type, and non-unicast indication, and may further include user information and terminal information. The AMF may perform the above steps based on the UE having no unicast session associated with the non-unicast session.

[0224] The MB-SMF receives the non-unicast session operation instruction, and the MB-SMF can send an authentication or authorization request to the AF (e.g., by the MB-UPF to the AF), and forward the authorization or authentication message interacted between the AF and the UE (e.g., by the MB-UPF, the MB-SMF, the AMF, the RAN node, etc.), and realize the initiation of the authorization or authentication of the non-unicast business operation instruction for the UE. The MB-SMF can obtain the authentication authorization instruction of the UE, for example, from the UDM, and perform the above-mentioned authorization or authentication process based on the authentication authorization instruction. The second instruction may further include application server information, which may be an IP address or an application server identifier, and the MB-SMF identifies the AF that is going to send the authentication or authorization request based on the application server information.

[0225] Step 4: [Optionally] The AMF sends a non-unicast session operation instruction (e.g., Nsmf_PDUSession_UpdateSMContext) including a second instruction to the SMF / I-SMF. The AMF may perform the above steps based on the UE having a unicast session associated with the non-unicast.

[0226] The SMF / I-SMF receives the non-unicast session operation indication, and the SMF / I-SMF can send an authentication or authorization request to the AF (e.g., by UPF to the AF), forward the authorization or authentication message interacted between the AF and the UE (e.g., by UPF, SMF, AMF, RAN node, etc.), and realize the initiation of the authorization or authentication of the non-unicast service operation indication for the UE. The SMF / I-SMF can obtain the authentication authorization indication of the UE, for example, from the UDM, and perform the above-mentioned authorization or authentication process based on the authentication authorization indication. The second indication may further include application server information, which may be an IP address or an application server identifier, and the SMF / I-SMF identifies the AF that is going to send the authentication or authorization request based on the application server information.

[0227] When the SMF is different from the I-SMF, the I-SMF may further send unicast session related information to the SMF, including a session management context identifier, and may not include non-unicast session information.

[0228] Step 5: [Optionally] The SMF sends a non-unicast session context operation indication (e.g. Nsmf_PDUSession_Create) containing second indication information to the MB-SMF. If the unicast session is served by multiple SMFs, the associated SMF ID indicates other SMFs serving this unicast session. The SMF searches for MB-SMFs serving this non-unicast session, and if the search fails, it may select one MB-SMF.

[0229] Step 6: [Optionally] The MB-SMF may check whether this UE has already joined this non-unicast session, and if so, stop the execution of the subsequent steps.

[0230] The MB-SMF receives the non-unicast session context operation indication, and the MB-SMF can send an authentication or authorization request to the AF (e.g., by the MB-UPF to the AF), forward the authorization or authentication message interacted between the AF and the UE (e.g., by the MB-UPF, the MB-SMF, the SMF, the AMF, the RAN node, etc.), and realize the initiation of the authorization or authentication of the non-unicast business operation indication for the UE. The MB-SMF can obtain the authentication authorization indication of the UE, for example, from the UDM, and perform the above-mentioned authorization or authentication process based on the authentication authorization indication. The second indication may further include application server information, which may be an IP address or an application server identifier, and the MB-SMF identifies the AF that is going to send the authentication or authorization request based on the application server information.

[0231] Step 7: [Optionally] If the MB-SMF does not serve this non-unicast session, search for the MB-SMF serving this non-unicast session and pass the operation to this MB-SMF, e.g., query the NEF or UDSF. If there is no MB-SMF serving this non-unicast session (i.e., the first UE joined this non-unicast session), the NEF or UDSF returns an ID to query the network function. If there are multiple MB-SMFs serving this non-unicast session, one can be selected, e.g., the MB-SMF of a nearby UE.

[0232] Step 8: [Optionally] If any RAN node supports non-unicast function, this step and steps 9a and 9b may not be performed. If any RAN node does not support non-unicast function, MB-SMF may send a third instruction (can be a third instruction without specific information) to SMF / I-SMF, which is used to indicate a cause, such as user already joined / user not left / user already left / user not joined / service already started / service not started / service already stopped / service not stopped / not allow user to join / allow user to join / not bind / bind / unbind / not unbind, etc., and SMF / I-SMF binds or unbinds the unicast session and the non-unicast session based on not receiving the third instruction or based on the third instruction. The MB-SMF records the SMF / I-SMF information (e.g., identifier, IP address) in the non-unicast session context, which is used to manage the control plane non-unicast tree (i.e., the above information is the control plane non-unicast tree information in the context), or deletes the SMF / I-SMF information from the non-unicast session context. Based on the presence or absence of SMF / I-SMF in the non-unicast session context, the MB-SMF may decide to send one or a combination of non-unicast QoS flow information, non-unicast session information, non-unicast service operation indication, and non-unicast session operation type to the SMF / I-SMF.

[0233] Step 9a and Step 9b: [Optionally] the SMF generates unicast QoS flow information based on the non-unicast QoS flow information, for example, when generating the unicast QoS flow information, the unicast session may further additionally support the service of the data stream indicated for the non-unicast QoS flow information, or may not further support the service capability of the data stream indicated for the non-unicast QoS flow information. When the SMF is different from the I-SMF, the I-SMF performs the above operations after receiving the unicast session related information returned by the SMF.

[0234] Optionally, the SMF may send a fourth instruction (which may be via the MB-SMF) to the AMF, which is used to instruct the association / disassociation with the non-unicast session, and may include one or a combination of a non-unicast session unicast resource operation instruction, a non-unicast session information, a non-unicast service information, a non-unicast session shared resource operation instruction, and a non-unicast session operation type. The AMF associates the unicast session with the non-unicast session / associates the unicast session with the non-unicast session / disassociates the unicast session with the non-unicast session / disassociates the unicast session with the non-unicast session / disassociates the unicast session with the non-unicast session based on not receiving the fourth instruction or based on the fourth instruction.

[0235] Step 10: [Optionally] The MB-SMF sends a fourth indication (e.g., Nsmf_PDUSession_CreateSMContext Response) to the AMF.

[0236] Step 11: [Optionally] The AMF instructs the RAN node to perform a non-unicast session unicast resource operation.

[0237] Step 12: The MB-SMF sends a non-unicast session operation indication to the AMF.

[0238] Step 13: The AMF sends a non-unicast service operation response indication (e.g., MBS Session Join ACK) to the UE.

[0239] Step 14: The AMF sends a non-unicast session shared resource operation instruction (e.g., a Multicast Create request) to the RAN node.

[0240] Step 15: The RAN node configures air interface transmission resources according to the non-unicast session shared resource operation instruction or the non-unicast session unicast resource operation instruction.

[0241] Step 16: [Optionally] The RAN node sends a non-unicast session shared resource operation response indication (e.g., Multicast Create response) to the AMF, which may include MB-SMF information, non-unicast session information, RAN node information, transmission endpoint information, etc.

[0242] Step 17: [Optionally], the AMF sends a non-unicast session shared resource operation response indication (e.g., Nsmf_MBSession_CreateSMContext) to the MB-SMF. The MB-SMF records the RAN node information and / or the transmission endpoint information in the non-unicast session context and / or increases (e.g., increases by 1) the count of the non-unicast tree path of the user plane used to manage the non-unicast tree of the user plane (i.e., the above information is the non-unicast tree information of the user plane in the context), or deletes the RAN node information and / or the transmission endpoint information from the non-unicast session context and / or decreases (e.g., decreases by 1) the count of the non-unicast tree path of the user plane. The MB-SMF can perform the above operation based on the response indication, for example, records if the response indication is a response indication to establish an indication for the non-unicast session shared resource, and deletes if the response indication is a response indication to release an indication for the non-unicast session shared resource. The MB-SMF may further subscribe or remove AMF information (e.g., AMF ID or IP address) serving the corresponding RAN node to or from the control plane multicast tree.

[0243] Optionally, the MB-SMF subscribes RAN node information to the non-unicast session context.

[0244] Step 18: [Optionally] The RAN node sends a non-unicast session unicast resource operation response indication (e.g., N2 Session Response) to the AMF, which may include unicast session information, non-unicast session information, etc. If the RAN node supports non-unicast capability, the non-unicast session information may be included, and the AMF can record the capability of the RAN node. The non-unicast session information may include an indication that a node is joining or an indication that a node is leaving, which may be used to indicate that a user plane node has joined or that a user plane node is leaving in the non-unicast session connection operation indication.

[0245] Step 19: [Optionally] The AMF sends a non-unicast session unicast resource operation response indication (e.g., Nsmf_PDUSession_UpdateSMContext) to the SMF.

[0246] Step 20: [Optionally] The SMF sends a non-unicast session context operation response indication (e.g., Nsmf_MBSession_Create) to the MB-SMF, such as a non-unicast context update response indication, a non-unicast context release response indication, etc., and may include non-unicast session information, a non-unicast session connection operation indication, etc. The non-unicast session connection operation indication is used to manage a core network node connection operation serving a non-unicast session. The SMF may send a non-unicast context operation response indication or a non-unicast context operation indication to the MB-SMF when it has not received a non-unicast session sharing / unicast resource operation response indication sent by the AMF, or may send a non-unicast context operation response indication or a non-unicast context operation indication after receiving a non-unicast session unicast resource operation response indication for all or part of the unicast sessions used to transmit non-unicast data. The non-unicast session connection operation instruction may or may not instruct the user plane to join / leave / retain / not join / not leave, and is used to manage the non-unicast tree of the user plane, i.e., the connection with the MB-UPF controlled by the MB-SMF, and may or may not instruct the control plane to join / leave / retain / not join / not leave, and is used to manage the non-unicast tree management of the control plane, i.e., the connection with the MB-SMF.

[0247] For example, if this UE is the first terminal using a unicast mode served by a UPF / I-UPF controlled by an SMF / I-SMF, the non-unicast session connection operation instruction may instruct the user plane to join; if this UE is the last terminal using a unicast mode served by a UPF / I-UPF controlled by an SMF / I-SMF, the non-unicast session connection operation instruction may instruct the user plane to leave; if this UE is the last terminal associated with a non-unicast session unicast resource managed by an SMF / I-SMF, the non-unicast session connection operation instruction may instruct the control plane to leave, or may not instruct the control plane to leave in order to reserve some context information for use in re-starting non-unicast business operations.

[0248] Step 21: [Optionally] The MB-SMF sends an N4 session modification indication (i.e., N4 Session Modification) to the MB-UPF, configuring the MB-UPF to control the transmission of non-unicast data, e.g., turn on data transmission when the first node joins the non-unicast tree, and stop data transmission when the last node leaves the non-unicast tree.

[0249] Step 22: The MB-UPF receives non-unicast data (eg, Multicast data).

[0250] Steps 23a, 23b, 23c, 23d: [Optionally] upon receiving non-unicast data, the MB-UPF forwards the non-unicast data via shared resources and / or unicast resources.

[0251] Step 24: The RAN node selects an air interface non-unicast transmission resource and / or an air interface unicast transmission resource to forward the non-unicast data.

[0252] Step 25: The RAN node forwards the non-unicast data through the selected air interface resource.

[0253] Example 4 In this example 4, as shown in FIG. 15, the process of triggering a non-unicast service operation may include the following steps:

[0254] Step 1: The UE sends a non-unicast service operation instruction, for example, a non-unicast service join / leave (eg, MBS Session Leave) instruction, which may include non-unicast session information.

[0255] Here, the AMF may decide whether to perform step 2 or step 7 based on whether the UE already has an associated PDU session, for example, perform step 2 if the UE has an associated PDU session, or perform step 7 if the UE does not have an associated PDU session.

[0256] Step 2: [Optionally] The AMF sends a non-unicast session operation instruction (e.g., Nsmf_PDUSession_UpdateSMContext) including a second instruction to the SMF / I-SMF, where the second instruction is used to instruct binding / unbinding the unicast session and the non-unicast session, and includes one or a combination of unicast session information, non-unicast service operation instruction, non-unicast session information, non-unicast service operation type (e.g., join / leave), and non-unicast session operation type, and may further include user information and terminal information. The AMF may perform the above steps based on the UE having a unicast session associated with the non-unicast.

[0257] Step 3: [Optionally] The SMF / I-SMF may check whether this UE has already joined this non-unicast session and, if so, stop the execution of the subsequent steps.

[0258] The SMF / I-SMF receives the non-unicast session operation indication, and the SMF / I-SMF can send an authentication or authorization request to the AF (e.g., by UPF to the AF), forward the authorization or authentication message interacted between the AF and the UE (e.g., by UPF, SMF, AMF, RAN node, etc.), and realize the initiation of the authorization or authentication of the non-unicast service operation indication for the UE. The SMF can obtain the authentication authorization indication of the UE, for example from the UDM, and perform the above-mentioned authorization or authentication process based on the authentication authorization indication. The second indication may further include application server information, which may be an IP address or an application server identifier, and the SMF identifies the AF that is going to send the authentication or authorization request based on the application server information.

[0259] When the SMF is different from the I-SMF, the I-SMF may further send unicast session related information to the SMF, including a session management context identifier, and may not include non-unicast session information.

[0260] Step 4: [Optionally] The SMF sends a non-unicast session context manipulation indication (e.g. Nsmf_PDUSession_Update) containing a second indication to the MB-SMF. In case the unicast session is served by multiple SMFs, the associated SMF ID indicates the other SMFs serving this unicast session. The SMF searches for MB-SMFs serving this non-unicast session, and if the search fails, it may select one MB-SMF.

[0261] The MB-SMF receives the non-unicast session operation instruction, and the MB-SMF sends an authentication or authorization request to the AF (e.g., by the MB-UPF to the AF), and forwards the authorization or authentication message interacted between the AF and the UE (e.g., by the MB-UPF, the MB-SMF, the SMF, the AMF, the RAN node, etc.), and can realize the initiation of the authorization or authentication of the non-unicast business operation instruction for the UE. The MB-SMF can obtain the authentication authorization instruction of the UE, for example, from the UDM, and perform the above-mentioned authorization or authentication process based on the authentication authorization instruction. The second instruction may further include application server information, which may be an IP address or an application server identifier, and the MB-SMF identifies the AF that is going to send the authentication or authorization request based on the application server information.

[0262] Step 5: [Optionally] The SMF generates unicast QoS flow information based on the non-unicast QoS flow information, for example, when generating the unicast QoS flow information, the unicast session may further additionally support the service of the data stream indicated for the non-unicast QoS flow information, or may not additionally support the service capability of the data stream indicated for the non-unicast QoS flow information. When the SMF is different from the I-SMF, the I-SMF performs the above operation after receiving the unicast session related information returned by the SMF.

[0263] Optionally, the SMF may send a fourth instruction to the AMF (possibly via the MB-SMF), which is used to instruct the association / disassociation with the non-unicast session, and includes one or a combination of a non-unicast session unicast resource operation instruction, a non-unicast session information, a non-unicast service information, a non-unicast session shared resource operation instruction, and a non-unicast session operation type. The AMF associates the unicast session with the non-unicast session / associates the unicast session with the non-unicast session / disassociates the unicast session with the non-unicast session / disassociates the unicast session with the non-unicast session / disassociates the unicast session with the non-unicast session based on not receiving the fourth instruction or based on the fourth instruction.

[0264] Step 6: [Optionally] The AMF sends a non-unicast session unicast resource operation instruction to the RAN node, for example sending an N2 Session request.

[0265] Step 7: [Optionally] The AMF may select one of the UE's PDU sessions as a unicast session associated with the non-unicast. The AMF may further select based on whether the RAN node serving the non-unicast service or the RAN node serving the non-unicast service all support the non-unicast function, or none of them support the non-unicast function, or none of them support the non-unicast function, and / or based on the UE capabilities, e.g. the UE does not support the non-unicast function. The AMF selects an MB-SMF, for example, a serving MB-SMF for this non-unicast session, and sends to it a non-unicast session operation instruction (for example, Nsmf_PDUSession_CreateSMContext(MBS Session Leave)) including a second instruction, where the second instruction is used to instruct binding / unbinding between the unicast session and the non-unicast session, and includes one or a combination of unicast session information, non-unicast service operation instruction, non-unicast session information, non-unicast service operation type (for example, join / leave), and non-unicast session operation type, and may further include user information and terminal information. The AMF may perform the above steps based on the UE having no unicast session associated with the non-unicast.

[0266] Step 8: [Optionally] If the MB-SMF does not serve this non-unicast session, search for the MB-SMF serving this non-unicast session and pass the operation to this MB-SMF. If there are multiple MB-SMFs serving this non-unicast session, select one, e.g., select the MB-SMF of a nearby UE.

[0267] The MB-SMF receives the non-unicast session operation instruction, and the MB-SMF can send an authentication or authorization request to the AF (e.g., by the MB-UPF to the AF), and forward the authorization or authentication message interacted between the AF and the UE (e.g., by the MB-UPF, the MB-SMF, the AMF, the RAN node, etc.), and realize the initiation of the authorization or authentication of the non-unicast business operation instruction for the UE. The MB-SMF can obtain the authentication authorization instruction of the UE, for example, from the UDM, and perform the above-mentioned authorization or authentication process based on the authentication authorization instruction. The second instruction may further include application server information, which may be an IP address or an application server identifier, and the MB-SMF identifies the AF that is going to send the authentication or authorization request based on the application server information.

[0268] Step 9: The MB-SMF sends a non-unicast session operation instruction to the AMF, for example, Nsmf_communication_N1N2MessageTransfer.

[0269] Step 10: The AMF sends a non-unicast service operation response indication to the UE, for example, sending an MBSSession Leave ACK.

[0270] Step 11: The AMF sends a non-unicast session shared resource operation instruction to the RAN node, for example, sending a Multicast Release request.

[0271] Step 12: The RAN node configures air interface transmission resources according to the non-unicast session shared resource operation instruction or the non-unicast session unicast resource operation instruction.

[0272] Step 13: [Optionally] The RAN node instructs the AMF to send a non-unicast session shared resource operation response indication (e.g., Multicast Release response), which may include MB-SMF information, non-unicast session information, RAN node information, transmission endpoint information, etc.

[0273] Step 14: [Optionally] the AMF sends a non-unicast session shared resource operation response indication (e.g., Nsmf_MBSession_ReleaseSMContext) to the MB-SMF. The MB-SMF records the RAN node information and / or the transmission endpoint information in the non-unicast session context and / or increases the count of the path (e.g., increases by 1) and is used to manage the user plane non-unicast tree (i.e., the above information is the user plane non-unicast tree information in the context), or deletes the RAN node information and / or the transmission endpoint information from the non-unicast session context and / or decreases the count of the path (e.g., decreases by 1). The MB-SMF can perform the above operation based on the response indication, for example, records if the response indication is a response indication to establish an indication for a non-unicast session shared resource, and deletes if the response indication is a response indication to release an indication for a non-unicast session shared resource.

[0274] Step 15: [Optionally] The RAN node sends a non-unicast session unicast resource operation response indication (e.g., N2 Session response) to the AMF, which may include unicast session information, non-unicast session information, etc. If the RAN node supports non-unicast capability, the non-unicast session information may be included, and the AMF can record the capability of the RAN node. The non-unicast session information may include an indication that a node is joining or an indication that a node is leaving, which may be used to indicate that a user plane node has joined or that a user plane node is leaving in the non-unicast session connection operation indication.

[0275] Step 16: [Optionally] The AMF sends a non-unicast session unicast resource operation response indication to the SMF, for example sending Nsmf_PDUSession_UpdateSMContext.

[0276] Step 17: [Optionally] The SMF sends a non-unicast session context operation response indication, such as a non-unicast context update response indication, a non-unicast context release response indication, etc., to the MB-SMF, and may include non-unicast session information, a non-unicast session connection operation indication, etc. The non-unicast session connection operation indication is used to manage the connection operation of the core network node serving the non-unicast session. The SMF can send a non-unicast context operation response indication or a non-unicast context operation indication to the MB-SMF when it has not received a non-unicast session sharing / unicast resource operation response indication sent by the AMF, or can send a non-unicast context operation response indication or a non-unicast context operation indication after receiving a non-unicast session unicast resource operation response indication for all or part of the unicast sessions used to transmit non-unicast data. The non-unicast session connection operation indication may or may not indicate that the user plane joins / leaves / keeps / does not join / does not leave, and is used to manage the non-unicast tree of the user plane, i.e., the connection with the MB-UPF controlled by the MB-SMF, and may or may not indicate that the control plane joins / leaves / keeps / does not join / does not leave, and is used to manage the non-unicast tree management of the control plane, i.e., the connection with the MB-SMF. The MB-SMF increases (e.g., increases by 1) the count of the non-unicast tree path of the user plane, or decreases (e.g., decreases by 1) the count of the non-unicast tree path of the control plane, or increases (e.g., increases by 1) the count of the non-unicast tree path of the control plane, or decreases (e.g., decreases by 1) the count of the non-unicast tree path of the control plane, or increases the record of the SMF / I-SMF information, or deletes the SMF / I-SMF information.

[0277] For example, if this UE is the first terminal using a unicast mode served by a UPF / I-UPF controlled by an SMF / I-SMF, the non-unicast session connection operation instruction may instruct the user plane to join; if this UE is the last terminal using a unicast mode served by a UPF / I-UPF controlled by an SMF / I-SMF, the non-unicast session connection operation instruction may instruct the user plane to leave; if this UE is the last terminal associated with a non-unicast session unicast resource managed by an SMF / I-SMF, the non-unicast session connection operation instruction may instruct the control plane to leave, or may not instruct the control plane to leave in order to reserve some context information for use in re-starting non-unicast business operations.

[0278] Step 18: [Optionally] The MB-SMF initiates an N4 Session Modification to configure the MB-UPF to control the transmission of non-unicast data, e.g., turn on data transmission when the first node joins the non-unicast tree and stop data transmission when the last node leaves the non-unicast tree.

[0279] It should be noted that the execution body of the non-unicast task operation triggering method according to the embodiment of the present application can be a non-unicast task operation triggering device, or a control module for executing the non-unicast task operation triggering method in the non-unicast task operation triggering device. In the embodiment of the present application, the non-unicast task operation triggering device executes the non-unicast task operation triggering method as an example, and the non-unicast task operation triggering device according to the embodiment of the present application is described.

[0280] Please refer to Figure 16, which is a structural diagram of a non-unicast task operation trigger device according to an embodiment of the present application used in the first network function. As shown in Figure 16, the non-unicast task operation trigger device 160 includes: A first obtaining module 161 for obtaining non-unicast session information or non-unicast service information; a first execution module 162 for executing a first operation based on the non-unicast session information or the non-unicast service information; wherein the first operation includes at least one of sending a first non-unicast session operation instruction to a second network function, and sending a second non-unicast session operation instruction or a non-unicast session context operation instruction to a third network function; wherein the first non-unicast session operation instruction is at least one of a non-unicast session shared resource operation instruction, a non-unicast task operation instruction, non-unicast session information, information of the first network function, non-unicast quality of service (QoS) flow information, and a non-unicast session operation type; wherein the second non-unicast session operation instruction is: at least one of a non-unicast session shared resource operation instruction, a non-unicast task operation instruction, a non-unicast session unicast resource operation instruction, non-unicast session information, information of the first network function, non-unicast QoS flow information, and a non-unicast session operation type; Wherein, the non-unicast session context operation instruction is at least one of a non-unicast session shared resource operation instruction, a non-unicast task operation instruction, a non-unicast session unicast resource operation instruction, and a non-unicast session connection operation instruction; Here, the non-unicast session shared resource operation instruction is: at least one of a non-unicast session shared resource operation type, a non-unicast task operation instruction, non-unicast session information, information of the first network function, non-unicast QoS flow information, and a non-unicast session operation type; Wherein, the non-unicast session unicast resource operation instruction is: At least one of a non-unicast session unicast resource operation type, a non-unicast task operation instruction, non-unicast session information, information of the first network function, unicast QoS flow information, a non-unicast session operation type, and unicast session information; Here, the non-unicast includes at least one of a multicast and a broadcast.

[0281] Optionally, the non-unicast session connection operation instruction further comprises: indicating that a user plane node is to join; indicating that the user plane node is leaving; indicating that the user plane node is to hold; indicating that the user plane node is not joining; and indicating that the user plane node is not to leave; not instructing a user plane node to join; not instructing the user plane node to leave; The user plane node does not indicate that it holds the The user plane node does not indicate not to join; and Not instructing the user plane node to stay put; indicating that a control plane node is to join; indicating that the control plane node is leaving; and indicating that the control plane node is to hold; indicating that the control plane node is not joining; and indicating that the control plane node is not to leave; and The control plane node does not indicate the joining; and The control plane node does not indicate that it is leaving; The control plane node does not indicate that it is to hold The control plane node does not indicate not to join; and and not instructing the control plane node not to leave.

[0282] Optionally, the first execution module 162 specifically: Based on the RAN capabilities, it is used to perform the first operation.

[0283] Optionally, the first execution module 162 specifically: performing the first operation based on non-unicast session context information corresponding to the non-unicast session information; and performing the first operation based on context information of a non-unicast service corresponding to the non-unicast service information.

[0284] Optionally, the first execution module 162 specifically: sending the first non-unicast session operation indication to the second network function when both RAN nodes support a non-unicast function; sending the first non-unicast session operation indication to the second network function when all RAN nodes serving the non-unicast service or the non-unicast session support a non-unicast function; sending the first non-unicast session operation instruction to the second network function when third network function information is not included in context information of a non-unicast task or a non-unicast session; sending the first non-unicast session operation instruction to a second network function when context information of the non-unicast task or session includes information of the second network function; and sending the first non-unicast session operation instruction to the third network function when the context information of the non-unicast task or the non-unicast session includes information of a second network function; Here, the non-unicast service corresponds to the non-unicast service information, and the non-unicast session corresponds to the non-unicast session information.

[0285] Optionally, the first execution module 162 specifically: When none of the RAN nodes support a non-unicast function, sending the second non-unicast session operation indication or a non-unicast session context operation indication to the third network function; sending the second non-unicast session operation indication or non-unicast session context operation indication to the third network function when none of the RAN nodes serving the non-unicast service or the non-unicast session supports a non-unicast function; When none of the RAN nodes supports a non-unicast function, sending the second non-unicast session operation indication or a non-unicast session context operation indication to the third network function; sending the second non-unicast session operation indication or the non-unicast session context operation indication to the third network function when none of the RAN nodes serving the non-unicast service or the non-unicast session supports a non-unicast function; sending the second non-unicast session operation instruction or the non-unicast session context operation instruction to the third network function when third network function information is included in the context information of the non-unicast task or the non-unicast session; When the context information of the non-unicast task or the non-unicast session does not include second network function information, sending the second non-unicast session operation instruction or the non-unicast session context operation instruction to the third network function; sending the second non-unicast session operation instruction or the non-unicast session context operation instruction to the third network function when the context information of the non-unicast task or the non-unicast session includes information of the third network function; and executing, when the second network function information is included in the context information of a non-unicast task or a non-unicast session, sending the second non-unicast session operation instruction or the non-unicast session context operation instruction to the third network function; Here, the non-unicast service corresponds to the non-unicast service information, and the non-unicast session corresponds to the non-unicast session information.

[0286] Optionally, the first execution module 162 further comprises: It is used to perform sending a first non-unicast session operation instruction to the second network function, or sending the first non-unicast session operation instruction to the second network function.

[0287] Optionally, the first acquisition module 161 is further used to acquire user information or terminal information; The first execution module 162 is further used to execute the first operation based on user context information corresponding to the user information, or to execute the first operation based on terminal context information corresponding to the terminal information.

[0288] Optionally, the first acquisition module 161 is further used to acquire user information or terminal information; The first execution module 162 further comprises: performing sending the first non-unicast session operation indication to the second network function when a user or terminal has no unicast session associated with the non-unicast function; performing sending the first non-unicast session operation instruction to the second network function when a user or terminal does not have a unicast session related to a non-unicast task; and performing sending the first non-unicast session operation indication to the second network function when a user or terminal does not have a unicast session associated with the non-unicast session; Here, the user corresponds to the user information, and the terminal corresponds to the terminal information, The non-unicast service corresponds to the non-unicast service information, and the non-unicast session corresponds to the non-unicast session information.

[0289] Optionally, the first acquisition module 161 is further used to acquire user information or terminal information; The first execution module 162 further comprises: performing, when a user or terminal has a unicast session associated with a non-unicast function, sending the second non-unicast session operation indication or a non-unicast session context operation indication to the third network function; When a user or terminal has a unicast session related to a non-unicast task, sending the second non-unicast session operation indication or the non-unicast session context operation indication to the third network function; and performing, when a user or terminal has a unicast session associated with the non-unicast session, sending the second non-unicast session operation indication or a non-unicast session context operation indication to the third network function; Here, the user corresponds to the user information, and the terminal corresponds to the terminal information, The non-unicast service corresponds to the non-unicast service information, and the non-unicast session corresponds to the non-unicast session information.

[0290] Optionally, the first executing module 162 is further used to execute sending the first non-unicast session operation instruction to the second network function.

[0291] Optionally, the first non-unicast session operation instruction comprises: Further including at least one of user information, user list information, terminal information, terminal list information, first instruction information, RAN node information, RAN node list information, and unicast session information; Wherein, the first indication information is used to indicate at least one of non-unicast resource operation type information, no need for paging, and need for paging; The non-unicast resource operation type information includes: The resource operations include at least one of a shared resource operation and a unicast resource operation.

[0292] Optionally, the second non-unicast session operation instruction further comprises: Further including at least one of user information, user list information, terminal information, terminal list information, first instruction information, and unicast session information; Wherein, the second indication information is used to indicate at least one of non-unicast resource operation type information, no need for paging, and need for paging; The non-unicast resource operation type information includes: The resource operations include at least one of a shared resource operation and a unicast resource operation.

[0293] Optionally, the non-unicast service operation instruction includes any one of a non-unicast start instruction, a non-unicast update instruction, a non-unicast stop instruction, a non-unicast join instruction, and a non-unicast leave instruction.

[0294] Optionally, the first execution module 162 is further adapted to execute the first operation upon receiving a report that data has arrived.

[0295] Optionally, the first obtaining module 161 is further used for obtaining first authorization information, the first authorization information including at least one of user non-unicast function authorization information associated with operator information, user non-unicast business authorization information associated with operator information, and user non-unicast session authorization information associated with operator information; The first execution module 162 is further used for executing the first operation according to the first permission information.

[0296] Optionally, the non-unicast transaction operation trigger device 160 further includes an eighth acquisition module; The eighth acquiring module 163 is used for acquiring the information of the third network function and unicast session information from the tenth network function according to the user information and / or the terminal information; The unicast session information includes: It includes at least one of a session management context identifier and a PDU session identifier.

[0297] Optionally, the non-unicast transaction operation trigger device 160 further includes a ninth acquisition module; The ninth obtaining module 164 is used for obtaining user information and / or terminal information from a tenth network function according to the identifier information before performing the first operation; Here, the identifier information is At least one of an IP address, a MAC address, a user identifier, and a terminal identifier is included; It can be understood that in the embodiment of the present application, the non-unicast business operation trigger device 160 can realize each process of the embodiment of the method shown in Figure 2 above, and achieve the same technical effect. In order to avoid repetition, it will not be described further here.

[0298] Please refer to Figure 17, which is a structural diagram of a non-unicast task operation trigger device according to an embodiment of the present application used for the second network function. As shown in Figure 17, the non-unicast task operation trigger device 170 includes: a second execution module 171 for performing a second operation based on at least one of the non-unicast capability of the first RAN node and the first indication information received from the first network function; Here, the second operation is at least one of: sending a single paging message to the first RAN node; sending a non-unicast session shared resource operation instruction to the first RAN node; suspending sending of the non-unicast session shared resource operation instruction; sending a non-unicast session unicast resource operation instruction to the first RAN node; suspending sending of the non-unicast session unicast resource operation instruction; and sending a group paging message to the first RAN node; The first indication information is used to indicate at least one of non-unicast resource operation type information, no need for paging, and need for paging; The non-unicast includes at least one of a multicast and a broadcast.

[0299] Optionally, the second execution module 171 further comprises, after receiving a failure indication sent by the first RAN node or a response time of the first RAN node times out: It is used to send at least one of a non-unicast session shared resource operation instruction and a non-unicast session unicast resource operation instruction to a second RAN node.

[0300] Optionally, the non-unicast service operation trigger device 170 may include: It further includes a second acquiring module for acquiring non-unicast capability information of the RAN node by receiving non-unicast related information from the RAN node.

[0301] It can be understood that in the embodiment of the present application, the non-unicast business operation trigger device 170 can realize each process of the embodiment of the method shown in Figure 3 above, and achieve the same technical effect. In order to avoid repetition, it will not be described further here.

[0302] Please refer to Figure 18, which is a structural diagram of a non-unicast task operation trigger device according to an embodiment of the present application used in the third network function. As shown in Figure 18, the non-unicast task operation trigger device 180 includes: information on the third network function; and a third sending module 181 for sending at least one of user information, terminal information, and unicast session information to a tenth network function; The unicast session information includes: It includes at least one of a session management context identifier and a PDU session identifier.

[0303] It can be understood that in the embodiment of the present application, the non-unicast business operation trigger device 180 can realize each process of the embodiment of the method shown in Figure 4 above, and achieve the same technical effect. In order to avoid repetition, it will not be described further here.

[0304] Referring to Figure 19, Figure 19 is a structural diagram of a triggering device for non-unicast task operation according to an embodiment of the present application, which is used in an access side network function. As shown in Figure 19, the triggering device for non-unicast task operation 190 includes: a fifth obtaining module 191 for obtaining a non-unicast session unicast resource operation instruction; and a fourth execution module 192 for instructing a core network function that a node is joining and / or a node is leaving.

[0305] It can be understood that in the embodiment of the present application, the non-unicast business operation trigger device 190 can realize each process of the embodiment of the method shown in Figure 5 above, and achieve the same technical effect. In order to avoid repetition, no further description will be given here.

[0306] Referring to Figure 20, it is a structural diagram of a management device for a non-unicast service multicast tree according to an embodiment of the present application used for the fourth network function. As shown in Figure 20, the management device 200 for a non-unicast service multicast tree includes: a non-unicast session connection operation instruction received from a fifth network function; RAN capabilities; a first management module 201 for managing a multicast tree according to at least one of a non-unicast session or a RAN node capability of serving a non-unicast service; Here, the multicast tree is The multicast tree includes at least one of a control plane multicast tree and a user plane multicast tree.

[0307] Optionally, the non-unicast session connection operation instruction further comprises: The instruction includes at least one of a user plane node management instruction and a control plane node management instruction.

[0308] Optionally, the user plane node management instruction further comprises: indicating that a user plane node is to join; indicating that the user plane node is leaving; indicating that the user plane node is to hold; indicating that the user plane node is not joining; and indicating that the user plane node is not to leave; not instructing a user plane node to join; not instructing the user plane node to leave; The user plane node does not indicate that it holds the The user plane node does not indicate not to join; and Not instructing the user plane node to stay put; A non-unicast session shared resource operation instruction; a non-unicast session unicast resource operation instruction; and / or The control plane node management instruction includes: indicating that a control plane node is to join; indicating that the control plane node is leaving; and indicating that the control plane node is to hold; indicating that the control plane node is not joining; and indicating that the control plane node is not to leave; and The control plane node does not indicate the joining; and The control plane node does not indicate that it is leaving; The control plane node does not indicate that it is to hold The control plane node does not indicate not to join; and The control plane node does not indicate that it will leave; A non-unicast session shared resource operation instruction; a non-unicast session unicast resource operation instruction;

[0309] Optionally, the management device 200 of this non-unicast service multicast tree: Further comprising a third acquiring module for acquiring RAN node information; Wherein, the first management module 201 is used for managing a control plane multicast tree, and the management of the control plane multicast tree includes: Subscribing the RAN node information to the control plane multicast tree; and removing the RAN node information from the control plane multicast tree.

[0310] Optionally, the third acquisition module further comprises: Used to obtain transmission endpoint information, The first management module 201 is used for managing a user plane multicast tree, and the managing of the user plane multicast tree includes: subscribing the transmission endpoint information to the user plane multicast tree; and removing the transmission endpoint information from the user plane multicast tree; Here, the transmission endpoint information is: It includes at least one of an IP address, a port, tunnel information, and node information.

[0311] Optionally, the first management module 201 is used to manage a user plane multicast tree, and the managing of the user plane multicast tree includes: Increasing a count of user plane nodes; and decreasing the count of user plane nodes.

[0312] and / or Optionally, the first management module 201 is used to manage a control plane multicast tree, and the managing of the control plane multicast tree includes: Increasing the count of control plane nodes; and decreasing the count of control plane nodes.

[0313] Optionally, the first management module 201 further comprises: managing the user plane multicast tree in accordance with the user plane node management instructions; managing the control plane multicast tree in accordance with the user plane node management instructions; managing the control plane multicast tree in accordance with the control plane node management instructions; and managing the user plane multicast tree in accordance with the control plane node management instructions.

[0314] Optionally, the first management module 201 is used to manage a control plane multicast tree, and the managing of the control plane multicast tree includes: Subscribing information of the fifth network function to the control plane multicast tree; and removing information of the fifth network function from the control plane multicast tree.

[0315] Optionally, the first management module 201 further comprises: managing the control plane multicast tree according to the control plane node management directive and information of the fifth network function; and managing the control plane multicast tree according to the user plane node management instructions and the information of the fifth network function.

[0316] Optionally, the first management module 201 further comprises: controlling a user plane function to initiate data transmission; and controlling the user plane function to stop data transmission.

[0317] Optionally, the first management module 201: Controlling a user plane function to initiate data transmission when a first node joins a user plane multicast tree; and controlling the user plane function to stop data transmission when the last node leaves the user plane multicast tree.

[0318] It can be understood that in the embodiment of the present application, the non-unicast service multicast tree management device 200 can realize each process of the embodiment of the method shown in Figure 6 above, and achieve the same technical effect. In order to avoid repetition, no further description will be given here.

[0319] Referring to Figure 21, it is a structural diagram of a management device for a non-unicast service multicast tree according to an embodiment of the present application used in the fifth network function. As shown in Figure 21, the management device 210 for a non-unicast service multicast tree includes: a first sending module 211 for sending a non-unicast session connection operation indication to a fourth network function according to the first information; Here, the first information is A user plane function controlled by the fifth network function transmits data to a first terminal using a non-unicast session unicast resource; stopping a user plane function controlled by the fifth network function from transmitting data to a final terminal using non-unicast session unicast resources; the fifth network function providing a service for a first terminal or user; and ceasing the fifth network function from providing service for the last terminal or user.

[0320] Optionally, the non-unicast session connection operation instruction further comprises: The instruction includes at least one of a user plane node management instruction and a control plane node management instruction.

[0321] It can be understood that in the embodiment of the present application, the non-unicast service multicast tree management device 210 can realize each process of the embodiment of the method shown in Figure 7 above, and achieve the same technical effect. In order to avoid repetition, no further description will be given here.

[0322] Referring to Figure 22, Figure 22 is a structural diagram of a non-unicast task and unicast session association device according to an embodiment of the present application used in the sixth network function. As shown in Figure 22, the non-unicast task and unicast session association device 220 includes: a second sending module 221 for sending a first operation instruction to the seventh network function according to at least one of the RAN capability, the RAN node capability serving the non-unicast service or the non-unicast session, the first binding instruction from the seventh network function, and the second binding instruction from the eighth network function; Wherein, the first binding instruction includes unicast session information, and at least one of a non-unicast service operation instruction, non-unicast session information, a non-unicast service operation type, a non-unicast session operation type, and a non-unicast instruction; Here, the second binding instruction is: including at least one of: user already joined, user not left, user already left, user not joined, business already started, business not started, business already stopped, business not stopped, not allowing user to join, allowing user to join, not binding, binding, unbinding, and not unbinding; Here, the first operation instruction is: The instruction includes at least one of an association instruction, a disassociation instruction, a non-association instruction, and a maintenance of association instruction.

[0323] Optionally, the first binding indication comprises: The information further includes at least one of user information and terminal information.

[0324] Optionally, the second sending module 221 further comprises: Used to transmit at least one of a non-unicast session unicast resource operation instruction, a non-unicast session information, a non-unicast service information, a non-unicast session shared resource operation instruction, a non-unicast session operation type, a unicast session information, user information, and terminal information to the eighth network function.

[0325] Optionally, the second sending module 221 further comprises: Any RAN node supports non-unicast or any RAN node serving a non-unicast service or session supports non-unicast; and It is used to send a not binding instruction to the seventh network function according to at least one of the second binding instructions of the eighth network function, which are at least one of: a user has already joined, a user has not left, business has not started, business has already stopped, not allowing the user to join, not binding, and unbinding.

[0326] Optionally, the second sending module 221 further comprises: None of the RAN nodes support non-unicast, none of the RAN nodes serving the non-unicast service or non-unicast session support non-unicast, none of the RAN nodes support non-unicast, none of the RAN nodes serving the non-unicast service or non-unicast session support non-unicast, and It is used to send a binding instruction to the seventh network function according to at least one of the second binding instructions of the eighth network function, which are at least one of: user not joined, user already left, business already started, business not stopped, allowing user joining, binding, and not unbinding.

[0327] It can be understood that in the embodiment of the present application, the associating device 220 between a non-unicast task and a unicast session can realize each process of the embodiment of the method shown in Fig. 8 above, and achieve the same technical effect. In order to avoid repetition, no further description will be given here.

[0328] Please refer to Figure 23, which is a structural diagram of a non-unicast task and unicast session association device according to an embodiment of the present application used in the seventh network function. As shown in Figure 23, the non-unicast task and unicast session association device 230 includes: a fourth acquisition module 231 for acquiring a first operation instruction of a sixth network function or a second operation instruction of an eighth network function; According to the first operation instruction or the second operation instruction, a third execution module 232 for performing at least one of associating the unicast session with the non-unicast session, associating the unicast session with the non-unicast function, disassociating the unicast session with the non-unicast session, and disassociating the unicast session with the non-unicast function; Here, the first operation instruction includes at least one of an association instruction, an association cancellation instruction, a non-association instruction, and an association maintenance instruction, The second operation instruction includes at least one of an associating instruction, an unassociating instruction, a non-associating instruction, and an association maintaining instruction.

[0329] Optionally, the non-unicast service and unicast session associating device 230 may include: Further comprising a third sending module for sending a first binding indication to the sixth network function based on at least one of a terminal capability, a RAN capability, and a RAN capability for serving a non-unicast service or a non-unicast session; Wherein, the first binding instruction includes unicast session information, and The information includes at least one of a non-unicast service operation instruction, non-unicast session information, a non-unicast service operation type, a non-unicast session operation type, and a non-unicast instruction.

[0330] Optionally, the fourth acquisition module 231 further comprises: Obtaining capability information of a terminal; and obtaining capability information of the RAN node.

[0331] Optionally, the third transmitting module further comprises: sending a first binding indication to the sixth network function when the terminal does not support non-unicast; sending a first binding indication to the sixth network function when none of the RAN nodes support non-unicast, when none of the RAN nodes serving the non-unicast service or the non-unicast session support non-unicast, when none of the RAN nodes support non-unicast, or when none of the RAN nodes serving the non-unicast service or the non-unicast session support non-unicast; Wherein, the first binding instruction includes unicast session information, and The information includes at least one of a non-unicast service operation instruction, non-unicast session information, a non-unicast service operation type, a non-unicast session operation type, and a non-unicast instruction.

[0332] It can be understood that in the embodiment of the present application, the associating device 230 between a non-unicast task and a unicast session can realize each process of the embodiment of the method shown in Figure 9 above, and achieve the same technical effect. In order to avoid repetition, no further description will be given here.

[0333] Referring to Figure 24, Figure 24 is a structural diagram of a non-unicast task and unicast session association device according to an embodiment of the present application used in the eighth network function. As shown in Figure 24, the non-unicast task and unicast session association device 240 includes: A terminal or user has a bound non-unicast session or service; a fourth sending module 241 for sending a second operation instruction to a seventh network function according to at least one of: the terminal or the user having no bound non-unicast session or no non-unicast service; Here, the second operation instruction includes at least one of an associating instruction, an unassociating instruction, a non-associating instruction, and an association maintaining instruction.

[0334] Optionally, the non-unicast service and unicast session associating device 240 may include: a fifth obtaining module for obtaining a third binding indication of a sixth network function; a second management module for managing a non-unicast service or a non-unicast session of the terminal according to the third binding instruction, or for managing a non-unicast service or a non-unicast session of the user according to the third binding instruction; Here, the third binding instruction includes at least one of: the user has not joined; the user has already left; the service has already started; the service has not stopped; allowing the user to join; binding; and not unbinding.

[0335] It can be understood that in the embodiment of the present application, the non-unicast task and unicast session associating device 240 can realize each process of the method embodiment shown in Fig. 10 above, and achieve the same technical effect. In order to avoid repetition, no further description will be given here.

[0336] Referring to Figure 25, Figure 25 is a structural diagram of a non-unicast service authentication or authorization device according to an embodiment of the present application used in the ninth network function. As shown in Figure 25, the non-unicast service authentication or authorization device 250 includes: a fifth obtaining module 251 for obtaining non-unicast indication information; and a fifth sending module 252 for sending an authentication or authorization message to the application server; Here, the non-unicast instruction information includes at least one of unicast session information, a non-unicast service operation instruction, a non-unicast session information, a non-unicast service operation type, a non-unicast session operation type, and a non-unicast instruction.

[0337] Optionally, the authentication or authorization device 250 for the non-unicast service may include: a seventh obtaining module for obtaining an authentication permission indication from a tenth network function according to the non-unicast indication information; The fifth sending module is specifically used for performing, according to the authentication and authorization instruction, sending an authentication or authorization message to the application server.

[0338] Optionally, the authentication or authorization device 250 for the non-unicast service may include: Further comprising a forwarding module for forwarding authentication or authorization messages between the application server and a terminal; Here, the terminal is associated with the user information or corresponds to the terminal information.

[0339] It can be understood that in the embodiment of the present application, the authentication or authorization device 250 for non-unicast service can realize each process of the embodiment of the method shown in Figure 11 above, and achieve the same technical effect. In order to avoid repetition of the description, it will not be described further here.

[0340] Optionally, as shown in Fig. 26, the embodiment of the present application further provides a network function 260, which includes a processor 261, a memory 262, and a program or instruction stored in the memory 262 and capable of running on the processor 261, and when the program or instruction is executed by the processor 261, it can realize each process of the method embodiment shown in Fig. 2 to Fig. 15 above, and achieve the same technical effect. In order to avoid repetition, no further description will be given here.

[0341] The embodiments of the present application further provide a readable storage medium, on which a program or instruction is stored, which, when executed by a processor, can realize each process of the method embodiments shown in Figures 2 to 15 and achieve the same technical effects. In order to avoid repetition, no further description will be given here.

[0342] Wherein, the processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0343] The embodiment of the present application further provides a chip, the chip including a processor and a communication interface, the communication interface is coupled to the processor, the processor is used to run a program or instruction of a network side device, and realize each process of the embodiment shown in the above Figures 2 to 15, and can achieve the same technical effect. In order to avoid repetition, no further description will be given here.

[0344] It should be understood that the chips referred to in the embodiments of the present application may be referred to as system level chips, system chips, chip systems, or systems on chips.

[0345] The embodiments of the present application provide a computer program product, the computer program product is stored in a non-volatile storage medium, and the computer program product can be executed by at least one processor to realize each process of the above method embodiments and achieve the same technical effects. In order to avoid repetition, no further description will be given here.

[0346] The embodiments of the present application provide a network function, which is configured to execute each process of each embodiment of the method as described above, and can achieve the same technical effect. In order to avoid repetition, it will not be described further here.

[0347] It should be explained that in this specification, the terms "comprise", "includes", or any other variants thereof are intended to cover the non-exclusive "comprise", whereby a process, method, article, or apparatus that includes a set of elements includes not only those elements, but also other elements not expressly listed or inherent to such process, method, article, or apparatus. Absent any further limitations, an element limited by the phrase "comprises a" does not preclude the presence of other identical elements in the process, method, article, or apparatus that includes the element. It should be noted that the scope of the method and apparatus in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may include performing functions in an essentially simultaneous manner or in reverse order based on the functions involved, for example, the described method can be performed in a different order than described, and various steps can be added, omitted, or combined. Also, features described with reference to some examples can be combined in other examples.

[0348] From the above description of the embodiments, it is clear to those skilled in the art that the methods of the above embodiments can be realized in the form of software and a necessary general-purpose hardware platform. Of course, they can also be realized in hardware, but in many cases the former is a more preferred embodiment. Based on this understanding, the technical solution of the present application may be substantially or in part embodied in the form of a software product. The computer software product is stored in a storage medium (e.g., ROM / RAM, magnetic disk, optical disk) and includes some instructions for causing a terminal (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0349] The above describes the embodiments of the present application in conjunction with the drawings, but the present application is not limited to the above specific embodiments. The above specific embodiments are merely illustrative and not limiting. Those skilled in the art can take the suggestions of this application and make many forms without departing from the spirit and scope of the claims of this application, all of which belong to the protection scope of this application.

Claims

1. 1. A method for triggering a non-unicast transaction operation performed by a first network function, comprising: Obtaining non-unicast session information or non-unicast service information; performing a first operation based on the non-unicast session information or the non-unicast service information; wherein the first operation includes at least one of sending a first non-unicast session operation instruction to a second network function, and sending a second non-unicast session operation instruction or a non-unicast session context operation instruction to a third network function; wherein the first non-unicast session operation instruction is: At least one of a non-unicast session shared resource operation instruction, a non-unicast task operation instruction, non-unicast session information, information of the first network function, non-unicast quality of service (QoS) flow information, and a non-unicast session operation type; wherein the second non-unicast session operation instruction is: at least one of a non-unicast session shared resource operation instruction, a non-unicast task operation instruction, a non-unicast session unicast resource operation instruction, non-unicast session information, information of the first network function, non-unicast QoS flow information, and a non-unicast session operation type; Wherein, the non-unicast session context operation instruction is at least one of a non-unicast session shared resource operation instruction, a non-unicast task operation instruction, a non-unicast session unicast resource operation instruction, and a non-unicast session connection operation instruction; Here, the non-unicast session shared resource operation instruction is: at least one of a non-unicast session shared resource operation type, a non-unicast task operation instruction, non-unicast session information, information of the first network function, non-unicast QoS flow information, and a non-unicast session operation type; Wherein, the non-unicast session unicast resource operation instruction is: At least one of a non-unicast session unicast resource operation type, a non-unicast task operation instruction, non-unicast session information, information of the first network function, unicast QoS flow information, a non-unicast session operation type, and unicast session information; Here, the non-unicast includes at least one of a multicast and a broadcast.

2. The non-unicast session connection operation instruction is indicating that a user plane node is to join; indicating that the user plane node is leaving; indicating that the user plane node is to hold; indicating that the user plane node is not joining; and indicating that the user plane node is not to leave; not instructing a user plane node to join; not instructing the user plane node to leave; The user plane node does not indicate that it holds the The user plane node does not indicate not to join; and Not instructing the user plane node to stay put; indicating that a control plane node is to join; indicating that the control plane node is leaving; and indicating that the control plane node is to hold; indicating that the control plane node is not joining; and indicating that the control plane node is not to leave; and The control plane node does not indicate the joining; The control plane node does not indicate that it is leaving; The control plane node does not indicate that it is to hold The control plane node does not indicate not to join; and and not indicating that the control plane node is to remain.

3. The performing of the first operation includes: The method of claim 1 , comprising performing the first operation based on a radio access network (RAN) capability.

4. performing a first operation based on the non-unicast session information or the non-unicast service information, performing the first operation based on non-unicast session context information corresponding to the non-unicast session information; and performing the first operation based on context information of a non-unicast service corresponding to the non-unicast service information.

5. The performing of the first operation includes: sending the first non-unicast session operation indication to the second network function when all RAN nodes support a non-unicast function; sending the first non-unicast session operation indication to the second network function when all RAN nodes serving the non-unicast service or the non-unicast session support a non-unicast function; sending the first non-unicast session operation instruction to the second network function when third network function information is not included in context information of a non-unicast task or a non-unicast session; sending the first non-unicast session operation instruction to a second network function when context information of the non-unicast task or session includes information of the second network function; sending the first non-unicast session operation instruction to the third network function when the context information of the non-unicast task or the non-unicast session includes information of a second network function; The method of claim 1 , wherein the non-unicast service corresponds to the non-unicast service information, and the non-unicast session corresponds to the non-unicast session information.

6. The performing of the first operation includes: When none of the RAN nodes supports a non-unicast function, sending the second non-unicast session operation indication or a non-unicast session context operation indication to the third network function; sending the second non-unicast session operation indication or the non-unicast session context operation indication to the third network function when none of the RAN nodes serving the non-unicast service or the non-unicast session supports a non-unicast function; When none of the RAN nodes supports a non-unicast function, sending the second non-unicast session operation indication or the non-unicast session context operation indication to the third network function; When none of the RAN nodes serving the non-unicast service or the non-unicast session supports a non-unicast function, sending the second non-unicast session operation indication or the non-unicast session context operation indication to the third network function; sending the second non-unicast session operation instruction or the non-unicast session context operation instruction to the third network function when third network function information is included in the context information of the non-unicast task or the non-unicast session; When the context information of the non-unicast task or the non-unicast session does not include second network function information, sending the second non-unicast session operation instruction or the non-unicast session context operation instruction to the third network function; sending the second non-unicast session operation instruction or the non-unicast session context operation instruction to the third network function when the context information of the non-unicast task or the non-unicast session includes information of the third network function; and executing, when the second network function information is included in the context information of a non-unicast task or a non-unicast session, sending the second non-unicast session operation instruction or the non-unicast session context operation instruction to the third network function; The method of claim 1 , wherein the non-unicast service corresponds to the non-unicast service information, and the non-unicast session corresponds to the non-unicast session information.

7. The method comprises:

7. The method of claim 6, further comprising: sending a first non-unicast session operation instruction to the second network function; or performing sending the first non-unicast session operation instruction to the second network function.

8. Prior to performing the first operation, the method further comprises: Obtaining user information or terminal information; 2. The method of claim 1, further comprising: performing the first operation based on user context information corresponding to the user information; or performing the first operation based on terminal context information corresponding to the terminal information.

9. Prior to performing the first operation, the method further comprises: The method further includes obtaining user information or terminal information; The performing of the first operation includes: performing sending the first non-unicast session operation indication to the second network function when a user or terminal has no unicast session associated with the non-unicast function; performing sending the first non-unicast session operation instruction to the second network function when a user or terminal does not have a unicast session related to a non-unicast task; and performing, when a user or terminal does not have a unicast session associated with the non-unicast session, sending the first non-unicast session operation indication to the second network function; Here, the user corresponds to the user information, and the terminal corresponds to the terminal information, The method of claim 1 , wherein the non-unicast service corresponds to the non-unicast service information, and the non-unicast session corresponds to the non-unicast session information.

10. Prior to performing the first operation, the method further comprises: The method further includes obtaining user information or terminal information; The performing of the first operation includes: performing, when a user or terminal has a unicast session associated with a non-unicast function, sending the second non-unicast session operation indication or a non-unicast session context operation indication to the third network function; When a user or terminal has a unicast session related to a non-unicast task, sending the second non-unicast session operation indication or the non-unicast session context operation indication to the third network function; and performing, when a user or terminal has a unicast session associated with the non-unicast session, sending the second non-unicast session operation indication or a non-unicast session context operation indication to the third network function; Here, the user corresponds to the user information, and the terminal corresponds to the terminal information, The method of claim 1 , wherein the non-unicast service corresponds to the non-unicast service information, and the non-unicast session corresponds to the non-unicast session information.

11. The method comprises: The method of claim 10 , further comprising: performing sending the first non-unicast session operation indication to the second network function.

12. The first non-unicast session operation instruction is: Further including at least one of user information, user list information, terminal information, terminal list information, first instruction information, RAN node information, RAN node list information, and unicast session information; Wherein, the first indication information is used to indicate at least one of non-unicast resource operation type information, no need for paging, and need for paging; The non-unicast resource operation type information includes: The method of claim 1 , comprising at least one of a shared resource operation and a unicast resource operation.

13. The second non-unicast session operation instruction: Further including at least one of user information, user list information, terminal information, terminal list information, second instruction information, and unicast session information; Wherein, the second indication information is used to indicate at least one of non-unicast resource operation type information, no need for paging, and need for paging; The non-unicast resource operation type information includes: The method of claim 1 , comprising at least one of a shared resource operation and a unicast resource operation.

14. The method of claim 1 , wherein the non-unicast service operation instruction includes any one of a non-unicast start instruction, a non-unicast update instruction, a non-unicast stop instruction, a non-unicast join instruction, and a non-unicast leave instruction.

15. The performing of the first operation includes: The method of claim 1 , further comprising: performing said first operation upon receiving a report of arrived data.

16. The method comprises: The method further includes obtaining first authorization information, the first authorization information including at least one of user non-unicast function authorization information associated with the operator information, user non-unicast service authorization information associated with the operator information, and user non-unicast session authorization information associated with the operator information; Here, performing the first operation includes: The method of claim 1 , further comprising: performing the first operation in accordance with the first authorization information.

17. The method comprises: Further comprising: obtaining information of the third network function and unicast session information from a tenth network function according to user information and / or terminal information; The unicast session information includes:

2. The method of claim 1, comprising at least one of a session management context identifier and a PDU session identifier.

18. Before performing the first operation, and further comprising: obtaining user information and / or terminal information from a tenth network function according to the identifier information; Here, the identifier information is The method of claim 1 , comprising at least one of an IP address, a MAC address, a user identifier, and a terminal identifier.

19. A method for triggering a non-unicast service operation performed by a second network function, comprising: performing a second operation based on at least one of the non-unicast capability of the first RAN node and the first indication received from the first network function; Here, the second operation is at least one of: sending a single paging message to the first RAN node; sending a non-unicast session shared resource operation instruction to the first RAN node; suspending sending of the non-unicast session shared resource operation instruction; sending a non-unicast session unicast resource operation instruction to the first RAN node; suspending sending of the non-unicast session unicast resource operation instruction; and sending a group paging message to the first RAN node; The first indication information is used to indicate at least one of non-unicast resource operation type information, no need for paging, and need for paging; The method for triggering a non-unicast business operation, wherein the non-unicast includes at least one of a multicast and a broadcast.

20. After receiving a failure indication sent by the first RAN node or a response time of the first RAN node times out, the method includes:

20. The method of claim 19, further comprising: transmitting at least one of a non-unicast session shared resource operation indication and a non-unicast session unicast resource operation indication to the second RAN node.

21. The method comprises:

20. The method of claim 19, further comprising obtaining non-unicast capability information of the RAN node by receiving non-unicast related information from the RAN node.

22. A method for triggering a non-unicast service operation performed by a third network function, comprising: information on the third network function; and sending at least one of user information, terminal information, and unicast session information to a tenth network function; The unicast session information includes: A method for triggering a non-unicast service operation, comprising at least one of a session management context identifier and a PDU session identifier.

23. A method for triggering a non-unicast service operation performed by an access network side device, comprising: Obtaining a non-unicast session unicast resource operation instruction; A method for triggering a non-unicast service operation, comprising instructing a core network function to at least one of a node joining and a node leaving.

24. A method for managing a non-unicast service multicast tree executed by a fourth network function, comprising: a non-unicast session connection operation instruction received from a fifth network function; RAN capabilities; and and managing the multicast tree according to at least one of: a non-unicast session or a RAN node capability for serving the non-unicast service; Here, the multicast tree is A method for managing non-unicast service multicast trees, including at least one of a control plane multicast tree and a user plane multicast tree.

25. The non-unicast session connection operation instruction is 25. The method of claim 24, comprising at least one of a user plane node management indication and a control plane node management indication.

26. The user plane node management instruction includes: indicating that a user plane node is to join; indicating that the user plane node is leaving; indicating that the user plane node is to hold; indicating that the user plane node is not joining; and indicating that the user plane node is not to leave; not instructing a user plane node to join; not instructing the user plane node to leave; The user plane node does not indicate that it holds the The user plane node does not indicate not to join; and Not instructing the user plane node to stay put; A non-unicast session shared resource operation instruction; a non-unicast session unicast resource operation instruction; and / or The control plane node management instruction includes: indicating that a control plane node is to join; indicating that the control plane node is leaving; and indicating that the control plane node is to hold; indicating that the control plane node is not joining; and indicating that the control plane node is not to leave; and The control plane node does not indicate the joining; The control plane node does not indicate that it is leaving; The control plane node does not indicate that it is to hold The control plane node does not indicate not to join; and The control plane node does not indicate that it will leave; A non-unicast session shared resource operation instruction; 26. The method of claim 25, further comprising at least one of the following features: a non-unicast session unicast resource manipulation indication;

27. The method comprises: obtaining RAN node information; Wherein, managing the multicast tree includes managing a control plane multicast tree, and managing the control plane multicast tree includes: Subscribing the RAN node information to the control plane multicast tree; and removing the RAN node information from the control plane multicast tree.

28. The method comprises: obtaining transmission endpoint information; The managing of the multicast tree includes managing a user plane multicast tree, and the managing of the user plane multicast tree includes: subscribing the transmission endpoint information to the user plane multicast tree; and removing the transmission endpoint information from the user plane multicast tree; Here, the transmission endpoint information is:

25. The method of claim 24, including at least one of an IP address, a port, tunnel information, and node information.

29. The managing of the multicast tree includes managing a user plane multicast tree, and the managing of the user plane multicast tree includes: Increasing a count of user plane nodes; and decreasing a count of user plane nodes; and / or Managing the multicast tree includes managing a control plane multicast tree, and managing the control plane multicast tree includes: Increasing the count of control plane nodes; and decreasing a count of control plane nodes.

30. The method comprises: managing the user plane multicast tree in accordance with the user plane node management instructions; managing the control plane multicast tree in accordance with the user plane node management instructions; managing the control plane multicast tree in accordance with the control plane node management instructions; and managing the user plane multicast tree in accordance with the control plane node management instructions.

31. Managing the multicast tree includes managing a control plane multicast tree, and managing the control plane multicast tree includes: Subscribing information of the fifth network function to the control plane multicast tree; and removing information of the fifth network function from the control plane multicast tree.

32. The method comprises: managing the control plane multicast tree according to the control plane node management directive and information of the fifth network function; 26. The method of claim 25, further comprising at least one of: managing the control plane multicast tree according to the user plane node management instructions and information of the fifth network function.

33. The method comprises: controlling a user plane function to initiate data transmission; and controlling a user plane function to stop data transmission.

34. The method comprises: Controlling a user plane function to initiate data transmission when a first node joins the user plane multicast tree; and controlling a user plane function to stop data transmission when the last node leaves the user plane multicast tree.

35. A method for managing a non-unicast service multicast tree executed by a fifth network function, comprising the steps of: sending a non-unicast session connection operation indication to a fourth network function according to the first information; Here, the first information is A user plane function controlled by the fifth network function transmits data to a first terminal using a non-unicast session unicast resource; stopping a user plane function controlled by the fifth network function from transmitting data to a final terminal using non-unicast session unicast resources; the fifth network function providing a service for a first terminal or user; and c) causing the fifth network function to stop providing service for the last terminal or user.

36. The non-unicast session connection operation instruction is 36. The method of claim 35, comprising at least one of a user plane node management indication and a control plane node management indication.

37. A method for associating a non-unicast task executed by a sixth network function with a unicast session, comprising the steps of: sending a first operation instruction to a seventh network function according to at least one of the RAN capability, the RAN node capability for serving a non-unicast service or session, the first binding instruction from the seventh network function, and the second binding instruction from the eighth network function; Wherein, the first binding instruction includes unicast session information, and at least one of a non-unicast service operation instruction, non-unicast session information, a non-unicast service operation type, a non-unicast session operation type, and a non-unicast instruction; Here, the second binding instruction is: including at least one of: user already joined, user not left, user already left, user not joined, business already started, business not started, business already stopped, business not stopped, not allowing user to join, allowing user to join, not binding, binding, unbinding, and not unbinding; Here, the first operation instruction is: A method for associating a non-unicast task with a unicast session, the method including at least one of an association instruction, an association cancellation instruction, a non-association instruction, and an association maintenance instruction.

38. The first binding instruction is 40. The method of claim 37, further comprising at least one of user information and terminal information.

39. The method comprises:

38. The method of claim 37, further comprising sending at least one of a non-unicast session unicast resource operation instruction, a non-unicast session information, a non-unicast service information, a non-unicast session shared resource operation instruction, a non-unicast session operation type, a unicast session information, user information, and terminal information to the eighth network function.

40. The transmitting of the first operation instruction to the seventh network function includes: Any RAN node supports non-unicast or any RAN node serving a non-unicast service or session supports non-unicast; and sending a not-binding instruction to the seventh network function according to at least one of a second binding instruction of the eighth network function, the second binding instruction being at least one of: a user has already joined, a user has not left, a service has not started, a service has already stopped, not allowing the user to join, not binding, and unbinding; Or, The transmitting of the first operation instruction to the seventh network function includes: None of the RAN nodes support non-unicast, none of the RAN nodes serving the non-unicast service or non-unicast session support non-unicast, none of the RAN nodes support non-unicast, none of the RAN nodes serving the non-unicast service or non-unicast session support non-unicast, and 38. The method of claim 37, comprising sending a binding indication to the seventh network function according to at least one of second binding indications of the eighth network function being at least one of: user not joining, user already leaving, service already started, service not stopped, allowing user joining, binding, and not unbinding.

41. A method for associating a non-unicast task and a unicast session executed by a seventh network function, comprising the steps of: obtaining a first operation instruction for a sixth network function or a second operation instruction for an eighth network function; According to the first operation instruction or the second operation instruction, performing at least one of associating the unicast session with a non-unicast session, associating the unicast session with a non-unicast function, disassociating the unicast session with the non-unicast session, and disassociating the unicast session with the non-unicast function; Here, the first operation instruction includes at least one of an association instruction, an association cancellation instruction, a non-association instruction, and an association maintenance instruction, The method for associating a non-unicast task with a unicast session, wherein the second operation instruction includes at least one of an association instruction, an association cancellation instruction, a non-association instruction, and an association maintenance instruction.

42. The method comprises: and sending a first binding indication to the sixth network function based on at least one of a terminal capability, a RAN capability, and a RAN capability for serving a non-unicast service or a non-unicast session; Wherein, the first binding instruction includes unicast session information, and 42. The method of claim 41, comprising at least one of a non-unicast service operation indication, non-unicast session information, a non-unicast service operation type, a non-unicast session operation type, and a non-unicast indication.

43. The method comprises: Obtaining capability information of a terminal; and obtaining capability information of the RAN node.

44. The method comprises: sending a first binding indication to the sixth network function when the terminal does not support non-unicast; sending a first binding indication to the sixth network function when none of the RAN nodes support non-unicast, when none of the RAN nodes serving the non-unicast service or non-unicast session support non-unicast, when none of the RAN nodes support non-unicast, or when none of the RAN nodes serving the non-unicast service or non-unicast session support non-unicast; Wherein, the first binding instruction includes unicast session information, and 42. The method of claim 41, comprising at least one of a non-unicast service operation indication, non-unicast session information, a non-unicast service operation type, a non-unicast session operation type, and a non-unicast indication.

45. A method for associating a non-unicast task and a unicast session executed by an eighth network function, comprising the steps of: A terminal or user has a bound non-unicast session or service; and sending a second operation instruction to a seventh network function according to at least one of: the terminal or the user having no bound non-unicast sessions or no bound non-unicast services; Here, the second operation instruction includes at least one of an association instruction, an association cancellation instruction, a non-association instruction, and an association maintenance instruction.

46. The method comprises: obtaining a third binding indication of a sixth network function; and managing a non-unicast service or a non-unicast session of the terminal according to the third binding instruction, or managing a non-unicast service or a non-unicast session of the user according to the third binding instruction; 46. ​​The method of claim 45, wherein the third binding indication includes at least one of: user not joining, user already left, service already started, service not stopped, allowing user joining, binding, and not unbinding.

47. A method for authenticating or authorizing a non-unicast service executed by a ninth network function, comprising: Obtaining non-unicast indication information; sending an authentication or authorization message to an application server; Here, the non-unicast instruction information includes at least one of unicast session information, non-unicast task operation instruction, non-unicast session information, non-unicast task operation type, non-unicast session operation type, and non-unicast instruction, and is an authentication or authorization method for a non-unicast task.

48. The non-unicast indication information is Further including at least one of user information, terminal information, and application server information; wherein the application server information is associated with the application server; 48. The method of claim 47, including at least one of an IP address and an application server identifier.

49. The method comprises: obtaining an authentication permission indication from a tenth network function according to the non-unicast indication information; 48. The method of claim 47, further comprising: performing, in accordance with the authentication authorization indication, sending an authentication or authorization message to the application server.

50. The method comprises: and forwarding authentication or authorization messages between the application server and a terminal.

49. The method of claim 48, wherein the terminal is associated with or corresponds to the user information.

51. A trigger device for a non-unicast task operation used in a first network function, comprising: A first acquisition module for acquiring non-unicast session information or non-unicast service information; a first execution module for executing a first operation based on the non-unicast session information or the non-unicast service information; wherein the first operation includes at least one of sending a first non-unicast session operation instruction to a second network function, and sending a second non-unicast session operation instruction or a non-unicast session context operation instruction to a third network function; wherein the first non-unicast session operation instruction is: At least one of a non-unicast session shared resource operation instruction, a non-unicast task operation instruction, non-unicast session information, information of the first network function, non-unicast quality of service (QoS) flow information, and a non-unicast session operation type; wherein the second non-unicast session operation instruction is: at least one of a non-unicast session shared resource operation instruction, a non-unicast task operation instruction, a non-unicast session unicast resource operation instruction, non-unicast session information, information of the first network function, non-unicast QoS flow information, and a non-unicast session operation type; Wherein, the non-unicast session context operation instruction is at least one of a non-unicast session shared resource operation instruction, a non-unicast task operation instruction, a non-unicast session unicast resource operation instruction, and a non-unicast session connection operation instruction; Here, the non-unicast session shared resource operation instruction is: at least one of a non-unicast session shared resource operation type, a non-unicast task operation instruction, non-unicast session information, information of the first network function, non-unicast QoS flow information, and a non-unicast session operation type; Wherein, the non-unicast session unicast resource operation instruction is: At least one of a non-unicast session unicast resource operation type, a non-unicast task operation instruction, non-unicast session information, information of the first network function, unicast QoS flow information, a non-unicast session operation type, and unicast session information; Here, the non-unicast includes at least one of a multicast and a broadcast.

52. A trigger device for a non-unicast service operation used in a second network function, comprising: a second execution module for performing a second operation based on at least one of the non-unicast capability of the first RAN node and the first indication information received from the first network function; Here, the second operation is at least one of: sending a single paging message to the first RAN node; sending a non-unicast session shared resource operation instruction to the first RAN node; suspending sending of the non-unicast session shared resource operation instruction; sending a non-unicast session unicast resource operation instruction to the first RAN node; suspending sending of the non-unicast session unicast resource operation instruction; and sending a group paging message to the first RAN node; The first indication information is used to indicate at least one of non-unicast resource operation type information, no need for paging, and need for paging; The non-unicast service operation trigger device, wherein the non-unicast includes at least one of a multicast and a broadcast.

53. A trigger device for a non-unicast service operation used in a third network function, comprising: information on the third network function; and a third sending module for sending at least one of the user information, the terminal information, and the unicast session information to a tenth network function; The unicast session information includes: A trigger device for a non-unicast service operation, comprising at least one of a session management context identifier and a PDU session identifier.

54. A trigger device for a non-unicast service operation used in an access network side device, comprising: a fifth obtaining module for obtaining a non-unicast session unicast resource operation instruction; and a fourth execution module for instructing a core network function to at least one of a node joining and a node leaving.

55. A management device for a non-unicast service multicast tree used in a fourth network function, a non-unicast session connection operation instruction received from a fifth network function; RAN capabilities; and a first management module for managing the multicast tree according to at least one of a non-unicast session or a RAN node capability for serving the non-unicast service; Here, the multicast tree is A management device for non-unicast service multicast trees, the management device including at least one of a control plane multicast tree and a user plane multicast tree.

56. A management device for a non-unicast service multicast tree used in a fifth network function, comprising: a first sending module for sending a non-unicast session connection operation indication to a fourth network function according to the first information; Here, the first information is A user plane function controlled by the fifth network function transmits data to a first terminal using a non-unicast session unicast resource; stopping a user plane function controlled by the fifth network function from transmitting data to a final terminal using non-unicast session unicast resources; the fifth network function providing a service for a first terminal or user; and c) causing the fifth network function to stop providing a service for the last terminal or user.

57. A device for associating a non-unicast service with a unicast session, the device being used for a sixth network function, a second sending module for sending a first operation instruction to the seventh network function according to at least one of the RAN capability, the RAN node capability serving the non-unicast service or the non-unicast session, the first binding instruction from the seventh network function, and the second binding instruction from the eighth network function; Wherein, the first binding instruction includes unicast session information, and at least one of a non-unicast service operation instruction, non-unicast session information, a non-unicast service operation type, a non-unicast session operation type, and a non-unicast instruction; Here, the second binding instruction is: including at least one of: user already joined, user not left, user already left, user not joined, business already started, business not started, business already stopped, business not stopped, not allowing user to join, allowing user to join, not binding, binding, unbinding, and not unbinding; Here, the first operation instruction is: An apparatus for associating a non-unicast task with a unicast session, the apparatus including at least one of an association instruction, an association release instruction, a non-association instruction, and an association maintenance instruction.

58. A device for associating a non-unicast service with a unicast session, the device being used in a seventh network function, a fourth acquisition module for acquiring a first operation instruction of a sixth network function or a second operation instruction of an eighth network function; According to the first operation instruction or the second operation instruction, a third execution module for performing at least one of associating the unicast session with the non-unicast session, associating the unicast session with the non-unicast function, disassociating the unicast session with the non-unicast session, and disassociating the unicast session with the non-unicast function; Here, the first operation instruction includes at least one of an association instruction, an association cancellation instruction, a non-association instruction, and an association maintenance instruction, The second operation instruction includes at least one of an association instruction, an association cancellation instruction, a non-association instruction, and an association maintenance instruction.

59. An association device for associating a non-unicast service with a unicast session, the association device being used in an eighth network function, comprising: A terminal or user has a bound non-unicast session or service; a fourth sending module for sending a second operation instruction to a seventh network function according to at least one of: the terminal or the user having no bound non-unicast session or no non-unicast service; Here, the second operation instruction includes at least one of an association instruction, an association cancellation instruction, a non-association instruction, and an association maintenance instruction.

60. A non-unicast service authentication or authorization device used for a ninth network function, a fifth acquiring module for acquiring non-unicast indication information; and a fifth sending module for sending an authentication or authorization message to the application server; Here, the non-unicast instruction information includes at least one of unicast session information, non-unicast business operation instruction, non-unicast session information, non-unicast business operation type, non-unicast session operation type, and non-unicast instruction, and is an authentication or authorization device for non-unicast business.

61. A network function comprising a processor, a memory, and a program or instructions stored in the memory and operable to run on the processor, the program or instructions, when executed by the processor, implementing steps of a method for triggering a non-unicast service operation as claimed in any one of claims 1 to 23, or implementing steps of a method for managing a non-unicast service multicast tree as claimed in any one of claims 24 to 36, or implementing steps of a method for associating a non-unicast service with a unicast session as claimed in any one of claims 37 to 46, or implementing steps of a method for authenticating or authorizing a non-unicast service as claimed in any one of claims 47 to 50.

62. A readable storage medium having a program or instructions stored on the readable storage medium, which, when executed by a processor, realizes the steps of a method for triggering a non-unicast service operation as claimed in any one of claims 1 to 23, or realizes the steps of a method for managing a non-unicast service multicast tree as claimed in any one of claims 24 to 36, or realizes the steps of a method for associating a non-unicast service with a unicast session as claimed in any one of claims 37 to 46, or realizes the steps of a method for authenticating or authorizing a non-unicast service as claimed in any one of claims 47 to 50.

63. A chip comprising a processor and a communications interface, the communications interface coupled to the processor, the processor running a program or instructions, the chip being used to implement steps of a method for triggering a non-unicast service operation as claimed in any one of claims 1 to 23, or to implement steps of a method for managing a non-unicast service multicast tree as claimed in any one of claims 24 to 36, or to implement steps of a method for associating a non-unicast service with a unicast session as claimed in any one of claims 37 to 46, or to implement steps of a method for authenticating or authorizing a non-unicast service as claimed in any one of claims 47 to 50.

64. A computer program product, the computer program product being stored in a non-volatile storage medium, the computer program product being executed by at least one processor to implement the steps of the method for triggering a non-unicast service operation as claimed in any one of claims 1 to 23, or to implement the steps of the method for managing a non-unicast service multicast tree as claimed in any one of claims 24 to 36, or to implement the steps of the method for associating a non-unicast service with a unicast session as claimed in any one of claims 37 to 46, or to implement the steps of the method for authenticating or authorizing a non-unicast service as claimed in any one of claims 47 to 50.

65. A network function configured to perform the steps of a method for triggering a non-unicast service operation as claimed in any one of claims 1 to 23, or the steps of a method for managing a non-unicast service multicast tree as claimed in any one of claims 24 to 36, or the steps of a method for associating a non-unicast service with a unicast session as claimed in any one of claims 37 to 46, or the steps of a method for authenticating or authorizing a non-unicast service as claimed in any one of claims 47 to 50.

Images