RU55484U1 - AUTOMATED SYSTEM OF ACCEPTANCE OF PAYMENTS FOR COMMUNICATION SERVICES - Google Patents

Abstract

The utility model relates to data processing devices for commercial applications, in particular, to systems for receiving payments for cellular telephone services and can be used in GSM cellular communication systems. The technical result of the proposed utility model is to increase the efficiency of receiving payments for communication services provided to subscribers, expanding methods of receiving payments, achieving universality of methods of receiving payments for subscribers. The technical result is achieved by the fact that an automated system for receiving payments for communication services, comprising a payment management device, a cashier’s terminal device, an external payment system processing center device, a billing system device, a prepaid system device, and the payment management device includes a device I / O, cryptographic protection device, SMS gateway device, USSD gateway device, request processing device, storage device connected Erez routing device; the terminal device of the operator-cashier includes an input-output device, a cryptographic protection device, a routing device, a message generating device, a storage device; the billing system device includes an input-output device, a routing device, a personal account management device, a second routing device, a call evaluation device, a switch management device, a pre-paid system device includes an input-output device, a routing device, a user’s personal account management device, a storage device charging device.

Description

The utility model relates to data processing devices for commercial use, in particular, to systems for receiving payments for telephone services, including cellular, and can be used in communication systems.

There are known systems for receiving payments for communication services, including a billing system (see, for example, L.Z.Dich, Billing systems in telecommunications, M .: Radio and communications, 2003, pp. 7-29).

The disadvantages of the systems - similar to those declared are the insufficiently wide possibilities of payment for communication services provided to subscribers.

A known system of payment for services selected as the closest of analogues (RF patent No. 2162245, IPC 7 G 06 F 17/60, publication date 2001.01.20), including a central control device in the form of a billing system.

The disadvantage of the closest analogue is the insufficiently wide possibilities of payment for communication services provided to subscribers.

The problem the proposed utility model aims to solve is to create an efficient and reliable device for receiving payments for communication services through a cashier’s terminal, a subscriber’s mobile phone, processing centers of external payment systems using TCP / IP or SMS networks as transports and USSD-requests and crediting of received funds to personal accounts of subscribers located in one or more billing systems or pre-paid systems.

The technical result of the proposed utility model is to increase the efficiency of receiving payments for communication services provided to subscribers, expanding methods of receiving payments, achieving universality of methods of receiving payments for subscribers.

The technical result is achieved by the fact that the automated system for receiving payments for communication services, comprising a payment management device, is equipped with a cashier operator terminal device, an external payment system processing center device, a billing system device, a prepaid system device;

wherein the payment management device includes an input / output device, a cryptographic protection device, an SMS gateway device, a USSD gateway device, a request processing device, a storage device connected via a routing device; the terminal device of the operator-cashier includes an input-output device, a cryptographic protection device, a routing device, a message generating device, a storage device; the billing system device includes an input-output device, a routing device, a personal account management device, a second routing device, a call evaluation device, a switch control device; The pre-paid system device includes an input-output device, a routing device, a device for managing personal accounts of subscribers, a storage device, a charging device.

The utility model is illustrated by drawings.

Figure 1 presents a block diagram of a system.

Figure 2 presents a block diagram of a payment control device.

Figure 3 presents the block diagram of the device terminal of the operator-cashier.

Figure 4 presents a block diagram of a billing system device.

Figure 5 presents a block diagram of a device pre-system.

Figure 6 presents a block diagram of the algorithm of the request processing device, which is part of the payment control device.

In Fig.7 presents a block diagram of the algorithm of the device for generating messages, which is part of the device terminal of the operator-cashier.

On Fig presents a block diagram of the algorithm of the device for managing personal accounts, which is part of the device pre-paid system.

Figure 9 presents a block diagram of the algorithm of the charging device, which is part of the device pre-system.

The automated system for receiving payments for communication services is distributed (Fig. 1), it includes a payment management device 1 connected via a communication network (for example, the Internet or a specialized network) to a device of a cashier’s operator 2, and a processing center device external payment system 3, a billing system 5 device, a pre-paid system 6 device, and also a mobile phone 4 is connected via a GSM wireless network to the device ozhet simultaneously include several terminal devices cashier operator 2, multiple devices processing center external payment system 3, multiple devices Billing

system 5, several devices pre-pay system 6. Several devices mobile phone 4 can be connected to it.

