Communication method and device

By introducing the interaction mechanism between the first network element and the second network element in the communication network, generating and updating the billing information of multicast/broadcast services, the billing problem of 5G multicast broadcast services is solved, and the billing problem of users and Accurate management of network resources.

CN118921632APending Publication Date: 2024-11-08HUAWEI TECH CO LTD
View PDF 0 Cites 3 Cited by

Patent Information

Application Number
CN202310514439.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-05-08
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

The lack of multicast mode in the existing 4G mobile communication networks has caused operators to be unable to charge users who receive multicast service data and cannot effectively measure and bill. Especially in 5G networks, multicast broadcast applications are becoming more and more widespread, and new needs billing method to adapt.

Method used

Through the interaction between the first network element and the second network element, messages containing multicast/broadcast service identification, trigger event and usage report are generated and sent, and the billing information is updated to facilitate the terminal joining the multicast/broadcast service. Billing. Specifically, the first network element may be a billing function network element, the second network element is a session management function network element or a billing trigger function network element. The interactive message includes the terminal joining or exiting the multicast/broadcast service, and changes in the transmission method etc. to trigger events to ensure that operators can accurately calculate and charge.

Benefits of technology

It realizes accurate billing of 5G multicast broadcast services, can be allocated according to the user's usage and transmission methods, improves the operator's revenue management capabilities, and ensures reasonable allocation and billing of network resources.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118921632A_ABST
    Figure CN118921632A_ABST
Patent Text Reader

Abstract

The embodiment of the invention provides a communication method and device, and relates to the technical field of communication. The first network element receives a first message from the second network element, wherein the first message comprises an identifier of a first multicast / broadcast service (MBS) and at least one of the following information: a trigger event of the first message, a transmission mode of the first MBS, and a usage report of a terminal joining the first MBS for the first MBS; and the first network element updates the charging information of the first MBS according to the first message. By adopting the method provided by the invention, the multicast service or the broadcast service can be charged, and the charging strategy is further optimized.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communication technology, and in particular, to a communication method and device. Background Art

[0002] In order to measure the occupancy of network resources by users (which can be understood as individual terminals receiving multicast / broadcast service data, or content providers sending multicast / broadcast service data), operators charge users according to preset tariff rules.

[0003] At present, the enhanced multimedia broadcast / multicast service (eMBMS) in the 4th generation (4G) mobile communication network only has a broadcast mode, but no multicast mode (i.e., multicast mode). The core network cannot sense which user equipment (UE) has received the broadcast service data, so the operator cannot charge the users who receive the broadcast service data, but can only charge the content providers of the broadcast service data. However, as the 5th generation (5G) multicast broadcast is applied to venue multicast (e.g., concerts, ball games, etc.), operators are in urgent need of a new billing method to adapt to the needs of 5G multicast broadcast. Summary of the invention

[0004] The present application provides a communication method and device to optimize multicast broadcast billing.

[0005] In the first aspect, the present application provides a communication method, which can be executed through the interaction between a first network element and a second network element, wherein the first network element can be a charging function network element (charging function, CHF), or a network element capable of implementing the charging function, and the second network element can be a session management function network element (session management function, SMF), or a charging trigger function (charging trigger function, CTF), and CTF can be a separate network element or a module in SMF responsible for billing, and the application is not specifically limited here.

[0006] The second network element generates a first message, the first message including an identifier of a first multicast / broadcast service (MBS) and at least one of the following information: a triggering event of the first message, a transmission method of the first MBS, and a usage report of the first MBS by a terminal joining the first MBS; the second network element sends the first message to the first network element; the first network element updates the billing information of the first MBS according to the first message.

[0007] In the present application, the first network element updates the billing information of the first MBS according to the first message. The first message includes information such as the triggering event of the first message, the transmission method of the MBS, and the usage report of the terminal joining the MBS for the MBS. In this way, the first network element can charge the terminal joining the first MBS and charge the user. Compared with the existing technology that does not support charging users, the billing of multicast broadcast can be further optimized.

[0008] It should be understood that the usage report of the terminal joining the first MBS for the first MBS can be replaced by "usage report of the terminal joining the first MBS", and the usage report may include: total traffic of the first MBS, uplink traffic, downlink traffic, uplink / downlink traffic, triggering event of the first message, time of triggering the first message, etc.

[0009] It should be understood that updating the billing information of the first MBS can be understood as: opening the billing information of the first MBS; updating the billing information of the first MBS; terminating the billing of the first MBS (Termination), etc.

[0010] In an optional manner, the triggering event of the first message includes:

[0011] The terminal joins the first MBS;

[0012] The terminal exits the first MBS;

[0013] The transmission mode of the first MBS changes.

[0014] The above situation serves as a triggering event of the first message, which facilitates the second network element to determine when to report the first message, so that the second network element can update the charging information of the first MBS in time.

[0015] It should be noted that: the terminal joining the first MBS can be understood as joining the first MBS session, and the change in the transmission mode of the first MBS can be understood as the change in the transmission mode of the first MBS.

[0016] In an optional manner, the transmission method of the first MBS is a 5G core network individual multicast / broadcast service traffic transmission method (5GC Individual MBS traffic delivery method) or a 5G core network shared multicast / broadcast service traffic transmission method (5GC shared MBS traffic delivery method).

[0017] In an optional manner, the third network element generates a second message, and the third network element sends the second message to the first network element, where the second message includes at least one of the following information:

[0018] The charging identifier of the first MBS, the triggering event of the second message, the service type of the first MBS, the quality of service (QoS) information of the first MBS, the service area of ​​the first MBS, and the usage report of the first MBS.

[0019] In an optional manner, the second message further includes an identifier of the first multicast / broadcast service.

[0020] The above-mentioned third network element can be a multicast / broadcast-session management function (MB-SMF) or CTF. CTF can be a separate network element or a module responsible for billing in MB-SMF. The second message is sent to the first network element through the third network element. The first network element can perform billing for the first MBS and learn about the network resources occupied by the first MBS.

[0021] In an optional manner, the triggering event of the second message includes at least one of the following:

[0022] Activate the session corresponding to the first MBS;

[0023] Deactivating a session corresponding to the first MBS;

[0024] A multicast / broadcast user plane function network element is added for transmitting data of the first MBS;

[0025] Deleting a multicast / broadcast user plane function network element used to transmit data of the first MBS;

[0026] Adding access network equipment for transmitting data of the first MBS;

[0027] Deleting the access network device that transmits the data of the first MBS;

[0028] A user plane function network element is added for transmitting data of the first MBS;

[0029] Deleting a user plane function network element used to transmit data of the first MBS;

[0030] The service area of ​​the first MBS changes.

[0031] The above situation serves as a triggering event of the second message, which facilitates the third network element to determine when to report the second message, so that the third network element can update the charging information of the first MBS in time.

[0032] In an optional manner, the first network element updates the charging information of the first MBS according to the second message.

[0033] It should be understood that updating the billing information of the first MBS can be understood as: opening the billing information of the first MBS; updating the billing information of the first MBS; terminating the billing of the first MBS (Termination), etc.

[0034] After the third network element reports the second message, the first network element updates the charging information of the first MBS according to the second message, so as to timely know the resource occupancy of the first MBS.

[0035] In an optional manner, the usage report includes a rate group.

[0036] In an optional manner, the first network element sends a quota of the terminal for the rate group of the first MBS to the second network element.

[0037] In an optional manner, the first network element sends the quota of the rate group of the first MBS to the third network element.

[0038] In an optional manner, the first network element sends a first charging policy to the second network element, where the first charging policy includes a triggering event of a first message; and the second network element determines a triggering event of the first message for sending the first message according to the first charging policy.

[0039] In an optional manner, the first network element sends a second charging policy to the third network element, where the second charging policy includes a triggering event of the second message; and the third network element determines a triggering event of the second message for sending the second message according to the second charging policy.

[0040] In an optional manner, the first network element is a CHF; the second network element is an SMF; the third network element is an MB-SMF; or, the second network element is a first CTF, and the third network element is a second CTF.

[0041] In an optional manner, the second network element sends context request information of the first MBS to the third network element; the second network element receives context information of the first MBS from the third network element, the context information including identification information of the first network element; the second network element sends a first message to the first network element according to the identification information of the first network element.

[0042] It should be understood that the context request information of the first MBS may be an MBS session context status subscription request (Nmbsmf_MBSSession_ContextStatusSubscribe request).

[0043] This method can ensure that the second network element and the third network element send messages to the same first network element, which is conducive to the first network element to uniformly schedule the quota of the first MBS session and the terminal joining the first MBS. In addition, the billing information of the first MBS session and the terminal joining the first MBS is centralized on the same first network element, which can also facilitate the query of all billing data related to the first MBS.

[0044] In the second aspect, the present application provides a communication method, which can be executed through the interaction between a first network element and a third network element, wherein the first network element may be a CHF, or a network element capable of implementing a billing function, and the third network element may be an MB-SMF, or a module for billing in the MB-SMF, or a CTF, which is not specifically limited in the present application.

[0045] The third network element generates a second message, the second message includes an identifier of the first multicast / broadcast service MBS and at least one of the following information: a triggering event of the second message, a service type of the first MBS, and a usage report of the first MBS; the third network element sends the second message to the first network element; the first network element updates the billing information of the first MBS according to the second message.

[0046] By sending the second message to the first network element through the third network element, the first network element can charge the first MBS and learn the network resources occupied by the first MBS through the dynamic topology changes between the base station and the user plane network element.

[0047] In an optional manner, the second message further includes: a charging identifier of the first MBS, quality of service QoS information of the first MBS, and a service area of ​​the first MBS.

[0048] In an optional manner, the triggering event of the second message includes one of the following:

[0049] Activate the session corresponding to the first MBS;

[0050] Deactivating a session corresponding to the first MBS;

[0051] A multicast / broadcast user plane function network element is added for transmitting data of the first MBS;

[0052] Deleting a multicast / broadcast user plane function network element used to transmit data of the first MBS;

[0053] Adding access network equipment for transmitting data of the first MBS;

[0054] Deleting the access network device that transmits the data of the first MBS;

[0055] A user plane function network element is added for transmitting data of the first MBS;

[0056] Deleting a user plane function network element used to transmit data of the first MBS;

[0057] The service area of ​​the first MBS changes.

[0058] It should be understood that the session corresponding to the first MBS in this article can be replaced by: the first MBS session.

[0059] In an optional manner, the third network element receives a second charging policy from the first network element, where the second charging policy includes a triggering event of the second message; and the third network element determines a triggering event of the second message for sending the second message according to the second charging policy.

[0060] It should be understood that the billing strategy in this article may include: MultipleUnitInformation.

[0061] In a third aspect, an embodiment of the present application provides a communication device, which may be a first network element (such as the first network element in the first aspect, the first network element in the second aspect) or a chip disposed inside the first network element, or a second network element (such as the second network element in the first aspect, the second network element in the second aspect) or a chip disposed inside the second network element, or a third network element (such as the third network element in the first aspect, the third network element in the second aspect) or a chip disposed inside the third network element. The communication device has the function of implementing any aspect of the first to second aspects above, for example, the communication device includes a module or unit or means corresponding to the steps involved in any aspect of the first to second aspects above, and the function or unit or means may be implemented by software, or by hardware, or may be implemented by hardware executing the corresponding software.

