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 charging function network element deployed in a first network sending to a second charging function 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 creating or updating a first charging data record (CDR), and the first CDR is used for generating a charging bill. Thus, a second charging function network element deployed in a second network may generate, on the basis of first charging information provided by a first charging function 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 disclosure claims priority to a Chinese patent application filed with the Patent Office of China on January 16, 2024, with application number 202410070545.3 and application name “Billing Method and Device for Satellite Communication,” the entire contents of which are incorporated by reference into this disclosure. 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 billing function network element deployed in a first network. The method includes: sending first billing information of a terminal device using satellite services to a second billing function network element deployed in the second network; wherein the first billing information is used to create or update a first billing data record CDR, and the first CDR is used to generate a billing bill.

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

[0008] In some embodiments, the first charging information is charging information regarding satellite communications for the first network.

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

[0010] an operator identifier of the first network;

[0011] an operator identifier of the second network;

[0012] Providing the terminal device using the satellite service in the first network with the identifier of the satellite and / or the identifier of the constellation of the satellite service;

[0013] Providing satellite quality of service (QoS) of the satellite service to terminal devices using the satellite service in the first network;

[0014] a satellite service indication SSI corresponding to a terminal device in the first network using the satellite service, used to instruct the corresponding terminal device to access the first network via the satellite service;

[0015] a satellite service type indication corresponding to the terminal device using the satellite service in the first network, used to indicate whether the satellite service used by the corresponding terminal device is a backhaul service or a terminal direct connection service;

[0016] a satellite type indication corresponding to the terminal device using the satellite service in the first network, used to indicate the type of satellite providing the satellite service to the corresponding terminal device;

[0017] an uplink data usage and / or downlink data usage corresponding to a terminal device in the first network using the satellite service;

[0018] at least one of an identifier, a start time, an end time, and a duration of a data connection session of a terminal device using the satellite service in the first network;

[0019] the number of data connection sessions of terminal devices in the first network using the satellite service;

[0020] An identifier of a terminal device in the first network that uses the satellite service.

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

[0022] the total uplink data usage and / or the total downlink data usage corresponding to the terminal direct connection service in the first network;

[0023] the total uplink data usage and / or the total downlink data usage corresponding to the backhaul service in the first network;

[0024] the total uplink data usage and / or the total downlink data usage for each satellite category corresponding to the terminal direct connection service in the first network;

[0025] a total amount of uplink data usage and / or a total amount of downlink data usage for each satellite category corresponding to the backhaul service in the first network;

[0026] The total number of protocol data unit (PDU) connections and / or the total PDU connection duration corresponding to the terminal direct connection service in the first network;

[0027] The total number of PDU connections and / or the total duration of PDU connections corresponding to the backhaul service in the first network.

[0028] In some embodiments, the first billing information is sent in response to a set condition being met, and the set condition includes at least one of the following:

[0029] The current time is the target sending time, and the interval between the target sending time and the previous sending time is a preset time length;

[0030] receiving an information sending instruction, wherein the information sending instruction is used to instruct the first charging function network element to send the first charging information;

[0031] The trigger event used to trigger the sending of billing information occurs.

[0032] In some embodiments, the first billing information is carried in a billing request message sent by the first billing function network element to the second billing function network element, and the billing request message also carries first quota information, wherein the first quota information is for the first network, and the first quota information includes first quota application information for applying for a quota, and / or first quota usage information for informing that a quota has been used.

[0033] In some embodiments, the method further comprises:

[0034] Sending a first billing mode indication to the second billing function network element;

[0035] The first billing mode indication is used to instruct the first billing function network element to send billing information about satellite communication for the first network.

[0036] In some embodiments, the method further comprises:

[0037] receiving a first billing mode indication sent by the second billing function network element;

[0038] The first billing mode indication is used to instruct the first billing function network element to send billing information about satellite communication for the first network.

[0039] In some embodiments, the first billing information is billing information for a single terminal device using the satellite service, and is sent by a billing trigger function network element deployed in the first network to the first billing function network element in response to a billing trigger event of a data connection session of the single terminal device being triggered, and is sent by the first billing function network element to the second billing function network element in response to receiving the billing information of the single terminal device.

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

[0041] an operator identifier of the first network;

[0042] an operator identifier of the second network;

[0043] an identifier of a satellite and / or an identifier of a constellation providing the satellite service for the single terminal device;

[0044] QoS of the satellite providing the satellite service for the single terminal device;

[0045] The satellite service indication SSI corresponding to the single terminal device is used to indicate that the single terminal device accesses the first network via the satellite service;

[0046] The satellite service type indication corresponding to the single terminal device is used to indicate whether the satellite service is a backhaul service or a terminal direct connection service;

[0047] The satellite type indication corresponding to the single terminal device is used to indicate the type of satellite providing the satellite service;

[0048] The uplink data usage and / or downlink data usage corresponding to the single terminal device;

[0049] at least one of an identifier, a start time, an end time, and a duration of a data connection session of the single terminal device;

[0050] The identifier of the single terminal device;

[0051] QoS flow identifier.

[0052] In some embodiments, the first charging information is carried in a charging request message sent by the charging triggering function network element to the first charging function network element, and / or carried in a charging request message sent by the first charging function network element to the second charging function network element;

[0053] The charging request message also carries at least one of the following information:

[0054] First charging negotiation information, wherein the first charging negotiation information is used to negotiate the charging trigger event and / or reporting category, wherein the reporting category includes immediate reporting and / or deferred reporting;

[0055] Second quota information, wherein the second quota information is for the first network or the single terminal device, and the second quota information includes second quota application information for applying for a quota, and / or second quota usage information for notifying the used quota.

[0056] In some embodiments, the method further comprises:

[0057] The second charging function network element is determined according to at least one of the following information:

[0058] at least one of a CHF address provided by a 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;

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

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

[0061] SMF locally provides billing feature information.

[0062] In some embodiments, the method further comprises:

[0063] A second CDR is created based on the first charging information received from the charging trigger function network element, where the second CDR is used to generate a charging bill.

[0064] In some embodiments, the method further comprises:

[0065] Receiving the billing information to be updated sent by the billing trigger function network element;

[0066] updating the second CDR based on the billing information to be updated;

[0067] Forward the to-be-updated billing information to the second billing function network element, where the to-be-updated billing information is used to update the first CDR.

[0068] In some embodiments, the to-be-updated charging information is carried in a charging update message sent by the charging triggering function network element to the first charging function network element, and / or carried in a charging update message sent by the first charging function network element to the second charging function network element;

[0069] The billing update message also carries at least one of the following information:

[0070] Second charging negotiation information, wherein the second charging negotiation information is used to negotiate the charging trigger event and / or reporting category, wherein the reporting category includes immediate reporting and / or deferred reporting;

[0071] The third quota information is for the first network or the single terminal device, and includes third quota application information for applying for a quota and / or third quota usage information for notifying the used quota.

[0072] In some embodiments, the to-be-updated charging information is sent by the charging trigger function network element in response to satisfying at least one of the following update triggering conditions:

[0073] A billing condition change, wherein the billing condition includes at least one of a type of satellite providing the satellite service, satellite service quality, and a satellite identifier;

[0074] The rate group limit is reached;

[0075] The quota limit was reached.

[0076] In some embodiments, the method further comprises:

[0077] Receiving a billing termination instruction sent by the billing trigger function network element;

[0078] closing the second CDR based on the charging termination indication;

[0079] The charging termination instruction is forwarded to the second charging function network element, where the charging termination instruction is used to close the first CDR.

[0080] In some embodiments, the charging termination indication is carried in a charging termination message sent by the charging trigger function to the first charging function network element, and / or carried in a charging termination message sent by the first charging function network element to the second charging function network element;

[0081] The charging termination message also carries at least one of the following information:

[0082] The second charging information of the single terminal device is used to update the first CDR and the second CDR;

[0083] Fourth quota information, wherein the fourth quota information is for the first network or the single terminal device, and the fourth quota information includes fourth quota application information for applying for a quota, and / or fourth quota usage information for notifying the used quota.

[0084] In some embodiments, the method further comprises:

[0085] Sending a second billing mode indication to the second charging function network element;

[0086] The second billing mode indication is used to instruct the first billing function network element to send the billing information of the single terminal device using the satellite service to the second billing function network element in response to receiving the billing information for the single terminal device using the satellite service. The billing information of the single terminal is sent to the first billing function network element by the billing trigger function network element deployed in the first network in response to a billing trigger event of the data connection session of the single terminal device being triggered.

[0087] In some embodiments, the method further comprises:

[0088] receiving a second billing mode indication sent by the second billing function network element;

[0089] The second billing mode indication is used to instruct the first billing function network element to send the billing information of the single terminal device using the satellite service to the second billing function network element in response to receiving the billing information for the single terminal device using the satellite service. The billing information of the single terminal is sent to the first billing function network element by the billing trigger function network element deployed in the first network in response to a billing trigger event of the data connection session of the single terminal device being triggered.

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

[0091] 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 billing function network element deployed in a second network. The method includes: receiving first billing information of a terminal device using satellite services sent by a first billing function network element deployed in the first network; and creating or updating a first billing data record CDR based on the first billing information, wherein the first CDR is used to generate a billing bill.

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

[0093] In some embodiments, the first charging information is charging information regarding satellite communications for the first network.

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

[0095] an operator identifier of the first network;

[0096] an operator identifier of the second network;

[0097] Providing the terminal device using the satellite service in the first network with the identifier of the satellite and / or the identifier of the constellation of the satellite service;

[0098] Providing satellite quality of service (QoS) of the satellite service to terminal devices using the satellite service in the first network;

[0099] a satellite service indication SSI corresponding to a terminal device in the first network using the satellite service, used to instruct the corresponding terminal device to access the first network via the satellite service;

[0100] a satellite service type indication corresponding to the terminal device using the satellite service in the first network, used to indicate whether the satellite service used by the corresponding terminal device is a backhaul service or a terminal direct connection service;

[0101] a satellite type indication corresponding to the terminal device using the satellite service in the first network, used to indicate the type of satellite providing the satellite service to the corresponding terminal device;

[0102] an uplink data usage and / or downlink data usage corresponding to a terminal device in the first network using the satellite service;

[0103] at least one of an identifier, a start time, an end time, and a duration of a data connection session of a terminal device using the satellite service in the first network;

[0104] the number of data connection sessions of terminal devices in the first network using the satellite service;

[0105] An identifier of a terminal device in the first network that uses the satellite service.

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

[0107] the total uplink data usage and / or the total downlink data usage corresponding to the terminal direct connection service in the first network;

[0108] the total uplink data usage and / or the total downlink data usage corresponding to the backhaul service in the first network;

[0109] the total uplink data usage and / or the total downlink data usage for each satellite category corresponding to the terminal direct connection service in the first network;

[0110] a total amount of uplink data usage and / or a total amount of downlink data usage for each satellite category corresponding to the backhaul service in the first network;

[0111] The total number of protocol data unit (PDU) connections and / or the total PDU connection duration corresponding to the terminal direct connection service in the first network;

[0112] The total number of PDU connections and / or the total duration of PDU connections corresponding to the backhaul service in the first network.

[0113] In some embodiments, the first billing information is sent in response to a set condition being met, and the set condition includes at least one of the following:

[0114] The current time is the target sending time, and the interval between the target sending time and the previous sending time is a preset time length;

[0115] receiving an information sending instruction, wherein the information sending instruction is used to instruct the first charging function network element to send the first charging information;

[0116] The trigger event used to trigger the sending of billing information occurs.

[0117] In some embodiments, the first billing information is carried in a billing request message sent by the first billing function network element to the second billing function network element, and the billing request message also carries first quota information, wherein the first quota information is for the first network, and the first quota information includes first quota application information for applying for a quota, and / or first quota usage information for informing that a quota has been used.

[0118] In some embodiments, the method further comprises:

[0119] receiving a first billing mode indication sent by the first billing function network element;

[0120] The first billing mode indication is used to instruct the first billing function network element to send billing information about satellite communication for the first network.

[0121] In some embodiments, the method further comprises:

[0122] Sending a first billing mode indication to the first billing function network element;

[0123] The first billing mode indication is used to instruct the first billing function network element to send billing information about satellite communication for the first network.

[0124] In some embodiments, the first billing information is billing information for a single terminal device using the satellite service, and is sent by a billing trigger function network element deployed in the first network to the first billing function network element in response to a billing trigger event of a data connection session of the single terminal device being triggered, and is sent by the first billing function network element to the second billing function network element in response to receiving the billing information of the single terminal device.

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

[0126] an operator identifier of the first network;

[0127] an operator identifier of the second network;

[0128] an identifier of a satellite and / or an identifier of a constellation providing the satellite service for the single terminal device;

[0129] QoS of the satellite providing the satellite service for the single terminal device;

[0130] The satellite service indication SSI corresponding to the single terminal device is used to indicate that the single terminal device accesses the first network via the satellite service;

[0131] The satellite service type indication corresponding to the single terminal device is used to indicate whether the satellite service is a backhaul service or a terminal direct connection service;

[0132] The satellite type indication corresponding to the single terminal device is used to indicate the type of satellite providing the satellite service;

[0133] The uplink data usage and / or downlink data usage corresponding to the single terminal device;

[0134] at least one of an identifier, a start time, an end time, and a duration of a data connection session of the single terminal device;

[0135] The identifier of the single terminal device;

[0136] QoS flow identifier.

[0137] In some embodiments, the first charging information is carried in a charging request message sent by the charging triggering function network element to the first charging function network element, and / or carried in a charging request message sent by the first charging function network element to the second charging function network element;

[0138] The charging request message also carries at least one of the following information:

[0139] First charging negotiation information, wherein the first charging negotiation information is used to negotiate the charging trigger event and / or reporting category, wherein the reporting category includes immediate reporting and / or deferred reporting;

[0140] Second quota information, wherein the second quota information is for the first network or the single terminal device, and the second quota information includes second quota application information for applying for a quota, and / or second quota usage information for notifying the used quota.

[0141] In some embodiments, the second charging function network element is determined according to at least one of the following information:

[0142] at least one of a CHF address provided by a 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;

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

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

[0145] SMF locally provides billing feature information.

[0146] In some embodiments, the method further comprises:

[0147] receiving the to-be-updated billing information forwarded by the first billing function network element, wherein the to-be-updated billing information is sent by the billing triggering function network element to the first billing function network element;

[0148] The first CDR is updated based on the billing information to be updated.

[0149] In some embodiments, the to-be-updated charging information is carried in a charging update message sent by the charging triggering function network element to the first charging function network element, and / or carried in a charging update message sent by the first charging function network element to the second charging function network element;

[0150] The billing update message also carries at least one of the following information:

[0151] Second charging negotiation information, wherein the second charging negotiation information is used to negotiate the charging trigger event and / or reporting category, wherein the reporting category includes immediate reporting and / or deferred reporting;

[0152] The third quota information is for the first network or the single terminal device, and includes third quota application information for applying for a quota and / or third quota usage information for notifying the used quota.

[0153] In some embodiments, the to-be-updated charging information is sent by the charging trigger function network element in response to satisfying at least one of the following update triggering conditions:

[0154] A billing condition change, wherein the billing condition includes at least one of a type of satellite providing the satellite service, satellite service quality, and a satellite identifier;

[0155] The rate group limit is reached;

[0156] The quota limit was reached.

[0157] In some embodiments, the method further comprises:

[0158] receiving a charging termination instruction forwarded by the first charging function network element, wherein the charging termination instruction is sent by the charging triggering function network element to the first charging function network element;

[0159] Based on the charging termination indication, the first CDR is closed.

[0160] In some embodiments, the charging termination indication is carried in a charging termination message sent by the charging trigger function to the first charging function network element, and / or carried in a charging termination message sent by the first charging function network element to the second charging function network element;

[0161] The charging termination message also carries at least one of the following information:

[0162] The second charging information of the single terminal device is used to update the first CDR and the second CDR;

[0163] Fourth quota information, wherein the fourth quota information is for the first network or the single terminal device, and the fourth quota information includes fourth quota application information for applying for a quota, and / or fourth quota usage information for notifying the used quota.

[0164] In some embodiments, the method further comprises:

[0165] receiving a second billing mode indication sent by the first billing function network element;

[0166] The second billing mode indication is used to instruct the first billing function network element to send the billing information of the single terminal device using the satellite service to the second billing function network element in response to receiving the billing information for the single terminal device using the satellite service. The billing information of the single terminal is sent to the first billing function network element by the billing trigger function network element deployed in the first network in response to a billing trigger event of the data connection session of the single terminal device being triggered.

[0167] In some embodiments, the method further comprises:

[0168] Sending a second billing mode indication to the first charging function network element;

[0169] The second billing mode indication is used to instruct the first billing function network element to send the billing information of the single terminal device using the satellite service to the second billing function network element in response to receiving the billing information for the single terminal device using the satellite service. The billing information of the single terminal is sent to the first billing function network element by the billing trigger function network element deployed in the first network in response to a billing trigger event of the data connection session of the single terminal device being triggered.

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

