Backhaul charging method and apparatus, network device, and readable storage medium

By sending billing data requests in the core network, including satellite backhaul type and identifier, billing of satellite backhaul traffic is realized, solving the problem of satellite backhaul billing in the existing technology, and improving resource allocation efficiency.

WO2024234872A1PCT designated stage expired Publication Date: 2024-11-21DATANG MOBILE COMM EQUIP CO LTD
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2024/086775
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-12
Filing Date
2024-04-09
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

The prior art cannot realize effective billing when satellite backhauls, resulting in low efficiency in satellite transmission resource allocation.

Method used

The first functional entity of the core network sends a billing data request to the second functional entity, including parameters such as satellite return type, satellite identity and on-satellite data network access identifier DNAI, triggering back-pass billing, realizing satellite return to return to satellite billing of traffic transmission.

Benefits of technology

It realizes effective billing of satellite backhaul traffic, solves the billing problem under the satellite backhaul architecture, and improves resource allocation efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024086775_21112024_PF_FP_ABST
    Figure CN2024086775_21112024_PF_FP_ABST
Patent Text Reader

Abstract

The present application provides a backhaul charging method and apparatus, a network device, and a readable storage medium. The method comprises: sending a charging data request to a second functional entity, the charging data request being used for backhaul charging, wherein the charging data request comprises a backhaul charging related parameter.
Need to check novelty before this filing date? Find Prior Art

Description

Backhaul billing method, device, network equipment and readable storage medium

[0001] This disclosure claims priority to the Chinese patent application filed with the China Patent Office on May 12, 2023, with application number 202310536785.3 and application name “Backhaul billing method, device, network device and readable storage medium”, the entire contents of which are incorporated by reference into this disclosure. Technical Field

[0002] The present disclosure relates to the field of wireless technology, and in particular to a backhaul billing method, apparatus, network device, and readable storage medium. Background Art

[0003] For remote areas, disaster-stricken areas, deserts and other areas where it is difficult to deploy base stations, gateways and other equipment, information exchange needs to be achieved through satellites. In this way, satellites can be integrated with the fifth generation (5G) network and the satellite's transmission resources can be used as backhaul for ground fixed base stations or mobile base stations.

[0004] At present, since different satellite types will bring different delays when transmitting back via satellite, in order to ensure the effective allocation of satellite transmission resources, it is necessary to bill satellite backhaul. However, the use of relevant technical solutions cannot achieve backhaul billing.

[0005] Summary of the Invention

[0006] The present disclosure aims to provide a backhaul billing method, apparatus, network device, and readable storage medium for implementing backhaul billing.

[0007] An embodiment of the present disclosure provides a backhaul charging method, wherein the method is performed by a first functional entity and includes:

[0008] Sending a charging data request to the second functional entity, where the charging data request is used for backhaul charging; wherein the charging data request includes backhaul charging-related parameters.

[0009] Optionally, in the backhaul billing method, the billing data request is an initial request for backhaul billing;

[0010] The backhaul billing related parameters include one or more of the following parameters:

[0011] Satellite backhaul type;

[0012] Satellite ID of the preset type of satellite;

[0013] Onboard Data Network Access Identifier DNAI.

[0014] Optionally, in the backhaul billing method, the billing data request is a request for updating billing data for backhaul billing; and the backhaul billing-related parameters include one or more of the following parameters:

[0015] Satellite returns type change information;

[0016] Current satellite backhaul type;

[0017] Satellite ID of the preset type of satellite;

[0018] Onboard Data Network Access Identifier DNAI;

[0019] Satellite backhaul type usage report.

[0020] Optionally, in the backhaul billing method, the billing data request is a request for termination of billing data for backhaul billing; and the backhaul billing-related parameters include:

[0021] Satellite backhaul type usage report.

[0022] Optionally, the backhaul billing method further includes:

[0023] Obtain a first response message sent by the second functional entity; wherein the first response message includes a usage report of the satellite backhaul type.

[0024] Optionally, in the backhaul billing method, the usage report includes:

[0025] A first usage report is used to record the satellite backhaul traffic using the current satellite backhaul type; or

[0026] The second usage report is used to record the satellite backhaul traffic using the current satellite backhaul type and the satellite backhaul traffic using the historical satellite backhaul type.

[0027] Optionally, in the backhaul billing method, sending a billing data request to the second functional entity includes:

[0028] When the backhaul charging trigger condition is obtained, a charging data request is sent to the second functional entity.

[0029] Optionally, the backhaul billing method further includes:

[0030] During the first session establishment process, when at least one of the following events is obtained, it is determined that the backhaul charging trigger condition is obtained:

[0031] Get the return satellite type;

[0032] Obtain satellite identification;

[0033] Based on the mapping relationship between the ground synchronous orbit GEO satellite identification ID and DNAI configured locally by the first functional entity, the on-board DNAI is selected.

[0034] Optionally, the backhaul billing method further includes:

[0035] During the first session modification process, the backhaul charging trigger condition is determined to be obtained when at least one of the following events is obtained:

[0036] Get usage reports for satellite backhaul types;

[0037] Obtain information on changes in satellite return types;

[0038] Get the satellite ID of the preset type of satellite;

[0039] Based on the mapping relationship between the GEO satellite identification ID and DNAI configured locally by the first functional entity, the on-board DNAI is selected.

[0040] Optionally, in the backhaul charging method, when the network where the first functional entity is located is the access network of the terminal, after obtaining the first response message sent by the second functional entity, the method further includes:

[0041] A first request message is sent to a third functional entity of the local network of the terminal, wherein the first request message includes a usage report of a satellite backhaul type.

[0042] Optionally, in the backhaul charging method, when the network where the first functional entity is located is a local network of the terminal, the method further includes:

[0043] Obtaining a second request message sent by a fourth functional entity of the access network of the terminal; wherein the second request message includes a usage report of a satellite backhaul type;

[0044] According to the second request message, a charging data request is sent to the second functional entity; the backhaul charging related parameters in the charging data request include the usage report.

[0045] Optionally, the backhaul billing method further includes:

[0046] Sending a third request message to the UPF entity, where the third request message is used to request the UPF entity to start counting traffic backhauled by the satellite for the first session;

[0047] Obtain a second response message fed back by the UPF entity based on the third request message; wherein, the second response message includes a usage report of the satellite backhaul type obtained after performing the traffic counting on the first session.

[0048] The present disclosure also provides a backhaul charging method, which is performed by a second functional entity and includes:

[0049] Obtain a charging data request sent by the first functional entity, where the charging data request is used for backhaul charging; wherein the charging data request includes backhaul charging-related parameters.

[0050] Optionally, in the backhaul billing method, the billing data request is an initial request for backhaul billing; and the backhaul billing-related parameters include one or more of the following parameters:

[0051] Satellite backhaul type;

[0052] Satellite ID of the preset type of satellite;

[0053] Onboard Data Network Access Identifier DNAI.

[0054] Optionally, in the backhaul billing method, the billing data request is a request for updating billing data for backhaul billing; and the backhaul billing-related parameters include one or more of the following parameters:

[0055] Satellite returns type change information;

[0056] Current satellite backhaul type;

[0057] Satellite ID of the preset type of satellite;

[0058] Onboard Data Network Access Identifier DNAI;

[0059] Satellite backhaul type usage report.

[0060] Optionally, in the backhaul billing method, the billing data request is a request for termination of billing data for backhaul billing; and the backhaul billing-related parameters include:

[0061] Satellite backhaul type usage report.

[0062] Optionally, the backhaul billing method further includes:

[0063] A first response message is sent to the first functional entity; wherein the first response message includes a usage report of the satellite backhaul type.

[0064] Optionally, in the backhaul billing method, the usage report includes:

[0065] A first usage report is used to record the satellite backhaul traffic using the current satellite backhaul type; or

[0066] The second usage report is used to record the satellite backhaul traffic using the current satellite backhaul type and the satellite backhaul traffic using the historical satellite backhaul type.

[0067] The present disclosure also provides a network device, which includes a memory, a transceiver, and a processor:

[0068] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0069] Sending a charging data request to the second functional entity, where the charging data request is used for backhaul charging; wherein the charging data request includes backhaul charging-related parameters.

[0070] Optionally, in the network device, the billing data request is an initial request for backhaul billing;

[0071] The backhaul billing related parameters include one or more of the following parameters:

[0072] Satellite backhaul type;

[0073] Satellite ID of the preset type of satellite;

[0074] Onboard Data Network Access Identifier DNAI.

[0075] Optionally, in the network device, the billing data request is a request for updating billing data for backhaul billing; and the backhaul billing-related parameters include one or more of the following parameters:

[0076] Satellite returns type change information;

[0077] Current satellite backhaul type;

[0078] Satellite ID of the preset type of satellite;

[0079] Onboard Data Network Access Identifier DNAI;

[0080] Satellite backhaul type usage report.

[0081] Optionally, in the network device, the billing data request is a request for termination of billing data for backhaul billing; wherein the backhaul billing-related parameters include:

[0082] Satellite backhaul type usage report.

[0083] Optionally, in the network device, the processor is further configured to:

[0084] Obtain a first response message sent by the second functional entity; wherein the first response message includes a usage report of the satellite backhaul type.

[0085] Optionally, in the network device, the processor sending the charging data request to the second functional entity includes:

[0086] When the backhaul charging trigger condition is obtained, a charging data request is sent to the second functional entity.

[0087] The present disclosure also provides a network device, which includes a memory, a transceiver, and a processor:

[0088] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0089] Obtain a charging data request sent by the first functional entity, where the charging data request is used for backhaul charging; wherein the charging data request includes backhaul charging-related parameters.

[0090] Optionally, in the network device, the billing data request is an initial request for backhaul billing; and the backhaul billing-related parameters include one or more of the following parameters:

[0091] Satellite backhaul type;

[0092] Satellite ID of the preset type of satellite;

[0093] Onboard Data Network Access Identifier DNAI.

[0094] Optionally, in the network device, the billing data request is a request for updating billing data for backhaul billing; and the backhaul billing-related parameters include one or more of the following parameters:

[0095] Satellite returns type change information;

[0096] Current satellite backhaul type;

[0097] Satellite ID of the preset type of satellite;

[0098] Onboard Data Network Access Identifier DNAI;

[0099] Satellite backhaul type usage report.

[0100] Optionally, in the network device, the billing data request is a request for termination of billing data for backhaul billing; wherein the backhaul billing-related parameters include:

[0101] Satellite backhaul type usage report.

[0102] Optionally, in the network device, the processor is further configured to:

[0103] A first response message is sent to the first functional entity; wherein the first response message includes a usage report of the satellite backhaul type.

[0104] The present disclosure also provides a backhaul charging device, which is applied to a first functional entity and includes:

[0105] The sending unit is used to send a billing data request to the second functional entity, where the billing data request is used for backhaul billing; wherein the billing data request includes backhaul billing related parameters.

[0106] The present disclosure also provides a backhaul charging device, which is applied to a second functional entity and includes:

[0107] The obtaining unit is configured to obtain a charging data request sent by the first functional entity, wherein the charging data request is used for backhaul charging; wherein the charging data request includes backhaul charging related parameters.

[0108] An embodiment of the present disclosure further provides a processor-readable storage medium, wherein the processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the backhaul billing method as described in any one of the above items.

[0109] The beneficial effects of the above technical solution disclosed in the present invention are as follows:

[0110] The backhaul billing method described in the embodiment of the present invention is adopted, and the first functional entity of the core network is used to trigger a billing data request for backhaul billing. The billing data request sent includes backhaul billing-related parameters to implement billing of satellite backhaul traffic, so as to solve the problem in related technologies that backhaul billing cannot be implemented when satellite backhaul is used. BRIEF DESCRIPTION OF THE DRAWINGS

[0111] FIG1 is a schematic diagram of a wireless communication system architecture according to an embodiment of the present disclosure;

[0112] FIG2 is a flow chart of a backhaul billing method according to one embodiment of the present disclosure;

[0113] FIG3 is a flow chart of obtaining a usage report of a satellite backhaul type using the method according to an embodiment of the present disclosure;

[0114] FIG4 is a flow chart of implementation mode 1 of the backhaul billing method in an embodiment of the present disclosure;

[0115] FIG5 is a flow chart of a second embodiment of the backhaul billing method according to an embodiment of the present disclosure;

[0116] FIG6 is a flow chart of implementation method 3 of the backhaul billing method in an embodiment of the present disclosure;

[0117] FIG7 is a flow chart of a fourth embodiment of the backhaul billing method according to an embodiment of the present disclosure;

[0118] FIG8 is a flow chart of a fifth embodiment of the backhaul billing method according to an embodiment of the present disclosure;

[0119] FIG9 is a flow chart of a backhaul billing method according to another embodiment of the present disclosure;

[0120] FIG10 is a schematic diagram of the structure of a network device according to one embodiment of the present disclosure;

[0121] FIG11 is a schematic structural diagram of a network device according to another embodiment of the present disclosure;

[0122] FIG12 is a schematic structural diagram of a backhaul billing device according to one embodiment of the present disclosure;

[0123] FIG13 is a schematic structural diagram of a backhaul billing device according to another embodiment of the present disclosure. DETAILED DESCRIPTION

[0124] The following will be combined with the accompanying drawings in the embodiments of the present disclosure to clearly and completely describe the technical solutions in the embodiments of the present disclosure. Obviously, the embodiments described are only part of the embodiments of the present disclosure and not all of the embodiments. Based on the embodiments of the present disclosure, all other embodiments obtained by ordinary technicians in this field without making any creative efforts shall fall within the scope of protection of the present disclosure.

[0125] In the embodiments of the present disclosure, the term "and / or" describes the association relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally indicates that the associated objects are in an "or" relationship.

[0126] In the embodiments of the present disclosure, the term "plurality" refers to two or more than two, and other quantifiers are similar thereto.

[0127] The technical solution provided by the embodiment of the present disclosure can be applicable to a variety of systems, especially 5G systems. For example, the applicable system can be a global system of mobile communication (GSM) system, a code division multiple access (CDMA) system, a wideband code division multiple access (WCDMA) general packet radio service (GPRS) system, a long term evolution (LTE) system, a LTE frequency division duplex (FDD) system, a LTE time division duplex (TDD) system, an advanced long term evolution (LTE-A) system, a universal mobile telecommunication system (UMTS), a world-wide interoperability for microwave access (WiMAX) system, a 5G new air interface (NR) system, etc. These various systems include terminal equipment and network equipment. The system may also include a core network part, such as an evolved packet system (EPS), a 5G system (5GS), etc.

[0128] Figure 1 shows a block diagram of a wireless communication system applicable to embodiments of the present disclosure. The wireless communication system includes a terminal device (also referred to as a User Equipment (UE)) 1, a base station 2, a satellite 3, and a core network 4. The core network 4 may include multiple functional entities. Satellite 3 is deployed between base station 2 and core network 4 to facilitate information exchange between the two.

[0129] Optionally, the backhaul strategy of satellite 3 includes but is not limited to only one or more of geostationary satellite Orbit (GEO), medium Earth orbit satellite (MEO), low Earth orbit satellite (LEO), other satellites OTHERSAT, dynamic geostationary satellite (DYNAMIC_GEO), dynamic medium Earth orbit satellite (DYNAMIC_MEO), dynamic low Earth orbit satellite (DYNAMIC_LEO) and dynamic other satellites (DYNAMIC_OTHERSAT).

[0130] In order to realize backhaul billing under the satellite backhaul architecture, the embodiment of the present disclosure provides a backhaul billing method, which uses the first functional entity of the core network to trigger a billing data request for backhaul billing. The billing data request sent includes backhaul billing-related parameters to realize billing of satellite backhaul traffic, so as to solve the problem in related technologies that backhaul billing under the satellite backhaul architecture cannot be realized.

[0131] The backhaul charging method described in one embodiment of the present disclosure is executed by a first functional entity, as shown in FIG2 , and includes:

[0132] S210: Send a charging data request to the second functional entity, where the charging data request is used for backhaul charging; wherein the charging data request includes backhaul charging-related parameters.

[0133] In the embodiment of the present disclosure, optionally, the first functional entity includes but is not limited to a session management function (SMF) entity that can only include a core network, and the second functional entity includes but is not limited to a charging function (CHF) entity that can only include a core network.

[0134] The billing data request described in this embodiment is adopted, and the characteristic that SMF can obtain the satellite backhaul type from AMF is utilized. The SMF entity triggers the backhaul billing and sends a billing data request for backhaul billing to the CHF entity.

[0135] Optionally, during the process of establishing, modifying and / or releasing the first session of the terminal, the first functional entity (SMF entity) sends a charging data request for backhaul charging to the second functional entity (CHF entity).

[0136] Optionally, during the first session establishment process of the terminal, in step S210, the charging data request sent by the first functional entity to the second functional entity is an initial request for backhaul charging; wherein the backhaul charging-related parameters include one or more of the following parameters:

[0137] Satellite backhaul type;

[0138] Satellite ID of the preset type of satellite;

[0139] Onboard Data Network Access Identifier DNAI.

[0140] It should be noted that in the embodiments of the present disclosure, the satellite backhaul types mentioned include but are not limited to only one or more of GEO (Geostationary Orbit), MEO (Medium Earth Orbit), LEO (Low Earth Orbit), OTHERSAT, YNAMIC_GEO, DYNAMIC_MEO, DYNAMIC_LEO and DYNAMIC_OTHERSAT.

[0141] Optionally, the first session is a protocol data unit (PDU) session.

[0142] Among them, after the terminal sends a PDU session establishment request to the fifth functional entity (including but not limited to only the Access and Mobility Management Function (AMF) entity), if the AMF entity determines based on the configuration that the base station serving the terminal uses satellite backhaul, the AMF entity includes the satellite backhaul type when sending the PDU session request message to the SMF entity, that is, the satellite backhaul type of the base station serving the terminal for satellite backhaul of the first session (PDU session).

[0143] Optionally, when the backhaul billing related parameter includes a satellite identifier of a preset type of satellite, the preset type of satellite includes and is limited to only include a GEO satellite.