[0062] In one possible design, the communication device includes a processing unit and a transceiver unit, wherein the transceiver unit can be used to send and receive signals to achieve communication between the communication device and other devices; the processing unit can be used to perform some internal operations of the communication device. The transceiver unit can be called an input-output unit, a communication unit, etc., and the transceiver unit can be a transceiver; the processing unit can be a processor. When the communication device is a module (such as a chip) in a communication device, the transceiver unit can be an input-output interface, an input-output circuit or an input-output pin, etc., and can also be called an interface, a communication interface or an interface circuit, etc.; the processing unit can be a processor, a processing circuit or a logic circuit, etc.

[0063] In another possible design, the communication device includes a processor and may also include a transceiver, the transceiver is used to send and receive signals, and the processor executes program instructions to complete the method in any possible design or implementation of the first aspect to the second aspect. The communication device may also include one or more memories, the memory is used to couple with the processor, and the memory can store the necessary computer programs or instructions for implementing the functions involved in any aspect of the first aspect to the second aspect. The processor can execute the computer program or instructions stored in the memory, and when the computer program or instructions are executed, the communication device implements the method in any possible design or implementation of the first aspect to the third aspect.

[0064] In another possible design, the communication device includes a processor, which can be used to couple with a memory. The memory can store necessary computer programs or instructions for implementing the functions involved in any one of the first to second aspects. The processor can execute the computer program or instructions stored in the memory, and when the computer program or instructions are executed, the communication device implements the method in any possible design or implementation of the first to second aspects.

[0065] In another possible design, the communication device includes a processor and an interface circuit, wherein the processor is used to communicate with other devices through the interface circuit and execute the method in any possible design or implementation of the first to second aspects above.

[0066] It can be understood that in the third aspect above, the processor can be implemented by hardware or by software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor can be a general-purpose processor, which is implemented by reading the software code stored in the memory. In addition, the above processors can be one or more, and the memories can be one or more. The memory can be integrated with the processor, or the memory can be separately set from the processor. In the specific implementation process, the memory can be integrated with the processor on the same chip, or can be set on different chips respectively. The embodiment of the present application does not limit the type of memory and the setting method of the memory and the processor.

[0067] In a fourth aspect, an embodiment of the present application provides a communication system, which includes the first network element, the second network element and the third network element in the above-mentioned first aspect to the second aspect.

[0068] In a fifth aspect, the present application provides a chip system, which includes a processor and may also include a memory, for implementing the method described in any possible design of the first aspect to the second aspect. The chip system may be composed of a chip, or may include a chip and other discrete devices.

[0069] In a sixth aspect, the present application also provides a computer-readable storage medium, in which computer-readable instructions are stored. When the computer-readable instructions are executed on a computer, the computer executes a method in any possible design of the first aspect to the second aspect.

[0070] In a seventh aspect, the present application provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the methods of the various embodiments of the first to second aspects described above.

[0071] For the technical effects that can be achieved in the above-mentioned second to seventh aspects, please refer to the description of the technical effects that can be achieved by the corresponding possible design schemes in the above-mentioned first aspect, and this application will not repeat them here. BRIEF DESCRIPTION OF THE DRAWINGS

[0072] Figure 1A A schematic diagram of a communication system is shown;

[0073] Figure 1B A schematic diagram of another communication system is shown;

[0074] Figure 2 A schematic diagram of yet another communication system is shown;

[0075] Figure 3 A schematic diagram showing a data transmission method;

[0076] Figure 4 A schematic flow chart of a communication method is shown;

[0077] Figure 5 A schematic flow chart of a communication method is shown;

[0078] Figure 6 A schematic flow chart of a communication method is shown;

[0079] Figure 7 A schematic flow chart of a communication method is shown;

[0080] Figure 8 A schematic flow chart of a communication method is shown;

[0081] Fig. 9 A schematic flow chart of a communication method is shown;

[0082] Fig.10A schematic diagram of the structure of a communication device provided in an embodiment of the present application is shown;

[0083] Fig.11 A schematic diagram showing the structure of another communication device provided in an embodiment of the present application is shown;

[0084] Fig.12 A schematic diagram of the structure of another communication device provided in an embodiment of the present application is shown. DETAILED DESCRIPTION

[0085] In order to make the purpose, technical solution and advantages of the present application clearer, the present application will be further described in detail below with reference to the accompanying drawings. The specific operating method in the method embodiment can also be applied to the device embodiment or system embodiment. Among them, in the description of the present application, unless otherwise specified, the meaning of "multiple" is two or more. Therefore, the implementation of the device and the method can refer to each other, and the repetitions will not be repeated.

[0086] The following explains some terms used in the system architecture of the embodiment of the present application to facilitate understanding by those skilled in the art.

[0087] 1) User equipment, also known as terminal equipment, is a device with wireless transceiver functions, which can communicate with one or more core network (CN) devices (or core devices) via access network equipment (or access equipment) in (radio) access network (RAN).

[0088] User equipment can also be called access terminal, terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, user agent or user device, etc. User equipment can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; it can also be deployed on the water (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons and satellites, etc.). User equipment can be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a smart phone, a mobile phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), etc. Alternatively, the user equipment can also be a handheld device with wireless communication function, a computing device or other device connected to a wireless modem, a vehicle-mounted device, a wearable device, a drone device or a terminal in the Internet of Things, the Internet of Vehicles, a 5G mobile communication network and any form of terminal in the future network, a relay user device or a terminal in the future evolved public land mobile network (PLMN), etc. Among them, the relay user equipment can be, for example, a 5G residential gateway (RG). For example, the user equipment can be a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc. The embodiment of the present application does not limit the type or category of terminal equipment. The user equipment can also include terminal side equipment, such as a local switch (LSW), and / or a customer premise equipment (CPE), etc., or the user equipment can access the network through an LSE or a CPE.

[0089] 2) Network equipment refers to equipment that can provide wireless access functions for terminals, such as RAN equipment. Among them, network equipment can support at least one wireless communication technology, such as long term evolution (LTE), new radio (NR), wideband code division multiple access (WCDMA), etc.

[0090] For another example, the network device may include a core network device, and the core network device may include, for example, a core network element (network function, NF) such as an access and mobility management function (AMF).

[0091] In the present application, the (wireless) access network equipment may be used to provide network access functions for authorized user equipment in a specific area, and may use transmission tunnels of different qualities according to the level of the user equipment, service requirements, etc.

[0092] RAN equipment can manage wireless resources, provide access services for user equipment, and then complete the forwarding of control signals and user equipment data between user equipment and the core network. RAN can also be understood as a base station in a traditional network.

[0093] Exemplarily, the access network device in the embodiment of the present application may be any communication device with wireless transceiver function for communicating with user equipment. The access network equipment includes but is not limited to: evolved NodeB (eNB), radio network controller (RNC), Node B (NB), base station controller (BSC), base transceiver station (BTS), home evolved NodeB (HeNB, or home Node B, HNB), baseband unit (BBU), access point (AP) in wireless fidelity (WIFI) system, wireless relay node, wireless backhaul node, transmission point (TP) or transmission and reception point (TRP), etc., and can also be a gNB in ​​5G, such as NR, system, or a transmission point (TRP or TP), one or a group of (including multiple antenna panels) antenna panels of a base station in a 5G system, or it can also be a network node constituting a gNB or a transmission point, such as a baseband unit (BBU), or a distributed unit (DU), etc.

[0094] In some deployments, the gNB may include a centralized unit (CU) and a DU. The gNB may also include an active antenna unit (AAU). The CU implements some functions of the gNB, and the DU implements some functions of the gNB. For example, the CU is responsible for processing non-real-time protocols and services, and implementing the functions of the radio resource control (RRC) and packet data convergence protocol (PDCP) layers. The DU is responsible for processing physical layer protocols and real-time services, and implementing the functions of the radio link control (RLC) layer, the media access control (MAC) layer, and the physical (PHY) layer. The AAU implements some physical layer processing functions, radio frequency processing, and related functions of active antennas. Since the information of the RRC layer will eventually become the information of the PHY layer, or be converted from the information of the PHY layer, under this architecture, high-level signaling, such as RRC layer signaling, can also be considered to be sent by the DU, or by the DU+AAU. It can be understood that the access network device can be a device including one or more of a CU node, a DU node, and an AAU node. In addition, the CU may be classified as an access network device in an access network (radio access network, RAN), or the CU may be classified as an access network device in a core network, and this application does not limit this.

[0095] 3) User plane network element: used for packet routing and forwarding, as well as QoS processing of user plane data, etc.

[0096] In a 5G communication system, the user plane network element may be a user plane function (UPF) network element. In future communication systems, the user plane network element may still be a UPF network element, or may have other names, which are not limited in this application.

[0097] 4) Data network element: a network used to provide data transmission.

[0098] In a 5G communication system, the data network element may be a data network (DN) element. In future communication systems, the data network element may still be a DN element, or may have other names, which are not limited in this application.

[0099] 5) Authentication server: used to perform security authentication of users. In the 5G communication system, the authentication server can be an authentication server function (AUSF).

[0100] 6) Mobility management network element: mainly used for mobility management and access management. In the 5G communication system, the access management network element can be AMF, which mainly performs functions such as mobility management and access authentication / authorization. In addition, it is also responsible for transmitting user policies between the terminal and the policy control function (PCF) network element.

[0101] 7) Network data analysis network element: mainly used to provide network data analysis function. In the 5G communication system, the network data analysis network element can be a network data analysis function (NWDAF).

[0102] 8) Session management network element: mainly used for session management, allocation and management of Internet protocol (IP) addresses of user equipment, selection of endpoints of manageable user plane functions, policy control and charging function interfaces, and downlink data notification, etc.

[0103] In the 5G communication system, the session management network element can be an SMF network element, which completes terminal IP address allocation, UPF selection, and billing and QoS policy control.

[0104] 9) Application network element: In the 5G communication system, the application network element can be an application function (AF) network element, which represents the application function of a third party or operator. It is the interface for the 5G network to obtain external application data and is mainly used to convey the requirements of the application side to the network side.

[0105] 10) Unified data management network element: responsible for the management of user identification, contract data, authentication data, and user service network element registration management. In the 5G communication system, the unified data management network element can be unified data management (UDM).

[0106] 11) Unified data storage network element: used to store and retrieve UE's subscription data, etc. In the 5G communication system, the unified data storage network element can be a unified data repository (UDR).

[0107] 12) Policy control network element: including user contract data management function, policy control function, billing policy control function, QoS control, etc., a unified policy framework used to guide network behavior, and provide policy rule information for control plane functional network elements (such as AMF, SMF network elements, etc.).

[0108] In a 5G communication system, the policy control network element may be a PCF.

[0109] 13) Network function repository function network element: provides storage and selection functions for network function entity information for other core network elements. In the 5G communication system, this network element can be a network function repository function network element (network function repository function, NRF).

[0110] 14) Unstructured data storage network element: stores and retrieves its unstructured data, such as UE context. In the 5G communication system, the unstructured data storage network element can be an unstructured data storage function (UDSF).

[0111] 15) Charging network element: mainly used to perform charging functions. In the 5G communication system, the charging network element may be a charging network element (Charging Function, CHF).

[0112] 16) Edge security network element: It is mainly used for communication between different operator networks. As the border gateway of different operator networks, it is responsible for message filtering and policy management on the control plane interface between operators. In the 5G communication system, the edge security network element can be a security edge protection proxies (SEPP).