[0171] 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 billing function network element deployed in a first network, and the device includes: a transceiver module for sending first billing information of a terminal device using satellite services to a second billing function network element deployed in the second network; wherein the first billing information is used to create or update a first billing data record CDR, and the first CDR is used to generate a billing bill.

[0172] 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 billing function network element deployed in a second network, and the device includes: a transceiver module for receiving first billing information of a terminal device using satellite services sent by a first billing function network element deployed in the first network; and a processing module for creating or updating a first billing data record CDR based on the first billing information, wherein the first CDR is used to generate a billing bill.

[0173] 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.

[0174] According to the sixth aspect of an embodiment of the present disclosure, a billing system for satellite communication is proposed, comprising a first billing function network element deployed in a first network and a second billing function network element deployed in a second network; wherein, the first billing function 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 billing function 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.

[0175] In some embodiments, the system further includes a charging trigger function network element deployed in the first network; the charging trigger function network element is configured to:

[0176] In response to a billing trigger event for a data connection session of a single terminal device using satellite service being triggered, billing information of the single terminal device is sent to the first billing function network element, wherein the billing information of the single terminal device is used by the first billing function network element to generate a second CDR, and is forwarded to the second billing function network element to generate a first CDR.

[0177] In some embodiments, the billing trigger function network element is also used to: send billing information to be updated to the first billing function network element; wherein the billing information to be updated is used to update the second CDR, and is forwarded to the second billing function network element to update the first CDR.

[0178] In some embodiments, the charging trigger function network element is further used to: send a charging termination indication to the first charging function network element, wherein the charging termination indication is used to close the second CDR, and is used to forward it to the second charging function network element to close the first CDR.

[0179] 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.

[0180] 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.

[0181] 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.

[0182] The solution proposed in the embodiment of the present disclosure is that a first billing function network element deployed in a first network sends first billing information of a terminal device using satellite services to a second billing function network element deployed in a second network, wherein the first billing information is used to create or update a first billing data record CDR, and the first CDR is used to generate a billing bill. As a result, the second billing function network element deployed in the second network can generate a first CDR for generating a billing bill based on the first billing information provided by the first billing function 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

[0183] 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.

[0184] Figure 1 is a schematic diagram of satellite backhaul;

[0185] Figure 2 is another schematic diagram of satellite backhaul;

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0207] In some remote areas and areas beyond the reach of terrestrial networks, such as deserts, offshore areas, 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 network connectivity issues in remote areas, aviation, oceans, 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 base stations and core network elements, network connectivity services can be provided to users. Satellites can provide terminal satellite access services (also known as direct satellite connections) for users in sparsely populated areas (such as oceans and forests), where terminals connect to the core network via satellite and gateways. They can also provide backhaul services (also known as backhaul services) for base stations, where base stations connect to the core network via satellite. These satellite access or backhaul services can also be provided in emergency or temporary situations (such as disaster areas).

[0208] In satellite access scenarios, there are two main types of satellite payloads: transparent and regenerative. In satellite transparent transmission mode, the satellite acts as a radio frequency (RF) remote unit, completely transparent to base station protocols. In satellite regenerative mode, the satellite can have some protocol layer functions of the base station or core network. Referring to the schematic diagram of satellite backhaul shown in Figure 1, in the satellite backhaul scenario, terminal devices access the core network through the terrestrial access network. Satellite backhaul is used between the core network and the terrestrial access network to provide transmission for the N2 / N3 reference point. The satellite system transparently carries the payload of the Third Generation Partnership Project (3GPP) reference point communication. As shown in Figure 2, a base station can have multiple candidate satellite backhauls on the N2 and N3 interfaces, such as geostationary orbit (GEO) satellite backhaul, low Earth orbit (LEO) satellite backhaul, and LEO satellite backhaul with inter-satellite link (ISL). The base station's N2 and N3 interfaces use the same satellite backhaul at specific times.

[0209] However, due to the high cost of building satellite networks and other reasons, most mobile network operators (MNOs) do not have their own satellite networks. In order to provide network connection services to users in remote areas, aviation, oceans, deserts and other areas, they need to rent satellites from satellite service providers (SSPs) or satellite network operators (SNOs) that own satellite networks to provide satellite access services or satellite backhaul services to their users. In this case, MNOs are usually called terrestrial network operators. In addition to providing satellite services to MNOs, SNOs can also establish core network systems. In the scenario where the MNO rents a satellite, the MNO will count the satellite categories and data volume used by users to charge users for calls, and the SSP or SNO will generate bills based on the actual amount of data used by the MNO or the amount of data specified in the agreement to charge the MNO. Among them, due to the different types of satellites, the service quality of the return link provided is also different. For example, high-orbit satellites are nearly 36,000 kilometers from the ground, the service time of a single satellite is long, and the delay of the return link is longer. Low-orbit satellites are 500 kilometers from the ground, the service time of a single satellite is short, and the delay of the return link is shorter. SSP or SNO will also generate different bills according to different satellite types to differentiate billing.

[0210] In related technologies, such as SNOs, the SNO typically identifies and counts the MNO's traffic usage based on its own satellite network and then generates a bill. The MNO, in turn, counts user traffic based on its own core network's User Plane Function (UPF) or Session Management Function (SMF) network elements. The MNO then compares this data with the SNO's bill to pay for satellite rental. Under this billing model, due to differences in the network elements used for statistics and the format of data packets, the total data transmission volume counted by the SNO and the MNO can easily differ, resulting in inaccurate SNO billing results. Accurately billing for satellite-based communications has become a pressing issue.

[0211] 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.

[0212] 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.

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

[0214] As shown in FIG3 , the satellite communication billing system 300 may include but is not limited to a first billing function network element 301 deployed in a first network and a second billing function network element 302 deployed in a second network.

[0215] In some embodiments, the first network, a communications network provided by an MNO, can be referred to as a terrestrial network. The second network, a communications network provided by an SSP or 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, it is also an SNO. When an SNO leases satellite resources to an MNO and provides satellite services to the MNO, it is also an SSP.

[0216] In some embodiments, the first charging function network element 301 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.

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

[0218] In some embodiments, referring to FIG4 , the satellite communication charging system 300 may further include a charging trigger function network element 303 deployed in the first network.

[0219] In some embodiments, the billing trigger function network element 303 is, for example, an SMF network element or other network element with a billing trigger function, which is not limited in the present disclosure.

[0220] It can be understood that the satellite communication billing system 300 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.

[0221] The following embodiments of the present disclosure can be applied to the satellite communication billing system shown in Figure 3 or Figure 4 or some of the entities therein, but are not limited thereto. The entities shown in Figures 3 and 4 are examples. The satellite communication billing system may include all or part of the entities shown in Figures 3 or 4, or may include other entities other than those shown in Figures 3 or 4. 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.

[0222] 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.

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

[0224] Figure 5 is an interactive diagram illustrating a satellite communication billing method according to an embodiment of the present disclosure. As shown in Figure 5, the method according to an embodiment of the present disclosure is applied to the satellite communication billing system 300 shown in Figure 3 or Figure 4, and includes the following steps 501-502.

[0225] Step 501 : The first charging function network element 301 sends first charging information of a terminal device using satellite services to the second charging function network element 302 .

[0226] 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.

[0227] In some embodiments, the charging trigger function network element 303 may send charging information of the terminal device using the satellite service to the first charging function network element 301. The first charging function network element 301 may directly forward the charging information sent once or multiple times by the charging trigger function network element 303 to the second charging function network element 302. Accordingly, the first charging information in step 501 may include the charging information sent once or multiple times by the charging trigger function network element 303.

[0228] In some embodiments, the charging trigger function network element 303 may send charging information of the terminal device using the satellite service to the first charging function network element 301. The first charging function network element 301 may integrate the charging information sent once or multiple times by the charging trigger function network element 303 and send the integrated charging information to the second charging function network element 302. Accordingly, the first charging information in step 501 may include integrated charging information, which is obtained by integrating the charging information sent once or multiple times by the charging trigger function network element 303.

[0229] In some embodiments, the billing trigger function network element 303 can send billing information of the terminal equipment using satellite services to the first billing function network element 301. The first billing function network element 301 can generate a CDR based on the billing information sent once or multiple times by the billing trigger function network element 303, and send the CDR or the information in the CDR to the second billing function network element 302. Accordingly, the first billing information in step 501 may include the CDR or the information in the CDR, which is generated based on the billing information sent once or multiple times by the billing trigger function network element 303.

[0230] In some embodiments, the first billing information may be for some terminal devices using satellite services in the first network, or for all terminal devices using satellite services in the first network, which is not limited in this application. The number of these some or all terminal devices may be one or more, which is not limited in this application. The satellite service may include at least one of a terminal direct connection service and a backhaul service.

[0231] In some embodiments, the first billing function network element 301 can first determine whether the terminal device in the first network accesses the first network via satellite service. When it is determined that at least one terminal device accesses the first network via satellite service, the first billing information of some terminal devices in the at least one terminal device can be sent to the second billing function network element 302, or the first billing information of all terminal devices in the at least one terminal device can be sent to the second billing function network element 302.

[0232] In some embodiments, 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 the configuration that the terminal device is using the satellite backhaul service to access the base station, then determines the type of the satellite service as the type of satellite backhaul service, and sends the type of satellite backhaul service to the SMF network element, and the SMF network element sends the type of satellite backhaul service to the first billing function network element 301.

[0233] 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 Satellite).

[0234] In some embodiments, the first charging function network element 301 may send first charging information of a terminal device using satellite services to the second charging function network element 302 in response to a set condition being met. The set condition includes at least one of the following:

[0235] The current time is the target sending time, and the interval between the target sending time and the previous sending time is the preset length;

[0236] receiving an information sending instruction, wherein the information sending instruction is used to instruct the first billing function network element 301 to send first billing information;

[0237] The trigger event used to trigger the sending of billing information occurs.

[0238] The preset duration may be obtained through negotiation between the first charging function network element 301 and the second charging function network element 302 .

[0239] Step 502: The second charging function network element 302 creates or updates a first charging data record CDR based on the first charging information. The first CDR is used to generate a charging bill.

[0240] In some embodiments, after receiving the first billing information, the second billing function network element 302 may create a first CDR based on the first billing information if the first CDR has not been created, or may update the created first CDR if the first CDR has been created.

[0241] In some embodiments, the first CDR may include one or more of the first billing information.

[0242] In some embodiments, the second charging function network element 302 may send a charging response message to the first charging function network element 301 .

[0243] In some embodiments, the charging response message may be sent in response to generating the first CDR, wherein the charging response message is used to indicate that the second charging function network element 302 has generated the first CDR.

[0244] In some embodiments, the charging response message may be sent in response to receiving the first charging information, wherein the charging response message is used to indicate that the second charging function network element 302 has received the first charging information.

[0245] Among them, the second charging function network element 302 sends a charging response message to the first charging function network element 301, which can be executed in an interchangeable order or simultaneously with step 502, and this application does not impose any restrictions on this.

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

[0247] In the billing method for satellite communications provided by the embodiments of the present disclosure, a first billing function network element deployed in a first network can send first billing information of a terminal device using satellite services to a second billing function network element deployed in a second network, wherein the first billing information is used to create or update a first billing data record CDR, and the first CDR is used to generate a billing bill. As a result, the second billing function network element deployed in the second network can generate a first CDR for generating a billing bill based on the first billing information provided by the first billing function 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.

[0248] In addition, when the same SSP or SNO provides satellite services to different MNOs, the SSP or SNO needs to adapt to the billing methods of different MNOs. By adopting the satellite communication billing method provided in the embodiment of the present application, when the same SSP or SNO provides satellite services to different MNOs, the SSP or SNO can generate CDRs corresponding to different MNOs based on the same method, thereby solving the problem that the same SSP or SNO needs to adapt to the billing methods of different MNOs and improving the efficiency of generating billing results.

[0249] In some embodiments, the first billing function network element 301 can transmit first billing information of a terminal device using satellite services to the second billing function network element 302 using different transmission modes. For example, one transmission mode may include: the first billing function network element 301 transmits first billing information of a terminal device using satellite services to the second billing function network element 302, where the first billing information is billing information regarding satellite communications for the first network. This mode is described in detail below.

[0250] Figure 6 is an interactive diagram illustrating a satellite communication billing method according to an embodiment of the present disclosure. As shown in Figure 6, the method according to an embodiment of the present disclosure is applied to the satellite communication billing system 300 shown in Figure 3 or Figure 4, and includes the following steps 601-602.

[0251] In step 601 , the first charging function network element 301 sends first charging information of a terminal device using satellite services to the second charging function network element 302 , wherein the first charging information is charging information about satellite communications for a first network.

[0252] As a possible implementation manner, the first billing information may include at least one of the following information:

[0253] The operator identifier of the first network, used to uniquely identify the operator of the first network;

[0254] The operator identifier of the second network, used to uniquely identify the operator of the second network;

[0255] an identifier (Satellite ID) of a satellite and / or an identifier (Constellation ID) of a constellation that provides satellite services to terminal devices using satellite services in the first network; wherein a constellation may refer to a constellation of satellites that belong to the same SSP or SNO and form a satellite network, or may refer to a group of satellites working in coordination;

[0256] Satellite quality of service (Satellite QoS) for providing satellite services to terminal devices using the satellite services in the first network; wherein the satellite quality of service may include a calculated result of at least one of the following attributes: throughput, delay, jitter, and error rate;

[0257] Satellite service information (SSI) corresponding to a terminal device using satellite service in the first network, used to instruct the corresponding terminal device to access the first network via satellite service;

[0258] a satellite service type indication corresponding to a terminal device using a satellite service in the first network, used to indicate whether the satellite service used by the corresponding terminal device is a backhaul service or a terminal direct connection service;

[0259] A satellite category indicator (Satellite Category) corresponding to a terminal device using satellite services in the first network, used to indicate the type of satellite providing satellite services for the corresponding terminal device;

[0260] Uplink data usage (Uplink Volume) and / or downlink data usage (Downlink Volume) corresponding to a terminal device using satellite services in the first network;

[0261] at least one of an identifier, a start time (Start Timestamp), an end time (End Timestamp), and a duration (Time duration) of a data connection session of a terminal device using a satellite service in the first network;

[0262] The number of data connection sessions of terminal devices using satellite services in the first network (Connection number);

[0263] The identifier of the terminal device using the satellite service in the first network is used to uniquely identify the corresponding terminal device.

[0264] Among them, the terminal devices using satellite services in the above-mentioned first network may include all terminal devices using satellite services in the first network, or include some terminal devices using satellite services in the first network, wherein the number of all or some terminal devices may be one or more, and this application does not impose any restrictions on this. Optionally, the above-mentioned satellite identifier and / or constellation identifier, satellite service quality, satellite service indication, satellite service type indication, satellite type indication, uplink data usage and / or downlink data usage, data connection session identifier, start time, end time and duration, number of data connection sessions, and terminal device identifier may respectively correspond to a single terminal device or multiple terminal devices among all or some of the terminal devices.

[0265] Among them, the types of satellites providing satellite services may include medium-orbit satellites or medium-earth orbit satellite types, low-orbit satellites or low-earth orbit satellite types, high-orbit satellites or geostationary satellite types, and other satellite types.

[0266] The data connection session may be a protocol data unit session (PDU session) defined in the 3GPP standard specification, or may be other forms of sessions, which are not limited in the embodiments of the present disclosure.

[0267] In some embodiments, for any terminal device, if the first billing information includes a satellite service indicator (SSI) corresponding to the terminal device, the terminal device is instructed to access the first network via a satellite service; if the first billing information does not include the satellite service indicator (SSI) corresponding to the terminal device, 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.

[0268] 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, for any terminal device, when the first billing information includes the SSI corresponding to the terminal device, 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 satellite service, and the satellite service is a backhaul service; when the first billing information includes the SSI corresponding to the terminal device, 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 satellite service, and the satellite service is a terminal direct connection service. Alternatively, when the first billing information includes the SSI corresponding to the terminal device 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 the SSI corresponding to the terminal device 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.

[0269] It is understandable that the billing rules may be different for different types of satellites providing satellite services. In some embodiments, the SSI may further indicate the type of satellite providing satellite services, such as the SSI including a satellite type indicator for indicating the type of satellite providing satellite services. For example, for any terminal device, if the first billing information includes the SSI corresponding to the terminal device and the value of the satellite type indication included in the SSI is "LEO", the terminal device can be instructed to access the first network via satellite service, and the type of satellite providing satellite service is a low-orbit satellite type; if the first billing information includes the SSI corresponding to the terminal device and the value of the satellite type indication included in the SSI is "GEO", the terminal device can be instructed to access the first network via satellite service, and the type of satellite providing satellite service is a high-orbit satellite type; if the first billing information includes the SSI corresponding to the terminal device and the value of the satellite type indication included in the SSI is "MEO", the terminal device can be instructed to access the first network via satellite service, and the type of satellite providing satellite service is a medium-orbit satellite type; if the first billing information includes the SSI corresponding to the terminal device and the value of the satellite type indication included in the SSI is "OTHER_SAT", the terminal device can be instructed to access the first network via satellite service, and the type of satellite providing satellite service is other satellite types.

