System and method for providing a digital meeting tool

Systems and methods include data storage that stores user information for a plurality of user devices, a beacon that is configured to be associated with a first unique identifier, a meeting server that receives, from the data storage, data that includes user information one of the user devices, assigns the first unique identifier to one of the user devices based in part on similarities between the user information and an entity associated with the beacon, and creates a digital asset that includes the first unique identifier and first information, and a communication interface associated with the meeting server that transmits, via a network, the digital asset to the one of the user devices. The beacon broadcasts the first unique identifier via a short-range transmission at a first location and the one of the user devices detects the first unique identifier at the first location, compares it to the identifier associated with the digital asset, and displays a notification that includes the first information if there is a match.

FIELD OF THE DISCLOSURE

The present disclosure relates to systems and methods for providing a digital meeting tool that alerts a user to the presence of a proximity sensor associated with another individual.

BACKGROUND OF THE DISCLOSURE

In crowded environments such as recruiting events, conferences, trade shows etc., it is difficult for a recruiter or other person to identify someone that is unknown or has an unfamiliar appearance. When a job applicant is attempting to meet the recruiter, there may be a lot of friction involved in figuring out the meeting place, timing, and location, and one or both parties may spend a significant amount of time approaching strangers as they search for one another. When creating recruiting events or similar meet-ups, there is a need to connect the right people at the event. There is also a need to tag, track and maintain the connection with passive candidates.

These and other drawbacks exist.

DETAILED DESCRIPTION OF THE EMBODIMENTS

The following description is intended to convey a thorough understanding of the embodiments described by providing a number of specific exemplary embodiments and details involving systems and methods for providing a digital meeting tool to a user device. It should be appreciated, however, that the present disclosure is not limited to these specific embodiments and details, which are examples only. It is further understood that one possessing ordinary skill in the art, in light of known systems and methods, would appreciate the use of the invention for its intended purposes and benefits in any number of alternative embodiments, depending on specific design and other needs. A company and system supporting a company are used as examples for the disclosure. The disclosure is not intended to be limited to companies only.

In various embodiments, a user device receives a notification about an event, such as, for example, a recruiting event hosted by a company or a similar type meet-up, such as, for example, a trade show. The notification may contain a link to download a digital asset to the user device. For example, the notification may contain a link to add the digital asset to, for example, a Passbook of an iPhone user. The notification may contain a link to add the digital asset to a Google Wallet of an Android user. The digital asset may include identifiers associated with one or more recruiting devices. The digital asset may include a picture and contact information for the recruiter(s) associated with the one or more recruiting devices, and the address for the recruiting event. When the user device enters the location of the recruiting event and is in close vicinity, the recruiting devices at the event may be broadcasting their unique identifiers. When the user device detects an identifier that matches the identifier in the digital asset, the user device may generate a notification providing additional information about the recruiter, the job, the company, and other information related to the event. The notification may contain picture/title/bio of the hiring manager and links to various other relevant content such as list of positions, company profiles, company facilities, benefits etc. The notification may provide location information showing how close the user device is to the recruiting device.

FIG. 1depicts an exemplary embodiment of a system100for providing a digital meeting tool to a user device, according to various embodiments of the disclosure. The system100may include various network-enabled computer systems, including, as depicted inFIG. 1for example, Entity101(comprising meeting processor106), user device102b, beacon104b, database109, and network108. It is also noted that the system100illustrates only a single instance of each component. It will be appreciated that multiple instances of these components may be used. For example, various embodiments may include a plurality of user devices102b, recruiter beacons104b, databases109, and/or meeting processors106. Moreover, the system100may include other devices not depicted inFIG. 1.

In various example embodiments, meeting processor106may be a stand-alone component separate from Entity101. Each processor may comprise one or more network-enabled computers. As referred to herein, a network-enabled computer system and/or device may include, but is not limited to: e.g., any computer device, or communications device including, e.g., a server, a network appliance, a personal computer (PC), a workstation, a mobile device, a phone, a handheld PC, a personal digital assistant (PDA), a thin client, a fat client, an Internet browser, or other device. The network-enabled computer systems may execute one or more software applications to, for example, receive data as input from an entity accessing the network-enabled computer system, process received data, transmit data over a network, and receive data over a network. The one or more network-enabled computer systems may also include one or more software applications, such as meeting application105, to enable a user of recruiter beacon104to transmit one or more signals to user device102. In various embodiments, meeting application105may be integrated into a native mobile banking application and/or a mobile optimized web site associated with Entity101, for example. The functionality of meeting application105also may be integrated into an online banking website.

