A method and apparatus for configuring an mbs session

Abstract

Embodiments of the present application provide a method and device for configuring an MBS session, the method comprising: a session management function network element detecting a first event for an MBS session; the session management function network element establishing or releasing a data transmission channel between a user plane function network element and a multicast source node for the MBS session according to the first event and a policy corresponding to the MBS session, wherein the policy is used to determine a timing for establishing or releasing the data transmission channel for the MBS session. Embodiments of the present application can configure different timings for establishing the data transmission channel between the user plane network element and the multicast source node for different MBS sessions, improve the flexibility of establishing and / or releasing the data transmission channel, and save the processing resources of the user plane function network element while ensuring the quality of the MBS session communication.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method and apparatus for configuring an MBS session. Background Technology

[0002] Currently, for 5G (5th generation) multicast / broadcast service (MBS), data transmission channels between user plane network elements and multicast source nodes are established at fixed times (such as during MBS session configuration or establishment). Furthermore, to ensure the transmission rate of the MBS session, processing resources for user plane network elements need to be reserved for the MBS session. However, in reality, MBS service data transmission is only possible when the MBS session is active. Therefore, existing technologies suffer from a single data transmission channel establishment method and resource waste. Summary of the Invention

[0003] This application provides a method and apparatus for configuring MBS sessions. Different timings can be provided for establishing data transmission channels between user plane network elements and multicast source nodes for different MBS sessions. This can improve the flexibility of establishing and / or releasing data transmission channels while ensuring the quality of MBS session communication, and save processing resources of user plane functional network elements.

[0004] Firstly, a method for configuring an MBS session is provided. This method can be executed by a session management function network element or a chip within the session management function network element. Taking the execution of the method by the session management function network element as an example, the method includes: the session management function network element detecting a first event for the MBS session; the session management function network element establishing or releasing a data transmission channel between the user plane function network element and the multicast source node for the MBS session according to the first event and the policy corresponding to the MBS session, wherein the policy is used to determine the timing for establishing or releasing the data transmission channel for the MBS session.

[0005] In this embodiment, the session management function network element triggers the timing of establishing or releasing the data transmission channel between the user plane function network element and the multicast source node based on the detected first event for the MBS session and the policy corresponding to the MBS session. This can enable different MBS sessions to correspond to different timings for establishing and / or releasing data transmission channels. For example, different policies can be configured for different MBS sessions, which improves the flexibility of establishing and / or releasing data transmission channels and can save core network resources while ensuring the quality of MBS service communication.

[0006] In one possible implementation, the strategy may include a first strategy, which contains at least one first type of event. This first type of event triggers the session management function network element to establish a data transmission channel for the MBS session. Correspondingly, if the first event matches a second event in the first strategy, where the second event is one of at least one first type of event, then the session management function network element establishes a data transmission channel between the user plane function network element and the multicast source node for the MBS session.

[0007] This implementation method allows the session management function network element to establish a data transmission channel for the MBS session when the first event matches the event in the first strategy, thus improving the flexibility of data transmission channel establishment.

[0008] In one possible implementation, at least one type-1 event includes, but is not limited to, one or more of the following:

[0009] At least one event in the MBS session configuration process corresponding to the MBS session;

[0010] At least one event in the MBS session establishment process corresponding to the MBS session;

[0011] At least one event in the MBS session activation process corresponding to the MBS session;

[0012] At least one event in the MBS session start transmission process corresponding to the MBS session.

[0013] It should be understood that the above examples are for illustrative purposes only and not specific limitations.

[0014] In one possible implementation, at least one event in the MBS session start transmission process corresponding to the MBS session includes: the arrival of the MBS session transmission start time. For example, the session management function network element can detect the start of MBS service transmission based on the MBS service start time record, or the session management function network element has a pre-configured MBS session transmission start time, and the session management function network element detects that the MBS session transmission start time has arrived, etc.

[0015] In this way, a data transmission channel can be established at the start of the MBS session, which can greatly reduce resource waste.

[0016] In one possible implementation, if the first event matches the second event in the first strategy, the session management function network element also reserves processing resources for the user plane function network element for the MBS session.

[0017] This ensures that user plane function elements can process MBS sessions promptly after transmission begins, thereby improving MBS session transmission efficiency.

[0018] In one possible implementation, the first strategy further includes a data transmission channel establishment method corresponding to each of the at least one first-type events, wherein the data transmission channel establishment method is either a first method or a second method; wherein the first method involves the user plane function network element allocating a port for communication with the multicast source node and notifying the multicast source node of the port; and the second method involves the user plane function network element sending a request to the multicast source node to join the multicast tree corresponding to the multicast source node. Correspondingly, the session management function network element can establish a data transmission channel for the MBS session according to the data transmission channel establishment method corresponding to the second event.

[0019] Through this implementation method, the first strategy can be used simultaneously to determine the data transmission channel establishment method, further improving the flexibility of establishing the data transmission channel. It eliminates the need for additional interaction with other network elements to determine the data transmission channel establishment method, thereby improving the efficiency of data transmission channel establishment.

[0020] In one possible implementation, the strategy includes a second strategy containing at least one second type of event, which triggers the session management function network element to release the data transmission channel for the MBS session. Correspondingly, if the first event matches a third event in the second strategy, where the third event is one of at least one second type of event, then the session management function network element releases the data transmission channel between the user plane function network element and the multicast source node for the MBS session.

[0021] This implementation method allows the session management function network element to release the data transmission channel for the MBS session when the first event matches the event in the second strategy, thus improving the flexibility of data transmission channel release.

[0022] In one possible implementation, at least one of the second type of events includes, but is not limited to, one or more of the following:

[0023] At least one event in the MBS session cancellation configuration process corresponding to the MBS session;

[0024] At least one event in the MBS session release process corresponding to the MBS session;

[0025] At least one event in the MBS session deactivation process corresponding to the MBS session;

[0026] At least one event in the MBS session termination transmission process corresponding to the MBS session.

[0027] It should be understood that the above examples are for illustrative purposes only and not specific limitations.

[0028] In one possible implementation, at least one event in the MBS session termination transmission process corresponding to the MBS session includes: the MBS session transmission termination time arriving.

[0029] In this way, the data transmission channel can be released at the end of the MBS session, thus ensuring the communication quality of the MBS session.

[0030] In one possible implementation, if the first event matches the third event in the second strategy, the session management function network element can also release the processing resources of the user plane function network element reserved for the MBS session.

[0031] Through this implementation method, the session management function network element can promptly release the processing resources of the user plane function network element reserved for MBS sessions, further saving core network resources.

[0032] In one possible implementation, the session management function network element obtains the policy corresponding to the MBS session from the application function network element; or, the session management function network element obtains the policy corresponding to the MBS session from the application function network element through the multicast / broadcast service function network element or the network presentation function network element.

[0033] With this implementation method, the timing of establishing and / or releasing the data transmission channel can be directly provided by the AF as an MBS parameter. Therefore, the multicast source node can flexibly configure the timing of establishing and / or releasing the data transmission channel corresponding to each MBS session according to the actual needs of the service.

[0034] In one possible implementation, the session management function network element can obtain indication information from the application function network element, or obtain indication information from the application function network element through the multicast / broadcast service function network element or the network presentation function network element; wherein, the indication information is used to determine one or more events; the session management function network element generates a policy corresponding to the MBS session based on the indication information, wherein the policy includes one or more events.

[0035] Through this implementation method, the timing of establishing and / or releasing the data transmission channel can be provided directly or indirectly by the AF as an MBS parameter (i.e., the strategy is generated by the SMF based on the first indication information provided by the AF). Therefore, the multicast source node can flexibly configure the timing of establishing and / or releasing the data transmission channel corresponding to each MBS session according to the actual needs of the service.

[0036] In one possible implementation, the instruction information includes one or more of the following:

[0037] The first piece of information is used to indicate the start time of the MBS session;

[0038] The second information is used to instruct the MBS session configuration process, MBS session establishment process, MBS session activation process, or MBS session start transmission process corresponding to the MBS session.

[0039] The third piece of information is used to indicate the end time of the MBS session;

[0040] The fourth piece of information is used to instruct the MBS session cancellation configuration process, MBS session release process, MBS session deactivation process, or MBS session termination transmission process corresponding to the MBS session.

[0041] The fifth piece of information is used to indicate the Quality of Service (QoS) requirements corresponding to the MBS session.

[0042] It should be understood that the above information is for illustrative purposes only and not as a limitation.

[0043] In one possible implementation, the session management function network element can send a query message to the policy control network element. The query message is used to query the policy and QoS requirements corresponding to the MBS session. The session management function network element receives a response message returned by the policy control network element, which carries the policy and QoS requirements corresponding to the MBS session.

[0044] In this method, the timing of establishing and / or releasing data transmission channels is configured as a parameter within the core network in the PCF / UDR. The AF does not directly provide this parameter information, but only provides QoS requirement information. Thus, operators can select different timings for establishing and / or releasing data transmission channels for different MBS sessions according to their operating strategies. The decision-making power lies with the operator, which facilitates deployment.

[0045] Secondly, a method for configuring an MBS session is provided. This method can be executed by an application function network element or a chip within the application function network element. Taking the method executed by an application function network element as an example, it includes: the application function network element generating a policy corresponding to the MBS session, wherein the policy is used to determine the timing for establishing or releasing a data transmission channel between a user plane function network element and a multicast source node for the MBS session, and the policy includes one or more events; the application function network element sending the policy corresponding to the MBS session to a session management function network element, or the application function network element sending the policy corresponding to the MBS session to the session management function network element through a multicast / broadcast service function network element or a network presentation function network element.

[0046] The implementation methods of the second aspect can be referred to the description of the corresponding implementation methods in the first aspect, and will not be repeated here.

[0047] Thirdly, a method for configuring an MBS session is provided. This method can be executed by an application function network element or a chip within the application function network element. Taking the method executed by an application function network element as an example, it includes: the application function network element generating indication information, wherein the indication information is used to determine one or more events; the application function network element sending the indication information to a session management function network element, so that the session management function network element generates a policy corresponding to the MBS session based on the indication information; wherein the policy is used to determine the timing for establishing or releasing a data transmission channel between the user plane function network element and the multicast source node for the MBS session, and the policy includes one or more events.

[0048] The implementation methods of the third aspect can be referred to the description of the corresponding implementation methods in the first aspect, and will not be repeated here.

[0049] Fourthly, a method for configuring an MBS session is provided. This method can be executed by a policy control network element or a chip within the policy control network element. Taking the method executed by the policy control network element as an example, it includes: the policy control network element receiving a query message from a session management function network element, wherein the query message is used to query the policy and QoS requirements corresponding to the MBS session; the policy control network element determining the policy and QoS requirements corresponding to the MBS session; and the policy control network element sending a response message to the session management function network element, wherein the response message carries the policy and QoS requirements corresponding to the MBS session.

