JP6921153B2 - Billing system, billing server, billing method and program - Google Patents

Description

The present invention relates to a billing system, a billing server, a billing method and a program.

In recent years, the introduction of MEC (Mobile Edge Computing) has been studied in order to provide a service that requires high-capacity or low-latency communication via a mobile network (see Non-Patent Document 1).

The MEC server that provides the service using the MEC is connected to the radio access network that constitutes the mobile network. As a result, the communication path between the communication terminal of the user who uses the service and the MEC server is shortened, and the user can use the service with low delay. Further, since the communication load on the mobile network is reduced by shortening the communication path, the telecommunications carrier can provide a large-capacity communication with a small capital investment.

ETSI GS MEC 002 V2.1.1 (2018-10) Multi-access Edge Computing (MEC); Phase 2: Use Cases and Requirements

As the communication load on the mobile network is reduced by the introduction of MEC, it is desired to appropriately determine the charge for using MEC.

The present invention has been made to solve the above-mentioned problems, and an object of the present invention is to provide a billing system, a billing server, a billing method, and a program capable of appropriately determining a fee for using MEC. ..

The billing system according to the present invention is a billing system having a billing server connected to a core network of a mobile network including a wireless access network and a core network, and a MEC (Mobile Edge Computing) server connected to the wireless access network. The MEC server is provided with a communication unit that communicates with a communication terminal connected to the mobile network, and the billing server is a first billing condition and a first billing condition regarding the use of the core server connected to the core network by the communication terminal. A storage unit that is different and stores the second billing condition regarding the use of the MEC server, an acquisition unit that acquires the first log information regarding the use of the core server and the second log information regarding the use of the MEC server, and the first charge. It is provided with a billing information generation unit that generates the first billing information based on the condition and the first log information and generates the second billing information based on the second billing condition and the second log information. It is a feature.

Further, in the billing system according to the present invention, the first billing condition is the billing condition for the first communication via the core network or the first transaction between the core server and the communication terminal, and the second billing condition is the MEC. It is preferable that the billing condition is related to the second communication between the server and the communication terminal or the second transaction between the MEC server and the communication terminal.

Further, in the billing system according to the present invention, can the MEC server transmit the processing result information regarding the second transaction with the first communication terminal communicating by the communication unit to the aggregation server via the core network? When it is determined that the processing result information can be transmitted by the determination unit that determines whether or not it is possible, the processing result information is transmitted to the aggregation server via the core network, and it is determined that the processing result information cannot be transmitted. In this case, it is preferable to further include a transmission processing unit that transmits the processing result information to the aggregation server via the second communication terminal that communicates with the communication unit.

Further, in the billing system according to the present invention, it is preferable that the billing server further includes an output unit for outputting the first billing information and the second billing information.

Further, in the billing system according to the present invention, the storage unit further stores the third billing condition regarding the third communication via the core network by the MEC server, which is different from the first billing condition and the second billing condition. It is preferable that the acquisition unit further acquires the third log information regarding the third communication, and the charge information generation unit further generates the third charge information based on the third charge condition and the third log information.

Further, in the billing system according to the present invention, it is preferable that the MEC server further includes a log information generation unit that generates the second log information, and the acquisition unit acquires the second log information from the MEC server.

The billing server according to the present invention is a billing server connected to the core network of a mobile network composed of a wireless access network and a core network, and the communication terminal connected to the mobile network uses the core server connected to the core network. Regarding the use of the core server and the storage unit that stores the first charge condition regarding the first charge condition and the second charge condition regarding the use of the MEC (Mobile Edge Computing) server connected to the wireless access network, which is different from the first charge condition. The acquisition unit that acquires the first log information and the second log information related to the use of the MEC server generates the first billing information based on the first billing condition and the first log information, and the second billing condition and the second. It is characterized by including a billing information generation unit that generates a second billing information based on the log information.

The billing method according to the present invention is a billing method by a billing server connected to a core network of a mobile network including a storage unit and composed of a wireless access network and a core network, and is a billing method by a communication terminal connected to the mobile network. The first billing condition regarding the use of the core server connected to the network and the second billing condition regarding the use of the MEC (Mobile Edge Computing) server connected to the wireless access network, which is different from the first billing condition, are stored in the storage unit. It is stored, the first log information regarding the use of the core server and the second log information regarding the use of the MEC server are acquired, the first billing information is generated based on the first billing condition and the first log information, and the second billing information is generated. It is characterized in that the second billing information is generated based on the billing condition and the second log information.

The program according to the present invention is a computer program that includes a storage unit and connects to a core network of a mobile network composed of a wireless access network and a core network, and is connected to the core network by a communication terminal connected to the mobile network. The first billing condition regarding the use of the core server to be used and the second billing condition regarding the use of the MEC (Mobile Edge Computing) server which is different from the first billing condition and is connected to the wireless access network are stored in the storage unit. The first log information related to the use of the core server and the second log information related to the use of the MEC server are acquired, the first billing information is generated based on the first billing condition and the first log information, and the second billing condition and the second billing condition It is characterized in that the second billing information is generated based on the second log information, and the operation is executed.

The billing system, billing server, billing method and program according to the present invention make it possible to appropriately determine the fee for using the MEC.

It is a schematic diagram for demonstrating the outline of this invention. It is a figure which shows an example of the schematic structure of the billing system 1. It is a figure which shows an example of the schematic structure of the core server 3. It is a figure which shows an example of the schematic structure of the MEC server 4. It is a figure which shows an example of the schematic structure of the billing server 6. It is a figure which shows an example of the data structure of the terminal charge condition table T1. It is a figure which shows an example of the data structure of the server billing condition table T2. It is a figure which shows an example of the data structure of the processing result information table T3. It is a figure which shows an example of the data structure of the 3rd log information table T4. It is a flow chart which shows an example of the flow of the 1st service processing. It is a flow chart which shows an example of the flow of the 2nd service processing. It is a flow chart which shows an example of the flow of the 2nd service processing. It is a flow chart which shows an example of the flow of the 2nd service processing. It is a flow chart which shows an example of the flow of the charge information generation processing.

Hereinafter, various embodiments of the present invention will be described with reference to the drawings. However, it should be noted that the technical scope of the present invention is not limited to those embodiments, but extends to the inventions described in the claims and their equivalents.

(Outline of the present invention)
FIG. 1 is a schematic diagram for explaining an outline of the present invention.

The billing system according to the present invention includes a billing server connected to a core network of a mobile network including a radio access network and a core network, and a MEC (Mobile Edge Computing) server connected to the radio access network. The MEC server communicates with a communication terminal connected to the mobile network. The billing server generates billing information about the communication terminal.

