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

Abstract

The present disclosure provides a backhaul charging processing method and apparatus, a network device, and a readable storage medium. The method in the embodiments of the present disclosure comprises: sending a charging data request to a second function entity, the charging data request being a charging request that is about satellite backhaul and is related to edge computing charging.

Description

Method, device, network equipment and readable storage medium for processing backhaul billing

[0001] This disclosure claims priority to the Chinese patent application filed with the China Patent Office on August 7, 2023, with application number 202310987993.5 and application name “Processing method, device, network device and readable storage medium for backhaul billing”, the entire contents of which are incorporated herein by reference. Technical Field

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

[0003] For remote areas, disaster-stricken regions, deserts, and other areas where it's difficult to deploy base stations and gateways, information exchange needs to be achieved via satellite. Related technologies already support the deployment of edge computing services on satellites, providing edge computing services to users through satellite backhaul. However, these technical solutions don't allow for billing for edge computing services transmitted via satellite backhaul.

[0004] Summary of the Invention

[0005] The purpose of the present disclosure is to provide a method, apparatus, network device and readable storage medium for processing backhaul billing to solve the problem that related technical solutions cannot bill for edge computing services backhauled via satellite.

[0006] To achieve the above objectives, the present disclosure provides a method for processing backhaul billing, which is performed by a first functional entity. The method includes:

[0007] A billing data request is sent to the second functional entity, where the billing data request is a billing request related to edge computing billing regarding satellite backhaul.

[0008] In some embodiments, the charging data request includes at least one of the following:

[0009] a first billing data request, wherein the first billing data request is used to request billing of an application service provider for deploying an EAS on a satellite;

[0010] a second charging data request, where the second charging data request is used to request charging for resources used by the EAS deployed by the application service provider ASP on the satellite;

[0011] A third billing data request is used to request billing for traffic of terminal data passing through the EAS.

[0012] In some embodiments, the sending the first charging data request to the second functional entity includes:

[0013] Obtaining a lifecycle management LCM notification of an edge application server EAS sent by a satellite service provider, wherein the EAS LCM notification includes first EAS configuration and billing related parameters;

[0014] According to the lifecycle management LCM notification of the EAS, a first charging data request is sent to the second functional entity, where the first charging data request includes charging-related parameters of the first EAS configuration backhauled by satellite.

[0015] In some embodiments, the first EAS configuration charging-related parameters include:

[0016] The satellite return type of the satellite;

[0017] Or, identification information of the satellite;

[0018] Alternatively, the satellite return type of the satellite and the identification information of the satellite.

[0019] In some embodiments, the sending the second charging data request to the second functional entity includes:

[0020] Acquiring performance report data, the performance report data including parameter information related to virtualized resource usage of the EAS;

[0021] A second charging data request is sent to the second functional entity according to the performance report data, where the second charging data request includes a second EAS configuration charging-related parameter.

[0022] In some embodiments, the second EAS configuration charging-related parameter includes at least one of the following:

[0023] The IP address of the EAS;

[0024] The satellite return type of the satellite;

[0025] identification information of the satellite;

[0026] Incoming traffic of the EAS;

[0027] outgoing traffic of the EAS;

[0028] The storage status of the EAS;

[0029] The memory usage of the EAS.

[0030] In some embodiments, the third billing data request includes: an initial billing data request, a billing data update request, and a billing data termination request;

[0031] The initial charging data request, the charging data update request and the charging data termination request respectively include a satellite backhaul usage report of the satellite.

[0032] In some embodiments, the satellite backhaul usage report includes at least one of the following:

[0033] Uplink traffic of the onboard user plane function (UPF);

[0034] Downlink traffic of onboard UPF;

[0035] The satellite return type of the satellite;

[0036] identification information of the satellite;

[0037] Configuration information of the on-board EAS, including the IP address of the on-board EAS;

[0038] Onboard Data Network Access Identifier DNAI;

[0039] The on-board UPF is the UPF corresponding to the EAS.

[0040] In some embodiments, the sending the third charging data request to the second functional entity includes:

[0041] When a first triggering event is met, sending the initial charging data request to the second functional entity;

[0042] The first triggering event includes at least one of the following:

[0043] Get the satellite return type;

[0044] Get the satellite's ID.

[0045] Based on the mapping relationship between the identifier of the GEO satellite locally configured by the first functional entity and the DNAI, the on-board UPF is selected.

[0046] In some embodiments, the sending the third charging data request to the second functional entity includes:

[0047] When a second triggering event is met, sending the charging data update request to the second functional entity;

[0048] The second triggering event includes at least one of the following:

[0049] The type of satellite backhaul has changed;

[0050] Get the changed satellite return type;

[0051] Get the updated satellite ID;

[0052] Based on the mapping relationship between the identifier of the GEO satellite locally configured by the first functional entity and the DNAI, the on-board UPF is selected.

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

[0054] Acquire a charging data response sent by the second functional entity, where the charging data response includes a call detail record (CDR) corresponding to the charging data request.

[0055] The embodiment of the present disclosure further provides a method for processing backhaul billing, which is executed by a second functional entity. The method includes:

[0056] Obtaining a billing data request sent by a first functional entity, where the billing data request is a billing request related to edge computing billing for satellite backhaul;

[0057] A charging data response is sent according to the charging data request, wherein the charging data response includes a call detail record (CDR) corresponding to the charging data request.

[0058] In some embodiments, the charging data request includes at least one of the following:

[0059] a first billing data request, wherein the first billing data request is used to request billing of an application service provider for deploying an EAS on a satellite;

[0060] a second charging data request, where the second charging data request is used to request charging for resources used by the EAS deployed by the application service provider ASP on the satellite;

[0061] A third billing data request is used to request billing for traffic of terminal data passing through the EAS.

[0062] In some embodiments, the first charging data request includes first EAS configuration charging related parameters related to satellite backhaul, and the first EAS configuration charging related parameters include:

[0063] The satellite return type of the satellite;

[0064] Or, identification information of the satellite;

[0065] Alternatively, the satellite return type of the satellite and the identification information of the satellite.

[0066] In some embodiments, the second charging data request includes a second EAS configuration charging-related parameter, and the second EAS configuration charging-related parameter includes at least one of the following:

[0067] The IP address of the EAS;

[0068] The satellite return type of the satellite;

[0069] identification information of the satellite;

[0070] Incoming traffic of the EAS;

[0071] outgoing traffic of the EAS;

[0072] The storage status of the EAS;

[0073] The memory usage of the EAS.

[0074] In some embodiments, the third billing data request includes: an initial billing data request, a billing data update request, and a billing data termination request;

[0075] The initial charging data request, the charging data update request and the charging data termination request respectively include a satellite backhaul usage report of the satellite.

[0076] In some embodiments, the satellite backhaul usage report includes at least one of the following:

[0077] Uplink traffic of the onboard user plane function (UPF);

[0078] Downlink traffic of onboard UPF;

[0079] The satellite return type of the satellite;

[0080] identification information of the satellite;

[0081] EAS configuration information, including the IP address of the onboard EAS;

[0082] Onboard Data Network Access Identifier DNAI;

[0083] The on-board UPF is the UPF corresponding to the EAS.

[0084] The embodiment of the present disclosure further provides a network device, including a memory, a transceiver, and a processor;

[0085] 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:

[0086] A billing data request is sent to the second functional entity, where the billing data request is a billing request related to edge computing billing regarding satellite backhaul.

[0087] In some embodiments, the charging data request includes at least one of the following:

[0088] a first billing data request, wherein the first billing data request is used to request billing of an application service provider for deploying an EAS on a satellite;

[0089] a second charging data request, where the second charging data request is used to request charging for resources used by the EAS deployed by the application service provider ASP on the satellite;

[0090] A third billing data request is used to request billing for traffic of terminal data passing through the EAS.

[0091] In some embodiments, the processor further implements the following steps:

[0092] Obtaining a lifecycle management LCM notification of an edge application server EAS sent by a satellite service provider, wherein the EAS LCM notification includes first EAS configuration and billing related parameters;

[0093] According to the lifecycle management LCM notification of the EAS, a first charging data request is sent to the second functional entity, where the first charging data request includes charging-related parameters of the first EAS configuration backhauled by satellite.

[0094] In some embodiments, the first EAS configuration charging-related parameters include:

[0095] The satellite return type of the satellite;

[0096] Or, identification information of the satellite;

[0097] Alternatively, the satellite return type of the satellite and the identification information of the satellite.

[0098] In some embodiments, the processor further implements the following steps:

[0099] Acquiring performance report data, the performance report data including parameter information related to virtualized resource usage of the EAS;

[0100] A second charging data request is sent to the second functional entity according to the performance report data, where the second charging data request includes a second EAS configuration charging-related parameter.

[0101] In some embodiments, the second EAS configuration charging-related parameter includes at least one of the following:

[0102] The IP address of the EAS;

[0103] The satellite return type of the satellite;

[0104] identification information of the satellite;

[0105] Incoming traffic of the EAS;

[0106] outgoing traffic of the EAS;

[0107] The storage status of the EAS;

[0108] The memory usage of the EAS.

[0109] In some embodiments, the third billing data request includes: an initial billing data request, a billing data update request, and a billing data termination request;

[0110] The initial charging data request, the charging data update request and the charging data termination request respectively include a satellite backhaul usage report of the satellite.

[0111] In some embodiments, the satellite backhaul usage report includes at least one of the following:

[0112] Uplink traffic of the onboard user plane function (UPF);

[0113] Downlink traffic of onboard UPF;

[0114] The satellite return type of the satellite;

[0115] identification information of the satellite;

[0116] Configuration information of the on-board EAS, including the IP address of the on-board EAS;

[0117] Onboard Data Network Access Identifier DNAI;

[0118] The on-board UPF is the UPF corresponding to the EAS.

[0119] In some embodiments, the processor further implements the following steps:

[0120] When a first triggering event is met, sending the initial charging data request to the second functional entity;

[0121] The first triggering event includes at least one of the following:

[0122] Get the satellite return type;