[0050] In one possible implementation, the policy control network element stores the mapping relationship between QoS requirements and policies. Accordingly, the policy control network element obtains the QoS requirements corresponding to the MBS session from the unified database network element; based on the QoS requirements and mapping relationship corresponding to the MBS session, the policy control network element determines the policy corresponding to the MBS session.

[0051] In one possible implementation, the unified database network element stores the mapping relationship between QoS requirements and policies. Accordingly, the policy control network element obtains the policies and QoS requirements corresponding to the MBS session from the unified database network element.

[0052] The implementation methods of the fourth aspect can be referred to the description of the corresponding implementation methods in the first aspect, and will not be repeated here.

[0053] Fifthly, a communication device is provided, the device comprising modules / units / technical means for implementing the method described in the first aspect or any possible embodiment of the first aspect.

[0054] For example, the apparatus may include: a transceiver unit for detecting a first event for an MBS session; and a processing unit for: if the first event matches an event in a policy corresponding to the MBS session, then establishing or releasing a data transmission channel between the user plane function network element and the multicast source node for the MBS session, wherein the policy is used to determine the timing for establishing or releasing the data transmission channel for the MBS session.

[0055] In a sixth aspect, a communication device is provided, the device comprising modules / units / technical means for implementing the methods described in the second aspect or any possible implementation of the second aspect.

[0056] For example, the apparatus may include: a processing unit, configured to generate a policy corresponding to an MBS session, wherein the policy is used to determine the timing for establishing or releasing a data transmission channel between a user plane function network element and a multicast source node for the MBS session, and the policy includes one or more events; and a transceiver unit, configured to send the policy corresponding to the MBS session to a session management function network element, or to send the policy corresponding to the MBS session to a session management function network element through a multicast / broadcast service function network element or a network presentation function network element.

[0057] In a seventh aspect, a communication device is provided, the device comprising modules / units / technical means for implementing the methods described in the third aspect or any possible implementation of the third aspect.

[0058] For example, the apparatus may include: a processing unit for generating indication information, wherein the indication information is used to determine one or more events; a transceiver unit for sending the indication information to a session management function network element, so that the session management function network element generates a policy corresponding to the MBS session according to the indication information; wherein the policy is used to determine the timing for establishing or releasing a data transmission channel between the user plane function network element and the multicast source node for the MBS session, and the policy includes one or more events.

[0059] Eighthly, a communication device is provided, the device comprising modules / units / technical means for implementing the methods described in the fourth aspect or any possible implementation of the fourth aspect.

[0060] For example, the apparatus may include: a transceiver unit, configured to receive a query message from a session management function network element, wherein the query message is used to query the policy and QoS requirements corresponding to the MBS session; a processing unit, configured to determine the policy and QoS requirements corresponding to the MBS session; and the transceiver unit is further configured to send a response message to the session management function network element, wherein the response message carries the policy and QoS requirements corresponding to the MBS session.

[0061] A ninth aspect provides a communication device including a processor and a memory; wherein the processor and the memory are coupled, the memory is used to store computer execution instructions, and the processor is used to execute the computer execution instructions stored in the memory to cause the communication device to perform the method as described in the first aspect or any possible implementation of the first aspect, or the second aspect or any possible implementation of the second aspect, or the third aspect or any possible implementation of the third aspect.

[0062] In a tenth aspect, a chip is provided, including logic circuits and input / output interfaces;

[0063] The input / output interface is used to receive signals from other communication devices outside the chip and transmit them to the logic circuit, or to send signals from the logic circuit to other communication devices outside the chip. The logic circuit is used to implement the method as described in the first aspect or any possible implementation of the first aspect, or the second aspect or any possible implementation of the second aspect, or the third aspect or any possible implementation of the third aspect.

[0064] Eleventhly, a computer-readable storage medium is provided, wherein a computer program or instructions are stored therein, which, when executed by a communication device, implement the method as described in the first aspect or any possible implementation of the first aspect, or the second aspect or any possible implementation of the second aspect, or the third aspect or any possible implementation of the third aspect.

[0065] In a twelfth aspect, a computer program product is provided that, when run on a computer, causes the method described in the first aspect or any possible implementation thereof, or the second aspect or any possible implementation thereof, or the third aspect or any possible implementation thereof, to be executed. Attached Figure Description

[0066] Figure 1 This is a schematic diagram of the network architecture of a 5G communication system.

[0067] Figure 2 This is a schematic diagram of the MBS system architecture in a 5G communication system.

[0068] Figure 3 A flowchart for configuring an MBS session;

[0069] Figure 4 This is a state diagram of an MBS session;

[0070] Figure 5 A flowchart for configuring an MBS session is provided as an embodiment of this application;

[0071] Figure 6An example of an MBS session configuration process provided in this application embodiment;

[0072] Figure 7 Another example of MBS session configuration process provided in this application embodiment;

[0073] Figure 8 Another example of MBS session configuration process provided in this application embodiment;

[0074] Figure 9 Another example of MBS session configuration process provided in this application embodiment;

[0075] Figure 10 Another example of MBS session configuration process provided in this application embodiment;

[0076] Figure 11 Another example of MBS session configuration process provided in this application embodiment;

[0077] Figure 12 A schematic diagram of the structure of a possible communication device provided for an embodiment of this application;

[0078] Figure 13 A schematic diagram of another possible communication device provided for embodiments of this application;

[0079] Figure 14 This is a schematic diagram of a possible chip structure provided for an embodiment of this application. Detailed Implementation

[0080] The embodiments of this application can be applied to various communication systems, such as satellite communication systems, Internet of Things (IoT), narrowband Internet of Things (NB-IoT) systems, Global System for Mobile Communications (GSM), Enhanced Data Rate for GSM Evolution (EDGE), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access 2000 (CDMA2000), Time Division-Synchronization Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), and fifth-generation (5G) communication systems, such as 5G New Radio (NR). The three major application scenarios of 5G mobile communication systems are also applicable: enhanced mobile broadband (eMBB), ultra-reliable low latency communications (uRLLC), and massive machine-type communications. Type communications (mMTC), device-to-device (D2D) communication systems, machine-to-machine (M2M) communication systems, vehicle-to-everything (V2X) communication systems, 6th generation (6G) communication systems or other future evolution systems, or other wireless communication systems using wireless access technologies, etc., as long as there is a need for MBS data transmission in the communication system, the technical solution of the embodiments of this application can be adopted.

[0081] For ease of explanation, the embodiments of this application mainly take a 5G communication system as an example.

[0082] See Figure 1 This is a schematic diagram of the network architecture of a 5G communication system, including the radio access network (RAN) and the core network.

[0083] A wireless access network (WLAN) is used to implement functions related to wireless access. A WLAN includes at least one WLAN device and may also include at least one terminal. The terminal connects wirelessly to the WLAN device, and the WLAN device connects to the core network wirelessly or via a wired connection.

[0084] The radio access network equipment can be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next-generation NodeB (gNB) in a 5G mobile communication system, a next-generation base station in a 6G mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system; it can also be a module or unit that performs some of the functions of a base station, for example, it can be a central unit (CU) or a distributed unit (DU). Here, the CU performs the functions of the radio resource control protocol and the packet data convergence protocol (PDCP) of the base station, and can also perform the functions of the service data adaptation protocol (SDAP); the DU performs the functions of the radio link control layer and the medium access control (MAC) layer of the base station, and can also perform some or all of the physical layer functions. For specific descriptions of the above-mentioned protocol layers, please refer to the relevant technical specifications of the 3rd Generation Partnership Project (3GPP). Wireless access network equipment can be macro base stations, micro base stations, indoor stations, relay nodes, or donor nodes, etc. The embodiments of this application do not limit the specific technologies or equipment forms used in the wireless access network equipment.

[0085] A terminal can also be called a terminal device, user equipment (UE), mobile station, mobile terminal, etc. Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc. The embodiments of this application do not limit the specific technologies or device forms used in the terminals.

[0086] The core network is responsible for functions such as session management, mobility management, policy management, security authentication, and maintaining subscription data for the mobile network. The core network mainly includes the following network elements: 1) Access and Mobility Management Function (AMF): primarily responsible for mobility management in the mobile network, such as user location updates, user network registration, and user handover; 2) Session Management Function (SMF): primarily responsible for session management in the mobile network, such as session establishment, modification, and release. Specific functions include: 3) User plane function (UPF): mainly responsible for processing user packets, such as forwarding and billing; 4) Policy control function (PCF): responsible for providing policies to AMF and SMF, such as quality of service (QoS) policies and slice selection policies; 5) Unified data management (UDM): used to store user data, such as subscription information and authentication / authorization information; 6) Application function (AF): responsible for providing services to the 3GPP network, such as influencing service routing and interacting with PCF for policy control.

[0087] In addition, the communication system also includes a data network (DN), which is a network that provides data transmission services to users, such as IP Multimedia Service (IMS) and the Internet. Terminals can access the DN by establishing a Protocol Data Unit (PDU) session between the terminal, the RAN, the UPF, and the DN.

[0088] It should be understood that Figure 1 This is merely an illustration; the communication system may also include other network elements or devices, and this application does not impose any restrictions. Furthermore, Figure 1 The number of network elements or devices shown is only for illustrative purposes; the actual number may be more or less.

[0089] See Figure 2 This is a schematic diagram of the architecture of a 5G multicast / broadcast service (MBS) system in a 5G communication system. MBS is a point-to-multipoint bearer service used to send data from a single data source to multiple receivers. The PDU session corresponding to MBS is called an MBS session.

[0090] like Figure 2 As shown, the MBS architecture includes: an SMF network element for MBS session configuration, namely the multicast / broadcast session management function (MB-SMF); a UPF network element for MBS data transmission, namely the MB-UPF; and a multicast / broadcast service function (MBSF) for configuring MBS requirements between the AF and MB-SMF. The MB-UPF can be configured by the MB-SMF and connects to the AF / application server (AS) via the N6 connection to obtain MBS data. Simultaneously, it connects to the NG-RAN via the N3 connection to send MBS data to the RAN. The MBSF primarily initiates MBS session establishment / management requests to the MB-SMF based on the multicast service requirements of the AF / AS and performs related configurations.

[0091] It should be understood that, in this document, MB-SMF can be used specifically for implementing MBS session configuration functions, or it can be used simultaneously for implementing MBS session configuration functions and other functions; this application does not impose any restrictions. Similarly, MB-UPF can be used specifically for implementing MBS data transmission functions, or it can be used simultaneously for implementing MBS data transmission functions and other functions; this application does not impose any restrictions. Likewise, MBSF can be used specifically for implementing MBS demand configuration functions, or it can be used simultaneously for implementing MBS demand configuration functions and other functions; this application does not impose any restrictions.

[0092] It is important to note that, in Figure 2 In this configuration, some ports carry the "mb" identifier, indicating that these ports may have undergone partial modifications to meet multicast / broadcast requirements and have the function of transmitting MBS-related services. Their basic functions are compatible with port numbers without "mb". For example, Nmb1 represents port N1, which has been partially modified for multicast / broadcast requirements, and N6mb represents port N6, which has been partially modified for multicast / broadcast requirements.