[0113] 17) Service communication proxy network element: used to support indirect communication and discovery of proxy network functions. In a 5G communication system, the service communication proxy network element may include a service communication proxy (SCP).

[0114] 19) Network open network element: In the 5G communication system, the network open network element can be a network open function (NEF) network element, which is mainly used to expose the services and capabilities of the 3GPP network function to the AF, and also allows the AF to provide information to the 3GPP network function.

[0115] 19) Network slice selection function network element: responsible for selecting network slices for UE. In the 5G communication system, this application network element can be a network slice selection function (NSSF) network element.

[0116] In future communication systems, such as the sixth generation (6th generation, 6G) communication system, the above network elements or devices may still use their names in the 5G communication system, or may have other names, which is not limited in the embodiments of the present application. The functions of the above network elements or devices can be completed by an independent network element or by several network elements. In actual deployment, the network elements in the core network can be deployed on the same or different physical devices. For example, as a possible deployment, AMF and SMF can be deployed on the same physical device. For another example, the network elements of the 5G core network can be deployed on the same physical device as the network elements of the 4G core network. This is not limited in the embodiments of the present application.

[0117] In a 5G communication system, the application network element may be an application function (AF) network element. In future communication systems, the application network element may still be an AF network element, or may have other names, which are not limited in this application.

[0118] like Figure 1A and Figure 1B The figure shows a schematic diagram of the 5G network architecture, where: Figure 1A This is a schematic diagram of the 5G network architecture under a non-service architecture. Figure 1B The following is a schematic diagram of the 5G network architecture under the service-based architecture (SBA). The service-based architecture is the basic architecture of the 5G network. Service-orientedness is mainly reflected in the control plane. The essence of SBA is to define network functions as several "service" modules that can be flexibly called according to the three principles of "self-contained, reusable, and independently managed". Based on this, operators can flexibly customize the network according to business needs. The interaction between network functions is realized by service calls. Each network function presents a general service interface to the outside world, which can be called by authorized network functions or services. Figure 1B The figure shows an exemplary service-oriented architecture diagram of a 5G network. In this architecture, core network elements can communicate with other core network elements through service-oriented interfaces. For example, the service-oriented interface corresponding to AMF is called Namf interface, and the interface corresponding to LMF is called Nlmf interface.

[0119] Figure 1A and Figure 1BThe 5G network architecture shown may include three parts, namely, terminal, DN and operator network. The functions of some network elements are briefly introduced below.

[0120] The operator network may include but is not limited to one or more of the following network elements: AUSF, PCF, UDM, AF, AMF, SMF network element, RAN) equipment, UPF and NSSF, etc. In the above operator network, network elements or devices other than radio access network equipment may be referred to as core network network elements or core network equipment.

[0121] also, Figure 1A Some of the communication interfaces shown include:

[0122] The N1 interface is the signaling plane interface between the AMF and the UE, and is used to exchange signaling messages between the core network and the UE, such as UE registration, UE establishment of protocol data unit (PDU) sessions, and network side configuration of UE policies.

[0123] The N2 interface is the interface between the AMF and the RAN and is used to transmit radio bearer control information from the core network to the (R)AN.

[0124] The N3 interface is the interface between the RAN and the UPF and is used to transfer UE service data between the (R)AN and the UPF.

[0125] The N4 interface is the interface between SMF and UPF, and is used to transmit information between the control plane and the user plane, including the control plane terminal equipment completing the network access operation according to the contract information with the operator.

[0126] The N6 interface is the interface between UPF and DN and is used to transfer UE service data between UPF and DN.

[0127] N5 interface is the interface between PCF and AF.

[0128] The N7 interface is the interface between PCF and SMF, and is used to send PDU session granularity and service data flow granularity control strategy.

[0129] The N8 interface is the interface between AMF and UDM, which is used by AMF to obtain access and mobility management-related subscription data and authentication data from UDM, and AMF to register UE's current mobility management-related information with UDM.

[0130] The N9 interface is the interface between two UPFs. Figure 1AAs shown, the N9 interface is an interface between an intermediate UPF (I-UPF) and a UPF serving as a PDU session anchor (PSA).

[0131] The N10 interface is the interface between SMF and UDM, which is used by SMF to obtain session management-related contract data from UDM, and SMF to register UE current session-related information with UDM.

[0132] The N11 interface is the interface between SMF and AMF, and is used to transmit PDU session tunnel information between RAN and UPF, transmit control messages sent to UE, transmit radio resource control information sent to RAN, etc.

[0133] N12 interface, including the interface between AMF and AUSF.

[0134] N13 interface, including the interface between AUSF and UDM.

[0135] N22 interface, including the interface between NSSF and AMF.

[0136] It is understandable that the above network element or function can be a network element in a hardware device, a software function running on dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform). Optionally, the above network element or function can be implemented by one device, or by multiple devices, or a functional module in one device, which is not specifically limited in the embodiments of the present application.

[0137] The session management network element, user plane network element, and mobility management network element in this application can be Figure 1A The SMF, UPF, and AMF in the network may also be network elements having the functions of the above SMF, UPF, and AMF in future communications such as 6G networks, and this application is not limited to this. In the embodiments of this application, SMF, UPF, and AMF are described as examples of session management network elements, user plane network elements, and mobility management network elements, respectively.

[0138] It should be noted that Figure 1A and / or Figure 1B The names of the network elements and the interfaces between the network elements are only examples. In a specific implementation, the names of the network elements and the interfaces between the network elements may be other names, and the embodiments of the present application do not specifically limit this.

[0139] In previous generations of mobile communication technologies, such as the 3rd generation (3G) and 4G mobile communication technologies, the promotion of multicast / broadcast solutions encountered great difficulties. Specifically, the existing multicast / broadcast solutions need to add proprietary network elements and interfaces that support multicast / broadcast on the basis of the existing communication architecture, and also require proprietary multicast / broadcast channel support, which not only increases the overhead of the operator, but also increases the complexity of the terminal.

[0140] To overcome the above difficulties, supporting multicast / broadcast functions (5G multicast broadcast service, 5MBS) based on the 5th generation mobile communication network architecture has become a key research topic.

[0141] like Figure 2 As shown in the figure, it is the architecture adopted by the latest 5G multicast / broadcast technical specifications, which provides a network architecture for supporting multicast / broadcast services. Figure 1A The architecture shown in the figure is expanded. For example, two functional entities, namely, a multicast broadcast session management function (MB-SMF) and a multicast broadcast user plane function (MB-UPF), are added to support multicast / broadcast services / functions.

[0142] Among them, MB-SMF can implement the control plane function of multicast / broadcast services and is responsible for the management of multicast / broadcast services / groups / sessions. From the control plane, MB-SMF can be connected to NEF and / or multicast / broadcast service function (multicast / broadcast service function, MBSF), for example, for receiving relevant information of multicast / broadcast services (for example, description of multicast / broadcast services). In addition, MB-SMF can also be connected to PCF, for example, PCC rules related to multicast / broadcast services can be extracted. From the user plane, MB-UPF can be connected to multicast / broadcast service transport function (multicast / broadcast service transport function, MBSTF) and / or AF / AS to receive service data of multicast / broadcast services. It should be noted that MB-SMF and SMF can be co-located or deployed separately, and MB-UPF and UPF can be co-located or deployed separately, and this application does not limit this.

[0143] It should be noted that the above-mentioned MB-SMF or MB-UPF name is an example. In the 5G network, MB-SMF or MB-UPF may also be other names, which are not limited in this application. Figure 2 When billing for the architecture, CHF is also included, and billing is performed through information interaction between CHF, SMF, and MB-SMF.

[0144] In the embodiments of the present application, functions may also be referred to as network elements, network functions, functional entities, devices, etc. For example, access and mobility management functions may also be referred to as access and mobility management network elements, or access and mobility management network functions, or access and mobility management functional entities, etc. The names of the functions are not limited in the present application, and those skilled in the art may replace the names of the above functions with other names to perform the same functions, which are all within the scope of protection of the present application.

[0145] like Figure 3 As shown, the access network device supports the multicast / broadcast function, which can be understood as the access network device supports the transmission of multicast / broadcast service data in the 5G core network shared multicast / broadcast service traffic transmission mode, and the access network device does not support the multicast / broadcast function, which can be understood as the access network device does not support the transmission of multicast / broadcast service data in the 5G core network shared multicast / broadcast service traffic transmission mode, that is, only supports the transmission of multicast / broadcast service data in the 5G core network shared multicast / broadcast service traffic delivery mode. It should be understood that after the multicast / broadcast service data reaches the access network device (for example, RAN), it is processed by the service data adaptation protocol (SDAP) layer, packet data convergence protocol (PDCP) layer, radio link control (RLC) layer, media access control (MAC) layer, and physical (PHY) layer of the RAN, and is sent to each UE that receives the multicast / broadcast service data.

[0146] Multiple users using 5GC shared MBS traffic delivery jointly occupy one network resource, while multiple users using 5GC Individual MBS traffic delivery each occupy one network resource. The UE uses different transmission modes, and the UE occupies different network resources. However, different billing strategies are not currently provided for different transmission modes. In addition, 4G only has a broadcast mode, and operators cannot directly charge users of broadcast service data, but can only charge content providers of broadcast service data. However, multicast is introduced in 5G, and it is not clear how operators charge users of multicast service data. Considering the above situation, it is urgent to optimize the current billing strategy.

[0147] Based on this, the present application provides a communication method such as Figure 4 As shown, the communication method can be implemented through data interaction between the first network element and the second network element, wherein the first network element can be a CHF, or a network element capable of implementing a billing function, and the second network element can be an SMF, or a module for billing in the SMF, or a CTF, which is not specifically limited in this application. Execute as follows:

[0148] Step 401: A second network element generates a first message, where the first message includes an identifier of a first MBS and at least one of the following information:

[0149] The triggering event of the first message, the transmission mode of the first MBS, and the usage report of the first MBS by the terminal joining the first MBS.

[0150] As mentioned above, the first message is used for charging request in this application, and the first message can be sent alone or carried in other messages, which is not specifically limited in this application. The first message carries the identifier of the first MBS so that the first network element knows which service to charge for. For example, if the identifier of the first MBS is a multicast video service, the first network element can calculate the traffic for the multicast video service.

[0151] Among them, the triggering event of the first message instructs the second network element to report the specific reason for the first message to the first network element so that the first network element can adjust the billing information (wherein, the billing information can be understood as a charging data record (CDR), and the call record can also be understood as details or bills). For example, if the triggering event of the first message is that terminal 1 exits the session corresponding to the first MBS, then terminal 1 will no longer report the traffic data related to the first MBS. The first network element can deduct the reported traffic usage of terminal 1 and generate a CDR for terminal 1's use of the first MBS this time. This is only an example explanation and is not specifically limited in actual application. Among them, the transmission method of the first MBS is 5GC Individual MBS traffic delivery method or 5GC Shared MBS traffic delivery method. The first network element may adjust the billing information according to the transmission mode of the first MBS reported by the first network element. For example, when the 5GC Individual MBS traffic delivery method is used, the first network element may perform traffic billing for the terminals joining the first MBS individually. When the 5GC Shared MBS traffic delivery method is used, the first network element may uniformly perform traffic billing for the terminals joining the first MBS and evenly distribute the traffic billing to each terminal. This is only an example and is not specifically limited in actual application. Among them, the usage report of the terminal joining the first MBS for the first MBS can indicate the current billing situation of the terminal, so as to facilitate the first network element to update the billing information of the first MBS. For example, the usage report may include the rate group of the terminal (the rate group may indicate services of the same billing type, and the rate group may correspond to billing rules, such as 5 yuan / GB for traffic, free calls, and 0.5 yuan / message for text messages). The first network element may adjust the billing information of the first MBS according to the rate group situation of the terminal. The traffic used within the billing rules corresponding to the rate group shall not be charged, and the traffic exceeding the billing rules corresponding to the rate group shall be charged using a tiered pricing method.

