Patent Application
20150134383
This disclosure relates to asset management.
Large organizations, such as corporations, governments, and universities, often invest large amounts of money into physical assets. Common examples of such physical assets may include computer equipment, audio/video equipment, IT infrastructure equipment, furniture, and other types of office equipment. Many organizations may also own or manage various types of industry-specific assets. For example, a semiconductor manufacturer may own test benches for testing chips, and a police force may own a fleet of bicycles. For a law firm or accounting firm, certain documents or papers may be considered assets. Generally speaking, any physical object may be considered by an organization to be an asset, and what constitutes an asset may vary from organization to organization.
As organizations get larger, it is not uncommon for them to occupy multiple floors of a building, multiple buildings, or even multiple sites, often making keeping track of all of the organization's assets quite challenging. As technology makes many assets smaller and more portable, managing such assets becomes even more challenging. In order to keep track of all of their assets, many organizations implement asset management programs that require assets to be associated with a particular location, a particular individual, or a particular group. Such systems, however, typically lose track of an undesirably large percentage of assets because assets get moved to new locations or transferred to new individuals without the system being updated. Many organizations also utilize asset management equipment to further keep track of all of their assets. Such equipment typically utilizes barcode or radio frequency identification (RFID) technology to determine the location of certain assets.
In one example a method includes receiving, from each of one or more positioning devices, a corresponding position identification (ID) value, determining a tier value associated with each received position ID value, determining asset position information based on each received position ID value and each determined tier value; and transmitting the determined asset position information to a receiver.
In another example, a device includes a memory and one or more processors. The one or more processors are configured to receive, from each of one or more positioning devices, a corresponding position identification (ID) value, determine a tier value associated with each received position ID value, determine asset position information based on each received position ID value and each determined tier value, and transmit the determined asset position information to a receiver.
In another example, a computer-readable storage medium is encoded with instructions. The instructions, when executed, cause one or more processors of a device to receive, from each of one or more positioning devices, a corresponding position identification (ID) value, determine a tier value associated with each received position ID value, determine asset position information based on each received position ID value and each determined tier value; and transmit the determined asset position information to a receiver.
In another example, an asset tracking system includes one or more landmark tags, each configured to transmit a corresponding position identification (ID) value, and an asset tag configured to receive the corresponding position ID values from the one or more landmark tags, determine a tier value associated with each received position ID value, determine asset position information based on each received position ID value and each determined tier value, and transmit the determined asset position information. The system further includes a receiver configured to receive the asset position information transmitted by the asset tag and relay the received asset position information, and a server configured to receive the asset position information relayed by the receiver, determine a unique asset identifier based on the received asset position information, and associate the receiver with the determined unique asset identifier.
The details of one or more examples are set forth in the accompanying drawings and the description below. Other features, objects, and advantages will be apparent from the description and drawings, and from the claims.
It has been increasingly significant to have an efficient and practical indoor asset tracking system. Among many challenges and hurdles towards large-scale practical indoor asset tracking system, the fine-granularity and location accuracy of the system, given inexpensive cost and longer lifetime of asset tags (e.g., usually required to last more than 2-3 years with coin-cell batteries) is the critical issue. Enabling fine-granularity up to desk (bench) level (sub 2 meter) is extremely challenging without increasing hardware cost and sophisticated technologies. Techniques of this disclosure are generally directed to addressing these potential problems, and propose a simple and inexpensive, yet fine-granular asset tracking system.
Achieving fine-granular resolutions/accuracies has significant importance and may provide new business/service opportunities with respect to indoor positioning systems. Several existing indoor positioning systems implement impractical solutions that require greater hardware and deployment costs. This disclosure proposes a new asset tracking system by introducing a separate, simple, and inexpensive landmark tag which can be used as a reference point. Additionally, this disclosure proposes tiered approaches, so that finer-granularity positioning can be achieved.
In current asset location detection systems, an asset tag affixed to the asset typically transmits a message to a receiver, and based on which receiver picks up the message, the system determines an approximate location for the asset tag. More sophisticated systems may use triangulation of multiple receivers and/or measurements of signal strength to attempt to determine a more accurate location for the asset. Achieving any sort of fine granularity, however, with these receiver-based systems is often cost prohibitive, because of the number of receiver devices required. Receiver devices tend to be fairly expensive relative to the cost of other system components in the asset location detection system.
This disclosure introduces a new system component for determining locations at a fine granularity. This new component may be referred to in this disclosure as a landmark tag or, more generically, as a positioning device. In contrast to existing systems where a location is determined based on a signal transmitted by an asset tag, according to the techniques of this disclosure, a location can be determined based on a signal received by an asset tag. An asset tag can receive position signals from one or more landmark tags. The position signal transmitted by the landmark tag and received by the asset tag may include a unique position identification (ID) value that uniquely identifies the landmark tag. The asset tags can then transmit to the receiver asset position information for determining a position of the asset tag. Such asset position information may, for example, include the position ID values of all landmark tags for which a signal is detected, only the position ID value of the landmark tag which has the highest signal strength, the position ID values of the landmark tags with the two highest signal strengths, and/or some other such asset position information based on the received position ID values. Based on the asset position information transmitted from the asset tag, a central server, which knows the locations of the landmark tags, may calculate the location of the asset tag. As it is contemplated that the landmark tags will be inexpensive compared to the receivers, a relatively large number of landmark tags may be used to achieve fine granularity.
Asset tags 101A-101C are configured to be attached to various assets, and each of asset tags 101A-101C may be associated with a unique asset tag ID. Each of asset tags 101A-101C may be configured to transmit a signal that can be detected by various receivers, such as receiver 103. Additionally, each of asset tags 101A-101C may determine asset position information by processing received data.
Asset tags 101A-101C may either engage in 1-way communication or 2-way communication with receiver 103. An asset tag configured only for 1-way communication may send information to receiver 103 but not receive information from receiver 103. Limiting the asset tag to 1-way communication may simplify the hardware requirements and possibly make the asset tags smaller and less expensive to manufacture. Limiting the asset tag to 1-way communication may additionally reduce battery consumption. In some implementations, asset tags 101A-101C may engage in 2-way communication, such that each of asset tags 101A-101C may both send information to and receive information from receiver 103. In a system with asset tags configured for 2-way communication, server 105 may initiate a real-time inquiry of the asset usage detected by the asset tags.
Database 107 may also store a location for receiver 103. Thus, based on the location of receiver 103, server 105 can provide to a user of asset tracking system 100 an estimate of the location for an asset tag. For example, if receiver 103 detects a signal transmitted by asset tag 101A, then it can be determined that asset tag 101A is in a room, building, or other location associated with, e.g., in proximity to or reception range of, receiver 103. Although not shown in
Server 105 and database 107 are generally intended to represent any computing system and data storage system and may take many different forms. Server 105 and database 107, collectively, may, for example, comprise an application server, a catalog server, a database server, a file server, a home server, a mobile server, a proxy server, a stand-alone server, a web server, a personal computer, a mobile device such as a smartphone or tablet, or any other type of network device. In some examples, some or all of the functionality described herein relative to server 105 and database 107 may be performed by receiver 103.
Communication channel 108 generally represents any suitable communication medium, or collection of different communication media, for transmitting data between asset tag 101A and receiver 103. Communication channel 108 is usually a relatively short-range communication channel, and may implement a physical channel structure similar to Wi-Fi, Bluetooth, 3G, 4G, cellular, or the like, such as implementing defined 2.4, GHz, 3.6 GHz, 5 GHz, 60 GHz or Ultrawideband (UWB) frequency band structures. However, communication channel 108 is not necessarily limited in this respect, and may comprise any wireless or wired communication medium, such as a radio frequency (RF) spectrum or one or more physical transmission lines, one or more proprietary communication protocols, or any combination of wireless and wired transmission media.
Communication channel 109 generally represents any suitable communication medium, or collection of different communication media, for transmitting data between receiver 103 and server 105. Communication channel 109 may be any type of short-range or long-range communication channel, and may comprise any wireless or wired communication medium, such as a radio frequency (RF) spectrum or one or more physical transmission lines, or any combination of wireless and wired media. In other examples, communication channel 109 may form part of a packet-based network, such as a wired or wireless local area network, a wide-area network, or a global network such as the Internet. Additionally, communication channel 109 may be used by receiver 103 and server 105 to create a peer-to-peer link.
Processors 120 may implement functionality and/or execute instructions within receiver 103. Processor 120 is generally intended to represent all processing capabilities of receiver 103. It is contemplated that in some implementations, the processing capabilities of receiver 103 may actually be distributed across multiple processing elements. Processors 120 on receiver 103 may receive and execute instructions stored by memory 122 that control the functionality of TX/RX unit 124 and other units within receiver 103. These instructions executed by processors 120 may cause receiver 103 to store information within or retrieve information from memory 122 during program execution.
Memory 122 within receiver 103 may store information for processing during operation of receiver 103. Memory 122 may include temporary memory that is not for long-term storage. Such temporary memory be configured for short-term storage of information as volatile memory and therefore not retain stored contents if powered off. Examples of volatile memories include random access memories (RAM), dynamic random access memories (DRAM), static random access memories (SRAM), and other forms of volatile memories known in the art. Memory 122 may also include one or more computer-readable storage media. Such computer-readable storage media may be configured to store larger amounts of information than volatile memory and may further be configured for long-term storage of information as non-volatile memory space and retain information after power on/off cycles. Examples of non-volatile memories include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. Memory 122 may also store program instructions for execution by processor 120 and/or data associated received from any of asset tags 101A-101C. Memory 122 in receiver 103 is generally intended to represent all the memory that may be contained in receiver 103, including, for example, caches, RAM, and storage media.
TX/RX unit 124 may include various mixers, filters, amplifiers, modems, and other components designed for signal modulation, as well as one or more antennas and other components designed for transmitting and receiving data. TX/RX unit 124 is generally intended to represent all the communication components and functionality of receiver 103. Receiver 103 may be configured to transmit and receive data using multiple communications protocols. As one example, TX/RX unit 124 may receive information from any of asset tags 101A-101C using Bluetooth and transmit (e.g., relay) information to server 105 using WiFi and/or a wired LAN connection.
Power supply 126 generally represents any power source or combination of power sources that may be used to power receiver 103. It is contemplated that receiver 103 may be larger than asset tags 101A-101C but still generally small, such as the size of a smoke detector, for example. Accordingly, it is contemplated that power supply 126 may also be relatively small for receiver 103. For example, it is contemplated that some implementations of receiver 103 may operate using one or more AA, AA, C, D, or 9V batteries. In some implementations, receiver 103 may include multiple power sources, such as wall power and battery power.
Asset tags 301 and LM tags 309 may implement various hardware solutions. For instance, each of asset tags 301 and/or each of LM tags 309 may include one or more processors (e.g., programmable processors), and one or more memory units. Additionally, each of asset tags 301 and LM tags 309 may be lower-cost than receiver 303, due to reduced resource requirements. Each of LM tags 309 may be lower-cost than each of asset tags 301, as LM tags 309 may only transmit data, whereas asset tags 301 may receive as well as transmit data. Additionally, asset tags 301 may be configured to perform various levels of processing of data (e.g., to determine tier information from the received data). In various examples, one or more of asset tags 301 and LM tags 309 may implement radio frequency (RF) based technologies to transmit and receive data (e.g. asset tag IDs and/or position ID values). For instance, one or more of asset tags 301 and LM tags 309 may implement one or more short-range RF technologies for transmitting and receiving data. By implementing short-range communication technologies such as short-range RF hardware, asset tags 301 and/or LM tags 309 may provide one or more potential advantages. As one example, asset tags 301 and LM tags 309 may, by implementing short-range RF hardware, reduce costs incurred in deploying asset tracking system 300. Because short-range RF hardware tends to be a low-cost alternative to other tracking systems (e.g., systems that implement long-range communication systems), asset tracking system 300 may accommodate a greater number of assets (e.g., to be identified by asset tags 301) and/or greater accuracy with respect to position ID values (e.g., as identified by LM tags 309). Another potential advantage provided by implementing short-range RF hardware is that asset tags 301 and/or LM tags 309 may cause less interference (e.g., harmful signal interference) among one another.
In various implementations of asset tracking system 300, one or more of asset tags 301 and/or LM tags 309 may incorporate short-range devices that implement Bluetooth® technologies. For instance, one or more of asset tags 301 and/or LM tags 309 may include Bluetooth® Low Energy (“BLE”) or Bluetooth® 4.0 technologies. In examples where one or more of asset tags 301 incorporate BLE technology, each of such asset tags 301 may be powered by a small coin-cell battery. Additionally, such BLE devices (which are powered by small coin-cell batteries) may be small in size and relatively inexpensive when compared to other types of communication devices. Additionally, based on being battery-powered, asset tags 301 may be portable, and therefore may be physically moved with the corresponding asset being identified. In this manner, techniques of this disclosure may provide hardware configurations for asset tags 301 that are efficient in terms of resource (e.g., energy) consumption, space consumption, and portability.
Additionally, in examples where one or more of LM tags 309 incorporate BLE technology, LM tags may be powered either by battery or by plug-in outlets (e.g., wall outlets that provide alternating current, or AC). For example, because one or more of LM tags 309 may indicate a fixed location (e.g., a particular pillar number in a warehouse), LM tags 309 may not require the same portability as asset tags 301. Additionally, associations between each of LM tags 309 and its corresponding location information may be provisioned and stored at server 305 and/or database 307. As a result, portability may not be important (and may, in fact, be undesirable) with respect to LM tags 309. In turn, due to the diminished portability requirements, LM tags 309 may optionally utilize wall outlet or wall socket power, thereby mitigating or potentially eliminating the need to replace batteries. In some examples, LM tags 309 may be equipped with batteries as a “backup” power source, in case of any outlet/socket power failure.
According to various implementations of the techniques described herein, receiver 303 may incorporate BLE technology. For instance, receiver 303 may include, be, or be part of a short-range communication device that implements BLE technology. In various examples, receiver 303 may perform a so-called “observer” or central role, by monitoring (or “listening”) for asset messages sent by one or more of asset tags 301. In turn, receiver 303 may transmit or relay any asset messages received from asset tags 301 to server 305. In some examples, receiver 303 may transmit data to server 305 using short-range communication, such as BLE-based or other Bluetooth®-based capabilities.
In other examples, receiver 303 may transmit data to server 305 using other (e.g., long-range) communication mechanisms, such as those provided by internet protocol (IP), WiFi®, Ethernet, 3G, 4G, etc. In examples where receiver 303 is configured to transmit or relay data to server 305 using long-range communication, receiver 303 may be equipped with both BLE technology (to listen for and receive asset messages), as well as long-range communication technology (to transmit or relay data to server 305). For instance, receiver 303 may be equipped with a BLE-based module, as well as an IP network capable module. In such examples, receiver 303 may be more expensive than any of asset tags 301 and LM tags 309, due to the inclusion of both BLE and IP network capable modules. To mitigate added costs, techniques of this disclosure provide for deploying a single receiver for multiple asset tags. For instance, in the implementation illustrated in
One or both of server 305 and database 307 may maintain data to track the assets identified by asset tags 301. Additionally, server 305 and/or database 307 may provision, establish, and track associations between each of LM tags 309 and the associated location. For instance, database 307 may store the asset-asset ID associations for asset tags 301, and the LM tag-position ID associations for LM tags 309. In this example, server 305 may access the various associations by reading the pertinent data from database 307. Additionally, in case any of the associations are to be updated, server 305 may write the updates to database 307, to maintain up-to-date association information with respect to asset tags 301 and LM tags 309. According to some examples of this disclosure, server 305 may apply one or more proximity algorithms to determine asset positions corresponding to asset tags 301 based on position ID values and tier information included in asset messages relayed by receiver 303.
In various implementations of the techniques described herein, LM tags 309 may periodically send position ID information (e.g., in the form of “landmark messages”) to asset tags 301. In examples, the time period between consecutive transmissions of position ID values may be pre-set, and may be referred to herein as a “sleep time” associated with the particular one or more of LM tags 309. Similarly, asset tags 301 may implement a sleep time between transmitting asset messages to receiver 303. In some examples, one or more of asset tags 301 may implement an ad hoc or reactive sleep time, such as by transmitting an asset message to receiver 303 only in response to receiving an asset message from one of LM tags 309.
In various instances, asset tags 301 may implement longer sleep times than LM tags 309. In other words, according to these examples, LM tags 309 may transmit landmark messages more frequently than asset tags 301 transmit asset messages. As one example, if LM tags 309 are not entirely reliant on battery power, LM tags 309 may be better equipped than asset tags 301 to more frequently transmit messages.
Additionally, tier 1 LM tags 309 may provide fine-granular (or “fine-grained”) position information, while tier 1 LM tags 309 may provide coarse-granular (or “coarse-grained”) position information. For instance, tier 1 LM tags 309 may indicate a more precise position (e.g., a shelf number), while tier 2 tags 309 may indicate a more general position (e.g., a pillar number in a warehouse). In the example of
Conversely, as shown in
In various implementations of the multi-tiered techniques described herein, LM tags 309 may transmit their respective tier levels, in addition to the position ID values of their respective locations. For instance, LM tag 309A may transmit a corresponding position ID value along with a “tier 1” indicator, LM tag 309B may transmit a corresponding position ID value along with a “tier 2” indicator, and so on. In turn, asset tags 301 may utilize the received tier indicators in a variety of ways, in accordance with various techniques described herein.
In one example implementation, each of asset tags 301 may determine whether it has received any landmark messages with tier 1 indicators. If an asset tag 301 has received a tier 1 indicator, that asset tag 301 may disregard any received landmark messages with tier 2 indicators. Additionally, such an asset tag 301 may determine whether it has received multiple landmark messages with tier 1 indicators. If the asset tag 301 has received multiple tier 1 indicators, the asset tag 301 may determine which of the received tier 1 landmark messages has the greatest signal strength (expressed by a received signal strength indicator, or ‘RSSI’). In turn, the asset tag 301 may embed the position ID value of the tier 1 landmark signal with the greatest RSSI in the asset messages to be transmitted. For instance, asset tag 301C may receive a tier 1 landmark message from LM tag 309C, and a tier 2 landmark message from LM tag 309D. According to this example implementation, asset tag 301C may disregard the tier 2 landmark message received from LM tag 301D, based on having received the tier 1 landmark message from LM tag 301C. Additionally, based on having received only a single tier 1 landmark message, asset tag 301C may select the position ID value received from tier 1 LM tag 309C for inclusion with asset messages to be transmitted to receiver 303.
In another example implementation, asset tags 301 may include, with the transmitted asset messages, position ID value information for a single tier 1 landmark and a single tier 2 landmark, provided that the asset tag 301 has received at least one landmark message of each tier. According to this implementation, if an asset tag 301 receives multiple landmark messages of the same tier, such an asset tag 301 may choose from the equally-tiered landmark messages, based on the RSSI. In the example of
In this way, techniques of this disclosure may be implemented in a tiered manner. While
Asset tags 301 may determine an asset position based on the one or more received position ID values and the tier level of each received position ID value (606). As described with respect to
While
For instance, tier 2 LM tag 309A may transmit data (e.g., ID values) at a greater (also referred to as “higher” or “stronger”) signal strength than the lower (or “weaker”) signal strength at which tier 1 LM tag 309B transmits data. As described with respect to
In this manner, techniques of this disclosure may be directed to a method including receiving, from each of one or more positioning devices, a corresponding position identification (ID) value, determining a tier value associated with each received position ID value; determining asset position information based on each received position ID value and each determined tier value; and transmitting the determined asset position information to a receiver. For instance, the method described above may be a method of asset tracking According to some examples, determining the tier value associated with each received position ID value includes determining that a first received position ID value is associated with a first tier, and determining that a second received position ID value is associated with a second tier. In some examples, determining the asset position information includes determining the asset position information according to only the first position ID value associated with the first tier. According to some examples, determining the asset position information according to only the first position ID value associated with the first tier includes determining that the first tier is associated with fine-granularity position information and that the second tier is associated with coarse-granularity position information.
According to some examples, determining the asset position information may include determining the asset position information according to both of the first position ID value associated with the first tier and the second position ID value associated with the second tier. In some examples, determining the asset position information according to both of the first position ID value associated with the first tier and the second position ID value associated with the second tier may comprise including, in the asset position information, both of the first position ID value and the second position ID value. According to some examples, determining the tier value associated with each received position ID value may include determining that a first received position ID value is associated with a first tier, and determining that a second received position ID value is associated with the first tier.
In some examples, determining the asset position information based on each determined tier value may include selecting between the first received position ID value and the second received position ID value. According to some examples, selecting between the first received position ID value and the second received position ID value may include determining which of the first received position ID value and the second received position ID value is associated with a greater signal strength. In some examples, determining which of the first received position ID value and the second received position ID value is associated with a greater signal strength may include determining a respective received signal strength indicator (RSSI) value corresponding to each of the first received position ID value and the second received position ID value.
In this manner, aspects of this disclosure may be directed to a device including a memory, and one or more processors. For instance, the device is operable or configured to perform asset tracking According to various examples, the one or more processors are configured to receive, from each of one or more positioning devices, a corresponding position identification (ID) value, determine a tier value associated with each received position ID value, determine asset position information based on each received position ID value and each determined tier value, and transmit the determined asset position information to a receiver. According to some examples, to determine the tier value associated with each received position ID value, the one or more processors are configured to determine that a first received position ID value is associated with a first tier, and to determine that a second received position ID value is associated with a second tier.
According to some examples, to determine the asset position information, the one or more processors are configured to determine the asset position information according to only the first position ID value associated with the first tier. In some examples, to determine the asset position information according to only the first position ID value associated with the first tier, the one or more processors are configured to determine that the first tier is associated with fine-granularity position information and that the second tier is associated with coarse-granularity position information. According to some examples, to determine the asset position information, the one or more processors are configured to determine the asset position information according to both of the first position ID value associated with the first tier and the second position ID value associated with the second tier.
In some examples, to determine the asset position information according to both of the first position ID value associated with the first tier and the second position ID value associated with the second tier, the one or more processors are configured to include both of the first position ID value and the second position ID value in the asset position information. According to some examples, to determine the tier value associated with each received position ID value, the one or more processors are configured to determine that a first received position ID value is associated with a first tier, and to determine that a second received position ID value is associated with the first tier.
According to some examples, to determine the asset position information based on each received position ID value and each determined tier value, the one or more processors are configured to select between the first received position ID value and the second received position ID value. In some examples, to select between the first received position ID value and the second received position ID value, the one or more processors are configured to determine which of the first received position ID value and the second received position ID value is associated with a greater signal strength. According to some examples, to determine which of the first received position ID value and the second received position ID value is associated with a greater signal strength, the one or more processors are configured to determine a respective received signal strength indicator (RSSI) value corresponding to each of the first received position ID value and the second received position ID value.
In this manner, aspects of this disclosure may be directed to a computer-readable storage medium encoded with instructions that, when executed, cause one or more processors of a device to receive, from each of one or more positioning devices, a corresponding position identification (ID) value, to determine a tier value associated with each received position ID value, to determine asset position information based on each received position ID value and each determined tier value, and to transmit the determined asset position information to a receiver.
In this manner, aspects of this disclosure may be directed to an asset tracking system includes one or more landmark tags, each configured to transmit a corresponding position identification (ID) value, and an asset tag configured to receive the corresponding position ID values from the one or more landmark tags, determine a tier value associated with each received position ID value, determine asset position information based on each received position ID value and each determined tier value, and transmit the determined asset position information. The system further includes a receiver configured to receive the asset position information transmitted by the asset tag and relay the received asset position information, and a server configured to receive the asset position information relayed by the receiver, determine a unique asset identifier based on the received asset position information, and associate the receiver with the determined unique asset identifier.
By way of example, and not limitation, such computer-readable storage media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage, or other magnetic storage devices, flash memory, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if instructions are transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. It should be understood, however, that computer-readable storage media and data storage media do not include connections, carrier waves, signals, or other transitory media, but are instead directed to non-transitory, tangible storage media. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.
Instructions may be executed by one or more processors, such as one or more digital signal processors (DSPs), general purpose microprocessors, application specific integrated circuits (ASICs), field programmable logic arrays (FPGAs), or other equivalent integrated or discrete logic circuitry. Accordingly, the term “processor,” as used herein may refer to any of the foregoing structure or any other structure suitable for implementation of the techniques described herein. In addition, in some aspects, the functionality described herein may be provided within dedicated hardware and/or software modules configured for encoding and decoding, or incorporated in a combined codec. Also, the techniques could be fully implemented in one or more circuits or logic elements.
The techniques of this disclosure may be implemented in a wide variety of devices or apparatuses, including a wireless handset, an integrated circuit (IC) or a set of ICs (e.g., a chip set). Various components, modules, or units are described in this disclosure to emphasize functional aspects of devices configured to perform the disclosed techniques, but do not necessarily require realization by different hardware units. Rather, as described above, various units may be combined in a codec hardware unit or provided by a collection of interoperative hardware units, including one or more processors as described above, in conjunction with suitable software and/or firmware.
Various examples have been described. These and other examples are within the scope of the following claims.
This application claims the benefit of U.S. Provisional Application 61/902,743 filed 11 Nov. 2013, the entire content of which is incorporated by reference.
| Number | Date | Country | |
|---|---|---|---|
| 61902743 | Nov 2013 | US |
