Charging method and device for satellite communication

Abstract

The embodiment of the invention discloses a charging method and device for satellite communication, and relates to the technical field of satellite communication, service support and core networks, and the method comprises the steps that a first network element deployed in a first network sends first charging information of terminal equipment using satellite service to a second network element deployed in a second network, the first charging information is used for generating a first charging data record CDR, and the first CDR is used for generating a charging bill. Therefore, the second network element deployed in the second network can generate the first CDR for generating the charging bill based on the first charging information provided by the first network element deployed in the first network, thereby avoiding the problem that the charging results of the second network and the first network are inconsistent, and improving the accuracy of the charging result of satellite communication.

Description

Technical Field

[0001] The present disclosure relates to the technical fields of satellite communication, service support, and core network, and particularly to a charging method and device for satellite communication. Background Art

[0002] In some remote areas and areas where the ground network cannot be covered, such as deserts, oceans far from shore bases, and flights in progress, users cannot use ground network services. Satellite communication has the advantages of all-weather, wide area coverage, and reliability, and can effectively solve the network connection problems in remote areas, aviation, oceans, deserts, etc. that cannot be solved by the ground network, and provide network connection services for users. In order to provide network connection services for users in remote areas, aviation, oceans, deserts, etc., ground operators usually rent satellites from satellite service providers or satellite network operators that own satellite networks. And how to accurately charge for satellite-based communication has become an urgent problem to be solved. Summary of the Invention

[0003] Embodiments of the present disclosure propose a charging method and device for satellite communication, which can at least solve the problem of how to accurately charge for satellite-based communication in related technologies.

[0004] According to a first aspect of the embodiments of the present disclosure, a charging method for satellite communication is proposed. The method is applied to a first network element deployed in a first network, and the method includes: sending first charging information of a terminal device using satellite services to a second network element deployed in a second network, where the first charging information is used to generate a first charging data record CDR, and the first CDR is used to generate a charging bill.

[0005] In some embodiments, the first charging information includes:

[0006] A satellite service indication SSI, which is used to indicate that the terminal device accesses the first network through the satellite service.

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

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

[0009] A satellite type indication, which is used to indicate the type of the satellite providing the satellite service;

[0010] The quality of satellite service;

[0011] A satellite identifier and / or a constellation identifier;

[0012] An operator identifier.

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

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

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

[0016] In some embodiments, the first information to be updated is sent when an update trigger condition is met, where the update trigger condition includes at least one of the following conditions: a change in the charging condition, 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; reaching the limit of a rate group; reaching the quota limit.

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

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

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

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

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

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

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

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

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

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

[0027] According to a second aspect of the embodiments of the present disclosure, a charging method for satellite communication is provided. The method is applied to a second network element deployed in a second network, and the method includes: receiving first charging information sent by a first network element deployed in a first network, where the first charging information includes charging information of a terminal device using satellite services; generating a first charging data record (CDR) based on the first charging information, and the first CDR is used to generate a charging bill.

[0028] In some embodiments, the first charging information includes:

[0029] A satellite service indication (SSI) for indicating that the terminal device accesses the first network through the satellite service.

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

[0031] A satellite service type indication for indicating that the satellite service is a backhaul service or a terminal direct connection service;

[0032] A satellite type indication for indicating the type of the satellite providing the satellite service;

[0033] The quality of the satellite service;

[0034] The satellite identifier and / or the constellation identifier;

[0035] The operator identifier.

[0036] In some embodiments, the first charging information is sent when it is determined that the terminal device accesses the first network through the satellite service.

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

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

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

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

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

[0042] According to a third aspect of the embodiments of the present disclosure, a charging device for satellite communication is provided. The device is applied to a first network element deployed in a first network, and the device includes: a transceiver module, configured to send first charging information of a terminal device using satellite services to a second network element deployed in a second network, where the first charging information is used to generate a first charging data record (CDR), and the first CDR is used to generate a charging bill.

[0043] According to a fourth aspect of the embodiments of the present disclosure, a charging device for satellite communication is provided. The device is applied to a second network element deployed in a second network, and the device includes: a transceiver module, configured to receive the first charging information sent by a first network element deployed in a first network, where the first charging information includes charging information of a terminal device using satellite services; a processing module, configured to generate a first charging data record (CDR) based on the first charging information, and the first CDR is used to generate a charging bill.

[0044] According to a fifth aspect of the embodiments of the present disclosure, an electronic device is provided, which includes: one or more processors; one or more memories for storing instructions; where the processor is configured to call the instructions to cause the electronic device to execute the charging method for satellite communication described in the first aspect or the optional implementation manner of the first aspect, or execute the charging method for satellite communication described in the second aspect or the optional implementation manner of the second aspect.

[0045] According to a sixth aspect of the embodiments of the present disclosure, a charging system for satellite communication is provided, which includes a first network element deployed in a first network and a second network element deployed in a second network; where the first network element is configured to implement the charging method for satellite communication described in the first aspect or the optional implementation manner of the first aspect, and the second network element is configured to implement the charging method for satellite communication described in the second aspect or the optional implementation manner of the second aspect.

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

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

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

[0049] According to a seventh aspect of the embodiments of the present disclosure, a storage medium is provided. The storage medium stores instructions that, when run on an electronic device, cause the electronic device to execute the method described in the first aspect, the second aspect, the optional implementation manners of the first aspect, or the optional implementation manners of the second aspect.

[0050] According to an eighth aspect of the embodiments of the present disclosure, a program product is provided. When the program product is executed by an electronic device, the electronic device is caused to execute the method described in the first aspect, the second aspect, the optional implementation manners of the first aspect, or the optional implementation manners of the second aspect.

[0051] According to a ninth aspect of the embodiments of the present disclosure, a computer program is provided. When it runs on a computer, the computer is caused to execute the method described in the first aspect, the second aspect, the optional implementation manners of the first aspect, or the optional implementation manners of the second aspect.

[0052] In the solution proposed by the embodiments of the present disclosure, a first network element deployed in a first network sends first charging information of a terminal device using satellite services to a second network element deployed in a second network. The first charging information is used to generate a first charging data record (CDR), and the first CDR is used to generate a charging bill. Thus, the second network element deployed in the second network can generate a first CDR for generating a charging bill based on the first charging information provided by the first network element deployed in the first network, thereby avoiding the problem of inconsistent charging results between the second network and the first network and improving the accuracy of the charging results of satellite communications. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] To more clearly illustrate the technical solutions in the embodiments of the present disclosure or the background art, the following will describe the drawings required to be used in the embodiments of the present disclosure or the background art.

[0054] Figure 1 is a schematic diagram of the architecture of a satellite communication charging system shown according to an embodiment of the present disclosure;

[0055] Figure 2 is another schematic diagram of the architecture of a satellite communication charging system shown according to an embodiment of the present disclosure;

[0056] Figure 3It is an interaction schematic diagram of a billing method for satellite communication shown according to an embodiment of the present disclosure;

[0057] Figure 4 It is an interaction schematic diagram of a billing method for satellite communication shown according to an embodiment of the present disclosure;

[0058] Figure 5 It is an interaction schematic diagram of a billing method for satellite communication shown according to an embodiment of the present disclosure;

[0059] Figure 6 It is an interaction schematic diagram of a billing method for satellite communication shown according to an embodiment of the present disclosure;

[0060] Figure 7 It is an interaction schematic diagram of a billing method for satellite communication shown according to an embodiment of the present disclosure;

[0061] Figure 8 It is an interaction schematic diagram of a billing method for satellite communication shown according to an embodiment of the present disclosure;

[0062] Figure 9 It is an interaction schematic diagram of a billing method for satellite communication shown according to an embodiment of the present disclosure;

[0063] Figure 10 It is an interaction schematic diagram of a billing method for satellite communication shown according to an embodiment of the present disclosure;

[0064] Figure 11 It is a flowchart of a billing method for satellite communication shown according to an embodiment of the present disclosure;

[0065] Figure 12 It is a flowchart of a billing method for satellite communication shown according to an embodiment of the present disclosure;

[0066] Figure 13 It is a flowchart of a billing method for satellite communication shown according to an embodiment of the present disclosure

[0067] Figure 14 It is a flowchart of a billing method for satellite communication shown according to an embodiment of the present disclosure;

[0068] Figure 15 It is a flowchart of a billing method for satellite communication shown according to an embodiment of the present disclosure;

[0069] Figure 16 It is a flowchart of a billing method for satellite communication shown according to an embodiment of the present disclosure;

[0070] Figure 17 It is a flowchart of a billing method for satellite communication shown according to an embodiment of the present disclosure;

[0071] Figure 18 is a schematic flowchart of a billing method for satellite communication according to an embodiment of the present disclosure;

[0072] Figure 19 is a schematic flowchart of a billing method for satellite communication according to an embodiment of the present disclosure;

[0073] Figure 20 is a schematic flowchart of a billing method for satellite communication according to an embodiment of the present disclosure;

[0074] Figure 21 is a schematic structural diagram of a billing device for satellite communication proposed by an embodiment of the present disclosure;

[0075] Figure 22 is a schematic structural diagram of a billing device for satellite communication proposed by an embodiment of the present disclosure;

[0076] Figure 23 is a schematic structural diagram of an electronic device proposed by an embodiment of the present disclosure;

[0077] Figure 24 is a schematic structural diagram of a chip proposed by an embodiment of the present disclosure. Detailed implementation manners

[0078] In some remote areas and regions where the ground network cannot be covered, such as deserts, oceans far from the shore base, and flights in progress, users cannot use the ground network service. Satellite communication has the advantages of all-weather, wide-area coverage, and reliability, etc., and can effectively solve the network connection problems in remote areas, aviation, oceans, deserts and other regions that cannot be solved by the ground network, and provide network connection services for users. By deploying independent base stations in areas where the ground network cannot reach, and then using satellites to provide data backhaul links between the base stations and core network elements, network connection services can be provided for users. However, usually due to reasons such as high satellite network construction costs, most ground operators do not have their own satellite networks. In order to provide network connection services for users in remote areas, aviation, oceans, deserts and other regions, they need to rent satellites from satellite service providers or satellite network operators that own satellite networks. Therefore, satellite service providers or satellite network operators need to generate bills based on information such as the traffic used by the users of ground operators, and bill the ground operators. At the same time, due to different types of satellites and different service qualities of the provided backhaul links, satellite service providers or satellite network operators will also generate different bills according to different satellite types for differential billing. For example, geostationary satellites are as high as nearly 36,000 kilometers from the ground, with a long single-satellite service time and a long delay of the backhaul link, while low-earth orbit satellites are 500 kilometers from the ground, with a short single-satellite service time and a short delay of the backhaul link.

