Energy-saving electronic card

Abstract

A method, computer system, and computer program product for energy-efficient data exchange are provided. The system may include a first electronic card device (ECD) comprising a first switch and a second switch. The system may include a first switch configured to energize the first ECD in response to the engagement of the first ECD with a second ECD. The system may include a first ECD configured to exchange data with the second ECD. The system may include a docking component configured to receive the first ECD. The system may include the docking component, which includes an actuator configured to engage the second switch to turn on the first ECD when the docking component receives the first ECD. The system may include a first ECD configured to transmit received data from the second ECD to a mobile device associated with the docking component.

Description

Background Technology

[0001] This invention relates generally to the field of computing, and more specifically to portable electronic devices for information exchange.

[0002] In a typical meeting environment, people meet and exchange contact information, such as by exchanging business cards or other identifying information manually or electronically. While exchanging business cards or similar items can help people maintain long-term connections, it can be difficult to recall later which card was associated with which person, especially, for example, if exchanging business cards in a populated environment such as a large conference where the meetings between people last only a short time. As another example, in such a large conference environment, it may not be possible to meet and exchange business cards with everyone or every ideal meeting person in the first place. Summary of the Invention

[0003] Embodiments of the present invention disclose a computer system for energy-efficient data exchange. The invention may include a first electronic card device (ECD) comprising a first switch and a second switch. The invention may include a first switch configured to energize the first ECD in response to engagement of the first ECD with a second ECD. The invention may include a first ECD configured to exchange data with the second ECD. The invention may include a docking component configured to receive the first ECD. The invention may include the docking component, which includes an actuator configured to engage the second switch to energize the first ECD in response to the docking component receiving the first ECD. The invention may include a first ECD configured to transmit received data from the second ECD to a mobile device associated with the docking component.

[0004] This invention also discloses a method and computer program product for energy-saving data exchange. The invention may include detecting the activation of a first switch to power on a first electronic card device (ECD). The invention may include determining, in response to the detected activation of the first switch, that a second ECD is within a threshold proximity range of the first ECD. The invention may include sending accumulated information from the first ECD to a mobile device in response to determining that the first ECD is docked. The invention may include storing accumulated information in the first ECD in response to determining that the first ECD is not docked. The invention may include detecting the deactivation of the first switch that powers off the first ECD in response to the second ECD being outside a threshold proximity range of the first ECD. Attached Figure Description

[0005] These and other objects, features, and advantages of the present invention will become clear from the following detailed description of its illustrative embodiments, which is taken in conjunction with the accompanying drawings. The various features in the drawings are not to scale, as they are illustrated for clarity and to facilitate understanding of the invention by those skilled in the art in conjunction with specific embodiments. In the drawings:

[0006] Figure 1 A networked computer environment according to at least one embodiment is shown;

[0007] Figure 2 This is a block diagram of an electronic card system according to at least one embodiment;

[0008] Figure 3 This is an operational flowchart illustrating an energy-saving data exchange process according to at least one embodiment;

[0009] Figure 4 This is an electrical diagram of an exemplary electronic card device according to at least one embodiment;

[0010] Figure 5 This is a block diagram illustrating the interaction of exemplary electronic cards according to at least one embodiment;

[0011] Figure 6 According to at least one embodiment Figure 1 A block diagram depicting the internal and external components of a computer and server;

[0012] Figure 7 Includes embodiments according to this disclosure Figure 1 A block diagram illustrating a cloud computing environment for a computer system; and

[0013] Figure 8 According to embodiments of this disclosure Figure 7 A block diagram illustrating the functional layers of an illustrative cloud computing environment. Detailed Implementation

[0014] This document discloses detailed embodiments of the claimed structures and methods; however, it is to be understood that the disclosed embodiments are merely illustrative of the claimed structures and methods, which can be implemented in various forms. The invention can be embodied in many different forms and should not be construed as limited to the exemplary embodiments set forth herein. Rather, these exemplary embodiments are provided to make this disclosure thorough and complete, and to fully convey the scope of the invention to those skilled in the art. Details of well-known features and techniques may be omitted in the description to avoid unnecessarily obscuring the presented embodiments.

[0015] This invention can be a system, method, and / or computer program product at any possible level of technical detail integration. The computer program product may include a computer-readable storage medium (or media) having computer-readable program instructions thereon for causing a processor to execute aspects of the invention.

[0016] Computer-readable storage media can be tangible devices capable of retaining and storing instructions for use by an instruction execution device. Computer-readable storage media can be, for example, but not limited to, electronic storage devices, magnetic storage devices, optical storage devices, electromagnetic storage devices, semiconductor storage devices, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of computer-readable storage media includes the following: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), portable compact disc read-only memory (CD-ROM), digital universal disc (DVD), memory sticks, floppy disks, mechanical encoding devices (such as punched cards or protrusions in grooves with instructions recorded thereon), and any suitable combination of the foregoing. As used herein, computer-readable storage media should not be construed as transient signals themselves, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmission media (e.g., light pulses passing through fiber optic cables), or electrical signals transmitted through wires.

[0017] The computer-readable program instructions described herein can be downloaded from a computer-readable storage medium to a corresponding computing / processing device or to an external computer or external storage device via a network (e.g., the Internet, a local area network, a wide area network, and / or a wireless network). The network may include copper transmission cables, optical transmission fibers, wireless transmissions, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards them to a computer-readable storage medium within the corresponding computing / processing device.

[0018] Computer-readable program instructions used to perform the operations of this invention may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, integrated circuit configuration data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​(such as Smalltalk, Python, C++, etc.) and procedural programming languages ​​(such as the "C" programming language or similar programming languages). The computer-readable program instructions may be executed entirely on a user's computer, partially on a user's computer, as a standalone software package, partially on a user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter case, the remote computer may be connected to the user's computer via any type of network (including a local area network (LAN) or a wide area network (WAN)) or may be connected to an external computer (e.g., via the Internet using an Internet service provider). In some embodiments, to perform aspects of this invention, electronic circuits, including, for example, programmable logic circuits, field-programmable gate arrays (FPGAs), or programmable logic arrays (PLAs), may execute computer-readable program instructions to personalize the electronic circuits by utilizing state information from the computer-readable program instructions.

[0019] This document describes various aspects of the invention with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-readable program instructions.

[0020] These computer-readable program instructions may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / actions specified in one or more blocks of a flowchart and / or block diagram. These computer-readable program instructions may also be stored in a computer-readable storage medium that causes a computer, programmable data processing apparatus, and / or other device to operate in a particular manner, wherein the computer-readable storage medium storing the instructions comprises an article of manufacture containing instructions that implement aspects of the functions / actions specified in one or more blocks of a flowchart and / or block diagram.

[0021] The computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other device to produce a computer-implemented process, thereby causing the instructions to be executed on the computer, other programmable apparatus, or other device to perform the functions / actions specified in one or more blocks of a flowchart and / or block diagram.

[0022] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of instructions containing one or more executable instructions for implementing a specified logical function. In some alternative implementations, the functions marked in the blocks may occur in a different order than those marked in the figures. For example, depending on the function involved, two consecutively shown blocks may actually be completed as a single step, executed simultaneously in a partially or fully temporarily overlapping manner, or these blocks may sometimes be executed in reverse order. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or action or executes a combination of dedicated hardware and computer instructions.