[0123] Get the satellite's identity;

[0124] Based on the mapping relationship between the identifier of the GEO satellite locally configured by the first functional entity and the DNAI, the on-board UPF is selected.

[0125] In some embodiments, the processor further implements the following steps:

[0126] When a second triggering event is met, sending the charging data update request to the second functional entity;

[0127] The second triggering event includes at least one of the following:

[0128] The type of satellite backhaul has changed;

[0129] Get the changed satellite return type;

[0130] Get the updated satellite ID;

[0131] Based on the mapping relationship between the identifier of the GEO satellite locally configured by the first functional entity and the DNAI, the on-board UPF is selected.

[0132] In some embodiments, the processor further implements the following steps:

[0133] Acquire a charging data response sent by the second functional entity, where the charging data response includes a call detail record (CDR) corresponding to the charging data request.

[0134] The embodiment of the present disclosure further provides a network device, including a memory, a transceiver, and a processor;

[0135] 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:

[0136] Obtaining a billing data request sent by a first functional entity, where the billing data request is a billing request related to edge computing billing for satellite backhaul;

[0137] A charging data response is sent according to the charging data request, wherein the charging data response includes a call detail record (CDR) corresponding to the charging data request.

[0138] In some embodiments, the charging data request includes at least one of the following:

[0139] a first billing data request, wherein the first billing data request is used to request billing of an application service provider for deploying an EAS on a satellite;

[0140] a second charging data request, where the second charging data request is used to request charging for resources used by the EAS deployed by the application service provider ASP on the satellite;

[0141] A third billing data request is used to request billing for traffic of terminal data passing through the EAS.

[0142] In some embodiments, the first charging data request includes first EAS configuration charging related parameters related to satellite backhaul, and the first EAS configuration charging related parameters include:

[0143] The satellite return type of the satellite;

[0144] Or, identification information of the satellite;

[0145] Alternatively, the satellite return type of the satellite and the identification information of the satellite.

[0146] In some embodiments, the second charging data request includes a second EAS configuration charging-related parameter, and the second EAS configuration charging-related parameter includes at least one of the following:

[0147] The IP address of the EAS;

[0148] The satellite return type of the satellite;

[0149] identification information of the satellite;

[0150] Incoming traffic of the EAS;

[0151] outgoing traffic of the EAS;

[0152] The storage status of the EAS;

[0153] The memory usage of the EAS.

[0154] In some embodiments, the third billing data request includes: an initial billing data request, a billing data update request, and a billing data termination request;

[0155] The initial charging data request, the charging data update request and the charging data termination request respectively include a satellite backhaul usage report of the satellite.

[0156] In some embodiments, the satellite backhaul usage report includes at least one of the following:

[0157] Uplink traffic of the onboard user plane function (UPF);

[0158] Downlink traffic of onboard UPF;

[0159] The satellite return type of the satellite;

[0160] identification information of the satellite;

[0161] EAS configuration information, including the IP address of the onboard EAS;

[0162] Onboard Data Network Access Identifier DNAI;

[0163] The on-board UPF is the UPF corresponding to the EAS.

[0164] The embodiment of the present disclosure further provides a backhaul billing processing device, which is applied to a first functional entity, and includes:

[0165] The first sending unit is used to send a billing data request to the second functional entity, where the billing data request is a billing request related to edge computing billing for satellite backhaul.

[0166] The present disclosure also provides a backhaul billing processing device, which is applied to a second functional entity. The device includes:

[0167] A first acquiring unit is configured to acquire a billing data request sent by a first functional entity, where the billing data request is a billing request related to edge computing billing for satellite backhaul;

[0168] The second sending unit is configured to send a charging data response according to the charging data request, where the charging data response includes a call detail record (CDR) corresponding to the charging data request.

[0169] 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 steps of the method for processing billing data as described above.

[0170] The above technical solution disclosed in the present invention has at least the following beneficial effects:

[0171] In an embodiment of the present disclosure, the first functional entity sends a billing data request to the second functional entity, and the billing data request is a billing request related to edge computing billing for satellite backhaul. Through the billing data request, the second functional entity can achieve the purpose of billing for satellite edge computing services, thereby solving the problem that related technical solutions cannot bill for edge computing services transmitted via satellite backhaul. BRIEF DESCRIPTION OF THE DRAWINGS

[0172] FIG1 is a structural diagram of a network system to which the embodiments of the present disclosure may be applied;

[0173] FIG2 is a flow chart showing a method for processing backhaul billing according to an embodiment of the present disclosure;

[0174] FIG3 shows one interactive diagram of a method for processing backhaul billing according to an embodiment of the present disclosure;

[0175] FIG4 is a schematic diagram showing the relationship between the EAS including the CTF and the converged billing system in an embodiment of the present disclosure;

[0176] FIG5 is a schematic diagram showing one of the information transmission paths based on the architecture shown in FIG4 ;

[0177] FIG6 shows a second schematic diagram of an information transmission path based on the architecture shown in FIG4 ;

[0178] FIG7 shows a third schematic diagram of an information transmission path based on the architecture shown in FIG4 ;

[0179] FIG8 shows a second interactive diagram of the method for processing backhaul billing according to an embodiment of the present disclosure;

[0180] FIG9 shows a third interactive diagram of the method for processing backhaul billing according to an embodiment of the present disclosure;

[0181] FIG10 shows a fourth interactive diagram of the method for processing backhaul billing according to an embodiment of the present disclosure;

[0182] FIG11 shows a fifth interactive diagram of a method for processing backhaul billing according to an embodiment of the present disclosure;

[0183] FIG12 is a second flow chart showing a method for processing backhaul billing according to an embodiment of the present disclosure;

[0184] FIG13 is a block diagram showing a structure of a network device according to an embodiment of the present disclosure;

[0185] FIG14 shows one of the module schematic diagrams of the backhaul billing processing device according to an embodiment of the present disclosure;

[0186] FIG. 15 shows a second module diagram of the backhaul billing processing device according to an embodiment of the present disclosure. DETAILED DESCRIPTION

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

[0188] The terms "first," "second," and the like in the specification and claims of the present disclosure are used to distinguish similar objects and are not necessarily used to describe a particular order or sequential sequence. It should be understood that the terms used in this manner are interchangeable where appropriate so that the embodiments of the present disclosure described herein may be implemented in a sequence other than those illustrated or described herein. In addition, the terms "including" and "having," and any variations thereof, are intended to cover non-exclusive inclusions, e.g., a process, method, system, product, or apparatus comprising a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units that are not explicitly listed or that are inherent to such processes, methods, products, or apparatus.

[0189] In the embodiments of the present disclosure, the term "and / or" describes the relationship between associated objects, indicating that three possible relationships 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. In the embodiments of the present disclosure, the term "plurality" refers to two or more, and other quantifiers are similar.

[0190] In the embodiments of the present disclosure, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present disclosure should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0191] Figure 1 shows a block diagram of a wireless communication system to which the embodiments of the present disclosure can be applied. The wireless communication system includes a terminal device 1 (also referred to as a terminal (User Equipment, UE)), a base station 2, a satellite 3, and a core network 4. The core network 4 may include multiple functional entities. Among them, the satellite 3 is deployed between the base station 2 and the core network 4 to implement information exchange between the base station 2 and the core network 4. It should be noted that in Figure 1, 5GC is the abbreviation of 5th-Generation Core, which is the fifth-generation mobile communication core, AF is the abbreviation of Application Function, which is the application function, and ISL is the abbreviation of Inter-Satellite Link, which is the inter-satellite link.

[0192] In some embodiments, the return 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).

[0193] In related technologies, both the User Plane Function (UPF) and Edge Application Servers (EAS) can be deployed on satellites, providing users with satellite edge computing services via satellite backhaul. This scenario currently only supports GEO. In related technologies, the base station first establishes a Protocol Data Unit (PDU) session with the Destination Network (DN) on the ground, and the Domain Name System (DNS) on the ground resolves the Internet Protocol (IP) address of the EAS on the satellite. The Session Management Function (SMF) selects the target Data Network Access Identifier (DNAI) (associated with the onboard UPF) based on the UE subscription information, UE location, application function (AF) information and EAS information reported by the Edge Application Server Discovery Function (EASDF), and selects the onboard UPF as the uplink classifier (UL CL) / branching point (BP) or local PDU session anchor (local-PSA) and inserts it into the PDU session process.

[0194] The following describes in detail the backhaul billing processing method provided by the embodiments of the present disclosure through some embodiments and application scenarios in conjunction with the accompanying drawings.

[0195] As shown in FIG2 , an embodiment of the present disclosure provides a method for processing backhaul billing, which is executed by a first functional entity. The method includes:

[0196] Step 201: Send a billing data request to the second functional entity, where the billing data request is a billing request related to edge computing billing for satellite backhaul.

[0197] For example, the billing data request can be a billing request related to an edge application server (EAS), and the EAS is deployed on a satellite, that is, the EAS can also be described as an on-satellite EAS. Through the billing data request, the second functional entity can implement the relevant billing of the on-satellite EAS, that is, achieve the purpose of billing the satellite edge computing service, thereby solving the problem that the related technical solutions cannot bill the edge computing services transmitted via the satellite.

[0198] In some embodiments, the first functional entity is a charging trigger function (CTF) or a charging enablement function (CEF).

[0199] The above-mentioned CEF is a consumer of the Nchf (service-based interface provided by AMF) billing service, and for the purpose of billing information collection, it can consume management services and / or services opened by other network functions.

[0200] As an implementation manner, the CTF may be embedded in the EAS or located in the SMF.

[0201] In some embodiments, the second functional entity is a Charging Function (CHF), which provides quota management and generates CDRs for charging events received from CTF or CEF via Nchf.

[0202] In an embodiment of the present disclosure, the first functional entity sends a billing data request to the second functional entity, and the billing data request is a billing request related to edge computing billing for satellite backhaul. Through the billing data request, the second functional entity can achieve the purpose of billing for satellite edge computing services, thereby solving the problem that related technical solutions cannot bill for edge computing services transmitted via satellite backhaul.