[0093] This article defines the network element that provides MBS data for MB-UPF as a multicast source node. Figure 2 In the scenario shown, the multicast source node can be either an AS or an AF. For example, if the AS is integrated on the AF (or the AS and AF are integrated into one network element), the multicast source node can be considered as the AF, and the MB-UPF obtains MBS data from the AF by establishing an N6 connection with the AF; if the AF and AS are two different network elements, such as the AF located in the core network and the AS located in the DN, the multicast source node can be considered as the AS, and the MB-UPF obtains MBS data from the AS by establishing an N6 connection with the AS.

[0094] Of course, the multicast source node can be other network elements besides the AS. For example, an MB-STF can be set between the MB-UPF and the AF / AS. The MB-UPF can then establish an N5 connection with the multicast / broadcast service transport function (MBSTF) and obtain MBS data from the AF / AS through the MB-STF. In this case, the multicast source node can be considered as the MB-STF. This application does not limit the specific implementation method of the multicast source node.

[0095] Furthermore, in specific implementations, multicast source nodes can have different names, such as MBS server, content provider, etc. Alternatively, the name of a network element can be directly used to refer to the multicast source node, for example, in... Figure 2 In the scenario shown, the multicast source node can also be referred to as AF / AS.

[0096] There are two ways for MB-UPF and multicast source nodes to obtain multicast data:

[0097] Method 1: In the MBS session configuration process, the MB-SMF obtains the downlink port allocated by the MB-UPF for establishing the Ingress Tunnel, and sends this downlink port information to the multicast source node via the AF, whereby the multicast source node establishes the downlink multicast channel. Subsequently, during MBS session transmission, the MB-UPF receives MBS data from the multicast source node through the Ingress Tunnel.

[0098] Method 2: The DN where the multicast source node resides supports multicast transmission. MBS data is sent in the form of multicast packets, and the multicast tree (i.e., the transmission path of the multicast signal) is maintained through multicast control protocols such as Internet Group Management Protocol (IGMP), Protocol Independent Multicast (PIM), and Multicast Listener Discovery (MLD). During the MBS session configuration or establishment process, the MB-SMF provides the MB-UPF with the multicast address corresponding to the multicast source node. The MB-UPF then sends a Join message based on protocols such as IGMP, PIM, and MLD to the multicast source node, thus joining the multicast tree (i.e., connecting the MB-UPF node to the multicast tree, allowing it to receive downlink MBS data from the multicast source node as a node in the multicast tree). Afterward, the MB-UPF receives MBS data from the multicast source node based on the transmission path of the multicast tree.

[0099] It should be understood that the transmission paths of the Ingress Tunnel created by method 1 and the multicast tree created by method 2 are both used to transmit MBS data from the multicast source node to the MB-UPF. In the following text, these two transmission channels can be collectively referred to as data transmission channels.

[0100] For example, see Figure 3 The flowchart for configuring an MBS session includes the following steps:

[0101] S301 and AF send a TMGI allocation request to NEF / MBSF. The TMGI is used to identify an MBS session.

[0102] S302 and NEF / MBSF perform authorization verification for AF.

[0103] S303, NEF / MBSF discovers and selects an MB-SMF to manage the MBS session.

[0104] S304, NEF / MBSF sends a TMGI allocation request to the selected MB-SMF.

[0105] S305 and MB-SMF allocate a TMGI and feed the TMGI back to NEF / MBSF. NEF / MBSF then feeds back the allocated TMGI to AF.

[0106] It should be understood that S301 to S305 are optional. Figure 3 The dashed line in the middle indicates that it is optional.

[0107] S306, AF sends a Service Announcement to the UE, informing the UE of information related to the MBS session, including the MBS session ID (TMGI or source specific multicast address, which identifies a multicast service through the multicast address and source address), and other MBS session-related information.

[0108] S307: The AF sends a multicast session request to the NEF / MBSF, and may provide the NEF / MBSF with information related to the MBS session. If S301-S305 were not executed before, the AF provides the NEF / MBSF with a source-specific multicast address or requests the network to assign an identifier (such as TMGI) for the MBS session. MBS-related information may also include QoS requirements. The NEF / MBSF performs authorization verification for the content provider.

[0109] S308 and NEF / MBSF discover and select MB-SMF as the entry management network element.

[0110] S309, NEF / MBSF requests MB-SMF to allocate an identifier and ingress resources for the MBS session, and indicates whether an ingress transport address is required. It also provides MB-SMF with the service area for the MBS session.

[0111] S3010 and MB-SMF update NF configuration to NRF based on the MBS session ID they serve.

[0112] S3011, MB-SMF sends a multicast session management policy binding request (SM Policy Association Request) to MB-PCF (PCF with multicast / broadcast service management function), which includes MBS session ID, AF identifier, and QoS requirements.

[0113] S3012, MB-PCF registers with Binding Support Function (BSF) (BSF is mainly used to determine the binding relationship between session and PCF), the MB-PCF is responsible for controlling the MBS session, and provides a policy association identifier for the MBS session ID.

[0114] S3013, MB-PCF sends a multicast / broadcast session management policy association response (SM MBS PolicyAssociation Response) to MB-SMF, which includes the policy related to the MBS session ID.

[0115] S3014, MB-SMF selects MB-UPF according to the strategy and establishes a data transmission channel between MB-UPF and multicast source node.

[0116] If MBS data is received using method 1, the MB-SMF requests the MB-UPF to reserve user plane entry resources and requests the MB-UP to allocate a downlink port for establishing an Ingress Tunnel.

[0117] If MBS data is received using method 2, the MB-SMF configures the multicast address of the multicast source node to the MB-UPF and requests the MB-UPF to join the multicast tree of the multicast source node. Of course, the MB-UPF may also join the multicast tree during the MBS session establishment process.

[0118] S3015. If MB-SMF requests an Ingress Tunnel, MB-UPF will send back the Ingress address to MB-SMF. This address includes the IP address of MB-UPF and the downstream port of MB-UPF.

[0119] S3016, MB-SMF provides the Ingress Address and TMGI to NEF / MBSF, and may also include a success / failure indication for the reservation of transmission resources.

[0120] S3017 and NEF / MBSF send the Ingress Address and TMGI back to AF.

[0121] S3018, AF sends a Service Announcement to UE.

[0122] See Figure 4This diagram illustrates the states of an MBS session. MBS session states include start / stop, configuration complete, inactive (also known as MBS session establishment complete), and active. After the MBS service begins, the MBS session configuration process is performed to configure service requirements and other parameters. Then, the MBS session establishment process creates the MBS session transmission path, and the MBS session activation process activates the data transmission of the MBS session.

[0123] According to S3014, Method 1 involves configuring the IngressTunnel from MB-UPF to the multicast source node during the MBS session configuration process, i.e., establishing a data transmission path from MB-UPF to the multicast source node. Furthermore, to ensure the transmission rate of the MBS session, processing resources for MB-UPF need to be reserved for the MBS session. Figure 4 It is known that actual MBS data transmission only occurs when the MBS session is active. Therefore, the data transmission path from MB-UPF to the multicast source node established by Method 1 before the MBS session is active will waste reserved MB-UPF processing resources. Method 2, on the other hand, adds MB-UPF to the multicast tree during the MBS session configuration or establishment process, thus establishing a data transmission path from MB-UPF to the multicast source node. Similarly, according to... Figure 4 It is known that actual MBS data transmission only occurs when the MBS session is active. Therefore, after the MB-UPF is added to the multicast tree and before the MBS session is active, since no terminal receives MBS data, and the MB-UPF needs to continuously receive multicast data packets from the multicast source node and discard the data packets through packet filtering, there is also a problem of wasted MB-UPF processing resources.

[0124] To address the aforementioned technical problems, this application provides a technical solution that allows for more flexible configuration of the timing of establishing a data transmission channel between the MB-UPF and the multicast source node. This improves the flexibility of establishing and / or releasing data transmission channels while ensuring the quality of MBS session communication, and saves MB-UPF processing resources.

[0125] The following description is in conjunction with the accompanying drawings. In the following description, the technical solutions provided in the embodiments of this application are applied to... Figure 2 The application scenario shown is an example.

[0126] See Figure 5 This is a flowchart of configuring an MBS session provided in an embodiment of this application, in which the method is applied... Figure 2 Taking the system shown as an example, the method includes:

[0127] S501, MB-SMF detected the first event for the MBS session.

[0128] S502, MB-SMF establishes or releases a data transmission channel between MB-UPF and multicast source node for MBS session according to the first event and the policy corresponding to MBS session. The policy corresponding to MBS session is used to determine the timing for establishing or releasing the data transmission channel for MBS session.

[0129] For ease of description, this application refers to the strategy used to determine the timing of establishing a data transmission channel for an MBS session as the first strategy, and the strategy used to determine the timing of releasing a data transmission channel for an MBS session as the second strategy.

[0130] (I) The following describes the specific scheme by which MB-SMF establishes a data transmission channel between MB-UPF and multicast source node for MBS session based on the first event and the first policy corresponding to MBS session.

[0131] Specifically, the first strategy may include at least one first-type event (or an indication parameter corresponding to the at least one first-type event), wherein the first-type event is used to trigger the MB-SMF to establish a data transmission channel for the MBS session. In other words, as long as the MB-SMF detects the occurrence of the first-type event in the first strategy, the MB-SMF establishes a data transmission channel between the MB-UPF and the multicast source node for the MBS session.

[0132] For example, if the first event detected by MB-SMF in S501 matches the second event in the first policy, where the second event is one of at least one of the first type of events, then MB-SMF establishes a data transmission channel between MB-UPF and the multicast source node for the MBS session. Optionally, MBSMF may also instruct MB-UPF to reserve processing resources for the MBS session.

[0133] The first event detected by the MB-SMF can be a notification from another network function (NF) regarding a second type of event, or it can be the MB-SMF detecting a change in the MBS state. This application does not impose any restrictions on this.

[0134] For example, the following are some possible Type I events:

[0135] 1) At least one event in the MBS session configuration process corresponding to the MBS session. For example, it could be the MB-SMF receiving the MBS session start request from the MBSF / NEF, or the MB-SMF receiving the session management policy (SMpolicy) configured for the MBS session by the MB-PCF.

[0136] 2) At least one event in the MBS session establishment process corresponding to the MBS session. For example, it could be that the MB-SMF receives a request from the SMF to query the multicast session context, or the MB-SMF receives a request from the RAN to establish an N3 transport tunnel from the MB-UPF to the RAN, or other SMFs send a request to the MB-SMF to establish an N9 transport tunnel between the MB-UPF and the UPF, etc.

[0137] 3) At least one event in the MBS session activation process corresponding to the MBS session. For example, specifically, it could be the MB-SMF receiving an AF / MBSF / NEF notification that the MBS session has started transmission.

