Method and apparatus for reliable remote payments |
|
IPC classes for russian patent Method and apparatus for reliable remote payments (RU 2544794):
  
 Method and device for implementing cognitive network / 2544792
Invention relates to telecommunication. The method includes steps of: determining a type of a received network task; according to the type of the received network task, selecting a cognitive capability identifier corresponding to the type of the network task, where the cognitive capability identifier is configured to identify a cognitive capability of a network device; using network devices with the cognitive capability identifier as alternative network devices; determining an alternative network device that is among the alternative network devices and has a cognitive capability that meets a condition for performing the network task is a target network device; and controlling the target network device to perform the network task. In the method of implementing a cognitive network disclosed in the present invention, the cognitive capability of each network device is identified through cognitive capability identification on network devices to clearly embody a difference between the network devices, it is evaluated, according to the cognitive capability identifiers of different devices, whether the network devices need to perform a network task, and a device that meets the condition for performing the network task is selected, in order to ensure that the network task is smoothly performed. A method and a device for implementing a cognitive network are disclosed.
 Method for setting subbands in multicarrier communication system and radio base station apparatus / 2544781
Group of inventions relates to mobile radio communication. In the apparatus, a modulating unit modulates encoded Dch data to generate Dch data symbols. The modulating unit modulates encoded Lch data to generate Lch data symbols. An assigning unit assigns the Dch and Lch data symbols to subcarriers constituting OFDM symbols and outputs them to a multiplexing unit. At the same time, the assigning section assigns a set of Dch and Lch data symbols to each subcarrier for a respective subband.
 Supporting downlink, dl, triggered cqi feedback on hs-dpcch channel in cell in cell-fach state / 2544758
Disclosed is initiating and operating a high-speed dedicated physical control channel, HS-DPCCH, to report a current channel quality indicator, CQI. User equipment, UE, may receive a high speed-shared control channel, HS-SCCH, command from a Node B triggering a feedback response (i.e. a feedback regarding CQI and/or ACK/NACK on the HS-DPCCH channel). The UE may perform a physical random access channel (PRACH) procedure in response to receiving the command, and may also initiate a collision resolution procedure. The user equipment may transmit a current channel quality indicator (CQI) of the user equipment on a high-speed dedicated physical control channel (HS-DPCCH) prior (before, beforehand) to achieving collision resolution (i.e. a result from the collision resolution procedure).
 Wireless base station device using cooperative harq transmission system, wireless terminal device, wireless communication system and wireless communication method / 2544746
Invention relates to the technology of a cooperative transmission system which uses a distributed antenna. In a transmitting device at the serving eNB side, a first packet transmitting unit carries out an operation for packet transmission of retransmitted data. On the other hand, in a transmitting device at a cooperative eNB side, a second packet transmitting unit carries out an operation of transmitting a new data packet corresponding to information transmitted from the serving eNB by a packet transmitting unit. Control information on transmission by the serving eNB and the cooperative eNB to UE is transmitted only through a PUCCH from the UE to the serving eNB and a PDCCH from the serving eNB to the UE. The serving eNB and the cooperative eNB transmit the new data packet and the communication control information or the like through an X2 interface.
 Method and apparatus for reporting measurement data / 2544236
Invention relates to communication systems. Disclosed is a method of reporting measurement data, which includes initiating a plurality of measurements by user equipment to provide measurement data; initiating transmission, from the user equipment to a network element, a message indicating presence of measurement data; and in response to a message coming from said network element and requesting said measurement data, initiating a response transmitted from said user equipment to said network element and containing only part of said measurement data, as well as information indicating presence of additional measurement data.
 Method and device for data processing in communication network / 2544235
Invention relates to a wireless communication system which employs a discontinuous reception (DRX) function and is intended for efficient use of the DRX function.
 Home evolved node b (henb) blind detection for hierarchy configuration / 2544234
Invention relates to communication engineering and can be used for blind detection performed by a home base station (eNodeB). An apparatus for determining a synchronisation level comprises deciding means configured to decide whether or not a predefined condition is met; receiving means configured to receive a first signal at predefined mute time intervals; control means configured to control time synchronisation based on a first signal; inhibiting means configured to inhibit sending a second signal at said predefined mute time intervals, if the deciding means decides that the predefined condition is met, wherein the second signal corresponds to the first signal; monitoring means configured to monitor, if the first signal is received at the defined mute time intervals, if the deciding means decides that the predefined condition is met, and determining means configured to determine a first mute time interval based on the monitoring results obtained by the monitoring means, and a predefined rule, wherein the first mute time interval is one of the predefined mute time intervals, wherein the monitoring means detects reception of the first signal, wherein, according to said predefined rule, a first synchronisation level is determined, which corresponds to the mute time interval of the received first signal, and a second synchronisation level associated with the apparatus is defined as the next synchronisation level below the first synchronisation level.
 Audibility improvement for reference signals / 2544003
