Charging method and apparatus for satellite communication

Abstract

The embodiments of the present disclosure relate to the technical field of satellite communications, service support and core networks. Disclosed are a charging method and apparatus for satellite communication. The method comprises: a first network element deployed in a first network sending to a second network element deployed in a second network first charging information of a terminal device that uses a satellite service, wherein the first charging information is used for generating a first charging data record (CDR), and the first CDR is used for generating a charging bill. Thus, a second network element deployed in a second network may generate, on the basis of first charging information provided by a first network element deployed in a first network, a first CDR that is used for generating a charging bill, such that the problem of inconsistency between a charging result of the second network and a charging result of the first network is avoided, thereby improving the accuracy of charging results of satellite communication.

Description

Satellite communication billing method and device

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on January 16, 2024, with application number 202410070529.4 and application name “Billing Method and Device for Satellite Communication”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present disclosure relates to the technical fields of satellite communications, business support and core networks, and in particular to a billing method and device for satellite communications. Background Art

[0003] In some remote areas and areas beyond the reach of terrestrial networks, such as deserts, offshore areas far from shore, and in-flight aircraft, users are unable to access terrestrial network services. Satellite communications, with their advantages of all-weather, wide-area coverage, and reliability, can effectively address connectivity issues in remote areas, aviation, oceans, and deserts, where terrestrial networks are unable to address them, providing users with network connectivity services. To provide network connectivity services to users in remote, aviation, ocean, and desert areas, terrestrial operators typically lease satellites from satellite service providers or operators that own satellite networks. However, accurately billing for satellite-based communications has become a pressing issue.

[0004] Summary of the Invention

[0005] The embodiments of the present disclosure provide a billing method and apparatus for satellite communications, which can at least solve the problem of how to accurately bill satellite-based communications in related technologies.

[0006] According to a first aspect of an embodiment of the present disclosure, a billing method for satellite communications is proposed. The method is applied to a first network element deployed in a first network, and the method includes: sending first billing information of a terminal device using satellite services to a second network element deployed in a second network, wherein the first billing information is used to generate a first billing data record CDR, and the first CDR is used to generate a billing bill.

[0007] In some embodiments, the first billing information includes:

[0008] The satellite service indication SSI is used to instruct the terminal device to access the first network via the satellite service.

[0009] In some embodiments, the first billing information further includes at least one of the following information:

[0010] A satellite service type indication, used to indicate whether the satellite service is a backhaul service or a terminal direct connection service;

[0011] a satellite type indication, used to indicate the type of satellite providing the satellite service;

[0012] Satellite service quality;

[0013] Satellite identification and / or constellation identification;

[0014] Operator ID.

[0015] In some embodiments, the method further includes: determining that the terminal device accesses the first network via the satellite service.

[0016] In some embodiments, the first network is a terrestrial network and the second network is a satellite network.

[0017] In some embodiments, the method further includes: sending first information to be updated to the second network element, wherein the first information to be updated is used to update the first CDR.

[0018] In some embodiments, the first information to be updated is sent when an update trigger condition is met, wherein the update trigger condition includes at least one of the following conditions: a change in billing conditions, wherein the billing conditions include at least one of the type of satellite providing the satellite service, satellite service quality, and satellite identification; reaching a rate group limit; reaching a quota limit.

[0019] In some embodiments, the method further includes: sending a first charging termination indication to the second network element, wherein the first charging termination indication is used to close the first CDR.

[0020] In some embodiments, the first billing termination indication is carried in a first billing termination request message sent by the first network element to the second network element, and the first billing termination request message also carries second billing information of the terminal device, and the second billing information is used to update the first CDR.

[0021] In some embodiments, the method further includes: sending third billing information of the terminal device using satellite service to a third network element deployed in the first network, wherein the third billing information is used to generate a second CDR, and the second CDR is used to generate a billing bill.

[0022] In some embodiments, the third billing information includes first information to be negotiated, and the first information to be negotiated is carried in a second billing request message sent by the first network element to the third network element. The second billing request message is sent after the first network element receives the first billing response message sent by the second network element. The first billing response message carries the first information to be negotiated, and the first billing response message is sent by the second network element in response to generating the first CDR.

[0023] In some embodiments, the first billing information includes second information to be negotiated, and the second information to be negotiated is carried in a first billing request message sent by the first network element to the second network element. The first billing request message is sent after the first network element receives a second billing response message sent by the third network element. The second billing response message carries the second information to be negotiated, and the second billing response message is sent by the third network element in response to generating the second CDR.

[0024] In some embodiments, the first network element is a session management function (SMF) network element, and the second network element and the third network element are charging function (CHF) network elements respectively.

[0025] In some embodiments, the second network element and / or the third network element is determined by the SMF network element based on at least one of the following information: a CHF address provided by a policy control function PCF for the data connection session of the terminal device, at least one of a CHF instance identifier and / or a CHF set identifier associated with the data connection session; billing feature information provided by a unified data management function UDM; a CHF instance discovered by a network storage function NRF; and billing feature information provided locally by the SMF.

[0026] In some embodiments, the method further includes: sending second information to be updated to the third network element, wherein the second information to be updated is used to update the second CDR; sending the second information to be updated to the second network element, wherein the second information to be updated is used to update the first CDR.

[0027] In some embodiments, the method further includes: sending a second billing termination indication to the second network element, wherein the second billing termination indication is used to close the first CDR; and sending a third billing termination indication to the third network element, wherein the third billing termination indication is used to close the second CDR.

[0028] In some embodiments, the second billing termination indication is carried in a second billing termination request message sent by the first network element to the second network element, and the second billing termination request message also carries fourth billing information of the terminal device, and the fourth billing information is used to update the first CDR; the third billing termination indication is carried in a third billing termination request message sent by the first network element to the third network element, and the third billing termination request message also carries fifth billing information of the terminal device, and the fifth billing information is used to update the second CDR.

[0029] According to a second aspect of an embodiment of the present disclosure, a billing method for satellite communications is proposed, which is applied to a second network element deployed in a second network. The method includes: receiving first billing information sent by a first network element deployed in a first network, wherein the first billing information includes billing information of a terminal device using satellite services; based on the first billing information, generating a first billing data record CDR, wherein the first CDR is used to generate a billing bill.

[0030] In some embodiments, the first billing information includes:

[0031] The satellite service indication SSI is used to instruct the terminal device to access the first network via the satellite service.

[0032] In some embodiments, the first billing information further includes at least one of the following information:

[0033] A satellite service type indication, used to indicate whether the satellite service is a backhaul service or a terminal direct connection service;

[0034] a satellite type indication, used to indicate the type of satellite providing the satellite service;

[0035] Satellite service quality;

[0036] Satellite identification and / or constellation identification;

[0037] Operator ID.

[0038] In some embodiments, the first billing information is sent when it is determined that the terminal device accesses the first network via the satellite service.

[0039] In some embodiments, the first network is a terrestrial network and the second network is a satellite network.

[0040] In some embodiments, the method further includes: receiving information to be updated sent by the first network element; and updating the first CDR based on the information to be updated.

[0041] In some embodiments, the information to be updated is sent when an update trigger condition is met, wherein the update trigger condition includes at least one of the following conditions: a change in billing conditions, wherein the billing conditions include at least one of the type of satellite providing the satellite service, the satellite service quality, and the satellite identification; reaching a rate group limit; reaching a quota limit.

[0042] In some embodiments, the method further includes: receiving a charging termination indication sent by the first network element; and closing the first CDR based on the charging termination indication.

[0043] In some embodiments, the billing termination indication is carried in a first billing termination request message sent by the first network element to the second network element, and the first billing termination request message also carries second billing information of the terminal device, and the second billing information is used to update the first CDR.

[0044] According to a third aspect of an embodiment of the present disclosure, a billing device for satellite communication is proposed, which is applied to a first network element deployed in a first network, and the device includes: a transceiver module, which is used to send first billing information of a terminal device using satellite services to a second network element deployed in a second network, wherein the first billing information is used to generate a first billing data record CDR, and the first CDR is used to generate a billing bill.

[0045] According to a fourth aspect of an embodiment of the present disclosure, a billing device for satellite communication is proposed, which is applied to a second network element deployed in a second network, and the device includes: a transceiver module for receiving first billing information sent by a first network element deployed in a first network, wherein the first billing information includes billing information of a terminal device using satellite services; and a processing module for generating a first billing data record CDR based on the first billing information, wherein the first CDR is used to generate a billing bill.

[0046] According to the fifth aspect of an embodiment of the present disclosure, an electronic device is proposed, comprising: one or more processors; one or more memories for storing instructions; wherein the processor is used to call the instructions so that the electronic device executes the billing method for satellite communication as described in the first aspect or the optional implementation of the first aspect, or executes the billing method for satellite communication as described in the second aspect or the optional implementation of the second aspect.

[0047] According to the sixth aspect of an embodiment of the present disclosure, a billing system for satellite communication is proposed, comprising a first network element deployed in a first network and a second network element deployed in a second network; wherein, the first network element is configured to implement the billing method for satellite communication described in the first aspect or the optional implementation manner of the first aspect, and the second network element is configured to implement the billing method for satellite communication described in the second aspect or the optional implementation manner of the second aspect.

[0048] In some embodiments, the system also includes a third network element deployed in the first network; the third network element is used to: receive third billing information of a terminal device using satellite services sent by the first network element; generate a second CDR based on the third billing information, and the second CDR is used to generate a billing bill.

[0049] In some embodiments, the third network element is further used to: receive second information to be updated sent by the first network element; and update the second CDR based on the second information to be updated.

[0050] In some embodiments, the third network element is further configured to: receive a charging termination indication sent by the first network element; and close the second CDR based on the charging termination indication.

[0051] According to the seventh aspect of the embodiment of the present disclosure, a storage medium is proposed, which stores instructions. When the instructions are run on an electronic device, the electronic device executes the method described in the first aspect or the second aspect, the optional implementation of the first aspect or the optional implementation of the second aspect.

[0052] According to an eighth aspect of an embodiment of the present disclosure, a program product is proposed. When the program product is executed by an electronic device, the electronic device executes the method described in the first aspect or the second aspect, the optional implementation of the first aspect, or the optional implementation of the second aspect.

[0053] According to the ninth aspect of the embodiments of the present disclosure, a computer program is proposed, which, when running on a computer, enables the computer to execute the method described in the first aspect or the second aspect, the optional implementation of the first aspect, or the optional implementation of the second aspect.

[0054] According to the solution proposed in the embodiment of the present disclosure, a first network element deployed in a first network sends first billing information of a terminal device using satellite services to a second network element deployed in a second network, wherein the first billing information is used to generate a first billing data record CDR, and the first CDR is used to generate a billing invoice. As a result, the second network element deployed in the second network can generate a first CDR for generating a billing invoice based on the first billing information provided by the first network element deployed in the first network, thereby avoiding the problem of inconsistent billing results between the second network and the first network, and improving the accuracy of the billing results of satellite communications. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure or the background technology, the drawings required for use in the embodiments of the present disclosure or the background technology will be described below.

[0056] FIG1 is a schematic diagram of the architecture of a satellite communication billing system according to an embodiment of the present disclosure;

[0057] FIG2 is another schematic diagram of the architecture of a satellite communication billing system according to an embodiment of the present disclosure;

[0058] FIG3 is an interactive diagram illustrating a satellite communication charging method according to an embodiment of the present disclosure;

[0059] FIG4 is an interactive diagram illustrating a satellite communication charging method according to an embodiment of the present disclosure;

[0060] FIG5 is an interactive diagram illustrating a satellite communication billing method according to an embodiment of the present disclosure;

[0061] FIG6 is an interactive diagram illustrating a satellite communication charging method according to an embodiment of the present disclosure;

[0062] FIG7 is an interactive diagram illustrating a satellite communication charging method according to an embodiment of the present disclosure;

[0063] FIG8 is an interactive diagram illustrating a satellite communication charging method according to an embodiment of the present disclosure;

[0064] FIG9 is an interactive diagram illustrating a satellite communication billing method according to an embodiment of the present disclosure;

[0065] FIG10 is an interactive diagram illustrating a satellite communication charging method according to an embodiment of the present disclosure;

[0066] FIG11 is a flow chart of a satellite communication billing method according to an embodiment of the present disclosure;

[0067] FIG12 is a flow chart of a satellite communication billing method according to an embodiment of the present disclosure;

[0068] FIG13 is a flow chart of a satellite communication billing method according to an embodiment of the present disclosure;

[0069] FIG14 is a flow chart of a satellite communication billing method according to an embodiment of the present disclosure;

[0070] FIG15 is a flow chart of a satellite communication billing method according to an embodiment of the present disclosure;

[0071] FIG16 is a flow chart of a satellite communication billing method according to an embodiment of the present disclosure;

[0072] FIG17 is a flow chart of a satellite communication billing method according to an embodiment of the present disclosure;

[0073] FIG18 is a flow chart of a satellite communication billing method according to an embodiment of the present disclosure;

[0074] FIG19 is a flow chart of a satellite communication billing method according to an embodiment of the present disclosure;

[0075] FIG20 is a flow chart of a satellite communication billing method according to an embodiment of the present disclosure;