[0270] In some embodiments, the SSI may include a satellite service type indication and a satellite type indication. For example, for any terminal device, when the first billing information includes the SSI corresponding to the terminal device, and the value of the satellite service type indication included in the SSI is "0" and the value of the satellite type indication is "LEO", the terminal device may be instructed to access 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 corresponding to the terminal device, and the value of the satellite service type indication included in the SSI is "0" and the value of the satellite type indication is "GEO", the terminal device may be instructed to access 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. The type is a high-orbit satellite type; when the first billing information includes the SSI corresponding to the terminal device, and the value of the satellite service type indication included in the SSI is "1" and the value of the satellite type indication is "LEO", 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 the satellite providing the backhaul service is a low-orbit satellite type; when the first billing information includes the SSI corresponding to the terminal device, and the value of the satellite service type indication included in the SSI is "1" and the value of the satellite type indication is "GEO", 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 the satellite providing the backhaul service is a high-orbit satellite type.

[0271] In some embodiments, the satellite service type indicator and the satellite type indicator may be different from the satellite service indicator SSI. For example, for any terminal device, the first billing information may include the SSI, satellite service type indicator, and satellite type indicator corresponding to the terminal device. For example, if the SSI value is "1" and the satellite service type indicator value is "0," indicating that the terminal device accesses the first network via satellite service and the satellite service is a terminal direct connection service, when the SSI value is "1" and the satellite service type indicator value is "0," the satellite type indicator value is "LEO," indicating that the type of satellite providing the terminal direct connection service is a low-orbit satellite; the satellite type indicator value is "GEO," indicating that the type of satellite providing the terminal direct connection service is a high-orbit satellite; the satellite type indicator value is "MEO," indicating that the type of satellite providing the terminal direct connection service is a medium-orbit satellite; and the satellite type indicator value is "OTHER_SAT," indicating that the type of satellite providing the terminal direct connection service is other satellite types. Among them, taking the value of the SSI as "1" and the value of the satellite service type indication as "1", indicating that the terminal device accesses the first network through a satellite service and the satellite service is a backhaul service as an example, when the value of the SSI is "1" and the value of the satellite service type indication is "1", the value of the satellite type indication is "LEO", which can indicate that the type of satellite providing the backhaul service is a low-orbit satellite type; the value of the satellite type indication is "GEO", which can indicate that the type of satellite providing the backhaul service is a high-orbit satellite type; the value of the satellite type indication is "MEO", which can indicate that the type of satellite providing the backhaul service is a medium-orbit satellite type; the value of the satellite type indication is "OTHE "R_SAT", which can indicate that the type of satellite providing return service is other satellite types; the value of the satellite type indication is "DYNAMIC_GEO", which can indicate that the type of satellite providing return service is a dynamic high-orbit satellite type; the value of the satellite type indication is "DYNAMIC_MEO", which can indicate that the type of satellite providing return service is a dynamic medium-orbit satellite type; the value of the satellite type indication is "DYNAMIC_LEO", which can indicate that the type of satellite providing return service is a dynamic low-orbit satellite type; the value of the satellite type indication is "DYNAMIC_OTHER_SAT", which can indicate that the type of satellite providing return service is a dynamic other satellite type.

[0272] As another possible implementation, the first billing information includes at least one of the following information:

[0273] the total uplink data usage and / or the total downlink data usage corresponding to the terminal direct connection service in the first network;

[0274] a total uplink data usage and / or a total downlink data usage corresponding to the backhaul service in the first network;

[0275] the total uplink data usage and / or the total downlink data usage under each satellite category corresponding to the terminal direct connection service in the first network;

[0276] a total amount of uplink data usage and / or a total amount of downlink data usage for each satellite category corresponding to the backhaul service in the first network;

[0277] The total number of protocol data unit (PDU) connections and / or the total PDU connection duration corresponding to the terminal direct connection service in the first network;

[0278] The total number of PDU connections and / or the total duration of PDU connections corresponding to the backhaul service in the first network.

[0279] As another possible implementation, the first billing information may include at least one of the following information:

[0280] The operator identifier of the first network, used to uniquely identify the operator of the first network;

[0281] The operator identifier of the second network, used to uniquely identify the operator of the second network;

[0282] an identifier (Satellite ID) of a satellite and / or an identifier (Constellation ID) of a constellation that provides satellite services to terminal devices using satellite services in the first network; wherein a constellation may refer to a constellation of satellites that belong to the same SSP or SNO and form a satellite network, or may refer to a group of satellites working in coordination;

[0283] Satellite quality of service (Satellite QoS) for providing satellite services to terminal devices using the satellite services in the first network; wherein the satellite quality of service may include a calculated result of at least one of the following attributes: throughput, delay, jitter, and error rate;

[0284] Satellite service information (SSI) corresponding to a terminal device using satellite service in the first network, used to instruct the corresponding terminal device to access the first network via satellite service;

[0285] a satellite service type indication corresponding to a terminal device using a satellite service in the first network, used to indicate whether the satellite service used by the corresponding terminal device is a backhaul service or a terminal direct connection service;

[0286] A satellite category indicator (Satellite Category) corresponding to a terminal device using satellite services in the first network, used to indicate the type of satellite providing satellite services for the corresponding terminal device;

[0287] Uplink data usage (Uplink Volume) and / or downlink data usage (Downlink Volume) corresponding to a terminal device using satellite services in the first network;

[0288] at least one of an identifier, a start time (Start Timestamp), an end time (End Timestamp), and a duration (Time duration) of a data connection session of a terminal device using a satellite service in the first network;

[0289] The number of data connection sessions of terminal devices using satellite services in the first network (Connection number);

[0290] An identifier of a terminal device using a satellite service in the first network, used to uniquely identify the corresponding terminal device;

[0291] the total uplink data usage and / or the total downlink data usage corresponding to the terminal direct connection service in the first network;

[0292] a total uplink data usage and / or a total downlink data usage corresponding to the backhaul service in the first network;

[0293] the total uplink data usage and / or the total downlink data usage under each satellite category corresponding to the terminal direct connection service in the first network;

[0294] a total amount of uplink data usage and / or a total amount of downlink data usage for each satellite category corresponding to the backhaul service in the first network;

[0295] The total number of protocol data unit (PDU) connections and / or the total PDU connection duration corresponding to the terminal direct connection service in the first network;

[0296] The total number of PDU connections and / or the total duration of PDU connections corresponding to the backhaul service in the first network.

[0297] For the description of the above information included in the first billing information, please refer to other related parts and will not be repeated here.

[0298] In some embodiments, the first billing information can be carried in a billing request message sent by the first billing function network element 301 to the second billing function network element 302, and the billing request message also carries first quota information, wherein the first quota information is for the first network, and the first quota information includes first quota application information for applying for a quota, and / or first quota usage information for informing that the quota has been used.

[0299] By sending the first quota information to the second charging function network element 302 through the first charging function network element 301 to apply for a quota from the second network or to inform that the quota has been used, refined control of traffic can be achieved.

[0300] In some embodiments, in response to a set condition being met, the first charging function network element 301 may send first charging information of a terminal device using satellite services, or send a charging request message carrying the first charging information, or send a charging request message carrying the first charging information and first quota information to the second charging function network element 302. The set condition includes at least one of the following:

[0301] The current time is the target sending time, and the interval between the target sending time and the previous sending time is the preset length;

[0302] receiving an information sending instruction, wherein the information sending instruction is used to instruct the first billing function network element 301 to send first billing information;

[0303] The trigger event used to trigger the sending of billing information occurs.

[0304] The target sending time and the last sending time are both times when the billing information needs to be sent to the second billing function network element 302. The last sending time is before the target sending time and is separated from the target sending time by a preset time interval.

[0305] The preset duration may be obtained through negotiation between the first charging function network element 301 and the second charging function network element 302 .

[0306] In some embodiments, the first charging function network element 301 and the second charging function network element 302 may determine, through negotiation, a sending mode in which the first charging function network element 301 sends the first charging information to the second charging function network element 302 .

[0307] As a possible negotiation method, the first charging function network element 301 may send a first charging mode indication to the second charging function network element 302, wherein the first charging mode indication is used to instruct the first charging function network element 301 to send charging information about satellite communications for the first network. Furthermore, based on the first charging mode indication, the first charging function network element 301 may use the sending mode shown in step 601 or an optional implementation of step 601 to send first charging information for the terminal device using satellite services to the second charging function network element 302.

[0308] In some embodiments, the first billing mode indication sent by the first billing function network element 301 to the second billing function network element 302 may be carried in a billing mode request sent by the first billing function network element 301 to the second billing function network element 302. The billing mode request may also carry setting condition related information, so that the first billing function network element 301 can determine, based on the setting condition related information, when the setting condition is met, when the first billing information is sent. Then, in response to the setting condition being met, based on the first billing mode indication, the first billing information of the terminal device using the satellite service is sent to the second billing function network element 302 using the sending mode shown in step 601 or an optional implementation of step 601. The setting condition related information may, for example, include at least one of the following: a preset duration between the target sending time and the previous sending time; instruction information for instructing the first billing function network element 301 to send billing information in response to receiving an information sending instruction; and instruction information for instructing the first billing function network element 301 to send billing information in response to the occurrence of a trigger event, wherein the trigger event is used to trigger the sending of the billing information.

[0309] As another possible negotiation method, the second charging function network element 302 can send a first charging mode indication to the first charging function network element 301. Correspondingly, the first charging function network element 301 can receive the first charging mode indication sent by the second charging function network element 302. The first charging mode indication is used to instruct the first charging function network element 301 to send charging information related to satellite communications for the first network. Therefore, based on the first charging mode indication, the first charging function network element 301 can use the sending mode shown in step 601 or an optional implementation of step 601 to send the first charging information of the terminal device using the satellite service to the second charging function network element 302.

[0310] In some embodiments, the first billing mode indication sent by the second billing function network element 302 to the first billing function network element 301 may be carried in a billing mode response sent by the second billing function network element 302 to the first billing function network element 301. The billing mode response may also carry setting condition related information, so that the first billing function network element 301 can determine, based on the setting condition related information, when the first billing information is sent, when the setting condition is met. Then, in response to the setting condition being met, based on the first billing mode indication, the first billing information of the terminal device using the satellite service is sent to the second billing function network element 302 using the sending mode shown in step 601 or an optional implementation of step 601. The setting condition related information may, for example, include at least one of the following: a preset duration between the target sending time and the previous sending time; instruction information for instructing the first billing function network element 301 to send billing information in response to receiving an information sending instruction; and instruction information for instructing the first billing function network element 301 to send billing information in response to the occurrence of a triggering event, wherein the triggering event is used to trigger the sending of the billing information.

[0311] As another possible negotiation method, the first billing function network element 301 may send a first billing mode indication to the second billing function network element 302, and the second billing function network element 302 may return the first billing mode indication to the first billing function network element 301, wherein the first billing mode indication is used to instruct the first billing function network element 301 to send billing information about satellite communications for the first network. Thus, the first billing function network element 301 may send the first billing information of the terminal device using the satellite service to the second billing function network element 302 based on the first billing mode indication using the sending mode shown in step 601 or an optional implementation of step 601.

[0312] In some embodiments, the first billing mode indication sent by the first billing function network element 301 to the second billing function network element 302 may be carried in the billing mode request sent by the first billing function network element 301 to the second billing function network element 302, and the first billing mode indication sent by the second billing function network element 302 to the first billing function network element 301 may be carried in the billing mode response returned by the second billing function network element 302 to the first billing function network element 301. The billing mode request and / or the billing mode response may also carry setting condition related information, so that the first billing function network element 301 may determine, based on the setting condition related information, when the first billing function network element 301 meets the setting condition, to send the first billing information of the terminal device using the satellite service to the second billing function network element 302 based on the first billing mode indication and using the sending mode shown in step 601 or the optional implementation method of step 601. Among them, the setting condition related information may include, for example, at least one of the following: preset duration information between the target sending time and the previous sending time; indication information for instructing the first billing function network element 301 to send billing information in response to receiving an information sending instruction; indication information for instructing the first billing function network element 301 to send billing information in response to the occurrence of a triggering event, wherein the triggering event is used to trigger the sending of billing information.

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

[0314] Step 602: The second charging function network element 302 creates or updates a first charging data record CDR based on the first charging information. The first CDR is used to generate a charging bill.

[0315] In some embodiments, the first CDR may include one or more of the first billing information.

[0316] In some embodiments, the second charging function network element 302 may send a charging response message to the first charging function network element 301. The second charging function network element 302 may send a charging response message to the first charging function network element 301, and the step 602 may be performed in a swapped order or simultaneously, which is not limited in this application.

[0317] In some embodiments, the charging response message may include a first quota response message, wherein the first quota response message may be directed to the first network.

[0318] In some embodiments, the first quota response message may include at least one of the parameters shown in Table 1 below:

[0319] Table 1 Parameters included in the first quota response message and their corresponding meanings

[0320] The granted quota information (Quota Grant Information) may include at least one of the parameters shown in Table 2 below:

[0321] Table 2 Permitted quota information includes parameters and their corresponding meanings

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

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

[0324] The satellite communication billing method provided by the embodiment of the present disclosure is that a first billing function network element deployed in a first network can send first billing information of a terminal device using satellite services to a second billing function network element deployed in a second network, wherein the first billing information is billing information about satellite communications for the first network, so that the second billing function network element deployed in the second network can generate a first CDR for generating a billing bill based on the first billing information provided by the first billing function 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. In addition, by having the first billing function network element send billing information about satellite communications for the first network to the second billing function network element, the first billing function network element is prevented from sending billing information of a single terminal device to the second billing function network element multiple times, saving signaling and resource overhead and simplifying the process of sending billing information.

[0325] In some embodiments, the first billing function network element 301 may transmit first billing information of a terminal device using satellite services to the second billing function network element 302 using different transmission modes. For example, one transmission mode may include: the first billing function network element 301 transmits first billing information of a terminal device using satellite services to the second billing function network element 302, where the first billing information is billing information for a single terminal device using satellite services. This mode is described in detail below.

[0326] 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 300 shown in Figure 4, and includes the following steps 701-703.

[0327] Step 701: The charging trigger function network element 303 sends first charging information of a terminal device using satellite services to the first charging function network element 301, wherein the first charging information is charging information for a single terminal device using satellite services.

[0328] In some embodiments, the charging trigger function network element 303 may send the charging information of the single terminal device to the first charging function network element 301 in response to a charging trigger event of a data connection session of the single terminal device using the satellite service being triggered.

[0329] Taking the billing trigger function network element 303 as the SMF network element, the first billing function network element 301 as the CHF network element, and the data connection session of a single terminal device using satellite service as a PDU session as an example, the SMF network element and the CHF network element can interact with the AMF, UPF, Policy Control Function (PCF) and Access Network (AN) in the first network to implement the establishment of the PDU session, PDU session authentication / authorization, session management policy modification, etc., and then the SMF network element can, when determining that the single terminal device uses satellite service, respond to the billing trigger event of the PDU session of the single terminal device being triggered, send the billing information of the single terminal device to the CHF network element to obtain authorization to perform billing based on the default billing trigger event.

[0330] In some embodiments, the first billing information may include at least one of the following information:

[0331] The operator identifier of the first network, used to uniquely identify the operator of the first network;

[0332] The operator identifier of the second network, used to uniquely identify the operator of the second network;

[0333] The identifier of the satellite and / or constellation providing satellite services for a single terminal device, where a constellation may refer to a constellation of satellites belonging to the same SSP or SNO and forming a satellite network, or may refer to a group of satellites working in coordination;

[0334] Quality of service (QoS) of a satellite providing satellite services to a single terminal device, wherein the QoS of the satellite may include a calculated result of at least one of the attributes of throughput, delay, jitter, and error rate;

[0335] A satellite service indication SSI corresponding to a single terminal device, used to indicate that the single terminal device accesses the first network via a satellite service;

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

[0337] The satellite type indication corresponding to a single terminal device is used to indicate the type of satellite providing satellite services;

[0338] Uplink data usage and / or downlink data usage corresponding to a single terminal device;

[0339] At least one of an identifier, a start time, an end time, and a duration of a data connection session of a single terminal device;

[0340] Identification of individual terminal devices;

[0341] QoS flow identifier.

[0342] Among them, the types of satellites providing satellite services may include medium-orbit satellites or medium-earth orbit satellite types, low-orbit satellites or low-earth orbit satellite types, high-orbit satellites or geostationary satellite types, and other satellite types.