The mobile network is, for example, a 4th generation mobile communication system (4G). In this case, the radio access network is LTE (Long Term Evolution), and the core network is EPC (Evolved Packet Core). The communication terminal connects to the mobile network by registering the location in the HSS (Home Subscriber Server) included in the core network via a wireless base station such as an eNB (evolved Node B).

The communication terminal executes the first communication via the core network. The first communication is, for example, communication in which the communication terminal transmits a processing request for the first transaction between the communication terminal and the core server to the core server connected to the core network. The core server is a server that connects to a data network different from the mobile network, such as the Internet, and connects to the core network via the data network. The first transaction is a series of processes related to a predetermined service, and is, for example, a series of processes related to a service for end users who use a communication terminal, such as a real-time translation service. When the predetermined service is a real-time translation service, the series of processes is, for example, a process from the transmission of the word / phrase to be translated by the communication terminal to the reception of the translation result. The series of processes may be a process from the transmission of the start instruction of the real-time translation to the transmission of the end instruction of the real-time translation. The core server starts the first transaction in response to receiving the processing request of the first transaction, and sends the processing response to the communication terminal. In addition, the core server generates the processing result information of the first transaction.

Further, the communication terminal executes the second communication with the MEC server. The second communication is, for example, a communication in which the communication terminal transmits a processing request for the second transaction to the MEC server. The MEC server starts the second transaction in response to receiving the processing request of the second transaction, and transmits the processing response to the communication terminal. In addition, the MEC server generates processing result information of the second transaction. The second transaction is, for example, a process related to a service of the same type as the first transaction.

The billing server stores the first billing condition and the second billing condition. The first billing condition is a billing condition relating to the use of the core server, for example, a billing condition relating to the first communication by the communication terminal or the first transaction between the core server and the communication terminal. The first billing condition is, for example, a unit price per communication volume of the first communication or a unit price per number of times of the first transaction. The second billing condition is a billing condition relating to the use of the MEC server, for example, a billing condition relating to a second communication between the MEC server and the communication terminal or a second transaction between the MEC server and the communication terminal. The second billing condition is a billing condition different from the first billing condition.

The billing server acquires the first log information regarding the use of the core server and the second log information regarding the use of the MEC server. The billing server acquires the first log information from the core server. The first log information is information including, for example, the communication volume of the first communication or the number of times of the first transaction. Further, the billing server acquires the second log information from the MEC server. The second log information is information including, for example, the communication volume of the second communication or the number of times of the second transaction.

The billing server generates the first billing information based on the first billing condition and the first log information. The billing server calculates the billing amount for the first communication by multiplying the unit price per communication volume of the first communication included in the first billing condition by the communication volume of the first communication included in the first log information. .. In addition, the billing server calculates the billing amount for the first transaction by multiplying the unit price per number of first transactions included in the first billing condition by the number of first transactions included in the first log information. .. The billing server generates the first billing information by summing the generated billing amount for the first communication and the billing amount for the first transaction.

Further, the billing server generates the second billing information based on the second billing condition and the second log information. The billing server calculates the billing amount for the second communication by multiplying the unit price per communication volume of the second communication included in the second billing condition by the communication volume of the second communication included in the second log information. .. In addition, the billing server calculates the billing amount for the second transaction by multiplying the unit price per number of second transactions included in the second billing condition by the number of second transactions included in the second log information. .. The billing server generates the second billing information by summing the generated billing amount for the second communication and the billing amount for the second transaction.

The billing server outputs the first billing information and the second billing information. For example, the billing server outputs the first billing information and the second billing information by transmitting them to the billing statement creation device of the telecommunications carrier operating the mobile network. The billing statement creation device is an information processing device such as a server that creates billing information for a contracted user who has made a contract to connect a communication terminal to a mobile network based on the first billing information, the second billing information, and the like. ..

As described above, the billing server generates billing information by applying different first billing conditions and second billing conditions to the use of the core server and the use of the MEC server. By doing so, the billing server can appropriately determine the charge for using the MEC.

The above description of FIG. 1 is merely an explanation for deepening the understanding of the contents of the present invention. Specifically, the present invention may be carried out in each of the embodiments described below, and may be carried out by various modifications without substantially exceeding the principles of the present invention. All such variations are included within the scope of the present invention and the present specification.

(Outline configuration of system)
FIG. 2 is a diagram showing an example of a schematic configuration of the billing system 1 according to the present invention. The billing system 1 includes a plurality of communication terminals 2a and 2b, a core server 3, a MEC server 4, an aggregation server 5, and a billing server 6. The communication terminals 2a and 2b connect to the mobile network 7 including the radio access network 71 and the core network 72. The core server 3 and the aggregation server 5 connect to the core network 72 via the data network 8. The MEC server 4 connects to the radio access network 71. The billing server 6 connects to the core network 72. The communication terminal 2a is an example of a first communication terminal, and the communication terminal 2b is an example of a second communication terminal. Hereinafter, when it is not necessary to distinguish between them, the plurality of communication terminals 2a and 2b are collectively referred to as the communication terminal 2.

The radio access network 71 is a radio access network provided by the radio base station 711. The radio access network 71 is, for example, LTE in 4G or NG-RAN (Next Generation Radio Access Network) in a fifth generation mobile communication system (5G). The radio base station 711 is, for example, an eNB in 4G or a gNB (gNodeB) in 5G.

The core network 72 is a network that controls communication of a communication terminal connected to the wireless access network 71. The core network 72 is, for example, EPC in 4G or 5GC (5G Core) in 5G. The core network 72 is connected to the data network 8 via the gateway 721. The gateway 721 relays the communication between the mobile network 7 and the data network 8 and stores the communication amount of the relayed communication. The gateway 721 is, for example, a PGW (Packet Data Network Gateway) in 4G or an UPF (User Plane Function) in 5G.

The data network 8 is, for example, the Internet.

The communication terminal 2 is a terminal such as a mobile phone, a multifunctional mobile phone (so-called "smartphone"), a notebook PC (Personal Computer), or a tablet PC. The communication terminal 2 may be an IoT (Internet of Things) terminal such as a sensor terminal. The communication terminal 2 connects to the mobile network 7 based on a contract made in advance between the contract user and the telecommunications carrier that operates the mobile network 7.

The core server 3 is a server that executes a first transaction related to a predetermined service. The core server 3 starts the first transaction in response to receiving the processing request of the first transaction from the communication terminal 2, and transmits the processing response to the communication terminal 2. The core server 3 is managed by a telecommunications carrier that provides a predetermined service. When the predetermined service is provided by a service provider different from the telecommunications carrier, the core server 3 may be managed by the service provider.

