Charging method, device and equipment and non-instantaneous readable storage medium

Abstract

The invention provides a charging method, device and equipment and a non-instantaneous readable storage medium, and the method comprises the steps: obtaining charging information for communication between terminals through a satellite under the condition that a charging triggering condition is satisfied; and sending a charging data request to a second network element, wherein the charging data request carries the charging information. According to the scheme, related charging under a UE-satellite-UE scene (namely a scene in which terminals communicate through a satellite) can be supported and realized.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a billing method, apparatus, device and non-transiently readable storage medium. Background Technology

[0002] In the scenario of UE (User Equipment)-satellite-UE communication, IMS (IP Multimedia Subsystem) is currently unable to charge for UEs accessing via satellite; in the scenario of UE-satellite-UE, it is also unable to charge for packets transmitted via satellite.

[0003] As mentioned above, existing technologies have limitations in supporting billing for UE-satellite-UE scenarios. Summary of the Invention

[0004] The purpose of this application is to provide a billing method, apparatus, device, and non-transiently readable storage medium to solve the problem that the prior art cannot support the implementation of related billing for UE-satellite-UE scenarios.

[0005] To address the aforementioned technical problems, this application provides a billing method applied to a first network element, comprising:

[0006] If the billing trigger conditions are met, obtain billing information for communication between terminals via satellite;

[0007] A billing data request is sent to the second network element, the billing data request carrying the billing information.

[0008] Optionally, the billing trigger condition includes at least one of the following:

[0009] A session establishment request has been received;

[0010] A session re-establishment request has been received.

[0011] Received a session update request;

[0012] Received session release request;

[0013] Receive a handover instruction or release instruction for the first network element;

[0014] Received a Session Initiation Protocol (SIP) response.

[0015] Optionally, if the billing triggering conditions include receiving a session establishment request or receiving a SIP response, the billing data request is an initial billing data request;

[0016] And / or, if the billing triggering conditions include receiving a session re-establishment request, receiving a session update request, receiving a handover indication for the first network element, or receiving a SIP response, the billing data request is an update billing data request;

[0017] And / or, if the billing triggering conditions include receiving a session release request, receiving a release instruction for the first network element, or receiving a SIP response, the billing data request is an end-of-billing-data request.

[0018] Optionally, when the billing data request is an initial billing data request, an update billing data request, or a termination billing data request, the billing information includes at least one of the following:

[0019] The first information indicates that the service supports communication between terminals via satellite;

[0020] Insertion indication of the first network element;

[0021] The second information is the indication of the first network element on the ground;

[0022] The third information indicates the ground IP address of the first network element;

[0023] Ground communication start timestamp information;

[0024] Ground communication end timestamp information.

[0025] Optionally, when the billing data request is an initial billing data request, an update billing data request, or a termination billing data request, the billing information includes at least one of the following:

[0026] The first information indicates that the service supports communication between terminals via satellite;

[0027] Insertion indication of the first network element;

[0028] The satellite's identification information;

[0029] The fourth information is the indication of the first network element on the satellite;

[0030] The fifth piece of information indicates the on-board IP address of the first network element;

[0031] Satellite communication start timestamp information;

[0032] Satellite communication end timestamp information;

[0033] The sixth information indicates information about satellites that support inter-terminal communication via satellite.

[0034] Optional, also includes:

[0035] Receive the billing data response sent by the second network element.

[0036] This application also provides a billing method applied to a second network element, including:

[0037] Receive a billing data request sent by the first network element when the billing triggering conditions are met, wherein the billing data request carries billing information for communication between terminals via satellite;

[0038] Create a billing data record based on the billing data request.

[0039] Optionally, the billing trigger condition includes at least one of the following:

[0040] A session establishment request has been received;

[0041] A session re-establishment request has been received.

[0042] Received a session update request;

[0043] Received session release request;

[0044] Receive a handover instruction or release instruction for the first network element;

[0045] Received a Session Initiation Protocol (SIP) response.

[0046] Optionally, if the billing triggering conditions include receiving a session establishment request or receiving a SIP response, the billing data request is an initial billing data request;

[0047] And / or, if the billing triggering conditions include receiving a session re-establishment request, receiving a session update request, receiving a handover indication for the first network element, or receiving a SIP response, the billing data request is an update billing data request;

[0048] And / or, if the billing triggering conditions include receiving a session release request, receiving a release instruction for the first network element, or receiving a SIP response, the billing data request is an end-of-billing-data request.

[0049] Optionally, when the billing data request is an initial billing data request, an update billing data request, or a termination billing data request, the billing information includes at least one of the following:

[0050] The first information indicates that the service supports communication between terminals via satellite;

[0051] Insertion indication of the first network element;

[0052] The second information is the indication of the first network element on the ground;

[0053] The third information indicates the ground IP address of the first network element;

[0054] Ground communication start timestamp information;

[0055] Ground communication end timestamp information.

[0056] Optionally, when the billing data request is an initial billing data request, an update billing data request, or a termination billing data request, the billing information includes at least one of the following:

[0057] The first information indicates that the service supports communication between terminals via satellite;

[0058] Insertion indication of the first network element;

[0059] The satellite's identification information;

[0060] The fourth information is the indication of the first network element on the satellite;

[0061] The fifth piece of information indicates the on-board IP address of the first network element;

[0062] Satellite communication start timestamp information;

[0063] Satellite communication end timestamp information;

[0064] The sixth information indicates information about satellites that support inter-terminal communication via satellite.

[0065] Optional, also includes:

[0066] Send a billing data response to the first network element.

[0067] Optionally, the billing data record includes at least one of the following:

[0068] The first information indicates that the service supports communication between terminals via satellite;

[0069] Insertion indication of the first network element;

[0070] The second information is the indication of the first network element on the ground;

[0071] The third information indicates the ground IP address of the first network element;

[0072] Ground communication start timestamp information;

[0073] Ground communication end timestamp information;

[0074] The satellite's identification information;

[0075] The fourth information is the indication of the first network element on the satellite;

[0076] The fifth piece of information indicates the on-board IP address of the first network element;

[0077] Satellite communication start timestamp information;

[0078] Satellite communication end timestamp information;

[0079] The sixth information indicates information about satellites that support inter-terminal communication via satellite.

[0080] This application embodiment also provides a billing device, which is a first network element, including a memory, a transceiver, and a processor:

[0081] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:

[0082] If the billing trigger conditions are met, obtain billing information for communication between terminals via satellite;

[0083] The transceiver sends a billing data request to the second network element, and the billing data request carries the billing information.

[0084] Optionally, the billing trigger condition includes at least one of the following:

[0085] A session establishment request has been received;

[0086] A session re-establishment request has been received.

[0087] Received a session update request;

[0088] Received session release request;

[0089] Receive a handover instruction or release instruction for the first network element;

[0090] Received a Session Initiation Protocol (SIP) response.

[0091] Optionally, if the billing triggering conditions include receiving a session establishment request or receiving a SIP response, the billing data request is an initial billing data request;

[0092] And / or, if the billing triggering conditions include receiving a session re-establishment request, receiving a session update request, receiving a handover indication for the first network element, or receiving a SIP response, the billing data request is an update billing data request;

[0093] And / or, if the billing triggering conditions include receiving a session release request, receiving a release instruction for the first network element, or receiving a SIP response, the billing data request is an end-of-billing-data request.

[0094] Optionally, when the billing data request is an initial billing data request, an update billing data request, or a termination billing data request, the billing information includes at least one of the following:

[0095] The first information indicates that the service supports communication between terminals via satellite;

[0096] Insertion indication of the first network element;

[0097] The second information is the indication of the first network element on the ground;

[0098] The third information indicates the ground IP address of the first network element;

[0099] Ground communication start timestamp information;

[0100] Ground communication end timestamp information.

[0101] Optionally, when the billing data request is an initial billing data request, an update billing data request, or a termination billing data request, the billing information includes at least one of the following:

[0102] The first information indicates that the service supports communication between terminals via satellite;

[0103] Insertion indication of the first network element;

[0104] The satellite's identification information;

[0105] The fourth information is the indication of the first network element on the satellite;

[0106] The fifth piece of information indicates the on-board IP address of the first network element;

[0107] Satellite communication start timestamp information;

[0108] Satellite communication end timestamp information;

[0109] The sixth information indicates information about satellites that support inter-terminal communication via satellite.

[0110] Optionally, the operation further includes:

[0111] The transceiver receives the billing data response sent by the second network element.

[0112] This application embodiment also provides a billing device, which is a second network element, including a memory, a transceiver, and a processor:

[0113] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:

[0114] The transceiver receives a billing data request sent by the first network element when the billing triggering conditions are met. The billing data request carries billing information for communication between terminals via satellite.

[0115] Create a billing data record based on the billing data request.

[0116] Optionally, the billing trigger condition includes at least one of the following:

[0117] A session establishment request has been received;

[0118] A session re-establishment request has been received.

[0119] Received a session update request;

[0120] Received session release request;

[0121] Receive a handover instruction or release instruction for the first network element;

[0122] Received a Session Initiation Protocol (SIP) response.

[0123] Optionally, if the billing triggering conditions include receiving a session establishment request or receiving a SIP response, the billing data request is an initial billing data request;

[0124] And / or, if the billing triggering conditions include receiving a session re-establishment request, receiving a session update request, receiving a handover indication for the first network element, or receiving a SIP response, the billing data request is an update billing data request;

[0125] And / or, if the billing triggering conditions include receiving a session release request, receiving a release instruction for the first network element, or receiving a SIP response, the billing data request is an end-of-billing-data request.

[0126] Optionally, when the billing data request is an initial billing data request, an update billing data request, or a termination billing data request, the billing information includes at least one of the following:

[0127] The first information indicates that the service supports communication between terminals via satellite;

[0128] Insertion indication of the first network element;

[0129] The second information is the indication of the first network element on the ground;

[0130] The third information indicates the ground IP address of the first network element;

[0131] Ground communication start timestamp information;

[0132] Ground communication end timestamp information.

[0133] Optionally, when the billing data request is an initial billing data request, an update billing data request, or a termination billing data request, the billing information includes at least one of the following:

[0134] The first information indicates that the service supports communication between terminals via satellite;

[0135] Insertion indication of the first network element;

[0136] The satellite's identification information;

[0137] The fourth information is the indication of the first network element on the satellite;

[0138] The fifth piece of information indicates the on-board IP address of the first network element;

[0139] Satellite communication start timestamp information;

[0140] Satellite communication end timestamp information;

[0141] The sixth information indicates information about satellites that support inter-terminal communication via satellite.

[0142] Optionally, the operation further includes:

[0143] The transceiver sends a billing data response to the first network element.

[0144] Optionally, the billing data record includes at least one of the following:

[0145] The first information indicates that the service supports communication between terminals via satellite;

[0146] Insertion indication of the first network element;

[0147] The second information is the indication of the first network element on the ground;

[0148] The third information indicates the ground IP address of the first network element;

[0149] Ground communication start timestamp information;

[0150] Ground communication end timestamp information;

[0151] The satellite's identification information;

[0152] The fourth information is the indication of the first network element on the satellite;

[0153] The fifth piece of information indicates the on-board IP address of the first network element;

[0154] Satellite communication start timestamp information;

[0155] Satellite communication end timestamp information;

[0156] The sixth information indicates information about satellites that support inter-terminal communication via satellite.

[0157] This application embodiment also provides a billing device, applied to a first network element, including:

[0158] The first acquisition unit is used to acquire billing information for communication between terminals via satellite when the billing triggering conditions are met.

[0159] The first sending unit is used to send a billing data request to the second network element, wherein the billing data request carries the billing information.

[0160] Optionally, the billing trigger condition includes at least one of the following:

[0161] A session establishment request has been received;

[0162] A session re-establishment request has been received.

[0163] Received a session update request;

[0164] Received session release request;

[0165] Receive a handover instruction or release instruction for the first network element;

[0166] Received a Session Initiation Protocol (SIP) response.

[0167] Optionally, if the billing triggering conditions include receiving a session establishment request or receiving a SIP response, the billing data request is an initial billing data request;

[0168] And / or, if the billing triggering conditions include receiving a session re-establishment request, receiving a session update request, receiving a handover indication for the first network element, or receiving a SIP response, the billing data request is an update billing data request;

[0169] And / or, if the billing triggering conditions include receiving a session release request, receiving a release instruction for the first network element, or receiving a SIP response, the billing data request is an end-of-billing-data request.

[0170] Optionally, when the billing data request is an initial billing data request, an update billing data request, or a termination billing data request, the billing information includes at least one of the following:

[0171] The first information indicates that the service supports communication between terminals via satellite;

[0172] Insertion indication of the first network element;

[0173] The second information is the indication of the first network element on the ground;

[0174] The third information indicates the ground IP address of the first network element;