[0144] Among them, after the AMF entity obtains the PDU session establishment request sent by the terminal, if the AMF entity determines that the base station serving the terminal uses GEO satellite backhaul, the AMF entity includes the satellite identifier of the GEO satellite when sending the PDU session request message to the SMF entity.

[0145] In this way, the SMF entity can obtain the satellite return type and the satellite identifier of the preset type satellite (GEO satellite) from the AMF entity, and when sending a billing data request to the CHF entity, it can include the satellite return type and / or the satellite identifier of the preset type satellite (GEO satellite).

[0146] Optionally, the satellite identifier of the GEO satellite may be configured by an Operation Administration and Maintenance (OAM) entity.

[0147] In the embodiment of the present disclosure, optionally, the SMF entity can configure the mapping relationship between the on-board data network access identifier (DNAI) and the on-board UPF through the operator (such as a 1:1 mapping relationship), and the SMF selects the on-board user plane function (UPF) entity based on the obtained on-board data network access identifier (DNAI). It should be noted that when the billing data request is an initial request for backhaul billing, the backhaul billing-related parameters may include one or more of the following parameters in addition to one or more of the above parameters:

[0148] Billing ID;

[0149] PDU session identifier;

[0150] Quality of Service (QoS) monitoring reports.

[0151] Using this implementation, during the establishment of the first session (PDU session), the SMF entity creates a billing identifier for the first session (PDU session), and based on the backhaul billing trigger condition, sends a billing data request to the CHF entity for the initial request for backhaul billing to authorize the contracted user to start the PDU session.

[0152] In the embodiment of the present disclosure, the backhaul billing triggering condition is an event for triggering billing of a PDU session for satellite backhaul.

[0153] In the embodiment of the present disclosure, optionally, in step S210, sending a charging data request to the second functional entity includes:

[0154] When the backhaul charging trigger condition is obtained, a charging data request is sent to the second functional entity.

[0155] In one embodiment, optionally, the method further comprises:

[0156] During the first session establishment process, the backhaul charging trigger condition is determined to be obtained when at least one of the following events is obtained:

[0157] Get the return satellite type;

[0158] Obtain satellite identification;

[0159] Based on the mapping relationship between the GEO satellite identification ID and DNAI configured locally in the SMF, the on-board DNAI is selected.

[0160] In the embodiment of the present disclosure, the UPF entity corresponding to the first session (PDU session) can be a ground device or an on-board device. After the SMF entity determines that the satellite backhaul type is GEO and determines the satellite ID of GEO, the on-board UPF can be selected. Therefore, after obtaining the backhaul satellite type, satellite identifier and / or the mapping relationship between the GEO satellite identifier ID and DNAI configured locally by the first functional entity, the SMF entity selects one of the on-board DNAIs, which can be used as a trigger condition for sending a billing data request for backhaul billing.

[0161] Optionally, in step S210, the charging data request sent by the first functional entity to the second functional entity is a request for updating charging data for backhaul charging; wherein the backhaul charging-related parameters include one or more of the following parameters:

[0162] Satellite returns type change information;

[0163] Current satellite backhaul type;

[0164] Satellite ID of the preset type of satellite;

[0165] Onboard Data Network Access Identifier DNAI;

[0166] Satellite backhaul type usage report.

[0167] In the embodiment of the present disclosure, optionally, during the modification process of the first session (PDU session), the backhaul charging trigger condition is determined to be obtained when at least one of the following events is obtained:

[0168] Get usage reports for satellite backhaul types;

[0169] Obtain information on changes in satellite return types;

[0170] Get the satellite ID of the preset type of satellite;

[0171] Based on the mapping relationship between the GEO satellite identification ID and DNAI configured locally by the first functional entity, the on-board DNAI is selected.

[0172] In this implementation, during the modification process of the first session (PDU session), if the above-mentioned trigger condition is received or the quota requirement is met, the SMF entity can send a billing data update request to the CHF entity. The billing data request includes the above-mentioned parameters and requests quota management for each UPF entity.

[0173] In addition, the usage report can be triggered by a backhaul billing event, that is, when a satellite backhaul type usage report is obtained through the UPF entity, the backhaul billing trigger condition is determined and a billing data request is sent to the second functional entity.

[0174] In another embodiment, when the satellite backhaul type changes, the UPF entity selected by the SMF entity may also change, so the N4 session modification process will occur. Based on this, during the modification process of the first session (PDU session), if the change information of the satellite backhaul type is obtained, the satellite identifier of the preset type satellite is obtained, and / or the mapping relationship between the GEO satellite identifier ID and DNAI configured locally by the first functional entity is obtained, the on-board DNAI is selected, then it can be determined that the satellite backhaul type has changed, the backhaul billing trigger condition is determined, and a billing data request is sent to the second functional entity.

[0175] In this implementation of the embodiment of the present disclosure, during the modification process of the first session (PDU session), when the SMF entity sends a billing data request to the CHF entity, the backhaul billing-related parameters may include, in addition to one or more items of satellite backhaul type change information, current satellite backhaul type, satellite identifier of preset type satellite, onboard data network access identifier DNAI and satellite backhaul type usage report, user location change information, service node change information, changes in the terminal in the current reporting area and QoS monitoring report.

[0176] In the disclosed embodiment, the satellite backhaul type usage report is used to record traffic usage via the satellite backhaul type. For example, when the billing data request is a request to update billing data for backhaul billing, the satellite backhaul type usage report in the backhaul billing-related parameters is used to record the number of QoS flow identifiers (QFIs) transmitted via the GEO satellite (current satellite backhaul type) for the corresponding PDU session.

[0177] In the embodiment of the present disclosure, during the release process of the first session (PDU session), in step S210, the charging data request sent by the SMF entity to the CHF entity is a request for termination of the charging data for backhaul charging. The backhaul charging related parameters in the charging data request include:

[0178] Satellite backhaul type usage report.

[0179] Optionally, the usage report includes:

[0180] A first usage report is used to record the satellite backhaul traffic using the current satellite backhaul type; or

[0181] The second usage report is used to record the satellite backhaul traffic using the current satellite backhaul type and the satellite backhaul traffic using the historical satellite backhaul type.

[0182] Specifically, the backhaul billing-related parameters may include a first usage report, which only records the traffic usage of the current satellite backhaul type. The traffic usage may be the number of QFIs returned through the current satellite backhaul type; for example, when the current satellite backhaul type is GEO, the backhaul billing-related parameters include a first usage report, which records that the number of QFIs returned through GEO is 2.

[0183] In another embodiment, the backhaul billing-related parameters may include a second usage report that records traffic usage for the current satellite backhaul type and traffic usage for the historical satellite backhaul types. For example, when the current satellite backhaul type includes GEO and the historical satellite backhaul type includes LEO, the backhaul billing-related parameters include the second usage report, recording the number of QFIs backhauled via GEO as 2 and the number of QFIs backhauled via LEO as 5.

[0184] In another embodiment of the present disclosure, as shown in FIG3 , the method further includes:

[0185] S310, the first function entity (SMF entity) sends a third request message to the UPF entity, where the third request message is used to request the UPF entity to start counting the traffic backhauled by the satellite for the first session;

[0186] Optionally, the SMF entity sends a third request message to the UPF entity, requesting the UPF entity to start counting the number of traffic types returned through a certain satellite in each PDU session (first session) or each QFI.

[0187] S320, obtaining a second response message fed back by the UPF entity according to the third request message; wherein, the second response message includes a usage report of the satellite backhaul type obtained after counting the traffic in the first session / or each QFI.

[0188] In this embodiment, optionally, in step S310, the third request message is used to request the UPF entity to start counting the traffic usage for each PDU session (first session) and / or each QFI through each satellite backhaul type; thus, in step S320, the second response message fed back by the UPF entity obtained by the SMF entity includes the traffic usage for counting the traffic for each PDU session and / or each QFI through each satellite backhaul type.

[0189] For example, the usage report included in the second response message may include the content shown in Table 1 below:

[0190] Table 1

[0191] The usage report indicates that for the first session, the number of QFIs returned via the satellite backhaul type GEO is 2. After the satellite backhaul type is switched (executing N4 session modification), the number of QFIs returned via the satellite backhaul type LEO is 5.

[0192] It should be noted that the above content and form of the satellite backhaul type usage report are only examples and are not limited to the above structural form.

[0193] In addition, the execution order of each step in the method described in the embodiment of the present disclosure is not limited to the above description, and the order of each step can be appropriately changed or executed simultaneously.

[0194] The specific implementation process of the backhaul billing method described in the embodiment of the present disclosure is described in detail below in conjunction with specific implementation methods.

[0195] Implementation Method 1

[0196] In the first embodiment, as shown in FIG4 , based on the PDU session establishment and modification process of the terminal, the specific implementation of the backhaul billing method according to the embodiment of the present disclosure includes the following steps:

[0197] S401, the terminal UE sends a PDU session establishment request to the AMF entity;