The MEC server 4 is a server for executing a second transaction related to a predetermined service. The MEC server 4 starts the second transaction in response to receiving the processing request of the second transaction from the communication terminal 2, and transmits the processing response to the communication terminal 2. The MEC server 4 is managed by a telecommunications carrier. When a predetermined service is provided by a service provider different from the telecommunications carrier, the MEC server 4 may be managed by the service provider, and the telecommunications carrier may be managed based on a management contract with the service provider or the like. May be managed by.

The aggregation server 5 is a server that acquires and stores processing result information related to a predetermined service. The aggregation server 5 acquires the processing result information related to the first transaction from the core server 3. Further, the aggregation server 5 acquires the processing result information related to the second transaction from the MEC server 4. The aggregation server 5, the core server 3, and the MEC server 4 are connected based on a contract made in advance between the contract user and the telecommunications carrier. The aggregation server 5 is managed by a telecommunications carrier. When the predetermined service is provided by a service provider different from the telecommunications carrier, the aggregation server 5 may be managed by the service provider.

The billing server 6 is a server that generates billing information about the communication terminal 2. The billing server 6 acquires the first log information regarding the use of the core server 3 and the second log information regarding the use of the MEC server 4. The first log information is log information related to the first communication by the communication terminal 2 via the core network 72 and the first transaction between the core server 3 and the communication terminal 2. The second log information is log information relating to the second communication between the MEC server 4 and the communication terminal 2 and the second transaction between the MEC server 4 and the communication terminal 2. The billing server 6 generates billing information for the communication terminal 2 based on the acquired first log information and the second log information. The billing server 6 is managed by a telecommunications carrier.

In the billing system 1, the plurality of communication terminals 2 are terminals contracted by the same contract user, for example, a business mobile phone provided to an employee by a contract user who is a company. The plurality of communication terminals 2 may be contracted by different contract users who have the same billing destination, or may be contracted by contract users whose billing destinations are different from each other. The core server 3 and the MEC server 4 are servers that provide a predetermined service to the communication terminal 2 based on a contract made in advance between the contract user and the communication carrier. The predetermined service is, for example, a real-time translation service or the like. A predetermined service may be provided to an employee by a company that is a contract user, or may be provided to an end user who is a general consumer.

When the communication terminal 2 acquires a predetermined service usage operation from the user, the communication terminal 2 transmits a processing request for the first transaction to the core server 3 based on a contract made in advance between the contract user and the communication carrier. Alternatively, the processing request for the second transaction is transmitted to the MEC server 4. For example, the telecommunications carrier provides a service by the core server 3 to a contract user who allows a predetermined communication delay, and provides a service by the MEC server 4 to a contract user who does not tolerate a predetermined communication delay. As a result, the telecommunications carrier can provide services that meet various demands regarding communication delays of users.

The aggregation server 5 provides processing result information regarding the first transaction and the second transaction acquired from the core server 3 and the MEC server 4 in response to a request from the telecommunications carrier or the service provider. As a result, the telecommunications carrier or the service telecommunications carrier can grasp the usage status of the predetermined service by the user of the communication terminal 2 without accessing the core server 3 and the MEC server 4.

FIG. 3 is a diagram showing an example of a schematic configuration of the core server 3. The core server 3 includes a first storage unit 31, a first communication unit 32, and a first processing unit 33.

The first storage unit 31 is a device for storing a program or data, and includes, for example, a semiconductor memory device. The first storage unit 31 stores an operating system program, a driver program, an application program, data, and the like used for processing by the first processing unit 33. The program is installed in the first storage unit 31 from a computer-readable and non-temporary portable storage medium such as a CD-ROM or a DVD-ROM using a known setup program or the like.

The first communication unit 32 includes a communication interface circuit that enables the core server 3 to communicate with other devices. The communication interface circuit included in the first communication unit 32 is a communication interface circuit such as a wired LAN (Local Area Network) or a wireless LAN. The first communication unit 32 receives the data transmitted from the other device, supplies the data to the first processing unit 33, and transmits the data supplied from the first processing unit 33 to the other device.

The first processing unit 33 includes one or more processors and peripheral circuits thereof. The first processing unit 33 is, for example, a CPU (Central Processing Unit), and controls the operation of the core server 3 in an integrated manner. The first processing unit 33 may be a DSP (Digital Signal Processor), an LSI (Large-Scaled IC), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or the like. The first processing unit 33 controls the operation of the first communication unit 32 so that various processes of the core server 3 are executed in an appropriate procedure based on the program stored in the first storage unit 31. The first processing unit 33 executes processing based on the program stored in the first storage unit 31. In addition, the first processing unit 33 can execute a plurality of programs in parallel.

The first processing unit 33 includes a first service processing unit 331, a first log information generation unit 332, and a first transmission processing unit 333 as functional blocks. Each of these parts is a functional module realized by a program executed by the first processing unit 33. Further, each of these parts may be mounted on the core server 3 as firmware.

FIG. 4 is a diagram showing an example of a schematic configuration of the MEC server 4. The MEC server 4 includes a second storage unit 41, a second communication unit 42, and a second processing unit 43.

The second storage unit 41 is a device for storing a program or data, and includes, for example, a semiconductor memory device. The second storage unit 41 stores an operating system program, a driver program, an application program, data, and the like used for processing by the second processing unit 43. The program is installed in the second storage unit 41 from a computer-readable and non-temporary portable storage medium such as a CD-ROM or a DVD-ROM using a known setup program or the like.

The second communication unit 42 includes a communication interface circuit that enables the MEC server 4 to communicate with other devices. The communication interface circuit included in the second communication unit 42 is a communication interface circuit such as a wired LAN or a wireless LAN. The second communication unit 42 receives the data transmitted from the other device, supplies the data to the second processing unit 43, and transmits the data supplied from the second processing unit 43 to the other device.

The second processing unit 43 includes one or more processors and peripheral circuits thereof. The second processing unit 43 is, for example, a CPU, and controls the operation of the MEC server 4 in an integrated manner. The second processing unit 43 may be a DSP, LSI, ASIC, FPGA or the like. The second processing unit 43 controls the operation of the second communication unit 42 so that various processes of the MEC server 4 are executed in an appropriate procedure based on the program stored in the second storage unit 41. The second processing unit 43 executes processing based on the program stored in the second storage unit 41. In addition, the second processing unit 43 can execute a plurality of programs in parallel.

The second processing unit 43 includes a second service processing unit 431, a second log information generation unit 432, a determination unit 433, and a second transmission processing unit 434 as functional blocks. Each of these parts is a functional module realized by a program executed by the second processing unit 43. Further, each of these parts may be mounted on the MEC server 4 as firmware.