[0076] FIG21 is a schematic diagram of the structure of a satellite communication billing device according to an embodiment of the present disclosure;

[0077] FIG22 is a schematic diagram of the structure of a satellite communication billing device according to an embodiment of the present disclosure;

[0078] FIG23 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure;

[0079] FIG24 is a schematic diagram of the structure of the chip proposed in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0080] In some remote areas and areas beyond the reach of terrestrial networks, such as deserts, offshore areas far from shore, and in-flight aircraft, users cannot access terrestrial network services. Satellite communications, with their advantages of all-weather, wide-area coverage, and reliability, can effectively address connectivity issues in remote areas, aviation, oceanic areas, and deserts, where terrestrial networks cannot, providing users with network connectivity services. By deploying independent base stations in areas beyond terrestrial network coverage and using satellites to provide data backhaul links between the base stations and core network elements, network connectivity services can be provided to users. However, due to the high cost of building satellite networks, most terrestrial operators do not have their own satellite networks. To provide network connectivity services to users in remote areas, aviation, oceanic areas, and deserts, they must lease satellites from satellite service providers or satellite network operators that own satellite networks. Therefore, satellite service providers or satellite network operators must generate bills based on user traffic and other information from terrestrial operators and bill the terrestrial operators. At the same time, due to the different types of satellites, the service quality of the return link provided is also different. Satellite service providers or satellite network operators will also generate different bills based on different satellite types to differentiate billing. For example, high-orbit satellites are nearly 36,000 kilometers above the ground, with long service times for single satellites and longer return link delays. Low-orbit satellites are 500 kilometers above the ground, with short service times for single satellites and shorter return link delays.

[0081] For example, satellite service providers typically use their own satellite networks to identify and count traffic usage by terrestrial operators, then generate bills. Terrestrial operators, in turn, use their own core network to count user traffic and compare the data to the satellite service provider's bills to pay for satellite rentals. This billing model can lead to discrepancies between the total data transmission volume reported by the satellite service provider and that reported by the terrestrial operator due to differences in network elements and data packet formats, resulting in inaccurate billing results for the satellite service provider. Accurate billing for satellite-based communications has become a pressing issue.

[0082] In response to the above problems, the embodiments of the present disclosure provide a satellite communication billing method, a satellite communication billing device, an electronic device, a satellite communication billing system, a storage medium, a program product, and a computer program.

[0083] In order to better understand the satellite communication billing method disclosed in the embodiment of the present disclosure, the satellite communication billing system applicable to the embodiment of the present disclosure is first described below.

[0084] FIG1 is a schematic diagram of the architecture of a satellite communication billing system according to an embodiment of the present disclosure.

[0085] As shown in FIG1 , the satellite communication billing system 100 may include, but is not limited to, a first network element 101 deployed in a first network and a second network element 102 deployed in a second network.

[0086] In some embodiments, the first network, which is a communication network provided by a mobile network operator (MNO), can be referred to as a terrestrial network. The second network, which is a communication network provided by a satellite service provider (SSP) or a satellite network operator (SNO), can be referred to as a satellite network. It should be noted that when an SSP has its own core network system and can independently operate satellite network services, the SSP is also an SNO; when an SNO leases satellite resources to an MNO and provides satellite services to the MNO, the SNO is also an SSP.

[0087] In some embodiments, the first network element 101 is, for example, a session management function (SMF) network element or other network element with a charging trigger function, and the present disclosure does not limit this.

[0088] In some embodiments, the second network element 102 is, for example, a charging function (CHF) network element or other network element capable of implementing charging, which is not limited in the present disclosure.

[0089] In some embodiments, referring to FIG. 2 , the satellite communication charging system 100 may further include a third network element 103 deployed in the first network.

[0090] In some embodiments, the third network element 103 is, for example, a CHF network element or other network element capable of implementing billing, which is not limited in the present disclosure.

[0091] It can be understood that the satellite communication billing system 100 described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. A person skilled in the art can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0092] The following embodiments of the present disclosure can be applied to the satellite communication billing system shown in Figure 1 or Figure 2 or some of the entities therein, but are not limited thereto. The entities shown in Figures 1 and 2 are examples. The satellite communication billing system may include all or part of the entities shown in Figures 1 or 2, or may include other entities other than those shown in Figures 1 or 2. The number and form of each entity are arbitrary, and each entity can be physical or virtual. The connection relationship between the entities is an example, and the entities can be connected or disconnected. The connection can be in any manner, either directly or indirectly, and can be wired or wireless.

[0093] The embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), future radio access (FRA), new radio access technology (RAT), new radio (NR), new radio access (NX), future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (Ultra Mobile Broadband), and other technologies. Broadband (UMB), IEEE802.11 (Wi-Fi (registered trademark)), IEEE802.16 (WiMAX (registered trademark)), IEEE802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) network, Device-to-Device (D2D) system, Machine-to-Machine (M2M) system, Internet of Things (IoT) system, Vehicle-to-Everything (V2X), systems using other communication methods, and next-generation systems based on them. In addition, multiple systems can also be combined (for example, a combination of LTE or LTE-A with 5G, etc.) for application.

[0094] The following describes a satellite communication billing method of the satellite communication billing system 100 proposed in an embodiment of the present disclosure.

[0095] Figure 3 is an interactive diagram of a satellite communication billing method according to an embodiment of the present disclosure. As shown in Figure 3, the method according to the embodiment of the present disclosure is applied to the satellite communication billing system 100 shown in Figure 1 or Figure 2, and includes the following steps 301-303.

[0096] Step 301: The first network element 101 sends first billing information of a terminal device using satellite service to the second network element 102.

[0097] In some embodiments, the first network element 101 may receive a data connection session establishment request sent by a terminal device, and in response to the establishment request, determine whether the terminal device accesses the first network via a satellite service. If it is determined that the terminal device accesses the first network via a satellite service, it is determined that the terminal device uses the satellite service, and then sends first billing information of the terminal device to the second network element 102. The data connection session establishment request is used to request establishment of a data connection session for the terminal device.

[0098] In some embodiments, the first network element 101 may send a first charging request message to the second network element 102, wherein the first charging request message carries first charging information of a terminal device using satellite services. The first charging request message is used to request the second network element 102 to generate a CDR.

[0099] In some embodiments, the first network element 101 can receive a request to establish a data connection session sent by a terminal device, and in response to the establishment request, determine whether the terminal device accesses the first network via satellite service. If it is determined that the terminal device accesses the first network via satellite service, it is determined that the terminal device uses satellite service, and then sends the above-mentioned first billing request message to the second network element 102 to request the second network element 102 to start establishing a CDR to bill for this data connection session.

[0100] In some embodiments, the data connection session can be a protocol data unit session (PDU session) defined in the 3GPP standard specification, or can be other forms of sessions, which are not limited in the embodiments of the present disclosure. The embodiments of the present disclosure are described using the data connection session as a PDU session as an example.

[0101] In some embodiments, when the first network element is an SMF network element, the satellite service used by the terminal device can be determined as a backhaul service in the following manner: the access and mobility management function (AMF) network element determines, based on configuration, that the terminal device is using a satellite backhaul service to access the base station, determines the type of the satellite service as a satellite backhaul service, and sends the type of the satellite backhaul service to the first network element. The backhaul service refers to a connection provided by a satellite between the base station and the core network, i.e., the terminal device is connected to the core network via the base station and the satellite in sequence.

[0102] In some embodiments, the satellite service used by the terminal device can be determined as a terminal direct connection service in the following manner: specify the radio access technology (RAT) "NR(LEO)", "NR(MEO)", "NR(GEO)" and "NR(OTHERSAT)" to distinguish different New Radio (NR) satellite access types, and the AMF determines the RAT type based on the indication provided in the N2 interface. Among them, NR(LEO) means New Radio (Low Earth Orbit), NR(MEO) means New Radio (Medium Earth Orbit), NR(GEO) means New Radio (Geostationary Orbit), and NR(OTHERSAT) means New Radio (Other Satellites). Among them, the terminal direct connection service refers to the terminal device being connected to the core network through the satellite and the gateway station in sequence.

[0103] The first billing information is billing information used to generate a charging data record (CDR), where the billing information is information related to satellite billing. The CDR is the raw data used to generate the billing invoice. The present embodiment does not limit the name of the first billing information, and may be, for example, "billing-related information," "information used for billing," or the like.

[0104] In some embodiments, the first billing information may include a satellite service indication (SSI), where the SSI indicates that the terminal device accesses the first network via a satellite service. In some embodiments, if the first billing information does not include the SSI, the terminal device is instructed to access the first network via a non-satellite service. The non-satellite service may be, for example, a terrestrial operator network service.

[0105] It is understandable that satellite services may include the following types: backhaul services and terminal direct connection services, and different satellite service types may correspond to different billing rules. In some embodiments, the SSI may further indicate the type of satellite service, such as the SSI includes a satellite service type indication, which is used to indicate that the satellite service is a backhaul service or a terminal direct connection service. For example, when the first billing information includes the SSI, and the value of the satellite service type indication included in the SSI is "0", it can be indicated that the terminal device accesses the first network via the satellite service, and the satellite service is a backhaul service; when the first billing information includes the SSI, and the value of the satellite service type indication included in the SSI is "1", it can be indicated that the terminal device accesses the first network via the satellite service, and the satellite service is a terminal direct connection service. Alternatively, when the first billing information includes SSI and the value of the satellite service type indication included in the SSI is "1", the terminal device can be instructed to access the first network via satellite service, and the satellite service is a backhaul service; when the first billing information includes SSI and the value of the satellite service type indication included in the SSI is "0", the terminal device can be instructed to access the first network via satellite service, and the satellite service is a terminal direct connection service.

[0106] It is understandable that the billing rules may be different depending on the type of satellite providing satellite services. In some embodiments, the SSI may include a satellite type indication to indicate the type of satellite providing satellite services. The type of satellite providing satellite services may include medium-orbit satellites, low-orbit satellites, high-orbit satellites, or other satellite types. For example, when the first billing information includes SSI, and the value of the satellite type indication included in the SSI is "0", it can be indicated that the terminal device accesses the first network via satellite services, and the type of satellite providing satellite services is a low-orbit satellite type; when the first billing information includes SSI, and the value of the satellite type indication included in the SSI is "1", it can be indicated that the terminal device accesses the first network via satellite services, and the type of satellite providing satellite services is a high-orbit satellite type.

[0107] In some embodiments, the SSI may include a satellite service type indication and a satellite type indication. For example, when the first billing information includes an SSI, and the value of the satellite service type indication included in the SSI is "0" and the value of the satellite type indication is "0", the terminal device may be instructed to access the first network via a satellite service, and the satellite service is a terminal direct connection service, and the type of satellite providing the terminal direct connection service is a low-orbit satellite type; when the first billing information includes an SSI, and the value of the satellite service type indication included in the SSI is "0" and the value of the satellite type indication is "1", the terminal device may be instructed to access the first network via a satellite service, and the satellite service is a terminal direct connection service, and the type of satellite providing the terminal direct connection service is a low-orbit satellite type. High-orbit satellite type; when the first billing information includes SSI, and the value of the satellite service type indication included in the SSI is "1" and the value of the satellite type indication is "0", the terminal device can be instructed to access the first network through satellite service, and the satellite service is a backhaul service, and the type of satellite providing the backhaul service is a low-orbit satellite type; when the first billing information includes SSI, and the value of the satellite service type indication included in the SSI is "1" and the value of the satellite type indication is "1", the terminal device can be instructed to access the first network through satellite service, and the satellite service is a backhaul service, and the type of satellite providing the backhaul service is a high-orbit satellite type.

[0108] In some embodiments, the satellite service type indication and the satellite type indication may be different indications from the satellite service indication SSI. That is, in addition to the SSI, the first billing information may also include at least one of the satellite service type indication and the satellite type indication. For example, when the first billing information includes the SSI, the satellite service type indication and the satellite type indication, and the value of the SSI is "1", the value of the satellite service type indication is "0", and the value of the satellite type indication is "0", it can be indicated that the terminal device accesses the first network via satellite service, and the satellite service is a terminal direct connection service, and the type of satellite providing the terminal direct connection service is a low-orbit satellite type; when the first billing information includes the SSI, the satellite service type indication and the satellite type indication, and the value of the SSI is "1", the value of the satellite service type indication is "0", and the value of the satellite type indication is "1", it can be indicated that the terminal device accesses the first network via satellite service, and the satellite service is a terminal direct connection service, and the type of satellite providing the terminal direct connection service is a low-orbit satellite type. High-orbit satellite type; when the first billing information includes SSI, satellite service type indication and satellite type indication, and the value of SSI is "1", the value of satellite service type indication is "1" and the value of satellite type indication is "0", the terminal device can be instructed to access the first network via satellite service, and the satellite service is a backhaul service, and the type of satellite providing the backhaul service is a low-orbit satellite type; when the first billing information includes SSI, satellite service type indication and satellite type indication, and the value of SSI is "1", the value of satellite service type indication is "1" and the value of satellite type indication is "1", the terminal device can be instructed to access the first network via satellite service, and the satellite service is a backhaul service, and the type of satellite providing the backhaul service is a high-orbit satellite type.

