Camera Control Slave Devices With Multiple Identifiers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional Camera Control Interface (CCI) bus systems face data collisions when multiple slave devices are configured with the same Slave Device Identifier (SID), leading to operational inefficiencies and potential hardware complexity increases.
Innovation Solution
Implementing a control data bus that allows multiple slave devices to be configured with unique and shared Slave Device Identifiers, enabling concurrent and individual communication modes using a Camera Control Data Extension (CCIe) bus protocol, which manages access through an address list to prevent collisions and optimize data transfer.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If multiple slave devices are configured with the same slave device identifier on a single bus, then device complexity is reduced and ease of manufacture is improved, but data collisions occur and reliability deteriorates
Solution Approach 1:
The patent segments the slave device identifier into two parts: a first slave device identifier that can be shared among multiple devices, and a second slave device identifier that is unique to each device. This segmentation allows devices to be manufactured with identical identifiers (improving ease of manufacture) while maintaining unique identification through the second identifier (preventing data collisions and improving reliability).
Solution Approach 2:
The patent adds another dimension to the identifier system by introducing a second slave device identifier that operates in conjunction with the first identifier. This dimensional expansion allows the system to distinguish between devices that share the same first identifier, thereby eliminating data collisions while maintaining manufacturing simplicity.
2Device complexity
If multiple slave devices use the same slave device identifier, then hardware complexity is reduced, but data collisions occur causing operational inefficiencies
Solution Approach 1:
The patent segments the identification function into two components: a shared first slave device identifier that reduces hardware complexity, and a unique second slave device identifier that prevents data collisions and maintains productivity by ensuring reliable communication with each device.
Solution Approach 2:
The second slave device identifier acts as an intermediary mechanism that resolves the conflict between using shared identifiers (for simplicity) and unique identifiers (for reliable communication). It mediates between these two requirements by providing uniqueness only when needed for data transmission, while allowing shared identifiers to be used for basic device recognition.
3Ease of manufacture
If conventional CCI bus systems are used with identical slave devices, then manufacturing is simplified, but data collisions arise during communication
Solution Approach 1:
The patent segments the slave device identifier into a first identifier that can be duplicated across devices (simplifying manufacturing) and a second identifier that provides unique addressing (preventing data collisions and information loss during communication).
Solution Approach 2:
The patent changes the parameter of identifier uniqueness from a binary state (either unique or shared) to a multi-level structure where the first identifier can be shared but the combined identifier (first and second identifiers together) must be unique. This parameter change allows manufacturing simplicity while preventing data collisions.
Data Source
AI summary
System, methods and apparatus are described that facilitate transmission of data, particularly between two devices within an electronic apparatus. An address list may associate each of a plurality of slave devices coupled to a control data bus with a plurality of slave device identifiers. Access to the control data bus may be controlled based on the address list such that, in a first mode of operation information may be broadcast to multiple slave devices using a first group slave device identifier and, in a second mode of operation, information may be exchanged with a single slave device using an individualized slave device identifier.