FIG. 5 is a diagram showing an example of a schematic configuration of the billing server 6. The billing server 6 includes a third storage unit 61, a third communication unit 62, and a third processing unit 63.

The third storage unit 61 is a device for storing a program or data, and includes, for example, a semiconductor memory device. The third storage unit 61 stores an operating system program, a driver program, an application program, data, and the like used for processing by the third processing unit 63. The program is installed in the third storage unit 61 from a computer-readable and non-temporary portable storage medium such as a CD-ROM or a DVD-ROM using a known setup program or the like.

The third communication unit 62 includes a communication interface circuit that enables the billing server 6 to communicate with other devices. The communication interface circuit included in the third communication unit 62 is a communication interface circuit such as a wired LAN or a wireless LAN. The third communication unit 62 receives the data transmitted from the other device, supplies the data to the third processing unit 63, and transmits the data supplied from the third processing unit 63 to the other device.

The third processing unit 63 includes one or more processors and peripheral circuits thereof. The third processing unit 63 is, for example, a CPU, and controls the operation of the billing server 6 in an integrated manner. The third processing unit 63 may be a DSP, LSI, ASIC, FPGA or the like. The third processing unit 63 controls the operation of the third communication unit 62 so that various processes of the billing server 6 are executed in an appropriate procedure based on the program stored in the third storage unit 61. The third processing unit 63 executes processing based on the program stored in the third storage unit 61. Further, the third processing unit 63 can execute a plurality of programs in parallel.

The third processing unit 63 includes an acquisition unit 631, a billing information generation unit 632, and an output unit 633 as functional blocks. Each of these parts is a functional module realized by a program executed by the third processing unit 63. Further, each of these parts may be mounted on the billing server 6 as firmware.

(Data structure of various data)
FIG. 6 is a diagram showing an example of the data structure of the terminal billing condition table T1 stored in the third storage unit 61 of the billing server 6. The terminal billing condition table T1 is a table that manages the first billing condition regarding the use of the core server 3 and the second billing condition regarding the use of the MEC server 4. In the terminal billing condition table T1, the terminal identification information, the first billing condition, and the second billing condition are stored in association with each other.

The terminal identification information is identification information for uniquely identifying the communication terminal 2. The terminal identification information is, for example, subscriber identification information such as IMSI (International Mobile Subscriber Identity) that identifies a contract for connecting the communication terminal 2 to the mobile network. The first billing condition is information indicating a billing condition relating to the first communication and the first transaction. The second billing condition is information indicating a billing condition relating to the second communication and the second transaction.

The first billing condition includes a billing condition for the first communication and a billing condition for the first transaction. The billing conditions for the first communication include the type, packet unit price, and flat-rate communication charge. The type is information indicating the type of billing for the first communication, and is, for example, "pay-as-you-go billing" or "flat-rate billing". "Pay-as-you-go" is a method of charging an amount of money according to the amount of communication, and "flat-rate charging" is a method of charging a predetermined amount of money regardless of the amount of communication. The packet unit price is information indicating the charge amount per unit communication amount (for example, one packet) when the type is "pay-as-you-go". The flat-rate communication charge is information indicating the charge amount per predetermined period (for example, one month) when the type is "flat-rate charge". The flat-rate communication charge may be 0 yen. The flat-rate communication charge may be information indicating the amount charged per day or per year.

The billing conditions for the first transaction include the type, transaction unit price, and flat-rate usage fee. The type is information indicating the type of charge for the first transaction, and is, for example, "number of charges" or "fixed charge". "Number of charges" is a method of charging an amount according to the number of transactions, and "fixed charge" is a method of charging a predetermined amount regardless of the number of transactions. The transaction unit price is information indicating the billing amount per unit transaction number (for example, one time) when the type is "metered amount". The flat-rate usage fee is information indicating the billing amount per predetermined period (for example, one month) when the type is "flat-rate". The flat-rate usage fee may be 0 yen. The flat-rate usage fee may be information indicating the amount charged per day or per year.

Further, in the billing conditions related to the first communication, a billing condition of a type combining "pay-as-you-go billing" and "flat-rate billing" may be set. For example, a billing condition may be set so that a predetermined amount of money is charged per month as a monthly fee and an amount of money corresponding to the amount of communication per month is further charged. In this case, both the packet unit price and the flat-rate charge are stored in the terminal billing condition table T1. Further, in this case, the billing condition may be set so that only the communication amount at a predetermined time (for example, from 20:00 to 8:00) is subject to pay-as-you-go billing. Similarly, in the billing conditions relating to the first transaction, a billing condition of a type combining "number of times billing" and "flat-rate billing" may be set.

The second billing condition includes a billing condition for the second communication and a billing condition for the second transaction. The billing conditions for the second communication include the type, packet unit price, and flat-rate communication charge. The billing conditions for the second transaction include the type, transaction unit price, and flat-rate usage fee.

The second billing condition is different from the first billing condition. The second billing condition may be more favorable to the contract user than the first billing condition. For example, when the type of the billing condition for the first communication is "pay-as-you-go", the type of the billing condition for the second communication is set to "flat-rate billing". The type of the billing condition for the first communication and the billing condition for the second communication are both set to "pay-as-you-go", and the packet unit price of the billing condition for the second communication is smaller than the packet unit price of the billing condition for the first communication. It may be set.

Similar to the billing condition for the first communication, the billing condition for the second communication may be set as a type of billing condition that combines "pay-as-you-go" and "flat-rate billing". Further, as in the billing condition for the first transaction, the billing condition for the second transaction may be set as a type of billing condition that combines "number of charges" and "flat-rate billing".

The various data in the terminal billing condition table T1 are set in advance based on the contract made between the contract user of the communication terminal 2 and the communication carrier.

FIG. 7 is a diagram showing an example of the data structure of the server billing condition table T2 stored in the third storage unit 61 of the billing server 6. The server billing condition table T2 is a table that manages the third billing condition regarding the third communication between the MEC server 4 and the aggregation server 5 via the core network 72. The server billing condition table T2 stores the server identification information in association with the third billing condition.

The server identification information is identification information for uniquely identifying the MEC server 4. The third billing condition is information indicating a billing condition for the third communication, and includes a type, a packet unit price, and a flat-rate communication charge. The third billing condition is different from the first billing condition and the second billing condition. The third billing condition may be more favorable to the contract user than the first billing condition. Further, similarly to the first billing condition and the second billing condition, a billing condition of a type combining "pay-as-you-go billing" and "flat-rate billing" may be set in the billing condition related to the third communication.

The various data in the server billing condition table T2 are set in advance based on the contract made between the contract user and the telecommunications carrier.