[0109] In some embodiments, taking the data connection session of the terminal device as a PDU session as an example, the first billing information may include one or more parameters shown in Table 1 below.

[0110] Table 1 First billing information and corresponding description

[0111] In some embodiments, the charging information of the PDU session (PDU Session Charging Information) may include at least one of the parameters shown in Table 2 below.

[0112] Table 2 Parameters and corresponding descriptions of the billing information of the PDU session

[0113] In some embodiments, the FBC information may include usage volume.

[0114] In some embodiments, the QBC information (QBC Information) may include at least one of the parameters shown in Table 3 below.

[0115] Table 3 Parameters included in QBC information and their corresponding descriptions

[0116] In some embodiments, the quota information may include at least one of the parameters shown in Table 4 below.

[0117] Table 4 Quota information includes parameters and corresponding descriptions

[0118] In some embodiments, the information included in the first billing information and the form of each information can be set as needed.

[0119] For example, when the first charging information includes charging information of a terminal device UE1 using a satellite service, since different satellite service types may correspond to different charging rules, and different types of satellites providing satellite services may correspond to different charging rules, the first charging information may include an SSI corresponding to UE1, indicating that UE1 accesses the first network via satellite service, and the SSI may include a satellite service type indication, indicating that the satellite service used by UE1 is a terminal direct connection service, and the SSI may include a satellite type indication, indicating that the type of satellite providing the terminal direct connection service for UE1 is a low-orbit satellite type; since different satellite service qualities may correspond to different charging rules, the first charging information may include a satellite service quality corresponding to UE1, indicating the service quality of the satellite providing the satellite service for UE1; since different satellites providing satellite services may correspond to different charging rules, the first charging information may include a satellite identifier corresponding to UE1, indicating the identifier of the satellite providing the satellite service for UE1; to facilitate charging the operator, the first charging information may include an operator identifier, indicating the identifier of the operator providing the first network; and to uniquely identify the data connection session, the first charging information may include a charging identifier.

[0120] In step 302, the second network element 102 generates a first charging data record CDR based on the first charging information. The first CDR is used to generate a charging bill.

[0121] In some embodiments, the first CDR may include one or more of the first billing information. For example, due to different satellite service types and / or different types of satellites providing satellite services, the corresponding billing rules may be different, then the first billing information may include SSI, and the first CDR may also include SSI; due to different satellite service qualities, the corresponding billing rules may be different, then the first billing information may include satellite service quality, and the first CDR may also include satellite service quality; due to different satellites providing satellite services, the corresponding billing rules may be different, then the first billing information may include satellite identification, and the first CDR may also include satellite identification; in order to facilitate charging the operator, the first billing information may include operator identification, and the first CDR may also include operator identification; in order to uniquely identify the data connection session, the first billing information may include billing identification, and the first CDR may also include billing identification. It should be noted that the rules for generating the first CDR based on the first billing information can be set as needed, and the present disclosure does not limit this.

[0122] Step 303 : The second network element 102 sends a first charging response message to the first network element 101 .

[0123] In some embodiments, in response to generating the first CDR, the second network element 102 may send a first charging response message to the first network element 101. The first charging response message is used to indicate that the second network element 102 has generated the first CDR. Accordingly, step 303 may be performed after step 302.

[0124] In some embodiments, in response to receiving the first charging information, the second network element 102 may send a first charging response message to the first network element 101. The first charging response message is used to indicate that the second network element 102 has received the first charging information. Accordingly, step 303 may be performed after step 302, before step 302, or simultaneously with step 302.

[0125] FIG3 illustrates the example of step 303 being performed after step 302 .

[0126] In some embodiments, the first charging response message may carry one or more of the parameters shown in Table 5 below.

[0127] Table 5 Parameters carried in the first accounting response message and their corresponding descriptions

[0128] In some embodiments, the quota management (Quota Management) parameters may include one or more of the parameters shown in Table 6 below.

[0129] Table 6 Quota management parameters include parameters and corresponding descriptions

[0130] In some embodiments, the charging configuration parameters may include one or more parameters shown in the following Table 7. The parameters shown in Table 7 are also applicable to the charging configuration parameters shown in Table 2.

[0131] Table 7 Billing configuration parameters include parameters and corresponding descriptions

[0132] It should be noted that, taking the billing configuration parameter as an example, when both the first billing request message and the first billing response message carry the billing configuration parameter, the value of the billing configuration parameter carried in the first billing request message and the first billing response message may be the same or different.

[0133] In some embodiments, step 303 is optional and may be omitted or replaced in different embodiments.

[0134] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 3 .

[0135] In a satellite communications billing method provided by an embodiment of the present disclosure, a first network element deployed in a first network can send first billing information of a terminal device using satellite services to a second network element deployed in a second network. The first billing information is used to generate a first charging data record (CDR), which is used to generate a billing invoice. As a result, the second network element deployed in the second network can generate a first CDR for generating a billing invoice based on the first billing information provided by the first network element deployed in the first network. This avoids the problem of inconsistent billing results between the second network and the first network, and improves the accuracy of satellite communications billing results.

[0136] Figure 4 is an interactive diagram of a satellite communication billing method according to an embodiment of the present disclosure. As shown in Figure 4, the method according to an embodiment of the present disclosure is applied to the satellite communication billing system 100 shown in Figure 1 or Figure 2, and includes the following steps 401-406.

[0137] Step 401: The first network element 101 sends first billing information of a terminal device using satellite service to the second network element 102.

[0138] The optional implementation of step 401 can refer to the optional implementation of step 301 in Figure 3 and other related parts in the embodiment involved in Figure 3, which will not be repeated here.

[0139] In step 402, the second network element 102 generates a first charging data record CDR based on the first charging information. The first CDR is used to generate a charging bill.

[0140] The optional implementation of step 402 can refer to the optional implementation of step 302 in FIG. 3 and other related parts in the embodiment involved in FIG. 3 , which will not be described in detail here.

[0141] Step 403 : The second network element 102 sends a first charging response message to the first network element 101 .

[0142] The optional implementation of step 403 can refer to the optional implementation of step 303 in Figure 3 and other related parts in the embodiment involved in Figure 3, which will not be repeated here.

[0143] Step 404 : The first network element 101 sends first information to be updated to the second network element 102 .

[0144] The first information to be updated is information that needs to be updated and is used to update the first CDR.

[0145] In some embodiments, the first network element 101 may send a first charging update request message to the second network element 102 , wherein the first charging update request message carries first information to be updated.

[0146] The first billing update request message is used to request an update of a generated CDR.

[0147] In some embodiments, the first information to be updated may include billing configuration parameters.

[0148] In some embodiments, the first information to be updated may include QBC information and / or FBC information. Optionally, the QBC information may include quota information, and / or the FBC information may include quota information. The quota information may include quota application information for applying for quota and / or quota usage information for notifying the used quota.

[0149] In some embodiments, the first to-be-updated information may be sent when an update triggering condition is satisfied, wherein the update triggering condition includes at least one of the following conditions:

[0150] a change in charging conditions, wherein the charging conditions include at least one of the type of satellite providing satellite services, satellite service quality, and satellite identification;

[0151] The rate group limit is reached;

[0152] The quota limit was reached.

[0153] In some embodiments, in response to a change in charging conditions, the first network element 101 sends first to-be-updated information to the second network element 102 , which is applicable to converged charging scenarios and offline charging scenarios.

[0154] In some embodiments, the limit per rating group (Limit per Rating Group) may include at least one of the following: expiry of data time limit per RG, expiry of data volume limit per RG, and expiry of data event limit per RG. In some embodiments, in response to reaching a limit of a rating group, the first network element 101 sends to-be-updated information to the second network element 102, which is applicable to converged billing scenarios and offline billing scenarios.

[0155] In some embodiments, reaching a quota limit triggers a quota management trigger. Optionally, the triggering of a quota management trigger may include at least one of the following: time threshold reached, volume threshold reached, unit threshold reached, time quota exhausted, volume quota exhausted, unit quota exhausted, expiry of quota validity time, or re-authorization request from the CHF. In some embodiments, in response to reaching the quota limit, the first network element 101 sends first to-be-updated information to the second network element 102, which is applicable to converged billing scenarios.

[0156] In some embodiments, when the update trigger condition includes a change in billing conditions, the first information to be updated may include information related to the changed billing conditions. For example, when the update trigger condition is a change in satellite identification, the first information to be updated may include the satellite identification of the latest satellite providing satellite services.

[0157] In some embodiments, when the update triggering condition includes reaching a limit of a rate group, the first to-be-updated information may include information related to the reached limit of the rate group.

[0158] In some embodiments, when the update triggering condition includes reaching a quota limit, the first to-be-updated information may include information related to the reached quota limit.

[0159] Step 405: The second network element 102 updates the first CDR based on the first information to be updated.

[0160] Step 406 : The second network element 102 sends a first charging update response message to the first network element 101 .

[0161] In some embodiments, in response to updating the first CDR, the second network element 102 may send a first billing update response message to the first network element 101. The first billing update response message is used to indicate that the first CDR has been updated. Accordingly, step 406 may be performed after step 405.

[0162] In some embodiments, in response to receiving the first information to be updated, the second network element 102 may send a first billing update response message to the first network element 101. The first billing update response message is used to indicate that the second network element 102 has received the first information to be updated. Accordingly, step 406 may be performed after step 405, before step 405, or simultaneously with step 405.

[0163] FIG. 4 illustrates an example in which step 406 is performed after step 405 .

[0164] In some embodiments, step 403 is optional and may be omitted or replaced in different embodiments.

[0165] In some embodiments, step 406 is optional and may be omitted or replaced in different embodiments.

[0166] In the satellite communications billing method provided by the embodiments of the present disclosure, a second network element deployed in a second network can generate a first CDR for generating a bill based on first billing information provided by a first network element deployed in a first network. This avoids inconsistent billing results between the second network and the first network, and improves the accuracy of satellite communications billing results. Furthermore, the second network element can promptly update the first CDR based on first to-be-updated information sent by the first network element, thereby ensuring the timeliness of the billing results generated by the second network element.

[0167] Figure 5 is an interactive diagram of a satellite communication billing method according to an embodiment of the present disclosure. As shown in Figure 5, the method according to the embodiment of the present disclosure is applied to the satellite communication billing system 100 shown in Figure 1 or Figure 2, and includes the following steps 501-506.

[0168] Step 501: The first network element 101 sends first billing information of a terminal device using satellite service to the second network element 102.

[0169] The optional implementation of step 501 can refer to the optional implementation of step 301 in Figure 3 and other related parts in the embodiment involved in Figure 3, which will not be repeated here.

[0170] In step 502, the second network element 102 generates a first charging data record CDR based on the first charging information. The first CDR is used to generate a charging bill.

[0171] The optional implementation of step 502 can refer to the optional implementation of step 302 in Figure 3 and other related parts in the embodiment involved in Figure 3, which will not be repeated here.

[0172] Step 503 : The second network element 102 sends a first charging response message to the first network element 101 .

[0173] The optional implementation of step 503 can refer to the optional implementation of step 303 in Figure 3 and other related parts in the embodiment involved in Figure 3, which will not be repeated here.

[0174] Step 504 : The first network element 101 sends a first charging termination indication to the second network element 102 .

[0175] The first billing termination indication is used to close the first CDR.

[0176] In some embodiments, the first network element 101 may send a first charging termination request message to the second network element 102 , wherein the message carries a first charging termination indication.

[0177] In some embodiments, the first network element 101 may send a first billing termination indication or a first billing termination request message carrying the first billing termination indication to the second network element 102 in response to detecting that the established data connection session of the terminal device is released.

[0178] In some embodiments, the first billing termination request message may also carry the second billing information of the terminal device using the satellite service. The second billing information is used to update the first CDR. The second billing information may be the billing information of the terminal device generated when the data connection session of the terminal device is released. The information included in the second billing information can be set as needed, and the details can be referred to the first billing information, which will not be repeated here. The embodiment of the present application does not limit the name of the second billing information, which may be, for example, "billing-related information", "information used for billing", etc.

[0179] In some embodiments, the first charging termination request message may further carry a usage report (Usage Report), wherein the usage report includes detailed information on the usage of data traffic and may be used to update the first CDR.

[0180] Step 505: The second network element 102 closes the first CDR based on the first charging termination instruction.

[0181] Step 506 : The second network element 102 sends a first charging termination response message to the first network element 101 .

[0182] In some embodiments, in response to closing the first CDR, the second network element 102 may send a first billing termination response message to the first network element 101. The first billing termination response message is used to indicate that the previously generated first CDR has been closed. Accordingly, step 506 may be performed after step 505.

[0183] In some embodiments, in response to receiving the first billing termination indication, the second network element 102 may send a first billing termination response message to the first network element 101. The first billing termination response message is used to indicate that the second network element 102 has received the first billing termination indication. Accordingly, step 506 may be performed after step 505, before step 505, or simultaneously with step 505.

[0184] FIG. 5 illustrates an example in which step 506 is performed after step 505 .

[0185] In some embodiments, step 503 is optional and may be omitted or replaced in different embodiments.

[0186] In some embodiments, step 506 is optional and may be omitted or replaced in different embodiments.

[0187] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 5 .