[0198] S402, the AMF entity sends a PDU session establishment request or a PDU session change request to the SMF entity; wherein, if the AMF entity determines based on the configuration that the base station gNB of the terminal uses satellite backhaul, the PDU session establishment request or PDU session change request sent includes the satellite backhaul type; in addition, if the AMF entity determines that the gNB serving the UE uses GEO satellite backhaul, the AMF entity carries the satellite identifier of the GEO satellite in the PDU session establishment request or PDU session change request sent to the SMF entity;

[0199] S403, the SMF entity obtains the contract data confirmation from the Unified Data Management (UDM) entity;

[0200] S404, the SMF entity sends a PDU session establishment response message to the AMF entity; optionally, the PDU session establishment response message includes an SM context identifier;

[0201] S405, the UE and the core network perform a secondary confirmation of the PDU session authorization;

[0202] S406, executing PCF entity selection, session management policy establishment and modification, etc.;

[0203] S407, the SMF entity selects SSCmode and one or more UPF entities for the PDU session; optionally, the SMF entity can select the on-board UPF entity based on the GEO satellite identifier obtained from the AMF entity and the DNAI value configured by the operator (1:1 mapping relationship);

[0204] S408, the SMF entity executes the session management policy adjustment program and reports PDU session related events to the PCF entity;

[0205] S409, the SMF entity creates a charging identifier Charging Id for the PDU session and sends a charging data request to the CHF entity for returning the initial request for charging to authorize the subscriber to start the PDU session, which is triggered by the PDU session charging event;

[0206] Specifically, during the PDU session establishment process, a backhaul trigger condition is determined based on at least one of the following events, triggering the sending of a charging data request to the CHF entity:

[0207] Get the return satellite type;

[0208] Obtain satellite identification;

[0209] Based on the mapping relationship between the GEO satellite identification ID and DNAI configured locally by the first functional entity, the on-board DNAI is selected.

[0210] In one embodiment, when the SMF entity sends a charging data request for an initial request for backhaul charging to the CHF entity, the backhaul charging related parameters in the charging data request may include the parameters in Table 2 below:

[0211] Table 2

[0212] S410, the CHF entity opens the corresponding call detail record (CDR) for the corresponding PDU;

[0213] S411, the CHF entity sends a charging data response message of the charging data request to the SMF entity;

[0214] S412, the N4 session establishment or update process is performed between the SMF entity and the UPF entity;

[0215] S413, information exchange between the SMF entity and the AMF entity;

[0216] S414: The UE, AMF entity, and base station perform a PDU session establishment and acceptance interaction.

[0217] S415, the AMF entity sends a PDU session update request to the SMF entity;

[0218] S416, N4 session modification is performed between the SMF entity and the UPF entity;

[0219] S417, the SMF entity sends a charging data request to the CHF entity, where the charging data request is for updating the charging data for backhaul charging;

[0220] During the PDU session modification process, when at least one of the following events is obtained, it is determined that a backhaul billing trigger condition is obtained, and a billing data request is sent to the CHF entity according to the backhaul billing trigger condition:

[0221] Get usage reports for satellite backhaul types;

[0222] Obtain information on changes in satellite return types;

[0223] Get the satellite ID of the preset type of satellite;

[0224] Based on the mapping relationship between the GEO satellite identification ID and DNAI configured locally by the first functional entity, the on-board DNAI is selected.

[0225] Specifically, during the PDU session modification process, if the service start data flow of the first session requires the quota of the CHF entity, the SMF entity can send a billing data request to the CHF entity. The billing data request includes the parameters in Table 2, requesting quota management for each UPF entity.

[0226] Based on this, the usage report can be triggered by a backhaul billing event, that is, when a satellite backhaul type usage report is obtained through the UPF entity, the backhaul billing trigger condition is determined and a billing data request is sent to the second functional entity.

[0227] In another embodiment, when the satellite backhaul type changes, the UPF entity selected by the SMF entity may also change, so the N4 session modification process will occur. Based on this, during the modification process of the first session (PDU session), if the change information of the satellite backhaul type is obtained, the satellite identifier of the preset type satellite is obtained, and / or the mapping relationship between the GEO satellite identifier ID and DNAI configured locally by the first functional entity is obtained, the on-board DNAI is selected, then it can be determined that the satellite backhaul type has changed, the backhaul billing trigger condition is determined, and a billing data request is sent to the second functional entity.

[0228] In one embodiment, when the SMF entity sends a charging data request for updating charging data for backhaul charging to the CHF entity, the backhaul charging related parameters in the charging data request may include the parameters in Table 3 below:

[0229] Table 3

[0230] Optionally, the satellite backhaul type usage report is used to record the traffic of the PDU backhauled via the current satellite backhaul type. For example, when the current satellite backhaul type is GEO, the satellite backhaul type usage report may record the number of QFIs backhauled via GEO as 2.

[0231] Based on the above PDU session modification process, the satellite backhaul type of the PDU session can be switched to LEO.

[0232] S418, the CHF entity updates the CDR according to the charging data request sent by the SMF entity;

[0233] S419, the CHF entity sends a charging data response message (first response message) to the SMF entity, where the first response message includes a usage report of the satellite backhaul type.

[0234] Among them, the usage report can be a first usage report, which is only used to record the satellite return traffic of the current satellite return type; or it can also be a second usage report, which is used to record the satellite return traffic using the current satellite return type and the satellite return traffic using the historical satellite return type.

[0235] S420, the SMF entity sends a PDU session update response message to the AMF entity;

[0236] S421, optionally, the SMF entity sends an SM context status notification message to the AMF entity;

[0237] S422. Optionally, when the PDU session type is IPv6, the SMF entity sends the IPv6 address configuration to the terminal.

[0238] It should be noted that the above-mentioned PDU session establishment and modification process is only used to illustrate the implementation process of backhaul billing during the PDU session establishment and modification process using the embodiment of the present disclosure. The establishment and modification process involved is not limited to only including the above-mentioned implementation steps.

[0239] Implementation Method 2

[0240] In the second embodiment, when backhauling via satellite, the AMF entity initiates a PDU session modification because it confirms based on the OAM configuration that the base station serving the UE is backhauled via satellite, and confirms the satellite backhaul type, or obtains the GEO satellite ID. In this case, billing can be triggered by the SMF.

[0241] As shown in FIG5 , when the PDU session modification process is performed using this implementation, the implementation process of the backhaul billing method according to the embodiment of the present disclosure includes the following steps:

[0242] S501: The UE and the core network execute a PDU session change request process. This process is not an improvement of the present disclosure and will not be described in detail here.

[0243] S502, the SMF entity and the PCF entity execute the SM policy management adjustment procedure;

[0244] S503, N4 session establishment / modification request and response is executed between the SMF entity and the PCF entity;

[0245] S504, the SMF entity obtains the PDU session modification of the AMF entity, and the SMF entity sends a billing data request to the CHF entity. The billing data request is for billing data update for backhaul billing;

[0246] Similar to the first embodiment, in the second embodiment, during the PDU session modification process, when at least one of the following events is obtained, it is determined that a backhaul billing trigger condition is obtained, and a billing data request is sent to the CHF entity according to the backhaul billing trigger condition:

[0247] Get usage reports for satellite backhaul types;

[0248] Obtain information on changes in satellite return types;

[0249] Get the satellite ID of the preset type of satellite;

[0250] Based on the mapping relationship between the GEO satellite identification ID and DNAI configured locally by the first functional entity, the on-board DNAI is selected.

[0251] In addition, in this second embodiment, as in the first embodiment, when the SMF entity sends a billing data request for updating billing data for backhaul billing to the CHF entity, the backhaul billing related parameters in the billing data request may include the parameters in Table 3, which are not repeated here.

[0252] S505, the CHF entity updates the CDR according to the charging data request sent by the SMF entity;

[0253] S506, the CHF entity sends a charging data response message (first response message) to the SMF entity, where the first response message includes a usage report of the satellite backhaul type.

[0254] Among them, the usage report can be a first usage report, which is only used to record the satellite backhaul traffic of the current satellite backhaul type; or it can also be a second usage report, which is used to record the satellite backhaul traffic using the current satellite backhaul type and the satellite backhaul traffic using the historical satellite backhaul type.

[0255] S507: The PDU session modification process continues between the UE and the core network.

[0256] Implementation Method 3

[0257] This third embodiment is used to illustrate the process of releasing the billing data that needs to be reported for a PDU session when backhauling via a satellite.

[0258] 6 , based on the terminal's PDU session release process, a specific implementation of the backhaul billing method according to an embodiment of the present disclosure includes the following steps:

[0259] S601, a PDU session request process is performed between the UE and the core network;

[0260] S602, the SMF entity and the UPF entity execute the request and response for N4 session release;

[0261] S603, the SMF entity sends a billing data request to the CHF entity, and the billing data for backhaul billing is terminated; optionally, the backhaul billing related parameters in the backhaul billing data request include a usage report of the satellite backhaul type.

[0262] Optionally, the usage report includes:

[0263] A first usage report is used to record the satellite backhaul traffic using the current satellite backhaul type; or

[0264] The second usage report is used to record the satellite backhaul traffic using the current satellite backhaul type and the satellite backhaul traffic using the historical satellite backhaul type.