FIG. 8 is a diagram showing an example of the data structure of the processing result information table T3. The processing result information table T3 is a table that manages information regarding the first communication and the first transaction regarding the use of the core server 3, or the second communication and the second transaction regarding the use of the MEC server 4. The processing result information table T3 related to the first communication and the first transaction is stored in the first storage unit 31 of the core server 3, and the processing result information table T3 related to the second communication and the second transaction is stored in the second storage unit 41 of the MEC server 4, respectively. Be remembered. In the processing result information table T3, the time, the terminal identification information, the processing content, and the communication amount are stored in association with each other.

The time is the time when the core server 3 or the MEC server 4 receives a processing request for a predetermined transaction from the communication terminal 2. The processing result is information indicating the content and result of the first transaction or the second transaction executed in response to the request from the communication terminal 2. The processing result includes, for example, information such as the content of the processing request received from the communication terminal 2, the content and execution result of the transaction started in response to the processing request, and the content of the processing response transmitted to the communication terminal 2. included. The communication volume is the communication volume of the first communication or the second communication generated with respect to the first transaction or the second transaction. The communication amount may include both the communication amount related to the communication transmitted from the communication terminal 2 and the communication amount related to the communication transmitted to the communication terminal 2, and includes only one of them. You may.

Various data of the processing result information table T3 are generated by the core server 3 when the core server 3 executes the first transaction, and are stored in the first storage unit 31. Further, various data of the processing result information table T3 are generated by the MEC server 4 when the MEC server 4 executes the second transaction, and are stored in the second storage unit 41.

FIG. 9 is a diagram showing an example of the data structure of the third log information table T4 stored in the gateway 721. The third log information table T4 is a table that manages the third log information regarding the third communication between the MEC server 4 and the aggregation server 5 via the core network 72. In the third log information table T4, the time, the transmission source, the transmission destination, and the communication amount are stored in association with each other.

The time is the time when the gateway 721 relays the data related to the third communication. The source and the destination are information that identifies the device that is the source of the relayed data and the device that is the destination, respectively, and is, for example, the IP address of the device. The communication volume is information indicating the size of the relayed data.

Various data in the third log information table T4 are set by the gateway 721 when the gateway 721 relays data related to the third communication.

(Processing flow)
FIG. 10 is a sequence diagram showing an example of the flow of the first service processing executed by the billing system 1. The first service process is executed when the communication terminal 2 transmits a processing request for the first transaction to the core server 3 based on the contract between the contract user and the communication carrier. The first service processing is realized by the processing unit such as the processor of each device collaborating with each component based on the programs stored in the communication terminal 2, the core server 3, and the aggregation server 5. In the following description, it is assumed that the user of the communication terminal 2a uses a predetermined service.

First, the communication terminal 2a accepts a user's operation to use a predetermined service (S101). When the predetermined service is a real-time translation service, the usage operation is, for example, an operation of inputting a word or phrase to be translated into the communication terminal 2a. In response to the acceptance of the usage operation, the communication terminal 2a transmits the processing request of the first transaction to the core server 3 (S102).

In response to receiving the processing request, the first service processing unit 331 of the core server 3 executes the first transaction (S103) and transmits the processing response to the communication terminal 2a (S104). For example, when the predetermined service is a real-time translation service, the first service processing unit 331 executes translation processing of words and phrases included in the processing request as the first transaction, and sends a processing response including the translation result to the communication terminal 2a. Send.

Subsequently, the first log information generation unit 332 generates processing result information regarding the executed first transaction (S105). The first log information generation unit 332 generates, as the processing result information, information associating the time when the processing request is received, the identification information of the communication terminal 2a that transmitted the processing request, the processing content, and the communication volume of the communication related to the first transaction. Then, it is stored in the processing result information table T3. The first log information generation unit 332 may store only the communication amount of either the data transmitted from the communication terminal 2a or the data transmitted from the core server 3 in the communication related to the first transaction.

Subsequently, the first transmission processing unit 333 transmits the processing result information to the aggregation server 5 via the first communication unit 32 (S106). The first transmission processing unit 333 may transmit only the data related to the first transaction among the processing result information. The data related to the first transaction is, for example, the terminal identification information and the processing result. The aggregation server 5 acquires and stores the transmitted processing result information (S107), and ends a series of processing.

FIG. 11 is a sequence diagram showing an example of the flow of the second service processing executed by the billing system 1. The second service process is executed when the communication terminal 2 transmits a processing request for the second transaction to the MEC server 4 based on the contract between the contract user and the communication carrier. The second service processing is realized by the processing unit such as the processor of each device collaborating with each component based on the programs stored in the communication terminal 2, the MEC server 4, and the aggregation server 5.

First, the communication terminal 2a accepts a user's operation to use a predetermined service (S201). In response to the acceptance of the usage operation, the communication terminal 2a transmits a processing request for the second transaction to the MEC server 4 (S202).

In response to receiving the processing request, the second service processing unit 431 of the MEC server 4 executes the second transaction (S203) and transmits the processing response to the communication terminal 2a (S204). For example, the second service processing unit 431 executes the translation processing of the words and phrases included in the processing request as the second transaction, and transmits the processing response including the translation result to the communication terminal 2a.

Subsequently, the second log information generation unit 432 generates processing result information regarding the executed second transaction (S205). The second log information generation unit 432 generates, as the processing result information, information associating the time when the processing request is received, the identification information of the communication terminal 2a that transmitted the processing request, the processing content, and the communication volume of the communication related to the second transaction. Then, it is stored in the processing result information table T3.

Subsequently, the determination unit 433 determines whether or not the processing result information can be transmitted to the aggregation server 5 via the core network 72 (S206). For example, the determination unit 433 causes the second processing unit 43 to send the processing result information to the aggregation server 5 depending on whether or not the application program for transmitting the processing result information via the core network 72 is operating normally. Determine if transmission is possible.

When it is determined that the processing result information can be transmitted, the second transmission processing unit 434 transmits the processing result information to the aggregation server 5 via the core network 72 (S207). The second transmission processing unit 434 transmits the processing result information table T3 as the processing result information via the second communication unit 42. The second transmission processing unit 434 may transmit only the data related to the second transaction among the data in the processing result information table T3. The aggregation server 5 acquires and stores the transmitted processing result information (S208), and ends a series of processing.

FIG. 12 is a sequence diagram showing an example of a processing flow when it is determined that the processing result information cannot be transmitted to the aggregation server 5 via the core network 72 in the second service processing. Since S301 to S306 in FIG. 12 are the same as the processes in S201 to S206 in FIG. 11, the description thereof will be omitted.