[0175] Ground communication start timestamp information;

[0176] Ground communication end timestamp information.

[0177] Optionally, when the billing data request is an initial billing data request, an update billing data request, or a termination billing data request, the billing information includes at least one of the following:

[0178] The first information indicates that the service supports communication between terminals via satellite;

[0179] Insertion indication of the first network element;

[0180] The satellite's identification information;

[0181] The fourth information is the indication of the first network element on the satellite;

[0182] The fifth piece of information indicates the on-board IP address of the first network element;

[0183] Satellite communication start timestamp information;

[0184] Satellite communication end timestamp information;

[0185] The sixth information indicates information about satellites that support inter-terminal communication via satellite.

[0186] Optional, also includes:

[0187] The first receiving unit is used to receive the billing data response sent by the second network element.

[0188] This application also provides a billing device applied to a second network element, comprising:

[0189] The second receiving unit is used to receive a billing data request sent by the first network element when the billing triggering conditions are met. The billing data request carries billing information for communication between terminals via satellite.

[0190] The first creation unit is used to create a billing data record based on the billing data request.

[0191] Optionally, the billing trigger condition includes at least one of the following:

[0192] A session establishment request has been received;

[0193] A session re-establishment request has been received.

[0194] Received a session update request;

[0195] Received session release request;

[0196] Receive a handover instruction or release instruction for the first network element;

[0197] Received a Session Initiation Protocol (SIP) response.

[0198] Optionally, if the billing triggering conditions include receiving a session establishment request or receiving a SIP response, the billing data request is an initial billing data request;

[0199] And / or, if the billing triggering conditions include receiving a session re-establishment request, receiving a session update request, receiving a handover indication for the first network element, or receiving a SIP response, the billing data request is an update billing data request;

[0200] And / or, if the billing triggering conditions include receiving a session release request, receiving a release instruction for the first network element, or receiving a SIP response, the billing data request is an end-of-billing-data request.

[0201] Optionally, when the billing data request is an initial billing data request, an update billing data request, or a termination billing data request, the billing information includes at least one of the following:

[0202] The first information indicates that the service supports communication between terminals via satellite;

[0203] Insertion indication of the first network element;

[0204] The second information is the indication of the first network element on the ground;

[0205] The third information indicates the ground IP address of the first network element;

[0206] Ground communication start timestamp information;

[0207] Ground communication end timestamp information.

[0208] Optionally, when the billing data request is an initial billing data request, an update billing data request, or a termination billing data request, the billing information includes at least one of the following:

[0209] The first information indicates that the service supports communication between terminals via satellite;

[0210] Insertion indication of the first network element;

[0211] The satellite's identification information;

[0212] The fourth information is the indication of the first network element on the satellite;

[0213] The fifth piece of information indicates the on-board IP address of the first network element;

[0214] Satellite communication start timestamp information;

[0215] Satellite communication end timestamp information;

[0216] The sixth information indicates information about satellites that support inter-terminal communication via satellite.

[0217] Optional, also includes:

[0218] The second sending unit is used to send a billing data response to the first network element.

[0219] Optionally, the billing data record includes at least one of the following:

[0220] The first information indicates that the service supports communication between terminals via satellite;

[0221] Insertion indication of the first network element;

[0222] The second information is the indication of the first network element on the ground;

[0223] The third information indicates the ground IP address of the first network element;

[0224] Ground communication start timestamp information;

[0225] Ground communication end timestamp information;

[0226] The satellite's identification information;

[0227] The fourth information is the indication of the first network element on the satellite;

[0228] The fifth piece of information indicates the on-board IP address of the first network element;

[0229] Satellite communication start timestamp information;

[0230] Satellite communication end timestamp information;

[0231] The sixth information indicates information about satellites that support inter-terminal communication via satellite.

[0232] This application embodiment also provides a non-transient readable storage medium storing a program for causing a processor to execute the aforementioned billing method on the first network element side or the second network element side.

[0233] The beneficial effects of the above technical solution in this application are as follows:

[0234] In the above scheme, the billing method obtains billing information for communication between terminals via satellite when the billing trigger condition is met; sends a billing data request to the second network element, the billing data request carrying the billing information; and can support the implementation of relevant billing for UE-satellite-UE scenarios (i.e., scenarios where terminals communicate via satellite). Attached Figure Description

[0235] Figure 1 This is a schematic diagram of the wireless communication system architecture according to an embodiment of this application;

[0236] Figure 2 This is a schematic diagram of the UE-SAT-UE communication path in an embodiment of this application. Figure 1 ;

[0237] Figure 3 This is a schematic diagram of the UE-SAT-UE communication path in an embodiment of this application. Figure 2 ;

[0238] Figure 4 This is a schematic diagram of the offline billing architecture according to an embodiment of this application;

[0239] Figure 5 This is a schematic diagram of the online billing architecture according to an embodiment of this application;

[0240] Figure 6 This is a schematic diagram of the converged billing architecture according to an embodiment of this application;

[0241] Figure 7 This is a schematic diagram of the billing method in an embodiment of this application. Figure 1 ;

[0242] Figure 8 This is a schematic diagram of the billing method in an embodiment of this application. Figure 2 ;

[0243] Figure 9 This is a schematic diagram of the billing process in an embodiment of this application. Figure 1 ;

[0244] Figure 10 This is a schematic diagram of the billing process in an embodiment of this application. Figure 2 ;

[0245] Figure 11 This is a schematic diagram of the billing process in an embodiment of this application. Figure 3 ;

[0246] Figure 12 This is a schematic diagram of the billing process in an embodiment of this application. Figure 4 ;

[0247] Figure 13 This is a schematic diagram of the billing process in an embodiment of this application. Figure 5 ;

[0248] Figure 14 This is a schematic diagram of the billing process in an embodiment of this application. Figure 6 ;

[0249] Figure 15 This is a schematic diagram of the billing process in an embodiment of this application. Figure 7 ;

[0250] Figure 16 This is a schematic diagram of the billing process in an embodiment of this application. Figure 8 ;

[0251] Figure 17 This is a schematic diagram of the billing process in an embodiment of this application. Figure 9 ;

[0252] Figure 18 This is a schematic diagram of the billing device structure according to an embodiment of this application. Figure 1 ;

[0253] Figure 19 This is a schematic diagram of the billing device structure according to an embodiment of this application. Figure 2 ;

[0254] Figure 20 This is a schematic diagram of the billing device structure according to an embodiment of this application. Figure 1 ;

[0255] Figure 21 This is a schematic diagram of the billing device structure according to an embodiment of this application. Figure 2 . Detailed Implementation

[0256] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0257] In the embodiments of this application, the term "and / or" describes the relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. The character " / " generally indicates that the preceding and following associated objects have an "or" relationship.

[0258] In the embodiments of this application, the term "multiple" refers to two or more, and other quantifiers are similar.

[0259] It should be noted that the technical solutions provided in this application can be applied to a variety of systems. For example, applicable systems may include Global System for Mobile Communication (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA) General Packet Radio Service (GPRS), Long Term Evolution (LTE), LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), Long Term Evolution Advanced (LTE-A), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX), 5G New Radio (NR) and its evolutionary communication systems, and 6G (sixth generation mobile communication technology) systems. All of these systems include terminal equipment and network equipment. The system may also include a core network component, such as the Evolved Packet System (EPS) or the 5G system (5GS).

[0260] Figure 1 This diagram illustrates a block diagram of a wireless communication system to which embodiments of this application may be applied. The wireless communication system includes terminal equipment and network equipment.

[0261] The terminal devices involved in the embodiments of this application can be devices that provide voice and / or data connectivity to users, handheld devices with wireless connectivity, or other processing devices connected to a wireless modem. The names of the terminal devices may differ in different systems; for example, in 5G or 6G systems, the terminal device may be called User Equipment (UE). Wireless terminal devices can be USB storage devices, other personal computer memory devices, and dongles. They can also communicate with one or more core networks (CNs) via a Radio Access Network (RAN). Wireless terminal devices can be mobile terminal devices, such as mobile phones (or "cellular" phones) and computers with mobile terminal devices. For example, they can be portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile devices that exchange voice and / or data with the radio access network. Examples of such devices include Personal Communication Service (PCS) phones, cordless phones, Session Initiated Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), personal computers, tablets, and Machine-type Communication (MTC) terminal devices. Wireless terminal devices can also be referred to as systems, subscriber units, subscriber stations, mobile stations, mobile devices, remote stations, access points, remote terminals, access terminals, user terminals, user agents, user devices, and wireless access devices and routers / modems that meet the limitations of this definition; however, this application does not limit the scope of the embodiments.

[0262] The network device involved in this application embodiment can be a base station, which may include multiple cells providing services to terminals. Depending on the specific application, a base station may also be called an access point, or a device in the access network that communicates with wireless terminal devices through one or more sectors on the air interface, or other names. The network device can be used to exchange received air frames with Internet Protocol (IP) packets, acting as a router between the wireless terminal device and the rest of the access network, where the rest of the access network may include an Internet Protocol (IP) communication network. The network device can also coordinate the attribute management of the air interface. For example, the network equipment involved in the embodiments of this application can be a base transceiver station (BTS) in a Global System for Mobile communications (GSM) or Code Division Multiple Access (CDMA), a NodeB in a Wide-band Code Division Multiple Access (WCDMA) system, an evolved Node B (eNB or e-NodeB) in a long term evolution (LTE) system, a 5G base station (gNB) in a next generation system, a Home evolved Node B (HeNB), a relay node, a femto, a pico, network testing equipment, etc., and is not limited in the embodiments of this application. In some network structures, the network equipment may include centralized unit (CU) nodes and distributed unit (DU) nodes, and the centralized unit and distributed unit may also be geographically separated.

[0263] Network devices and terminal devices can each use one or more antennas for multiple-input multiple-output (MIMO) transmission. MIMO transmission can be single-user MIMO (SU-MIMO) or multiple-user MIMO (MU-MIMO). Depending on the configuration and number of antenna combinations, MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO, or massive-MIMO, and can also be diversity transmission, precoding transmission, or beamforming transmission, etc.

[0264] The following section will first introduce the content related to the solutions provided in the embodiments of this application.

[0265] (a) UE-SAT-UE scenario;

[0266] In satellite research, an important research direction is how to achieve "UE-Satellite-UE (UE-SAT-UE)" communication. UE-SAT-UE communication refers to the communication between UEs (multi-terminals) served by one or more satellites, where user plane traffic does not pass through the terrestrial network to avoid long delays.

[0267] Currently, a prerequisite for satellite standards is that the next-generation Node B (gNB) is on a satellite (i.e., the gNB is deployed on a satellite). In IMS networks, the media plane function IMS-AGW (IMS Access Gateway) can perform functions such as traffic monitoring and codec conversion. Based on regulatory requirements, it is also currently required that IMS-AGW be deployed on a satellite, such as... Figure 2 The diagram shows the UE-SAT-UE communication path, where the UPF (User Plane Function) and IMS-AGW are deployed on satellites. In this scheme, IMS-AGW and IMS-GWF (IMS Gateway Function) are the same network entity, only their names differ slightly in different protocols.

[0268] Furthermore, IMS-AGW can also be deployed on the ground, meaning only the base station and UPF are on the satellite, such as... Figure 3 As shown.

[0269] (II) UE-SAT-UE process;

[0270] based on Figure 2The architecture and session call process include: UE A confirms the availability of a satellite and negotiates with UE B, and then communicates through that satellite.

[0271] Furthermore, regarding the scenario of UE-SAT-UE data returning to the ground, that is: when the satellite flies away, if no other satellite can be found to take over, the UE's data will no longer be able to be transmitted via satellite. At this time, the data will return to the ground. For this scenario, the relevant session process includes: the satellite network element and the ground network element communicate and negotiate to change the communication path between UEs to ensure that UEs can continue to communicate through the ground network element.

[0272] (III) IMS Billing Architecture;

[0273] 5G IMS (IP Multimedia Subsystem) billing refers to the process of charging for multimedia communication services in a 5G network environment. This process includes billing for services such as voice, video, and messaging used by users. Below are some basic steps and components involved in 5G IMS billing:

[0274] 1. Session Establishment and Signaling: In the IMS architecture, all communication services (such as VoLTE (Voice over Long-Term Evolution), video calls, etc.) are controlled via the SIP (Session Initiation Protocol). During session establishment, relevant signaling information is used to initiate the billing process.

[0275] Specifically, in the IMS architecture, session establishment involves multiple network elements, which initiate the billing process through specific signaling. The following is an overview of the main network elements and signaling:

[0276] P-CSCF (Proxy Call Session Control Function):

[0277] • Function: The P-CSCF is the first point of contact between the user and the IMS network, and is mainly responsible for handling incoming and outgoing SIP messages.