[0265] Specifically, the backhaul billing-related parameters may include a first usage report, which only records the traffic usage of the current satellite backhaul type. The traffic usage may be the number of QFIs returned through the current satellite backhaul type; for example, when the current satellite backhaul type is GEO, the backhaul billing-related parameters include a first usage report, which records that the number of QFIs returned through GEO is 2.

[0266] In another embodiment, the backhaul billing-related parameters may include a second usage report that records traffic usage for the current satellite backhaul type and traffic usage for the historical satellite backhaul types. For example, when the current satellite backhaul type includes GEO and the historical satellite backhaul type includes LEO, the backhaul billing-related parameters include the second usage report, recording the number of QFIs backhauled via GEO as 2 and the number of QFIs backhauled via LEO as 5.

[0267] S604, the CHF entity closes the CDR for this PDU session;

[0268] S605, the CHF entity sends a charging data response message to the SMF entity to indicate the termination of the charging data;

[0269] S606: Continue to execute PDU session release.

[0270] It should be noted that the above-mentioned PDU session release process is only used to illustrate the implementation process of releasing the billing data that needs to be reported when the PDU session is released using the method of the embodiment of the present disclosure. Each step of the implementation process is not described in detail here.

[0271] Implementation Method 4

[0272] The backhaul billing method described in the embodiments of this disclosure can be applied not only to non-roaming scenarios but also to home-routed roaming scenarios. In the fourth embodiment, the establishment, modification, and release of the PDU session triggered by the terminal in the visited network can trigger billing by the SMF entity of the visited network.

[0273] 7 , the specific implementation process of the fourth embodiment includes the following steps:

[0274] S701, the terminal sends a PDU session establishment request to the AMF entity in the access network (i.e., roaming network); the AMF entity selects the SMF entity in the terminal access network and the SMF entity in the local network, such as the SMF entity in the access network is marked as V-SMF and the SMF entity in the local network is marked as H-SMF;

[0275] S702, the AMF entity sends a PDU session establishment request to the V-SMF. The PDU session establishment request may include the satellite backhaul type and GEO satellite identifier determined by the AMF entity.

[0276] S703, the terminal UE indicates that as a roamer, the V-SMF selects a CHF entity in the visited network, such as marked as V-CHF;

[0277] S704: The V-SMF sends a charging data request to the V-CHF for the initial request for backhaul charging, and indicates "bound as roamer". Optionally, the charging event for the PDU session backhauled by the satellite can be placed in the roaming charging profile.

[0278] Optionally, the backhaul billing related parameters in the billing data request may be as shown in Table 2, including one or more items of billing identifier, PDU session ID, satellite backhaul type, GEO satellite ID, onboard DNAI and QoS monitoring report.

[0279] S705, the CHF entity opens the corresponding CDR for the corresponding PDU;

[0280] S706, the CHF entity sends a charging data response message of the charging data request to the SMF entity;

[0281] S707, V-SMF sends a PDU session response message to the AMF entity;

[0282] S708, N4 session establishment is performed between the V-UPF and the V-SMF;

[0283] S709, V-SMF sends a PDU session establishment request message to H-SMF, including the roaming charging profile, which may include the satellite backhaul type;

[0284] S710, H-SMF performs registration and subscription of PDU session;

[0285] S711, performing PDU session authorization between the terminal and the core network of the local network;

[0286] S712, the core network performs session management, policy establishment and modification, etc.

[0287] S713, H-SMF for CHF selection;

[0288] S714: The H-SMF sends a charging data request to the H-CHF to transmit the initial charging request, indicating that the terminal is an "outbound roamer" and may include a roaming charging profile.

[0289] S715, H-CHF opens the CDR corresponding to the "outbound roamer" for the corresponding PDU;

[0290] S716, H-CHF sends a charging data response message to H-SMF;

[0291] S717, N4 session is established between H-SMF and H-UPF;

[0292] S718, H-SMF starts counting each QFI;

[0293] S719, H-SMF sends a PDU session establishment response message to V-SMF; optionally, it includes a roaming charging profile;

[0294] S720, the V-SMF sends a charging data request to the V-CHF. The charging data request is for updating the charging data used for backhaul charging. Optionally, the charging data request may include a roaming charging profile for recording the charging information obtained by the H-SMF.

[0295] S721, the V-CHF entity updates the CDR according to the charging data request sent by the V-SMF entity;

[0296] S722, the V-CHF entity sends a charging data response message to the V-SMF entity;

[0297] S723, N1N2 session exchange is performed between V-SMF and AMF;

[0298] S724: The terminal, base station and AMF entity perform PDU session establishment and acceptance interaction;

[0299] S725, AMF sends a PDU session update request to the V-SMF entity;

[0300] S726, N4 session modification is performed between the V-SMF entity and the V-UPF entity;

[0301] S727, the V-SMF entity sends a billing data request to the V-CHF entity. The billing data request is for updating the billing data for backhaul billing. The triggering conditions for sending the billing data request are the same as the backhaul billing triggering conditions in the PDU session modification in Implementation Method 1, and are not repeated here. In addition, the backhaul billing-related parameters in the billing data request may include the references in Table 3, which are not repeated here.

[0302] S728, the V-CHF entity updates the CDR according to the charging data request sent by the V-SMF entity;

[0303] S729, the V-CHF entity sends a charging data response message (first response message) to the V-SMF entity. The first response message includes a usage report of the satellite backhaul type.

[0304] S730, the V-SMF entity sends a PDU session update request to the H-SMF entity;

[0305] S731, the H-SMF entity sends a charging data request to the H-CHF entity;

[0306] S732, the H-CHF entity updates the CDR;

[0307] S733, the H-CHF entity sends a charging data response message to the H-SMF entity.

[0308] It should be noted that the PDU session establishment and update process in the above-mentioned roaming scenario is only used to illustrate the backhaul billing implementation process when the PDU session in the roaming scenario is established and updated using the method described in the embodiment of the present disclosure. The PDU session establishment and update process in the roaming scenario is not described in detail here for each step of the implementation process.

[0309] According to the PDU session establishment and update process of the above-mentioned roaming scenario, in the embodiment of the present disclosure, the first functional entity can be the above-mentioned V-SMF or H-SMF, and the backhaul billing process performed is applicable to the backhaul billing method of the present disclosure.

[0310] According to the above, when the first functional entity is a V-SMF, and when the network where the first functional entity is located is an access network of the terminal, after obtaining the first response message sent by the second functional entity, the method further includes:

[0311] A first request message is sent to a third function entity (H-SMF entity) of the local network of the terminal, wherein the first request message includes a usage report of a satellite backhaul type.

[0312] Among them, the H-SMF entity can send a billing data request to the H-CHF entity of the terminal's local network based on the usage report of the satellite backhaul type in the first request message sent by the V-SMF entity, and the billing data request includes a usage report for backhaul billing.

[0313] In another embodiment, when the first functional entity is an H-SMF and the network where the first functional entity is located is a local network of the terminal, the method further includes:

[0314] Obtaining a second request message sent by a fourth function entity (V-SMF entity) of an access network of the terminal; wherein the second request message includes a usage report of a satellite backhaul type;

[0315] According to the second request message, a charging data request is sent to the second functional entity; the backhaul charging related parameters in the charging data request include the usage report.

[0316] The method described in this embodiment is adopted, and the SMF entity is used to trigger the billing data request for backhaul billing. The billing data request sent includes backhaul billing-related parameters to implement billing of satellite backhaul traffic, so as to solve the problem in related technologies that backhaul billing cannot be implemented under the satellite backhaul architecture.

[0317] Implementation Method Five

[0318] This fifth embodiment is used to illustrate the entire process of implementing backhaul charging through SMF (or (Charging Trigger Function, CTF)) during the establishment, modification and release of the PDU session.

[0319] Specifically, as shown in FIG8 , the implementation process includes:

[0320] S801, SMF receives a PDU session establishment request; wherein the PDU session establishment request may include a satellite backhaul type;

[0321] S802, the SMF entity sends a charging data request to the CHF entity, which is used for the initial request of backhaul charging; wherein the backhaul charging parameters in the charging data request may include the parameters in Table 2, which are not described in detail here;

[0322] S803, CHF entity creates CDR;

[0323] S804, the CHF entity sends a charging data response message of the charging data request to the SMF entity;

[0324] S805: If the SMF entity obtains the satellite backhaul type, or obtains a change in the satellite backhaul type, it performs the N4 session establishment and modification process with the UPF entity, and requests a usage report on the satellite backhaul type from the UPF;

[0325] S806, UPF starts counting QFIs related to the satellite return type and monitors a reporting event;

[0326] S807, UPF / PSA UPF sends a satellite backhaul type usage report to SMF;

[0327] S808, the SMF entity sends a charging data request to the CHF entity. The charging data request is for updating the charging data for backhaul charging. The backhaul charging parameters in the charging data request may also include the parameters in Table 3, which are not described in detail here.

[0328] S809, the CHF entity updates the CDR according to the charging data request sent by the SMF entity;

[0329] S810, the CHF entity sends a charging data response message (a first response message) to the SMF entity, where the first response message includes a usage report of the satellite backhaul type;