[0152] Specifically, the triggering events of the first message include the following situations:

[0153] Case 1: The terminal joins the session corresponding to the first MBS

[0154] Since the terminal joins the first MBS, the services used by the terminal have changed. The rate group corresponding to the terminal's use of the first MBS may be different from the rate group for the terminal's use of other services (such as browsing the Internet for news, making phone calls, etc.). Therefore, the second network element will be triggered to report the first message so that the first network element can send the authorized quota and the triggering event of the first message to the second network element.

[0155] It should be understood that the terminal joining the session corresponding to the first MBS can be replaced by the following expressions: the terminal joining the first MBS session, the terminal joining the first MBS, and so on.

[0156] Case 2: The terminal exits the session corresponding to the first MBS

[0157] Since the terminal exits the first MBS, that is, the terminal no longer needs to receive services of the first MBS, the usage of the first MBS by the terminal may change, which triggers the second network element to report the first message so that the first network element can deduct the usage reported by the second network element and update the billing information of the first MBS.

[0158] It should be understood that the terminal exits the session corresponding to the first MBS can be replaced by the following expressions: the terminal exits the first MBS session, the terminal exits the first MBS, and so on.

[0159] Case 3: Change in the transmission method of the first MBS

[0160] Due to the change in the transmission method of the first MBS, the billing method of the first MBS may change, such as the 5GCIndividual MBS traffic delivery method becomes the 5GC Shared MBS traffic delivery method, and the second network element cannot count the traffic under the 5GC Shared MBS traffic delivery method, etc., which triggers the second network element to report the first message so that the first network element can update the billing policy of the first MBS. The first network element can also deduct the usage of the 5GC Individual MBS traffic delivery method reported by the second network element and update the billing information of the first MBS.

[0161] In addition, in actual application, the triggering event of the first message may also be that the terminal exits the session corresponding to the first MBS, and the transmission mode of the first MBS changes, the terminal joins the session corresponding to the first MBS, and the transmission mode of the first MBS changes, the first terminal exits the session corresponding to the first MBS, the second terminal joins the session corresponding to the first MBS, the first terminal exits the session corresponding to the first MBS, the second terminal joins the session corresponding to the first MBS, and the transmission mode of the first MBS changes, etc., which are not specifically limited in this application. In addition, when there are multiple terminals joining / exiting the session corresponding to the first MBS, a timer can be set, and after the timer ends, the second network element reports the first message, which can reduce the interaction of signaling.

[0162] Step 402: The second network element sends a first message to the first network element.

[0163] During the service registration phase, the first network element can register with the NRF whether it supports 5G multicast broadcast capabilities. When the second network element determines that it needs to request the first network element to charge the first MBS, it can request the first network element from the NRF. The request message needs to carry an identifier indicating that the NRF needs to return the first network element that supports 5G multicast broadcast capabilities. The NRF returns the first network element that supports 5G multicast broadcast capabilities in the response. Then the second network element can determine the first network element, and the second network element can send the first message to the first network element.

[0164] Step 403: The first network element updates the charging information of the first MBS according to the first message.

[0165] Specifically, for different first messages, the updating of the billing information of the first MBS in step 403 can be understood differently. For example, when the session corresponding to the first MBS is established and the terminal joins the first MBS for the first time, the first message can be understood as initialization (Initial), then the above-mentioned updating of the billing information of the first MBS can be understood as opening the billing information of the first MBS; when there is a terminal joining the session corresponding to the first MBS, and the location of the terminal changes from receiving services at a base station supporting MBS to receiving services at a base station not supporting MBS, the first message can be understood as update (Update), then the above-mentioned updating of the billing information of the first MBS can be understood as updating the billing information of the first MBS; when the joining terminal of the session corresponding to the first MBS exits the session corresponding to the first MBS, the above-mentioned updating of the billing information of the first MBS can be understood as terminating the billing of the first MBS (Termination). The present application does not specifically limit the specific meaning of "update" in step 403, which can be flexibly determined according to actual applications and is not specifically limited here.

[0166] It should be noted that the first message may include one or more of the following:

[0167] Charging Data Request (Charging Data Request / Charging Data Request[Initial] / Charging Data Request[Update] / Charging Data Request[Termination]); Converged Charging Create Request (Nchf_ConvergedCharging_Create request); Converged Charging Update Request (Nchf_ConvergedCharging_Update request); Converged Charging Release Request (Nchf_ConvergedCharging_Release request); Offline Charging Create Request (Nchf_OfflineOnlyCharging_Create request); Offline Charging Update Request (Nchf_OfflineOnlyCharging_Update request); Offline Charging Release Request (Nchf_OfflineOnlyCharging_Release request), etc. The first message may also be a new message, which is not limited in this patent.

[0168] Typically, the charging information of the first MBS may include: the total traffic of the first MBS, uplink traffic, downlink traffic, uplink / downlink traffic, UPF ID, MBS session information (such as the ID of the terminal joining the MBS session, session ID, QoS, etc.), etc.

[0169] Specifically, when the first message is different information, the first network element may update the charging information of the first MBS in different ways. Here, the charging information of the first MBS is described by taking the CDR of the first MBS as an example, as follows:

[0170] Mode 1: The first message includes the identifier of the first MBS and the triggering event of the first message

[0171] The first network element obtains the identifier of the first MBS and the triggering event of the first message, and updates the CDR of the first MBS. For example, when the triggering event of the first message is that the terminal joins the session corresponding to the first MBS, the first network element opens the CDR of the first MBS and records the identifier of the first MBS on the CDR, that is, when the second network element subsequently sends the first message to the first network element carrying the identifier of the first MBS, the first network element can update the CDR. In addition, the first network element can also record the joining time of the terminal and the identifier of the second network element on the CDR.

[0172] Mode 2: The first message includes the identifier of the first MBS and the transmission mode of the first MBS

[0173] The first network element obtains the identifier of the first MBS and the transmission mode of the first MBS, and updates the CDR of the first MBS. For example, when the triggering event of the first message is that the terminal joins the session corresponding to the first MBS, the first network element opens the CDR of the first MBS and records the identifier of the first MBS and the transmission mode of the first MBS in the CDR. The first network element may send the triggering event of the first MBS to the second network element according to the identifier of the first MBS. The first network element may also send the quota authorized by the first MBS to the second network element according to the transmission mode of the first MBS and the rate group of the first MBS.

[0174] Mode 3: The first message includes the identifier of the first MBS, the transmission mode of the first MBS, and the usage report of the terminal joining the first MBS for the first MBS

[0175] The first network element obtains the identifier of the first MBS, the transmission mode of the first MBS, and the usage report of the terminal joining the first MBS for the first MBS, and updates the CDR of the first MBS. For example, when the triggering event of the first message is the change of the transmission mode of the first MBS, the first network element can obtain the usage report of the first MBS and perform a fee deduction process. The first network element can record the transmission mode of the first MBS, the identifier of the first MBS, and the usage report of the terminal joining the first MBS for the first MBS in the CDR. The first network element can also issue the quota authorized by the first MBS to the second network element according to the transmission mode of the first MBS and the rate group of the first MBS. For example, when the triggering event of the first message is that the terminal exits the session corresponding to the first MBS, the first network element can record the usage report of the first MBS in the CDR, and perform a fee deduction process according to the billing rules corresponding to the usage and rate group. The first network element can also issue a quota to delete the authorization of the first MBS to the second network element according to the triggering event of the first message.

[0176] In addition, there are other methods, such as the first message includes the identifier of the first MBS, the triggering event of the first message, and the transmission mode of the first MBS; the first message includes the identifier of the first MBS, the triggering event of the first message, and the usage report of the terminal joining the first MBS for the first MBS; the first message includes the identifier of the first MBS, and the usage report of the terminal joining the first MBS for the first MBS; the first message includes the identifier of the first MBS, the triggering event of the first message, the transmission mode of the first MBS, and the usage report of the terminal joining the first MBS for the first MBS. You can refer to the above methods 1 to 3 to understand how the first network element updates the billing information of the first MBS.

[0177] In the present application, the first network element updates the billing information of the first MBS according to the first message. The first message includes information such as the triggering event of the first message, the transmission method of the MBS, and the usage report of the terminal joining the MBS for the MBS. In this way, the first network element can charge the terminal joining the MBS, charge the user, and further optimize the billing of multicast broadcast.

[0178] The present application also provides a communication method such as Figure 5 As shown, the communication method can be implemented through data interaction among a first network element, a second network element and a third network element, wherein the first network element may be a CHF, or a network element capable of implementing a billing function, the second network element may be an SMF, or a module for billing in the SMF, or a first CTF, and the third network element may be an MB-SMF, or a module for billing in the MB-SMF, or a second CTF, which is not specifically limited in the present application. Figure 5 Take the first network element as CHF1, CHF2, the second network element as SMF, and the third network element as MB-SMF as an example. In actual implementation, it may be divided into two different schemes for execution. The specific implementation is as follows:

[0179] Solution 1:

[0180] Step 501A: The MB-SMF generates a second message, where the second message includes at least one of the following information:

[0181] The triggering event of the second message, the service type of the first MBS, the usage report of the first MBS, and the identifier of the first MBS.

[0182] The second message mentioned above is used for charging request in this application, and the second message can be sent alone or carried in other messages, which is not specifically limited in this application. The second message carries the identifier of the first MBS so that the first network element knows which service to charge.

[0183] It should be noted that the second message may include one or more of the following:

[0184] Charging Data Request (Charging Data Request / Charging Data Request[Initial] / Charging Data Request[Update] / Charging Data Request[Termination]); Converged Charging Create Request (Nchf_ConvergedCharging_Create request); Converged Charging Update Request (Nchf_ConvergedCharging_Update request); Converged Charging Release Request (Nchf_ConvergedCharging_Release request); Offline Charging Create Request (Nchf_OfflineOnlyCharging_Create request); Offline Charging Update Request (Nchf_OfflineOnlyCharging_Update request); Offline Charging Release Request (Nchf_OfflineOnlyCharging_Release request), etc. The second message may also be a new message, which is not limited in this patent.

[0185] The triggering event of the second message indicates that the third network element reports the specific reason of the first message to the first network element so that the first network element can adjust the billing information. For example, if the triggering event of the second message is to activate the session corresponding to the first MBS, the first network element can generate the billing information of the first MBS. This is only an example description, and it is not specifically limited in actual application. The service type of the first MBS is broadcast or multicast, and the first network element can configure the billing policy according to the different service types of the first MBS. The usage report of the first MBS can indicate the current billing situation of the first MBS, so that the first network element can update the billing information of the first MBS. For example, the first network element can adjust the quota information of the first MBS according to the usage report of the first MBS.