The components depicted inFIG. 1may store information in various electronic storage media, such as database109. Electronic information, files, and documents may be stored in various ways, including, for example, a flat file, indexed file, hierarchical database, relational database, such as a database created and maintained with software from, for example, Oracle® Corporation, a Microsoft® SQL system, an Amazon cloud hosted database or any other queryable structured data storage mechanism.

The components depicted inFIG. 1may be coupled via one or more networks, such as, for example, network108. Network108may be one or more of a wireless network, a wired network or any combination of wireless network and wired network. For example, network108may include one or more of a fiber optics network, a passive optical network, a cable network, an Internet network, a satellite network, a wireless LAN, a Global System for Mobile Communication (“GSM”), a Personal Communication Service (“PCS”), a Personal Area Network (“PAN”), D-AMPS, Wi-Fi, Fixed Wireless Data, IEEE 802.11b, 802.15.1, 802.11n and 802.11g or any other wired or wireless network for transmitting and receiving a data signal. Network108may comprise one or more secure communication channels for securely exchanging information between requestor device102a, dispenser device102b, and financial institution101.

In addition, network108may include, without limitation, telephone lines, fiber optics, IEEE Ethernet 902.3, a wide area network (“WAN”), a local area network (“LAN”), or a global network such as the Internet. Also network108may support an Internet network, a wireless communication network, a cellular network, or the like, or any combination thereof. Network108may further include one network, or any number of the exemplary types of networks mentioned above, operating as a stand-alone network or in cooperation with each other. Network108may utilize one or more protocols of one or more network elements to which they are communicatively coupled. Network108may translate to or from other protocols to one or more protocols of network devices. Although network108is depicted as a single network, it should be appreciated that according to one or more embodiments, network108may comprise a plurality of interconnected networks, such as, for example, the Internet, a service provider's network, a cable television network, corporate networks, and home networks.

In various example embodiments, user device102bmay be associated with user102a. User102amay be an individual or entity that desires to attend an event hosted by Entity101. The event may be a networking event, job fair or job recruiting event, and user102amay be a job applicant. Entity101may have one or more job openings that it posts on one or more web site and/or job boards. Entity101may be a company or institution, such as, for example, a bank, other type of financial institution, including a credit card and/or debit card provider, for example, or any other entity that offers accounts to customers.

User device102bmay be, for example, a handheld PC, a phone, a smartphone, a PDA, a tablet computer, or other device. User device102bmay include an iPhone, iPod, iPad from Apple® or any other mobile device running Apple's iOS operating system, any device running Google's Android® operating system, including for example, Google's wearable device, Google Glass, any device running Microsoft's Windows® Mobile operating system, and/or any other smartphone or like wearable mobile device (e.g., smart watch). Beacon104bmay be implemented in a device similar to user device102b. In various embodiments, a device associated with beacon104bmay execute certain aspects of meeting application105.

Meeting processor106may store a list of contact information for various individuals, including user102a. The list may include email addresses, phone numbers, usernames on social media accounts, and other contact information associated with one or more individuals. In various embodiments, the individuals may be potential job applicants. The list may be created by meeting processor106. The list may be provided to meeting processor106from another network-enabled computer (not shown). For each individual on the list, the list may include information related to the type of job or position that individual will be invited to apply for. User102amay apply for a job by filling out an online application, and this information may be stored in the list by meeting processor106.

Meeting processor106may create a digital asset for each individual on the list. The digital assets may be stored in database109. Meeting processor106may create digital asset103for user102a, based on the information provided by user102a. Meeting processor106may assign one or more beacons to each digital asset in database109. Meeting processor106may assign beacon104bto digital asset103. Beacon104bmay be a device that leverages Bluetooth Low Energy (BLE) to establish a region around the device by broadcasting signal107using one or more transceivers. The transceivers may use Bluetooth Low Energy (BLE) technology. The transceivers may include, for example, iBeacons. The transceivers may include RFID transmitters and receivers, cameras, scanners, and/or Near Field Communication (NFC) capabilities, which may allow for communication with other devices by touching them together or bringing them into close proximity. Exemplary NFC standards include ISO/IEC 18092:2004, which defines communication modes for Near Field Communication Interface and Protocol (NFCIP-1). Other exemplary NFC standards include those created by the NFC Forum. Beacon104bmay be hardware and/or software implemented on a device similar to user device102b.