[0079] In related technologies, taking a satellite service provider as an example, usually, the satellite service provider identifies and counts the usage traffic of a terrestrial operator based on its own satellite network, and then generates a bill. The terrestrial operator also counts the usage traffic of users based on its own core network, and then compares the bill provided by the satellite service provider to pay the satellite rental fee. In this billing mode, due to reasons such as different network elements counted by both parties and different data packet formats, it is easy to cause the total amount of data transmission counted by the satellite service provider to be inconsistent with the total amount of data transmission counted by the terrestrial operator, resulting in a problem of low accuracy of the billing result of the satellite service provider. How to accurately bill satellite-based communications has become an urgent problem to be solved.

[0080] In view of the above problems, embodiments of the present disclosure propose a billing method for satellite communications, a billing device for satellite communications, an electronic device, a billing system for satellite communications, a storage medium, a program product, and a computer program.

[0081] To better understand the billing method for satellite communications disclosed in embodiments of the present disclosure, the billing system for satellite communications applicable to embodiments of the present disclosure will be described first below.

[0082] Figure 1 is a schematic diagram of the architecture of a billing system for satellite communications shown according to embodiments of the present disclosure.

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

[0084] In some embodiments, the first network is a communication network provided by a Mobile Network Operator (MNO), which may be referred to as a terrestrial network. The second network is a communication network provided by a Satellite Service Provider (SSP) or a Satellite Network Operator (SNO), which may be referred to as a satellite network. It should be noted that when the SSP has its own core network system and can independently operate satellite network services, the SSP is also the SNO at this time; when the SNO leases satellite resources to the MNO and provides satellite services to the MNO, the SNO is also the SSP at this time.

[0085] In some embodiments, the first network element 101 is, for example, a network element with a billing trigger function such as a Session Management Function (SMF) network element or other network elements, and the present disclosure does not limit this.

[0086] In some embodiments, the second network element 102 is, for example, a Charging Function (CHF) network element or other network elements capable of implementing charging, and the present disclosure does not limit this.

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

[0088] In some embodiments, the third network element 103 is, for example, a CHF network element or other network elements capable of implementing charging, and the present disclosure does not limit this.

[0089] It can be understood that the charging system 100 for satellite communication described in the embodiments of the present disclosure is for more clearly illustrating the technical solutions of the embodiments of the present disclosure, and does not constitute a limitation on the technical solutions proposed in the embodiments of the present disclosure. Those of ordinary skill in the art know that with the evolution of the system architecture and the emergence of new service scenarios, the technical solutions proposed in the embodiments of the present disclosure are equally applicable to similar technical problems.

[0090] The following embodiments of the present disclosure can be applied to Figure 1 or Figure 2 the charging system for satellite communication shown or some of the main bodies therein, but not limited thereto. Figure 1 and Figure 2 The main bodies shown are examples. The charging system for satellite communication may include Figure 1 or Figure 2 all or part of the main bodies, or may also include Figure 1 or Figure 2 other main bodies outside. The number and form of each main body are arbitrary. Each main body can be physical or virtual. The connection relationship between each main body is an example. Each main body may not be connected or may be connected. Their connection can be in any way, either directly connected or indirectly connected, either wired connected or wireless connected.