[0138] 4) At least one event in the MBS session start transmission process corresponding to the MBS session. For example, it could be that the MB-SMF discovers the start of service transmission based on the start time record of the MBS service, or that the MB-SMF has a pre-configured start time for the MBS session transmission, and the MB-SMF discovers that the start time for the MBS session transmission has arrived, etc.

[0139] It should be understood that the above four examples are merely examples and not specific limitations.

[0140] In one possible design, the first policy corresponding to different MBS sessions can contain different events.

[0141] For example, for services with long transmission durations and large data volumes, such as video downloads, a data transmission channel can be established close to the MBS session transmission process, such as during the MBS session start transmission process or the MBS session activation process. Accordingly, the events included in the first strategy can be at least one event in the MBS session start transmission process or at least one event in the MBS session activation process.

[0142] For example, for services with high real-time transmission requirements, such as live streaming and virtual reality (VR), data transmission channels can be established at an earlier time to ensure the real-time performance of MBS data transmission. For instance, a data transmission channel can be established during the MBS session configuration process or the MBS session establishment process. Accordingly, the events included in the first strategy can be at least one event in the MBS session configuration process or at least one event in the MBS session establishment process.

[0143] For example, for services with a late start time, a data transmission channel can be established at an even later time. For instance, if the current time is 9:00, and the AF has configured the multicast service but indicates that the MBS session will start at 10:00, then the data transmission tunnel can be established during the session establishment process or when the MBS session starts transmitting, and the processing resources of the UPF can be reserved. Accordingly, the events included in the first strategy can be at least one event in the MBS session establishment process or at least one event in the MBS session start transmitting process.

[0144] In this way, different data transmission channels can be established at different times for different MBS sessions, saving resources while taking into account the transmission needs of different MBS sessions.

[0145] In one implementation, the first strategy may further include a data transmission channel establishment method (or data transmission channel type) corresponding to each of the at least one first-type events, wherein the data transmission channel establishment method is either a first method or a second method; wherein the first method involves the MB-UPF allocating a port for communication with the multicast source node and notifying the multicast source node of the port (see the description of method 1 above); and the second method involves the MB-UPF sending a request to the multicast source node to join the multicast tree corresponding to the multicast source node (see the description of method 2 above). Correspondingly, the MB-SMF establishes a data transmission channel for the MBS session according to the data transmission channel establishment method corresponding to the second event.

[0146] In practical implementation, the first strategy can be represented by encoding. For example, Table 1 lists several possible first strategies, where 1, 2, 3, and 4 represent four different times for establishing data transmission channels, such as: MBS session configuration process, MBS session establishment process, MBS session activation process, and MBS session start time. a and b represent two different data transmission channel establishment methods, such as method 1 and method 2. If the first strategy corresponding to MB-SMF is 2, b, it means that after MB-SMF detects one or more events in the MBS session establishment process (e.g., MB-SMF receives a request from another SMF to initiate a query of the multicast session context, or MB-SM receives a request from the RAN to establish an N3 transmission tunnel from MB-UPF to the RAN, or MB-SM receives a request from another SMF to initiate the establishment of an N9 transmission tunnel between MB-UPF and other UPFs, etc.), the data transmission channel is established by adding MB-UPF to the multicast tree of the multicast source node.

[0147] Table 1 Examples of the First Strategy

[0148]

[0149] Of course, in practical applications, the first strategy may not include the method of establishing the data transmission channel. Instead, the MB-SMF may choose one of the two methods, Method 1 and Method 2, to establish the data transmission channel based on the local policy or the policy sent by other network elements (such as PCF). This application does not impose any restrictions.

[0150] Based on the above, the embodiments of this application, through policy configuration, can configure different timings for establishing data transmission channels for different MBS sessions, thereby improving the flexibility of establishing data transmission channels while ensuring the quality of MBS service communication, and thus saving resources.

[0151] The following describes the method for obtaining the first strategy in MB-SMF.

[0152] Method 1: MB-SMF can obtain the first policy from AF.

[0153] Specifically, the AF generates the first policy, and then the AF can send the first policy directly to the MB-SMF, or the AF can send the first policy to the MB-SMF through other network elements (such as NEF or MBSF, etc.). This application does not impose any restrictions.

[0154] In specific implementation, the AF can issue the first policy to the MB-SMF according to the session granularity, or the AF can issue the first policy to the MB-SMF according to the business granularity; this application does not impose any restrictions.

[0155] For example, such as Figure 6 The image shows an example of an MBS session configuration process provided in an embodiment of this application, including:

[0156] S601~S602 and AF can carry the data packet characteristics of MBS service (such as IP address range, data packet description rules, etc.) and the first policy in the MBS session configuration request sent to MB-SMF, or carry the identification information of MBS session (such as TMGI, etc.) and the first policy.

[0157] If the first strategy includes a method for establishing a data transmission channel and that method is method 2, then AF may also simultaneously send the source specific multicast IP address of the multicast session.

[0158] After receiving the first policy, S603 and MB-SMF record the first policy.

[0159] Specifically, MB-SMF stores the first policy in the context of the MBS session.

[0160] It should be understood that if the AF (Active Advisor) issues the first policy to the MB-SMF at the session level, the MB-SMF can directly use the MBS session identifier as an index to record the first policy of the MBS session. If the AF issues the first policy to the MB-SMF at the service level, the MB-SMF can map the service to the MBS session / Quality of Service (QoS) flow, and then record the first policy corresponding to the MBS session at the granularity of the MBS session / QoS flow.

[0161] S604 and MB-SMF can receive an event (such as the first event) that may trigger the establishment of a data transmission channel in the subsequent process, and determine whether to establish a data transmission channel and how to establish the data transmission channel according to the first strategy.

[0162] MB-SMF is the process of establishing a data transmission channel between MB-UPF and the multicast source node for the MBS session after determining that a data transmission channel needs to be established.

[0163] If the MB-SMF determines that the data transmission channel establishment method is mode 1 (i.e., the data transmission channel type is Ingress Tunnel) based on the first policy, the local policy, or the policy obtained from the PCF, then:

[0164] The S605A and MB-SMF send an MB-UPF configuration request to the MB-UPF to request the configuration of the downlink port used to establish the data transmission channel and to request the MB-UPF to reserve the corresponding processing resources.

[0165] The S606A and MB-UPF send a configuration response back to the MB-SMF to provide feedback on the MB-UPF's entry address (including the MB-UPF's IP address and downlink port).

[0166] S607A and MB-SMF send the MB-UPF entry address back to AF.

[0167] If the MB-SMF determines that the data transmission channel is established in mode 2 (i.e., the data transmission channel type is the multicast tree corresponding to the multicast source node) based on the first policy, the local policy, or the policy obtained from the PCF, and the MB-SMF does not have the multicast address corresponding to the multicast source node stored locally, then:

[0168] S605B and MB-SMF query AF for the multicast address corresponding to the multicast source node;

[0169] S606B and MB-SMF send MB-UPF configuration requests to MB-UPF, including configuring the multicast address corresponding to the multicast source node for MB-UPF and notifying MB-UPF to join the multicast tree corresponding to the multicast source node.

[0170] S607B and MB-UPF can join the multicast tree corresponding to the multicast source node, for example by sending a join message based on protocols such as IGMP / PIM / MLD to the multicast source node.

[0171] In this method, the timing of establishing the data transmission channel can be directly provided by the AF as an MBS parameter, and the multicast source node can flexibly configure the timing of establishing the data transmission channel corresponding to each MBS session according to the actual needs of the service.

[0172] Method 2: The AF does not directly issue the first policy, but issues the first instruction information. After the MB-SMF obtains the first instruction information from the AF, it generates the first policy based on the first instruction information.

[0173] Specifically, the AF generates first indication information, which is used to determine one or more events. Then, the AF can directly send the first indication information to the MB-SMF, or the AF can send the first indication information to the MB-SMF through other network elements (such as NEF or MBSF), which is not limited in this application. After receiving the first indication information, the MB-SMF determines the one or more events based on the first indication information and generates a first policy corresponding to the MBS session. The first policy includes the one or more events (or includes parameters used to indicate the one or more events). Optionally, the first indication information is carried in the MBS session configuration request sent by the AF to the MB-SMF.

[0174] The first indication information may include one or more of the following:

[0175] Instruction information 1 is used to indicate the MBS session establishment process corresponding to the MBS session. Accordingly, the MB-SMF determines event 1 (the MBS session establishment process corresponding to the MBS session) based on instruction information 1 and generates a first policy containing event 1. Subsequently, after detecting the occurrence of event 1, the MB-SMF establishes a data transmission channel.

[0176] Instruction information 2 is used to instruct the MBS session activation process corresponding to the MBS session. Accordingly, the MB-SMF determines event 2 (the MBS session activation process corresponding to the MBS session) based on instruction information 2 and generates a first policy containing event 2. Subsequently, after detecting the occurrence of event 2, the MB-SMF establishes a data transmission channel.

[0177] Instruction information 3 is used to indicate the MBS session configuration process corresponding to the MBS session. Accordingly, the MB-SMF determines event 3 (the MBS session configuration process corresponding to the MBS session) based on instruction information 3 and generates a first policy containing event 3. Subsequently, after detecting the occurrence of event 3, the MB-SMF establishes a data transmission channel.

[0178] Indication information 4 is used to indicate the start of the transmission process for the MBS session corresponding to the MBS session. Accordingly, the MB-SMF determines event 4 (the start of the transmission process for the MBS session corresponding to the MBS session) based on indication information 4 and generates a first policy containing event 4. Subsequently, after detecting the occurrence of event 4, the MB-SMF establishes a data transmission channel.

[0179] Indication information 5 indicates the start time of the MBS session. Accordingly, the MB-SMF determines event 5 (the start time of the MBS session) based on indication information 5 and generates a first policy containing event 5. Subsequently, after detecting event 5 (i.e., the arrival of the MBS session start time), the MB-SMF establishes a data transmission channel. In specific implementation, the MB-SMF can set a timer based on the MBS session start time, so that the timer expires exactly when the MBS session start time arrives. Event 5 can then also be a timer timeout; that is, the MB-SMF establishes a data transmission channel by detecting the timer timeout.

[0180] Indication information 6 indicates the QoS requirements of the MBS session. Different QoS requirements can be mapped to different data transmission channel establishment times.

[0181] It should be understood that the above examples are merely illustrations and not specific limitations.

[0182] When the first instruction information includes multiple items as described above, the first strategy can be generated based on the instruction information with the highest priority according to a preset priority order. For example, the priority order is: Instruction 1 > Instruction 2 > Instruction 3 > Instruction 4 > Instruction 5 > Instruction 6. It should be understood that this is merely an example and not a limitation; the actual priority order can be adjusted according to requirements.

[0183] For example, such as Figure 7 The image shows another example of an MBS session configuration process provided in this application embodiment, including:

[0184] S701~S702 and AF send MBS session configuration requests to NEF / MBSF or directly to MB-SMF. The MBS session configuration request includes the QoS requirements of the MBS session, as well as indication information 3 (MBS session configuration procedure) or indication information 5 (MBS session start time).