Beacon104bmay broadcast a unique identifier within an area around the beacon (shown as signal107). The range of signal107may be limited, and the strength of signal107may decrease as it is transmitted out from beacon104b. User device102bmay include one or more sensors for detecting signal107. The sensors may be Bluetooth-enabled.

In various embodiments, beacon104bmay be associated with user104a. User104amay be a recruiter for Entity101. Meeting processor106may assign beacon104bto digital asset103based on similarities between user102aand user104a. For example, in various embodiments, user102amay be a job applicant for a position with Entity101and user104amay be a recruiter for Entity101. Entity101may be hosting a recruiting event or job fair, and user104awill be there with beacon104b. Meeting processor106may create a digital asset103for user102athat includes a description of the event, the date and time, a description of the job or jobs that the user102acan apply for, a picture of user104a, the unique identifier associated with beacon104b, contact information for user104a, and one or more links for websites associated with Entity101. User104amay be a recruiter for the specific type of job that user102ahas applied for.

User device102bmay receive digital asset103via network108. Meeting processor106may send digital asset103in an email, text message, SMS, MMS, and/or via a messaging program associated with user102a's social media account (or accounts). User device102bmay receive notification from meeting processor106that includes a link to download digital asset103. For example, notification301is shown inFIG. 3A. Notification301may be an email, text message, MMS, or other electronic message. Notification301may include information302about the upcoming event (where user102awill be attending). The information may include the name of the event, the date and time, and the location. Notification301may include links303aand303bfor the user102ato select and download a digital asset to user device102b. Each link may be associated with a different digital asset (e.g., each digital asset may be associated with a unique job or unique recruiter). In various embodiments, digital asset103may be stored in, for example, a passbook. If the user selects links303aand/or303b, user device102bmay be connected to one or more websites where the user102acan download digital asset103to user device102b. In various embodiments, digital asset103may be part of a software application that user102amay install on user device102b.

FIG. 3Bdepicts a screenshot of an example embodiment of a digital asset103on user device102b. The digital asset may be configured to work with, for example, Apple Passbook. The digital asset also may be configured to work with Google Wallet. The digital asset103shows the event information304a(including the date and time of the event, the name of the event, the physical address, etc.). The digital asset103includes a picture304bof the user104aassociated with beacon104b. The digital asset103includes contact information304cfor the user104a(e.g., name, job title, phone number). The digital asset103may include a bar code/QR code305that is linked to user102a's email address.

FIG. 3Cdepicts a screenshot of an example embodiment of a digital asset on user device102b. This may be the same digital asset as the one shown inFIG. 3B. The digital asset may include contact information306for user104a(e.g., an email address, a link to a LinkedIn profile, etc.). The digital asset may include job information307, such as links to job postings, recruiting events, and other careers with Entity101.

The user of user device102bmay be able to forward digital asset103to other user devices. The digital asset103may be sent as an attachment to an email, text message, SMS, MMS, in-app message, or electronic message on a social media platform. The user of user device102bmay forward the link in notification301to other user devices. In various embodiments, meeting processor106may update digital asset103and provided the updated digital asset to user device102b. Meeting processor106may update the digital asset to reflect changes in the venue of the event, changes to the event description, changes to the recruiter104aand/or recruiter device104b, etc.

User102amay bring user device102bto the event described in the event information304ashown inFIG. 3A. User104amay be at the event with beacon104b. Beacon104bmay be linked to another device used by user104a, and user104amay configure beacon104bto transmit its unique identifier. Beacon104bmay itself be part of a device that is similar to user device102b. In various embodiments, beacon104bmay automatically broadcast its unique identifier via signal107. User device102bmay contain digital asset103, which includes the unique identifier associated with beacon104b. When user device102bis at or nearby the same location as beacon104b, user device102bmay detect signal107broadcast by beacon104b. The signal107may include beacon104b's unique identifier. User device102bmay compare the detected unique identifier with the unique identifier in digital asset103.