[0330] S811, the SMF entity sends the granted quota to the UPF / PSA UPF in a response message of the usage report;

[0331] S812, UPF / PSA UPF reports the last satellite backhaul traffic usage report to SMF;

[0332] S813, the SMF entity sends a charging data request to the CHF entity for terminating backhaul charging; optionally, the charging data request includes a usage report of the satellite backhaul type;

[0333] S814, CHF entity closes CDR;

[0334] S815, the CHF entity sends a charging data response message to the SMF entity;

[0335] S816, the SMF entity sends a usage report response message to the UPF / PSA UPF.

[0336] One embodiment of the present disclosure further provides a backhaul charging method, as shown in FIG9 , which is performed by a second functional entity. The method includes:

[0337] S910: Obtain a charging data request sent by a first functional entity, where the charging data request is used for backhaul charging; wherein the charging data request includes backhaul charging-related parameters.

[0338] By adopting the backhaul billing method described in this embodiment, the first functional entity can send a billing data request to the second functional entity for backhaul billing, and use the backhaul billing-related parameters included in the sent billing data request to implement billing of satellite backhaul traffic, so as to solve the problem in related technologies that backhaul billing cannot be implemented under the satellite backhaul architecture.

[0339] Optionally, in the backhaul billing method, the billing data request is an initial request for backhaul billing; and the backhaul billing-related parameters include one or more of the following parameters:

[0340] Satellite backhaul type;

[0341] Satellite ID of the preset type of satellite;

[0342] Onboard Data Network Access Identifier DNAI.

[0343] Optionally, in the backhaul billing method, the billing data request is a request for updating billing data for backhaul billing; and the backhaul billing-related parameters include one or more of the following parameters:

[0344] Satellite returns type change information;

[0345] Current satellite backhaul type;

[0346] Satellite ID of the preset type of satellite;

[0347] Onboard Data Network Access Identifier DNAI;

[0348] Satellite backhaul type usage report.

[0349] Optionally, in the backhaul billing method, the billing data request is a request for termination of billing data for backhaul billing; and the backhaul billing-related parameters include:

[0350] Satellite backhaul type usage report.

[0351] Optionally, the backhaul billing method further includes:

[0352] A first response message is sent to the first functional entity; wherein the first response message includes a usage report of the satellite backhaul type.

[0353] Optionally, in the backhaul billing method, the usage report includes:

[0354] A first usage report is used to record the satellite backhaul traffic using the current satellite backhaul type; or

[0355] The second usage report is used to record the satellite backhaul traffic using the current satellite backhaul type and the satellite backhaul traffic using the historical satellite backhaul type.

[0356] The implementation process of the backhaul charging method described in the embodiment of the present disclosure applied to the second functional entity can refer to the implementation process applied to the first functional entity, and will not be repeated here.

[0357] One embodiment of the present disclosure further provides a network device, as shown in FIG10 , including a memory 1010 , a transceiver 1020 , and a processor 1030 :

[0358] The memory 1010 is used to store computer programs; the transceiver 1020 is used to send and receive data under the control of the processor; the processor 1030 is used to read the computer program in the memory and perform the following operations:

[0359] Sending a charging data request to the second functional entity, where the charging data request is used for backhaul charging; wherein the charging data request includes backhaul charging-related parameters.

[0360] Optionally, in the network device, the billing data request is an initial request for backhaul billing;

[0361] The backhaul billing related parameters include one or more of the following parameters:

[0362] Satellite backhaul type;

[0363] Satellite ID of the preset type of satellite;

[0364] Onboard Data Network Access Identifier DNAI.

[0365] Optionally, in the network device, the billing data request is a request for updating billing data for backhaul billing; and the backhaul billing-related parameters include one or more of the following parameters:

[0366] Satellite returns type change information;

[0367] Current satellite backhaul type;

[0368] Satellite ID of the preset type of satellite;

[0369] Onboard Data Network Access Identifier DNAI;

[0370] Satellite backhaul type usage report.

[0371] Optionally, in the network device, the billing data request is a request for termination of billing data for backhaul billing; wherein the backhaul billing-related parameters include:

[0372] Satellite backhaul type usage report.

[0373] Optionally, in the network device, the processor 1030 is further configured to:

[0374] Obtain a first response message sent by the second functional entity; wherein the first response message includes a usage report of the satellite backhaul type.

[0375] Optionally, in the network device, the usage report includes:

[0376] A first usage report is used to record the satellite backhaul traffic using the current satellite backhaul type; or

[0377] The second usage report is used to record the satellite backhaul traffic using the current satellite backhaul type and the satellite backhaul traffic using the historical satellite backhaul type.

[0378] Optionally, in the network device, the processor 1030 sending the charging data request to the second functional entity includes:

[0379] When the backhaul charging trigger condition is obtained, a charging data request is sent to the second functional entity.

[0380] Optionally, in the network device, the processor 1030 is further configured to:

[0381] During the first session establishment process, when at least one of the following events is obtained, it is determined that the backhaul charging trigger condition is obtained:

[0382] Get the return satellite type;

[0383] Obtain satellite identification;

[0384] Based on the mapping relationship between the GEO satellite identification ID and DNAI configured locally by the first functional entity, the on-board DNAI is selected.

[0385] Optionally, in the network device, the processor 1030 is further configured to:

[0386] During the first session modification process, the backhaul charging trigger condition is determined to be obtained when at least one of the following events is obtained:

[0387] Get usage reports for satellite backhaul types;

[0388] Obtain information on changes in satellite return types;

[0389] Get the satellite ID of the preset type of satellite;

[0390] Based on the mapping relationship between the GEO satellite identification ID and DNAI configured locally by the first functional entity, the on-board DNAI is selected.

[0391] Optionally, in the network device, when the network where the first functional entity is located is an access network of the terminal, after obtaining the first response message sent by the second functional entity, the processor 1030 is further configured to:

[0392] A first request message is sent to a third functional entity of the local network of the terminal, wherein the first request message includes a usage report of a satellite backhaul type.

[0393] Optionally, in the network device, when the network where the first functional entity is located is a local network of the terminal, the processor 1030 is further configured to:

[0394] Obtaining a second request message sent by a fourth functional entity of the access network of the terminal; wherein the second request message includes a usage report of a satellite backhaul type;

[0395] The processor 1030 sends a charging data request to the second functional entity according to the second request message; the backhaul charging related parameters in the charging data request include the usage report.

[0396] Optionally, in the network device, the processor 1030 is further configured to:

[0397] Sending a third request message to the UPF entity, where the third request message is used to request the UPF entity to start counting traffic backhauled by the satellite for the first session;

[0398] Obtain a second response message fed back by the UPF entity based on the third request message; wherein, the second response message includes a usage report of the satellite backhaul type obtained after performing the traffic counting on the first session.

[0399] In FIG10 , the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 1030 and various circuits of memory represented by memory 1010. 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 are therefore not further described herein. The bus interface provides an interface. The transceiver 1020 may be a plurality of components, i.e., a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, such as a wireless channel, a wired channel, an optical cable, and the like. The processor 1030 is responsible for managing the bus architecture and general processing, and the memory 1010 may store data used by the processor 1030 when performing operations.

[0400] The processor 1030 may 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 may also adopt a multi-core architecture.

[0401] One embodiment of the present disclosure further provides a network device, as shown in FIG11 , including a memory 1110 , a transceiver 1120 , and a processor 1130 :

[0402] The memory 1110 is used to store computer programs; the transceiver 1120 is used to send and receive data under the control of the processor; the processor 1130 is used to read the computer program in the memory and perform the following operations:

[0403] Obtain a charging data request sent by the first functional entity, where the charging data request is used for backhaul charging; wherein the charging data request includes backhaul charging-related parameters.

[0404] Optionally, in the network device, the billing data request is an initial request for backhaul billing; and the backhaul billing-related parameters include one or more of the following parameters:

[0405] Satellite backhaul type;

[0406] Satellite ID of the preset type of satellite;

[0407] Onboard Data Network Access Identifier DNAI.

[0408] Optionally, in the network device, the billing data request is a request for updating billing data for backhaul billing; and the backhaul billing-related parameters include one or more of the following parameters:

[0409] Satellite returns type change information;

[0410] Current satellite backhaul type;

[0411] Satellite ID of the preset type of satellite;

[0412] Onboard Data Network Access Identifier DNAI;

[0413] Satellite backhaul type usage report.

[0414] Optionally, in the network device, the billing data request is a request for termination of billing data for backhaul billing; wherein the backhaul billing-related parameters include:

[0415] Satellite backhaul type usage report.

[0416] Optionally, in the network device, the method further includes:

[0417] A first response message is sent to the first functional entity; wherein the first response message includes a usage report of the satellite backhaul type.

[0418] Optionally, in the network device, the usage report includes:

[0419] A first usage report is used to record the satellite backhaul traffic using the current satellite backhaul type; or

[0420] The second usage report is used to record the satellite backhaul traffic using the current satellite backhaul type and the satellite backhaul traffic using the historical satellite backhaul type.

