Processing method and device for return charging, network equipment and readable storage medium

Abstract

The invention provides a return charging processing method and device, network equipment and a readable storage medium, and aims to solve the problem that an edge computing service returned through a satellite cannot be charged in an existing scheme. The method comprises the steps that a charging data request is sent to a second functional entity, the charging data request is a charging request related to an edge application server EAS, and the EAS is deployed on a satellite. Through the charging data request, the second functional entity can realize the related charging of the on-satellite EAS, namely, the purpose of charging the satellite edge computing service is realized, so that the problem that the satellite edge computing service cannot be charged in the existing scheme is solved.

Description

Technical Field

[0001] The present application 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

[0002] For areas such as remote areas, disaster-stricken areas, and deserts where it is difficult to deploy base stations, gateways, and other equipment, information exchange needs to be achieved through satellites. Related technologies already support the deployment of edge computing services on satellites, that is, to provide edge computing services to users through satellite backhaul, but existing solutions cannot charge for edge computing services backhauled by satellites. Summary of the invention

[0003] The purpose of this application is to provide a method, apparatus, network device and readable storage medium for processing backhaul billing to solve the problem that existing solutions are unable to bill for edge computing services backhauled via satellite.

[0004] In order to achieve the above object, the present application provides a backhaul billing processing method, which is performed by a first functional entity, and the method includes:

[0005] A charging data request is sent to the second functional entity, where the charging data request is a charging request related to an edge application server EAS, and the EAS is deployed on a satellite.

[0006] Optionally, the charging data request includes at least one of the following:

[0007] a first charging data request, the first charging data request being used to request charging an application service provider for deploying the EAS on a satellite;

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

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

[0010] Optionally, sending the first charging data request to the second functional entity includes:

[0011] 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 billing-related parameter;

[0012] 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 EAS charging related parameters.

[0013] Optionally, the first EAS charging related parameter includes:

[0014] The IP address of the EAS;

[0015] or, the IP address of the EAS and the satellite return type of the satellite;

[0016] or, the IP address of the EAS and the identification information of the satellite;

[0017] Or, the IP address of the EAS, the satellite return type of the satellite, and the identification information of the satellite.

[0018] Optionally, sending the second charging data request to the second functional entity includes:

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

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

[0021] Optionally, the second EAS charging-related parameter includes at least one of the following:

[0022] The IP address of the EAS;

[0023] The satellite return type of the satellite;

[0024] identification information of the satellite;

[0025] Incoming traffic of the EAS;

[0026] outgoing traffic of the EAS;

[0027] The storage status of the EAS;

[0028] The memory usage of the EAS.

[0029] Optionally, the third charging data request includes: an initial charging data request, a charging data update request and a charging data termination request;

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

[0031] Optionally, the satellite backhaul usage report includes at least one of the following:

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

[0033] Downlink traffic of onboard UPF;

[0034] The satellite return type of the satellite;

[0035] identification information of the satellite;

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

[0037] Onboard Data Network Access Identifier DNAI;

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

[0039] Optionally, the sending a third charging data request to the second functional entity includes:

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

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

[0042] Get the satellite return type;

[0043] Get the satellite's identity;

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

[0045] Optionally, the sending a third charging data request to the second functional entity includes:

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

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

[0048] The type of satellite backhaul has changed;

[0049] Get the changed satellite return type;

[0050] Get the updated satellite ID;

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

[0052] Optionally, the method further comprises:

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

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

[0055] Acquire a charging data request sent by a first functional entity, where the charging data request is a charging request related to an edge application server EAS, and the EAS is deployed on a satellite;

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

[0057] Optionally, the charging data request includes at least one of the following:

[0058] a first charging data request, the first charging data request being used to request charging an application service provider for deploying the EAS on a satellite;

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

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

[0061] Optionally, the first charging data request includes a first EAS charging related parameter, and the first EAS charging related parameter includes:

[0062] The IP address of the EAS;

[0063] or, the IP address of the EAS and the satellite return type of the satellite;

[0064] or, the IP address of the EAS and the identification information of the satellite;

[0065] Or, the IP address of the EAS, the satellite return type of the satellite, and the identification information of the satellite.

[0066] Optionally, 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:

[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] Optionally, the third charging data request includes: an initial charging data request, a charging data update request and a charging 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] Optionally, 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] Configuration information of the EAS, including the IP address of the EAS on board;