[0185] S703. After receiving the MBS session configuration request, the MB-SMF generates a first policy based on instruction information 3 or instruction information 5. For example, if the MB-SMF receives instruction information 3, the event included in the first policy is the MBS session configuration process, that is, the MB-SMF establishes a data transmission channel in the MBS session configuration process; if the MB-SMF receives instruction information 5, the event included in the first policy is the arrival of the MBS session start time, that is, the MB-SMF establishes a data transmission channel when the MBS session start time arrives.

[0186] The steps following S704 can be referred to the steps following S604 above, and will not be repeated here.

[0187] It should be understood that the above example is based on the AF sending the first instruction information to the MB-SMF according to the session granularity. Of course, in the specific implementation, the AF can also send the first instruction information to the MB-SMF according to the business granularity. This application does not impose any restrictions.

[0188] In this method, the timing of establishing the data transmission channel can be indirectly provided by the AF (i.e., the first strategy is generated by the MB-SMF based on the first indication information provided by the AF), and the multicast source node can flexibly configure the timing of establishing the data transmission channel corresponding to each MBS session according to the actual needs of the service.

[0189] Method 3: MB-SMF queries the first strategy from PCF or UDR.

[0190] For example, the MB-SMF sends a query message to the PCF using the MBS identifier (Identity document, ID) (or QoS flow ID) of a certain MBS session. The query message is used to query the first policy and QoS requirements corresponding to the MBS session. The PCF returns a response message, which carries the first policy and QoS requirements corresponding to the MBS session. The MB-SMF receives the response message returned by the PCF and obtains the first policy and QoS requirements corresponding to the MBS session.

[0191] In its implementation, the PCF can store the mapping relationship between QoS requirements and the first policy. After receiving a query message, the PCF sends a request to the UDR to query the QoS requirements corresponding to the MBS session; the UDR returns the query result to the PCF, namely the QoS requirements corresponding to the MBS session; after receiving the QoS requirements corresponding to the MBS session returned by the UDR, the PCF determines the first policy corresponding to the MBS session based on the QoS requirements corresponding to the MBS session and the mapping relationship between QoS requirements and the first policy; then the PCF returns the QoS requirements and the first policy corresponding to the MBS session to the MB-SMF in a response message.

[0192] Alternatively, the UDR can store the mapping relationship between QoS requirements and the first policy. After receiving the query message, the PCF sends a query message to the UDR to query the first policy and QoS requirements corresponding to the MBS session; after receiving the query message from the PCF, the UDR determines the QoS requirements corresponding to the MBS session, and then determines the first policy corresponding to the MBS session based on the QoS requirements corresponding to the MBS session and the mapping relationship between QoS requirements and the first policy, and returns the QoS requirements and first policy corresponding to the MBS session to the PCF; the PCF then returns the QoS requirements and first policy corresponding to the MBS session to the MB-SMF.

[0193] Alternatively, the UDR can store the mapping relationship between QoS requirements and the first policy. After receiving the query message, the PCF first sends a first query message to the UDR to query the QoS requirements corresponding to the MBS session; after receiving the first query message from the PCF, the UDR determines the QoS requirements corresponding to the MBS session and returns the QoS requirements corresponding to the MBS session to the PCF; after receiving the QoS requirements corresponding to the MBS session, the PCF sends a second query message to the UDR to query the first policy corresponding to the MBS session; after receiving the second query message from the PCF, the UDR determines the first policy corresponding to the MBS session based on the QoS requirements corresponding to the MBS session, the mapping relationship between QoS requirements and the first policy, and returns the first policy corresponding to the MBS session to the PCF; finally, the PCF returns the QoS requirements and the first policy corresponding to the MBS session to the MB-SMF.

[0194] The mapping relationship between QoS requirements and the first policy can be such that different QoS levels correspond to different first policies (different first policies contain different events), or different latency requirements correspond to different first policies; this application does not impose specific limitations. For example, a data transmission channel can be created in the MBS session configuration process for services with a 5G QoS Identifier (5QI) set to a preset identifier (e.g., 1 or 2). (Where 5QI can be mapped to specific QoS requirements, such as a packet error rate of 0.01%, latency of 100ms, and other QoS requirement information when 5QI is 1). Alternatively, a data transmission channel can be created in the MBS session configuration process for MBS sessions with a service latency of a preset latency (e.g., less than 5ms).

[0195] Of course, in practical applications, other network elements can also store the mapping relationship between QoS requirements and the first policy, and perform the mapping operation from QoS requirements to policies; this application does not impose any restrictions. For example, the MB-SMF can also store the mapping relationship between QoS requirements and the first policy, and the MB-SMF determines the first policy corresponding to the MBS session based on the QoS requirements of the MBS session and the mapping relationship between QoS requirements and the first policy.

[0196] Optionally, the AF can include the MBS session ID and QoS requirements corresponding to the MBS session in the MBS session configuration request and send it to the UDR via network elements such as NEF or MBSF.

[0197] For example, such as Figure 8 The image shows another example of an MBS session configuration process provided in this application embodiment, including:

[0198] S801 and AF send an MBS session configuration request to NEF / MBSF, which carries the MBS session ID and QoS requirements corresponding to the MBS session.

[0199] S802, UDR and NEF / MBSF interact to update the information stored locally in UDR, such as the MBS session ID and QoS requirements corresponding to the MBS session;

[0200] S803, MB-SMF queries the first strategy from PCF or UDR;

[0201] The steps following S804 can be referred to the steps following S603 above, and will not be repeated here.

[0202] In this method, the timing of establishing a data transmission channel is configured as a parameter within the core network in the PCF / UDR. The AF does not directly provide this parameter information, but only provides QoS requirement information. Thus, operators can select different data transmission channel establishment times for different MBS sessions according to their operating strategies. The decision-making power is in the hands of the operators, which facilitates deployment (for example, only the MB-SMF and PCF / UDR processing logic needs to be modified, and the changes to the existing MBS architecture are minor).

[0203] (II) The following describes the scheme by which MB-SMF releases the data transmission channel between MB-UPF and the multicast source node for the MBS session based on the first event and the second strategy corresponding to the MBS session.

[0204] Specifically, the second strategy includes at least one second type of event (or an indication parameter corresponding to the at least one second type of event), which is used to trigger MB-SMF to release the data transmission channel for the MBS session. In other words, as long as MB-SMF detects the second type of event in the second strategy, MB-SMF will release the data transmission channel between MB-UPF and the multicast source node for the MBS session.

[0205] For example, if the first event detected by MB-SMF in S501 matches the third event in the second strategy, where the third event is one of at least one of the second type of events, then MB-SMF releases the data transmission channel between MB-UPF and the multicast source node for the MBS session. Optionally, MB-SMF releases the processing resources of MB-UPF reserved for the MBS session.

[0206] Similarly, the first event detected by the MB-SMF could be a notification received by the MB-SMF from other network elements regarding a second type of event, or the MB-SMF detecting a change in the MBS state; this application does not impose any restrictions.

[0207] For example, the following are some possible examples of the second type of event:

[0208] 1) At least one event in the MBS session cancellation configuration process corresponding to the MBS session;

[0209] 2) At least one event in the MBS session release procedure corresponding to the MBS session. For example, it could be that the MB-SMF receives a request from another SMF to the MB-SMF to request the UE to leave the MBS session, or receives a request from the RAN to the MB-SMF to release the N3 transmission tunnel from the MB-UPF to the RAN, or receives a request from another SMF to the MB-SMF to release the N9 transmission tunnel between the MB-UPF and the UPF, etc.

[0210] 3) At least one event in the MBS session deactivation process corresponding to the MBS session. For example, this could be the MB-SMF receiving a message from the MB-UPF reporting that it has not received multicast data packets for a period of time, or the MB-SMF receiving a message from the AF / MBSF / NEF notifying it that multicast session data transmission has stopped, etc.

[0211] 4) At least one event in the MBS session termination transmission process corresponding to the MBS session. For example, specifically, it could be that the MB-SMF discovers that the service has stopped sending based on the MBS service termination time record, or the MB-SMF receives a notification from the AF that the multicast service has stopped sending, or the MB-SMF has a pre-configured MBS session termination time and discovers that the MBS session termination time has arrived, etc.

[0212] It should be understood that the above four examples are merely examples and not specific limitations.

[0213] Similarly, different events can be included in the second strategy corresponding to different MBS sessions.

[0214] For example, for services with long transmission duration and large data traffic, such as video download, the data transmission channel can be released near the end of the MBS session transmission process, such as during the MBS session end transmission process or the MBS session deactivation process. Accordingly, the events included in the first strategy can be at least one event in the MBS session end transmission process or at least one event in the MBS session deactivation process.

[0215] For example, for services with high real-time transmission requirements, such as live streaming and VR, data transmission channels can be released at a later time to ensure the real-time performance of MBS data transmission (mainly corresponding to the needs of service reconnection scenarios). This can be achieved by releasing the data transmission channel during the MBS session cancellation configuration process or the MBS session cancellation establishment process. Accordingly, the events included in the first strategy can be at least one event from the MBS session cancellation configuration process or at least one event from the MBS session release process. In this way, different data transmission channel release times can be implemented for different MBS sessions, saving resources while accommodating the transmission needs of different MBS sessions.

[0216] In practical implementation, the second strategy can be represented by encoding. For example, Table 2 lists several possible second strategies, where 1', 2', 3', and 4' represent four different times for releasing the data transmission channel, such as: MBS session cancellation configuration process, MBS session release process, MBS session deactivation process, and MBS session end time. If the second strategy corresponding to MB-SMF is 3', it means that the data transmission channel is released after MB-SMF detects one or more events in the MBS session deactivation process. Since the type of the data transmission channel is determined during the release phase, the second strategy does not need to carry the type of the data transmission channel (i.e., the specific establishment method corresponding to the data transmission channel to be released during the establishment phase, i.e., methods 1 and 2 above).

[0217] Table 2 Examples of the Second Strategy

[0218]

[0219] Of course, the second strategy can also include the type of data transmission channel, with a' and b' representing data transmission channel establishment methods 1 and 2, respectively. Table 3 lists several possible second strategies.

[0220] Table 3 Examples of the Second Strategy

[0221]

[0222] In addition, the first and second strategies can also be jointly encoded, as shown in Table 4, where 1, 2, 3, and 4 represent four different times for releasing the data transmission channel, and 5, 6, 7, and 8 represent four different times for releasing the data transmission channel. a and b represent data transmission channel establishment methods 1 and 2, respectively.

[0223] Table 4 Examples of Strategy 1 and Strategy 2

[0224]

[0225] Based on the above, this application embodiment, through policy configuration, can configure different timings for releasing data transmission channels for different MBS sessions, thereby improving the flexibility of releasing data transmission channels while ensuring the quality of MBS service communication, and thus saving resources.

[0226] The following describes several possible methods for obtaining a second strategy using MB-SMF.