When it is determined in S306 that the processing result information cannot be transmitted, the second transmission processing unit 434 transmits the processing result information to the aggregation server 5 via the communication terminal 2b (S307). The communication terminal 2b is a communication terminal designated in advance by the contract user as a communication terminal for relaying the processing result information. Preferably, the communication terminal 2b is a communication terminal in which the type of billing condition for the first communication is set to "flat-rate billing".

The second transmission processing unit 434 transmits the processing result information and the transmission instruction for transmitting the processing result information to the aggregation server 5 to the communication terminal 2b via the second communication unit 42. The communication terminal 2b transmits the received processing result information to the aggregation server 5 according to the received transmission instruction.

The aggregation server 5 acquires and stores the transmitted processing result information (S308), and ends a series of processing.

In this way, when it is determined that the MEC server 4 cannot transmit the processing result information to the aggregation server 5 via the core network 72, the processing result is processed via the communication terminal 2b designated in advance as the contract user. Send information. By doing so, the MEC server 4 can reliably transmit the processing result information to the aggregation server 5 even when the own device cannot transmit the processing result information, and the availability of the billing system 1 can be improved. can.

Further, for example, the contract user has the type of the billing condition related to the first communication of the communication terminal 2b set to "flat-rate billing" among the plurality of communication terminals 2, and the type of the billing condition related to the first communication of the other communication terminal. Can be contracted so that is set to "pay-as-you-go". As a result, the contract user can transmit the processing result information to the aggregation server 5 at low cost without paying the charge due to the pay-as-you-go billing by paying the flat-rate communication charge for one communication terminal 2b.

The processing result information of the second transaction for the communication terminal 2b may also be transmitted via the communication terminal 2b in the same manner as the processing result information for the communication terminal 2a.

Further, in the second service processing, the communication terminal 2a may determine whether or not the MEC server 4 can transmit the processing result information to the aggregation server 5. In this case, if it is determined that transmission is not possible, the communication terminal 2a may transmit the information regarding the processing response received from the MEC server 4 to the aggregation server 5 via the communication terminal 2b.

FIG. 13 is a sequence diagram showing an example of a processing flow when the communication terminal 2a determines in the second service processing that the MEC server 4 cannot transmit the processing result information to the aggregation server 5. Since the processes of S401 to S404 of FIG. 13 are the same as the processes of S201 to S204 of FIG. 11, the description thereof will be omitted.

The communication terminal 2a determines whether or not the MEC server 4 can transmit the processing result information to the aggregation server 5 (S405). For example, the communication terminal 2a transmits a keep-alive signal to the MEC server 4, and whether or not the MEC server 4 can transmit the processing result information to the aggregation server 5 depending on whether or not there is a response of the keep-alive signal. To judge. Since the processing when it is determined that transmission is possible is the same as S205 to S208 in FIG. 11, the description thereof will be omitted.

If it is determined that transmission is not possible, the communication terminal 2a transmits information regarding the processing response to the aggregation server 5 via the communication terminal 2b (S406). The communication terminal 2a transmits the information regarding the processing response and the transmission instruction for transmitting the processing response information to the aggregation server 5 to the communication terminal 2b. The information regarding the processing response is, for example, information including the processing request transmitted in S402 and the processing response received in S404. The communication terminal 2b transmits the information regarding the received processing response to the aggregation server 5 according to the received transmission instruction.

The aggregation server 5 acquires and stores information regarding the transmitted processing response (S407), and ends a series of processing. By doing so, the billing system 1 makes it possible to send information indicating the contents of the second transaction in the MEC server 4 to the aggregation server 5 even if the MEC server 4 does not operate normally, and billing is performed. The availability of the system 1 can be improved. That is, since the information regarding the processing response includes the processing content corresponding to the processing request transmitted by the communication terminal 2a, the telecommunications carrier can obtain the processing result information, but the communication carrier can obtain the second processing response based on the information regarding the processing response. You can grasp the status of transactions.

FIG. 14 is a sequence diagram showing an example of the flow of the billing information generation process by the billing system 1. The billing information generation process is realized by the processing unit such as the processor of each device collaborating with each component based on the programs stored in the billing server 6, the gateway 721, the MEC server 4, and the core server 3. ..

First, the acquisition unit 631 of the billing server 6 transmits a transmission request for the first log information regarding the first communication and the first transaction to the core server 3 via the third communication unit 62 (S501). When the first transmission processing unit 333 of the core server 3 receives the transmission request of the first log information via the first communication unit 32, it is stored in the first storage unit 31 via the first communication unit 32. The processing result information is transmitted as the first log information (S502). The acquisition unit 631 acquires by receiving the transmitted first log information via the third communication unit 62 (S503).

Further, the acquisition unit 631 transmits a request for transmitting the second log information regarding the second communication and the second transaction to the MEC server 4 via the third communication unit 62 (S504). When the second transmission processing unit 434 of the MEC server 4 receives the transmission request of the second log information via the second communication unit 42, it is stored in the second storage unit 41 via the second communication unit 42. The processing result information is transmitted as the second log information (S505). The acquisition unit 631 acquires by receiving the transmitted second log information via the third communication unit 62 (S506).

Further, the acquisition unit 631 transmits a transmission request for the third log information regarding the third communication to the gateway 721 via the third communication unit 62 (S507). When the gateway 721 receives the request for transmitting the third log information, the gateway 721 transmits the third log information table T4 as the third log information (S508). The acquisition unit 631 acquires by receiving the transmitted third log information via the third communication unit 62 (S509).

Subsequently, the billing information generation unit 632 of the billing server 6 generates the first billing information based on the first billing condition and the first log information, and the second billing information based on the second billing condition and the second log information. The billing information is generated, and the third billing information is generated based on the third billing condition and the third log information (S510).

The billing information generation unit 632 acquires the billing conditions related to the first communication of the communication terminal 2 from the terminal billing condition table T1. When the type of the acquired billing condition for the first communication is "flat-rate billing", the billing information generation unit 632 sets the flat-rate communication charge for the billing condition as the billing amount for the first communication. When the type of the billing condition of the acquired first communication is "pay-as-you-go billing", the billing information generation unit 632 acquires the packet unit price of the first communication. Further, the billing information generation unit 632 calculates the communication amount of the first communication of the communication terminal 2 by referring to the first log information and summing the values of the communication amount associated with the communication terminal 2. The billing information generation unit 632 sets the amount obtained by multiplying the acquired packet unit price by the number of packets corresponding to the calculated communication amount of the first communication as the billing amount for the first communication.