[0091] 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 (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, next-generation systems extended based on them, etc. In addition, multiple systems can be combined (for example, a combination of LTE or LTE-A and 5G, etc.) and applied.

[0092] The following describes the satellite communication charging method of the charging system 100 for satellite communication proposed in the embodiments of the present disclosure.

[0093] Figure 3 It is an interaction schematic diagram of the satellite communication charging method shown in the embodiments of the present disclosure. As Figure 3 shown, the method involved in the embodiments of the present disclosure is applied toFigure 1 or Figure 2 The billing system 100 for satellite communication as shown, and the method includes the following steps 301-303.

[0094] Step 301, the first network element 101 sends the first billing information of the terminal device using satellite services to the second network element 102.

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

[0096] In some embodiments, the first network element 101 may send a first billing request message to the second network element 102, where the first billing request message carries the first billing information of the terminal device using satellite services. Among them, the first billing request message is used to request the second network element 102 to generate a CDR.

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

[0098] In some embodiments, the data connection session may be a protocol data unit session (PDU session) defined by the 3GPP standard specification, or may be other forms of sessions, and the embodiments of the present disclosure do not limit this. The embodiments of the present disclosure are described by taking the data connection session as a PDU session as an example.

[0099] In some embodiments, when the first network element is an SMF network element, the satellite service used by the terminal device can be determined as a backhaul service in the following manner: The Access and Mobility management function (AMF) network element determines, based on the configuration, that the terminal device is accessing the base station using satellite backhaul service, 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 first network element. Among them, the backhaul service refers to the connection provided by the satellite between the base station and the core network, that is, the terminal device connects to the core network through the base station and the satellite in sequence.

[0100] 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 radio access technologies (RATs) "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) represents New Radio (Low Earth Orbit), NR(MEO) represents New Radio (Medium Earth Orbit), NR(GEO) represents New Radio (Geostationary Orbit), and NR(OTHERSAT) represents New Radio (Other Satellites). Among them, the terminal direct connection service refers to the terminal device connecting to the core network through the satellite and the gateway station in sequence.

[0101] Among them, the first charging information is the charging information used to generate a Charging Data Record (CDR), where the charging information is information related to satellite charging. Among them, the CDR is the original data used to generate the charging bill. In the embodiments of the present application, the name of the first charging information is not limited, and it is, for example, "charging-related information", "information for charging", etc.

[0102] In some embodiments, the first charging information may include a Satellite Service Indicator (SSI), where the SSI is used to indicate the manner in which the terminal device accesses the first network through the satellite service. In some embodiments, when the first charging information does not include the SSI, it indicates that the terminal device accesses the first network through a non-satellite service. Among them, the non-satellite service is, for example, a ground operator network service.

[0103] It can be understood that satellite services can include the following types: backhaul services and device-to-device (D2D) services. Different types of satellite services may correspond to different charging rules. In some embodiments, the SSI can further indicate the type of satellite service. For example, the SSI includes a satellite service type indication for indicating whether the satellite service is a backhaul service or a D2D service. For example, when the first charging information includes the SSI and the value of the satellite service type indication included in the SSI is "0", it can indicate that the terminal device accesses the first network through the satellite service and the satellite service is a backhaul service; when the first charging information includes the SSI and the value of the satellite service type indication included in the SSI is "1", it can indicate that the terminal device accesses the first network through the satellite service and the satellite service is a D2D service. Or, when the first charging information includes the SSI and the value of the satellite service type indication included in the SSI is "1", it can indicate that the terminal device accesses the first network through the satellite service and the satellite service is a backhaul service; when the first charging information includes the SSI and the value of the satellite service type indication included in the SSI is "0", it can indicate that the terminal device accesses the first network through the satellite service and the satellite service is a D2D service.

[0104] It can be understood that different types of satellites providing satellite services may have different charging rules. In some embodiments, the SSI can include a satellite type indication for indicating the type of the satellite providing the satellite service. The type of the satellite providing the satellite service can include medium Earth orbit (MEO) satellites, low Earth orbit (LEO) satellites, geostationary orbit (GEO) satellites, or other satellite types. For example, when the first charging information includes the SSI and the value of the satellite type indication included in the SSI is "0", it can indicate that the terminal device accesses the first network through the satellite service and the type of the satellite providing the satellite service is an LEO satellite type; when the first charging information includes the SSI and the value of the satellite type indication included in the SSI is "1", it can indicate that the terminal device accesses the first network through the satellite service and the type of the satellite providing the satellite service is a GEO satellite type.

[0105] In some embodiments, the SSI may include a satellite service type indication and a satellite type indication. For example, when the first charging information includes the SSI, and the value of the satellite service type indication included in the SSI is "0" and the value of the satellite type indication is "0", it may indicate that the terminal device accesses the first network through satellite services, and the satellite service is a terminal direct connection service, and the type of the satellite providing the terminal direct connection service is a low-earth orbit satellite type; when the first charging information includes the SSI, and the value of the satellite service type indication included in the SSI is "0" and the value of the satellite type indication is "1", it may indicate that the terminal device accesses the first network through satellite services, and the satellite service is a terminal direct connection service, and the type of the satellite providing the terminal direct connection service is a geostationary orbit satellite type; when the first charging information includes the SSI, and the value of the satellite service type indication included in the SSI is "1" and the value of the satellite type indication is "0", it may indicate that the terminal device accesses the first network through satellite services, and the satellite service is a backhaul service, and the type of the satellite providing the backhaul service is a low-earth orbit satellite type; when the first charging information includes the SSI, and the value of the satellite service type indication included in the SSI is "1" and the value of the satellite type indication is "1", it may indicate that the terminal device accesses the first network through satellite services, and the satellite service is a backhaul service, and the type of the satellite providing the backhaul service is a geostationary orbit satellite type.

[0106] In some embodiments, the satellite service type indication and the satellite type indication may be different from the satellite service indication SSI. That is, in addition to the SSI, the first charging information may further include at least one of the satellite service type indication and the satellite type indication. For example, when the first charging information includes the SSI, the satellite service type indication, and the satellite type indication, and the value of the SSI is "1", the value of the satellite service type indication is "0", and the value of the satellite type indication is "0", it may indicate that the terminal device accesses the first network through satellite service, and the satellite service is a terminal direct connection service, and the type of the satellite providing the terminal direct connection service is a low-earth orbit satellite type; when the first charging information includes the SSI, the satellite service type indication, and the satellite type indication, and the value of the SSI is "1", the value of the satellite service type indication is "0", and the value of the satellite type indication is "1", it may indicate that the terminal device accesses the first network through satellite service, and the satellite service is a terminal direct connection service, and the type of the satellite providing the terminal direct connection service is a geostationary orbit satellite type; when the first charging information includes the SSI, the satellite service type indication, and the satellite type indication, and the value of the SSI is "1", the value of the satellite service type indication is "1", and the value of the satellite type indication is "0", it may indicate that the terminal device accesses 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-earth orbit satellite type; when the first charging information includes the SSI, the satellite service type indication, and the satellite type indication, and the value of the SSI is "1", the value of the satellite service type indication is "1", and the value of the satellite type indication is "1", it may indicate that the terminal device accesses 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 geostationary orbit satellite type.

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

[0108] Table 1 First Charging Information and Corresponding Descriptions

[0109]

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

[0111] Table 2 Parameters Included in the Charging Information of the PDU Session and Corresponding Descriptions

[0112]

[0113] In some embodiments, the FBC Information may include the Usage Volume.

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

[0115] Table 3 Parameters Included in the QBC Information and Corresponding Descriptions

[0116]

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

[0118] Table 4 Parameters Included in the Quota Information and Corresponding Descriptions

[0119] Parameter Name Description Quota Application Information Quota application information, used for quota application. Quota Usage Information Quota usage information, used to represent the used quota.

[0120] In some embodiments, what information is included in the first charging information and what form each type of information is in can be set as needed.

[0121] For example, in the case where the first charging information includes the charging information of the terminal device UE1 using satellite services, since the types of satellite services are different, the corresponding charging rules may be different, and since the types of satellites providing satellite services are different, the corresponding charging rules may be different, the first charging information may include the SSI corresponding to UE1, indicating that UE1 accesses the first network through satellite services, and the SSI may include a satellite service type indication, indicating that the satellite service used by UE1 is a terminal direct connection service, and the SSI may include a satellite type indication, indicating that the type of satellite providing the terminal direct connection service for UE1 is a low-earth orbit satellite type; since the satellite service quality is different, the corresponding charging rules may be different, the first charging information may include the satellite service quality corresponding to UE1, indicating the service quality of the satellite providing satellite services for UE1; since the satellites providing satellite services are different, the corresponding charging rules may be different, the first charging information may include the satellite identifier corresponding to UE1, indicating the identifier of the satellite providing satellite services for UE1; for the convenience of charging the operator, the first charging information may include an operator identifier, indicating the identifier of the operator providing the first network; for uniquely identifying a data connection session, the first charging information may include a charging identifier.

[0122] Step 302, the second network element 102 generates a first charging data record CDR based on the first charging information, and the first CDR is used to generate a charging bill.

[0123] In some embodiments, the first CDR may include one or more of the first charging information. For example, due to different satellite service types and / or different types of satellites providing satellite services, the corresponding charging rules may be different. Then, the first charging information may include SSI, and the first CDR may also include SSI. Due to different satellite service qualities, the corresponding charging rules may be different. Then, the first charging information may include satellite service quality, and the first CDR may also include satellite service quality. Due to different satellites providing satellite services, the corresponding charging rules may be different. Then, the first charging information may include satellite identification, and the first CDR may also include satellite identification. For the convenience of charging the operator, the first charging information may include operator identification, and the first CDR may also include operator identification. For the purpose of uniquely identifying a data connection session, the first charging information may include a charging identifier, and the first CDR may also include a charging identifier. It should be noted that the rules for generating the first CDR based on the first charging information can be set as needed, and the present disclosure does not limit this.

[0124] Step 303, the second network element 102 sends a first charging response message to the first network element 101.

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

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

[0127] Figure 3 Taking the case where step 303 is executed after step 302 as an example for illustration.

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

[0129] Table 5 Parameters Carried by the First Charging Response Message and Corresponding Descriptions

[0130]

[0131] In some embodiments, the Quota Management parameter may include one or more of the parameters shown in Table 6 below.

[0132] The parameters included in the quota management parameters in Table 6 and the corresponding descriptions

[0133] Parameter Name Description Time Quota Threshold Time threshold Volume Quota Threshold Quantitative quota threshold Quota Holding Time Quota duration

[0134] In some embodiments, the charging configuration parameters may include one or more of the parameters shown in Table 7 below. Among them, the parameters shown in Table 7 also apply to the charging configuration parameters shown in Table 2.

[0135] The parameters included in the charging configuration parameters in Table 7 and the corresponding descriptions

[0136]

[0137] It should be noted that taking the charging configuration parameters as an example, when both the first charging request message and the first charging response message carry the charging configuration parameters, the values of the charging configuration parameters carried in the first charging request message and the first charging response message may be the same or different.

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

[0139] In some embodiments, reference can be made to Figure 3 other optional implementation manners described before or after the corresponding specification.

[0140] For the charging method of satellite communication provided by the embodiments of the present disclosure, a first network element deployed in a first network may send first charging information of a terminal device using satellite services to a second network element deployed in a second network, where the first charging information is used to generate a first charging data record CDR, and the first CDR is used to generate a charging bill. Thus, the second network element deployed in the second network can generate a first CDR for generating a charging bill based on the first charging information provided by the first network element deployed in the first network, thereby avoiding the problem of inconsistent charging results between the second network and the first network and improving the accuracy of the charging results of satellite communication.

[0141] Figure 4 is an interaction schematic diagram of the charging method of satellite communication shown according to the embodiments of the present disclosure. As Figure 4 shown, the method involved in the embodiments of the present disclosure is applied to Figure 1 or Figure 2 the satellite communication charging system 100 shown, and the method includes the following steps 401-406.

[0142] Step 401, the first network element 101 sends first charging information of a terminal device using satellite services to the second network element 102.

[0143] An optional implementation manner of step 401 can be referred toFigure 3 Alternative implementation methods of step 301 of Figure 3 and other related parts in the involved embodiments will not be elaborated here.

[0144] Step 402: The second network element 102 generates a first charging data record CDR based on the first charging information, and the first CDR is used to generate a charging bill.

[0145] Alternative implementation methods of step 402 can be referred to Figure 3 alternative implementation methods of step 302 of Figure 3 and other related parts in the involved embodiments will not be elaborated here.

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

[0147] Alternative implementation methods of step 403 can be referred to Figure 3 alternative implementation methods of step 303 of Figure 3 and other related parts in the involved embodiments will not be elaborated here.

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

[0149] Among them, the first information to be updated is the information that needs to be updated and is used to update the first CDR.

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

[0151] Among them, the first charging update request message is used to request an update to the generated CDR.

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

[0153] In some embodiments, the first information to be updated may include QBC information and / or FBC information. Optionally, the QBC information may include quota information, and / or the FBC information may include quota information. Among them, the quota information may include quota application information for applying for a quota and / or quota usage information for informing the used quota.

[0154] In some embodiments, the first information to be updated may be sent when an update trigger condition is met, where the update trigger condition includes at least one of the following conditions:

[0155] The charging condition changes, where the charging condition includes at least one of the type of satellite providing satellite services, the quality of satellite services, and the satellite identifier;

[0156] The limit of the rating group is reached;

[0157] The quota limit is reached.

[0158] In some embodiments, in response to the change of the charging condition, the first network element 101 sends the first information to be updated to the second network element 102, which is applicable to the convergent charging scenario and the offline charging scenario.

[0159] In some embodiments, the 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, expiry of data event limit per RG. In some embodiments, in response to reaching the limit of the rating group, the first network element 101 sends the information to be updated to the second network element 102, which is applicable to the convergent charging scenario and the offline charging scenario.

[0160] In some embodiments, when the quota limit is reached, the quota management triggers are triggered. Optionally, triggering 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, re-authorization request by CHF. In some embodiments, in response to reaching the quota limit, the first network element 101 sends the first information to be updated to the second network element 102, which is applicable to the convergent charging scenario.

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

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

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

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

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

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

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

[0168] Figure 4 Taking the case where step 406 is executed after step 405 as an example for illustration.

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

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

[0171] The charging method for satellite communication provided by the embodiments of the present disclosure. The second network element deployed in the second network can generate a first CDR for generating a charging bill based on the first charging information provided by the first network element deployed in the first network, thereby avoiding the problem of inconsistent charging results between the second network and the first network and improving the accuracy of the charging results for satellite communication. Moreover, the second network element can update the first CDR in a timely manner according to the first information to be updated sent by the first network element, thereby ensuring the timeliness of the charging results generated by the second network element.

[0172] Figure 5 is an interaction schematic diagram of the charging method for satellite communication shown according to the embodiments of the present disclosure. As Figure 5 shown, the method involved in the embodiments of the present disclosure is applied to Figure 1 or Figure 2 the satellite communication charging system 100 shown, and this method includes the following steps 501-506.

[0173] Step 501, the first network element 101 sends the first charging information of the terminal device using the satellite service to the second network element 102.

[0174] For the optional implementation manner of step 501, reference can be made to Figure 3 the optional implementation manner of step 301 in Figure 3 and other related parts in the involved embodiments, which will not be elaborated here.

[0175] Step 502, the second network element 102 generates a first charging data record CDR based on the first charging information, and the first CDR is used to generate a charging bill.

[0176] For the optional implementation manner of step 502, reference can be made to Figure 3 the optional implementation manner of step 302 in Figure 3 and other related parts in the involved embodiments, which will not be elaborated here.

[0177] Step 503, the second network element 102 sends a first charging response message to the first network element 101.

[0178] For the optional implementation manner of step 503, reference can be made to Figure 3 the optional implementation manner of step 303 in Figure 3 and other related parts in the involved embodiments, which will not be elaborated here.

[0179] Step 504, the first network element 101 sends a first charging termination indication to the second network element 102.

[0180] Among them, the first charging termination indication is used to close the first CDR.

[0181] In some embodiments, the first network element 101 may send a first charging termination request message to the second network element 102, where a first charging termination indication is carried in the message.

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

[0183] In some embodiments, the first charging termination request message may further carry second charging information of the above-mentioned terminal device using satellite services. The second charging information is used to update the first CDR. The second charging information may be the charging information of the terminal device generated when the data connection session of the terminal device is released. The information included in the second charging information may be set as needed, specifically referring to the first charging information, which will not be elaborated here. In the embodiments of the present application, the name of the second charging information is not limited, and it may be, for example, "charging-related information", "information for charging", etc.

[0184] In some embodiments, the first charging termination request message may further carry a UsageReport. The UsageReport includes detailed information on the usage of data traffic and can be used to update the first CDR.

[0185] Step 505, the second network element 102 closes the first CDR based on the first charging termination indication.

[0186] Step 506, the second network element 102 sends a first charging termination response message to the first network element 101.

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

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

[0189] Figure 5 Taking the example that step 506 is executed after step 505 for illustration.

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

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

[0192] In some embodiments, reference may be made to Figure 5 other optional implementation manners described before or after the corresponding specification.

[0193] The billing method for satellite communication provided by the embodiments of the present disclosure. The second network element deployed in the second network can generate a first CDR for generating a billing statement based on the first billing information provided by the first network element deployed in the first network, thereby avoiding the problem of inconsistent billing results between the second network and the first network and improving the accuracy of the billing results for satellite communication. Moreover, the second network element can timely close the first CDR according to the first billing termination instruction sent by the first network element, so as to ensure that the second network element stops billing in a timely manner.

[0194] Figure 6 is an interaction schematic diagram of the billing method for satellite communication shown according to the embodiments of the present disclosure. As Figure 6 shown, the method involved in the embodiments of the present disclosure is applied to Figure 2 the billing system 100 for satellite communication shown. The method includes the following steps 601-606.

[0195] Step 601, the first network element 101 sends the first billing information of the terminal device using the satellite service to the second network element 102.

[0196] The optional implementation manner of step 601 can be referred to Figure 3 the optional implementation manner of step 301 of Figure 3 and other related parts in the involved embodiments, which will not be elaborated here.

[0197] Step 602, the second network element 102 generates a first billing data record CDR based on the first billing information. The first CDR is used to generate a billing statement.

[0198] The optional implementation manner of step 602 can be referred to Figure 3 the optional implementation manner of step 302 of Figure 3 and other related parts in the involved embodiments, which will not be elaborated here.

[0199] Step 603, the second network element 102 sends a first billing response message to the first network element 101.

[0200] The optional implementation manner of step 603 can be referred to Figure 3Optional implementation of step 303, and Figure 3 Other related parts in the involved embodiments will not be elaborated here.

[0201] Step 604, the first network element 101 sends the third charging information of the terminal device using satellite services to the third network element 103.

[0202] Among them, the terminal device using satellite services in step 604 and the terminal device using satellite services in step 601 can be the same terminal device.

[0203] Among them, the third charging information is the charging information used to generate CDR. Among them, the name of the third charging information in the embodiments of the present application is not limited, for example, it is "charging-related information", "information for charging", etc. Among them, the information included in the third charging information can be set as needed, and specifically, reference can be made to the first charging information, which will not be elaborated here.

[0204] In some embodiments, the first network element 101 can receive a data connection session establishment request sent by the terminal device, and in response to the establishment request, determine whether the terminal device accesses the first network through satellite services. In the case where it is determined that the terminal device accesses the first network through satellite services, it is determined that the terminal device uses satellite services, and then the third charging information is sent to the third network element 103.

[0205] In some embodiments, the first network element 101 can send a second charging request message to the third network element 103, where the second charging request message carries the third charging information. Among them, the second charging request message is used to request the third network element 103 to generate CDR.

[0206] In some embodiments, the first network element 101 can receive a data connection session establishment request sent by the terminal device, and in response to the establishment request, determine whether the terminal device accesses the first network through satellite services. In the case where it is determined that the terminal device accesses the first network through satellite services, it is determined that the terminal device uses satellite services, and then the above-mentioned second charging request message is sent to the third network element 103 to request the third network element 103 to start establishing CDR to charge for this data connection session.

[0207] In some embodiments, the data connection session can be a PDU session defined by the 3GPP standard specification, or can be other forms of sessions, and the embodiments of the present disclosure do not limit this. The embodiments of the present disclosure will be described by taking the data connection session as a PDU session as an example.

[0208] In some embodiments, when the first charging information includes an operator identifier, since the operator identifier is used to charge the operator and is irrelevant to the charging rules when the operator charges the user to whom the terminal device belongs, the operator identifier may not be included in the third charging information. To facilitate the operator to charge the user to whom the terminal device belongs, the third charging information may include the subscriber identifier of the user to whom the terminal device belongs. In addition, the information included in the third charging information may be the same as the information included in the first charging information. That is, the first charging information may include the operator identifier but not the subscriber identifier, and the third charging information may include the subscriber identifier but not the operator identifier. In addition, the other information included in the first charging information and the third charging information may be the same.

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

[0210] In some embodiments, the information included in the third charging information can be set as needed, and the third network element 103 can generate a second CDR based on the third charging information. Among them, the second CDR may include one or more of the information in the third charging information. For example, since the satellite service types are different, and / or the types of satellites providing satellite services are different, the corresponding charging rules may be different, so the third charging information may include SSI, and the second CDR may also include SSI; since the satellite service qualities are different, the corresponding charging rules may be different, so the third charging information may include satellite service quality, and the second CDR may also include satellite service quality; since the satellites providing satellite services are different, the corresponding charging rules may be different, so the third charging information may include satellite identifiers, and the second CDR may also include satellite identifiers; to facilitate charging the user to whom the terminal device belongs, the third charging information may include the subscriber identifier, and the second CDR may also include the subscriber identifier; to uniquely identify the second CDR, the third charging information may include a charging identifier, and the second CDR may also include the charging identifier. It should be noted that the rules for generating the second CDR based on the third charging information can be set as needed, and the present disclosure does not limit this.

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

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

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

[0214] Figure 6 Taking the case where step 606 is executed after step 605 as an example for illustration.

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

[0216] It should be noted that steps 601-603 may be executed before step 604, or after step 606, or simultaneously with steps 604-606, and the present disclosure does not limit this. Among them, in the case where the information that needs to be negotiated is not included in the first charging information and the third charging information, steps 601-603 and steps 604-606 may be executed simultaneously.

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

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

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

[0220] The charging feature information provided by the Unified Data Management (UDM);

[0221] The CHF instance discovered by the Network Repository Function (NRF);

[0222] The charging feature information locally provided by the SMF.

[0223] In some embodiments, when using the NRF to discover a CHF instance, in the case where the charging rule of the data connection session of the terminal device indicates that the data connection session is "offline only", the NRF may select a CHF instance that supports the CHF "offline only" service instance.

[0224] Among them, the charging rules include "offline only", "online only", and "converged charging", indicating whether the service data stream in the data connection session of the terminal device performs online charging, offline charging, or converged activation. The charging rules can be pre-configured in the SMF network element, and the SMF network element activates the charging rules for the data connection session of the terminal device. Alternatively, the PCF can also send and activate dynamic charging rules to the SMF, or the PCF can send and activate the specified pre-configured charging rules to the SMF.

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

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

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

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

[0229] In some embodiments, reference may be made to Figure 6 other optional implementation manners described before or after the corresponding specification.

[0230] The charging method for satellite communication provided by the embodiments of the present disclosure enables the second network element to generate a first CDR for generating a charging bill based on the first charging information of the terminal device using satellite services provided by the first network element, and the third network element can generate a second CDR for generating a charging bill based on the third charging information of the terminal device provided by the first network element. Since the second network element and the third network element perform charging based on the same data source, the problem of inconsistent charging results between the second network and the first network can be avoided, and the accuracy of the charging result for satellite communication is improved.

[0231] Figure 7 is an interaction schematic diagram of the charging method for satellite communication shown in the embodiments of the present disclosure. As Figure 7 shown, the method involved in the embodiments of the present disclosure is applied to Figure 2 the satellite communication charging system 100 shown in

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

[0233] For the optional implementation manners of step 701, reference can be made to Figure 3 the optional implementation manners of step 301 in Figure 3 and other related parts in the involved embodiments, which will not be elaborated here.

[0234] Step 702, the second network element 102 generates a first charging data record CDR based on the first charging information, and the first CDR is used to generate a charging bill.

[0235] For the optional implementation manners of step 702, reference can be made to Figure 3 the optional implementation manners of step 302 in Figure 3 and other related parts in the involved embodiments, which will not be elaborated here.

[0236] Step 703, the second network element 102 sends a first charging response message to the first network element 101, and the first charging response message carries first information to be negotiated.

[0237] For the optional implementation manners of step 703, reference can be made to Figure 3 the optional implementation manners of step 303 in Figure 3 and other related parts in the involved embodiments, which will not be elaborated here.

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

[0239] Among them, the first information to be negotiated is information that needs to be negotiated between the second network and the first network.

[0240] In some embodiments, the first information to be negotiated may include, for example, a charging configuration parameter (charging profile).

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

[0242] Step 704, the first network element 101 sends a second charging request message to the third network element 103, where the second charging request message carries third charging information of a terminal device using satellite services, and the third charging information includes the first information to be negotiated.

[0243] For the optional implementation manners of step 704, reference can be made toFigure 6 Alternative implementation of step 604, and Figure 6 Other related parts in the embodiments involved will not be elaborated here.

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

[0245] Step 705, the third network element 103 generates a second CDR based on the third charging information, and the second CDR is used to generate a charging bill.

[0246] Alternative implementation of step 705 can be referred to Figure 6 Alternative implementation of step 605, and Figure 6 Other related parts in the embodiments involved will not be elaborated here.

[0247] Step 706, the third network element 103 sends a second charging response message to the first network element 101.

[0248] Alternative implementation of step 706 can be referred to Figure 6 Alternative implementation of step 606, and Figure 6 Other related parts in the embodiments involved will not be elaborated here.

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

[0250] In some embodiments, reference can be made to Figure 7 Other alternative implementations described before or after the corresponding specification.

[0251] The charging method for satellite communication provided by the embodiments of the present disclosure enables the second network element to generate a first CDR for generating a charging bill based on the first charging information of the terminal device using satellite services provided by the first network element, and the third network element can generate a second CDR for generating a charging bill based on the third charging information of the terminal device provided by the first network element. Since the second network element and the third network element perform charging based on the same data source, the problem of inconsistent charging results between the second network and the first network can be avoided, and the accuracy of the charging results for satellite communication is improved. Moreover, by the first network element receiving the first information to be negotiated from the second network element and carrying the first information to be negotiated in the second charging request message and sending it to the third network element, information negotiation dominated by the second network can be achieved.

[0252] Figure 8 is an interaction schematic diagram of the charging method for satellite communication shown according to the embodiments of the present disclosure. AsFigure 8 As shown, the method according to an embodiment of the present disclosure is applied to Figure 2 the billing system 100 for satellite communication shown in the figure, and the method includes the following steps 801-806.

[0253] Step 801, a first network element 101 sends a second billing request message to a third network element 103, where the second billing request message carries third billing information of a terminal device using satellite services.

[0254] For an alternative implementation of step 801, reference may be made to Figure 6 the alternative implementation of step 604 in Figure 6 and other related parts in the embodiments involved, which will not be elaborated here.

[0255] Step 802, the third network element 103 generates a second CDR based on the third billing information, and the second CDR is used to generate a billing statement.

[0256] For an alternative implementation of step 802, reference may be made to Figure 6 the alternative implementation of step 605 in Figure 6 and other related parts in the embodiments involved, which will not be elaborated here.

[0257] Step 803, the third network element 103 sends a second billing response message to the first network element 101, and the second billing response message carries second information to be negotiated.

[0258] For an alternative implementation of step 803, reference may be made to Figure 6 the alternative implementation of step 606 in Figure 6 and other related parts in the embodiments involved, which will not be elaborated here.

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

[0260] Wherein, the second information to be negotiated is information that needs to be negotiated between the second network and the first network. Wherein, the first information to be negotiated and the second information to be negotiated may be the same or different, and the present disclosure does not limit this.

[0261] In some embodiments, the second information to be negotiated may include, for example, a charging configuration parameter (charging profile).

[0262] In some embodiments, among the third billing information carried in the second billing request message, the second information to be negotiated may be included. When the third network element 103 determines that the second information to be negotiated is feasible, the second information to be negotiated may be carried in the second billing response message and sent to the first network element 101.

[0263] Step 804: The first network element 101 sends a first charging request message to the second network element 102. The first charging request message carries first charging information of a terminal device using satellite services, and the first charging information includes second information to be negotiated.

[0264] For the optional implementation of step 804, reference can be made to Figure 3 the optional implementation of step 301 in Figure 3 and other related parts in the embodiments involved. Details are not described herein again.

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

[0266] Step 805: The second network element 102 generates a first charging data record (CDR) based on the first charging information. The first CDR is used to generate a charging bill.

[0267] For the optional implementation of step 805, reference can be made to Figure 3 the optional implementation of step 302 in Figure 3 and other related parts in the embodiments involved. Details are not described herein again.

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

[0269] For the optional implementation of step 806, reference can be made to Figure 3 the optional implementation of step 303 in Figure 3 and other related parts in the embodiments involved. Details are not described herein again.

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

[0271] In some embodiments, reference can be made to Figure 8 other optional implementations described before or after the corresponding specification.

[0272] The charging method for satellite communication provided by the embodiments of the present disclosure enables a second network element to generate a first CDR for generating a charging bill based on the first charging information of the terminal device using satellite services provided by a first network element. A third network element can generate a second CDR for generating a charging bill based on the third charging information of the terminal device provided by the first network element. Since the second network element and the third network element perform charging based on the same data source, the problem of inconsistent charging results between the second network and the first network can be avoided, and the accuracy of the charging results for satellite communication is improved. Moreover, by the first network element receiving second information to be negotiated from the third network element and carrying the second information to be negotiated in the first charging request message and sending it to the second network element, information negotiation dominated by the first network can be achieved.

[0273] Figure 9 is an interaction schematic diagram of the charging method for satellite communication shown according to the embodiments of the present disclosure. As Figure 9 shown, the method involved in the embodiments of the present disclosure is applied to Figure 2 the satellite communication charging system 100 shown in Figure 6 、 Figure 7 or Figure 8 Based on the charging method for satellite communication shown, the method further includes the following steps 901-906.

[0274] Step 901, the first network element 101 sends second information to be updated to the third network element 103.

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

[0276] Among them, the second charging update request message is used to request an update to the generated CDR.

[0277] The second information to be updated is the information that needs to be updated. Among them, the second information to be updated may be the same as or different from the first information to be updated, and the present disclosure does not limit this.

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

[0279] In some embodiments, the second information to be updated may include QBC information and / or FBC information. Optionally, the QBC information may include quota information, and / or the FBC information may include quota information. Among them, the quota information may include quota application information for applying for a quota and / or quota usage information for informing the used quota.

[0280] In some embodiments, the second information to be updated may be sent when an update trigger condition is met, where the update trigger condition includes at least one of the following conditions:

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

[0282] The limit of the rate group is reached;

[0283] The quota limit is reached.

[0284] Among them, for the description of the update trigger condition, reference can be made to other embodiments, which will not be elaborated here.

[0285] In some embodiments, when the update trigger condition includes a change in the charging condition, the second information to be updated may include information related to the changed charging condition. For example, when the update trigger condition is a change in the satellite identifier, the second information to be updated may include the satellite identifier of the latest satellite providing the satellite service.

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

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

[0288] Step 902, the third network element 103 updates the second CDR based on the second information to be updated.

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

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

[0291] In some embodiments, in response to receiving the second information to be updated, the third network element 103 may send a second charging update response message to the first network element 101. Among them, the second charging update response message is used to indicate that the third network element 103 has received the second information to be updated. Correspondingly, step 903 may be executed after step 902, or before step 902, or simultaneously with step 902.

[0292] Figure 9Taking the execution of step 903 after step 902 as an example for illustration.

[0293] Step 904, the first network element 101 sends second information to be updated to the second network element 102.

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

[0295] Among them, the third charging update request message is used to request an update to the generated CDR.

[0296] In some embodiments, the second information to be updated may be sent when an update trigger condition is met, where the update trigger condition includes at least one of the following conditions:

[0297] The charging condition changes, where the charging condition includes at least one of the type of satellite providing satellite services, satellite service quality, and satellite identifier;

[0298] The limit of the rate group is reached;

[0299] The quota limit is reached.

[0300] Among them, for the description of the update trigger condition, reference may be made to other embodiments, which will not be elaborated here.

[0301] Step 905, the second network element 102 updates the first CDR based on the second information to be updated.

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

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

[0304] In some embodiments, in response to receiving the second information to be updated, the second network element 102 may send a third charging update response message to the first network element 101. Among them, the third charging update response message is used to indicate that the second network element 102 has received the second information to be updated. Correspondingly, step 906 may be executed after step 905, or before step 905, or simultaneously with step 905.

[0305] Figure 9 Taking the execution of step 906 after step 905 as an example for illustration.

[0306] It should be noted that steps 901-903 and steps 904-906 can be executed simultaneously, or steps 901-903 can be executed before step 904, or steps 901-903 can be executed after step 904. The present disclosure does not limit this.

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

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

[0309] In some embodiments, reference can be made to Figure 9 other optional implementation manners described before or after the corresponding specification.

[0310] The charging method for satellite communication provided by the embodiments of the present disclosure sends second information to be updated to a third network element and a second network element through a first network element. The second network element and the third network element update the CDRs they have generated according to the second information to be updated sent by the first network element, which can ensure the timeliness and consistency of the charging results generated by the second network element and the third network element.

[0311] Figure 10 is an interaction schematic diagram of the charging method for satellite communication shown according to the embodiments of the present disclosure. As Figure 10 shown, the method involved in the embodiments of the present disclosure is applied to Figure 2 the satellite communication charging system 100 shown. Based on the charging methods shown in Figure 6 , Figure 7 , Figure 8 or Figure 9 shown, the method further includes the following steps 1001-1006.

[0312] Step 1001, the first network element 101 sends a second charging termination instruction to the second network element 102.

[0313] Among them, the second charging termination instruction is used to close the first CDR.

[0314] In some embodiments, the first network element 101 can send a second charging termination request message to the second network element 102, and the second charging termination instruction is carried in the message.

[0315] In some embodiments, the first network element 101 can send a second charging termination instruction or a second charging termination request message carrying the second charging termination instruction to the second network element 102 in response to detecting the release of the data connection session of the established terminal device.

[0316] In some embodiments, the second charging termination request message may further carry the fourth charging information of the above terminal device using the satellite service. The fourth charging information is used to update the first CDR. The fourth charging information may be the charging information of the terminal device generated when the data connection session of the terminal device is released. The information included in the fourth charging information may be set as needed, and specifically, reference may be made to the first charging information, which will not be elaborated here. In the embodiments of the present application, the name of the fourth charging information is not limited, and it may be, for example, "charging-related information", "information for charging", etc.

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

[0318] Step 1002, the second network element 102 closes the first CDR based on the second charging termination indication.

[0319] Step 1003, the second network element 102 sends a second charging termination response message to the first network element 101.

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

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

[0322] Figure 10 Taking the case where step 1003 is executed after step 1002 as an example for illustration.

[0323] Step 1004, the first network element 101 sends a third charging termination indication to the third network element 103.

[0324] The third charging termination indication is used to close the second CDR.

[0325] In some embodiments, the first network element 101 may send a third charging termination request message to the third network element 103, and the third charging termination indication is carried in the message.

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

[0327] In some embodiments, the third charging termination request message may further carry the fifth charging information of the above-mentioned terminal device using the satellite service. The fifth charging information is used to update the second CDR. The fifth charging information may be the charging information of the terminal device generated when the data connection session of the terminal device is released. The information included in the fifth charging information may be set as needed, specifically referring to the first charging information, which will not be elaborated here. In the embodiments of the present application, the name of the fifth charging information is not limited, and it may be, for example, "charging-related information", "information for charging", etc. In some embodiments, the fifth charging information and the fourth charging information may include the same charging information.

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

[0329] Step 1005, the third network element 103 closes the second CDR based on the third charging termination indication.

[0330] Step 1006, the third network element 103 sends a third charging termination response message to the first network element 101.

[0331] In some embodiments, in response to closing the second CDR, the third network element 103 may send a third charging termination response message to the first network element 101. The third charging termination response message is used to indicate that the second CDR generated previously has been closed. Correspondingly, step 1006 may be executed after step 1005.

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

[0333] Figure 10 Taking the example that step 1006 is executed after step 1005 for illustration.

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

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

[0336] In some embodiments, reference may be made to Figure 10 other optional implementation manners described before or after the corresponding specification.

[0337] The charging method for satellite communication provided by the embodiments of the present disclosure enables a first network element to send a second charging termination indication to a second network element and a third charging termination indication to a third network element, so that the second network element and the third network element can timely close the CDRs they have generated according to the received charging termination indications, thereby ensuring that the second network element and the third network element stop charging in a timely manner and ensuring the consistency of the charging results generated by the second network element and the third network element.

[0338] Figure 11 is a schematic flowchart of the charging method for satellite communication shown in the embodiments of the present disclosure. As Figure 11 shown, the method involved in the embodiments of the present disclosure is applied to a first network element deployed in a first network, and the method includes the following step 1101.

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

[0340] For the specific implementation process, principle, and optional implementation manners of step 1101, reference may be made to the relevant parts in other embodiments and will not be elaborated here.

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

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

[0343] In some embodiments, the SMF network element may determine the second network element according to at least one of the following information:

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

[0345] The charging feature information provided by the unified data management function UDM;

[0346] CHF instances discovered by the Network Storage Function NRF;

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

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

[0349] Satellite Service Indicator SSI, used to indicate that the terminal device accesses the first network through satellite services.

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

[0351] Satellite service type indicator, used to indicate that the satellite service is a backhaul service or a terminal direct connection service;

[0352] Satellite type indicator, used to indicate the type of the satellite providing the satellite service;

[0353] Satellite service quality;

[0354] Satellite identifier and / or constellation identifier;

[0355] Operator identifier.

[0356] In some embodiments, the method may further include: the first network element determines that the terminal device accesses the first network through satellite services.

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

[0358] In some embodiments, the second network element may further send a first billing response message to the first network element, and correspondingly, the first network element may also receive the first billing response message sent by the second network element.

[0359] For the satellite communication billing method provided by the embodiments of the present disclosure, the first network element deployed in the first network may send the first billing information of the terminal device using satellite services to the second network element deployed in the second network, where the first billing information is used to generate a first Call Detail Record CDR, and the first CDR is used to generate a billing statement. Thus, the second network element deployed in the second network can generate a first CDR for generating a billing statement based on the first billing information provided by the first network element deployed in the first network, thereby avoiding the problem of inconsistent billing results between the second network and the first network and improving the accuracy of the satellite communication billing results.

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

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

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

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

[0364] In some embodiments, the first information to be updated is sent when an update trigger condition is met, where the update trigger condition includes at least one of the following conditions:

[0365] The charging condition changes, where the charging condition includes at least one of the type of satellite providing satellite services, satellite service quality, and satellite identifier;

[0366] The limit of the rate group is reached;

[0367] The quota limit is reached.

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

[0369] For the specific implementation process, principle, and optional implementation manners of steps 1201-1204, reference may be made to the relevant parts in other embodiments, which will not be elaborated here.

[0370] The communication method according to an embodiment of the present disclosure may include at least one of steps 1201 to 1204. For example, step 1201 may be implemented as an independent embodiment, step 1201 + 1203 may be implemented as an independent embodiment, step 1201 + 1202 + 1203 may be implemented as an independent embodiment, step 1201 + 1203 + 1204 may be implemented as an independent embodiment, step 1201 + 1202 + 1203 + 1204 may be implemented as an independent embodiment, etc., but not limited thereto.

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

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

[0373] The billing method for satellite communication provided by the embodiments of the present disclosure enables a second network element deployed in a second network to generate a first CDR for generating a billing statement based on the first billing information provided by a first network element deployed in a first network, thereby avoiding the problem of inconsistent billing results between the second network and the first network and improving the accuracy of the billing results for satellite communication. Moreover, the second network element can update the first CDR in a timely manner according to the first information to be updated sent by the first network element, thereby ensuring the timeliness of the billing results generated by the second network element.

[0374] Figure 13 is a schematic flowchart of the billing method for satellite communication shown according to the embodiments of the present disclosure. As Figure 13 shown, the method involved in the embodiments of the present disclosure is applied to a first network element deployed in a first network, and the method includes the following steps 1301-1304.

[0375] Step 1301, send the first billing information of the terminal device using the satellite service to a second network element deployed in a second network, where the first billing information is used to generate a first Call Detail Record (CDR), and the first CDR is used to generate a billing statement.

[0376] Step 1302, receive a first billing response message sent by the second network element.

[0377] Step 1303, send a first billing termination indication to the second network element, where the first billing termination indication is used to close the first CDR.

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

[0379] Step 1304, receive a first billing termination response message sent by the second network element.

[0380] For the specific implementation processes, principles, and optional implementation manners of steps 1301-1304, reference can be made to the relevant parts in other embodiments, which will not be elaborated here.

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

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

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

[0384] The billing method for satellite communication provided by the embodiments of the present disclosure enables a second network element deployed in a second network to generate a first CDR for generating a billing statement based on the first billing information provided by a first network element deployed in a first network, thereby avoiding the problem of inconsistent billing results between the second network and the first network and improving the accuracy of the billing results for satellite communication. Moreover, the second network element can timely close the first CDR according to the billing termination instruction sent by the first network element, thereby ensuring that the second network element stops billing in a timely manner.

[0385] Figure 14 is a schematic flowchart of the billing method for satellite communication shown according to the embodiments of the present disclosure. As Figure 14 shown, the method involved in the embodiments of the present disclosure is applied to a first network element deployed in a first network, and the method includes the following steps 1401 - 1404.

[0386] Step 1401, send a first billing request message to a second network element deployed in a second network, where the first billing request message carries the first billing information of the terminal device using the satellite service, and the first billing information is used to generate a first call data record CDR, and the first CDR is used to generate a billing statement.

[0387] Step 1402, receive a first billing response message sent by the second network element, where the first billing response message carries first information to be negotiated.

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

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

[0390] For the specific implementation processes, principles, and optional implementation manners of Steps 1401 - 1404, reference may be made to the relevant parts in other embodiments, which will not be elaborated here.

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

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

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

[0394] Charging feature information provided by the Unified Data Management (UDM) function;

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

[0396] Charging feature information locally provided by the SMF.

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

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

[0399] The charging method for satellite communication provided by the embodiments of the present disclosure enables a second network element to generate a first CDR for generating a charging bill based on the first charging information of a terminal device using satellite services provided by a first network element. A third network element can generate a second CDR for generating a charging bill based on the third charging information of the terminal device provided by the first network element. Since the second network element and the third network element perform charging based on the same data source, the problem of inconsistent charging results between the second network and the first network can be avoided, and the accuracy of the charging results for satellite communication can be improved. Moreover, by the first network element receiving first information to be negotiated from the second network element and carrying the first information to be negotiated in a second charging request message and sending it to the third network element, parameter negotiation dominated by the second network can be achieved.

[0400] Figure 15 is a schematic flowchart of the charging method for satellite communication shown according to the embodiments of the present disclosure. As Figure 15 shown, the method involved in the embodiments of the present disclosure is applied to a first network element deployed in a first network, and the method includes the following steps 1501-1504.

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

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

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

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

[0405] The specific implementation processes, principles, and optional implementation manners of steps 1501-1504 can be found in the relevant parts of other embodiments and will not be elaborated here.

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

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

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

[0409] The charging feature information provided by the Unified Data Management Function (UDM);

[0410] The CHF instance discovered by the Network Repository Function (NRF);

[0411] The charging feature information locally provided by the Session Management Function (SMF).

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

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

[0414] The charging method for satellite communication provided by the embodiments of the present disclosure enables the second network element to generate a first CDR for generating a charging bill based on the first charging information of the terminal device using satellite services provided by the first network element, and the third network element can generate a second CDR for generating a charging bill based on the third charging information of the terminal device provided by the first network element. Since the second network element and the third network element perform charging based on the same data source, the problem of inconsistent charging results between the second network and the first network can be avoided, and the accuracy of the charging results for satellite communication is improved. And by the first network element receiving the second information to be negotiated from the third network element and carrying the second information to be negotiated in the first charging request message and sending it to the second network element, parameter negotiation dominated by the first network can be achieved.

[0415] Figure 16 It is a schematic flowchart of the charging method for satellite communication shown in the embodiments of the present disclosure. As Figure 16 shown, the method involved in the embodiments of the present disclosure is applied to the first network element deployed in the first network. Based on the charging method for satellite communication shown in Figure 14 or 15, this method further includes the following steps 1601 - 1604.

[0416] Step 1601, send the second information to be updated to the third network element, where the second information to be updated is used to update the second CDR.

[0417] Step 1602: Receive the second charging update response message sent by the third network element.

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

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

[0420] The specific implementation processes, principles, and optional implementation manners of steps 1601 - 1604 can be found in the relevant parts of other embodiments and will not be elaborated here.

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

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

[0423] The charging method for satellite communication provided by the embodiments of the present disclosure enables the second network element and the third network element to update the CDRs they have generated according to the second information to be updated sent by the first network element by sending the second information to be updated from the first network element to the third network element and the second network element, thereby ensuring the timeliness and consistency of the charging results generated by the second network element and the third network element.

[0424] Figure 17 It is a schematic flowchart of the charging method for satellite communication shown according to the embodiments of the present disclosure. As Figure 17 shown, the method involved in the embodiments of the present disclosure is applied to the first network element deployed in the first network. Based on the charging method for satellite communication shown in Figure 14 or 15, the method further includes the following steps 1701 - 1704.

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

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

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

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

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

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

[0431] The specific implementation processes, principles, and alternative implementation manners of steps 1701-1704 may refer to the relevant parts in other embodiments and will not be elaborated here.

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

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

[0434] The charging method for satellite communication provided by the embodiments of the present disclosure sends a second charging termination indication to a second network element and a third charging termination indication to a third network element through a first network element, so that the second network element and the third network element can timely close the CDRs they have generated according to the charging termination indication sent by the first network element, thereby ensuring that the second network element and the third network element stop charging in a timely manner to ensure the consistency of the charging results generated by the second network element and the third network element.

[0435] Figure 18 is a schematic flowchart of the charging method for satellite communication shown according to the embodiments of the present disclosure. As Figure 18 shown, the method involved in the embodiments of the present disclosure is applied to a second network element deployed in a second network, and the method includes the following steps 1801-1802.

[0436] Step 1801: Receive first charging information sent by a first network element deployed in a first network, where the first charging information includes charging information of a terminal device using satellite services.

[0437] In some embodiments, the first charging information includes:

[0438] A satellite service indication (SSI) for indicating that the terminal device accesses the first network through satellite services.

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

[0440] A satellite service type indication for indicating whether the satellite service is a backhaul service or a terminal direct connection service;

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

[0442] Quality of satellite service;

[0443] Satellite identification and / or constellation identification;

[0444] Operator identification.

[0445] In some embodiments, the first charging information is sent when it is determined that the terminal device accesses the first network through satellite services.

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

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

[0448] For the specific implementation process, principle, and optional implementation methods of steps 1801-1802, reference can be made to the relevant parts in other embodiments and will not be elaborated here.

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

[0450] For the charging method of satellite communication provided in the embodiments of the present disclosure, the second network element may receive the first charging information sent by the first network element deployed in the first network, and generate a first charging data record CDR for generating a charging bill based on the first charging information. Thus, through the second network element deployed in the second network, based on the first charging information provided by the first network element deployed in the first network, a first CDR for generating a charging bill is generated, thereby avoiding the problem of inconsistent charging results between the second network and the first network and improving the accuracy of the charging results of satellite communication.

[0451] Figure 19 It is a schematic flowchart of the charging method of satellite communication shown in the embodiments of the present disclosure. As Figure 19 shown, the method involved in the embodiments of the present disclosure is applied to a second network element deployed in the second network. The method includes the following steps 1901-1906.

[0452] Step 1901: Receive the first charging information sent by the first network element deployed in the first network, where the first charging information includes the charging information of the terminal device using satellite services.

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

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

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

[0456] Among them, the information to be updated can be the first information to be updated or the second information to be updated in the foregoing embodiments.

[0457] In some embodiments, the information to be updated is sent when an update trigger condition is met. Among them, the update trigger condition includes at least one of the following conditions:

[0458] The charging condition changes, where the charging condition includes at least one of the type of satellite providing satellite services, the quality of satellite services, and the satellite identifier;

[0459] The limit of the rate group is reached;

[0460] The quota limit is reached.

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

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

[0463] Among them, the charging update response message can be the first charging update response message or the third charging update response message in the foregoing embodiments.

[0464] For the specific implementation processes, principles, and optional implementation manners of Steps 1901 - 1906, reference can be made to the relevant parts in other embodiments, which will not be elaborated here.

[0465] In some embodiments, Step 1903 is optional, and in different embodiments, one or more of these steps can be omitted or replaced.

[0466] In some embodiments, Step 1906 is optional, and in different embodiments, one or more of these steps can be omitted or replaced.

[0467] The charging method for satellite communication provided by the embodiments of the present disclosure, the second network element deployed in the second network, can generate a first CDR for generating a charging bill based on the first charging information provided by the first network element deployed in the first network, thereby avoiding the problem of inconsistent charging results between the second network and the first network and improving the accuracy of the charging results for satellite communication. Moreover, the second network element can update the first CDR in a timely manner according to the information to be updated sent by the first network element, thereby ensuring the timeliness of the charging results generated by the second network element.

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

[0469] Step 2001, receive first billing information sent by a first network element deployed in a first network, where the first billing information includes billing information of a terminal device using satellite services.

[0470] Step 2002, generate a first call detail record CDR based on the first billing information, and the first CDR is used to generate a billing statement.

[0471] Step 2003, send a first billing response message to the first network element.

[0472] Step 2004, receive a billing termination indication sent by the first network element.

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

[0474] Among them, the billing termination indication can be the first billing termination indication or the second billing termination indication in the foregoing embodiments.

[0475] Step 2005, close the first CDR based on the billing termination indication.

[0476] Step 2006, send a billing termination response message to the first network element.

[0477] Among them, the billing update response message can be the first billing termination response message or the second billing termination response message in the foregoing embodiments.

[0478] For the specific implementation processes, principles, and optional implementation manners of steps 2001-2006, reference can be made to the related parts in other embodiments, which will not be elaborated here.

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

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

[0481] The billing method for satellite communication provided by the embodiments of the present disclosure. The second network element deployed in the second network can generate a first CDR for generating a billing statement based on the first billing information provided by the first network element deployed in the first network, thereby avoiding the problem of inconsistent billing results between the second network and the first network and improving the accuracy of the billing results for satellite communication. Moreover, the second network element can close the first CDR in a timely manner according to the billing termination instruction sent by the first network element, so as to ensure that the second network element stops billing in a timely manner.

[0482] The embodiments of the present disclosure also propose a device for implementing any of the above methods. For example, a device is proposed. The above device includes units or modules for implementing the steps performed by the first network element in any of the above methods. Again, another device is proposed, including units or modules for implementing the steps performed by the second network element in any of the above methods.

[0483] It should be understood that the division of the units or modules in the above device is only a division of logical functions. In actual implementation, they can be fully or partially integrated into a physical entity or physically separated. In addition, the units or modules in the device can 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 instructions are stored in the memory. The processor calls the instructions stored in the memory to implement any of the above methods or the functions of the units or modules of the above device. 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 inside or outside the device. Alternatively, the units or modules in the device can be implemented in the form of a hardware circuit, and the functions of some or all of the units or modules can be implemented through the design of the hardware circuit. The above hardware circuit can be understood as one or more processors. For example, in one implementation, the above hardware circuit is an application-specific integrated circuit (ASIC), and the functions of some or all of the above units or modules are implemented through the design of the logical relationship of the components in the circuit. Again, in another implementation, the above hardware circuit can be implemented through 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 through a configuration file to implement the functions of some or all of the above units or modules. All the units or modules of the above device can be fully implemented in the form of a processor calling software, or fully implemented in the form of a hardware circuit, or partially implemented in the form of a processor calling software, and the remaining part is implemented in the form of a hardware circuit.

[0484] In the embodiments of the present disclosure, a processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and running capabilities, 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), etc.; in another implementation, the processor can achieve certain functions through the logical relationship of hardware circuits, and the logical relationship of the above hardware circuits is fixed or can be reconfigured. For example, the processor is a hardware circuit implemented by 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 to implement the configuration of the hardware circuit 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.