The payment management device 1 (Fig. 2) contains an input-output device 8, a cryptographic protection device 9, an SMS-gateway device 10, a USSD-gateway device 11, a routing device 12, a request processing device 13, a storage device 14. An input-output device 8, the payment control device is connected to the first input-output of the cryptographic protection device 9, the second input-output of which is connected to the first input-output of the routing device 12. The SMS gateway device 10 is connected to the second input-output of the routing device 12. stroystvo USSD-gateway 11 is connected to the third input-output of the routing device 12. The fourth input 12 is connected to output routing device to the first input-output request processing unit 13. The second input-output request processing unit 13 connected to the input-output storage device 14.

The input-output device 8 is a gateway between the payment control device 1 and the communication network. The gateway can be implemented either using your own router or the provider’s router, the communication channel of which is accessed using a modem or network adapter.

The cryptographic protection device 9 is intended for decryption of requests received by the payment control device 1 and encryption of sent messages. This device can be implemented on a computer built, for example, based on the Intel Pentium processor, using well-known software products, such as the CryptoPro crypto library. Methods for constructing cryptographic protection devices are described in publicly available sources (see, for example, Belkin P.Yu. “Software and hardware for information security. Protection of programs and data: Textbook." ISBN: 5-256-01533-8)

The SMS gateway device 10 is a gateway between the GSM network and the payment management device 1 and is intended for receiving SMS requests for making payments from the GSM network and transmitting responses in the form of SMS messages to the GSM network. The SMS gateway device is implemented on a computer built, for example, based on the Intel Pentium processor, using software that interacts with the SMS center (SMSC) of the GSM network via SMPP. SMS gateway

represents an SMPP client, the principles of which are described in publicly available sources (see, for example, ACIF DR G581: 2002 "SMPP Protocol - Inter-Network Short Message Interchange", ISBN: 1740002326). The specifications of the SMPP protocol are described in the documents of the organization SMS Forum (www.smpp.org).

The USSD gateway device 11 is a gateway between the GSM network and the payment management device 1 and is intended to receive USSD requests for payments from the GSM network and transmit responses in the form of USSD messages to the GSM network. The device USSD-gateway 11 is implemented on a computer built, for example, based on an Intel Pentium processor, using software that interacts with the USSD center (USSDC) of a GSM network via SMPP. The USSD gateway is an SMPP client whose construction principles are described in publicly available sources (see, for example, ACIF DR G581: 2002 "SMPP Protocol - Inter-Network Short Message Interchange", ISBN: 1740002326). The specifications of the SMPP protocol are described in the documents of the organization SMS Forum (www.smpp.org).

Routing device 12 is designed to route received requests of received and sent electronic messages. This device 12 can be implemented on a computer built, for example, based on an Intel Pentium processor or based on a network router, for example, manufactured by Cisco. The principles for constructing a routing device in networks are described in publicly available sources (see, for example, Mark Sportak "Computer networks and network technologies").

The request processing device 13 is designed to process incoming requests and implements the business logic of receiving payments. This device 13 is a software and hardware complex that can be implemented on a computer built, for example, based on the Intel Pentium processor, using standard software (for example, Oracle DBMS, Borland Delphi). In this case, the request processing device 13 is connected to the routing device 12 and the storage device 14 through suitable communication channels. The request processing device 13 receives requests for performing operations related to making payments, and performs operations in accordance with the algorithm, which is described below with reference to Fig.6:

At step 31, the request processing device 13 receives from the routing device 12 a request to perform an operation in the form of a data packet containing an identifier of the type of operation and operation parameters.

At step 32, the request processing device 13 parses the request data packet, extracting from it the value of the identifier of the type of operation and the value of the parameters of the operation. The following types of operations are possible: login of a system participant (bank_login), termination of a system participant (bank_exit), checking the availability of a subscriber's account for crediting a payment by subscriber number (bank_account), crediting a payment to a subscriber's account (bank_payment), crediting a payment using a fixed-value payment card - scratch cards (bank_scratch).

At step 33, the request processing device 13 compares the type of operation with the type of operation of a member of the system (bank_login). If the identifiers match, proceeds to step 34. Otherwise, proceeds to step 39.

At step 34, the request processing device 13 extracts the name and password of the system participant from the operation parameters.

At step 35, the request processing device 13 compares the name and password with the entries of the database of participants in the system implemented in the storage device 14. If the received data matches the name and password of one of the registered participants in the system, proceeds to step 36, otherwise, proceeds to step 38.

At step 36, the request processing device 13 generates a unique session identifier for a system participant and records the correspondence of the session identifier and the system participant with a session activity sign in the session database of the storage device 14.

At step 37, the request processing device 13 generates a successful operation response message containing the session identifier, and proceeds to step 61.

At step 38, the request processing device 13 generates a response error message about the operation and proceeds to step 61.

At step 39, the request processing device 13 extracts a session identifier from the operation parameters.

At step 40, the request processing device 13 compares the received session identifier with the records of the active session identifiers in the session database of the storage device 14. If the session identifier is found to correspond to the system participant, go to step 42, otherwise, to step 41.

At step 41, the request processing device 13 generates a response error message about the operation and proceeds to step 61.

At step 42, the request processing device 13 retrieves from the session database the correspondence of the system participant to the transmitted session identifier.

At step 43, the request processing device 13, depending on the value of the transaction type identifier, proceeds to one of the steps: step 44 (bank_exit identifier), step 46 (bank_account identifier), step 48 (bank_payment identifier), step 59 (bank_scratch identifier).

At step 44, the request processing device 13 writes a sign of the end of the session to the session identifier in the session database of the storage device 14.

At step 45, the request processing device 13 generates a response message about the successful completion of the operation and proceeds to step 61.

At step 46, the request processing device 13 extracts the subscriber number from the request parameters and searches the database of payment directions of the storage device 14 for the subscriber's number matching the payment direction. For example, the following payment directions are possible - billing system, pre-payment system.

At step 47, the request processing device 13 in accordance with the direction of payment generates a message requesting information about the subscriber. The message contains the identifier of the payment direction and the subscriber number. Next, go to step 56.

At step 48, the request processing device 13 extracts the subscriber number from the request parameters and searches the database of payment directions of the storage device 14 for the subscriber's number matching the payment direction. For example, the following payment directions are possible - billing system, pre-paid system.

At step 49, the request processing device 13 in accordance with the direction of payment generates a message with a request for payment. The message contains the identifier of the direction of payment, subscriber number, payment amount, payment identifier. Next, go to step 56.

At step 50, the request processing device 13 extracts from the request parameters the pin code of the payment card, which is a unique sequence of digits of a certain length that identifies the payment card. For example, a pin code may contain 16 digits.

At step 51, the request processing device 13 compares the received pin code of the payment card with the pin codes in the payment card database of the storage device 14. If the pin code is found, proceeds to step 52, otherwise to step 55.

At step 52, the request processing device 13 retrieves the parameters of the payment card from the payment card database of the storage device 14, including the serial number of the payment card and the face value in accordance with the received PIN code.

At step 53, the request processing device 13 extracts the subscriber number from the request parameters and searches the database of payment directions of the storage device 14 for the subscriber's number to match the payment direction.

At step 54, the request processing device 13 in accordance with the direction of payment generates a message with a request for payment. The message contains the identifier of the payment direction, the subscriber number, the payment amount equal to the face value of the payment card. Next, go to step 56.

At step 55, the request processing device 13 generates a response error message about the operation and proceeds to step 61.

At step 56, the request processing device 13 transmits the generated message to the routing device 12.

At step 57, the request processing device 13 receives from the routing device 14 a response to the transmitted message and extracts the result of the request from it.

At step 58, the request processing device 13 checks the result of the query. If the result contains an error code, proceeds to step 59. Otherwise, proceed to step 60.

At step 59, the request processing device 13 generates an operation error message and proceeds to step 61.

At step 60, the request processing device 13 generates a success message and proceeds to step 61.

At step 61, the request processing device 13 transmits the generated message about the result of the operation to the routing device 12.

Storage device 14 is a permanent memory device of a computer, implemented, for example, on a hard disk drive. The following databases are implemented in the storage device 14: a database of system participants, a database of payment directions, a database of payment cards. Each entry

The database of system participants contains the name of the system participant and password for entering the system, as well as additional information about the system participant (for example, details of the organization, sign of permission to work with the system, etc.). Each record of the database of payment directions contains a direction identifier representing a sequence of letters and numbers of a certain length, and a template (mask) of subscriber numbers corresponding to this payment direction. Each record of the database of payment cards contains a pin code of the card, which can be stored in encrypted form, the serial number of the card, the face value of the card, the status of the card and other information about the card.

The terminal device of the cashier-operator 2 (Fig. 3) contains an input-output device 15, a cryptographic protection device 16, a routing device 17, a message generating device 18, a storage device 19. An input-output device 15 is connected to the first input-output of the cryptographic protection device 16. The second the input-output of the cryptographic protection device 16 is connected to the first input-output of the routing device 17. The second input-output of the routing device 17 is connected to the input-output of the message generating device 18. The third input-output of the routing device I 17 is connected to a first input-output of the storage device. The second input-output device for generating messages 18 is connected to the second input-output of the storage device 19.

The input-output device 15 is a gateway between the terminal device of the operator-cashier 2 and the communication network. The gateway can be implemented either using your own router or the provider’s router, the communication channel of which is accessed using a modem or network adapter.

The cryptographic protection device 16 is intended for encryption of messages transmitted by the device of the cashier’s operator terminal 2 and decryption of received messages. This device 16 can be implemented on a computer built, for example, based on an Intel Pentium processor, by using well-known software products, for example, the CryptoPro crypto library. Methods for constructing cryptographic protection devices are described in publicly available sources (see, for example, Belkin P.Yu. “Software and hardware for information security. Protection of programs and data: Textbook." ISBN: 5-256-01533-8)

Routing device 17 is designed to route received requests of received and sent electronic messages. This device can be implemented on a computer built, for example, based on an Intel Pentium processor or based on a network router, for example, manufactured by Cisco. The principles for constructing a routing device in networks are described in publicly available sources (see, for example, Mark Sportak "Computer networks and network technologies").

The message generating device 18 is intended for generating electronic messages containing a request for payment. This device 18 is a software and hardware complex that can be implemented on a computer built, for example, based on the Intel Pentium processor, using standard software (for example, Borland Delphi). In this case, the message generating device 18 is connected to the routing device 17 and the storage device 19 by means of suitable communication channels. The message generating device 18 generates requests for performing operations related to making payments, and performs operations in accordance with the algorithm, which is described below with reference to Fig.7:

At step 62, the message generating device 18 receives a command from the cashier operator to search for a subscriber to make a payment.

At step 63, the message generating apparatus 18 extracts the subscriber number from the command parameters.

At step 64, the message generating device 18 generates a message to request the availability of a subscriber's account for crediting a payment.

At step 65, the message generating device 18 transmits the message to the routing device 17.

At step 66, the message generating device 18 receives from the routing device 17 a response to the account availability request and extracts the result of the request from it.

At step 67, the message generating apparatus 18 checks the result of the query. If the account is unavailable, proceeds to step 68, otherwise, to step 69.

At step 68, the message generating apparatus 18 generates an error message and proceeds to step 77.

At step 69, the message generating apparatus 18 requests the payment amount from the cashier operator.

At step 70, the message generating device 18 receives from the cashier operator the value of the payment amount and the command to make the payment.

At step 71, the message generating device 18 generates a message requesting a payment and captures it as an event in the payment database implemented in the storage device 19.

At step 72, the message generating device 18 transmits a payment request message to the routing device 17.

At step 73, the message generating device 18 receives a response message from the routing device 17 containing the result of the payment request.

At step 74, the message generating apparatus 18 checks the result of the query. If the result contains an error code, proceeds to step 75, otherwise, to step 76.

At step 75, the message generating apparatus 18 generates an error message and proceeds to step 77.

At step 76, the message generating device 18 generates a successful payment message and proceeds to step 77.

At step 77, the message generating device 18 issues a message to the cashier operator about the result of the operation.

The storage device 19 is a permanent memory device of a computer, implemented, for example, on a hard disk drive. The storage device 19 implements a database of payments made from the terminal.

The device processing center of the external payment system 3 is designed to perform transactions on the subscriber's account and make the payment. Description and principles of operation of device 3 are available in publicly available sources (for example, Plastic Cards. - 5th ed., Revised and additional. Authors: Bystrov LV, Voronin AS, Gamolsky A.Yu., Grachev A .N., Delberg L., Ermolaev E.V., Ivashutin O.I., Ikonnikov A.N., Imenitov E.L., Kalistratov N.V., Kolesov I.B., Kochetkova N.M., Kuznetsov V.A., Likorenko Y.A., Morozov A.G., Perlin Yu.V., Pechnikov A.V., Popov V.I., Pyatizbyantsev N.P., Sakharov D.V., Strelchenko Yu. .A., Selivanov Yu.V., Spiranov I.A., Tovb Yu.S., Torkhov V.L., Filippovskaya L.M., Khlystun L.Yu., Shamraev A.V., M .: Publishing group "BDC- Press ”, 2005. - 624 p., incl. ISBN 5-93306-066-6)

The mobile phone 4 device is a terminal terminal equipment of the GSM standard - a multifunctional mobile station with

the ability to receive and transmit data and speech. A description of the operating principles of device 4 is available in the GSM standard documentation. The device is used to generate and transmit by the subscriber payment requests in the form of SMS or USSD messages and subscriber authentication.

The functionality and principles of building the device billing system 5 are described in publicly available sources (see, for example, E. A. Tarzivolov “Billing systems for mobile communications”, M. LLC “Mobile communications”, 1999, Dich L.Z. “Billing systems in telecommunications ”, M. Radio and communications, 2003). When constructing an automated system for accepting payments for communication services, for example, a billing system produced by the CBOSS association (www.cboss.ru) can be used

Below is an example of building a device billing system 5.

The device billing system 5 (figure 4) contains an input-output device 20, a routing device 21, a device for managing personal accounts of subscribers 22, a storage device 23, a device for evaluating conversations 24, a control device for the switch 25. The input-output device 20 is connected to the first input routing device output. The second input-output of the routing device 21 is connected to the first input-output of the user account management device 22. The second input-output of the user account management device 22 is connected to the input-output of the storage device 23. The third input-output of the user account management device 22 is connected to the first input the output of the call assessment device 24. The fourth input-output of the subscriber’s account management device 22 is connected to the input of the output of the control device of the switch 25,

The input-output device 20 is a gateway between the device billing system 5 and the communication network. The gateway can be implemented using your own router.

Routing device 21 is designed to route received requests of received and sent electronic messages. This device can be implemented on a computer built, for example, based on an Intel Pentium processor or based on a network router, for example, manufactured by Cisco. The principles for constructing a routing device in networks are described in publicly available sources (see, for example, Mark Sportak "Computer networks and network technologies").

The device for managing personal accounts of subscribers 22 is intended for settlements with subscribers, crediting and debiting funds from personal accounts of subscribers, billing subscribers for payment of communication services. This device 22

can be implemented on the basis of the Sun Fire server manufactured by Sun Microsystems, using standard software (for example, Oracle DBMS, Oracle Developer Suite).

The storage device 23 is a permanent memory device of a computer, implemented, for example, on a hard disk drive.

The device for evaluating conversations 24 is intended for downloading data on conversations of subscribers, calculating the cost of calls and transmitting information about the cost to the device for managing personal accounts of subscribers 22 for debiting funds. This device 24 can be implemented on a computer built, for example, based on an Intel Pentium processor, using standard software (for example, Oracle DBMS, Oracle Developer Suite).

The control device of the switch 25 is designed to control the status of the subscriber in the HLR (database of home subscribers of the GSM switch) (enable / disable, change the set of services) based on the data received from the device for managing personal accounts of subscribers. This device 25 can be implemented on a computer built, for example, based on an Intel Pentium processor, using standard software (for example, Oracle DBMS, Oracle Developer Suite).

The device pre-paid system 6 (Fig. 5) contains an input-output device 26, a routing device 27, a device for managing personal accounts of subscribers 28, a storage device 29, a charging device 30. An input-output device 26 is connected to the first input-output of the routing device 27. The second input-output of the routing device 27 is connected to the first input-output of the device for managing personal accounts of subscribers 28. The second input-output of the device for managing personal accounts of subscribers 28 is connected to the input-output of storage device 29. s input-output control unit accounts of subscribers 28 connected to the first input-output of the charging device 30.

The input-output device 26 is a gateway between the device pre-system 6 and the communication network. The gateway can be implemented either using your own router, or using the equipment of the provider.

Routing device 27 is designed to route received requests of received and sent electronic messages. This device 27 can be implemented on a computer built, for example, based on an Intel processor

Pentium or based on a network router, for example, manufactured by Cisco. The principles for constructing a routing device in networks are described in publicly available sources (see, for example, Mark Sportak "Computer networks and network technologies").

The device for managing personal accounts of subscribers 28 is intended for managing funds on personal accounts of subscribers. This device 28 is a hardware-software complex that can be implemented on the basis of the Sun Fire server manufactured by Sun Microsystems, using standard software (for example, Oracle DBMS, Sun Java Developer Platform). In this case, the device for managing personal accounts of subscribers 28 is connected to the routing device 27 and the storage device 29 through suitable communication channels. The device for managing personal accounts of subscribers 28 performs operations associated with changing the status of the personal account of the subscriber in accordance with the algorithm, which is described below with reference to Fig.

At step 78, the device for managing personal accounts of subscribers 28 receives, through the routing device 27, a command to perform operations with the personal account of the subscriber in the form of an electronic message. For example, the following types of operations are possible: checking the existence of a personal account of a subscriber, making a payment to a personal account (replenishment), requesting permission to provide services to a subscriber.

At step 79, the device for managing personal accounts of subscribers 28 extracts a subscriber number from the received message.

At step 80, the device for managing personal accounts of subscribers 28 compares the received number with entries in the database of personal accounts of subscribers implemented in the storage device 29. If the personal account is not found, proceeds to step 81, otherwise, to step 82.

At step 81, the device for managing personal accounts of subscribers 28 generates a response error message and proceeds to step 97.

At step 82, the device for managing personal accounts of subscribers 28 extracts the type of operation from the message.

At step 83, the device for managing personal accounts of subscribers 28, depending on the type of operation, proceeds to one of the stages: checking the existence of the personal account of the subscriber - step 84, making a payment to the personal account - step 85, requesting permission to provide the service - step 89.

At step 84, the device for managing personal accounts of subscribers 28 generates a response message about the presence of a personal account and proceeds to step 97.

At step 85, the device for managing personal accounts of subscribers 28 downloads the value of the balance on the personal account of the subscriber (personal account balance) from the database of personal accounts implemented in the storage device 29.

At step 86, the device for managing personal accounts of subscribers 28 extracts from the received electronic message the value of the payment amount and adds to the value of the balance of the personal account.

At step 87, the device for managing personal accounts of subscribers 28 stores the new balance value in the database of personal accounts.

At step 88, the device for managing personal accounts of subscribers 28 generates a response message about the successful completion of the operation and proceeds to step 97.

At step 89, the device for managing personal accounts of subscribers 28 extracts the values of service parameters from the received message.

At step 90, the device for managing personal accounts of subscribers 28 generates a message requesting the cost of the service and transmits it to the charging device 30.

At step 91, the device for managing personal accounts of subscribers 28 receives a response message containing the cost of the provided service from the charging device 30.

At step 92, the device for managing personal accounts of subscribers 28 loads the value of the balance on the personal account of the subscriber (personal account balance) from the database of personal accounts implemented in the storage device 29.

At step 93, the device for managing personal accounts of subscribers 28 compares the cost of the service with the balance value. If the cost of the service is greater than the balance value, proceeds to step 94, otherwise, to step 95.

At step 94, the device for managing personal accounts of subscribers 28 generates a response message about the prohibition of the provision of services and proceeds to step 97.

At step 95, the device for managing personal accounts of subscribers 28 subtracts the cost of the service from the balance value and writes the new value to the database of personal accounts implemented in the storage device 29.

At step 96, the device for managing personal accounts of subscribers 28 generates a response message about the permission to provide services and proceeds to step 97.

At step 97, the device for managing personal accounts of subscribers 28 transmits a response message about the result of the operation to the routing device 27.

The storage device 29 is a permanent memory device of a computer, implemented, for example, on a hard disk drive. AT

the storage device 29 can be implemented a database of personal accounts of subscribers and a database of tariffs.

Billing device 30 is intended for calculating the cost of subscriber calls in real time, determining the possibility of establishing and / or continuing a connection, taking into account the balance of funds in the subscriber's personal account. This device 30 is a hardware-software complex and can be implemented on the basis of the Sun Fire server manufactured by Sun Microsystems, using standard software (for example, Oracle DBMS, Sun Java Developer Platform). The charging device 30 performs operations associated with calculating the cost of services in accordance with the algorithm, which is described below with reference to Fig.9:

At step 98, the charging device 30 receives an electronic message from the personal account management device 28 requesting the cost of the service.

At step 99, the charging device 30 extracts service parameters from the received message.

At step 100, the charging device 30 searches for a tariff for the service in the tariff database implemented in the storage device 29.

At step 101, the charging device 30 performs the calculation of the cost of the service in accordance with the value of the tariff and parameters of the service.

At step 102, the charging device 30 generates a response message with the cost of the service.

At step 103, the charging device 30 transmits a response message to the personal account management device 28.

The inventive utility model can be implemented as follows.

Each of the actions associated with the payment procedure is considered by the system as an event. At the same time, a period of time is set during which the event is expected to occur. If the event does not occur within a specified period of time, it is believed that the payment process is violated.

Before participants in the system, cashier operators and external payment systems can use it to receive payments, they must register with the system administration. To do this, they must inform the administration of the information necessary for participation in the system, a list of which is indicated, for example, in the rules for using the system (name, address, payment details and other details necessary for conducting financial transactions). With system participants

an agreement is concluded on the provision of services for receiving payments, in accordance with which they undertake to transfer the received funds to the settlement account of the organization that provides communication services, minus a commission. The system administration assigns a name and password to each registered participant in the system; they are necessary to start working with the system. The mentioned data communicated by the participant in the system, and the name and password assigned to him through the input-output device 8 are entered into the payment control device 1, in the routing device 12 of which the received data is recognized as data communicated during registration and characterizing the participant in the system, and through the processing device Requests 13 transfer them to the storage device 14, where they are recorded in the database of system participants.

To receive payments through the mobile phone 4 device, registration is not required, since in this case a participant in the system is identified by a subscriber number, which is contained in an SMS or USSD message in accordance with the specifications of the GSM standard. In this case, payment cards of a fixed denomination (scratch cards) are used as a means of payment. The subscriber independently generates a request for payment using a payment card of a fixed nominal value and transfers it to the payment control device 1.

After a participant in the system is registered properly and receives a name and password from the system administration, he can begin working in the system. In order to connect to the payment control device 1, a member of the operator-cashier system or an external payment system enters the name and password assigned to it, respectively, into the terminal of the operator-cashier 2 device or the processing center device 3. The entered data corresponding to the name and password are transmitted via the communication channel to the payment control device 1, in which the request processing device 13 compares the received data with the records of the database of participants in the system implemented in the storage device 14. If it is established that the received data does not match the name and password of any of the registered participants in the system, the communication session is interrupted, otherwise the communication session continues.

The procedure for making a payment by the cashier operator using the inventive utility model can be carried out as follows. The following describes an example of a specific implementation of a utility model.

The participant of the operator-cashier system using the message generating device 18 generates a message with a request for payment. In order to generate a message, the cashier operator using the message generating device 18, which is part of the device, the cashier operator 2 terminal, using the keyboard and the mouse, selects the appropriate command in the menu and enters the cashier operator 2 terminal into the device to generate a message containing a request for payment. The routing device 17 of the device 2 recognizes the data corresponding to the entered command as the data to be transmitted to the payment control device 1 and transmits them via the communication channel to the specified device. The data received via the communication channel, the routing device 12 included in the payment control device 1, is recognized as the data corresponding to the payment request and transmitted to the request processing device 13. The request processing device 13 records the data arrival as an event, determines the date and time of receipt, and transmits them to the database of the storage device 14. Based on the payment data contained in the request, the request processing device 13 generates a message containing a command to conduct the pl Teja to the account, and transmits it to a routing device 12. The routing device 12 based on the information contained in the message, determines to which of the devices 5, billing system or device prepaid system 6 intended message and transmits it via the communication channel.

If the message is intended for the device billing system 5, the procedure continues to be performed as follows. The routing device 21, which is part of the billing system 5, recognizes the incoming data and transmits them to the personal account management device 22. The personal account management device 22 changes the balance on the personal account of the subscriber in the database of the storage device 23 and checks the status of the personal account. If the personal account has been disconnected due to a small balance of funds, the personal account manager 22 creates a command to turn on the phone numbers belonging to the personal account and transfers it to the switch control device 25. The switch control device 25 executes the command to turn on the phone numbers and returns a response about the result of the execution of the personal account management device 22, which changes the state of the personal account in the database of the storage device 23 and returns the result of the operation through the device Routing device 21 to the payment control device 1. Routing device 12 devices

Billing System 1 receives a response from the device, the billing system 5 and transmits it to the request processing device 13, which records the funds transfer event in the database of the storage device 14 and through the routing device 12 transmits a message about the end of the operation via the communication channel to the terminal device of the cashier-operator 2 The routing device 17 of the device, the terminal of the operator-cashier 2 recognizes the message about the end of the operation and records the fact of being held as an event in the database of the storage device 19.

If the message containing the command to make a payment to the personal account, generated by the request processing device 13 of the payment control device 1, is addressed by the routing device 12 for transmission to the device pre-payment system 6, the procedure for crediting the payment continues as follows. The routing device 27, which is part of the swap system 6, recognizes the incoming data and transfers them to the personal account management device 28. The personal account management device 28 changes the balance in the personal account of the subscriber in the database of the storage device 29. When the communication service is provided, the charging device 30 calculates the cost of the service and compares it with the balance in the personal account from the database of the storage device 29. If the funds in the personal account are enough to provide the service, the device tariff Display 30 allows the provision of services. After crediting funds to the personal account, the personal account management device 28 returns the result of the operation through the routing device 27 to the payment management device 1. The routing device 12 of the payment management device 1 receives a response from the pre-payment system 5 and transmits it to the request processing device 13, which fixes the event of crediting funds in the database of the storage device 14 and through the routing device 12 transmits a message about the end of the operation on the channel with bind the terminal of the operator-cashier 2 to the device. The routing device 17 of the device, the terminal of the operator-cashier 2 recognizes the message about the end of the operation and fixes the fact of being held as an event in the database of the storage device 19.

The procedure for making a payment by an external payment system is similar to the procedure for making a payment by the cashier operator, except that the message requesting the payment forms the processing center of the external payment system 3. The principles of the processing center are described in public sources (for example, plastic cards. - 5- ed., revised and additional Authors: Bystrov L.V., Voronin A.S., Gamolsky A.Yu., Grachev A.N., Delberg L.,

Ermolaev E.V., Ivashutin O.I., Ikonnikov A.N., Imenitov E.L., Kalistratov N.V., Kolesov I.B., Kochetkova N.M., Kuznetsov V.A., Likorenko I. .A., Morozov A.G., Perlin Yu.V., Pechnikov A.V., Popov V.I., Pyatizbyantsev N.P., Sakharov D.V., Strelchenko Yu.A., Selivanov Yu.V. ., Spiranov I.A., Tovb Yu.S., Torkhov V.L., Filippovskaya L.M., Khlystun L.Yu., Shamraev A.V., M.: Publishing Group “BDC-Press”, 2005 . - 624 p., Incl. ISBN 5-93306-066-6)

The procedure for making a payment yourself by a subscriber of a communication company through a mobile phone 4 device is performed using special payment cards of a fixed nominal value. Each payment card has a unique code (PIN), the database of which is located in the storage device 14 of the payment control device. The communications company distributes payment cards, which are marked with a PIN code under the protective layer, through arbitrary trading networks. A subscriber of a communications company acquires a payment card in a retail network, removes the protective layer and enters the PIN code printed on the payment card into the mobile phone 4 using the keypad in the SMS or USSD message input mode. The mobile phone 4 device generates a message containing a request for payment acceptance and transmits it to the GSM mobile communication network, which delivers the specified message to the SMS gateway device 10 or the USSD gateway device 11 of the payment management device 1. The received message is transmitted to the device routing 12, which recognizes it as data corresponding to the request for payment and transmits it to the request processing device 13. The request processing device 13 records the receipt of data as an event, about determines the date and time of receipt and transmits them to the database of the storage device 14. Based on the data about the pin code of the card contained in the request, the request processing device 13 checks the correspondence of the pin code in the pin code database in the storage device 14, determines the face value of the card and generates a message containing a command to make a payment in the amount corresponding to the face value of the card to the personal account, and transfers it to routing device 12. Routing device 12, based on the information contained in the message, determines It tells which of the devices billing system 5 or pre-system 6 is intended for the message and transmits it through the communication channel. The further sequence of actions when making a payment is similar to the sequence of actions when making a payment by a cashier operator or an external payment system. After receiving a message from the device, the billing system 5 or the pre-payment system 6 about the payment being credited, the request processing device 13 generates a message

about the successful completion of the operation and sends it to the routing device 12. The routing device 12 transmits a message to the device SMS gateway 10 or USSD gateway 11 depending on the type of the original message. The device SMS gateway 10 or USSD gateway 11 transmits a message to the GSM network. The mobile phone 4 device receives a message about the result of the operation from the GSM network and displays it to the subscriber.

Claims (1)

An automated system for receiving payments for communication services, comprising a payment control device, characterized in that it is equipped with a cashier operator terminal device, an external payment system processing center device, a billing system device, a prepaid system device, and the payment control device includes a device I / O device, cryptographic protection device, SMS gateway device, USSD gateway device, request processing device, storage device connected via the device routing property; the terminal device of the operator-cashier includes an input-output device, a cryptographic protection device, a routing device, a message generating device, a storage device; the billing system device includes an input-output device, a routing device, a personal account management device, a second routing device, a call evaluation device, a switch management device, a pre-paid system device includes an input-output device, a routing device, a user’s personal account management device, a storage device charging device.