[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 application also 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 charging data request is sent to the second functional entity, where the charging data request is a charging request related to an edge application server EAS, and the EAS is deployed on a satellite.

[0087] Optionally, the charging data request includes at least one of the following:

[0088] a first charging data request, the first charging data request being used to request charging an application service provider for deploying the EAS on a satellite;

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

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

[0091] Optionally, 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 LCM notification of the EAS includes a first EAS billing-related parameter;

[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 the EAS charging related parameters.

[0094] Optionally, the first EAS charging related parameter includes:

[0095] The IP address of the EAS;

[0096] or, the IP address of the EAS and the satellite return type of the satellite;

[0097] or, the IP address of the EAS and the identification information of the satellite;

[0098] Or, the IP address of the EAS, the satellite return type of the satellite, and the identification information of the satellite.

[0099] Optionally, the processor further implements the following steps:

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

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

[0102] Optionally, the second EAS charging-related parameter includes at least one of the following:

[0103] The IP address of the EAS;

[0104] The satellite return type of the satellite;

[0105] identification information of the satellite;

[0106] Incoming traffic of the EAS;

[0107] outgoing traffic of the EAS;

[0108] The storage status of the EAS;

[0109] The memory usage of the EAS.

[0110] Optionally, the third charging data request includes: an initial charging data request, a charging data update request and a charging data termination request;

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

[0112] Optionally, the satellite backhaul usage report includes at least one of the following:

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

[0114] Downlink traffic of onboard UPF;

[0115] The satellite return type of the satellite;

[0116] identification information of the satellite;

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

[0118] Onboard Data Network Access Identifier DNAI;

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

[0120] Optionally, the processor further implements the following steps:

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

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

[0123] Get the satellite return type;

[0124] Get the satellite's identity;

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

[0126] Optionally, the processor further implements the following steps:

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

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

[0129] The type of satellite backhaul has changed;

[0130] Get the changed satellite return type;

[0131] Get the updated satellite ID;

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

[0133] Optionally, the processor further implements the following steps:

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

[0135] The embodiment of the present application also provides a network device, including a memory, a transceiver, and a processor;

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

[0137] Acquire a charging data request sent by a first functional entity, where the charging data request is a charging request related to an edge application server EAS, and the EAS is deployed on a satellite;

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

[0139] Optionally, the charging data request includes at least one of the following:

[0140] a first charging data request, the first charging data request being used to request charging an application service provider for deploying the EAS on a satellite;

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

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

[0143] Optionally, the first charging data request includes a first EAS charging related parameter, and the first EAS charging related parameter includes:

[0144] The IP address of the EAS;

[0145] or, the IP address of the EAS and the satellite return type of the satellite;

[0146] or, the IP address of the EAS and the identification information of the satellite;

[0147] Or, the IP address of the EAS, the satellite return type of the satellite, and the identification information of the satellite.

[0148] Optionally, 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:

[0149] The IP address of the EAS;

[0150] The satellite return type of the satellite;

[0151] identification information of the satellite;

[0152] Incoming traffic of the EAS;

[0153] outgoing traffic of the EAS;

[0154] The storage status of the EAS;

[0155] The memory usage of the EAS.

[0156] Optionally, the third charging data request includes: an initial charging data request, a charging data update request and a charging data termination request;

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

[0158] Optionally, the satellite backhaul usage report includes at least one of the following:

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

[0160] Downlink traffic of onboard UPF;

[0161] The satellite return type of the satellite;

[0162] identification information of the satellite;

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

[0164] Onboard Data Network Access Identifier DNAI;

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

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

[0167] The first sending unit is used to send a charging data request to the second functional entity, where the charging data request is a charging request related to an edge application server EAS, and the EAS is deployed on a satellite.

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

[0169] A first acquisition unit is used to acquire a charging data request sent by a first functional entity, where the charging data request is a charging request related to an edge application server EAS, and the EAS is deployed on a satellite;

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

[0171] An embodiment of the present application 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.

[0172] The above technical solution of the present application has at least the following beneficial effects:

[0173] In an embodiment of the present application, 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 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, to achieve the purpose of billing the satellite edge computing service, thereby solving the problem that the existing solution cannot bill the edge computing service transmitted back by the satellite. BRIEF DESCRIPTION OF THE DRAWINGS

[0174] Figure 1 A structural diagram showing a network system to which the embodiments of the present application can be applied;

[0175] Figure 2 A flowchart of a method for processing backhaul billing according to an embodiment of the present application is shown;

[0176] Figure 3One of the interactive schematic diagrams showing the method for processing backhaul billing in an embodiment of the present application;

[0177] Figure 4 A schematic diagram showing the relationship between the EAS including CTF and the converged billing system in an embodiment of the present application;

[0178] Figure 5 Indicates based on Figure 4 One of the schematic diagrams of the information transmission path of the architecture shown;

[0179] Figure 6 Indicates based on Figure 4 The second schematic diagram of the information transmission path of the architecture shown;

[0180] Figure 7 Indicates based on Figure 4 Schematic diagram of information transmission path of the architecture shown in the third one;

[0181] Figure 8 A second interactive diagram showing a method for processing backhaul billing according to an embodiment of the present application;

[0182] Fig. 9 A third interactive diagram showing a method for processing backhaul billing according to an embodiment of the present application;

[0183] Fig.10 A fourth interactive diagram showing a method for processing backhaul billing according to an embodiment of the present application;

[0184] Fig.11 A fifth interactive diagram showing a method for processing backhaul billing according to an embodiment of the present application;

[0185] Fig.12 A second flowchart of a method for processing backhaul billing according to an embodiment of the present application is shown;

[0186] Fig.13 A structural block diagram showing a network device according to an embodiment of the present application;

[0187] Fig.14 One of the module schematic diagrams showing the backhaul billing processing device of the embodiment of the present application;

[0188] Fig.15 The second module schematic diagram of the backhaul billing processing device according to the embodiment of the present application. DETAILED DESCRIPTION

[0189] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0190] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present application described herein, for example, are implemented in a sequence other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, the process, method, system, product or equipment comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or equipment.

[0191] In the embodiments of the present application, the term "and / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent three situations: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects before and after are in an "or" relationship. In the embodiments of the present application, the term "plurality" refers to two or more than two, and other quantifiers are similar.

[0192] In the embodiments of the present application, 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 application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.

[0193] Figure 1 A block diagram of a wireless communication system to which the embodiments of the present application can be applied is shown. 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 realize information interaction between the base station 2 and the core network 4.

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

[0195] In related technologies, UPF and edge application servers (EAS) can be deployed on satellites to provide users with satellite edge computing services through satellite backhaul. Currently, only GEO is supported in this scenario. 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 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 to become the uplink classifier (UL CL) / branching point (BP) or the local PDU session anchor (local-PSA) and inserts it into the PDU session process.

[0196] The following is a detailed description of the backhaul billing processing method provided by the embodiment of the present application through some embodiments and their application scenarios in combination with the accompanying drawings.

[0197] like Figure 2 As shown, an embodiment of the present application provides a method for processing backhaul billing, which is executed by a first functional entity, and the method includes:

[0198] Step 201: Send a charging data request to a second functional entity, wherein the charging data request is a charging 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.

[0199] Optionally, the first functional entity is a charging trigger function (CTF) or a charging enablement function (CEF).

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

[0201] As an implementation manner, the above CTF can be embedded in the EAS or located in the SMF.

[0202] Optionally, the second functional entity is a charging function (Charging Function, CHF), which provides quota management and provides a call detail record (CDR) generation function to generate CDRs for charging events received from CTF or CEF through Nchf.

[0203] In an embodiment of the present application, 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 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, to achieve the purpose of billing the satellite edge computing service, thereby solving the problem that the existing solution cannot bill the edge computing service transmitted back by the satellite.

[0204] Optionally, 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, 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;

[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 application, the first functional entity may simultaneously send at least two of the first billing data request, the second billing data request and the third billing data to the second functional entity, or may send at least two of the 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 a request for EAS lifecycle management 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] Optionally, 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 a first EAS billing-related parameter;

[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 the EAS charging related parameters.

[0213] In the embodiment of the present application, before the first functional entity obtains the above-mentioned LCM notification, it subscribes to the above-mentioned LCM notification of the EAS 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 acquiring the EAS LCM request sent by the ASP and performing corresponding processing (creation / instantiation, upgrade or deletion) based on the request.

[0215] Optionally, the first EAS charging related parameter includes:

[0216] The IP address of the EAS;

[0217] or, the IP address of the EAS and the satellite return type of the satellite;

[0218] or, the IP address of the EAS and the identification information of the satellite;

[0219] Or, the IP address of the EAS, the satellite return type of the satellite, and the identification information of the satellite.

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

[0221] Optionally, sending the second charging data request to the second functional entity includes:

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

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

[0224] In this embodiment of the present application, the above 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] Optionally, the second EAS 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 the traffic of the terminal data through the EAS based on the billing scheme of the SMF.

[0239] Optionally, the third charging data request includes: an initial charging data request, a charging data update request and a charging 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] Optionally, 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, the configuration information 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] Optionally, the sending a third charging data request to the second functional entity includes:

[0250] When a first triggering event is satisfied, 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] Optionally, the sending a 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] Optionally, the method of the embodiment of the present application 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 an embodiment of the present application, 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 combination with Embodiment 1 and Embodiment 2.

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

[0267] like Figure 3 As shown, 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 ValueChanges) 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 EAS is deployed on a satellite and its life cycle begins, the SSP needs to perform billing, such as counting the start and end time 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 ​​(modify MOI Attributes) or delete MOI (delete MOI) operations.

[0273] Step 3) EAS LCM process: The MnS producer performs corresponding processing according to the EAS LCM request 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] Exemplarily, the EAS LCM notification may be notify MOI Creation, notify MOI AttributeValue Changes or notify MOIDeletion.

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

[0279] Step 5ch-a) Billing data request: CEF generates billing data related to the EAS LCM notification and sends a first billing data request for billing the deployment of the on-board 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]

[0283]

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

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

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

[0287] Embodiment 2: For the scenario of supporting edge computing via satellite, EAS is deployed on the satellite, such as Figure 4 As shown in the figure, 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 it is deployed separately, it may not be on the satellite, and billing may not be timely. Figure 4 ABMF stands for Account Balance Management Function, RF stands for Rating Function, CGF stands for Charging Gateway Function, and Bx is the interface for transferring bill files between CGF and BD domains in any network domain, subsystem or service. Nchf is a service-oriented interface. The signal transmission path diagram is shown in the figure below. Figure 5 , Figure 6 or Figure 7 As shown, Ga is the reference point between CDF and CGF, and is mainly used to transmit CDR between the two.