[0203] In an embodiment of the present disclosure, a first functional entity sends a billing data request to a second functional entity. The billing data request is a billing request related to an edge application server EAS, and the EAS is deployed on a satellite. Through the billing data request, the second functional entity can realize the relevant billing of the EAS on the satellite, that is, to achieve the purpose of billing the satellite edge computing service, thereby solving the problem that the relevant technical solutions cannot bill the edge computing services transmitted back by the satellite.

[0204] In some embodiments, the charging data request includes at least one of the following:

[0205] A first billing data request, wherein the first billing data request is used to request billing of an application service provider (ASP) for deploying the EAS on a satellite;

[0206] a second charging data request, where the second charging data request is used to request charging for resources used on the satellite by the EAS deployed by the application service provider ASP;

[0207] A third billing data request is used to request billing for traffic of terminal data passing through the EAS.

[0208] In an embodiment of the present disclosure, the first functional entity may simultaneously send at least two of the above-mentioned first billing data request, the second billing data request and the third billing data to the above-mentioned second functional entity, or may send at least two of the above-mentioned first billing data request, the second billing data request and the third billing data request in different orders.

[0209] For the first billing data request mentioned above, the edge infrastructure (satellite service provider) provides satellite resources and signs an agreement with the ASP to allow the ASP to deploy EAS on the satellite. The ASP initiates an EAS lifecycle management request to the satellite service provider, and then the ASP and the satellite service provider (Satellite Service Provider, SSP) settle based on the EAS configuration.

[0210] In some embodiments, the sending the first charging data request to the second functional entity includes:

[0211] Obtaining a Life Cycle Management (LCM) notification of an edge application server EAS sent by a satellite service provider, wherein the LCM notification of the EAS includes first EAS configuration and billing related parameters;

[0212] According to the lifecycle management LCM notification of the EAS, a first charging data request is sent to the second functional entity, where the first charging data request includes charging-related parameters of the first EAS configuration backhauled by satellite.

[0213] It should be noted that, in the embodiment of the present disclosure, the first EAS configuration charging-related parameter may also be referred to as the first EAS charging-related parameter. In the embodiment of the present disclosure, before the first functional entity obtains the above-mentioned LCM notification, it subscribes to the above-mentioned EAS LCM notification from the satellite service provider (or satellite service provider).

[0214] The above-mentioned EAS LCM notification is sent to the first functional entity by the satellite service provider after obtaining the EAS LCM request sent by the ASP and performing corresponding processing (creation / instantiation, upgrade or deletion) based on the request.

[0215] In some embodiments, the first EAS configuration charging-related parameters include:

[0216] The satellite return type of the satellite;

[0217] Or, identification information of the satellite;

[0218] Alternatively, the satellite return type of the satellite and the identification information of the satellite.

[0219] For the second billing data request mentioned above, the edge infrastructure (satellite service provider) provides satellite resources and signs an agreement with the ASP, allowing the ASP to deploy EAS on the satellite. The edge infrastructure (satellite service provider) initiates the measurement of how much resources the EAS uses and then initiates billing.

[0220] In some embodiments, the sending the second charging data request to the second functional entity includes:

[0221] Acquiring performance report data, the performance report data including parameter information related to virtualized resource usage of the EAS;

[0222] A second charging data request is sent to the second functional entity according to the performance report data, where the second charging data request includes a second EAS configuration charging-related parameter.

[0223] It should be noted that, in the embodiment of the present disclosure, the second EAS configuration charging-related parameters may also be referred to as second EAS charging-related parameters.

[0224] In the embodiment of the present disclosure, the performance report data may include at least one of the following parameters:

[0225] Average virtual CPU usage;

[0226] Average virtual memory usage;

[0227] Average virtual disk usage;

[0228] The amount of incoming data;

[0229] The amount of outgoing data.

[0230] In some embodiments, the second EAS configuration charging-related parameter includes at least one of the following:

[0231] The IP address of the EAS;

[0232] The satellite return type of the satellite;

[0233] identification information of the satellite;

[0234] Incoming traffic of the EAS;

[0235] outgoing traffic of the EAS;

[0236] The storage status of the EAS;

[0237] The memory usage of the EAS.

[0238] For the third billing data request, the satellite operator charges for the terminal data flow through the EAS based on the SMF billing scheme.

[0239] In some embodiments, the third billing data request includes: an initial billing data request, a billing data update request, and a billing data termination request;

[0240] The initial charging data request, the charging data update request and the charging data termination request respectively include a satellite backhaul usage report of the satellite.

[0241] In some embodiments, the satellite backhaul usage report includes at least one of the following:

[0242] Uplink traffic of the onboard user plane function (UPF);

[0243] Downlink traffic of onboard UPF;

[0244] The satellite return type of the satellite;

[0245] identification information of the satellite;

[0246] Configuration information of the on-board EAS, including the IP address of the on-board EAS;

[0247] Onboard Data Network Access Identifier DNAI;

[0248] The on-board UPF is the UPF corresponding to the EAS.

[0249] In some embodiments, the sending the third charging data request to the second functional entity includes:

[0250] When a first triggering event is met, sending the initial charging data request to the second functional entity;

[0251] The first triggering event includes at least one of the following:

[0252] Get the satellite return type;

[0253] Get the satellite's identity;

[0254] Based on the mapping relationship between the identifier of the GEO satellite locally configured by the first functional entity and the DNAI, the on-board UPF is selected.

[0255] In some embodiments, the sending the third charging data request to the second functional entity includes:

[0256] When a second triggering event is met, sending the charging data update request to the second functional entity;

[0257] The second triggering event includes at least one of the following:

[0258] The type of satellite backhaul has changed;

[0259] Get the changed satellite return type;

[0260] Get the updated satellite ID;

[0261] Based on the mapping relationship between the identifier of the GEO satellite locally configured by the first functional entity and the DNAI, the on-board UPF is selected.

[0262] In some embodiments, the method of the present disclosure further includes:

[0263] A target charging data response sent by the second functional entity is obtained, where the target charging data response includes a call detail record (CDR) corresponding to the charging data request.

[0264] In the disclosed embodiment, the second functional entity generates the above-mentioned CDR based on the billing data request to achieve the purpose of billing the satellite edge computing service.

[0265] The following describes the process of implementing on-board EAS-related billing through the above-mentioned first billing data request in conjunction with the first and second embodiments.

[0266] Example 1: For a scenario where edge computing is supported by satellite, EAS is deployed on the satellite. Therefore, the use of the on-board EAS needs to be charged during its life cycle, and the charging is triggered by CEF.

[0267] As shown in FIG3 , the method includes:

[0268] Step 1) CEF subscribes to notifications about EAS LCM from the Management Service (MnS) producer.

[0269] The MnS producer may also be described as a satellite service provider or a satellite service provider, on which the EAS is deployed.

[0270] The notification of the EAS LCM may be at least one of a Managed Object Instance (MOI) creation notification (notify MOI Creation), a MOI attribute value change notification (notify MOI Attribute Value Changes) and a MOI deletion notification (notify MOIDeletion).

[0271] Step 2) EAS LCM request: The MnS consumer (ASP) sends an EAS LCM request to the MnS producer.

[0272] If the EAS is deployed on a satellite and its lifecycle begins, the SSP must perform billing, such as counting the start and end times of EAS use, and complete the EAS LCM request through the EAS Inversion of Control (IOC) function's create MOI (createMOI), change MOI attribute values ​​(modifyMOI Attributes), or delete MOI (deleteMOI) operations.

[0273] Step 3) EAS LCM process: The MnS producer processes the EAS LCM request accordingly and executes EAS LCM.

[0274] For example, the MnS producer performs MOI instantiation / creation, MOI upgrade, and MOI deletion processing based on EAS LCM requests.

[0275] Step 4) EAS LCM response: The MnS producer sends the EAS LCM result to the MnS consumer.

[0276] Step 5) EAS LCM notification: The MnS producer sends an EAS LCM notification to the CEF.

[0277] Illustratively, the EAS LCM notification may be notify MOI Creation, notify MOI Attribute Value Changes, or notify MOIDeletion.

[0278] Step 5ch: CEF decides whether to trigger charging, and executes step 5ch-a if it is determined to trigger charging.

[0279] Step 5ch-a) Charging data request: CEF generates charging data related to the EAS LCM notification and sends a first charging data request for charging the deployment of the onboard EAS.

[0280] Exemplarily, the parameters included in the first charging data request may be one or more parameters in Table 1.

[0281] Table 1

[0282] Step 5 chb) Create CDR: CHF stores the received information and creates a CDR related to the event.

[0283] Step 5 chc) Charging data response: CHF notifies CEF of the result of the request.

[0284] In this embodiment, charging is triggered by CEF, and the purpose of charging the application service provider for deploying the EAS on the satellite is achieved through the first EAS charging-related parameter in the first charging data request.

[0285] Example 2: For the scenario of supporting edge computing through satellite, EAS is deployed on the satellite, as shown in Figure 4, and CTF is added to EAS. The rationality of embedding CTF in EAS is that it can be directly placed on the satellite and directly trigger billing. If deployed separately, not necessarily on the satellite, billing may not be timely. ABMF in Figure 4 is the Account Balance Management Function, RF is the Rating Function, CGF is the Charging Gateway Function, and Bx is the call record file transmission interface between the CGF and the BD domain of any network domain, subsystem or business. Nchf is a service-based interface. The signal transmission path diagrams are shown in Figure 5, Figure 6 or Figure 7 respectively. Ga is the reference point between CDF and CGF, which is mainly used to transmit CDRs between the two.

[0286] First, in this embodiment, the EASDF sends a Domain Name System (DNS) response (including the EAS IP address) to the satellite service consumer (e.g., UE), indicating that the satellite service consumer can send data to the onboard EAS; or the satellite service consumer obtains the satellite (SAT) return type, satellite ID, etc. through other means (e.g., application layer). As shown in Figure 8, the specific process includes:

[0287] Step 1) Billable event trigger configuration: Configure MnS Producer (CTF) for events that require billing interaction.

[0288] Step 2) EAS deployment request: The MnS consumer (satellite service consumer) sends an EAS deployment request to the MnS producer. The EAS deployment request is used to request MOI instantiation / creation, MOI upgrade, and MOI deletion.

[0289] Step 3) EAS deployment process: The MnS producer processes the request accordingly and executes the EAS deployment request on the satellite.

[0290] For example, the MnS producer performs MOI instantiation / creation, MOI upgrade, and MOI deletion processing based on the request.

[0291] Step 4) EAS deployment response: The MnS consumer sends an EAS deployment request to the MnS producer.

[0292] Step 4ch-a) Billing Data Request: The MnS Producer generates billing data related to the EAS deployment request and sends a first billing data request to the CHF. This request includes the satellite backhaul type, satellite ID, or onboard EAS IP address. This request is used to bill for the use of the EAS on the satellite, process the related charging data, and generate a CDR. For example, the parameters included in this first billing data request may be one or more of the parameters listed in Table 1.

[0293] 4ch-b) Create CDR: CHF stores the received information and creates a CDR related to the event.

[0294] 4ch-c) Billing data response: CHF notifies the MnS producer of the result of the request.

[0295] In this embodiment, charging is triggered by CTF, and the first EAS charging-related parameter in the first charging data request is used to achieve the purpose of charging the application service provider for deploying the EAS on the satellite.

[0296] The following describes the process of implementing on-board EAS-related billing through the second billing data request in conjunction with the third and fourth embodiments.

[0297] Example 3: For edge computing scenarios supported by satellite, edge infrastructure resources (satellite service provider SSP) are utilized by ASPs, i.e., EAS is deployed on satellites. The SSP needs to charge the ASP for the amount of resources used, and the amount of resource usage needs to be billed, and billing is triggered by the CEF. This example specifies the interaction between the MnS producer (producer), CEF, and CHF to implement converged billing for edge infrastructure resource usage.

[0298] As shown in Figure 9, the specific process includes:

[0299] Step 1) Create a measurement job: CEF creates a measurement job to collect performance measurements related to the virtualized resource (VR) usage of EAS to ensure the performance of the MnS producer. The performance measurement can be one or more of the following:

[0300] Average virtual CPU usage;

[0301] Average virtual memory usage;

[0302] Average virtual disk usage;

[0303] The amount of incoming data;

[0304] The amount of outgoing data.

[0305] Step 1a) Subscribe to performance data file notification: If the measurement job selects the file reporting method, the CEF subscribes to the performance data notification.

[0306] Step 2) Generate performance metrics of resource usage for EAS: The performance assurance MnS producer generates performance metrics based on the measurement job.

[0307] Step 3) Reporting performance data to CEF: The performance assurance MnS manufacturer reports performance data to CEF according to the reporting method selected by CEF for the measurement work.

[0308] If the File Data reporting method is selected:

[0309] Step 3a) reporting performance data via notifyFileReady;

[0310] Step 3b) CEF obtains the file containing the performance data.

[0311] If the streaming data reporting method is selected:

[0312] Steps 3c) and 3d) If the connection has not yet been established, the performance guarantee MnS producer establishes a stream connection with the CEF;

[0313] Step 3e) Performance data is reported by the report Stream Data operation;

[0314] Step 3ch-a) Determine whether to trigger charging: The CEF determines whether to trigger charging. If charging is triggered, proceed to step 3ch-b).

[0315] Step 3ch-b) Billing data request: The CEF generates billing data for the collected resource usage and sends a second billing data request to the CHF. For data transmitted to the onboard EAS, the billing data request adds the satellite backhaul type or satellite RAT type or satellite ID to bill for the use of resources on the satellite; to process the relevant billing data and generate a CDR.

[0316] Exemplarily, the parameters included in the second charging data request may be one or more parameters in Table 2.

[0317] Table 2

[0318] 3ch-c) Create CDR: The CHF stores the received information and decides whether to store the information for future aggregation or create a CDR related to the event.

[0319] 3ch-d) Charging data response: CHF notifies CEF of the result of the request.

[0320] Example 4: For edge computing scenarios supported by satellite, the edge infrastructure resources (satellite service provider) are utilized by the ASP. That is, the EAS is deployed on the satellite. The SSP needs to charge the ASP for the amount of resources used. The CTF is embedded in the MnS producer and deployed on the satellite. Billing is triggered by the CTF. This solution uses performance data to report on the utilization of edge-enabled infrastructure resources.

[0321] As shown in Figure 10, the specific process includes:

[0322] Step 1) Generate performance data for EAS resource usage: The performance assurance MnS producer generates performance data (measurements or KPIs) about the usage of edge-enabled infrastructure resources supporting EAS based on a mapping of VR usage measurements received from the ETSI NFV MANO system. The performance data about edge-enabled infrastructure resources can be related to the amount of data transferred for EAS, EAS virtual CPU usage, EAS virtual memory usage, EAS virtual disk usage, or EAS virtual storage.

[0323] Step 1ch-a) Billing data request: The performance guarantee MnS Producer generates billing data related to the collected resource usage and sends a billing data request to the CHF. For data transmitted to the onboard EAS, the billing data request adds the satellite backhaul type or satellite RAT type or satellite ID to process the relevant billing data and generate a CDR for billing the use of resources on the satellite.

[0324] Exemplarily, the parameters included in the second charging data request may be one or more parameters in Table 2.

[0325] Step 1ch-b) Create CDR: CHF stores the received information and creates a CDR related to the event.

[0326] Step 1ch-c) Charging data response: CHF notifies the performance guarantee MnS producer of the request result.

[0327] Step 2) Reporting of CDRs to the Financial Domain (BD): CHF (via CGF) reports CDRs to BD.

[0328] The following describes the process of implementing on-board EAS-related billing through the third billing data request in conjunction with the fifth and sixth embodiments.

[0329] Example 5: When backhauling via satellite, for non-roaming and roaming with local breakout scenarios, the billing of the PDU session is implemented by session based charging to charge for traffic passing through the satellite; the SMF determines the satellite backhaul type and satellite ID, such as GEO, and determines the GEO satellite ID, and can select the on-board UPF through DNAI (UPF can be used as PSA, or as UL CL / BP and local PSA) to support edge computing; therefore, the UE accesses the edge computing server on the satellite through the on-board UPF, and the SMF determines to select the on-board DNAI. After accessing the on-board EAS, billing can be triggered.

[0330] The Mobile Network Operator (MNO)'s CHF configuration includes quotas and reporting thresholds for charging users for using the 5G System (5GS) features that support edge computing. The specific process is shown in Figure 11 and includes:

[0331] 1) The UE starts using satellite edge applications. The CTF in the SMF receives one or more of the following charging events, triggering charging:

[0332] a)SMF determines the satellite return type

[0333] The satellite return parameters mentioned above can be GEO, MEO, LEO, OTHERSAT, DYNAMIC_GEO, DYNAMIC_MEO, DYNAMIC_LEO or DYNAMIC_OTHERSAT.

[0334] b) SMF obtains the GEO satellite ID;

[0335] c) If the SMF selects the onboard UPF based on the mapping relationship between the locally configured GEO satellite ID and DNAI.

[0336] 2) Charging Data Request [Initial, Quota Requested]: The SMF sends a charging data request to the CHF, namely the initial charging data request (Charging Data Request [Initial]). This request may contain one or more of the parameters shown in Table 3 for satellite backhaul billing:

[0337] Table 3

[0338] 3) Account, rating, and reservation control: CHF rates the request and checks whether the corresponding funds can be reserved on the edge application's account balance. If the account has sufficient funds, CHF will execute the corresponding reservation.

[0339] 4) Open CDR: According to the policy, CHF opens service-related CDR for edge applications.

[0340] 5) Accounting data response [initial, grant quota]: CHF grants the reserved number of units to SMF.

[0341] 6) Supervision of the granting unit: SMF monitors the consumption of the granting unit.

[0342] 7) UE edge application usage is ongoing: SMF continues to provide services.

[0343] 8) Quota Management Trigger: A trigger associated with quota management is satisfied. Unit determination is performed when applicable.

[0344] 9) Billing data request [Update, Quota Requested]: The SMF sends a billing data update request to the CHF, which contains a satellite backhaul usage report to obtain more units for continued service and reports on the units used.

[0345] The satellite backhaul usage report is the same as above. This request may include one or more of the parameters shown in Table 4 for satellite backhaul billing:

[0346] Table 4

[0347] 10) Account, rating, and reservation control: Similar to step 4, you can choose to deduct funds corresponding to usage from the account balance.

[0348] 11) Update CDR: Based on the policy, CHF updates the CDR with the billing data related to the service.

[0349] 12) Billing data response [update, grant quota]: CHF grants the quota for the service to SMF and reserves the number of units.

[0350] 13) Service in progress: NF (CTF) continues to provide services.

[0351] 14) UE stops using the edge application: requests the SMF to end service delivery and perform this operation.

[0352] 15) Billing Data Request [Termination]: The SMF sends a billing data termination request to the CHF. This request includes a satellite backhaul usage report, which is used to bill data related to the service termination using the final consumed units. The satellite backhaul usage report is the same as above. This request may include one or more of the parameters shown in Table 5, which are for satellite backhaul billing:

[0353] Table 5

[0354] 16) Account, Rating Control: CHF performs the service termination process, which includes rating usage using reported charging data and deducting funds corresponding to the usage from the account balance.

[0355] 17) Closing CDR: As per policy, CHF closes the CDR with billing data related to the termination of service and the last reporting unit.

[0356] 18) Billing data response [terminate]: CHF notifies SMF of the request result.