If there is a match, user device102bmay display a notification for user102a. The notification may include information from digital asset103. The notification may show the picture304bof user104a. The notification may inform user102athat user104ais at the event. User device102bmay determine how close user device102bis to beacon104b, based on the strength of signal107. The notification may display the location of user device102brelative to beacon104b. The notification may include contact information for user104a(e.g., a contact number associated with beacon104b). If there is no match, user device102bmay display a second notification to user102aindicating that user104ahas not been detected at the event.

FIG. 2depicts an example system200that provides providing a digital meeting tool to a user device. As shown inFIG. 2, system200may include a client device202, a network204, a front-end controlled domain206, a back-end controlled domain212, and a backend218. Front-end controlled domain206may include one or more load balancers208and one or more web servers210. Back-end controlled domain212may include one or more load balancers214and one or more application servers216.

Client device202may be a network-enabled computer. Client device202may be similar to user device102band/or user device that includes beacon104band executes a meeting application105. Client device202may be configured to receive digital asset103. As referred to herein, a network-enabled computer may include, but is not limited to: e.g., any computer device, or communications device including, e.g., a server, a network appliance, a personal computer (PC), a workstation, a mobile device, a phone, a handheld PC, a personal digital assistant (PDA), a thin client, a fat client, an Internet browser, or other device. The one or more network-enabled computers of the example system200may execute one or more software applications to enable, for example, network communications.

Client device202also may be a mobile device: For example, a mobile device may include an iPhone, iPod, iPad from Apple® or any other mobile device running Apple's iOS operating system, any device running Google's Android® operating system, including for example, Google's wearable device, Google Glass, any device running Microsoft's Windows® Mobile operating system, and/or any other smartphone or like wearable mobile device.

Network204may be one or more of a wireless network, a wired network, or any combination of a wireless network and a wired network. For example, network204may include one or more of a fiber optics network, a passive optical network, a cable network, an Internet network, a satellite network, a wireless LAN, a Global System for Mobile Communication (GSM), a Personal Communication Service (PCS), a Personal Area Networks, (PAN), D-AMPS, Wi-Fi, Fixed Wireless Data, IEEE 802.11b, 802.15.1, 802.11n, and 802.11g or any other wired or wireless network for transmitting and receiving a data signal.

In addition, network204may include, without limitation, telephone lines, fiber optics, IEEE Ethernet 902.3, a wide area network (WAN), a local area network (LAN) or a global network such as the Internet. Also, network110may support an Internet network, a wireless communication network, a cellular network, or the like, or any combination thereof. Network204may further include one network, or any number of example types of networks mentioned above, operating as a stand-alone network or in cooperation with each other. Network204may utilize one or more protocols of one or more network elements to which they are communicatively couples. Network204may translate to or from other protocols to one or more protocols of network devices. Although network204is depicted as a single network, it should be appreciated that according to one or more embodiments, network204may comprise a plurality of interconnected networks, such as, for example, the Internet, a service provider's network, a cable television network, corporate networks, and home networks.

Front-end controlled domain206may be implemented to provide security for backend218. Load balancer(s)208may distribute workloads across multiple computing resources, such as, for example computers, a computer cluster, network links, central processing units or disk drives. In various embodiments, load balancer(s)208may distribute workloads across, for example, web server(S)210and/or backend218systems. Load balancing aims to optimize resource use, maximize throughput, minimize response time, and avoid overload of any one of the resources. Using multiple components with load balancing instead of a single component may increase reliability through redundancy. Load balancing is usually provided by dedicated software or hardware, such as a multilayer switch or a Domain Name System (DNS) server process.

Load balancer(s)208and214may include software that monitoring the port where external clients, such as, for example, client device202, connect to access various services of a financial institution or third party that provides the digital tool (such as system100shown inFIG. 1), for example. Load balancer(s)208may forward requests to one of the application servers216and/or backend218servers, which may then reply to load balancer208. This may allow load balancer(s)208to reply to client device202without client device202ever knowing about the internal separation of functions. It also may prevent client devices from contacting backend servers directly, which may have security benefits by hiding the structure of the internal network and preventing attacks on backend218or unrelated services running on other ports, for example.