[0288] First, in this embodiment, EASDF sends a Domain Name System (DNS) response (including EAS IP address) to the satellite service consumer (such as 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 (such as application layer). Figure 8 As shown, the specific process includes:

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

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

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

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

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

[0294] Step 4ch-a) Billing data request: MnS Producer generates billing data related to the EAS deployment request and sends a first billing data request to CHF, which includes the satellite backhaul type or satellite ID or on-board EAS IP address for billing the use of the EAS on the satellite, so as to process the related charging data and generate CDR. Exemplarily, the parameters included in the first billing data request may be one or more parameters in Table 1.

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

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

[0297] In this embodiment, charging is triggered by CTF, 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.

[0298] The following describes the process of implementing on-board EAS-related billing through the second billing data request in conjunction with Embodiment 3 and Embodiment 4.

[0299] Embodiment 3: For the scenario of edge computing supported by satellite, the resources of edge infrastructure (satellite service provider SSP) are utilized by ASP, i.e. EAS is deployed on satellite, and SSP needs to charge ASP for the resources used, and the resources used need to be charged, and the billing is triggered by CEF. This embodiment specifies the interaction between MnS producer (producer), CEF and CHF to realize converged billing for edge infrastructure resource usage.

[0300] like Fig. 9 As shown, the specific process includes:

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

[0302] Average virtual CPU usage;

[0303] Average virtual memory usage;

[0304] Average virtual disk usage;

[0305] The amount of incoming data;

[0306] The amount of outgoing data.

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

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

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

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

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

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

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

[0314] Steps 3c) and 3d) The performance guarantee MnS producer establishes a streaming connection with the CEF if the connection has not yet been established;

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

[0316] Step 3ch-a) Determine whether to trigger billing: CEF decides whether to trigger billing. If billing is triggered, execute step 3ch-b);

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

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

[0319] Table 2

[0320]

[0321]

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

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

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

[0325] like Fig.10 As shown, the specific process includes:

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

[0327] Step 1ch-a) Billing data request: Performance guarantee MnS Producer generates billing data related to the collected resource usage and sends a billing data request to CHF. For transmitting data to the on-board EAS, the satellite backhaul type or satellite RAT type or satellite ID is added to the billing data request to process the relevant billing data and generate CDR for billing the use of resources on the satellite.

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

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

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

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

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

[0333] Embodiment 5: When backhauling via satellite, for non-roaming and roaming with local breakout scenarios, the billing of PDU sessions is implemented by session based charging to charge for traffic passing through the satellite; 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.

[0334] The CHF configuration of the MNO has quotas and reporting thresholds for charging users for using 5GS functions that support edge computing. The specific process is as follows: Fig.11 As shown, including:

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