[0421] In FIG11 , the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 1130 and various circuits of memory represented by memory 1110. 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 are therefore not further described herein. The bus interface provides an interface. The transceiver 1120 may be a plurality of components, i.e., a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, such as a wireless channel, a wired channel, an optical cable, and the like. The processor 1130 is responsible for managing the bus architecture and general processing, and the memory 1110 may store data used by the processor 1130 when performing operations.

[0422] The processor 1130 may 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 may also adopt a multi-core architecture.

[0423] One embodiment of the present disclosure further provides a backhaul billing device, which is applied to a first functional entity. As shown in FIG12 , the device includes:

[0424] The sending unit 1201 is configured to send a charging data request to the second functional entity, where the charging data request is used for backhaul charging; wherein the charging data request includes backhaul charging related parameters.

[0425] Optionally, in the backhaul billing apparatus, the billing data request is an initial request for backhaul billing;

[0426] The backhaul billing related parameters include one or more of the following parameters:

[0427] Satellite backhaul type;

[0428] Satellite ID of the preset type of satellite;

[0429] Onboard Data Network Access Identifier DNAI.

[0430] Optionally, in the backhaul billing device, the billing data request is a request for updating billing data for backhaul billing; and the backhaul billing-related parameters include one or more of the following parameters:

[0431] Satellite returns type change information;

[0432] Current satellite backhaul type;

[0433] Satellite ID of the preset type of satellite;

[0434] Onboard Data Network Access Identifier DNAI;

[0435] Satellite backhaul type usage report.

[0436] Optionally, in the backhaul billing device, the billing data request is a request for termination of billing data for backhaul billing; wherein the backhaul billing-related parameters include:

[0437] Satellite backhaul type usage report.

[0438] Optionally, the backhaul billing device further comprises:

[0439] The first message obtaining unit 1202 is configured to obtain a first response message sent by the second functional entity; wherein the first response message includes a usage report of a satellite backhaul type.

[0440] Optionally, in the backhaul billing device, the usage report includes:

[0441] A first usage report is used to record the satellite backhaul traffic using the current satellite backhaul type; or

[0442] The second usage report is used to record the satellite backhaul traffic using the current satellite backhaul type and the satellite backhaul traffic using the historical satellite backhaul type.

[0443] Optionally, in the backhaul billing device, the sending unit 1201 sends the billing data request to the second functional entity, including:

[0444] When the backhaul charging trigger condition is obtained, a charging data request is sent to the second functional entity.

[0445] Optionally, in the backhaul billing device, the sending unit 1201 is further configured to:

[0446] During the first session establishment process, when at least one of the following events is obtained, it is determined that the backhaul charging trigger condition is obtained:

[0447] Get the return satellite type;

[0448] Obtain satellite identification;

[0449] Based on the mapping relationship between the GEO satellite identification ID and DNAI configured locally by the first functional entity, the on-board DNAI is selected.

[0450] Optionally, in the backhaul billing device, the sending unit 1201 is further configured to:

[0451] During the first session modification process, the backhaul charging trigger condition is determined to be obtained when at least one of the following events is obtained:

[0452] Get usage reports for satellite backhaul types;

[0453] Obtain information on changes in satellite return types;

[0454] Get the satellite ID of the preset type of satellite;

[0455] Based on the mapping relationship between the GEO satellite identification ID and DNAI configured locally by the first functional entity, the on-board DNAI is selected.

[0456] Optionally, in the backhaul charging device, when the network where the first functional entity is located is the access network of the terminal, after obtaining the first response message sent by the second functional entity, the sending unit 1201 is further configured to:

[0457] A first request message is sent to a third functional entity of the local network of the terminal, wherein the first request message includes a usage report of a satellite backhaul type.

[0458] Optionally, in the backhaul billing device, when the network where the first functional entity is located is a local network of the terminal, the device further includes:

[0459] The second message obtaining unit 1203 is configured to obtain a second request message sent by a fourth functional entity of the access network of the terminal, wherein the second request message includes a usage report of a satellite backhaul type;

[0460] According to the second request message, a charging data request is sent to the second functional entity; the backhaul charging related parameters in the charging data request include the usage report.

[0461] Optionally, in the backhaul billing device, the sending unit 1201 is further configured to:

[0462] Sending a third request message to the UPF entity, where the third request message is used to request the UPF entity to start counting traffic backhauled by the satellite for the first session;

[0463] Obtain a second response message fed back by the UPF entity based on the third request message; wherein, the second response message includes a usage report of the satellite backhaul type obtained after performing the traffic counting on the first session.

[0464] One embodiment of the present disclosure further provides a backhaul billing device, which is applied to a second functional entity. As shown in FIG13 , the device includes:

[0465] The obtaining unit 1301 is configured to obtain a charging data request sent by a first functional entity, where the charging data request is used for backhaul charging; wherein the charging data request includes backhaul charging related parameters.

[0466] Optionally, in the backhaul billing device, the billing data request is an initial request for backhaul billing; and the backhaul billing-related parameters include one or more of the following parameters:

[0467] Satellite backhaul type;

[0468] Satellite ID of the preset type of satellite;

[0469] Onboard Data Network Access Identifier DNAI.

[0470] Optionally, in the backhaul billing device, the billing data request is a request for updating billing data for backhaul billing; and the backhaul billing-related parameters include one or more of the following parameters:

[0471] Satellite returns type change information;

[0472] Current satellite backhaul type;

[0473] Satellite ID of the preset type of satellite;

[0474] Onboard Data Network Access Identifier DNAI;

[0475] Satellite backhaul type usage report.

[0476] Optionally, in the backhaul billing device, the billing data request is a request for termination of billing data for backhaul billing; wherein the backhaul billing-related parameters include:

[0477] Satellite backhaul type usage report.

[0478] Optionally, the backhaul billing device further comprises:

[0479] The message sending unit 1302 is configured to send a first response message to the first functional entity; wherein the first response message includes a usage report of a satellite backhaul type.

[0480] Optionally, in the backhaul billing device, the usage report includes:

[0481] A first usage report is used to record the satellite backhaul traffic using the current satellite backhaul type; or

[0482] The second usage report is used to record the satellite backhaul traffic using the current satellite backhaul type and the satellite backhaul traffic using the historical satellite backhaul type.

[0483] It should be noted here that the above-mentioned device provided in the embodiment of the present disclosure can implement all the method steps implemented in the above-mentioned method embodiment and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as those in the method embodiment will not be described in detail here.

[0484] It should be noted that the division of units in the embodiments of the present disclosure is schematic and is merely a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of the present disclosure may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0485] If the integrated unit is implemented in the form of 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 the present disclosure is essentially or the part that contributes to the relevant technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present disclosure. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0486] An embodiment of the present disclosure further provides a processor-readable storage medium, wherein the processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the backhaul billing method as described in any one of the above items.

[0487] The processor-readable storage medium can be any available medium or data storage device that can be accessed by the processor, including but not limited to magnetic storage (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO)), optical storage (such as CDs, DVDs, BDs, HVDs, etc.), and semiconductor storage (such as ROMs, EPROMs, EEPROMs, non-volatile memories (NAND FLASH), solid-state drives (SSDs)), etc.

[0488] In addition, in the embodiments of the present disclosure, the English abbreviations mentioned can be referred to as shown in the following Table 4:

[0489] Table 4

[0490] Those skilled in the art will appreciate that the embodiments of the present disclosure may be provided as methods, systems, or computer program products. Therefore, the present disclosure may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, the present disclosure may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage and optical storage, etc.) containing computer-usable program code.

[0491] The present disclosure is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present disclosure. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0492] 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 specific manner, so that the instructions stored in the processor-readable memory produce a product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

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

[0494] Obviously, those skilled in the art may make various changes and modifications to the present disclosure without departing from the spirit and scope of the present disclosure. Thus, if these modifications and variations of the present disclosure fall within the scope of the claims of the present disclosure and their equivalents, the present disclosure is intended to include these modifications and variations.

Claims

1. A backhaul charging method, performed by a first functional entity, comprising: Sending a charging data request to the second functional entity, where the charging data request is used for backhaul charging; wherein the charging data request includes backhaul charging related parameters.

2. The backhaul billing method according to claim 1, wherein: The billing data request is an initial request for backhaul billing; The backhaul billing related parameters include one or more of the following parameters: Satellite backhaul type; Satellite ID of the preset type of satellite; On-board Data Network Access Identifier DNAI.

3. The backhaul billing method according to claim 1, wherein: The billing data request is a request for updating billing data for backhaul billing; wherein the backhaul billing related parameters include one or more of the following parameters: Satellite returns type change information; Current satellite backhaul type; Satellite ID of the preset type of satellite; Onboard Data Network Access Identifier DNAI; Satellite backhaul type usage report.

4. The backhaul billing method according to claim 1, wherein: The charging data request is a request for termination of charging data for backhaul charging; wherein the backhaul charging related parameters include: Satellite backhaul type usage report.

5. The backhaul billing method according to claim 1, wherein: The method further comprises: Obtain a first response message sent by the second functional entity; wherein the first response message includes a usage report of the satellite backhaul type.

