Patent Application
20190258292
The present disclosure relates generally to docking systems, and, more particularly, to docking systems for portable computing devices such as, for example, tablet computing devices.
As portable computing devices continue to increase in capability and functionality, deployment of portable computing devices in business offices, hospitals, industrial settings, and other types of environments, also continues to increase. In some instances, such as to assist in obtaining and/or maintaining an advantage over competitors, for example, a business may place a premium on obtaining the most capable and/or most up-to-date portable computing devices as soon as those devices become available. Thus, in addition to securing up-to-date portable computing devices, such as tablet computing devices, for example, a business may also obtain protective enclosures, such as cases that surround and safeguard portable computing devices. Such enclosures may reduce the likelihood of damage to the portable computing device in the event that the device is dropped, rained or spilled upon, or the like.
At times, portable computing devices may benefit from occasionally being connected to docking systems. For example, it may be advantageous to dock or attach a portable computing device, such as a tablet computing device, for example, to a battery charger to permit charging of an onboard battery. In other instances, it may be advantageous to establish a wired connection between a portable computing device and a particular network, such as to permit more secure communications that may be less vulnerable to surreptitious electronic eavesdropping of wireless signals, for example. However, typical docking systems impose numerous restrictions on various aspects of docking, utilization, operation, etc., of portable computing devices. These restrictions may, at times, be considered cumbersome and may thus diminish the appeal of particular types of portable computing devices.
Claimed subject matter is particularly pointed out and distinctly claimed in the concluding portion of the specification. However, both as to organization and/or method of operation, together with objects, features, and/or advantages thereof, it may best be understood by reference to the following detailed description if read with the accompanying drawings in which:
Reference is made in the following detailed description to accompanying drawings, which form a part hereof, wherein like numerals may designate like parts throughout that are corresponding and/or analogous. It will be appreciated that the figures have not necessarily been drawn to scale, such as for simplicity and/or clarity of illustration. For example, dimensions of some aspects may be exaggerated relative to others. Further, it is to be understood that other embodiments may be utilized. Furthermore, structural and/or other changes may be made without departing from claimed subject matter. References throughout this specification to “claimed subject matter” refer to subject matter intended to be covered by one or more claims, or any portion thereof, and are not necessarily intended to refer to a complete claim set, to a particular combination of claim sets (e.g., method claims, apparatus claims, etc.), or to a particular claim.
References throughout this specification to one implementation, an implementation, one embodiment, an embodiment, and/or the like means that a particular feature, structure, characteristic, and/or the like described in relation to a particular implementation and/or embodiment is included in at least one implementation and/or embodiment of claimed subject matter. Thus, appearances of such phrases, for example, in various places throughout this specification are not necessarily intended to refer to the same implementation and/or embodiment or to any one particular implementation and/or embodiment. Furthermore, it is to be understood that particular features, structures, characteristics, and/or the like described are capable of being combined in various ways in one or more implementations and/or embodiments and, therefore, are within intended claim scope. In general, of course, as has always been the case for the specification of a patent application, these and other issues have a potential to vary in a particular context of usage. In other words, throughout the disclosure, particular context of description and/or usage provides helpful guidance regarding reasonable inferences to be drawn; however, likewise, “in this context” in general without further qualification refers at least to the context of the present patent application.
Some example methods, apparatuses, and/or articles of manufacture are disclosed herein that may be used, in whole or in part, to facilitate and/or support one or more operations and/or techniques for a docking system for a portable computing device, such as implemented in connection with one or more computing and/or communication networks, devices, and/or protocols discussed herein, for example. As used herein, “portable computing device,” “mobile device,” “handheld device,” or like terms may be used interchangeably and refer to any kind of special purpose computing platform and/or apparatus that may from time to time have a position or location that changes. In some instances, a portable computing device may, for example, be capable of communicating with other devices, mobile or otherwise, through wireless transmission or receipt of information according to one or more communication protocols. As a way of illustration, special purpose portable computing devices may include, for example, cellular telephones, smart telephones, personal digital assistants (PDAs), laptop computers, personal entertainment systems, gaming devices, tablet personal computers (PC), personal audio or video devices, personal navigation devices, or the like. It should be appreciated, however, that these are merely examples of portable computing devices that may be used, at least in part, to implement one or more operations and/or techniques for a docking system, and that claimed subject matter is not limited in this regard.
As alluded to previously, portable computing devices, such as tablet computing devices, for example, may be protected from damage via placement of a computing device within an enclosure while the device is deployed in an operational environment. Operational environments may include, but are not limited to, offices, hospitals, industrial and/or administrative settings, business establishments, as well as a wide variety of other types of environments, virtually without limitation. Thus, in many instances, a portable computing device operating within a protective enclosure may comprise a particularly effective workplace tool due, at least in part, to its ability to provide instantaneous computing power to numerous situations. However, a need to occasionally dock a portable computing device, while within a protective enclosure, to a particular docking system may represent a drawback to the convenience associated with utilizing such computing devices.
For example, in a factory environment, a portable computing device may be utilized to allow a user, such as a factory equipment operator, to enter a number of parameters collected at various locations within the factory. At times, the user may dock or return the portable computing device to a docking system to permit collected parameters to be processed by, for example, more capable, fixed computing stations, such as a mainframe server, for example. However, if the user is required to interact with the portable computing device while the device is connected to a docking system, certain manipulations of the portable computing device may not be easily accomplished. For example, if a user selects to display content, such as parameters, forms, etc., utilizing a first display mode, such as a landscape mode, transition to a second display mode, such as to a portrait mode, may involve reorienting and/or rearranging hardwired connections, for example.
In addition, it is recognized that particular portable computing devices may be compatible with certain particular types or brands of docking systems. In some instances, connecting a portable computing device with incompatible or mismatched docking system equipment may, for example, damage a portable computing device, docking system, or both. Accordingly, a portable computing device user operating in a large factory, hospital, university, for example, may be required to travel a significant distance simply to find a docking system compatible with his or her particular portable computing device.
Another example may relate to a use of portable computing devices operating as point-of-sale terminals in a retail setting. In such instances, one or more retail staff members may, for example, be required to periodically remove portable computing devices from order counters or other forward areas of the retail establishment so that the portable computing devices can be securely stored at the close of a business day. However, users may determine that removal of portable computing devices from protective enclosures, as well as detaching chip and pin readers and/or other ancillary devices from the portable computing device, comprises a burdensome and/or time-consuming task. Additionally, such attaching and reattaching of ancillary devices, as well as charging devices, which may occur several times per day, may give rise to undue deterioration of device connectors, receptacles, cables, etc.
Further, portable computing devices operating in retail environments, for example, may be vulnerable to theft by unruly and/or unscrupulous individuals. Thus, a retail business owner or other personnel, for example, may secure a portable computing device to a relatively fixed object utilizing cable and lock mechanism, for example. However, such physical security measures may be easily compromised by surreptitiously obtaining a key, for example, by severing a cable, or compromised (e.g., stolen) by other means. In such instances, theft of portable computing devices may not only represent loss of physical assets, such as the portable computing device itself, but may also represent a loss of valuable trade secrets, such as proprietary software, proprietary configuration files, employee passwords, and so forth.
Accordingly, embodiments of claimed subject matter may provide a docking system that alleviates many of the drawbacks and vulnerabilities of conventional portable computer docking systems. In particular embodiments, a docking system for a portable computing device, such as a handheld tablet computing device, for example, may permit the portable computing device to be easily disengaged and rotated, in a plane, counterclockwise, clockwise, or inverted, so as to accommodate any number of computing applications that display parameters in portrait mode or landscape mode, for example. In addition, embodiments may facilitate a portable computing device, operating within a protective enclosure, to be docked to a large variety of compatible docking assemblies, which may permit secure communication through a wired network interface, for example, to provide charging of onboard batteries without requiring a user to physically insert a cable into a receptacle of the computing device, which may be termed as “cable-free” charging. In particular embodiments, a docking system for a portable computing device may additionally comprise, for example, security features that may sufficiently reduce the likelihood of theft of the computing device but without involving bulky and/or unwieldy cables and/or keyed locks, or other easily-defeated security measures.
In view of the above,
It should be noted that enclosure 120 is merely an example enclosure, which may enclose a tablet computing device, and claimed subject matter is not limited in this respect. In other embodiments, enclosure 120 may accommodate other electronic devices, for example, such as other types of displays and/or devices that provide user interfaces, for example, without necessarily providing “computing” capabilities per se.
In embodiments, case mount 350 may be capable of facilitating and/or supporting communications with a variety of portable computing devices, such as tablet computing devices, for example. Accordingly, case mount 350 may comprise signal conditioning and/or other electronics, which facilitate and/or support communication with, for example, tablet computing devices manufactured by the Samsung® Company of South Korea, tablet computing devices manufactured by Apple® Incorporated, of Cupertino Calif., and/or tablet computing devices manufactured by other entities and claimed subject matter is not limited in this respect. Accordingly, portable computing device 150 may comprise any display and/or computing device and claimed subject matter is not limited in this respect. In certain embodiments, case plate 205 of portable computing device enclosure 120 may comprise a common base plate capable of being interchanged with differently sized portable computing device enclosures. Thus, case mount 350 may comprise a capability to communicate with various portable computing devices, including tablet computing devices comprising various case sizes. By way of example, but not limitation, in some instances, case sizes of approximately 250.0 mm×180.0 mm (9.7 inch×6.9 inch), 230.0 mm×160.0 mm (9.0 inch×6.2 inch), and/or 200.0 mm×130.0 mm (7.7 inch×5.2 inch), 200.0 mm×120.0 mm (7.7 inch×4.8 inch) may be used herein, although claimed subject matter is not limited in this respect. It should also be noted that in particular embodiments, a portable computing device may not be disposed within an enclosure, such as enclosure 120, for example. In such instances, a case mount, such as case mount 350, may be secured to a removable panel of the portable computing device.
In particular embodiments, such securing of case side 160 of enclosure 120 to an enclosure side of case mount 350 may be facilitated by way of screws or other types of fasteners, which may provide compatibility with VESA (Video Electronics Standards Association) mounting brackets. Although four screw-type fasteners may be fitted and/or mated with screw bosses 302 of an enclosure side of case mount 350, embodiments of claimed subject matter may utilize a different number of screw-type fasteners and/or screw bosses, or other types of fasteners, for example, to fixedly attach or secure an enclosure side of case mount 350 to, for example, case side 160 of enclosure 120. For example, an enclosure side of case mount 350 may be attached or secured to case side 160 of enclosure 120 utilizing three or fewer screw holes, or may utilize a greater number of screw-type fasteners, such as five or greater screw-type fasteners, for example.
As described in detail herein, case mount 350 may be removably secured to base mount 450 by way of one or more notches which may operate to physically connect with latches of base mount 450. Base mount 450 may attach or couple to a relatively fixed and/or stable surface, such as a wall or a desk, or may be attached to a base or stand, just to illustrate possible examples.
In particular embodiments, case mount 350 may comprise, for example, a circular or round-shaped body having a plurality of contacts 435, and one or more notches 420A-420D. Also in particular embodiments, base mount 450 may comprise a plurality contact pins such as “pogo” pins 430 (further described with reference to
Additionally, although latches 410A-410D and notches 420A-420D are shown in
As shown in
In embodiments, base mount 450 may comprise a manual lock/unlock feature 440. Accordingly, responsive to insertion of, for example, a rod or cylinder-shaped tool, perhaps accompanied by applying clockwise or counterclockwise rotation, for example, latches 410A-410D may be manually disengaged from corresponding notches 420A-420D, for example. In particular embodiments, base mount 450 may be unlatched or disengaged from case mount 350 via a computer-implemented method or application that runs on portable computing device 150, for example.
In particular embodiments, operations and/or functions of contact group 515A, shown in a first quadrant of a surface of case mount 350, for example, may be replicated in electrically divided/independent quadrants comprising contact groups 515B, 515C, and 515D. Thus, in certain embodiments, case mount 350, which may be attached to portable computing device enclosure 120, may be disengaged from base mount 450 and rotated 90.0°, as represented by arrow 520, and reengaged with base mount 450 to permit contact group 515B to come into contact with base mount contacts 510. Likewise, case mount 350 may be disengaged from base mount 450 and rotated an additional 90.0° to permit contact group 515C to come into contact with base mount contacts 510. Further, case mount 350 may be disengaged from base mount 450 and rotated an additional 90.0° so as to permit contact group 515D to come into contact with base mount contacts 510. In addition, as case mount 350 is rotated relative to base mount 450, latches of case mount 350, as represented by latch 410A, remain capable of coupling with corresponding notches of base mount 450.
In particular embodiments, base mount contacts 510 may comprise spring-loaded contacting pins such as “pogo” pins comprising relatively slender cylinder-shaped pins, wherein a top and/or distal portion of a pogo pin is capable of extension and/or retraction relative to a base portion of the pin. However, it should be noted that base mount contacts 510 may utilize other approaches toward maintaining a sufficient and/or suitable electrical connection with individual contacts of contact groups 515A-515D, and claimed subject matter is not limited in this respect. In addition, it should be noted that although 12 of base mount contacts 510 are indicated in
In the embodiment of
In another embodiment, fasteners 464A and 464B of solenoid actuators 462A and 462B, respectively, may operate to hold a solenoid slug into position within the body of the solenoid and against a tensioned spring, wherein the spring operates to apply a force along a longitudinal axis of a solenoid actuator. In such an embodiment, orientation of solenoid actuators 462A and 462B may be reversed from the orientation shown in
Accordingly, in such embodiment, after solenoid actuators 462A and 462B are energized utilizing a sufficient electrical current flowing through the coil of the solenoid, for example, solenoid actuator longitudinal shafts 464C and 464D may apply a force to a raised wall (not shown on cam ring 451 of
It should be noted that embodiments of claimed subject matter may embrace a variety of approaches, other than that of the embodiment of
In particular embodiments, latches 410A-410D may engage with notches 420A-420D via a locking approach rather than by way of application of clamping pressure to notches 420A-420D. For example, in an embodiment, latch 410A, for example, may engage with notch 420A, wherein latch 410A may be positioned on or over an extending lip of notch 420A. In a particular embodiment, one or more springs, for example, may facilitate deflection of the latch, during engagement and/or disengagement of latch 410A with notch 420A. After such deflection, for example, latch 410A may come to rest under the extending lip of notch 420A. In embodiments, if a user attempts to separate case mount 350 from base mount 450, proximity of latch 410A with notch 420A, for example operates to separation of case mount 350 from base mount 450. In particular embodiments, if one or more solenoid is utilized to actuate the cam ring, latch 410A, for example, may be moved outward, such as in a direction opposite arrows 447A, thus permitting latch 410A to become disengaged from a lip of notch 420A, thereby permitting case mount 350 to be separated from base mount 450.
In particular embodiments, one or more magnets positioned around cam ring 451 may provide an additional approach toward securing base mount 450 to case mount 350. In embodiments, magnets may be built into housing 450A so as to provide attraction to corresponding metallic elements of case mount 350. In particular embodiments, use of magnets in base mount 450 may facilitate case mount 350 and enclosure 120 to be held into place instead of or in addition to engaging latches 410A-410D with one or more of notches 420A-420D.
In the embodiment of
Network interface 480 of
Network protocol converter 484 may operate to facilitate protocol conversion between Ethernet and USB, although claimed subject matter is intended to embrace protocol conversion between any number of serial and/or parallel data stream conversions. Although not explicitly shown in
Latches 410A-410D may also be disengaged and or engaged from corresponding notches of a case mount, for example, responsive to receipt of an instruction generated by a computer program operating, for example, on portable computing device 150. In addition, in particular embodiments, prior to release of latches 410A-410D, lock controller 488 may notify DC-DC converter/regulator 482 to remove power from base mount contacts 510. In certain embodiments, removal of power, such as DC power, for example, may minimize or reduce likelihood of electrical arcing between one or more of base mount contacts 510 and one or more contacts of contact group 515A-515D. Such arcing may be prone to occurring if an electrical current, such as may flow through one of contact groups 515A-515D to one or more of base mount contacts 510, for example, is interrupted, such as by electrically disconnecting one of contact group 515 from base mount contacts 510.
Microcontroller 490 may direct operations of base mount 450. In embodiments, microcontroller 490 may comprise one or more computer processors coupled to one or more memory devices, which may provide one or more sources of executable computer instructions in the form physical states and/or signals (e.g., stored in memory states), for example. Microcontroller 490 may communicate with portable computing device 150 by way of base mount contacts 510, which may physically connect (e.g., via pogo pins) to contact group 515A, contact group 515B, contact group 515C, or contact group 515D, as described with reference to
As shown in
(3.0×1010 cm/s)/(400.0×106/s)=75.0 cm (1)
Accordingly, a conductor comprising a length of 75.0 cm corresponds to the free-space wavelength of a 400.0 MHz signal. Thus, at least in particular embodiments, conductor lengths, such as L1 and L2, for example, of
In certain embodiments, it may be advantageous to utilize conductor lengths equivalent to significantly smaller fractions, such as one-tenth of one-quarter (λ/40) of the free-space wavelengths of signal frequencies (e.g., 400.0 MHz), which may be computed substantially in accordance with expression 2, below:
(18.75 cm)/10.0=1.875 cm=0.738 inch
Thus, in particular embodiments, it may be advantageous to maintain conductor lengths within case mount 350, for example, to less than one-tenth of one quarter wavelength (λ/4), of a signal frequency. If conductor lengths comprise less than approximately λ/40, input signal impedance, such as input signal impedance computed or assessed at one of contact groups 515A, 515B, 515C, or 515D, for example, may facilitate a voltage standing wave ratio (VSWR) of less than 1.67:1.0. In other embodiments, conductor lengths maintained below approximately one-sixteenth of one-quarter wavelength of a signal frequency (e.g., 1/16 of λ/4) may facilitate an input signal VSWR of less than, for example, 1.5:1.0. In other embodiments, VSWR of 2.0:1.0 may comprise an upper threshold, above which measures of signal quality, such as bit error rate and signal plus noise and distortion (SINAD), may reach unacceptable levels, for example.
Further, in embodiments in which USB communications occurs at increased data communication speeds, such as 800.0 Mb per second, conductor lengths, such as conductor lengths within case mount 350, may be scaled accordingly so as to maintain an input signal VSWR of less than, for example, 1.5:1.0. In such an instance, just as an example, conductor lengths comprising 1/16 of λ/4 (e.g., 0.934 cm or 0.369 inch computed for a signal frequency of 800.0 MHz) may facilitate an input signal VSWR of less than 1.5:1.0. In embodiments, strip line and/or microstrip transmission lines may be utilized to convey signals to and from contact group 515A, for example, to contact group interface 382, although claimed subject matter is not limited to any particular transmission line technique. In embodiments, contact group interface 382 and USB hub 386 are positioned proximate with contact group 515B and contact group 5.5 C so as to allow conductor lengths L3 and L4 to be negligibly small in relation to free space wavelength (λ).
Case mount 350 may additionally comprise external USB ports 368, for example. In particular embodiments, external USB ports 388 may be coupled to a chip and/or pin reader, such as for use in a retail establishment, for example, a barcode reader, a magnetic stripe reader, and so forth, as may be appropriate for service and/or other types of environments wherein the portable computing device 150, for example, may be utilized. It should be noted that external USB ports 388 may operate to communicate with additional types of devices, and claimed subject matter is not limited in this respect. Case mount 350 may further comprise voltage signaling module 384, which may comprise, for example, a signature resistor, which may provide an indication to microcontroller 490 of base mount 450 as to an operating voltage of portable computing device 150. For example, in one embodiment, if voltage signaling module 384 comprises an approximately 5.0 kΩ resistor, microcontroller 490 may instruct DC-DC converter/regulator to provide 12.0 V, just as a possible example, for use by portable computing device 150.
Case mount 350 may additionally comprise device-specific signal conditioning 392, which may adapt one or more discrete signals from base mount 450 to signals capable of being interpreted by portable computing device 150. For example, device-specific signal conditioning 392 may provide appropriate signal levels at, for example, appropriate timing intervals specific to portable computing device 150. Device-specific signal conditioning 392 may provide overvoltage protection to portable computing device 150 such as, for example, by terminating a voltage signal to portable computing device 150 that may bring about damage to the portable computing device, for example. In another embodiment, device-specific signal conditioning 392 may provide a signal to portable computing device 150 to indicate that an external USB port, such as one or more of external USB ports 388, for example, is to be powered by base mount 450 rather than portable computing device 150, just as an example. Case mount 350 may further comprise device charge monitor 390, which may, for example, monitor a rate of charging of portable computing device 150, which may ensure that portable computing device 150 does not consume electrical current at a rate beyond one or more specified limits. In addition, case mount 350 comprises device-specific wiring interface 394, in which conductors are arranged and/or organized into a cable suitable for use with portable computing device 150. In one example, device-specific wiring interface 394 provide communication with an Apple iPad® utilizing, for example, a “lightning” connector.
It should be noted that although RFID mount 910 is shown disposed directly beneath base mount 450, in other embodiments, mount 910 may be positioned at different locations, for a variety of reasons, such as ergonomics, handicapped access (Americans with Disabilities Act), speed, and/or ease of use.
In particular embodiments, hinge 1232 may be designed to present a predetermined threshold amount of friction during, for example, rotation of base mount 450 and housing 1245 about axis 1235. In a particular embodiment, hinge 1232 may be capable of presenting sufficient friction so as to require torque approximately in the range of 1.0-10.0 Nm to rotate base mount 450 and housing 1245 about axis 1235, and claimed subject matter is not limited in this respect.
In the context of the present disclosure, the term “connection,” the term “component” and/or similar terms are intended to be physical, but are not necessarily always tangible. Whether or not these terms refer to tangible subject matter, thus, may vary in a particular context of usage. As an example, a tangible connection and/or tangible connection path may be made, such as by a tangible, electrical connection, such as an electrically conductive path comprising metal or other electrical conductor, that is able to conduct electrical current between two tangible components. Likewise, a tangible connection path may be at least partially affected and/or controlled, such that, as is typical, a tangible connection path may be open or closed, at times resulting from influence of one or more externally derived signals, such as external currents and/or voltages, such as for an electrical switch. Non-limiting illustrations of an electrical switch include a transistor, a diode, etc. However, a “connection” and/or “component” in a particular context of usage, likewise, although physical, can also be non-tangible, such as a connection between a client and a server over a network, which generally refers to the ability for the client and server to transmit, receive, and/or exchange communications, as discussed in more detail later.
In a particular context of usage, such as a particular context in which tangible components are being discussed, therefore, the terms “coupled” and “connected” are used in a manner so that the terms are not synonymous. Similar terms may also be used in a manner in which a similar intention is exhibited. Thus, “connected” is used to indicate that two or more tangible components and/or the like, for example, are tangibly in direct physical contact. Thus, using the previous example, two tangible components that are electrically connected are physically connected via a tangible electrical connection, as previously discussed. However, “coupled,” is used to mean that potentially two or more tangible components are tangibly in direct physical contact. Nonetheless, is also used to mean that two or more tangible components and/or the like are not necessarily tangibly in direct physical contact, but are able to co-operate, liaise, and/or interact, such as, for example, by being “optically coupled.” Likewise, the term “coupled” may be understood to mean indirectly connected in an appropriate context. It is further noted, in the context of the present disclosure, the term “physical,” if used in relation to memory, such as memory components or memory states, as examples, necessarily implies that memory, memory components, and/or memory states, continuing with the example, is tangible.
Additionally, in the present disclosure, in a particular context of usage, such as a situation in which tangible components (and/or similarly, tangible materials) are being discussed, a distinction exists between being “on” and being “over.” As an example, deposition of a substance “on” a substrate refers to a deposition involving direct physical and tangible contact without an intermediary, such as an intermediary substance (e.g., an intermediary substance formed during an intervening process operation), between the substance deposited and the substrate in this latter example; nonetheless, deposition “over” a substrate, while understood to potentially include deposition “on” a substrate (since being “on” may also accurately be described as being “over”), is understood to include a situation in which one or more intermediaries, such as one or more intermediary substances, are present between the substance deposited and the substrate so that the substance deposited is not necessarily in direct physical and tangible contact with the substrate.
A similar distinction is made in an appropriate particular context of usage, such as in which tangible materials and/or tangible components are discussed, between being “beneath” and being “under.” While “beneath,” in such a particular context of usage, is intended to necessarily imply physical and tangible contact (similar to “on,” as just described), “under” potentially includes a situation in which there is direct physical and tangible contact, but does not necessarily imply direct physical and tangible contact, such as if one or more intermediaries, such as one or more intermediary substances, are present. Thus, “on” is understood to mean “immediately over” and “beneath” is understood to mean “immediately under.”
It is likewise appreciated that terms such as “over” and “under” are understood in a similar manner as the terms “up,” “down,” “top,” “bottom,” and so on, previously mentioned. These terms may be used to facilitate discussion, but are not intended to necessarily restrict scope of claimed subject matter. For example, the term “over,” as an example, is not meant to suggest that claim scope is limited to only situations in which an embodiment is right side up, such as in comparison with the embodiment being upside down, for example. An example includes a flip chip, as one illustration, in which, for example, orientation at various times (e.g., during fabrication) may not necessarily correspond to orientation of a final product. Thus, if an object, as an example, is within applicable claim scope in a particular orientation, such as upside down, as one example, likewise, it is intended that the latter also be interpreted to be included within applicable claim scope in another orientation, such as right side up, again, as an example, and vice-versa, even if applicable literal claim language has the potential to be interpreted otherwise. Of course, again, as always has been the case in the specification of a patent application, particular context of description and/or usage provides helpful guidance regarding reasonable inferences to be drawn.
Unless otherwise indicated, in the context of the present disclosure, the term “or” if used to associate a list, such as A, B, or C, is intended to mean A, B, and C, here used in the inclusive sense, as well as A, B, or C, here used in the exclusive sense. With this understanding, “and” is used in the inclusive sense and intended to mean A, B, and C; whereas “and/or” can be used in an abundance of caution to make clear that all of the foregoing meanings are intended, although such usage is not required. In addition, the term “one or more” and/or similar terms is used to describe any feature, structure, characteristic, and/or the like in the singular, “and/or” is also used to describe a plurality and/or some other combination of features, structures, characteristics, and/or the like. Furthermore, the terms “first,” “second,” and “third,” and the like are used to distinguish different aspects, such as different components, as one example, rather than supplying a numerical limit or suggesting a particular order, unless expressly indicated otherwise. Likewise, the term “based on” and/or similar terms are understood as not necessarily intending to convey an exhaustive list of factors, but to allow for existence of additional factors not necessarily expressly described.
It has proven convenient at times, principally for reasons of common usage, to refer to such physical signals and/or physical states as bits, values, elements, parameters, symbols, characters, terms, numbers, numerals, measurements, content, and/or the like. It should be understood, however, that all of these and/or similar terms are to be associated with appropriate physical quantities and are merely convenient labels. Unless specifically stated otherwise, as apparent from the preceding discussion, it is appreciated that throughout this specification discussions utilizing terms such as “processing,” “computing,” “calculating,” “determining,” “establishing,” “obtaining,” “identifying,” “selecting,” “generating,” and/or the like may refer to actions and/or processes of a specific apparatus, such as a special purpose computer and/or a similar special purpose computing and/or network device. In the context of this specification, therefore, a special purpose computer and/or a similar special purpose computing and/or network device is capable of processing, manipulating and/or transforming signals and/or states, typically in the form of physical electronic and/or magnetic quantities, within memories, registers, and/or other storage devices, processing devices, and/or display devices of the special purpose computer and/or similar special purpose computing and/or network device. In the context of this particular disclosure, as mentioned, the term “specific apparatus” therefore includes a general purpose computing and/or network device, such as a general purpose computer, once it is programmed to perform particular functions, such as pursuant to program software instructions.
In the preceding description, various aspects of claimed subject matter have been described. For purposes of explanation, specifics, such as amounts, systems, and/or configurations, as examples, were set forth. In other instances, well-known features were omitted and/or simplified so as not to obscure claimed subject matter. While certain features have been illustrated and/or described herein, many modifications, substitutions, changes, and/or equivalents will now occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all modifications and/or changes as fall within claimed subject matter.
The present application is a continuation of U.S. patent application Ser. No. 16/156,177, entitled “Docking System for Portable Computing Device in an Enclosure”, filed Oct. 10, 2018, now U.S. patent Ser. No. ______, which is a continuation of U.S. patent application Ser. No. 15/659,556, entitled “Docking System for Portable Computing Device in an Enclosure”, filed Jul. 25, 2017, now U.S. Pat. No. 10,101,770, which claims priority to U.S. Provisional Patent Application Ser. No. 62/368,947, entitled “Docking System for Tablet Enclosure,” filed Jul. 29, 2016, which are assigned to the assignee hereof and the entire disclosures of which are expressly incorporated herein by reference.
| Number | Date | Country | |
|---|---|---|---|
| 62368947 | Jul 2016 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16156177 | Oct 2018 | US |
| Child | 16402498 | US | |
| Parent | 15659556 | Jul 2017 | US |
| Child | 16156177 | US |