[0336] a) SMF determines the satellite return type

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

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

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

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

[0341] Table 3

[0342]

[0343]

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

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

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

[0347] 6) Supervision of granting units: SMF monitors the consumption of granting units.

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

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

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

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

[0352] Table 4

[0353]

[0354]

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

[0356] 11) Update CDR: According to the policy, CHF updates the CDR with the billing data related to the service.

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

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

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

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

[0361] Table 5

[0362]

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

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

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

[0366] Embodiment 6: When backhauling via satellite, 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 ULCL / BP and local PSA; the SMF triggers an update to the billing of traffic via satellite based on the receipt of a notification of a change in the satellite backhaul type, as well as the new satellite backhaul type or satellite ID.

[0367] Specifically, the process includes:

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

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

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

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

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

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

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

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

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

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

[0378] In an embodiment of the present application, 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 the edge application server EAS, and the EAS is deployed on the 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 existing solution cannot bill the satellite edge computing service.

[0379] like Fig.12 As shown, the embodiment of the present application also provides a method for processing backhaul billing, which is performed by a second functional entity, and the method includes:

[0380] Step 1201: Obtain a charging data request sent by a first functional entity, where the charging data request is a charging request related to an edge application server EAS, and the EAS is deployed on a satellite.

[0381] Optionally, the first functional entity is a charging trigger function (CTF) or a charging enablement function (CEF).

[0382] The above CEF is a consumer of Nchf billing services and may consume management services and / or services opened by other network functions for the purpose of billing information collection.

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

[0384] Optionally, the second functional entity is a charging function (Charging Function, CHF), which provides quota management and provides a call detail record (CDR) generation function to generate CDRs for charging events received from CTF or CEF through Nchf.

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

[0386] In an embodiment of the present application, the second functional entity obtains a billing data request sent by the first functional entity, where 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 implement relevant billing of the EAS on board, that is, to achieve the purpose of billing the satellite edge computing service, thereby solving the problem that the existing solution cannot bill for the edge computing service transmitted back via the satellite.

[0387] Optionally, the charging data request includes at least one of the following:

[0388] a first charging data request, the first charging data request being used to request charging an application service provider for deploying the EAS on a satellite;

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

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

[0391] Optionally, the first charging data request includes a first EAS charging related parameter, and the first EAS charging related parameter includes:

[0392] The IP address of the EAS;

[0393] or, the IP address of the EAS and the satellite return type of the satellite;

[0394] or, the IP address of the EAS and the identification information of the satellite;

[0395] Or, the IP address of the EAS, the satellite return type of the satellite, and the identification information of the satellite.

[0396] Optionally, 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:

[0397] The IP address of the EAS;

[0398] The satellite return type of the satellite;

[0399] identification information of the satellite;

[0400] Incoming traffic of the EAS;

[0401] outgoing traffic of the EAS;

[0402] The storage status of the EAS;

[0403] The memory usage of the EAS.

[0404] Optionally, the third charging data request includes: an initial charging data request, a charging data update request and a charging data termination request;

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

[0406] Optionally, the satellite backhaul usage report includes at least one of the following:

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

[0408] Downlink traffic of onboard UPF;

[0409] The satellite return type of the satellite;

[0410] identification information of the satellite;

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

[0412] Onboard Data Network Access Identifier DNAI;

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

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

[0415] In an embodiment of the present application, the second functional entity obtains a billing data request sent by the first functional entity, where 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 implement relevant billing of the EAS on board, that is, to achieve the purpose of billing the satellite edge computing service, thereby solving the problem that the existing solution cannot bill for the edge computing service transmitted back via the satellite.

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

[0417] like Fig.13 As shown, an embodiment of the present application provides a network device, including a memory 1320, a transceiver 1300, and a processor 1310;

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

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

[0420] A charging data request is sent to the second functional entity, where the charging data request is a charging request related to an edge application server EAS, and the EAS is deployed on a satellite.

[0421] Optionally, the charging data request includes at least one of the following:

[0422] a first charging data request, the first charging data request being used to request charging an application service provider for deploying the EAS on a satellite;

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

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

[0425] Optionally, the processor further implements the following steps:

[0426] 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 billing-related parameter;

[0427] 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 EAS charging related parameters.

[0428] Optionally, the first EAS charging related parameter includes:

[0429] The IP address of the EAS;

[0430] or, the IP address of the EAS and the satellite return type of the satellite;

[0431] or, the IP address of the EAS and the identification information of the satellite;