[0188] In the satellite communications billing method provided by the embodiments of the present disclosure, a second network element deployed in a second network can generate a first CDR for generating a bill based on first billing information provided by a first network element deployed in a first network. This avoids inconsistent billing results between the second network and the first network, and improves the accuracy of satellite communications billing results. Furthermore, the second network element can promptly close the first CDR based on a first billing termination instruction sent by the first network element, thereby ensuring that the second network element stops billing in a timely manner.

[0189] Figure 6 is an interactive diagram of a satellite communication billing method according to an embodiment of the present disclosure. As shown in Figure 6, the method according to the embodiment of the present disclosure is applied to the satellite communication billing system 100 shown in Figure 2, and includes the following steps 601-606.

[0190] Step 601: The first network element 101 sends first billing information of a terminal device using satellite service to the second network element 102.

[0191] The optional implementation of step 601 can refer to the optional implementation of step 301 in Figure 3 and other related parts in the embodiment involved in Figure 3, which will not be repeated here.

[0192] In step 602, the second network element 102 generates a first charging data record CDR based on the first charging information. The first CDR is used to generate a charging bill.

[0193] The optional implementation of step 602 can refer to the optional implementation of step 302 in Figure 3 and other related parts in the embodiment involved in Figure 3, which will not be repeated here.

[0194] Step 603 : The second network element 102 sends a first charging response message to the first network element 101 .

[0195] The optional implementation of step 603 can refer to the optional implementation of step 303 in Figure 3 and other related parts in the embodiment involved in Figure 3, which will not be repeated here.

[0196] Step 604 : The first network element 101 sends third charging information of the terminal device using the satellite service to the third network element 103 .

[0197] The terminal device using the satellite service in step 604 and the terminal device using the satellite service in step 601 may be the same terminal device.

[0198] The third billing information is billing information used to generate a CDR. The present embodiment does not limit the name of the third billing information, and may be, for example, "billing-related information," "information used for billing," or the like. The information included in the third billing information can be configured as needed. For details, refer to the first billing information and will not be further described here.

[0199] In some embodiments, the first network element 101 can receive a request to establish a data connection session sent by a terminal device, and in response to the establishment request, determine whether the terminal device accesses the first network via satellite service. If it is determined that the terminal device accesses the first network via satellite service, it is determined that the terminal device uses satellite service, and then sends third billing information to the third network element 103.

[0200] In some embodiments, the first network element 101 may send a second charging request message to the third network element 103, wherein the second charging request message carries third charging information. The second charging request message is used to request the third network element 103 to generate a CDR.

[0201] In some embodiments, the first network element 101 can receive a request to establish a data connection session sent by a terminal device, and in response to the establishment request, determine whether the terminal device accesses the first network via satellite service. If it is determined that the terminal device accesses the first network via satellite service, it is determined that the terminal device uses satellite service, and then sends the above-mentioned second billing request message to the third network element 103 to request the third network element 103 to start establishing a CDR to bill for this data connection session.

[0202] In some embodiments, the data connection session may be a PDU session defined in the 3GPP standard, or may be other forms of sessions, which are not limited in the embodiments of the present disclosure. The embodiments of the present disclosure are described by taking the data connection session as a PDU session as an example.

[0203] In some embodiments, when the first billing information includes an operator identifier, since the operator identifier is used to charge the operator and has nothing to do with the billing rules when the operator charges the user to which the terminal device belongs, the third billing information may not include the operator identifier. In order to facilitate the operator to charge the user to which the terminal device belongs, the third billing information may include the user identifier (Subscriber Identifier) ​​of the user to which the terminal device belongs. In addition, the third billing information and the first billing information may include the same information. That is, the first billing information may include the operator identifier but not the user identifier, and the third billing information may include the user identifier but not the operator identifier. In addition, the other information included in the first billing information and the third billing information may be the same.

[0204] Step 605: The third network element 103 generates a second CDR based on the third charging information. The second CDR is used to generate a charging bill.

[0205] In some embodiments, the information included in the third billing information can be set as needed, and the third network element 103 can generate a second CDR based on the third billing information. The second CDR can include one or more of the third billing information. For example, due to different satellite service types and / or different types of satellites providing satellite services, the corresponding billing rules may vary. In this case, the third billing information can include the SSI, and the second CDR can also include the SSI. Due to different satellite service qualities, the corresponding billing rules may vary. In this case, the third billing information can include the satellite service quality, and the second CDR can also include the satellite service quality. Due to different satellites providing satellite services, the corresponding billing rules may vary. In this case, the third billing information can include the satellite identifier, and the second CDR can also include the satellite identifier. To facilitate charging the user to whom the terminal device belongs, the third billing information can include a user identifier, and the second CDR can also include the user identifier. To uniquely identify the second CDR, the third billing information can include a billing identifier, and the second CDR can also include the billing identifier. It should be noted that the rules for generating the second CDR based on the third billing information can be set as needed, and this disclosure does not limit this.

[0206] Step 606 : The third network element 103 sends a second charging response message to the first network element 101 .

[0207] In some embodiments, in response to generating the second CDR, the third network element 103 may send a second charging response message to the first network element 101. The second charging response message is used to indicate that the third network element 103 has generated the second CDR. Accordingly, step 606 may be performed after step 605.

[0208] In some embodiments, in response to receiving the third charging information, the third network element 103 may send a second charging response message to the first network element 101. The second charging response message is used to indicate that the third network element 103 has received the third charging information. Accordingly, step 606 may be performed after step 605, before step 605, or simultaneously with step 605.

[0209] FIG. 6 illustrates an example in which step 606 is performed after step 605 .

[0210] In some embodiments, the second charging response message may carry one or more of the parameters shown in Table 5.

[0211] It should be noted that steps 601-603 may be performed before step 604, or after step 606, or simultaneously with steps 604-606, and this disclosure does not impose any restrictions thereon. In the event that the first billing information and the third billing information do not include information requiring negotiation, steps 601-603 and steps 604-606 may be performed simultaneously.

[0212] In some embodiments, the first network element is an SMF network element, and the second network element and the third network element are CHF network elements respectively.

[0213] In some embodiments, when the first network element is an SMF network element, and the second network element and the third network element are respectively CHF network elements, the SMF network element may determine the second network element and / or the third network element based on at least one of the following information:

[0214] At least one of a CHF address, a CHF instance identifier associated with the data connection session, and / or a CHF set identifier provided by the Policy Control Function (PCF) for the data connection session of the terminal device;

[0215] The Unified Data Management (UDM) function provides billing feature information;

[0216] CHF instances discovered by the Network Repository Function (NRF);

[0217] Billing feature information provided locally by the SMF.

[0218] In some embodiments, when using NRF to discover a CHF instance, if the charging rules of the data connection session of the terminal device indicate that the data connection session is "offline only", NRF can select a CHF instance that supports the CHF "offline only" service instance.

[0219] Among them, the charging rules include "offline only", "online only", and "convergent billing", which indicate whether the service data flow in the data connection session of the terminal device is subject to online billing, offline billing, or converged activation. The charging rules can be pre-configured in the SMF network element, which activates the charging rules for the data connection session of the terminal device. Alternatively, the PCF can issue and activate dynamic charging rules to the SMF, or the PCF can issue and activate specified pre-configured charging rules to the SMF.

[0220] In some embodiments, the information based on which the SMF network element determines the second network element may be the same as or different from the information based on which the SMF network element determines the third network element, and this disclosure does not limit this.

[0221] In some embodiments, the SMF network element may determine the second network element and / or the third network element in response to the data connection session of the terminal device starting to be established. For example, the SMF network element may determine the second network element and / or the third network element during the establishment of the data connection session of the terminal device.

[0222] In some embodiments, step 603 is optional and may be omitted or replaced in different embodiments.

[0223] In some embodiments, step 606 is optional and may be omitted or replaced in different embodiments.

[0224] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 6 .

[0225] The satellite communication billing method provided by the embodiment of the present disclosure enables the second network element to generate a first CDR for generating a billing bill based on the first billing information of the terminal device using the satellite service provided by the first network element, and the third network element to generate a second CDR for generating a billing bill based on the third billing information of the terminal device provided by the first network element. Since the second network element and the third network element perform billing based on the same data source, the problem of inconsistent billing results between the second network and the first network can be avoided, thereby improving the accuracy of the billing results of satellite communications.

[0226] Figure 7 is an interactive diagram of a satellite communication billing method according to an embodiment of the present disclosure. As shown in Figure 7, the method according to the embodiment of the present disclosure is applied to the satellite communication billing system 100 shown in Figure 2, and the method includes the following steps 701-706.

[0227] Step 701: The first network element 101 sends a first charging request message to the second network element 102, wherein the first charging request message carries first charging information of a terminal device using satellite services.

[0228] The optional implementation of step 701 can refer to the optional implementation of step 301 in Figure 3 and other related parts in the embodiment involved in Figure 3, which will not be repeated here.

[0229] In step 702, the second network element 102 generates a first charging data record CDR based on the first charging information. The first CDR is used to generate a charging bill.

[0230] The optional implementation of step 702 can refer to the optional implementation of step 302 in Figure 3 and other related parts in the embodiment involved in Figure 3, which will not be repeated here.

[0231] Step 703: The second network element 102 sends a first charging response message to the first network element 101. The first charging response message carries the first information to be negotiated.

[0232] The optional implementation of step 703 can refer to the optional implementation of step 303 in Figure 3 and other related parts in the embodiment involved in Figure 3, which will not be repeated here.

[0233] In some embodiments, the second network element 102 may send a first charging response message to the first network element 101 in response to generating the first CDR.

[0234] The first information to be negotiated is information that needs to be negotiated between the second network and the first network.

[0235] In some embodiments, the first information to be negotiated may include, for example, a charging profile.

[0236] In some embodiments, the first billing information carried in the first billing request message may include first information to be negotiated. When the second network element 102 determines that the first information to be negotiated is feasible, it may carry the first information to be negotiated in the first billing response message and send it to the first network element 101.

[0237] In step 704, the first network element 101 sends a second charging request message to the third network element 103, wherein the second charging request message carries third charging information of the terminal device using the satellite service, and the third charging information includes the first information to be negotiated.

[0238] The optional implementation of step 704 can refer to the optional implementation of step 604 in Figure 6 and other related parts in the embodiment involved in Figure 6, which will not be repeated here.

[0239] In some embodiments, the first network element 101 may add the first information to be negotiated received from the second network element 102 to the third billing information as part of the third billing information, carry it in the second billing request message, and send it to the third network element 103.

[0240] Step 705: The third network element 103 generates a second CDR based on the third charging information. The second CDR is used to generate a charging bill.

[0241] The optional implementation of step 705 can refer to the optional implementation of step 605 in Figure 6 and other related parts in the embodiment involved in Figure 6, which will not be repeated here.

[0242] Step 706 : The third network element 103 sends a second charging response message to the first network element 101 .

[0243] The optional implementation of step 706 can refer to the optional implementation of step 606 in Figure 6 and other related parts in the embodiment involved in Figure 6, which will not be repeated here.

[0244] In some embodiments, step 706 is optional and may be omitted or replaced in different embodiments.

[0245] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 7 .

[0246] The satellite communications billing method provided by the disclosed embodiments enables a second network element to generate a first CDR for generating a billing invoice based on first billing information of a terminal device using satellite services provided by a first network element, and a third network element to generate a second CDR for generating a billing invoice based on third billing information of the terminal device provided by the first network element. Because the second and third network elements perform billing based on the same data source, inconsistent billing results between the second and first networks can be avoided, thereby improving the accuracy of satellite communications billing results. Furthermore, by having the first network element receive first information to be negotiated from the second network element and carry the first information to be negotiated in a second billing request message, which is then sent to the third network element, information negotiation led by the second network can be achieved.

[0247] Figure 8 is an interactive diagram of a satellite communication billing method according to an embodiment of the present disclosure. As shown in Figure 8, the method according to the embodiment of the present disclosure is applied to the satellite communication billing system 100 shown in Figure 2, and includes the following steps 801-806.

[0248] Step 801: The first network element 101 sends a second charging request message to the third network element 103, wherein the second charging request message carries third charging information of a terminal device using satellite services.

[0249] The optional implementation of step 801 can refer to the optional implementation of step 604 in Figure 6 and other related parts in the embodiment involved in Figure 6, which will not be repeated here.

[0250] In step 802, the third network element 103 generates a second CDR based on the third charging information. The second CDR is used to generate a charging bill.

[0251] The optional implementation of step 802 can refer to the optional implementation of step 605 in Figure 6 and other related parts in the embodiment involved in Figure 6, which will not be repeated here.

[0252] Step 803 : The third network element 103 sends a second charging response message to the first network element 101 , where the second charging response message carries the second information to be negotiated.

[0253] The optional implementation of step 803 can refer to the optional implementation of step 606 in Figure 6 and other related parts in the embodiment involved in Figure 6, which will not be repeated here.

[0254] In some embodiments, the third network element 103 may send a second charging response message to the first network element 101 in response to generating the second CDR.

[0255] The second information to be negotiated is information that needs to be negotiated between the second network and the first network. The first information to be negotiated and the second information to be negotiated may be the same or different, and this disclosure does not impose any limitation on this.