[0357] Example 6: When using satellite backhaul, for non-roaming and roaming with local breakout scenarios, the billing of PDU sessions is implemented by session based charging for traffic billing via satellite; since the UE switches to a base station using a different satellite backhaul type or satellite ID (GEO satellite), the SMF will receive the latest satellite backhaul type or satellite ID (GEO satellite ID) and select a new on-board UPF based on the new DNAI (UPF can be used as PSA, or as UL CL / BP and local PSA; the SMF triggers an update to the billing of traffic via satellite based on the received notification of the change in satellite backhaul type and the new satellite backhaul type or satellite ID.

[0358] Specifically, the process includes:

[0359] 1)-8) are the same as 1)-8) in Example 5.

[0360] 9) If the satellite backhaul type changes, the UPF selected by the SMF may also change, resulting in an N4 session modification process; therefore, the Charging Data Request [update] may be triggered by the following events:

[0361] a) Change in satellite backhaul type (e.g., GEO to LEO);

[0362] b) SMF obtains new (current) satellite backhaul type;

[0363] c)SMF obtains a new satellite ID;

[0364] d) If the SMF selects the onboard UPF based on the mapping between the locally configured GEO satellite ID and DNAI.

[0365] The CTF in the SMF sends a billing data request [Update, Quota Requested]: The SMF sends a billing update request to the CHF, which includes a traffic usage report for the PDU session using satellite backhaul through the UPF. The usage report is triggered by the satellite backhaul billing event update and performs quota management on each UPF.

[0366] Among them, the satellite backhaul usage report can be found in Table 3.

[0367] 10)-18) are the same as 10)-18) in Example 5.

[0368] Based on the above embodiment, the purpose of charging the traffic of terminal data passing through the EAS is achieved.

[0369] In an embodiment of the present disclosure, the first functional entity sends a billing data request to the second functional entity, where the billing data request is a billing request related to the edge application server EAS, and the EAS is deployed on a satellite. Through the billing data request, the second functional entity can realize the relevant billing of the EAS on the satellite, that is, realize the purpose of billing the satellite edge computing service, thereby solving the problem that the relevant technical solutions cannot bill the satellite edge computing service.

[0370] As shown in FIG12 , an embodiment of the present disclosure further provides a method for processing backhaul billing, which is executed by a second functional entity. The method includes:

[0371] Step 1201: Obtain a billing data request sent by a first functional entity, where the billing data request is a billing request related to edge computing billing for satellite backhaul.

[0372] For example, the billing data request may be a billing request related to an edge application server (EAS), and the EAS is deployed on a satellite. This billing data request enables the second functional entity to implement billing related to the on-board EAS, that is, to achieve the purpose of billing for satellite edge computing services, thereby resolving the problem that related technical solutions cannot bill edge computing services transmitted via satellite.

[0373] In some embodiments, the first functional entity is a charging trigger function (CTF) or a charging enablement function (CEF).

[0374] The above-mentioned CEF is a consumer of Nchf billing services and can consume management services and / or services exposed by other network functions for the purpose of billing information collection.

[0375] As an implementation manner, the CTF is embedded in the EAS or located in the SMF.

[0376] In some embodiments, the second functional entity is a Charging Function (CHF), which provides quota management and generates CDRs for charging events received from CTF or CEF via Nchf.

[0377] Step 1202: Send a charging data response according to the charging data request, where the charging data response includes a call detail record (CDR) corresponding to the charging data request.

[0378] In an embodiment of the present disclosure, the second functional entity obtains a billing data request sent by the first functional entity, and the billing data request is a billing request related to edge computing billing for satellite backhaul. Through the billing data request, the second functional entity can achieve the purpose of billing for satellite edge computing services, thereby solving the problem that related technical solutions cannot bill for edge computing services transmitted via satellite backhaul.

[0379] In some embodiments, the charging data request includes at least one of the following:

[0380] a first billing data request, wherein the first billing data request is used to request billing of an application service provider for deploying an EAS on a satellite;

[0381] a second charging data request, where the second charging data request is used to request charging for resources used by the EAS deployed by the application service provider ASP on the satellite;

[0382] A third billing data request is used to request billing for traffic of terminal data passing through the EAS.

[0383] In some embodiments, the first charging data request includes first EAS configuration charging related parameters related to satellite backhaul, and the first EAS configuration charging related parameters include:

[0384] The satellite return type of the satellite;

[0385] Or, identification information of the satellite;

[0386] Alternatively, the satellite return type of the satellite and the identification information of the satellite.

[0387] In some embodiments, the second charging data request includes a second EAS configuration charging-related parameter, and the second EAS configuration charging-related parameter includes at least one of the following:

[0388] The IP address of the EAS;

[0389] The satellite return type of the satellite;

[0390] identification information of the satellite;

[0391] Incoming traffic of the EAS;

[0392] outgoing traffic of the EAS;

[0393] The storage status of the EAS;

[0394] The memory usage of the EAS.

[0395] In some embodiments, the third billing data request includes: an initial billing data request, a billing data update request, and a billing data termination request;

[0396] The initial charging data request, the charging data update request and the charging data termination request respectively include a satellite backhaul usage report of the satellite.

[0397] In some embodiments, the satellite backhaul usage report includes at least one of the following:

[0398] Uplink traffic of the onboard user plane function (UPF);

[0399] Downlink traffic of onboard UPF;

[0400] The satellite return type of the satellite;

[0401] identification information of the satellite;

[0402] EAS configuration information, including the IP address of the onboard EAS;

[0403] Onboard Data Network Access Identifier DNAI;

[0404] The on-board UPF is the UPF corresponding to the EAS.

[0405] It should be noted that the above-mentioned charging data request has been described in detail in the method embodiment on the first functional entity side and will not be repeated here.

[0406] In an embodiment of the present disclosure, the second functional entity obtains a billing data request sent by the first functional entity, and the billing data request is a billing request related to satellite backhaul and edge computing billing. Through the billing data request, the second functional entity can achieve the purpose of billing for satellite edge computing services, thereby solving the problem that related technical solutions cannot bill for edge computing services transmitted via satellite backhaul.

[0407] It should be noted that the method executed by the second functional entity is a method corresponding to the method executed by the above-mentioned first functional entity. The specific interaction process between the two has been described in detail in the embodiment of the first functional entity side and will not be repeated here.

[0408] As shown in FIG13 , an embodiment of the present disclosure provides a network device including a memory 1320 , a transceiver 1300 , and a processor 1310 ;

[0409] The memory 1320 is used to store computer programs; the transceiver 1300 is used to send and receive data under the control of the processor 1310;

[0410] In one embodiment of the present disclosure, the processor 1310 is configured to read the computer program in the memory 1320 and perform the following operations:

[0411] A billing data request is sent to the second functional entity, where the billing data request is a billing request related to edge computing billing regarding satellite backhaul.

[0412] In some embodiments, the charging data request includes at least one of the following:

[0413] a first billing data request, wherein the first billing data request is used to request billing of an application service provider for deploying an EAS on a satellite;

[0414] a second charging data request, where the second charging data request is used to request charging for resources used by the EAS deployed by the application service provider ASP on the satellite;

[0415] A third billing data request is used to request billing for traffic of terminal data passing through the EAS.

[0416] In some embodiments, the processor further implements the following steps:

[0417] Obtaining a lifecycle management LCM notification of an edge application server EAS sent by a satellite service provider, wherein the EAS LCM notification includes first EAS configuration and billing related parameters;

[0418] According to the lifecycle management LCM notification of the EAS, a first charging data request is sent to the second functional entity, where the first charging data request includes charging-related parameters of the first EAS configuration backhauled by satellite.

[0419] In some embodiments, the first EAS configuration charging-related parameters include:

[0420] The satellite return type of the satellite;

[0421] Or, identification information of the satellite;

[0422] Alternatively, the satellite return type of the satellite and the identification information of the satellite.

[0423] In some embodiments, the processor further implements the following steps:

[0424] Acquiring performance report data, the performance report data including parameter information related to virtualized resource usage of the EAS;

[0425] A second charging data request is sent to the second functional entity according to the performance report data, where the second charging data request includes a second EAS configuration charging-related parameter.

[0426] In some embodiments, the second EAS configuration charging-related parameter includes at least one of the following:

[0427] The IP address of the EAS;

[0428] The satellite return type of the satellite;

[0429] identification information of the satellite;

[0430] Incoming traffic of the EAS;

[0431] outgoing traffic of the EAS;

[0432] The storage status of the EAS;

[0433] The memory usage of the EAS.

[0434] In some embodiments, the third billing data request includes: an initial billing data request, a billing data update request, and a billing data termination request;

[0435] The initial charging data request, the charging data update request and the charging data termination request respectively include a satellite backhaul usage report of the satellite.

[0436] In some embodiments, the satellite backhaul usage report includes at least one of the following:

[0437] Uplink traffic of the onboard user plane function (UPF);

[0438] Downlink traffic of onboard UPF;

[0439] The satellite return type of the satellite;

[0440] identification information of the satellite;

[0441] Configuration information of the on-board EAS, including the IP address of the on-board EAS;

[0442] Onboard Data Network Access Identifier DNAI;

[0443] The on-board UPF is the UPF corresponding to the EAS.

[0444] In some embodiments, the processor further implements the following steps:

[0445] When a first triggering event is met, sending the initial charging data request to the second functional entity;

[0446] The first triggering event includes at least one of the following:

[0447] Get the satellite return type;

[0448] Get the satellite's identity;

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

[0450] In some embodiments, the processor further implements the following steps:

[0451] When a second triggering event is met, sending the charging data update request to the second functional entity;

[0452] The second triggering event includes at least one of the following:

[0453] The type of satellite backhaul has changed;

[0454] Get the changed satellite return type;

[0455] Get the updated satellite ID;

[0456] Based on the mapping relationship between the identifier of the GEO satellite locally configured by the first functional entity and the DNAI, the on-board UPF is selected.

[0457] In some embodiments, the processor further implements the following steps:

[0458] Acquire a charging data response sent by the second functional entity, where the charging data response includes a call detail record (CDR) corresponding to the charging data request.

[0459] In another embodiment of the present disclosure, the processor 1310 is configured to read the computer program in the memory 1320 and perform the following operations:

[0460] Obtaining a billing data request sent by a first functional entity, where the billing data request is a billing request related to edge computing billing for satellite backhaul;