[0186] Specifically, the triggering events of the second message include the following situations:

[0187] Case 1: Activate the session corresponding to the first MBS

[0188] Since the session corresponding to the first MBS is activated, the first network element will generate charging information based on this, which will trigger the third network element to report the second message.

[0189] Case 2: Deactivate the session corresponding to the first MBS

[0190] Since the session corresponding to the first MBS is deactivated, the first network element no longer generates charging information based on the first MBS, which triggers the third network element to report the second message.

[0191] Case 3: Adding a multicast / broadcast user plane function network element for transmitting the first MBS data

[0192] Due to the addition of a multicast / broadcast user plane functional network element for transmitting the data of the first MBS, the CHF may need to update the authorized quota. For example, the total quota of the first MBS session is 10MB. If there is only one UPF for transmitting the data of the first MBS, then the quota given by the CHF to this UPF is 10MB, but if there are two UPFs, then each UPF is 5MB.

[0193] Case 4: Deleting the multicast / broadcast user plane function network element used to transmit the first MBS data

[0194] Since the CHF may need to record the final usage reported by the multicast / broadcast user plane functional network element in the CDR of the first MBS and perform a fee deduction process, when situation 4 occurs, it is necessary to report the second message.

[0195] Case 5: Adding access network equipment for transmitting the first MBS data

[0196] Case 6: Deleting the access network device that transmits the first MBS data

[0197] Case 7: Adding a user plane function network element for transmitting data of the first MBS

[0198] Case 8: Deleting the user plane function network element used to transmit the first MBS data

[0199] In the above-mentioned cases 5 to 8, the data of the first MBS is copied one more time and forwarded to the RAN / UPF, which is helpful for the operator to know the actual network resource occupation of the MBS session. The CHF can record the copying situation corresponding to the current usage of the MBS session on the CDR (the copying situation can be reflected in the number of copies, specific copying information, etc.), so when the above-mentioned situation occurs, the second message needs to be reported.

[0200] Case 9: The service area of ​​the first MBS changes

[0201] In 4G MBMS, the data of the first MBS will be transmitted to all base stations in the designated service area, so the usage of the first MBS can be calculated based on the data size of the first MBS and the number of base stations in the designated service area. Therefore, when the service area of ​​the first MBS changes, the number of base stations in the area will also change, and the second message needs to be reported.

[0202] Of course, in actual application, the triggering event of the second message may be a combination of the above situations, such as: adding a RAN for transmitting data of the first MBS, and at the same time, deleting the UPF used to transmit data of the first MBS, etc., which is not specifically limited here.

[0203] In addition, the second message also includes: a charging identifier of the first MBS, quality of service QoS information of the first MBS, and a service area of ​​the first MBS.

[0204] Specifically, after receiving the MBS session request message from the content provider, the MB-SMF can generate a charging identifier for the first MBS according to the parameters of the MBS session carried in the MBS session request message, so that the first network element can determine the need to charge the session corresponding to the first MBS according to the charging identifier of the first MBS. The second message includes the QoS information of the first MBS and the service area of ​​the first MBS, which can facilitate the operator to perform billing reconciliation.

[0205] Step 502A: MB-SMF sends a second message to CHF1.

[0206] During the service registration phase, CHF can register with NRF whether it supports 5G multicast broadcast capabilities. When MB-SMF receives a request to create a multicast / broadcast session, it can request CHF from NRF. The request message needs to carry an identifier indicating that NRF needs to return a CHF that supports 5G multicast broadcast capabilities. Then MB-SMF can determine CHF1 and send a second message to CHF1.

[0207] Step 503A: CHF1 updates the charging information of the first MBS according to the second message.

[0208] Specifically, for different second messages, the updating of the billing information of the first MBS in step 503A can be understood differently. For example, when the first MBS session is established, the first message can be understood as initialization (Initial), then the above-mentioned updating of the billing information of the first MBS can be understood as opening the billing information of the first MBS; when a new MB-UPF is added to the first MBS session, the first message can be understood as update (Update), then the above-mentioned updating of the billing information of the first MBS can be understood as updating the billing information of the first MBS; when the first MBS session is released, the above-mentioned updating of the billing information of the first MBS can be understood as terminating the billing of the first MBS (Termination). The present application does not specifically limit the specific meaning of "update" in step 503A, which can be flexibly determined according to actual applications and is not specifically limited here.

[0209] Specifically, when the second message is different information, the first network element may update the charging information of the first MBS in different ways, as follows:

[0210] Mode 1: The second message includes the identifier of the first MBS and the service type of the first MBS

[0211] After the first network element obtains the identifier of the first MBS and the service type of the first MBS, it opens the CDR of the first MBS, such as opening the CDR of the first MBS and recording the identifier and service type of the first MBS. The first network element may send the trigger event of the first MBS to the third network element according to the identifier and service type of the first MBS. The first network element may also send the quota authorized by the first MBS to the third network element according to the rate group of the first MBS.

[0212] Mode 2: The second message includes the identifier of the first MBS and the triggering event of the second message

[0213] The first network element obtains the identifier of the first MBS and the triggering event of the second message, and updates the CDR of the first MBS. For example, when the triggering event of the first message is the addition of a new MB-UPF, the first network element obtains the identifier of the first MBS to find the corresponding CDR, and records the newly added MB-UPF identifier in the CDR. The second network element may also adjust the quota authorized by the first MBS according to the rate group of the first MBS, and update the quota authorized by the first MBS to the second network element.

[0214] Mode 3: The second message includes the identifier of the first MBS, the triggering event of the second message, and the usage report of the first MBS

[0215] The first network element obtains the identifier of the first MBS, the triggering event of the second message, and the usage report of the first MBS, and updates the CDR of the first MBS. For example, when the triggering event of the first message is to delete the MB-UPF, the first network element obtains the identifier of the first MBS to find the corresponding CDR, and records the triggering event and the usage report on the CDR. The first network element can deduct fees based on the usage report of the first MBS. The first network element can also adjust the quota authorized by the first MBS based on the triggering event and usage report of the second message, and issue the quota authorized by the first MBS to the third network element.

[0216] Step 501B, SMF generates a first message.

[0217] Step 502B: SMF sends a first message to CHF2.

[0218] Step 503B: CHF2 updates the charging information of the first MBS according to the first message.

[0219] The execution of the above steps 501A-501B, 501B-502B may not be sequentially distinguished. The billing information of the first MBS is updated through different CHFs. In actual application, this method cannot integrate different billing information of the first MBS.

[0220] The above-mentioned solution 1 can count the usage and number of copies of the data of the first MBS of the first MBS session, which is helpful to measure the occupation of network resources by the first MBS session and charge the content provider. At the same time, solution 1 can measure the usage of the terminal joining the first MBS under different transmission modes, which is helpful to measure the occupation of network resources when the user uses the first MBS and charge the user.

[0221] Option 2:

[0222] Optionally, in order to ensure the consistency of CHF1 and CHF2, the following steps 504 to 506 may be performed. In this case, steps 501A to 501C may be performed first, and then steps 504 to 506 may be performed. Step 506 may replace the above-mentioned step 501B and be performed as follows, wherein the steps identical to those in solution 1 are not repeated here:

[0223] Step 504: SMF sends context request information of the first MBS to MB-SMF.

[0224] Step 505: MB-SMF sends the context information of the first MBS to SMF, wherein the context information of the first MBS includes: identification information of CHF1.

[0225] Step 506: SMF sends a first message to CHF1 according to the identification information of CHF1.

[0226] Step 507: CHF1 updates the charging information of the first MBS according to the second message.

[0227] After obtaining the context information of the first MBS, the SMF will separately save the context information of the first MBS and provide the context information of the first MBS to all UEs requesting to join the multicast group on the SMF. The SMF can generate a billing identifier for the context information of the first MBS and request the billing information of the first MBS from CHF1 when the first UE requests to join the session corresponding to the first MBS.

[0228] In the above solution 2, since the SMF and MB-SMF send messages to the same CHF, it is also beneficial to measure the user usage more accurately. At the same time, when the quota of the first MBS is used for all users joining the first MBS, it can be adjusted in time when the quota is exhausted or the remaining quota reaches a threshold.

[0229] It should also be noted that the triggering event of the above-mentioned first message can be sent as a first charging policy through the first network element, and the triggering event of the above-mentioned second message can be sent as a second charging policy through the first network element.

[0230] In order to better illustrate the solution of the present application, the following specific application scenario can be used for illustration. Of course, in actual application, the specific scenario is not limited. The following scenario is illustrated by taking the data interaction of AF, SMF (equivalent to the second network element), MB-SMF (equivalent to the third network element), MB-UPF, UPF, CHF (equivalent to the first network element), UE, RAN, and AMF as an example.

[0231] Scene 1 UE joins the multicast group using 5GC Shared MBS traffic delivery method

[0232] Refer to the attached Figure 6 Execute as follows:

[0233] Step 601: AF sends a request message to MB-SMF.