[0278] • Signaling: During the session establishment phase, the P-CSCF generates an initial SIP INVITE request containing the necessary information for session establishment. Additionally, the P-CSCF is responsible for forwarding these SIP messages to other network elements, including accounting trigger signaling.

[0279] S-CSCF (Serving Call Session Control Function):

[0280] • Function: The S-CSCF is the central scheduling and control point, responsible for session management, routing decisions, and the execution of service policies.

[0281] • Signaling: The S-CSCF processes SIP INVITEs from the P-CSCF and determines how to continue the session based on the user's service configuration. Regarding billing, the S-CSCF initiates relevant billing signaling and may interact with billing systems (such as OCS (Online Charging System) or OFCS (Offline Charging System)) to confirm billing details.

[0282] I-CSCF (Interrogating Call Session Control Function):

[0283] • Function: The main function of the I-CSCF is to query the HSS (Home Subscriber Server) to determine the user's S-CSCF and route the request to the appropriate S-CSCF.

[0284] • Signaling: Although the I-CSCF does not directly initiate charging signaling in the charging process, it plays an important role in determining the target S-CSCF and further signaling routing.

[0285] OCS (Online Charging System) and OFCS (Offline Charging System):

[0286] • Function: OCS enables real-time billing and is suitable for prepaid users; while OFCS is responsible for generating billing records and is suitable for postpaid users.

[0287] • Signaling: Direct interaction with these systems is usually initiated by the S-CSCF, which uses signaling sent via protocols such as Diameter (Computer Protocol) or other protocols.

[0288] 2. Billing Data Generation: When a user initiates a session (such as making a VoLTE call), IMS generates a call detail record (CDR). These call detail records contain all billing-related information, such as session start and end times, data usage, and service quality.

[0289] 3. Online and offline billing:

[0290] Online Charging System (OCS): Billing occurs in real-time during service usage and is commonly used for prepaid users. OCS allows control over user service usage; for example, service can be immediately stopped when the account balance is insufficient.

[0291] Offline Charging System (OFCS): Billing is performed after service usage and is applicable to postpaid users. Detailed billing records are sent to the billing system after service usage, where costs are calculated and bills are generated.

[0292] 4. Integration of the billing system: The IMS billing system needs to be integrated with other business support systems (BSS) and operations support systems (OSS) of the operator, including account management, customer service and network operation and maintenance, to ensure the accuracy of billing information and the smoothness of the billing process.

[0293] 5. Application of Policy Control and Charging Rules: The Policy and Charging Rules Function (PCRF) plays a key role in IMS billing. It is responsible for defining and controlling how traffic is billed, including the management of factors such as quality of service and data priority.

[0294] Specifically, the offline billing architecture can be as follows: Figure 4 As shown, the following content is involved:

[0295] Billing Domain;

[0296] CDF: Charging Data Function;

[0297] CGF: Charging Gateway Function;

[0298] CCF: Charging Collection Function;

[0299] BGCF: Breakout Gateway Control Function.

[0300] MGCF: Multimedia Gateway Control Function;

[0301] MRFC: Media Resource Function Controller;

[0302] SIP AS: Session Initiation Protocol Application Server;

[0303] P-CSCF: Proxy Call Session Control Function;

[0304] I-CSCF: Interrogating Call Session Control Function;

[0305] S-CSCF: Serving Call Session Control Function.

[0306] IBCF: Interconnection Border Control Function;

[0307] E-CSCF: Emergency Call Session Control Function;

[0308] TRF: Transit and Roaming Function;

[0309] ATCF: Access Transfer Control Function;

[0310] IMS Transit Functions, also known as IMS transmission functions.

[0311] Where Bi, Ga, and Rf represent the corresponding interfaces.

[0312] In addition, online billing architecture can be as follows: Figure 5 As shown, the following content is involved:

[0313] Billing Domain;

[0314] MRFC: Media Resource Function Controller;

[0315] SIP AS: Session Initiation Protocol Application Server;

[0316] S-CSCF: Serving Call Session Control Function.

[0317] IMS-GWF: IMS Gateway Function;

[0318] OCS: Online Charging System;

[0319] In this context, Ro and ISC represent the corresponding interfaces.

[0320] Furthermore, a converged billing architecture can be as follows: Figure 6 As shown, the following content is involved:

[0321] IMS Node;

[0322] CTF: Charging Trigger Function;

[0323] CHF: Charging Function;

[0324] CGF: Charging Gateway Function;

[0325] Billing Domain;

[0326] Wherein, Nchf, Bi, and Ga represent the corresponding interfaces; the IMS node may include at least one of MRFC, IMS-GWF, and SIPAS.

[0327] Based on the above, embodiments of this application provide a billing method, apparatus, device, and non-transient readable storage medium to solve the problem that the prior art cannot support billing for UE-satellite-UE scenarios. The method, apparatus, device, and non-transient readable storage medium are based on the same application concept. Since the principles by which the method, apparatus, device, and non-transient readable storage medium solve the problem are similar, their implementations can be referred to interchangeably, and repeated details will not be repeated.

[0328] The billing method provided in this application embodiment is applied to the first network element, such as... Figure 7 As shown, it includes:

[0329] Step 71: If the billing triggering conditions are met, obtain the billing information for communication between terminals via satellite;

[0330] Step 72: Send a billing data request to the second network element, wherein the billing data request carries the billing information.

[0331] The first network element can be implemented as an IMS-GW / AS (IMS gateway or application server), and the second network element can be implemented as a billing function CHF or an online billing system OCS; or, the first network element can be implemented as a proxy call session control function P-CSCF or a service call session control function S-CSCF, and the second network element can be implemented as a billing data function CDF; but it is not limited thereto.

[0332] The billing method provided in this application embodiment obtains billing information for communication between terminals via satellite when the billing triggering conditions are met; sends a billing data request to a second network element, wherein the billing data request carries the billing information; and can support the implementation of relevant billing for UE-satellite-UE scenarios (i.e., scenarios where terminals communicate via satellite).

[0333] The billing triggering conditions include at least one of the following: receiving a session establishment request; receiving a session re-establishment request; receiving a session update request; receiving a session release request; receiving a handover indication or release indication for the first network element; or receiving a Session Initiation Protocol (SIP) response. This supports billing in various scenarios. The session can be a communication session between terminals via satellite, and / or the SIP response can be a 200 OK message, but is not limited to this.

[0334] In this embodiment, when the charging triggering condition includes receiving a session establishment request or receiving a SIP response, the charging data request is an initial charging data request; and / or, when the charging triggering condition includes receiving a session re-establishment request, receiving a session update request, receiving a handover indication for the first network element, or receiving a SIP response, the charging data request is an update charging data request; and / or, when the charging triggering condition includes receiving a session release request, receiving a release indication for the first network element, or receiving a SIP response, the charging data request is an end charging data request. This clarifies the specific charging data request in each case.

[0335] Where the billing data request is an initial billing data request, an update billing data request, or a termination billing data request, the billing information includes at least one of the following: first information, indicating support for satellite communication between terminals; an insertion instruction for the first network element; second information, indicating the first network element on the ground; third information, indicating the ground IP address of the first network element; ground communication start timestamp information; and ground communication end timestamp information. This clarifies the relevant billing information for ground communication in each case. The ground communication start timestamp information can also be expressed as any one of the following: the start timestamp information for satellite communication between terminals, the start timestamp information for the ground gateway function (GWF), etc.; and / or, the ground communication end timestamp information can also be expressed as any one of the following: the end timestamp information for satellite communication between terminals, the end timestamp information for the ground GWF, etc., without limitation. The insertion instruction for the first network element can be used to indicate the insertion of the first network element for satellite communication between terminals, but is not limited thereto.

[0336] In this embodiment of the application, when the billing data request is an initial billing data request, an update billing data request, or a termination billing data request, the billing information includes at least one of the following: first information, indicating a service supporting inter-terminal communication via satellite; an insertion indication of the first network element; the identification information of the satellite; fourth information, indicating the first network element on the satellite; fifth information, indicating the on-board IP address of the first network element; satellite communication start timestamp information; satellite communication end timestamp information; and sixth information, indicating information about the satellite supporting inter-terminal communication via satellite. This clarifies the relevant billing information for satellite communication in each case. The satellite communication start timestamp information can also be expressed as any one of the following: the start timestamp information for inter-terminal communication via satellite, the start timestamp information for the on-board gateway function (GWF), etc.; and / or, the satellite communication end timestamp information can also be expressed as any one of the following: the end timestamp information for inter-terminal communication via satellite, the end timestamp information for the on-board GWF, etc., without limitation here.

[0337] Furthermore, the billing method further includes receiving a billing data response sent by the second network element. This ensures the complete implementation of the billing scheme.

[0338] This application also provides a billing method applied to a second network element, such as... Figure 8 As shown, it includes:

[0339] Step 81: Receive a billing data request sent by the first network element when the billing triggering conditions are met. The billing data request carries billing information for communication between terminals via satellite.

[0340] Step 81: Create a billing data record based on the billing data request.

[0341] The billing method provided in this application embodiment receives a billing data request sent by a first network element when the billing trigger condition is met. The billing data request carries billing information for communication between terminals via satellite. Based on the billing data request, a billing data record is created. This method can support billing for UE-satellite-UE scenarios (i.e., scenarios where terminals communicate via satellite).

[0342] The billing triggering conditions include at least one of the following: receiving a session establishment request; receiving a session re-establishment request; receiving a session update request; receiving a session release request; receiving a handover indication or release indication for the first network element; or receiving a Session Initiation Protocol (SIP) response. This allows for billing in various scenarios.

[0343] In this embodiment, when the charging triggering condition includes receiving a session establishment request or receiving a SIP response, the charging data request is an initial charging data request; and / or, when the charging triggering condition includes receiving a session re-establishment request, receiving a session update request, receiving a handover indication for the first network element, or receiving a SIP response, the charging data request is an update charging data request; and / or, when the charging triggering condition includes receiving a session release request, receiving a release indication for the first network element, or receiving a SIP response, the charging data request is an end charging data request. This clarifies the specific charging data request in each case.

[0344] Wherein, when the billing data request is an initial billing data request, an update billing data request, or an end billing data request, the billing information includes at least one of the following: first information, the first information indicating a service that supports communication between terminals via satellite; an insertion indication of the first network element; second information, the second information being an indication of the first network element on the ground; third information, the third information indicating the ground IP address of the first network element; ground communication start timestamp information; and ground communication end timestamp information.

[0345] This clarifies the relevant billing information for terrestrial communications under various circumstances.

[0346] In this embodiment of the application, when the billing data request is an initial billing data request, an update billing data request, or a termination billing data request, the billing information includes at least one of the following: first information, indicating a service supporting inter-terminal communication via satellite; an insertion indication of the first network element; identification information of the satellite; fourth information, indicating the first network element on the satellite; fifth information, indicating the on-board IP address of the first network element; satellite communication start timestamp information; satellite communication end timestamp information; and sixth information, indicating information about the satellite supporting inter-terminal communication via satellite. This clarifies the relevant billing information for satellite communication in each case.

[0347] Furthermore, the billing method further includes sending a billing data response to the first network element. This ensures the complete implementation of the billing scheme.

[0348] It should be noted that the relevant content of the first network element and the second network element mentioned above can be referred to each other, and the repeated parts will not be repeated.

[0349] The following provides an example illustrating the billing method provided in the embodiments of this application.

[0350] To address the aforementioned technical issues, this application provides a billing method, specifically a billing scheme that supports IMS-UE-satellite-UE communication. Examples of how this scheme is implemented in various scenarios are provided below.

[0351] I. Integrated Billing;

[0352] Based on the current converged billing architecture, the three network elements MRFC (Media Resource Function Controller), IMS-GWF (connected to S-CSCF using ISC), and SIPAS can serve as CTFs.

[0353] Among them, IMS-GWF can support converged billing, so it can be used as the triggering network element for converged billing; MRFC and SIPAS (i.e. IMS-AS) can support offline only charging via Nchf interface, so SIP AS can be used as the triggering network element for offline billing in this scheme.

[0354] In this scheme, except for IMS-GWF which is only applicable to "converged billing", other IMS nodes can be configured as "converged billing" or "offline only billing". When configured as "offline only billing", Nchf (interface) converged billing service is the default service used by IMS nodes, unless the offline only Nchf service must be used based on operator policies.

[0355] The following provides a specific example of how to implement this scenario.

[0356] Example 1: Session establishment and update;

[0357] Specifically, such as Figure 9 As shown, the operations include the following:

[0358] 1) UE A (Terminal A) sends a session request INVITE (which may correspond to a session establishment request), which carries information indicating access to the network via NR (New Radio) satellite. If the UE is not roaming and the P-CSCF supports UE-satellite-UE communication, then P-CSCF A (i.e., the P-CSCF on Terminal A's side) updates the SIP INVITE, and this request (including the satellite ID) is forwarded to the IMS-GWF / AS (i.e., the IMS network management or application server).

[0359] 2) After the IMS-GWF / AS A on the ground (i.e., the IMS-GWF / AS on the terminal A side; or IMS-AGW / AS) performs service control, it sends a Charging Data Request [Initial] to the CHF to record the start of a user session and the opening of a media component in the CHFCDR (Charging Data Recording). The request includes at least one of the following: UE-SAT-UE information (corresponding to the first information above, which indicates that the service supports inter-terminal communication via satellite), AGW inserted indication (which may correspond to the insertion indication of the first network element above), indication that the AGW that can serve the UE is on the ground (i.e., indicating that the AGW is on the ground, AGWon the ground indication; corresponding to the second information above), AGW IP address (corresponding to the third information above, which indicates the ground IP address of the first network element), ground communication start timestamp information, and ground communication end timestamp information. The CHF CDR (which may correspond to the aforementioned billing information) may include at least one of the following: UE-SAT-UEinformation (corresponding to the aforementioned first information, which indicates support for satellite-based communication between terminals), AGW inserted indication (which may correspond to the aforementioned insertion indication of the first network element), AGW on the ground for UE-satellite-UE communication (which may correspond to the aforementioned second information), AGW IP address (which may correspond to the aforementioned third information), ground communication start timestamp information, and ground communication end timestamp information. This operation may correspond to obtaining billing information for satellite-based communication between terminals when the billing triggering conditions are met; sending a billing data request to the second network element, wherein the billing data request carries the billing information; and the billing data request being an initial billing data request.

[0360] 3) CHF initiates CDR for the PDU (Protocol Data Unit) session and sends a Charging Data Response [Initial] to IMS-AGW. This operation corresponds to receiving the charging data request sent by the first network element when the charging trigger conditions are met, wherein the charging data request carries charging information for communication between terminals via satellite; a charging data record is created according to the charging data request; and a charging data response is sent to the first network element, wherein the charging data response may be an initial charging data response.

[0361] The following content can be added to the CHF CDR:

[0362]

[0363]

[0364] 4) The ground-based IMS-GWF / AS and P-CSCF forward the aforementioned SIP INVITE to other P-CSCF Bs (such as the P-CSCF on the UE B side); specifically, for example, the INVITE is sent to the IMS-AS on the UE B side, and then transmitted to the P-PCSCF on the UE B side. Afterwards, more SIP signaling and optional more charging data requests can be exchanged, enabling UE A and UE B to negotiate the handover of the ground-based IMS-AGW to the satellite-based IMS-AGW. It should be noted that the P-CSCFs in the diagram do not distinguish between P-CSCF A and P-CSCF B; they can encompass multiple P-CSCFs.

[0365] 5) After P-CSCF B and P-CSCF A interact, they can determine that UE-SAT-UE communication will be used. P-CSCF A selects the IMS-GWF located on the satellite (which can be IMS-GWF / AS in the diagram). The IMS-GWF / AS on the satellite receives a response (which may include P-CSCF A receiving a 200 OK message indicating successful handover and forwarding it). This is to clarify... Figure 9 The text does not distinguish between P-CSCF B and P-CSCF A, which can be included in P-CSCF; it does not distinguish between IMS-GWF / AS located on the ground or on satellite, nor does it distinguish between CHF located on the ground or on satellite.

[0366] 6) After IMS-GWF / AS performs service control, if the trigger is active, the SIP200OK response sent by UE A triggers a billing data request [update] to update the PDU session (which can be understood as triggering billing after switching to the on-board IMS-GWF and confirming the use of the on-board network element); wherein, the request [update] may include at least one of the following: UE-SAT-UE information (which may correspond to the first information mentioned above), AGW inserted indication (AGW insertion indication, which may correspond to the insertion indication of the first network element mentioned above), the satellite ID serving the UE (which may correspond to the identification information of the satellite mentioned above), the indication that the AGW is located on the satellite (i.e., indicating that the AGW is located on the satellite, AGW on the satellite indication; which may correspond to the fourth information mentioned above), the AGW IP address in IMS-GWF / AS (which may correspond to the fifth information mentioned above), satellite communication start timestamp information, satellite communication end timestamp information, and satellite information (which may correspond to the sixth information mentioned above). This operation corresponds to obtaining billing information for satellite communication between terminals when the billing triggering conditions are met; sending a billing data request to the second network element, wherein the billing data request carries the billing information; the billing triggering conditions include receiving a Session Initiation Protocol (SIP) response; and the billing data request is an update billing data request.

[0367] 7) CHF initiates CDR and sends a Charging Data Response [Update] to IMS-AGW / AS to confirm the Charging Data Request. This operation corresponds to receiving the charging data request sent by the first network element when the charging trigger conditions are met, wherein the charging data request carries charging information for communication between terminals via satellite; a charging data record is created according to the charging data request; and a charging data response is sent to the first network element, wherein the charging data response may be an updated charging data response.

[0368] The following content can be added to the CHF CDR:

[0369]

[0370]

[0371] 8) IMS-AGW / AS sends an acknowledgment response 200 OK to P-CSCF, and P-CSCF forwards it to the corresponding UE, such as P-CSCF A forwarding it to UE A.

[0372] 9) If UE A decides to end the call, UE A sends a session release request; that is, it performs the release of the IMS AGW on satellite.

[0373] 10) Upon receiving a session release request, the IMS-AGW sends a Charging Data Request [Termination] to terminate the UE-SAT-UE session. This operation corresponds to obtaining charging information for inter-terminal communication via satellite when the charging trigger condition is met. The charging data request carries the charging information and is sent to the second network element. The charging trigger condition includes receiving the session release request. The charging data request is a termination charging request. The charging data request includes at least one of the following: UE-SAT-UE information, AGW inserted indication (corresponding to the insertion indication of the first network element), AGW on the ground indication, AGW IP address (corresponding to the third and / or fifth information), ground communication start timestamp information, ground communication end timestamp information, AGW on the satellite indication, satellite communication start timestamp information, satellite communication end timestamp information, and satellite information (corresponding to the sixth information).

[0374] 11) The CHF confirms receipt of data and closes the P-CSCF CDR, sending a Charging Data Response [Termination] to the IMS-AGW. This operation corresponds to receiving a charging data request sent by the first network element when the charging trigger condition is met, wherein the charging data request carries charging information for communication between terminals via satellite; a charging data record is created according to the charging data request; and a charging data response is sent to the first network element. The CDR contains at least one of the following: UE-SAT-UE information, AGW inserted indication (which may correspond to the insertion indication of the first network element), AGW on the ground indication, AGWIP address (which may correspond to the third and / or fifth information mentioned above), ground communication start timestamp information, ground communication end timestamp information, AGW on the satellite indication, satellite communication start timestamp information, satellite communication end timestamp information, and satellite information (which may correspond to the sixth information mentioned above).

[0375] It should be noted that the relevant billing responses involved in this scheme may carry relevant billing data records such as CHF CDR, but are not limited to this.

[0376] Example 2: If, due to satellite movement, or if no satellite can serve two UEs (ISL (Inter-Satellite Link) can also not serve two UEs), the IMS-AGW may change, resulting in an IMS-AGW IP address switch. For example, it may switch to an IMS-AGW on another satellite, or traffic may be routed back to the ground, selecting a ground-based IMS-AGW. The billing process for this can be as follows: Figure 10 As shown, the operations include the following:

[0377] 1) In an ongoing SIP session, UE A sends an INVITE to P-CSCF A; P-CSCF A interacts with the 5G core network (5GC) to determine to use the IMS-GW on the ground and the Qos (Quality of Service) packet filter list update, and sends a Re-INVITE to the IMS-AGW / AS on the UE A side.

[0378] Specifically, if the early notification does not include the target satellite ID, or if the two satellites identified by the satellite IDs received by P-CSCF A for the initiating network and the satellite IDs stored for the terminating network do not have ISLs, then P-CSCF determines that the optimized media route cannot continue. P-CSCF decides to activate the terrestrial fallback route, sending a SIP message (i.e., a Re-INVITE in the diagram) to the IMS AS, requesting it to send a SIP Re-INVITE to the terminating network (corresponding to the IMS-GW / AS (gateway or application server) on the UE B side in the diagram). This SIP message may contain an IP address allocated in the terrestrial IMS AGW, which the terminating network can use as the destination for media traffic. This SIP message does not contain any satellite IDs.

[0379] 2) After receiving a Re-INVITE, if the trigger is active, the IMS-AGW / AS on the UE A side sends a Charging Data Request [Update] to the CHF on the UE A side. This request may include at least one of the following: UE-SAT-UEinformation (corresponding to the first information mentioned above, which indicates support for satellite communication between terminals), AGW inserted indication (corresponding to the insertion indication of the first network element mentioned above), AGW on the ground indication (corresponding to the second information mentioned above), AGW IP address (corresponding to the third information mentioned above), ground communication start timestamp information, and ground communication end timestamp information, so that the CHF can update the session. This operation is equivalent to obtaining billing information for satellite communication between terminals when the billing trigger condition is met; sending a billing data request to the second network element, wherein the billing data request carries the billing information; the billing trigger condition includes receiving a session update request; the billing data request is an update billing data request.

[0380] 3) CHF initiates CDR and sends Charging DataResponse[Update] to the corresponding (i.e., UE A side) IMS-AGW / AS. This operation corresponds to receiving the charging data request sent by the first network element when the charging trigger condition is met, as described above. The charging data request carries charging information for communication between terminals via satellite. Based on the charging data request, a charging data record is created; and a charging data response is sent to the first network element. The information contained in the CDR in this operation can be found in the CDR-related content under operation 14) of this embodiment, and will not be repeated here.

[0381] 4) Upon receiving a SIP Re-INVITE request, the IMS AS (on the UE A side) sends a SIP Re-INVITE to the terminating network. This SIP Re-INVITE may contain an SDP (Session Description Protocol) proposal with an IP address allocated in the IMS AGW, which the terminating network uses as the destination for media traffic. After system interaction with UE B (corresponding to More SIP signaling in the diagram), the terrestrial IMS-GW is determined, and the insertion of the terrestrial ULCL (Uplink Classifier) ​​is completed. Specifically, this may include the terrestrial IMS-GWF network element on the UE A side receiving information from P-CSCF A and sending information (which may carry terrestrial GWF information or GWF handover indication) to the IMS-GWF of UE B for negotiation handover. Once negotiation is complete, GWF handover can begin.

[0382] 5) UE B sends SIP 200OK to P-CSCF B; P-CSCF B forwards the SIP 200OK to the corresponding IMS-AGW / AS, and the SIP 200OK carries an SDP response (which can indicate that the IMS-AGW is located on the ground and can carry the handover indication of the IMS-AGW).

[0383] 6) The IMS-GWF / AS sends a Charging Data Request [Update] to the CHF on the UE B side. This request may include at least one of the following: UE-SAT-UE information (corresponding to the first information mentioned above, which indicates support for satellite communication between terminals), AGW inserted indication (which may correspond to the insertion indication of the first network element mentioned above), IMS-AGW on the ground indication (which may correspond to the second information mentioned above), AGW IP address (which may correspond to the third information mentioned above), ground communication start timestamp information, and ground communication end timestamp information, in order to update the previously initiated session. This operation is equivalent to obtaining the billing information for satellite communication between terminals when the billing trigger conditions are met; sending a billing data request to the second network element, the billing data request carrying the billing information; the billing trigger conditions include receiving a handover indication for the first network element or receiving a Session Initiation Protocol (SIP) response; the billing data request is an update billing data request.

[0384] 7) CHF initiates CDR and sends Charging Data Response [Update] to IMS-AGW. This operation corresponds to receiving the charging data request sent by the first network element when the charging trigger conditions are met, wherein the charging data request carries charging information for communication between terminals via satellite; a charging data record is created according to the charging data request; and a charging data response is sent to the first network element.

[0385] The following content can be added to the CDR:

[0386]

[0387] 8) The IMS-AGW on UE B sends a SIP 200 OK message to the IMS-AGW on UE A. Afterwards, the relevant entities perform further SIP signaling interactions.

[0388] 9) After the IMS-AGW on the UE A side performs service control, if the trigger is active, the IMS-GWF / AS sends a Charging Data Request [Update] to the CHF on the UE A side. This request may include at least one of the following: UE-SAT-UE information (corresponding to the first information mentioned above, which indicates support for satellite communication between terminals), AGW Insertion Indication (AGW Insertion Indication, which may correspond to the insertion indication of the first network element mentioned above), AGW On the Ground Indication (AGW on the ground indication; which may correspond to the second information mentioned above), AGW IP address (which may correspond to the third information mentioned above), ground communication start timestamp information, and ground communication end timestamp information, so that the CHF can update the session. This operation is equivalent to obtaining the billing information for satellite communication between terminals when the billing trigger condition is met; sending a billing data request to the second network element, wherein the billing data request carries the billing information; the billing trigger condition includes receiving a Session Initiation Protocol (SIP) response; the billing data request is an update billing data request.