[0256] In some embodiments, the second information to be negotiated may include, for example, a charging profile.

[0257] In some embodiments, the third billing information carried by the second billing request message may include second information to be negotiated. When the third network element 103 determines that the second information to be negotiated is feasible, it may carry the second information to be negotiated in the second billing response message and send it to the first network element 101.

[0258] In step 804, the first network element 101 sends a first charging request message to the second network element 102, wherein the first charging request message carries first charging information of the terminal device using the satellite service, and the first charging information includes the second information to be negotiated.

[0259] The optional implementation of step 804 can refer to the optional implementation of step 301 in FIG. 3 and other related parts in the embodiment involved in FIG. 3 , which will not be described in detail here.

[0260] In some embodiments, the first network element 101 may add the second information to be negotiated received from the third network element 103 to the first billing information as part of the first billing information, carry it in the first billing request message, and send it to the second network element 102.

[0261] In step 805 , the second network element 102 generates a first charging data record CDR based on the first charging information. The first CDR is used to generate a charging bill.

[0262] The optional implementation of step 805 can refer to the optional implementation of step 302 in FIG. 3 and other related parts in the embodiment involved in FIG. 3 , which will not be described in detail here.

[0263] Step 806 : The second network element 102 sends a first charging response message to the first network element 101 .

[0264] The optional implementation of step 806 can refer to the optional implementation of step 303 in FIG. 3 and other related parts in the embodiment involved in FIG. 3 , which will not be described in detail here.

[0265] In some embodiments, step 806 is optional and may be omitted or replaced in different embodiments.

[0266] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 8 .

[0267] The satellite communications billing method provided by the disclosed embodiments enables a second network element to generate a first CDR for generating a billing invoice based on first billing information of a terminal device using satellite services provided by a first network element, and a third network element to generate a second CDR for generating a billing invoice based on third billing information of the terminal device provided by the first network element. Because the second and third network elements perform billing based on the same data source, inconsistent billing results between the second and first networks can be avoided, thereby improving the accuracy of satellite communications billing results. Furthermore, by having the first network element receive second information to be negotiated from the third network element and carry the second information to be negotiated in a first billing request message, which is then sent to the second network element, information negotiation led by the first network can be achieved.

[0268] Figure 9 is a schematic diagram illustrating an interaction of a satellite communications billing method according to an embodiment of the present disclosure. As shown in Figure 9, the method according to an embodiment of the present disclosure is applied to the satellite communications billing system 100 shown in Figure 2. Based on the satellite communications billing method shown in Figures 6, 7, or 8, the method further includes the following steps 901-906.

[0269] Step 901 : The first network element 101 sends second information to be updated to the third network element 103 .

[0270] In some embodiments, the first network element 101 may send a second charging update request message to the third network element 103 , wherein the second charging update request message carries second information to be updated.

[0271] The second billing update request message is used to request an update of the generated CDR.

[0272] The second information to be updated is information that needs to be updated. The second information to be updated may be the same as or different from the first information to be updated, and this disclosure does not impose any limitation on this.

[0273] In some embodiments, the second information to be updated may include billing configuration parameters.

[0274] In some embodiments, the second information to be updated may include QBC information and / or FBC information. Optionally, the QBC information may include quota information, and / or the FBC information may include quota information. The quota information may include quota application information for applying for quota and / or quota usage information for notifying the used quota.

[0275] In some embodiments, the second to-be-updated information may be sent when an update triggering condition is satisfied, wherein the update triggering condition includes at least one of the following conditions:

[0276] a change in charging conditions, wherein the charging conditions include at least one of the type of satellite providing satellite services, satellite service quality, and satellite identification;

[0277] The rate group limit is reached;

[0278] The quota limit was reached.

[0279] For the description of the update triggering conditions, please refer to other embodiments and will not be repeated here.

[0280] In some embodiments, when the update trigger condition includes a change in billing conditions, the second information to be updated may include information related to the changed billing conditions. For example, when the update trigger condition is a change in satellite identification, the second information to be updated may include the satellite identification of the latest satellite providing satellite services.

[0281] In some embodiments, when the update triggering condition includes reaching a limit of a rate group, the second to-be-updated information may include information related to the reached limit of the rate group.

[0282] In some embodiments, when the update triggering condition includes reaching a quota limit, the second to-be-updated information may include information related to the reached quota limit.

[0283] Step 902: The third network element 103 updates the second CDR based on the second information to be updated.

[0284] Step 903 : The third network element 103 sends a second charging update response message to the first network element 101 .

[0285] In some embodiments, in response to updating the second CDR, the third network element 103 may send a second charging update response message to the first network element 101. The second charging update response message is used to indicate that the second CDR has been updated. Accordingly, step 903 may be performed after step 902.

[0286] In some embodiments, in response to receiving the second information to be updated, the third network element 103 may send a second billing update response message to the first network element 101. The second billing update response message is used to indicate that the third network element 103 has received the second information to be updated. Accordingly, step 903 may be performed after step 902, before step 902, or simultaneously with step 902.

[0287] FIG. 9 illustrates an example in which step 903 is performed after step 902 .

[0288] Step 904 : The first network element 101 sends second information to be updated to the second network element 102 .

[0289] In some embodiments, the first network element 101 may send a third charging update request message to the second network element 102 , wherein the third charging update request message carries the second information to be updated.

[0290] The third billing update request message is used to request an update of the generated CDR.

[0291] In some embodiments, the second to-be-updated information may be sent when an update triggering condition is satisfied, wherein the update triggering condition includes at least one of the following conditions:

[0292] a change in charging conditions, wherein the charging conditions include at least one of the type of satellite providing satellite services, satellite service quality, and satellite identification;

[0293] The rate group limit is reached;

[0294] The quota limit was reached.

[0295] For the description of the update triggering conditions, please refer to other embodiments and will not be repeated here.

[0296] Step 905: The second network element 102 updates the first CDR based on the second information to be updated.

[0297] Step 906 : The second network element 102 sends a third charging update response message to the first network element 101 .

[0298] In some embodiments, in response to updating the first CDR, the second network element 102 may send a third charging update response message to the first network element 101. The third charging update response message is used to indicate that the first CDR has been updated. Accordingly, step 906 may be performed after step 905.

[0299] In some embodiments, in response to receiving the second information to be updated, the second network element 102 may send a third billing update response message to the first network element 101. The third billing update response message is used to indicate that the second network element 102 has received the second information to be updated. Accordingly, step 906 may be performed after step 905, before step 905, or simultaneously with step 905.

[0300] FIG. 9 illustrates an example in which step 906 is performed after step 905 .

[0301] It should be noted that steps 901-903 and steps 904-906 can be executed simultaneously, or steps 901-903 can be executed before step 904, or steps 901-903 can be executed after step 904, and the present disclosure does not impose any restrictions on this.

[0302] In some embodiments, step 903 is optional and may be omitted or replaced in different embodiments.

[0303] In some embodiments, step 906 is optional and may be omitted or replaced in different embodiments.

[0304] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 9 .

[0305] The satellite communication billing method provided by the embodiment of the present disclosure sends the second information to be updated to the third network element and the second network element through the first network element. The second network element and the third network element update their respectively generated CDRs according to the second information to be updated sent by the first network element, thereby ensuring the timeliness and consistency of the billing results generated by the second network element and the third network element.

[0306] Figure 10 is a schematic diagram illustrating an interaction of a satellite communications billing method according to an embodiment of the present disclosure. As shown in Figure 10, the method according to an embodiment of the present disclosure is applied to the satellite communications billing system 100 shown in Figure 2. Based on the satellite communications billing method shown in Figures 6, 7, 8, or 9, the method further includes the following steps 1001-1006.

[0307] Step 1001: The first network element 101 sends a second charging termination indication to the second network element 102.

[0308] The second billing termination indication is used to close the first CDR.

[0309] In some embodiments, the first network element 101 may send a second charging termination request message to the second network element 102 , wherein the message carries a second charging termination indication.

[0310] In some embodiments, the first network element 101 may send a second billing termination indication or a second billing termination request message carrying the second billing termination indication to the second network element 102 in response to detecting that the established data connection session of the terminal device is released.

[0311] In some embodiments, the second billing termination request message may also carry the fourth billing information of the terminal device using the satellite service. The fourth billing information is used to update the first CDR. The fourth billing information may be the billing information of the terminal device generated when the data connection session of the terminal device is released. The information included in the fourth billing information can be set as needed, and specific reference may be made to the first billing information, which will not be repeated here. The embodiment of the present application does not limit the name of the fourth billing information, which may be, for example, "billing-related information," "information used for billing," and the like.

[0312] In some embodiments, the second charging termination request message may further carry a usage report, wherein the usage report includes detailed information on the usage of the data traffic and may be used to update the first CDR.

[0313] Step 1002: The second network element 102 closes the first CDR based on the second charging termination indication.

[0314] Step 1003 : The second network element 102 sends a second charging termination response message to the first network element 101 .

[0315] In some embodiments, in response to closing the first CDR, the second network element 102 may send a second billing termination response message to the first network element 101. The second billing termination response message is used to indicate that the previously generated first CDR has been closed. Accordingly, step 1003 may be performed after step 1002.

[0316] In some embodiments, in response to receiving the second billing termination indication, the second network element 102 may send a second billing termination response message to the first network element 101. The second billing termination response message is used to indicate that the second network element 102 has received the second billing termination indication. Accordingly, step 1003 may be performed after step 1002, before step 1002, or simultaneously with step 1002.

[0317] FIG10 illustrates the example of step 1003 being executed after step 1002.

[0318] Step 1004 : The first network element 101 sends a third charging termination indication to the third network element 103 .

[0319] The third billing termination indication is used to close the second CDR.

[0320] In some embodiments, the first network element 101 may send a third charging termination request message to the third network element 103 , wherein the message carries a third charging termination indication.

[0321] In some embodiments, the first network element 101 may send a third billing termination indication or a third billing termination request message carrying the third billing termination indication to the third network element 103 in response to detecting that the established data connection session of the terminal device is released.

[0322] In some embodiments, the third billing termination request message may also carry the fifth billing information of the terminal device using the satellite service. The fifth billing information is used to update the second CDR. The fifth billing information may be the billing information of the terminal device generated when the data connection session of the terminal device is released. The information included in the fifth billing information can be set as needed, and the details may refer to the first billing information, which will not be repeated here. The embodiment of the present application does not limit the name of the fifth billing information, which may be, for example, "billing related information", "information used for billing", etc. In some embodiments, the fifth billing information and the fourth billing information may include the same billing information.

[0323] In some embodiments, the third charging termination request message may further carry a usage report, wherein the usage report includes detailed information on the usage of the data traffic and may be used to update the second CDR.

[0324] Step 1005: The third network element 103 closes the second CDR based on the third charging termination indication.

[0325] Step 1006 : The third network element 103 sends a third charging termination response message to the first network element 101 .

[0326] In some embodiments, in response to closing the second CDR, the third network element 103 may send a third billing termination response message to the first network element 101. The third billing termination response message indicates that the previously generated second CDR has been closed. Accordingly, step 1006 may be performed after step 1005.

[0327] In some embodiments, in response to receiving the third billing termination indication, the third network element 103 may send a third billing termination response message to the first network element 101. The third billing termination response message is used to indicate that the third network element 103 has received the third billing termination indication. Accordingly, step 1006 may be performed after step 1005, before step 1005, or simultaneously with step 1005.

[0328] FIG10 illustrates the example of step 1006 being executed after step 1005.

[0329] In some embodiments, step 1003 is optional and may be omitted or replaced in different embodiments.

[0330] In some embodiments, step 1006 is optional and may be omitted or replaced in different embodiments.

[0331] In some embodiments, reference may be made to other optional implementations recorded before or after the description corresponding to FIG. 10 .

[0332] The satellite communication billing method provided by the embodiment of the present disclosure sends a second billing termination indication to the second network element through the first network element, and sends a third billing termination indication to the third network element, so that the second network element and the third network element can promptly close their respective generated CDRs according to the billing termination indications respectively received, thereby ensuring that the second network element and the third network element stop billing in a timely manner to ensure the consistency of the billing results generated by the second network element and the third network element.

[0333] FIG11 is a flow chart of a satellite communication billing method according to an embodiment of the present disclosure. As shown in FIG11 , the method according to an embodiment of the present disclosure is applied to a first network element deployed in a first network, and the method includes the following steps 1101 .

[0334] Step 1101: Send first charging information of a terminal device using satellite services to a second network element deployed in a second network, wherein the first charging information is used to generate a first charging data record CDR, and the first CDR is used to generate a charging bill.

[0335] The specific implementation process, principle and optional implementation method of step 1101 can be found in the relevant parts of other embodiments and will not be repeated here.

[0336] In some embodiments, the first network element may send a first charging request message to the second network element, wherein the message carries first charging information of the terminal device using the satellite service.

[0337] In some embodiments, the first network element is an SMF network element and the second network element is a CHF network element.

[0338] In some embodiments, the SMF network element may determine the second network element based on at least one of the following information:

[0339] At least one of a CHF address provided by the policy control function PCF for the data connection session of the terminal device, a CHF instance identifier associated with the data connection session, and / or a CHF set identifier;