[0461] A charging data response is sent according to the charging data request, wherein the charging data response includes a call detail record (CDR) corresponding to the charging data request.

[0462] In some embodiments, the charging data request includes at least one of the following:

[0463] a first billing data request, wherein the first billing data request is used to request billing of an application service provider for deploying an EAS on a satellite;

[0464] a second charging data request, where the second charging data request is used to request charging for resources used by the EAS deployed by the application service provider ASP on the satellite;

[0465] A third billing data request is used to request billing for traffic of terminal data passing through the EAS.

[0466] In some embodiments, the first charging data request includes first EAS configuration charging related parameters related to satellite backhaul, and the first EAS configuration charging related parameters include:

[0467] The satellite return type of the satellite;

[0468] Or, identification information of the satellite;

[0469] Alternatively, the satellite return type of the satellite and the identification information of the satellite.

[0470] In some embodiments, the second charging data request includes a second EAS configuration charging-related parameter, and the second EAS configuration charging-related parameter includes at least one of the following:

[0471] The IP address of the EAS;

[0472] The satellite return type of the satellite;

[0473] identification information of the satellite;

[0474] Incoming traffic of the EAS;

[0475] outgoing traffic of the EAS;

[0476] The storage status of the EAS;

[0477] The memory usage of the EAS.

[0478] In some embodiments, the third billing data request includes: an initial billing data request, a billing data update request, and a billing data termination request;

[0479] The initial charging data request, the charging data update request and the charging data termination request respectively include a satellite backhaul usage report of the satellite.

[0480] In some embodiments, the satellite backhaul usage report includes at least one of the following:

[0481] Uplink traffic of the onboard user plane function (UPF);

[0482] Downlink traffic of onboard UPF;

[0483] The satellite return type of the satellite;

[0484] identification information of the satellite;

[0485] EAS configuration information, including the IP address of the onboard EAS;

[0486] Onboard Data Network Access Identifier DNAI;

[0487] The on-board UPF is the UPF corresponding to the EAS.

[0488] In FIG13 , the bus architecture may include any number of interconnected buses and bridges, specifically various circuits linked together by one or more processors represented by processor 1310 and memory represented by memory 1320. 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 1300 may be a plurality of components, namely, 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 1310 is responsible for managing the bus architecture and general processing, and the memory 1320 may store data used by the processor 1310 when performing operations.

[0489] The processor 1310 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.

[0490] It should be noted here that the above-mentioned network device provided in the embodiment of the present disclosure can implement all the method steps implemented in the above-mentioned method embodiment applied to the first functional entity or the second functional entity, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0491] As shown in FIG14 , an embodiment of the present disclosure further provides a backhaul billing processing device, which is applied to a first functional entity. The device includes:

[0492] The first sending unit 1401 is used to send a billing data request to the second functional entity, where the billing data request is a billing request related to edge computing billing for satellite backhaul.

[0493] In some embodiments, the charging data request includes at least one of the following:

[0494] a first billing data request, wherein the first billing data request is used to request billing of an application service provider for deploying an EAS on a satellite;

[0495] a second charging data request, where the second charging data request is used to request charging for resources used by the EAS deployed by the application service provider ASP on the satellite;

[0496] A third billing data request is used to request billing for traffic of terminal data passing through the EAS.

[0497] In some embodiments, the first sending unit includes:

[0498] A first obtaining subunit is configured to obtain a lifecycle management LCM notification of an edge application server EAS sent by a satellite service provider, wherein the EAS LCM notification includes a first EAS configuration and billing related parameter;

[0499] The first sending subunit is used to send a first billing data request to the second functional entity according to the lifecycle management LCM notification of the EAS, where the first billing data request includes the first EAS configuration billing related parameters about the satellite backhaul.

[0500] In some embodiments, the first EAS configuration charging-related parameters include:

[0501] The satellite return type of the satellite;

[0502] Or, identification information of the satellite;

[0503] Alternatively, the satellite return type of the satellite and the identification information of the satellite.

[0504] In some embodiments, the first sending unit includes:

[0505] a second acquiring subunit, configured to acquire performance report data, wherein the performance report data includes parameter information related to virtualized resource usage of the EAS;

[0506] The second sending subunit is configured to send a second charging data request to the second functional entity according to the performance report data, where the second charging data request includes a second EAS configuration charging-related parameter.

[0507] In some embodiments, the second EAS configuration charging-related parameter includes at least one of the following:

[0508] The IP address of the EAS;

[0509] The satellite return type of the satellite;

[0510] identification information of the satellite;

[0511] Incoming traffic of the EAS;

[0512] outgoing traffic of the EAS;

[0513] The storage status of the EAS;

[0514] The memory usage of the EAS.

[0515] In some embodiments, the third billing data request includes: an initial billing data request, a billing data update request, and a billing data termination request;

[0516] The initial charging data request, the charging data update request and the charging data termination request respectively include a satellite backhaul usage report of the satellite.

[0517] In some embodiments, the satellite backhaul usage report includes at least one of the following:

[0518] Uplink traffic of the onboard user plane function (UPF);

[0519] Downlink traffic of onboard UPF;

[0520] The satellite return type of the satellite;

[0521] identification information of the satellite;

[0522] Configuration information of the on-board EAS, including the IP address of the on-board EAS;

[0523] Onboard Data Network Access Identifier DNAI;

[0524] The on-board UPF is the UPF corresponding to the EAS.

[0525] In some embodiments, the first sending unit is configured to send the initial charging data request to the second functional entity when a first triggering event is satisfied;

[0526] The first triggering event includes at least one of the following:

[0527] Get the satellite return type;

[0528] Get the satellite's identity;

[0529] Based on the mapping relationship between the identifier of the GEO satellite locally configured by the first functional entity and the DNAI, the on-board UPF is selected.

[0530] In some embodiments, the first sending unit is configured to send the charging data update request to the second functional entity when a second triggering event is satisfied;

[0531] The second triggering event includes at least one of the following:

[0532] The type of satellite backhaul has changed;

[0533] Get the changed satellite return type;

[0534] Get the updated satellite ID;

[0535] Based on the mapping relationship between the identifier of the GEO satellite locally configured by the first functional entity and the DNAI, the on-board UPF is selected.

[0536] In some embodiments, the apparatus of the present disclosure further includes:

[0537] The second acquiring unit is configured to acquire a charging data response sent by the second functional entity, where the charging data response includes a call detail record CDR corresponding to the charging data request.

[0538] 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 applied to the first functional entity, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0539] As shown in FIG15 , an embodiment of the present disclosure further provides a backhaul billing processing device, which is applied to a second functional entity. The device includes:

[0540] The first acquiring unit 1501 is configured to acquire a billing data request sent by a first functional entity, where the billing data request is a billing request related to edge computing billing for satellite backhaul;

[0541] The second sending unit 1502 is configured to send a charging data response according to the charging data request, where the charging data response includes a call detail record (CDR) corresponding to the charging data request.

[0542] In some embodiments, the charging data request includes at least one of the following:

[0543] a first billing data request, wherein the first billing data request is used to request billing of an application service provider for deploying an EAS on a satellite;

[0544] a second charging data request, where the second charging data request is used to request charging for resources used by the EAS deployed by the application service provider ASP on the satellite;

[0545] A third billing data request is used to request billing for traffic of terminal data passing through the EAS.

[0546] In some embodiments, the first charging data request includes first EAS configuration charging related parameters related to satellite backhaul, and the first EAS configuration charging related parameters include:

[0547] The satellite return type of the satellite;

[0548] Or, identification information of the satellite;

[0549] Alternatively, the satellite return type of the satellite and the identification information of the satellite.

[0550] In some embodiments, the second charging data request includes a second EAS configuration charging-related parameter, and the second EAS configuration charging-related parameter includes at least one of the following:

[0551] The IP address of the EAS;

[0552] The satellite return type of the satellite;

[0553] identification information of the satellite;

[0554] Incoming traffic of the EAS;

[0555] outgoing traffic of the EAS;

[0556] The storage status of the EAS;

[0557] The memory usage of the EAS.

[0558] In some embodiments, the third billing data request includes: an initial billing data request, a billing data update request, and a billing data termination request;

[0559] The initial charging data request, the charging data update request and the charging data termination request respectively include a satellite backhaul usage report of the satellite.

[0560] In some embodiments, the satellite backhaul usage report includes at least one of the following:

[0561] Uplink traffic of the onboard user plane function (UPF);

[0562] Downlink traffic of onboard UPF;

[0563] The satellite return type of the satellite;

[0564] identification information of the satellite;

[0565] EAS configuration information, including the IP address of the onboard EAS;

[0566] Onboard Data Network Access Identifier DNAI;

[0567] The on-board UPF is the UPF corresponding to the EAS.

[0568] 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 applied to the second functional entity, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

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

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

[0571] In some embodiments of the present disclosure, a processor-readable storage medium is also provided, which stores program instructions. The program instructions are used to enable the processor to execute all the steps implemented by the method embodiment for implementing the above-mentioned first functional entity or all the steps implemented by the method embodiment for implementing the second functional entity, and can achieve the same technical effects. The parts and beneficial effects of this embodiment that are the same as those of the method embodiment will not be described in detail here.

[0572] The terminal device involved in the embodiments of the present disclosure may be a device that provides voice and / or data connectivity to a user, a handheld device with wireless connection function, or other processing devices connected to a wireless modem. In different systems, the name of the terminal device may also be different. For example, in a 5G system, the terminal device may be called User Equipment (UE). A wireless terminal device can communicate with one or more core networks (CN) via a radio access network (RAN). The wireless terminal device may be a mobile terminal device, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal device. For example, it may be a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device that exchanges voice and / or data with a radio access network. For example, personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), and other devices. The wireless terminal device may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, a remote terminal device, an access terminal device, a user terminal device, a user agent, or a user device, but is not limited in the embodiments of the present disclosure.