[0343] The data connection session may be a PDU session defined in the 3GPP standard specification, or may be a session in other forms, which is not limited in the embodiments of the present disclosure.

[0344] In some embodiments, when the first billing information includes a satellite service indicator (SSI) corresponding to a single terminal device, the single terminal device is instructed to access the first network via a satellite service; and when the first billing information does not include the satellite service indicator (SSI) corresponding to the single terminal device, the single 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.

[0345] 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 corresponding to a single terminal device may further indicate the type of satellite service used by the single terminal device. For example, the SSI corresponding to the single terminal device includes a satellite service type indication, which is used to indicate that the satellite service used by the single terminal device is a backhaul service or a terminal direct connection service. For example, when the first billing information includes the SSI corresponding to the single terminal device, and the value of the satellite service type indication included in the SSI is "0", it can be indicated that the single terminal device accesses the first network via satellite service, and the satellite service is a backhaul service; when the first billing information includes the SSI corresponding to the single terminal device, and the value of the satellite service type indication included in the SSI is "1", it can be indicated that the single terminal device accesses the first network via satellite service, and the satellite service is a terminal direct connection service. Alternatively, when the first billing information includes the SSI corresponding to the single terminal device and the value of the satellite service type indication included in the SSI is "1", the single 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 the SSI corresponding to the single terminal device and the value of the satellite service type indication included in the SSI is "0", the single terminal device can be instructed to access the first network via satellite service, and the satellite service is a terminal direct connection service.

[0346] It is understandable that different types of satellites providing satellite services may result in different billing rules. In some embodiments, the SSI corresponding to a single terminal device may further indicate the type of satellite providing satellite services. For example, the SSI corresponding to the single terminal device includes a satellite type indicator for indicating the type of satellite providing satellite services. For example, when the first billing information includes the SSI corresponding to the single terminal device and the value of the satellite type indication included in the SSI is "LEO", the single terminal device can be instructed to access the first network via satellite service, and the type of satellite providing satellite service is a low-orbit satellite type; when the first billing information includes the SSI corresponding to the single terminal device and the value of the satellite type indication included in the SSI is "GEO", the single terminal device can be instructed to access the first network via satellite service, and the type of satellite providing satellite service is a high-orbit satellite type; when the first billing information includes the SSI corresponding to the single terminal device and the value of the satellite type indication included in the SSI is "MEO", the single terminal device can be instructed to access the first network via satellite service, and the type of satellite providing satellite service is a medium-orbit satellite type; when the first billing information includes the SSI corresponding to the single terminal device and the value of the satellite type indication included in the SSI is "OTHER_SAT", the single terminal device can be instructed to access the first network via satellite service, and the type of satellite providing satellite service is other satellite types.

[0347] In some embodiments, the SSI corresponding to a single terminal device may include a satellite service type indication and a satellite type indication. For example, when the first billing information includes the SSI corresponding to the single terminal device, and the value of the satellite service type indication included in the SSI is "0" and the value of the satellite type indication is "LEO", it can be indicated that the single terminal device accesses the first network through 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 corresponding to the single terminal device, and the value of the satellite service type indication included in the SSI is "0" and the value of the satellite type indication is "GEO", it can be indicated that the single terminal device accesses the first network through 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 the SSI corresponding to the single terminal device, and the value of the satellite service type indication included in the SSI is "1" and the value of the satellite type indication is "LEO", the single 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 the SSI corresponding to the single terminal device, and the value of the satellite service type indication included in the SSI is "1" and the value of the satellite type indication is "GEO", the single 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.

[0348] In some embodiments, the satellite service type indication and satellite type indication corresponding to a single terminal device may be different indications. For example, the first billing information may include the SSI, satellite service type indication, and satellite type indication corresponding to the single terminal device. Among them, taking the value of the SSI as "1" and the value of the satellite service type indication as "0", indicating that the single terminal device accesses the first network via satellite service and the satellite service is a terminal direct connection service as an example, when the value of the SSI is "1" and the value of the satellite service type indication is "0", the value of the satellite type indication is "LEO", which can indicate that the type of satellite providing terminal direct connection service for the single terminal device is a low-orbit satellite type; the value of the satellite type indication is "GEO", which can indicate that the type of satellite providing terminal direct connection service for the single terminal device is a high-orbit satellite type; the value of the satellite type indication is "MEO", which can indicate that the type of satellite providing terminal direct connection service for the single terminal device is a medium-orbit satellite type; the value of the satellite type indication is "OTHER_SAT", which can indicate that the type of satellite providing terminal direct connection service for the single terminal device is other satellite types. Among them, taking the value of the SSI as "1" and the value of the satellite service type indication as "1", indicating that the single terminal device accesses the first network via a satellite service and the satellite service is a backhaul service as an example, when the value of the SSI is "1" and the value of the satellite service type indication is "1", the value of the satellite type indication is "LEO", which can indicate that the type of satellite providing backhaul service for the single terminal device is a low-orbit satellite type; the value of the satellite type indication is "GEO", which can indicate that the type of satellite providing backhaul service for the single terminal device is a high-orbit satellite type; the value of the satellite type indication is "MEO", which can indicate that the type of satellite providing backhaul service for the single terminal device is a medium-orbit satellite type; the value of the satellite type indication is "OTHER_S AT", which can indicate that the type of satellite providing backhaul service for the single terminal device is other satellite types; the value of the satellite type indication is "DYNAMIC_GEO", which can indicate that the type of satellite providing backhaul service for the single terminal device is a dynamic high-orbit satellite type; the value of the satellite type indication is "DYNAMIC_MEO", which can indicate that the type of satellite providing backhaul service for the single terminal device is a dynamic medium-orbit satellite type; the value of the satellite type indication is "DYNAMIC_LEO", which can indicate that the type of satellite providing backhaul service for the single terminal device is a dynamic low-orbit satellite type; the value of the satellite type indication is "DYNAMIC_OTHER_SAT", which can indicate that the type of satellite providing backhaul service for the single terminal device is a dynamic other satellite type.

[0349] It should be noted that the single terminal device in step 701 and the optional implementation manner refers to a single terminal device using satellite services.

[0350] Step 702 : In response to receiving the first charging information, the first charging function network element 301 sends the first charging information to the second charging function network element 302 .

[0351] In some embodiments, the billing trigger function network element 303 can send the billing information of the single terminal device to the first billing function network element 301 in response to a billing trigger event of a data connection session of a single terminal device using satellite service being triggered. After receiving the first billing information, the first billing function network element 301 can immediately forward the first billing information to the second billing function network element 302.

[0352] In some embodiments, the charging trigger function network element 303 may send a charging request message to the first charging function network element 301, and the first charging function network element 301 may send a charging request message to the second charging function network element 302. In some embodiments, the first charging information may be carried in the charging request message sent by the charging trigger function network element 303 to the first charging function network element 301, and / or carried in the charging request message sent by the first charging function network element 301 to the second charging function network element 302. In some embodiments, the charging request message sent by the charging trigger function network element 303 to the first charging function network element 301, and / or the charging request message sent by the first charging function network element 301 to the second charging function network element 302, may also carry at least one of the following information:

[0353] First billing negotiation information, wherein the first billing negotiation information is used to negotiate a billing trigger event and / or a reporting category, wherein the reporting category includes immediate reporting and / or deferred reporting;

[0354] The second quota information is for the first network or a single terminal device, and includes second quota application information for applying for a quota and / or second quota usage information for notifying the used quota.

[0355] The first charging negotiation information is used to negotiate a charging trigger event and / or a reporting category between an MNO and an SNO or between an MNO and an SSP.

[0356] The charging triggering event is an event for triggering charging, and may refer to the charging triggering event of the data connection session of the above-mentioned single terminal device.

[0357] Among them, the meaning of immediate reporting is that, for the current billing event, the current count is closed, the billing information is sent immediately, and a new count is established at the same time; the meaning of deferred reporting is that, for the current billing event, the current count is closed and stored together with the billing information generated by the billing trigger function network element 303. The stored count will be sent to the second billing function network element 302 in the next billing request message, and the new count will be started by the billing trigger function network element 303.

[0358] In some embodiments, the first charging negotiation information may include at least one of the parameters shown in Table 3 below:

[0359] Table 3 Parameters included in the first billing negotiation information and their corresponding meanings

[0360] In some embodiments, taking the data connection session as a PDU session as an example, the charging trigger event and the reporting category may include at least one charging trigger event and the corresponding reporting category shown in Table 4:

[0361] Table 4 Billing trigger events and corresponding reporting categories

[0362] In some embodiments, the second quota information may be sent when at least one quota management condition shown in Table 5 below is satisfied:

[0363] Table 5 Quota management conditions and corresponding reporting categories

[0364] The charging trigger function network element 303 sends the second quota information to the first charging function network element 301, and the first charging function network element 301 forwards the second quota information to the second charging function network element 302 to apply for a quota from the second network or inform that the quota has been used, thereby achieving refined control of traffic.

[0365] In some embodiments, the first charging function network element 301 may determine which CHF network element the second charging function network element 302 is based on at least one of the following information:

[0366] 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 a data connection session of a terminal device; wherein the terminal device may refer to a single terminal device using a satellite service;

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

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

[0369] SMF locally provides billing feature information.

[0370] In some embodiments, the SMF may be the charging trigger function network element in the aforementioned embodiments.

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

[0372] 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.

[0373] In some embodiments, the first charging function network element 301 may determine the second charging function network element 302 in response to the start of establishment of a data connection session of a single terminal device using satellite services. For example, the first charging function network element 301 may determine the second charging function network element 302 during the establishment of the data connection session of the single terminal device.

[0374] In some embodiments, the first charging function network element 301 and the second charging function network element 302 may determine, through negotiation, a sending mode in which the first charging function network element 301 sends the first charging information to the second charging function network element 302 .

[0375] As a possible negotiation method, the first charging function network element 301 may send a second charging mode indication to the second charging function network element 302. The second charging mode indication is used to instruct the first charging function network element 301 to send the charging information of a single terminal device using satellite services to the second charging function network element 302 in response to receiving the charging information for the single terminal device. The charging information for the single terminal device is sent to the first charging function network element 301 by the charging trigger function network element 303 in response to a charging trigger event for the data connection session of the single terminal device being triggered. Furthermore, based on the second charging mode indication, the first charging function network element 301 may use the sending mode described in the embodiment of the present application to send the first charging information for the single terminal device to the second charging function network element 302. Optionally, the second charging mode indication sent by the first charging function network element 301 to the second charging function network element 302 may be included in the charging mode request sent by the first charging function network element 301 to the second charging function network element 302.

[0376] As another possible negotiation method, the second charging function network element 302 may send a second charging mode indication to the first charging function network element 301, wherein the second charging mode indication is used to instruct the first charging function network element 301 to send the charging information of a single terminal device using satellite services to the second charging function network element 302 in response to receiving the charging information for the single terminal device. The charging information of the single terminal is sent to the first charging function network element 301 by the charging trigger function network element 303 in response to a charging trigger event of a data connection session of the single terminal device being triggered. Accordingly, the first charging function network element 301 may receive the second charging mode indication sent by the second charging function network element 302. Thus, the first charging function network element 301 may send the first charging information for the single terminal device to the second charging function network element 302 based on the second charging mode indication using the sending mode shown in the embodiment of the present application. Optionally, the second charging mode indication sent by the second charging function network element 302 to the first charging function network element 301 may be carried in a charging mode response sent by the second charging function network element 302 to the first charging function network element 301 .

[0377] As another possible negotiation method, the first charging function network element 301 may send a second charging mode indication to the second charging function network element 302, and the second charging function network element 302 may return the second charging mode indication to the first charging function network element 301. The second charging mode indication is used to instruct the first charging function network element 301 to send the charging information of a single terminal device using satellite services to the second charging function network element 302 in response to receiving the charging information for the single terminal device. The charging information of the single terminal device is sent to the first charging function network element 301 by the charging trigger function network element 303 in response to a charging trigger event for the data connection session of the single terminal device. Therefore, the first charging function network element 301 can send the first charging information for the single terminal device to the second charging function network element 302 based on the second charging mode indication using the sending mode shown in the embodiment of the present application. Optionally, the second billing mode indication sent by the first billing function network element 301 to the second billing function network element 302 can be carried in the billing mode request sent by the first billing function network element 301 to the second billing function network element 302, and the second billing mode indication sent by the second billing function network element 302 to the first billing function network element 301 can be carried in the billing mode response returned by the second billing function network element 302 to the first billing function network element 301.

[0378] The optional implementation of step 702 can refer to the optional implementation of step 501 in Figure 5 and other related parts in the embodiment involved in Figure 5, and will not be repeated here.

[0379] Step 703: The second charging function network element 302 creates a first charging data record CDR based on the first charging information. The first CDR is used to generate a charging bill.

[0380] Among them, the optional implementation of step 703 can refer to the optional implementation of step 502 in Figure 5 and other related parts in the embodiment involved in Figure 5, and will not be repeated here.

[0381] In some embodiments, the first charging function network element 301 may also create a second CDR based on the first charging information received from the charging trigger function network element 303. The second CDR is used to generate the charging bill. The step of the first charging function network element 301 creating the second CDR and step 702 may be performed in a swapped order or simultaneously, and this application does not limit this. In some embodiments, the second CDR may include one or more of the first charging information.

[0382] The first billing function network element 301 creates a second CDR based on the first billing information provided by the billing trigger function network element 303, and the second billing function network element 302 creates a first CDR based on the first billing information forwarded by the first billing function network element. This can ensure that the first billing function network element 301 and the second billing function network element 302 are billed based on the same data, avoiding the problem of inconsistent billing results between the first network and the second network, and improving the accuracy of the billing results of satellite communications.

[0383] In some embodiments, the second charging function network element 302 may send a charging response message to the first charging function network element 301 , and the first charging function network element 301 may forward the charging response message to the charging triggering function network element 303 .

[0384] Among them, the second billing function network element 302 sends a billing response message to the first billing function network element 301, which can be executed in an alternate order or simultaneously with step 703. The first billing function network element 301 forwards the billing response message to the billing trigger function network element 303, which can be executed in an alternate order or simultaneously with step 702. This application does not impose any restrictions on this.

[0385] In some embodiments, the billing response message may include at least one of the following: first updated billing negotiation information, a second quota response message, wherein the second quota response message may be directed to the first network or a single terminal device. The parameters included in the second quota response message may refer to Table 1 and Table 2, which will not be repeated here. The first updated billing negotiation information is used to negotiate billing trigger events and / or reporting categories. For explanations of the first updated billing negotiation information, please refer to the first billing negotiation information, which will not be repeated here. It can be understood that the billing trigger events and / or reporting categories included in the first updated billing negotiation information will replace the billing trigger events and / or reporting categories in the first billing negotiation information originally set by the first billing function network element 301.

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

[0387] In summary, the billing method for satellite communication provided by the embodiment of the present disclosure is that the billing trigger function network element deployed in the first network can send first billing information of a terminal device using satellite services to the first billing function network element deployed in the first network, wherein the first billing information is billing information for a single terminal device using satellite services, and the first billing function network element can send the first billing information to the second billing function network element deployed in the second network in response to receiving the first billing information, so that the second billing function network element can generate a first CDR for generating a billing bill based on the first billing information provided by the billing trigger function network element, 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.

[0388] Figure 8 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 8, the method according to an embodiment of the present disclosure is applied to the satellite communications billing system 300 shown in Figure 4. This method, based on the method shown in Figure 7, further includes the following steps 801-804.

[0389] In step 801 , the charging triggering function network element 303 sends the charging information to be updated to the first charging function network element 301 .

[0390] The billing information to be updated is the billing information that needs to be updated and can be used to update the second CDR and the first CDR. The billing information to be updated can include updated information of one or more types of information included in the first billing information in the embodiment shown in FIG7 , which will not be described in detail here.

[0391] In some embodiments, the charging triggering function network element 303 may send the charging information to be updated to the first charging function network element 301 in response to establishment or modification of a data connection session of a single terminal device using satellite services.

[0392] In some embodiments, the charging trigger function network element 303 may send the charging information to be updated to the first charging function network element 301 in response to satisfying at least one of the following update trigger conditions:

[0393] 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;

[0394] The rate group limit is reached;

[0395] The quota limit was reached.

[0396] In some embodiments, in response to a change in charging conditions, the charging triggering function network element 303 sends charging information to be updated to the first charging function network element 301, which is applicable to converged charging scenarios and offline charging scenarios.

[0397] 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 charging trigger function network element 303 sends charging information to be updated to the first charging function network element 301, which is applicable to converged charging scenarios and offline charging scenarios.

[0398] In some embodiments, reaching a quota limit triggers quota management triggers. Optionally, the quota management triggers 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 CHF. In some embodiments, in response to reaching the quota limit, the charging trigger function network element 303 sends the charging information to be updated to the first charging function network element 301, which is applicable to converged billing scenarios.