6. The backhaul charging method according to claim 3, 4 or 5, wherein: The usage report includes: A first usage report for recording satellite backhaul traffic using the current satellite backhaul type; or The second usage report is used to record the satellite backhaul traffic using the current satellite backhaul type and the satellite backhaul traffic using the historical satellite backhaul type.

7. The backhaul billing method according to claim 1, wherein: Sending a charging data request to the second functional entity includes: When the backhaul charging trigger condition is obtained, a charging data request is sent to the second functional entity.

8. The backhaul billing method according to claim 7, wherein: The method further comprises: During the first session establishment process, when at least one of the following events is obtained, it is determined that the backhaul charging trigger condition is obtained: Get the type of the backhaul satellite; Get satellite identification; Based on the mapping relationship between the ground synchronous orbit GEO satellite identification ID and DNAI configured locally by the first functional entity, the on-board DNAI is selected.

9. The backhaul billing method according to claim 7, wherein: The method further comprises: In the first session modification process, when at least one of the following events is obtained, it is determined that the backhaul charging trigger condition is obtained: Get usage report of satellite backhaul type; Obtain information about changes in satellite return types; Get the satellite ID of the preset type of satellite; Based on the mapping relationship between the GEO satellite identification ID and DNAI configured locally by the first functional entity, select the on-board DNAI.

10. The backhaul billing method according to claim 5, wherein: In a case where the network where the first functional entity is located is an access network of the terminal, after obtaining the first response message sent by the second functional entity, the method further includes: A first request message is sent to a third functional entity of the local network of the terminal, wherein the first request message includes a usage report of a satellite backhaul type.

11. The backhaul billing method according to claim 1, wherein: When the network where the first functional entity is located is a local network of the terminal, the method further includes: Obtaining a second request message sent by a fourth functional entity of the access network of the terminal; wherein the second request message includes a usage report of a satellite backhaul type; According to the second request message, a charging data request is sent to the second functional entity; and the backhaul charging related parameters in the charging data request include the usage report.

12. The backhaul billing method according to claim 1, wherein: The method further comprises: Sending a third request message to the UPF entity, where the third request message is used to request the UPF entity to start counting the traffic backhauled by the satellite for the first session; Obtain a second response message fed back by the UPF entity based on the third request message; wherein the second response message includes a usage report of the satellite backhaul type obtained after performing the traffic counting on the first session.

13. A backhaul charging method, performed by a second functional entity, the method comprising: A charging data request sent by a first functional entity is obtained, where the charging data request is used for backhaul billing; wherein the charging data request includes backhaul billing related parameters.

14. The backhaul charging method according to claim 13, wherein: The charging data request is an initial request for backhaul charging; wherein the backhaul charging related parameters include one or more of the following parameters: Satellite backhaul type; Satellite ID of the preset type of satellite; On-board Data Network Access Identifier DNAI.

15. The backhaul charging method according to claim 13, wherein: The billing data request is a request for updating billing data for backhaul billing; wherein the backhaul billing related parameters include one or more of the following parameters: Satellite returns type change information; Current satellite backhaul type; Satellite ID of the preset type of satellite; Onboard Data Network Access Identifier DNAI; Satellite backhaul type usage report.

16. The backhaul charging method according to claim 13, wherein: The charging data request is a request for termination of charging data for backhaul charging; wherein the backhaul charging related parameters include: Satellite backhaul type usage report.

17. The backhaul charging method according to claim 13, wherein: The method further comprises: A first response message is sent to the first functional entity; wherein the first response message includes a usage report of a satellite backhaul type.

18. The backhaul charging method according to claim 15, 16 or 17, wherein: The usage report includes: A first usage report for recording satellite backhaul traffic using the current satellite backhaul type; or The second usage report is used to record the satellite backhaul traffic using the current satellite backhaul type and the satellite backhaul traffic using the historical satellite backhaul type.

19. A network device comprising a memory, a transceiver, and a processor: A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: Sending a charging data request to the second functional entity, wherein the charging data request is used for backhaul charging; wherein, The billing data request includes return billing related parameters.

20. The network device according to claim 19, wherein: The billing data request is an initial request for backhaul billing; The backhaul billing related parameters include one or more of the following parameters: Satellite backhaul type; Satellite ID of the preset type of satellite; On-board Data Network Access Identifier DNAI.

21. The network device according to claim 19, wherein: The billing data request is a request for updating billing data for backhaul billing; wherein the backhaul billing related parameters include one or more of the following parameters: Satellite returns type change information; Current satellite backhaul type; Satellite ID of the preset type of satellite; Onboard Data Network Access Identifier DNAI; Satellite backhaul type usage report.

22. The network device according to claim 19, wherein: The charging data request is a request for termination of charging data for backhaul charging; wherein the backhaul charging related parameters include: Satellite backhaul type usage report.

23. The network device according to claim 19, wherein: The processor is further configured to: Obtain a first response message sent by the second functional entity; wherein the first response message includes a usage report of the satellite backhaul type.

24. The network device according to claim 19, wherein: The processor sends a charging data request to the second functional entity, including: When the backhaul charging trigger condition is obtained, a charging data request is sent to the second functional entity.

25. A network device, comprising a memory, a transceiver, and a processor: A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: Obtaining a charging data request sent by the first functional entity, wherein the charging data request is used for backhaul charging; wherein, The billing data request includes return billing related parameters.

26. The network device according to claim 25, wherein: The charging data request is an initial request for backhaul charging; wherein the backhaul charging related parameters include one or more of the following parameters: Satellite backhaul type; Satellite ID of the preset type of satellite; On-board Data Network Access Identifier DNAI.

27. The network device according to claim 25, wherein: The billing data request is a request for updating billing data for backhaul billing; wherein the backhaul billing related parameters include one or more of the following parameters: Satellite returns type change information; Current satellite backhaul type; Satellite ID of the preset type of satellite; Onboard Data Network Access Identifier DNAI; Satellite backhaul type usage report.

28. The network device according to claim 25, wherein: The charging data request is a request for termination of charging data for backhaul charging; wherein the backhaul charging related parameters include: Satellite backhaul type usage report.

29. The network device according to claim 25, wherein: The processor is further configured to: A first response message is sent to the first functional entity; wherein the first response message includes a usage report of a satellite backhaul type.

30. A backhaul charging device, applied to a first functional entity, comprising: The sending unit is used to send a charging data request to the second functional entity, wherein the charging data request is used for backhaul billing; wherein the charging data request includes backhaul billing related parameters.

31. The device according to claim 30, wherein The billing data request is an initial request for backhaul billing; The backhaul billing related parameters include one or more of the following parameters: Satellite backhaul type; Satellite ID of the preset type of satellite; On-board Data Network Access Identifier DNAI.

32. The device according to claim 30, wherein: The billing data request is a request for updating billing data for backhaul billing; wherein the backhaul billing related parameters include one or more of the following parameters: Satellite returns type change information; Current satellite backhaul type; Satellite ID of the preset type of satellite; Onboard Data Network Access Identifier DNAI; Satellite backhaul type usage report.

33. The device according to claim 30, wherein: The charging data request is a request for termination of charging data for backhaul charging; wherein the backhaul charging related parameters include: Satellite backhaul type usage report.

34. The device according to claim 30, wherein: The device also includes: The first message acquisition unit is used to obtain a first response message sent by the second functional entity; wherein the first response message includes a usage report of a satellite backhaul type.

35. The device according to claim 30, wherein: The sending unit is specifically configured to send a charging data request to the second functional entity when a backhaul charging trigger condition is obtained.

36. A backhaul charging device, applied to a second functional entity, comprising: The obtaining unit is used to obtain a charging data request sent by the first functional entity, wherein the charging data request is used for backhaul charging; wherein the charging data request includes backhaul charging related parameters.

37. The device according to claim 36, wherein The charging data request is an initial request for backhaul charging; wherein the backhaul charging related parameters include one or more of the following parameters: Satellite backhaul type; Satellite ID of the preset type of satellite; On-board Data Network Access Identifier DNAI.

38. The device according to claim 36, wherein The billing data request is a request for updating billing data for backhaul billing; wherein the backhaul billing related parameters include one or more of the following parameters: Satellite returns type change information; Current satellite backhaul type; Satellite ID of the preset type of satellite; Onboard Data Network Access Identifier DNAI; Satellite backhaul type usage report.

39. The device according to claim 36, wherein: The charging data request is a request for termination of charging data for backhaul charging; wherein the backhaul charging related parameters include: Satellite backhaul type usage report.

40. The apparatus of claim 36, wherein: The device also includes: A message sending unit is used to send a first response message to the first functional entity; wherein the first response message includes a usage report of a satellite backhaul type.

41. A processor-readable storage medium storing a computer program, wherein the computer program is used to cause the processor to execute the backhaul billing method described in any one of claims 1 to 12, or to cause the processor to execute the backhaul billing method described in any one of claims 13 to 18.

Citation Information

Patent Citations

  • Shipborne satellite communication method and device, shore-side central station and shipborne terminal station

    CN109600857A

  • Charging method, device and system

    CN116074775A

  • Charging method, apparatus and system

    US20220278907A1

  • Charging functions and methods for updating charging resources

    WO2023059234A1