A variety of scheduling algorithms may be used by load balancer(s)208to determine which backend server to send a request to. Simple algorithms may include, for example, random choice or round robin. Load balancers208also may account for additional factors, such as a server's reported load, recent response times, up/down status (determined by a monitoring poll of some kind), number of active connections, geographic location, capabilities, or how much traffic it has recently been assigned.

Web server(s)210may include hardware (e.g., one or more computers) and/or software (e.g., one or more applications) that deliver web content that can be accessed by, for example a client device (e.g., client device202) through a network (e.g., network204), such as the Internet. In various examples, web servers, may deliver web pages, relating to, for example, online banking applications and the like, to clients (e.g., client device202). Web server(s)210may use, for example, a hypertext transfer protocol (HTTP or sHTTP) to communicate with client device202. The web pages delivered to client device may include, for example, HTML documents, which may include images, style sheets and scripts in addition to text content.

A user agent, such as, for example, a web browser, web crawler, or native mobile application, may initiate communication by making a request for a specific resource using HTTP and web server210may respond with the content of that resource or an error message if unable to do so. The resource may be, for example a file on stored on backend218. Web server(s)210also may enable or facilitate receiving content from client device202so client device202may be able to, for example, submit web forms, including uploading of files.

Web server(s) also may support server-side scripting using, for example, Active Server Pages (ASP), PHP, or other scripting languages. Accordingly, the behavior of web server(s)210can be scripted in separate files, while the actual server software remains unchanged.

Load balancers214may be similar to load balancers208as described above.

Application server(s)216may include hardware and/or software that is dedicated to the efficient execution of procedures (e.g., programs, routines, scripts) for supporting its applied applications. Application server(s)216may comprise one or more application server frameworks, including, for example, Java application servers (e.g., Java platform, Enterprise Edition (Java EE), the .NET framework from Microsoft®, PHP application servers, and the like). The various application server frameworks may contain a comprehensive service layer model. Also, application server(s)216may act as a set of components accessible to, for example, a financial institution or other entity implementing system200and/or system100, through an API defined by the platform itself. For Web applications, these components may be performed in, for example, the same running environment as web server(s)210, and application servers216may support the construction of dynamic pages. Application server(s)216also may implement services, such as, for example, clustering, fail-over, and load-balancing. In various embodiments, where application server(s)216are Java application servers, the web server(s)210may behaves like an extended virtual machine for running applications, transparently handling connections to databases associated with backend218on one side, and, connections to the Web client (e.g., client device202) on the other.

Backend218may include hardware and/or software that enables the backend services of, for example, a financial institution or other entity that maintains a distributes system similar to system200and/or system100. For example, backend218may include, a system of record, online banking applications, a rewards platform, a payments platform, a lending platform, including the various services associated with, for example, auto and home lending platforms, a statement processing platform, one or more platforms that provide mobile services, one or more platforms that provide online services, a card provisioning platform, a general ledger system, system100shown inFIG. 1, and the like. Backend218may be associated with various databases, including account databases that maintain, for example, customer account information, product databases that maintain information about products and services available to customers, content databases that store content associated with, for example, a financial institution, and the like. Backend218also may be associated with one or more servers that enable the various services provided by system200. Backend218may be associated with one or more servers that enable the various services provided by system100.

FIG. 4is a flow chart illustrating an example method for providing a digital meeting tool to a user device. The method400shown inFIG. 4can be executed or otherwise performed by one or more combinations of various systems. The method400as described below may be carried out by the system for providing a digital meeting tool, as shown inFIGS. 1, 2, 3a, and3bby way of example, and various elements of that system are referenced in explaining the method ofFIG. 4. Each block shown inFIG. 4represents one or more processes, methods, or subroutines in the exemplary method400. Referring toFIG. 4, the exemplary method400may begin at block401.

At block401, a contact list associated with one or more user devices may be received. Each of the user devices on the list may be associated with a user interested in attending an event. The event may be a job fair, for example, or any other like event where individuals may meet, such as, for example, a trade show. For example, in various embodiments, the event may be a dating event. The event may be a social event, such as a concert or a baseball game. Each user on the list may have previously expressed interest in attending the event. The contact list may include a contact number and/or email address associated with the user's device. In one example, the event may be a job fair, and each user on the list may be job candidates who are planning to attend the job fair. One candidate, John, may provide his email address and phone number associated with his smartphone to the entity hosting the event. John may have previously submitted this information in an online and/or paper application. The entity hosting the event—in this example, Company X—may receive a list of attendees (a contact list) that includes John's contact information.