[0340] Unified Data Management (UDM) provides billing feature information.

[0341] CHF instance discovered by the Network Storage Function NRF;

[0342] Billing feature information provided locally by the SMF.

[0343] In some embodiments, the first billing information includes:

[0344] The satellite service indication SSI is used to instruct the terminal device to access the first network via satellite service.

[0345] In some embodiments, the first billing information further includes at least one of the following information:

[0346] Satellite service type indication, used to indicate whether the satellite service is a backhaul service or a terminal direct connection service;

[0347] Satellite type indication, used to indicate the type of satellite providing satellite services;

[0348] Satellite service quality;

[0349] Satellite identification and / or constellation identification;

[0350] Operator ID.

[0351] In some embodiments, the method may further include: the first network element determining that the terminal device accesses the first network via satellite service.

[0352] In some embodiments, the first network is a terrestrial network and the second network is a satellite network.

[0353] In some embodiments, the second network element may further send a first charging response message to the first network element. Correspondingly, the first network element may further receive the first charging response message sent by the second network element.

[0354] In a satellite communications billing method provided by an embodiment of the present disclosure, a first network element deployed in a first network can send first billing information of a terminal device using satellite services to a second network element deployed in a second network. The first billing information is used to generate a first charging data record (CDR), which is used to generate a billing invoice. As a result, the second network element deployed in the second network can generate a first CDR for generating a billing invoice based on the first billing information provided by the first network element deployed in the first network. This avoids the problem of inconsistent billing results between the second network and the first network, and improves the accuracy of satellite communications billing results.

[0355] Figure 12 is a flow chart of a satellite communication billing method according to an embodiment of the present disclosure. As shown in Figure 12, the method according to the embodiment of the present disclosure is applied to a first network element deployed in a first network, and includes the following steps 1201-1204.

[0356] Step 1201: Send first charging information of a terminal device using satellite services to a second network element deployed in a second network, wherein the first charging information is used to generate a first charging data record CDR, and the first CDR is used to generate a charging bill.

[0357] Step 1202: Receive a first charging response message sent by the second network element.

[0358] Step 1203: Send first information to be updated to the second network element, where the first information to be updated is used to update the first CDR.

[0359] In some embodiments, the first to-be-updated information is sent when an update triggering condition is satisfied, wherein the update triggering condition includes at least one of the following conditions:

[0360] a change in charging conditions, wherein the charging conditions include at least one of the type of satellite providing satellite services, satellite service quality, and satellite identification;

[0361] The rate group limit is reached;

[0362] The quota limit was reached.

[0363] Step 1204: Receive a first charging update response message sent by the second network element.

[0364] The specific implementation process, principles and optional implementation methods of steps 1201-1204 can be found in the relevant parts of other embodiments and will not be repeated here.

[0365] The communication method involved in the embodiments of the present disclosure may include at least one of steps 1201 to 1204. For example, step 1201 may be implemented as an independent embodiment, steps 1201+1203 may be implemented as an independent embodiment, steps 1201+1202+1203 may be implemented as an independent embodiment, steps 1201+1203+1204 may be implemented as an independent embodiment, steps 1201+1202+1203+1204 may be implemented as an independent embodiment, and so on, but the present invention is not limited thereto.

[0366] In some embodiments, step 1202 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0367] In some embodiments, step 1204 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0368] The satellite communications billing method provided by the disclosed embodiments enables a second network element deployed in a second network to generate a first CDR for generating a bill based on first billing information provided by a first network element deployed in a first network, thereby avoiding the problem of inconsistent billing results between the second network and the first network and improving the accuracy of satellite communications billing results. Furthermore, the second network element can promptly update the first CDR based on the first to-be-updated information sent by the first network element, thereby ensuring the timeliness of the billing results generated by the second network element.

[0369] Figure 13 is a flow chart of a satellite communication billing method according to an embodiment of the present disclosure. As shown in Figure 13, the method according to an embodiment of the present disclosure is applied to a first network element deployed in a first network, and includes the following steps 1301-1304.

[0370] Step 1301: Send first charging information of a terminal device using satellite services to a second network element deployed in a second network, wherein the first charging information is used to generate a first charging data record CDR, and the first CDR is used to generate a charging bill.

[0371] Step 1302: Receive a first charging response message sent by the second network element.

[0372] Step 1303: Send a first charging termination instruction to the second network element, where the first charging termination instruction is used to close the first CDR.

[0373] In some embodiments, the first billing termination indication is carried in a first billing termination request message sent by the first network element to the second network element. The first billing termination request message also carries second billing information of the terminal device. The second billing information is used to update the first CDR.

[0374] Step 1304: Receive a first charging termination response message sent by the second network element.

[0375] The specific implementation process, principles and optional implementation methods of steps 1301-1304 can be found in the relevant parts of other embodiments and will not be repeated here.

[0376] The communication method involved in the embodiments of the present disclosure may include at least one of steps 1301 to 1304. For example, step 1301 may be implemented as an independent embodiment, steps 1301+1303 may be implemented as an independent embodiment, steps 1301+1302+1303 may be implemented as an independent embodiment, steps 1301+1303+1304 may be implemented as an independent embodiment, steps 1301+1302+1303+1304 may be implemented as an independent embodiment, and so on, but the present invention is not limited thereto.

[0377] In some embodiments, step 1302 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0378] In some embodiments, step 1304 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0379] The satellite communications billing method provided by the disclosed embodiments enables a second network element deployed in a second network to generate a first CDR for generating a bill based on first billing information provided by a first network element deployed in a first network. This avoids inconsistent billing results between the second network and the first network, and improves the accuracy of satellite communications billing results. Furthermore, the second network element can promptly close the first CDR based on a billing termination instruction sent by the first network element, thereby ensuring that billing by the second network element is stopped promptly.

[0380] Figure 14 is a flow chart of a satellite communication billing method according to an embodiment of the present disclosure. As shown in Figure 14, the method according to the embodiment of the present disclosure is applied to a first network element deployed in a first network, and includes the following steps 1401-1404.

[0381] Step 1401: Send a first billing request message to a second network element deployed in a second network, wherein the first billing request message carries first billing information of a terminal device using satellite services, wherein the first billing information is used to generate a first billing data record CDR, and the first CDR is used to generate a billing bill.

[0382] Step 1402: Receive a first charging response message sent by the second network element, wherein the first charging response message carries first information to be negotiated.

[0383] Step 1403: Send a second billing request message to a third network element deployed in the first network, wherein the second billing request message carries third billing information of the terminal device using the satellite service, wherein the third billing information is used to generate a second CDR, the second CDR is used to generate a billing bill, and the third billing information includes the first information to be negotiated.

[0384] Step 1404: Receive a second charging response message sent by the third network element.

[0385] The specific implementation process, principles and optional implementation methods of steps 1401-1404 can be found in the relevant parts of other embodiments and will not be repeated here.

[0386] In some embodiments, the second network element is an SMF network element, and the second network element and the third network element are respectively CHF network elements.

[0387] The second network element and / or the third network element is determined by the SMF network element according to at least one of the following information:

[0388] At least one of a CHF address provided by the policy control function PCF for the data connection session of the terminal device, a CHF instance identifier associated with the data connection session, and / or a CHF set identifier;

[0389] Unified Data Management (UDM) provides billing feature information.

[0390] CHF instance discovered by the Network Storage Function NRF;

[0391] SMF locally provides billing feature information.

[0392] The communication method involved in the embodiments of the present disclosure may include at least one of steps 1401 to 1404. For example, step 1401 may be implemented as an independent embodiment, steps 1401+1402 may be implemented as an independent embodiment, steps 1401+1402+1403 may be implemented as an independent embodiment, steps 1401+1402+1403+1404 may be implemented as an independent embodiment, and so on, but the present invention is not limited thereto.

[0393] In some embodiments, step 1404 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0394] The satellite communications billing method provided by the disclosed embodiments enables a second network element to generate a first CDR for generating a billing invoice based on first billing information of a terminal device using satellite services provided by a first network element, and a third network element to generate a second CDR for generating a billing invoice based on third billing information of the terminal device provided by the first network element. Because the second and third network elements perform billing based on the same data source, inconsistent billing results between the second and first networks can be avoided, thereby improving the accuracy of satellite communications billing results. Furthermore, by having the first network element receive first information to be negotiated from the second network element and carry the first information to be negotiated in a second billing request message, which is then sent to the third network element, parameter negotiation led by the second network can be implemented.

[0395] Figure 15 is a flow chart of a satellite communication billing method according to an embodiment of the present disclosure. As shown in Figure 15, the method according to an embodiment of the present disclosure is applied to a first network element deployed in a first network, and includes the following steps 1501-1504.

[0396] Step 1501: Send third billing information of a terminal device using satellite services to a third network element deployed in the first network, wherein the third billing information is used to generate a second CDR, and the second CDR is used to generate a billing bill.

[0397] Step 1502: Receive a second charging response message sent by a third network element, where the second charging response message carries second information to be negotiated.

[0398] Step 1503: Send first billing information of a terminal device using satellite services to a second network element deployed in a second network, wherein the first billing information is used to generate a first charging data record CDR, the first CDR is used to generate a bill, and the first billing information includes second information to be negotiated.

[0399] Step 1504: Receive a first charging response message sent by the second network element.

[0400] The specific implementation process, principles and optional implementation methods of steps 1501-1504 may be related to other embodiments and will not be repeated here.

[0401] In some embodiments, the second network element is an SMF network element, and the second network element and the third network element are respectively CHF network elements.

[0402] The second network element and / or the third network element is determined by the SMF network element according to at least one of the following information:

[0403] At least one of a CHF address provided by the policy control function PCF for the data connection session of the terminal device, a CHF instance identifier associated with the data connection session, and / or a CHF set identifier;

[0404] Unified Data Management (UDM) provides billing feature information.

[0405] CHF instance discovered by the Network Storage Function NRF;

[0406] SMF locally provides billing feature information.

[0407] The communication method involved in the embodiments of the present disclosure may include at least one of steps 1501 to 1504. For example, step 1501 may be implemented as an independent embodiment, steps 1501+1502 may be implemented as an independent embodiment, steps 1501+1502+1503 may be implemented as an independent embodiment, steps 1501+1502+1503+1504 may be implemented as an independent embodiment, etc., but the present invention is not limited thereto.

[0408] In some embodiments, step 1504 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0409] The satellite communications billing method provided by the disclosed embodiments enables a second network element to generate a first CDR for generating a billing invoice based on first billing information of a terminal device using satellite services provided by a first network element, and a third network element to generate a second CDR for generating a billing invoice based on third billing information of the terminal device provided by the first network element. Because the second and third network elements perform billing based on the same data source, inconsistent billing results between the second network and the first network can be avoided, thereby improving the accuracy of satellite communications billing results. Furthermore, by having the first network element receive second information to be negotiated from the third network element and carry the second information to be negotiated in a first billing request message, which is then sent to the second network element, parameter negotiation led by the first network can be implemented.

[0410] Figure 16 is a flow chart illustrating a satellite communications billing method according to an embodiment of the present disclosure. As shown in Figure 16, the method according to an embodiment of the present disclosure is applied to a first network element deployed in a first network. Based on the satellite communications billing method illustrated in Figures 14 or 15, the method further includes the following steps 1601-1604.

[0411] Step 1601: Send second information to be updated to a third network element, where the second information to be updated is used to update a second CDR.

[0412] Step 1602: Receive a second billing update response message sent by the third network element.

[0413] Step 1603: Send second information to be updated to the second network element, where the second information to be updated is used to update the first CDR.

[0414] Step 1604: Receive a third charging update response message sent by the second network element.

[0415] The specific implementation process, principles and optional implementation methods of steps 1601-1604 may be related to other embodiments and will not be repeated here.

[0416] In some embodiments, step 1602 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0417] In some embodiments, step 1604 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0418] The satellite communication billing method provided by the embodiment of the present disclosure sends the second information to be updated to the third network element and the second network element through the first network element, so that the second network element and the third network element can update their respective generated CDRs according to the second information to be updated sent by the first network element, thereby ensuring the timeliness and consistency of the billing results generated by the second network element and the third network element.

[0419] Figure 17 is a flow chart illustrating a satellite communications billing method according to an embodiment of the present disclosure. As shown in Figure 17 , the method according to an embodiment of the present disclosure is applied to a first network element deployed in a first network. Based on the satellite communications billing method illustrated in Figures 14 or 15 , the method further includes the following steps 1701-1704.

[0420] Step 1701: Send a second charging termination instruction to a second network element, where the second charging termination instruction is used to close a first CDR.

[0421] In some embodiments, the second billing termination indication is carried in a second billing termination request message sent by the first network element to the second network element. The second billing termination request message also carries fourth billing information of the terminal device. The fourth billing information is used to update the first CDR.

[0422] Step 1702: Receive a second charging termination response message sent by the second network element.

[0423] Step 1703: Send a third charging termination instruction to the third network element, where the third charging termination instruction is used to close the second CDR.

[0424] Step 1704: Receive a third charging termination response message sent by a third network element.