[0389] 10) CHF initiates CDR and sends a Charging Data Response [Update] to the corresponding (i.e., UE A side) IMS-AGW. This operation corresponds to receiving the charging data request sent by the first network element when the charging trigger condition is met, as described above. The charging data request carries charging information for inter-terminal communication via satellite. Based on the charging data request, a charging data record is created; and a charging data response is sent to the first network element. The information contained in the CDR in this operation can be found in the CDR-related content under operation 14) of this embodiment, and will not be repeated here.

[0390] 11) The IMS-AGW on the UE A side sends a SIP 200 OK message to UE A.

[0391] 12) Both the MO (Move Initiation) and MT (Move Termination) sides release the IMS-AGW on the satellite; this may include: the IMS-AGW receiving a release instruction.

[0392] 13) If the trigger is active, the IMS-GWF / AS on UE A side sends a ChargingData Request[Termination] to the CHF on UE A side; correspondingly, the IMS-GWF / AS on UE B side sends a ChargingData Request[Termination] to the CHF on UE B side; the request includes at least one of the following: UE-SAT-UE information (which may correspond to the first information mentioned above), AGW inserted indication (which may correspond to the insertion indication of the first network element mentioned above), the satellite ID serving the UE (which may correspond to the identification information of the satellite mentioned above), the indication that the corresponding AGW is located on the satellite (which may correspond to the fourth information mentioned above), the AGW IP address (which may correspond to the fifth information mentioned above), satellite communication start timestamp information, satellite communication end timestamp information, and satellite information (which may correspond to the sixth information mentioned above), so as to update the session for the corresponding CHF. This operation corresponds to the above-mentioned acquisition of billing information for satellite communication between terminals when the billing trigger condition is met; sending a billing data request to the second network element, wherein the billing data request carries the billing information; the billing trigger condition includes receiving a release instruction for the first network element; the billing data request is to end the billing data request.

[0393] 14) CHF initiates CDR and sends a Charging Data Response [Termination] to the corresponding IMS-AGW. This operation corresponds to receiving the charging data request sent by the first network element when the charging trigger condition is met, wherein the charging data request carries charging information for communication between terminals via satellite; a charging data record is created according to the charging data request; and a charging data response is sent to the first network element.

[0394] The following content can be added to the CDR:

[0395]

[0396] II. Offline billing;

[0397] Based on the IMSoffline charging architecture and current standardization progress, since the P-CSCF can obtain the satellite ID of the serving UE from the PCF (Policy Control Function), the P-CSCF can be used as the charging triggering network element in this scheme. The following is a specific example of the implementation of this scheme (the case of AS triggering is not considered for the time being).

[0398] Example 1: The session establishment MO process can be as follows Figure 11 (The session establishment message sequence diagram (mobile initiation) is shown, including the following operations:)

[0399] 1. Session initiated; UE A sends a session request INVITE, which indicates that it carries information about accessing the network via NR satellite. If the UE is not roaming and the P-CSCF supports UE-satellite-UE communication, the current UE-SAT-UE procedure can proceed.

[0400] 2. The P-CSCF receives the destination's response and final response (i.e., 200 OK (invite) in the diagram) and performs service control.

[0401] Based on the final response received above, the P-CSCF sends a Charging Data Request [Start] to the CDF to record the start of a user session and the activation of a media component. The request includes at least one of the following: UE-SAT-UE information (which may correspond to the first information mentioned above), AGW inserted indication (which may correspond to the insertion indication of the first network element mentioned above), satellite ID that can serve the UE (which may correspond to the satellite identification information mentioned above), indication that the AGW is located on a satellite (which may correspond to the fourth information mentioned above), AGW IP address (which may correspond to the fifth information mentioned above), satellite communication start timestamp information, satellite communication end timestamp information, and satellite information (which may correspond to the sixth information mentioned above). The P-CSCF CDR may include at least one of the following for UE-satellite-UE communication: UE-SAT-UE information (corresponding to the first information mentioned above), AGW inserted indication (corresponding to the insertion indication of the first network element mentioned above), satellite ID (corresponding to the identification information of the satellite mentioned above), AGW indication on the satellite (corresponding to the fourth information mentioned above), AGW IP address (corresponding to the fifth information mentioned above), satellite communication start timestamp information, satellite communication end timestamp information, and satellite information (corresponding to the sixth information mentioned above). This operation may correspond to obtaining billing information for inter-terminal communication via satellite when the billing trigger condition is met; sending a billing data request to the second network element, wherein the billing data request carries the billing information; the billing trigger condition includes receiving a Session Initiation Protocol (SIP) response; and the billing data request is an initial billing data request.

[0402] 3. The CDF confirms receipt of data and initiates P-CSCF CDR, sending a Charging Data Response to the P-CSCF (which may correspond to the charging data request sent by the first network element when the charging trigger conditions are met, the charging data request carrying charging information for satellite communication between terminals; creating a charging data record based on the charging data request; and sending a charging data response to the first network element). Subsequent related execution entities perform more SIP signaling interactions until a SIP session is established.

[0403] The P-CSCF CDR can include the following:

[0404]

[0405] Here's a clarification regarding billing for the MT (Meeting Establishment) process: the process is similar to MO (Meeting on Order) except that the sender and receiver of operations 1 and 2 are reversed. Figure 11 The arrows for operations 1 and 2 in the code are in opposite directions; its enhancements (i.e., the changes involved in the scheme) are also similar to those in the MO, including: adding at least one of the following to the charging data request: UE-SAT-UE information (which may correspond to the first information mentioned above), AGW inserted indication (which may correspond to the insertion indication of the first network element mentioned above), satellite ID, AGW indication on the satellite, AGW IP address, satellite communication start timestamp information, satellite communication end timestamp information, and satellite information (which may correspond to the sixth information mentioned above); and adding at least one of the following to the CDR: UE-SAT-UE information (which may correspond to the first information mentioned above), AGW inserted indication (which may correspond to the insertion indication of the first network element mentioned above), satellite ID, AGW indication on the satellite, AGW IP address, satellite communication start timestamp information, satellite communication end timestamp information, and satellite information (which may correspond to the sixth information mentioned above); but not limited to these.

[0406] Example 2: If, due to satellite movement, or if no satellite can serve two UEs (IMS also cannot serve two UEs), the IMS-AGW may change, resulting in an IMS-AGW IP address switch. For example, it may switch to an IMS-AGW on a different satellite, or traffic may be routed back to the ground, selecting a terrestrial IMS-AGW. The billing process for this can be as follows: Figure 12 (The media modification message sequence diagram shows the following operations:)

[0407] 1. In an ongoing SIP session, if satellite movement or the absence of satellites to serve two UEs (and the inability of IMS to serve two UEs), UE A will generate a SIP RE-INVITE or SIP UPDATE in the middle of the session and send it to the corresponding P-CSCF, which will then forward it. Further SIP signaling interactions will then occur.

[0408] 2. After receiving the corresponding response (i.e., 200 OK (invite / update)) and performing service control, the P-CSCF sends a 200 OK (carrying an SDP offer) to UE A. Specifically, the destination replies with a response including the SDP offer. If the final response (i.e., 200 OK (carrying an SDP offer)) only includes the SDP offer, the PSCF should wait for a SIP ACK (acknowledgment).

[0409] 3. UE A sends a SIP ACK (response) to P-CSCF, which carries an SDP offer.

[0410] 4. When modifying the media, the P-CSCF sends a billing data request [temporarily] to the CDF so that the modified media component is recorded in the P-CSCF CDR; the request may include at least one of the following: UE-SAT-UE information (which may correspond to the first information mentioned above), AGW insertion indication (which may correspond to the insertion indication of the first network element mentioned above), the satellite ID serving the UE (which may correspond to the identification information of the satellite mentioned above), the indication that the AGW is located on the satellite (which may correspond to the fourth information mentioned above), the IMS AGW IP address (which may correspond to the fifth information mentioned above), satellite communication start timestamp information, satellite communication end timestamp information, and satellite information (which may correspond to the sixth information mentioned above). The P-CSCF CDR may include at least one of the following: UE-SAT-UE information (which may correspond to the first information mentioned above), AGW inserted indication (which may correspond to the insertion indication of the first network element mentioned above), satellite ID serving the UE (which may correspond to the identification information of the satellite mentioned above), IMS AGW insertion indication, IMS AGW IP address (which may correspond to the fifth information mentioned above), satellite communication start timestamp information, satellite communication end timestamp information, and satellite information (which may correspond to the sixth information mentioned above). This operation may correspond to obtaining billing information for inter-terminal communication via satellite when the billing trigger condition is met; sending a billing data request to the second network element, wherein the billing data request carries the billing information; the billing trigger condition includes receiving a Session Initiation Protocol (SIP) response; and the billing data request is an update billing data request.

[0411] 5. The CDF confirms the received data and updates the P-CSCF CDR; the CDF sends a Charging Data Response to the P-CSCF (which may correspond to the charging data request sent by the first network element when the charging trigger conditions are met, the charging data request carrying charging information for communication between terminals via satellite; based on the charging data request, a charging data record is created; and a charging data response is sent to the first network element). The subsequent SIP session continues.

[0412] The following content can be added to the P-CSCF CDR:

[0413]

[0414]

[0415] Example 3: The MO session release process can be as follows Figure 13 (The session release message sequence diagram (SIP BYE (end) triggers a billing data request)) shows the following operations:

[0416] 1. The session has been released, which may include: UE A sending a BYE message to P-CSCF, and P-CSCF forwarding it accordingly.

[0417] 2. Upon session termination, the P-CSCF sends a Charging Data Request [Stop] to the CDF to record the termination of a session and the cessation of a media component in the P-CSCF CDR. This request may include at least one of the following: UE-SAT-UE information (corresponding to the first information mentioned above), AGW inserted indication (corresponding to the insertion indication of the first network element mentioned above), satellite ID (corresponding to the satellite identification information mentioned above), AGW location on satellite indication (corresponding to the fourth information mentioned above), IMS AGW IP address (corresponding to the fifth information mentioned above), satellite communication start timestamp information, satellite communication end timestamp information, and satellite information (corresponding to the sixth information mentioned above). The P-CSCF CDR may include: UE-SAT-UE information (corresponding to the first information mentioned above), AGW inserted indication (corresponding to the insertion indication of the first network element mentioned above), satellite ID used for UE-satellite-UE communication (i.e., the satellite ID serving the UE), AGW location on satellite indication (corresponding to the fourth information mentioned above), and IMS AGW. At least one of the following: IP address (which may correspond to the fifth piece of information above), satellite communication start timestamp information, satellite communication end timestamp information, and satellite information (which may correspond to the sixth piece of information above). This operation may correspond to obtaining billing information for satellite communication between terminals when the billing trigger condition is met; sending a billing data request to the second network element, wherein the billing data request carries the billing information; the billing trigger condition includes receiving a session release request; and the billing data request is an end-of-billing data request.

[0418] 3. The CDF confirms receipt of data and closes the P-CSCF CDR. The P-CSCF CDR may contain at least one of the following for UE-satellite-UE communication: UE-SAT-UE information (corresponding to the first information mentioned above), AGW inserted indication (corresponding to the insertion indication of the first network element mentioned above), satellite ID, AGW location on satellite indication (corresponding to the fourth information mentioned above), IMS AGW IP address (corresponding to the fifth information mentioned above), satellite communication start timestamp information, satellite communication end timestamp information, and satellite information (corresponding to the sixth information mentioned above). The CDF sends a Charging Data Response to the P-CSCF. This may correspond to receiving a charging data request sent by the first network element when the charging trigger condition is met. The charging data request carries charging information for communication between terminals via satellite. Based on the charging data request, a charging data record is created. A charging data response is sent to the first network element. Afterward, the P-CSCF may receive a 200 OK message indicating successful session release and forward it to UE A.

[0419] The following content can be added to the P-CSCF CDR:

[0420]

[0421]

[0422] Example 4: The MT session release process can be as follows Figure 14 (The session release message sequence diagram (SIP 200 OK triggers billing data request) is shown, including the following operations:)

[0423] 1. The session has been released, which may include: the P-CSCF receiving the BYE message and forwarding the BYE message to the corresponding UEA, and the P-CSCF performing service control.

[0424] 2. Session release is confirmed by UE A. Specifically, UE A sends a 200 OK message (i.e., SIP 200 OK) to P-CSCF for session release confirmation, and P-CSCF forwards it.