[0485] Figure 21 is a schematic structural diagram of a billing device for satellite communication proposed in the embodiments of the present disclosure. Among them, the billing device for satellite communication can be applied to an electronic device, such as the first network element in the foregoing embodiments. As Figure 21 shown, the satellite communication billing device 2100 may include at least one of a transceiver module 2101, a processing module 2102, etc.

[0486] In some embodiments, the transceiver module 2101 is configured to send first billing information of a terminal device using satellite services to a second network element deployed in a second network, where the first billing information is used to generate a first Call Detail Record (CDR), and the first CDR is used to generate a billing statement.

[0487] In some embodiments, the processing module 2102 is configured to determine that the terminal device accesses the first network through satellite services.

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

[0489] In some embodiments, the first charging information includes:

[0490] A satellite service indication (SSI) for indicating that the terminal device accesses the first network through satellite services.

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

[0492] A satellite service type indication for indicating whether the satellite service is a backhaul service or a terminal direct connection service;

[0493] A satellite type indication for indicating the type of the satellite providing the satellite service;

[0494] The quality of satellite service;

[0495] The satellite identifier and / or the constellation identifier;

[0496] The operator identifier.

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

[0498] In some embodiments, the first information to be updated is sent when an update trigger condition is met, where the update trigger condition includes at least one of the following conditions:

[0499] The charging condition changes, where the charging condition includes at least one of the type of the satellite providing the satellite service, the quality of satellite service, and the satellite identifier;

[0500] The limit of the rate group is reached;

[0501] The quota limit is reached.

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

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

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

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

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

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

[0508] In some embodiments, the second and / or third network element(s) is / are determined by the SMF network element according to at least one of the following information:

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

[0510] Charging feature information provided by a unified data management function (UDM);

[0511] CHF instances discovered by a network repository function (NRF);

[0512] Charging feature information locally provided by the SMF.

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

[0514] In some embodiments, the transceiver module 2101 is configured to send a second charging termination indication to the second network element, where the second charging termination indication is used to close a first CDR; and send a third charging termination indication to the third network element, where the third charging termination indication is used to close a second CDR.

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

[0516] Figure 22 It is a schematic structural diagram of a charging device for satellite communication proposed by an embodiment of the present disclosure. Among them, the charging device for satellite communication can be applied to an electronic device, such as the second network element in the foregoing embodiment. As Figure 22 shown, the satellite communication charging device 2200 may include at least one of a transceiver module 2201, a processing module 2202, etc.

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

[0518] In some embodiments, the first charging information is sent when it is determined that the terminal device accesses the first network through satellite services.

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

[0520] In some embodiments, the first charging information includes:

[0521] A satellite service indication SSI, which is used to indicate that the terminal device accesses the first network through satellite services.

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

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

[0524] A satellite type indication, which is used to indicate the type of the satellite providing the satellite service;

[0525] The satellite service quality;

[0526] A satellite identifier and / or a constellation identifier;

[0527] An operator identifier.

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

[0529] In some embodiments, the information to be updated is sent when an update trigger condition is met, where the update trigger condition includes at least one of the following conditions:

[0530] The charging condition changes, where the charging condition includes at least one of the type of satellite providing satellite services, the quality of satellite services, and the satellite identifier;

[0531] The limit of the rate group is reached;

[0532] The quota limit is reached.

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

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

[0535] Figure 23 It is a schematic structural diagram of an electronic device 2300 proposed by an embodiment of the present disclosure. The electronic device 2300 may be the above-mentioned first network element, or the above-mentioned second network element, or a chip, a chip system, or a processor that supports the first network element to implement any of the above methods, and may also be a chip, a chip system, or a processor that supports the second network element to implement any of the above methods. The electronic device 2300 can be used to implement the methods described in the above method embodiments, and for details, reference can be made to the descriptions in the above method embodiments.

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

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

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

[0539] In some embodiments, the transceiver 2303 may include a receiver and a transmitter, and the receiver and the transmitter may be separate or integrated. In some embodiments, terms such as transceiver, transceiver unit, transceiver machine, and transceiver circuit may be replaced with each other, terms such as transmitter, transmitter unit, transmitter machine, and transmitter circuit may be replaced with each other, and terms such as receiver, receiver unit, receiver machine, and receiver circuit may be replaced with each other.

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

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