[0425] In some embodiments, the third billing termination indication is carried in a third billing termination request message sent by the first network element to the third network element. The third billing termination request message also carries fifth billing information of the terminal device. The fifth billing information is used to update the second CDR.

[0426] The specific implementation process, principles and optional implementation methods of steps 1701-1704 may be related to other embodiments and will not be repeated here.

[0427] In some embodiments, step 1702 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0428] In some embodiments, step 1704 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0429] The satellite communication billing method provided by the embodiment of the present disclosure sends a second billing termination indication to the second network element through the first network element, and sends a third billing termination indication to the third network element, so that the second network element and the third network element can promptly close their respective generated CDRs according to the billing termination indication sent by the first network element, thereby ensuring that the second network element and the third network element stop billing in a timely manner to ensure the consistency of the billing results generated by the second network element and the third network element.

[0430] Figure 18 is a flow chart of a satellite communication billing method according to an embodiment of the present disclosure. As shown in Figure 18, the method according to an embodiment of the present disclosure is applied to a second network element deployed in a second network, and the method includes the following steps 1801-1802.

[0431] Step 1801: Receive first billing information sent by a first network element deployed in a first network, wherein the first billing information includes billing information of a terminal device using a satellite service.

[0432] In some embodiments, the first billing information includes:

[0433] The satellite service indication SSI is used to instruct the terminal device to access the first network via satellite service.

[0434] In some embodiments, the first billing information further includes at least one of the following information:

[0435] Satellite service type indication, used to indicate whether the satellite service is a backhaul service or a terminal direct connection service;

[0436] Satellite type indication, used to indicate the type of satellite providing satellite services;

[0437] Satellite service quality;

[0438] Satellite identification and / or constellation identification;

[0439] Operator ID.

[0440] In some embodiments, the first billing information is sent when it is determined that the terminal device accesses the first network via satellite service.

[0441] In some embodiments, the first network is a terrestrial network and the second network is a satellite network.

[0442] Step 1802: Generate a first charging data record (CDR) based on the first charging information. The first CDR is used to generate a charging bill.

[0443] The specific implementation process, principles and optional implementation methods of steps 1801-1802 can be found in the relevant parts of other embodiments and will not be repeated here.

[0444] In some embodiments, the second network element may further send a first charging response message to the first network element.

[0445] In a satellite communications billing method provided by an embodiment of the present disclosure, a second network element may receive first billing information sent by a first network element deployed in a first network and, based on the first billing information, generate a first charging data record (CDR) for generating a bill. Thus, the second network element deployed in the second network generates the first CDR for generating a bill based on the first billing information provided by the first network element deployed in the first network, thereby avoiding the problem of inconsistent billing results between the second network and the first network and improving the accuracy of satellite communications billing results.

[0446] Figure 19 is a flow chart of a satellite communication billing method according to an embodiment of the present disclosure. As shown in Figure 19, the method according to an embodiment of the present disclosure is applied to a second network element deployed in a second network, and includes the following steps 1901-1906.

[0447] Step 1901: Receive first billing information sent by a first network element deployed in a first network, wherein the first billing information includes billing information of a terminal device using a satellite service.

[0448] Step 1902: Generate a first CDR based on the first billing information. The first CDR is used to generate a billing bill.

[0449] Step 1903: Send a first charging response message to the first network element.

[0450] Step 1904: Receive the information to be updated sent by the first network element.

[0451] The information to be updated may be the first information to be updated or the second information to be updated in the aforementioned embodiment.

[0452] In some embodiments, the information to be updated is sent when an update triggering condition is satisfied, wherein the update triggering condition includes at least one of the following conditions:

[0453] a change in charging conditions, wherein the charging conditions include at least one of the type of satellite providing satellite services, satellite service quality, and satellite identification;

[0454] The rate group limit is reached;

[0455] The quota limit was reached.

[0456] Step 1905: Update the first CDR based on the information to be updated.

[0457] Step 1906: Send a billing update response message to the first network element.

[0458] The accounting update response message may be the first accounting update response message or the third accounting update response message in the aforementioned embodiment.

[0459] The specific implementation process, principles and optional implementation methods of steps 1901-1906 can be found in the relevant parts of other embodiments and will not be repeated here.

[0460] In some embodiments, step 1903 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0461] In some embodiments, step 1906 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0462] In the satellite communications billing method provided by the embodiments of the present disclosure, a second network element deployed in a second network can generate a first CDR for generating a bill based on first billing information provided by a first network element deployed in a first network. This avoids inconsistent billing results between the second network and the first network, and improves the accuracy of satellite communications billing results. Furthermore, the second network element can promptly update the first CDR based on the pending update information sent by the first network element, thereby ensuring the timeliness of the billing results generated by the second network element.

[0463] Figure 20 is a flow chart of a satellite communication billing method according to an embodiment of the present disclosure. As shown in Figure 20, the method according to the embodiment of the present disclosure is applied to a second network element deployed in a second network, and includes the following steps 2001-2006.

[0464] Step 2001: Receive first billing information sent by a first network element deployed in a first network, wherein the first billing information includes billing information of a terminal device using a satellite service.

[0465] Step 2002: Generate a first charging data record (CDR) based on the first charging information. The first CDR is used to generate a charging bill.

[0466] Step 2003: Send a first charging response message to the first network element.

[0467] Step 2004: Receive a billing termination indication sent by the first network element.

[0468] In some embodiments, the billing termination indication is carried in a first billing termination request message sent by the first network element to the second network element. The first billing termination request message also carries second billing information of the terminal device. The second billing information is used to update the first CDR.

[0469] The billing termination instruction may be the first billing termination instruction or the second billing termination instruction in the aforementioned embodiment.

[0470] Step 2005: close the first CDR based on the charging termination indication.

[0471] Step 2006: Send a billing termination response message to the first network element.

[0472] The accounting update response message may be the first accounting termination response message or the second accounting termination response message in the aforementioned embodiment.

[0473] The specific implementation process, principles and optional implementation methods of steps 2001-2006 can be found in the relevant parts of other embodiments and will not be repeated here.

[0474] In some embodiments, step 2003 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0475] In some embodiments, step 2006 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0476] In the satellite communications billing method provided by the embodiments of the present disclosure, a second network element deployed in a second network can generate a first CDR for generating a bill based on first billing information provided by a first network element deployed in a first network. This avoids inconsistent billing results between the second network and the first network, and improves the accuracy of satellite communications billing results. Furthermore, the second network element can promptly close the first CDR based on a billing termination instruction sent by the first network element, thereby ensuring that the second network element stops billing in a timely manner.

[0477] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a first network element in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a second network element in any of the above methods.

[0478] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0479] In the embodiment of the present disclosure, the processor is a circuit with signal processing capability. In one implementation, the processor can be a circuit with instruction reading and execution capability, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP); in another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit, and the logical relationship of the above hardware circuit is fixed or reconfigurable, such as a hardware circuit implemented by a processor as an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0480] Figure 21 is a schematic diagram of the structure of a satellite communication billing device according to an embodiment of the present disclosure. This satellite communication billing device can be applied to electronic devices, such as the first network element in the aforementioned embodiment. As shown in Figure 21 , the satellite communication billing device 2100 may include at least one of a transceiver module 2101 and a processing module 2102.

[0481] In some embodiments, the transceiver module 2101 is used to send first billing information of a terminal device using satellite services to a second network element deployed in a second network, wherein the first billing information is used to generate a first billing data record CDR, and the first CDR is used to generate a billing bill.

[0482] In some embodiments, the processing module 2102 is used to determine whether the terminal device accesses the first network via satellite service.

[0483] In some embodiments, the first network is a terrestrial network and the second network is a satellite network.

[0484] In some embodiments, the first billing information includes:

[0485] The satellite service indication SSI is used to instruct the terminal device to access the first network via satellite service.

[0486] In some embodiments, the first billing information further includes at least one of the following information:

[0487] Satellite service type indication, used to indicate whether the satellite service is a backhaul service or a terminal direct connection service;

[0488] Satellite type indication, used to indicate the type of satellite providing satellite services;

[0489] Satellite service quality;

[0490] Satellite identification and / or constellation identification;

[0491] Operator ID.

[0492] In some embodiments, the transceiver module 2101 is configured to send first information to be updated to the second network element, wherein the first information to be updated is used to update the first CDR.

[0493] In some embodiments, the first to-be-updated information is sent when an update triggering condition is satisfied, wherein the update triggering condition includes at least one of the following conditions:

[0494] a change in charging conditions, wherein the charging conditions include at least one of the type of satellite providing satellite services, satellite service quality, and satellite identification;

[0495] The rate group limit is reached;

[0496] The quota limit was reached.

[0497] In some embodiments, the transceiver module 2101 is configured to send a first billing termination indication to the second network element, wherein the first billing termination indication is used to close the first CDR.

[0498] In some embodiments, the first billing termination indication is carried in a first billing termination request message sent by the first network element to the second network element. The first billing termination request message also carries second billing information of the terminal device. The second billing information is used to update the first CDR.

[0499] In some embodiments, the transceiver module 2101 is used to send third billing information of a terminal device using satellite services to a third network element deployed in the first network, wherein the third billing information is used to generate a second CDR, and the second CDR is used to generate a billing bill.

[0500] In some embodiments, the third billing information includes first information to be negotiated, and the first information to be negotiated is carried in a second billing request message sent by the first network element to the third network element. The second billing request message is sent after the first network element receives the first billing response message sent by the second network element. The first billing response message carries the first information to be negotiated. The first billing response message is sent by the second network element in response to generating the first CDR.

[0501] In some embodiments, the first billing information includes second information to be negotiated, and the second information to be negotiated is carried in a first billing request message sent by the first network element to the second network element. The first billing request message is sent after the first network element receives the second billing response message sent by the third network element. The second billing response message carries the second information to be negotiated. The second billing response message is sent by the third network element in response to generating a second CDR.

[0502] In some embodiments, the first network element is a session management function SMF network element, and the second network element and the third network element are charging function CHF network elements respectively.

[0503] In some embodiments, the second network element and / or the third network element is determined by an SMF network element according to at least one of the following information:

[0504] At least one of a CHF address provided by the policy control function PCF for the data connection session of the terminal device, a CHF instance identifier associated with the data connection session, and / or a CHF set identifier;

[0505] Unified Data Management (UDM) provides billing feature information.

[0506] CHF instance discovered by the Network Storage Function NRF;

[0507] SMF locally provides billing feature information.

[0508] In some embodiments, the transceiver module 2101 is used to send the second information to be updated to the third network element, wherein the second information to be updated is used to update the second CDR; and send the second information to be updated to the second network element, wherein the second information to be updated is used to update the first CDR.

[0509] In some embodiments, the transceiver module 2101 is configured to send a second billing termination instruction to the second network element, wherein the second billing termination instruction is used to close the first CDR; and send a third billing termination instruction to the third network element, wherein the third billing termination instruction is used to close the second CDR.

[0510] In some embodiments, the second billing termination indication is carried in a second billing termination request message sent by the first network element to the second network element. The second billing termination request message also carries the fourth billing information of the terminal device, and the fourth billing information is used to update the first CDR; the third billing termination indication is carried in a third billing termination request message sent by the first network element to the third network element. The third billing termination request message also carries the fifth billing information of the terminal device, and the fifth billing information is used to update the second CDR.

[0511] Figure 22 is a schematic diagram of the structure of a satellite communication billing device according to an embodiment of the present disclosure. This satellite communication billing device can be applied to electronic devices, such as the second network element in the aforementioned embodiment. As shown in Figure 22, the satellite communication billing device 2200 may include at least one of a transceiver module 2201 and a processing module 2202.

[0512] In some embodiments, the transceiver module 2201 is used to receive first billing information sent by a first network element deployed in a first network, wherein the first billing information includes billing information of a terminal device using satellite services; the processing module 2202 is used to generate a first billing data record CDR based on the first billing information, and the first CDR is used to generate a billing bill.

[0513] In some embodiments, the first billing information is sent when it is determined that the terminal device accesses the first network via satellite service.

[0514] In some embodiments, the first network is a terrestrial network and the second network is a satellite network.

[0515] In some embodiments, the first billing information includes:

[0516] The satellite service indication SSI is used to instruct the terminal device to access the first network via satellite service.

[0517] In some embodiments, the first billing information further includes at least one of the following information:

[0518] Satellite service type indication, used to indicate whether the satellite service is a backhaul service or a terminal direct connection service;

[0519] Satellite type indication, used to indicate the type of satellite providing satellite services;

[0520] Satellite service quality;

[0521] Satellite identification and / or constellation identification;

[0522] Operator ID.

[0523] In some embodiments, the transceiver module 2201 is used to receive the information to be updated sent by the first network element; the processing module 2202 is used to update the first CDR based on the information to be updated.

[0524] In some embodiments, the information to be updated is sent when an update triggering condition is satisfied, wherein the update triggering condition includes at least one of the following conditions:

[0525] a change in charging conditions, wherein the charging conditions include at least one of the type of satellite providing satellite services, satellite service quality, and satellite identification;

[0526] The rate group limit is reached;

[0527] The quota limit was reached.

[0528] In some embodiments, the transceiver module 2201 is configured to receive a charging termination indication sent by a first network element; and the processing module 2202 is configured to close the first CDR based on the charging termination indication.