[0425] 3. Upon confirming the termination of the SIP session and the termination of the Rx session (if necessary), the P-CSCF sends a ChargingData Request [Stop] to the CDF so that the P-CSCF CDR records information about the termination of a session and the termination and acknowledgment messages of a media component; the request may include at least one of the following: UE-SAT-UE information (which may correspond to the first information mentioned above), AGW inserted indication (which may correspond to the insertion indication of the first network element mentioned above), satellite ID (which may correspond to the identification information of the satellite mentioned above), indication that the AGW is located on the satellite (which may correspond to the fourth information mentioned above), IMSAGW IP address (which may correspond to the fifth information mentioned above), satellite communication start timestamp information, satellite communication end timestamp information, and satellite information (which may correspond to the sixth information mentioned above); the P-CSCF CDR may include the following for UE-SAT-UE communication: UE-SAT-UE information (which may correspond to the first information mentioned above), AGW... At least one of the following: insertedindication (AGW insertion indication, which may correspond to the insertion indication of the first network element mentioned above), satellite ID (including the satellite ID serving the UE, and / or the satellite ID supporting inter-terminal communication via satellite), AGW location on satellite indication, IMS AGW IP address, satellite communication start timestamp information, satellite communication end timestamp information, and satellite information (which may correspond to the sixth information mentioned above). The reported billing information must rely on the time of receiving the SIP BYE message, not the time of receiving the corresponding acknowledgment (which can also be understood as billing based on the SIP BYE information released during the session). This operation may correspond to obtaining billing information for inter-terminal communication via satellite when the billing trigger condition is met; sending a billing data request to the second network element, the billing data request carrying the billing information; the billing trigger condition includes receiving a Session Initiation Protocol (SIP) response (corresponding to the SIP 200 OK mentioned above), and the billing data request being an end-of-billing data request. The "satellite ID serving the UE" and the "satellite ID supporting inter-terminal communication via satellite" may represent the same or different information, which is not limited here.

[0426] 4. The CDF confirms receipt of data and closes the P-CSCF CDR, sending a Charging Data Response to the P-CSCF. This may correspond to receiving a charging data request sent by the first network element when the charging triggering conditions are met, wherein the charging data request carries charging information for communication between terminals via satellite. Based on the charging data request, a charging data record is created; and a charging data response is sent to the first network element. The P-CSCF CDR may include at least one of the following for UE-SAT-UE communication: UE-SAT-UE information (corresponding to the first information mentioned above), AGW insertion indication (corresponding to the insertion indication of the first network element mentioned above), satellite ID, AGW location on satellite indication, IMS AGW IP address, satellite communication start timestamp information, satellite communication end timestamp information, and satellite information (corresponding to the sixth information mentioned above).

[0427] The following content can be added to the P-CSCF CDR:

[0428]

[0429]

[0430] III. Online Billing;

[0431] Based on the architecture of IMSonline billing and the current standardization progress, since only IMS-GWF or AS can trigger billing, and IMS-AGW / AS (i.e., IMS-AGW or IMS-AS) can obtain satellite ID, this solution can use IMS-AGW / AS as the billing triggering network element; since IMS-AGW is deployed on each satellite, billing information can be uniformly sent back to the ground OCS (Online Charging System);

[0432] Online billing includes the following three methods:

[0433] -Immediate Event Charging (IEC); and,

[0434] -Event charging with unit reservation (ECUR, charged per unit reservation event), and,

[0435] -Session Charging with Unit Reservation (SCUR, charged per unit reserved session).

[0436] Therefore, the billing process will be illustrated with examples below.

[0437] Example 1: Immediate Event Charging (IEC), as follows Figure 15 The message sequence diagram (for session-independent processes) shows the following operations:

[0438] 1. The P-CSCF receives session-independent SIP requests (e.g., subscription requests; which may correspond to session establishment requests in billing trigger conditions). The P-CSCF forwards this request to the IMS-GWF / AS.

[0439] 2. After performing service control, the IMS-GWF / AS sends a Debit Units Request [Event] to the OCS to request the unit to provide services. This request includes at least one of the following: UE-SAT-UE information (corresponding to the first information mentioned above), AGW inserted indication (corresponding to the insertion indication of the first network element mentioned above), satellite ID that can serve the UE (corresponding to the satellite identification information mentioned above), AGW indication on the satellite, AGW IP address (corresponding to the fifth information mentioned above), satellite communication start timestamp information, satellite communication end timestamp information, and satellite information (corresponding to the sixth information mentioned above). The OCS performs credit control. This operation corresponds to obtaining billing information for inter-terminal communication via satellite when the billing trigger condition is met; sending a billing data request to the second network element, the billing data request carrying the billing information; the billing trigger condition includes receiving a session establishment request, and the billing data request is an initial billing request.

[0440] 3. The OCS sends a Debit Units Response ([event]) to the IMS-GWF / AS to confirm the Debit Units Request, authorizing the requesting unit. This operation corresponds to receiving the billing data request sent by the first network element when the billing trigger conditions are met, wherein the billing data request carries billing information for inter-terminal communication via satellite; based on the billing data request, a billing data record is created; and a billing data response is sent to the first network element.

[0441] 4. After receiving the Debit Units Response, the IMS-GWF / AS sends a SIP request (SIPrequest) to the P-CSCF.

[0442] 5. P-CSCF forwards received SIP requests.

[0443] Example 2: Session Charging with Unit Reservation (SCUR) is similar to ECR, and can be described in detail as follows: Figure 16 (The P-CSCF in the process can also be S-CSCF, without limitation) As shown, the following operations are involved:

[0444] 1) UE A sends a session request INVITE, which carries information indicating access to the network via NR satellite. If the UE is not roaming and the P-CSCF supports UE-satellite-UE communication, then P-CSCF A (i.e., the P-CSCF on the terminal A side) updates SIPIVITE (which may correspond to the session establishment request in the charging trigger condition), and this request (including the satellite ID) is forwarded to IMS-GWF / AS (i.e., the IMS network management or application server).

[0445] 2) After performing service control, the IMS-GWF / AS A on the ground (i.e., the IMS-GWF / AS on the terminal A side) sends a Reserve Units Request [Initial] to the OCS to request service units. This request includes at least one of the following: UE-SAT-UE information (which may correspond to the first information mentioned above), AGW inserted indication (which may correspond to the insertion indication of the first network element mentioned above), satellite ID that can serve the UE (which may correspond to the identification information of the satellite mentioned above), AGW indication on the satellite, AGW IP address (which may correspond to the fifth information mentioned above), satellite communication start timestamp information, satellite communication end timestamp information, and satellite information (which may correspond to the sixth information mentioned above). This operation may correspond to obtaining the billing information for communication between terminals via satellite when the billing trigger condition is met; sending a billing data request to the second network element, wherein the billing data request carries the billing information; the billing trigger condition includes receiving a session establishment request; the billing data request is an initial billing data request. The online credit control session has been initiated.

[0446] 3) In the Reserve Units Response, the OCS authorizes the unit and sends a Reserve Units Response to the IMS-GWF / AS A; this can correspond to receiving the billing data request sent by the first network element when the billing trigger conditions are met, wherein the billing data request carries billing information for communication between terminals via satellite; based on the billing data request, a billing data record is created; and a billing data response is sent to the first network element.

[0447] 4) The ground-based IMS-GWF / AS and P-CSCF forward the aforementioned SIP INVITE to other P-CSCF Bs (such as the P-CSCF on the UE B side). Afterwards, more SIP signaling and optional more Reserve Units Requests can be exchanged, enabling UE A and UE B to negotiate the handover of the ground-based IMS-AGW to the satellite-based IMS-AGW. Note that the P-CSCFs in the diagram do not distinguish between P-CSCF A and P-CSCF B; they can encompass multiple P-CSCFs.

[0448] 5) After P-CSCF B and P-CSCF A interact, it can be determined that UE-SAT-UE communication will be used. P-CSCF A selects the IMS-GWF located on the satellite, and the IMS-GWF / AS on the satellite receives a response (which may include P-CSCF A receiving a 200 OK message indicating successful handover and forwarding it).

[0449] 6) After IMS-GWF / AS performs service control, if the trigger is active, the SIP 200OK response triggers a reserved unit request [update] to update the Credit-Control session in IMS-GWF / AS (which may correspond to obtaining billing information for inter-terminal communication via satellite when the billing trigger condition is met; sending a billing data request to the second network element, the billing data request carrying the billing information; the billing trigger condition includes receiving a Session Initiation Protocol (SIP) response; the billing data request is an update billing data request); wherein, the request [update] may include at least one of the following: UE-SAT-UE information (which may correspond to the first information mentioned above), AGW inserted indication (which may correspond to the insertion indication of the first network element mentioned above), the satellite ID serving the UE (which may correspond to the satellite identification information mentioned above), the indication of the AGW on the satellite, the AGW IP address in IMS-GWF / AS (which may correspond to the fifth information mentioned above), satellite communication start timestamp information, satellite communication end timestamp information, and satellite information (which may correspond to the sixth information mentioned above). New service units are requested, and existing service units (if any) are also reported.

[0450] 7) The OCS performs Credit Control and sends a Reserve Units Response to the IMS-GWF / AS to confirm the Reserve Units Request; this corresponds to receiving the billing data request sent by the first network element when the billing trigger conditions are met, wherein the billing data request carries billing information for communication between terminals via satellite; based on the billing data request, a billing data record is created; and a billing data response is sent to the first network element. A new service unit is authorized.

[0451] 8) IMS-AGW / AS sends an acknowledgment response 200 OK to P-CSCF, and P-CSCF forwards it to the corresponding UE, such as P-CSCF A forwarding it to UE A.

[0452] Example 3: If, due to satellite movement, or if no satellite can serve two UEs (IMS also cannot serve two UEs), the IMS-AGW may change, resulting in an IMS-AGW IP address switch. For example, it may switch to an IMS-AGW on a different satellite, or traffic may be routed back to the ground, selecting a terrestrial IMS-AGW. The billing process for this can be as follows: Figure 17 (The message sequence diagram of the mid-session procedure is shown below. The P-CSCF in the process can also be the S-CSCF, without restriction.) It involves the following operations:

[0453] 1) In an ongoing SIP session, the P-CSCF receives a SIP RE-INVITE (which may correspond to a session re-establishment request) and forwards it to the IMS-GWF / AS.

[0454] 2) Upon receiving a SIP RE-INVITE, the IMS-GWF / AS performs service control and sends a Reserve UnitsRequest [Update] to the local OCS (i.e., OCS(home)) to update previously initiated sessions. This request may include at least one of the following: UE-SAT-UE information (corresponding to the first information mentioned above), AGW inserted indication (corresponding to the insertion indication of the first network element mentioned above), satellite ID (corresponding to the satellite identification information mentioned above), AGW indication on the satellite, AGW IP address (corresponding to the fifth information mentioned above), satellite communication start timestamp information, satellite communication end timestamp information, and satellite information (corresponding to the sixth information mentioned above). New service units are requested, and the service units being used (if any) are also reported. This operation corresponds to the above-mentioned acquisition of billing information for satellite communication between terminals when the billing triggering conditions are met; sending a billing data request to the second network element, wherein the billing data request carries the billing information; the billing triggering conditions include receiving a session re-establishment request; and the billing data request is an update billing data request.

[0455] 3) The OCS performs credit control and authorizes new service units in the Reserve Units Response; the OCS sends the Reserve Units Response to the IMS-GWF / AS. This operation corresponds to receiving the billing data request sent by the first network element when the billing trigger conditions are met, wherein the billing data request carries billing information for communication between terminals via satellite; based on the billing data request, a billing data record is created; and a billing data response is sent to the first network element.

[0456] 4) The IMS-GWF / AS sends the RE-INVITE to the P-CSCF, which then forwards it. Further SIP signaling interactions are then performed.

[0457] 5) The P-CSCF receives the SIP 200OK message (or the SIP 200OK message carrying RE-INVITE) for RE-INVITE confirmation and forwards it to the IMS-GWF / AS.

[0458] 6) After IMS-GWF / AS performs service control, if the trigger is active, IMS-GWF / AS sends a Reserve Units Request [Update] to OCS to update the session. This request may include at least one of the following: UE-SAT-UE information (corresponding to the first information mentioned above), AGW inserted indication (corresponding to the insertion indication of the first network element mentioned above), satellite ID (corresponding to the satellite identification information mentioned above), AGW indication on the satellite, AGW IP address (corresponding to the fifth information mentioned above), satellite communication start timestamp information, satellite communication end timestamp information, and satellite information (corresponding to the sixth information mentioned above). New service units are requested, and used service units (if they exist) are also reported. This operation corresponds to obtaining billing information for satellite communication between terminals when the billing triggering conditions are met; sending a billing data request to the second network element, wherein the billing data request carries the billing information; the billing triggering conditions include receiving a session update request or receiving a Session Initiation Protocol (SIP) response; and the billing data request is an update billing data request.