[0234] The request message is an MBS session creation request (Nmbsmf MBSSession Create Request, which carries MBS session information (including QoS parameters such as 5G QoS indicator (5G QoS identifier, 5QI), allocation and retention priority (allocation and retention priority, ARP), maximum bit rate (maximum bit rate, MBR)), MBS service type (multicast / broadcast), etc., and optionally carries an MBS session ID or a request to allocate a temporary mobile group identity (temporary mobile group identity, TMGI), MBS service area, etc.

[0235] Step 602: MB-SMF may generate a charging identifier for the MBS session and send a request message to the CHF.

[0236] The request message may be a Charging Data Request, or may be an Nchf_ConvergedCharging_Create message, or may be an Nchf_OfflineOnlyCharging_Create message, which is mainly used to request a charging policy (i.e., the second charging policy). The request message carries a charging ID, an MBS session ID, an MBS service type, and MBS session information (including QoS parameters such as 5QI, ARP, and MBR), and may optionally carry an MBS service area. If it is an online charging scenario, the request message may also include a quota management request.

[0237] Step 603, CHF opens CDR and sends a response message to MB-SMF, where the response message includes a trigger event (that is, the trigger event of the second message mentioned above, which will not be described in detail here and can be understood by referring to the above).

[0238] Specifically, the response message is a charging data response Charging Data Response, which can provide usage report triggers applicable to multicast services, including adding / deleting MB-UPF, adding / deleting base stations / UPF, MBS service area changes (which can be TA granularity, SA granularity or Cell granularity), etc. (that is, the triggering event of the second message). If it is an online charging scenario, the response message can also include the quota information allocated by CHF for the multicast session.

[0239] Step 604: The MB-SMF selects a MB-UPF and requests it to establish an MBS session.

[0240] The above step 604 may select the MB-UPF based on the local settings of the MB-SMF.

[0241] Step 605: MB-SMF sends a response message to AF.

[0242] The response message is an MBS session creation response Nmbsmf MBSSession Create Response, so that the AF knows that the MBS session creation is completed.

[0243] Step 606: The UE sends a PDU Session Modification request message to the AMF.

[0244] The PDU Session Modification request message is sent through the established PDU session and carries a request to join a multicast group and an identifier of the multicast group.

[0245] Step 607: AMF sends the request message to SMF via Nsmf PDUSession UpdateSMContext request.

[0246] If the SMF finds that the MBS session context of the multicast group is not subscribed, step 608 may be executed.

[0247] Step 608: SMF sends a message Nmbsmf MBSSession ContextStatusSubscribe to MB-SMF to request to obtain the MBS session context information.

[0248] Step 609: MB-SMF sends the context information of the MBS session to SMF.

[0249] In step 609, the identifier of the MB-SMF selecting the CHF and the multicast QosFlow information (QoS Profile) etc. may be carried.

[0250] Step 610: SMF sends a response message to AMF to confirm acceptance of the UE's request to join the multicast group.

[0251] Step 611: AMF sends a message to RAN that the UE joins the multicast group.

[0252] If the RAN does not establish a shared tunnel for the multicast group that the UE joins, step 612 is executed.

[0253] Step 612: RAN sends a shared tunnel establishment request message to MB-SMF through AMF.

[0254] The request message is Nmbsmf MBSSession ContextUpdate request, which may carry a multicast group identifier, a RAN Node ID, and tunnel information allocated by the RAN for the shared tunnel (N3mb).

[0255] Step 613: MB-SMF sends a Charging Data Request to CHF.

[0256] The Charging Data Request may be understood as the second message mentioned above, and may include charging information and a newly added base station identifier.

[0257] Step 614: CHF updates the CDR of the multicast session and sends a response message to MB-SMF.

[0258] Step 615: MB-SMF sends a session update request message to MB-UPF.

[0259] The request message is used to request allocation of tunnel information for the shared tunnel (N3mb), and at the same time sends the tunnel information allocated by the RAN to the shared tunnel (N3mb) in step 612.

[0260] Step 616: MB-SMF receives the session update request response message sent by MB-UPF.

[0261] The response message includes the tunnel information allocated by the MB-UPF for the shared tunnel (N3mb).

[0262] Step 617, MB-SMF sends a response to AMF, carrying the tunnel information allocated by MB-UPF for the shared tunnel (N3mb), and transparently transmits it to RAN through AMF.

[0263] Step 618: RAN sends a PDU session modification response message to AMF.

[0264] Step 619: AMF sends a request message to SMF.

[0265] The request message is Nsmf PDUSession UpdateSMContext request, and carries an identifier that the RAN supports MBS.

[0266] Step 620: SMF sends a Charging Data Request to CHF.

[0267] The Charging Data Request can be understood as the first message, which carries the identifier of the multicast group to which the UE joins, the action of identifying the UE to join the multicast session, the UE using the 5GC Shared MBS traffic delivery method to join the multicast group, and the UE's rate group.

[0268] The above step 619 may be sent by the SMF to the CHF by default when the UE joins the session, or may be based on the local configuration of the SMF.

[0269] Step 621, CHF opens / updates CDR and sends a response message to SMF.

[0270] The response message is Charging Data Response, which can optionally provide triggering events applicable to the first message of the usage of the multicast service, including the UE joining the multicast group, the UE's transmission mode change, etc. If it is an online charging scenario, the response message can also include the quota of the rate group related to the multicast service allocated by the CHF to the UE. In addition, when the first UE in the multicast group joins the multicast group, step 621 is to open the CDR. When it is not the first UE in the multicast group to join the multicast group, step 621 is to update the CDR.

[0271] Step 622, SMF sends a response message Nsmf PDUSession UpdateSMContext response to AMF.

[0272] It should be noted that the above-mentioned interaction steps between SMF and CHF, steps 620 and 621, can also be performed after step 607. The present application does not specifically limit the execution order of steps 620 and 621. The above-mentioned scenario 1 is only an exemplary description. Similarly, the interaction steps between MB-SMF and CHF, steps 602 and 603, for example, can also be performed after step 604. The present application does not specifically limit the execution order of steps 602 and 603. The above-mentioned scenario 1 is only an exemplary description. The interaction steps between MB-SMF and CHF, steps 613 and 614, can also be performed after step 616. The present application does not specifically limit the execution order of steps 613 and 614. The above-mentioned scenario 1 is only an exemplary description.

[0273] Scene 2 UE joins the multicast group using 5GC Individual MBS traffic delivery method

[0274] Refer to the attached Figure 7 Execute as follows:

[0275] Step 701: AF sends a request message to MB-SMF.

[0276] Step 702: MB-SMF may generate a charging identifier for the MBS session and send a request message to the CHF.

[0277] Step 703: CHF opens the CDR and sends a response message to the MB-SMF, where the response message includes the triggering event.

[0278] Step 704: MB-SMF selects a MB-UPF and requests it to establish a session.

[0279] Step 705: MB-SMF sends a response message to AF.

[0280] Steps 701 to 705 can be understood by referring to steps 601 to 605 in the above scenario 1, and are not described in detail here.

[0281] Step 706: The UE sends a PDU Session Modification request message to the AMF.

[0282] Step 707: AMF sends a request message to SMF via Nsmf_PDUSession_UpdateSMContext request.

[0283] Step 708: SMF sends a message Nmbsmf_MBSSession_ContextStatusSubscribe to MB-SMF to request to obtain the MBS session context information.

[0284] Step 709: MB-SMF sends the context information of the MBS session to SMF.

[0285] Step 710: SMF sends a response message to AMF to confirm acceptance of the UE's request to join the multicast group.

[0286] Step 711: AMF sends a message to RAN that the UE joins the multicast group.

[0287] Step 712: RAN sends a PDU session modification response message to AMF.

[0288] Step 713: AMF sends a request message to SMF.

[0289] Step 714: SMF sends a Charging Data Request to CHF.

[0290] The Charging Data Request can be understood as the first message mentioned above, carrying the multicast group identifier of the UE, the action of identifying the UE to join the multicast session, the UE using the 5GC Individual MBS traffic delivery method to join the multicast group, and the UE's rate group.

[0291] The above step 714 may be sent by the SMF to the CHF by default when the UE joins the session, or may be based on the local configuration of the SMF.

[0292] Step 715: CHF updates CDR and sends a response message to SMF.

[0293] The response message is Charging Data Response, which may optionally provide triggering events applicable to the use of the multicast service, including UE exiting the multicast group, UE transmission mode change, etc. If it is an online charging scenario, the response message may also include the quota of the rate group related to the multicast service allocated by the CHF to the UE.

[0294] CHF can also instruct SMF / UPF to separately count the UE's use of multicast services and set up a special rate group (that is, when the UE adopts the 5GC Individual MBS traffic delivery method, the UPF uses the N3 tunnel of the UE's PDU session to forward messages. CHF can instruct UPF to distinguish between ordinary services and multicast services).

[0295] If the RAN does not support MBS, and the UPF does not establish a shared tunnel with the MB-UPF for the multicast group, step 716 is executed.

[0296] Step 716: SMF sends a request message for establishing a shared tunnel to UPF.

[0297] Step 717, UPF allocates shared tunnel information to SMF.

[0298] Step 718: SMF sends a shared tunnel establishment request message to MB-SMF.

[0299] The request message carries the multicast group identifier, UPF identifier, and tunnel information allocated by UPF to the shared tunnel (N19mb).

[0300] Step 719: MB-SMF sends a Charging Data Request to CHF.

[0301] The Charging Data Request may be understood as the second message mentioned above, and may include charging information and a newly added UPF identifier.

[0302] Step 720: CHF updates the CDR of the multicast session and sends a Charging Data Response message to MB-SMF.

[0303] Step 721, MB-SMF sends a session update request message to MB-UPF.

[0304] The request message is used to request allocation of tunnel information for the shared tunnel (N19mb), and at the same time sends the tunnel information allocated by the RAN to the shared tunnel (N19mb) in step 716.

[0305] Step 722: MB-UPF sends a response to MB-SMF.

[0306] Step 723, MB-SMF sends a response to SMF, carrying the tunnel information allocated by MB-UPF for the shared tunnel (N19mb).

[0307] Step 724, SMF sends the tunnel information allocated by MB-UPF to the shared tunnel (N19mb) to UPF.

[0308] Step 725, SMF sends a response message Nsmf_PDUSession_UpdateSMContext response to AMF.

[0309] It should be noted that the above-mentioned interaction steps between SMF and CHF, steps 714 and 715, can also be performed after step 724. The present application does not specifically limit the execution order of steps 714 and 715. The above-mentioned scenario 2 is only an exemplary description. Similarly, the interaction steps between MB-SMF and CHF, steps 702 and 703, for example, can also be performed after step 704. The present application does not specifically limit the execution order of steps 702 and 703. The above-mentioned scenario 2 is only an exemplary description. The interaction steps between MB-SMF and CHF, steps 719 and 720, can also be performed after step 721. The present application does not specifically limit the execution order of steps 719 and 720. The above-mentioned scenario 2 is only an exemplary description.

[0310] Scene 3 UE uses 5GC Shared MBS traffic delivery method to exit the multicast group

[0311] Refer to the attached Figure 8 Execute as follows:

[0312] Step 801: UE sends a PDU Session Modification request message to AMF.

[0313] The PDU Session Modification request message is sent through the established PDU session and carries a request to exit the multicast group and an identifier of the multicast group.

[0314] Step 802, AMF sends a request message to SMF via Nsmf_PDUSession_UpdateSMContext request.

[0315] Step 803: SMF sends a Charging Data Request to CHF.

[0316] The Charging Data Request can be understood as the first message mentioned above, carrying the multicast group identifier of the UE to exit, the action of the UE to exit the multicast session, the UE's use of the 5GC Shared MBS traffic delivery method to exit the multicast group, and the UE's usage report. The usage report includes the UE's rate group, the time when the UE joins and exits the multicast group, and the start and end time of the UE's use of the current transmission method.

[0317] Optionally, if CHF instructs SMF to delay reporting the first message, SMF may provide CHF with the single or multiple transmission modes used by the UE after exiting the multicast group and the start and end time of each transmission mode used.

[0318] Step 804: CHF updates CDR and sends a response message to SMF.

[0319] The response message is Charging Data Response. Optionally, the CHF may delete the triggering event of the first message previously sent to the SMF (eg, in the MBS session creation phase) and the quota information of the first MBS.

[0320] If the RAN supports MBS and the UE is the last UE in the multicast group on the RAN, step 805 is executed.

[0321] Step 805, SMF sends a response message Nsmf_PDUSession_UpdateSMContext response to AMF.

[0322] Step 806: AMF sends a message to RAN that the UE exits the multicast group.

[0323] Step 807: RAN sends a Nmbsmf_MBSSession_ContextUpdate request message to MB-SMF through AMF to request the release of the shared tunnel (N3mb).

[0324] Step 808: MB-SMF requests MB-UPF to release the shared tunnel (N3mb).

[0325] Step 809: When MB-UPF releases the shared tunnel, it may additionally carry the statistics of multicast service usage in the response.

[0326] Step 810: MB-SMF sends a Charging Data Request to CHF.

[0327] The Charging Data Request may be understood as the second message mentioned above, wherein the second message includes reporting the usage of the multicast service statistics reported by the MB-UPF and the ID of the released base station.

[0328] Step 811, CHF updates the CDR of the multicast session and sends a Charging Data Response message to MB-SMF.

[0329] Step 812: MB-SMF sends a response message Nmbsmf_MBSSession_ContextUpdateresponse to the RAN.

[0330] It should be noted that the above-mentioned SMF and CHF interaction steps, steps 803 and 804, can also be performed after step 805. The present application does not specifically limit the execution order of steps 803 and 804. The above-mentioned scenario 3 is only an exemplary description. Similarly, the MB-SMF and CHF interaction steps, steps 810 and 811, for example, can also be performed after step 807. The present application does not specifically limit the execution order of steps 810 and 811. The above-mentioned scenario 3 is only an exemplary description.