Further, the billing information generation unit 632 acquires the billing conditions related to the first transaction of the communication terminal 2 from the terminal billing condition table T1. When the type of the billing condition related to the acquired first transaction is "flat-rate billing", the billing information generation unit 632 sets the flat-rate usage fee of the billing condition as the billing amount related to the first transaction. When the type of the billing condition related to the acquired first transaction is "number-of-times billing", the billing information generation unit 632 acquires the transaction unit price of the first transaction. In addition, the billing information generation unit 632 refers to the first log information and calculates the number of first transactions associated with the communication terminal 2. The billing information generation unit 632 sets the amount obtained by multiplying the acquired transaction unit price by the calculated number of times of the first transaction as the billing amount for the first transaction. The billing information generation unit 632 generates information in which the identification information of the communication terminal 2 is associated with the total billing amount of the billing amount related to the first communication and the billing amount related to the first transaction as the first billing information.

Further, the billing information generation unit 632 acquires the billing conditions related to the second communication of the communication terminal 2 from the terminal billing condition table T1. When the type of the acquired billing condition for the second communication is "flat-rate billing", the billing information generation unit 632 sets the flat-rate communication charge for the billing condition as the billing amount for the second communication. When the type of the acquired billing condition for the second communication is "pay-as-you-go billing", the billing information generation unit 632 acquires the packet unit price for the second communication. Further, the billing information generation unit 632 calculates the communication amount of the second communication of the communication terminal 2 by referring to the second log information and summing the values of the communication amount associated with the communication terminal 2. The billing information generation unit 632 sets an amount obtained by multiplying the acquired packet unit price by the number of packets corresponding to the calculated communication amount of the second communication as the billing amount for the second communication.

Further, the billing information generation unit 632 acquires the billing conditions related to the second transaction of the communication terminal 2 from the terminal billing condition table T1. When the type of the billing condition related to the acquired second transaction is "flat-rate billing", the billing information generation unit 632 sets the flat-rate usage fee of the billing condition as the billing amount related to the second transaction. When the type of the billing condition related to the acquired second transaction is "number of billing", the billing information generation unit 632 acquires the transaction unit price of the second transaction. In addition, the billing information generation unit 632 refers to the second log information and calculates the number of second transactions associated with the communication terminal 2. The billing information generation unit 632 sets the amount obtained by multiplying the acquired unit price by the calculated number of times of the second transaction as the billing amount for the second transaction. The billing information generation unit 632 generates information in which the identification information of the communication terminal 2 is associated with the total billing amount of the billing amount related to the second communication and the billing amount related to the second transaction as the second billing information.

Further, the billing information generation unit 632 acquires the billing conditions related to the third communication of the MEC server 4 from the server billing table T3. When the type of the acquired billing condition for the third communication is "flat-rate billing", the billing information generation unit 632 sets the flat-rate communication charge for the billing condition as the billing amount for the third communication. When the type of the acquired billing condition for the third communication is "pay-as-you-go billing", the billing information generation unit 632 acquires the packet unit price for the third communication. Further, the billing information generation unit 632 calculates the communication amount of the third communication of the MEC server 4 by referring to the third log information and summing the values of the communication amount associated with the MEC server 4. The billing information generation unit 632 transmits information in which the identification information of the MEC server 4 is associated with the billing amount related to the third communication obtained by multiplying the acquired packet unit price by the number of packets corresponding to the calculated communication volume of the third communication. Generate as billing information.

Subsequently, the output unit 633 outputs the first billing information, the second billing information, and the third billing information to the billing statement creation device (not shown) of the telecommunications carrier via the third communication unit 62. (S511), and the series of processes is completed.

The core server 3 transmits the first log information when it receives the transmission request of the first log information transmitted from the billing server 6, but the present invention is not limited to this. The core server 3 may transmit the first log information to the billing server 6 periodically or irregularly even when the transmission request is not received. Similarly, the MEC server 4 and the gateway 721 may transmit the second log information and the third log information to the billing server 6 periodically or irregularly, respectively, even when the transmission request is not received.

As described above, the billing server 6 has different first billing conditions for the first communication by the communication terminal 2 via the core network 72 and the second communication between the MEC server 4 and the communication terminal 2. And the second billing condition are applied to generate billing information. By doing so, the billing server 6 can appropriately determine the charge for using the MEC.

That is, the communication load given to the mobile network 7 by the second communication for MEC is smaller than the communication load by the first communication via the core network 72. By making it possible for the billing server 6 to apply different billing conditions to the first communication and the second communication, it is possible to realize a fee setting that is convincing to the contract user of the communication terminal 2.

Further, the billing server 6 applies a third billing condition different from the first billing condition and the second billing condition to the third communication by the MEC server 4 via the core network 72 to generate billing information. By doing so, the billing server 6 can provide the contract user with an appropriate charge system including the third communication by the MEC server 4 in addition to the first communication and the second communication.

For example, when the number of second transactions in the MEC server 4 increases because the second billing condition is set to a condition advantageous to the contract user, the communication volume of the third communication for transmitting the processing result information increases. The contract user may bear a high communication fee. The billing server 6 makes the third billing condition related to the third communication a favorable billing condition for the contract user, and makes it possible to realize the charge setting while suppressing the burden on the contract user.

In the above description, the first billing condition is related to both the first communication and the first transaction, but the first billing condition may be related to either one of the first communication and the first transaction. In this case, in S311 the billing server 6 generates information in which the identification information of the communication terminal 2 is associated with either the billing amount related to the first communication or the billing amount related to the first transaction as the first billing information.

Further, in the above description, the second billing condition is related to both the second communication and the second transaction, but the second billing condition may be related to either one of the second communication and the second transaction. In this case, in S311 the billing server 6 generates information in which the identification information of the communication terminal 2 is associated with either the billing amount related to the second communication or the billing amount related to the second transaction as the second billing information.

Further, when the first billing condition relates only to the first communication, the billing server 6 may acquire the first log information from the gateway 721 instead of the core server 3 in S303.

Further, in the above description, the first transaction and the second transaction are assumed to be processes related to the same type of service, but the first transaction and the second transaction may be processes related to services different from each other.

Further, in the above description, the core server 3 and the MEC server 4 are assumed to start the first transaction and the second transaction in response to the processing request from the communication terminal 2, respectively, but the present invention is not limited to this. For example, the core server 3 and the MEC server 4 may transmit a processing request for executing a predetermined process to each of the plurality of communication terminals 2 in response to an operation by the contract user. In this case, the core server 3 may instruct the MEC server 4 to transmit the processing request, and the MEC server 4 may transmit the processing request in response to the instruction from the core server 3. By doing so, the communication load on the mobile network 7 can be suppressed as compared with the case where the core server 3 transmits a processing request to each of the plurality of communication terminals 2. Further, by doing so, the communication volume of the first communication is suppressed, so that the contract user can use the service at a lower cost.