[0459] 7) The OCS performs credit control and authorizes new service units in the Reserve Units Response; the OCS sends the Reserve Units Response to the IMS-GWF / AS. This operation corresponds to receiving the billing data request sent by the first network element when the billing trigger conditions are met, wherein the billing data request carries billing information for communication between terminals via satellite; a billing data record is created according to the billing data request; and a billing data response is sent to the first network element.

[0460] 8) The IMS-GWF / AS sends a SIP 200 OK message to the P-CSCF to confirm the RE-INVITE mentioned above, and the P-CSCF forwards it.

[0461] It should be noted that the relevant content of the above embodiments can be referred to interchangeably, and repeated details will not be repeated. Furthermore, the network elements involved in the accompanying drawings may be a single network element or cover multiple network elements (for example, the P-CSCF may cover the P-CSCF on both the UE A and UE B sides in the process), and this is not limited here. In addition, for specific details regarding the UE A-related network elements and / or UE B-related network elements involved in the accompanying drawings, please refer to the current relevant solutions and / or Figure 10 The details are as follows, and will not be elaborated further. It should be noted that the network element P-CSCF in the diagram can also be implemented as S-CSCF; this is not a restriction.

[0462] Based on the above, the solutions provided in this application involve the following:

[0463] 1. Different charging triggering network elements trigger different charging methods for IMS of UE-SAT-UE;

[0464] 2. Based on 1, IMS-GWF (CTF in it) triggers converged billing or online billing for UE-SAT-UE communication based on the received satellite ID of the UE accessing the network via NR satellite and the billing trigger conditions.

[0465] 3. The P-CSCF (CTF in P-CSCF) triggers offline billing for UE-SAT-UE communication based on the received satellite ID of the UE accessing the network via NR satellite and the billing trigger conditions.

[0466] 4. Based on 2 and 3, the billing data request may include one or more of the following billing parameters: satellite information (such as satellite ID), UE-SAT-UE information, AGW inserted indication, indication of AGW location on the satellite, AGW IP address, satellite communication start timestamp information, and satellite communication end timestamp information, etc.

[0467] In summary, based on this solution, IMS can be used to bill UE-SAT-UE services, and even traffic that supports UE-SAT-UE services through multiple satellites or back to the ground can be clearly billed.

[0468] This application embodiment also provides a billing device, wherein the billing device is a first network element, such as... Figure 18 As shown, it includes a memory 181, a transceiver 182, and a processor 183:

[0469] Memory 181 is used to store computer programs; transceiver 182 is used to send and receive data under the control of processor 183; processor 183 is used to read the computer program in memory 181 and perform the following operations:

[0470] If the billing trigger conditions are met, obtain billing information for communication between terminals via satellite;

[0471] The transceiver 182 sends a billing data request to the second network element, and the billing data request carries the billing information.

[0472] The billing device provided in this application embodiment obtains billing information for communication between terminals via satellite when the billing triggering conditions are met; sends a billing data request to a second network element, wherein the billing data request carries the billing information; and can support the implementation of relevant billing for UE-satellite-UE scenarios (i.e., scenarios where terminals communicate via satellite).

[0473] Specifically, transceiver 182 is used to receive and send data under the control of processor 183.

[0474] Among them, Figure 18 In this context, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits together, represented by one or more processors (processor 183) and memory (memory 181). The bus architecture may also link together various other circuits, such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 182 may be multiple elements, including transmitters and receivers, providing a unit for communicating with various other devices over transmission media, including wireless channels, wired channels, optical fibers, etc. The processor 183 is responsible for managing the bus architecture and general processing, and the memory 181 may store data used by the processor 183 during operation.

[0475] The processor 183 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture.

[0476] The billing triggering conditions include at least one of the following: receiving a session establishment request; receiving a session re-establishment request; receiving a session update request; receiving a session release request; receiving a handover indication or release indication for the first network element; or receiving a Session Initiation Protocol (SIP) response.

[0477] In this embodiment of the application, when the charging triggering condition includes receiving a session establishment request or receiving a SIP response, the charging data request is an initial charging data request; and / or, when the charging triggering condition includes receiving a session re-establishment request, receiving a session update request, receiving a handover indication for the first network element, or receiving a SIP response, the charging data request is an update charging data request; and / or, when the charging triggering condition includes receiving a session release request, receiving a release indication for the first network element, or receiving a SIP response, the charging data request is an end charging data request.

[0478] Wherein, when the billing data request is an initial billing data request, an update billing data request, or an end billing data request, the billing information includes at least one of the following: first information, the first information indicating a service that supports communication between terminals via satellite; an insertion indication of the first network element; second information, the second information being an indication of the first network element on the ground; third information, the third information indicating the ground IP address of the first network element; ground communication start timestamp information; and ground communication end timestamp information.

[0479] In this embodiment of the application, when the billing data request is an initial billing data request, an update billing data request, or an end billing data request, the billing information includes at least one of the following: first information, the first information indicating a service that supports inter-terminal communication via satellite; an insertion indication of the first network element; identification information of the satellite; fourth information, the fourth information being an indication of the first network element on the satellite; fifth information, the fifth information indicating the on-board IP address of the first network element; satellite communication start timestamp information; satellite communication end timestamp information; and sixth information, the sixth information indicating information about the satellite that supports inter-terminal communication via satellite.

[0480] Furthermore, the operation also includes: receiving a billing data response sent by the second network element through the transceiver.

[0481] It should be noted that the device provided in this application embodiment can implement all the method steps implemented in the first network element side method embodiment and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0482] This application embodiment also provides a billing device, which is a second network element, such as... Figure 19 As shown, it includes a memory 191, a transceiver 192, and a processor 193:

[0483] Memory 191 is used to store computer programs; transceiver 192 is used to send and receive data under the control of processor 193; processor 193 is used to read the computer program in memory 191 and perform the following operations:

[0484] The transceiver 192 receives a billing data request sent by the first network element when the billing trigger condition is met. The billing data request carries billing information for communication between terminals via satellite.

[0485] Create a billing data record based on the billing data request.

[0486] The billing device provided in this application embodiment receives a billing data request sent by a first network element when the billing triggering conditions are met. The billing data request carries billing information for communication between terminals via satellite. Based on the billing data request, a billing data record is created. This device can support billing for UE-satellite-UE scenarios (i.e., scenarios where terminals communicate via satellite).

[0487] Specifically, transceiver 192 is used to receive and send data under the control of processor 193.

[0488] Among them, Figure 19 In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits together, represented by one or more processors (processor 193) and memory (memory 191). The bus architecture can also link various other circuits, such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 192 can be multiple elements, including transmitters and receivers, providing a unit for communicating with various other devices over transmission media, including wireless channels, wired channels, optical fibers, etc. The processor 193 is responsible for managing the bus architecture and general processing, and the memory 191 can store data used by the processor 193 during operation.

[0489] The processor 193 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture.

[0490] The billing triggering conditions include at least one of the following: receiving a session establishment request; receiving a session re-establishment request; receiving a session update request; receiving a session release request; receiving a handover indication or release indication for the first network element; or receiving a Session Initiation Protocol (SIP) response.

[0491] In this embodiment of the application, when the charging triggering condition includes receiving a session establishment request or receiving a SIP response, the charging data request is an initial charging data request; and / or, when the charging triggering condition includes receiving a session re-establishment request, receiving a session update request, receiving a handover indication for the first network element, or receiving a SIP response, the charging data request is an update charging data request; and / or, when the charging triggering condition includes receiving a session release request, receiving a release indication for the first network element, or receiving a SIP response, the charging data request is an end charging data request.

[0492] Wherein, when the billing data request is an initial billing data request, an update billing data request, or an end billing data request, the billing information includes at least one of the following: first information, the first information indicating a service that supports communication between terminals via satellite; an insertion indication of the first network element; second information, the second information being an indication of the first network element on the ground; third information, the third information indicating the ground IP address of the first network element; ground communication start timestamp information; and ground communication end timestamp information.

[0493] In this embodiment of the application, when the billing data request is an initial billing data request, an update billing data request, or an end billing data request, the billing information includes at least one of the following: first information, the first information indicating a service that supports inter-terminal communication via satellite; an insertion indication of the first network element; identification information of the satellite; fourth information, the fourth information being an indication of the first network element on the satellite; fifth information, the fifth information indicating the on-board IP address of the first network element; satellite communication start timestamp information; satellite communication end timestamp information; and sixth information, the sixth information indicating information about the satellite that supports inter-terminal communication via satellite.

[0494] Furthermore, the operation also includes: sending a billing data response to the first network element through the transceiver.

[0495] The billing data record includes at least one of the following: first information, indicating a service that supports communication between terminals via satellite; insertion indication of the first network element; second information, indicating the first network element on the ground; third information, indicating the ground IP address of the first network element; ground communication start timestamp information; ground communication end timestamp information; satellite identification information; fourth information, indicating the first network element on the satellite; fifth information, indicating the on-board IP address of the first network element; satellite communication start timestamp information; satellite communication end timestamp information; and sixth information, indicating information about the satellite that supports communication between terminals via satellite.

[0496] It should be noted that the device provided in this application embodiment can implement all the method steps implemented in the above second network element side method embodiment and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0497] This application embodiment also provides a billing device, applied to a first network element, such as... Figure 20 As shown, it includes:

[0498] The first acquisition unit 201 is used to acquire billing information for communication between terminals via satellite when the billing triggering conditions are met.

[0499] The first sending unit 202 is used to send a billing data request to the second network element, wherein the billing data request carries the billing information.

[0500] The billing device provided in this application embodiment obtains billing information for communication between terminals via satellite when the billing triggering conditions are met; sends a billing data request to a second network element, wherein the billing data request carries the billing information; and can support billing for UE-satellite-UE scenarios (i.e., scenarios where terminals communicate via satellite).

[0501] The billing triggering conditions include at least one of the following: receiving a session establishment request; receiving a session re-establishment request; receiving a session update request; receiving a session release request; receiving a handover indication or release indication for the first network element; or receiving a Session Initiation Protocol (SIP) response.

[0502] In this embodiment of the application, when the charging triggering condition includes receiving a session establishment request or receiving a SIP response, the charging data request is an initial charging data request; and / or, when the charging triggering condition includes receiving a session re-establishment request, receiving a session update request, receiving a handover indication for the first network element, or receiving a SIP response, the charging data request is an update charging data request; and / or, when the charging triggering condition includes receiving a session release request, receiving a release indication for the first network element, or receiving a SIP response, the charging data request is an end charging data request.

[0503] Wherein, when the billing data request is an initial billing data request, an update billing data request, or an end billing data request, the billing information includes at least one of the following: first information, the first information indicating a service that supports communication between terminals via satellite; an insertion indication of the first network element; second information, the second information being an indication of the first network element on the ground; third information, the third information indicating the ground IP address of the first network element; ground communication start timestamp information; and ground communication end timestamp information.

[0504] In this embodiment of the application, when the billing data request is an initial billing data request, an update billing data request, or an end billing data request, the billing information includes at least one of the following: first information, the first information indicating a service that supports inter-terminal communication via satellite; an insertion indication of the first network element; identification information of the satellite; fourth information, the fourth information being an indication of the first network element on the satellite; fifth information, the fifth information indicating the on-board IP address of the first network element; satellite communication start timestamp information; satellite communication end timestamp information; and sixth information, the sixth information indicating information about the satellite that supports inter-terminal communication via satellite.

[0505] Furthermore, the billing device further includes: a first receiving unit, used to receive the billing data response sent by the second network element.

[0506] It should be noted that the apparatus provided in this application embodiment can implement all the method steps implemented in the first network element side method embodiment and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0507] This application also provides a billing device applied to a second network element, such as... Figure 21 As shown, it includes:

[0508] The second receiving unit 211 is used to receive a billing data request sent by the first network element when the billing triggering condition is met. The billing data request carries billing information for communication between terminals via satellite.

[0509] The first creation unit 212 is used to create a billing data record according to the billing data request.

[0510] The billing device provided in this application embodiment receives a billing data request sent by a first network element when the billing trigger condition is met. The billing data request carries billing information for communication between terminals via satellite. Based on the billing data request, a billing data record is created. This device can support billing for UE-satellite-UE scenarios (i.e., scenarios where terminals communicate via satellite).

[0511] The billing triggering conditions include at least one of the following: receiving a session establishment request; receiving a session re-establishment request; receiving a session update request; receiving a session release request; receiving a handover indication or release indication for the first network element; or receiving a Session Initiation Protocol (SIP) response.