[0227] Method 1: MB-SMF can obtain the second strategy from AF.

[0228] Specifically, the AF generates a second policy, which can then be sent directly to the MB-SMF, or the AF can send the second policy to the MB-SMF through other network elements (such as NEF or MBSF). This application does not impose any restrictions on this.

[0229] Similarly, in specific implementations, the AF can issue a second policy to the MB-SMF according to the session granularity, or the AF can issue a second policy to the MB-SMF according to the business granularity; this application does not impose any restrictions.

[0230] For example, such as Figure 9 The image shows another example of an MBS session configuration process provided in this application embodiment, including:

[0231] In the MBS session configuration request sent to the MB-SMF by S901 to S902, the AF carries the packet characteristics of the MBS service (such as IP address range, packet description rules, etc.) and the second policy, or carries the identification information of the MBS session (such as TMGI, etc.) and the second policy. If the second policy includes the release method of the data transmission channel and the method is mode 2, the AF may also send the source specific multicast IP address of the multicast session at the same time.

[0232] It should be understood that the AF can send the first and second policies to the MB-SMF in the same message, or it can send the first and second policies to the MB-SMF in separate messages. For example, the AF can send the first and second policies to the MB-SMF simultaneously in the MBS session configuration request, or the AF can send the first policy to the MBS session configuration request and the second policy to the MBS session establishment request.

[0233] S903. After receiving the second policy, the MB-SMF records it. Specifically, the MB-SMF stores the second policy in the context of the MBS session. It should be understood that if the AF issues the second policy to the MB-SMF at the session level, the MB-SMF directly records the second policy of the MBS session using the MBS session identifier as an index. If the AF issues the second policy to the MB-SMF at the service level, the MB-SMF can map the service to the MBS session / QoS flow, and then record the second policy corresponding to the MBS session at the MBS session level.

[0234] S904 and MB-SMF can then receive events that may trigger the release of the data transmission channel in subsequent processes, and determine whether to release the data transmission channel based on the second strategy.

[0235] If the data transmission channel corresponding to the MBS session is established in mode 1 (i.e., the data transmission channel type is Ingress Tunnel), then:

[0236] The S905A and MB-SMF send release requests to the MB-UPF to request the release of the corresponding downlink ports and to request the MB-UPF to release the corresponding processing resources.

[0237] S906A and MB-UPF release responses to MB-SMF to provide feedback on the release status;

[0238] S907A and MB-SMF send an ingress tunnel release notification to AF.

[0239] If the data transmission channel corresponding to the MBS session is established in mode 2 (i.e., the data transmission channel type is the multicast tree corresponding to the multicast source node), then:

[0240] S905B and MB-SMF notify MB-UPF to release resources and leave the multicast tree corresponding to the multicast source node;

[0241] S906B and MB-UPF leave the multicast tree corresponding to the multicast source node; MB-UPF sends a leave request to the multicast source node or stops sending periodic request data packets (depending on the specific protocol configuration).

[0242] In this method, the release timing of the data transmission channel can be directly provided by the AF as an MBS parameter, and the multicast source node can flexibly configure the release timing of the data transmission channel corresponding to each MBS session according to the actual needs of the service.

[0243] Method 2: The AF does not directly issue the second policy, but issues the second instruction information. After the MB-SMF obtains the second instruction information from the AF, it generates the second policy based on the second instruction information.

[0244] Specifically, the AF generates second indication information, which is used to determine one or more events. The AF can then directly send the second indication information to the MB-SMF, or it can send it through other network elements (such as the NEF or MBSF), which is not limited in this application. After receiving the second indication information, the MB-SMF determines the one or more events based on the second indication information and generates a second policy corresponding to the MBS session. This second policy includes the one or more events (or includes parameters used to indicate the one or more events). Optionally, the second indication information can be carried in the MBS session configuration request sent by the AF to the MB-SMF.

[0245] Similarly, the second instruction information may include one or more of the following:

[0246] Instruction information 1' is used to indicate the MBS session release procedure corresponding to the MBS session. Accordingly, the MB-SMF determines event 1' (the MBS session release procedure corresponding to the MBS session) based on instruction information 1' and generates a second policy containing event 1'. Subsequently, after detecting the occurrence of event 1', the MB-SMF releases the data transmission channel.

[0247] Instruction information 2' is used to instruct the MBS session deactivation process corresponding to the MBS session. Accordingly, the MB-SMF determines event 2' (the MBS session deactivation process corresponding to the MBS session) based on instruction information 2' and generates a second policy containing event 2'. Subsequently, after detecting the occurrence of event 2', the MB-SMF releases the data transmission channel.

[0248] Instruction information 3' is used to instruct the MBS session cancellation configuration procedure corresponding to the MBS session. Accordingly, the MB-SMF determines event 3' (the MBS session cancellation configuration procedure corresponding to the MBS session) based on instruction information 3' and generates a second policy containing event 3'. Subsequently, after detecting the occurrence of event 3', the MB-SMF releases the data transmission channel.

[0249] Indication information 4' indicates the termination of the MBS session transmission process corresponding to the MBS session. Accordingly, the MB-SMF determines event 4' (the termination of the MBS session transmission process corresponding to the MBS session) based on indication information 4' and generates a second policy containing event 4'. Subsequently, after detecting the occurrence of event 4', the MB-SMF releases the data transmission channel.

[0250] Indication information 5' indicates the end time of the MBS session. Accordingly, the MB-SMF determines event 5' (the end time of the MBS session) based on indication information 5' and generates a second policy containing event 5'. Subsequently, after detecting event 5' (i.e., the end time of the MBS session has arrived), the MB-SMF releases the data transmission channel. In specific implementation, the MB-SMF can set a timer based on the end time of the MBS session, so that the timer expires exactly when the end time of the MBS session arrives. Event 5' can also be a timer timeout, meaning the MB-SMF releases the data transmission channel upon detecting a timer timeout.

[0251] Indication 6' indicates the QoS requirements of the MBS session. Different QoS requirements can be mapped to different data transmission channel release times.

[0252] It should be understood that the above examples are merely illustrations and not specific limitations.

[0253] When the first instruction information includes multiple items as described above, the first strategy can be generated based on the instruction information with the highest priority according to a preset priority order. For example, the priority order is: Instruction 1'>Instruction 2'>Instruction 3'>Instruction 4'>Instruction 5'>Instruction 6'. It should be understood that this is merely an example and not a limitation; the actual priority order can be adjusted according to requirements.

[0254] For example, the AF sends an MBS session configuration request to the MB-SMF via the NEF / MBSF or directly. This request includes the QoS requirements for the MBS session and either indication information 3' (MBS session cancellation configuration procedure) or indication information 5' (MBS session end time). Upon receiving the MBS session configuration request, the MB-SMF generates a second policy based on indication information 3' or 5'. For instance, if the MB-SMF receives indication information 3', the second policy includes the MBS session cancellation configuration procedure, meaning the MB-SMF releases the data transmission channel during this procedure. If the MB-SMF receives indication information 5', the second policy includes the MBS session end time, meaning the MB-SMF releases the data transmission channel when the MBS session end time arrives.

[0255] It should be understood that the AF can send the first and second indication information to the MB-SMF in the same message, or it can send the first and second indication information to the MB-SMF in separate messages. For example, the AF can send the first and second indication information to the MB-SMF simultaneously in the MBS session configuration request, or the AF can send the first indication information to the MB-SMF in the MBS session configuration request and the second indication information to the MBS session establishment request.

[0256] For example, such as Figure 10 The image shows another example of an MBS session configuration process provided in this application embodiment, including:

[0257] S1001~S1002, AF sends MBS session configuration requests to NEF / MBSF or directly to MB-SMF. The MBS session configuration request includes the QoS requirements of the MBS session, as well as indication information 3' (MBS session cancellation configuration procedure) or indication information 5' (MBS session end time).

[0258] S1003. After receiving the MBS session configuration request, the MB-SMF generates a second policy based on indication information 3' or indication information 5'. For example, if the MB-SMF receives indication information 3', the event included in the second policy is the MBS session cancellation configuration process, that is, the MB-SMF releases the data transmission channel during the MBS session cancellation configuration process; if the MB-SMF receives indication information 5', the event included in the first policy is the arrival of the MBS session end time, that is, the MB-SMF releases the data transmission channel when the MBS session end time arrives.

[0259] The steps following S1004 can be referred to the steps following S904 above, and will not be repeated here.

[0260] It should be understood that the above example is based on the AF sending the second instruction information to the MB-SMF according to the session granularity. Of course, in the specific implementation, the AF can also send the second instruction information to the MB-SMF according to the business granularity. This application does not impose any restrictions.

[0261] In this method, the release timing of the data transmission channel can be indirectly provided by the AF (i.e., the second strategy is generated by the MB-SMF based on the second indication information provided by the AF), and the multicast source node can flexibly configure the release timing of the data transmission channel corresponding to each MBS session according to the actual needs of the service.

[0262] Method 3: MB-SMF queries the second policy from PCF or UDR based on QoS requirements.

[0263] For example, the MB-SMF sends a query message to the PCF with the MBS session ID (or QoS flow ID) of a certain MBS session. The query message is used to query the second policy and QoS requirements corresponding to the MBS session. The PCF returns a response message, which carries the second policy and QoS requirements corresponding to the MBS session. The MB-SMF receives the response message returned by the PCF and obtains the second policy and QoS requirements corresponding to the MBS session.

[0264] In its implementation, the PCF can store the mapping relationship between QoS requirements and the second policy. After receiving a query message, the PCF sends a request to the UDR to query the QoS requirements corresponding to the MBS session; the UDR returns the query result to the PCF, namely the QoS requirements corresponding to the MBS session; after receiving the QoS requirements corresponding to the MBS session returned by the UDR, the PCF determines the second policy corresponding to the MBS session based on the QoS requirements corresponding to the MBS session and the mapping relationship between the QoS requirements and the second policy; then the PCF returns the QoS requirements and the second policy corresponding to the MBS session to the MB-SMF in a response message.

[0265] Alternatively, the UDR can store the mapping relationship between QoS requirements and the second policy. After receiving the query message, the PCF sends a query message to the UDR to query the second policy and QoS requirements corresponding to the MBS session. After receiving the query message from the PCF, the UDR determines the QoS requirements corresponding to the MBS session, and then determines the second policy corresponding to the MBS session based on the QoS requirements and the mapping relationship between the QoS requirements and the second policy. The UDR then returns the QoS requirements and the second policy corresponding to the MBS session to the PCF. The PCF then returns the QoS requirements and the second policy corresponding to the MBS session to the MB-SMF.