[0399] In some embodiments, when the update trigger condition includes a change in billing conditions, the billing 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 billing information to be updated may include the satellite identification of the latest satellite providing satellite services.

[0400] In some embodiments, where the update triggering condition includes reaching a limit of a rate group, the billing information to be updated may include information related to the reached limit of the rate group.

[0401] In some embodiments, where the update triggering condition includes reaching a quota limit, the billing information to be updated may include information related to the reached quota limit.

[0402] In step 802, the first charging function network element 301 updates the second CDR based on the charging information to be updated.

[0403] Step 803 : The first charging function network element 301 forwards the charging information to be updated to the second charging function network element 302 .

[0404] In some embodiments, the billing trigger function network element 303 may send a billing update message to the first billing function network element 301, and the first billing function network element 301 may send a billing update message to the second billing function network element 302. The billing update message is used to request an update of the generated CDR. In some embodiments, the billing information to be updated may be carried in the billing update message sent by the billing trigger function network element 303 to the first billing function network element 301, and / or carried in the billing update message sent by the first billing function network element 301 to the second billing function network element 302. In some embodiments, the billing update message sent by the billing trigger function network element 303 to the first billing function network element 301, and / or the billing update message sent by the first billing function network element 301 to the second billing function network element 302, may also carry at least one of the following information:

[0405] Second billing negotiation information, wherein the second billing negotiation information is used to negotiate a billing trigger event and / or a reporting category, wherein the reporting category includes immediate reporting and / or deferred reporting;

[0406] The third quota information is for the first network or a single terminal device, and includes third quota application information for applying for a quota and / or third quota usage information for notifying the used quota.

[0407] The second charging negotiation information is used to negotiate charging trigger events and / or reporting categories between the MNO and the SNO or between the MNO and the SSP.

[0408] For explanations of the second billing negotiation information and the third quota information, please refer to the first billing negotiation information and the second quota information, which will not be repeated here.

[0409] The third quota information is sent to the first charging function network element 301 by the charging trigger function network element 303, and the first charging function network element 301 forwards the third quota information to the second charging function network element 302 to apply for a quota from the second network or inform that the quota has been used, thereby achieving refined control of traffic.

[0410] Step 804: The second charging function network element 302 updates the first CDR based on the charging information to be updated.

[0411] In some embodiments, the second charging function network element 302 may send a charging update response message to the first charging function network element 301, and the first charging function network element 301 may forward the charging update response message to the charging triggering function network element 303. The charging update response message is used to indicate that the CDR has been updated or that the charging information to be updated has been received.

[0412] Among them, the second billing function network element 302 sends a billing update response message to the first billing function network element 301, which can be executed in an alternate order or simultaneously with step 804. The first billing function network element 301 forwards the billing update response message to the billing trigger function network element 303, which can be executed in an alternate order or simultaneously with step 802. This application does not impose any restrictions on this.

[0413] In some embodiments, the billing update response message may include at least one of the following: second updated billing negotiation information, a third quota response message, wherein the third quota response message may be directed to the first network or a single terminal device. The parameters included in the third quota response message may refer to Table 1 and Table 2, which will not be repeated here. The second updated billing negotiation information is used to negotiate billing trigger events and / or reporting categories. For the explanation of the second updated billing negotiation information, reference may be made to the first billing negotiation information, which will not be repeated here. It can be understood that the billing trigger events and / or reporting categories included in the second updated billing negotiation information will replace the billing trigger events and / or reporting categories in the second billing negotiation information originally set by the first billing function network element 301.

[0414] In some embodiments, steps 801 - 804 may be performed after step 703 .

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

[0416] In summary, the billing method for satellite communication provided by the embodiment of the present disclosure sends the billing information to be updated to the first billing function network element through the billing triggering function network element, the first billing function network element updates the second CDR based on the billing information to be updated, the first billing function network element forwards the billing information to be updated to the second billing function network element, and the second billing function network element updates the first CDR based on the billing information to be updated, which can ensure the timeliness and consistency of the billing results generated by the first network and the second network.

[0417] Figure 9 is an interactive diagram illustrating 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 300 shown in Figure 4. Based on the satellite communications billing method shown in Figures 7 or 8, the method further includes the following steps 901-904.

[0418] Step 901 : The charging triggering function network element 303 sends a charging termination indication to the first charging function network element 301 .

[0419] The billing termination indication is used to indicate closing of the generated CDR.

[0420] In some embodiments, the charging trigger function network element 303 may send a charging termination indication to the first charging function network element 301 in response to detecting that an established data connection session of a single terminal device is released.

[0421] Step 902: The first charging function network element 301 closes the second CDR based on the charging termination indication.

[0422] Step 903 : The first charging function network element 301 forwards the charging termination instruction to the second charging function network element 302 .

[0423] Step 904: The second charging function network element 302 closes the first CDR based on the charging termination indication.

[0424] In some embodiments, the billing trigger function network element 303 may send a billing termination message to the first billing function network element 301, and the first billing function network element 301 may send a billing termination message to the second billing function network element 302. The billing termination message is used to request to close the generated CDR. In some embodiments, the billing termination indication may be carried in the billing termination message sent by the billing trigger function network element 303 to the first billing function network element 301, and / or carried in the billing termination message sent by the first billing function network element 301 to the second billing function network element 302. In some embodiments, the billing termination message sent by the billing trigger function network element 303 to the first billing function network element 301, and / or the billing termination message sent by the first billing function network element 301 to the second billing function network element 302, may also carry at least one of the following information:

[0425] Second billing information of a single terminal device using satellite service, used to update the first CDR and the second CDR;

[0426] Fourth quota information, wherein the fourth quota information is for the first network or a single terminal device, and the fourth quota information includes fourth quota application information for applying for a quota and / or fourth quota usage information for notifying the used quota.

[0427] For the explanation of the fourth quota information, please refer to the second quota information, which will not be repeated here.

[0428] The second billing information may be billing information for a single terminal device generated when the data connection session of the single terminal device is released. The information included in the second billing information can be configured as needed. For details, please refer to the first billing information in the embodiment shown in FIG. 7 , and will not be described in detail here. The embodiment of the present application does not limit the name of the second billing information, and may be, for example, "billing-related information," "information used for billing," or the like.

[0429] It can be understood that when the billing termination message carries the second billing information of a single terminal device using satellite services, the first billing function network element 301 can close the second CDR based on the billing termination indication after updating the second CDR based on the second billing information, and the second billing function network element 302 can close the first CDR based on the billing termination indication after updating the first CDR based on the second billing information.

[0430] In some embodiments, the second charging function network element 302 may send a charging termination response message to the first charging function network element 301, and the first charging function network element 301 may forward the charging termination response message to the charging triggering function network element 303. The charging update termination message is used to indicate that the CDR has been closed, or that a charging termination indication or charging termination message has been received.

[0431] Among them, the second billing function network element 302 sends a billing termination response message to the first billing function network element 301, which can be executed in an interchangeable order or simultaneously with step 904. The first billing function network element 301 forwards the billing termination response message to the billing trigger function network element 303, which can be executed in an interchangeable order or simultaneously with step 902. This application does not impose any restrictions on this.

[0432] In some embodiments, steps 901-904 may be performed after step 703 or after step 804, and this application does not impose any limitation on this.

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

[0434] The satellite communication billing method provided by the embodiment of the present disclosure includes a billing triggering function network element sending a billing termination indication to a first billing function network element, the first billing function network element closing a second CDR based on the billing termination indication, the first billing function network element forwarding the billing termination indication to a second billing function network element, and the second billing function network element closing the first CDR based on the billing termination indication, thereby ensuring that the second billing function network element and the first billing function network element stop billing in a timely manner to ensure the consistency of the billing results generated by the first network and the second network.

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

[0436] Step 1001: Send first billing information of a terminal device using satellite services to a second billing function network element deployed in a second network; wherein the first billing information is used to create or update a first charging data record CDR, and the first CDR is used to generate a billing bill.

[0437] In some embodiments, the method further comprises:

[0438] Determine that the terminal device accesses the first network through a satellite service.

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

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

[0441] In a billing method for satellite communications provided by an embodiment of the present disclosure, a first billing function network element deployed in a first network sends first billing information of a terminal device using satellite services to a second billing function network element deployed in a second network, wherein the first billing information is used to create or update a first billing data record CDR, and the first CDR is used to generate a billing bill. As a result, the second billing function network element deployed in the second network can generate a first CDR for generating a billing bill based on the first billing information provided by the first billing function 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.

[0442] 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 billing function network element deployed in a first network, and the method includes the following steps 1101 .

[0443] Step 1101: Send first billing information of a terminal device using satellite services to a second billing function network element deployed in a second network; wherein the first billing information is billing information about satellite communications for the first network, and the first billing information is used to create or update a first billing data record CDR, and the first CDR is used to generate a billing invoice.

[0444] 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.

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

[0446] an operator identifier of the first network;

[0447] an operator identifier of the second network;

[0448] an identifier of a satellite and / or an identifier of a constellation that provides satellite services to a terminal device using satellite services in the first network;

[0449] providing a satellite quality of service (QoS) of the satellite service to a terminal device using the satellite service in the first network;

[0450] a satellite service indication SSI corresponding to a terminal device using a satellite service in the first network, used to indicate that the corresponding terminal device accesses the first network via the satellite service;

[0451] a satellite service type indication corresponding to a terminal device using a satellite service in the first network, used to indicate whether the satellite service used by the corresponding terminal device is a backhaul service or a terminal direct connection service;

[0452] A satellite type indication corresponding to a terminal device using satellite services in the first network, used to indicate the type of satellite providing satellite services for the corresponding terminal device;

[0453] uplink data usage and / or downlink data usage corresponding to a terminal device using satellite services in the first network;

[0454] at least one of an identifier, a start time, an end time, and a duration of a data connection session of a terminal device using a satellite service in the first network;

[0455] the number of data connection sessions of terminal devices using the satellite service in the first network;

[0456] An identifier of a terminal device using a satellite service in a first network.

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

[0458] the total uplink data usage and / or the total downlink data usage corresponding to the terminal direct connection service in the first network;

[0459] a total uplink data usage and / or a total downlink data usage corresponding to the backhaul service in the first network;

[0460] the total uplink data usage and / or the total downlink data usage under each satellite category corresponding to the terminal direct connection service in the first network;

[0461] a total amount of uplink data usage and / or a total amount of downlink data usage for each satellite category corresponding to the backhaul service in the first network;

[0462] The total number of protocol data unit (PDU) connections and / or the total PDU connection duration corresponding to the terminal direct connection service in the first network;

[0463] The total number of PDU connections and / or the total duration of PDU connections corresponding to the backhaul service in the first network.

[0464] In some embodiments, the first billing information is sent in response to a set condition being satisfied, where the set condition includes at least one of the following:

[0465] The current time is the target sending time, and the interval between the target sending time and the previous sending time is the preset length;

[0466] receiving an information sending instruction, wherein the information sending instruction is used to instruct the first billing function network element to send first billing information;

[0467] The trigger event used to trigger the sending of billing information occurs.

[0468] In some embodiments, the first billing information is carried in a billing request message sent by the first billing function network element to the second billing function network element, and the billing request message also carries first quota information, wherein the first quota information is for the first network, and the first quota information includes first quota application information for applying for a quota, and / or first quota usage information for informing that the quota has been used.

[0469] In some embodiments, the method further comprises:

[0470] Sending a first billing mode indication to the second billing function network element;

[0471] The first charging mode indication is used to instruct the first charging function network element to send charging information about satellite communication for the first network.

[0472] In some embodiments, the method further comprises:

[0473] receiving a first billing mode indication sent by a second billing function network element;

[0474] The first charging mode indication is used to instruct the first charging function network element to send charging information about satellite communication for the first network.

[0475] The step of sending to the second charging function network element and / or receiving the first charging mode indication sent by the second charging function network element may be performed before step 1101 .

[0476] The satellite communication billing method provided by the embodiment of the present disclosure is that a first billing function network element deployed in a first network can send first billing information of a terminal device using satellite services to a second billing function network element deployed in a second network, wherein the first billing information is billing information about satellite communications for the first network, so that the second billing function network element deployed in the second network can generate a first CDR for generating a billing bill based on the first billing information provided by the first billing function 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. In addition, by having the first billing function network element send billing information about satellite communications for the first network to the second billing function network element, the first billing function network element is prevented from sending billing information of a single terminal device to the second billing function network element multiple times, saving signaling and resource overhead and simplifying the process of sending billing information.

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

[0478] Step 1201: Send first billing information of a terminal device using satellite services to a second billing function network element deployed in a second network; wherein the first billing information is billing information for a single terminal device using satellite services, and is sent to the first billing function network element by the billing trigger function network element in response to a billing trigger event of a data connection session of the single terminal device being triggered. The first billing information is used to create a first billing data record CDR, and the first CDR is used to generate a billing invoice.

[0479] In some embodiments, the first charging information is sent by the first charging function network element to the second charging function network element in response to receiving the charging information of the single terminal device.

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

[0481] an operator identifier of the first network;

[0482] The operator identifier of the second network;

[0483] The identification of the satellite and / or constellation providing the satellite service to the individual terminal device;

[0484] QoS of the satellite providing satellite services to a single terminal device;

[0485] A satellite service indication SSI corresponding to a single terminal device, used to indicate that the single terminal device accesses the first network via a satellite service;

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

[0487] The satellite type indication corresponding to a single terminal device is used to indicate the type of satellite providing satellite services;

[0488] Uplink data usage and / or downlink data usage corresponding to a single terminal device;

[0489] At least one of an identifier, a start time, an end time, and a duration of a data connection session of a single terminal device;

[0490] Identification of individual terminal devices;

[0491] QoS flow identifier.

[0492] In some embodiments, the first charging information is carried in a charging request message sent by the charging triggering function network element to the first charging function network element, and / or carried in a charging request message sent by the first charging function network element to the second charging function network element;

[0493] The charging request message sent by the charging triggering function network element to the first charging function network element, and / or the charging request message sent by the first charging function network element to the second charging function network element, further carries at least one of the following information:

[0494] First billing negotiation information, wherein the first billing negotiation information is used to negotiate a billing trigger event and / or a reporting category, wherein the reporting category includes immediate reporting and / or deferred reporting;

[0495] The second quota information is for the first network or a single terminal device, and includes second quota application information for applying for a quota and / or second quota usage information for notifying the used quota.

[0496] In some embodiments, the method further comprises:

[0497] The second charging function network element is determined based on at least one of the following information:

[0498] 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;

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

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

[0501] SMF locally provides billing feature information.

[0502] In some embodiments, the method further comprises:

[0503] A second CDR is created based on the first charging information received from the charging trigger function network element, and the second CDR is used to generate a charging bill.

[0504] In some embodiments, the method may further include:

[0505] Sending a second billing mode indication to the second billing function network element;

[0506] Among them, the second billing mode indication is used to instruct the first billing function network element to send the billing information of a single terminal device to the second billing function network element in response to receiving the billing information for a single terminal device using satellite services. The billing information of the single terminal is sent to the first billing function network element by the billing trigger function network element deployed in the first network in response to the billing trigger event of the data connection session of the single terminal device being triggered.

[0507] In some embodiments, the method may further include:

[0508] receiving a second billing mode indication sent by a second billing function network element;

[0509] Sending a second billing mode indication to the second billing function network element;

[0510] Among them, the second billing mode indication is used to instruct the first billing function network element to send the billing information of a single terminal device to the second billing function network element in response to receiving the billing information for a single terminal device using satellite services. The billing information of the single terminal is sent to the first billing function network element by the billing trigger function network element deployed in the first network in response to the billing trigger event of the data connection session of the single terminal device being triggered.

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

[0512] In the billing method for satellite communications provided by the embodiment of the present disclosure, a first billing function network element deployed in a first network can forward the first billing information sent by a billing trigger function network element to a second billing function network element deployed in a second network, wherein the first billing information is billing information for a single terminal device using satellite services, so that the second billing function network element can generate a first CDR for generating a billing bill based on the first billing information provided by the billing trigger function network element, 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.

[0513] Figure 13 is a flow chart illustrating a satellite communications 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 billing function network element deployed in a first network. In addition to the method shown in Figure 12, the method further includes the following steps 1301-1303.

[0514] Step 1301: Receive the billing information to be updated sent by the billing trigger function network element.

[0515] Step 1302: Update the second CDR based on the billing information to be updated.

[0516] Step 1303: Forward the billing information to be updated to the second charging function network element, where the billing information to be updated is used to update the first CDR.

[0517] In some embodiments, the billing information to be updated is carried in a billing update message sent by the billing triggering function network element to the first billing function network element, and / or carried in a billing update message sent by the first billing function network element to the second billing function network element;

[0518] The charging update message sent by the charging triggering function network element to the first charging function network element, and / or the charging update message sent by the first charging function network element to the second charging function network element, further carries at least one of the following information:

[0519] Second billing negotiation information, wherein the second billing negotiation information is used to negotiate a billing trigger event and / or a reporting category, wherein the reporting category includes immediate reporting and / or deferred reporting;

[0520] The third quota information is for the first network or a single terminal device, and includes third quota application information for applying for a quota and / or third quota usage information for notifying the used quota.

[0521] In some embodiments, the charging information to be updated is sent by the charging trigger function network element in response to satisfying at least one of the following update trigger conditions:

[0522] 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;

[0523] The rate group limit is reached;

[0524] The quota limit was reached.

[0525] Among them, steps 1302 and 1303 can be executed in an interchanged order or simultaneously, and this application does not impose any restrictions on this.

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

[0527] The satellite communication billing method provided by the embodiment of the present disclosure updates the second CDR based on the billing information to be updated sent by the billing triggering function network element through the first billing function network element deployed in the first network, and forwards the billing information to be updated to the second billing function network element deployed in the second network, so that the second billing function network element can update the first CDR based on the billing information to be updated, thereby ensuring the timeliness and consistency of the billing results generated by the first network and the second network.

[0528] Figure 14 is a flow chart illustrating a satellite communications billing method according to an embodiment of the present disclosure. As shown in Figure 14, the method according to an embodiment of the present disclosure is applied to a first billing function network element deployed in a first network. In addition to the method shown in Figures 12 or 13, the method further includes the following steps 1401-1403.

[0529] Step 1401: Receive a charging termination indication sent by a charging trigger function network element.

[0530] Step 1402: Based on the charging termination indication, close the second CDR.

[0531] Step 1403: Forward the charging termination instruction to the second charging function network element, where the charging termination instruction is used to close the first CDR.

[0532] In some embodiments, the charging termination indication is carried in a charging termination message sent by the charging trigger function to the first charging function network element, and / or carried in a charging termination message sent by the first charging function network element to the second charging function network element;

[0533] The charging termination message sent by the charging trigger function to the first charging function network element, and / or the charging termination message sent by the first charging function network element to the second charging function network element, further carries at least one of the following information:

[0534] Second billing information of a single terminal device, used to update the first CDR and the second CDR;

[0535] Fourth quota information, wherein the fourth quota information is for the first network or a single terminal device, and the fourth quota information includes fourth quota application information for applying for a quota and / or fourth quota usage information for notifying the used quota.

[0536] Among them, steps 1402 and 1403 can be executed in an interchanged order or simultaneously, and this application does not impose any restrictions on this.

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

[0538] The satellite communication billing method provided by the embodiment of the present disclosure closes the second CDR based on the billing termination indication sent by the billing triggering function network element through a first billing function network element deployed in the first network, and forwards the billing termination indication to a second billing function network element deployed in the second network, so that the second billing function network element can close the first CDR based on the billing termination indication, thereby ensuring that the second billing function network element and the first billing function network element stop billing in time to ensure the consistency of the billing results generated by the first network and the second network.

[0539] 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 second billing function network element deployed in a first network, and includes the following steps 1501-1502.

[0540] Step 1501: Receive first billing information of a terminal device using satellite services sent by a first billing function network element deployed in a first network.

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

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

[0543] Step 1502: Create or update a first charging data record CDR based on the first charging information. The first CDR is used to generate a charging bill.

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

[0545] The billing method for satellite communications provided by the embodiment of the present disclosure receives first billing information of a terminal device using satellite services sent by a first billing function network element deployed in a first network through a second billing function network element deployed in a second network, and creates or updates a first billing data record CDR based on the first billing information. The first CDR is used to generate a billing bill, so that the second billing function network element deployed in the second network can generate a first CDR for generating a billing bill based on the first billing information provided by the first billing function 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.

[0546] Figure 16 is a flow chart of a satellite communication 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 second billing function network element deployed in a first network, and includes the following steps 1601-1602.

[0547] Step 1601: Receive first billing information of a terminal device using satellite services sent by a first billing function network element deployed in a first network, wherein the first billing information is billing information about satellite communications for the first network.

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

[0549] an operator identifier of the first network;

[0550] an operator identifier of the second network;

[0551] an identifier of a satellite and / or an identifier of a constellation that provides satellite services to a terminal device using satellite services in the first network;

[0552] providing a satellite quality of service (QoS) of the satellite service to a terminal device using the satellite service in the first network;

[0553] a satellite service indication SSI corresponding to a terminal device using a satellite service in the first network, used to indicate that the corresponding terminal device accesses the first network via the satellite service;

[0554] a satellite service type indication corresponding to a terminal device using a satellite service in the first network, used to indicate whether the satellite service used by the corresponding terminal device is a backhaul service or a terminal direct connection service;

[0555] A satellite type indication corresponding to a terminal device using satellite services in the first network, used to indicate the type of satellite providing satellite services for the corresponding terminal device;

[0556] uplink data usage and / or downlink data usage corresponding to a terminal device using satellite services in the first network;

[0557] at least one of an identifier, a start time, an end time, and a duration of a data connection session of a terminal device using a satellite service in the first network;

[0558] the number of data connection sessions of terminal devices using the satellite service in the first network;

[0559] An identifier of a terminal device using a satellite service in a first network.

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

[0561] the total uplink data usage and / or the total downlink data usage corresponding to the terminal direct connection service in the first network;

[0562] a total uplink data usage and / or a total downlink data usage corresponding to the backhaul service in the first network;

[0563] the total uplink data usage and / or the total downlink data usage under each satellite category corresponding to the terminal direct connection service in the first network;

[0564] a total amount of uplink data usage and / or a total amount of downlink data usage for each satellite category corresponding to the backhaul service in the first network;

[0565] The total number of protocol data unit (PDU) connections and / or the total PDU connection duration corresponding to the terminal direct connection service in the first network;

[0566] The total number of PDU connections and / or the total duration of PDU connections corresponding to the backhaul service in the first network.

[0567] In some embodiments, the first billing information is sent in response to a set condition being satisfied, where the set condition includes at least one of the following:

[0568] The current time is the target sending time, and the interval between the target sending time and the previous sending time is the preset length;

[0569] receiving an information sending instruction, wherein the information sending instruction is used to instruct the first billing function network element to send first billing information;

[0570] The trigger event used to trigger the sending of billing information occurs.

[0571] In some embodiments, the first billing information is carried in a billing request message sent by the first billing function network element to the second billing function network element, and the billing request message also carries first quota information, wherein the first quota information is for the first network, and the first quota information includes first quota application information for applying for a quota, and / or first quota usage information for informing that the quota has been used.

[0572] In some embodiments, the method further comprises:

[0573] receiving a first billing mode indication sent by a first billing function network element;

[0574] The first charging mode indication is used to instruct the first charging function network element to send charging information about satellite communication for the first network.

[0575] In some embodiments, the method further comprises:

[0576] Sending a first billing mode indication to the first billing function network element;

[0577] The first charging mode indication is used to instruct the first charging function network element to send charging information about satellite communication for the first network.

[0578] Step 1602: Create or update a first charging data record CDR based on the first charging information. The first CDR is used to generate a charging bill.

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

[0580] The satellite communications billing method provided by the embodiments of the present disclosure includes a method in which a second billing function network element deployed in a second network receives first billing information for a terminal device using satellite services, sent by a first billing function network element deployed in a first network. The first billing information is billing information regarding satellite communications for the first network. Based on the first billing information, a first charging data record (CDR) is created or updated. The first CDR is used to generate a billing invoice. This method enables the second billing function network element to generate the first CDR for generating the billing invoice based on the first billing information provided by the first billing function network element, 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, by receiving the billing information regarding satellite communications for the first network sent by the first billing function network element through the second billing function network element, the second billing function network element avoids having to receive billing information for a single terminal device sent by the first billing function network element multiple times, saving signaling and resource overhead and simplifying the billing information transmission process.

[0581] Figure 17 is a flow chart of a satellite communication 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 second billing function network element deployed in a first network, and includes the following steps 1701-1702.

[0582] Step 1701: Receive first billing information of a terminal device using satellite services sent by a first billing function network element deployed in a first network, wherein the first billing information is billing information for a single terminal device using satellite services, and is sent to the first billing function network element by a billing trigger function network element deployed in the first network in response to a billing trigger event of a data connection session of the single terminal device being triggered.

[0583] In some embodiments, the first charging information may be sent by the first charging function network element to the second charging function network element in response to receiving the charging information of the single terminal device.

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

[0585] an operator identifier of the first network;

[0586] an operator identifier of the second network;

[0587] The identification of the satellite and / or constellation providing the satellite service to the individual terminal device;

[0588] QoS of the satellite providing satellite services to a single terminal device;

[0589] A satellite service indication SSI corresponding to a single terminal device, used to indicate that the single terminal device accesses the first network via a satellite service;

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

[0591] The satellite type indication corresponding to a single terminal device is used to indicate the type of satellite providing satellite services;

[0592] Uplink data usage and / or downlink data usage corresponding to a single terminal device;

[0593] At least one of an identifier, a start time, an end time, and a duration of a data connection session of a single terminal device;

[0594] Identification of individual terminal devices;

[0595] QoS flow identifier.

[0596] In some embodiments, the first charging information is carried in a charging request message sent by the charging triggering function network element to the first charging function network element, and / or carried in a charging request message sent by the first charging function network element to the second charging function network element;

[0597] The charging request message sent by the charging triggering function network element to the first charging function network element, and / or the charging request message sent by the first charging function network element to the second charging function network element, further carries at least one of the following information:

[0598] First billing negotiation information, wherein the first billing negotiation information is used to negotiate a billing trigger event and / or a reporting category, wherein the reporting category includes immediate reporting and / or deferred reporting;

[0599] The second quota information is for the first network or a single terminal device, and includes second quota application information for applying for a quota and / or second quota usage information for notifying the used quota.

[0600] In some embodiments, the second charging function network element is determined based on at least one of the following information:

[0601] 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;

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

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

[0604] SMF locally provides billing feature information.

[0605] In some embodiments, the method further comprises:

[0606] receiving a second billing mode indication sent by the first billing function network element;

[0607] Among them, the second billing mode indication is used to instruct the first billing function network element to send the billing information of a single terminal device to the second billing function network element in response to receiving the billing information for a single terminal device using satellite services. The billing information of the single terminal is sent to the first billing function network element by the billing trigger function network element deployed in the first network in response to the billing trigger event of the data connection session of the single terminal device being triggered.

[0608] In some embodiments, the method further comprises:

[0609] Sending a second billing mode indication to the first billing function network element;

[0610] Among them, the second billing mode indication is used to instruct the first billing function network element to send the billing information of a single terminal device to the second billing function network element in response to receiving the billing information for a single terminal device using satellite services. The billing information of the single terminal is sent to the first billing function network element by the billing trigger function network element deployed in the first network in response to the billing trigger event of the data connection session of the single terminal device being triggered.

[0611] Step 1702: Create a first charging data record (CDR) based on the first charging information. The first CDR is used to generate a charging bill.

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

[0613] The billing method for satellite communication provided by the embodiment of the present disclosure receives, through the second billing function network element, first billing information of a terminal device using satellite service sent by the first billing function network element, wherein the first billing information is billing information for a single terminal device using satellite service, and is sent to the first billing function network element by the billing trigger function network element in response to a billing trigger event of a data connection session of the single terminal device being triggered, and the second billing function network element creates or updates a first billing data record CDR based on the first billing information, and the first CDR is used to generate a billing bill, so that the second billing function network element can generate the first CDR for generating a billing bill based on the first billing information provided by the billing trigger function network element, 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 communication.

[0614] Figure 18 is a flow chart illustrating a satellite communications 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 billing function network element deployed in a first network. The method, based on that shown in Figure 17 , further includes the following steps 1801-1802.

[0615] Step 1801: Receive the billing information to be updated forwarded by the first charging function network element, wherein the billing information to be updated is sent by the charging triggering function network element to the first charging function network element.

[0616] Step 1802: Update the first CDR based on the billing information to be updated.

[0617] In some embodiments, the billing information to be updated is carried in a billing update message sent by the billing triggering function network element to the first billing function network element, and / or carried in a billing update message sent by the first billing function network element to the second billing function network element;

[0618] The charging update message sent by the charging triggering function network element to the first charging function network element, and / or the charging update message sent by the first charging function network element to the second charging function network element, further carries at least one of the following information:

[0619] Second billing negotiation information, wherein the second billing negotiation information is used to negotiate a billing trigger event and / or a reporting category, wherein the reporting category includes immediate reporting and / or deferred reporting;

[0620] The third quota information is for the first network or a single terminal device, and includes third quota application information for applying for a quota and / or third quota usage information for notifying the used quota.

[0621] In some embodiments, the charging information to be updated is sent by the charging trigger function network element in response to satisfying at least one of the following update trigger conditions:

[0622] 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;

[0623] The rate group limit is reached;

[0624] The quota limit was reached.

[0625] 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.

[0626] The satellite communication billing method provided by the embodiment of the present disclosure comprises the following steps: the second billing function network element receives the billing information to be updated forwarded by the first billing function network element, and updates the first CDR based on the billing information to be updated. The billing information to be updated is sent by the billing trigger function network element to the first billing function network element, so that the second billing function network element can update the first CDR based on the billing information to be updated, thereby ensuring the timeliness of the billing results generated by the second network.

[0627] Figure 19 is a flow chart illustrating a satellite communications 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 billing function network element deployed in a first network. The method, in addition to that shown in Figures 17 or 18, further includes the following steps 1901-1902.

[0628] Step 1901: Receive a charging termination instruction forwarded by a first charging function network element, wherein the charging termination instruction is sent by a charging triggering function network element to the first charging function network element.

[0629] Step 1902: Based on the charging termination indication, close the first CDR.

[0630] In some embodiments, the charging termination indication is carried in a charging termination message sent by the charging trigger function to the first charging function network element, and / or carried in a charging termination message sent by the first charging function network element to the second charging function network element;

[0631] The charging termination message sent by the charging trigger function to the first charging function network element, and / or the charging termination message sent by the first charging function network element to the second charging function network element, further carries at least one of the following information:

[0632] Second billing information of a single terminal device, used to update the first CDR and the second CDR;

[0633] Fourth quota information, wherein the fourth quota information is for the first network or a single terminal device, and the fourth quota information includes fourth quota application information for applying for a quota and / or fourth quota usage information for notifying the used quota.

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

[0635] The satellite communication billing method provided by the embodiment of the present disclosure receives the billing termination indication forwarded by the first billing function network element through the second billing function network element, and closes the first CDR based on the billing termination indication, wherein the billing termination indication is sent by the billing triggering function network element to the first billing function network element, so that the second billing function network element can close the first CDR in time based on the billing termination indication, thereby ensuring that the second billing function network element stops billing in time.

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

[0637] 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.

[0638] 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.

[0639] Figure 20 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 billing function network element in the aforementioned embodiment. As shown in Figure 20 , the satellite communication billing device 2000 may include at least one of a transceiver module 2001 and a processing module 2002.

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

[0641] In some embodiments, the processing module 2002 is configured to determine whether the terminal device accesses the first network via a satellite service.

[0642] In some embodiments, the first billing information is billing information regarding satellite communications for the first network.

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

[0644] an operator identifier of the first network;

[0645] an operator identifier of the second network;

[0646] an identifier of a satellite and / or an identifier of a constellation that provides satellite services to a terminal device using satellite services in the first network;

[0647] providing a satellite quality of service (QoS) of the satellite service to a terminal device using the satellite service in the first network;

[0648] a satellite service indication SSI corresponding to a terminal device using a satellite service in the first network, used to indicate that the corresponding terminal device accesses the first network via the satellite service;

[0649] a satellite service type indication corresponding to a terminal device using a satellite service in the first network, used to indicate whether the satellite service used by the corresponding terminal device is a backhaul service or a terminal direct connection service;

[0650] A satellite type indication corresponding to a terminal device using satellite services in the first network, used to indicate the type of satellite providing satellite services for the corresponding terminal device;

[0651] uplink data usage and / or downlink data usage corresponding to a terminal device using satellite services in the first network;

[0652] at least one of an identifier, a start time, an end time, and a duration of a data connection session of a terminal device using a satellite service in the first network;

[0653] the number of data connection sessions of terminal devices using the satellite service in the first network;

[0654] An identifier of a terminal device using a satellite service in a first network.

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

[0656] the total uplink data usage and / or the total downlink data usage corresponding to the terminal direct connection service in the first network;

[0657] a total uplink data usage and / or a total downlink data usage corresponding to the backhaul service in the first network;

[0658] the total uplink data usage and / or the total downlink data usage under each satellite category corresponding to the terminal direct connection service in the first network;

[0659] a total amount of uplink data usage and / or a total amount of downlink data usage for each satellite category corresponding to the backhaul service in the first network;