At block402, meeting processor106may associate each name on the contact list with a beacon or other transmitter, such as a BLE transmitter, NFC transmitter, RFID transmitter or the like. Each beacon may be implemented using a mobile device. For example, a representative affiliated with or associated with Company X that is recruiting individuals may configure a mobile device to act or serve as a beacon for the event. Each beacon may have a unique identifier that it can transmit using a short-range transmission method (e.g., Bluetooth, NFC, RFID, etc.). The beacon may be associated with an individual who will be attending the event and needs to meet with one or more of the users on the contact list. In this example, beacon A may be associated with a recruiter who works for Company X—Bob. Meeting processor106may create an entry in database109for John that includes his contact information, the information on the jobs he applied for, biographical information, and other relevant information. Meeting processor106may associate Bob's beacon (beacon A) with John's information in the database based at least in part on the fact that Bob is a recruiter for Company X, will be attending the job fair that John has applied to attend, and is associated with the specific types of jobs that John applied for and/or is interested in. A meeting application (e.g., meeting application105) may be used to implement beacon104b.

At block403, meeting processor106may create a digital asset for a user (e.g., John) based on the information associated with the user (e.g., John) in database109. In this example, the digital asset may be designed to work with, for example, Apple Passbook on John's smartphone. The digital asset may include beacon A's unique identifier. The digital asset may include information about the job fair (e.g., the location, date and time, directions, etc). The digital asset may include a picture of Bob. The digital asset may include one or more links to descriptions of different jobs offered by Company X that John may be qualified for.

At block404, the digital asset may be provided to the user's device. In this example, John may receive a notification sent to his smartphone that includes the digital asset (e.g., as an attachment to an email or text message). The notification may include a link to one or more websites hosted by Company X where John can download the digital asset. John may download the digital asset to his smartphone and attend the job fair using the information provided in the digital asset. In various embodiments, John may download the digital asset using an application on his user device. Once the digital asset is on his phone, John may open the application and “add” the digital asset to his passbook (e.g., if his user device is an iPhone).

At block405, the beacon may broadcast a signal that includes its unique identifier. In this example, Bob may be at the job fair with beacon A, and may use an application associated with beacon A to continuously broadcast beacon A's unique identifier using a short-range transmission method (e.g., Bluetooth, NFC, iBeacon technology, RFID).

At block406, the user device may detect the signal from the beacon. In this example, John may be attending the job fair hosted by Company X. John's smartphone, which contains the digital asset, may detect the signal being broadcast by beacon A (associated with Bob). John's smartphone may be equipped with hardware and/or software to detect short-range transmissions (e.g., Bluetooth, NFC, iBeacon technology, RFID). Upon receiving the signal, John's smartphone may compare the unique identifier in the signal with the unique identifier associated with the digital asset on John's smartphone. If there is a match, the digital asset may provide a notification on John's smartphone (block407). The notification may inform John that Bob is at the event. The notification may include Bob's picture. The notification may include Bob's contact information. The notification may show Bob's current location at the event. If John's smartphone detects one or more signals, but cannot determine a match, the digital asset may display one or more notifications informing John that Bob's beacon was not detected. The digital asset may provide a notification asking John to move closer to the event, or move into a different room (e.g., so that his device can better pickup beacon signals without interference).

It is further noted that the software described herein may be tangibly embodied in one of more physical media, such as, but not limited to, a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a hard drive, read only memory (ROM), random access memory (RAM), as well as other physical media capable of storing software, or combinations thereof. Moreover, the figures illustrate various components (e.g., servers, computers, processors, etc.) separately. The functions described as being performed at various components may be performed at other components, and the various components bay be combined or separated. Other modifications also may be made.

In the preceding specification, various preferred embodiments have been described with references to the accompanying drawings. It will, however, be evident that various modifications and changes may be made thereto, and additional embodiments may be implemented, without departing from the broader scope of the invention as set forth in the claims that follow. The specification and drawings are accordingly to be regarded as an illustrative rather than restrictive sense.