[0266] Alternatively, the UDR can store the mapping relationship between QoS requirements and the second policy. After receiving the query message, the PCF first sends a third query message to the UDR to query the QoS requirements corresponding to the MBS session; after receiving the third query message from the PCF, the UDR determines the QoS requirements corresponding to the MBS session and returns the QoS requirements corresponding to the MBS session to the PCF; after receiving the QoS requirements corresponding to the MBS session, the PCF sends a fourth query message to the UDR to query the second policy corresponding to the MBS session; after receiving the fourth query message from the PCF, the UDR determines the second policy corresponding to the MBS session based on the QoS requirements corresponding to the MBS session and the mapping relationship between the QoS requirements and the second policy, and returns the second policy corresponding to the MBS session to the PCF; finally, the PCF returns the QoS requirements and the second policy corresponding to the MBS session to the MB-SMF.

[0267] It should be understood that MB-SMF can query the first and second policies corresponding to a certain MBS session using the MBS session ID before and after the MBS session ID, or it can query the first and second policies corresponding to a certain MBS session simultaneously using the MBS session ID. This application does not impose any restrictions.

[0268] Similarly, the mapping relationship between QoS requirements and the second policy can be that different QoS levels correspond to different second policies (different second policies include different events included in the policies), or different latency requirements correspond to different second policies. This application does not impose specific limitations. For example, it is possible to set the MBS session corresponding to a service with 5QI of 1 or 2 to release the data transmission channel during the MBS session deconfiguration process, or to set the mapping rule that MBS sessions with a service latency of less than 5ms release the data transmission channel during the MBS session deconfiguration process.

[0269] Of course, in practical applications, other network elements can also store the mapping relationship between QoS requirements and the second policy, and perform the mapping operation from QoS requirements to policies; this application does not impose any restrictions. For example, the MB-SMF can also store the mapping relationship between QoS requirements and the second policy, and the MB-SMF determines the second policy corresponding to the MBS session based on the QoS requirements of the MBS session and the mapping relationship between the QoS requirements and the second policy.

[0270] Optionally, the AF can include the MBS session ID and QoS requirements corresponding to the MBS session in the MBS session configuration request and send it to the UDR via network elements such as NEF or MBSF.

[0271] For example, such as Figure 11 The image shows another example of an MBS session configuration process provided in this application embodiment, including:

[0272] S1101, AF sends an MBS session configuration request to NEF / MBSF, which carries the MBS session ID and QoS requirements corresponding to the MBS session;

[0273] S1102, UDR and NEF / MBSF interact to update the information stored locally in UDR, such as the MBS session ID and QoS requirements corresponding to the MBS session;

[0274] S1103, MB-SMF queries the second strategy from PCF or UDR;

[0275] The steps S1104 and the steps following S1104 can be referred to the steps S903 and the steps following S903 above, and will not be repeated here.

[0276] In this method, the timing of releasing the data transmission channel is configured as a parameter within the core network in the PCF / UDR. The AF does not directly provide this parameter information, but only provides QoS requirement information. Thus, operators can select different data transmission channel release times for different MBS sessions according to their operating strategies. The decision-making power is in the hands of the operators, which facilitates deployment (for example, only the MB-SMF and PCF / UDR processing logic needs to be modified, and the changes to the existing MBS architecture are minor).

[0277] It should be understood that the various embodiments described above in this application can be combined with each other to achieve different technical effects.

[0278] It is understood that, in order to achieve the functions in the above embodiments, each communication device includes hardware structures and / or software modules corresponding to perform each function. Those skilled in the art should readily recognize that, based on the units and method steps described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0279] Figure 12 and Figure 13 The diagram illustrates the possible structures of communication devices provided in embodiments of this application. These communication devices can be used to implement the functions described in the method embodiments above, and therefore can also achieve the beneficial effects of the method embodiments described above. In the embodiments of this application, the communication device can be as follows: Figure 2 The shown are MB-SMF, AF, PCF, UDM, etc., or chips in MB-SMF, AF, PCF, UDM, etc.

[0280] For example, when the communication device 1200 is used to implement the above method embodiments Figure 5 The functions of MB-SMF shown are as follows:

[0281] Transceiver unit 1201 is used to detect the first event for the MBS session;

[0282] The processing unit 1202 is configured to: if the first event matches the event in the policy corresponding to the MBS session, then establish or release a data transmission channel between the user plane function network element and the multicast source node for the MBS session, wherein the policy is used to determine the timing for establishing or releasing the data transmission channel for the MBS session.

[0283] For example, when the communication device 1200 is used to implement the above method embodiments Figure 6 or Figure 9 The function of AF shown is:

[0284] Processing unit 1202 is used to generate a policy corresponding to an MBS session, wherein the policy is used to determine the timing for establishing or releasing a data transmission channel between a user plane function network element and a multicast source node for an MBS session, and the policy includes one or more events.

[0285] The transceiver unit 1201 is used to send the policy corresponding to the MBS session to the session management function network element, or to send the policy corresponding to the MBS session to the session management function network element through the multicast / broadcast service function network element or the network presentation function network element.

[0286] For example, when the communication device 1200 is used to implement the above method embodiments Figure 7 or Figure 10 The function of AF shown is:

[0287] Processing unit 1202 is used to generate indication information, wherein the indication information is used to determine one or more events;

[0288] The transceiver unit 1201 is used to send indication information to the session management function network element so that the session management function network element generates a policy corresponding to the MBS session according to the indication information; wherein, the policy is used to determine the timing for establishing or releasing the data transmission channel between the user plane function network element and the multicast source node for the MBS session, and the policy includes one or more events.

[0289] For example, when the communication device 1200 is used to implement the above method embodiments Figure 8 or Figure 11 When the functions of PCF or UDM are shown:

[0290] The transceiver unit 1201 is used to receive query messages from the session management function network element, wherein the query message is used to query the policy and quality of service (QoS) requirements corresponding to the MBS session.

[0291] The processing unit 1202 is used to determine the policy and QoS requirements corresponding to the MBS session; the transceiver unit 1201 is also used to send a response message to the session management function network element, the response message carrying the policy and QoS requirements corresponding to the MBS session.

[0292] A more detailed description of the transceiver unit 1201 and the processing unit 1202 can be obtained directly from the relevant descriptions in the above method embodiments, and will not be repeated here.

[0293] like Figure 13 As shown, the communication device 1300 includes a processor 1310 and an interface circuit 1320. The processor 1310 and the interface circuit 1320 are coupled to each other. It is understood that the interface circuit 1320 can be a transceiver or an input / output interface.

[0294] Optionally, the communication device 1300 may also include a memory 1330 for storing instructions executed by the processor 1310, or storing input data required by the processor 1310 to execute instructions, or storing data generated after the processor 1310 executes instructions.

[0295] When the communication device 1300 is used to implement Figure 12 In the device shown, the processor 1310 is used to implement the functions of the processing unit 1202, and the interface circuit 1320 is used to implement the functions of the transceiver unit 1201.

[0296] Based on the same technical concept, this application also provides a chip, see [link to relevant documentation]. Figure 14 The chip may include logic circuitry and input / output interfaces. Optionally, it may also include a memory. The input / output interfaces can be used to receive code instructions (stored in the memory, which can be read directly from the memory or via other devices) and transmit them to the logic circuitry; the logic circuitry can be used to execute the code instructions to perform the methods described in the above method embodiments.

[0297] Alternatively, the input / output interface can also be a signal transmission interface circuit between the logic circuit and the transceiver. For example, in a transmitting scenario, the logic circuit is used to perform XX to obtain Y data (XX includes, but is not limited to, operations such as determining, judging, processing, calculating, searching, and comparing); the input / output interface can be used to send the Y data to the transmitter. As another example, in a receiving scenario, the input / output interface can be used to receive Z data from the receiver and send the Z data to the logic circuit; the logic circuit is used to perform XX processing on the Z data (XX includes, but is not limited to, operations such as determining, judging, processing, calculating, searching, and comparing).

[0298] For example, when the chip is used to implement the above method embodiments Figure 5 The functions of MB-SMF shown are as follows:

[0299] Input / output interface, used to input the first event for the MBS session;

[0300] The logic circuit is used to: if the first event matches the event in the policy corresponding to the MBS session, then establish or release the data transmission channel between the user plane function network element and the multicast source node for the MBS session, wherein the policy is used to determine the timing for establishing or releasing the data transmission channel for the MBS session.

[0301] For example, when the chip is used to implement the above method embodiments Figure 6 or Figure 9 The function of AF shown is:

[0302] A logic circuit is used to generate a policy corresponding to an MBS session, wherein the policy is used to determine when to establish or release a data transmission channel between a user plane function element and a multicast source node for an MBS session, and the policy includes one or more events.

[0303] Input / output interfaces are used to output the policies corresponding to the MBS session.

[0304] For example, when the chip is used to implement the above method embodiments Figure 7 or Figure 10 The function of AF shown is:

[0305] A logic circuit used to generate indication information, wherein the indication information is used to determine one or more events;

[0306] The input / output interface is used to output indication information so that the session management function network element can generate the policy corresponding to the MBS session based on the indication information. The policy is used to determine the timing for establishing or releasing the data transmission channel between the user plane function network element and the multicast source node for the MBS session. The policy includes one or more events.

[0307] For example, when the chip is used to implement the above method embodiments Figure 8 or Figure 11 When the functions of PCF or UDM are shown:

[0308] The input / output interface is used to input query messages from the session management function network element, where the query message is used to query the policy and quality of service (QoS) requirements corresponding to the MBS session;

[0309] Logic circuitry used to determine the policies and QoS requirements corresponding to MBS sessions;

[0310] The input / output interface is also used to output response messages, which carry the policies and QoS requirements corresponding to the MBS session.

[0311] A more detailed description of the above logic circuits and input / output interfaces can be obtained directly from the relevant descriptions in the above method embodiments, and will not be repeated here.

[0312] Based on the same technical concept, embodiments of this application also provide a computer-readable storage medium storing a computer program or instructions, which, when executed by a communication device, implements the method described in the above method embodiments.

[0313] Based on the same technical concept, embodiments of this application also provide a computer program product that, when run on a computer, causes the methods described in the above method embodiments to be executed.

[0314] It is understood that the processor in the embodiments of this application may be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor may be a microprocessor or any conventional processor.

[0315] The method steps in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Alternatively, the ASIC can reside in a base station or terminal. Of course, the processor and storage medium can also exist as discrete components in the base station or terminal.

[0316] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both types of storage media.

[0317] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0318] Depending on whether the specification uses "optional": In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. In the textual description of this application, the character " / " generally indicates an "or" relationship between the preceding and following related objects; in the formulas of this application, the character " / " indicates a "division" relationship between the preceding and following related objects. "Including at least one of A, B, and C" can mean: including A; including B; including C; including A and B; including A and C; including B and C; including A, B, and C.

[0319] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

Claims

1. A method for configuring a multicast / broadcast service MBS session, characterized in that, include: The session management function network element detects the first event for the MBS session; The session management function network element establishes or releases a data transmission channel between the user plane function network element and the multicast source node for the MBS session according to the first event and the policy corresponding to the MBS session, wherein the policy is used to determine the timing for establishing or releasing the data transmission channel for the MBS session. The strategy includes multiple triggering events, each corresponding to an establishment condition for establishing the data transmission channel for the MBS session or a release condition for releasing the data transmission channel. The triggering events are selected from events in the configuration, establishment, activation, start transmission, deconfiguration, release, deactivation, or end transmission process of the MBS session.