[0660] The total number of protocol data unit (PDU) connections and / or the total PDU connection duration corresponding to the terminal direct connection service in the first network;

[0661] The total number of PDU connections and / or the total duration of PDU connections corresponding to the backhaul service in the first network.

[0662] In some embodiments, the first billing information is sent in response to a set condition being satisfied, where the set condition includes at least one of the following:

[0663] The current time is the target sending time, and the interval between the target sending time and the previous sending time is the preset length;

[0664] receiving an information sending instruction, wherein the information sending instruction is used to instruct the first billing function network element to send first billing information;

[0665] The trigger event used to trigger the sending of billing information occurs.

[0666] In some embodiments, the first billing information is carried in a billing request message sent by the first billing function network element to the second billing function network element, and the billing request message also carries first quota information, wherein the first quota information is for the first network, and the first quota information includes first quota application information for applying for a quota, and / or first quota usage information for informing that the quota has been used.

[0667] In some embodiments, the transceiver module 2001 is configured to:

[0668] Sending a first billing mode indication to the second billing function network element;

[0669] The first charging mode indication is used to instruct the first charging function network element to send charging information about satellite communication for the first network.

[0670] In some embodiments, the transceiver module 2001 is configured to:

[0671] receiving a first billing mode indication sent by a second billing function network element;

[0672] The first charging mode indication is used to instruct the first charging function network element to send charging information about satellite communication for the first network.

[0673] In some embodiments, the first billing information is billing information for a single terminal device using satellite services, and is sent by a billing trigger function network element deployed in the first network to a first billing function network element in response to a billing trigger event of a data connection session of the single terminal device being triggered, and is sent by the first billing function network element to a second billing function network element in response to receiving the billing information of the single terminal device.

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

[0675] an operator identifier of the first network;

[0676] an operator identifier of the second network;

[0677] The identification of the satellite and / or constellation providing the satellite service to the individual terminal device;

[0678] QoS of the satellite providing satellite services to a single terminal device;

[0679] A satellite service indication SSI corresponding to a single terminal device, used to indicate that the single terminal device accesses the first network via a satellite service;

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

[0681] The satellite type indication corresponding to a single terminal device is used to indicate the type of satellite providing satellite services;

[0682] Uplink data usage and / or downlink data usage corresponding to a single terminal device;

[0683] At least one of an identifier, a start time, an end time, and a duration of a data connection session of a single terminal device;

[0684] Identification of individual terminal devices;

[0685] QoS flow identifier.

[0686] In some embodiments, the first charging information is carried in a charging request message sent by the charging triggering function network element to the first charging function network element, and / or carried in a charging request message sent by the first charging function network element to the second charging function network element;

[0687] The charging request message sent by the charging triggering function network element to the first charging function network element, and / or the charging request message sent by the first charging function network element to the second charging function network element, further carries at least one of the following information:

[0688] First billing negotiation information, wherein the first billing negotiation information is used to negotiate a billing trigger event and / or a reporting category, wherein the reporting category includes immediate reporting and / or deferred reporting;

[0689] The second quota information is for the first network or a single terminal device, and includes second quota application information for applying for a quota and / or second quota usage information for notifying the used quota.

[0690] In some embodiments, the processing module 2002 is configured to determine the second charging function network element based on at least one of the following information:

[0691] 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;

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

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

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

[0695] In some embodiments, the processing module 2002 is configured to:

[0696] A second CDR is created based on the first charging information received from the charging trigger function network element, and the second CDR is used to generate a charging bill.

[0697] In some embodiments, the transceiver module 2001 is configured to receive billing information to be updated sent by a billing trigger function network element;

[0698] Processing module 2002, configured to update the second CDR based on the billing information to be updated;

[0699] The transceiver module 2001 is used to forward the billing information to be updated to the second billing function network element, and the billing information to be updated is used to update the first CDR.

[0700] In some embodiments, the billing information to be updated is carried in a billing update message sent by the billing triggering function network element to the first billing function network element, and / or carried in a billing update message sent by the first billing function network element to the second billing function network element;

[0701] The charging update message sent by the charging triggering function network element to the first charging function network element, and / or the charging update message sent by the first charging function network element to the second charging function network element, further carries at least one of the following information:

[0702] Second billing negotiation information, wherein the second billing negotiation information is used to negotiate a billing trigger event and / or a reporting category, wherein the reporting category includes immediate reporting and / or deferred reporting;

[0703] The third quota information is for the first network or a single terminal device, and includes third quota application information for applying for a quota and / or third quota usage information for notifying the used quota.

[0704] In some embodiments, the charging information to be updated is sent by the charging trigger function network element in response to satisfying at least one of the following update trigger conditions:

[0705] 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;

[0706] The rate group limit is reached;

[0707] The quota limit was reached.

[0708] In some embodiments, the transceiver module 2001 is configured to receive a charging termination indication sent by a charging trigger function network element;

[0709] The processing module 2002 is configured to close the second CDR based on the charging termination indication;

[0710] The transceiver module 2001 is configured to forward a charging termination instruction to the second charging function network element, where the charging termination instruction is used to close the first CDR.

[0711] In some embodiments, the charging termination indication is carried in a charging termination message sent by the charging trigger function to the first charging function network element, and / or carried in a charging termination message sent by the first charging function network element to the second charging function network element;

[0712] The charging termination message sent by the charging trigger function to the first charging function network element, and / or the charging termination message sent by the first charging function network element to the second charging function network element, further carries at least one of the following information:

[0713] Second billing information of a single terminal device, used to update the first CDR and the second CDR;

[0714] Fourth quota information, wherein the fourth quota information is for the first network or a single terminal device, and the fourth quota information includes fourth quota application information for applying for a quota and / or fourth quota usage information for notifying the used quota.

[0715] In some embodiments, the transceiver module 2001 is configured to:

[0716] Sending a second billing mode indication to the second billing function network element;

[0717] Among them, the second billing mode indication is used to instruct the first billing function network element to send the billing information of a single terminal device to the second billing function network element in response to receiving the billing information for a single terminal device using satellite services. The billing information of the single terminal is sent to the first billing function network element by the billing trigger function network element deployed in the first network in response to the billing trigger event of the data connection session of the single terminal device being triggered.

[0718] In some embodiments, the transceiver module 2001 is configured to:

[0719] receiving a second billing mode indication sent by a second billing function network element;

[0720] Among them, the second billing mode indication is used to instruct the first billing function network element to send the billing information of a single terminal device to the second billing function network element in response to receiving the billing information for a single terminal device using satellite services. The billing information of the single terminal is sent to the first billing function network element by the billing trigger function network element deployed in the first network in response to the billing trigger event of the data connection session of the single terminal device being triggered.

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

[0722] 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 second billing function 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.

[0723] In some embodiments, the transceiver module 2101 is used to receive first billing information of a terminal device using satellite services sent by a first billing function network element deployed in a first network; the processing module 2102 is used to create or update a first billing data record CDR based on the first billing information, and the first CDR is used to generate a billing bill.

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

[0725] In some embodiments, the first billing information is billing information regarding satellite communications for the first network.

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

[0727] an operator identifier of the first network;

[0728] an operator identifier of the second network;

[0729] an identifier of a satellite and / or an identifier of a constellation that provides satellite services to a terminal device using satellite services in the first network;

[0730] providing a satellite quality of service (QoS) of the satellite service to a terminal device using the satellite service in the first network;

[0731] a satellite service indication SSI corresponding to a terminal device using a satellite service in the first network, used to indicate that the corresponding terminal device accesses the first network via the satellite service;

[0732] a satellite service type indication corresponding to a terminal device using a satellite service in the first network, used to indicate whether the satellite service used by the corresponding terminal device is a backhaul service or a terminal direct connection service;

[0733] A satellite type indication corresponding to a terminal device using satellite services in the first network, used to indicate the type of satellite providing satellite services for the corresponding terminal device;

[0734] uplink data usage and / or downlink data usage corresponding to a terminal device using satellite services in the first network;

[0735] at least one of an identifier, a start time, an end time, and a duration of a data connection session of a terminal device using a satellite service in the first network;

[0736] the number of data connection sessions of terminal devices using the satellite service in the first network;

[0737] An identifier of a terminal device using a satellite service in a first network.

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

[0739] the total uplink data usage and / or the total downlink data usage corresponding to the terminal direct connection service in the first network;

[0740] a total uplink data usage and / or a total downlink data usage corresponding to the backhaul service in the first network;

[0741] the total uplink data usage and / or the total downlink data usage under each satellite category corresponding to the terminal direct connection service in the first network;

[0742] a total amount of uplink data usage and / or a total amount of downlink data usage for each satellite category corresponding to the backhaul service in the first network;

[0743] The total number of protocol data unit (PDU) connections and / or the total PDU connection duration corresponding to the terminal direct connection service in the first network;

[0744] The total number of PDU connections and / or the total duration of PDU connections corresponding to the backhaul service in the first network.

[0745] In some embodiments, the first billing information is sent in response to a set condition being satisfied, where the set condition includes at least one of the following:

[0746] The current time is the target sending time, and the interval between the target sending time and the previous sending time is the preset length;

[0747] receiving an information sending instruction, wherein the information sending instruction is used to instruct the first billing function network element to send first billing information;

[0748] The trigger event used to trigger the sending of billing information occurs.

[0749] In some embodiments, the first billing information is carried in a billing request message sent by the first billing function network element to the second billing function network element, and the billing request message also carries first quota information, wherein the first quota information is for the first network, and the first quota information includes first quota application information for applying for a quota, and / or first quota usage information for informing that the quota has been used.

[0750] In some embodiments, the transceiver module 2101 is configured to:

[0751] receiving a first billing mode indication sent by a first billing function network element;

[0752] The first charging mode indication is used to instruct the first charging function network element to send charging information about satellite communication for the first network.

[0753] In some embodiments, the transceiver module 2101 is configured to:

[0754] Sending a first billing mode indication to the first billing function network element;

[0755] The first charging mode indication is used to instruct the first charging function network element to send charging information about satellite communication for the first network.

[0756] In some embodiments, the first billing information is billing information for a single terminal device using satellite services, and is sent by a billing trigger function network element deployed in the first network to a first billing function network element in response to a billing trigger event of a data connection session of the single terminal device being triggered, and is sent by the first billing function network element to a second billing function network element in response to receiving the billing information of the single terminal device.

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

[0758] an operator identifier of the first network;

[0759] an operator identifier of the second network;

[0760] The identification of the satellite and / or constellation providing the satellite service to the individual terminal device;

[0761] QoS of the satellite providing satellite services to a single terminal device;

[0762] A satellite service indication SSI corresponding to a single terminal device, used to indicate that the single terminal device accesses the first network via a satellite service;

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

[0764] The satellite type indication corresponding to a single terminal device is used to indicate the type of satellite providing satellite services;

[0765] Uplink data usage and / or downlink data usage corresponding to a single terminal device;

[0766] At least one of an identifier, a start time, an end time, and a duration of a data connection session of a single terminal device;

[0767] Identification of individual terminal devices;

[0768] QoS flow identifier.

[0769] In some embodiments, the first charging information is carried in a charging request message sent by the charging triggering function network element to the first charging function network element, and / or carried in a charging request message sent by the first charging function network element to the second charging function network element;

[0770] The charging request message sent by the charging triggering function network element to the first charging function network element, and / or the charging request message sent by the first charging function network element to the second charging function network element, further carries at least one of the following information:

[0771] First billing negotiation information, wherein the first billing negotiation information is used to negotiate a billing trigger event and / or a reporting category, wherein the reporting category includes immediate reporting and / or deferred reporting;

[0772] The second quota information is for the first network or a single terminal device, and includes second quota application information for applying for a quota and / or second quota usage information for notifying the used quota.

[0773] In some embodiments, the second charging function network element is determined based on at least one of the following information:

[0774] 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;

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

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

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

[0778] In some embodiments, the transceiver module 2101 is configured to receive billing information to be updated forwarded by the first billing function network element, wherein the billing information to be updated is sent by the billing triggering function network element to the first billing function network element;

[0779] The processing module 2102 is configured to update the first CDR based on the billing information to be updated.

[0780] In some embodiments, the billing information to be updated is carried in a billing update message sent by the billing triggering function network element to the first billing function network element, and / or carried in a billing update message sent by the first billing function network element to the second billing function network element;

[0781] The charging update message sent by the charging triggering function network element to the first charging function network element, and / or the charging update message sent by the first charging function network element to the second charging function network element, further carries at least one of the following information:

[0782] Second billing negotiation information, wherein the second billing negotiation information is used to negotiate a billing trigger event and / or a reporting category, wherein the reporting category includes immediate reporting and / or deferred reporting;

[0783] The third quota information is for the first network or a single terminal device, and includes third quota application information for applying for a quota and / or third quota usage information for notifying the used quota.

[0784] In some embodiments, the charging information to be updated is sent by the charging trigger function network element in response to satisfying at least one of the following update trigger conditions:

[0785] 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;

[0786] The rate group limit is reached;

[0787] The quota limit was reached.

[0788] In some embodiments, the transceiver module 2101 is configured to receive a charging termination instruction forwarded by the first charging function network element, wherein the charging termination instruction is sent by the charging triggering function network element to the first charging function network element;

[0789] The processing module 2102 is configured to close the first CDR based on the charging termination indication.

[0790] In some embodiments, the charging termination indication is carried in a charging termination message sent by the charging trigger function to the first charging function network element, and / or carried in a charging termination message sent by the first charging function network element to the second charging function network element;

[0791] The charging termination message sent by the charging trigger function to the first charging function network element, and / or the charging termination message sent by the first charging function network element to the second charging function network element, further carries at least one of the following information:

[0792] Second billing information of a single terminal device, used to update the first CDR and the second CDR;

[0793] Fourth quota information, wherein the fourth quota information is for the first network or a single terminal device, and the fourth quota information includes fourth quota application information for applying for a quota and / or fourth quota usage information for notifying the used quota.

[0794] In some embodiments, the transceiver module 2101 is configured to:

[0795] receiving a second billing mode indication sent by the first billing function network element;

[0796] Among them, the second billing mode indication is used to instruct the first billing function network element to send the billing information of a single terminal device to the second billing function network element in response to receiving the billing information for a single terminal device using satellite services. The billing information of the single terminal is sent to the first billing function network element by the billing trigger function network element deployed in the first network in response to the billing trigger event of the data connection session of the single terminal device being triggered.

[0797] In some embodiments, the transceiver module 2101 is configured to:

[0798] Sending a second billing mode indication to the first billing function network element;

[0799] Among them, the second billing mode indication is used to instruct the first billing function network element to send the billing information of a single terminal device to the second billing function network element in response to receiving the billing information for a single terminal device using satellite services. The billing information of the single terminal is sent to the first billing function network element by the billing trigger function network element deployed in the first network in response to the billing trigger event of the data connection session of the single terminal device being triggered.

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

[0801] Figure 22 is a schematic diagram of the structure of an electronic device 2200 proposed in an embodiment of the present disclosure. Electronic device 2200 can be the first billing function network element described above, or the second billing function network element described above, or a chip, chip system, or processor that supports the first billing function network element in implementing any of the above methods, or a chip, chip system, or processor that supports the second billing function network element in implementing any of the above methods. Electronic device 2200 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.

[0802] As shown in Figure 22, the electronic device 2200 includes one or more processors 2201. The processor 2201 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 2201 is used to call instructions to enable the electronic device 2200 to perform any of the above methods.

[0803] In some embodiments, the electronic device 2200 further includes one or more memories 2202 for storing instructions. In some embodiments, all or part of the memory 2202 may also be located outside the electronic device 2200.

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

[0805] In some embodiments, the transceiver 2203 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.

[0806] In some embodiments, the electronic device 2200 further includes one or more interface circuits 2204, which are connected to the memory 2202. The interface circuits 2204 can be used to receive signals from the memory 2202 or other devices, and can be used to send signals to the memory 2202 or other devices. For example, the interface circuit 2204 can read instructions stored in the memory 2202 and send the instructions to the processor 2201.

[0807] The electronic device 2200 described in the above embodiment may be a first billing function network element or a second billing function network element, but the scope of the electronic device 2200 described in the present disclosure is not limited thereto, and the structure of the electronic device 2200 may not be limited by FIG. 22 . 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.

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

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

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

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

[0812] The present disclosure also provides a storage medium having instructions stored thereon, which, when executed on the electronic device 2200, causes the electronic device 2200 to perform 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.

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

[0814] 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.

[0815] 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.

[0816] 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.

[0817] 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.

[0818] 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.

[0819] 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.

[0820] 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.

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

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

[0823] 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.

[0824] 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.

[0825] 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.

[0826] 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.

[0827] 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.

[0828] 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.

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

[0830] 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.

[0831] 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.

[0832] 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.

[0833] In some embodiments, obtaining data, information, etc. may comply with local laws and regulations.

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

[0835] 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.

[0836] 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.

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