[0512] In this embodiment of the application, when the charging triggering condition includes receiving a session establishment request or receiving a SIP response, the charging data request is an initial charging data request; and / or, when the charging triggering condition includes receiving a session re-establishment request, receiving a session update request, receiving a handover indication for the first network element, or receiving a SIP response, the charging data request is an update charging data request; and / or, when the charging triggering condition includes receiving a session release request, receiving a release indication for the first network element, or receiving a SIP response, the charging data request is an end charging data request.

[0513] Wherein, when the billing data request is an initial billing data request, an update billing data request, or an end billing data request, the billing information includes at least one of the following: first information, the first information indicating a service that supports communication between terminals via satellite; an insertion indication of the first network element; second information, the second information being an indication of the first network element on the ground; third information, the third information indicating the ground IP address of the first network element; ground communication start timestamp information; and ground communication end timestamp information.

[0514] In this embodiment of the application, when the billing data request is an initial billing data request, an update billing data request, or an end billing data request, the billing information includes at least one of the following: first information, the first information indicating a service that supports inter-terminal communication via satellite; an insertion indication of the first network element; identification information of the satellite; fourth information, the fourth information being an indication of the first network element on the satellite; fifth information, the fifth information indicating the on-board IP address of the first network element; satellite communication start timestamp information; satellite communication end timestamp information; and sixth information, the sixth information indicating information about the satellite that supports inter-terminal communication via satellite.

[0515] Furthermore, the billing device further includes a second sending unit, used to send a billing data response to the first network element.

[0516] The billing data record includes at least one of the following: first information, indicating a service that supports communication between terminals via satellite; insertion indication of the first network element; second information, indicating the first network element on the ground; third information, indicating the ground IP address of the first network element; ground communication start timestamp information; ground communication end timestamp information; satellite identification information; fourth information, indicating the first network element on the satellite; fifth information, indicating the on-board IP address of the first network element; satellite communication start timestamp information; satellite communication end timestamp information; and sixth information, indicating information about the satellite that supports communication between terminals via satellite.

[0517] It should be noted that the apparatus provided in this application embodiment can implement all the method steps implemented in the above second network element side method embodiment and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0518] It should be noted that the division of units in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0519] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0520] This application embodiment also provides a non-transient readable storage medium storing a program for causing a processor to execute the aforementioned billing method on the first network element side or the second network element side.

[0521] The non-transiently readable storage medium can be any available medium or data storage device that the processor can access, including but not limited to magnetic memory (e.g., floppy disk, hard disk, magnetic tape, magneto-optical disk (MO)), optical memory (e.g., compact disc (CD), digital video disc (DVD), Blu-ray disc (BD), high-definition versatile disc (HVD)), and semiconductor memory (e.g., ROM, erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), non-volatile memory (NAND (Non-volatile Memory Device) FLASH), solid state hard disk (SSD)).

[0522] The aforementioned implementation embodiments of the billing method on the first network element side or the second network element side are all applicable to the embodiments of the non-transiently readable storage medium and can achieve the same technical effect.

[0523] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.

[0524] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0525] These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0526] These processors can execute instructions that can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable device for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0527] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A billing method applied to a first network element, characterized in that, include: If the billing trigger conditions are met, obtain billing information for communication between terminals via satellite; A billing data request is sent to the second network element, the billing data request carrying the billing information.

2. The billing method according to claim 1, characterized in that, The billing trigger condition includes at least one of the following: A session establishment request has been received; A session re-establishment request has been received. Received a session update request; Received session release request; Receive a handover instruction or release instruction for the first network element; Received a Session Initiation Protocol (SIP) response.

3. The billing method according to claim 1 or 2, characterized in that, When the billing triggering conditions include receiving a session establishment request or receiving a SIP response, the billing data request is an initial billing data request; And / or, if the billing triggering conditions include receiving a session re-establishment request, receiving a session update request, receiving a handover indication for the first network element, or receiving a SIP response, the billing data request is an update billing data request; And / or, if the billing triggering conditions include receiving a session release request, receiving a release instruction for the first network element, or receiving a SIP response, the billing data request is an end-of-billing-data request.

4. The billing method according to claim 3, characterized in that, When the billing data request is an initial billing data request, an update billing data request, or a termination billing data request, the billing information includes at least one of the following: The first information indicates that the service supports communication between terminals via satellite; Insertion indication of the first network element; The second information is the indication of the first network element on the ground; The third information indicates the ground IP address of the first network element; Ground communication start timestamp information; Ground communication end timestamp information.

5. The billing method according to claim 3, characterized in that, When the billing data request is an initial billing data request, an update billing data request, or a termination billing data request, the billing information includes at least one of the following: The first information indicates that the service supports communication between terminals via satellite; Insertion indication of the first network element; The satellite's identification information; The fourth information is the indication of the first network element on the satellite; The fifth piece of information indicates the on-board IP address of the first network element; Satellite communication start timestamp information; Satellite communication end timestamp information; The sixth information indicates information about satellites that support inter-terminal communication via satellite.

6. The billing method according to claim 1, characterized in that, Also includes: Receive the billing data response sent by the second network element.

7. A billing method applied to a second network element, characterized in that, include: Receive a billing data request sent by the first network element when the billing triggering conditions are met, wherein the billing data request carries billing information for communication between terminals via satellite; Create a billing data record based on the billing data request.

8. The billing method according to claim 7, characterized in that, The billing trigger condition includes at least one of the following: A session establishment request has been received; A session re-establishment request has been received. Received a session update request; Received session release request; Receive a handover instruction or release instruction for the first network element; Received a Session Initiation Protocol (SIP) response.

9. The billing method according to claim 7 or 8, characterized in that, When the billing triggering conditions include receiving a session establishment request or receiving a SIP response, the billing data request is an initial billing data request; And / or, if the billing triggering conditions include receiving a session re-establishment request, receiving a session update request, receiving a handover indication for the first network element, or receiving a SIP response, the billing data request is an update billing data request; And / or, if the billing triggering conditions include receiving a session release request, receiving a release instruction for the first network element, or receiving a SIP response, the billing data request is an end-of-billing-data request.

10. The billing method according to claim 9, characterized in that, When the billing data request is an initial billing data request, an update billing data request, or a termination billing data request, the billing information includes at least one of the following: The first information indicates that the service supports communication between terminals via satellite; Insertion indication of the first network element; The second information is the indication of the first network element on the ground; The third information indicates the ground IP address of the first network element; Ground communication start timestamp information; Ground communication end timestamp information.

11. The billing method according to claim 9, characterized in that, When the billing data request is an initial billing data request, an update billing data request, or a termination billing data request, the billing information includes at least one of the following: The first information indicates that the service supports communication between terminals via satellite; Insertion indication of the first network element; The satellite's identification information; The fourth information is the indication of the first network element on the satellite; The fifth piece of information indicates the on-board IP address of the first network element; Satellite communication start timestamp information; Satellite communication end timestamp information; The sixth information indicates information about satellites that support inter-terminal communication via satellite.

12. The billing method according to claim 7, characterized in that, Also includes: Send a billing data response to the first network element.

13. The billing method according to claim 7, characterized in that, The billing data record includes at least one of the following: The first information indicates that the service supports communication between terminals via satellite; Insertion indication of the first network element; The second information is the indication of the first network element on the ground; The third information indicates the ground IP address of the first network element; Ground communication start timestamp information; Ground communication end timestamp information; The satellite's identification information; The fourth information is the indication of the first network element on the satellite; The fifth piece of information indicates the on-board IP address of the first network element; Satellite communication start timestamp information; Satellite communication end timestamp information; The sixth information indicates information about satellites that support inter-terminal communication via satellite.

14. A billing device, wherein the billing device is a first network element, characterized in that, Includes memory, transceiver, and processor: A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations: If the billing trigger conditions are met, obtain billing information for communication between terminals via satellite; The transceiver sends a billing data request to the second network element, and the billing data request carries the billing information.

15. The billing device according to claim 14, characterized in that, The billing trigger condition includes at least one of the following: A session establishment request has been received; A session re-establishment request has been received. Received a session update request; Received session release request; Receive a handover instruction or release instruction for the first network element; Received a Session Initiation Protocol (SIP) response.

16. The billing device according to claim 14 or 15, characterized in that, When the billing triggering conditions include receiving a session establishment request or receiving a SIP response, the billing data request is an initial billing data request; And / or, if the billing triggering conditions include receiving a session re-establishment request, receiving a session update request, receiving a handover indication for the first network element, or receiving a SIP response, the billing data request is an update billing data request; And / or, if the billing triggering conditions include receiving a session release request, receiving a release instruction for the first network element, or receiving a SIP response, the billing data request is an end-of-billing-data request.

17. The billing device according to claim 16, characterized in that, When the billing data request is an initial billing data request, an update billing data request, or a termination billing data request, the billing information includes at least one of the following: The first information indicates that the service supports communication between terminals via satellite; Insertion indication of the first network element; The second information is the indication of the first network element on the ground; The third information indicates the ground IP address of the first network element; Ground communication start timestamp information; Ground communication end timestamp information.

18. The billing device according to claim 16, characterized in that, When the billing data request is an initial billing data request, an update billing data request, or a termination billing data request, the billing information includes at least one of the following: The first information indicates that the service supports communication between terminals via satellite; Insertion indication of the first network element; The satellite's identification information; The fourth information is the indication of the first network element on the satellite; The fifth piece of information indicates the on-board IP address of the first network element; Satellite communication start timestamp information; Satellite communication end timestamp information; The sixth information indicates information about satellites that support inter-terminal communication via satellite.

19. The billing device according to claim 14, characterized in that, The operation also includes: The transceiver receives the billing data response sent by the second network element.

20. A billing device, wherein the billing device is a second network element, characterized in that, Includes memory, transceiver, and processor: A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations: The transceiver receives a billing data request sent by the first network element when the billing triggering conditions are met. The billing data request carries billing information for communication between terminals via satellite. Create a billing data record based on the billing data request.

21. The billing device according to claim 20, characterized in that, The billing trigger condition includes at least one of the following: A session establishment request has been received; A session re-establishment request has been received. Received a session update request; Received session release request; Receive a handover instruction or release instruction for the first network element; Received a Session Initiation Protocol (SIP) response.

22. The billing device according to claim 20 or 21, characterized in that, When the billing triggering conditions include receiving a session establishment request or receiving a SIP response, the billing data request is an initial billing data request; And / or, if the billing triggering conditions include receiving a session re-establishment request, receiving a session update request, receiving a handover indication for the first network element, or receiving a SIP response, the billing data request is an update billing data request; And / or, if the billing triggering conditions include receiving a session release request, receiving a release instruction for the first network element, or receiving a SIP response, the billing data request is an end-of-billing-data request.

23. The billing device according to claim 22, characterized in that, When the billing data request is an initial billing data request, an update billing data request, or a termination billing data request, the billing information includes at least one of the following: The first information indicates that the service supports communication between terminals via satellite; Insertion indication of the first network element; The second information is the indication of the first network element on the ground; The third information indicates the ground IP address of the first network element; Ground communication start timestamp information; Ground communication end timestamp information.

24. The billing device according to claim 22, characterized in that, When the billing data request is an initial billing data request, an update billing data request, or a termination billing data request, the billing information includes at least one of the following: The first information indicates that the service supports communication between terminals via satellite; Insertion indication of the first network element; The satellite's identification information; The fourth information is the indication of the first network element on the satellite; The fifth piece of information indicates the on-board IP address of the first network element; Satellite communication start timestamp information; Satellite communication end timestamp information; The sixth information indicates information about satellites that support inter-terminal communication via satellite.

25. The billing device according to claim 20, characterized in that, The operation also includes: The transceiver sends a billing data response to the first network element.

26. The billing device according to claim 20, characterized in that, The billing data record includes at least one of the following: The first information indicates that the service supports communication between terminals via satellite; Insertion indication of the first network element; The second information is the indication of the first network element on the ground; The third information indicates the ground IP address of the first network element; Ground communication start timestamp information; Ground communication end timestamp information; The satellite's identification information; The fourth information is the indication of the first network element on the satellite; The fifth piece of information indicates the on-board IP address of the first network element; Satellite communication start timestamp information; Satellite communication end timestamp information; The sixth information indicates information about satellites that support inter-terminal communication via satellite.

27. A billing device, applied to a first network element, characterized in that, include: The first acquisition unit is used to acquire billing information for communication between terminals via satellite when the billing triggering conditions are met. The first sending unit is used to send a billing data request to the second network element, wherein the billing data request carries the billing information.

28. A billing device applied to a second network element, characterized in that, include: The second receiving unit is used to receive a billing data request sent by the first network element when the billing triggering conditions are met. The billing data request carries billing information for communication between terminals via satellite. The first creation unit is used to create a billing data record based on the billing data request.

29. A non-transiently readable storage medium, characterized in that, The non-transiently readable storage medium stores a program for causing a processor to execute the billing method according to any one of claims 1 to 13.

Images