Changeable Wireless Beacon IDs for Secure Personal-Device Pairing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional wireless beacons in casino environments have static beacon identifiers that can be exploited for security breaches, compromising communication security between personal devices and casino devices like EGMs and smart tables.
Innovation Solution
Implementing wireless beacons with changeable beacon identifiers that dynamically generate unique IDs for secure pairing between personal devices and casino devices, using a casino management system to authenticate and authorize connected actions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If static beacon identifiers are used in wireless beacons, then device complexity is reduced and ease of operation is improved, but communication security deteriorates and vulnerability to hacking increases
Solution Approach 1:
The beacon identifier transitions from a static value to a dynamic value that changes with each pairing session. The system generates a new beacon ID for each pairing request, ensuring that even if one beacon ID is compromised, previous and future pairings remain secure. This dynamic approach directly addresses the security vulnerability while maintaining system manageability through automated generation and rotation.
Solution Approach 2:
The beacon identifier parameter is changed from a fixed static value to a variable dynamic value. The system implements parameter rotation where the beacon ID changes over time and across different pairing sessions. This parameter transformation enables secure one-time pairing while the casino management system tracks and manages these changing parameters centrally.
2Reliability
If dynamic beacon identifiers are generated for each pairing session, then communication security is enhanced, but device complexity increases and operational procedures become more complex
Solution Approach 1:
The system implements self-service through automated beacon ID generation and management. When a pairing request is initiated, the casino management server automatically generates a new beacon ID, transmits it to the beacon, and manages the pairing process without requiring manual intervention. This automation maintains ease of operation despite the increased security measures.
Solution Approach 2:
The casino management server acts as an intermediary that handles the complexity of dynamic beacon ID management. It receives pairing requests, generates appropriate beacon IDs, transmits them to beacons, and validates pairings. This intermediary approach shields end-users from the underlying complexity while enabling secure dynamic pairing.
3Reliability
If beacon identifiers are changed dynamically, then protection against hacking attempts is improved, but loss of time occurs during ID generation and validation
Solution Approach 1:
The system performs preliminary actions by pre-generating and storing multiple beacon IDs in the casino management server before they are needed. When a pairing request occurs, the system can quickly retrieve and assign a pre-generated beacon ID rather than creating one from scratch, reducing the time penalty associated with dynamic ID generation.
Solution Approach 2:
The beacon ID generation and transmission process is rushed through efficiently by implementing streamlined protocols. The casino management server generates beacon IDs and transmits them to beacons in rapid succession, minimizing the time users wait during the pairing process while still maintaining the security benefits of dynamic ID generation.
Data Source
AI summary
A system includes a casino management server and an electronic casino device that includes a beacon configured to wirelessly communicate with personal devices of players. The device transmits a request for a custom beacon ID to the casino management server, receives the custom beacon ID from the casino management server in response to the request; and configures the beacon with the custom beacon ID, thereby broadcasting the custom beacon ID to the personal device of the player. The server receives, from the personal device of the player, a pairing request that includes a received beacon ID as received by the personal device based on the broadcasting, validates that the received beacon ID matches the custom beacon ID, stores a valid association between the personal device of the player and the electronic casino device; and authorizes connected actions to be performed by the personal device based on the association.