[0023] The exemplary embodiments described below provide systems, methods, and program products for exchanging data using portable, energy-efficient electronic devices. Therefore, this embodiment improves the technical field of portable electronic devices for exchanging information by providing a standalone electronic card device and a card holder (e.g., a card holder for a smartphone or other mobile device) configured to minimize the power consumption of the electronic card device and facilitate its convenient storage. More specifically, the card holder may include a magnet that engages with a magnet on the electronic card device when the electronic card device is mated (e.g., attached, placed, or inserted) in the card holder. If the electronic card device knows it is attached to a user's smartphone (e.g., mated in a card holder attached to the back of the user's smartphone), then the electronic card device may automatically transfer one or more stored pieces of information to the user's smartphone. If the electronic card device knows it is not attached to a user's smartphone (e.g., not mated in a card holder attached to the back of the user's smartphone), then the electronic card device may continue to store information until the electronic card device comes into contact with the user's smartphone.

[0024] As mentioned earlier, in atypical meeting environments, people can meet and exchange contact information, such as by exchanging business cards or other identifying information manually or electronically. While exchanging business cards or similar items may help people maintain long-term connections, it can be difficult to recall later which business card was associated with which person, especially, for example, if exchanging business cards in a populated environment such as a large conference where the meetings between people last only a short time. As another example, in such a large conference environment, it may not be possible to meet and exchange business cards with everyone or every ideal meeting person in the first place.

[0025] Therefore, it is particularly advantageous to provide a method for exchanging information using an electronic card device (ECD). It is also advantageous to provide a method for determining the presence of an ECD in a card holder (e.g., a smartphone-based holder) and, after making that determination, transferring information from the ECD to the user's smartphone. It is further advantageous to provide a convenient method for storing the electronic card device together with the user's smartphone.

[0026] According to at least one embodiment, the ECD may also be referred to as, for example, an electronic business card device, a business card device, a card device, a card, or a device. The ECD may be equipped with two magnets and two reed switches, arranged in pairs (magnets, reed switches). One magnet-reed pair may be configured to be powered on when the ECD is in the presence of another ECD (e.g., a partner's electronic business card), enabling the exchange of contacts and possibly other information. The other magnet-reed pair may be configured to be powered on when the ECD is mated in a card holder. The first and second reed switches may be arranged in parallel.

[0027] According to one embodiment, when the ECD is placed in the card holder of a user's smartphone, a second reed switch residing on the ECD, independent of the first reed switch, can be engaged to power the ECD. Then, if information is available, the ECD can exchange information contained on the ECD with the smartphone. Furthermore, the ECD can register an indication in its device memory that it is attached to the smartphone (e.g., docked in the card holder). Once this information is exchanged and / or registered to the ECD, the ECD can be automatically powered off via software. Next, when the ECD comes into contact with another ECD, the first reed switch can be engaged, and the ECD can exchange information. Again, once information is exchanged and / or registered to the ECD, the ECD can be automatically powered off via software. Thereafter, if the ECD knows it is attached to the user's smartphone, the ECD can immediately transmit accumulated information to the user's smartphone. If the ECD knows it is not attached to the user's smartphone, it stores the accumulated information for use when the ECD comes into contact with the smartphone.

[0028] According to at least one embodiment, when the ECD is "paired" or when a near-field communication (NFC) signal is detected at any time, the user can choose to exchange information only with the phone. It is conceivable that the option to only be available when paired could be more energy-efficient. Because of NFC's lower power consumption and lack of formal pairing requirements, NFC may be superior to... (Bluetooth and all Bluetooth-based trademarks and logos are trademarks or registered trademarks of Bluetooth SIG, Inc. and / or its subsidiaries.)

[0029] According to one implementation, by first connecting to an ECD in a secure area away from other NFC devices, a user can avoid accidentally transmitting information from their ECD to someone's phone or another NFC device other than the phone docked to the ECD (e.g., because it can receive nearby NFC signals). During the initial docking "handshake," the user's phone can identify itself by exchanging a unique number / token with the ECD. Thereafter, when sending messages, the electronic card device can use the token to encrypt the information sent to the user's phone.

[0030] According to one embodiment, when it is determined that an ECD is present in the card holder, the ECD can store a record of docking with the smartphone in its memory. When released from the card holder, this record can be updated to reflect that the ECD is no longer in close proximity to or docked with the smartphone.

[0031] According to one embodiment, if the ECD has stored contact information as a result of card-to-card interaction and is in the holder, the information can be transmitted to the user's smartphone via NFC, Bluetooth, or any other proximity-based communication mechanism. The ECD can automatically power off itself upon completion of the required transaction. It is conceivable that, as a result of this disclosure, the disclosed ECD may only require charging approximately once a year, or even be used continuously.

[0032] In some embodiments, the shared electronic information may include basic contact information. Other information, such as photographs, areas of interest, and matching one or more criteria, may also be shared. In some embodiments, the computer-implemented agent may filter or negotiate the sharing or exchange of information based on one or more criteria. Examples of criteria may include, but are not limited to, areas or topics of interest, job titles or roles, individuals with one or more specific professions (e.g., technical professions), or others. The computer-implemented agent may reside on and run on the ECD. In another embodiment, the computer-implemented agent may run on a remote computer system, such as in a cloud computing environment, communicate with the ECD, and act on behalf of the ECD. In some embodiments, the exchange of information (such as phone numbers) may require negotiation or permission.

[0033] In some embodiments, when information is shared with a participant or attendee of the same type of meeting, and that participant or attendee then exchanges information with others via their ECD, and those others have sufficiently overlapping interests as specified by matching criteria or standards, information about the newcomer can be sent to the original person, for example, with the newcomer's permission, to disseminate the information. Such permission or authorization can be specified and included as part of the criteria. If the newcomer encounters another person with sufficiently overlapping interests beyond the first person's matching criteria, then that person's contact information and interests can be relayed to the first person with that person's permission, and so on. In this way, any party to a meeting or conference can effectively satisfy everyone in the meeting or conference with matching interests exceeding a prescribed threshold. Then, based on the number or quantity of prescribed matching conditions, the virtually satisfied individuals can be prioritized for follow-up.

[0034] In some embodiments, the matching criteria need not be symmetrical. For example, an ECD may store extremely strict matching criteria associated with one party (e.g., specific or strictly defined interests, such as a particular technical field), while a second ECD associated with another meeting participant may store general, broad interest criteria, which could include virtual meetings with any participant or attendee. In some implementations, a person who waives information may simply be willing to waive their information if the overlap in interests exceeds their own threshold, rather than just the receiver's threshold. In other cases, meeting participants may not wish to exchange their information unless they meet the given individual in person. Therefore, the corresponding ECD can be stored and operated according to different criteria associated with a particular user. ECDs and methods thereof can support all such user criteria and their information exchange needs. Furthermore, the criteria for a given individual (and therefore the criteria associated with the ECD associated with that individual) may stipulate that providing personal information is for the exchange of small payments, such as to avoid bulk advertising.

[0035] In some embodiments, the business card device or ECD may include a processor, memory, and power source (such as a battery). A self-contained ECD can be initiated by detecting the addition of a new near-field device and can immediately begin the sequential exchange of information. In some embodiments, the user may not need to remove the device from their pocket or bag for this exchange.

[0036] In some embodiments, to avoid accidentally collecting contacts via proximity, the ECD can be implemented with a button or other actuator to initiate a contact exchange. The ECD can also be implemented with a sensor to detect movement such as shaking the ECD to initiate a contact exchange. For example, a user can shake the ECD to wake it (and potentially power the ECD in the process). In another aspect, the ECD can be implemented to detect taps and / or proximity to each other within millimeters and initiate a contact exchange in response. In various implementations, the device can be synchronized with the user's smartphone via wireless technologies such as NFC and Bluetooth.

[0037] In another embodiment, an ECD can be implemented to exchange tokens. The token can then be sent to or returned to another computer or system that can act on the token, for example, to send contact information associated with the token to a device associated with the user of the ECD. For example, a business ECD can be distributed to users attending a meeting, and the token exchange can be implemented. In one aspect, the ECD can be implemented to exchange tokens within a defined perimeter where the meeting takes place. When the ECD returns to the meeting's registration desk, a reader device can download the collected tokens, cross-reference the tokens with a registration database, and then send the collected contacts, along with other contacts matching one or more criteria for the user, to the user. In one aspect, this final transmission can be made via email, short message service (SMS), an application, or another service or method.

[0038] In embodiments of this disclosure, the ECD may include one or more power sources, such as a lithium-ion battery. The ECD may be encoded with program instructions for exchanging information and / or tokens. The ECD may be equipped with sensors capable of detecting the proximity of another such ECD. The card may transmit contact information electronically, and may also transmit information about other individuals when in close contact with another ECD. The level of detail of the exchanged information may be negotiated between the cards, for example, based on one or more criteria stored or retrieved by the ECD. In one aspect, a larger amount of contact information may be exchanged based on the similarity of the interests of the users of the discovered ECDs. The processor on the ECD may run a computer-implemented agent that can communicate with a neutral third-party agent (e.g., running on a remote computer system), providing the neutral third-party agent with information associated with the users of the ECD. The neutral third-party agent may determine the degree or level of commonality between the first ECD and another nearby ECD or device, and report the degree of commonality back to the agent operating as or on behalf of the ECD. Based on the level of commonality, the agent of the ECD may determine what information to share and provide that information to the neutral third-party agent. Then, a neutral third-party agent can transmit the shared information to another nearby ECD or device. As mentioned above, in another aspect, a computer-implemented agent can reside and operate remotely on behalf of the ECD and communicate with the ECD's processor. Yet another aspect allows for direct negotiation for sharing information between computer-implemented agents of the respective ECDs, for example, without the need for a third-party agent.

[0039] According to one embodiment, electronically transmitting contact and personal information can allow one party's contacts to share it with another party based on the consent of those parties and further agent-based negotiation establishing common interests. In one aspect, providing information can be in exchange for payment.

[0040] In one respect, contact information contained on or linked to a physical ECD can be uploaded (to a paired smartphone or similar device) using, for example, wireless technology standards (such as NFC or Bluetooth) in response to establishing proximity between the two devices. In another respect, contact information contained on a device similar to a physical business card can be uploaded to another device on demand, for example, via wireless communication or another communication method.

[0041] refer to Figure 1An exemplary networked computer environment 100 according to one embodiment is depicted. The networked computer environment 100 may include a computer 102 having a processor 104 and a data storage device 106 capable of running software program 108 and electronic card program 110a. The networked computer environment 100 may also include a server 112 capable of running electronic card program 110b that can interact with a database 114 and a communication network 116. The networked computer environment 100 may include multiple computers 102 and servers 112, only one of which is shown. The communication network 116 may include different types of communication networks, such as wide area networks (WANs), local area networks (LANs), telecommunications networks, wireless networks, public switched networks, and / or satellite networks. It should be understood that... Figure 1 This illustration provides only one possible implementation and does not imply any limitation regarding the environment in which different embodiments may be implemented. Many modifications can be made to the depicted environment based on design and implementation requirements.

[0042] Client computer 102 can communicate with server computer 112 via communication network 116. Communication network 116 may include connections such as wired, wireless communication links, or fiber optic cables. See below. Figure 6 As discussed, server computer 112 may include internal component 902a and external component 904a, and client computer 102 may include internal component 902b and external component 904b. Server computer 112 may also operate in a cloud computing service model (such as Software as a Service (SaaS), Platform as a Service (PaaS), or Infrastructure as a Service (IaaS)). Server 112 may also reside in a cloud computing deployment model, such as a private cloud, community cloud, public cloud, or hybrid cloud. Client computer 102 may be, for example, a mobile device, telephone, personal digital assistant, netbook, laptop computer, tablet computer, desktop computer, or any type of computing device capable of running programs, accessing networks, and accessing database 114. Depending on different implementations of this embodiment, electronic card programs 110a, 110b may interact with database 114, which may be embedded in different storage devices, such as, but not limited to, computer / mobile device 102, networked server 112, or cloud storage service.

[0043] Now refer to Figure 2 The document describes a block diagram illustrating an exemplary electronic card system 200 according to at least one embodiment. In one embodiment, the electronic card system 200 can be used in conjunction with [see also...] Figure 1 The networked computer environment described is implemented in a similar networked computer environment 100.

[0044] Electronic card system 200 may include means such as an electronic card device (ECD) 202 having the shape of a physical business card (or smart card or pocket-sized card or similar-sized card). In one embodiment, a first ECD 202 in electronic card system 200 may be adjacent to another device, such as a second ECD 204 (e.g., the other party's ECD) or a smartphone 206 (or a similar mobile device, such as, for example, a tablet or laptop computer)). In response to sensors on the respective devices (202, 204) detecting that the devices (e.g., ECD 202 and the other party's ECD 204) are within a threshold proximity (e.g., within a range of a few millimeters to about 25 centimeters), ECD 202 may pair with the other party's ECD 204 and begin wirelessly exchanging data. For example, ECD 202 may receive data (e.g., contact information associated with user 204a of the other party's ECD 204) and send the contact information associated with user 202a of ECD 202 to the other party's ECD 204. Alternatively, a token with an identifier associated with user 204a of the other party ECD204 can be received, and the token can be converted into contact information by another device (e.g., a computer system that reads the token and retrieves the contact information associated with the token from a database). The computer system may reside in the cloud, on another remote computer, or on ECD202, 204.

[0045] According to one embodiment, wireless technology (such as NFC) can enable communication between devices 202, 204, and 206, for example, when at least two such devices are within sufficient proximity. In at least some embodiments, different other wireless technologies, such as Bluetooth, standard Wi-Fi as defined by the IEEE 802.11 protocol, may be used alternatively or additionally. Such wireless technologies can allow pairing and information exchange between devices (e.g., ECD 202, 204).

[0046] According to one embodiment, ECD 202 and the counterpart ECD 204 may include one or more components, as will be further detailed with reference to ECD 202. In one embodiment, ECD 202 may include one or more pieces of information 210 stored in memory 212. Information 210 may include contact information, information about other individuals, and / or a photograph corresponding to user 202a, who may want to exchange the photograph with another person (e.g., user 204a in a meeting environment). In one embodiment, information 210 may be preloaded onto ECD 202 for exchange with one or more other devices (e.g., counterpart ECD 204). In another embodiment, memory 212 may include a token 208 having a specific identifier associated with ECD 202. Token 208 may be associated with or linked to a record in a remote (e.g., cloud-hosted) database that stores user 202a's information (e.g., contact information, information about other individuals, and / or photographs).

[0047] In one aspect, ECD 202 may include a smart card with a microchip or integrated circuit (IC) 214 embedded. In at least one embodiment, ECD 202 may include executing electronic card programs 110a, 110b (in... Figure 1 The microprocessor (shown in the diagram) is used. Electronic card programs 110a and 110b may include a single computer program or multiple program modules or instruction sets executed by one or more processors in a networked computer environment. Electronic card programs 110a and 110b may be implemented in a distributed cloud computing environment, where tasks can be performed by remote processing devices connected via a communication network (e.g., communication network 116). In one embodiment, electronic card programs 110a and 110b may include components that can be co-stored on one or more computer-readable storage media (such as, for example, memory 212) or other storage devices (e.g., memory 212, memory 212, memory 213, memory 214, memory 215, memory 216, memory 215, memory 216, memory 216, memory 217, memory 218, memory 219 ... Figure 1 The program instructions on the storage device 106 and database 114 shown. Electronic card programs 110a and 110b may include routines, objects, components, units, logic, data structures, and actions that can perform specific tasks or implement specific abstract data types.

[0048] According to one embodiment, electronic card programs 110a and 110b can be executed to act as agents for negotiating information exchange between ECD 202 and the counterpart ECD 204. For example, electronic card programs 110a and 110b (e.g., agent components) executing on a microprocessor can determine whether information (such as the interests of user 202a of ECD 202) intersects with information (such as the interests of user 204a of the counterpart ECD 204). In response to determining an intersection at a threshold level of interest, electronic card programs 110a and 110b can be executed to exchange contact information between ECD 202 and the counterpart ECD 204. The interests of the respective users 202a and 204a can be stored in the respective ECDs 202 and 204 and / or downloaded from a computer system storing such information in a database.

[0049] In one embodiment, electronic card programs 110a, 110b can incorporate the current context during negotiated information exchange. For example, the current context may include criteria for matching the interests of user 202a of designated ECD 202 with the interests of user 204a of counterpart ECD 204. The current context may also include the current meeting settings, such as meetings or meetings attended by individuals associated with the ECD. ECD 202 can verifiably establish that the individual associated with counterpart ECD 204 is a participant in the meeting or conference, for example, by querying a database of participants in the meeting, by obtaining or receiving electronic signals from badges associated with the meeting, or by other methods. In one example, only participants or attendees of a meeting or conference can be given such an ECD, and therefore, by contacting another such ECD, it is possible to automatically determine that an individual is a participant in a similar meeting or conference.

[0050] In one embodiment, ECD 202 may be configured or programmed to communicate with smartphone 206 to upload information accumulated in ECD 202 (e.g., received from another ECD 204) to smartphone 206.

[0051] In one embodiment, ECD 202 may include a light-emitting diode (LED) 216 configured for status indication. In one embodiment, LED 216 may be illuminated when negotiation between ECD 202 and peer ECD 204 begins (e.g., in response to initiating negotiation). In one embodiment, LED 216 may be turned off after negotiation between ECD 202 and peer ECD 204 fails or information exchange is completed (e.g., negotiation ends). Different LED shading methods may be employed in various embodiments. For example, LED 216 may be configured to turn yellow at the start of contact and during negotiation between ECD 202 and peer ECD 204. LED 216 may then be configured to briefly turn green once negotiation is determined to have succeeded, or briefly turn green if negotiation is determined to have failed. In other embodiments, LED 216 may employ different shading methods. In another aspect, ECD 202 may be configured to vibrate at the start of negotiation and to stop vibrating after negotiation fails or information exchange is completed.

[0052] According to one embodiment, electronic card programs 110a, 110b can be executed to control the power cycle of ECD 202 (e.g., power on / off) in order to minimize the energy requirements of ECD 202's battery 218, as will be further detailed below.

[0053] In one embodiment, ECD 202 may be initially (e.g., by default) completely de-energized. In one embodiment, ECD 202 may be powered off when disconnected from the other ECD 204 and before docking with smartphone 206, as described below. In at least one embodiment, ECD 202 may be energized by engaging the other ECD 204. In various embodiments, as will be described further in detail below, ECD 202 may be energized by docking with smartphone 206. In one embodiment, electronic card programs 110a, 110b may have two different startup scripts based on whether ECD 202 is energized from contact with the other ECD 204 or from contact with smartphone 206. In another embodiment, electronic card programs 110a, 110b may have a startup script including parameters indicating whether ECD 202 is powered from contact with the other ECD 204 or from contact with smartphone 206. Alternatively, electronic card programs 110a and 110b may have a startup script and implement a proximity-based communication mechanism (e.g., NFC, Bluetooth) to determine whether ECD 202 is connected to the other party ECD 204 or smartphone 206.

[0054] In at least one embodiment, ECD 202 may automatically power off in response to physical disconnection from the other party ECD 204 and / or smartphone 206, as will be further detailed below. In various embodiments, ECD 202 may power off smartphone 206 via settings on the accompanying application components of electronic card programs 110a, 110b running on smartphone 206.

[0055] In one aspect, the energization and de-energization of ECD202 and 204 can be achieved by interlocking the magnet of the ECD and the accompanying reed device. In another aspect, the energization and de-energization of ECD202 and 204 can be achieved by a physical mechanical switch.

[0056] ECD 202 may include two magnets (first magnet 220a and second magnet 222a) and two switching devices (first switching device 220b and second switching device 222b). In various embodiments, switching devices 220b, 222b may include one or more reed relays and / or reed switches. In at least some embodiments, the two switching devices 220b, 222b may also include mechanical switches. Therefore, embodiments of this disclosure may use the term "switch" to include reed relays, reed switches, and / or mechanical switches. In one embodiment, the two magnets and two switching devices may be arranged as a magnet-switch pair, wherein the first magnet 220a and the first switching device 220b provide a first magnet-switch pair, and the second magnet 222a and the second switching device 222b provide a second magnet-switch pair. According to one embodiment, the first and second switching devices 220b, 220b may be arranged in parallel and provide two paths for completing a circuit configured to turn on or activate ECD 202 (e.g., by turning on a mechanical switch or engaging a reed switch or relay).

[0057] The counterparty ECD204 may similarly include a first magnet 224a and a first switching device 224b arranged in a first magnet-switch pair, and a second magnet 226a and a second switching device 226b arranged in a second magnet-switch pair.

[0058] According to one embodiment, when the first switching device 220b of ECD 202 and the first switching device 224b of the counterpart ECD 204 are mechanical switches, a magnet may not be necessary. In various embodiments, the first mechanical switch of ECD 202 (e.g., the first switching device 220b) and the first mechanical switch of the counterpart ECD 204 (e.g., the first switching device 224b) can be pressed together in opposite directions to complete the corresponding circuit path and energize the respective ECDs.

[0059] In one embodiment, the first magnet-switch pair of ECD 202 (e.g., first magnet 220a, first switching device 220b) can engage the first magnet-switch pair of the other ECD 204 (e.g., first magnet 224a, first switching device 224b), such that the interaction between the first magnet 220a of ECD 202 and the first magnet 224a of the other ECD 204 can actuate the first switching devices 220b and 224b of ECD 202 and 204, respectively. Therefore, the first magnets 220a and 224a on the respective ECDs 202 and 204 can activate the accompanying switching devices 220b and 224b to close a first circuit path (operationally coupled to the switching device) and energize the respective ECDs 202 and 204. In one embodiment, the first magnet-switch pair of ECD 202 can be configured to disengage from the corresponding first magnet-switch pair of the other ECD 204 to de-energize ECD 202. Switches 220b and 224b can spring back to the closed position, allowing them to re-engage in response to contact between ECD 202 and the other ECD 204.

[0060] According to other embodiments, when the first switching device 220b of ECD 202 and the first switching device 224b of the counterpart ECD 204 are mechanical switches, the magnet can be paired with the mechanical switch (e.g., a magnet-mechanical switch pair). In such an embodiment, the interaction between the first magnet 220a of ECD 202 and the first magnet 224a of the counterpart ECD 204 can respectively activate the first mechanical switches of ECD 202 and 204 to complete their respective circuit paths and turn on their respective ECDs.

[0061] In at least one embodiment, the smartphone 206 of the first user 202a may include a docking component, such as a holder 228. In one embodiment, the holder 228 may be configured to receive an ECD 202 for storage and portability. The ECD 202 may dock with the smartphone 206 in the holder 228 and is configured to transmit or exchange data stored in the ECD 202 (e.g., data received from a peer ECD) with the smartphone 206. In one embodiment, the holder 226 may be removably attached to the smartphone 206. In one embodiment, the holder 228 may include an actuator, such as a third magnet 230, which may interact with a second magnet 222a of the ECD 202 when the ECD 202 is received by the holder 228 (e.g., placed or docked). The interaction between the third magnet 230 of the holder 228 and the second magnet 222a of the ECD 202 can activate the second switching device 222b of the ECD 202 to close the second circuit path (operationally coupled to the switching device), which is configured to energize the ECD 202.

[0062] According to one embodiment, when the second switching device 222b of ECD 202 is a second mechanical switch, the second magnet 222a of ECD 202 is optional. In such an embodiment, the third magnet 230 of holder 228 may be configured to actuate the second mechanical switch to close a second circuit path (operationally coupled to the mechanical switch) configured to energize ECD 202. According to another embodiment, holder 228 may include a mechanical actuator configured to engage (e.g., press) the second mechanical switch to close the second circuit path configured to energize ECD 202. According to at least one embodiment, the actuator in holder 228 may include a third mechanical switch. In this implementation, the interaction (e.g., pressing together) of the second mechanical switch of ECD 202 and the third mechanical switch of holder 228 in opposite directions may activate the second switching device 222b of ECD 202 to close the second circuit path configured to energize ECD 202. Furthermore, activating the third mechanical switch can alert the docking component to communication from the ECD202, allowing the docking component to be put into more cycles to NFC or Bluetooth.

[0063] When ECD 202 is placed or docked in holder 228, a second switching device 222b contained in ECD 202 can engage independently of the first switching device 220b to energize ECD 202. The second switching device 222b can be activated in response to an interaction between the third magnet 230 of holder 228 and the second magnet 222a of ECD 202. Once ECD 202 is docked in holder 228 and energized, electronic card programs 110a, 110b can exchange information 210 with smartphone 206 if new information is available. In one embodiment, electronic card programs 110a, 110b can register the docking status in memory 212 of ECD 202. In various embodiments, once the information exchange between ECD 202 and smartphone 206 is completed and / or the docking status is registered in memory 212, electronic card programs 110a, 110b can implement a script to de-energize ECD 202. According to one embodiment, if ECD 202 contacts ECD 204, the first switching device 220b can be engaged to turn on ECD 202, as previously described. Next, electronic card programs 110a and 110b can be executed to exchange information 210 between ECDs 202 and 204. Subsequently, if electronic card programs 110a and 110b determine that ECD 202 is connected to smartphone 206, they can transmit the received information to smartphone 206. If not, electronic card programs 110a and 110b can store the received information in memory 212 until ECD 202 contacts smartphone 206.

[0064] According to one embodiment, electronic card programs 110a and 110b can determine whether ECD 202 is docked with smartphone 206 by checking the docking status in memory 212. In another embodiment, electronic card programs 110a and 110b can implement NFC or other communication methods (e.g., Bluetooth) to determine whether ECD 202 is close enough to smartphone 206 for transmitting information to smartphone 206.

[0065] According to at least one embodiment, electronic card programs 110a, 110b enable user 202a to select a first option associated with exchanging information with smartphone 206 only when ECD 202 is docked in holder 228 (e.g., in an accompanying application running on smartphone 206). Electronic card programs 110a, 110b may also provide a second option associated with exchanging information with smartphone 206 at any time an NFC signal is detected from smartphone 206 (e.g., when ECD 202 is sufficiently close to smartphone 206 but not docked in holder 228). It is contemplated that selecting the first option (e.g., the docking-only option) may be more energy-efficient for ECD 202 than selecting the second option (e.g., the NFC signal detection option).

[0066] According to one embodiment, electronic card programs 110a, 110b can implement NFC to enable wireless communication between ECD 202 and smartphone 206. Due to the lower power consumption of NFC in battery 218 and the lack of formal pairing requirements between ECD 202 and smartphone 206, NFC is likely preferred over Bluetooth. When user 202a first connects ECD 202 to smartphone 206, smartphone 206 can exchange a unique number or identification token with ECD 202. After this first handshake operation, when sending information to smartphone 206, ECD 202 can use the unique number or identification token to encrypt the information being sent to smartphone 206. In one embodiment, user 202a can perform the first handshake operation in a secure area away from any other NFC device to ensure that the unique number or identification token received by ECD 202 originates from smartphone 206.

[0067] As a result of the first handshake operation and the encryption of information using the unique number or identification token of smartphone 206, the problem of unintentionally transmitting information (e.g., contact information) to another user's smartphone (e.g., because it can receive nearby NFC signals) instead of user 202a's smartphone 206 can be avoided.

[0068] In some embodiments, ECD 202 may include a physical switch configured to allow user 202a to manually power on / off ECD 202. For example, if user 202a does not have a holder 228 attached to smartphone 206, user 202a can use the physical switch to manually power on ECD 202 for exchanging information when in proximity to smartphone 206. Subsequently, user 202a can use the physical switch to power off ECD 202.

[0069] In another embodiment, ECD 202 may be powered on by default, and control over functions for power-off and docking with smartphone 206 may be provided via settings on an accompanying application running on smartphone 206. In this embodiment, ECD 202 may be updated with the latest settings via NFC the next time ECD 202 connects to smartphone 206 (e.g., via docking).

[0070] In another embodiment, when ECD 202 is powered on by activating the first switching device 220b, ECD 202 can be powered off until it first encounters the other ECD 204. Thereafter, ECD 202 can remain powered on (e.g., even after losing contact with the other ECD 204) until ECD 202 uploads accumulated information to smartphone 206. Subsequently, electronic card programs 110a, 110b can software-shut down ECD 202. Therefore, ECD 202 can be powered off until it first captures new information from another ECD (e.g., the other ECD 204), after which ECD 202 can remain powered on until the accumulated information is uploaded to the paired smartphone 206.

[0071] According to this embodiment, a user using client computer 102 or server computer 112 can use electronic card programs 110a, 110b (correspondingly) to exchange information about using portable energy-saving electronic devices (e.g., ECD 202) with another user. See below for further details. Figure 2 (detailed description above) and Figures 3 to 5 (Detailed description below) The electronic card method is explained in more detail.

[0072] According to one embodiment, an electronic card method typically includes connecting a first ECD to another second ECD (e.g., a peer ECD). The electronic card method then includes energizing the ECD via a first switching device (e.g., a first reed switch / relay) in response to interaction between corresponding first magnets of the first ECD and corresponding first magnets of the second ECD. Next, the electronic card method may include exchanging information with the second ECD via NFC or another wireless communication protocol. Subsequently, the electronic card method may include determining whether the first ECD is docked with a mobile device. If the electronic card method determines that the first ECD is docked with a mobile device, the electronic card method may include exchanging information with the mobile device via NFC or another wireless communication protocol (e.g., uploading accumulated information from the first ECD to the mobile device). If the electronic card method determines that the first ECD is not docked with a mobile device, the electronic card method may include de-energizing the first ECD by losing contact with the second ECD (deactivation of the first switching device) or by powering it off via a software instruction after exchanging information with the second ECD.

[0073] In at least one embodiment, the electronic card method may include: after one or more information exchanges between the first ECD and other second ECDs, the first ECD docks with the mobile device. The electronic card method may then include energizing the first ECD via a second switching device (e.g., a second reed switch / relay) in response to interaction between a second magnet of the first ECD and a third magnet of a card or ECD holder attached to the user's mobile device. Once docked with the mobile device, the electronic card method may include the first ECD exchanging information with the mobile device via NFC or other wireless communication protocols. Subsequently, the electronic card method may include de-energizing the first ECD via software instructions to de-energize it after exchanging information with the mobile device.

[0074] See now Figure 3 The description depicts, according to at least one embodiment, such as in combination Figure 2 The flowchart describes the operation of an exemplary energy-saving data exchange process 300 used by electronic card programs 110a and 110b.

[0075] At 302, power is detected via a first switching device. According to one embodiment, the first ECD (e.g., ECD 202) can contact another second ECD (e.g., counterpart ECD 204) to exchange information stored on the respective ECDs. Electronic card programs 110a, 110b can detect activation of the first switching device (e.g., a switch or relay) in the first ECD to turn it on.

[0076] As previously referenced Figure 2 The ECD may include two magnets and two switching devices arranged as magnet-switch pairs, wherein a first magnet and a first switching device provide a first magnet-switch pair, and a second magnet and a second switching device provide a second magnet-switch pair. According to one embodiment, the first and second switching devices may be arranged in parallel and provide two paths for completing a circuit (e.g., via physically turning on a switch or engaging a switch relay), the circuit being configured to energize or activate the ECD. In an embodiment, the first magnet-switch pair of the ECD may engage the first magnet-switch pair of the other ECD such that interaction between the first magnets on the respective ECDs can activate an accompanying first switching device to close a first circuit path and energize the respective ECD. Electronic card programs 110a, 110b may determine that the second ECD is within a threshold proximity of the first ECD in response to detecting activation of the first switching device. In one embodiment, the first and second ECDs may be snapped together in response to interlocking of the first magnet of the first ECD with the corresponding first magnet of the second ECD.

[0077] Then, at 304, data is exchanged with the other ECD. In response to the first ECD's first magnet-switch pair engaging the corresponding first magnet-switch pair of the second or other ECD to power on the first ECD, the first ECD can initiate communication. The ECD's memory can load information associated with the ECD's user. In one embodiment, as previously referenced... Figure 2 As described, the electronic card programs 11Oa and 11Ob executing on the microprocessor of the ECD can negotiate data exchange with the other ECD based on the current context. Exchangeable data may include, for example, contact information, personal information and / or photographs, and / or other information. Alternatively, information loadable into memory may include tokens linked to records in a database storing information such as contact information, personal information, and / or photographs. The current context may include criteria for matching the interests of a first user of the ECD with the interests of a second user of the other ECD, as identified by the ECD. The current context may also include criteria that the first user of the ECD and the second user of the other ECD are participants in a designated meeting.

[0078] Then at 306, electronic card programs 110a, 110b determine whether the ECD is docked to a mobile device. According to one embodiment, the user's mobile device (e.g., smartphone 206) may include a docking component or holder (e.g., holder 228) configured to receive the ECD for storage and portability. In one embodiment, the holder may include a third magnet that can interact with a second magnet of the ECD when the ECD is placed inside the holder (e.g., docked). The interaction between the third magnet of the holder and the second magnet of the ECD can activate a second switching device of the ECD to close a second circuit path configured to energize the ECD. In one embodiment, electronic card programs 110a, 110b may register a docking state or docking record in the memory of the ECD in response to detecting that the second switching device has closed the second circuit path to energize the ECD. Therefore, electronic card programs 110a, 110b can determine whether the ECD is docked to a mobile device by checking the docking state in the ECD's memory. In another embodiment, electronic card programs 110a, 110b may implement NFC or any other proximity-based communication mechanism (e.g., Bluetooth) to determine whether the ECD is close enough to the mobile device so that the ECD can be docked in the holder.

[0079] If the electronic card procedures 110a and 110b determine that the ECD is docked at 306, then at 312, information is exchanged with the mobile device, as will be further described below. However, if the electronic card procedures 110a and 110b determine that the ECD is not docked at 306, then at 308, the ECD is de-energized. According to one embodiment, the ECD can be de-energized by losing contact with the other ECD. The electronic card procedures 110a and 110b can detect the deactivation of a first switching device configured to de-energize the first ECD in response to the second ECD being outside a threshold proximity to the first ECD. In such an embodiment, the first magnet of the corresponding ECD may not interact, resulting in the deactivation of the first switching device and the disconnection or interruption of the first circuit path. In at least one embodiment, the BECD procedures 110a and 110b can execute a shutdown script to automatically de-energize the ECD upon completion of a transaction with the other ECD. According to one embodiment, before the ECD is powered off, electronic card programs 110a, 110b can store received or accumulated data in the ECD's memory until the ECD comes into contact with a mobile device (e.g., is received in a holder). In one embodiment, electronic card programs 110a, 110b can also update the records in the ECD's memory to reflect when the ECD is not docked with a mobile device (e.g., by recording an un-docked state).

[0080] In some instances, an ECD can be connected to multiple other ECDs (e.g., multiple peer ECDs) to exchange information before docking the ECDs to transfer data to a mobile device. In such cases, the electronic card process 300 can return to 302 to access power via a first reed device in response to connection to another ECD.

[0081] Then, at 310, power is detected via a second switching device. When the ECD is inserted into the holder (e.g., docked), the second switching device (e.g., a reed switch / relay or mechanical switch) included in the ECD can be engaged to energize the ECD independently of the first switching device. In one embodiment, electronic card programs 110a, 110b can detect the activation of the second switching device to turn on the ECD. The second switching device can be activated in response to the interaction between a third magnet of the holder and a second magnet of the ECD, as previously referenced. Figure 2 In one embodiment, electronic card programs 110a and 110b may detect the closure of a second circuit path in response to the interaction between a third magnet of the holder and a second magnet of the ECD. In another embodiment, electronic card programs 110a and 110b may also energize the ECD and register a docking state or docking record in the ECD's memory in response to the detection of activation of the second reed device.

[0082] Next, at 312, the data is transmitted to the mobile device. Once the ECD is docked in the holder and powered on, electronic card programs 110a, 110b can initiate data transfer to the mobile device if new information is available. In one embodiment, for example, by receiving data from a peer ECD, the data to be transferred may include information accumulated in the ECD. In one embodiment, electronic card programs 110a, 110b executing on the microprocessor or microcontroller of the ECD may use NFC or other proximity-based communication mechanisms to perform the data transfer to the mobile device. In another embodiment, a remote agent communicating with the microprocessor or microcontroller of the ECD can initiate the transfer of information to the mobile device.

[0083] Power was then cut off at 314. Once data has been transmitted or uploaded to a mobile device, electronic card programs 110a and 110b can implement a shutdown script to automatically shut down the ECD.

[0084] According to one embodiment, when an ECD is docked to a mobile device and powered off via software (e.g., a shutdown script), it can interact with other ECDs to exchange data. In such embodiments, in response to connecting to another ECD, the electronic card process 300 can return to 302 to engage power via a first switching device.

[0085] In different embodiments, if the ECD is carried in the holder of the mobile device, the electronic card process can begin at 312, where the ECD is energized via activation of a second switching device, as previously described. Referring below... Figure 5 This interaction will be described further.

[0086] Now for reference Figure 4 Electrical diagram 400 depicts an exemplary electronic card device (ECD) 402 according to at least one embodiment. According to one embodiment, ECD 402 may be similar to ECD 202 and its counterpart ECD 204, as previously referenced. Figure 2 As stated above.

[0087] According to one embodiment, ECD 402 may include a first magnet 404a capable of activating another such peer ECD and a second magnet 404b capable of interacting with a third magnet of an ECD holder, as referenced. Figure 2As described. In one embodiment, ECD 402 may include a microcontroller 406, such as, for example, the depicted ultra-low power microcontroller: MSP430-G2 (but not limited thereto). In one embodiment, microcontroller 406 may be connected to a switching circuit 408 comprising two switching devices (e.g., reed devices) connected in parallel. In one embodiment, a first reed relay 410a of switching circuit 408 completes a first circuit path 412a, and a second reed relay 410b of switching circuit 408 completes a second circuit path 412b. Other switching devices (e.g., mechanical switches), as previously described, are also contemplated in various embodiments.

[0088] In one embodiment, the first reed relay 410a may be activated (e.g., turned on) in response to the presence of a first magnet 414 of another ECD in the vicinity of ECD 402. Similarly, the first reed relay 410a may be deactivated (e.g., turned off) when the first magnet 414 of the other ECD is not in the vicinity. In one embodiment, the second reed relay 410b may be activated (e.g., turned on) in response to the interaction of a second magnet 404b of ECD 402 with a third magnet of the ECD holder (not shown). As previously described, activation of the second reed relay 410b may automatically trigger the sending or exchange of data with a mobile device. Although not specifically depicted, in various embodiments, ECD 402 may also include a button that can be manually triggered to send or exchange data with a mobile device.

[0089] In at least one embodiment, the microcontroller 406 may also be coupled to an NFC module 416, which may allow the ECD 402 to communicate with another device (e.g., another peer ECD and / or mobile device). Although not specifically depicted, in various embodiments, the ECD 402 may also include a Wi-Fi module and other wireless communication modules, such as a Bluetooth module for performing proximity-based communication with another device.

[0090] In various embodiments, ECD 402 may include an LED assembly 418. In one embodiment, LED 418 may be illuminated in different shades based on the different functions performed in ECD 402. For example, LED 418 may be illuminated in red to indicate that the device is ready, LED 418 may be illuminated in yellow to indicate that information is being shared or exchanged with another device, and LED 418 may be illuminated in green to indicate that an identifier has been received. Other light-colored encoding may also be utilized. Although not specifically depicted, in various embodiments, ECD 402 may also include a vibration assembly. In one embodiment, the vibration assembly may vibrate to indicate different functions or modes of ECD 402. For example, in response to initiating negotiation to share or exchange information, the vibration assembly may vibrate and may stop vibrating after negotiation fails or after information exchange is completed.

[0091] According to one embodiment, ECD 402 may further include a programming port 420 that enables programming of microcontroller 406. In one embodiment, programming port 420 enables ECD 402 to be programmed using electronic card programs 110a, 110b. In one embodiment, electronic card programs 110a, 110b running on microcontroller 406 enable microcontroller 406 to function as an energy-saving agent that can provide data to another device (e.g., a peer ECD), receive data from another device (e.g., a peer ECD), and / or exchange data with another device (e.g., a peer ECD) in a manner configured to conserve energy provided by battery 422 to power ECD 402. The energy-saving agent can also be used to upload accumulated data from other devices to another device, such as a mobile device (e.g., a smartphone, tablet, laptop computer), and / or another computer system in a manner configured to conserve energy of battery 422.

[0092] Now refer to Figure 5 A block diagram 500 depicts an exemplary electronic card interaction between a first ECD 502 and a second ECD 504 according to at least one embodiment. According to one embodiment, the first and second ECDs 502, 504 may be similar to those previously referenced. Figure 2 The ECD 202 and 204 described.

[0093] In such Figure 5In the embodiments depicted, the first ECD 502 may be located in a holder 506 (e.g., a docking assembly) attached to a mobile device 508. In one embodiment, the mobile device 508 may include a smartphone. In other embodiments, the mobile device 508 may include other user devices, such as, for example, a tablet or laptop computer. The first ECD 502 may include two magnets (a first magnet 510a and a second magnet 512a) and two switching devices (a first reed device 510b and a second reed device 512b). In one embodiment, the two magnets and the two reed devices may be arranged as a magnet-reed pair, wherein the first magnet 510a and the first reed device 510b provide a first magnet-reed pair, and the second magnet 512a and the second reed device 512b provide a second magnet-reed pair. According to one embodiment, the holder 506 may include a third magnet 518 configured to engage the second magnet 512a of the first ECD 502.

[0094] According to one embodiment, a first magnet-reed pair may be provided or arranged on the first end portion of the corresponding ECD 502, 504, and a second magnet-reed pair may be provided or arranged on the second end of the corresponding ECD 502, 504 opposite to the first end, such as... Figure 5 As shown, this allows ECD 502 to interact simultaneously with the third magnet 518 of retainer 506 and the first magnet-reed pair (e.g., 514a, 514b) of counterpart ECD 504.

[0095] According to one embodiment, electronic card programs 110a and 110b running on the first ECD 502 can determine that the first ECD 502 is docked in the holder 506 based on the activation (to energize the ECD) of the second reed device 512b in response to the interaction between the second magnet 512a of the ECD 502 and the third magnet 518 of the holder 506. After inferring the presence of the first ECD 502 in the holder 506, the electronic card programs 110a and 110b can register the docking status or record in the memory of the first ECD 502. Then, the electronic card programs 110a and 110b can transmit any new data stored in the first ECD 502 to the mobile device 508 via NFC or any other proximity-based communication mechanism. After the information is transmitted to the mobile device 508, the first ECD 502 can be automatically shut down via a shutdown script implemented by the electronic card programs 110a and 110b.

[0096] Subsequently, the first ECD 502, docked in the holder 506 of the mobile device 508 and powered off via software, can interact with the second ECD 504 to exchange data.

[0097] In one embodiment, a first magnet-reed pair (e.g., first magnet 510a, first reed device 510b) of the first ECD 502 can engage a first magnet-reed pair (e.g., first magnet 514a, first reed device 514b) of the second ECD 504, such that the interaction between the first magnet 510a of the first ECD 502 and the first magnet 514a of the second ECD 504 can actuate the first reed devices 510b and 514b of the ECDs 502 and 504, respectively. Therefore, the first magnets 510a and 514a on the respective ECDs 502 and 504 can activate the accompanying reed devices 510b and 514b to close the first circuit path and connect the respective ECDs 502 and 504.

[0098] In one embodiment, the electronic card programs 110a, 110b executing on the microprocessor of the first ECD 502 can negotiate data exchange with the second ECD 504 based on the current context, as previously referenced. Figure 2 As described, once the data exchange between the ECDs is completed, the electronic card programs 110a and 110b can determine whether the first ECD 502 is docked with the mobile device 508 based on the docking status recorded in the memory of the first ECD 502. In response to determining the docking status, the electronic card programs 110a and 110b executing on the first ECD 502 can use NFC or other proximity-based communication mechanisms to transfer the received data to the mobile device 508. Afterward, the first ECD 502 can be automatically powered off again via a power-off script implemented by the electronic card programs 110a and 110b.

[0099] The computer's functionality can be enhanced by electronic card programs 110a and 110b, as these programs enable the computer to minimize the energy requirements of portable ECDs configured for exchanging data with other electronic devices. Electronic card programs 110a and 110b allow the computer to determine if another electronic device is within wireless communication range by detecting the ECD's power-on status (e.g., a first or second reed device) rather than relying on more energy-intensive proximity-based communication mechanisms. Electronic card programs 110a and 110b also enable the computer to automatically power off the ECD when the required data exchange transaction is complete.

[0100] It can be recognized that, Figures 2 to 5 The examples provided are merely illustrative and do not imply any limitation on how different embodiments may be implemented. Many modifications may be made to the depicted embodiments based on design and implementation requirements.

[0101] Figure 6 This is according to an exemplary embodiment of the present invention. Figure 1Block diagram 900 depicts the internal and external components of a computer. It should be understood that... Figure 6 This illustration provides only one possible implementation and does not imply any limitation regarding the environment in which different embodiments may be implemented. Many modifications can be made to the depicted environment based on design and implementation requirements.

[0102] Data processing systems 902 and 904 represent any electronic device capable of executing machine-readable program instructions. Data processing systems 902 and 904 can represent smartphones, computer systems, PDAs, or other electronic devices. Examples of computing systems, environments, and / or configurations that can be represented by data processing systems 902 and 904 include, but are not limited to, personal computer systems, server computer systems, thin clients, thick clients, handheld or laptop devices, multiprocessor systems, microprocessor-based systems, network PCs, minicomputer systems, and distributed cloud computing environments that include any of the aforementioned systems or devices.

[0103] The user client computer 102 and the network server 112 may include Figure 6 The diagram shows corresponding sets of internal components 902a, 902b and external components 904a, 904b. Each set of internal components 902a, 902b includes one or more processors 906, one or more computer-readable RAMs 908 and one or more computer-readable ROMs 910 on one or more buses 912, as well as one or more operating systems 914 and one or more computer-readable tangible storage devices 916. One or more operating systems 914, software programs 108 and electronic card programs 110a in client computer 102 and electronic card programs 110b in network server 112 may be stored on one or more computer-readable tangible storage devices 916 for execution by one or more processors 906 via one or more RAMs 908 (which typically include cache memory). Figure 6 In the embodiment shown, each computer-readable tangible storage device 916 is a disk storage device of an internal hard disk drive. Alternatively, each computer-readable tangible storage device 916 is a semiconductor storage device, such as ROM 910, EPROM, flash memory, or any other computer-readable tangible storage device capable of storing computer programs and digital information.

[0104] Each set of internal components 902a, 902b also includes an R / W drive or interface 918 for reading and writing from one or more portable computer-readable physical storage devices 920 (such as CD-ROM, DVD, Memory Stick, magnetic tape, disk, optical disc, or semiconductor storage devices). Software programs (such as software program 108 and electronic card programs 110a and 110b) can be stored on one or more of the respective portable computer-readable physical storage devices 920, read from the respective R / W drive or interface 918, and loaded into the respective hard disk drive 916.

[0105] Each set of internal components 902a, 902b may also include a network adapter (or switch port card) or interface 922, such as a TCP / IP adapter card, a wireless Wi-Fi interface card, or a 3G or 4G wireless interface card, or other wired or wireless communication links. Software program 108 and electronic card program 110a in client computer 102 and electronic card program 110b in network server computer 112 may be downloaded from an external computer (e.g., a server) via a network (e.g., the Internet, a local area network, or another wide area network) and the corresponding network adapter or interface 922. Software program 108 and electronic card program 110a in client computer 102 and electronic card program 110b in network server computer 112 are loaded into the corresponding hard disk drive 916 from the network adapter (or switch port adapter) or interface 922. The network may include copper wire, fiber optic, wireless transmission, routers, smartphones, switches, gateway computers, and / or edge servers.

[0106] Each set of external components 904a, 904b may include a computer display monitor 924, a keyboard 926, and a computer mouse 928. External components 904a, 904b may also include a touchscreen, a virtual keyboard, a touchpad, a pointing device, and other human-machine interface devices. Each set of internal components 902a, 902b also includes a device driver 930 connected to the computer display monitor 924, keyboard 926, and computer mouse 928. The device driver 930, R / W driver or interface 918, and network adapter or interface 922 include hardware and software (stored in storage device 916 and / or ROM 910).

[0107] It should be understood in advance that although this disclosure includes a detailed description of cloud computing, the implementation of the teachings set forth herein is not limited to a cloud computing environment. Rather, embodiments of the invention can be implemented in conjunction with any other type of computing environment now known or developed hereafter.

[0108] Cloud computing is a service delivery model for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, network bandwidth, servers, processing, memory, storage, applications, virtual machines, and services) that can be rapidly provisioned and released with minimal management effort or interaction with service providers. This cloud model may include at least five features, at least three service models, and at least four deployment models.

[0109] The characteristics are as follows:

[0110] On-demand self-service: Cloud consumers can unilaterally and automatically provide computing power, such as server time and network storage, as needed, without requiring human interaction with the service provider.

[0111] Wide Area Network (WAN) Access: Capabilities are available on the network and accessed through standard mechanisms that facilitate use by heterogeneous thin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

[0112] Resource pooling: A provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, where different physical and virtual resources are dynamically allocated and reallocated based on demand. There is a sense of location independence because consumers typically do not have control or knowledge of the exact location of the resources provided, but may be able to specify the location at a higher level of abstraction (e.g., country, state, or data center).

[0113] Rapid flexibility: The ability to provide capacity quickly and flexibly, automatically scaling down and up rapidly in some situations to scale up rapidly. For consumers, the available supply capacity often appears unlimited and can be purchased in any quantity at any time.

[0114] Measuring services: Cloud systems automatically control and optimize resource usage by leveraging metering capabilities at a level of abstraction appropriate to the service type (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported, providing transparency to both service providers and consumers.

[0115] The service model is as follows:

[0116] Software as a Service (SaaS): The capability offered to consumers is the ability to use the provider's applications running on cloud infrastructure. Applications can be accessed from different client devices via thin client interfaces such as web browsers (e.g., web-based email). Consumers do not manage or control the underlying cloud infrastructure, including the network, servers, operating system, storage, or even individual application capabilities, with the possible exception of mimicking user-specific application configuration settings.

[0117] Platform as a Service (PaaS): This provides consumers with the ability to deploy consumer-created or acquired applications onto cloud infrastructure using programming languages ​​and tools supported by the provider. Consumers do not manage or control the underlying cloud infrastructure, including networks, servers, operating systems, or storage, but they have control over the deployed applications and the configuration of any application hosting environments.

[0118] Infrastructure as a Service (IaaS): The capabilities offered to consumers are processing, storage, networking, and other basic computing resources that enable consumers to deploy and run arbitrary software, which may include operating systems and applications. Consumers do not manage or control the underlying cloud infrastructure, but rather have control over the operating system, storage, deployed applications, and potentially limited control over selected networking components (e.g., host firewalls).

[0119] The deployment model is as follows:

[0120] Private cloud: A cloud infrastructure that operates solely for an organization. It can be managed by the organization or a third party and can exist on-site or off-site.

[0121] Community cloud: A cloud infrastructure shared by several organizations and supporting a specific community with shared concerns (e.g., tasks, security requirements, policies, and compliance considerations). It can be managed by an organization or a third party and can exist on-site or off-site.

[0122] Public cloud: Makes cloud infrastructure available to the public or large industry groups and is owned by an organization that sells cloud services.

[0123] Hybrid cloud: A cloud infrastructure is a combination of two or more clouds (private, community, or public) that remain a single entity but are bound together by standardized or proprietary technologies that enable data and applications to be ported (e.g., cloud bursting for load balancing between clouds).

[0124] Cloud computing environments are service-oriented, focusing on statefulness, loose coupling, modularity, and semantic interoperability. At the heart of cloud computing is the infrastructure that includes a network of interconnected nodes.

[0125] See now Figure 7The diagram illustrates an illustrative cloud computing environment 1000. As shown, the cloud computing environment 1000 includes one or more cloud computing nodes 100 to which local computing devices used by cloud consumers can communicate. These local computing devices include, for example, personal digital assistants (PDAs) or cellular phones 1000A, desktop computers 1000B, laptop computers 1000C, and / or automotive computer systems 1000N. The nodes 100 can communicate with each other. They can be physically or virtually grouped (not shown) in one or more networks, such as private clouds, community clouds, public clouds, or hybrid clouds, or combinations thereof, as described above. This allows the cloud computing environment 1000 to provide infrastructure, platforms, and / or software as services that cloud consumers do not need to maintain on their local computing devices. It should be understood that... Figure 7 The computing devices 100A-N shown are intended to be illustrative only, and the computing node 100 and cloud computing environment 1000 can communicate with any type of computerized device via any type of network and / or network-addressable connectivity (e.g., using a web browser).

[0126] See now Figure 8 This illustrates a set of functional abstraction layers 1100 provided by the cloud computing environment 1000. It should be understood in advance that... Figure 8 The components, layers, and functions shown are intended to be illustrative only, and embodiments of the invention are not limited thereto. As described, the following layers and corresponding functions are provided:

[0127] The hardware and software layer 1102 includes hardware and software components. Examples of hardware components include: a mainframe 1104; a server 1106 based on a RISC (Reduced Instruction Set Computer) architecture; a server 1108; a blade server 1110; a storage device 1112; and a network and networking component 1114. In some embodiments, the software components include network application server software 1116 and database software 1118.

[0128] The virtualization layer 1120 provides an abstraction layer from which the following examples of virtual entities can be provided: virtual server 1122; virtual storage 1124; virtual network 1126, including virtual private network; virtual application and operating system 1128; and virtual client 1130.

[0129] In one example, management layer 1132 may provide the functions described below: Resource Provisioning 1134 Provides dynamic procurement of computing resources and other resources used to perform tasks within the cloud computing environment. Metering and Pricing 1136 Provides cost tracking as resources are utilized within the cloud computing environment and bills or invoices for the consumption of these resources. In one example, these resources may include application software licenses. Security Provides authentication for cloud consumers and tasks, as well as protection for data and other resources. User Portal 1138 Provides users and system administrators with access to the cloud computing environment. Service Level Management 1140 Provides cloud computing resource allocation and management to ensure that required service levels are met. Service Level Agreement (SLA) Planning and Fulfillment 1142 Provides pre-scheduling and procurement of cloud computing resources, anticipating future requirements for those resources according to the SLA.

[0130] Workload layer 1144 provides examples of functionalities that can leverage a cloud computing environment. Examples of workloads and functionalities that can be provided from this layer include: mapping and navigation 1146; software development and lifecycle management 1148; virtual classroom education delivery 1150; data analytics and processing 1152; transaction processing 1154; and energy-efficient data exchange 1156. Electronic card programs 110a and 110b provide a means of exchanging information using portable, energy-efficient electronic devices.

[0131] Various embodiments of the invention have been described for illustrative purposes, but are not intended to be exhaustive or limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope of the described embodiments. The terminology used herein has been chosen to best explain the principles of the embodiments, their practical application, or technical improvements to technologies found in the market, or to enable those skilled in the art to understand the embodiments disclosed herein.

Claims

1. A computer system for energy-efficient data exchange, comprising: A first electronic card device (ECD) includes a first circuit path having a first switch and a second circuit path having a second switch, wherein the first switch is configured to close the first circuit path to energize the first ECD independently of the second switch in response to the first switch of the first ECD engaging the second ECD, wherein the first ECD is configured to exchange data with the second ECD; and A docking assembly configured to receive a first ECD, the docking assembly including an actuator configured to engage a second switch and close a second circuit path without engaging the first switch, so as to energize the first ECD in response to receiving the first ECD by the docking assembly, wherein the first ECD is configured to transmit received data from the second ECD to a mobile device associated with the docking assembly.

2. The system according to claim 1, wherein, The first ECD also includes a first magnet-switch pair associated with the first switch and a second magnet-switch pair associated with the second switch, wherein the first switch and the second switch are arranged in parallel.

3. The system of claim 1, wherein the first ECD further includes a first magnet associated with the first switch and a second magnet associated with the second switch, and wherein the actuator of the docking assembly further includes a third magnet configured to interact with the second magnet to activate the second switch when the first ECD is received by the docking assembly.

4. The system according to claim 1, wherein, The first switch of the first ECD further includes a first mechanical switch, the second switch of the first ECD further includes a second mechanical switch, and the actuator of the docking assembly further includes a third mechanical switch, wherein the interaction between the first mechanical switch of the first ECD and the corresponding first mechanical switch of the second ECD is configured to energize the first ECD, and the interaction between the second mechanical switch of the first ECD and the third mechanical switch of the docking assembly is configured to energize the first ECD.

5. The system according to claim 2, wherein, The first switch of the first ECD further includes a first reed switch, and the second switch of the first ECD further includes a second reed switch.

6. The system according to claim 1, wherein, The first switch of the first ECD is configured to engage the corresponding first switch of the second ECD to power on the first ECD and enable data exchange with the second ECD, wherein the first switch of the first ECD is configured to disengage from the corresponding first switch of the second ECD to power off the first ECD.

7. The system of claim 1, wherein the first ECD is configured to be received by the docking component and powered off by executing a shutdown script, and wherein the first switch pair of the first ECD is configured to engage the corresponding first switch of the second ECD to power on the first ECD and enable data exchange with the second ECD.

8. The system according to claim 1, wherein, The docking assembly further includes a holder configured to be coupled to the mobile device, the holder including the actuator configured to engage the second switch of the first ECD when the first ECD is located in the holder.

9. The system according to claim 1, wherein, The first circuit path is configured to shut down to power the first ECD in response to the interaction between the first switch of the first ECD and the corresponding first switch of the second ECD.

10. The system according to claim 1, wherein, The second circuit path is configured to shut down to energize the first ECD in response to the interaction between the first switch of the first ECD and the actuator of the docking assembly.

11. The system of claim 1, wherein the first ECD further comprises a memory component, wherein the first ECD is configured to store docking records in the memory component when the second switch of the first ECD is activated, and wherein, The first ECD is configured to check the memory component to locate the docking record in order to determine whether the first ECD was received by the docking component.

12. The system of claim 3, wherein the first ECD is configured to transmit the received data from the second ECD to the mobile device in response to the engagement of the third magnet of the docking assembly and the second magnet of the first ECD with the second switch to energize the first ECD.

13. The system according to claim 3, wherein, The first magnet and the first switch are arranged on a first end of the first ECD, and the second magnet and the second switch are arranged on a second end of the first ECD opposite to the first end, wherein the first ECD is configured to interact with the second ECD simultaneously and be received by the docking assembly.

14. The system according to claim 12, wherein, The first ECD is configured to execute a shutdown script to automatically power off the first ECD when the received data has been transmitted to the mobile device.

15. A computer-implemented method, comprising: The activation of the first switch is detected in a first electronic card device ECD, which includes a first circuit path having a first switch and a second circuit path having a second switch, to close the first circuit path so that the first ECD is powered by the second ECD, wherein the activation of the first switch is independent of the second switch. In response to the detected activation of the first switch, it is determined that the second ECD is within the threshold proximity of the first ECD; Exchange data with the second ECD; In response to detecting engagement of the second switch to close the second circuit path without engaging the first switch, it is determined that the first ECD is docked with the mobile device, and the accumulated information is transmitted from the first ECD to the mobile device. In response to determining that the first ECD is not docked with the mobile device, the accumulated information is stored in the first ECD; and The detection responds to the deactivation of the first switch that turns off the first ECD when the second ECD is outside the threshold of the first ECD.

16. The method of claim 15, further comprising: The activation of the second switch is detected in the first ECD to energize the first ECD; In response to the detected activation of the second switch, it is determined that the first ECD is docked with the mobile device; The accumulated information is transmitted from the first ECD to the mobile device; as well as In response to the completion of transmitting the accumulated information to the mobile device, a shutdown script is executed to automatically power off the first ECD.

17. The method according to claim 15, wherein, Detecting the activation of the first switch to close the first circuit path in order to energize the first ECD further includes: The closure of the first circuit path is detected in response to the interaction between the first magnet of the first ECD and the corresponding first magnet of the second ECD.

18. The method of claim 16, further comprising: In response to the detected activation of the second switch to power on the first ECD, the docking status is recorded in the memory of the first ECD.

19. The method of claim 16, further comprising: In response to receiving at least one piece of information from the second ECD, the memory of the first ECD is checked to determine whether the first ECD is docked with the mobile device; as well as In response to the recognition of the docking status recorded in the memory of the first ECD, at least one piece of received information is transmitted to the mobile device.

20. A computer program product for energy-saving data exchange, the computer program product comprising: One or more computer-readable storage media and program instructions commonly stored on the one or more computer-readable storage media, the program instructions comprising: A program instruction in a first electronic card device ECD, which includes a first circuit path having a first switch and a second circuit path having a second switch, detects the activation of the first switch to close the first circuit path so that the first ECD is energized by the second ECD, wherein the activation of the first switch is independent of the second switch. In response to the detected activation of the first switch, program instructions are determined to be within the threshold proximity of the second ECD to the first ECD; Program instructions to exchange at least one piece of information with the second ECD; In response to detecting the engagement of the second switch to close the second circuit path without engaging the first switch, determining that the first ECD is docked with the mobile device, and transmitting accumulated information from the first ECD to the program instructions of the mobile device; In response to determining that the first ECD is not docked with the mobile device, a program instruction is given to store the accumulated information in the first ECD; and The program instruction to deactivate the first switch in response to the second ECD being outside the threshold of the first ECD is detected.

Images