[0331] Scene 4 UE uses 5GC Individual MBS traffic delivery method to exit the multicast group

[0332] Refer to the attached Fig. 9 Execute as follows:

[0333] Step 901: UE sends a PDU Session Modification request message to AMF.

[0334] The PDU Session Modification request message is sent through the established PDU session and carries a request to exit the multicast group and an identifier of the multicast group.

[0335] Step 902, AMF sends a request message to SMF via Nsmf_PDUSession_UpdateSMContext request.

[0336] Step 903: SMF sends a Charging Data Request to CHF.

[0337] The Charging Data Request can be understood as the first message mentioned above, carrying the multicast group identifier of the UE to exit, the action of the UE to exit the multicast session, the UE's use of 5GC Individual MBS traffic delivery method to exit the multicast group, and the UE's usage report. The usage report includes the UE's rate group, the time when the UE joins and exits the multicast group, and the start and end time of the UE's use of the current transmission method.

[0338] Optionally, if CHF instructs SMF to delay reporting the first message, SMF may provide CHF with the single or multiple transmission modes used by the UE after exiting the multicast group and the start and end time of each transmission mode used.

[0339] Step 904: CHF updates CDR and sends a response message to SMF.

[0340] If the UE is the last UE in the multicast group on the UPF, execute step 905.

[0341] Step 905, SMF sends a Nmbsmf_MBSSession_ContextUpdate request message to MB-SMF to request the release of the shared tunnel (N19mb).

[0342] Step 906, MB-SMF requests MB-UPF to release the shared tunnel (N19mb).

[0343] Step 907: When MB-UPF releases the shared tunnel, it may additionally carry statistics on the use of the multicast service in the response.

[0344] Step 908: MB-SMF sends a Charging Data Request to CHF.

[0345] The Charging Data Request may be understood as the second message mentioned above, wherein the second message includes reporting the usage of the multicast service statistics reported by the MB-UPF and the released UPF ID.

[0346] Step 909: CHF updates the CDR of the multicast session and sends a Charging Data Response message to MB-SMF.

[0347] Step 910: MB-SMF sends a response message Nmbsmf_MBSSession_ContextUpdateresponse to SMF.

[0348] Step 911, SMF sends a response message Nsmf_PDUSession_UpdateSMContext response to AMF.

[0349] It should be noted that the above-mentioned SMF and CHF interaction steps, steps 903 and 904, can also be performed after step 911. The present application does not specifically limit the execution order of steps 903 and 904. The above-mentioned scenario 4 is only an exemplary description. Similarly, the MB-SMF and CHF interaction steps, steps 908 and 909, for example, can also be performed after step 905. The present application does not specifically limit the execution order of steps 908 and 909. The above-mentioned scenario 4 is only an exemplary description.

[0350] The above-mentioned scenarios 1 to 4 can realize accurate billing of the first MBS session (based on volume / duration / event, rather than 4G MBMS based on coverage), and still support charging content providers. At the same time, by reporting the dynamic topology changes of base stations and UPFs, the detailed and accurate level of the measurement standard for the occupation of network resources by multicast sessions is improved, and it supports billing of terminals using the first MBS (based on volume / duration / event, 4G MBMS cannot charge terminals), and charges the terminals. At the same time, the usage time of users using shared transmission and the usage statistics of UPF of users using separate transmission are reported, which improves the detailed and accurate level of the measurement standard for the occupation of network resources by users in multicast sessions.

[0351] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of device interaction. It is understandable that, in order to implement the above functions, each device may include a hardware structure and / or software module corresponding to each function. It should be easily appreciated by those skilled in the art that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the embodiments of the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0352] The embodiment of the present application can divide the functional units of the device according to the above method example, for example, each functional unit can be divided according to each function, or two or more functions can be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of software functional units.

[0353] In the case of an integrated unit, Fig.10 FIG. 1 shows a possible exemplary block diagram of a communication device involved in an embodiment of the present application. Fig.10 As shown, the communication device 1000 may include: a processing unit 1001 and a transceiver unit 1002. The processing unit 1001 is used to control and manage the actions of the communication device 1000. The transceiver unit 1002 is used to support the communication between the communication device 1000 and other devices. Optionally, the transceiver unit 1002 may include a receiving unit and / or a sending unit, which are respectively used to perform receiving and sending operations. Optionally, the communication device 1000 may also include a storage unit for storing program code and / or data of the communication device 1000. The transceiver unit may be called an input-output unit, a communication unit, etc., and the transceiver unit may be a transceiver; the processing unit may be a processor. When the communication device is a module (such as a chip) in a communication device, the transceiver unit may be an input-output interface, an input-output circuit or an input-output pin, etc., and may also be called an interface, a communication interface or an interface circuit, etc.; the processing unit may be a processor, a processing circuit or a logic circuit, etc. Specifically, the device may be the above-mentioned first network element, second network element, and third network element, etc.

[0354] In one embodiment, the communication device 1000 may serve as a first network element, and the transceiver unit 1002 is configured to receive a first message from a second network element, where the first message includes an identifier of a first multicast / broadcast service MBS and at least one of the following information:

[0355] A triggering event of the first message, a transmission mode of the first MBS, and a usage report of the first MBS by a terminal joining the first MBS;

[0356] The processing unit 1001 updates the charging information of the first MBS according to the first message.

[0357] Optionally, the triggering event of the first message includes:

[0358] The terminal joins the session corresponding to the first MBS;

[0359] The terminal exits the session corresponding to the first MBS;

[0360] The transmission mode of the first MBS changes.

[0361] Optionally, the transmission method of the first MBS is 5G core network individual multicast / broadcast service traffic transmission method 5GC Individual MBS traffic delivery method or 5G core network shared multicast / broadcast service traffic transmission method 5GC Shared MBS traffic delivery method.

[0362] Optionally, the transceiver unit 1002 is further configured to receive a second message from a third network element, where the second message includes at least one of the following information:

[0363] The charging identifier of the first MBS, the triggering event of the second message, the service type of the first MBS, the quality of service QoS information of the first MBS, the service area of ​​the first MBS, and the usage report of the first MBS.

[0364] Optionally, the triggering event of the second message includes at least one of the following:

[0365] Activate the session corresponding to the first MBS;

[0366] Deactivating a session corresponding to the first MBS;

[0367] A multicast / broadcast user plane function network element is added for transmitting data of the first MBS;

[0368] Deleting a multicast / broadcast user plane function network element used to transmit data of the first MBS;

[0369] Adding access network equipment for transmitting data of the first MBS;

[0370] Deleting the access network device that transmits the data of the first MBS;

[0371] A user plane function network element is added for transmitting data of the first MBS;

[0372] Deleting a user plane function network element used to transmit data of the first MBS;

[0373] The service area of ​​the first MBS changes.

[0374] Optionally, the processing unit 1001 is further configured to update the charging information of the first MBS according to the second message.

[0375] Optionally, the usage report includes: rate group.

[0376] Optionally, the transceiver unit 1002 is further configured to send a quota of the terminal for the rate group of the first MBS to the second network element.

[0377] Optionally, the transceiver unit 1002 is further configured to send the quota of the rate group of the first MBS to the third network element.

[0378] Optionally, the transceiver unit 1002 is further configured to send a first charging policy to the second network element, where the first charging policy includes a triggering event of the first message.

[0379] Optionally, the transceiver unit 1002 is further configured to send a second charging policy to a third network element, where the second charging policy includes a triggering event of the second message.

[0380] Optionally, the first network element is a charging function network element CHF; the second network element is a session management function network element SMF; the third network element is a multicast broadcast session management function network element MB-SMF; or, the second network element is a first charging trigger function CTF, and the third network element is a second CTF.

[0381] In one embodiment, the communication device 1000 may serve as a second network element, and the processing unit 1001 is configured to generate a first message, where the first message includes an identifier of a first multicast / broadcast service MBS and at least one of the following information:

[0382] A triggering event of the first message, a transmission mode of the first MBS, and a usage report of the first MBS by a terminal joining the first MBS;

[0383] The transceiver unit 1002 is configured to send a first message to a first network element.

[0384] Optionally, the triggering event of the first message includes:

[0385] The terminal joins the first MBS;

[0386] The terminal exits the first MBS;

[0387] The transmission mode of the first MBS changes.

[0388] Optionally, the transmission method of the first MBS is 5G core network individual multicast / broadcast service traffic transmission method 5GC Individual MBS traffic delivery method or 5G core network shared multicast / broadcast service traffic transmission method 5GC Shared MBS traffic delivery method.

[0389] Optionally, the usage report includes: rate group.

[0390] Optionally, the transceiver unit 1002 is further configured to receive a quota of a rate group for the first MBS from a terminal of the first network element.

[0391] Optionally, the transceiver unit 1002 is further used to send context request information of the first MBS to a third network element; receive context information of the first MBS from the third network element, the context information including identification information of the first network element; and send a first message to the first network element according to the identification information of the first network element.

[0392] Optionally, the transceiver unit 1002 is further configured to receive a first charging policy from the first network element, where the first charging policy includes a triggering event of the first message;

[0393] The processing unit 1001 is further configured to determine, according to the first charging policy, a triggering event for sending the first message.

[0394] In one embodiment, the communication device 1000 may serve as a third network element, and the processing unit 1001 is configured to generate a second message, where the second message includes an identifier of the first multicast / broadcast service MBS and at least one of the following information:

[0395] The charging identifier of the first MBS, the triggering event of the second message, the service type of the first MBS, the quality of service QoS information of the first MBS, the service area of ​​the first MBS, and the usage report of the first MBS;

[0396] The transceiver unit 1002 is configured to send a second message to the first network element.

[0397] Optionally, the triggering event of the second message includes one of the following:

[0398] Activate the session corresponding to the first MBS;

[0399] Deactivating a session corresponding to the first MBS;

[0400] A multicast / broadcast user plane function network element is added for transmitting data of the first MBS;

[0401] Deleting a multicast / broadcast user plane function network element used to transmit data of the first MBS;

[0402] Adding access network equipment for transmitting data of the first MBS;

[0403] Deleting the access network device that transmits the data of the first MBS;

[0404] A user plane function network element is added for transmitting data of the first MBS;

[0405] Deleting a user plane function network element used to transmit data of the first MBS;

[0406] The service area of ​​the first MBS changes.

[0407] Optionally, the usage report includes: rate group.

[0408] Optionally, the transceiver unit 1002 is configured to receive a quota of a rate group of a first MBS from a first network element.

[0409] Optionally, the transceiver unit 1002 is configured to receive context request information of the first MBS from the second network element; and send context information of the first MBS to the second network element, where the context information includes an identifier of the first network element.

[0410] Optionally, the transceiver unit 1002 is configured to receive a second charging policy from the first network element, where the second charging policy includes a triggering event of the second message;

[0411] The processing unit 1001 is configured to determine, according to a second charging policy, a triggering event for sending a second message.

[0412] like Fig.11 As shown, a communication device 1100 is also provided in the present application. The communication device 1100 may be a chip or a chip system. The communication device may be located in a device involved in any of the above method embodiments, such as an access network device, or an SMF, etc., to perform actions corresponding to the device.