[0529] In some embodiments, the billing termination indication is carried in a first billing termination request message sent by the first network element to the second network element. The first billing termination request message also carries second billing information of the terminal device. The second billing information is used to update the first CDR.

[0530] Figure 23 is a schematic diagram of the structure of an electronic device 2300 proposed in an embodiment of the present disclosure. Electronic device 2300 can be the aforementioned first network element, or the aforementioned second network element, or a chip, chip system, or processor that supports the first network element in implementing any of the above methods, or a chip, chip system, or processor that supports the second network element in implementing any of the above methods. Electronic device 2300 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0531] As shown in Figure 23, the electronic device 2300 includes one or more processors 2301. The processor 2301 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control communication devices (such as base stations, baseband chips, terminals, terminal chips, distributed units (DUs) or centralized units (CUs), etc.), execute programs, and process program data. The processor 2301 is used to call instructions to enable the electronic device 2300 to perform any of the above methods.

[0532] In some embodiments, the electronic device 2300 further includes one or more memories 2302 for storing instructions. In some embodiments, all or part of the memories 2302 may also be located outside the electronic device 2300.

[0533] In some embodiments, the electronic device 2300 further includes one or more transceivers 2303. When the electronic device 2300 includes one or more transceivers 2303, the communication steps such as sending and receiving in the above method are performed by the transceiver 2303, and the other steps are performed by the processor 2301.

[0534] In some embodiments, the transceiver 2303 may include a receiver and a transmitter, which may be separate or integrated. In some embodiments, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0535] In some embodiments, the electronic device 2300 further includes one or more interface circuits 2304, which are connected to the memory 2302. The interface circuits 2304 can be used to receive signals from the memory 2302 or other devices, and can be used to send signals to the memory 2302 or other devices. For example, the interface circuits 2304 can read instructions stored in the memory 2302 and send the instructions to the processor 2301.

[0536] The electronic device 2300 described in the above embodiment may be a first network element or a second network element, but the scope of the electronic device 2300 described in the present disclosure is not limited thereto, and the structure of the electronic device 2300 may not be limited by FIG. 23. The electronic device may be an independent device or may be part of a larger device. For example, the electronic device may be: 1) an independent integrated circuit (IC), or a chip, or a chip system or subsystem; (2) a collection of one or more ICs. In some embodiments, the above IC collection may also include a storage component for storing data or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal, an intelligent terminal, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0537] FIG24 is a schematic diagram of the structure of a chip 2400 according to an embodiment of the present disclosure. If the electronic device 2300 can be a chip or a chip system, reference can be made to the schematic diagram of the structure of the chip 2400 shown in FIG24 , but the present disclosure is not limited thereto.

[0538] The chip 2400 includes one or more processors 2401 , and the processor 2401 is used to call instructions so that the chip 2400 executes any of the above methods.

[0539] In some embodiments, chip 2400 further includes one or more interface circuits 2402, which are connected to memory 2403. Interface circuits 2402 can be used to receive signals from memory 2403 or other devices, and can be used to send signals to memory 2403 or other devices. For example, interface circuit 2402 can read instructions stored in memory 2403 and send the instructions to processor 2401. In some embodiments, the terms interface circuit, interface, transceiver pin, and transceiver are interchangeable.

[0540] In some embodiments, the chip 2400 further includes one or more memories 2403 for storing instructions. In some embodiments, all or part of the memories 2403 may be external to the chip 2400.

[0541] The present disclosure also provides a storage medium having instructions stored thereon, which, when executed on the electronic device 2300, causes the electronic device 2300 to execute any of the above methods. In some embodiments, the storage medium is an electronic storage medium. In some embodiments, the storage medium is a computer-readable storage medium, but is not limited thereto and may also be a storage medium readable by other devices. In some embodiments, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a temporary storage medium.

[0542] The present disclosure also provides a program product, which, when executed by the electronic device 2300, enables the electronic device 2300 to perform any of the above methods. In some embodiments, the program product is a computer program product.

[0543] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

[0544] It is understood that the aforementioned satellite communication billing device, electronic device, satellite communication billing system, storage medium, program product, and computer program are all used to implement the method proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects of the corresponding method and will not be repeated here.

[0545] In some embodiments, the terms such as satellite communication billing method, information processing method, communication method, etc. can be replaced with each other, the terms such as satellite communication billing device, information processing device, communication device, etc. can be replaced with each other, and the terms such as information processing system, communication system, etc. can be replaced with each other.

[0546] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0547] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0548] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0549] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0550] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0551] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0552] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0553] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0554] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0555] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0556] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0557] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0558] In some embodiments, "network" can be interpreted as devices included in the network (eg, access network equipment, core network equipment, etc.).

[0559] In some embodiments, devices, etc. can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as "device", "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", and "subject" can be used interchangeably.

[0560] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc. can be used interchangeably.

[0561] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codeword", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0562] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0563] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0564] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0565] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

[0566] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0567] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "a certain", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, a certain A, any A, or first A, etc., but not limited to this.

[0568] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented using software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present disclosure are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer program can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a high-density digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0569] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0570] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0571] The above description is merely a specific embodiment of the present disclosure, but the scope of protection of the present disclosure is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this disclosure should be included in the scope of protection of the present disclosure. Therefore, the scope of protection of the present disclosure should be based on the scope of protection of the claims.

Claims

1. A charging method for satellite communication, characterized in that, The method is applied to a first network element deployed in a first network, and the method includes: Sending first charging information of a terminal device using satellite services to a second network element deployed in a second network, where the first charging information is used to generate a first charging data record CDR, and the first CDR is used to generate a charging bill.

2. The method according to claim 1, characterized in that, The first charging information includes: A satellite service indication SSI, which is used to indicate that the terminal device accesses the first network through the satellite service.

3. The method according to claim 2, wherein The first charging information further includes at least one of the following information: A satellite service type indication, which is used to indicate that the satellite service is a backhaul service or a terminal direct connection service; A satellite type indication, which is used to indicate the type of the satellite providing the satellite service; The quality of the satellite service; The satellite identifier and / or the constellation identifier; The operator identifier.

4. The method according to claim 1, characterized in that The method further includes: Determining that the terminal device accesses the first network through the satellite service.

5. The method according to claim 1, wherein The first network is a terrestrial network, and the second network is a satellite network.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: Sending first information to be updated to the second network element, where the first information to be updated is used to update the first CDR.

7. The method according to claim 6, wherein The first information to be updated is sent when an update trigger condition is met, where the update trigger condition includes at least one of the following conditions: The charging condition changes, where the charging condition includes at least one of the type of the satellite providing the satellite service, the quality of the satellite service, and the satellite identifier; The limit of the rate group is reached; The quota limit is reached.

8. The method according to any one of claims 1-5, characterized in that The method further includes: Sending a first charging termination indication to the second network element, where the first charging termination indication is used to close the first CDR.

9. The method according to claim 8, wherein The first charging termination indication is carried in a first charging termination request message sent by the first network element to the second network element, and the first charging termination request message further carries second charging information of the terminal device, and the second charging information is used to update the first CDR.

10. The method according to any one of claims 1 to 5, characterized in that, The method further includes: Sending third charging information of the terminal device using satellite services to a third network element deployed in the first network, where the third charging information is used to generate a second CDR, and the second CDR is used to generate a charging bill.

11. The method according to claim 10, characterized in that, The third charging information includes first information to be negotiated, and the first information to be negotiated is carried in a second charging request message sent by the first network element to the third network element. The second charging request message is sent after the first network element receives a first charging response message sent by the second network element. The first charging response message carries the first information to be negotiated, and the first charging response message is sent by the second network element in response to generating the first CDR.

12. The method according to claim 10, wherein The first charging information includes second information to be negotiated, and the second information to be negotiated is carried in a first charging request message sent by the first network element to the second network element. The first charging request message is sent after the first network element receives a second charging response message sent by the third network element. The second charging response message carries the second information to be negotiated, and the second charging response message is sent by the third network element in response to generating the second CDR.

13. The method according to claim 10, wherein The first network element is a session management function (SMF) network element, and the second network element and the third network element are respectively charging function (CHF) network elements.

14. The method according to claim 13, wherein The second network element and / or the third network element is determined by the SMF network element according to at least one of the following information: At least one of the CHF address provided by the policy control function (PCF) for the data connection session of the terminal device, the CHF instance identifier associated with the data connection session, and / or the CHF set identifier; Charging feature information provided by the unified data management function (UDM); CHF instances discovered by the network repository function (NRF); Charging feature information locally provided by the SMF.

15. The method according to claim 10, characterized in that, The method further includes: Sending second information to be updated to the third network element, where the second information to be updated is used to update the second CDR; Sending the second information to be updated to the second network element, where the second information to be updated is used to update the first CDR.

16. The method according to claim 10, wherein The method further includes: Sending a second charging termination indication to the second network element, where the second charging termination indication is used to close the first CDR; Sending a third charging termination indication to the third network element, where the third charging termination indication is used to close the second CDR.

17. The method according to claim 16, wherein The second charging termination indication is carried in a second charging termination request message sent by the first network element to the second network element, and the second charging termination request message further carries fourth charging information of the terminal device, and the fourth charging information is used to update the first CDR; The third charging termination indication is carried in a third charging termination request message sent by the first network element to the third network element, and the third charging termination request message further carries fifth charging information of the terminal device, and the fifth charging information is used to update the second CDR.

18. A billing method for satellite communication, characterized in that, The method is applied to a second network element deployed in a second network. The method includes: Receiving first charging information sent by a first network element deployed in a first network, where the first charging information includes charging information of a terminal device using satellite services; Generating a first charging data record (CDR) based on the first charging information, and the first CDR is used to generate a charging bill.

19. The method according to claim 18, wherein The first charging information includes: A satellite service indication (SSI) for indicating that the terminal device accesses the first network through the satellite service.

20. The method according to claim 19, wherein, The first charging information further includes at least one of the following information: A satellite service type indication for indicating that the satellite service is a backhaul service or a terminal direct connection service; A satellite type indication for indicating the type of the satellite providing the satellite service; Satellite service quality; Satellite identifier and / or constellation identifier; Operator identifier.

21. The method according to claim 18, wherein The first charging information is sent when it is determined that the terminal device accesses the first network through the satellite service.

22. The method according to claim 18, wherein The first network is a terrestrial network, and the second network is a satellite network.

23. The method according to any one of claims 18 - 22, characterized in that, The method further includes: Receiving the information to be updated sent by the first network element; Updating the first CDR based on the information to be updated.

24. The method according to claim 23, wherein The information to be updated is sent when an update trigger condition is met, where the update trigger condition includes at least one of the following conditions: The charging condition changes, where the charging condition includes at least one of the type of satellite providing the satellite service, satellite service quality, and satellite identifier; The limit of the rate group is reached; The quota limit is reached.

25. The method according to any one of claims 18 - 22, characterized in that, The method further includes: Receiving a charging termination instruction sent by the first network element; Closing the first CDR based on the charging termination instruction.

26. The method according to claim 25, wherein The charging termination instruction is carried in a first charging termination request message sent by the first network element to the second network element, and the first charging termination request message further carries second charging information of the terminal device, and the second charging information is used to update the first CDR.

27. A charging device for satellite communication, characterized in that, The device is applied to a first network element deployed in a first network, and the device includes: A transceiver module, configured to send first charging information of a terminal device using satellite service to a second network element deployed in a second network, where the first charging information is used to generate a first charging data record (CDR), and the first CDR is used to generate a charging bill.

28. A billing device for satellite communication, characterized in that, The device is applied to a second network element deployed in a second network, and the device includes: A transceiver module, configured to receive first charging information sent by a first network element deployed in a first network, where the first charging information includes charging information of a terminal device using satellite service; A processing module, configured to generate a first charging data record CDR based on the first charging information, and the first CDR is used to generate a charging bill.

29. An electronic device, characterized in that, Includes: One or more processors; One or more memories for storing instructions; Wherein, the processor is configured to call the instructions to cause the electronic device to execute the charging method for satellite communication according to any one of claims 1-17, or execute the charging method for satellite communication according to any one of claims 18-26.

30. A billing system for satellite communication, characterized in that, Includes a first network element deployed in a first network and a second network element deployed in a second network; Wherein, the first network element is configured to implement the charging method for satellite communication according to any one of claims 1-17, and the second network element is configured to implement the charging method for satellite communication according to any one of claims 18-26.

31. The charging system according to claim 30, wherein The system further includes a third network element deployed in the first network; the third network element is configured to: Receive third charging information of a terminal device using satellite service sent by the first network element; Generate a second CDR based on the third charging information, and the second CDR is used to generate a charging bill.

32. The charging system according to claim 31, wherein The third network element is further configured to: Receive second information to be updated sent by the first network element; Update the second CDR based on the second information to be updated.

33. The charging system according to claim 31, wherein The third network element is further configured to: Receive a charging termination indication sent by the first network element; Close the second CDR based on the charging termination indication.

34. A storage medium storing instructions, characterized in that, When the instruction runs on an electronic device, the electronic device is caused to execute the charging method for satellite communication according to any one of claims 1-17, or execute the charging method for satellite communication according to any one of claims 18-26.

Images