[0542] Figure 24 is a schematic structural diagram of the chip 2400 proposed in the embodiments of the present disclosure. For the case where the electronic device 2300 can be a chip or a chip system, reference can be made to Figure 24Schematic diagram of the structure of the chip 2400 shown, but not limited thereto.

[0543] The chip 2400 includes one or more processors 2401, and the processor 2401 is used to call instructions to cause the chip 2400 to execute any of the above methods.

[0544] In some embodiments, the chip 2400 further includes one or more interface circuits 2402. The interface circuit 2402 is connected to the memory 2403. The interface circuit 2402 can be used to receive signals from the memory 2403 or other devices, and the interface circuit 2402 can be used to send signals to the memory 2403 or other devices. For example, the interface circuit 2402 can read the instructions stored in the memory 2403 and send the instructions to the processor 2401. In some embodiments, terms such as interface circuit, interface, transceiver pin, transceiver, etc. can be used interchangeably.

[0545] In some embodiments, the chip 2400 further includes one or more memories 2403 for storing instructions. In some embodiments, all or part of the memory 2403 can be outside the chip 2400.

[0546] The present disclosure also proposes a storage medium. Instructions are stored on the above storage medium. When the above instructions run on the electronic device 2300, the electronic device 2300 is caused to execute any of the above methods. In some embodiments, the above storage medium is an electronic storage medium. In some embodiments, the above storage medium is a computer-readable storage medium, but not limited thereto, and it can also be a storage medium readable by other devices. In some embodiments, the above storage medium can be a non-transitory storage medium, but not limited thereto, and it can also be a transitory storage medium.