Invention relates to wireless communication engineering and can be used to improve audibility of transmitted reference signals. The method of improving audibility of reference signals in a wireless network includes a wireless communication device selecting one or more subframes as one or more positioning subframes for blanking data transmission; and said wireless communication device indicating one or more of said one or more positioning subframes as one or more multicast/broadcast single frequency network (MBSFN) subframes to additionally blank cell-specific reference signal (CRS) transmission over the one or more MBSFN subframes in a user plane.
 System and method for traffic to pilot power determination in uplink multiple input multiple output transmission / 2544000
Invention relates to wireless communication. Methods and apparatus are provided for uplink MIMO transmissions in a wireless communication system. In particular, scheduled uplink transmission power is allocated between a primary stream including an E-DPDCH and a secondary stream including an S-E-DPDCH. Specifically, a ratio between the power of the E-DPDCH and a primary pilot channel DPCCH, as well as a ratio between the power of the S-E-DPCCH and an unamplified power of the S-DPCCH, each corresponds to a first traffic to pilot power ratio. Further, the transport block size for a primary transport block provided on the E-DPDCH is determined based on the first traffic to pilot power ratio, while the transport block size for a secondary transport block provided on the S-E-DPDCH is determined based on a second traffic to pilot power ratio.
 Managing overload in communication network / 2543996
Invention relates to communication systems. Disclosed is a method of managing overload in a network node 20 of a communication network using a distributed queue system for transmitting data units. Said network node 20 has a priority queue (PQ) 40 for protocol data units (PDU) 50, 50a-n, in accordance with a constant retransmission protocol. The method comprises detecting 110 a state indicating overload and, in response, handling 120 content of the PDU 50, 50a-n in the PQ 40. A network node (20) and a computer-readable medium are also disclosed.
 Electronic device and method of controlling electronic device / 2455691
In the device, the main control section issues data containing fiscal information entered from an interface. The registration control section is connected to the main control section. The registration control section controls the registration section based on data issued from the main control section to issue a sales receipt. The memory control section is connected to the main control section and memory. The memory control section reads and writes fiscal information from and to memory under the control of the main control section. When data are entered into the main control section from the interface, the main control section controls the memory control section for writing fiscal data into the memory. The registration log creating section creates a registration log of the main control section controlling the memory control section for reading fiscal information from the memory.
 Fiscal printer / 2428743
Fiscal printer 1 comprises a detachable fiscal control circuit board 4, a fiscal board 8 installed on it, a real-time clock 10 and a circuit 15 to detect a fact of the fiscal control circuit board 4 extraction. The real-time clock 10 includes an input terminal 10b(1), where detection signals are input from the circuit 15, and a memory device 10c, which, as the signal of the fiscal control circuit board 4 withdrawal is input, memorises the data of this board 4 withdrawal and the time of the signal detection input, at the same time the data on withdrawal and the time of the signal input are associated with each other.
 Cheapaccutane (biliopathy) device control - cash machines / 2180971
The invention relates to vending equipment, namely, cash machines, printing receipts (tickets)
 Drive magazine / 2147380
 The method of control over revenue of electronic cash registers and control system / 2106015
The invention relates to methods of monitoring and collecting information on the revenue unauthorized cash registers (KA) tax services, as well as unauthorized access to the SPACECRAFT and is used at the enterprises of trade and in services to the population
 Block printing cash register / 2069388
The invention relates to a device for registering the reception of money, in particular to the blocks of printing cash registers, printing signs letters
 User intention output based on previous interactions with voice assistant / 2544787
Method of functioning of a smart automated assistant is offered. The method is performed in the electronic device containing the processor and memory where the instructions executed by the processor are saved. The processor executes instructions by which the user request is accepted, which includes the speech input accepted from the user. The information on the sender name is taken from the transfer accepted in the electronic device before reception of speech input. Meanwhile this transfer is accepted from the sender that is isolated from the mentioned user. The intention of the user is revealed on the basis of the mentioned text line and a sender name.
 Inferring user-specific location semantics from user data / 2544771
Invention relates to determining semantics for locations based on user data such as user activities and/or user communications. The user data are captured and analysed to identify keywords including locations. Location data describing the locations are obtained and associated with the user and keywords. The associations represent user context for the locations. The associations are used to deliver services and/or products to the user at various times such as when the user approaches or enters a particular location.
 Method, system and server for managing friends' feed in network / 2544755