It will be appreciated by those skilled in the art that various changes, substitutions and modifications can be made to this without departing from the spirit and scope of the invention. For example, the above-mentioned processing of each part may be executed in an appropriately different order within the scope of the present invention. Further, the above-described embodiments and modifications may be carried out in appropriate combinations within the scope of the present invention.

1 Billing system 4 MEC server 431 2nd service processing unit 432 2nd log information generation unit 433 Judgment unit 434 2nd transmission processing unit 6 Billing server 631 Acquisition unit 632 Billing information generation unit 633 Output unit

Claims (8)

A billing system including a billing server connected to the core network of a mobile network including a radio access network and a core network, and a MEC (Mobile Edge Computing) server connected to the radio access network.
The MEC server is
A communication unit that communicates with the first communication terminal and the second communication terminal connected to the mobile network, and
A determination unit that determines whether or not processing result information regarding a transaction with the first communication terminal can be transmitted to an aggregation server via the core network, and a determination unit.
When it is determined that the processing result information can be transmitted, the processing result information is transmitted to the aggregation server via the core network, and when it is determined that the processing result information cannot be transmitted, the processing result information cannot be transmitted. A transmission processing unit that transmits the processing result information to the aggregation server via the second communication terminal is provided.
The billing server
For each of the first communication terminal and the second communication terminal, the first billing condition for communication via the core network by each communication terminal is different from the first billing condition, and the use of the MEC server is different. A storage unit that stores the second billing condition related to
An acquisition unit that acquires the first log information related to communication via the core network and the second log information related to the use of the MEC server.
A billing information generation unit that generates first billing information based on the first billing condition and the first log information, and generates second billing information based on the second billing condition and the second log information. When,
With
The second communication terminal is a communication terminal that has been designated in advance by the user of the first communication terminal and the type of the first billing condition is set to a predetermined type.
A billing system characterized by that. The first billing condition is a billing condition relating to a first transaction between the first communication via the core network or a core server connected to the core network and the first communication terminal or the second communication terminal.
The second billing condition is a second communication between the MEC server and the first communication terminal or the second communication terminal, or a second communication between the MEC server and the first communication terminal or the second communication terminal. 2 Billing conditions for transactions,
The billing system according to claim 1. The billing server further includes an output unit that outputs the first billing information and the second billing information.
The billing system according to claim 1 or 2. The storage unit further stores the third billing condition regarding the third communication via the core network by the MEC server, which is different from the first billing condition and the second billing condition.
The acquisition unit further acquires the third log information regarding the third communication, and further acquires the third log information.
The billing information generation unit further generates the third billing information based on the third billing condition and the third log information.
The billing system according to any one of claims 1-3. The MEC server further includes a log information generation unit that generates the second log information.
The acquisition unit acquires the second log information from the MEC server.
The billing system according to any one of claims 1-4. A billing server connected to the core network of a mobile network composed of a wireless access network and a core network, and a first communication terminal and a second communication terminal connected to the wireless access network and connected to the mobile network are communicated with each other. It is determined whether or not the processing result information regarding the transaction with the first communication terminal can be transmitted to the aggregation server via the core network, and it is determined that the processing result information can be transmitted. In this case, the processing result information is transmitted to the aggregation server via the core network, and when it is determined that the processing result information cannot be transmitted, the processing result information is transmitted via the second communication terminal. A charging server of a charging system having a MEC (Mobile Edge Computing) server that transmits the above to the aggregation server.
For each of the first communication terminal and the second communication terminal, the first billing condition for communication via the core network by each communication terminal is different from the first billing condition, and the wireless access network A storage unit that stores the second billing condition regarding the use of the connected MEC server, and
An acquisition unit that acquires the first log information related to communication via the core network and the second log information related to the use of the MEC server.
A billing information generation unit that generates first billing information based on the first billing condition and the first log information, and generates second billing information based on the second billing condition and the second log information. When,
With
The second communication terminal is a communication terminal that has been designated in advance by the user of the first communication terminal and the type of the first billing condition is set to a predetermined type.
A billing server that features that. A billing server provided with a storage unit and connected to the core network of a mobile network composed of a wireless access network and a core network, and a first communication terminal and a second communication terminal connected to the wireless access network and connected to the mobile network. It is possible to communicate with the terminal, determine whether or not the processing result information regarding the transaction with the first communication terminal can be transmitted to the aggregation server via the core network, and transmit the processing result information. When it is determined that there is, the processing result information is transmitted to the aggregation server via the core network, and when it is determined that the processing result information cannot be transmitted, the processing result information is transmitted via the second communication terminal. It is a billing method by the billing server of a billing system having a MEC (Mobile Edge Computing) server that transmits the processing result information to the aggregation server.
For each of the first communication terminal and the second communication terminal, the first billing condition for communication via the core network by each communication terminal is different from the first billing condition, and the wireless access network The second billing condition regarding the use of the connected MEC server is stored in the storage unit, and the storage unit is stored.
Acquire the first log information regarding the communication via the core network and the second log information regarding the use of the MEC server.
The first billing information is generated based on the first billing condition and the first log information, and the second billing information is generated based on the second billing condition and the second log information.
Including that
The second communication terminal is a communication terminal that has been designated in advance by the user of the first communication terminal and the type of the first billing condition is set to a predetermined type.
A billing method characterized by that. A computer connected to the core network of a mobile network including a storage unit and composed of a wireless access network and a core network, and a first communication terminal and a second communication terminal connected to the wireless access network and connected to the mobile network. It is possible to communicate with the first communication terminal, determine whether or not the processing result information regarding the transaction with the first communication terminal can be transmitted to the aggregation server via the core network, and transmit the processing result information. When it is determined that the processing result information is transmitted to the aggregation server via the core network, and when it is determined that the processing result information cannot be transmitted, the processing result information is transmitted via the second communication terminal. A program of the computer of a billing system having a MEC (Mobile Edge Computing) server that transmits the processing result information to the aggregation server.
For each of the first communication terminal and the second communication terminal, the first billing condition for communication via the core network by each communication terminal is different from the first billing condition, and the wireless access network The second billing condition regarding the use of the connected MEC server is stored in the storage unit, and the storage unit is stored.
Acquire the first log information regarding the communication via the core network and the second log information regarding the use of the MEC server.
The first billing information is generated based on the first billing condition and the first log information, and the second billing information is generated based on the second billing condition and the second log information.
Let the computer do that
The second communication terminal is a communication terminal that has been designated in advance by the user of the first communication terminal and the type of the first billing condition is set to a predetermined type.
A program characterized by that.

Images