[0432] Or, the IP address of the EAS, the satellite return type of the satellite, and the identification information of the satellite.

[0433] Optionally, the processor further implements the following steps:

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

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

[0436] Optionally, the second EAS charging-related parameter includes at least one of the following:

[0437] The IP address of the EAS;

[0438] The satellite return type of the satellite;

[0439] identification information of the satellite;

[0440] Incoming traffic of the EAS;

[0441] outgoing traffic of the EAS;

[0442] The storage status of the EAS;

[0443] The memory usage of the EAS.

[0444] Optionally, the third charging data request includes: an initial charging data request, a charging data update request and a charging data termination request;

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

[0446] Optionally, the satellite backhaul usage report includes at least one of the following:

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

[0448] Downlink traffic of onboard UPF;

[0449] The satellite return type of the satellite;

[0450] identification information of the satellite;

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

[0452] Onboard Data Network Access Identifier DNAI;

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

[0454] Optionally, the processor further implements the following steps:

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

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

[0457] Get the satellite return type;

[0458] Get the satellite's identity;

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

[0460] Optionally, the processor further implements the following steps:

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

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

[0463] The type of satellite backhaul has changed;

[0464] Get the changed satellite return type;

[0465] Get the updated satellite ID;

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

[0467] Optionally, the processor further implements the following steps:

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

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

[0470] Acquire a charging data request sent by a first functional entity, where the charging data request is a charging request related to an edge application server EAS, and the EAS is deployed on a satellite;

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

[0472] Optionally, the charging data request includes at least one of the following:

[0473] a first charging data request, the first charging data request being used to request charging an application service provider for deploying the EAS on a satellite;

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

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

[0476] Optionally, the first charging data request includes a first EAS charging related parameter, and the first EAS charging related parameter includes:

[0477] The IP address of the EAS;

[0478] or, the IP address of the EAS and the satellite return type of the satellite;

[0479] or, the IP address of the EAS and the identification information of the satellite;

[0480] Or, the IP address of the EAS, the satellite return type of the satellite, and the identification information of the satellite.

[0481] Optionally, 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:

[0482] The IP address of the EAS;

[0483] The satellite return type of the satellite;

[0484] identification information of the satellite;

[0485] Incoming traffic of the EAS;

[0486] outgoing traffic of the EAS;

[0487] The storage status of the EAS;

[0488] The memory usage of the EAS.

[0489] Optionally, the third charging data request includes: an initial charging data request, a charging data update request and a charging data termination request;

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

[0491] Optionally, the satellite backhaul usage report includes at least one of the following:

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

[0493] Downlink traffic of onboard UPF;

[0494] The satellite return type of the satellite;

[0495] identification information of the satellite;

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

[0497] Onboard Data Network Access Identifier DNAI;

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

[0499] Among them, Fig.13 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 1310 and various circuits of memory represented by memory 1320 are linked together. The bus architecture may also link together various other circuits such as peripherals, 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 on a transmission medium, which transmission medium may include a wireless channel, a wired channel, an optical cable, and other transmission media. 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.

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

[0501] It should be noted here that the above-mentioned network device provided in the embodiment of the present application can implement all the method steps implemented by 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.

[0502] like Fig.14 As shown, the embodiment of the present application further provides a backhaul billing processing device, which is applied to a first functional entity, and the device includes:

[0503] The first sending unit 1401 is configured to send a charging data request to the second functional entity, where the charging data request is a charging request related to an edge application server EAS, and the EAS is deployed on a satellite.

[0504] Optionally, the charging data request includes at least one of the following:

[0505] a first charging data request, the first charging data request being used to request charging an application service provider for deploying the EAS on a satellite;

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

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

[0508] Optionally, the first sending unit includes:

[0509] 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 billing related parameter;

[0510] The first sending subunit is used to send a first charging data request to the second functional entity according to the lifecycle management LCM notification of the EAS, where the first charging data request includes the EAS charging related parameters.

[0511] Optionally, the first EAS charging related parameter includes:

[0512] The IP address of the EAS;

[0513] or, the IP address of the EAS and the satellite return type of the satellite;

[0514] or, the IP address of the EAS and the identification information of the satellite;

[0515] Or, the IP address of the EAS, the satellite return type of the satellite, and the identification information of the satellite.

[0516] Optionally, the first sending unit includes:

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

[0518] 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 charging related parameter.

[0519] Optionally, the second EAS charging-related parameter includes at least one of the following:

[0520] The IP address of the EAS;

[0521] The satellite return type of the satellite;