2. The method as described in claim 1, characterized in that, The strategy includes a first strategy, which contains at least one first type of event. The first type of event is used to trigger the session management function network element to establish the data transmission channel for the MBS session. The session management function network element establishes or releases a data transmission channel between the user plane function network element and the multicast source node for the MBS session based on the first event and the policy corresponding to the MBS session, including: If the first event matches the second event in the first strategy, wherein the second event is one of the at least one first type of event, then the session management function network element establishes a data transmission channel between the user plane function network element and the multicast source node for the MBS session.

3. The method as described in claim 2, characterized in that, The at least one type of first event includes one or more of the following: At least one event in the MBS session configuration process corresponding to the MBS session; At least one event in the MBS session establishment process corresponding to the MBS session; At least one event in the MBS session activation process corresponding to the MBS session; At least one event in the MBS session start transmission process corresponding to the MBS session.

4. The method as described in claim 2, characterized in that, At least one event in the MBS session start transmission process corresponding to the MBS session includes: the arrival of the transmission start time of the MBS session.

5. The method as described in claim 2, characterized in that, The method further includes: If the first event matches the second event in the first strategy, the session management function network element reserves the processing resources of the user plane function network element for the MBS session.

6. The method as described in claim 2, characterized in that, The first strategy further includes a data transmission channel establishment method corresponding to each of the at least one first type of event, wherein the data transmission channel establishment method is a first method or a second method; wherein the first method is that the user plane function network element allocates a port for communicating with the multicast source node and notifies the multicast source node of the port, and the second method is that the user plane function network element sends a request to the multicast source node to join the multicast tree corresponding to the multicast source node; The method further includes: the session management function network element establishing the data transmission channel for the MBS session according to the data transmission channel establishment method corresponding to the second event.

7. The method as described in claim 1, characterized in that, The strategy includes a second strategy, which contains at least one second type of event. The second type of event is used to trigger the session management function network element to release the data transmission channel for the MBS session. The session management function network element establishes or releases a data transmission channel between the user plane function network element and the multicast source node for the MBS session based on the first event and the policy corresponding to the MBS session, including: If the first event matches the third event in the second strategy, wherein the third event is one of the at least one second type of event, then the session management function network element releases the data transmission channel between the user plane function network element and the multicast source node for the MBS session.

8. The method as described in claim 7, characterized in that, The at least one type II event includes one or more of the following: At least one event in the MBS session cancellation configuration process corresponding to the MBS session; At least one event in the MBS session release process corresponding to the MBS session; At least one event in the MBS session deactivation process corresponding to the MBS session; At least one event in the MBS session termination transmission process corresponding to the MBS session.

9. The method as described in claim 7, characterized in that, At least one event in the MBS session termination transmission process corresponding to the MBS session includes: the arrival of the MBS session's transmission termination time.

10. The method as described in claim 7, characterized in that, The method further includes: If the first event matches the third event in the second strategy, the session management function network element releases the processing resources of the user plane function network element reserved for the MBS session.

11. The method according to any one of claims 1-10, characterized in that, Also includes: The session management function network element obtains the policy corresponding to the MBS session from the application function network element; or, The session management function network element obtains the policy corresponding to the MBS session from the application function network element through the multicast / broadcast service function network element or the network presentation function network element.

12. The method according to any one of claims 1-10, characterized in that, Also includes: The session management function network element obtains indication information from the application function network element, or obtains indication information from the application function network element through the multicast / broadcast service function network element or the network presentation function network element; wherein, the indication information is used to determine one or more events; The session management function network element generates a policy corresponding to the MBS session based on the instruction information, wherein the policy includes one or more events.

13. The method as described in claim 12, characterized in that, The instruction information includes one or more of the following: The first piece of information is used to indicate the start time of the MBS session; The second information is used to instruct the MBS session configuration process, MBS session establishment process, MBS session activation process, or MBS session start transmission process corresponding to the MBS session. The third piece of information is used to indicate the end time of the MBS session; The fourth piece of information is used to instruct the MBS session corresponding to the MBS session to perform the MBS session cancellation configuration process, MBS session release process, MBS session deactivation process, or MBS session end transmission process. The fifth piece of information is used to indicate the Quality of Service (QoS) requirements corresponding to the MBS session.

14. The method according to any one of claims 1-10, characterized in that, Also includes: The session management function network element sends a query message to the policy control network element. The query message is used to query the policy and quality of service (QoS) requirements corresponding to the MBS session. The session management function network element receives a response message returned by the policy control network element, and the response message carries the policy and QoS requirements corresponding to the MBS session.

15. A method for configuring an MBS session, characterized in that, include: The application function network element generates a policy corresponding to the MBS session, wherein the policy is used to determine the timing for establishing or releasing a data transmission channel between the user plane function network element and the multicast source node for the MBS session, and the policy includes one or more events; The application function network element sends the policy corresponding to the MBS session to the session management function network element, or the application function network element sends the policy corresponding to the MBS session to the session management function network element through the multicast / broadcast service function network element or the network presentation function network element. The strategy includes multiple triggering events, each corresponding to an establishment condition for establishing the data transmission channel for the MBS session or a release condition for releasing the data transmission channel. The triggering events are selected from events in the configuration, establishment, activation, start transmission, deconfiguration, release, deactivation, or end transmission process of the MBS session.

16. A method for configuring an MBS session, characterized in that, include: The application function network element generates indication information, wherein the indication information is used to determine one or more events; The application function network element sends the instruction information to the session management function network element, so that the session management function network element generates a policy corresponding to the MBS session according to the instruction information; wherein, the policy is used to determine the timing for establishing or releasing a data transmission channel between the user plane function network element and the multicast source node for the MBS session, and the policy includes one or more of the events; The strategy includes multiple triggering events, each corresponding to an establishment condition for establishing the data transmission channel for the MBS session or a release condition for releasing the data transmission channel. The triggering events are selected from events in the configuration, establishment, activation, start transmission, deconfiguration, release, deactivation, or end transmission process of the MBS session.

17. A method for configuring an MBS session, characterized in that, include: The policy control network element receives a query message from the session management function network element, wherein the query message is used to query the policy and quality of service (QoS) requirements corresponding to the MBS session; The policy control network element determines the policy and QoS requirements corresponding to the MBS session. The policy control network element sends a response message to the session management function network element, and the response message carries the policy and QoS requirements corresponding to the MBS session. The strategy includes multiple triggering events, each corresponding to an establishment condition for establishing a data transmission channel for the MBS session or a release condition for releasing the data transmission channel. The triggering events are selected from events in the configuration, establishment, activation, start transmission, deconfiguration, release, deactivation, or end transmission process of the MBS session.

18. The method as described in claim 17, characterized in that, The policy control network element stores the mapping relationship between QoS requirements and policies; The policy control network element determines the policy and QoS requirements corresponding to the MBS session, including: The policy control network element obtains the QoS requirements corresponding to the MBS session from the unified database network element. The policy control network element determines the policy corresponding to the MBS session based on the QoS requirements corresponding to the MBS session and the mapping relationship.

19. The method as described in claim 17, characterized in that, The unified database network element stores the mapping relationship between the QoS requirements and the policies; The policy control network element determines the policy and QoS requirements corresponding to the MBS session, including: The policy control network element obtains the policy and QoS requirements corresponding to the MBS session from the unified database network element.

20. A communication device, characterized in that, include: The transceiver unit is used to detect the first event for the MBS session; The processing unit is configured to: if the first event matches an event in the policy corresponding to the MBS session, then establish or release a data transmission channel between the user plane function network element and the multicast source node for the MBS session, wherein the policy is used to determine the timing for establishing or releasing the data transmission channel for the MBS session. The strategy includes multiple triggering events, each corresponding to an establishment condition for establishing the data transmission channel for the MBS session or a release condition for releasing the data transmission channel. The triggering events are selected from events in the configuration, establishment, activation, start transmission, deconfiguration, release, deactivation, or end transmission process of the MBS session.

21. A communication device, characterized in that, include: The processing unit is used to generate a policy corresponding to the MBS session, wherein the policy is used to determine the timing for establishing or releasing a data transmission channel between the user plane function network element and the multicast source node for the MBS session, and the policy includes one or more events. The transceiver unit is used to send the policy corresponding to the MBS session to the session management function network element, or to send the policy corresponding to the MBS session to the session management function network element through the multicast / broadcast service function network element or the network presentation function network element; The strategy includes multiple triggering events, each corresponding to an establishment condition for establishing the data transmission channel for the MBS session or a release condition for releasing the data transmission channel. The triggering events are selected from events in the configuration, establishment, activation, start transmission, deconfiguration, release, deactivation, or end transmission process of the MBS session.

22. A communication device, characterized in that, include: A processing unit is configured to generate indication information, wherein the indication information is used to determine one or more events; The transceiver unit is used to send the indication information to the session management function network element, so that the session management function network element generates a policy corresponding to the MBS session according to the indication information; wherein, the policy is used to determine the timing for establishing or releasing a data transmission channel between the user plane function network element and the multicast source node for the MBS session, and the policy includes one or more of the events; The strategy includes multiple triggering events, each corresponding to an establishment condition for establishing the data transmission channel for the MBS session or a release condition for releasing the data transmission channel. The triggering events are selected from events in the configuration, establishment, activation, start transmission, deconfiguration, release, deactivation, or end transmission process of the MBS session.

23. A communication device, characterized in that, include: The transceiver unit is used to receive query messages from the session management function network element, wherein the query messages are used to query the policy and quality of service (QoS) requirements corresponding to the MBS session. The processing unit is used to determine the policy and QoS requirements corresponding to the MBS session; The transceiver unit is also configured to send a response message to the session management function network element, the response message carrying the policy and QoS requirements corresponding to the MBS session; The strategy includes multiple triggering events, each corresponding to an establishment condition for establishing a data transmission channel for the MBS session or a release condition for releasing the data transmission channel. The triggering events are selected from events in the configuration, establishment, activation, start transmission, deconfiguration, release, deactivation, or end transmission process of the MBS session.

24. A communication device, characterized in that, Including processor and memory; The processor and the memory are coupled, the memory is used to store computer execution instructions, and the processor is used to execute the computer execution instructions stored in the memory to cause the communication device to perform the method as described in any one of claims 1 to 19.

25. A chip, characterized in that, Includes logic circuits and input / output interfaces; The input / output interface is used to receive signals from other communication devices outside the chip and transmit them to the logic circuit, or to send signals from the logic circuit to other communication devices outside the chip. The logic circuit is used to implement the method as described in any one of claims 1 to 19.

26. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions, which, when executed by a communication device, implement the method as described in any one of claims 1 to 19.

27. A computer program product, characterized in that, When it is run on a computer, it causes the method as described in any one of claims 1 to 19 to be performed.

Images