WO2022193971A1 - Procédé et dispositif de charge - Google Patents

Procédé et dispositif de charge Download PDF

Info

Publication number
WO2022193971A1
WO2022193971A1 PCT/CN2022/079455 CN2022079455W WO2022193971A1 WO 2022193971 A1 WO2022193971 A1 WO 2022193971A1 CN 2022079455 W CN2022079455 W CN 2022079455W WO 2022193971 A1 WO2022193971 A1 WO 2022193971A1
Authority
WO
WIPO (PCT)
Prior art keywords
charging
data
ees
network device
app
Prior art date
Application number
PCT/CN2022/079455
Other languages
English (en)
Chinese (zh)
Inventor
周汉
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2022193971A1 publication Critical patent/WO2022193971A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H04L12/1407—Policy-and-charging control [PCC] architecture
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/50—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP for cross-charging network operators

Definitions

  • the present application relates to the field of communications, and more particularly, to a charging method and device.
  • SA standalone
  • MEC mobile edge computing
  • EES edge enabler server
  • API application programming interface
  • CHF charging function
  • each EES When a large number of EESs interact with CHFs to obtain CDRs, since EESs are deployed at the edge of the network, and CHFs are generally deployed at the center of the network, each EES has an interface with the CHF, so the CHF needs to sense and communicate with the CHF.
  • a connection is established between each EES, which will make the networking between the EES and the CHF very complicated, and the connection between the CHF and each EES is based on a service interface, which requires the maintenance of the connection state between the EES and each CHF, The maintenance of a large number of stateful connections can be a heavy burden on CHF.
  • the present application provides a charging method, which can reduce the connection burden between the CHF and a large number of EESs when acquiring the charging CDR.
  • a charging method executed in an edge configuration server ECS, the method includes: acquiring first data, where the first data is aggregated data of a first APP collected by at least one edge-enabled server EES statistics Network resource usage data; determine first charging data according to the first data, and the first charging data is used by the charging system to charge the first APP; report the first charging data to the charging system Billing data.
  • the ECS is enabled to aggregate network resource usage data counted by at least one EES, and the charging data is generated and reported to the charging system (CHF).
  • This method effectively reduces the need to maintain a connection between the CHF and each EES. burden caused by the state.
  • the type of the network resource usage data includes: the first traffic usage, the first duration usage, or the first number of charging events.
  • the obtaining the first data includes: obtaining first charging policy information, where the first charging policy information is used to indicate the first data of the first APP. a charging policy; determining a first subscription rule according to the first charging policy information and the quantity of the at least one EES, so that each EES corresponds to a second charging policy; determining a first subscription rule according to the second charging policy Subscription request information, the first subscription request information corresponds to a first EES, and the first EES is one of the at least one EES; send the first subscription request information to the first EES; obtain the first EES data, where the first data corresponds to the first subscription request information.
  • the ECS is enabled to request different types of network resource usage data from different EESs for statistics, and the charging method is enabled to be more flexible.
  • the first charging policy information includes: the first traffic usage, the first duration usage, the first number of charging events, the first reporting trigger condition, the first A charging trigger condition or the identifier of the first APP.
  • the reporting the first charging data to the charging system includes: reporting the first charging data to the charging system according to the first reporting trigger condition 1 Billing data.
  • the first subscription request information includes an identifier of the first APP and a second charging policy corresponding to the first EES.
  • the first charging event includes an application program interface API call.
  • a charging method executed in an edge-enabled server EES, the method includes: collecting first data, where the first data provides the EES with network resources generated by providing a first application APP service usage data; sending the first data.
  • the EES sends the statistical network resource usage data to the ECS, enables the ECS to count the network resource usage data of multiple EESs, generates charging data and reports it to the charging system (CHF).
  • This method effectively reduces the The burden of maintaining the connection state between the CHF and each EES is eliminated.
  • the type of the network resource usage data includes: the first traffic usage, the first duration usage, or the first number of charging events.
  • the first charging event includes an application program interface API call.
  • the method includes: receiving first subscription request information, where the first subscription request information is used to indicate the amount of the network resource usage data collected by the EES statistics Type; statistics the first data according to the first subscription request information.
  • the EES counts the network resource usage data according to the first subscription request information, so that the ECS can count different types of network resource usage data sent by different EESs, and the billing method is more flexible.
  • a communication device in a third aspect, includes various units for implementing the first aspect or any possible implementation manner of the first aspect.
  • the communication device may be a network device or a baseband chip.
  • a communication device in a fourth aspect, includes various units for performing the second aspect or any possible implementation manner of the second aspect, wherein the communication device may be a network device or a baseband chip.
  • a communication device including a transceiver component and a processor, so that the communication device executes the first aspect or the method in any possible implementation manner of the first aspect.
  • the communication device may be a network device or a baseband chip. If the communication device is a network device, the transceiver component may be a transceiver, and if the communication device is a baseband chip, the transceiver component may be an input/output circuit of the baseband chip.
  • a communication device including a transceiver component and a processor.
  • the communication device is caused to perform the method of the second aspect or any possible implementation manner of the second aspect.
  • the communication device may be a network device or a baseband chip. If the communication device is a network device, the transceiver component may be a transceiver, and if the communication device is a baseband chip, the transceiver component may be an input/output circuit of the baseband chip.
  • a computer program product comprising: computer program code, when the computer program code is run by a network device, the network device causes the network device to execute the first aspect or any of the first aspects.
  • a computer program product comprising: computer program code, when the computer program code is run by a network device, the network device is made to execute the second aspect or any of the second aspect.
  • a computer-readable medium stores program codes, the program codes including instructions for executing the method in the first aspect or any possible implementation manner of the first aspect .
  • a computer-readable medium stores program code, the program code comprising instructions for executing the method in the second aspect or any possible implementation manner of the second aspect .
  • the ECS generates charging data and reports it to the charging system (CHF) by aggregating the network resource usage data collected by at least one EES.
  • CHF charging system
  • This method effectively reduces the need to maintain a connection state between the CHF and each EES. burden caused.
  • the ECS can request different types of network resource usage data from different EESs for statistics, enabling more flexible billing methods.
  • FIG. 1 is a schematic diagram of an example of a network architecture 100 applied by an embodiment of the present application
  • FIG. 2 is a schematic interaction diagram of a method 200 for charging according to an embodiment of the present application
  • FIG. 3 is a schematic interaction diagram of a method 300 for charging according to an embodiment of the present application.
  • FIG. 4 is a schematic block diagram of an example of a network device according to an embodiment of the present application.
  • FIG. 5 is a schematic block diagram of another example of a network device according to an embodiment of the present application.
  • FIG. 6 is a schematic block diagram of still another example of a network device according to an embodiment of the present application.
  • FIG. 7 is a schematic block diagram of still another example of a network device according to an embodiment of the present application.
  • GSM global system of mobile communication
  • CDMA code division multiple access
  • WCDMA wideband code division multiple access
  • GPRS general packet radio service
  • long term evolution long term evolution
  • LTE long term evolution
  • LTE frequency division duplex frequency division duplex
  • TDD time division duplex
  • UMTS universal mobile telecommunication system
  • WiMAX worldwide interoperability for microwave access
  • the terminal equipment in the embodiments of the present application may also be referred to as user equipment (user equipment, UE), access terminal, terminal equipment unit (subscriber unit), terminal equipment station, mobile station, mobile station (mobile station, MS), A remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, terminal device proxy or terminal device device.
  • Terminal devices may include various wireless communication capable handheld devices, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to a wireless modem. May also include subscriber units, cellular phones, smart phones, wireless data cards, personal digital assistant (PDA) computers, tablet computers, wireless modems, handheld devices ), laptop computer (laptop computer), machine type communication (MTC) terminal, station (station, ST) in wireless local area networks (WLAN).
  • PDA personal digital assistant
  • MTC machine type communication
  • station station, ST
  • WLAN wireless local area networks
  • the network device in this embodiment of the present application may be a device for communicating with a terminal device, and the network device may be a global system of mobile communication (GSM) system or a code division multiple access (code division multiple access, CDMA)
  • GSM global system of mobile communication
  • CDMA code division multiple access
  • the base station (base transceiver station, BTS) in the LTE system can also be the base station (nodeB, NB) in the wideband code division multiple access (WCDMA) system, or the evolutionary base station (evolutional base station) in the LTE system.
  • nodeB eNB or eNodeB
  • it can also be a wireless controller in a cloud radio access network (CRAN) scenario
  • the network device can be a relay station, an access point, a vehicle-mounted device, a wearable device, and 5G
  • the network equipment in the network or the network equipment in the future evolved PLMN network, etc., are not limited in the embodiments of the present application.
  • FIG. 1 is a network architecture 100 applied to an embodiment of the present application, and each network element that may be involved in the network architecture is described respectively.
  • Terminal device 110 For the description of the terminal device, reference may be made to the above description, which will not be repeated here.
  • (wireless) access network (radio access network, (R)AN) network element 120 used to provide network access functions for authorized terminal equipment in a specific area, and can use different quality according to the level of terminal equipment, service requirements, etc. transmission tunnel.
  • R radio access network
  • the (R)AN network element can manage wireless resources, provide access services for terminal equipment, and then complete the forwarding of control signals and terminal equipment data between the terminal equipment and the core network.
  • the (R)AN network element can also be understood as a traditional network. in the base station.
  • network element may also be referred to as an entity, a device, an apparatus, or a module, etc., which is not particularly limited in this application.
  • the description of “network element” is omitted in some descriptions.
  • the (R)AN network element is abbreviated as (R)AN, in this case, the “(R)AN ”)AN network element” should be understood as (R)AN network element or (R)AN entity, and below, the description of the same or similar situations is omitted.
  • User plane network element 130 used for packet routing and forwarding, and quality of service (quality of service, QoS) processing of user plane data, and the like.
  • the user plane network element may be a user plane function (UPF) network element.
  • the user plane network element may still be the UPF network element, or may have other names, which are not limited in this application.
  • Edge enabler server (EES) 140 used to manage each edge application server (EAS) deployed in the same edge data network (EDN), such as EAS registration, Domain name system (domain name system, DNS) resolution, etc.
  • EES can invoke the capability opening function of the 3GPP network.
  • the EES may be a control network element (such as a MEC platform (MEC platform, MEP) or a management network element in a mobile edge computing (MEC) node. It should be noted that the EES may belong to The operator may also belong to a third party. In a possible implementation manner, the EES in the charging system belongs to the operator.
  • MEC platform MEC platform
  • MEC mobile edge computing
  • An edge application server (edge application server, EAS) 141 provides services for data services of the UE, for example, provides application data streams to the UE.
  • EAS may be deployed in multiple EESs, for example, one EAS corresponds to one application (application, APP), the EAS includes multiple EAS instances, and one EAS instance may be deployed on one EES , in other words, one APP corresponds to multiple EESs.
  • application application
  • APP application
  • the EES can be used to count the network resource usage generated when the EAS provides the application data stream to the UE, and report it to the Charging Trigger Function (CTF).
  • CTF Charging Trigger Function
  • the type of network resource usage for APP statistics can be configured in the EES It can also be determined according to the subscription request information sent by the edge configuration server (ECS), and the type of network resource usage includes at least one of the following:
  • Traffic usage is the traffic consumed by the service accessed by the UE (service corresponding to the application data stream);
  • the duration usage is the duration consumed by the UE to access the service
  • the number of charging events is the number of specific actions performed by the UE to access the service, for example, the charging event is the action of opening APP#1 when the UE accesses APP#1, or opening a link when accessing a web page Action
  • CTF can generate billing data according to the number of billing events, or the number of application programming interface (application programming interface, API) calls, the API call number data is the number of times the EAS calls the EES API.
  • API application programming interface
  • the EES can count the network resource usage generated by the EAS according to the user granularity, and generate network resource usage data, that is, the statistics of the network resource usage of at least one APP corresponding to each user, and the ECS can differentiate the EES according to the APP ID. The reported network resource usage.
  • the EES can count the network resource usage generated by the EAS according to the application granularity, and generate network resource usage data, that is, statistics on the network resource usage corresponding to each application (service), and the network resource usage can be derived from for multiple users.
  • Access management network element 150 mainly used for mobility management and access management, etc., and can be used to implement other functions except session management in mobility management entity (mobility management entity, MME) functions, for example, legal Monitoring and access authorization/authentication functions.
  • mobility management entity mobility management entity, MME
  • the access management network element may be an access and mobility management function (AMF) network element.
  • AMF access and mobility management function
  • the access management network element may still be an AMF network element, or may have other names, which are not limited in this application.
  • Session management network element 160 mainly used for session management, Internet Protocol (IP) address allocation and management of terminal equipment, selection of endpoints that can manage user plane functions, policy control and charging function interfaces, and downlink data notification, etc.
  • IP Internet Protocol
  • the session management network element may be a session management function (session management function, SMF) network element.
  • SMF session management function
  • the session management network element may still be an SMF network element, or may have other names, which are not limited in this application.
  • Policy control network element 170 a unified policy framework for guiding network behavior, providing policy rule information and the like for control plane functional network elements (eg, AMF, SMF network elements, etc.).
  • control plane functional network elements eg, AMF, SMF network elements, etc.
  • the policy control network element may be a policy and charging rules function (policy and charging rules function, PCRF) network element.
  • policy control network element may be a policy control function (PCF) network element.
  • PCF policy control function
  • the policy control network element may still be the PCF network element, or may have other names, which are not limited in this application.
  • Storage function network element 180 used for maintaining real-time information of all network function services in the network.
  • the network storage network element may be a network repository function (NRF) network element.
  • NRF network repository function
  • the network storage network element may still be an NRF network element, or may have other names, which are not limited in this application.
  • Edge configuration server (ECS) 190 maintains the information of each EDN, including service scope and EES address.
  • Charging trigger function (CTF) 191 used to subscribe to one or more EESs to report network resource usage data, and generate charging data according to the network resource usage data reported by one or more EESs, and send it to the EES.
  • the billing system reports the billing data.
  • the CTF may also generate and report charging data according to a reporting trigger condition, where the reporting trigger condition is a condition (charging threshold) that is satisfied when the EES reports the network resource usage to the CTF (EES), and the reporting trigger Conditions (billing thresholds) include at least one of the following types:
  • the traffic usage threshold indicates that when the traffic consumed by the service accessed by the UE through the EAS (service corresponding to the application data flow) reaches the traffic usage threshold, the EES reports the traffic usage to the CTF;
  • the duration usage threshold is the duration threshold consumed by the UE accessing the service (service corresponding to the application data flow) through the EAS.
  • the duration threshold reaches the duration usage threshold, the EES reports the duration usage to the CTF;
  • the number of charging events is the number of specific actions performed by the UE to access the service, for example, the charging event is the action of opening APP#1 when the UE accesses APP#1, or opening a page when accessing a web page
  • the linked action, or the threshold of the number of application programming interface (API) calls is the number of times the EAS calls the API of the EES, and the CTF can generate charging data according to the number of charging events.
  • the EES reports the number of charging events to the CTF.
  • the CTF subscribes the network resource usage data report to the EES according to the charging trigger condition.
  • the CTF can obtain the charging trigger condition through the session management process of the user, or can obtain the charging trigger condition through the configured method, and the charging trigger condition includes at least one of the following types:
  • Threshold reporting The CTF instructs the EES to report to the CTF when the statistics of the network resource usage reaches the threshold.
  • the network resource usage includes the above-mentioned traffic usage, duration usage, or the number of API calls.
  • the CTF instructs the EES to periodically report the statistical network resource usage to the CTF.
  • the network resource usage includes the above-mentioned traffic usage, duration usage, or the number of API calls.
  • the CTF instructs the EES to report the statistics of the network resource usage to the CTF according to the triggered event.
  • the network resource usage includes the above-mentioned traffic usage, duration usage or the number of API calls (such as UE offline events).
  • the CTF may be an independent functional network element, or may be integrated with other functional network elements, such as integrated in the ECS. It should be noted that this application takes the integration of CTF into ECS as an example to describe the involved solution. Therefore, the functions of ECS can include the functions of CTF, but CTF can also implement this solution as an independent functional network element, which is not limited in this application. .
  • the ECS is used to aggregate the network resource usage data reported by each EES, and report the aggregated network resource usage data to the billing system.
  • the network resource usage data reported by the EES is counted according to the granularity of the APP, and the ECS may aggregate the network resource usage data reported by multiple EESs belonging to the same APP and report it to the billing system.
  • the network resource usage data reported by the EES is counted according to the granularity of the user, the information including the network resource usage data reported by the EES also includes the APP ID, and the ECS summarizes the corresponding APPs according to the APP ID.
  • the data on the network resource usage is reported to the billing system.
  • the ECS is further used to acquire the charging policy information of the APP.
  • the ECS determines the subscription rule according to the charging policy information.
  • the ECS can also determine the subscription rule in combination with the number of EESs, use the charging policy information to indicate the network resource usage data according to the traffic usage, and report the trigger condition (charging threshold) as reaching 10G Taking reporting as an example, then, assuming that the number of EES is 2, the subscription rule determined by ECS is: each EES counts network resource usage data according to traffic usage, and reports it to ECS when it reaches 5G.
  • the ECS generates billing data according to the network resource usage data reported by the EES, and reports it to the billing system.
  • the ECS can also be used to provide the registration service of the EES, and then determine the subscription rule according to the registration information obtained in the registration service and the charging policy information, where the registration information includes the information of the EAS instance, for example, the EAS (EAS instance) the corresponding APP ID, or the MEC service list (service list) required for the EAS to run.
  • the ECS assigns the charging threshold to each EAS instance corresponding to the EAS (in other words, assigns the charging threshold to the APP) according to the EAS (EAS instance) information and the charging policy obtained in the registration service.
  • EES Corresponding EES
  • the subscription rule can be set so that when the traffic usage of EAS#1 reaches 4G, its EES reports the network resource usage data; when the traffic usage of EAS#2 reaches 3G, its affiliated EES reports network resource usage data ; When the traffic usage of EAS#3 reaches 3G, the EES to which it belongs reports network resource usage data.
  • ECS sends the subscription rule to EES, and EES performs corresponding statistics and reporting according to the subscription rule.
  • ECS aggregates the network resource usage data reported by each EES, generates the corresponding billing data for each APP in combination with the APP ID, and reports it to the billing system.
  • the charging policy information is used to indicate the type of network resource usage data reported by the EES to the ECS, and the content may include at least one of the following:
  • the traffic usage is the traffic consumed by the service accessed by the UE through the EAS (the service corresponding to the application data stream), and the ECS generates the charging information of the APP according to the traffic usage;
  • Duration usage is the time consumed by the UE to access the service (service corresponding to the application data stream) through the EAS, and the ECS generates the charging information of the APP according to the duration usage;
  • the number of charging events is the number of specific actions performed by the UE to access the service, for example, the charging event is the action of opening APP#1 when the UE accesses APP#1, or opening a link when accessing a web page action, or the number of application programming interface (application programming interface, API) calls, the data of the number of API calls is the number of times the API corresponding to the service is called when the UE accesses the service (the service corresponding to the application data stream) through the EAS.
  • the number of charging events generates the charging information of APP#1;
  • the ECS obtains charging policies from other network functions (NFs), such as subscription databases or PCFs.
  • NFs network functions
  • PCFs PCFs
  • the charging policy and the APP are associated with the APP's identity (ID) (that is, the ECS can obtain the mapping relationship between the charging policy and the APP ID), and one APP ID corresponds to one charging Policy, the charging policy-related information obtained by ECS includes the corresponding APP ID, and ECS can determine the APP corresponding to the charging policy according to the APP ID.
  • ID the APP's identity
  • Data management network element 1100 used for processing terminal equipment identification, access authentication, registration, and mobility management.
  • the data management network element may be a unified data management (unified data management, UDM) network element.
  • UDM unified data management
  • the unified data management may still be a UDM network element, or may have other names, which are not limited in this application.
  • Billing network element used for pricing, deduction, quota and billing parameter delivery, processing quota usage reported by SMF, etc.
  • the charging function network element may be a charging function network element (charging function, CHF).
  • the charging network element may still be the CHF network element, or may have other names, which are not limited in this application.
  • network function entities such as AMF, SMF, PCF, GMF, and UDM are called network function (NF) network elements; or, in other network architectures, AMF, SMF, PC A set of network elements such as GMF, UDM, etc. can be called a control plane function (CPF) network element.
  • NF network function
  • CPF control plane function
  • the embodiments of the present application describe various embodiments in conjunction with core network equipment, wherein the functions of the core network are mainly to provide user connection, user management, and service bearer, as the bearer network provides an interface to an external network.
  • the establishment of user connection includes functions such as mobility management (mobile management, MM), call management (connection management, CM), switching/routing, and recording notification.
  • User management includes user description, quality of service (QoS), user communication records (accounting), virtual home environment (VHE) and security (corresponding security measures provided by the authentication center include Security management of mobile services and security processing of access to external networks).
  • Bearer connections include access to external public switched telephone networks (PSTNs), external circuit data networks and packet data networks, the internet and intranets, and mobile phone texting on the mobile network itself Service (short message service, SMS) server and so on.
  • PSTNs public switched telephone networks
  • SMS short message service
  • the basic services that the core network can provide include mobile office, e-commerce, communication, entertainment services, travel and location-based services, telemetry, simple messaging (surveillance control), and so on.
  • FIG. 2 is a schematic interaction diagram of a charging method 200 according to an embodiment of the present application.
  • ECS#1 obtains the charging policy information #A corresponding to APP#1, the type of the charging policy information #A and the method of obtaining the charging policy information #A refer to the previous description. It is not repeated here.
  • the charging policy information #A includes an APP #1 ID
  • the ECS #1 determines the APP #1 corresponding to the charging policy information #A according to the APP #1 ID.
  • the EAS instance corresponding to APP#1 is deployed on multiple EESs as an example, and the multiple EESs include EES#1 as an example for description.
  • EES#1 as an example for description.
  • the following descriptions about the related actions of EES#1 are all applicable to the multiple EESs. In order to make the description clearer, only the action descriptions of EES#1 are taken as an example here.
  • EES#1 sends registration request information #B to ECS#1, ECS#1 receives the information #B, and the information #B includes the EAS-related information corresponding to APP#1, such as the APP#1 ID corresponding to the EAS, which is required for the operation of the EAS. list of MEC services, etc.
  • ECS#1 After ECS#1 successfully receives information #B, it sends response information to EES#1.
  • ECS#1 determines a subscription rule for the network resource usage data of the EES corresponding to APP#1 according to the charging policy information #A, and generates subscription request information #C according to the subscription rule.
  • ECS#1 allocates the charging threshold corresponding to APP#1 to the APP#1 according to the charging policy information #A (optionally, there may also be registration request information #B). For each EAS instance that provides services (each EAS instance corresponds to one EES), please refer to the relevant description in the method 100 for the specific allocation method, which will not be repeated here.
  • ECS#1 determines a subscription rule for the network resource usage data of the EAS instance corresponding to APP#1 according to the allocation result, and generates subscription request information #C according to the subscription rule.
  • the subscription request information #C includes the APP#1 ID
  • the charging policy information #A corresponding to the APP#1 indicates the type of network resource usage data collected by the EES#1.
  • ECS#1 sends subscription request information #C to EES#1, and EES#1 receives the information #C.
  • EES#1 sends subscription response information #D to ECS#1, and ECS#1 receives the information #D.
  • EES#1 counts the network resource usage data of the corresponding EAS instance according to the subscription request information #C, and generates subscription notification information #E.
  • EES#1 sends subscription notification information #F to ECS#1, and ECS#1 receives the information #F.
  • ECS#1 summarizes the network resource usage data corresponding to each EES corresponding to APP#1 according to the subscription notification information #F sent by each EES (including EES#1), and generates charging data corresponding to APP#1, and Report to the billing system.
  • ECS#1 reports the charging data corresponding to APP#1 to the charging system (eg CHF).
  • FIG. 3 is a schematic interaction diagram of a charging method 300 according to another embodiment of the present application.
  • UE#1 initiates a registration request to ECS#1 through the core network, and requests to access edge service APP#1, and ECS#1 provides APP#1 to UE#1 according to the registration request of UE#1 Corresponding EES (including EES#1).
  • ECS#1 sends charging policy request information #G corresponding to APP#1 to PCF#1, where the charging policy request information #G includes APP#1 ID.
  • the charging policy request information #G further includes a list of MEC services required for the operation of the EAS corresponding to APP #1.
  • the charging policy request information #G further includes the address of ECS #1.
  • PCF #1 determines charging policy information #A according to charging policy request information #G.
  • PCF#1 determines the charging policy information #A of UE#1 for APP#1 according to the service subscription of UE#1 and the APP#1 ID in the charging policy request information #G.
  • For the description of the charging policy information #A reference may be made to the description of the charging policy information in the method 100, which will not be repeated here.
  • PCF#1 sends charging policy information #A to ECS#1.
  • PCF#1 addresses ECS#1 according to the address of ECS#1, and sends charging policy information #A to ECS#1.
  • PCF#1 addresses to ECS#1 according to the routing configuration information, and sends charging policy information #A to ECS#1.
  • ECS#1 determines a subscription rule for the network resource usage data of the EAS corresponding to APP#1 according to the charging policy information #A, sends the subscription rule to each EES, and uses the subscription notification information #F reported by each EES , summarize the network resource usage data corresponding to each EES corresponding to APP#1, and generate charging data information #H.
  • the interaction between the ECS#1 and the EES can be referred to the description in the method 200, and details are not repeated here.
  • ECS #1 sends charging data information #H to CHF #1, and CHF #1 receives the charging data information #H.
  • FIG. 4 is a schematic block diagram of an example of a network device according to an embodiment of the present application.
  • the network device 400 (which may also be referred to as a first network device, such as an ECS) includes:
  • a receiving unit 410 configured to acquire first data, where the first data is aggregated network resource usage data of the first APP counted by at least one edge-enabled server EES;
  • a processing unit 420 configured to determine first charging data according to the first data, where the first charging data is used by the charging system to charge the first APP;
  • the sending unit 430 is configured to report the first charging data to the charging system.
  • the type of the network resource usage data includes: the first traffic usage, the first duration usage, or the first number of charging events.
  • the receiving unit 410 is further configured to acquire first charging policy information, where the first charging policy information is used to indicate the first charging policy of the first APP;
  • the processing unit 420 is further configured to determine a first subscription rule according to the first charging policy information and the quantity of the at least one EES, so that each EES corresponds to a second charging policy;
  • the processing unit 420 is further configured to determine first subscription request information according to the second charging policy, where the first subscription request information corresponds to a first EES, and the first EES is one of the at least one EES;
  • the sending unit 430 is further configured to send the first subscription request information to the first EES;
  • the receiving unit 410 is further configured to acquire first data, where the first data corresponds to the first subscription request information.
  • the first charging policy information includes: the first traffic usage, the first duration usage, the first number of charging events, the first reporting trigger condition, the first charging trigger condition or the first charging trigger condition.
  • An APP logo is included in the first charging policy information.
  • the sending unit 430 is further configured to report the first charging data to the charging system according to the first reporting trigger condition.
  • the first subscription request information includes an identifier of the first APP and a second charging policy corresponding to the first EES.
  • the first charging event includes an application program interface API call.
  • each unit in the network device 400 provided in this embodiment of the present application and the above-mentioned other operations or functions are implemented by the network device (for example, in the method 100, method 200, or method 300 for charging provided by the embodiment of the present application, respectively).
  • ECS ECS
  • FIG. 5 is a schematic block diagram of still another example of a network device according to an embodiment of the present application.
  • the network device 500 also referred to as a second network device, such as EES
  • the network device 500 includes:
  • a processing unit 520 configured to count first data, where the first data is network resource usage data generated by the network device providing the first application APP service;
  • the sending unit 530 is configured to send the first data.
  • the type of the network resource usage data includes: the first traffic usage, the first duration usage, or the first number of charging events.
  • the first charging event includes an application program interface API call.
  • the network device 500 further includes:
  • a receiving unit 510 configured to receive first subscription request information, where the first subscription request information is used to indicate the type of the network resource usage data collected by the network device;
  • the processing unit 520 is further configured to count the first data according to the first subscription request information.
  • each unit in the network device 500 provided in this embodiment of the present application and the above-mentioned other operations or functions are implemented by the network device (for example, in the method 100, method 200, or method 300 for charging provided by the embodiment of the present application, respectively).
  • EES EES
  • FIG. 6 is a schematic block diagram of another example of a network device according to an embodiment of the present application.
  • the network device 600 includes a transceiver 610 and a processor 620 .
  • the processor 620 is configured to support the network device to perform the corresponding functions of the network device 400 (eg, ECS) in the above method.
  • the network device 600 may further include a memory 630 , where the memory 630 is coupled to the processor 620 and stores necessary program instructions and data of the network device 600 .
  • the processor 620 is specifically configured to execute the instructions stored in the memory 630, and when the instructions are executed, the network device 600 executes the method performed by the network device 400 in the foregoing methods.
  • the network device 400 shown in FIG. 4 may be implemented by the network device 600 shown in FIG. 6 .
  • the receiving unit 410 and the transmitting unit 430 shown in FIG. 4 may be implemented by the transceiver 610
  • the processing unit 420 may be implemented by the processor 620 .
  • FIG. 7 is a schematic block diagram of another example of a network device according to an embodiment of the present application.
  • the network device 700 includes a transceiver 710 and a processor 720, and the processor 720 is configured to support the network device to perform the corresponding functions of the network device 500 (eg, EES) in the above method.
  • the network device 700 may further include a memory 730 , where the memory 730 is coupled to the processor 720 and stores necessary program instructions and data of the network device 700 .
  • the processor 720 is specifically configured to execute the instructions stored in the memory 730. When the instructions are executed, the network device 700 executes the method performed by the network device 500 in the above method.
  • the network device 500 shown in FIG. 5 may be implemented by the network device 700 shown in FIG. 7 .
  • the receiving unit 510 and the transmitting unit 530 shown in FIG. 5 may be implemented by the transceiver 710
  • the processing unit 520 may be implemented by the processor 720 .
  • the present application takes the network device 400 and the network device 500 as examples to describe the method and device for charging according to the embodiments of the present application.
  • the method for charging in the embodiment of the present application may also be implemented by two baseband chips, and the first baseband chip in the two baseband chips is used to implement the correlation of the network device 400 (for example, the ECS) in the embodiment of the present application
  • the second baseband chip in the two baseband chips is used to implement related operations of the network device 500 (eg, EES) in the embodiment of the present application.
  • the input/output circuit of the first baseband chip can be used to implement the above-mentioned operations related to the transceiver of the network device 400 (eg ECS), and the input/output circuit of the second baseband chip can be used to implement the above related operations of the transceiver of the network device 500 (eg, EES).
  • the processor may be a central processing unit (central processing unit, CPU), and the processor may also be other general-purpose processors, digital signal processors (digital signal processors, DSP), dedicated integrated Circuit (application specific integrated circuit, ASIC), off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • CPU central processing unit
  • DSP digital signal processors
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • FPGA field programmable gate array
  • the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically programmable Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • Volatile memory may be random access memory (RAM), which acts as an external cache.
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • DDR SDRAM double data rate synchronous dynamic random access memory
  • enhanced SDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous connection dynamic random access memory Fetch memory
  • direct memory bus random access memory direct rambus RAM, DR RAM
  • the above embodiments may be implemented in whole or in part by software, hardware, firmware or any other combination.
  • the above-described embodiments may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions. When the computer program instructions are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated.
  • the computer may be a general purpose computer, special purpose computer, computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server or data center Transmission to another website site, computer, server or data center by wire (eg, infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that a computer can access, or a data storage device such as a server, a data center, or the like containing one or more sets of available media.
  • the usable media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, digital versatile disc (DVD)), or semiconductor media.
  • the semiconductor medium may be a solid state drive.
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium.
  • the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution.
  • the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, removable hard disk, read only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program codes.

Abstract

La présente demande utilise un procédé et un dispositif de charge, susceptibles de réduire la sollicitation provoquée par un CHF maintenant un état connecté pour chaque serveur périphérique d'activation (SPA ou EES) lors de l'acquisition de données de charge. Le procédé consiste : à acquérir dans un serveur périphérique de configuration (SPC ou ECS) des premières données agrégées d'utilisation de ressources de réseau d'une première application, comptées par au moins un EES ; à déterminer, selon les premières données, des premières données de charge utilisées par un système de charge pour charger la première application ; et à signaler les premières données de charge au système de charge.
PCT/CN2022/079455 2021-03-16 2022-03-07 Procédé et dispositif de charge WO2022193971A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110281441.3 2021-03-16
CN202110281441.3A CN115150762A (zh) 2021-03-16 2021-03-16 一种计费方法和设备

Publications (1)

Publication Number Publication Date
WO2022193971A1 true WO2022193971A1 (fr) 2022-09-22

Family

ID=83322048

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/079455 WO2022193971A1 (fr) 2021-03-16 2022-03-07 Procédé et dispositif de charge

Country Status (2)

Country Link
CN (1) CN115150762A (fr)
WO (1) WO2022193971A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020204474A1 (fr) * 2019-03-29 2020-10-08 삼성전자 주식회사 Dispositif et procédé permettant de fournir un service d'informatique en périphérie dans un système de communication sans fil
US20200359218A1 (en) * 2019-05-09 2020-11-12 Samsung Electronics Co., Ltd. Apparatus and method for providing mobile edge computing services in wireless communication system

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020204474A1 (fr) * 2019-03-29 2020-10-08 삼성전자 주식회사 Dispositif et procédé permettant de fournir un service d'informatique en périphérie dans un système de communication sans fil
US20200359218A1 (en) * 2019-05-09 2020-11-12 Samsung Electronics Co., Ltd. Apparatus and method for providing mobile edge computing services in wireless communication system

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Charging management; Study on charging aspects of edge computing (Release 17)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 28.815, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V0.4.0, 10 February 2021 (2021-02-10), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 29, XP051975360 *
HUAWEI: "pCR Add ECS charging information aggregation and technical solution", 3GPP DRAFT; S5-214711, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG5, no. e-meeting; 20210823 - 20210831, 1 September 2021 (2021-09-01), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052065233 *

Also Published As

Publication number Publication date
CN115150762A (zh) 2022-10-04

Similar Documents

Publication Publication Date Title
WO2021018021A1 (fr) Procédé et système de facturation ainsi que dispositif de communication
AU2019386646B9 (en) User access control method, information sending method, and apparatus
US8626156B2 (en) Methods, systems, and computer readable media for selective policy enhancement (PE) for high-usage roamers
KR102469191B1 (ko) 정보 전송방법 및 장치, 컴퓨터 판독가능 저장 매체
US9948646B1 (en) Machine type communication interworking function proxy
US20120195196A1 (en) SYSTEM AND METHOD FOR QoS CONTROL OF IP FLOWS IN MOBILE NETWORKS
US8903974B2 (en) Methods, systems, and computer readable media for user controlled policy sharing
WO2014000260A1 (fr) Procédé de traitement de qos, serveur d'application, élément de réseau de commande de qos et réseau mobile
WO2020108002A1 (fr) Procédé de détermination de politique de transmission, procédé de commande de politique, et dispositif
AU2020206808A1 (en) Communication method and communication apparatus
JP7233532B2 (ja) セッション管理のための方法および装置
US10958574B2 (en) Systems and methods for providing external services to core network traffic
WO2021136132A1 (fr) Procédé et appareil de traitement de paquets
WO2022021971A1 (fr) Procédé de communication, premier élément de réseau de commande de politique et système de communication
US20220225094A1 (en) Communication method, device, and system, and storage medium
US20230362604A1 (en) Charging function fallback
WO2019056244A1 (fr) Procédé et dispositif de distribution de données, et support de stockage et système
JP2023120240A (ja) インタラクティブサービスのためのｐｃ５上での装置間通信における課金
WO2020109853A1 (fr) Gestion de ressources optimisée reposant sur une analyse prédictive
US20230036993A1 (en) Monitoring an attribute of a network slice
WO2022193971A1 (fr) Procédé et dispositif de charge
WO2022141390A1 (fr) Procédé de communication et dispositif de réseau
WO2022267583A1 (fr) Procédé et appareil de communication
US20220353340A1 (en) Communication Method and Communication Apparatus
WO2023280000A1 (fr) Procédé de communication, système et appareil

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22770326

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22770326

Country of ref document: EP

Kind code of ref document: A1