[0522] identification information of the satellite;

[0523] Incoming traffic of the EAS;

[0524] outgoing traffic of the EAS;

[0525] The storage status of the EAS;

[0526] The memory usage of the EAS.

[0527] Optionally, the third charging data request includes: an initial charging data request, a charging data update request and a charging data termination request;

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

[0529] Optionally, the satellite backhaul usage report includes at least one of the following:

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

[0531] Downlink traffic of onboard UPF;

[0532] The satellite return type of the satellite;

[0533] identification information of the satellite;

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

[0535] Onboard Data Network Access Identifier DNAI;

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

[0537] Optionally, the first sending unit is used to send the initial charging data request to the second functional entity when a first trigger event is met;

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

[0539] Get the satellite return type;

[0540] Get the satellite's identity;

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

[0542] Optionally, the first sending unit is used to send the charging data update request to the second functional entity when a second trigger event is met;

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

[0544] The type of satellite backhaul has changed;

[0545] Get the changed satellite return type;

[0546] Get the updated satellite ID;

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

[0548] Optionally, the device of the embodiment of the present application further includes:

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

[0550] It should be noted here that the above-mentioned device provided in the embodiment of the present application can implement all the method steps implemented by 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.

[0551] like Fig.15 As shown, the embodiment of the present application further provides a backhaul billing processing device, which is applied to a second functional entity, and the device includes:

[0552] A first acquiring unit 1501 is configured to acquire a charging data request sent by a first functional entity, where the charging data request is a charging request related to an edge application server EAS, and the EAS is deployed on a satellite;

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

[0554] Optionally, the charging data request includes at least one of the following:

[0555] a first charging data request, the first charging data request being used to request charging an application service provider for deploying the EAS on a satellite;

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

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

[0558] Optionally, the first charging data request includes a first EAS charging related parameter, and the first EAS charging related parameter includes:

[0559] The IP address of the EAS;

[0560] or, the IP address of the EAS and the satellite return type of the satellite;

[0561] or, the IP address of the EAS and the identification information of the satellite;

[0562] Or, the IP address of the EAS, the satellite return type of the satellite, and the identification information of the satellite.

[0563] Optionally, 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:

[0564] The IP address of the EAS;

[0565] The satellite return type of the satellite;

[0566] identification information of the satellite;

[0567] Incoming traffic of the EAS;

[0568] outgoing traffic of the EAS;

[0569] The storage status of the EAS;

[0570] The memory usage of the EAS.

[0571] Optionally, the third charging data request includes: an initial charging data request, a charging data update request and a charging data termination request;

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

[0573] Optionally, the satellite backhaul usage report includes at least one of the following:

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

[0575] Downlink traffic of onboard UPF;

[0576] The satellite return type of the satellite;

[0577] identification information of the satellite;

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

[0579] Onboard Data Network Access Identifier DNAI;

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

[0581] It should be noted here that the above-mentioned device provided in the embodiment of the present application can implement all the method steps implemented by 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.

[0582] It should be noted that the division of units in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional unit in each embodiment of the present application may be integrated into a processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0583] 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 application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program codes.

[0584] In some embodiments of the present application, a processor-readable storage medium is also provided, which stores program instructions, and 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 effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0585] The terminal device involved in the embodiment of the present application may be a device that provides voice and / or data connectivity to a user, a handheld device with a 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 a 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 a "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 language and / or data with a wireless 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, and a user device, but is not limited in the embodiments of the present application.

[0586] The network device (or network side device) involved in the embodiment of the present application may be a base station, which may include multiple cells providing services for the terminal. Depending on the specific application scenario, the base station may also be called an access point, or may be a device in the access network that communicates with the wireless terminal device through one or more sectors on the air interface, or other names. The network device may be used to interchange received air frames with Internet Protocol (IP) packets, and serve 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 the attribute management of the air interface. For example, the network device involved in the embodiments of the present application may be a network device (Base TransceiverStation, BTS) in the Global System for Mobile communications (Global System for Mobile communications, GSM) or Code Division Multiple Access (Code Division Multiple Access, CDMA), or a network device (NodeB) in Wide-band Code Division Multiple Access (WCDMA), or an evolutionary network device (evolutional Node B, eNB or e-NodeB) in the Long Term Evolution (Long Term Evolution, LTE) system, a 5G base station (gNB) in the 5G network architecture (next generation system), or a home evolved Node B (Home evolved Node B, HeNB), a relay node, a home base station (femto), a pico base station (pico), etc., which is not limited in the embodiments of the present application. 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 arranged geographically separately.