[0413] Optionally, the chip system may consist of the chip, or may include the chip and other discrete devices.

[0414] The communication device 1100 includes a processor 1110 .

[0415] The processor 1110 is used to execute the computer program stored in the memory 1120 to implement the actions of each device in any of the above method embodiments.

[0416] The communication device 1100 may further include a memory 1120 for storing computer programs.

[0417] Optionally, the memory 1120 is coupled to the processor 1110. Coupling is an indirect coupling or communication connection between devices, units or modules, which can be electrical, mechanical or other forms, for information exchange between devices, units or modules. Optionally, the memory 1120 is integrated with the processor 1110.

[0418] The processor 1110 and the memory 1120 may be one or more and are not limited.

[0419] Optionally, in practical applications, the communication device 1100 may include a transceiver 1130 or may not include the transceiver 1130, which is illustrated by a dotted box in the figure. The communication device 1100 may exchange information with other devices through the transceiver 1130. The transceiver 1130 may be a circuit, a bus, a transceiver, or any other device that can be used for information exchange.

[0420] In a possible implementation, the communication device 1100 may be an access network device, or a session management network element, or a multicast / broadcast session management network element in the implementation of the above methods.

[0421] The specific connection medium between the transceiver 1130, the processor 1110 and the memory 1120 is not limited in the embodiment of the present application. Fig.11The memory 1120, the processor 1110 and the transceiver 1130 are connected by a bus. Fig.11 The connections between the other components are shown in bold lines, which are only for illustration and are not intended to be limiting. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig.11 Only one thick line is used to represent it, but it does not mean that there is only one bus or one type of bus. In the embodiment of the present application, the processor can be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, and can implement or execute the methods, steps and logic block diagrams disclosed in the embodiment of the present application. The general-purpose processor can be a microprocessor or any conventional processor, etc. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware processor for execution, or can be executed by a combination of hardware and software modules in the processor.

[0422] In the embodiment of the present application, the memory may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), etc., or a volatile memory (volatile memory), such as a random-access memory (RAM). The memory may also be any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory in the embodiment of the present application may also be a circuit or any other device that can implement a storage function, for storing computer programs, program instructions and / or data.

[0423] Based on the above embodiments, see Fig.12 The embodiment of the present application also provides another communication device 1200, including: an interface circuit 1210 and a logic circuit 1220; the interface circuit 1210 can be understood as an input and output interface, which can be used to execute the sending and receiving steps of each device in any of the above method embodiments, such as the sending step in the above step 203, in which the SMF sends the reference information of the first MBS session to the RAN; the logic circuit 1220 can be used to run codes or instructions to execute the method executed by each device in any of the above embodiments, which will not be repeated.

[0424] Based on the above embodiments, the embodiments of the present application further provide a computer-readable storage medium, which stores instructions. When the instructions are executed, the method executed by each device in any of the above method embodiments is implemented, for example, Figure 5In the embodiment shown, the method executed by CHF or MB-SMF or SMF is implemented. The computer-readable storage medium may include: a USB flash drive, a mobile hard disk, a read-only memory, a random access memory, a magnetic disk or an optical disk, and other media that can store program codes.

[0425] Based on the above embodiments, an embodiment of the present application provides a communication system, which includes the first network element (e.g., CHF), the second network element (e.g., SMF), and the third network element (e.g., MB-SMF) mentioned in any of the above method embodiments, and can be used to execute the method executed by each device in any of the above method embodiments.

[0426] In addition, the above-mentioned communication system may also include a terminal device (such as UE, or a first receiving end), which can execute the relevant method in any of the above-mentioned method embodiments by interacting with the access network device and the session management network element.

[0427] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0428] The present application is described with reference to the flowchart and / or block diagram of the method, device (system), and computer program product according to the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the process and / or box in the flowchart and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one process or multiple processes in the flowchart and / or one box or multiple boxes in the block diagram.

[0429] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0430] These computer program instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

Claims

1. A communication method, characterized in that: include: The first network element receives a first message from the second network element, where the first message includes an identifier of a first multicast / broadcast service MBS and at least one of the following information: a triggering event of the first message, a transmission mode of the first MBS, and a usage report of the first MBS by a terminal joining the first MBS; The first network element updates the charging information of the first MBS according to the first message.

2. The method according to claim 1, characterized in that The triggering event of the first message includes: The terminal joins the session corresponding to the first MBS; The terminal exits the session corresponding to the first MBS; The transmission mode of the first MBS changes.

3. The method according to claim 1 or 2, characterized in that: The transmission method of the first MBS is 5G core network individual multicast / broadcast service traffic transmission method 5GC Individual MBS traffic delivery method or 5G core network shared multicast / broadcast service traffic transmission method 5GC Shared MBS traffic delivery method.

4. The method according to any one of claims 1 to 3, characterized in that: Also includes: The first network element receives a second message from a third network element, where the second message includes at least one of the following information: The charging identifier of the first MBS, the triggering event of the second message, the service type of the first MBS, the quality of service QoS information of the first MBS, the service area of ​​the first MBS, and the usage report of the first MBS.

5. The method according to claim 4, characterized in that The triggering event of the second message includes at least one of the following: activating a session corresponding to the first MBS; Deactivating a session corresponding to the first MBS; A multicast / broadcast user plane function network element is added for transmitting data of the first MBS; Deleting a multicast / broadcast user plane function network element used to transmit data of the first MBS; Adding an access network device for transmitting data of the first MBS; deleting an access network device that transmits data of the first MBS; A user plane function network element is added for transmitting data of the first MBS; Deleting a user plane function network element used to transmit data of the first MBS; The service area of ​​the first MBS changes.

6. The method according to claim 4 or 5, characterized in that: Also includes: The first network element updates the charging information of the first MBS according to the second message.

7. The method according to any one of claims 1 to 6, characterized in that: The usage report includes: a rate group.

8. The method according to any one of claims 1 to 7, characterized in that: Also includes: The first network element sends a quota of the terminal for the first MBS rate group to the second network element.

9. The method according to any one of claims 1 to 8, characterized in that: Also includes: The first network element sends the quota of the rate group of the first MBS to the third network element.

10. The method according to any one of claims 1 to 9, characterized in that: Also includes: The first network element sends a first charging policy to the second network element, where the first charging policy includes a triggering event of the first message.

11. The method according to any one of claims 4 to 9, characterized in that: Also includes: The first network element sends a second charging policy to the third network element, where the second charging policy includes a triggering event of the second message.

12. The method according to any one of claims 1 to 11, characterized in that: The first network element is a charging function network element CHF; the second network element is a session management function network element SMF; the third network element is a multicast broadcast session management function network element MB-SMF; or, the second network element is a first charging trigger function CTF, and the third network element is a second CTF.

13. A communication method, characterized in that: include: The second network element generates a first message, where the first message includes an identifier of the first multicast / broadcast service MBS and at least one of the following information: a triggering event of the first message, a transmission mode of the first MBS, and a usage report of the first MBS by a terminal joining the first MBS; The second network element sends the first message to the first network element.

14. The method according to claim 13, characterized in that The triggering event of the first message includes: The terminal joins the first MBS; The terminal exits the first MBS; The transmission mode of the first MBS changes.

15. The method according to claim 13 or 14, characterized in that The transmission method of the first MBS is 5G core network individual multicast / broadcast service traffic transmission method 5GC Individual MBS traffic delivery method or 5G core network shared multicast / broadcast service traffic transmission method 5GC Shared MBS traffic delivery method.

16. The method according to any one of claims 13 to 15, characterized in that: The usage report includes: a rate group.

17. The method according to claim 16, characterized in that Also includes: The second network element receives a quota of the terminal for the first MBS rate group from the first network element.

18. The method according to any one of claims 13 to 17, characterized in that: The second network element sends a first message to the first network element, and the method further includes: The second network element sends context request information of the first MBS to the third network element; The second network element receives context information of the first MBS from the third network element, where the context information includes identification information of the first network element; The second network element sending a first message to the first network element includes: The second network element sends the first message to the first network element according to the identification information of the first network element.

19. The method according to any one of claims 13 to 18, characterized in that: Also includes: The second network element receives a first charging policy from the first network element, where the first charging policy includes a triggering event of the first message; The second network element determines, according to the first charging policy, a triggering event of the first message for sending the first message.

20. A communication method, characterized in that: include: The third network element generates a second message, where the second message includes at least one of the following information: The charging identifier of the first MBS, the triggering event of the second message, the service type of the first MBS, the quality of service QoS information of the first MBS, the service area of ​​the first MBS, the usage report of the first MBS, and the identifier of the first multicast / broadcast service MBS; The third network element sends the second message to the first network element.

21. The method according to claim 20, characterized in that The triggering event of the second message includes one of the following: activating a session corresponding to the first MBS; Deactivating a session corresponding to the first MBS; A multicast / broadcast user plane function network element is added for transmitting data of the first MBS; Deleting a multicast / broadcast user plane function network element used to transmit data of the first MBS; Adding an access network device for transmitting data of the first MBS; deleting an access network device that transmits data of the first MBS; A user plane function network element is added for transmitting data of the first MBS; Deleting a user plane function network element used to transmit data of the first MBS; The service area of ​​the first MBS changes.

22. The method according to claim 20 or 21, characterized in that The usage report includes: a rate group.

23. The method according to claim 22, characterized in that Also includes: The third network element receives the rate group and / or quota of the first MBS from the first network element.

24. The method according to any one of claims 20 to 23, characterized in that: Also includes: The third network element receives context request information of the first MBS from the second network element; The third network element sends context information of the first MBS to the second network element, where the context information includes an identifier of the first network element.

25. The method according to any one of claims 20 to 24, characterized in that: Also includes: The third network element receives a second charging policy from the first network element, where the second charging policy includes a triggering event of the second message; The third network element determines, according to the second charging policy, a triggering event for sending the second message.

26. A communication device, characterized in that: include: A functional module for implementing the method described in any one of claims 1-12, or any one of claims 13-19, or any one of claims 20-25.

27. A communication device, characterized in that: include: at least one processor and memory; The memory is used to store computer programs or instructions; The at least one processor is configured to execute the computer program or instruction so that the method according to any one of claims 1 to 12, any one of claims 13 to 19, or any one of claims 20 to 25 is performed.

28. A chip system, characterized in that: The chip system comprises: a processing circuit; the processing circuit is coupled to a storage medium; The processing circuit is used to execute part or all of the computer programs or instructions in the storage medium. When the part or all of the computer programs or instructions are executed, it is used to implement the method described in any one of claims 1-12, or any one of 13-19, or any one of 20-25.

29. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores instructions, and when the instructions are executed by a computer, the method according to any one of claims 1 to 12, any one of claims 13 to 19, or any one of claims 20 to 25 is executed.

30. A computer program product comprising a computer program or instructions, characterized in that When it is run on a computer, the method described in any one of claims 1 to 12, 13 to 19, or 20 to 25 is executed.

31. A communication system, characterized in that: include: A first network element, a second network element, and a third network element; The first network element is used to execute the method described in any one of claims 1-12, the second network element is used to execute the method described in any one of claims 13-19, and the third network element is used to execute the method described in any one of claims 20-25.

Citation Information

Cited By

  • Lightweight 5G private network charging method

    CN119172730A

  • Communication method and device

    EP4701240A1

  • Communication method and device

    WO2024230415A1