DETAILED ACTION
Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
Priority
Receipt is acknowledged of certified copies of papers required by 37 CFR 1.55.
Drawings
The drawings are objected to because FIGS. 8 and 9 contain unlabeled rectangular box(es). These figures must be provided with descriptive text labels.
PNG
media_image1.png
446
522
media_image1.png
Greyscale
PNG
media_image2.png
142
458
media_image2.png
Greyscale
In addition, FIG. 9 does not include reference numbers for the three unlabeled rectangular boxes. Reference numbers must be provided for the unlabeled boxes in FIG. 9 and the written description must be amended to include the reference numbers added to the drawings.
Corrected drawing sheets in compliance with 37 CFR 1.121(d) are required in reply to the Office action to avoid abandonment of the application. Any amended replacement drawing sheet should include all of the figures appearing on the immediate prior version of the sheet, even if only one figure is being amended. The figure or figure number of an amended drawing should not be labeled as “amended.” If a drawing figure is to be canceled, the appropriate figure must be removed from the replacement sheet, and where necessary, the remaining figures must be renumbered and appropriate changes made to the brief description of the several views of the drawings for consistency. Additional replacement sheets may be necessary to show the renumbering of the remaining figures. Each drawing sheet submitted after the filing date of an application must be labeled in the top margin as either “Replacement Sheet” or “New Sheet” pursuant to 37 CFR 1.121(d). If the changes are not accepted by the examiner, the applicant will be notified and informed of any required corrective action in the next Office action.
The objection to the drawings will not be held in abeyance. Applicant must show support for amendments and no new matter may be added.
Claim Interpretation - Means Plus Function
The following is a quotation of 35 U.S.C. 112(f):
(f) Element in Claim for a Combination. – An element in a claim for a combination may be expressed as a means or step for performing a specified function without the recital of structure, material, or acts in support thereof, and such claim shall be construed to cover the corresponding structure, material, or acts described in the specification and equivalents thereof.
The following is a quotation of pre-AIA 35 U.S.C. 112, sixth paragraph:
An element in a claim for a combination may be expressed as a means or step for performing a specified function without the recital of structure, material, or acts in support thereof, and such claim shall be construed to cover the corresponding structure, material, or acts described in the specification and equivalents thereof.
The claims in this application are given their broadest reasonable interpretation using the plain meaning of the claim language in light of the specification as it would be understood by one of ordinary skill in the art. The broadest reasonable interpretation of a claim element (also commonly referred to as a claim limitation) is limited by the description in the specification when 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, is invoked.
As explained in MPEP § 2181, subsection I, claim limitations that meet the following three-prong test will be interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph:
(A) the claim limitation uses the term “means” or “step” or a term used as a substitute for “means” that is a generic placeholder (also called a nonce term or a non-structural term having no specific structural meaning) for performing the claimed function;
(B) the term “means” or “step” or the generic placeholder is modified by functional language, typically, but not always linked by the transition word “for” (e.g., “means for”) or another linking word or phrase, such as “configured to” or “so that”; and
(C) the term “means” or “step” or the generic placeholder is not modified by sufficient structure, material, or acts for performing the claimed function.
Use of the word “means” (or “step”) in a claim with functional language creates a rebuttable presumption that the claim limitation is to be treated in accordance with 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph. The presumption that the claim limitation is interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, is rebutted when the claim limitation recites sufficient structure, material, or acts to entirely perform the recited function.
Absence of the word “means” (or “step”) in a claim creates a rebuttable presumption that the claim limitation is not to be treated in accordance with 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph. The presumption that the claim limitation is not interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, is rebutted when the claim limitation recites function without reciting sufficient structure, material or acts to entirely perform the recited function.
Claim limitations in this application that use the word “means” (or “step”) are being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, except as otherwise indicated in an Office action. Conversely, claim limitations in this application that do not use the word “means” (or “step”) are not being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, except as otherwise indicated in an Office action.
This application includes one or more claim limitations that do not use the word “means,” but are nonetheless being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, because the claim limitation(s) uses a generic placeholder that is coupled with functional language without reciting sufficient structure to perform the recited function and the generic placeholder is not preceded by a structural modifier. Such claim limitation(s) is/are:
an “external unit”, “additional unit”, a “converter unit”, and a “power supply unit” introduced in claim 1,
a “wireless communication unit” and a “WPAN communication unit” introduced in claim 2,
a “wire-bound communication unit” and a “USB communication unit” introduced in claim 3,
a “wire bound adapter communication unit” and a “USB adapter communication unit” introduced in claim 4,
a “plug connector element” introduced in claim 5,
a “display unit” introduced in claim 8,
a “retrofit part” introduced in claim 12,
an “external unit” and an “adapter unit” introduced in claim 14, and
a “WPAN communication unit” introduced in claim 15.
Because this/these claim limitation(s) is/are being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, it/they is/are being interpreted to cover the corresponding structure described in the specification as performing the claimed function, and equivalents thereof.
If applicant does not intend to have this/these limitation(s) interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, applicant may: (1) amend the claim limitation(s) to avoid it/them being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph (e.g., by reciting sufficient structure to perform the claimed function); or (2) present a sufficient showing that the claim limitation(s) recite(s) sufficient structure to perform the claimed function so as to avoid it/them being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph.
Claim Rejections - 35 USC § 112 - Indefinite
The following is a quotation of 35 U.S.C. 112(b):
(b) CONCLUSION.—The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the inventor or a joint inventor regards as the invention.
The following is a quotation of 35 U.S.C. 112 (pre-AIA ), second paragraph:
The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the applicant regards as his invention.
Claims 1-15 are rejected under 35 U.S.C. 112(b) or 35 U.S.C. 112 (pre-AIA ), second paragraph, as being indefinite for failing to particularly point out and distinctly claim the subject matter which the inventor or a joint inventor (or for applications subject to pre-AIA 35 U.S.C. 112, the applicant), regards as the invention.
Claim 1, lines 1 and 5 each recite “in particular”. It is not clear if the language that follows this language is required or optional.
Claim 1, lines 3-4, recites:
a communication interface for communication with an external unit by means of a first communication protocol,
The “external unit” and the “means of a first communication protocol” are recited amidst the functional recitation of the communication interface. It is not clear if these are required elements of the claimed invention (in which case the Examiner suggests affirmatively reciting them) or if they are non-limiting intended use (in which case the Examiner suggests removing them to avoid confusion).
Claim 1, lines 4-6, recites:
an adapter interface for communication with an additional unit, in particular the transceiver configuration device, by means of a second communication protocol ...
The “additional unit” and the “means of a second communication protocol” are recited amidst the functional recitation of the adapter interface. It is not clear if these are required elements of the claimed invention (in which case the Examiner suggests affirmatively reciting them) or if they are non-limiting intended use (in which case the Examiner suggests removing them to avoid confusion).
Claim 1, last two lines, recites:
characterized by a power supply unit for the autonomous power supply of at least the adapter unit.
It is not clear how to interpret “characterized by”. For example, it is not clear if this term should be interpreted as “wherein”, or if everything before this language is non-limiting intended use.
Claims 2-4 and 14 recite “in particular”. It is not clear how to interpret this language. See the discussion of similar language in claim 1.
Claim 12 recites “is designed as a retrofit part”. It is not clear what particular structure is being claimed (e.g., it is not clear how this further limits the structure of claim 1).
Claims 2-11, 14, and 15 all recite “characterized in that” and are rejected for the reasons discussed in claim 1.
Claims 2-15 are rejected because they depend from one or more of the claims rejected above and they fail to further limit the scope of claim 1 in such a way as to overcome the rejections of the claims from which they depend.
Claims 1-15 are also rejected because they include, or depend from claims that include, elements interpreted under 112(f) (see the 112(f) interpretations above) and there does not appear to be a linking between the 112(f) functions and the corresponding structure in the specification. See the discussion under Enablement, below. As a result, it is not clear what particular structure is within the scope of the claims.
Claim Rejections - 35 USC § 112 - Enablement
The following is a quotation of the first paragraph of 35 U.S.C. 112(a):
(a) IN GENERAL.—The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor or joint inventor of carrying out the invention.
The following is a quotation of the first paragraph of pre-AIA 35 U.S.C. 112:
The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor of carrying out his invention.
Claims 1-15 are rejected under 35 U.S.C. 112(a) or 35 U.S.C. 112 (pre-AIA ), first paragraph, as failing to comply with the enablement requirement. The claim(s) contains subject matter which was not described in the specification in such a way as to enable one skilled in the art to which it pertains, or with which it is most nearly connected, to make and/or use the invention.
Teachings of the Application.
The application at FIG. 8 illustrates a transceiver system 10 including an adapter 60. The adapter 60 includes a power supply unit 26, an adapter interface 64 including wire-bound adapter communication unit 66, a converter unit 74, a communication interface 20 including a wire-bound communication unit 30, a wireless communication unit 28, and a WPAN communication unit 36. The adapter 60 also forms a portion of a configuration unit 19 and a portion of a transceiver 12. See FIG. 8.
PNG
media_image1.png
446
522
media_image1.png
Greyscale
However, the figure does not appear to teach what particular structure is being claimed for each of these elements. In particular, FIG. 8 illustrates the invention as unlabeled boxes without teaching the particular structure.
Similarly, FIG. 9 illustrates a flow diagram of the method of operating the adapter 60.
PNG
media_image2.png
142
458
media_image2.png
Greyscale
Like FIG. 8, this figure has unlabeled boxes which do not teach what steps are performed. Furthermore, the boxes also do not have reference numbers, which makes it difficult to know what the boxes are supposed to represent. Line 100 and 102 are both described as “method steps”, and line 100 is also described as a method “sub-step”. See:
[0084] The method flow diagram shown schematically in FIG. 9 illustrates the method for operating the adapter 60. The method could comprise a plurality of method sub-steps. In the present case, the method for operating the adapter 60 is illustrated in an exemplary manner by means of a first method step 100 and a second method step 102. For communication with the external unit 16 by means of the communication interface 20, the external unit 16 is placed at least partially on the adapter 60 in the first method sub-step 100. The communication link is activated in the second method sub-step 100 [sic]. In this case, the power supply unit 26 is activated so that at least the adapter unit 62 is supplied with power autonomously by means of the power supply unit 26. Thus, the wireless communication link between the external unit 16 and the adapter 60 can be provided by means of the communication interface 20, wherein the communication interface 20 is formed by the WPAN communication unit 36 for wireless communication with the external unit 16.
The reference numbers do not appear to be used outside of this paragraph and this description teaches the method of operating the adapter in only a vague and general manner.
In summary, the application does not appear to teach how to make and use the invention.
Scope of the Claims.
Claim 1 recites
1 An adapter, in particular for a mobile transceiver configuration device, comprising
an adapter unit which comprises
a communication interface for communication with an external unit by means of a first communication protocol,
an adapter interface for communication with an additional unit, in particular the transceiver configuration device, by means of a second communication protocol, and
a converter unit for converting between the first communication protocol and the second communication protocol,
characterized by a power supply unit for the autonomous power supply of at least the adapter unit.
The scope of these claims are unclear (see the 112(b) rejections). However, in the interests of compact prosecution, the Examiner is interpreting the claim as if all of the elements are required.
The claim recites a “communication interface” and an “adapter interface”. These elements do not appear to be limited to any particular structure other than an “interface”. As a result, these elements have a broad scope that includes all structures for all “interfaces” to perform the recited functionality. The application does not appear to teach how to make and use these elements.
In the interests of compact prosecution the Examiner notes that the “unit” elements are interpreted under 112(f) (see the Claim Interpretation section above). There does not appear to be a linking between the 112(f) functions in the claim and a corresponding structure in the specification (this is discussed under “Written Description”). If Applicant successfully argues that the 112(f) interpretation is improper, then the application does not appear to teach how to make and use these elements.
Claim 13 recites a transceiver according to claim 1:
13. A transceiver system having an adapter according to claim 1, having the external unit and the additional unit.
This includes the broad scope of claim 1 and the application does not appear to teach how to make and use the subject matter of this claim. See also the discussion of claim 1.
Claim 14 recites a method for operating an adapter in accordance with claim 1.
14. A method for operating an adapter, in particular according to claim 1, having an external unit, wherein the adapter comprises an adapter unit with a communication interface for communication with the external unit, characterized in that at least the adapter unit is autonomously supplied with power.
This includes the broad scope of claim 1 and the application does not appear to teach how to make and use the subject matter of this claim. See also the discussion of claim 1.
Claims 2-12 depend from claim 1 and recite additional “units” with a broad scope and additional functionality. The application does not appear to teach how to make and use these additional elements. Furthermore, these claims do not appear to further limit the scope of claim 1 in such a manner as bring it within the teachings of the application.
Claim 15 depends from claim 14 and recites additional “units” with a broad scope and additional functionality. The application does not appear to teach how to make and use these additional elements. Furthermore, this claim does not appear to further limit the scope of claim 14 in such a manner as bring it within the teachings of the application.
When considering the teachings of the application and the scope of the claims, see MPEP 2173.05(g), 4th paragraph:
… Further, without reciting the particular structure, materials or steps that accomplish the function or achieve the result, all means or methods of resolving the problem may be encompassed by the claim. Ariad Pharmaceuticals., Inc. v. Eli Lilly & Co., 598 F.3d 1336, 1353, 94 USPQ2d 1161, 1173 (Fed. Cir. 2010) (en banc). Unlimited functional claim limitations that extend to all means or methods of resolving a problem may not be adequately supported by the written description or may not be commensurate in scope with the enabling disclosure, both of which are required by 35 U.S.C. 112(a) and pre-AIA 35 U.S.C. 112, first paragraph. In re Hyatt, 708 F.2d 712, 714, 218 USPQ 195, 197 (Fed. Cir. 1983); Ariad, 598 F.3d at 1340, 94 USPQ2d at 1167. …
This supports a finding that the broad scope of the claims may not be enabled by the teachings in the disclosure.
Other Considerations.
The nature of the invention is optical communications and methods. The components used in the various embodiments were known to one of ordinary skill. For example, one or ordinary skill would be familiar with components such as LEDs, OLEDs, Lightning ports (R), and a variety of different USB plugs in the context of the invention. Therefore, no teachings of how to make these individual components is required. Also, general signal processing and communications were also well-known.
Similarly, one of ordinary skill would also know how to perform other tasks in the present technological area and related to the invention, such as splicing and coupling the electrical and optical components together in a way that limits losses to a commercially acceptable level (although this is not explicitly taught in the application), and managing the temperature of electrical and optical components which are susceptible to performance degradation and undesirable operational variations based on temperature (although this is not explicitly taught in the application), and shielding components from EM interference because commercial systems routinely operate in the RF spectrum and would generate interference to electrical components within the system and outside of the system (although this is not explicitly taught).
However, the issues raised above regarding the scope of the claims and the teachings of the application are directed to making and using an apparatus with particular functionality that appears to require particular structures that are not obvious to one of ordinary skill.
Experimentation.
As discussed above, the claims do not appear to be limited to particular structures, and the application does not appear to teach the particular structures of the claimed elements. This broad scope includes many structures and method steps, and not all possibilities within the scope of the claims will produce the desired results or functions. Furthermore, the specification does not appear to identify or provide guidance as to what structures and steps within the scope of these claims are operative to make and use the invention, and which are not.
As a result, if one of ordinary skill were to attempt to make and use the full scope of the claims, it would require making, testing, or otherwise evaluating a large number of possible combination of structures and method steps to find what works and what does not work to perform the desired functionality. This results in a practically unlimited number of embodiments that would need to be made, tested, or otherwise evaluated to determine which embodiments are operative and which are inoperative.
This supports a finding that undue experimentation would be required to make and use the full scope of the claims.
Broadest Reasonable Interpretation and Opportunity to Amend.
During prosecution, Applicant has an opportunity to amend the claims to the desired scope. See MPEP 2111, 4th paragraph:
Because applicant has the opportunity to amend the claims during prosecution, giving a claim its broadest reasonable interpretation will reduce the possibility that the claim, once issued, will be interpreted more broadly than is justified. In re Yamamoto, 740 F.2d 1569, 1571 (Fed. Cir. 1984); In re Zletz, 893 F.2d 319, 321, 13 USPQ2d 1320, 1322 (Fed. Cir. 1989) (“During patent examination the pending claims must be interpreted as broadly as their terms reasonably allow.”); In re Prater, 415 F.2d 1393, 1404-05, 162 USPQ 541, 550-51 (CCPA 1969) … See also In re Morris, 127 F.3d 1048, 1054-55, 44 USPQ2d 1023, 1027-28 (Fed. Cir. 1997) (The court held that the PTO is not required, in the course of prosecution, to interpret claims in applications in the same manner as a court would interpret claims in an infringement suit. Rather, the “PTO applies to verbiage of the proposed claims the broadest reasonable meaning of the words in their ordinary usage as they would be understood by one of ordinary skill in the art, taking into account whatever enlightenment by way of definitions or otherwise that may be afforded by the written description contained in applicant’s specification.”).
Therefore, if Applicant intends the claims to have a scope that is narrower than the broadest reasonable interpretation, the claims should be amended during prosecution to more clearly provide the intended scope.
Conclusion.
The claims have a broad scope and the application does not appear to teach how to make the elements recited in the claim (and does not appear to teach corresponding method steps for operating the apparatus).
After careful consideration of the factors, the Examiner has concluded that the claims contain subject matter which was not described in the specification in such a way as to enable one skilled in the art to make and/or use the invention.
Claim Rejections - 35 USC § 112 - Written Description
The following is a quotation of the first paragraph of 35 U.S.C. 112(a):
(a) IN GENERAL.—The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor or joint inventor of carrying out the invention.
The following is a quotation of the first paragraph of pre-AIA 35 U.S.C. 112:
The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor of carrying out his invention.
Claims 1-15 are rejected under 35 U.S.C. 112(a) or 35 U.S.C. 112 (pre-AIA ), first paragraph, as failing to comply with the written description requirement. The claim(s) contains subject matter which was not described in the specification in such a way as to reasonably convey to one skilled in the relevant art that the inventor or a joint inventor, or for applications subject to pre-AIA 35 U.S.C. 112, the inventor(s), at the time the application was filed, had possession of the claimed invention.
As discussed above, the claims contain elements interpreted under 112(f) that do not appear to be described in the specification in such a way as to reasonably convey to one skilled in the art that the inventors, at the time the application was filed, had possession of the claimed invention. In particular, the application does not appear to teach the particular structure for the means-plus-function elements. See the discussion of the teachings of the application and the scope of the claims under “Enablement”.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
US 2021/0067249 (Hull) at FIG. 1 illustrates a free space optical communication system including an adapter 111 for a mobile device 110.
PNG
media_image3.png
460
647
media_image3.png
Greyscale
See, for example:
[0023] Certain aircraft equipment and systems, such as display 106, headset 109, and EFB 110, may use light communication (LC) to provide data and/or power connections to the aircraft. The LC-capable systems may have an embedded LC sensor 115 and LC transmitter 116 that are configured to communicate with LC access points 117, 118 onboard the aircraft. Alternatively, an external LC device 120 may connect directly to one or more device to support LC connections, such using as a dongle 120 that plugs into a USB or other port on display 106. The external LC communication device 120 has an LC sensor 121 and an LC transmitter 122. LC sensors 115, 121 (e.g., cameras or photodetectors) and LC transmitters 116, 122 (e.g., LED) need to be exposed to remote light sources and sensors in LC access points 117, 118.
Access Point Transceiver.
FIG. 3 illustrates a detailed view of an access point 300 including a controller 306, a set of lights for light communication 303, and a set of light sensors 309.
PNG
media_image4.png
455
742
media_image4.png
Greyscale
See, for example:
[0046] FIG. 3 depicts a light communication access point 300 for use in an aircraft according to an example embodiment. A first set of one or more lights 301 provide visible light for cockpit or cabin lighting. A second set of one or more lights 302 provide visible or invisible light for use in powering LC-capable devices. A third set of one or more lights 303 are adapted for transmitting data using visible or invisible light communications. Power supply 304 receives power from an aircraft electrical bus 305, such as an avionics bus or accessory bus. Power supply 304 provides power to cockpit/cabin lights 301, such as LEDs, incandescent, or fluorescent bulbs, which may be selected on or off by a crewmember or passenger. Power supply 304 also provides electricity to power lights 302, which may be LEDs or laser lights, that transmit power wirelessly to other devices. Controller 306 may manage when such wireless power is available and at what frequencies. Power lights 302 may transmit power over the same frequency or groups of one or more lights 302 may transmit power on different visible and/or invisible frequencies.
[0047] Data is transmitted using LC by encoding data bits using transmitter/encoder 307 into a signal that drives data lights 303, which then broadcast the information as light signals. Data lights may be LEDs or laser lights, for example. Data lights 303 may transmit data over the same frequency or groups of one or more lights 303 may transmit data on different frequencies. Controller 306 is coupled to an aircraft data network 308, which carries information, such as digital bit streams, packet data, voice, video, text, or other content. Controller 306 receives information to be broadcast and sends the information to transmitter/encoder 307, which encodes the information as digital signals that are transmitted by data lights 303 in the visible and/or invisible spectrum.
[0048] A light sensor 309 detects visible and/or invisible light and generates an electronic signal for receiver/decoder 310, which extracts data bits that are carried by the light. The extracted bits may carry information that can be processed by controller 306 and forwarded to aircraft data network 308. Light sensor 309 may be, for example, a camera, image sensor, or photodetector, such as a CMOS sensor or other electronic chip that converts photons to electrons for digital processing.
Communication Device.
FIG. 4 illustrates a detailed view of a light communications device including processors 401, memory 402, light sensor 414, and light source 417.
PNG
media_image5.png
561
747
media_image5.png
Greyscale
See, for example:
[0053] System memory 402 may be configured to store program instructions and/or data accessible by processor 401. In various embodiments, system memory 402 may be implemented using any suitable memory technology, such as Static Random-Access Memory (SRAM), Synchronous Dynamic RAM (SDRAM), nonvolatile/Flash-type memory, or any other type of memory. As illustrated, program instructions and data implementing certain operations and modules such as those described herein may be stored within system memory 402 as program instructions 410 and data storage 411, respectively. In other embodiments, program instructions and/or data may be received, sent, or stored upon different types of computer-accessible media or on similar media separate from system memory 402.
[0054] A computer-accessible medium may include any tangible and/or non-transitory storage media or memory media such as electronic, magnetic, or optical media—e.g., disk or CD/DVD-ROM coupled to device 400 via bus 403. The terms “tangible” and “non-transitory,” as used herein, are intended to describe a computer-readable storage medium (or “memory”) excluding propagating electromagnetic signals but are not intended to otherwise limit the type of physical computer-readable storage device that is encompassed by the phrase computer-readable medium or memory. For instance, the terms “non-transitory computer-readable medium” or “tangible memory” are intended to encompass types of storage devices that do not necessarily store information permanently, including for example, Random Access Memory (RAM). Program instructions and data stored on a tangible computer-accessible storage medium in non-transitory form may further be transmitted by transmission media or signals, such as electrical, electromagnetic, or digital signals, which may be conveyed via a communication medium such as a network and/or a wireless link.
[0060] Light communication is supported using a light sensor 414 and a receiver/decoder 415 to receive data and a transmitter/encoder 416 and light transmitter 417 to transmit data. Light sensor 414 may be, for example, a camera, image sensor, or photodetector, such as a CMOS sensor or other electronic chip that converts photons to electrons for digital processing. Light sensor 414 detects light and generates an electronic signal for receiver/decoder 415, which extracts data bits that are carried by the light. The extracted bits may carry information that can be used by processors 401A-N. Data can also be sent using LC by encoding data bits using transmitter/encoder 416 into a signal that drives light transmitter 417, which then broadcasts the information as light signals. Light transmitter 417 may be an LED or laser, for example. Light sensor 414 and light transmitter 417 may use invisible (e.g., infrared or ultraviolet) and/or visible light spectrum for high speed data communication.
US 11,128,376 (Passe) at FIG. 2 illustrates a wireless optical network including access points 209, 214, 215, 216 and mobile devices 201, 202.
PNG
media_image6.png
604
862
media_image6.png
Greyscale
See also the paragraph spanning cols. 7-8:
(25) FIG. 2 depicts an example system 200 for using wireless communication devices 201 and 202 that are capable of both RF and LC communication. Device 201 may be a tablet computer or smart phone, for example, that has an internal RF antenna (not shown) and an embedded LC sensor 203 and LC transmitter 204. Device 202 may be a laptop computer, for example, that has an internal RF antenna (not shown) and uses an internal (not shown) or external LC communication device 205. External LC communication device 205 may connect directly to device 202, such using as a dongle that plugs into a USB or other port on device 202, or may connect remotely via a cable or wireless connection. External LC communication device 205 has an LC sensor 206 and an LC transmitter 207. Typically, an RF antenna may be an internal component because the case or housing of devices 201 and 202 are transparent to RF signals. On the other hand, LC sensors 203, 206 (e.g., cameras or photodetectors) and LC transmitters 204, 207 (e.g., lights) need to be exposed to remote light sources and sensors.
US 2009/0310971 (Kim) at FIG. 5 illustrates a wireless optical communication system used with mobile devices.
PNG
media_image7.png
838
479
media_image7.png
Greyscale
Kim at [0076] teaches several configurations, including “granular source mode” in which plural light sources are organized into a group called a “cell”:
a cell consists of one or more light sources. Accordingly, a configuration mode of a cell can be classified into a single source mode consisting of one light source, and a granular source mode consisting of two or more light sources.
At [0077] it is taught that when moving from one adjacent light source to another, continuous data service is provided without requiring new initialization process because “no cell change occurs”:
In the granular source mode, when a VLC terminal enters a service area of another adjacent light source from a service area of a service source light source, since the adjacent light sources are providing user services in the same environment, the VLC terminal can receive continuous data without a separate synchronization or link setup process, i.e. a cell initialization process, and no cell change occurs.
At [0075], it is taught that the cells are dynamic and include adjacent light sources as the user moves:
the cell mapping is performed such that when a VLC terminal is located in a service area of a specific light source, all adjacent cells neighboring the specific light source are included in the relevant cell. However, the cell mapping may be performed such that only some of the adjacent cells are included in the cell. For example, the light sources to be added to the cell may be selected from the adjacent light sources taking into account a moving pattern of the VLC terminal. If the VLC terminal is characterized by moving only in a predetermined direction, the light sources to be added may be selected taking only the corresponding direction into account. As another example, if a moving velocity of the VLC terminal is higher than or equal to a specific velocity, a range of the light sources to be added may be extended to an area broader than the region of the adjacent light sources. In addition, the cell change may not be made despite movement of the VLC terminal, according to communication environments and types of user services.
FIG. 13 and [0080] teaches the communication, including data format in the uplink/downlink frames, including the unique IDs.
[0072] discusses the communication control device monitoring and updating the cells as the user moves to allow adjacent light sources to be within the cell for continuous service:
the communication control device 200 updates and stores the cell light source matrix and the adjacent light source matrix on a real-time basis, it detects adjacent light sources for the light source corresponding to the service area where the VLC terminal is located, using the adjacent light source matrix. Further, the communication control device 200 performs cell mapping such that the detected adjacent light sources are added to the cell, and updates the cell light source matrix and the adjacent light source matrix according to the cell mapping.
See also [0078] which teaches that when leaving a cell for another cell, the sign in process must be repeated:
where the cell has one light source mapped thereto, if a VLC terminal moves and leaves a service area of the current source service light source, the VLC terminal leaves the service area of the cell and enters a service area of another cell, or enters a service area of a light source for which no cell is formed. Accordingly, the VLC terminal should perform a synchronization procedure to establish a new communication link.
Kim at [0009] teaches the modulation of light at the terminal devices (“The LED driver 23 optically modulates the data input from the encoder 22, and drives the LED 24 so that the transmission data can be transferred to an external device.”).
Any inquiry concerning this communication or earlier communications from the examiner should be directed to DARREN WOLF whose telephone number is (571)270-3378. The examiner can normally be reached Monday through Friday, 7:00 AM to 3:00 PM.
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, KENNETH N. VANDERPUYE can be reached at 571-272-3078. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/DARREN E WOLF/Primary Examiner, Art Unit 26341