Invention relates to means of managing friends' feeds in a network. The method comprises receiving a friends' feeds viewing instruction; obtaining friends' feeds corresponding to viewing user identification information contained in the friends' feeds viewing instruction; determining friend intimacy degrees according to the viewing user identification information; sorting the obtained friends' feeds according to the friend intimacy degrees and one or more update parameters contained in the obtained friends' feeds, and outputting the sorted friends' feeds, wherein said one or more update parameters contain the time of interaction on friends' feeds and the periods of interaction on friends' feeds.
|
FIELD: physics, computer engineering. SUBSTANCE: invention relates to a method, a computer-readable medium and a mobile computing device for conducting remote payment transactions. The method comprises steps of establishing trust relations between a first and a second mobile computing device, wherein the second mobile computing device stores payment information associated with a user of said device, in order to conduct an electronic payment transaction using the second mobile computing device; initiating, using the first mobile computing device, a point-of-sale terminal payment transaction; communicating, using the first mobile computing device, with the second mobile computing device over a network in order to receive payment information from the second mobile computing device; and completing, using the first mobile computing device, the payment transaction using the point-of-sale terminal, using the payment information received from the second mobile computing device. EFFECT: high reliability of electronic payment transactions. 20 cl, 4 dwg
The level of technology Digital wallet (also known as "electronic wallets" or "electronic credit card and other personal payments based electronics allow users to make electronic purchases and make payments without requiring credit/debit cards or other standard payment media (for example, checks). Digital wallets are typically implemented as software and appropriate hardware and software (such as a smartphone, personal digital assistant, a computer, etc.), which stores information about the user's account. Some digital wallets can combine numerous credit/debit the user's account, allowing, thus, to the user to carry one electronic device and have access to multiple credit and debit accounts. Digital wallets can be used for transactions with a pre-configured point-of-sale. Typically, these POS terminals are in communication with a digital wallet using contactless communication. Since the digital wallet is fully linked with the electronic hardware and software, e.g. a smartphone) user, to make the payment, smartphone or other electronic devices must be physically present�SQL and be in the immediate vicinity of the POS. Essentially, the owner of digital wallets are usually unable to fully use your credit/Bank account for other remote entities (for example, a parent to a son or daughter), or otherwise to authorize the payment of purchases made on the destruction of another person. Brief description of the drawings The invention described here is explained by way of an example, without being limited by the accompanying drawings. For simplicity and clarity of explanation, the elements shown in the drawings are not necessarily to scale. For example, for clarity, the dimensions of some elements may be too large relative to the others. Additionally, when it is deemed acceptable, the reference positions are repeated in the drawings to indicate corresponding or analogous elements. Fig.1 is a simplified block diagram of one embodiment of the system for secure remote payment using a mobile computing device; Fig.2 is a simplified block diagram of the sequence of operations of one of the variants of the method of making payments using the system shown in Fig.1; Fig.3 is a simplified block diagram of the sequence of operations of one of the variants of the method of establishing trust vzaimootnoshenie� between mobile computing devices, it is shown in Fig.1; and Fig.4 is a simplified block diagram of the sequence of operations of one of the variants of the method of payment using a POS system using a mobile computing device in accordance with Fig.1. A detailed description of the invention Although the concept of this disclosure may be subjected to various forms of modifications and alternatives listed here are specific embodiments of the invention are shown by means of examples in the drawings and will be described here in detail. However, it should be understood that there is no intention to limit the concepts of the present disclosure specific open forms, but on the contrary, the intention is to cover all modifications, equivalents and alternatives falling within the spirit and scope of the invention defined by the appended claims. In the following description numerous specific details such as logic implementations, opcodes, means to specify operands, implementation splitting/sharing/duplication of resources, types and interrelationships of system components and logical options to split/join sets out to provide a more complete understanding of the present disclosure. However, it should be understood that special�hundred in the art in practice can be suggested implementation options for without such specific details. In other cases, management structure, schema-level logic elements and the complete sequence of software commands have not been shown in detail so as not to obscure the invention. Specialists in the art using appropriate descriptions, will be able to implement appropriate functionality without undue experimentation. Made in the description of the reference to "one implementation" "implementation option", "example embodiment," etc., indicate that the described implementation option may include a particular feature, structure, or characteristic, but every embodiment of the may not necessarily include the particular feature, structure, or characteristic. In addition, such phrases do not necessarily refer to the same embodiment of the. Additionally, when a particular feature, structure or characteristic described in conjunction with a variant of implementation, it is assumed that they are within the knowledge of experts in a given field of technology is able to implement such a feature, structure or characteristic in combination with other variants of implementation, regardless of whether expressly or not. Embodiments of the invention can be implemented by APPA�Turnovo implementation, firmware, software or any combination thereof. Embodiments of the invention implemented in a computer system, which may contain one or more mutual connections between components are made on the basis of the tire, and/or one or more mutual connections of type "point to point" between the components. Embodiments of the invention may also be implemented as commands, stored on a tangible computer-readable media that can be read and executed by one or more processors. Tangible machine-readable medium may include any mechanism for storing or transmitting information in a form readable by the machine (for example, computer device). For example, tangible machine-readable medium may include read-only memory (ROM), random access memory (RAM), disk storage on magnetic disks, optical media, flash memory devices, and more. Turning now to Fig.1, a system 100 for secure payment transactions has a remote or mobile computing device 102 payer and local or proxy mobile computing device 104. In use, as discussed in greater detail below, the local mobile computing device 104 when payments using cash�about the terminal 108 to the remote mobile computing device 102 acts as a proxy server. To perform such operations, the local mobile computing device 104 initiates a payment using cash terminal 108. At the time of payment of sale terminal 108 may request payment information from the local mobile computing device 104 to complete a payment transaction. In response to the payment request, the local mobile computing device 104 is performed with the possibility of a connection with a remote mobile computing device 102 to the network 106 to receive payment information from the device 102, which can be located at a distance from the local mobile computing device 104 and the POS device 108. Because mobile computing devices 102, 104 have a pre-established reliable relationships, such communication may be encrypted or otherwise protected. After the local mobile computing device 104 receives payment information from the remote mobile computing device 102, the mobile computing device 104 completes a payment transaction with the POS device 108, using the payment information. Thus, the user of the remote mobile computing device/payer 102 may authorize the use of your payment information (such as information p� credit account or checking account) the user of the local mobile computing device 104 without the physical presence at the POS terminal 108. For example, the parent may be a user of the mobile computing device 102 payer, and his son or daughter may be the user proxy mobile computing device 104. In such embodiments, the parent may use a mobile computing device 102 payer, remotely enable payment transactions carried out by the son or daughter using proxy mobile computing device 104. Although Fig.1 shows only one remote mobile computing device/payer 102, one of the local mobile computing device/proxy mobile computing device 104, a network 106 and one POS terminal 108, the system 100 may include any number of mobile computing devices 102, mobile computing devices 104, network 106, and point of sale terminals 108 similar or different architecture. For example, the remote computing device 102 may be configured to communication with numerous local mobile computing device 104 to allow each device 104 to carry out payment transactions with one or more POS devices 108, using the payment information provided by the remote mobile computing device/payer 102. Remote mobile vychislitel�e device 102 may be implemented as any type of mobile computing device, capable of performing the function described here. For example, the remote computing device 102 can be implemented as a cell phone, smart phone, mobile Internet device, pocket calculator, notebook, personal digital assistant, a telephony device, or other portable computing device. In the illustrative embodiment, the implementation shown in Fig.1, the remote mobile computing device 102 includes a processor 120, a microprocessor kit 124, memory 126, one or more peripheral devices 128 and circuit 130 connected. In some embodiments, several of the above-mentioned component can be introduced into the motherboard of the mobile computing device 102, while other components can connect to the motherboard by means of communication, for example, through the peripheral port. Additionally, it should be understood that the mobile computing device 102 may include other components, sub-components and devices, usually found in the computer and/or computing device, which for clarity is not shown in Fig.1. The processor 120 of the remote mobile computing device 102 may be implemented as any type of processor capable of performing a software/firmware, the�Oh how the microprocessor, a digital signal processor, microcontroller, etc., the Processor 120 as an example, is implemented as a single-core processor with a core 122 of the processor. However, in other embodiments, the processor 120 may be implemented as a multi-core processor having a plurality of cores of the CPU 122. Additionally, the remote mobile computing device 102 may include additional processors 120 having one or more cores of the CPU 122. Microprocessor a set 124 of the remote mobile computing device 102 may contain the core memory controller (ICSU or "North bridge"), the core controller input/output (ICH or "South bridge") and the device firmware. The device firmware of microprocessor kit 124 may be implemented as a storage device for storing data of a basic input / output system (BIOS) and/or commands, and/or other information (such as BIOS driver used during bootstrap mobile computing device 102). However, in other embodiments, can be used microprocessor kits with a different configuration. For example, in some embodiments, the microprocessor set 124 can be implemented as the core controller platform (RSN). In such embodiments, the OSU�of estline the core memory controller (MCH) might be part of the processor 120, or, otherwise, to be associated with the processor 120 and the processor 120 may communicate directly with the memory 126 (as shown by the dotted line in Fig.1). In some embodiments, the microprocessor set 124 may contain a mechanism 134 protection. The mechanism 134 may be implemented as hardware and/or firmware that can perform the functions of protection, encryption and/or authentication, as described in more detail below. For example, the security mechanism 134 can be implemented as out-of-band processor or otherwise contain out-of-band processor, a trusted platform module (TPM), and/or other remedies that improve the hardware and/or related software modules. As discussed in greater detail below, the mechanism 134 protection operates in conjunction with an appropriate mechanism 154 protection of the local mobile computing device 104 to establish a trust relationship between the mobile computing devices 102, 104. The communication processor 120 is connected to a microprocessor kit 124 through numerous signal path. These signal path (and the other signal path shown in Fig.1) can be implemented as any type of paths in the signal path, is able oble�to secure communication between the components of the mobile computing device 102. For example, the signal path can be implemented as a number of wires, cables, optical fibers, tracks of the PCB, through tires, intermediate devices and/or so forth. The memory 126 of the remote mobile computing device 102 may be implemented as one or more memory devices or data storage locations including, for example, the device dynamic RAM (DRAM), synchronous unit dynamic RAM (SDRAM), synchronous unit dynamic random access memory with double data rate (DDR SDRAM), a flash memory device and/or other volatile memory devices. The memory 126 of the communication means communicates with microprocessor kit 124 through numerous signal path. Although Fig.1 shows only one memory device 126, in other embodiments, the mobile computing device 102 may include additional memory devices. Various data and software can be stored in a storage device 126. For example, one or more operating systems, applications, programs, libraries, and drivers that make up the mass of the software executed by the processor 120, may be stored in memory 126 at runtime. Additionally, software about�sintered material and data stored in the memory 126 may be pumped between the memory device 126 and data storage peripherals 128 as part of the operations of memory management. Peripheral devices 128 remote mobile computing device 102 can include multiple peripheral or interface devices. For example, the peripheral device 128 may include a display, keyboard, mouse, one or more storage devices such as internal or external hard drive, and/or other peripheral devices. Specific devices included in the peripheral devices 128 may depend on such factors as the intended use of the remote mobile computing device 102. Peripheral devices 128 communication means are connected with the microprocessor kit 124 through numerous signal path, allowing, thus, the microprocessor set 124 and/or the processor 120 to receive input signals from peripheral devices 128 and to send output signals to the peripheral device 128. The scheme of connection 130 of the remote mobile computing device 102 may be implemented as any number of devices and circuits to enable communication between the remote mobile computing device/payer 102 and the local mobile computing device�/proxy mobile computing device 104 over the network 106. The network 106 may be implemented as any number of wired and/or wireless communication networks. For example, the network 106 may be implemented as or include one or more cellular networks, telephone networks, local or global networks (e.g. the Internet) or any combination of them. For example, in one embodiments, the network 106 is implemented or, alternatively, contains a cellular network, a Global system for mobile communication (GSM). In addition, the network 106 may include any number of additional devices to facilitate communication between the mobile computing devices 102, 104, such as routers, switches, intermediate computers and/or similar Mobile computing devices 102, 104 may use any suitable communication Protocol to communicate with each other over the network 106 in a specific type of network (s) 106. The circuit 130 also connects communication with microprocessor kit 124 through numerous signal path. The circuit 130 may include one or more wired and/or wireless network interfaces to facilitate communication over a wired and/or wireless portions of the network 106. In some embodiments, the circuit 130 may contain a schema 132 communication over short distances (NFC). Scheme 132 NFC may be implemented as a high-frequency electric�ical coupling scheme for a relatively short distance, that may be inserted within another circuit connection 130 or be separate from it. For example, in some embodiments, the effective communication range of the circuit 132 NFC does not exceed approximately ten inches. The relatively small range of communication circuits 132 NFC connection allows you to verify the physical presence of another communication device (for example, the local mobile computing device/proxy mobile computing device 104), using the scheme of 132 for NFC communication. Additionally, the circuit 132 NFC allows a remote mobile computing device/payer 102 to carry out contactless communication with the local mobile computing device/proxy mobile computing device 104 and other supporting contactless communication devices (for example, POS device 108). Local mobile computing device/proxy mobile computing device 104 may essentially be similar to the remote mobile computing device/payer 102 and may be implemented as any type of mobile computing device capable of performing the function described here. For example, similar to the remote mobile computing device 102, the local mobile computing device 104 may be realizou�but as a cell phone, smart phone, mobile Internet device, pocket calculator, notebook, personal digital assistant, a telephony device, or other portable computing device. In shown in Fig.1 embodiment of the local mobile computing device 104 includes a processor 140 having one or more cores of the CPU 142, microprocessor kit 144 containing the mechanism 154 protection, memory 146, one or more peripheral devices circuit 148 and 150 connection that contains the schema 152 NFC communication. Components are for example the local mobile computing device 104 is essentially similar, although not necessarily identical with the corresponding components of the remote mobile computing device 102. In essence, the above description of the processor 120, the core (EP) processor 122, microprocessor kit 124, memory 126, peripheral devices 128, circuits 130 communications, circuits 132 NFC and mechanism 134 protection of remote mobile computing device/payer 102 are equally applicable, respectively, to the processor 140, the core (s) CPU 142, the microprocessor set 144, a memory 146, a peripheral device 148, 150 links, the scheme 152 NFC and mechanism 154 protection of the local mobile computing device/proxy mobile computing device 104 and are not repeated here for clarity op�Sania. In use, as discussed above, the local mobile computing device/proxy mobile computing device 104 may communicate with a remote mobile computing device/payer 102 directly through the circuit 132, 152 NFC and/or via the network 106. Additionally, the local mobile computing device/proxy mobile computing device 104 may communicate with one or more POS devices 108 through the circuit 152 NFC to make payments. Such payment operations may be implemented as any type of operation in which the POS terminal 108 asks the local mobile computing device 104 a fee for services or products delivered to the POS device 108 or device or object that is associated with the POS device 108. In essence, the POS terminal 108 may be implemented as any device configured to communicate with the mobile computing devices to request and receive electronic payments. To do this, POS 108 contains a schema 160 contactless communication, which can be implemented as a communication scheme for a short distance, made with possibility of connection of this circuit with the circuit 152 NFC local mobile computing device 104. Of course, cash therm�nal 108 may include other circuitry and devices depending for example, on the type and use of the POS device 108. For example, the POS terminal 108 may include a processor, memory, storage device, display, keyboard or other input device, a printer and/or other devices normally present in POS terminals. As discussed above, the local mobile computing device 104 may be used to initiate a payment transaction, the POS device 108 and the completion of the payment transaction using the payment information received from a remote mobile computing device/payer 102. To do this, the local mobile computing device 104 transmits the payment requests and receives payment information from the remote mobile computing device 102 using a secure connection. Payment information may be implemented as any type of information requested by the POS device 108 to complete a payment transaction. For example, payment information may be implemented as account information of the user or the owner of the remote mobile computing device/payer 102, such as information on the status of the account by credit card, information on the status of the account on the payment card, Bank account information or other information about the accounts that can be used�to isolates to pay the debit. Such payment information may also contain information on the authentication for the account, such as your account password, a key access to the account, identification number and/or the like. As shown in Fig.2, an illustrative embodiment of a method 200 for reliable conducting a payment transaction using the system 100 shown in Fig.1, begins with step 202. In step 202 between the mobile computing devices 102, 104 establish trust. In step 202 may be used any suitable method of establishing trust relationships between devices 102, 104. In some embodiments, the circuit 132, 152 NFC devices 102, 104 is used to initially establish the trust by verifying the authenticity of the physical presence of the local mobile computing device/proxy mobile computing device 104 relative to the remote mobile computing device/payer 102. Trust relationships can be established for the local mobile computing device 104 and the user of the local mobile computing device 104 relative to the remote mobile computing device/payer 102. For example, can be generated by the password or access key, which d�should be entered in the local mobile computing device 104, before the remote mobile computing device 102 sends the payment information, in order thus to ensure that the local mobile computing device 104 is used by the corresponding user. An illustrative embodiment of a method 300 for establishing a trust relationship between the mobile computing devices 102, 104 shown in Fig.3. Method 300 begins with step 302, in which between the mobile computing devices 102, 104 establishes communication over a short distance. To do this, the devices 102, 104 can be located next to each other (for example, within ten centimeters or in physical contact) and circuits 132, 152 NFC devices 102, 104 can be controlled to establish a connection over a short distance. When you perform the requirements of establishing transmission over a short distance is provided by the physical presence of the local mobile computing device/proxy mobile computing device 104 relative to the remote mobile computing device/payer 102. Thus, confirms the authenticity of the identity of the local mobile computing device/proxy mobile computing device 104, that he could trust the remote mobile computing device/PL�teldec 102. In step 304, the mobile computing device 102, 104 is exchanged unique identification numbers. Unique identification numbers can be implemented as some type alpha/numeric entry, which uniquely identifies the corresponding device 102, 104. For example, in one embodiment, the implementation in step 304, the mobile computing device 102, 104 is exchanged numbers International identification for mobile equipment (International Mobile Equipment Identify (IMEI)). Unique identification number can be used to confirm the authenticity of the identification devices 102, 104 during subsequent communications, as described below. In step 306, the local mobile computing device/proxy mobile computing device 104 receives the shared access key from the remote mobile computing device/payer 102. Shared access key can be generated by the remote mobile computing device/payer 102 or user device 102 or device 104. Shared access key is used for authentication, identification of a person using the local mobile computing device/proxy mobile computing device 104. For example, before contact with UDA�military mobile computing device 102, to request payment information, the user of the local mobile computing device 104 may be asked to enter the shared access key checking, so that authorised person really uses the device 104. In some embodiments, the shared access key contains the associated timer which establishes a time period during which the shared access key will be valid. Upon expiration of the time set on the timer key access, from a remote mobile computing device/payer 102 must be received by the new access key. In step 308, the local mobile computing device/proxy mobile computing device 104 transmits or provides a list of applications that can be executed on the device 104 and which are allowed to communicate with the remote mobile computing device/payer 102 to request payment information. Providing a pre-defined list of applications that can request payment information, remote mobile computing device/payer 102 can verify that the requested application is not malicious, unauthorized application running on the local mobile computing �devices/proxy mobile computing device 104 or another device. In step 310, the remote mobile computing device/payer 102 generates a pair of private/public key encryption and uses the public key together with the local mobile computing device/proxy mobile computing device 104. Encryption keys can be used to encrypt the communication between the mobile computing devices 102, 104. Can be any suitable encryption methodology to generate a pair of private/public key encryption. For example, in one embodiment, the implementation may use an encryption algorithm of Rivest, Shamir and Adlemana (RSA). Encryption keys can be generated and stored in the relevant protection mechanisms 134, 154, which may also be used to encrypt communications between the devices 102, 104, using encryption keys. In step 312 may be exchanged for additional payment options between mobile vychilitelnye devices 102, 104. For example, in some embodiments, can be determined from the maximum specified limit currency that can be transferred to the local mobile computing device 104. Such limits currencies can be implemented as a General outcome, the limit value and/or a limit value for each operation. Additionally, at the stage� 312 may also be exchanged payment options based, for example, at the time of purchase, place of purchase, type of purchased items/services, etc., These payment options can use the local mobile computing device/proxy mobile computing device 104 to determine whether to request the remote mobile computing device/payer 102 to pay the particular payment transaction and also to provide the user of the remote mobile computing device/payer 102 a checksum on the types of operations that are paid by the user device 102. Returning to Fig.2, after between the mobile computing devices 102, 104 were established trust relationship, the local mobile computing device 104 may perform one or more payment transactions with one or more POS devices 108, using the payment information received from a remote mobile computing device 102 in step 204. Thus, the user of the local mobile computing device 104 may initiate and terminate the operation of payment for products and/or services via the POS device 108 that are paid by the user of the remote mobile computing device 102, using the payment information provided by him. For example, a son or daughter can IP�to alsowhat local mobile computing device 104, to buy a small amount of gasoline or other product/service that pays their parent (i.e. the user of the remote mobile computing device 102 that stores payment information). As shown in Fig.4, a variant of a method 400 for conducting a payment transaction begins with step 402, in which the local mobile computing device 104 determines whether initiated by the user of the payment operation using the cash terminal 108. In embodiments in which the POS terminal 108 contains a schema 160 contactless communication, the user may initiate a payment transaction, the positioning device 104 near the POS device 108, so that the circuit 152 NFC and the circuit 160 contactless communication could communicate with each other. However, in other embodiments, the payment transaction may be initiated by other means, such as, for example, clicking a button or entering information on the POS keyboard 108. In step 404, the local mobile computing device 104 prompts the user to enter a passkey. The user can enter the access key via the keyboard or other suitable input device of the mobile computing device 104. In response, the local mobile computing device�tvo 104 compares the entered passkey with shared access key taken from a remote mobile computing device/payer 102 in step 306 of the method 300. If the passkey has not been verified for authenticity, method 400 returns to step 404 where the user is again asked to enter the correct access key. Thus, it can be performed authentication to identify the user of the local mobile computing device 104. If you enter the access key passed in step 404 authentication, the local mobile computing device 104 establishes a secure communication connection with a remote mobile computing device 102 over the network 106 in step 406. A secure connection may be established using, for example, a unique identification number and the encryption keys are exchanged in the steps 304, 308 of the method 300. For example, the remote mobile computing device 102 may verify that the transmitted unique identification number coincides with the number provided by the local mobile computing device 104 while establishing a trusting relationship. If such numbers do not match, the remote mobile computing device 102 may terminate the connection or take other protective measures. In step 408, the local mobile computing device 104 adopt�et a payment request from the POS device 108. The payment request may be the answer to the previous interaction with the POS device 108, such as receipt of goods or services supplied to the POS device 108 or device or object that is associated with the device 108. The payment request may include a request of the account or other payment information, which should be charged the total cost of the product/service. In response to the reception of the payment request, the local mobile computing device 104 transmits the payment request to the remote mobile computing device 102 in step 410. Such transmission may be encrypted or otherwise protected using the shared public key encryption, as discussed above. In step 412, the remote mobile computing device 102 authenticates the request payment using the data transmitted by the local mobile computing device 104 while establishing a trusting relationship. For example, the remote mobile computing device 102 may be configured to authenticate a unique identification number (for example, the IMEI number) of the local mobile computing device 104, the authentication that the access key was entered correctly, and/or other authentication parameters set in step 300. If Zap�OS payment is authenticated, remote mobile computing device 102 transmits payment information to the local mobile computing device 104 in step 412. As discussed above, the payment information may be implemented as any type of information requested POS device 108 to complete the payment transaction. For example, payment information may be implemented as account information of the user or the owner of the remote mobile computing device/payer 102, such as information about credit card information on the payment card account, Bank account information or other information about the account that can be used to pay for the debit. After the local mobile computing device 104 received payment information from the remote mobile computing device 102, the local mobile computing device 104 in step 414 transmits payment information cash terminal 108. In response, the POS terminal 108 is conducting a payment transaction and in step 416 transmits a permission request payment of the local mobile computing device 104. Local mobile computing device 104 in step 418 sends a permission request to the remote computing device 102. In step 420, the remote mobile computing device 102 p�preset payment, based on the permission request. To do this, as discussed above, the remote mobile computing device 102 may verify that the required currency amount does not exceed the specified threshold and/or authenticates the other parameters set in method 300. If the payment is authorised, the remote mobile computing device 102 in step 420 transmits the authorization of the payment of the local mobile computing device 104. After the local mobile computing device 104 has received the authorization of payment from the remote mobile computing device 102, the local mobile computing device 104 in step 414 transmits the authorization of the payment of cash to the terminal 108. In response, the POS terminal 108 completes a payment transaction and in step 424 transmits a confirmation of payment of the local mobile computing device 104. Local mobile computing device 104 in step 426 sends payment confirmation to the remote computing device 102, which can save the receipt for future reference. Thus, the local mobile computing device 104 is applicable to complete the payment transaction, the POS device 108 at the location of the device 104, using the payment information stored and retrieved from remotely�about mobile computing device 102, which can be located at a distance from the POS device 108. Although the disclosure has been shown and described in detail in the drawings and in the above description, the drawings and description should be considered as examples, not restrictive, and it should be understood that have been shown and described illustrative embodiments of and that all changes and modifications that fall within the essence of the disclosure, should be considered reserved. 1. Method of remote payment transactions containing phases in which: 2. A method according to claim 1, wherein establishing a trust relationship between the first mobile computing device and the second mobile computing device comprises establishing communication between the first and second mobile computing devices using the connection for a short distance. 3. A method according to claim 1, wherein establishing a trust relationship between the first mobile computing device and the second mobile computing device comprises authentication of the physical presence of the first mobile computing device relative to the second mobile computing device. 4. A method according to claim 1, wherein establishing a trust relationship between the first mobile computing device and the second mobile computing device contains an exchange between the first and second mobile computing devices unique identification numbers that identify the corresponding first and second mobile computing devices. 5. A method according to claim 1, wherein establishing a trust relationship between the first mobile computing device and the second mobile computing�tive device comprises receiving the first mobile computing device from the second mobile computing device, the shared access key. 6. A method according to claim 1, wherein establishing a trust relationship between the first mobile computing device and the second mobile computing device comprises transmitting the list of applications from the first mobile computing device to the second mobile computing device, wherein the application list identifies an application running on the first mobile computing device is authorized to request payment information from the second mobile computing device. 7. A method according to claim 1, wherein establishing a trust relationship between the first mobile computing device and the second mobile computing device comprises receiving the first mobile computing device from the second mobile computing device public key pairs of public/private key. 8. A method according to claim 7, in which communication using the first mobile computing device to communicate with the second mobile computing device over the network includes establishing a secure communication connection between the first mobile computing device and the second mobile computing device using the public key. 9. A method according to claim 1, wherein establishing a trust relationship between the first mobile computing device vtorym mobile computing device comprises receiving the first mobile computing device payment options from the second mobile computing device, and payment parameters identify at least one of the following options: the maximum amount of currency at one operation and the time period within which the payment information can be received from the second mobile computing device. 10. A method according to claim 1, further comprising a stage on which: 11. A method according to claim 1, wherein the communication using the first mobile computing device, the second mobile computing device over the network for receiving payment information from the second mobile computing device includes the steps in which: 12. A method according to claim 1, wherein the communication using the first mobile computing device, the second mobile computing device over the network to accept payment information from the second mobile computing device, includes receiving at the first mobile computing device, the account information associated with the user of the second mobile computing device. 13. One or more tangible computer-readable media containing a set of commands in response to the execution result of which the first computing device: 14. One or more tangible machine-readable media according to claim 13, in which the establishment of a trust relationship with the second mobile computing device comprises authentication of the physical presence of the second mobile computing device relative to the first mobile computing device using the connection for a short distance. 15. One or more tangible machine-readable media according to claim 13, in which the establishment of a trust relationship with the second mobile computing device comprises: 16. One or more tangible machine-readable media according to claim 13, in which the establishment of a trust relationship with the second additional mobile computing device further comprises receiving payment options from the second mobile compute�professional device, and payment parameters identify the maximum amount of currency for each transaction. 17. One or more tangible machine-readable media according to claim 13, in which the set of commands further cause the result in the first computing device to the next: 18. One or more tangible machine-readable media according to claim 13, in which establishing a secure wireless connection with the second mobile computing device comprises: 19. A mobile computing device, containing�her: 20. Mobile computing device according to claim 19 wherein the set of commands further cause the process to establish a trust relationship with a trusted mobile computing device by:
|