[0573] The network device (or network-side device) involved in the embodiments of the present disclosure may be a base station, which may include multiple cells providing services to terminals. Depending on the specific application scenario, the base station may also be called an access point, or may be a device in an access network that communicates with a wireless terminal device through one or more sectors on an air interface, or may be called another name. The network device may be used to interchange received air frames with Internet Protocol (IP) packets, acting as a router between the wireless terminal device and the rest of the access network, wherein the rest of the access network may include an Internet Protocol (IP) communication network. The network device may also coordinate attribute management of the air interface. For example, the network device involved in the embodiments of the present disclosure may be a base transceiver station (BTS) in the Global System for Mobile communications (GSM) or code division multiple access (CDMA), a network device (NodeB) in wide-band code division multiple access (WCDMA), an evolutionary Node B (eNB or e-NodeB) in the Long Term Evolution (LTE) system, a 5G base station (gNB) in the 5G network architecture (next generation system), a home evolved Node B (HeNB), a relay node, a femto, a pico, etc., and is not limited in the embodiments of the present disclosure. In some network structures, the network device may include a centralized unit (CU) node and a distributed unit (DU) node, and the centralized unit and the distributed unit may also be geographically separated.

[0574] Network devices and terminal devices can each use one or more antennas for Multiple Input Multiple Output (MIMO) transmission. MIMO transmission can be single-user MIMO (SU-MIMO) or multi-user MIMO (MU-MIMO). Depending on the configuration and number of antenna combinations, MIMO transmission can be two-dimensional MIMO (2D-MIMO), three-dimensional MIMO (3D-MIMO), full-dimensional MIMO (FD-MIMO), or massive MIMO. It can also use diversity transmission, precoding, or beamforming.

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

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

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

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

[0579] It should be noted that it should be understood that the division of the above modules is merely a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated. Moreover, these modules can all be implemented in the form of software called by a processing element; or they can all be implemented in the form of hardware; or some modules can be implemented in the form of software called by a processing element, and some modules can be implemented in the form of hardware. For example, a module can be a separately established processing element, or it can be integrated into a chip of the above-mentioned device. In addition, it can also be stored in the memory of the above-mentioned device in the form of program code, and called by a processing element of the above-mentioned device to perform the functions of the above-mentioned module. The implementation of other modules is similar. In addition, these modules can all or partly be integrated together, or they can be implemented independently. The processing element described here can be an integrated circuit with signal processing capabilities. During implementation, each step of the above method or each module above can be completed by an integrated logic circuit of hardware in the processor element or instructions in the form of software.

[0580] For example, each module, unit, sub-unit or sub-module can be one or more integrated circuits configured to implement the above method, such as one or more application-specific integrated circuits (ASICs), one or more digital signal processors (DSPs), or one or more field programmable gate arrays (FPGAs). For another example, when a module is implemented by scheduling program code through a processing element, the processing element can be a general-purpose processor, such as a central processing unit (CPU) or other processor that can call program code. For another example, these modules can be integrated together and implemented in the form of a system-on-a-chip (SOC).

[0581] The terms "first," "second," and the like in the specification and claims of the present disclosure are used to distinguish similar objects and are not necessarily used to describe a specific order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate, so that the embodiments of the present disclosure described herein may be implemented in a sequence other than that illustrated or described herein. In addition, the terms "including" and "having," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or device that includes a series of steps or units need not be limited to those steps or units explicitly listed, but may include other steps or units that are not explicitly listed or that are inherent to these processes, methods, products, or devices. In addition, the use of "and / or" in the specification and claims to indicate at least one of the connected objects, for example, A and / or B and / or C, means including seven situations: A alone, B alone, C alone, both A and B present, both B and C present, both A and C present, and all A, B, and C present. Similarly, the use of "at least one of A and B" in the specification and claims should be understood to mean "A alone, B alone, or both A and B present."

[0582] 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 method for processing backhaul billing, executed by a first functional entity, the method comprising: A billing data request is sent to the second functional entity, where the billing data request is a billing request related to edge computing billing regarding satellite backhaul.

2. The method according to claim 1, wherein: The charging data request includes at least one of the following: a first charging data request, the first charging data request being used to request charging of an application service provider for deploying an EAS on a satellite; a second charging data request, the second charging data request being used to request charging for resources used on the satellite by the EAS deployed by an application service provider ASP; A third billing data request is used to request billing for traffic of terminal data passing through the EAS.

3. The method according to claim 2, wherein: The sending the first charging data request to the second functional entity includes: Obtaining a lifecycle management LCM notification of an edge application server EAS sent by a satellite service provider, wherein the LCM notification of the EAS includes a first EAS configuration billing related parameter; According to the lifecycle management LCM notification of the EAS, a first charging data request is sent to the second functional entity, where the first charging data request includes the first EAS configuration charging related parameters regarding satellite backhaul.

4. The method according to claim 3, wherein: The first EAS configuration charging related parameters include: The satellite return type of the satellite; Or, identification information of the satellite; Or, the satellite return type of the satellite and the identification information of the satellite.

5. The method according to claim 2, wherein: The sending the second charging data request to the second functional entity includes: Acquiring performance report data, the performance report data including parameter information related to virtualized resource usage of the EAS; According to the performance report data, a second charging data request is sent to the second functional entity, where the second charging data request includes a second EAS configuration charging related parameter.

6. The method according to claim 5, wherein: The second EAS configuration charging related parameter includes at least one of the following: The IP address of the EAS; The satellite return type of the satellite; identification information of the satellite; Incoming traffic of the EAS; outgoing traffic of the EAS; The storage status of the EAS; The memory usage of the EAS.

7. The method according to claim 2, wherein: The third charging data request includes: an initial charging data request, a charging data update request and a charging data termination request; The initial charging data request, the charging data update request and the charging data termination request respectively include a satellite backhaul usage report of the satellite.

8. The method according to claim 7, wherein: The satellite backhaul usage report includes at least one of the following: Uplink traffic of the onboard user plane function (UPF); Downlink traffic of onboard UPF; The satellite return type of the satellite; identification information of the satellite; Configuration information of the on-board EAS, the configuration information including the IP address of the on-board EAS; Onboard Data Network Access Identifier DNAI; The on-board UPF is the UPF corresponding to the EAS.

9. The method according to claim 7, wherein: The sending the third charging data request to the second functional entity includes: When a first triggering event is satisfied, sending the initial charging data request to the second functional entity; The first triggering event includes at least one of the following: Get the satellite return type; Get the satellite's identity; Based on the mapping relationship between the identifier of the GEO satellite locally configured by the first functional entity and the DNAI, the on-board UPF is selected.

10. The method according to claim 7, wherein: The sending the third charging data request to the second functional entity includes: When a second triggering event is met, sending the charging data update request to the second functional entity; The second triggering event includes at least one of the following: The type of satellite backhaul has changed; Get the changed satellite return type; Get the updated satellite ID; Based on the mapping relationship between the identifier of the GEO satellite locally configured by the first functional entity and the DNAI, the on-board UPF is selected.

11. The method according to claim 1, further comprising: Acquire a charging data response sent by the second functional entity, where the charging data response includes a call detail record CDR corresponding to the charging data request.

12. A method for processing backhaul billing, executed by a second functional entity, the method comprising: Obtain a billing data request sent by the first functional entity, where the billing data request is a billing request related to edge computing billing for satellite backhaul; According to the charging data request, a charging data response is sent, wherein the charging data response includes a call detail record CDR corresponding to the charging data request.

13. The method according to claim 12, wherein: The charging data request includes at least one of the following: a first charging data request, the first charging data request being used to request charging of an application service provider for deploying an EAS on a satellite; a second charging data request, the second charging data request being used to request charging for resources used on the satellite by the EAS deployed by an application service provider ASP; The third charging data request is used to request the terminal data to be charged. The EAS traffic is charged.

14. The method according to claim 13, wherein: The first charging data request includes first EAS configuration charging related parameters about satellite backhaul, and the first EAS configuration charging related parameters include: The satellite return type of the satellite; Or, identification information of the satellite; Or, the satellite return type of the satellite and the identification information of the satellite.

15. The method according to claim 13, wherein: The second charging data request includes a second EAS configuration charging related parameter, and the second EAS configuration charging related parameter includes at least one of the following: The IP address of the EAS; The satellite return type of the satellite; identification information of the satellite; Incoming traffic of the EAS; outgoing traffic of the EAS; The storage status of the EAS; The memory usage of the EAS.

16. The method according to claim 13, wherein: The third charging data request includes: an initial charging data request, a charging data update request and a charging data termination request; The initial charging data request, the charging data update request and the charging data termination request respectively include a satellite backhaul usage report of the satellite.

17. The method according to claim 16, wherein: The satellite backhaul usage report includes at least one of the following: Uplink traffic of the onboard user plane function (UPF); Downlink traffic of onboard UPF; The satellite return type of the satellite; identification information of the satellite; Configuration information of the EAS, including the IP address of the EAS on board; Onboard Data Network Access Identifier DNAI; The on-board UPF is the UPF corresponding to the EAS.

18. A network device comprising a memory, a transceiver, and a processor; Memory for storing computer programs; a transceiver, for transmitting and receiving data under the control of the processor; A processor is configured to read the computer program in the memory and perform the following operations: A billing data request is sent to the second functional entity, where the billing data request is a billing request related to edge computing billing regarding satellite backhaul.

19. The network device according to claim 18, wherein: The charging data request includes at least one of the following: a first charging data request, the first charging data request being used to request charging of an application service provider for deploying an EAS on a satellite; a second charging data request, the second charging data request being used to request charging for resources used on the satellite by the EAS deployed by an application service provider ASP; A third billing data request is used to request billing for traffic of terminal data passing through the EAS.

20. The network device according to claim 19, wherein: The processor also implements the following steps: Obtaining a lifecycle management LCM notification of an edge application server EAS sent by a satellite service provider, wherein the LCM notification of the EAS includes a first EAS configuration billing related parameter; According to the lifecycle management LCM notification of the EAS, a first charging data request is sent to the second functional entity, where the first charging data request includes the first EAS charging related parameters about the satellite backhaul.