[0587] 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 form and number of antenna combinations, MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO or massive-MIMO, or it can be diversity transmission, precoded transmission or beamforming transmission, etc.

[0588] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) that contain computer-usable program code.

[0589] The present application 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 application. 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 generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0590] 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 an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0591] 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, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

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

Claims

1. A method for processing backhaul billing, executed by a first functional entity, characterized in that: The method comprises: A charging data request is sent to the second functional entity, where the charging data request is a charging request related to an edge application server EAS, and the EAS is deployed on a satellite.

2. The method according to claim 1, characterized in that 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 an application service provider for deploying the 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, characterized in that 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 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 EAS charging related parameters.

4. The method according to claim 3, characterized in that The first EAS charging related parameters include: The IP address of the EAS; or, the IP address of the EAS and the satellite return type of the satellite; or, the IP address of the EAS and the identification information of the satellite; Or, the IP address of the EAS, the satellite return type of the satellite, and the identification information of the satellite.

5. The method according to claim 2, characterized in that: 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; A second charging data request is sent to a second functional entity according to the performance report data, where the second charging data request includes a second EAS charging related parameter.

6. The method according to claim 5, characterized in that 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.

7. The method according to claim 2, characterized in that 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, characterized in that 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, characterized in that: 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, characterized in that 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, characterized in that: Also includes: 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, characterized in that: The method comprises: Acquire a charging data request sent by a first functional entity, where the charging data request is a charging request related to an edge application server EAS, and the EAS is deployed on a satellite; 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, characterized in that 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 an application service provider for deploying the 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.

14. The method according to claim 13, characterized in that The first charging data request includes a first EAS charging related parameter, and the first EAS charging related parameter includes: The IP address of the EAS; or, the IP address of the EAS and the satellite return type of the satellite; or, the IP address of the EAS and the identification information of the satellite; Or, the IP address of the EAS, the satellite return type of the satellite, and the identification information of the satellite.

15. The method according to claim 13, characterized in that 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.

16. The method according to claim 13, characterized in that 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, characterized in that 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 onboard EAS; Onboard Data Network Access Identifier DNAI; The on-board UPF is the UPF corresponding to the EAS.

18. A network device, characterized in that: Including memory, transceiver, processor; A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: A charging data request is sent to the second functional entity, where the charging data request is a charging request related to an edge application server EAS, and the EAS is deployed on a satellite.

19. The network device according to claim 18, characterized in that: 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 an application service provider for deploying the 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, characterized in that: 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 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 EAS charging related parameters.

21. The network device according to claim 20, characterized in that: The first EAS charging related parameters include: The IP address of the EAS; or, the IP address of the EAS and the satellite return type of the satellite; or, the IP address of the EAS and the identification information of the satellite; Or, the IP address of the EAS, the satellite return type of the satellite, and the identification information of the satellite.

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

23. The network device according to claim 22, characterized in that: 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.

24. The network device according to claim 19, characterized in that: 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, characterized in that: 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, characterized in that: 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, characterized in that: 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, characterized in that: 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, characterized in that: Including memory, transceiver, processor; A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: Acquire a charging data request sent by a first functional entity, where the charging data request is a charging request related to an edge application server EAS, and the EAS is deployed on a satellite; 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, characterized in that: 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 an application service provider for deploying the 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.

31. The network device according to claim 30, characterized in that: The first charging data request includes a first EAS charging related parameter, and the first EAS charging related parameter includes: The IP address of the EAS; or, the IP address of the EAS and the satellite return type of the satellite; or, the IP address of the EAS and the identification information of the satellite; Or, the IP address of the EAS, the satellite return type of the satellite, and the identification information of the satellite.

32. The network device according to claim 30, characterized in that: 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.

33. The network device according to claim 30, characterized in that: 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, characterized in that: 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, characterized in that: The device comprises: The first sending unit is used to send a charging data request to the second functional entity, where the charging data request is a charging request related to an edge application server EAS, and the EAS is deployed on a satellite.

36. A backhaul billing processing device, applied to a second functional entity, characterized in that: The device comprises: A first acquisition unit is used to acquire a charging data request sent by a first functional entity, where the charging data request is a charging request related to an edge application server EAS, and the EAS is deployed on a satellite; 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.

37. A processor-readable storage medium, characterized in that: 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 backhaul billing processing method as described in any one of claims 1 to 11, or to execute the steps of the backhaul billing processing method as described in any one of claims 12 to 17.

Images