[0838] 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.

[0839] 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)).

[0840] 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.

[0841] 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.

[0842] 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 billing method for satellite communication, characterized in that, The method is applied to a first charging function 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 charging function network element deployed in the second network; wherein, the first charging information is used to create or update a first charging data record CDR, and the first CDR is used to generate a charging bill.

2. The method according to claim 1, wherein The method further includes: Determining that the terminal device accesses the first network through satellite services.

3. The method according to claim 1, wherein The first charging information is charging information about satellite communication for the first network.

4. The method according to claim 3, wherein The first charging information includes at least one of the following information: The operator identifier of the first network; The operator identifier of the second network; The identifier of the satellite and / or the identifier of the constellation that provides satellite services for the terminal device using satellite services in the first network; The quality of service QoS of the satellite that provides satellite services for the terminal device using satellite services in the first network; The satellite service indication SSI corresponding to the terminal device using satellite services in the first network, which is used to indicate that the corresponding terminal device accesses the first network through satellite services; The satellite service type indication corresponding to the terminal device using satellite services in the first network, which is used to indicate that the satellite service used by the corresponding terminal device is a backhaul service or a terminal direct connection service; The satellite type indication corresponding to the terminal device using satellite services in the first network, which is used to indicate the type of the satellite that provides satellite services for the corresponding terminal device; The uplink data usage amount and / or downlink data usage amount of the terminal device using satellite services in the first network; At least one of the identifier, start time, end time, and duration of the data connection session of the terminal device using satellite services in the first network; The number of data connection sessions of the terminal device using satellite services in the first network; The identifier of the terminal device using satellite services in the first network.

5. The method according to claim 3, characterized in that, The first charging information includes at least one of the following information: The total uplink data usage amount and / or total downlink data usage amount corresponding to the terminal direct connection service in the first network; The total uplink data usage amount and / or total downlink data usage amount corresponding to the backhaul service in the first network; The total uplink data usage amount and / or total downlink data usage amount under each satellite category corresponding to the terminal direct connection service in the first network; The total uplink data usage amount and / or total downlink data usage amount under each satellite category corresponding to the backhaul service in the first network; The total PDU connection amount and / or total PDU connection duration corresponding to the terminal direct connection service in the first network; The total PDU connection amount and / or total PDU connection duration corresponding to the backhaul service in the first network.

6. The method according to any one of claims 1-5, characterized in that, The first charging information is sent in response to meeting a set condition, and the set condition includes at least one of the following: The current moment is a target sending moment, and the interval between the target sending moment and the previous sending moment is a preset duration; Receive an information sending instruction, where the information sending instruction is used to instruct the first charging function network element to send the first charging information; A trigger event for triggering the sending of charging information occurs.

7. The method according to any one of claims 3-5, characterized in that, The first charging information is carried in a charging request message sent by the first charging function network element to the second charging function network element, and the charging request message also carries first quota information, where the first quota information is for the first network, and the first quota information includes first quota application information for applying for a quota and / or first quota usage information for informing the used quota.

8. The method according to any one of claims 3-5, characterized in that The method further includes: Send a first charging mode indication to the second charging function network element; Wherein, the first charging mode indication is used to instruct the first charging function network element to send charging information about satellite communication for the first network.

9. The method according to any one of claims 3-5, characterized in that, The method further includes: Receive a first charging mode indication sent by the second charging function network element; Wherein, the first charging mode indication is used to instruct the first charging function network element to send charging information about satellite communication for the first network.

10. The method according to claim 1, characterized in that, The first charging information is charging information for a single terminal device using the satellite service, and is sent by a charging trigger function network element deployed in the first network to the first charging function network element in response to a charging trigger event of a data connection session of the single terminal device, and is sent by the first charging function network element to the second charging function network element in response to receiving the charging information of the single terminal device.

11. The method according to claim 10, characterized in that, The first charging information is carried in a charging request message sent by the charging trigger function network element to the first charging function network element and / or carried in a charging request message sent by the first charging function network element to the second charging function network element; The charging request message also carries at least one of the following information: First charging negotiation information, where the first charging negotiation information is used to negotiate the charging trigger event and / or the reporting category, and the reporting category includes immediate reporting and / or deferred reporting; Second quota information, where the second quota information is for the first network or the single terminal device, and the second quota information includes second quota application information for applying for a quota and / or second quota usage information for informing the used quota.

12. The method according to claim 10, wherein The method further includes: Determine the second charging function 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 (UDM) function; CHF instances discovered by the Network Repository Function (NRF); Charging feature information locally provided by the Session Management Function (SMF).

13. The method according to any one of claims 10 - 12, characterized in that The method further includes: Create a second CDR based on the first charging information received from the charging trigger function network element, and the second CDR is used to generate a charging bill.

14. The method according to claim 13, wherein The method further includes: Receive the charging information to be updated sent by the charging trigger function network element; Update the second CDR based on the charging information to be updated; Forward the charging information to be updated to the second charging function network element, where the charging information to be updated is used to update the first CDR.

15. The method according to claim 14, characterized in that The charging information to be updated is carried in the charging update message sent by the charging trigger function network element to the first charging function network element, and / or carried in the charging update message sent by the first charging function network element to the second charging function network element; The charging update message further carries at least one of the following information: Second charging negotiation information, where the second charging negotiation information is used to negotiate the charging trigger event and / or the reporting category, and the reporting category includes immediate reporting and / or postponed reporting; Third quota information, where the third quota information is for the first network or the single terminal device, and the third quota information includes third quota application information for applying for a quota, and / or third quota usage information for informing the used quota.

16. The method according to claim 14, characterized in that, The charging information to be updated is sent by the charging trigger function network element in response to meeting at least one of the following update trigger conditions: The charging condition changes, where the charging condition includes at least one of the type of the satellite providing the satellite service, the satellite service quality, and the satellite identifier; Reach the limit of the rate group; Reach the quota limit.

17. The method according to claim 13, characterized in that The method further includes: Receive the charging termination indication sent by the charging trigger function network element; Close the second CDR based on the charging termination indication; Forward the charging termination indication to the second charging function network element, where the charging termination indication is used to close the first CDR.

18. The method according to claim 17, wherein The charging termination indication is carried in the charging termination message sent by the charging trigger to the first charging function network element, and / or carried in the charging termination message sent by the first charging function network element to the second charging function network element; The charging termination message further carries at least one of the following information: The second charging information of the single terminal device, which is used to update the first CDR and the second CDR; Fourth quota information, where the fourth quota information is for the first network or the single terminal device, and the fourth quota information includes fourth quota application information for applying for a quota, and / or fourth quota usage information for informing the used quota.

19. The method according to any one of claims 10 to 12, characterized in that The method further includes: Send a second charging mode indication to the second charging function network element; Wherein, the second charging mode indication is used to instruct the first charging function network element to send the charging information of the single terminal device to the second charging function network element in response to receiving the charging information of the single terminal device using the satellite service, and the charging information of the single terminal is sent by the charging trigger function network element deployed in the first network to the first charging function network element in response to the charging trigger event of the data connection session of the single terminal device being triggered. The method further includes:

20. The method according to any one of claims 10 to 12, characterized in that The method further includes: Receive the second charging mode indication sent by the second charging function network element; Wherein, the second charging mode indication is used to instruct the first charging function network element to send the charging information of the single terminal device to the second charging function network element in response to receiving the charging information for the single terminal device using the satellite service, and the charging information of the single terminal is sent by the charging trigger function network element deployed in the first network to the first charging function network element after being triggered by the charging trigger event of the data connection session of the single terminal device.

21. The method according to any one of claims 1-5, 10-12, characterized in that, The first network is a terrestrial network, and the second network is a satellite network.

22. A charging method for satellite communication, characterized in that, The method is applied to a second charging function network element deployed in the second network, and the method includes: Receive the first charging information of the terminal device using the satellite service sent by the first charging function network element deployed in the first network; Based on the first charging information, create or update a first charging data record CDR, and the first CDR is used to generate a charging bill.

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

24. The method according to claim 22, wherein The first charging information is the charging information about satellite communication for the first network.

25. The method according to claim 24, characterized in that, The first charging information includes at least one of the following information: The operator identifier of the first network; The operator identifier of the second network; The identifier of the satellite and / or the identifier of the constellation that provides the satellite service for the terminal device using the satellite service in the first network; The quality of service QoS of the satellite that provides the satellite service for the terminal device using the satellite service in the first network; The satellite service indication SSI corresponding to the terminal device using the satellite service in the first network, which is used to indicate that the corresponding terminal device accesses the first network through the satellite service; The satellite service type indication corresponding to the terminal device using the satellite service in the first network, which is used to indicate that the satellite service used by the corresponding terminal device is a backhaul service or a terminal direct connection service; The satellite type indication corresponding to the terminal device using the satellite service in the first network, which is used to indicate the type of the satellite that provides the satellite service for the corresponding terminal device; The uplink data usage and / or downlink data usage of the terminal device using the satellite service in the first network; At least one of the identifier, start time, end time, and duration of the data connection session of the terminal device using the satellite service in the first network; The number of data connection sessions of the terminal device using the satellite service in the first network; The identifier of the terminal device using the satellite service in the first network.

26. The method according to claim 24, wherein The first charging information includes at least one of the following information: The total uplink data usage and / or total downlink data usage corresponding to the terminal direct connection service in the first network; The total uplink data usage and / or total downlink data usage corresponding to the backhaul service in the first network; The total uplink data usage and / or total downlink data usage under each satellite category corresponding to the terminal direct connection service in the first network; The total uplink data usage and / or the total downlink data usage under each satellite category corresponding to the backhaul service in the first network; The total number of protocol data unit (PDU) connections and / or the total PDU connection duration corresponding to the device-to-device service in the first network; The total number of PDU connections and / or the total PDU connection duration corresponding to the backhaul service in the first network.

27. The method according to any one of claims 22-26, characterized in that, The first charging information is sent in response to meeting a set condition, and the set condition includes at least one of the following: The current time is the target sending time, and a preset duration is set between the target sending time and the previous sending time; An information sending instruction is received, where the information sending instruction is used to instruct the first charging functional network element to send the first charging information; A trigger event for triggering the sending of charging information occurs.

28. The method according to any one of claims 24-26, characterized in that, The first charging information is carried in a charging request message sent by the first charging functional network element to the second charging functional network element, and the charging request message also carries first quota information, where the first quota information is for the first network, and the first quota information includes first quota application information for applying for a quota, and / or first quota usage information for informing of the used quota.

29. The method according to any one of claims 24 - 26, characterized in that, The method further includes: Receiving a first charging mode indication sent by the first charging functional network element; Wherein, the first charging mode indication is used to instruct the first charging functional network element to send charging information about satellite communication for the first network.

30. The method according to any one of claims 24-26, characterized in that, The method further includes: Sending a first charging mode indication to the first charging functional network element; Wherein, the first charging mode indication is used to instruct the first charging functional network element to send charging information about satellite communication for the first network.

31. The method according to claim 22, wherein The first charging information is charging information for a single terminal device using the satellite service, and is sent by a charging trigger functional network element deployed in the first network to the first charging functional network element in response to a charging trigger event of a data connection session of the single terminal device, and is sent by the first charging functional network element to the second charging functional network element in response to receiving the charging information of the single terminal device.

32. The method according to claim 31, wherein The first charging information is carried in a charging request message sent by the charging trigger functional network element to the first charging functional network element, and / or carried in a charging request message sent by the first charging functional network element to the second charging functional network element; The charging request message further carries at least one of the following information: First charging negotiation information, where the first charging negotiation information is used to negotiate the charging trigger event and / or the reporting category, and the reporting category includes immediate reporting and / or deferred reporting; Second quota information, where the second quota information is for the first network or the single terminal device, and the second quota information includes second quota application information for applying for a quota, and / or second quota usage information for informing of the used quota.

33. The method according to claim 31, wherein The second charging functional network element determines 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; The charging characteristic information provided by the Unified Data Management Function (UDM); The CHF instance discovered by the Network Repository Function (NRF); The charging characteristic information locally provided by the Session Management Function (SMF).

34. The method according to any one of claims 31-33, characterized in that, The method further includes: Receiving the charging information to be updated forwarded by the first charging function network element, where the charging information to be updated is sent by the charging trigger function network element to the first charging function network element; Updating the first Call Detail Record (CDR) based on the charging information to be updated.

35. The method according to claim 34, characterized in that, The charging information to be updated is carried in the charging update message sent by the charging trigger function network element to the first charging function network element, and / or carried in the charging update message sent by the first charging function network element to the second charging function network element; The charging update message further carries at least one of the following information: Second charging negotiation information, where the second charging negotiation information is used to negotiate the charging trigger event and / or the reporting category, and the reporting category includes immediate reporting and / or deferred reporting; Third quota information, where the third quota information is for the first network or the single terminal device, and the third quota information includes third quota application information for applying for a quota, and / or third quota usage information for informing the used quota.

36. The method according to claim 34, wherein The charging information to be updated is sent by the charging trigger function network element in response to at least one of the following update trigger conditions being met: The charging condition changes, where the charging condition includes at least one of the type of satellite providing the satellite service, the satellite service quality, and the satellite identifier; The limit of the rate group is reached; The quota limit is reached.

37. The method according to any one of claims 31-33, characterized in that, The method further includes: Receiving the charging termination indication forwarded by the first charging function network element, where the charging termination indication is sent by the charging trigger function network element to the first charging function network element; Closing the first CDR based on the charging termination indication.

38. The method according to claim 37, wherein The charging termination indication is carried in the charging termination message sent by the charging trigger function to the first charging function network element, and / or carried in the charging termination message sent by the first charging function network element to the second charging function network element; The charging termination message further carries at least one of the following information: The second charging information of the single terminal device, which is used to update the first CDR and the second CDR; Fourth quota information, where the fourth quota information is for the first network or the single terminal device, and the fourth quota information includes fourth quota application information for applying for a quota, and / or fourth quota usage information for informing the used quota.

39. The method according to any one of claims 31 to 33, characterized in that, The method further includes: Receiving the second charging mode indication sent by the first charging function network element; The second charging mode indication is used to indicate that the first charging functional network element sends the charging information of the single terminal device to the second charging functional network element in response to receiving the charging information for the single terminal device using the satellite service. The charging information of the single terminal is sent by the charging trigger functional network element deployed in the first network to the first charging functional network element when being triggered by a charging trigger event of the data connection session of the single terminal device.

40. The method according to any one of claims 31 - 33, characterized in that, The method further includes: Sending a second charging mode indication to the first charging functional network element; The second charging mode indication is used to indicate that the first charging functional network element sends the charging information of the single terminal device to the second charging functional network element in response to receiving the charging information for the single terminal device using the satellite service. The charging information of the single terminal is sent by the charging trigger functional network element deployed in the first network to the first charging functional network element when being triggered by a charging trigger event of the data connection session of the single terminal device.

41. The method according to any one of claims 22-26, 31-33, characterized in that, The first network is a terrestrial network, and the second network is a satellite network.

42. A billing device for satellite communication, wherein, The device is applied to the first charging functional network element deployed in the first network, and the device includes: A transceiver module, configured to send the first charging information of the terminal device using the satellite service to the second charging functional network element deployed in the second network; wherein, the first charging information is used to create or update a first charging data record CDR, and the first CDR is used to generate a charging bill.

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

44. An electronic device, wherein, It 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 satellite communication charging method according to any one of claims 1-21, or execute the satellite communication charging method according to any one of claims 22-41.

45. A billing system for satellite communication, characterized in that, It includes a first charging functional network element deployed in the first network and a second charging functional network element deployed in the second network; Wherein, the first charging functional network element is configured to implement the satellite communication charging method according to any one of claims 1-21, and the second charging functional network element is configured to implement the satellite communication charging method according to any one of claims 22-41.

46. The charging system according to claim 45, characterized in that, The system further includes a charging trigger functional network element deployed in the first network; the charging trigger functional network element is used for: In response to a charging trigger event for a data connection session of a single terminal device using satellite services, the charging information of the single terminal device is sent to the first charging function network element, where the charging information of the single terminal device is used for the first charging function network element to generate a second CDR and for forwarding to the second charging function network element to generate a first CDR.

47. The charging system according to claim 46, characterized in that, The charging trigger function network element is further configured to: Send the charging information to be updated to the first charging function network element; Wherein, the charging information to be updated is used to update the second CDR and for forwarding to the second charging function network element to update the first CDR.

48. The charging system according to claim 46, wherein, The charging trigger function network element is further configured to: Send a charging termination indication to the first charging function network element, where the charging termination indication is used to close the second CDR and for forwarding to the second charging function network element to close the first CDR.

49. A storage medium, the storage medium stores instructions, characterized in that, When the instruction runs on the electronic device, the electronic device is caused to execute the satellite communication charging method according to any one of claims 1-21, or execute the satellite communication charging method according to any one of claims 22-41.

Images