21. The network device according to claim 20, wherein: The first EAS configuration charging related parameters include: The satellite return type of the satellite; Or, identification information of the satellite; Or, the satellite return type of the satellite and the identification information of the satellite.

22. The network device according to claim 19, wherein: The processor also implements the following steps: Acquire performance report data, the performance report data including information related to virtualized resource usage of EAS Related parameter information; According to the performance report data, a second charging data request is sent to the second functional entity, where the second charging data request includes a second EAS configuration charging related parameter.

23. The network device according to claim 22, wherein: The second EAS configuration charging related parameter includes at least one of the following: The IP address of the EAS; The satellite return type of the satellite; identification information of the satellite; Incoming traffic of the EAS; outgoing traffic of the EAS; The storage status of the EAS; The memory usage of the EAS.

24. The network device according to claim 19, wherein: The third charging data request includes: an initial charging data request, a charging data update request and a charging data termination request; The initial charging data request, the charging data update request and the charging data termination request respectively include a satellite backhaul usage report of the satellite.

25. The network device according to claim 24, wherein: The satellite backhaul usage report includes at least one of the following: Uplink traffic of the onboard user plane function (UPF); Downlink traffic of onboard UPF; The satellite return type of the satellite; identification information of the satellite; Configuration information of the on-board EAS, the configuration information including the IP address of the on-board EAS; Onboard Data Network Access Identifier DNAI; The on-board UPF is the UPF corresponding to the EAS.

26. The network device according to claim 24, wherein: The processor also implements the following steps: When a first triggering event is satisfied, sending the initial charging data request to the second functional entity; The first triggering event includes at least one of the following: Get the satellite return type; Get the satellite's identity; Based on the mapping relationship between the identifier of the GEO satellite locally configured by the first functional entity and the DNAI, the on-board UPF is selected.

27. The network device according to claim 24, wherein: The processor also implements the following steps: When a second triggering event is met, sending the charging data update request to the second functional entity; The second triggering event includes at least one of the following: The type of satellite backhaul has changed; Get the changed satellite return type; Get the updated satellite ID; Based on the mapping relationship between the identifier of the GEO satellite locally configured by the first functional entity and the DNAI, the on-board UPF is selected.

28. The network device according to claim 18, wherein: The processor also implements the following steps: Acquire a charging data response sent by the second functional entity, where the charging data response includes a call detail record CDR corresponding to the charging data request.

29. A network device comprising a memory, a transceiver, and a processor; Memory for storing computer programs; a transceiver, for transmitting and receiving data under the control of the processor; A processor is configured to read the computer program in the memory and perform the following operations: Obtain a billing data request sent by the first functional entity, where the billing data request is a billing request related to edge computing billing for satellite backhaul; According to the charging data request, a charging data response is sent, wherein the charging data response includes a call detail record CDR corresponding to the charging data request.

30. The network device according to claim 29, wherein: The charging data request includes at least one of the following: A first charging data request, wherein the first charging data request is used to request an application service provider Deploy EAS on satellites for billing; a second charging data request, the second charging data request being used to request charging for resources used on the satellite by the EAS deployed by an application service provider ASP; A third billing data request is used to request billing for traffic of terminal data passing through the EAS.

31. The network device according to claim 30, wherein: The first charging data request includes first EAS configuration charging related parameters about satellite backhaul, and the first EAS configuration charging related parameters include: The satellite return type of the satellite; Or, identification information of the satellite; Or, the satellite return type of the satellite and the identification information of the satellite.

32. The network device according to claim 30, wherein: The second charging data request includes a second EAS configuration charging related parameter, and the second EAS configuration charging related parameter includes at least one of the following: The IP address of the EAS; The satellite return type of the satellite; identification information of the satellite; Incoming traffic of the EAS; outgoing traffic of the EAS; The storage status of the EAS; The memory usage of the EAS.

33. The network device according to claim 30, wherein: The third charging data request includes: an initial charging data request, a charging data update request and a charging data termination request; The initial charging data request, the charging data update request and the charging data termination request respectively include a satellite backhaul usage report of the satellite.

34. The network device according to claim 33, wherein: The satellite backhaul usage report includes at least one of the following: Uplink traffic of the onboard user plane function (UPF); Downlink traffic of onboard UPF; The satellite return type of the satellite; identification information of the satellite; Configuration information of the EAS, including the IP address of the EAS on board; Onboard Data Network Access Identifier DNAI; The on-board UPF is the UPF corresponding to the EAS.

35. A backhaul billing processing device, applied to a first functional entity, the device comprising: The first sending unit is used to send a billing data request to the second functional entity, where the billing data request is a billing request related to edge computing billing regarding satellite backhaul.

36. The device according to claim 35, wherein The charging data request includes at least one of the following: a first charging data request, the first charging data request being used to request charging of an application service provider for deploying an EAS on a satellite; a second charging data request, the second charging data request being used to request charging for resources used on the satellite by the EAS deployed by an application service provider ASP; A third billing data request is used to request billing for traffic of terminal data passing through the EAS.

37. The device according to claim 36, wherein The first sending unit includes: A first acquisition subunit is used to acquire a lifecycle management LCM notification of an edge application server EAS sent by a satellite service provider, wherein the LCM notification of the EAS includes a first EAS configuration billing related parameter; The first sending subunit is used to send a first billing data request to the second functional entity according to the lifecycle management LCM notification of the EAS, wherein the first billing data request includes the first EAS configuration billing related parameters about the satellite backhaul.

38. The device according to claim 37, wherein The first EAS charging related parameters include: The satellite return type of the satellite; Or, identification information of the satellite; Or, the satellite return type of the satellite and the identification information of the satellite.

39. The apparatus according to claim 36, wherein the first sending unit comprises: A second acquisition subunit is used to acquire performance report data, wherein the performance report data includes parameter information related to virtualized resource usage of the EAS; The second sending subunit is used to send a second charging data request to the second functional entity according to the performance report data, where the second charging data request includes a second EAS configuration charging related parameter.

40. The device according to claim 39, wherein The second EAS configuration charging related parameter includes at least one of the following: The IP address of the EAS; The satellite return type of the satellite; identification information of the satellite; Incoming traffic of the EAS; outgoing traffic of the EAS; The storage status of the EAS; The memory usage of the EAS.

41. The apparatus of claim 36, wherein: The third charging data request includes: an initial charging data request, a charging data update request and a charging data termination request; The initial charging data request, the charging data update request and the charging data termination request respectively include a satellite backhaul usage report of the satellite.

42. The device according to claim 41, wherein The satellite backhaul usage report includes at least one of the following: Uplink traffic of the onboard user plane function (UPF); Downlink traffic of onboard UPF; The satellite return type of the satellite; identification information of the satellite; Configuration information of the on-board EAS, the configuration information including the IP address of the on-board EAS; Onboard Data Network Access Identifier DNAI; The on-board UPF is the UPF corresponding to the EAS.

43. The device according to claim 41, wherein The first sending unit is used for: When a first triggering event is satisfied, sending the initial charging data request to the second functional entity; The first triggering event includes at least one of the following: Get the satellite return type; Get the satellite's identity; Based on the mapping relationship between the identifier of the GEO satellite locally configured by the first functional entity and the DNAI, the on-board UPF is selected.

44. The device according to claim 41, wherein The first sending unit is used for: When a second triggering event is met, sending the charging data update request to the second functional entity; The second triggering event includes at least one of the following: The type of satellite backhaul has changed; Get the changed satellite return type; Get the updated satellite ID; Based on the mapping relationship between the identifier of the GEO satellite locally configured by the first functional entity and the DNAI, the on-board UPF is selected.

45. The apparatus of claim 35, further comprising: The second acquiring unit is configured to acquire a charging data response sent by the second functional entity, wherein the charging data response includes a call detail record CDR corresponding to the charging data request.

46. ​​A backhaul billing processing device, applied to a second functional entity, the device comprising: A first acquisition unit is used to acquire a billing data request sent by a first functional entity, where the billing data request is a billing request related to edge computing billing for satellite backhaul; The second sending unit is configured to send a charging data response according to the charging data request, wherein the charging data response includes a call detail record CDR corresponding to the charging data request.

47. The device according to claim 46, wherein The charging data request includes at least one of the following: a first charging data request, the first charging data request being used to request charging of an application service provider for deploying an EAS on a satellite; a second charging data request, the second charging data request being used to request charging for resources used on the satellite by the EAS deployed by an application service provider ASP; The third charging data request is used to request the terminal data to be charged. The EAS traffic is charged.

48. The apparatus of claim 47, wherein: The first charging data request includes a first EAS charging related parameter, and the first EAS charging related parameter includes: The satellite return type of the satellite; Or, identification information of the satellite; Or, the satellite return type of the satellite and the identification information of the satellite.

49. The apparatus of claim 47, wherein: The second charging data request includes a second EAS charging related parameter, and the second EAS charging related parameter includes at least one of the following: The IP address of the EAS; The satellite return type of the satellite; identification information of the satellite; Incoming traffic of the EAS; outgoing traffic of the EAS; The storage status of the EAS; The memory usage of the EAS.

50. The apparatus of claim 47, wherein: The third charging data request includes: an initial charging data request, a charging data update request and a charging data termination request; The initial charging data request, the charging data update request and the charging data termination request respectively include a satellite backhaul usage report of the satellite.

51. The apparatus of claim 50, wherein: The satellite backhaul usage report includes at least one of the following: Uplink traffic of the onboard user plane function (UPF); Downlink traffic of onboard UPF; The satellite return type of the satellite; identification information of the satellite; Configuration information of the EAS, including the IP address of the EAS on board; Onboard Data Network Access Identifier DNAI; The on-board UPF is the UPF corresponding to the EAS.

52. A processor-readable storage medium storing a computer program, wherein the computer program is used to cause the processor to execute the steps of the method for processing backhaul billing as described in any one of claims 1 to 11, or to execute the steps of the method for processing backhaul billing as described in any one of claims 12 to 17.

Images