[0547] The present disclosure also proposes a program product. When the above program product is executed by the electronic device 2300, the electronic device 2300 is caused to execute any of the above methods. In some embodiments, the above program product is a computer program product.

[0548] The present disclosure also proposes a computer program. When it runs on a computer, the computer is caused to execute any of the above methods.

[0549] It can be understood that the above-mentioned satellite communication billing device, electronic device, satellite communication billing system, storage medium, program product, and computer program are all used to execute the methods proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding methods, which will not be elaborated here.

[0550] In some embodiments, terms such as the billing method of satellite communication, the information processing method, and the communication method can be mutually replaced; terms such as the billing device of satellite communication, the information processing device, and the communication device can be mutually replaced; terms such as the information processing system and the communication system can be mutually replaced.

[0551] The embodiments of the present disclosure are not exhaustive. They are only illustrations of some embodiments and do not specifically limit the protection scope of the present disclosure. Without contradiction, each step in an embodiment can be implemented as an independent embodiment, and the steps can be combined arbitrarily. For example, the solution after removing some steps in an embodiment can also be implemented as an independent embodiment, and the order of the steps in an embodiment can be arbitrarily exchanged. Additionally, the optional implementation manners in an embodiment can be combined arbitrarily; moreover, the embodiments can be combined arbitrarily. For example, some or all of the steps of different embodiments can be combined arbitrarily, and an embodiment can be arbitrarily combined with the optional implementation manners of other embodiments.

[0552] In each embodiment of the present disclosure, without special instructions and logical conflicts, the terms and / or descriptions between the embodiments are consistent and can be referenced to each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

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

[0554] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular form, such as "a", "an", "the", "above", "said", "aforementioned", "this", etc., can mean "one and only one", or can also mean "one or more", "at least one", etc. For example, in the case of using articles such as "a", "an", "the" in English translation, the noun after the article can be understood as a singular expression form or a plural expression form.

[0555] In the embodiments of the present disclosure, "a plurality of" means two or more.

[0556] In some embodiments, terms such as "at least one of", "one or more", "a plurality of", "multiple", etc. can be mutually replaced.

[0557] In some embodiments, notations such as "at least one of A and B", "A and / or B", "in one case A, in another case B", "in response to one case A, in response to another case B", etc. may, according to the circumstances, include the following technical solutions: In some embodiments, A is performed (A is performed independently of B); in some embodiments, B is performed (B is performed independently of A); in some embodiments, one is selected from A and B for execution (A and B are selectively executed); in some embodiments, both A and B are performed (both A and B are performed). The same is true when there are more branches such as A, B, C, etc.

[0558] In some embodiments, notations such as "A or B" may, according to the circumstances, include the following technical solutions: In some embodiments, A is performed (A is performed independently of B); in some embodiments, B is performed (B is performed independently of A); in some embodiments, one is selected from A and B for execution (A and B are selectively executed). The same is true when there are more branches such as A, B, C, etc.

[0559] Prefix words such as "first", "second", etc. in the embodiments of the present disclosure are only used to distinguish different described objects, and do not constitute restrictions on the position, order, priority, quantity, content, etc. of the described objects. For the statements of the described objects, refer to the descriptions in the claims or the context of the embodiments. There should be no redundant restrictions due to the use of prefix words. For example, if the described object is "field", the ordinal numbers before "field" in "first field" and "second field" do not limit the position or order between the "fields", and "first" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of "first field" and "second field". Again, for example, if the described object is "level", the ordinal numbers before "level" in "first level" and "second level" do not limit the priority between the "levels". Again, for example, the quantity of the described object is not restricted by the ordinal number and can be one or more. Taking "first device" as an example, the quantity of "device" therein can be one or more. In addition, the objects modified by different prefix words can be the same or different. For example, if the described object is "device", "first device" and "second device" can be the same device or different devices, and their types can be the same or different; again, for example, if the described object is "information", "first information" and "second information" can be the same information or different information, and their contents can be the same or different.

[0560] In some embodiments, "including A", "containing A", "used to indicate A", "carrying A" can be interpreted as directly carrying A or as indirectly indicating A.

[0561] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "when...", "when...", "if...", "if..." can be mutually replaced.

[0562] 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 lower than", "above", etc. may 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", "below", etc. may be replaced with each other.

[0563] In some embodiments, "network" may be interpreted as the devices included in the network (e.g., access network devices, core network devices, etc.).

[0564] In some embodiments, devices, etc. may 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", "subject", etc. may be replaced with each other.

[0565] In some embodiments, terms such as "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. may be replaced with each other.

[0566] In some embodiments, the names of information and the like 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", "codebook", "codeword", "codepoint", "bit", "data", "program", "chip", etc. may be used interchangeably.

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

[0568] In some embodiments, data, information, etc. may be obtained after obtaining the consent of the user.

[0569] In addition, each element, each row, or each column in the tables of the embodiments of the present disclosure may be implemented as an independent embodiment, and any combination of any element, any row, and any column may also be implemented as an independent embodiment.

[0570] In some embodiments, "obtain", "acquire", "get", "receive", "transmit", "two-way transmission", "send and / or receive" may be used interchangeably, and it may be interpreted as receiving from other entities, obtaining from a protocol, obtaining from a higher layer, self-processing, self-implementation, etc.

[0571] In some embodiments, terms such as "send", "transmit", "report", "send down", "transmit", "two-way transmission", "send and / or receive" may be used interchangeably.

[0572] In some embodiments, terms such as "certain", "preseted", "preset", "set", "indicated", "a certain", "any", "first", etc. may be used interchangeably. "Specific A", "preseted A", "preset A", "set A", "indicated A", "a certain A", "any A", "first A" may be interpreted as A predefined in a protocol or the like, or as A obtained through setting, configuration, or indication, or as specific A, a certain A, any A, or first A, etc., but is not limited thereto.

[0573] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented in whole or in part 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, the processes or functions described in the embodiments of the present disclosure are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer program may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another. For example, the computer program may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains one or more integrated available media. The available media may be magnetic media (such as floppy disks, hard disks, magnetic tapes), optical media (such as high-density digital video discs (DVDs)), or semiconductor media (such as solid state disks (SSDs)), etc.

[0574] Those of ordinary skill in the art can realize that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in hardware or software depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present disclosure.

[0575] Those skilled in the art can 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 foregoing method embodiments, and will not be described herein again.

[0576] As described above, the above are only specific embodiments of the present disclosure, but the protection scope of the present disclosure is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present disclosure, and all should be covered by the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure should be subject to the protection scope of the claims.

Claims

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

2. The method according to claim 1, characterized in that The first billing information includes: The satellite service indication SSI is used to instruct the terminal device to access the first network via the satellite service.

3. The method according to claim 2, characterized in that The first billing information also includes at least one of the following information: A satellite service type indication, used to indicate whether the satellite service is a backhaul service or a terminal direct connection service; a satellite type indication, used to indicate the type of satellite providing the satellite service; Satellite service quality; Satellite identification and / or constellation identification; Operator ID.

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

5. The method according to claim 1, characterized in that: The first network is a terrestrial network, and the second network is a satellite network.

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

7. The method according to claim 6, characterized in that The first to-be-updated information is sent when an update triggering condition is met, wherein the update triggering condition includes at least one of the following conditions: The charging conditions are changed, wherein the charging conditions include at least one of the type of satellite providing the satellite service, the satellite service quality, and the satellite identification; The rate group limit is reached; The quota limit was reached.

8. The method according to any one of claims 1 to 5, characterized in that The method further comprises: A first billing termination indication is sent to the second network element, wherein the first billing termination indication is used to close the first CDR.

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

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

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

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

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

14. The method according to claim 13, characterized in that The second network element and / or the third network element is determined by the SMF network element according to at least one of the following information: at least one of a CHF address provided by a policy control function PCF for a data connection session of the terminal device, a CHF instance identifier associated with the data connection session, and / or a CHF set identifier; Unified data management (UDM) provides billing feature information; CHF instance discovered by the network storage function NRF; The billing characteristic information provided locally by the SMF.

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

16. The method according to claim 10, characterized in that The method further comprises: Sending a second charging termination indication to the second network element, wherein the second charging termination indication is used to close the first CDR; A third charging termination indication is sent to the third network element, wherein the third charging termination indication is used to close the second CDR.

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

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

19. The method according to claim 18, characterized in that The first billing information includes: The satellite service indication SSI is used to instruct the terminal device to access the first network via the satellite service.

20. The method according to claim 19, characterized in that The first billing information also includes at least one of the following information: A satellite service type indication, used to indicate whether the satellite service is a backhaul service or a terminal direct connection service; a satellite type indication, used to indicate the type of satellite providing the satellite service; Satellite service quality; Satellite identification and / or constellation identification; Operator ID.

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

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

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

24. The method according to claim 23, characterized in that The information to be updated is sent when an update trigger condition is met, wherein the update trigger condition includes at least one of the following conditions: The charging conditions are changed, wherein the charging conditions include at least one of the type of satellite providing the satellite service, the satellite service quality, and the satellite identification; The rate group limit is reached; The quota limit was reached.

25. The method according to any one of claims 18 to 22, characterized in that The method further comprises: receiving a charging termination instruction sent by the first network element; The first CDR is closed based on the charging termination indication.

26. The method according to claim 25, characterized in that The billing termination indication is carried in a first billing termination request message sent by the first network element to the second network element. The first billing termination request message also carries second billing information of the terminal device. The second billing information is used to update the first CDR.

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

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

29. An electronic device, characterized in that: include: one or more processors; one or more memories for storing instructions; The processor is used to call the instruction so that the electronic device executes the satellite communication billing method described in any one of claims 1-17, or executes the satellite communication billing method described in any one of claims 18-26.

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

31. The billing system according to claim 30, characterized in that: The system further includes a third network element deployed in the first network; the third network element is used for: receiving third charging information of a terminal device using satellite services sent by the first network element; Based on the third charging information, a second CDR is generated, where the second CDR is used to generate a charging bill.

32. The billing system according to claim 31, characterized in that: The third network element is further used for: Receiving second information to be updated sent by the first network element; The second CDR is updated based on the second information to be updated.

33. The billing system according to claim 31, characterized in that: The third network element is further used for: receiving a charging termination instruction sent by the first network element; The second CDR is closed based on the charging termination indication.

34. A storage medium storing instructions, characterized in that: When the instruction is executed on an electronic device, the electronic device executes the satellite communication charging method as claimed in any one of claims 1 to 17, or executes the satellite communication charging method as claimed in any one of claims 18 to 26.

Images