Add files using upload-large-folder tool
Browse filesThis view is limited to 50 files because it contains too many changes. See raw diff
- applicant/10708294.xml +0 -0
- applicant/10875584.xml +21 -0
- applicant/10907714.xml +387 -0
- applicant/11127438.xml +16 -0
- applicant/11198904.xml +463 -0
- applicant/11240256.xml +388 -0
- applicant/11277545.xml +841 -0
- applicant/11284751.xml +231 -0
- applicant/11357130.xml +30 -0
- applicant/11368298.xml +31 -0
- applicant/11391033.xml +560 -0
- applicant/11400595.xml +425 -0
- applicant/11403031.xml +99 -0
- applicant/11408375.xml +29 -0
- applicant/11421232.xml +15 -0
- applicant/11462049.xml +369 -0
- applicant/11499183.xml +870 -0
- applicant/11505207.xml +366 -0
- applicant/11536285.xml +290 -0
- applicant/11538824.xml +37 -0
- applicant/11539522.xml +39 -0
- applicant/11578424.xml +144 -0
- applicant/11593029.xml +520 -0
- applicant/11606289.xml +516 -0
- applicant/11614238.xml +2 -0
- applicant/11618162.xml +1 -0
- applicant/11624634.xml +0 -0
- applicant/11647425.xml +200 -0
- applicant/11672562.xml +74 -0
- applicant/11685894.xml +540 -0
- applicant/11706040.xml +336 -0
- applicant/11719508.xml +31 -0
- applicant/11722809.xml +15 -0
- applicant/11735531.xml +24 -0
- applicant/11736661.xml +190 -0
- applicant/11736899.xml +367 -0
- applicant/11742378.xml +1009 -0
- applicant/11751302.xml +525 -0
- applicant/11756486.xml +332 -0
- applicant/11767036.xml +26 -0
- applicant/11774106.xml +44 -0
- applicant/11774444.xml +0 -0
- applicant/11778521.xml +0 -0
- applicant/11782554.xml +0 -0
- applicant/11799200.xml +668 -0
- applicant/11843036.xml +0 -0
- applicant/11844920.xml +22 -0
- applicant/11850930.xml +28 -0
- applicant/11854279.xml +0 -0
- applicant/11854344.xml +333 -0
applicant/10708294.xml
ADDED
|
The diff for this file is too large to render.
See raw diff
|
|
|
applicant/10875584.xml
ADDED
|
@@ -0,0 +1,21 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>10875584</doc-number>
|
| 8 |
+
<date>2007-06-25</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<heading id="h-1">IN THE SPECIFICATION:</heading>
|
| 14 |
+
<p id="p-1" num="1">Please amend the Specification as follows.</p>
|
| 15 |
+
<p id="p-2" num="2">Page 1, after line 1 insert:</p>
|
| 16 |
+
<heading id="h-2">REFERENCE TO RELATED APPLICATIONS</heading>
|
| 17 |
+
<p id="p-3" num="3">This application claims priority of British Application No. 0402893.2, filed on February 10, 2004 in United Kingdom. The subject matter of this earlier filed application is hereby incorporated by reference.</p>
|
| 18 |
+
<p id="p-4" num="4">- 2 - Application No. 10/875,584 </p>
|
| 19 |
+
</description>
|
| 20 |
+
</us-patent-application>
|
| 21 |
+
|
applicant/10907714.xml
ADDED
|
@@ -0,0 +1,387 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>10907714</doc-number>
|
| 8 |
+
<date>2005-04-13</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<heading id="h-1">COMPOS<confidence value="8">I</confidence>
|
| 14 |
+
TION TO RETARD THE ONSET OF SYMPTOMS OF ALZHEIMER'S DISEASE </heading>
|
| 15 |
+
<heading id="h-2">DESCRIPTION</heading>
|
| 16 |
+
<p id="p-1" num="1">Field of the Invention [Para 1] This invention relates to a chemical composition and method for using said composition as a dietary supplement to increase the transfer of curcumin and other dietary substances and nutrients from the gastrointestinal tract into the bloodstream to retard the onset of symptoms of Alzheimer's disease in humans.</p>
|
| 17 |
+
<p id="p-2" num="2">Description of Related Art [Para 2] Alzheimer's disease is a debilitating degenerative affliction of the nervous system, which will become increasingly common during the next three decades as the American population ages. In the baby-boomer generation in particular, has aged. Current estimates reveal that by <part-num-ref name="baby-boomer generation in particular, has aged. Current estimates reveal that by">2035,</part-num-ref>
|
| 18 |
+
when the average individual of the "baby boomer" generation is age <part-num-ref name=""baby boomer" generation is age">85,</part-num-ref>
|
| 19 |
+
potentially 50% of Americans will have developed Alzheimer's disease. Alzheimer's Association website, http://search.a<confidence value="5">l</confidence>
|
| 20 |
+
z.org/AboutAD/statistics.asp. By providing a treatment that can delay the onset of symptoms of Alzheimer's by as little as five years, at age <part-num-ref name="onset of symptoms of Alzheimer's by as little as five years, at age">85,</part-num-ref>
|
| 21 |
+
fifty percent of the United States cases of Alzheimer's could be eliminated. <confidence value="66">Id</confidence>
|
| 22 |
+
. Alzheimer's disease has a negative impact on an individual's memory and cognitive functions, ability to perform the simple activities of daily living, and causes behavioral problems among its sufferers with which families must learn to cope. Typically, Alzheimer's disease also reduces the lifespan of an individual by increasing one's risk of succumbing to secondary infections and illnesses. The disease is associated with the accumulation of <confidence value="4">P</confidence>
|
| 23 |
+
-amyloid plaques in the brain which leads to the eventual destruction of brain cells. The primary cause of Alzheimer's disease may be flaws in the metabolic processes governing production, accumulation, or disposal of the <confidence value="2">p</confidence>
|
| 24 |
+
-amyloid protein fragments. Therefore, treatments for Alzheimer's disease often have focused on dissolving <confidence value="2">p</confidence>
|
| 25 |
+
-amyloid or preventing the aggregation of the <confidence value="2">p</confidence>
|
| 26 |
+
-amyloid fragments into plaque formations. </p>
|
| 27 |
+
<p id="p-3" num="3">[Para 3] Recent research has shown that people indigenous to the Indian subcontinent exhibit a much lower incidence of Alzheimer's disease than people living in the United States.</p>
|
| 28 |
+
<p id="p-4" num="4">Moreover, the research indicated that less than one percent of individuals in the examined population <boundary-data type="header">Page 1 of 25</boundary-data>
|
| 29 |
+
<page-break num="2"/>
|
| 30 |
+
on the Indian subcontinent developed Alzheimer's and that the overall incidence rates of the disease in that location are among the lowest ever reported. V. Chandra et al., Incidence of<confidence value="86">Al</confidence>
|
| 31 |
+
zheimer<confidence value="68">'s</confidence>
|
| 32 |
+
disease in a rural community in India: the Indo-US study, N<confidence value="8">e</confidence>
|
| 33 |
+
urology, 57(6): 98<confidence value="8">5</confidence>
|
| 34 |
+
-989 (2001). So<confidence value="88">me</confidence>
|
| 35 |
+
researchers have attributed the low incidence of Alzheimer's disease in India to regional diets that are high in the curry spice, turmeric. Turmeric contains a substance, curcumin, which has demonstrated metabolic activity similar to non-steroidal anti-inflammatory drugs. Giselle P. Lim et al., The Curry Spice Curcumin Reduces Ox<confidence value="5">i</confidence>
|
| 36 |
+
dative Damage and Amy<confidence value="585">loi</confidence>
|
| 37 |
+
d Pathology in an Alzheimer Transgenic Mouse, Journal of Neuroscience, 21(21), 8370-8377 (2001). </p>
|
| 38 |
+
<p id="p-5" num="5">[Para 4] Curcumin, a phenolic antioxidant phytochemical derived from the turmeric plant (Curcuma <confidence value="7">l</confidence>
|
| 39 |
+
onga), is an effective antioxidant, antispasmodic, anti-inflammatory, anticoagulant, anticarcinogenic, and aids immunomodulatory activities and wound healing in the body. <confidence value="56">Id</confidence>
|
| 40 |
+
. at <part-num-ref name="body. Id. at">8370.</part-num-ref>
|
| 41 |
+
</p>
|
| 42 |
+
<p id="p-6" num="6">Curcumin exhibits an affinity for <confidence value="4">P</confidence>
|
| 43 |
+
-amyloid and both inhibits the aggregation of <confidence value="4">P</confidence>
|
| 44 |
+
-amyloid fragments into plaque formations as well as dissolves existing <confidence value="4">P</confidence>
|
| 45 |
+
-amyloid plaques. F. Yang et al., Curcumin inhibits formation of <confidence value="82">A/</confidence>
|
| 46 |
+
<confidence value="222222222">oligomers</confidence>
|
| 47 |
+
and fibrils, binds plaques and reduces amyloid in vivo, <confidence value="5">J</confidence>
|
| 48 |
+
ournal of Biological Chemistry (2004). </p>
|
| 49 |
+
<p id="p-7" num="7">[Para 5] As an antioxidant, curcumin removes harmful free radicals from the body, thereby protecting the human body, and particularly, the brain, by preventing lipid peroxidation. This antioxidant property of curcumin limits the formation and accumulation of <confidence value="4">P</confidence>
|
| 50 |
+
-amyloid plaques within the brain. Giselle P. Lim et al., The Curry Spice Curcumin Reduces Oxidative Damage and Amyloid Patho<confidence value="8">l</confidence>
|
| 51 |
+
ogy in an A<confidence value="5">l</confidence>
|
| 52 |
+
zheimer Transgenic Mouse, Journal of Neuroscience, 21(21), at <part-num-ref name="Alzheimer Transgenic Mouse, Journal of Neuroscience, 21(21), at">8370</part-num-ref>
|
| 53 |
+
(2001). The non-steroidal anti-inflammatory activity of curcumin includes inhibiting cyclooxygenase <part-num-ref name="non-steroidal anti-inflammatory activity of curcumin includes inhibiting cyclooxygenase">2,</part-num-ref>
|
| 54 |
+
nuclear factor KB-mediated transcription of inflammatory cytokines, and the inhibition of inducible nitric oxide synthase. <confidence value="66">Id</confidence>
|
| 55 |
+
. at <part-num-ref name="inhibition of inducible nitric oxide synthase. Id. at">8372.</part-num-ref>
|
| 56 |
+
Research has shown that parenteral administering both low and high doses of curcumin reduces inflammation in the brain. <confidence value="66">Id</confidence>
|
| 57 |
+
. at <part-num-ref name="brain. Id. at">8373.</part-num-ref>
|
| 58 |
+
Curcumin may also stimulate microglial phagocytosis of amyloid in the brain as well as destroy plaques that accumulate within the brain. <confidence value="668">Id.</confidence>
|
| 59 |
+
</p>
|
| 60 |
+
<p id="p-8" num="8">at 8375.</p>
|
| 61 |
+
<p id="p-9" num="9">[Para 6] One disadvantage to the use of curcumin as an oral dietary supplement is that curcumin is poorly absorbed from inside the gastrointestinal tract into the human bloodstream.</p>
|
| 62 |
+
<p id="p-10" num="10">When ingested, curcumin normally remains in the gastrointestinal tract and uptake into the blood<confidence value="88">st</confidence>
|
| 63 |
+
ream is neg<confidence value="8888">ligi</confidence>
|
| 64 |
+
ble. R.A. S<confidence value="8888">harm</confidence>
|
| 65 |
+
a, Preclinical pharmacokinetic study of dietary curcumin and its effects on biomarkers of cancer chemoprevention, Cl<confidence value="88">in</confidence>
|
| 66 |
+
ical Cancer Research, V<confidence value="888">olu</confidence>
|
| 67 |
+
me <part-num-ref name="bloodstream is negligible. R.A. Sharma, Preclinical pharmacokinetic study of dietary curcumin and its effects on biomarkers of cancer chemoprevention, Clinical Cancer Research, Volume">6</part-num-ref>
|
| 68 |
+
(2000). Eve<confidence value="8">n</confidence>
|
| 69 |
+
with high dietary intake, curcumin is rapidly glucuronidated after ingestion, thereby resulting in low <confidence value="88">pl</confidence>
|
| 70 |
+
asma levels of curcum<confidence value="8">i</confidence>
|
| 71 |
+
n. F. Yang et al., Curcumin inhibits formation of A<confidence value="22">,6</confidence>
|
| 72 |
+
<confidence value="222222222">oligomers</confidence>
|
| 73 |
+
and fibrils, <boundary-data type="header">Page 2 of 25</boundary-data>
|
| 74 |
+
<page-break num="3"/>
|
| 75 |
+
binds plaques and reduces <confidence value="2222222">amy/old</confidence>
|
| 76 |
+
<confidence value="4">/</confidence>
|
| 77 |
+
n vivo, <confidence value="5">J</confidence>
|
| 78 |
+
ournal of Biological Chemistry, p. <part-num-ref name="(2000). Even with high dietary intake, curcumin is rapidly glucuronidated after ingestion, thereby resulting in low plasma levels of curcumin. F. Yang et al., Curcumin inhibits formation of A,6 oligomers and fibrils, binds plaques and reduces amy/old /n vivo, Journal of Biological Chemistry, p.">22</part-num-ref>
|
| 79 |
+
(2004). Thus, current research indicates that orally administered curcumin, for the most part, is excreted in the feces without being absorbed and processed by the human body. To make available the beneficial effects of curcumin to Alzheimer's sufferers, the bioavailability of curcumin in the human body must be increased. Currently, clinical trials are being conducted at the University of California, Los Angeles, to examine the safety and tolerability of intravenous curcumin, and to determine the effect curcumin has as a treatment for patients suffering from mild to moderate Alzheimer's disease. John <confidence value="8888">Ring</confidence>
|
| 80 |
+
<confidence value="88">ma</confidence>
|
| 81 |
+
n & <confidence value="668">Jen</confidence>
|
| 82 |
+
ny Ba<confidence value="888">rde</confidence>
|
| 83 |
+
ns, A Phase , Double-Blind, Placebo-Controlled Study of the Safety and <confidence value="222222222222">Tolerability</confidence>
|
| 84 |
+
of Two Doses of Curcumin C3 Comp<confidence value="5">l</confidence>
|
| 85 |
+
ex versus Placebo <confidence value="5">i</confidence>
|
| 86 |
+
n Pat<confidence value="5">i</confidence>
|
| 87 |
+
ents with M<confidence value="66">il</confidence>
|
| 88 |
+
d to Moderate <confidence value="22222222222">Alzheimer's</confidence>
|
| 89 |
+
Disease, National Institutes of Health, ClinicalTrials.gov (2003). </p>
|
| 90 |
+
<p id="p-11" num="11">[Para 7] Piperine, a botanical extract from the fruits of P<confidence value="66">ip</confidence>
|
| 91 |
+
er <confidence value="222222">nigrum</confidence>
|
| 92 |
+
(black pepper) and <confidence value="22222">P/per</confidence>
|
| 93 |
+
<confidence value="5">/</confidence>
|
| 94 |
+
ongum, has been determined to increase the bioavailability of curcumin in the body when both curcumin and piperine are taken together. Studies have shown that oral administration of 20.0 mg of piperine with 2.0 grams of curcumin increases the bioavailability of curcumin by 2,000%. U.S. Patent No. 6,054,585, issued to Majeed et al., on April <part-num-ref name="bioavailability of curcumin by 2,000%. U.S. Patent No. 6,054,585, issued to Majeed et al., on April">25,</part-num-ref>
|
| 95 |
+
<part-num-ref name="bioavailability of curcumin by 2,000%. U.S. Patent No. 6,054,585, issued to Majeed et al., on April 25,">2000,</part-num-ref>
|
| 96 |
+
describes a process for making high-purity piperine from black pepper or long pepper for nutritional uses, however the '585 patent does not discuss the use of curcumin with piperine as a means for retarding the onset of Alzheimer's disease. </p>
|
| 97 |
+
<p id="p-12" num="12">U.S. Patent Nos. 5,536,506, 5,744,161, and 5,972,382, issued to Majeed et al., on July 16, 1996, April 28, 1998, and October 26, 1999, respectively, all describe the use of piper as a bioavailability enhancer for aiding and improving gastrointestinal absorption and systemic utilization of nutrients and nutritional supplements. The use of piperine to enhance the bioavailability of curcumin and other beneficial substances, which are not easily absorbed by the human gastrointestinal tract, is claimed by the '506, '161, and '382 patents, however, none of the three prior art patents mention the use of piperine for enhancing the bioavailability of curcumin to retard the onset of symptoms of Alzheimer's disease in humans as claimed by the applicant's current patent application.</p>
|
| 98 |
+
<p id="p-13" num="13">[Para 8] Galantamine, a natural plant extract derived from the daffodil, snowdrop, and the spider lily, is an acetylcholinesterase inhibitor. Acetylcholinesterase is an enzyme that breaks down acetylcholine in the synaptic cleft between nerve cells. Acetylcholine is involved in memory and learning processes. Research has shown that the level of acetylcholine present in the nervous system of Alzheimer's patients is abnormally low. Galantamine increases the level of acetylcholine present in the brain by inhibiting the activity of acetylchol<confidence value="8">i</confidence>
|
| 99 |
+
nesterase. In addition to being a useful therapeutic agent in the treatment of Alzheimer's disease, galantamine may also be useful for treating mild cognitive impairment, an age-related condition often diagnosed as a precursor condition <boundary-data type="header">Page 3 of 25</boundary-data>
|
| 100 |
+
<page-break num="4"/>
|
| 101 |
+
and risk factor for developing Alzheimer's. Galantamine is also effective in treating Alzheimer's disease because it works to modulate nicotinic receptors on brain cells, which respond to acetylcholine, thereby preserving the number and functional integrity of nicotinic receptors in the brain. In Alzheimer's patients, the number and functional integrity of nicotinic receptors is diminished resulting in fewer receptors for acetylcholine. The benefits of treating Alzheimer's with galantamine are not affected by previous treatments using other acetylcholinesterase inhibitors. Thus, galantamine may work to effectively halt the progression of Alzheimer's disease and also allows a patient to regain some memory and cognitive functions as well as being able to perform some simple tasks of daily living. None of the three prior art patents mention the use of piperine for enhancing the bioavailability of galantamine to retard the onset of symptoms of Alzheimer's disease in humans as claimed by the applicant's current patent application. </p>
|
| 102 |
+
<p id="p-14" num="14">[Para 9] Huperzine A, an alkaloid plant extract from the club moss Huperzia serrata, is a nootropic agent that also strongly inhibits the activity of acetylcholinesterase. As huperzine A inhibits the break down of acetylcholine by acetylchol<confidence value="8">i</confidence>
|
| 103 |
+
nesterase, more acetylcholine becomes available to stimulate neurons. Huperzine A provides a long-lasting, potent means for inhibiting the enzymatic activity of acetylchol<confidence value="88">in</confidence>
|
| 104 |
+
esterase, thereby increasing the amount of acetylcholine present within the nervous system. The prior art does not describe the use of piperine for enhancing the bioavailability of huperzine A to retard the onset of symptoms of Alzheimer's disease in humans as claimed by the applicant's current patent application. </p>
|
| 105 |
+
<p id="p-15" num="15">[Para 10] Oleic acid increases the absorptivity of the intestines so that food and nutrients can be fully absorbed into the body. In this way, oleic acid aids the body in digesting and processing substances that are difficult to digest. Bile (phosphatidylcholine) is the body's principle source of oleic acid in the small intestine, however only small amounts are produced. Oleanolic acid and ursolic acid share similar properties with oleic acid and also enhance the effects of curcumin in the body.</p>
|
| 106 |
+
<p id="p-16" num="16">The prior art, including the United States patents discussed above, does not describe the use of piperine for enhancing the bioavailability of oleic acid to retard the onset of symptoms of Alzheimer's disease in humans as claimed by the applicant's current patent application.</p>
|
| 107 |
+
<p id="p-17" num="17">[Para 11] Pyritinol is a vitamin B6 derivative that improves glucose uptake within the brain, has antioxidant abilities, and enhances the immune system by increasing neutrophil activity. The Food and Drug Administration approved pyritinol for use to improve memory, concentration, and vigilance. Once again, the prior art does not describe the use of piperine for enhancing the bioavailability of pyritinol to retard the onset of symptoms of Alzheimer's disease in humans as claimed by the applicant's current patent application.</p>
|
| 108 |
+
<boundary-data type="header">Page 4 of 25</boundary-data>
|
| 109 |
+
<p id="p-18" num="18">
|
| 110 |
+
<page-break num="5"/>
|
| 111 |
+
[Para 12] Vinpocetine is another drug that has shown memory-enhancing properties in humans. Vinpocetine is believed to enhance blood flow in the brain, safeguard brain cells against damage, and inhibit the activity of a substance known as phosphodiesterase, all of which would retard the chances of developing symptoms of Alzheimer's disease. </p>
|
| 112 |
+
<p id="p-19" num="19">[Para 13] Vitamin B5, or pantothenic acid, is used by the human body along with choline to form acetylcholine. Thus, as important precursors to the formation of acetylcholine, which is often present in reduced levels in Alzheimer's patients, choline and vitamin B5 are necessary nutritional supplements for preventing the onset of symptoms associated with neurodegenerative disorders, such as Alzheimer's.</p>
|
| 113 |
+
<p id="p-20" num="20">[Para 14] Gamma tocopherol, an analog of vitamin E, has been proven to act as a strong antioxidant useful in the prevention of the symptoms of Alzheimer's disease in humans. Sesame lignans, preferably in the form of sesamolin, enhances the bioavailability of gamma tocopherol at the cellular level, thereby increasing the effectiveness of gamma tocopherol in combating the effects of the symptoms of Alzheimer's disease.</p>
|
| 114 |
+
<p id="p-21" num="21">[Para 15] U.S. Patent No. 6,572,899, issued to Gorsek on June 3, 2003, describes a composition of orally ingestible nutrients for treating memory loss, dementia, and Alzheimer's disease. The '899 patent does not describe the use of curcumin and piperine to delay the onset of symptoms of Alzheimer's disease as does the applicant's application.</p>
|
| 115 |
+
<p id="p-22" num="22">[Para 16] U.S. Patent No. 6,486,194, issued to Ducharme et al., on November 26, 2002, describes the use of enzyme inhibitors to disrupt the activity of cyclooxygenase to treat neurodegenerative diseases, including Alzheimer's disease. Although the '194 patent claims the oral administration of an enzyme inhibitor, the particular enzyme inhibited in that patent is not acetylcholinesterase, nor does the '194 invention describe the use of curcumin or piperine to retard the symptoms of Alzheimer's disease.</p>
|
| 116 |
+
<p id="p-23" num="23">[Para 17] U.S. Patent No. 6,646,013, issued to Barker et al., on November 11, 2003, describes a composition comprising multiple nutrients for reducing the risk of colorectal cancer in mammals. The '013 patent claims the use of curcumin as one of the cancer-preventing nutrients, however, the '013 does not describe the use of curcumin for preventing the onset of the symptoms of Alzheimer's disease in humans.</p>
|
| 117 |
+
<p id="p-24" num="24">[Para 18] U.S. Patent No. 6,133,306, issued to Beal on October 17, 2000, describes a method of inhibiting neurodegenerative diseases, including Alzheimer's disease, by administering nitroindazole to a patient to inhibit a neuronal oxide synthase. The '306 patent does not describe the use of curcumin or piperine to delay the onset of the symptoms of Alzheimer's disease in humans.</p>
|
| 118 |
+
<boundary-data type="header">Page 5 <confidence value="88">of</confidence>
|
| 119 |
+
<confidence value="88">25</confidence>
|
| 120 |
+
</boundary-data>
|
| 121 |
+
<p id="p-25" num="25">
|
| 122 |
+
<page-break num="6"/>
|
| 123 |
+
Other Publications <confidence value="8888">[Par</confidence>
|
| 124 |
+
a 19] K. Abascal & E. <confidence value="2222222">Yarnell</confidence>
|
| 125 |
+
, Alzheimer's disease: part 1- biology and botanicals, Alte<confidence value="8">r</confidence>
|
| 126 |
+
native & Complementary Therapies, 10(1), 18-21 (2004). </p>
|
| 127 |
+
<p id="p-26" num="26">[Para 20] K. Abascal & E. <confidence value="2222222">Yarnell</confidence>
|
| 128 |
+
, Alzheimer's disease: part 2- a botanical treatment plan, Alternative & Complementary Therapies, 10(2), 67-72 (2004). </p>
|
| 129 |
+
<p id="p-27" num="27">[Para 21] H.P.T. Ammon & M.A. <confidence value="2222">Wahl</confidence>
|
| 130 |
+
, Pharmaco<confidence value="5">l</confidence>
|
| 131 |
+
ogy <confidence value="88">of</confidence>
|
| 132 |
+
Curcuma <confidence value="22222">longa</confidence>
|
| 133 |
+
, Planta Medica, vol. 57, 1- <confidence value="8">7</confidence>
|
| 134 |
+
(1997). </p>
|
| 135 |
+
<p id="p-28" num="28">[Para 22] R.B. Arora et al., A<confidence value="885">nti</confidence>
|
| 136 |
+
-inflammatory studies on Curcuma longa (Turmeric), Indian Journal of Medical Research, 59(8), 1289-1295 (1971). </p>
|
| 137 |
+
<p id="p-29" num="29">[Para 23] Atal et al., Biochemical Basis of Enhanced Drug Bioavailability by Piperine: Evidence that Piperine is a Potent Inhibitor of Drug Metabolism, Journal of Pharmacology & Experimental Therapeutics, 232(1), 258-262 (1985).</p>
|
| 138 |
+
<p id="p-30" num="30">[Para 24] Atal et al., Scientific Evidence on the Role of Ayurvedic Herbals on Bioavailability of Drugs, Journal of Ethnopharmacology, vol. <part-num-ref name="Role of Ayurvedic Herbals on Bioavailability of Drugs, Journal of Ethnopharmacology, vol.">4,</part-num-ref>
|
| 139 |
+
229-232 (1981). </p>
|
| 140 |
+
<p id="p-31" num="31">[Para 25] D.L. Bai et al., Huperzine A, a potential therapeutic agent for treatment of Alzheimer's disease, Current Medicinal Chemistry, 7(3), 355-374 (2000).</p>
|
| 141 |
+
<p id="p-32" num="32">[Para 26] Bano et al., Effect of piperine on bioavailability and pharmacokinetics of propranolol and theophylline in healthy volunteers, European Journal of Clinical Pharmacology, 41:615-617 (1991).</p>
|
| 142 |
+
<p id="p-33" num="33">[Para 27] Bano et al., The Effect of Piperine on Pharmacokinetics of Phenytoin in Healthy Volunteers, Planta Medica, vol. <part-num-ref name="Effect of Piperine on Pharmacokinetics of Phenytoin in Healthy Volunteers, Planta Medica, vol.">17,</part-num-ref>
|
| 143 |
+
568-569 (1987). </p>
|
| 144 |
+
<p id="p-34" num="34">
|
| 145 |
+
<confidence value="888">[Pa</confidence>
|
| 146 |
+
<confidence value="8">r</confidence>
|
| 147 |
+
a 28] D. Bereczki & I. Fekete, A systematic review of vinpocetine therapy in acute ischaemic stroke, European Journal of Clinical Pharmacology, 55:349-352 (1999). </p>
|
| 148 |
+
<boundary-data type="header">Page 6 of 25</boundary-data>
|
| 149 |
+
<p id="p-35" num="35">
|
| 150 |
+
<page-break num="7"/>
|
| 151 |
+
[Para 29] Biope<confidence value="65882">rine@</confidence>
|
| 152 |
+
-Nature<confidence value="5">'</confidence>
|
| 153 |
+
s B<confidence value="4">i</confidence>
|
| 154 |
+
oavailab<confidence value="58888">ility</confidence>
|
| 155 |
+
Enhan<confidence value="66">ci</confidence>
|
| 156 |
+
ng Thermonutrient, Executive Summary, Sabinsa Corporation, Piscataway, N.J. (1996). </p>
|
| 157 |
+
<p id="p-36" num="36">[Para 30<confidence value="8">]</confidence>
|
| 158 |
+
<confidence value="5">J</confidence>
|
| 159 |
+
. Blasiak et al., Curcumin damages DNA in human gastric mucosa cells and <confidence value="7">l</confidence>
|
| 160 |
+
ymphocytes, Journal of Environmental Pathology, Toxicology and Oncology, 18(4), 271-276 (1999). </p>
|
| 161 |
+
<p id="p-37" num="37">[Para 31] F. <confidence value="22222">Bonte</confidence>
|
| 162 |
+
et al., Protective effect of curcuminoids on epidermal skin cells under free oxygen radical stress, Planta Medica, vol. 63, 265-266 (1997). </p>
|
| 163 |
+
<p id="p-38" num="38">
|
| 164 |
+
<confidence value="8888">[Par</confidence>
|
| 165 |
+
a 3<confidence value="8">2</confidence>
|
| 166 |
+
] Chem. Abstracts, 118: 6637, <confidence value="58855">Johri</confidence>
|
| 167 |
+
et al., An Ayurvedic formulation 'Trikatu and its Constituents<confidence value="4">;</confidence>
|
| 168 |
+
Journal of Ethnopharmacology, 37(2), 85-91 (1992). </p>
|
| 169 |
+
<p id="p-39" num="39">[Para 33] Chem. Abstracts, 110: 6454, Wood et al., Overseas Dev. Nat. Resource Inst., 3(2), 55- <confidence value="88">64</confidence>
|
| 170 |
+
(1988). </p>
|
| 171 |
+
<p id="p-40" num="40">
|
| 172 |
+
<confidence value="888">[Pa</confidence>
|
| 173 |
+
ra 34] D. Choud hary et al., Modulation of radioresponse of glyoxalase system by curcumin, Journal of Ethnopharmacology, vol. 64, 1-7 (1999). </p>
|
| 174 |
+
<p id="p-41" num="41">[Para 35] Dahanukar et al., Influence of Trikatu Powder on Rifampicin Bioavailability, Indian Drugs, July 1983, 402-404.</p>
|
| 175 |
+
<p id="p-42" num="42">[Para 36] DeKosky, Presentation to the Senate Appropriations Committee<confidence value="5">;</confidence>
|
| 176 |
+
Labor, Health and Human Services, Education , and Related Agencies Subcommittee (2001). </p>
|
| 177 |
+
<p id="p-43" num="43">
|
| 178 |
+
<confidence value="8888">[Par</confidence>
|
| 179 |
+
a 37] S.D. Deod<confidence value="88">ha</confidence>
|
| 180 |
+
r et al., Preliminary study on antirheumatic activity of curcumin (diferoyl methane), Indian Journal of Medical Research, vol. 71, 632-634 (1980). </p>
|
| 181 |
+
<p id="p-44" num="44">[Para 38] S.S. Deshpande & G.B. Maru, Effects of curcumin on the formation of benzo[a]pyrene derived DNA adducts in vitro, Cancer Letters, vol. <part-num-ref name="formation of benzo[a]pyrene derived DNA adducts in vitro, Cancer Letters, vol.">96,</part-num-ref>
|
| 182 |
+
71-80 (1995). </p>
|
| 183 |
+
<p id="p-45" num="45">[Para 39] U.R. Deshpande et al., Protective effect of turmeric (Curcuma longa L.) extract on carbon tetrachloride-induced liver damage in rats, Indian Journal of Experimental Biology, vol. 36, 573-577 (1998).</p>
|
| 184 |
+
<boundary-data type="header">Page 7 of 25</boundary-data>
|
| 185 |
+
<p id="p-46" num="46">
|
| 186 |
+
<page-break num="8"/>
|
| 187 |
+
[Para 40] M.S. Ebadi, Pharmacodynamic basis of herbal medicine, CRC Press (2002). </p>
|
| 188 |
+
<p id="p-47" num="47">[Para 41] T. Erkinjuntti et al., Efficacy of galantamine in probable vascular dementia and Alzheimer's disease combined with cerebrovascular disease: a randomised trial, Lancet, vol. <part-num-ref name="randomised trial, Lancet, vol.">359,</part-num-ref>
|
| 189 |
+
1283-1290 (2002). </p>
|
| 190 |
+
<p id="p-48" num="48">[Para 42] E. Ernst, Herbal medications for common ailments in the elderly, Drugs and Aging, 15(6), 423-428 (1999).</p>
|
| 191 |
+
<p id="p-49" num="49">
|
| 192 |
+
<confidence value="888">[Pa</confidence>
|
| 193 |
+
ra 43] H <confidence value="85">.J</confidence>
|
| 194 |
+
. Gertz & M. Kiefer, Review about Ginkgo biloba special extract EGb 761 (Ginkgo), Current Pharmaceutical Design, 10(3), 261-264 (2004). </p>
|
| 195 |
+
<p id="p-50" num="50">[Para 44] P.E. Gold et al., The lowdown on Ginkgo biloba, Scientific American, 288(4), 86-91 (2003).</p>
|
| 196 |
+
<p id="p-51" num="51">
|
| 197 |
+
<confidence value="8888">[Par</confidence>
|
| 198 |
+
a 45] M. G<confidence value="888888">rundma</confidence>
|
| 199 |
+
n & P. Del<confidence value="8">a</confidence>
|
| 200 |
+
ney, Antioxidant strategies for Alzheimer<confidence value="5">'</confidence>
|
| 201 |
+
s disease, Proceed<confidence value="8888">ings</confidence>
|
| 202 |
+
of the Nutrition Society, 61(2), 191-202 (2002). </p>
|
| 203 |
+
<p id="p-52" num="52">[Para 46] M.J. Howes et al., Plants with traditional uses and activities, relevant to the management of Alzheimer's disease and other cognitive disorders, Phytotherapy Research, 17(1), 1- <part-num-ref name="management of Alzheimer's disease and other cognitive disorders, Phytotherapy Research, 17(1), 1-">
|
| 204 |
+
<confidence value="88">18</confidence>
|
| 205 |
+
</part-num-ref>
|
| 206 |
+
(2003). </p>
|
| 207 |
+
<p id="p-53" num="53">[Para 47] <confidence value="5">S</confidence>
|
| 208 |
+
. Kanowski & R. Hoerr, Ginkgo biloba extract EGb 761 in dementia: intent-to-treat analyses of a 24-week, multi-center, double-blind, placebo-controlled, randomized trial, Pharmacopsychiatry, 36(6), 297-303 (2003). </p>
|
| 209 |
+
<p id="p-54" num="54">[Para 48] Kawada et al., Rapid Communication, Proceedings of the Society for Experimental Biology and Medicine, <part-num-ref name="Society for Experimental Biology and Medicine,">188,</part-num-ref>
|
| 210 |
+
229-233 (1988). </p>
|
| 211 |
+
<p id="p-55" num="55">[Para 49] B. Kiss B & E. Karpati, Mechanism of action of vinpocetine [in Hungarian<confidence value="5">;</confidence>
|
| 212 |
+
English abstract], Acta Pharm Hung, 66:213-214 (1996). </p>
|
| 213 |
+
<boundary-data type="header">Page 8 of 25</boundary-data>
|
| 214 |
+
<p id="p-56" num="56">
|
| 215 |
+
<page-break num="9"/>
|
| 216 |
+
[Para 50] D.S. Knopman, Part VI: primary drug therapies for Alzheimer's disease- noncholinominetic drugs- alternative medicines, Disease-a-Month: DM, 46(11), 745-760 (2000). </p>
|
| 217 |
+
<p id="p-57" num="57">[Para 51] S. Lalitha & R. Selvam, Prevention of H2<confidence value="4">0</confidence>
|
| 218 |
+
s-induced red blood cell lipid peroxidation by aqueous extracted turmeric, Asia Pacific Journal of Clin. Nutr., 8(2), 113-114 (1999). </p>
|
| 219 |
+
<p id="p-58" num="58">[Para 52] P.L. Le Bars et al., Influence of the severity of cognitive impairment on the effect of the Ginkgo biloba extract EGb <part-num-ref name="Ginkgo biloba extract EGb">761</part-num-ref>
|
| 220 |
+
in Alzheimer's disease, Neuropsychobiology, 45(1), 19-26 (2002). </p>
|
| 221 |
+
<p id="p-59" num="59">[Para 53] M. Majeed et al., Curcuminoids, NutriScience Publishers (1995).</p>
|
| 222 |
+
<p id="p-60" num="60">[Para 54] J.E. Mintzer & P. Kershaw, The efficacy of galantamine in the treatment of Alzheimer's disease: comparison of patients previously treated with acetylcholinesterase inhibitors to patients with no prior exposure, International Journal of Geriatric Psychiatry, vol. <part-num-ref name="treatment of Alzheimer's disease: comparison of patients previously treated with acetylcholinesterase inhibitors to patients with no prior exposure, International Journal of Geriatric Psychiatry, vol.">18,</part-num-ref>
|
| 223 |
+
292-297 (2003). </p>
|
| 224 |
+
<p id="p-61" num="61">[Para 55] M. Miyazaki, The effect of a cerebral vasodilator, vinpocetine, on cerebral vascular resistance evaluated by the Doppler ultrasonic technique in patients with cerebrovascular diseases, Angiology, 46:53-58 (1995).</p>
|
| 225 |
+
<p id="p-62" num="62">[Para 56] C. Nirmala et al., Curcumin treatment modulates collagen metabolism in isoproterenol induced myocardial necrosis in rats, Molecular and Cellular Biochemistry, vol. 197, 31-37 (1999).</p>
|
| 226 |
+
<p id="p-63" num="63">[Para 57] B.S. Oken et al., The efficacy of Ginkgo biloba on cognitive function in Alzheimer disease, Archives of Neurology, 55(11), 1409-1415 (1998).</p>
|
| 227 |
+
<p id="p-64" num="64">
|
| 228 |
+
<confidence value="888">[Pa</confidence>
|
| 229 |
+
ra 58] <confidence value="5">J</confidence>
|
| 230 |
+
. Olin & L. Schneider, Galantamine for Alzheimer<confidence value="5">'</confidence>
|
| 231 |
+
s disease (Cochrane review), In T<confidence value="88">he</confidence>
|
| 232 |
+
Cochrane Library, Issue <part-num-ref name="Cochrane Library, Issue">2</part-num-ref>
|
| 233 |
+
(2001). </p>
|
| 234 |
+
<p id="p-65" num="65">[Para 59] B.R. Ott & N.<confidence value="5">J</confidence>
|
| 235 |
+
. Owens, Complement<confidence value="56">ar</confidence>
|
| 236 |
+
y and alternative medicines for Alzheimer<confidence value="68">'s</confidence>
|
| 237 |
+
disease, Journal of Geriatric Psychiatry and Neurology, 11(4), 163-173 (1998). </p>
|
| 238 |
+
<p id="p-66" num="66">[Para 60] PDR FOR HERBAL MEDICINE<confidence value="5">S</confidence>
|
| 239 |
+
, Medical Economics Company, (2000). </p>
|
| 240 |
+
<boundary-data type="header">Page 9 of 25</boundary-data>
|
| 241 |
+
<p id="p-67" num="67">
|
| 242 |
+
<page-break num="10"/>
|
| 243 |
+
[Para 61] E.J. Park et al., Protective effect of curcumin in rat liver injury induced by carbon tetrach<confidence value="7">l</confidence>
|
| 244 |
+
oride, Journal of Pharm. Pharmacol., vol. 52, 437-440 (2000). </p>
|
| 245 |
+
<p id="p-68" num="68">
|
| 246 |
+
<confidence value="8">[</confidence>
|
| 247 |
+
Para 62] E.K. Perry et al., Medic<confidence value="5886">inal</confidence>
|
| 248 |
+
plants andAlzheimer<confidence value="5">'</confidence>
|
| 249 |
+
s disease: from ethnobotany to phytotherapy, Journal of Pharmacy and Pharmacology, 51(5), 527-534 (1999). </p>
|
| 250 |
+
<p id="p-69" num="69">[Para 63] D. Pratico & N. Delanty, Oxidative injury in diseases of the central nervous system:</p>
|
| 251 |
+
<p id="p-70" num="70">focus on Alzheimer's disease, American Journal of Medicine, 109(7), 577-585 (2000).</p>
|
| 252 |
+
<p id="p-71" num="71">[Para 64] V. Rajakrishnan et al., Neuroprotective role of curcumin from Curcuma longa on ethanol-induced brain damage, Phytotherapy Research, vol. 13, 571-574 (1999).</p>
|
| 253 |
+
<p id="p-72" num="72">[Para 65] A. Ramirez-Bosca et al., Antioxidant curcuma extracts decrease the blood peroxide levels of human subjects, Age, vol. <part-num-ref name="blood peroxide levels of human subjects, Age, vol.">18,</part-num-ref>
|
| 254 |
+
167-169 (1995). </p>
|
| 255 |
+
<p id="p-73" num="73">[Para 66] R.S. Ramsewak et al., Cytotoxicity, antioxidant, and anti-inflammatory activities of Curcumins I-I<confidence value="66">II</confidence>
|
| 256 |
+
from Curcuma longa, Phytomedicine, 7(4), 303-308 (2000). </p>
|
| 257 |
+
<p id="p-74" num="74">
|
| 258 |
+
<confidence value="888">[Pa</confidence>
|
| 259 |
+
ra 67] N.S. Rao & M.N.A. Rao, Free radical scavenging activity of curcuminoids, Arzne<confidence value="8">i</confidence>
|
| 260 |
+
m.- Forsch./Drug Res., 46(2), 169-171 (1996). </p>
|
| 261 |
+
<p id="p-75" num="75">
|
| 262 |
+
<confidence value="8">[</confidence>
|
| 263 |
+
Para 68] N.S. Rao & M.N.A. Rao, Nitric oxide scavenging by curcuminoids, <confidence value="66">Jo</confidence>
|
| 264 |
+
urnal of Pharm. </p>
|
| 265 |
+
<p id="p-76" num="76">Pharmacol., vol. 49, 105-107 (1997).</p>
|
| 266 |
+
<p id="p-77" num="77">[Para 69] M.A. Raskind et al., Galantamine in Alzheimer's disease: a 6-month, randomized, placebo-controlled trial with a 6-month extension, Neurology, vol. <part-num-ref name="6-month extension, Neurology, vol.">54,</part-num-ref>
|
| 267 |
+
2261-2268 (2000). </p>
|
| 268 |
+
<p id="p-78" num="78">
|
| 269 |
+
<confidence value="888">[Pa</confidence>
|
| 270 |
+
ra 70] R.R. Satos<confidence value="88">ka</confidence>
|
| 271 |
+
r et al., Evaluation of anti-in<confidence value="66">fl</confidence>
|
| 272 |
+
ammatory property <confidence value="88">of</confidence>
|
| 273 |
+
curcumin (diferoyl methane) in patients with postoperative inflammation, Internat<confidence value="88">io</confidence>
|
| 274 |
+
nal <confidence value="6688">Jour</confidence>
|
| 275 |
+
nal of Cl<confidence value="88">in</confidence>
|
| 276 |
+
ical P<confidence value="888">har</confidence>
|
| 277 |
+
macol<confidence value="8888">ogy,</confidence>
|
| 278 |
+
Therapy and Toxicology, 24(12), 651-654 (1986). </p>
|
| 279 |
+
<p id="p-79" num="79">[Para 71] G. Shoba et al., Influence of piperine on the pharmacokinetics of curcumin in animals and human volunteers, Planta Medica, 64(4), 353-356 (1998).</p>
|
| 280 |
+
<boundary-data type="header">Page 10 of 25</boundary-data>
|
| 281 |
+
<p id="p-80" num="80">
|
| 282 |
+
<page-break num="11"/>
|
| 283 |
+
<confidence value="888">[Pa</confidence>
|
| 284 |
+
ra 7<confidence value="86">2]</confidence>
|
| 285 |
+
A.A. Skol <confidence value="8">n</confidence>
|
| 286 |
+
ick, Old Chinese herbal medicine used for fever yields possible new Alzheimer disease therapy<confidence value="5">,</confidence>
|
| 287 |
+
<confidence value="6">J</confidence>
|
| 288 |
+
AMA: Journal of the American Medical Association, 277(10), <part-num-ref name="American Medical Association, 277(10),">776</part-num-ref>
|
| 289 |
+
(1997). </p>
|
| 290 |
+
<p id="p-81" num="81">
|
| 291 |
+
<confidence value="888">[Pa</confidence>
|
| 292 |
+
ra 7<confidence value="88">3]</confidence>
|
| 293 |
+
<confidence value="28">3.</confidence>
|
| 294 |
+
M. Snow, Herbal Monograph: Curcuma longa L. (Zingiberaceae), The Protocol <confidence value="6688">Jour</confidence>
|
| 295 |
+
nal of Botanical Medicine, Autumn issue, 43-46 (1995). </p>
|
| 296 |
+
<p id="p-82" num="82">
|
| 297 |
+
<confidence value="8888">[Par</confidence>
|
| 298 |
+
a 74] P.R. Solomon et al., Ginkgo for memory enhancement: a randomized controlled trial, <confidence value="5">J</confidence>
|
| 299 |
+
AMA: Journal of the American Medical Association, 288(7), 835-840 (2002). </p>
|
| 300 |
+
<p id="p-83" num="83">[Para 75] R.C. Srimal, Turmeric: a brief review of its medicinal properties, Fitoterapia, 68(6), 483- <part-num-ref name="brief review of its medicinal properties, Fitoterapia, 68(6), 483-">493</part-num-ref>
|
| 301 |
+
(1997). </p>
|
| 302 |
+
<p id="p-84" num="84">[Para 76] R.W. Stackman et al., Prevention of age-related spatial memory deficits in a transgenic mouse model of Alzheimer's disease by chronic Ginkgo biloba treatment, Experimental Neurology, 184(1), 510-520 (2003).</p>
|
| 303 |
+
<p id="p-85" num="85">[Para 77] SUBBARAM, Specification for Indian Patent No. 1232/DEL/89.</p>
|
| 304 |
+
<p id="p-86" num="86">[Para 78] M. Subramanian et al., Diminution of singlet oxygen-induced DNA damage by curcumin and related antioxidants, Mutation Research, vol. 311, 249-255 (1994).</p>
|
| 305 |
+
<p id="p-87" num="87">[Para 79] P.N. Tariot et al., A 5-month, randomized, placebo-controlled trial of galantamine in Alzheimer's disease, Neurology, vol. <part-num-ref name="5-month, randomized, placebo-controlled trial of galantamine in Alzheimer's disease, Neurology, vol.">54,</part-num-ref>
|
| 306 |
+
2269-2276 (2000). </p>
|
| 307 |
+
<p id="p-88" num="88">[Para 80] M. van Dongen et al., Ginkgo for elderly people with dementia and age-associated memory impairment: a randomized clinical trial, Journal of Clinical Epidemiology, 56(4), 367-376 (2003).</p>
|
| 308 |
+
<p id="p-89" num="89">[Para 81] G.K. Wilcock et al., Efficacy and safety of galantamine in patients with mild to moderate Alzheimer's disease: multicentre randomised controlled trial, BMJ, 321(7274), 1445-1449 (2000).</p>
|
| 309 |
+
<boundary-data type="header">Page 11 of 25</boundary-data>
|
| 310 |
+
<p id="p-90" num="90">
|
| 311 |
+
<page-break num="12"/>
|
| 312 |
+
[Para 82] A. Zangara, The psychopharmacology of huperzine A: an alkaloid with cognitive enhancing and neuroprotective properties of interest in the treatment of Alzheimer's disease, Pharmacology, Biochemistry and Behavior, 75(3), 675-686 (2003). </p>
|
| 313 |
+
<p id="p-91" num="91">[Para 83] Zutshi et al., Influence of Piperine on Rifampicin Blood Levels In Patients Of Pulmonary Tuberculosis, JAP<confidence value="5">1</confidence>
|
| 314 |
+
, 33(3), 223-224 (1985). </p>
|
| 315 |
+
<heading id="h-3">SUMMARY OF THE INVENTION</heading>
|
| 316 |
+
<p id="p-92" num="92">[Para 84] The applicant's invention is for a composition and method for using said composition as a dietary supplement to retard the onset of the symptoms of Alzheimer's disease in humans. The composition comprises a mixture of curcumin, piperine, oleic acid, oleanolic acid, ursolic acid, galantamine, huperzine A, choline, and vitamin B5. The composition may also include gamma tocopherol, sesame lignans preferably in the form of sesamolin, vinpocetine, and/or pyritinol.</p>
|
| 317 |
+
<p id="p-93" num="93">Said composition can be produced as a dietary supplement for human ingestion in any orally administrable form including, but not limited to, a caplet, capsule, tablet, jelly, serum, or drink.</p>
|
| 318 |
+
<p id="p-94" num="94">Piperine, a botanical pepper extract derived from the fruits of P<confidence value="66">ip</confidence>
|
| 319 |
+
er <confidence value="222222">n/grum</confidence>
|
| 320 |
+
(black pepper) and P<confidence value="6688">iper</confidence>
|
| 321 |
+
<confidence value="2">/</confidence>
|
| 322 |
+
ongum (long pepper), increases the bioavailability of curcumin in humans by increasing the absorption of curcumin from the gastrointestinal tract into the bloodstream. </p>
|
| 323 |
+
<p id="p-95" num="95">[Para 85] The composition contains each ingredient in the following ranges: 2.0-100.0 mg curcumin, 2.0-20.0 mg piperine, 20.0-100.0 mg oleic acid, 20.0-100.0 mg oleanolic acid, 20.0-100.0 mg ursolic acid, 5.0-200.0 mg galantamine, 25.0-250.0 pg huperzine A, 5.0-150.0 mg choline, and 20.0-200.00 mg vitamin B5. Gamma tocopherol, an optional ingredient, is included in the range of 150.0-250.0 mg, and sesamolin, another optional ingredient, is included in the composition at 10.0- 40.0 mg. If desired, vinpocetine, which is an optional ingredient of the mixture, can be included at 5.0-150.0 mg, and pyritinol, also an optional ingredient in the composition, may be included in an amount ranging from 20.0-200.0 mg.</p>
|
| 324 |
+
<p id="p-96" num="96">[Para 86] An object of this invention is to provide a composition, ingestible as a dietary supplement, for delaying the onset and progression of symptoms of Alzheimer's disease in humans.</p>
|
| 325 |
+
<p id="p-97" num="97">[Para 87] Another object of this invention is to provide a composition for retarding the onset and progression of symptoms of Alzheimer's disease in humans that contains curcumin.</p>
|
| 326 |
+
<boundary-data type="header">Page 12 of 25</boundary-data>
|
| 327 |
+
<p id="p-98" num="98">
|
| 328 |
+
<page-break num="13"/>
|
| 329 |
+
[Para 88] Still another object of this invention is to increase the bioavailability of curcumin and other nutrients ingested by including piperine in a composition for retarding the onset and progression of symptoms of Alzheimer's disease in humans. </p>
|
| 330 |
+
<p id="p-99" num="99">[Para 89] Yet another object of this invention is to provide an additional source of choline to the human body for use in forming acetylcholine, thereby enhancing the functionality of nerves in the brain, which use acetylcholine for neural transmissions.</p>
|
| 331 |
+
<p id="p-100" num="100">[Para 90] A further object of this invention is to provide a composition for retarding the onset and progression of symptoms of Alzheimer's disease in humans that will prevent the aggregation of and dissolve <confidence value="2">p</confidence>
|
| 332 |
+
-amyloid protein fragments in the brain. </p>
|
| 333 |
+
<p id="p-101" num="101">[Para 91] Another object of this invention is to provide a method for retarding the onset and progression of the symptoms of Alzheimer's disease in humans using the composition described herein as an ingestible dietary supplement taken orally in a beneficial regimen to be clinically determined.</p>
|
| 334 |
+
<p id="p-102" num="102">[Para 92] In accordance with these and other objects which will become apparent hereinafter, the instant invention will now be described with particular reference to the accompanying drawings.</p>
|
| 335 |
+
<heading id="h-4">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
|
| 336 |
+
<p id="p-103" num="103">[Para 93] Figure 1 shows a table of the pharmacokinetic parameters (mean <confidence value="2">i</confidence>
|
| 337 |
+
SEM) of oral curcumin 2.0 g/kg alone and in combination with a source of piperine, Bioperine<confidence value="5">®</confidence>
|
| 338 |
+
<part-num-ref name="source of piperine, Bioperine®">20</part-num-ref>
|
| 339 |
+
mg/kg, in rats (n= 6). </p>
|
| 340 |
+
<p id="p-104" num="104">[Para 94] Figure 2 shows a graphical representation of the effect of piperine (Bioperine<confidence value="68">®)</confidence>
|
| 341 |
+
on serum concentrations of curcumin in rats. </p>
|
| 342 |
+
<p id="p-105" num="105">[Para 95] Figure 3 shows a table of the pharmacokinetic parameters (mean + SEM) of oral curcumin 2.0 g alone and in combination with a source of piperine, Bioperine<confidence value="5">®</confidence>
|
| 343 |
+
<part-num-ref name="source of piperine, Bioperine®">20</part-num-ref>
|
| 344 |
+
mg, in normal healthy volunteers (n=8). </p>
|
| 345 |
+
<p id="p-106" num="106">[Para 96] Figure 4 shows a graphical representation of the effect of piperine (Bioperine<confidence value="68">®)</confidence>
|
| 346 |
+
on serum concentrations in normal healthy human volunteers. </p>
|
| 347 |
+
<heading id="h-5">DETAILED DESCRIPTION</heading>
|
| 348 |
+
<boundary-data type="header">Page 13 of 25</boundary-data>
|
| 349 |
+
<p id="p-107" num="107">
|
| 350 |
+
<page-break num="14"/>
|
| 351 |
+
[Para 97] The present invention relates to a composition for use as an orally-administered dietary supplement to delay the onset and symptoms of Alzheimer's disease in humans. Said composition comprises a mixture of curcumin for delaying the onset and progress of Alzheimer's disease symptomology in humans and piperine, a botanical pepper extract, for increasing the bioavailablity of curcumin in the bloodstream when said curcumin is orally administered to a patient. </p>
|
| 352 |
+
<p id="p-108" num="108">Preferably, the composition also includes oleic acid, oleanolic acid, ursolic acid, galantamine, huperzine A, choline, and vitamin B5. The composition may further include vinpocetine, pyritinol, gamma tocopherol, and/or sesame lignans, preferably in the form of sesamolin. Said composition can be produced as a dietary supplement for human ingestion in any orally administrable form including, but not limited to, a caplet, capsule, tablet, jelly, serum, or drink. Piperine, a botanical pepper extract, is derived from the fruits of plants in the Piperaceae family, and preferably from the fruits of P<confidence value="5588">iper</confidence>
|
| 353 |
+
<confidence value="222222">n/grum</confidence>
|
| 354 |
+
and P<confidence value="5588">iper</confidence>
|
| 355 |
+
<confidence value="2">/</confidence>
|
| 356 |
+
ongum<confidence value="6">.</confidence>
|
| 357 |
+
Most preferably, the piperine used in the composition is derived from the fruits of P<confidence value="66">ip</confidence>
|
| 358 |
+
er <confidence value="222222">n/grum</confidence>
|
| 359 |
+
, i.e. black pepper. The purpose of including piperine is to increase the bioavailability of curcumin and other substances in humans by increasing the absorption of curcumin and other nutrients from the gastrointestinal tract. </p>
|
| 360 |
+
<p id="p-109" num="109">[Para 98] Example 1: Bioavailability Studies: Curcumin and Piperine [Para 99] In this study, the bioavailability of curcumin was evaluated, with said curcumin being orally administered to animals, and subsequently, to normal healthy human volunteers along with a source of piperine (Bioperine<confidence value="4">®</confidence>
|
| 361 |
+
was the source of piperine used in this study). When taken orally only traces of curcumin appeared in the blood, whereas most of the oral dose was excreted though the feces. In both the preclinical studies performed on rats and in the clinical studies using normal healthy volunteers, piperine enhanced the bioavailability of curcumin as demonstrated in Figures <part-num-ref name="bioavailability of curcumin as demonstrated in Figures">1</part-num-ref>
|
| 362 |
+
through <part-num-ref name="through">4.</part-num-ref>
|
| 363 |
+
</p>
|
| 364 |
+
<p id="p-110" num="110">[Para 100] * <confidence value="6">*</confidence>
|
| 365 |
+
<confidence value="6">*</confidence>
|
| 366 |
+
[Para 101] Example 2: Proposed Clinical Trial of the Effectiveness of the Composition in Treating the Symptoms of Alzheimer's Disease [Para 102] To test the effectiveness of the composition in delaying the onset of the symptoms of Alzheimer's disease, a dietary supplement preparation is administered orally to patients who have manifested the symptoms of an early stage of Alzheimer's disease, as diagnosed by their physician and confirmed by an independent board-certified neurologist. Two weeks before the clinical trial, the patients undergo appropriate psychoneurological tests such as the Mini Mental Status Exam (MMSE), the Alzheimer Disease Assessment Scale (ADAS), the Boston Naming Test (BNT), and the Token Test (TT). Neuropsychological tests are repeated on Day <part-num-ref name="Token Test (TT). Neuropsychological tests are repeated on Day">0,</part-num-ref>
|
| 367 |
+
at <part-num-ref name="Token Test (TT). Neuropsychological tests are repeated on Day 0, at">6</part-num-ref>
|
| 368 |
+
weeks, and at <part-num-ref name="weeks, and at">3</part-num-ref>
|
| 369 |
+
months <boundary-data type="header">Page 14 of 25</boundary-data>
|
| 370 |
+
<page-break num="15"/>
|
| 371 |
+
during the clinical trial. The tests are performed by neuropsychologists who are not aware of the patients' treatment regimen. </p>
|
| 372 |
+
<p id="p-111" num="111">[Para 103] In this double blind study, patients are randomly assigned to the test composition or placebo at the beginning of the study. The test composition and placebo are administered orally one or two times per day. The test patients are evaluated for a period of five years to determine the effectiveness of treatment using the composition as compared to the control group individuals given a placebo. Scores are statistically compared between the test composition and the placebo for each of the three observational periods. Without treatment, the natural course of Alzheimer's disease results in significant deterioration of a patient's test scores during the course of the clinical trial. A patient treated with the composition is considered improved if the patient's scores remain the same or improve during the course of the clinical trial.</p>
|
| 373 |
+
<p id="p-112" num="112">[Para 104] * <confidence value="6">*</confidence>
|
| 374 |
+
<confidence value="6">*</confidence>
|
| 375 |
+
[Para 105] The preferred composition contains each ingredient in the following ranges and preferred ranges: Curcumin is included at 2.0-100.0 mg, and preferably at 10.0-40.0 mg. Piperine is included at 2.0-20.0 mg, and preferably at 5.0-10.0 mg. Oleic acid is included in the composition between a range of 20.0-100.0 mg, and preferably in the amount of <part-num-ref name="amount of">40</part-num-ref>
|
| 376 |
+
mg. Oleanolic acid is included in the composition between a range of 20.0-100.0 mg, and preferably in the amount of <part-num-ref name="amount of">40</part-num-ref>
|
| 377 |
+
mg. Ursolic acid is included in the composition between a range of 20.0-100.0 mg, and preferably in the amount of <part-num-ref name="amount of">40</part-num-ref>
|
| 378 |
+
mg. Galantamine is included in an amount ranging from 5.0-200.0 mg, and preferably at 16.0-24.0 mg. Huperzine A is included in the mixture at 25.0-250.0 pg, and preferably at 50.0-100.0 pg. </p>
|
| 379 |
+
<p id="p-113" num="113">[Para 106] Choline is included in the composition at 5.0-150.0 mg, and preferably at 20.0- 50.0 mg. Vitamin B5, or pantothenic acid, is included at 20.0-200.00 mg, and preferably at 50.0- 100.00 mg. Gamma tocopherol, an optional ingredient, is included in the range of 150.0-250.0 mg, and preferably at 200.0 mg. Sesame lignans, preferably in the form of sesamolin and also an optional ingredient, is included in the composition at 10.0-40.0 mg, and preferably at 20.0 mg. If desired, vinpocetine, which is an optional ingredient of the mixture, is included at 5.0-150.0 mg, and preferably at 20.0-50.0 mg. Pyritinol, also an optional ingredient in the composition, may be included in an amount ranging from 20.0-200.0 mg, and preferably at 100.0 mg.</p>
|
| 380 |
+
<p id="p-114" num="114">[Para 107] This invention also relates to a method for delaying the onset of symptoms of Alzheimer's disease in humans using the above-described composition as an ingestible dietary supplement. Preferably, the dietary supplement containing the composition is taken once or twice daily by a user. In this method, said composition may be produced and ingested in any orally <boundary-data type="header">Page 15 of 25</boundary-data>
|
| 381 |
+
<page-break num="16"/>
|
| 382 |
+
administrable form including, but not limited to, a caplet, capsule, tablet, jelly, serum, or drink. The composition and method may also be used to delay the onset of symptoms of other neurodegenerative diseases, similar to Alzheimer's disease, that affect aging humans, including, but not limited to, Parkinson's disease. </p>
|
| 383 |
+
<p id="p-115" num="115">[Para 108] The instant invention has been shown and described herein in what is considered to be the most practical and preferred embodiment. The applicant recognizes, however, that departures may be made therefrom within the scope of the invention and that obvious modifications will occur to a person skilled in the art.</p>
|
| 384 |
+
<boundary-data type="header">Page 16 of 25</boundary-data>
|
| 385 |
+
</description>
|
| 386 |
+
</us-patent-application>
|
| 387 |
+
|
applicant/11127438.xml
ADDED
|
@@ -0,0 +1,16 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="UTF-8"?>
|
| 2 |
+
<pat:SpecificationDocument xmlns:pat="urn:us:gov:doc:uspto:patent" xmlns="urn:us:gov:doc:uspto:patent" xmlns:ent="urn:us:gov:doc:uspto:enterprise" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:tbl="http://www.oasis-open.org/tables/exchange/1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:com="http://www.wipo.int/standards/XMLSchema/Common/1" pat:instanceFileName="11127438.03-21-2014.HT78QC84PXXIFW2.SPEC.xml" pat:id="HT78QC84PXXIFW2" xsi:schemaLocation="urn:us:gov:doc:uspto:patent XMLSchema/V1_3/SpecificationDocument_1_0.xsd">
|
| 3 |
+
<pat:DocumentCode>SPEC</pat:DocumentCode><pat:DocumentHeaderDetails pat:id="ID-00001">
|
| 4 |
+
<pat:ApplicationHeaderDetails><pat:ApplicationNumber>11127438</pat:ApplicationNumber></pat:ApplicationHeaderDetails>
|
| 5 |
+
<pat:PageTotalQuantity>1</pat:PageTotalQuantity>
|
| 6 |
+
<pat:ParagraphTotalQuantity>2</pat:ParagraphTotalQuantity>
|
| 7 |
+
</pat:DocumentHeaderDetails>
|
| 8 |
+
<pat:MailRoomDate>2014-03-21</pat:MailRoomDate>
|
| 9 |
+
<pat:Specification pat:id="Specification">
|
| 10 |
+
<?PageStart number="1"?>
|
| 11 |
+
<pat:BoundaryData><pat:HeaderText>Application No.: 11/127,438 Docket No.: AXJ-1<pat:OCRConfidenceData pat:levelNumber="5">0</pat:OCRConfidenceData>2CPRCE2</pat:HeaderText></pat:BoundaryData>
|
| 12 |
+
<pat:Heading pat:id="h-1">AMENDMENTS TO THE SPECIFICATION</pat:Heading>
|
| 13 |
+
<pat:P pat:id="p-1" pat:pNumber="1">Please amend the specification to insert the following new paragraph immediately before the <pat:PartName pat:idref="PN-00001">paragraph starting at page </pat:PartName><pat:PartNumber pat:id="PN-00001">4</pat:PartNumber> <pat:PartName pat:idref="PN-00002">(line </pat:PartName><pat:PartNumber pat:id="PN-00002">11)</pat:PartNumber> (i.e., immediately before the paragraph that begins: "An additional active agent...").</pat:P>
|
| 14 |
+
<pat:P pat:id="p-2" pat:pNumber="2">Particularly useful anti-C5 antibodies are h5G<pat:OCRConfidenceData pat:levelNumber="45">L.</pat:OCRConfidenceData>1, h5G<pat:OCRConfidenceData pat:levelNumber="4">1</pat:OCRConfidenceData>.1-scFv and functional fragments of h5G1.1. Methods for the <pat:PartName pat:idref="PN-00003">preparation of h5G <pat:OCRConfidenceData pat:levelNumber="868">1.1</pat:OCRConfidenceData>, h5G1.1-scFv and functional fragments of h5G<pat:OCRConfidenceData pat:levelNumber="5">1</pat:OCRConfidenceData>.1 are described in U.S. Patent No. 6,355,245 and "Inhibition of Complement Activity by Humanized Anti-C<pat:OCRConfidenceData pat:levelNumber="5">5</pat:OCRConfidenceData> Antibody and Single Chain Fv", Thomas et al., Molecular Immunology, Vol. </pat:PartName><pat:PartNumber pat:id="PN-00003">33</pat:PartNumber>, <pat:PartName pat:idref="PN-00004">No. 17/18, pages 1389-1401, </pat:PartName><pat:PartNumber pat:id="PN-00004">1996</pat:PartNumber>, the disclosures of which are incorporated herein in their entirety by this reference.</pat:P>
|
| 15 |
+
<pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber="8">2</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData>
|
| 16 |
+
</pat:Specification></pat:SpecificationDocument>
|
applicant/11198904.xml
ADDED
|
@@ -0,0 +1,463 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>11198904</doc-number>
|
| 8 |
+
<date>2005-08-05</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<heading id="h-1">PATENT</heading>
|
| 14 |
+
<heading id="h-2">IN THE UNITED STATES PATENT AND TRADEMARK OFFICE</heading>
|
| 15 |
+
<heading id="h-3">ATTORNEY DOCKET NO.:</heading>
|
| 16 |
+
<p id="p-1" num="1">0305-003-003-000000 </p>
|
| 17 |
+
<heading id="h-4">TITLE:</heading>
|
| 18 |
+
<heading id="h-5">VOICE CONTROLLABLE INTERACTIVE COMMUNICATION DISPLAY</heading>
|
| 19 |
+
<heading id="h-6">SYSTEM AND METHOD</heading>
|
| 20 |
+
<heading id="h-7">INVENTORS:</heading>
|
| 21 |
+
<p id="p-2" num="2">Edward K.Y. Jung;</p>
|
| 22 |
+
<p id="p-3" num="3">Royce A. Levien;</p>
|
| 23 |
+
<p id="p-4" num="4">Robert W. Lord;</p>
|
| 24 |
+
<p id="p-5" num="5">Mark A. Malamud;</p>
|
| 25 |
+
<p id="p-6" num="6">John D. Rinaldo, Jr.</p>
|
| 26 |
+
<heading id="h-8">SUBMITTED BY:</heading>
|
| 27 |
+
<p id="p-7" num="7">Anderson & Jans<confidence value="5">s</confidence>
|
| 28 |
+
on, LLP 8304 Cliffsage Ave. </p>
|
| 29 |
+
<p id="p-8" num="8">Austin, Texas 78759 <part-num-ref name="">(512)</part-num-ref>
|
| 30 |
+
826-5598 - Telephone <part-num-ref name="826-5598 - Telephone">(512)</part-num-ref>
|
| 31 |
+
233-2447 - Facsimile CERTIFICATE OF EXPRESS MAILING UNDER <part-num-ref name="233-2447 - Facsimile CERTIFICATE OF EXPRESS MAILING UNDER">37</part-num-ref>
|
| 32 |
+
CFR <confidence value="5">§</confidence>
|
| 33 |
+
1.10 I hereby certify that this correspondence is being deposited with the United States Postal Service Express Mail Service under <part-num-ref name="United States Postal Service Express Mail Service under">37</part-num-ref>
|
| 34 |
+
CFR <confidence value="5">§</confidence>
|
| 35 |
+
1.10 addressed to: </p>
|
| 36 |
+
<p id="p-9" num="9">Mail Stop Provisional Patent Application, Commissioner for Patents, P.O.</p>
|
| 37 |
+
<p id="p-10" num="10">Box 1450, Alexandria, VA 22213-1450, on this the 5th day of August, <part-num-ref name="5th day of August,">2005</part-num-ref>
|
| 38 |
+
Express Mailing Number: EV 735926227 US Ma<confidence value="88">rg</confidence>
|
| 39 |
+
aret <confidence value="222">Klo</confidence>
|
| 40 |
+
<page-break num="2"/>
|
| 41 |
+
0305-003-003-000000 </p>
|
| 42 |
+
<heading id="h-9">VOICE CONTROLLABLE INTERACTIVE</heading>
|
| 43 |
+
<heading id="h-10">COMMUNICATION DISPLAY SYSTEM AND</heading>
|
| 44 |
+
<heading id="h-11">METHOD</heading>
|
| 45 |
+
<p id="p-11" num="11">
|
| 46 |
+
<confidence value="2222222222">Inventor(s</confidence>
|
| 47 |
+
): </p>
|
| 48 |
+
<p id="p-12" num="12">Edward K.Y. Jung;</p>
|
| 49 |
+
<p id="p-13" num="13">Royce A. Levien;</p>
|
| 50 |
+
<p id="p-14" num="14">Robert W. Lord;</p>
|
| 51 |
+
<p id="p-15" num="15">Mark A. Malamud;</p>
|
| 52 |
+
<p id="p-16" num="16">John D. Rinaldo, Jr.</p>
|
| 53 |
+
<p id="p-17" num="17">Technical Field [0001] The present application relates generally to voice-enabled interactive communication systems.</p>
|
| 54 |
+
<p id="p-18" num="18">Summary [0002] In one aspect, a method for a voice-capable system includes but is not limited to receiving a vocal input to the voice-capable system; creating a first speech output version of the vocal input; receiving one or more instructions referential to the first speech output version of the vocal input, and creating a second speech output version of the vocal input representational of the first speech output version of the vocal input manipulated responsive to the one or more instructions. In addition to the foregoing, other method aspects are described in the claims, drawings, and text forming a part of the present application.</p>
|
| 55 |
+
<p id="p-19" num="19">
|
| 56 |
+
<confidence value="2">[</confidence>
|
| 57 |
+
0003] In another aspect, a voice-capable user interface is provided, the voice-capable user interface configured to manipulate a first speech output version of a vocal input. The voice-capable user interface includes a set of editing tools capable of interacting with the first speech output version of the vocal input, the set of tools including one or more of a forwarding tool configured to forward to an identified location in the first speech output version of the vocal input, a reverse tool configured to reverse to an identified location in the first speech output version of the vocal input, an undo tool configured to reverse a prior <boundary-data type="header">
|
| 58 |
+
<confidence value="888">-1-</confidence>
|
| 59 |
+
</boundary-data>
|
| 60 |
+
<page-break num="3"/>
|
| 61 |
+
0305-003-003-000000 action performed, a marking tool configured to mark a point in the first speech output version of the vocal input, and an expansion/contraction tool configured to expand and/or contract a predetermined length of the first speech output version of the vocal input; and a confirmation tool configured to produce a second speech output version of the vocal input representational of the first speech output version of the vocal input manipulated responsive to use of one or more tools of the set of editing tools. <confidence value="5">I</confidence>
|
| 62 |
+
n addition to the foregoing, other voice-capable user interface aspects are described in the claims, drawings, and text forming a part of the present application. </p>
|
| 63 |
+
<p id="p-20" num="20">[0004] In another aspect, a computer program product for a voice-capable system can include a signal bearing medium bearing one or more instructions including, but not limited to one or more instructions for receiving a vocal input to the voice-capable system;</p>
|
| 64 |
+
<p id="p-21" num="21">one or more instructions for receiving one or more instructions referential to the first speech output version of the vocal input; and one or more instructions for creating a second speech output version of the vocal input representational of the first speech output version of the vocal input manipulated responsive to the one or more instructions. In addition to the foregoing, other computer program product aspects are described in the claims, drawings, and text forming a part of the present application.</p>
|
| 65 |
+
<p id="p-22" num="22">[0005] In one or more various aspects, related systems include but are not limited to circuitry and/or programming for effecting the herein-referenced method aspects; the circuitry and/or programming can be virtually any combination of hardware, software, and/or firmware configured to effect the herein-referenced method aspects depending upon the design choices of the system designer. In addition to the foregoing, other system aspects are described in the claims, drawings, and text forming a part of the present application.</p>
|
| 66 |
+
<p id="p-23" num="23">[0006] In one aspect, a voice-capable communication device includes but is not limited to a processor, an an audio input and/or output circuitry coupled to the processor, a memory coupled to the processor, an interface module coupled to the processor, the interface module configured to (a) receive a vocal input to the voice-capable communication device, (b) receive one or more instructions referential to a first speech output version of the vocal <boundary-data type="header">
|
| 67 |
+
<confidence value="888">-2-</confidence>
|
| 68 |
+
</boundary-data>
|
| 69 |
+
<page-break num="4"/>
|
| 70 |
+
0305-003-003-000000 input; and (c) create a second speech output version of the vocal input representational of the first speech output version of the vocal input manipulated responsive to the one or more instructions. In addition to the foregoing, other communication device aspects are described in the claims, drawings, and text forming a part of the present application. </p>
|
| 71 |
+
<p id="p-24" num="24">[0007] In addition to the foregoing, various other method, system, and/or computer program product aspects are set forth and described in the text (e.g., claims and/or detailed description) and/or drawings of the present application.</p>
|
| 72 |
+
<p id="p-25" num="25">[0008] The foregoing is a summary and thus contains, by necessity, simplifications, generalizations and omissions of detail; consequently, those skilled in the art will appreciate that the summary is illustrative only and is NOT intended to be in any way limiting. Other aspects, features, and advantages of the devices and/or processes and/or other subject described herein will become apparent in the text set forth herein.</p>
|
| 73 |
+
<boundary-data type="header">
|
| 74 |
+
<confidence value="888">-3-</confidence>
|
| 75 |
+
</boundary-data>
|
| 76 |
+
<p id="p-26" num="26">
|
| 77 |
+
<page-break num="5"/>
|
| 78 |
+
0305-003-003-000000 Brief Description of the Drawings <confidence value="5">[</confidence>
|
| 79 |
+
0009<confidence value="5">]</confidence>
|
| 80 |
+
<confidence value="8">A</confidence>
|
| 81 |
+
better understanding of the subject matter of the application can be obtained when the following detailed description of the disclosed embodiments is considered in conjunction with the following drawings, in which: </p>
|
| 82 |
+
<p id="p-27" num="27">[0010] Figure 1 is a block diagram of an exemplary computer architecture that supports the claimed subject matter of the present application;</p>
|
| 83 |
+
<p id="p-28" num="28">
|
| 84 |
+
<confidence value="5">[</confidence>
|
| 85 |
+
0011] Figure 2 is a block diagram of a network environment that supports the claimed subject matter of the present application; </p>
|
| 86 |
+
<p id="p-29" num="29">[0012<confidence value="5">]</confidence>
|
| 87 |
+
Figure 3 is a block diagram of a communication device appropriate for embodiments of the subject matter of the present application; </p>
|
| 88 |
+
<p id="p-30" num="30">[0013] Figures 4A, 4B and 4C illustrate a flow diagram of a method in accordance with an embodiment of the subject matter of the present application; and [0014] Figure 5 illustrates an interface module in accordance with an embodiment of the subject matter of the present application.</p>
|
| 89 |
+
<p id="p-31" num="31">[0015] Figure 6 illustrates a voice-capable communication device in accordance with an embodiment of the subject mater of the present application.</p>
|
| 90 |
+
<p id="p-32" num="32">[0016] The use of the same symbols in different drawings typically indicates similar or identical items.</p>
|
| 91 |
+
<boundary-data type="header">
|
| 92 |
+
<confidence value="888">-4-</confidence>
|
| 93 |
+
</boundary-data>
|
| 94 |
+
<p id="p-33" num="33">
|
| 95 |
+
<page-break num="6"/>
|
| 96 |
+
Detailed Description of the Drawings [0017] In the description that follows, the subject matter of the application will be described with reference to acts and symbolic representations of operations that are performed by one or more computers, unless indicated otherwise. As such, it will be understood that such acts and operations, which are at times referred to as being computer- executed, include the manipulation by the processing unit of the computer of electrical signals representing data in a structured form. This manipulation transforms the data or maintains it at locations in the memory system of the computer which reconfigures or otherwise alters the operation of the computer in a manner well understood by those skilled in the art. The data structures where data is maintained are physical locations of the memory that have particular properties defined by the format of the data. However, although the subject matter of the application is being described in the foregoing context, it is not meant to be limiting as those of skill in the art will appreciate that some of the acts and operations described hereinafter can also be implemented in hardware, software, and/or firmware and/or some combination thereof. </p>
|
| 97 |
+
<p id="p-34" num="34">[0018] According to William <confidence value="5">C</confidence>
|
| 98 |
+
rossman, Founder/Director of CompSpeak 2050 Institute for the Study of Talking Computers and Oral Cultures, V<confidence value="66">IV</confidence>
|
| 99 |
+
Os, (e.g., voice-in<confidence value="5">/</confidence>
|
| 100 |
+
voice-out computers that may operate using visual displays) may make written language obsolete. </p>
|
| 101 |
+
<p id="p-35" num="35">
|
| 102 |
+
<confidence value="868">VIV</confidence>
|
| 103 |
+
Os potentially can perform the functions of written language without requiring people to learn to read and write and, therefore, enable illiterate people, using V<confidence value="66">IV</confidence>
|
| 104 |
+
Os, to access the stored information. </p>
|
| 105 |
+
<p id="p-36" num="36">[0019] Opening the doors for potentially billions of people to electronically-stored data presents a host of issues related to voice-enabled interaction. More particularly, according to <confidence value="22222222">Crossman</confidence>
|
| 106 |
+
, billions of illiterate people will be able to access data previously available only to the computer literate. The increase in the number of people with access to the Internet will increase the need for systems that provide voice capabilities for voice mail and the like. Rather than a user relying on a keyboard, interactions with display text (e.g., on the visual display of your office phone, or on the visual display of your mobile device) requires tools for voice email systems (or other voice interactive systems) so that people do <boundary-data type="header">
|
| 107 |
+
<confidence value="888">-5-</confidence>
|
| 108 |
+
</boundary-data>
|
| 109 |
+
<page-break num="7"/>
|
| 110 |
+
not have to rerecord a message every time they are unhappy with just a small part of what they said. </p>
|
| 111 |
+
<p id="p-37" num="37">[0020] To address the needs of a VIVO system, embodiments herein present voice- cabable systems and tools to enable a user to interact with voice transmissions to create transmittable oral outputs efficiently and without having to rerecord transmissions.</p>
|
| 112 |
+
<p id="p-38" num="38">
|
| 113 |
+
<confidence value="5">[</confidence>
|
| 114 |
+
0021] With reference to Figure 1, depicted is an exemplary computing system for implementing embodiments. Figure 1 includes a computer <part-num-ref name="computer">100,</part-num-ref>
|
| 115 |
+
which could be a VIVO- capable computer, including a processor <part-num-ref name="processor">110,</part-num-ref>
|
| 116 |
+
memory <part-num-ref name="processor 110, memory">120</part-num-ref>
|
| 117 |
+
and one or more drives <part-num-ref name="and one or more drives">130.</part-num-ref>
|
| 118 |
+
</p>
|
| 119 |
+
<p id="p-39" num="39">The drives 130 and their associated computer storage media, provide storage of computer readable instructions, data structures, program modules and other data for the computer <part-num-ref name="computer">100.</part-num-ref>
|
| 120 |
+
Drives <part-num-ref name="computer 100. Drives">130</part-num-ref>
|
| 121 |
+
can include an operating system <part-num-ref name="operating system">140,</part-num-ref>
|
| 122 |
+
application programs <part-num-ref name="operating system 140, application programs">150,</part-num-ref>
|
| 123 |
+
program modules <part-num-ref name="operating system 140, application programs 150, program modules">160,</part-num-ref>
|
| 124 |
+
such as user interface module <part-num-ref name="operating system 140, application programs 150, program modules 160, such as user interface module">170</part-num-ref>
|
| 125 |
+
and program data <part-num-ref name="and program data">180.</part-num-ref>
|
| 126 |
+
Computer <part-num-ref name="and program data 180. Computer">100</part-num-ref>
|
| 127 |
+
further includes user input devices <part-num-ref name="further includes user input devices">190</part-num-ref>
|
| 128 |
+
through which a user may enter commands and data. Input devices can include an electronic digitizer, a microphone, a keyboard and pointing device, commonly referred to as a mouse, trackball or touch pad. Other input devices may include a joystick, game pad, satellite dish, scanner, or the like. In one or more embodiments, user input devices <part-num-ref name="like. In one or more embodiments, user input devices">190</part-num-ref>
|
| 129 |
+
are VIVO enabling devices, enabling a user to provide voice activated responses and/or questions. </p>
|
| 130 |
+
<p id="p-40" num="40">[0022] These and other input devices can be connected to processor 110 through a user input interface that is coupled to a system bus, but may be connected by other interface and bus structures, such as a parallel port, game port or a universal serial bus (USB).</p>
|
| 131 |
+
<p id="p-41" num="41">Computers such as computer 100 may also include other peripheral output devices such as speakers, which may be connected through an output peripheral interface <part-num-ref name="output peripheral interface">195</part-num-ref>
|
| 132 |
+
or the like. </p>
|
| 133 |
+
<p id="p-42" num="42">More particularly, output devices can include VIVO enabling devices capable of providing voice output in response to voice input.</p>
|
| 134 |
+
<p id="p-43" num="43">[0023] Computer 100 may operate in a networked environment using logical connections to one or more remote computers, such as a remote computer accesible by a Wide Area Network (WAN). The remote computer may be a personal computer, a server, a router, a network PC, a peer device or other common network node, and can include many or all of the elements described above relative to computer <part-num-ref name="elements described above relative to computer">100.</part-num-ref>
|
| 135 |
+
Networking environments are <boundary-data type="header">-6-</boundary-data>
|
| 136 |
+
<page-break num="8"/>
|
| 137 |
+
commonplace in offices, enterprise-wide computer networks, intranets and the Internet. </p>
|
| 138 |
+
<p id="p-44" num="44">For example, in the subject matter of the present application, computer <part-num-ref name="present application, computer">100</part-num-ref>
|
| 139 |
+
may comprise the source machine from which data is being migrated, and the remote computer may comprise the destination machine. Note however that source and destination machines need not be connected by a network or any other means, but instead, data may be migrated via any media capable of being written by the source platform and read by the destination platform or platforms. When used in a LAN or WLAN networking environment, computer <part-num-ref name="LAN or WLAN networking environment, computer">100</part-num-ref>
|
| 140 |
+
is connected to the LAN through a network interface <part-num-ref name="network interface">196</part-num-ref>
|
| 141 |
+
or adapter. When used in a WAN networking environment, computer <part-num-ref name="WAN networking environment, computer">100</part-num-ref>
|
| 142 |
+
typically includes a modem or other means for establishing communications over the WAN, such as the Internet. It will be appreciated that other means of establishing a communications link between the computers may be used. </p>
|
| 143 |
+
<p id="p-45" num="45">[0024] According to one embodiment, computer 100 is connected in a networking environment such that the processor <part-num-ref name="processor">110</part-num-ref>
|
| 144 |
+
and/or user interface module <part-num-ref name="and/or user interface module">170</part-num-ref>
|
| 145 |
+
determine whether incoming data follows a secure protocol. The incoming data can be from a VIVO communication device or from another data source. The secure protocol can be code stored in memory <part-num-ref name="secure protocol can be code stored in memory">120.</part-num-ref>
|
| 146 |
+
For example, processor <part-num-ref name="secure protocol can be code stored in memory 120. For example, processor">110</part-num-ref>
|
| 147 |
+
can determine whether an incoming call is from a VIVO, determine that a secure protocol is necessary and apply an appropriate authentication. </p>
|
| 148 |
+
<p id="p-46" num="46">[0025] Referring now to Figure 2, illustrated is an exemplary block diagram of a system <part-num-ref name="system">200</part-num-ref>
|
| 149 |
+
capable of being operable with VIVO computer systems and interacting with a VIVO- type computer system. System <part-num-ref name="VIVO- type computer system. System">200</part-num-ref>
|
| 150 |
+
is shown including network controller <part-num-ref name="is shown including network controller">210,</part-num-ref>
|
| 151 |
+
a network <part-num-ref name="network">220,</part-num-ref>
|
| 152 |
+
and one or more communication devices <part-num-ref name="network 220, and one or more communication devices">230,</part-num-ref>
|
| 153 |
+
<part-num-ref name="network 220, and one or more communication devices 230,">240,</part-num-ref>
|
| 154 |
+
and <part-num-ref name="network 220, and one or more communication devices 230, 240, and">250.</part-num-ref>
|
| 155 |
+
Communication devices <part-num-ref name="network 220, and one or more communication devices 230, 240, and 250. Communication devices">230,</part-num-ref>
|
| 156 |
+
<part-num-ref name="network 220, and one or more communication devices 230, 240, and 250. Communication devices 230,">240,</part-num-ref>
|
| 157 |
+
and <part-num-ref name="network 220, and one or more communication devices 230, 240, and 250. Communication devices 230, 240, and">250</part-num-ref>
|
| 158 |
+
may include telephones, wireless telephones, cellular telephones, personal digital assistants, computer terminals or any other devices that are capable of sending and receiving data. </p>
|
| 159 |
+
<p id="p-47" num="47">[0026] Network controller 210 is connected to network <part-num-ref name="is connected to network">220.</part-num-ref>
|
| 160 |
+
Network controller <part-num-ref name="is connected to network 220. Network controller">210</part-num-ref>
|
| 161 |
+
may be located at a base station, a service center, or any other location on network <part-num-ref name="service center, or any other location on network">220.</part-num-ref>
|
| 162 |
+
</p>
|
| 163 |
+
<p id="p-48" num="48">Network 220 may include any type of network that is capable of sending and receiving communication signals, including VIVO-type signals. For example, network <part-num-ref name="may include any type of network that is capable of sending and receiving communication signals, including VIVO-type signals. For example, network">220</part-num-ref>
|
| 164 |
+
may <boundary-data type="header">
|
| 165 |
+
<confidence value="888">-7-</confidence>
|
| 166 |
+
</boundary-data>
|
| 167 |
+
<page-break num="9"/>
|
| 168 |
+
include a data network, such as the Internet, an <confidence value="7">i</confidence>
|
| 169 |
+
ntranet, a local area network (LAN), a wide area network (WAN), a cable network, and other like communication systems. </p>
|
| 170 |
+
<p id="p-49" num="49">Network 220 may also include a telecommunications network, such as a local telephone network, long distance telephone network, cellular telephone network, satellite communications network, cable television network and other like communications systems that interact with computer systems. Network <part-num-ref name="local telephone network, long distance telephone network, cellular telephone network, satellite communications network, cable television network and other like communications systems that interact with computer systems. Network">220</part-num-ref>
|
| 171 |
+
may include more than one network and may include a plurality of different types of networks. Thus, network <part-num-ref name="plurality of different types of networks. Thus, network">220</part-num-ref>
|
| 172 |
+
may include a plurality of data networks, a plurality of telecommunications networks, and a combination of data and telecommunications networks and other like communication systems. </p>
|
| 173 |
+
<p id="p-50" num="50">[0027] In operation, one of the communication devices <part-num-ref name="communication devices">230,</part-num-ref>
|
| 174 |
+
<part-num-ref name="communication devices 230,">240,</part-num-ref>
|
| 175 |
+
or <part-num-ref name="communication devices 230, 240, or">250,</part-num-ref>
|
| 176 |
+
may attempt a communication with a receiving communication device. The communication can be routed through network <part-num-ref name="communication can be routed through network">220</part-num-ref>
|
| 177 |
+
and network controller <part-num-ref name="and network controller">210</part-num-ref>
|
| 178 |
+
to the receiving communication device. For example, a call originator communication device <part-num-ref name="call originator communication device">230</part-num-ref>
|
| 179 |
+
may attempt a call to a call recipient communication device <part-num-ref name="call recipient communication device">240.</part-num-ref>
|
| 180 |
+
In an embodiment, controller <part-num-ref name="embodiment, controller">210</part-num-ref>
|
| 181 |
+
is a VIVO- enabled controller such that an audible format may be a speech format. According to an embodiment, controller <part-num-ref name="embodiment, controller">210</part-num-ref>
|
| 182 |
+
can include an interface module <part-num-ref name="interface module">212</part-num-ref>
|
| 183 |
+
that can interface with a caller to provide voice-enabled methods in accordance with embodiments herein. </p>
|
| 184 |
+
<p id="p-51" num="51">[0028] Controller 210 can alter the format of the call by performing speech-to-text conversion on the call when controller <part-num-ref name="call when controller">210</part-num-ref>
|
| 185 |
+
determines the format of the call requires a format change. Controller <part-num-ref name="format change. Controller">210</part-num-ref>
|
| 186 |
+
can additionally alter the format of the call by performing text-to-speech conversion on the call when controller <part-num-ref name="call when controller">210</part-num-ref>
|
| 187 |
+
determines the format of the call requires a format change. Controller <part-num-ref name="format change. Controller">210</part-num-ref>
|
| 188 |
+
can then send the call in an appropriate format to the call recipient <part-num-ref name="call recipient">240.</part-num-ref>
|
| 189 |
+
In one embodiment, controller <part-num-ref name="call recipient 240. In one embodiment, controller">210</part-num-ref>
|
| 190 |
+
is a VIVO-enabled controller that alters speech to text or speech to computer code via interface <part-num-ref name="VIVO-enabled controller that alters speech to text or speech to computer code via interface">212</part-num-ref>
|
| 191 |
+
in accordance with the requirements of a VIVO. </p>
|
| 192 |
+
<p id="p-52" num="52">[0029] Figure 3 is an exemplary block diagram of a communication device <part-num-ref name="communication device">300,</part-num-ref>
|
| 193 |
+
such as communication device <part-num-ref name="communication device 300, such as communication device">230</part-num-ref>
|
| 194 |
+
or <part-num-ref name="or">240</part-num-ref>
|
| 195 |
+
according to an embodiment. Communication device <part-num-ref name="embodiment. Communication device">300</part-num-ref>
|
| 196 |
+
can include a housing <part-num-ref name="housing">310,</part-num-ref>
|
| 197 |
+
a processor <part-num-ref name="processor">320,</part-num-ref>
|
| 198 |
+
audio input and/or output circuitry <part-num-ref name="processor 320, audio input and/or output circuitry">33<confidence value="5">0</confidence>
|
| 199 |
+
</part-num-ref>
|
| 200 |
+
coupled to processor <part-num-ref name="coupled to processor">320,</part-num-ref>
|
| 201 |
+
a display <part-num-ref name="display">340</part-num-ref>
|
| 202 |
+
coupled to processor <part-num-ref name="coupled to processor">320,</part-num-ref>
|
| 203 |
+
a user interface <part-num-ref name="user interface">360</part-num-ref>
|
| 204 |
+
coupled to processor <part-num-ref name="coupled to processor">320</part-num-ref>
|
| 205 |
+
and a memory <part-num-ref name="memory">370</part-num-ref>
|
| 206 |
+
coupled to processor <part-num-ref name="coupled to processor">320.</part-num-ref>
|
| 207 |
+
Processor <part-num-ref name="coupled to processor 320. Processor">320</part-num-ref>
|
| 208 |
+
can <boundary-data type="header">
|
| 209 |
+
<confidence value="888">-8-</confidence>
|
| 210 |
+
</boundary-data>
|
| 211 |
+
<page-break num="10"/>
|
| 212 |
+
also include a security module <part-num-ref name="security module">322.</part-num-ref>
|
| 213 |
+
Security module <part-num-ref name="security module 322. Security module">322</part-num-ref>
|
| 214 |
+
may be hardware coupled to the processor <part-num-ref name="processor">320.</part-num-ref>
|
| 215 |
+
Alternatively, security module <part-num-ref name="processor 320. Alternatively, security module">322</part-num-ref>
|
| 216 |
+
could be located within processor <part-num-ref name="could be located within processor">320,</part-num-ref>
|
| 217 |
+
or located in software located in memory <part-num-ref name="could be located within processor 320, or located in software located in memory">370</part-num-ref>
|
| 218 |
+
and executed by processor <part-num-ref name="and executed by processor">320,</part-num-ref>
|
| 219 |
+
or any other type of module. Memory <part-num-ref name="and executed by processor 320, or any other type of module. Memory">370</part-num-ref>
|
| 220 |
+
can include a random access memory, a read only memory, an optical memory, a subscriber identity module memory, or any other memory that can be coupled to a communication device. Display <part-num-ref name="communication device. Display">340</part-num-ref>
|
| 221 |
+
can be a liquid crystal display (LCD), a light emitting diode (LED) display, a plasma display, or any other means for displaying information. Audio input and/or output circuitry <part-num-ref name="plasma display, or any other means for displaying information. Audio input and/or output circuitry">330</part-num-ref>
|
| 222 |
+
can include a microphone, a speaker, a transducer, or any other audio input and/or output circuitry. User interface <part-num-ref name="transducer, or any other audio input and/or output circuitry. User interface">360</part-num-ref>
|
| 223 |
+
can include a keypad, buttons, a touch pad, a joystick, an additional display, or any other device useful for providing an interface between a user and an electronic device. </p>
|
| 224 |
+
<p id="p-53" num="53">[0030] Processor 320 can be configured to control the functions of communication device <part-num-ref name="functions of communication device">300.</part-num-ref>
|
| 225 |
+
Communication device <part-num-ref name="functions of communication device 300. Communication device">300</part-num-ref>
|
| 226 |
+
can send and receive signals across network <part-num-ref name="can send and receive signals across network">220</part-num-ref>
|
| 227 |
+
using a transceiver <part-num-ref name="transceiver">350</part-num-ref>
|
| 228 |
+
coupled to antenna <part-num-ref name="coupled to antenna">390.</part-num-ref>
|
| 229 |
+
Alternatively, communication device <part-num-ref name="coupled to antenna 390. Alternatively, communication device">300</part-num-ref>
|
| 230 |
+
can be a device relying on twisted pair technology and not utilize transceiver <part-num-ref name="device relying on twisted pair technology and not utilize transceiver">350.</part-num-ref>
|
| 231 |
+
</p>
|
| 232 |
+
<p id="p-54" num="54">[0031] According to an embodiment, a user can use either the user interface <part-num-ref name="user interface">360</part-num-ref>
|
| 233 |
+
for input and/or output of information to and from communication device <part-num-ref name="for input and/or output of information to and from communication device">300</part-num-ref>
|
| 234 |
+
or use input and/or output using the audio input and/or output circuitry <part-num-ref name="audio input and/or output circuitry">330.</part-num-ref>
|
| 235 |
+
Data received by communication device <part-num-ref name="audio input and/or output circuitry 330. Data received by communication device">300</part-num-ref>
|
| 236 |
+
can be displayed on display <part-num-ref name="can be displayed on display">340</part-num-ref>
|
| 237 |
+
and/or provided audibly through audio input and/or output circuitry <part-num-ref name="and/or provided audibly through audio input and/or output circuitry">330.</part-num-ref>
|
| 238 |
+
Communication device <part-num-ref name="and/or provided audibly through audio input and/or output circuitry 330. Communication device">300</part-num-ref>
|
| 239 |
+
can operate as a V<confidence value="66">IV</confidence>
|
| 240 |
+
O when operated in a fully audible format. For example, VIVO applications can be stored on memory <part-num-ref name="fully audible format. For example, VIVO applications can be stored on memory">370</part-num-ref>
|
| 241 |
+
and processed by processor <part-num-ref name="and processed by processor">320.</part-num-ref>
|
| 242 |
+
In an embodiment, processor <part-num-ref name="embodiment, processor">320</part-num-ref>
|
| 243 |
+
includes interface module <part-num-ref name="includes interface module">324</part-num-ref>
|
| 244 |
+
and optional security module <part-num-ref name="and optional security module">322.</part-num-ref>
|
| 245 |
+
According to an embodiment, interface module can be disposed within processor <part-num-ref name="embodiment, interface module can be disposed within processor">320</part-num-ref>
|
| 246 |
+
and/or can be an interface module coupled to the processor, the interface module configured to (a) receive a vocal input to the voice-capable communication device, (b) receive one or more instructions referential to a first speech output version of the vocal input; and (c) create a second speech output version of the vocal input representational of the first speech output version of the vocal input manipulated responsive to the one or more instructions. </p>
|
| 247 |
+
<boundary-data type="header">
|
| 248 |
+
<confidence value="888">-9-</confidence>
|
| 249 |
+
</boundary-data>
|
| 250 |
+
<p id="p-55" num="55">
|
| 251 |
+
<page-break num="11"/>
|
| 252 |
+
[0032] Referring now to Figures 4A, 4B and 4C, an exemplary flow diagram illustrates the operation of the processor <part-num-ref name="processor">320,</part-num-ref>
|
| 253 |
+
interface module <part-num-ref name="processor 320, interface module">324</part-num-ref>
|
| 254 |
+
and/or user interface <part-num-ref name="and/or user interface">360</part-num-ref>
|
| 255 |
+
and/or network controller <part-num-ref name="and/or network controller">210</part-num-ref>
|
| 256 |
+
according to an embodiment. </p>
|
| 257 |
+
<p id="p-56" num="56">
|
| 258 |
+
<confidence value="5">[</confidence>
|
| 259 |
+
0033<confidence value="5">]</confidence>
|
| 260 |
+
Block 410 provides for receiving a vocal input to the voice-capable system. The vocal input can be via a microphone from a user, can be a vocal input received via a network interface, can be a recorded vocal input, or can be a created vocal input from a digital source. </p>
|
| 261 |
+
<p id="p-57" num="57">
|
| 262 |
+
<confidence value="5">[</confidence>
|
| 263 |
+
0034<confidence value="5">]</confidence>
|
| 264 |
+
Block 420 provides for creating a first speech output version of the vocal input. </p>
|
| 265 |
+
<p id="p-58" num="58">The first speech output version can be a digitized representation of the vocal input created using known digitization methods. As will be appreciated by those of skill in the art, the digitization can be at a system-defined sampling rate that is appropriate for speaker recognition and/or system requirements for fidelity. In one embodiment, the sampling rate of the first speech output version is adjustable so that a VIVO system can interact with different systems. For example, a voice mail system may be storage limited requiring a lower sampling rate. Conversely, the sampling rate could be at a higher rate for purposes of editing the first speech output version, and later altered to a lower sampling rate after a destination system sampling rate is determined.</p>
|
| 266 |
+
<p id="p-59" num="59">[0035<confidence value="5">]</confidence>
|
| 267 |
+
Block 4202 provides for creating a speech representation having a substantially defined fidelity to the vocal input. A substantially defined fidelity to the vocal input can be a defined fidelity in accordance with known standards such as within parameters defined by a POTS (plain old telephone system), or another standard. For example, a fully digital system can define a fidelity which enables recognition of a speaker that is different from an analog representation. Accordingly, in one embodiment, the defined fidelity is adjustable in accordance with the speech representation required for a destination system. As one of skill in the art will appreciate, the defined fidelity depends on a number of characteristics of the speech representation including sampling rate, bandwidth of frequencies of the speech representation, signal to noise ratio of the speech representation, and the like. In some instances the substantially defined fidelity will be that combination of factors that the system designer deems appropriate for the application, such as, for example, fidelity that <boundary-data type="header">
|
| 268 |
+
<confidence value="8">-</confidence>
|
| 269 |
+
<confidence value="88">10</confidence>
|
| 270 |
+
<confidence value="8">-</confidence>
|
| 271 |
+
</boundary-data>
|
| 272 |
+
<page-break num="12"/>
|
| 273 |
+
allows some statistically significant identification of a speaker by a listener (e.g., 85% of listeners can identify the speaker at the define fidelity.) [0036] Block <part-num-ref name="define fidelity.) [0036] Block">4204</part-num-ref>
|
| 274 |
+
provides for audibly presenting a speech representation having a substantially defined fidelity to the vocal input. For example, the audible presentation can be such that a user can hear the speech representation to enable editing the audible presentation. The fidelity of the speech representation can be in a form that could be transmitted by the user so that a realistic representation for a format chosen by the user can be heard. </p>
|
| 275 |
+
<p id="p-60" num="60">[0037] Block 4206 provides for processing the vocal input to enable an audible instruction set to manipulate the first speech output version of the vocal input. More particularly, processor <part-num-ref name="vocal input. More particularly, processor">320</part-num-ref>
|
| 276 |
+
can process a first speech output version of the vocal input received via user interface <part-num-ref name="vocal input received via user interface">360</part-num-ref>
|
| 277 |
+
using interface module <part-num-ref name="using interface module">324.</part-num-ref>
|
| 278 |
+
Interface module <part-num-ref name="using interface module 324. Interface module">324</part-num-ref>
|
| 279 |
+
can include an audible instruction set or provide access to an audible instruction set, such as via memory <part-num-ref name="audible instruction set, such as via memory">370.</part-num-ref>
|
| 280 |
+
</p>
|
| 281 |
+
<p id="p-61" num="61">[0038] Displayed within block 4206 is optional block <part-num-ref name="is optional block">42062,</part-num-ref>
|
| 282 |
+
which provides for enabling a user to interact with the audible instruction set, the audible instruction set including one or more commands including one or more of a skip forward command, a reverse command, a delete command, a move command, an undo command, and/or a mark command. For example, a user interacting with interface module <part-num-ref name="user interacting with interface module">324</part-num-ref>
|
| 283 |
+
via a user interface can interact with the first speech output version of the vocal input via the audible instruction set. </p>
|
| 284 |
+
<p id="p-62" num="62">[0039] Also displayed within block 4206 is optional block <part-num-ref name="is optional block">42064</part-num-ref>
|
| 285 |
+
which provides for enabling the user interface to navigate the first speech output version of the vocal input via one or more of the audible instruction set and/or a non-audible user interface. </p>
|
| 286 |
+
<p id="p-63" num="63">[0040] Block 4208 provides for processing the vocal input to create the first speech output version of the vocal input, the processing including inserting one or more tags into the first speech output version of the vocal input to enable a user interface. Block <part-num-ref name="user interface. Block">4208</part-num-ref>
|
| 287 |
+
includes optional block <part-num-ref name="includes optional block">42082,</part-num-ref>
|
| 288 |
+
which provides for creating a table of the one or more tags, the table enabling an audible instruction set. The table can be stored in memory <part-num-ref name="table can be stored in memory">370</part-num-ref>
|
| 289 |
+
to provide access to the interface module <part-num-ref name="interface module">324.</part-num-ref>
|
| 290 |
+
The table can be configured to interact with an <boundary-data type="header">
|
| 291 |
+
<confidence value="8888">-11-</confidence>
|
| 292 |
+
</boundary-data>
|
| 293 |
+
<page-break num="13"/>
|
| 294 |
+
XML application, which can be a vocal XML application, or other interactive method as one of skill in the art will appreciate with the benefit of this disclosure. </p>
|
| 295 |
+
<p id="p-64" num="64">
|
| 296 |
+
<confidence value="5">[</confidence>
|
| 297 |
+
0041] Block 4208 also includes optional block <part-num-ref name="also includes optional block">42084,</part-num-ref>
|
| 298 |
+
which provides for processing the vocal input via a voice XML-based application, the voice XML-based application inserting the one or more tags into the first speech output version of the vocal input to enable the user interface to navigate the first speech output version of the vocal input. The voice XML-based application can interact with the table stored in memory <part-num-ref name="table stored in memory">370.</part-num-ref>
|
| 299 |
+
</p>
|
| 300 |
+
<p id="p-65" num="65">[0042] Block 42084 includes block <part-num-ref name="includes block">420842,</part-num-ref>
|
| 301 |
+
which provides for enabling the user interface to navigate the first speech output version of the vocal input via one or more of the audible instruction set and/or a non-audible user interface. Thus, a user can interact with the instruction set via a keyboard or other input device as is convenient to the user. </p>
|
| 302 |
+
<p id="p-66" num="66">
|
| 303 |
+
<confidence value="5">[</confidence>
|
| 304 |
+
0043<confidence value="5">]</confidence>
|
| 305 |
+
Block 430 provides for receiving one or more instructions referential to the first speech output version of the vocal input. More particularly, a user can interact with the first speech output version of the vocal input in accordance with the audible instruction set, or another method of interaction. </p>
|
| 306 |
+
<p id="p-67" num="67">[0044] Block 430 includes optional block <part-num-ref name="includes optional block">4302,</part-num-ref>
|
| 307 |
+
which provides for receiving the one or more instructions via a graphical user interface. A graphical user interface can be implemented via interface <part-num-ref name="graphical user interface can be implemented via interface">324</part-num-ref>
|
| 308 |
+
or another application present on a user device or the like. </p>
|
| 309 |
+
<p id="p-68" num="68">In one embodiment, the graphical user interface can be a voiceXML based application or other appropriate application.</p>
|
| 310 |
+
<p id="p-69" num="69">[0045] Block 430 further includes optional block <part-num-ref name="further includes optional block">4304</part-num-ref>
|
| 311 |
+
which provides for receiving an instruction to identify a location in the first speech output version of the vocal input. The instruction can be orally provided or via another input method. Block <part-num-ref name="instruction can be orally provided or via another input method. Block">4304</part-num-ref>
|
| 312 |
+
includes optional block <part-num-ref name="includes optional block">43042,</part-num-ref>
|
| 313 |
+
which provides for receiving an instruction to move forward in the first speech output version of the vocal input by a number of words/sounds/marks and/or move backward in the first speech output version of the vocal input by a number of words/sounds/marks, the voice-enabled system responding audibly and/or visually to the instruction to identify a location in the first speech output version of the vocal input. </p>
|
| 314 |
+
<p id="p-70" num="70">[0046<confidence value="5">]</confidence>
|
| 315 |
+
Block 430 further includes optional block <part-num-ref name="further includes optional block">4306</part-num-ref>
|
| 316 |
+
which provides for receiving an instruction to expand and/or contract a predetermined length of the first speech output <boundary-data type="header">
|
| 317 |
+
<confidence value="8">-</confidence>
|
| 318 |
+
<confidence value="88">12</confidence>
|
| 319 |
+
<confidence value="8">-</confidence>
|
| 320 |
+
</boundary-data>
|
| 321 |
+
<page-break num="14"/>
|
| 322 |
+
version of the vocal input. For example, if a user is leaving a voice mail, the user can interact with the vocal input to shorten or lengthen the voice mail. The expansion and contraction can be accomplished via known voice processing techniques that alter the voice mail. </p>
|
| 323 |
+
<p id="p-71" num="71">[0047] Block 4306 includes block <part-num-ref name="includes block">43062,</part-num-ref>
|
| 324 |
+
which provides for receiving an indication identifying the predetermined length including a starting point and time indication. For example, a user can identify a portion of the vocal input that relates to a voice mail to be output from the system that should be removed instead of having to rerecord the voice mail in its entirety. </p>
|
| 325 |
+
<p id="p-72" num="72">[0048] Block 43062 includes optional block <part-num-ref name="includes optional block">430622,</part-num-ref>
|
| 326 |
+
which provides for receiving the indication as a tag corresponding to a navigation interface. For example, the first speech output version of the vocal input can include tags automatically inserted into the first speech output version of the vocal input that enable a user to reference an output from the system to alter the output. A user can reference the tag by providing a number of seconds to delete, a section of the first speech output version of the vocal input between tags to delete or expand or the like. </p>
|
| 327 |
+
<p id="p-73" num="73">[0049] Block 440 provides for creating a second speech output version of the vocal input representational of the first speech output version of the vocal input manipulated responsive to the one or more instructions. The first speech output version of the vocal input can be intended for voice mail or another vocal output. Thus, the one or more instructions can be configured to create a voice mail output as the second speech output version of the vocal input. Block <part-num-ref name="vocal input. Block">440</part-num-ref>
|
| 328 |
+
includes optional block <part-num-ref name="includes optional block">4402,</part-num-ref>
|
| 329 |
+
which provides that the creating a second speech output person can include time-shifting a portion of the first speech output version of the vocal input, associating one or more speech-output-version words/sounds/marks with the first speech output version of the vocal input, segmenting the first speech output version of the vocal input in relation to at least one identifiable speech- output-version <confidence value="222222222222222">word/sound/mark</confidence>
|
| 330 |
+
, inserting one or more speech units into the first speech output version of the vocal input, redacting one or more speech units from the first speech output version of the vocal input, and/or re-ordering the first speech output version of the vocal input. The speech output version can include words, sounds and/or marks that <boundary-data type="header">
|
| 331 |
+
<confidence value="8">-</confidence>
|
| 332 |
+
<confidence value="88">13</confidence>
|
| 333 |
+
<confidence value="8">-</confidence>
|
| 334 |
+
</boundary-data>
|
| 335 |
+
<page-break num="15"/>
|
| 336 |
+
segment the first speech output version. In one embodiment, the words, sounds and/or marks can be spoken, inserted via a keyboard or provided by another method to enable manipulation of the first speech output version of the vocal input. </p>
|
| 337 |
+
<p id="p-74" num="74">
|
| 338 |
+
<confidence value="5">[</confidence>
|
| 339 |
+
0050] Block 440 also includes optional block <part-num-ref name="also includes optional block">4404,</part-num-ref>
|
| 340 |
+
which provides for audibly demonstrating a result of the one or more instructions. Thus, a user can hear the results of manipulating a speech output version of the vocal input. </p>
|
| 341 |
+
<p id="p-75" num="75">[0051] Block 440 also include optional block <part-num-ref name="also include optional block">4406</part-num-ref>
|
| 342 |
+
which provides that the creating a second speech output version of the vocal input representational of the first speech output version of the vocal input manipulated responsive to the one or more instructions can include creating the second speech output version of the vocal input having a substantially defined fidelity to the vocal input. </p>
|
| 343 |
+
<p id="p-76" num="76">[0052] Block 440 also includes <part-num-ref name="also includes">4408</part-num-ref>
|
| 344 |
+
which provides that the creating a second speech output version of the vocal input representational of the first speech output version of the vocal input manipulated responsive to the one or more instructions can include audibly presenting the second speech output version of the vocal input having a substantially defined fidelity to the vocal input. The audible presentation can be via a speaker, a headset or other appropriate audible presentation medium. In one embodiment, the audible presentation allows user to hear how an actual output heard by a destination entity would sound. Therefore, a user can determine the natural qualities of an output after manipulation of the vocal input. In one embodiment, the user is not the creator of the vocal input. Rather, the audible presentation can enable an assistant of other entity to check the vocal input after manipulation prior to any output being transmitted. The ability to audibly check a second speech output version of the vocal input after the user manipulates the vocal input can enable confirmation of the natural qualities of the output. </p>
|
| 345 |
+
<p id="p-77" num="77">[0053] Block 450 provides for displaying text in response to the creating a first speech output version of the vocal input. Block <part-num-ref name="vocal input. Block">450</part-num-ref>
|
| 346 |
+
includes optional block <part-num-ref name="includes optional block">4502</part-num-ref>
|
| 347 |
+
which provides for receiving an indication of a portion of the first speech output version of the vocal input to expand and/or contract the portion of the first speech output version, the indication via the displayed text. In an embodiment, rather than an audible presentation or in addition to <boundary-data type="header">
|
| 348 |
+
<confidence value="8">-</confidence>
|
| 349 |
+
<confidence value="88">14</confidence>
|
| 350 |
+
<confidence value="8">-</confidence>
|
| 351 |
+
</boundary-data>
|
| 352 |
+
<page-break num="16"/>
|
| 353 |
+
an audible presentation, a user can manipulate the first speech output version of the vocal input by manipulating a displayed text. </p>
|
| 354 |
+
<p id="p-78" num="78">[0054] Block 450 further includes optional block <part-num-ref name="further includes optional block">4504</part-num-ref>
|
| 355 |
+
which provides for processing the vocal input including inserting one or more tags into the displayed text to enable a user to edit the displayed text via an audible instruction set referential to the one or more tags. </p>
|
| 356 |
+
<p id="p-79" num="79">Thus, for example, an XML application can be used to display the text that is independent of or in addition to a voice XML application.</p>
|
| 357 |
+
<p id="p-80" num="80">[0055] Referring now to Figure 5, an embodiment is directed to voice-capable user interface configured to manipulate a first speech output version of a vocal input. Interface <part-num-ref name="vocal input. Interface">500</part-num-ref>
|
| 358 |
+
is shown including a set of editing tools <part-num-ref name="set of editing tools">510.</part-num-ref>
|
| 359 |
+
The voice-capable user interface includes, as shown in blocks <part-num-ref name="voice-capable user interface includes, as shown in blocks">512,</part-num-ref>
|
| 360 |
+
<part-num-ref name="voice-capable user interface includes, as shown in blocks 512,">514,</part-num-ref>
|
| 361 |
+
<part-num-ref name="voice-capable user interface includes, as shown in blocks 512, 514,">516</part-num-ref>
|
| 362 |
+
and <part-num-ref name="and">518,</part-num-ref>
|
| 363 |
+
respectively, a set of editing tools capable of interacting with the first speech output version of the vocal input, the set of tools including one or more of a forwarding tool configured to forward to an identified location in the first speech output version of the vocal input, a reverse tool configured to reverse to an identified location in the first speech output version of the vocal input, an undo tool configured to reverse a prior action performed, a marking tool configured to mark a point in the first speech output version of the vocal input, and an expansion/contraction tool configured to expand and/or contract a predetermined length of the first speech output version of the vocal input. Interface <part-num-ref name="vocal input. Interface">500</part-num-ref>
|
| 364 |
+
further includes block <part-num-ref name="further includes block">520</part-num-ref>
|
| 365 |
+
illustrating a confirmation tool configured to produce a second speech output version of the vocal input representational of the first speech output version of the vocal input manipulated responsive to use of one or more tools of the set of editing tools. </p>
|
| 366 |
+
<p id="p-81" num="81">[0056] In one embodiment, the block <part-num-ref name="block">510</part-num-ref>
|
| 367 |
+
set of editing tools is configured to operate on one or more of a mobile communication device, a voice email system, and a portable mobile device. In another embodiment, the tools shown in block <part-num-ref name="tools shown in block">510</part-num-ref>
|
| 368 |
+
are a set of editing tools includes a navigation tool that enables a user to identify a number of words detected in the first speech output version of the vocal input, the navigation tool is configured to enable a user to state a number of words to step forward, and/or a number of words to step back in the first speech output version of the vocal input. In one embodiment, the <boundary-data type="header">
|
| 369 |
+
<confidence value="8">-</confidence>
|
| 370 |
+
<confidence value="88">15</confidence>
|
| 371 |
+
<confidence value="8">-</confidence>
|
| 372 |
+
</boundary-data>
|
| 373 |
+
<page-break num="17"/>
|
| 374 |
+
navigation tool is configured to enable a user to state a number of words to delete, move, and/or mark in the first speech output version of the vocal input. Further, in an embodiment, the navigation tool is configured to enable a user to state a key word and move a cursor to at least one location where the key word is located in the first speech output version of the vocal input. Optionally, the navigation tool is configured to enable a user to state a numerical reference in the first speech output version of the vocal input and move a cursor to at least one location where the numerical reference is located. </p>
|
| 375 |
+
<p id="p-82" num="82">
|
| 376 |
+
<confidence value="5">[</confidence>
|
| 377 |
+
0057<confidence value="5">]</confidence>
|
| 378 |
+
In another embodiment, the navigation tool is configured to enable a user to provide a non-vocal audible command that affects the first speech output version of the vocal input. For example, in one configuration, the non-vocal audible command includes one or more of a click, a chime, and a beep. </p>
|
| 379 |
+
<p id="p-83" num="83">[0058] Referring now to Figure 6, a voice-capable communication device <part-num-ref name="voice-capable communication device">600</part-num-ref>
|
| 380 |
+
is shown. </p>
|
| 381 |
+
<p id="p-84" num="84">Thevoice-capable communication device 600 is shown including a processor <part-num-ref name="processor">610,</part-num-ref>
|
| 382 |
+
and a memory coupled to the processor, memory <part-num-ref name="processor, memory">620.</part-num-ref>
|
| 383 |
+
Memory <part-num-ref name="processor, memory 620. Memory">620</part-num-ref>
|
| 384 |
+
can include read-only memory (ROM) <part-num-ref name="can include read-only memory (ROM)">630</part-num-ref>
|
| 385 |
+
and/or read and write memory (RAM) <part-num-ref name="and/or read and write memory (RAM)">640.</part-num-ref>
|
| 386 |
+
</p>
|
| 387 |
+
<p id="p-85" num="85">[0059] The voice-capable communication device <part-num-ref name="voice-capable communication device">600</part-num-ref>
|
| 388 |
+
is shown f<confidence value="7">a</confidence>
|
| 389 |
+
ther including an interface module <part-num-ref name="interface module">670.</part-num-ref>
|
| 390 |
+
The interface module can be configured such that the interface module is coupled to the processor, located within the processor, and/or located in the memory. The optional locations of interface module <part-num-ref name="optional locations of interface module">670</part-num-ref>
|
| 391 |
+
are designated as interface module 670(1), 670(2) and 670(3). </p>
|
| 392 |
+
<p id="p-86" num="86">
|
| 393 |
+
<confidence value="5">[</confidence>
|
| 394 |
+
0060] Interface module 670 can be configured as an interface module within the processor <part-num-ref name="processor">610</part-num-ref>
|
| 395 |
+
and/or an interface module coupled to the processor, the interface module configured to (a) receive a vocal input to the voice-capable communication device, (b) receive one or more instructions referential to a first speech output version of the vocal input; and (c) create a second speech output version of the vocal input representational of the first speech output version of the vocal input manipulated responsive to the one or more instructions. </p>
|
| 396 |
+
<p id="p-87" num="87">[0061] Thevoice-capable communication device 600 is shown further including audio input and/or output circuitry <part-num-ref name="is shown further including audio input and/or output circuitry">660.</part-num-ref>
|
| 397 |
+
In one embodiment, the audio input and/or output <boundary-data type="header">
|
| 398 |
+
<confidence value="8">-</confidence>
|
| 399 |
+
<confidence value="888">16-</confidence>
|
| 400 |
+
</boundary-data>
|
| 401 |
+
<page-break num="18"/>
|
| 402 |
+
circuitry includes one or more of a microphone, a speaker, a transducer, an audio input and/or output circuit. </p>
|
| 403 |
+
<p id="p-88" num="88">
|
| 404 |
+
<confidence value="5">[</confidence>
|
| 405 |
+
0062<confidence value="5">]</confidence>
|
| 406 |
+
In one embodiment voice-capable communication device 600 is disposed in a housing <part-num-ref name="housing">650.</part-num-ref>
|
| 407 |
+
More particularly, housing <part-num-ref name="housing 650. More particularly, housing">650</part-num-ref>
|
| 408 |
+
is a housing coupled to the processor, the housing encasing the memory, the processor, and/or the audio input and/or output circuitry. </p>
|
| 409 |
+
<p id="p-89" num="89">[0063] Those with skill in the computing arts will recognize that the disclosed embodiments have relevance to a wide variety of applications and architectures in addition to those described above. In addition, the functionality of the subject matter of the present application can be implemented in software, hardware, or a combination of software and hardware. The hardware portion can be implemented using specialized logic; the software portion can be stored in a memory or recording medium and executed by a suitable instruction execution system such as a microprocessor.</p>
|
| 410 |
+
<p id="p-90" num="90">
|
| 411 |
+
<confidence value="5">[</confidence>
|
| 412 |
+
0064] While the subject matter of the application has been shown and described with reference to particular embodiments thereof, it will be understood by those skilled in the art that the foregoing and other changes in form and detail may be made therein without departing from the spirit and scope of the subject matter of the application, including but not limited to additional, less or modified elements and/or additional, less or modified blocks performed in the same or a different order. </p>
|
| 413 |
+
<p id="p-91" num="91">[0065<confidence value="5">]</confidence>
|
| 414 |
+
Those having skill in the art will recognize that the state of the art has progressed to the point where there is little distinction left between hardware and software implementations of aspects of systems; the use of hardware or software is generally (but not always, in that in certain contexts the choice between hardware and software can become significant) a design choice representing cost vs. efficiency tradeoffs. Those having skill in the art will appreciate that there are various vehicles by which processes and/or systems and/or other technologies described herein can be effected (e.g., hardware, software, and/or firmware), and that the preferred vehicle will vary with the context in which the processes and/or systems and/or other technologies are deployed. For example, if an implementer determines that speed and accuracy are paramount, the implementer may opt for a mainly hardware and/or firmware vehicle; alternatively, if flexibility is paramount, the implementer may opt for a mainly software implementation; or, yet again <boundary-data type="header">
|
| 415 |
+
<confidence value="8">-</confidence>
|
| 416 |
+
<confidence value="888">17-</confidence>
|
| 417 |
+
</boundary-data>
|
| 418 |
+
<page-break num="19"/>
|
| 419 |
+
alternatively, the implementer may opt for some combination of hardware, software, and/or firmware. Hence, there are several possible vehicles by which the processes and/or devices and/or other technologies described herein may be effected, none of which is inherently superior to the other in that any vehicle to be utilized is a choice dependent upon the context in which the vehicle will be deployed and the specific concerns (e.g., speed, flexibility, or predictability) of the implementer, any of which may vary. Those skilled in the art will recognize that optical aspects of implementations will typically employ optically-oriented hardware, software, and or firmware. </p>
|
| 420 |
+
<p id="p-92" num="92">[0066] The foregoing detailed description has set forth various embodiments of the devices and/or processes via the use of block diagrams, flowcharts, and/or examples.</p>
|
| 421 |
+
<p id="p-93" num="93">Insofar as such block diagrams, flowcharts, and/or examples contain one or more functions and/or operations, it will be understood by those within the art that each function and/or operation within such block diagrams, flowcharts, or examples can be implemented, individually and/or collectively, by a wide range of hardware, software, firmware, or virtually any combination thereof. In one embodiment, several portions of the subject matter described herein may be implemented via Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), digital signal processors (DSPs), or other integrated formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein, in whole or in part, can be equivalently implemented in standard integrated circuits, as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or as virtually any combination thereof, and that designing the circuitry and/or writing the code for the software and or firmware would be well within the skill of one of skill in the art in light of this disclosure.</p>
|
| 422 |
+
<p id="p-94" num="94">In addition, those skilled in the art will appreciate that the mechanisms of the subject matter described herein are capable of being distributed as a program product in a variety of forms, and that an illustrative embodiment of the subject matter described herein applies equally regardless of the particular type of signal bearing media used to actually carry out the distribution. Examples of a signal bearing media include, but are not limited to, the <boundary-data type="header">
|
| 423 |
+
<confidence value="8">-</confidence>
|
| 424 |
+
<confidence value="88">18</confidence>
|
| 425 |
+
<confidence value="8">-</confidence>
|
| 426 |
+
</boundary-data>
|
| 427 |
+
<page-break num="20"/>
|
| 428 |
+
following: recordable type media such as floppy disks, hard disk drives, CD ROMs, digital tape, and computer memory; and transmission type media such as digital and analog communication links using TDM or <confidence value="5">I</confidence>
|
| 429 |
+
P based communication links (e.g., packet links). </p>
|
| 430 |
+
<p id="p-95" num="95">
|
| 431 |
+
<confidence value="5">[</confidence>
|
| 432 |
+
0067] The herein described aspects depict different components contained within, or connected with, different other components. It is to be understood that such depicted architectures are merely exemplary, and that in fact many other architectures can be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively "associated" such that the desired functionality is achieved. Hence, any two components herein combined to achieve a particular functionality can be seen as "associated with" each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two components so associated can also be viewed as being "operably connected", or "operably coupled", to each other to achieve the desired functionality, and any two components capable of being so associated can also be viewed as being "operably couplable", to each other to achieve the desired functionality. Specific examples of operably couplable include but are not limited to physically mateable and/or physically interacting components and/or wirelessly interactable and/or wirelessly interacting components and/or logically interacting and/or logically interactable components. </p>
|
| 433 |
+
<p id="p-96" num="96">
|
| 434 |
+
<confidence value="5">[</confidence>
|
| 435 |
+
0068] Those skilled in the art will recognize that it is common within the art to implement devices and/or processes and/or systems in the fashion(s) set forth herein, and thereafter use engineering and/or business practices to integrate such implemented devices and/or processes and/or systems into more comprehensive devices and/or processes and/or systems. That is, at least a portion of the devices <confidence value="222222">and/or</confidence>
|
| 436 |
+
processes and/or systems described herein can be integrated into comprehensive devices and/or processes and/or systems via a reasonable amount of experimentation. Those having skill in the art will recognize that examples of such comprehensive devices and/or processes and/or systems might include - as appropriate to context and application -- all or part of devices and/or processes and/or systems of (a) an air conveyance (e.g., an airplane, rocket, hovercraft, helicopter, etc.) , (b) a ground conveyance (e.g., a car, truck, locomotive, tank, armored <boundary-data type="header">
|
| 437 |
+
<confidence value="8">-</confidence>
|
| 438 |
+
<confidence value="888">19-</confidence>
|
| 439 |
+
</boundary-data>
|
| 440 |
+
<page-break num="21"/>
|
| 441 |
+
personnel carrier, etc.), (c) a building (e.g., a home, warehouse, office, etc.), (d) an appliance (e.g., a refrigerator, a washing machine, a dryer, etc.), (e) a communications system (e.g., a networked system, a telephone system, a Voice over <confidence value="5">I</confidence>
|
| 442 |
+
P system, etc.), (f) a business entity (e.g., an Internet Service Provider (ISP) entity such as Comcast Cable, Quest, Southwestern Bell, etc.); or (g) a <confidence value="22222222222222">wired/wireless</confidence>
|
| 443 |
+
services entity such as Sprint, Cingular, Nextel, etc.), etc. </p>
|
| 444 |
+
<p id="p-97" num="97">
|
| 445 |
+
<confidence value="5">[</confidence>
|
| 446 |
+
0069<confidence value="5">]</confidence>
|
| 447 |
+
While particular aspects of the present subject matter described herein have been shown and described, it will be apparent to those skilled in the art that, based upon the teachings herein, changes and modifications may be made without departing from the subject matter described herein and its broader aspects and, therefore, the appended claims are to encompass within their scope all such changes and modifications as are within the true spirit and scope of this subject matter described herein. Furthermore, it is to be understood that the invention is defined by the appended claims. It will be understood by those within the art that, in general, terms used herein, and especially in the appended claims (e.g., bodies of the appended claims) are generally intended as "open" terms (e.g., the term "including" should be interpreted as "including but not limited to," the term "having" should be interpreted as "having at least," the te<confidence value="8">r</confidence>
|
| 448 |
+
m "includes" should be interpreted as "includes but is not limited to," etc.). It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, as an aid to understanding, the following appended claims may contain usage of the introductory phrases "at least one" and "one or more" to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles "a" or "an" limits any particular claim containing such introduced claim recitation to inventions containing only one such recitation, even when the same claim includes the introductory phrases "one or more" or "at least one" and indefinite articles such as "a" or "an" (e.g., "a" and/or "an<confidence value="5">"</confidence>
|
| 449 |
+
should typically be interpreted to mean "at least one<confidence value="5">"</confidence>
|
| 450 |
+
or "one or more"); the same holds true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the <boundary-data type="header">
|
| 451 |
+
<confidence value="8">-</confidence>
|
| 452 |
+
<confidence value="88">20</confidence>
|
| 453 |
+
<confidence value="8">-</confidence>
|
| 454 |
+
</boundary-data>
|
| 455 |
+
<page-break num="22"/>
|
| 456 |
+
art will recognize that such recitation should typically be interpreted to mean at least the recited number (e.g., the bare recitation of "two recitations," without other modifiers, typically means at least two recitations, or two or more recitations). Furthermore, in those instances where a convention analogous to "at least one of A, B, and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., " a system having at least one of A, B, and C" would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.). In those instances where a convention analogous to "at least one of A, B, or C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., " a system having at least one of A, B, or C" would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.). </p>
|
| 457 |
+
<boundary-data type="header">
|
| 458 |
+
<confidence value="888">-21</confidence>
|
| 459 |
+
<confidence value="8">-</confidence>
|
| 460 |
+
</boundary-data>
|
| 461 |
+
</description>
|
| 462 |
+
</us-patent-application>
|
| 463 |
+
|
applicant/11240256.xml
ADDED
|
@@ -0,0 +1,388 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>11240256</doc-number>
|
| 8 |
+
<date>2005-09-30</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<boundary-data type="header">Attorney, J. I. <confidence value="222222">J'maev</confidence>
|
| 14 |
+
PATENT </boundary-data>
|
| 15 |
+
<boundary-data type="header">Reg. No. 45,669 HP-200408085-<confidence value="8">1</confidence>
|
| 16 |
+
</boundary-data>
|
| 17 |
+
<boundary-data type="header">Expr. Mail EO 913 084 953 US 200408085-1</boundary-data>
|
| 18 |
+
<boundary-data type="header">September 30, 2005</boundary-data>
|
| 19 |
+
<heading id="h-1">METHOD AND APPARATUS</heading>
|
| 20 |
+
<heading id="h-2">FOR</heading>
|
| 21 |
+
<heading id="h-3">VALIDATION <confidence value="5">O</confidence>
|
| 22 |
+
F CONTINUOUS ACCESS </heading>
|
| 23 |
+
<heading id="h-4">TO A DATA STRUCTURE</heading>
|
| 24 |
+
<p id="p-1" num="1">
|
| 25 |
+
<boundary-data type="line-number">
|
| 26 |
+
<confidence value="8">5</confidence>
|
| 27 |
+
</boundary-data>
|
| 28 |
+
<confidence value="88">By</confidence>
|
| 29 |
+
Eric C. Scoredos </p>
|
| 30 |
+
<heading id="h-5">BACKGROUND</heading>
|
| 31 |
+
<p id="p-2" num="2">
|
| 32 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 33 |
+
[0001] In a multi-processor system, data is shared through the use of special data structures that have associated with them a read/write lock mechanism. The read/write lock mechanism, in traditional terms, is used to prevent one process from modifying data in the data structure during a period of time when a second process is relying upon the integrity of the data in the same data structure. Typically, a first processing thread will <boundary-data type="line-number">15 </boundary-data>
|
| 34 |
+
acquire a read lock before it accesses data stored in the data structure. So long as the first processing thread continues to hold the read lock, a second process will be prevented from acquiring a write lock. In fact, a write lock is only granted to a process when there are no read locks outstanding. This prevents a second process from modifying data stored in the data structure while a first process holds a read lock. This process is especially <boundary-data type="line-number">20 </boundary-data>
|
| 35 |
+
important in a multi-processor system where a data structure is copied into a local cache memory. Since the data structure is copied into a local cache memory, it is important not to modify the original copy of the data structure so long as a read lock is held by the first process. This ensures that the original copy of the data structure remains consistent with the local cache copy of the data structure. It should be appreciated that the original copy <boundary-data type="line-number">25 </boundary-data>
|
| 36 |
+
of the data structure is typically maintained in a main memory or in some other form of computer readable medium, for example a hard drive. </p>
|
| 37 |
+
<p id="p-3" num="3">[0002<confidence value="5">]</confidence>
|
| 38 |
+
It should be appreciated that many applications rely on extremely large data structures. In the case where an extremely large data structure is copied into a local cache memory, a first process must be able to rely on the consistency of the data stored in the <boundary-data type="header">
|
| 39 |
+
<confidence value="5">1</confidence>
|
| 40 |
+
</boundary-data>
|
| 41 |
+
<boundary-data type="header">App<confidence value="11">..</confidence>
|
| 42 |
+
HP-20040 808 <confidence value="8822">5-1-</confidence>
|
| 43 |
+
Rev- <confidence value="1">I</confidence>
|
| 44 |
+
<confidence value="8">a</confidence>
|
| 45 |
+
doc </boundary-data>
|
| 46 |
+
<page-break num="2"/>
|
| 47 |
+
<boundary-data type="header">Attorney, J. I. <confidence value="222222">J'maev</confidence>
|
| 48 |
+
PATENT </boundary-data>
|
| 49 |
+
<boundary-data type="header">Reg. No. 45,669 HP-200408085-<confidence value="5">1</confidence>
|
| 50 |
+
</boundary-data>
|
| 51 |
+
<boundary-data type="header">Expr. Mail <confidence value="5">E</confidence>
|
| 52 |
+
O 913 084 953 US 200408085-1 </boundary-data>
|
| 53 |
+
<boundary-data type="header">September 30, 2005</boundary-data>
|
| 54 |
+
data structure vis-<confidence value="4">a</confidence>
|
| 55 |
+
-vis the original copy of the data structure. When the first process needs to be suspended so as to allow other applications to run, the first process may need to relinquish its original read lock. <confidence value="22222222">Up.until</confidence>
|
| 56 |
+
now, there has been no way to determine whether or not a different process has acquired an intervening write lock when the first <boundary-data type="line-number">5 </boundary-data>
|
| 57 |
+
process reacquires a read-lock to the data structure to continue processing. An intervening write lock can be considered to be a write lock that is granted to yet a second process in between the time where the first process relinquishes its original read lock and the time when the first process has been granted another read lock for the same data structure. Because the first process cannot determine whether or not an intervening write <boundary-data type="line-number">10 </boundary-data>
|
| 58 |
+
lock was granted, the first process must assume its local cache copy of the data structure is inconsistent with the original copy of the data structure. This means that the first process must revalidate the entire data structure. Typically, this means that the first process must refresh its local cache copy of the data structure. This is accomplished by reloading a fresh copy of the data structure back into the local cache memory used by the <boundary-data type="line-number">15 </boundary-data>
|
| 59 |
+
first process. Hence, any processing that was accomplished prior to relinquishing the first read lock must be undertaken a new. </p>
|
| 60 |
+
<boundary-data type="header">
|
| 61 |
+
<confidence value="8">2</confidence>
|
| 62 |
+
</boundary-data>
|
| 63 |
+
<boundary-data type="header">AppHP-200408085-<confidence value="5">1</confidence>
|
| 64 |
+
-Rev- <confidence value="22222">a.doc</confidence>
|
| 65 |
+
</boundary-data>
|
| 66 |
+
<boundary-data type="header">Attorney, <confidence value="66">J.</confidence>
|
| 67 |
+
I. <confidence value="222222">J'maev</confidence>
|
| 68 |
+
PATENT </boundary-data>
|
| 69 |
+
<boundary-data type="header">Reg. No. 45,669 HP-200408085-<confidence value="8">1</confidence>
|
| 70 |
+
</boundary-data>
|
| 71 |
+
<boundary-data type="header">Expr. Mail EO 913 084 953 US 200408085-1</boundary-data>
|
| 72 |
+
<boundary-data type="header">September 30, 2005</boundary-data>
|
| 73 |
+
<heading id="h-6">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
|
| 74 |
+
<p id="p-4" num="4">
|
| 75 |
+
<page-break num="3"/>
|
| 76 |
+
[0003] Several alternative embodiments will hereinafter be described in conjunction with the appended drawings and figures, wherein like numerals denote like elements, and <boundary-data type="line-number">5 </boundary-data>
|
| 77 |
+
in which: </p>
|
| 78 |
+
<p id="p-5" num="5">Fig. 1 is a flow diagram that depicts one example method for validating continuous access to a data structure;</p>
|
| 79 |
+
<p id="p-6" num="6">Fig. 2 is a flow diagram that de<confidence value="8">p</confidence>
|
| 80 |
+
icts one example method for determini<confidence value="8">n</confidence>
|
| 81 |
+
g when an intervening write lock has been granted; </p>
|
| 82 |
+
<p id="p-7" num="7">
|
| 83 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 84 |
+
Fig. 3 is a flow diagram that illustrates yet another example variation of the present method wherein one or more secondary read locks are granted before a first process reacquires a first read lock; </p>
|
| 85 |
+
<p id="p-8" num="8">Fig. 4 is a flow diagram that depicts an example variation of the present method for clearing a dirty bit once it is used to determine if an intermediate write lock was granted;</p>
|
| 86 |
+
<p id="p-9" num="9">
|
| 87 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 88 |
+
Fig. 5 is a flow diagram that depicts an example variation of the present method wherein a dirty bit is set to upon granting an intervening write lock; </p>
|
| 89 |
+
<p id="p-10" num="10">Fig. 6 is a block diagram that depicts one example embodiment of a system that enables continuous access to a data structure; and Fig. 7 is a data flow diagram that depicts the internal operation of various alternative <boundary-data type="line-number">20 </boundary-data>
|
| 90 |
+
example embodiments of a system that enables continuous access to a data structure. </p>
|
| 91 |
+
<boundary-data type="header">
|
| 92 |
+
<confidence value="8">3</confidence>
|
| 93 |
+
</boundary-data>
|
| 94 |
+
<boundary-data type="header">AppHP-200408085-<confidence value="5">1</confidence>
|
| 95 |
+
-Rev- <confidence value="22222">a.doc</confidence>
|
| 96 |
+
</boundary-data>
|
| 97 |
+
<boundary-data type="header">Attorney, J. I. J'maev PATENT</boundary-data>
|
| 98 |
+
<boundary-data type="header">Reg. No. 45,669 HP-200408085-<confidence value="8">1</confidence>
|
| 99 |
+
</boundary-data>
|
| 100 |
+
<boundary-data type="header">Expr. Mail E<confidence value="5">O</confidence>
|
| 101 |
+
913 084 953 US 200408085-1 </boundary-data>
|
| 102 |
+
<boundary-data type="header">September 30, 2005</boundary-data>
|
| 103 |
+
<heading id="h-7">
|
| 104 |
+
<confidence value="88">DE</confidence>
|
| 105 |
+
TAILED DESCRIPTION </heading>
|
| 106 |
+
<p id="p-11" num="11">
|
| 107 |
+
<page-break num="4"/>
|
| 108 |
+
[0004] Fig. 1 is a flow diagram that depicts one example method for validating continuous access to a data structure. According to this example method, a first process is able to validate continuous access to a data structure by acquiring a first read lock (step <boundary-data type="line-number">5 </boundary-data>
|
| 109 |
+
5). The first process processes data that is included in the data structure by continuing to hold the first read lock (step 10). In accordance with this example method, the first process may need to relinquish the first read lock in order to allow other processes to run. </p>
|
| 110 |
+
<p id="p-12" num="12">As such, the first read lock is relinquished by the first process (step 15). At some point subsequent to relinquishing the first read lock, the first process will reacquire the first <boundary-data type="line-number">10 </boundary-data>
|
| 111 |
+
read lock (step 20). The first process then needs to determine whether an intervening write lock was granted (step 25). In the event that an intervening write lock was granted, the first process must assume that the data stored in the data structure has been modified. </p>
|
| 112 |
+
<p id="p-13" num="13">Accordingly, the data structure needs to be revalidated (step 35). In the event that an intervening write lock was not granted, the first process can continue processing the data <boundary-data type="line-number">15 </boundary-data>
|
| 113 |
+
structure (step 30). It should be appreciated that this process is useful in those situations where the data structure is large and includes data referencing facilities. One example of a data structure that includes data referencing facilities is a linked list. In a linked list, references to elements within the data structure are often modified as elements are added or removed to the data structure. As such, any processing that was accomplished prior to <boundary-data type="line-number">20 </boundary-data>
|
| 114 |
+
relinquishing the read lock can no longer continue because the data references included in the data structure can no longer he relied upon by the first process to access data stored in the data structure and the data structure can no longer be consistently navigated. As such, a new copy of the data structure must be reloaded into a local cache memory used by the first process to store a copy of the data structure. </p>
|
| 115 |
+
<p id="p-14" num="14">
|
| 116 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 117 |
+
[0005<confidence value="5">]</confidence>
|
| 118 |
+
Fig. 2 is a flow diagram that depicts one example method for determining when an intervening write lock has been granted. According to this example variation of the present method, a first process determines whether or not an intervening write lock was granted by examining a dirty bit included in a reacquired first read lock (step 40). It should be appreciated that the the dirty bit is included in the reacquired first read lock and <boundary-data type="header">
|
| 119 |
+
<confidence value="8">4</confidence>
|
| 120 |
+
</boundary-data>
|
| 121 |
+
<boundary-data type="header">AppHP-200408085-<confidence value="5">1</confidence>
|
| 122 |
+
-Rev-<confidence value="6">I</confidence>
|
| 123 |
+
<confidence value="22222">a.doc</confidence>
|
| 124 |
+
</boundary-data>
|
| 125 |
+
<page-break num="5"/>
|
| 126 |
+
<boundary-data type="header">Attorney, J. I. <confidence value="222222">J'maev</confidence>
|
| 127 |
+
PATENT </boundary-data>
|
| 128 |
+
<boundary-data type="header">Reg. No. 45,669 HP<confidence value="5">-</confidence>
|
| 129 |
+
200408085<confidence value="68">-1</confidence>
|
| 130 |
+
</boundary-data>
|
| 131 |
+
<boundary-data type="header">Expr. Mail E<confidence value="5">O</confidence>
|
| 132 |
+
913 084 953 US 200408085-1 </boundary-data>
|
| 133 |
+
<boundary-data type="header">September 30, 2005</boundary-data>
|
| 134 |
+
not in the data structure itself. In the situation where a dirty bit is included in the data structure itself, there is no method for determining the status of the dirty bit in the event a different process acquires a read lock. In yet another example variation of the present method, the first process will clear the dirty bit in the reacquired first read lock when the <boundary-data type="line-number">5 </boundary-data>
|
| 135 |
+
dirty bit is in fact set. By including the dirty bit in the read lock, a plurality of read locks may be granted to a plurality of processes each of which has an indicator (i.e. the dirty bit included in the read lock) as to the consistency of a local cache copy of the data structure vis-<confidence value="5">a</confidence>
|
| 136 |
+
-vis an original copy. This despite the number of processes waiting to acquire read locks to continue processing at any given time. </p>
|
| 137 |
+
<p id="p-15" num="15">
|
| 138 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 139 |
+
[0006] Fig. 3 is a flow diagram that illustrates yet another example variation of the present method wherein one or more secondary read locks are granted before a first process reacquires a first read lock. In this variation of the present method, a second process is granted a read lock before a first read lock is reacquired by the first process (step 50). A read lock count is incremented (step <part-num-ref name="read lock count is incremented (step">65)</part-num-ref>
|
| 140 |
+
when the second read lock is <boundary-data type="line-number">15 </boundary-data>
|
| 141 |
+
released by a process (step 55), but still wants to reacquire the read lock (step <part-num-ref name="read lock (step">60)</part-num-ref>
|
| 142 |
+
and continuing processing the data structure. When the second read lock is reacquired by the second process (step 53), the read lock count is decremented (step 57). In this manner, a running count of the number of outstanding processes awaiting regrant of read locks is maintained. </p>
|
| 143 |
+
<p id="p-16" num="16">
|
| 144 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 145 |
+
[0007] Fig. 4 is a flow diagram that depicts an example variation of the present method for clearing a dirty bit once it is used to determine if an intermediate write lock was granted. In this example variation of the present method, a dirty bit included in a reacquired first read lock is used to determine if an intermediate write lock was granted. </p>
|
| 146 |
+
<p id="p-17" num="17">In order to ensure that the dirty bit is cleared only by the last process holding a read lock <boundary-data type="line-number">25 </boundary-data>
|
| 147 |
+
where there are no other processes waiting to acquire the read lock to continue processing, the dirty bit is cleared (step <part-num-ref name="dirty bit is cleared (step">85)</part-num-ref>
|
| 148 |
+
when a read lock is relinquished by the first process (step <part-num-ref name="first process (step">75)</part-num-ref>
|
| 149 |
+
and there are no other read locks waiting to be reacquired (step 80). It should be appreciated that, according to this variation of the present method, a <boundary-data type="header">
|
| 150 |
+
<confidence value="8">5</confidence>
|
| 151 |
+
</boundary-data>
|
| 152 |
+
<boundary-data type="header">AppHP-200408085-<confidence value="5">1</confidence>
|
| 153 |
+
-Rev-<confidence value="1">1</confidence>
|
| 154 |
+
<confidence value="22222">a.doc</confidence>
|
| 155 |
+
</boundary-data>
|
| 156 |
+
<page-break num="6"/>
|
| 157 |
+
<boundary-data type="header">Attorney, J. I. <confidence value="222222">J'maev</confidence>
|
| 158 |
+
PATENT </boundary-data>
|
| 159 |
+
<boundary-data type="header">Reg. No. 45,669 HP<confidence value="5">-</confidence>
|
| 160 |
+
200408085<confidence value="68">-1</confidence>
|
| 161 |
+
</boundary-data>
|
| 162 |
+
<boundary-data type="header">Expr. Mail EO 913 084 953 US 200408085-1</boundary-data>
|
| 163 |
+
<boundary-data type="header">September 30, 2005</boundary-data>
|
| 164 |
+
determination is made as to whether or not there are other read locks outstanding is made by consulting the read lock count which is maintained as heretofore described. </p>
|
| 165 |
+
<p id="p-18" num="18">[0008] Fig. <confidence value="5">5</confidence>
|
| 166 |
+
is a flow diagram that depicts an example variation of the present method wherein a dirty bit is set to upon granting an intervening write lock. According to <boundary-data type="line-number">5 </boundary-data>
|
| 167 |
+
this variation of the present method, when there are no other read locks outstanding (step <part-num-ref name="present method, when there are no other read locks outstanding (step">95)</part-num-ref>
|
| 168 |
+
for a particular data structure, a write lock is granted (step <part-num-ref name="write lock is granted (step">100)</part-num-ref>
|
| 169 |
+
in response to receiving a write lock request (step 90). Accordingly, a dirty bit is set in a read lock (step 105). It should be appreciated that the read lock can then be reacquired by the first process or <confidence value="8">s</confidence>
|
| 170 |
+
hared with other processes that need to a<confidence value="8">c</confidence>
|
| 171 |
+
cess a local cache copy of a data <boundary-data type="line-number">10 </boundary-data>
|
| 172 |
+
structure or need access to the data structure itself. </p>
|
| 173 |
+
<p id="p-19" num="19">[0009] Fig. 6 is a block diagram that depicts one example embodiment of a system<confidence value="5">,</confidence>
|
| 174 |
+
that enables continuous access to a data structure. According to this example embodiment, a system that enables continuous access to a data structure comprises a main data memory <part-num-ref name="main data memory">215,</part-num-ref>
|
| 175 |
+
a system memory <part-num-ref name="system memory">240,</part-num-ref>
|
| 176 |
+
and a first processing unit <part-num-ref name="first processing unit">205.</part-num-ref>
|
| 177 |
+
In this example <boundary-data type="line-number">15 </boundary-data>
|
| 178 |
+
embodiment, the first processing unit <part-num-ref name="first processing unit">205</part-num-ref>
|
| 179 |
+
includes a first process or <part-num-ref name="first process or">200</part-num-ref>
|
| 180 |
+
and a local cache memory <part-num-ref name="local cache memory">210.</part-num-ref>
|
| 181 |
+
It should be appreciated that the local cache memory <part-num-ref name="local cache memory">210</part-num-ref>
|
| 182 |
+
is used to store a copy of the data structure <part-num-ref name="data structure">290</part-num-ref>
|
| 183 |
+
that is otherwise stored in the main data memory <part-num-ref name="main data memory">215.</part-num-ref>
|
| 184 |
+
It should further be appreciated that the data structure <part-num-ref name="data structure">290</part-num-ref>
|
| 185 |
+
stored in the main data memory <part-num-ref name="main data memory">215</part-num-ref>
|
| 186 |
+
may be copied into a plurality of cache memories <part-num-ref name="plurality of cache memories">(210,</part-num-ref>
|
| 187 |
+
235), each of which services <boundary-data type="line-number">20 </boundary-data>
|
| 188 |
+
a corresponding processor <part-num-ref name="corresponding processor">(200,</part-num-ref>
|
| 189 |
+
230). It should be appreciated that a first processing unit <part-num-ref name="first processing unit">205</part-num-ref>
|
| 190 |
+
is communicatively coupled to the main data memory <part-num-ref name="main data memory">215</part-num-ref>
|
| 191 |
+
and the system memory <part-num-ref name="system memory">240</part-num-ref>
|
| 192 |
+
by means of a bus <part-num-ref name="bus">220.</part-num-ref>
|
| 193 |
+
A second processing unit <part-num-ref name="second processing unit">225</part-num-ref>
|
| 194 |
+
is also coupled to the main data memory <part-num-ref name="main data memory">215</part-num-ref>
|
| 195 |
+
and the system memory <part-num-ref name="system memory">240</part-num-ref>
|
| 196 |
+
by means of the bus <part-num-ref name="bus">220.</part-num-ref>
|
| 197 |
+
</p>
|
| 198 |
+
<p id="p-20" num="20">[0010] This example embodiment of a system that enables continuous access to a data <boundary-data type="line-number">
|
| 199 |
+
<confidence value="86">25</confidence>
|
| 200 |
+
</boundary-data>
|
| 201 |
+
structure as heretofore described further includes various functional modules each of which comprises an instruction sequence that can be executed by any one of the processor <part-num-ref name="processor">(200,</part-num-ref>
|
| 202 |
+
<part-num-ref name="processor (200,">230)</part-num-ref>
|
| 203 |
+
in a multi-processor system. An instruction sequence that implements a functional module, according to one alternative embodiment, is stored in the system <boundary-data type="header">
|
| 204 |
+
<confidence value="8">6</confidence>
|
| 205 |
+
</boundary-data>
|
| 206 |
+
<boundary-data type="header">AppHP-200408085-<confidence value="5">1</confidence>
|
| 207 |
+
-Rev- <confidence value="22222">a.doc</confidence>
|
| 208 |
+
</boundary-data>
|
| 209 |
+
<page-break num="7"/>
|
| 210 |
+
<boundary-data type="header">Attorney, J. I. <confidence value="222222">J'maev</confidence>
|
| 211 |
+
PATENT </boundary-data>
|
| 212 |
+
<boundary-data type="header">Reg. No. 45,669 HP-200408085-<confidence value="8">1</confidence>
|
| 213 |
+
</boundary-data>
|
| 214 |
+
<boundary-data type="header">Expr. Mail EO 913 084 953 US 200408085-1</boundary-data>
|
| 215 |
+
<boundary-data type="header">September 30, 2005</boundary-data>
|
| 216 |
+
memory <part-num-ref name="system memory">240.</part-num-ref>
|
| 217 |
+
The reader is advised that the term "minimally causes the processor" and variants thereof is intended to serve as an open-ended enumeration of functions performed by the processor as it executes a particular functional module (i.e. instruction sequence). As such, an embodiment where a particular functional module causes a <boundary-data type="line-number">5 </boundary-data>
|
| 218 |
+
processor to perform functions in addition to those defined in the appended claims is to be included in the scope of the claims appended hereto. </p>
|
| 219 |
+
<p id="p-21" num="21">[0011] The functional modules (and their corresponding instruction sequences) described thus far that enable continuous access to a data structure are, according to one alternative embodiment, imparted onto a computer readable medium. Examples of such <boundary-data type="line-number">10 </boundary-data>
|
| 220 |
+
media include, but are not limited to, random access memory, read-only memory (ROM), Compact Disk (CD) ROM, Digital Versatile Disk (DVD), floppy disks, hard disk drives and magnetic tape. This computer readable medium, which alone or in combination can constitute a stand-alone product, can be used to convert a general-purpose computing device into a device that supports continuous access to a data structure wherein said <boundary-data type="line-number">15 </boundary-data>
|
| 221 |
+
device is capable of supporting continuous access to a data structure according to the techniques and teachings presented herein. Accordingly, the claims appended hereto are to include such computer readable medium imparted with such instruction sequences that enable execution of the present method and all of the teachings herein described. </p>
|
| 222 |
+
<p id="p-22" num="22">[0012] According to one example embodiment, a system that enables continuous <boundary-data type="line-number">20 </boundary-data>
|
| 223 |
+
access to a data structure includes a first reader process <part-num-ref name="first reader process">255</part-num-ref>
|
| 224 |
+
which is typically stored in the system memory <part-num-ref name="system memory">240.</part-num-ref>
|
| 225 |
+
In yet another example embodiment, the system further includes a lock manager <part-num-ref name="lock manager">250,</part-num-ref>
|
| 226 |
+
which is also stored in the system memory <part-num-ref name="system memory">240.</part-num-ref>
|
| 227 |
+
In yet another alternative example embodiment, the system further includes a second reader process <part-num-ref name="second reader process">260,</part-num-ref>
|
| 228 |
+
which is also stored in the system memory <part-num-ref name="system memory">240.</part-num-ref>
|
| 229 |
+
Also stored in the system memory, <boundary-data type="line-number">25 </boundary-data>
|
| 230 |
+
according to yet another example embodiment, is a writer process <part-num-ref name="writer process">285.</part-num-ref>
|
| 231 |
+
It should further be appreciated that various alternative example embodiments use the system memory <part-num-ref name="system memory">240</part-num-ref>
|
| 232 |
+
to store at least one of a reader count <part-num-ref name="reader count">265,</part-num-ref>
|
| 233 |
+
a first read lock <part-num-ref name="first read lock">270,</part-num-ref>
|
| 234 |
+
a second read lock <part-num-ref name="second read lock">275,</part-num-ref>
|
| 235 |
+
and a write lock <part-num-ref name="write lock">280.</part-num-ref>
|
| 236 |
+
</p>
|
| 237 |
+
<boundary-data type="header">
|
| 238 |
+
<confidence value="8">7</confidence>
|
| 239 |
+
</boundary-data>
|
| 240 |
+
<boundary-data type="header">AppHP-200408085- <confidence value="6">I</confidence>
|
| 241 |
+
-Rev-<confidence value="6">I</confidence>
|
| 242 |
+
<confidence value="22222">a.doc</confidence>
|
| 243 |
+
</boundary-data>
|
| 244 |
+
<boundary-data type="header">Attorney, J. I. <confidence value="222222">J'maev</confidence>
|
| 245 |
+
PATENT </boundary-data>
|
| 246 |
+
<boundary-data type="header">Reg. No. 45,669 HP-200408085-<confidence value="8">1</confidence>
|
| 247 |
+
</boundary-data>
|
| 248 |
+
<boundary-data type="header">Expr. Mail EO 913 084 953 US 200408085-1</boundary-data>
|
| 249 |
+
<boundary-data type="header">September 30, 2005</boundary-data>
|
| 250 |
+
<p id="p-23" num="23">
|
| 251 |
+
<page-break num="8"/>
|
| 252 |
+
[0013] Fig. 7 is a data flow diagram that depicts the internal operation of various alternative example embodiments of a system that enables continuous access to a data structure. According to one example embodiment, a processor <part-num-ref name="processor">200</part-num-ref>
|
| 253 |
+
executes the first reader process <part-num-ref name="first reader process">255.</part-num-ref>
|
| 254 |
+
When executed by the processor <part-num-ref name="processor">200,</part-num-ref>
|
| 255 |
+
the first reader process <part-num-ref name="first reader process">255</part-num-ref>
|
| 256 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 257 |
+
begins processing data stored in a data structure which is typically stored in the main data memory <part-num-ref name="main data memory">215.</part-num-ref>
|
| 258 |
+
In operation, the first reader process <part-num-ref name="first reader process">255,</part-num-ref>
|
| 259 |
+
when executed by the processor <part-num-ref name="processor">200,</part-num-ref>
|
| 260 |
+
minimally causes the processor to acquire a read lock for a data structure stored in the main data memory. Accordingly, the first reader process receives a first read lock <part-num-ref name="first read lock">270.</part-num-ref>
|
| 261 |
+
Once the processor, as it continues to execute the first reader process <part-num-ref name="first reader process">255,</part-num-ref>
|
| 262 |
+
acquires <boundary-data type="line-number">10 </boundary-data>
|
| 263 |
+
the first read lock <part-num-ref name="first read lock">270,</part-num-ref>
|
| 264 |
+
the processor <part-num-ref name="processor">200</part-num-ref>
|
| 265 |
+
creates a local copy of the data structure in a corresponding first cache memory <part-num-ref name="corresponding first cache memory">210.</part-num-ref>
|
| 266 |
+
The processor in this example embodiment then begins engaging in a process using the local copy of the data structure. The processor may engage in any type of application processing and the claims appended hereto are not intended to be limited to any particular application wherein the present method and <boundary-data type="line-number">15 </boundary-data>
|
| 267 |
+
embodiments thereof may be useful. At some point in time, the processor <part-num-ref name="processor">200,</part-num-ref>
|
| 268 |
+
as it continues to execute the first reader process <part-num-ref name="first reader process">255,</part-num-ref>
|
| 269 |
+
is further minimally caused to relinquish the first read lock before it actually completes the process in which it is engaged. Once the first read lock <part-num-ref name="first read lock">270</part-num-ref>
|
| 270 |
+
is relinquished, the processor <part-num-ref name="processor">200,</part-num-ref>
|
| 271 |
+
as it continues to execute the first reader process <part-num-ref name="first reader process">255,</part-num-ref>
|
| 272 |
+
will then reacquire the first read lock at some subsequent point in <boundary-data type="line-number">20 </boundary-data>
|
| 273 |
+
time. Once the processor reacquires the first read lock <part-num-ref name="first read lock">270,</part-num-ref>
|
| 274 |
+
the processor needs to determine if an intervening write lock was granted. Based on this determination, the processor <part-num-ref name="processor">200,</part-num-ref>
|
| 275 |
+
as it continues to execute the first reader process <part-num-ref name="first reader process">255,</part-num-ref>
|
| 276 |
+
will continue to engage in the process which was otherwise suspended when the processor relinquished the first reader lock. The processor <part-num-ref name="processor">200</part-num-ref>
|
| 277 |
+
will continue to engage in the suspended process <boundary-data type="line-number">25 </boundary-data>
|
| 278 |
+
when an intervening write lock was not granted. In the event that an intervening write lock was granted, the processor <part-num-ref name="processor">200,</part-num-ref>
|
| 279 |
+
as it continues to execute the first reader process <part-num-ref name="first reader process">255,</part-num-ref>
|
| 280 |
+
is further minimally caused to refresh the local copy of the data structure. </p>
|
| 281 |
+
<p id="p-24" num="24">[0014] Fig. 7 further illustrates that, according to one alternative example embodiment, the first reader process <part-num-ref name="first reader process">255,</part-num-ref>
|
| 282 |
+
when executed by the processor <part-num-ref name="processor">200,</part-num-ref>
|
| 283 |
+
causes the <boundary-data type="header">
|
| 284 |
+
<confidence value="8">8</confidence>
|
| 285 |
+
</boundary-data>
|
| 286 |
+
<boundary-data type="header">App<confidence value="68">_H</confidence>
|
| 287 |
+
P-200408085-<confidence value="5">1</confidence>
|
| 288 |
+
-Rev-<confidence value="5">I</confidence>
|
| 289 |
+
a.doc </boundary-data>
|
| 290 |
+
<page-break num="9"/>
|
| 291 |
+
<boundary-data type="header">Attorney, J. I. <confidence value="222222">J'maev</confidence>
|
| 292 |
+
PATENT </boundary-data>
|
| 293 |
+
<boundary-data type="header">Reg. No. 45,669 HP-200408085-<confidence value="8">1</confidence>
|
| 294 |
+
</boundary-data>
|
| 295 |
+
<boundary-data type="header">Expr. Mail E<confidence value="5">O</confidence>
|
| 296 |
+
913 084 953 US 200408085-1 </boundary-data>
|
| 297 |
+
<boundary-data type="header">September 30, 2005</boundary-data>
|
| 298 |
+
processor to determine if an intervening write lock was granted by minimally causing the processor to examine a dirty bit <part-num-ref name="dirty bit">271,</part-num-ref>
|
| 299 |
+
which is included in a reacquired read lock <part-num-ref name="reacquired read lock">270.</part-num-ref>
|
| 300 |
+
In yet another alternative example embodiment, the first reader process <part-num-ref name="first reader process">255</part-num-ref>
|
| 301 |
+
further minimally causes the processor to clear the dirty bit <part-num-ref name="dirty bit">271.</part-num-ref>
|
| 302 |
+
Also included in one alternative <boundary-data type="line-number">
|
| 303 |
+
<confidence value="5">5</confidence>
|
| 304 |
+
</boundary-data>
|
| 305 |
+
example embodiment and stored in the system memory <part-num-ref name="system memory">240</part-num-ref>
|
| 306 |
+
is a lock manager <part-num-ref name="lock manager">250.</part-num-ref>
|
| 307 |
+
The lock manager <part-num-ref name="lock manager">250,</part-num-ref>
|
| 308 |
+
when executed by the processor <part-num-ref name="processor">200,</part-num-ref>
|
| 309 |
+
minimally causes the processor to grant a second read lock <part-num-ref name="second read lock">275</part-num-ref>
|
| 310 |
+
to a second reader process <part-num-ref name="second reader process">260.</part-num-ref>
|
| 311 |
+
When the lock manager <part-num-ref name="lock manager">250</part-num-ref>
|
| 312 |
+
acknowledges that the second read lock <part-num-ref name="second read lock">275</part-num-ref>
|
| 313 |
+
has been relinquished, the lock manager <part-num-ref name="lock manager">258,</part-num-ref>
|
| 314 |
+
when executed by the processor, causes the processor to increment a read count <part-num-ref name="read count">265</part-num-ref>
|
| 315 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 316 |
+
which is stored in the system memory <part-num-ref name="system memory">240.</part-num-ref>
|
| 317 |
+
The read lock counter is only incremented when the second process indicates, during the course of relinquishing the second read lock, that it intends to reacquire the second reac lock. When the second reader process <part-num-ref name="second reader process">260</part-num-ref>
|
| 318 |
+
subsequently reacquires the second read lock <part-num-ref name="second read lock">275,</part-num-ref>
|
| 319 |
+
the processor <part-num-ref name="processor">200,</part-num-ref>
|
| 320 |
+
as it continues to execute the lock manager <part-num-ref name="lock manager">250,</part-num-ref>
|
| 321 |
+
is further minimally caused to decrement the read lock <boundary-data type="line-number">15 </boundary-data>
|
| 322 |
+
count <part-num-ref name="read lock count">265.</part-num-ref>
|
| 323 |
+
In this manner, the processor keeps a running tally of the number of read locks outstanding. The number of processes that are waiting to reacquire read locks is used to in yet another alternative example embodiment of a system that enables continuous access to a data structure. In this alternative example embodiment, the processor is caused to determine if an intervening write lock was granted by examining <boundary-data type="line-number">20 </boundary-data>
|
| 324 |
+
the dirty bit <part-num-ref name="dirty bit">271</part-num-ref>
|
| 325 |
+
included in the first read lock <part-num-ref name="first read lock">270.</part-num-ref>
|
| 326 |
+
However, in this alternative example embodiment, the processor <part-num-ref name="processor">200</part-num-ref>
|
| 327 |
+
is caused to clear the dirty bit when the reader count <part-num-ref name="reader count">265</part-num-ref>
|
| 328 |
+
indicates that there are no other read locks waiting to be reacquired. In other words, the first reader process <part-num-ref name="first reader process">255</part-num-ref>
|
| 329 |
+
is the only reader process that is holding a valid read lock. This ensures that the last reader process that was waiting to reacquire a read lock is the only <boundary-data type="line-number">25 </boundary-data>
|
| 330 |
+
process that is allowed to clear the dirty bit <part-num-ref name="dirty bit">271</part-num-ref>
|
| 331 |
+
included in the first read lock <part-num-ref name="first read lock">270.</part-num-ref>
|
| 332 |
+
It should be appreciated that this first read lock <part-num-ref name="first read lock 270. It should be appreciated that this first read lock">270</part-num-ref>
|
| 333 |
+
is reacquire by the first reader process <part-num-ref name="first reader process">255</part-num-ref>
|
| 334 |
+
after the first reader process <part-num-ref name="first reader process">2<confidence value="66">55</confidence>
|
| 335 |
+
</part-num-ref>
|
| 336 |
+
relinquishes the first read lock prior to completing a process which requires continuous access to the data structure stored in the local cache, which is servicing a processor executing the first reader process <part-num-ref name="first reader process">2<confidence value="668">55.</confidence>
|
| 337 |
+
</part-num-ref>
|
| 338 |
+
</p>
|
| 339 |
+
<boundary-data type="header">
|
| 340 |
+
<confidence value="8">9</confidence>
|
| 341 |
+
</boundary-data>
|
| 342 |
+
<boundary-data type="header">AppHP-200408085-<confidence value="5">1</confidence>
|
| 343 |
+
-Rev- <confidence value="6">I</confidence>
|
| 344 |
+
<confidence value="8">a</confidence>
|
| 345 |
+
.doc </boundary-data>
|
| 346 |
+
<boundary-data type="header">Attorney, J. I. <confidence value="222222">J'maev</confidence>
|
| 347 |
+
PATENT </boundary-data>
|
| 348 |
+
<boundary-data type="header">Reg. No. 45,669 HP-200408085-<confidence value="8">1</confidence>
|
| 349 |
+
</boundary-data>
|
| 350 |
+
<boundary-data type="header">Expr. Mail <confidence value="5">E</confidence>
|
| 351 |
+
O 913 084 953 US 200408085-1 </boundary-data>
|
| 352 |
+
<boundary-data type="header">September 30, 2005</boundary-data>
|
| 353 |
+
<p id="p-25" num="25">
|
| 354 |
+
<page-break num="10"/>
|
| 355 |
+
[0015] In yet another alternative example embodiment, a system that enables continuous access to data structure further includes a writer process <part-num-ref name="writer process">285.</part-num-ref>
|
| 356 |
+
In this alternative example embodiment, the lock manager <part-num-ref name="lock manager">250,</part-num-ref>
|
| 357 |
+
when executed by the processor <part-num-ref name="processor">200,</part-num-ref>
|
| 358 |
+
minimally causes the processor to grant a write lock <part-num-ref name="write lock">280</part-num-ref>
|
| 359 |
+
to the writer process <part-num-ref name="writer process">285.</part-num-ref>
|
| 360 |
+
It <boundary-data type="line-number">
|
| 361 |
+
<confidence value="5">5</confidence>
|
| 362 |
+
</boundary-data>
|
| 363 |
+
will be appreciated that the processor <part-num-ref name="processor">200</part-num-ref>
|
| 364 |
+
in this alternative example embodiment also sets a dirty bit <part-num-ref name="dirty bit">271</part-num-ref>
|
| 365 |
+
included in a first read lock <part-num-ref name="first read lock">270</part-num-ref>
|
| 366 |
+
(or other read lock's granted by the lock manager <part-num-ref name="lock manager">250)</part-num-ref>
|
| 367 |
+
once a write lock <part-num-ref name="write lock">280</part-num-ref>
|
| 368 |
+
is granted to the writer process <part-num-ref name="writer process">285.</part-num-ref>
|
| 369 |
+
The writer process <part-num-ref name="writer process">285</part-num-ref>
|
| 370 |
+
is then able to interact and modify the data structure <part-num-ref name="data structure">290</part-num-ref>
|
| 371 |
+
stored in the data memory <part-num-ref name="data memory">215.</part-num-ref>
|
| 372 |
+
It should also be appreciated that the lock manager <part-num-ref name="lock manager">250</part-num-ref>
|
| 373 |
+
of this alternative <boundary-data type="line-number">10 </boundary-data>
|
| 374 |
+
example embodiment will not allow the processor to issue a write lock <part-num-ref name="write lock">280</part-num-ref>
|
| 375 |
+
there are one or more read locks outstanding. </p>
|
| 376 |
+
<p id="p-26" num="26">[0016] While the present method and apparatus has been described in terms of several alternative and exemplary embodiments, it is contemplated that alternatives, modifications, permutations, and equivalents thereof will become apparent to those <boundary-data type="line-number">15 </boundary-data>
|
| 377 |
+
skilled in the art upon a reading of the specification and study of the drawings. It is therefore intended that the true spirit and scope of the claims appended hereto include all such alternatives, modifications, permutations, and equivalents. </p>
|
| 378 |
+
<boundary-data type="header">
|
| 379 |
+
<confidence value="88">10</confidence>
|
| 380 |
+
</boundary-data>
|
| 381 |
+
<boundary-data type="header">AppHP-200408085<confidence value="5">-</confidence>
|
| 382 |
+
<confidence value="6">I</confidence>
|
| 383 |
+
-Rev- <confidence value="6">I</confidence>
|
| 384 |
+
<confidence value="22222">a.doc</confidence>
|
| 385 |
+
</boundary-data>
|
| 386 |
+
</description>
|
| 387 |
+
</us-patent-application>
|
| 388 |
+
|
applicant/11277545.xml
ADDED
|
@@ -0,0 +1,841 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>11277545</doc-number>
|
| 8 |
+
<date>2006-03-27</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<boundary-data type="header">DOCKET NO: <confidence value="22222222">SEMCPSO5</confidence>
|
| 14 |
+
0663US1 </boundary-data>
|
| 15 |
+
<heading id="h-1">TITLE: ELECTRONIC EQUIPMENT AND SERVICE PROVIDING PERSONALIZED</heading>
|
| 16 |
+
<heading id="h-2">CALL FEATURES</heading>
|
| 17 |
+
<heading id="h-3">TECHNICAL FIELD OF THE INVENTION</heading>
|
| 18 |
+
<p id="p-1" num="1">
|
| 19 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 20 |
+
The present invention relates generally to electronic equipment, and more specifically to a service for providing personalized call features to electronic equipment within a communications network. </p>
|
| 21 |
+
<heading id="h-4">DESCRIPTION OF THE RELATED ART</heading>
|
| 22 |
+
<p id="p-2" num="2">Electronic equipment such as portable electronic devices have been popular for decades, and yet <boundary-data type="line-number">10 </boundary-data>
|
| 23 |
+
continue to increase in popularity. In the communications area, advances in electronic equipment such as digital telephones, mobile phones, pagers, communicators, electronic organizers, personal digital assistants (PDAs), smartphones, etc. have made it possible for seemingly everyone to own one or more different devices. </p>
|
| 24 |
+
<p id="p-3" num="3">In fact, users are increasingly viewing electronic equipment such a mobile phone, etc., as an item of <boundary-data type="line-number">15 </boundary-data>
|
| 25 |
+
preference. Many different types of electronic equipment today allow the user to customize their experience using the electronic equipment. For example, the user of a mobile phone may select particular wallpapers, screen savers, ring tones, banners, casing colors, etc. Each selection further customizes the mobile phone to the likes and preferences of the user. The mobile phone has therefore increasingly become an extension of the user's own personality. </p>
|
| 26 |
+
<p id="p-4" num="4">
|
| 27 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 28 |
+
Despite such past improvements in the user's ability to customize his or her experience, there still have been limitations. For example, the user's selection of wallpaper, ring tone, banners, casing color, etc., personalizes a mobile phone from the perspective of the user. However, such selections do little to share or extend the user's personality with a called or calling device on another end of a call involving the user's mobile phone. The called or calling device is unable to see or hear the user's wallpaper selection, ringtone, <boundary-data type="line-number">25 </boundary-data>
|
| 29 |
+
etc. </p>
|
| 30 |
+
<p id="p-5" num="5">In view of the aforementioned shortcomings associated with existing electronic equipment such as mobile phones, there is a strong need in the art for electronic equipment and service that personalizes the user even with respect to a called/calling device at the other end of a call.</p>
|
| 31 |
+
<boundary-data type="header">
|
| 32 |
+
<confidence value="8">1</confidence>
|
| 33 |
+
</boundary-data>
|
| 34 |
+
<boundary-data type="header">DOCKET NO: <confidence value="22222222">SEMCPSO5</confidence>
|
| 35 |
+
0663US1 </boundary-data>
|
| 36 |
+
<heading id="h-5">SUMMARY</heading>
|
| 37 |
+
<p id="p-6" num="6">
|
| 38 |
+
<page-break num="2"/>
|
| 39 |
+
According to one aspect of the invention, a server provides call hold f<confidence value="8">u</confidence>
|
| 40 |
+
nctions to a communications network th<confidence value="8">r</confidence>
|
| 41 |
+
ough which a call between a user electronic equipment and one or more <confidence value="22222222222222">called/calling</confidence>
|
| 42 |
+
devices is routed. The server includes a network interface that connects the server to the communications network, and <boundary-data type="line-number">5 </boundary-data>
|
| 43 |
+
a controller that is coupled to the communications network via the network interface. The controller is operatively configured to communicate a media object to at least one of the one or more <confidence value="22222222222222">called/calling</confidence>
|
| 44 |
+
devices in response to the user electronic equipment placing the call on hold. </p>
|
| 45 |
+
<p id="p-7" num="7">According to another aspect, the controller is operatively configured to communicate the media object to the at least one of the one or more <confidence value="22222222222222">called/calling</confidence>
|
| 46 |
+
devices using a same network connection within <boundary-data type="line-number">10 </boundary-data>
|
| 47 |
+
the communications network upon which the call has been established. </p>
|
| 48 |
+
<p id="p-8" num="8">In accordance with another aspect, the controller is operatively configured to stop communicating the media object in response to the user electronic equipment having taken the call off hold.</p>
|
| 49 |
+
<p id="p-9" num="9">With yet another aspect, the controller is operative to stream the media object.</p>
|
| 50 |
+
<p id="p-10" num="10">In still another aspect, the controller is operative to reproduces the media object as an audio signal <boundary-data type="line-number">15 </boundary-data>
|
| 51 |
+
when communicating the media object. </p>
|
| 52 |
+
<p id="p-11" num="11">According to yet another aspect, the server further includes a library of media objects, and the controller enables a user of the user electronic equipment to select from the library the communicated media object..</p>
|
| 53 |
+
<p id="p-12" num="12">According to still another aspect, the server further includes a library of media objects, and the <boundary-data type="line-number">20 </boundary-data>
|
| 54 |
+
controller communicates the media object selected from among the library of media objects as a function of an identity of the <confidence value="22222222222222">called/calling</confidence>
|
| 55 |
+
device to which the media object is communicated. </p>
|
| 56 |
+
<p id="p-13" num="13">In accordance with yet another aspect, the server further includes a library of media objects, and the controller communicates the media object selected generally randomly from among the library of media objects.</p>
|
| 57 |
+
<p id="p-14" num="14">
|
| 58 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 59 |
+
In accordance with still another aspect, the media object comprises an audio object. </p>
|
| 60 |
+
<p id="p-15" num="15">According to another aspect, the media object comprises a visual object.</p>
|
| 61 |
+
<p id="p-16" num="16">According to yet another aspect, the media object represents an advertisement.</p>
|
| 62 |
+
<p id="p-17" num="17">With yet another aspect, the controller is further configured to provide conference call functions with respect to the call between a user electronic equipment and one or more <confidence value="22222222222222">called/calling</confidence>
|
| 63 |
+
devices. </p>
|
| 64 |
+
<boundary-data type="header">
|
| 65 |
+
<confidence value="8">2</confidence>
|
| 66 |
+
</boundary-data>
|
| 67 |
+
<boundary-data type="header">DOCKET NO: <confidence value="22222222">SEMCPSO5</confidence>
|
| 68 |
+
0663US1 </boundary-data>
|
| 69 |
+
<p id="p-18" num="18">
|
| 70 |
+
<page-break num="3"/>
|
| 71 |
+
Yet with another aspect, the controller communicates the media object to each of the one or more called/calling devices participating in the conference call. </p>
|
| 72 |
+
<p id="p-19" num="19">According to still another aspect, the controller communicates the media object to the at least one of the one or more <confidence value="22222222222222">called/calling</confidence>
|
| 73 |
+
devices in response to receiving a request from the user electronic equipment <boundary-data type="line-number">5 </boundary-data>
|
| 74 |
+
indicating that the call has been placed on hold. </p>
|
| 75 |
+
<p id="p-20" num="20">In accordance with another aspect, the request includes criteria based upon which the controller determines the media object to communicate among a library of media objects.</p>
|
| 76 |
+
<p id="p-21" num="21">According to still another aspect, a user electronic equipment designed for use in combination with a server as described above is provided. The user electronic equipment includes call circuitry that enables <boundary-data type="line-number">10 </boundary-data>
|
| 77 |
+
the user electronic equipment to establish a call with a called/calling device, hold circuitry that enables the user electronic equipment to place the call established with the called/calling device on hold, and a controller operative in conjunction with the call circuitry and hold circuitry to communicate a request to the server indicating that the call is placed on hold. </p>
|
| 78 |
+
<p id="p-22" num="22">In accordance with another aspect, the request includes criteria based upon which the controller <boundary-data type="line-number">15 </boundary-data>
|
| 79 |
+
determines the media object to communicate among a library of media objects. </p>
|
| 80 |
+
<p id="p-23" num="23">According to another aspect of the invention, a server is presented for providing audio-video voicemail functions to a communications network th<confidence value="8">r</confidence>
|
| 81 |
+
ough which a call between a user electronic equipment and a calling device is routed. The server includes a network interface that connects the server to the communications network. In addition, the server includes a controller that is coupled to the communications <boundary-data type="line-number">20 </boundary-data>
|
| 82 |
+
network via the network interface. The controller is operatively configured to receive audio-video mail from the calling device when the user electronic equipment does not answer the call. </p>
|
| 83 |
+
<p id="p-24" num="24">In yet another aspect, the controller is operatively configured to push user details to the calling device in addition to receiving the audio-video mail.</p>
|
| 84 |
+
<p id="p-25" num="25">In still another aspect, the controller is operatively configured to push the audio-video mail to the <boundary-data type="line-number">25 </boundary-data>
|
| 85 |
+
user electronic equipment. </p>
|
| 86 |
+
<p id="p-26" num="26">To the accomplishment of the foregoing and related ends, the invention, then, comprises the features hereinafter f<confidence value="8">u</confidence>
|
| 87 |
+
lly described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative embodiments of the invention. These embodiments are indicative, however, of but a few of the various ways in which the principles of the <boundary-data type="line-number">30 </boundary-data>
|
| 88 |
+
invention may be employed. Other objects, advantages and novel features of the invention will become apparent from the following detailed description of the invention when considered in conjunction with the drawings. </p>
|
| 89 |
+
<boundary-data type="header">
|
| 90 |
+
<confidence value="8">3</confidence>
|
| 91 |
+
</boundary-data>
|
| 92 |
+
<boundary-data type="header">DOCKET NO: <confidence value="22222222">SEMCPSO5</confidence>
|
| 93 |
+
0663US1 </boundary-data>
|
| 94 |
+
<p id="p-27" num="27">
|
| 95 |
+
<page-break num="4"/>
|
| 96 |
+
It should be emphasized that the term "comprises/comprising" when used in this specification is taken to specify the presence of stated features, integers, steps or components but does not preclude the presence or addition of one or more other features, integers, steps, components or groups thereof<confidence value="5">.</confidence>
|
| 97 |
+
</p>
|
| 98 |
+
<heading id="h-6">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
|
| 99 |
+
<p id="p-28" num="28">
|
| 100 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 101 |
+
Fig. 1 is an exemplary diagram of one or more hold servers provided in a communications network in accordance with an embodiment of the present invention; </p>
|
| 102 |
+
<p id="p-29" num="29">Fig. 2A is a perspective view of an exemplary mobile phone in accordance with an embodiment of the present invention;</p>
|
| 103 |
+
<p id="p-30" num="30">
|
| 104 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 105 |
+
Fig. 2B is a perspective view of an exemplary mobile phone representing a called/calling device in accordance with an embodiment of the present invention; </p>
|
| 106 |
+
<p id="p-31" num="31">Fig. 2C is a perspective view of an exemplary mobile phone representing a called/calling device in accordance with another embodiment of the present invention;</p>
|
| 107 |
+
<p id="p-32" num="32">Fig. 2D is a perspective view of an exemplary mobile phone representing a called/calling device in <boundary-data type="line-number">15 </boundary-data>
|
| 108 |
+
accordance with still another embodiment of the present invention; </p>
|
| 109 |
+
<p id="p-33" num="33">Fig. 2E is a perspective view of an exemplary mobile phone representing a called/calling device in accordance with yet another embodiment of the present invention;</p>
|
| 110 |
+
<p id="p-34" num="34">Fig. 2F is a perspective view of an exemplary mobile phone representing a called/calling device in accordance with still yet an embodiment of the present invention;</p>
|
| 111 |
+
<p id="p-35" num="35">
|
| 112 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 113 |
+
Fig. 3 is a block diagram of an exemplary mobile phone in accordance with an embodiment of the present invention; </p>
|
| 114 |
+
<p id="p-36" num="36">Figs. 4A, 4B and 4C represent exemplary displays on the mobile phone of Fig. 3 for selecting personalized caller hold functions in accordance with an embodiment of the present invention;</p>
|
| 115 |
+
<p id="p-37" num="37">Fig. 5 is a block diagram of an exemplary hold server in accordance with an embodiment of the <boundary-data type="line-number">25 </boundary-data>
|
| 116 |
+
present invention; </p>
|
| 117 |
+
<p id="p-38" num="38">Fig. 6 is an exemplary flowchart suitable for programming a mobile phone to request the hold server to communicate selected audio <confidence value="222222">and/or</confidence>
|
| 118 |
+
video to a <confidence value="22222222222222">called/calling</confidence>
|
| 119 |
+
device while a call is placed on hold; </p>
|
| 120 |
+
<p id="p-39" num="39">Fig. 7 is an exemplary flowchart suitable for programming a hold server to communicate selected audio <confidence value="222222">and/or</confidence>
|
| 121 |
+
video to a <confidence value="22222222222222">called/calling</confidence>
|
| 122 |
+
device in response to a user mobile phone placing a call on hold; </p>
|
| 123 |
+
<boundary-data type="header">
|
| 124 |
+
<confidence value="8">4</confidence>
|
| 125 |
+
</boundary-data>
|
| 126 |
+
<boundary-data type="header">DOCKET NO: SEMCPS<confidence value="56">05</confidence>
|
| 127 |
+
0663U<confidence value="68">S1</confidence>
|
| 128 |
+
</boundary-data>
|
| 129 |
+
<p id="p-40" num="40">
|
| 130 |
+
<page-break num="5"/>
|
| 131 |
+
Fig. 8 is an exemplary flowchart suitable for programming a voicemail server to receive and forward audio-video voicemail messages from a calling device to a user's mobile phone; and Figs. 9A, 9B and 9C represent exemplary displays on the mobile phone of Fig. 3 for selecting audio-video mail hold functions in accordance with an embodiment of the present invention. </p>
|
| 132 |
+
<p id="p-41" num="41">
|
| 133 |
+
<boundary-data type="line-number">
|
| 134 |
+
<confidence value="8">5</confidence>
|
| 135 |
+
</boundary-data>
|
| 136 |
+
</p>
|
| 137 |
+
<heading id="h-7">DETAILED DESCRIPTION OF EMBODIMENTS</heading>
|
| 138 |
+
<p id="p-42" num="42">The present invention will now be described with reference to the drawings, wherein like reference numerals are used to refer to like elements throughout.</p>
|
| 139 |
+
<p id="p-43" num="43">The term "electronic equipment" as referred to herein includes various types of communication <boundary-data type="line-number">10 </boundary-data>
|
| 140 |
+
equipment such as conventional public switched telephone network (PSTN) equipment (e.g., land phones, etc.) as well as portable radio communication equipment. The term "portable radio communication equipment", also referred to herein as a "mobile radio terminal", includes all equipment such as mobile phones, pagers, communicators, e.g., electronic organizers, personal digital assistants (PDAs), smartphones or the like. In the present application, the invention is described primarily in the context of a mobile phone <boundary-data type="line-number">15 </boundary-data>
|
| 141 |
+
communications network. However, it will be appreciated that the invention is not intended to be limited to a mobile phone communications network. The present invention relates to any type of electronic equipment within a corresponding communications network. </p>
|
| 142 |
+
<p id="p-44" num="44">Referring initially to Fig. 1, the present invention is exemplified as part of a mobile phone communications network <part-num-ref name="mobile phone communications network">10.</part-num-ref>
|
| 143 |
+
As an example, the communications network <part-num-ref name="communications network">10</part-num-ref>
|
| 144 |
+
includes one or more mobile <boundary-data type="line-number">20 </boundary-data>
|
| 145 |
+
phone service providers <part-num-ref name="includes one or more mobile phone service providers">12.</part-num-ref>
|
| 146 |
+
Each service provider <part-num-ref name="includes one or more mobile phone service providers 12. Each service provider">12</part-num-ref>
|
| 147 |
+
may be any of a variety of different providers offering mobile phone service either currently or in the future. For example, Service Provider A may represent a provider such as Verizon Wireless, etc., and Service Provider B may represent a different provider such as T-Mobile, etc. Each service provider <part-num-ref name="different provider such as T-Mobile, etc. Each service provider">12</part-num-ref>
|
| 148 |
+
provides wireless communication service to subscribers of the service. Fig. 1 illustrates how each service provider <part-num-ref name="illustrates how each service provider">12</part-num-ref>
|
| 149 |
+
provides wireless communication service to users of <boundary-data type="line-number">25 </boundary-data>
|
| 150 |
+
mobile phones <part-num-ref name="provides wireless communication service to users of mobile phones">16</part-num-ref>
|
| 151 |
+
within the region of the provider <part-num-ref name="provider">12.</part-num-ref>
|
| 152 |
+
Such regions are defined in a cellular wireless communications network, for example, by the geographical locations of cellular towers <part-num-ref name="geographical locations of cellular towers">18</part-num-ref>
|
| 153 |
+
as is known. </p>
|
| 154 |
+
<p id="p-45" num="45">The particular wireless communications networks of the service providers <part-num-ref name="service providers">12</part-num-ref>
|
| 155 |
+
may be expanded via appropriate gateways to include other networks in order to form the overall communications network <part-num-ref name="overall communications network">10.</part-num-ref>
|
| 156 |
+
</p>
|
| 157 |
+
<p id="p-46" num="46">For example, the service providers <part-num-ref name="service providers">12</part-num-ref>
|
| 158 |
+
may each be linked to the Internet <part-num-ref name="Internet">20</part-num-ref>
|
| 159 |
+
or other wide area network(s) <boundary-data type="line-number">30 </boundary-data>
|
| 160 |
+
(WAN(s)) via an appropriate gateway <part-num-ref name="appropriate gateway">22.</part-num-ref>
|
| 161 |
+
In addition, or in the alternative, each of the service providers <part-num-ref name="service providers">12</part-num-ref>
|
| 162 |
+
may be linked to the conventional PSTN <part-num-ref name="conventional PSTN">24</part-num-ref>
|
| 163 |
+
by way of an appropriate gateway <part-num-ref name="appropriate gateway">26.</part-num-ref>
|
| 164 |
+
As is conventional, the mobile phone communications network <part-num-ref name="mobile phone communications network">10</part-num-ref>
|
| 165 |
+
of Fig. 1 allows a mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 166 |
+
to call or receive calls from another mobile phone via communications routed through the service provider network(s), the PSTN, the <boundary-data type="header">
|
| 167 |
+
<confidence value="8">5</confidence>
|
| 168 |
+
</boundary-data>
|
| 169 |
+
<page-break num="6"/>
|
| 170 |
+
<boundary-data type="header">DOCKET NO: SEMCPS<confidence value="66">05</confidence>
|
| 171 |
+
0663US1 </boundary-data>
|
| 172 |
+
Internet, etc., or any combination thereof<confidence value="5">.</confidence>
|
| 173 |
+
Thus, the communications network <part-num-ref name="communications network">10</part-num-ref>
|
| 174 |
+
of the present invention can have virtually any structure represented by one or more networks alone or in combination. </p>
|
| 175 |
+
<p id="p-47" num="47">In accordance with the present invention, one or more video conference and/or hold servers <part-num-ref name="present invention, one or more video conference and/or hold servers">30</part-num-ref>
|
| 176 |
+
are included within the communications network <part-num-ref name="communications network">10.</part-num-ref>
|
| 177 |
+
The servers <part-num-ref name="servers">30</part-num-ref>
|
| 178 |
+
may be included directly within the <boundary-data type="line-number">5 </boundary-data>
|
| 179 |
+
network of the service providers <part-num-ref name="service providers">12,</part-num-ref>
|
| 180 |
+
or accessible to the service providers via the Internet <part-num-ref name="Internet">20,</part-num-ref>
|
| 181 |
+
the PSTN <part-num-ref name="PSTN">24,</part-num-ref>
|
| 182 |
+
etc. Voice and data communications between the different individual networks <part-num-ref name="different individual networks">12,</part-num-ref>
|
| 183 |
+
<part-num-ref name="different individual networks 12,">20,</part-num-ref>
|
| 184 |
+
<part-num-ref name="different individual networks 12, 20,">24</part-num-ref>
|
| 185 |
+
and the mobile phones <part-num-ref name="mobile phones">16</part-num-ref>
|
| 186 |
+
may be carried out using conventional communication protocols currently available within mobile networks (e.g., as part of conventional voice communications, web access, video casting, etc.). </p>
|
| 187 |
+
<p id="p-48" num="48">As will be described in more detail below, the servers <part-num-ref name="servers">30</part-num-ref>
|
| 188 |
+
are each capable of providing <boundary-data type="line-number">10 </boundary-data>
|
| 189 |
+
videoconferencing and/or call hold functions within the communications network <part-num-ref name="communications network">10.</part-num-ref>
|
| 190 |
+
According to one embodiment, the user of a mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 191 |
+
may place a call on hold between the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 192 |
+
and a <confidence value="22222222222222">called/calling</confidence>
|
| 193 |
+
device in the form of another mobile phone <part-num-ref name="form of another mobile phone">16</part-num-ref>
|
| 194 |
+
(or other type of electronic equipment). By placing the call on hold, the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 195 |
+
of the user transmits a request to a corresponding server <part-num-ref name="corresponding server">30</part-num-ref>
|
| 196 |
+
requesting that the server <part-num-ref name="server">30</part-num-ref>
|
| 197 |
+
transmit to the <confidence value="22222222222222">called/calling</confidence>
|
| 198 |
+
device(s) a personalized media object while the <boundary-data type="line-number">15 </boundary-data>
|
| 199 |
+
call is on hold. As referred to herein, a "media object<confidence value="5">"</confidence>
|
| 200 |
+
can be any audio and/or visual data file or reproduction thereof<confidence value="5">.</confidence>
|
| 201 |
+
The audio may be a personalized message, a favorite song, a favorite comedy routine, etc. The visual data file may be a video clip, still image, slideshow of images, etc. </p>
|
| 202 |
+
<p id="p-49" num="49">For example, the server <part-num-ref name="server">30</part-num-ref>
|
| 203 |
+
may be configured to stream a media object to the <confidence value="22222222222222">called/calling</confidence>
|
| 204 |
+
device via the same network connection upon which the call has been established. This allows the <confidence value="22222222222222">called/calling</confidence>
|
| 205 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 206 |
+
device to reproduce the media object selected by the user of the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 207 |
+
and thereby enjoy listening to and/or watching a personalized call hold message while waiting for the user of the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 208 |
+
to take the call off hold. The media object provided by the server <part-num-ref name="server">30</part-num-ref>
|
| 209 |
+
thereby becomes a further extension of the personality of the user of the mobile phone <part-num-ref name="mobile phone">16.</part-num-ref>
|
| 210 |
+
</p>
|
| 211 |
+
<p id="p-50" num="50">According to another example, in the case of an audio-based media object, the server <part-num-ref name="server">30</part-num-ref>
|
| 212 |
+
may <boundary-data type="line-number">25 </boundary-data>
|
| 213 |
+
simply reproduce the media object and communicate the audio message to the <confidence value="22222222222222">called/calling</confidence>
|
| 214 |
+
device as part of the standard voice communications. This allows a called/calling device to receive the audio message without necessarily having to reproduce the media object itself<confidence value="5">.</confidence>
|
| 215 |
+
Of course, with the relatively recent introduction of 3G technology and the ongoing improvements of mobile phones, many mobile phones are already capable, and soon almost every mobile phone will be capable of receiving and reproducing media <boundary-data type="line-number">30 </boundary-data>
|
| 216 |
+
objects whether the media objects be provided as complete digital files, streamed, etc. </p>
|
| 217 |
+
<p id="p-51" num="51">In accordance with still another aspect of the invention, the servers <part-num-ref name="servers">30</part-num-ref>
|
| 218 |
+
may each be capable of receiving combination audio-video mail messages. For example, if a device within the network <part-num-ref name="network">10</part-num-ref>
|
| 219 |
+
calls a user mobile phone <part-num-ref name="user mobile phone">16</part-num-ref>
|
| 220 |
+
and the user is unable to answer, the server <part-num-ref name="server">30</part-num-ref>
|
| 221 |
+
receives a message comprising both audio and video data. The server <part-num-ref name="server">30</part-num-ref>
|
| 222 |
+
can subsequently push details regarding the user to the <confidence value="22222222222222">called/calling</confidence>
|
| 223 |
+
<part-num-ref name="called/calling">35</part-num-ref>
|
| 224 |
+
device using known push technology previously associated with email functions using mobile phones. Such <boundary-data type="header">
|
| 225 |
+
<confidence value="8">6</confidence>
|
| 226 |
+
</boundary-data>
|
| 227 |
+
<page-break num="7"/>
|
| 228 |
+
<boundary-data type="header">DOCKET NO: <confidence value="22222222">SEMCPSO5</confidence>
|
| 229 |
+
0663U<confidence value="68">S1</confidence>
|
| 230 |
+
</boundary-data>
|
| 231 |
+
user details again are useful for extending the personality of the user. Moreover, the server <part-num-ref name="server">30</part-num-ref>
|
| 232 |
+
can push the audio-video mail to the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 233 |
+
of the user so as to be available promptly to the user. </p>
|
| 234 |
+
<p id="p-52" num="52">Further, the servers <part-num-ref name="servers">30</part-num-ref>
|
| 235 |
+
may each be capable of providing conventional video conference capabilities. As is known, a video conference server provided within the service provider <part-num-ref name="service provider">12</part-num-ref>
|
| 236 |
+
network or <boundary-data type="line-number">5 </boundary-data>
|
| 237 |
+
elsewhere can be utilized to combine three or more mobile phones <part-num-ref name="network or elsewhere can be utilized to combine three or more mobile phones">16</part-num-ref>
|
| 238 |
+
or other <confidence value="22222222222222">called/calling</confidence>
|
| 239 |
+
devices into a common conference call. Moreover, with the advent of 3G technology and increased data transfer rates, video conference calls including both audio and video are now available. </p>
|
| 240 |
+
<p id="p-53" num="53">For sake of convenience, the servers <part-num-ref name="servers">30</part-num-ref>
|
| 241 |
+
described herein are each capable of serving as a hold server for call hold functions, an audio-video mail server for audio-video mail functions and a video <boundary-data type="line-number">10 </boundary-data>
|
| 242 |
+
conference server for videoconference functions. However, those having ordinary skill in the art will appreciate that one or more dedicated server(s) could instead handle the respective functions without departing from the scope of the invention. </p>
|
| 243 |
+
<p id="p-54" num="54">Fig. 2A illustrates a mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 244 |
+
in accordance with the present invention. The mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 245 |
+
as described herein can represent both a user mobile phone <part-num-ref name="user mobile phone">16</part-num-ref>
|
| 246 |
+
in accordance with the present invention, <boundary-data type="line-number">15 </boundary-data>
|
| 247 |
+
or a called or calling mobile phone <part-num-ref name="called or calling mobile phone">16</part-num-ref>
|
| 248 |
+
between which a call with the user mobile phone <part-num-ref name="user mobile phone">16</part-num-ref>
|
| 249 |
+
is established. </p>
|
| 250 |
+
<p id="p-55" num="55">Those having ordinary skill in the art will find it readily apparent from the context of the description provided herein whether the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 251 |
+
is being referred to as a user mobile phone <part-num-ref name="user mobile phone">16</part-num-ref>
|
| 252 |
+
or a <confidence value="22222222222222">called/calling</confidence>
|
| 253 |
+
device mobile phone <part-num-ref name="called/calling device mobile phone">16.</part-num-ref>
|
| 254 |
+
Moreover, although the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 255 |
+
of the present invention may have the features described herein, those with ordinary skill will be appreciate that the <confidence value="22222222222222">called/calling</confidence>
|
| 256 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 257 |
+
device mobile phone <part-num-ref name="called/calling device mobile phone">16</part-num-ref>
|
| 258 |
+
need not necessarily have the same features. A single type mobile phone is described herein merely for convenience. </p>
|
| 259 |
+
<p id="p-56" num="56">The mobile phone 16 as shown in Fig. 2A has a "brick" or "block" design type housing, but it will be appreciated that other type housings such as clamshell or slide-type housings may be utilized without departing from the scope of the invention.</p>
|
| 260 |
+
<p id="p-57" num="57">
|
| 261 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 262 |
+
The mobile phone 16 includes a display <part-num-ref name="display">34</part-num-ref>
|
| 263 |
+
and keypad <part-num-ref name="and keypad">36.</part-num-ref>
|
| 264 |
+
As is conventional, the display <part-num-ref name="display">34</part-num-ref>
|
| 265 |
+
displays information to a user such as operating state, time, phone numbers, contact information, various navigational menus, etc., which enable the user to utilize the various features of the mobile phone <part-num-ref name="mobile phone">16.</part-num-ref>
|
| 266 |
+
</p>
|
| 267 |
+
<p id="p-58" num="58">Similarly, the keypad <part-num-ref name="keypad">36</part-num-ref>
|
| 268 |
+
may be conventional in that it provides for a variety of user input operations. For example, the keypad <part-num-ref name="keypad">36</part-num-ref>
|
| 269 |
+
typically includes alphanumeric keys for allowing entry of alphanumeric <boundary-data type="line-number">30 </boundary-data>
|
| 270 |
+
information such as telephone numbers, phone lists, contact information, notes, etc. In addition, the keypad <part-num-ref name="keypad">36</part-num-ref>
|
| 271 |
+
typically includes special function keys such as a "call send" key <part-num-ref name=""call send" key">38</part-num-ref>
|
| 272 |
+
for initiating or answering a call, and a "call end" key <part-num-ref name=""call end" key">40</part-num-ref>
|
| 273 |
+
for ending<confidence value="5">,</confidence>
|
| 274 |
+
or "hanging up" a call. Special function keys may also include menu navigation keys 42a, 42b and 42<confidence value="66">c,</confidence>
|
| 275 |
+
for example, for navigating through a menu displayed on the display <part-num-ref name="display">34</part-num-ref>
|
| 276 |
+
to select different phone functions, profiles, settings, etc., as is conventional. Other keys included in the <boundary-data type="header">
|
| 277 |
+
<confidence value="8">7</confidence>
|
| 278 |
+
</boundary-data>
|
| 279 |
+
<page-break num="8"/>
|
| 280 |
+
<boundary-data type="header">DOCKET NO: SEMCPS<confidence value="56">05</confidence>
|
| 281 |
+
0663US1 </boundary-data>
|
| 282 |
+
keypad <part-num-ref name="keypad">36</part-num-ref>
|
| 283 |
+
may include a volume key (not shown), on/off power key (also not shown), as well as various other keys such as a web browser launch key, camera key, etc. </p>
|
| 284 |
+
<p id="p-59" num="59">The mobile phone keypad 36 also includes a "hold" function key <part-num-ref name=""hold" function key">44</part-num-ref>
|
| 285 |
+
for placing a call on hold. As is well known, sometimes the user of the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 286 |
+
desires to place the party or parties at the other <boundary-data type="line-number">5 </boundary-data>
|
| 287 |
+
end of a call on hold. By placing a call on "hold", the <confidence value="22222222222222">called/calling</confidence>
|
| 288 |
+
device(s) at the other end of a conventional voice call do not receive audio from the user's mobile phone <part-num-ref name="user's mobile phone">16.</part-num-ref>
|
| 289 |
+
In the case of a video phone call in which both audio and video signals are exchanged between the user's mobile phone <part-num-ref name="user's mobile phone">16</part-num-ref>
|
| 290 |
+
and the <confidence value="22222222222222">called/calling</confidence>
|
| 291 |
+
device(s), by placing a call on "hold" at least one or both of the audio and video from the user's mobile phone <part-num-ref name="user's mobile phone">16</part-num-ref>
|
| 292 |
+
is not sent to the <confidence value="22222222222222">called/calling</confidence>
|
| 293 |
+
device(s). In other words, the <confidence value="22222222222222">called/calling</confidence>
|
| 294 |
+
device(s) <boundary-data type="line-number">10 </boundary-data>
|
| 295 |
+
either receive video but no audio from the user's mobile phone 16; receive audio but no video; or do not receive audio or video. </p>
|
| 296 |
+
<p id="p-60" num="60">In the embodiment of Fig. 2A the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 297 |
+
includes a dedicated "hold" function key <part-num-ref name="dedicated "hold" function key">44</part-num-ref>
|
| 298 |
+
that toggles a call between "on hold" and "off hold". Alternatively, the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 299 |
+
may associate more than one function with a given key on the keypad <part-num-ref name="keypad">36.</part-num-ref>
|
| 300 |
+
For example, mobile phones commonly have a hold <boundary-data type="line-number">15 </boundary-data>
|
| 301 |
+
feature associated with the "call send" key <part-num-ref name=""call send" key">38.</part-num-ref>
|
| 302 |
+
When making a call, the user enters a phone number and presses the "call send" key <part-num-ref name=""call send" key">38.</part-num-ref>
|
| 303 |
+
When receiving an incoming call, the "call send" key <part-num-ref name=""call send" key">38</part-num-ref>
|
| 304 |
+
may be programmed to act as a "call answer" key. When participating in a call, the "call send" key <part-num-ref name=""call send" key">38</part-num-ref>
|
| 305 |
+
may serve as a "call hold" key for placing the call on hold. A user may wish to place a call on hold for any of a variety of known reasons. For example, the user may be on a call when another incoming call arrives. By pressing a <boundary-data type="line-number">20 </boundary-data>
|
| 306 |
+
dedicated hold key <part-num-ref name="dedicated hold key">44</part-num-ref>
|
| 307 |
+
the user may place the current call on hold and then answer the new incoming call. </p>
|
| 308 |
+
<p id="p-61" num="61">Alternatively, in the case of a multifunction hold key the user may press the "call send" key <part-num-ref name=""call send" key">38</part-num-ref>
|
| 309 |
+
once to place the current call on hold and a second time to answer the new incoming call. </p>
|
| 310 |
+
<p id="p-62" num="62">Those having ordinary skill in the art will appreciate that the particular mechanism utilized by a user to place a call on hold is not germane to the invention. The mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 311 |
+
simply requires a means <boundary-data type="line-number">25 </boundary-data>
|
| 312 |
+
for allowing a user to place a call on hold. The specific form or format of the key(s) for placing a call on hold is not intended to limit the scope of the invention. </p>
|
| 313 |
+
<p id="p-63" num="63">In the particular embodiment of Fig. 2A, the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 314 |
+
includes the display <part-num-ref name="display">34</part-num-ref>
|
| 315 |
+
and separate keypad <part-num-ref name="and separate keypad">36.</part-num-ref>
|
| 316 |
+
In an alternative embodiment, the display <part-num-ref name="display">34</part-num-ref>
|
| 317 |
+
may comprise a touchscreen which itself includes one or more keys. In yet another embodiment, the display <part-num-ref name="display">34</part-num-ref>
|
| 318 |
+
may comprise a touchscreen that includes all <boundary-data type="line-number">30 </boundary-data>
|
| 319 |
+
or substantially all of the keys used to operate the phone <part-num-ref name="phone">16</part-num-ref>
|
| 320 |
+
so as to include a very limited keypad <part-num-ref name="very limited keypad">36</part-num-ref>
|
| 321 |
+
or no keypad <part-num-ref name="or no keypad">36</part-num-ref>
|
| 322 |
+
at all. As will be appreciated, the particular form and function of the keys included in the keypad <part-num-ref name="keypad">36</part-num-ref>
|
| 323 |
+
or <confidence value="2222222222222222222">touchscreen/display</confidence>
|
| 324 |
+
<part-num-ref name="or touchscreen/display">34</part-num-ref>
|
| 325 |
+
are not germane to the invention in its broadest sense. </p>
|
| 326 |
+
<p id="p-64" num="64">The features of the present invention are described herein in the context of a mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 327 |
+
suitable for carrying out video phone calls. For example, Fig. 2A illustrates how a video of a person at the <part-num-ref name="">35</part-num-ref>
|
| 328 |
+
<confidence value="22222222222222">called/calling</confidence>
|
| 329 |
+
device is transmit<confidence value="8">t</confidence>
|
| 330 |
+
ed over the communications network <part-num-ref name="communications network">10</part-num-ref>
|
| 331 |
+
and displayed by the mobile phone <boundary-data type="header">
|
| 332 |
+
<confidence value="8">8</confidence>
|
| 333 |
+
</boundary-data>
|
| 334 |
+
<page-break num="9"/>
|
| 335 |
+
<boundary-data type="header">DOCKET NO: SEMCPS<confidence value="56">05</confidence>
|
| 336 |
+
0663US1 </boundary-data>
|
| 337 |
+
<part-num-ref name="mobile phone">16</part-num-ref>
|
| 338 |
+
of the user in accordance with the present invention. Similarly, the <confidence value="22222222222222">called/calling</confidence>
|
| 339 |
+
device will display a video of the user of the mobile phone <part-num-ref name="mobile phone">16.</part-num-ref>
|
| 340 |
+
As is known, the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 341 |
+
is capable of sending and receiving video as well as audio during a call with a called/calling device. Moreover, the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 342 |
+
is capable of participating in video conference calls as is known. The particular technologies for <boundary-data type="line-number">5 </boundary-data>
|
| 343 |
+
communicating audio and video in both conference call and non-conference call settings are considered conventional. Accordingly, a detailed description of such technologies has been omitted for sake of brevity. </p>
|
| 344 |
+
<p id="p-65" num="65">On the other hand, many of the features of the present invention may be enjoyed even simply with traditional voice communications. In the broadest sense, the present invention is not intended to be limited in scope to any particular form of communications, e.g., whether audio and/or video.</p>
|
| 345 |
+
<p id="p-66" num="66">
|
| 346 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 347 |
+
Fig. 2B illustrates a mobile phone <part-num-ref name="mobile phone">16,</part-num-ref>
|
| 348 |
+
but in this case the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 349 |
+
constitutes the <confidence value="22222222222222">called/calling</confidence>
|
| 350 |
+
device at the other end of a call with a user's mobile phone <part-num-ref name="user's mobile phone">16</part-num-ref>
|
| 351 |
+
in accordance with the present invention. Fig. 2B represents circumstances whereby the user's mobile phone <part-num-ref name="user's mobile phone">16</part-num-ref>
|
| 352 |
+
has placed a call on hold. </p>
|
| 353 |
+
<p id="p-67" num="67">As is described below with respect to Fig. 6, the user's mobile phone <part-num-ref name="user's mobile phone">16</part-num-ref>
|
| 354 |
+
when desiring to place a call on hold sends a request to one of the hold servers <part-num-ref name="hold servers">30.</part-num-ref>
|
| 355 |
+
The request prompts the hold server <part-num-ref name="hold server">30</part-num-ref>
|
| 356 |
+
to send a media <boundary-data type="line-number">15 </boundary-data>
|
| 357 |
+
object to the <confidence value="22222222222222">called/calling</confidence>
|
| 358 |
+
mobile phone <part-num-ref name="called/calling mobile phone">16.</part-num-ref>
|
| 359 |
+
In the exemplary embodiment of Fig. 2B, the hold server <part-num-ref name="hold server">30</part-num-ref>
|
| 360 |
+
provides a media object including audio such as a song preselected by the user of the mobile phone requesting the hold. The audio is reproduced by the mobile phone through the speaker <part-num-ref name="speaker">46</part-num-ref>
|
| 361 |
+
as shown, for example. In addition, the media object provided by the hold server <part-num-ref name="hold server">30</part-num-ref>
|
| 362 |
+
can include a visual portion such as one or more still images or a video shown on the display <part-num-ref name="display">34.</part-num-ref>
|
| 363 |
+
As a consequence, when the user of the mobile <boundary-data type="line-number">20 </boundary-data>
|
| 364 |
+
phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 365 |
+
places a call on hold, the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 366 |
+
of the party at the other end of the call will be able to enjoy the audio and/or video images provided by the hold server <part-num-ref name="hold server">30.</part-num-ref>
|
| 367 |
+
Thus, the audio and video becomes an extension of the personality of the user of the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 368 |
+
that placed the call on hold. As is shown in Fig. 2B, the display <part-num-ref name="display">34</part-num-ref>
|
| 369 |
+
also may display a small "On Hold" message to visually indicate that the call has been placed on hold. </p>
|
| 370 |
+
<p id="p-68" num="68">
|
| 371 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 372 |
+
Fig. 2C illustrates another embodiment of the invention whereby the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 373 |
+
at the other end of the call placed on hold receives and reproduces a form of corporate logo or other type advertisement. </p>
|
| 374 |
+
<p id="p-69" num="69">For example, Fig. 2C represents a brief commercial video displayed on the display <part-num-ref name="display">34</part-num-ref>
|
| 375 |
+
together with commercial jingle reproduced via the speaker <part-num-ref name="speaker">46.</part-num-ref>
|
| 376 |
+
Thus, sales professionals are able to provide to callers on the other end a brief promotion while they place a call on hold. </p>
|
| 377 |
+
<p id="p-70" num="70">
|
| 378 |
+
<boundary-data type="line-number">30 </boundary-data>
|
| 379 |
+
Fig. 2D illustrates a simple embodiment whereby a media object containing only an audio portion is provided to the <confidence value="22222222222222">called/calling</confidence>
|
| 380 |
+
device by the hold server <part-num-ref name="hold server">30.</part-num-ref>
|
| 381 |
+
</p>
|
| 382 |
+
<p id="p-71" num="71">Figs. 2E and 2F illustrate an embodiment of the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 383 |
+
with video conference capability. </p>
|
| 384 |
+
<p id="p-72" num="72">In Fig. 2E, the display <part-num-ref name="display">34</part-num-ref>
|
| 385 |
+
is divided into different sections with each section providing an image of one of the participants at the other end of the video conference. Fig. 2F illustrates the case where one of the <boundary-data type="line-number">35 </boundary-data>
|
| 386 |
+
participants (e.g., in the lower right quadrant) places the call on hold from his mobile phone <part-num-ref name="call on hold from his mobile phone">16.</part-num-ref>
|
| 387 |
+
As a result, the hold server <part-num-ref name="hold server">30</part-num-ref>
|
| 388 |
+
provides a media object to the <confidence value="22222222222222">called/calling</confidence>
|
| 389 |
+
devices of the other participants (e.g., the <boundary-data type="header">
|
| 390 |
+
<confidence value="8">9</confidence>
|
| 391 |
+
</boundary-data>
|
| 392 |
+
<page-break num="10"/>
|
| 393 |
+
<boundary-data type="header">DOCKET NO: SEMCPS<confidence value="56">05</confidence>
|
| 394 |
+
0663US1 </boundary-data>
|
| 395 |
+
mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 396 |
+
in Fig. 2F). Again, the media object may include audio, still image(s) and/or video as represented in Fig. 2F. In the case of a video conference call, however, the user of the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 397 |
+
requesting the hold may prefer not to request a media object including audio as the audio may be distracting to the other participants who may prefer to continue the video conference amongst themselves. </p>
|
| 398 |
+
<p id="p-73" num="73">
|
| 399 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 400 |
+
Fig. 3 represents a functional block diagram of the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 401 |
+
in accordance with the invention. The construction of the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 402 |
+
is generally conventional with the exception of the hold and voicemail functions. Preferably, the hold and voicemail functions are implemented primarily via application software within the mobile phone <part-num-ref name="mobile phone">16.</part-num-ref>
|
| 403 |
+
However, it will be apparent to those having ordinary skill in the art that such operation can be carried out via primarily software, hardware, firmware, or combinations <boundary-data type="line-number">10 </boundary-data>
|
| 404 |
+
thereof, without departing from the scope of the invention. </p>
|
| 405 |
+
<p id="p-74" num="74">The mobile phone 16 includes a primary control circuit <part-num-ref name="primary control circuit">48</part-num-ref>
|
| 406 |
+
that is configured to carry out overall control of the functions and operations of the mobile phone <part-num-ref name="mobile phone">16.</part-num-ref>
|
| 407 |
+
The control circuit <part-num-ref name="control circuit">48</part-num-ref>
|
| 408 |
+
may include a CPU, microcontroller, or microprocessor, etc., collectively referred to herein simply as a CPU <part-num-ref name="CPU">50.</part-num-ref>
|
| 409 |
+
The CPU <part-num-ref name="CPU">50</part-num-ref>
|
| 410 |
+
executes code stored in memory within the control circuit <part-num-ref name="control circuit">48</part-num-ref>
|
| 411 |
+
(not shown) and/or in a separate memory <part-num-ref name="separate memory">52</part-num-ref>
|
| 412 |
+
in <boundary-data type="line-number">15 </boundary-data>
|
| 413 |
+
order to carry out conventional operation of the mobile phone functions <part-num-ref name="mobile phone functions">54</part-num-ref>
|
| 414 |
+
within the mobile phone <part-num-ref name="mobile phone">16.</part-num-ref>
|
| 415 |
+
In addition, however, the CPU <part-num-ref name="CPU">50</part-num-ref>
|
| 416 |
+
executes code stored in the memory <part-num-ref name="memory">52</part-num-ref>
|
| 417 |
+
in accordance with the present invention in order to perform a hold function <part-num-ref name="hold function">56,</part-num-ref>
|
| 418 |
+
media player function <part-num-ref name="hold function 56, media player function">58</part-num-ref>
|
| 419 |
+
and voicemail function <part-num-ref name="and voicemail function">60.</part-num-ref>
|
| 420 |
+
</p>
|
| 421 |
+
<p id="p-75" num="75">As is explained in more detail below, the hold function <part-num-ref name="hold function">56</part-num-ref>
|
| 422 |
+
enables a user of the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 423 |
+
to place a call on hold. In addition, the hold function <part-num-ref name="hold function">56</part-num-ref>
|
| 424 |
+
serves to send a request to the hold server <part-num-ref name="hold server">30</part-num-ref>
|
| 425 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 426 |
+
requesting that a media object or objects be sent to the <confidence value="22222222222222">called/calling</confidence>
|
| 427 |
+
devices at the other end of the call. </p>
|
| 428 |
+
<p id="p-76" num="76">Moreover, the hold function <part-num-ref name="hold function">56</part-num-ref>
|
| 429 |
+
enables the user to take the call off hold and send a request to the hold server <part-num-ref name="hold server">30</part-num-ref>
|
| 430 |
+
that conventional communications resume. </p>
|
| 431 |
+
<p id="p-77" num="77">The media player function 58 serves to play media objects stored within the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 432 |
+
as is conventional<confidence value="5">.</confidence>
|
| 433 |
+
In addition, however, the media player function <part-num-ref name="media player function">58</part-num-ref>
|
| 434 |
+
itself may be used to provide a media <boundary-data type="line-number">25 </boundary-data>
|
| 435 |
+
object to one or more <confidence value="22222222222222">called/calling</confidence>
|
| 436 |
+
devices at the other end of a call when the call is placed on hold. </p>
|
| 437 |
+
<p id="p-78" num="78">However, this aspect of the invention is the subject of another application filed by applicant.</p>
|
| 438 |
+
<p id="p-79" num="79">The voicemail function 60 serves to provide audio-video mail in accordance with the invention as discussed below in relation to Fig. 8.</p>
|
| 439 |
+
<p id="p-80" num="80">The mobile phone 16 further may include a media library <part-num-ref name="media library">62.</part-num-ref>
|
| 440 |
+
The media library <part-num-ref name="media library">62</part-num-ref>
|
| 441 |
+
represents a <boundary-data type="line-number">30 </boundary-data>
|
| 442 |
+
storage medium that stores various media objects in the form of audio files, video files, picture/image files, etc. The storage medium preferably is a non-volatile memory such as a large capacity flash memory or micro-hard drive, each of which are well known in personal media players. In a more limited context, the media library <part-num-ref name="media library">62</part-num-ref>
|
| 443 |
+
may be represented by a relatively small capacity compact disk (CD), mini-disk, flash card, etc., each of which may be inserted into the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 444 |
+
for reproduction of the media objects thereon. </p>
|
| 445 |
+
<boundary-data type="header">
|
| 446 |
+
<confidence value="88">10</confidence>
|
| 447 |
+
</boundary-data>
|
| 448 |
+
<boundary-data type="header">DOCKET NO: SEMCPS<confidence value="66">05</confidence>
|
| 449 |
+
0663US1 </boundary-data>
|
| 450 |
+
<p id="p-81" num="81">
|
| 451 |
+
<page-break num="11"/>
|
| 452 |
+
Alternatively, media object(s) also may reside on remote storage. For example, the media objects may reside on a remote server also accessible by the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 453 |
+
via a wireless Internet connection. </p>
|
| 454 |
+
<p id="p-82" num="82">A person having ordinary skill in the art of computer programming and specifically in applications programming for mobile phones will consider it obvious in view of the description provided herein how to <boundary-data type="line-number">5 </boundary-data>
|
| 455 |
+
program a mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 456 |
+
to operate and carry out the f<confidence value="8">u</confidence>
|
| 457 |
+
nctions described herein. Accordingly, details as to the specific programming code have been left out for sake of brevity. Also, while the hold function <part-num-ref name="hold function">56</part-num-ref>
|
| 458 |
+
and voicemail function <part-num-ref name="and voicemail function">60</part-num-ref>
|
| 459 |
+
are carried out via the CPU <part-num-ref name="CPU">50</part-num-ref>
|
| 460 |
+
and application software in the memory <part-num-ref name="memory">44</part-num-ref>
|
| 461 |
+
in accordance with a preferred embodiment of the invention, such functions could also be carried out via dedicated hardware, firmware, software, or combinations thereof, without departing from the scope of the <boundary-data type="line-number">10 </boundary-data>
|
| 462 |
+
invention. </p>
|
| 463 |
+
<p id="p-83" num="83">Continuing to refer to Fig. 3, the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 464 |
+
includes an antenna <part-num-ref name="antenna">64</part-num-ref>
|
| 465 |
+
coupled to a radio circuit <part-num-ref name="radio circuit">66.</part-num-ref>
|
| 466 |
+
The radio circuit <part-num-ref name="radio circuit">66</part-num-ref>
|
| 467 |
+
includes a radio frequency transmitter and receiver for transmitting and receiving signals via the antenna <part-num-ref name="antenna">64</part-num-ref>
|
| 468 |
+
as is conventional. The mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 469 |
+
further includes an audio processing circuit <part-num-ref name="audio processing circuit">68</part-num-ref>
|
| 470 |
+
for processing the audio signal transmitted by/received from the radio circuit <part-num-ref name="radio circuit">66.</part-num-ref>
|
| 471 |
+
In addition, the <boundary-data type="line-number">15 </boundary-data>
|
| 472 |
+
audio processing circuit <part-num-ref name="audio processing circuit">68</part-num-ref>
|
| 473 |
+
serves to process the audio signal provided by the control circuit <part-num-ref name="control circuit">48</part-num-ref>
|
| 474 |
+
during playback of media objects. Coupled to the audio processing circuit <part-num-ref name="audio processing circuit">68</part-num-ref>
|
| 475 |
+
are the aforementioned speaker <part-num-ref name="aforementioned speaker">46,</part-num-ref>
|
| 476 |
+
and a microphone <part-num-ref name="microphone">70</part-num-ref>
|
| 477 |
+
which enable a user to listen and speak via the mobile phone <part-num-ref name="mobile phone">10</part-num-ref>
|
| 478 |
+
as is conventional<confidence value="5">.</confidence>
|
| 479 |
+
In addition, a headphone jack <part-num-ref name="headphone jack">72</part-num-ref>
|
| 480 |
+
coupled to the audio processing circuit <part-num-ref name="audio processing circuit">68</part-num-ref>
|
| 481 |
+
is provided. This allows a headset to be connected to the mobile phone <part-num-ref name="mobile phone">16.</part-num-ref>
|
| 482 |
+
</p>
|
| 483 |
+
<p id="p-84" num="84">
|
| 484 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 485 |
+
The mobile phone 16 also includes a video signal processing circuit <part-num-ref name="video signal processing circuit">76</part-num-ref>
|
| 486 |
+
as shown in Fig. 3. The video signal processing circuit allows the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 487 |
+
to reproduce media objects including images and/or videos on the display <part-num-ref name="display">34.</part-num-ref>
|
| 488 |
+
Moreover, the video signal processing allows a still images and/or videos from the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 489 |
+
to be captured via a camera <part-num-ref name="camera">78</part-num-ref>
|
| 490 |
+
included in the phone <part-num-ref name="phone">16.</part-num-ref>
|
| 491 |
+
The camera <part-num-ref name="camera">78</part-num-ref>
|
| 492 |
+
is preferably mounted on the face of the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 493 |
+
as shown in Figs. 2A t<confidence value="8">h</confidence>
|
| 494 |
+
ru 2F so as to be capable of <boundary-data type="line-number">25 </boundary-data>
|
| 495 |
+
capturing an image of the user. During video conference calls, the camera <part-num-ref name="camera">78</part-num-ref>
|
| 496 |
+
captures an image that is then communicated along with the audio to the video conference server <part-num-ref name="video conference server">30</part-num-ref>
|
| 497 |
+
to the <confidence value="22222222222222">called/calling</confidence>
|
| 498 |
+
devices on the other end of the call. </p>
|
| 499 |
+
<p id="p-85" num="85">The mobile phone 16 also includes the aforementioned display <part-num-ref name="aforementioned display">34,</part-num-ref>
|
| 500 |
+
keypad <part-num-ref name="aforementioned display 34, keypad">36,</part-num-ref>
|
| 501 |
+
and specifically the "hold key" <part-num-ref name=""hold key"">44,</part-num-ref>
|
| 502 |
+
coupled to the control circuit <part-num-ref name="control circuit">48.</part-num-ref>
|
| 503 |
+
The mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 504 |
+
further includes an I/O interface <part-num-ref name="I/O interface">80.</part-num-ref>
|
| 505 |
+
</p>
|
| 506 |
+
<p id="p-86" num="86">
|
| 507 |
+
<boundary-data type="line-number">30 </boundary-data>
|
| 508 |
+
The <confidence value="66">I/</confidence>
|
| 509 |
+
O interface 80 may be in the form of any one of many typical mobile phone <confidence value="66">I/</confidence>
|
| 510 |
+
O interfaces, such as a multi-element connector at the base of the mobile phone <part-num-ref name="mobile phone">16.</part-num-ref>
|
| 511 |
+
As is typical, the <confidence value="66">I/</confidence>
|
| 512 |
+
O interface <part-num-ref name="I/O interface">80</part-num-ref>
|
| 513 |
+
may be used to couple the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 514 |
+
to a battery charger to charge a power supply unit <part-num-ref name="power supply unit">82</part-num-ref>
|
| 515 |
+
within the mobile phone <part-num-ref name="mobile phone">
|
| 516 |
+
<confidence value="885">10.</confidence>
|
| 517 |
+
</part-num-ref>
|
| 518 |
+
In addition, or in the alternative, the <confidence value="66">I/</confidence>
|
| 519 |
+
O interface <part-num-ref name="I/O interface">80</part-num-ref>
|
| 520 |
+
may serve to connect the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 521 |
+
to a wired personal hands-free adaptor (not shown) or Bluetooth adaptor (also not shown) for use with a <boundary-data type="line-number">35 </boundary-data>
|
| 522 |
+
Bluetooth-based hands-free adaptor. Further, the <confidence value="66">I/</confidence>
|
| 523 |
+
O interface <part-num-ref name="I/O interface">80</part-num-ref>
|
| 524 |
+
may serve to connect the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 525 |
+
to a personal computer or other device via a data cable, etc. As another alternative, the <confidence value="66">I/</confidence>
|
| 526 |
+
O interface <part-num-ref name="I/O interface">80</part-num-ref>
|
| 527 |
+
may <boundary-data type="header">
|
| 528 |
+
<confidence value="88">11</confidence>
|
| 529 |
+
</boundary-data>
|
| 530 |
+
<page-break num="12"/>
|
| 531 |
+
<boundary-data type="header">DOCKET NO: SEMCPS<confidence value="56">05</confidence>
|
| 532 |
+
0663U<confidence value="68">S1</confidence>
|
| 533 |
+
</boundary-data>
|
| 534 |
+
serve to connect the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 535 |
+
to a docking station including an audio amplifier, speakers and/or video display to allow for enhanced viewing/listening of the media objects as part of the media player function. </p>
|
| 536 |
+
<p id="p-87" num="87">Additionally, the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 537 |
+
in accordance with the present invention includes a hold on/off <boundary-data type="line-number">5 </boundary-data>
|
| 538 |
+
detector <part-num-ref name="hold on/off detector">84.</part-num-ref>
|
| 539 |
+
However, this aspect of the invention is also the subject of another application filed by the applicant. </p>
|
| 540 |
+
<p id="p-88" num="88">Referring now to Figs. 4A, 4B and 4C, an exemplary user interface presented on the display <part-num-ref name="display">34</part-num-ref>
|
| 541 |
+
is shown illustrating how a user may make appropriate selections in accordance with the invention. Suppose the user of the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 542 |
+
wishes to activate the call hold functions of the present invention. The user <boundary-data type="line-number">10 </boundary-data>
|
| 543 |
+
may press a menu button on the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 544 |
+
and be presented with the display of menu selections as represented in Fig. 4A. The user may selection the "Settings" selection in order to proceed to the next menu as represented in Fig. 4B. In Fig. 4B, the user is presented with the option of adjusting the "hold settings". </p>
|
| 545 |
+
<p id="p-89" num="89">By selecting "hold settings", the user is then presented with the display represented in Fig. 4C. The user may then customize the hold settings using conventional principles as used with respect to selecting ring <boundary-data type="line-number">15 </boundary-data>
|
| 546 |
+
tones, wallpaper, etc. For example, Fig. 4C illustrates how the user is presented with the option of turning the call hold features on or off. In addition, the user can select whether the media objects delivered to the <confidence value="22222222222222">called/calling</confidence>
|
| 547 |
+
devices at the other end of a held call receive audio, video, or combined audio and video objects. Moreover, the user is presented with the option of whether hold service via the hold server <part-num-ref name="hold server">30</part-num-ref>
|
| 548 |
+
is utilized. As noted in the present application, the hold servers <part-num-ref name="hold servers">30</part-num-ref>
|
| 549 |
+
may be used to communicate one or more <boundary-data type="line-number">20 </boundary-data>
|
| 550 |
+
media objects to the <confidence value="22222222222222">called/calling</confidence>
|
| 551 |
+
devices at the other end of a held call<confidence value="5">.</confidence>
|
| 552 |
+
In this case, the user would select that the service be "on". As covered in a related application filed by the applicant, however, the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 553 |
+
itself may provide the media objects to the <confidence value="22222222222222">called/calling</confidence>
|
| 554 |
+
devices. In such case, the user would select that the service be "off<confidence value="5">'</confidence>
|
| 555 |
+
, yet the hold function mentioned above remain <confidence value="58866">"on".</confidence>
|
| 556 |
+
</p>
|
| 557 |
+
<p id="p-90" num="90">The user of the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 558 |
+
may also select personalized media files as represented in Fig. 4C. </p>
|
| 559 |
+
<p id="p-91" num="91">
|
| 560 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 561 |
+
Although not shown, the user may select particular songs, personal videos, advertisements, promotional videos, etc. to be communicated to the <confidence value="22222222222222">called/calling</confidence>
|
| 562 |
+
devices at the other end of a held call. Moreover, the user may select to input different criteria to be used in conjunction with the selection of the particular media objects to be communicated. For example, the user may be presented with an option to associate specific media objects (e.g., songs) based on the identification of the <confidence value="22222222222222">called/calling</confidence>
|
| 563 |
+
party. Alternatively, the user may <boundary-data type="line-number">30 </boundary-data>
|
| 564 |
+
be presented with an option to randomly select media objects to be communicated, for example. </p>
|
| 565 |
+
<p id="p-92" num="92">Fig. 5 is an exemplary embodiment of one of the servers <part-num-ref name="servers">30.</part-num-ref>
|
| 566 |
+
A server <part-num-ref name="server">30</part-num-ref>
|
| 567 |
+
includes a general control unit <part-num-ref name="general control unit">90,</part-num-ref>
|
| 568 |
+
that itself may include a master control unit (MCU) <part-num-ref name="master control unit (MCU)">92.</part-num-ref>
|
| 569 |
+
The MCU <part-num-ref name="MCU">92</part-num-ref>
|
| 570 |
+
includes hardware, software, firmware, or any combination thereof, for carrying out the herein described video conference function <part-num-ref name="herein described video conference function">94,</part-num-ref>
|
| 571 |
+
hold function <part-num-ref name="herein described video conference function 94, hold function">96</part-num-ref>
|
| 572 |
+
and audio-video mail function <part-num-ref name="and audio-video mail function">98.</part-num-ref>
|
| 573 |
+
The video conference function <part-num-ref name="video conference function">94</part-num-ref>
|
| 574 |
+
is conventional and <boundary-data type="line-number">35 </boundary-data>
|
| 575 |
+
not described in detail herein. The hold function is represented in Fig. 7 discussed below. The audio-video mail function <part-num-ref name="audio-video mail function">98</part-num-ref>
|
| 576 |
+
is represented in Fig. 8 discussed below. </p>
|
| 577 |
+
<boundary-data type="header">
|
| 578 |
+
<confidence value="88">12</confidence>
|
| 579 |
+
</boundary-data>
|
| 580 |
+
<boundary-data type="header">DOCKET NO: <confidence value="22222222">SEMCPSO5</confidence>
|
| 581 |
+
0663US1 </boundary-data>
|
| 582 |
+
<p id="p-93" num="93">
|
| 583 |
+
<page-break num="13"/>
|
| 584 |
+
A server 30 preferably includes a media database <part-num-ref name="media database">100</part-num-ref>
|
| 585 |
+
for storing one or more media objects for use in carrying out the hold f<confidence value="8">u</confidence>
|
| 586 |
+
nction <part-num-ref name="hold function">96.</part-num-ref>
|
| 587 |
+
The media objects may consist of a library assembled by the service provider, and/or may represent a collection of media objects provided by one or more users of the mobile phones <part-num-ref name="mobile phones">16</part-num-ref>
|
| 588 |
+
in accordance with the present invention. The media objects may include different songs, <boundary-data type="line-number">5 </boundary-data>
|
| 589 |
+
advertisements, music videos, personal videos, promotional videos, etc. The users of the service may have uploaded the media objects to the server and the media database <part-num-ref name="media database">100</part-num-ref>
|
| 590 |
+
in advance. Alternatively, if bandwidth permits the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 591 |
+
may upload the media object(s) to the server <part-num-ref name="server">30</part-num-ref>
|
| 592 |
+
at the time of requesting a hold. </p>
|
| 593 |
+
<p id="p-94" num="94">The media database 100 in the server <part-num-ref name="server">30</part-num-ref>
|
| 594 |
+
may also include different criteria provided to the server <boundary-data type="line-number">10 </boundary-data>
|
| 595 |
+
from the mobile phone requesting that a call be placed on hold. For example, the media objects associated with a particular user may be stored in the database <part-num-ref name="database">100</part-num-ref>
|
| 596 |
+
together with any particular selection criteria commonly utilized by the user. The user may then transmit particular selection criteria requests with the hold request and the MCU <part-num-ref name="MCU">92</part-num-ref>
|
| 597 |
+
can apply the criteria to the media objects within the database <part-num-ref name="database">100</part-num-ref>
|
| 598 |
+
to select a particular media object or objects. </p>
|
| 599 |
+
<p id="p-95" num="95">
|
| 600 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 601 |
+
The server 30 also preferably includes an audio-video mail database <part-num-ref name="audio-video mail database">102</part-num-ref>
|
| 602 |
+
for storing audio-video mail as discussed in more detail below with respect to Fig. 8. Moreover, the server <part-num-ref name="server">30</part-num-ref>
|
| 603 |
+
includes an interface <part-num-ref name="interface">104</part-num-ref>
|
| 604 |
+
for connecting the server <part-num-ref name="server">30</part-num-ref>
|
| 605 |
+
to the communications network <part-num-ref name="communications network">10</part-num-ref>
|
| 606 |
+
as is conventional. </p>
|
| 607 |
+
<p id="p-96" num="96">Turning now to Fig. 6, the process of carrying out a hold function from the perspective of a user's mobile phone <part-num-ref name="user's mobile phone">16</part-num-ref>
|
| 608 |
+
in accordance with the present invention will now be described. Initially, it is assumed that <boundary-data type="line-number">20 </boundary-data>
|
| 609 |
+
the user is engaged in a call between the user's mobile phone <part-num-ref name="user's mobile phone">16</part-num-ref>
|
| 610 |
+
and one or more called/calling devices. </p>
|
| 611 |
+
<p id="p-97" num="97">Such standard call or conference call is established using conventional techniques within the network <part-num-ref name="network">10.</part-num-ref>
|
| 612 |
+
</p>
|
| 613 |
+
<p id="p-98" num="98">Beginning in step 110, the CPU <part-num-ref name="CPU">50</part-num-ref>
|
| 614 |
+
of the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 615 |
+
(Fig. <part-num-ref name="(Fig.">3)</part-num-ref>
|
| 616 |
+
determines if the user has requested that the call be placed on hold. The CPU <part-num-ref name="CPU">50</part-num-ref>
|
| 617 |
+
may detect whether the user has requested that the call be placed on hold by way of, for example, the user pressing the hold f<confidence value="8">u</confidence>
|
| 618 |
+
nction key <part-num-ref name="hold function key">44.</part-num-ref>
|
| 619 |
+
If a hold request has not been <boundary-data type="line-number">25 </boundary-data>
|
| 620 |
+
detected, the CPU <part-num-ref name="CPU">50</part-num-ref>
|
| 621 |
+
will continue to loop around step <part-num-ref name="will continue to loop around step">110</part-num-ref>
|
| 622 |
+
as shown in Fig. 6. </p>
|
| 623 |
+
<p id="p-99" num="99">If the user has requested that the call be placed on hold as determined in step <part-num-ref name="call be placed on hold as determined in step">110,</part-num-ref>
|
| 624 |
+
the process proceeds to step <part-num-ref name="process proceeds to step">112.</part-num-ref>
|
| 625 |
+
In step <part-num-ref name="process proceeds to step 112. In step">112,</part-num-ref>
|
| 626 |
+
the CPU <part-num-ref name="CPU">50</part-num-ref>
|
| 627 |
+
determines if the user has selected a particular hold criteria as discussed above. Again, for example, the user may request that the particular media object to be communicated to the <confidence value="22222222222222">called/calling</confidence>
|
| 628 |
+
devices be based on the identity of the <confidence value="22222222222222">called/calling</confidence>
|
| 629 |
+
parties. If the user <boundary-data type="line-number">30 </boundary-data>
|
| 630 |
+
has selected particular hold criteria as determined in step <part-num-ref name="user has selected particular hold criteria as determined in step">112,</part-num-ref>
|
| 631 |
+
the CPU <part-num-ref name="CPU">50</part-num-ref>
|
| 632 |
+
proceeds to step <part-num-ref name="proceeds to step">114</part-num-ref>
|
| 633 |
+
in which the CPU <part-num-ref name="CPU">50</part-num-ref>
|
| 634 |
+
determines the particular hold criteria most recently selected by the user. Next, in step <part-num-ref name="user. Next, in step">116</part-num-ref>
|
| 635 |
+
the CPU <part-num-ref name="CPU">50</part-num-ref>
|
| 636 |
+
causes the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 637 |
+
to transmit a hold request to the appropriate server <part-num-ref name="appropriate server">30</part-num-ref>
|
| 638 |
+
within the communications network <part-num-ref name="communications network">10</part-num-ref>
|
| 639 |
+
together with the particular hold criteria. Typically this will be via the radio circuit <part-num-ref name="radio circuit">66</part-num-ref>
|
| 640 |
+
to the service provider <part-num-ref name="service provider">12,</part-num-ref>
|
| 641 |
+
and thereon within the communications network <part-num-ref name="communications network">10</part-num-ref>
|
| 642 |
+
as necessary. The <part-num-ref name="">35</part-num-ref>
|
| 643 |
+
appropriate server <part-num-ref name="appropriate server">30</part-num-ref>
|
| 644 |
+
may be determined based on conventional network protocol such as distance away, <boundary-data type="header">
|
| 645 |
+
<confidence value="88">13</confidence>
|
| 646 |
+
</boundary-data>
|
| 647 |
+
<page-break num="14"/>
|
| 648 |
+
<boundary-data type="header">DOCKET NO: SEMCPS<confidence value="66">05</confidence>
|
| 649 |
+
0663US1 </boundary-data>
|
| 650 |
+
server workload, etc. In addition, in step <part-num-ref name="may be determined based on conventional network protocol such as distance away, server workload, etc. In addition, in step">116</part-num-ref>
|
| 651 |
+
the CPU <part-num-ref name="CPU">50</part-num-ref>
|
| 652 |
+
stops transmitting audio and video from the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 653 |
+
(e.g., via the microphone <part-num-ref name="microphone">70</part-num-ref>
|
| 654 |
+
and camer<confidence value="7">a</confidence>
|
| 655 |
+
<part-num-ref name="and camera">78)</part-num-ref>
|
| 656 |
+
to the <confidence value="22222222222222">called/calling</confidence>
|
| 657 |
+
devices. </p>
|
| 658 |
+
<p id="p-100" num="100">Preferably, the server <part-num-ref name="server">30</part-num-ref>
|
| 659 |
+
is part of a server already serving as part of the communications link for the ongoing call. Consequently, a connection with the <confidence value="22222222222222">called/calling</confidence>
|
| 660 |
+
devices will have already been <boundary-data type="line-number">5 </boundary-data>
|
| 661 |
+
established and a separate connection need not be obtained in order for the server <part-num-ref name="server">30</part-num-ref>
|
| 662 |
+
to communicate the media object to the called/calling devices in place of the audio and/or video that ordinary would be communicated from the user's mobile phone <part-num-ref name="user's mobile phone">16.</part-num-ref>
|
| 663 |
+
Otherwise, the server <part-num-ref name="server">30</part-num-ref>
|
| 664 |
+
preferably is configured to establish a connection with the <confidence value="22222222222222">called/calling</confidence>
|
| 665 |
+
devices in order to transfer the media object. In such case, however, it may be necessary to modify a conventional mobile phone at the <confidence value="22222222222222">called/calling</confidence>
|
| 666 |
+
end to receive the <boundary-data type="line-number">10 </boundary-data>
|
| 667 |
+
media object without disruption of the current connection on which the call has been placed on hold. </p>
|
| 668 |
+
<p id="p-101" num="101">If in step 112 the CPU <part-num-ref name="CPU">50</part-num-ref>
|
| 669 |
+
determines that the user has not selected any particular hold criteria, the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 670 |
+
transmits the hold request to the appropriate server <part-num-ref name="appropriate server">30</part-num-ref>
|
| 671 |
+
without any particular hold criteria. </p>
|
| 672 |
+
<p id="p-102" num="102">The server 30 may then draw from the media database a default media object associated with the user and communicate the media object to the <confidence value="22222222222222">called/calling</confidence>
|
| 673 |
+
devices at the other end of the call. </p>
|
| 674 |
+
<p id="p-103" num="103">
|
| 675 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 676 |
+
In step 118, the CPU <part-num-ref name="CPU">50</part-num-ref>
|
| 677 |
+
determines if the user has requested that the call be taken off hold. If no, the CPU <part-num-ref name="CPU">50</part-num-ref>
|
| 678 |
+
continues to loop around step <part-num-ref name="continues to loop around step">118</part-num-ref>
|
| 679 |
+
and the server <part-num-ref name="server">30</part-num-ref>
|
| 680 |
+
continues to communicate the media object(s) to the called/calling devices. Whether the user has requested that the call be taken off hold can again be determined based on the user pressing the hold function key <part-num-ref name="hold function key">44</part-num-ref>
|
| 681 |
+
a second time, for example. Upon detecting that the user has requested that the call be taken off hold, the CPU <part-num-ref name="CPU">50</part-num-ref>
|
| 682 |
+
proceeds to step <part-num-ref name="proceeds to step">120</part-num-ref>
|
| 683 |
+
in <boundary-data type="line-number">20 </boundary-data>
|
| 684 |
+
which the CPU <part-num-ref name="CPU">50</part-num-ref>
|
| 685 |
+
transmits an end hold request to the server <part-num-ref name="server">30</part-num-ref>
|
| 686 |
+
responsible for communicating the media object to the called/calling devices. In response, the server <part-num-ref name="server">30</part-num-ref>
|
| 687 |
+
stops communicating the media object. The CPU <part-num-ref name="CPU">50</part-num-ref>
|
| 688 |
+
causes the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 689 |
+
to return to conventional operation whereby audio and video from the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 690 |
+
continues to be transmitted to the called/calling devices as in a conventional call<confidence value="5">.</confidence>
|
| 691 |
+
In addition, the CPU <part-num-ref name="CPU">50</part-num-ref>
|
| 692 |
+
returns to step <part-num-ref name="returns to step">110.</part-num-ref>
|
| 693 |
+
</p>
|
| 694 |
+
<p id="p-104" num="104">
|
| 695 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 696 |
+
Fig. 7 illustrates the operation of the server <part-num-ref name="server">30</part-num-ref>
|
| 697 |
+
in conjunction with carrying out the hold function in accordance with the present invention. Again, it is assumed that a call between the user's mobile phone <part-num-ref name="user's mobile phone">16</part-num-ref>
|
| 698 |
+
and the called/calling devices has already been established. It is also assumed that the server <part-num-ref name="server">30</part-num-ref>
|
| 699 |
+
is part of a server already part of the connection forming the call between the user's mobile phone and the <confidence value="22222222222222">called/calling</confidence>
|
| 700 |
+
devices as discussed above. Thus, beginning in step <part-num-ref name="called/calling devices as discussed above. Thus, beginning in step">124</part-num-ref>
|
| 701 |
+
the MCU <part-num-ref name="MCU">92</part-num-ref>
|
| 702 |
+
of the server <part-num-ref name="server">30</part-num-ref>
|
| 703 |
+
(Fig. <part-num-ref name="(Fig.">5)</part-num-ref>
|
| 704 |
+
functions <boundary-data type="line-number">30 </boundary-data>
|
| 705 |
+
simply to route the typical audio and/or video between the user's mobile phone <part-num-ref name="user's mobile phone">16</part-num-ref>
|
| 706 |
+
and the <confidence value="22222222222222">called/calling</confidence>
|
| 707 |
+
devices. Next, in step <part-num-ref name="called/calling devices. Next, in step">126</part-num-ref>
|
| 708 |
+
the MCU <part-num-ref name="MCU">92</part-num-ref>
|
| 709 |
+
determines if a hold request has been received as a result of step <part-num-ref name="result of step">116</part-num-ref>
|
| 710 |
+
in Fig. 6. If no, the MCU <part-num-ref name="MCU">92</part-num-ref>
|
| 711 |
+
loops back to step <part-num-ref name="loops back to step">124</part-num-ref>
|
| 712 |
+
as shown. </p>
|
| 713 |
+
<p id="p-105" num="105">If yes in step 126, the MCU <part-num-ref name="MCU">92</part-num-ref>
|
| 714 |
+
proceeds to step <part-num-ref name="proceeds to step">128</part-num-ref>
|
| 715 |
+
in which the MCU <part-num-ref name="MCU">92</part-num-ref>
|
| 716 |
+
selects an appropriate media object(s) based on the hold request and any criteria contained therewith received in step <part-num-ref name="hold request and any criteria contained therewith received in step">126.</part-num-ref>
|
| 717 |
+
As <part-num-ref name="hold request and any criteria contained therewith received in step 126. As">35</part-num-ref>
|
| 718 |
+
previously described, preferably the MCU <part-num-ref name="MCU">92</part-num-ref>
|
| 719 |
+
acquires the media object from the media database <part-num-ref name="media database">100</part-num-ref>
|
| 720 |
+
in <boundary-data type="header">
|
| 721 |
+
<confidence value="88">14</confidence>
|
| 722 |
+
</boundary-data>
|
| 723 |
+
<page-break num="15"/>
|
| 724 |
+
<boundary-data type="header">DOCKET NO: SEMCPS<confidence value="56">05</confidence>
|
| 725 |
+
0663US1 </boundary-data>
|
| 726 |
+
accordance with any prescribed criteria. The MCU <part-num-ref name="MCU">92</part-num-ref>
|
| 727 |
+
then proceeds to transmit the audio and/or video to the <confidence value="22222222222222">called/calling</confidence>
|
| 728 |
+
devices in place of the audio and/or video from the user's mobile phone <part-num-ref name="user's mobile phone">18</part-num-ref>
|
| 729 |
+
as represented in step <part-num-ref name="as represented in step">130.</part-num-ref>
|
| 730 |
+
The MCU <part-num-ref name="MCU">92</part-num-ref>
|
| 731 |
+
can transmit the media object in any suitable manner. For example, in the case of video it is preferable to stream the audio and video data to the <confidence value="22222222222222">called/calling</confidence>
|
| 732 |
+
devices to reduce bandwidth <boundary-data type="line-number">5 </boundary-data>
|
| 733 |
+
requirements. Alternatively, if the bandwidth is available the server <part-num-ref name="server">30</part-num-ref>
|
| 734 |
+
may simply reproduce the audio and/or video and feed it to the <confidence value="22222222222222">called/calling</confidence>
|
| 735 |
+
devices in real time in place of the audio and/or video from the user's mobile phone <part-num-ref name="user's mobile phone">16.</part-num-ref>
|
| 736 |
+
</p>
|
| 737 |
+
<p id="p-106" num="106">In step 132 the MCU <part-num-ref name="MCU">92</part-num-ref>
|
| 738 |
+
determines if the server <part-num-ref name="server">30</part-num-ref>
|
| 739 |
+
has received an end hold request as a result of step <part-num-ref name="result of step">120</part-num-ref>
|
| 740 |
+
in Fig. 6. If not, the MCU <part-num-ref name="MCU">92</part-num-ref>
|
| 741 |
+
continues to loop through steps <part-num-ref name="continues to loop through steps">130</part-num-ref>
|
| 742 |
+
and <part-num-ref name="and">132.</part-num-ref>
|
| 743 |
+
Upon receiving an end <boundary-data type="line-number">10 </boundary-data>
|
| 744 |
+
hold request as determined in step <part-num-ref name="end hold request as determined in step">132,</part-num-ref>
|
| 745 |
+
the MCU stops communicating the media object to the <confidence value="22222222222222">called/calling</confidence>
|
| 746 |
+
devices and returns to step <part-num-ref name="called/calling devices and returns to step">124.</part-num-ref>
|
| 747 |
+
As a result, normal call communications may resume. </p>
|
| 748 |
+
<p id="p-107" num="107">Fig. 8 illustrates the operation of the audio-video mail function of the present invention. In such case, the server <part-num-ref name="server">30</part-num-ref>
|
| 749 |
+
provides mail service functions as noted above. Specifically, using conventional voicemail techniques the server <part-num-ref name="server">30</part-num-ref>
|
| 750 |
+
determines if a user's mobile phone <part-num-ref name="user's mobile phone">18</part-num-ref>
|
| 751 |
+
is unavailable and, if so, is <boundary-data type="line-number">15 </boundary-data>
|
| 752 |
+
configured to transfer the call of a calling device into the server mail function. Thus, the server <part-num-ref name="server">30</part-num-ref>
|
| 753 |
+
in step <part-num-ref name="in step">140</part-num-ref>
|
| 754 |
+
determines if an incoming call to the user's mobile phone <part-num-ref name="user's mobile phone">18</part-num-ref>
|
| 755 |
+
has been received into the mail function <part-num-ref name="mail function">98</part-num-ref>
|
| 756 |
+
(Fig. 5). If yes, the MCU <part-num-ref name="MCU">92</part-num-ref>
|
| 757 |
+
in step <part-num-ref name="in step">142</part-num-ref>
|
| 758 |
+
proceeds to communicate an audio and/or video mail greeting to the calling device and invites the caller to leave a message. Next, in step <part-num-ref name="message. Next, in step">144</part-num-ref>
|
| 759 |
+
the MCU <part-num-ref name="MCU">92</part-num-ref>
|
| 760 |
+
determines if the calling device has left a message. For example, the MCU <part-num-ref name="MCU">92</part-num-ref>
|
| 761 |
+
determines if the connection has been lost (e.g., <boundary-data type="line-number">20 </boundary-data>
|
| 762 |
+
the caller hung up) or if there is no audio or video being received. If an audio or video response is received as determined in step <part-num-ref name="audio or video response is received as determined in step">144,</part-num-ref>
|
| 763 |
+
the MCU <part-num-ref name="MCU">92</part-num-ref>
|
| 764 |
+
stores the audio-video mail message into the audio-video mail database <part-num-ref name="audio-video mail database">102</part-num-ref>
|
| 765 |
+
as represented in step <part-num-ref name="as represented in step">146.</part-num-ref>
|
| 766 |
+
If, in step <part-num-ref name="as represented in step 146. If, in step">140,</part-num-ref>
|
| 767 |
+
a call is not received, the MCU <part-num-ref name="MCU">92</part-num-ref>
|
| 768 |
+
continues to loop through step <part-num-ref name="continues to loop through step">140.</part-num-ref>
|
| 769 |
+
</p>
|
| 770 |
+
<p id="p-108" num="108">Following step 146, the MCU <part-num-ref name="MCU">92</part-num-ref>
|
| 771 |
+
in step <part-num-ref name="in step">148</part-num-ref>
|
| 772 |
+
determines if the user of the mobile phone <part-num-ref name="mobile phone">18</part-num-ref>
|
| 773 |
+
has <boundary-data type="line-number">25 </boundary-data>
|
| 774 |
+
chosen to have details about the user pushed back to the calling device in accordance with the present invention. As described below in connection with Figs. 9A-9C, the user may select to have the server <part-num-ref name="server">30</part-num-ref>
|
| 775 |
+
transmit information relating to the user (e.g., user contact details, availability information, etc.) in response to the server <part-num-ref name="server">30</part-num-ref>
|
| 776 |
+
receiving audio-video mail for the mobile phone <part-num-ref name="mobile phone">18.</part-num-ref>
|
| 777 |
+
If the user has requested user details be provided to the calling device, the MCU <part-num-ref name="MCU">92</part-num-ref>
|
| 778 |
+
proceeds to step <part-num-ref name="proceeds to step">150</part-num-ref>
|
| 779 |
+
in which the server <part-num-ref name="server">30</part-num-ref>
|
| 780 |
+
retrieves from the <boundary-data type="line-number">30 </boundary-data>
|
| 781 |
+
audio/video mail database <part-num-ref name="audio/video mail database">102</part-num-ref>
|
| 782 |
+
user details previously identified by the user of the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 783 |
+
and preferably previously uploaded to the server <part-num-ref name="server">30.</part-num-ref>
|
| 784 |
+
The server <part-num-ref name="server">30</part-num-ref>
|
| 785 |
+
then proceeds to push the details to the calling device in the form of audio and/or video information. The mechanism for pushing the details to the calling device may be conventional techniques now commonly associated with various email platforms for use with mobile phones. If in step <part-num-ref name="calling device may be conventional techniques now commonly associated with various email platforms for use with mobile phones. If in step">148</part-num-ref>
|
| 786 |
+
the user of the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 787 |
+
has not selected for details to be <part-num-ref name="has not selected for details to be">35</part-num-ref>
|
| 788 |
+
pushed to the caller, the MCU <part-num-ref name="MCU">92</part-num-ref>
|
| 789 |
+
skips step <part-num-ref name="skips step">150</part-num-ref>
|
| 790 |
+
as shown in Fig. 8. </p>
|
| 791 |
+
<boundary-data type="header">
|
| 792 |
+
<confidence value="88">15</confidence>
|
| 793 |
+
</boundary-data>
|
| 794 |
+
<boundary-data type="header">DOCKET NO: <confidence value="22222222">SEMCPSO5</confidence>
|
| 795 |
+
0663US1 </boundary-data>
|
| 796 |
+
<p id="p-109" num="109">
|
| 797 |
+
<page-break num="16"/>
|
| 798 |
+
Following steps 148 and/or <part-num-ref name="and/or">150,</part-num-ref>
|
| 799 |
+
the MCU <part-num-ref name="MCU">92</part-num-ref>
|
| 800 |
+
proceeds to step <part-num-ref name="proceeds to step">152</part-num-ref>
|
| 801 |
+
in which the MCU <part-num-ref name="MCU">92</part-num-ref>
|
| 802 |
+
determines whether the user of the mobile phone <part-num-ref name="mobile phone">16</part-num-ref>
|
| 803 |
+
has previously requested that audio-video mail be pushed out to the user's mobile phone <part-num-ref name="user's mobile phone">16.</part-num-ref>
|
| 804 |
+
If yes, the MCU <part-num-ref name="MCU">92</part-num-ref>
|
| 805 |
+
proceeds to step <part-num-ref name="proceeds to step">154</part-num-ref>
|
| 806 |
+
in which the MCU <part-num-ref name="MCU">92</part-num-ref>
|
| 807 |
+
causes the server <part-num-ref name="server">30</part-num-ref>
|
| 808 |
+
to push the audio-video mail left by the calling device in step <part-num-ref name="calling device in step">146</part-num-ref>
|
| 809 |
+
out to the user's <boundary-data type="line-number">5 </boundary-data>
|
| 810 |
+
mobile phone <part-num-ref name="user's mobile phone">16.</part-num-ref>
|
| 811 |
+
Again, the mechanism for pushing the details to the calling device may be conventional techniques now commonly associated with various email platforms for use with mobile phones. If no in step <part-num-ref name="calling device may be conventional techniques now commonly associated with various email platforms for use with mobile phones. If no in step">152,</part-num-ref>
|
| 812 |
+
the MCU <part-num-ref name="MCU">92</part-num-ref>
|
| 813 |
+
may proceed to step <part-num-ref name="may proceed to step">156</part-num-ref>
|
| 814 |
+
instead of step <part-num-ref name="instead of step">154</part-num-ref>
|
| 815 |
+
and simply send a mail notification to the user's mobile phone <part-num-ref name="user's mobile phone">16</part-num-ref>
|
| 816 |
+
as is typical with standard voicemail with mobile phones. Following step <part-num-ref name="as is typical with standard voicemail with mobile phones. Following step">154</part-num-ref>
|
| 817 |
+
or step <part-num-ref name="or step">156,</part-num-ref>
|
| 818 |
+
the MCU <part-num-ref name="MCU">92</part-num-ref>
|
| 819 |
+
returns to step <part-num-ref name="returns to step">140</part-num-ref>
|
| 820 |
+
as shown in Fig. 8. </p>
|
| 821 |
+
<p id="p-110" num="110">
|
| 822 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 823 |
+
Figs. 9A, 9B and 9C illustrate an exemplary interface presented on the display <part-num-ref name="display">34</part-num-ref>
|
| 824 |
+
of the user's mobile phone <part-num-ref name="user's mobile phone">16</part-num-ref>
|
| 825 |
+
for permitting a user to select audio-video mail f<confidence value="8">u</confidence>
|
| 826 |
+
nctions, etc. in accordance with the embodiment of Fig. 8. Again, by stepping th<confidence value="8">r</confidence>
|
| 827 |
+
ough appropriately labeled menus the user may select desired user details, whether the user details are to be pushed to the calling device via the server <part-num-ref name="server">30,</part-num-ref>
|
| 828 |
+
whether the received mail is to be pushed to the mobile phone <part-num-ref name="mobile phone">16,</part-num-ref>
|
| 829 |
+
etc. Preferably, each time the user changes the <boundary-data type="line-number">15 </boundary-data>
|
| 830 |
+
configuration of the phone, the mobile phone <part-num-ref name="mobile phone">18</part-num-ref>
|
| 831 |
+
transmits the updated configuration information to the server <part-num-ref name="server">30</part-num-ref>
|
| 832 |
+
so that the server <part-num-ref name="server">30</part-num-ref>
|
| 833 |
+
will already have on record the desired user settings, as will be appreciated. </p>
|
| 834 |
+
<p id="p-111" num="111">Although the invention has been shown and described with respect to certain preferred embodiments, it is obvious that equivalents and modifications will occur to others skilled in the art upon the reading and understanding of the specification. The present invention includes all such equivalents and <part-num-ref name="present invention includes all such equivalents and">20</part-num-ref>
|
| 835 |
+
modifications, and is limited only by the scope of the following claims. </p>
|
| 836 |
+
<boundary-data type="header">
|
| 837 |
+
<confidence value="88">16</confidence>
|
| 838 |
+
</boundary-data>
|
| 839 |
+
</description>
|
| 840 |
+
</us-patent-application>
|
| 841 |
+
|
applicant/11284751.xml
ADDED
|
@@ -0,0 +1,231 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>11284751</doc-number>
|
| 8 |
+
<date>2005-11-22</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<boundary-data type="header">Attorney Docket No.: CE15281JSW_Kreitzer</boundary-data>
|
| 14 |
+
<boundary-data type="header">(7463-186)</boundary-data>
|
| 15 |
+
<heading id="h-1">ARCHITECTURE FOR SHARING PODCAST INFORMATION</heading>
|
| 16 |
+
<p id="p-1" num="1">Inventor(s) Stuart S. Kreitzer Joseph L. Dvorak Charles D. Estes </p>
|
| 17 |
+
<heading id="h-2">FIELD</heading>
|
| 18 |
+
<p id="p-2" num="2">[0001] This invention relates generally to podcasts, and more particularly to a method and system for sharing podcast information while playing a podcast presentation.</p>
|
| 19 |
+
<heading id="h-3">BACKGROUND</heading>
|
| 20 |
+
<p id="p-3" num="3">[0002] Podcasting is a known method of publishing audio and video programs via the Internet, allowing users to subscribe to a feed of files that usually come in MP3 format. Although "Podcasting" in its strictest sense is distinct from other types of online media delivery because of its subscription model, which uses a feed to deliver an enclosed file, the word "Podcast" is frequently used to describe the posting of any link to a media-player- compatible audio file on a website. Some radio personalities post MP3 versions of their shows daily, and even though these are simple download links and not part of any subscription model, they are nonetheless typically referred to as "Podcasts." Listeners may subscribe to feeds using "podcatching" software, which periodically checks for and downloads new content automatically. Most podcatching software enables the user to copy podcasts to portable music players. Any digital audio player or computer with audio-playing software can play podcasts.</p>
|
| 21 |
+
<p id="p-4" num="4">[0003] Many cellular phones now include MP3 functionality and enable the listening of Podcasts. Sharing information about a particular podcast with a friend or colleague today involves calling or emailing your friend or colleague, <confidence value="8888">EV33</confidence>
|
| 22 |
+
69813<confidence value="5588">96US</confidence>
|
| 23 |
+
<boundary-data type="header">
|
| 24 |
+
<confidence value="22">1.</confidence>
|
| 25 |
+
</boundary-data>
|
| 26 |
+
<page-break num="2"/>
|
| 27 |
+
<boundary-data type="header">Attorney Docket No.: CE1528<confidence value="5">1</confidence>
|
| 28 |
+
JSW_Kreitzer </boundary-data>
|
| 29 |
+
<boundary-data type="header">(7463-186)</boundary-data>
|
| 30 |
+
probably after writing down the universal<confidence value="5">/</confidence>
|
| 31 |
+
uniform resource locators of the podcast. </p>
|
| 32 |
+
<heading id="h-4">SUMMARY</heading>
|
| 33 |
+
<p id="p-5" num="5">[0004] Embodiments in accordance with the present invention can provide a data construct and a way to easily share great podcasts (or easy access thereto) with their friends and colleagues. If a listener enjoys a particular podcast on a mobile phone and would like to share or refer the podcast to another user perhaps because it is very entertaining or contains information that would be of interest to the other party, then embodiments herein enable such access to other users along with the ability to annotate or comment on such podcasts and trans<confidence value="8">m</confidence>
|
| 34 |
+
it such annotation or commentary with others. </p>
|
| 35 |
+
<p id="p-6" num="6">[0005] In a first embodiment of the present invention, a communication construct used for sharing podcast information associated with a podcast can include a link or hyperlink capable of being sent to a remote device while playing the podcast, metadata appended to the link associated with the podcast, and a communication packet enabling a user to transfer the link and the appended metadata while the user is playing the podcast. The link can be a universal record locator (URL) to the podcast and the metadata appended can include constructs having start times for the podcast, end times for the podcast, bookmarks for portions of the podcast, digital rights management information, display description, podcast category, or relevant images. The appended metadata can also include URLs for mobile blogging, a sender's weblog, a video blog, a social contact site, contact information from a sender, or a vCard record. The communication constructs enable podcatcher software in a user's computer to automatically download the podcast associated with the link. Note, the link and associated metadata is decoded at the remote device to enable customized retrieval of content, where the remote device can retrieve the podcast associated with the link via a high bandwidth channel for downloading the podcast. The communication construct can be a hierarchy of metadata enabling a sender to mark a URL <boundary-data type="header">
|
| 36 |
+
<confidence value="8">2</confidence>
|
| 37 |
+
</boundary-data>
|
| 38 |
+
<page-break num="3"/>
|
| 39 |
+
<boundary-data type="header">Attorney Docket No.: CE1528<confidence value="5">1</confidence>
|
| 40 |
+
JSW_Kreitzer </boundary-data>
|
| 41 |
+
<boundary-data type="header">(7463-186)</boundary-data>
|
| 42 |
+
associated with the podcast, mark a starting point for a portion of the podcast, or mark an ending point for the podcast. The communication construct can further include a hierarchy of metadata enabling a sender to attach additional metadata to the associated metadata including links to other websites, links to a sender<confidence value="8">'</confidence>
|
| 43 |
+
s weblog, mobile weblog, or video blog, or a sender<confidence value="8">'</confidence>
|
| 44 |
+
s contact information. Note, a hyperlink is known as a link from a hypertext file to another location or file which is typically activated by clicking on a highlighted word or icon at a particular location on a screen. Of course, a link or hyperlink as used interchangeably here should not be limited to the traditional definition of hyperlink, but should include other reasonably equivalent links that can generally enable the download of podcasts. </p>
|
| 45 |
+
<p id="p-7" num="7">[0006] In a second embodiment of the present invention, a user interface for creating a communication construct used for sharing podcast information associated with a podcast can include an input device for creating or retrieving a link capable of being sent to a remote device while playing the podcast, means for appending metadata to the link associated with the podcast, and a communication packet generator enabling a user to transfer the link and the appended metadata while the user is playing the podcast.</p>
|
| 46 |
+
<p id="p-8" num="8">The link can be a universal record locator (URL) to the podcast and the appended metadata can be constructs having start times for the podcast, end times for the podcast, bookmarks for portions of the podcast, digital rights management information, display description, podcast category, or relevant images. The appended metadata can also include URLs for mobile blogging, a sender's weblog, a video blog, a social contact site, contact information from a sender, or a vCard record. The communication construct can enable podcatcher software in a user's computer to automatically download the podcast associated with the link. The link and associated metadata can be decoded at the remote device to enable customized retrieval of content. The remote device can retrieve the podcast associated with the link via a high bandwidth channel for downloading the podcast.</p>
|
| 47 |
+
<boundary-data type="header">
|
| 48 |
+
<confidence value="8">3</confidence>
|
| 49 |
+
</boundary-data>
|
| 50 |
+
<boundary-data type="header">Attorney Docket No.: CE<confidence value="5">1</confidence>
|
| 51 |
+
5281JSW_Kreitzer </boundary-data>
|
| 52 |
+
<boundary-data type="header">(7463-186)</boundary-data>
|
| 53 |
+
<p id="p-9" num="9">
|
| 54 |
+
<page-break num="4"/>
|
| 55 |
+
[0007] The communication construct can include a hierarchy of metadata enabling a sender to mark a URL associated with the podcast, mark a starting point for a portion of the podcast, or mark an ending point for the podcast. </p>
|
| 56 |
+
<p id="p-10" num="10">The communication construct can further include a hierarchy of metadata enabling a sender to attach additional metadata to the associated metadata including links to other websites, links to a sender's weblog, mobile weblog, or video blog, or a sender's contact information.</p>
|
| 57 |
+
<p id="p-11" num="11">[0008] The terms "a" or "an," as used herein, are defined as one or more than one. The term "plurality," as used herein, is defined as two or more than two. The term "another," as used herein, is defined as at least a second or more. The terms "including" and/or "having," as used herein, are defined as comprising (i.e., open language). The term "coupled," as used herein, is defined as connected, although not necessarily directly, and not necessarily mechanically. The term "suppressing" can be defined as reducing or removing, either partially or completely.</p>
|
| 58 |
+
<p id="p-12" num="12">[0009] The terms "program," <confidence value="5">"</confidence>
|
| 59 |
+
software application," and the like as used herein, are defined as a sequence of instructions designed for execution on a computer system. A program, computer program, or software application may include a subroutine, a function, a procedure, an object method, an object implementation, an executable application, an applet, a <confidence value="2222222">servlet</confidence>
|
| 60 |
+
, a source code, an object code, a shared library/dynamic load library and/or other sequence of instructions designed for execution on a computer system. </p>
|
| 61 |
+
<p id="p-13" num="13">[0010] Other embodiments, when configured in accordance with the inventive arrangements disclosed herein, can include a system for performing and a machine readable storage for causing a machine to perform the various processes and methods disclosed herein.</p>
|
| 62 |
+
<heading id="h-5">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
|
| 63 |
+
<p id="p-14" num="14">[0011] FIG. 1 is a block diagram of a system for sharing podcast information in accordance with an embodiment of the present invention.</p>
|
| 64 |
+
<boundary-data type="header">
|
| 65 |
+
<confidence value="8">4</confidence>
|
| 66 |
+
</boundary-data>
|
| 67 |
+
<boundary-data type="header">Attorney Docket No.: CE1528<confidence value="5">1</confidence>
|
| 68 |
+
JSW_Kreitzer </boundary-data>
|
| 69 |
+
<boundary-data type="header">(7463-186)</boundary-data>
|
| 70 |
+
<p id="p-15" num="15">
|
| 71 |
+
<page-break num="5"/>
|
| 72 |
+
[0012] FIG. 2 is a flow chart illustrating a method of sharing podcast information in accordance with an embodiment of the present invention. </p>
|
| 73 |
+
<heading id="h-6">DETAILED DESCRIPTION OF THE DRAWINGS</heading>
|
| 74 |
+
<p id="p-16" num="16">[0013] While the specification concludes with claims defining the features of embodiments of the invention that are regarded as novel, it is believed that the invention will be better understood from a consideration of the following description in conjunction with the figures, in which like reference numerals are carried forward.</p>
|
| 75 |
+
<p id="p-17" num="17">[0014] Referring to FIG. 1, a block diagram of a wireless communication system <part-num-ref name="wireless communication system">100</part-num-ref>
|
| 76 |
+
is shown for sharing podcast information in accordance with an embodiment herein. The podcast information can be carried in a mobile device or a wireless communication device <part-num-ref name="wireless communication device">101</part-num-ref>
|
| 77 |
+
such as a selective call receiver or transceiver that can include a transceiver <part-num-ref name="transceiver">102</part-num-ref>
|
| 78 |
+
and a processor <part-num-ref name="processor">104</part-num-ref>
|
| 79 |
+
coupled to the transceiver <part-num-ref name="transceiver">102.</part-num-ref>
|
| 80 |
+
The processor <part-num-ref name="processor">104</part-num-ref>
|
| 81 |
+
can be programmed to receive podcast information and other information and/or content over a wireless network or a wired network via a local access point <part-num-ref name="local access point">150</part-num-ref>
|
| 82 |
+
device network gateway for example. Note, the transceiver <part-num-ref name="transceiver">102</part-num-ref>
|
| 83 |
+
can be a part of a cellular phone, a satellite phone, a smart phone, a laptop computer, a personal digital assistant, or a two-way messaging device or other communication device and the local access point <part-num-ref name="local access point">150</part-num-ref>
|
| 84 |
+
can be any type of connection to podcast content such as an Internet connection. </p>
|
| 85 |
+
<p id="p-18" num="18">[0015] The wireless communication device <part-num-ref name="wireless communication device">101</part-num-ref>
|
| 86 |
+
can further include a user interface <part-num-ref name="user interface">106</part-num-ref>
|
| 87 |
+
having a presentation system <part-num-ref name="presentation system">114</part-num-ref>
|
| 88 |
+
(such as audio speakers and amplifiers) and a display <part-num-ref name="display">112.</part-num-ref>
|
| 89 |
+
The wireless communication device <part-num-ref name="wireless communication device">101</part-num-ref>
|
| 90 |
+
can further include a keypad <part-num-ref name="keypad">116,</part-num-ref>
|
| 91 |
+
a memory <part-num-ref name="memory">105</part-num-ref>
|
| 92 |
+
for storing URLs, metadata, podcast content (etc.), and a power supply <part-num-ref name="power supply">110.</part-num-ref>
|
| 93 |
+
The device <part-num-ref name="device">101</part-num-ref>
|
| 94 |
+
can further include a digital rights management module <part-num-ref name="digital rights management module">107</part-num-ref>
|
| 95 |
+
which can be part of the memory <part-num-ref name="memory">105.</part-num-ref>
|
| 96 |
+
The wireless communication device <part-num-ref name="wireless communication device">101</part-num-ref>
|
| 97 |
+
can further optionally or alternatively include a data bus, link, or interface <part-num-ref name="data bus, link, or interface">108</part-num-ref>
|
| 98 |
+
for coupling the processor <part-num-ref name="processor">104</part-num-ref>
|
| 99 |
+
with the gateway <part-num-ref name="gateway">150</part-num-ref>
|
| 100 |
+
in a wired or tethered fashion as <boundary-data type="header">
|
| 101 |
+
<confidence value="8">5</confidence>
|
| 102 |
+
</boundary-data>
|
| 103 |
+
<page-break num="6"/>
|
| 104 |
+
<boundary-data type="header">Attorney Docket No.: CE15281JSW_Kreitzer</boundary-data>
|
| 105 |
+
<boundary-data type="header">(7463-186)</boundary-data>
|
| 106 |
+
opposed to a wireless link. The wireless transceiver <part-num-ref name="wireless transceiver">102</part-num-ref>
|
| 107 |
+
can utilize existing technology for exchanging wireless messages with a base station <part-num-ref name="base station">118</part-num-ref>
|
| 108 |
+
over a link or network to communicate to another wireless device <part-num-ref name="link or network to communicate to another wireless device">103</part-num-ref>
|
| 109 |
+
that the user of device <part-num-ref name="user of device">101</part-num-ref>
|
| 110 |
+
wishes to share podcast information with. Once the wireless device <part-num-ref name="wireless device">101</part-num-ref>
|
| 111 |
+
transmits a podcast link or URL and other metadata to the wireless device <part-num-ref name="wireless device">103,</part-num-ref>
|
| 112 |
+
the wireless device <part-num-ref name="wireless device">103</part-num-ref>
|
| 113 |
+
can retrieve the podcast content from an appropriate network gateway <part-num-ref name="appropriate network gateway">155</part-num-ref>
|
| 114 |
+
such as an internet connection via their personal computer <part-num-ref name="internet connection via their personal computer">153</part-num-ref>
|
| 115 |
+
for example. The wireless device may also be able to retrieve podcast content using its own high-speed wireless data connection, if available, as an alternative to connecting to the internet via a personal computer <part-num-ref name="personal computer">153.</part-num-ref>
|
| 116 |
+
Of course, the device <part-num-ref name="device">101</part-num-ref>
|
| 117 |
+
can also communicate directly to device <part-num-ref name="can also communicate directly to device">103</part-num-ref>
|
| 118 |
+
if applicable wireless technologies are utilized (Bluetooth, WiFi, Talkaround, etc.). The wireless technology used can be any wireless technology such as, for example, GSM (Global System for Mobile communication), TDMA (Time Division Multiple Access), or CDMA (Code Division Multiple Access), just to mention a few. </p>
|
| 119 |
+
<p id="p-19" num="19">[0016] The processor <part-num-ref name="processor">104</part-num-ref>
|
| 120 |
+
can use computing and/or processing such as a microprocessor and/or a DSP (Digital Signal Processor) technology. </p>
|
| 121 |
+
<p id="p-20" num="20">Additionally, the processor <part-num-ref name="processor">104</part-num-ref>
|
| 122 |
+
can include media such as RAM (Random Access Memory), DRAM (Dynamic RAM), ROM (Read Only Memory), and/or Flash memory for data processing and storage. The presentation system <part-num-ref name="presentation system">114</part-num-ref>
|
| 123 |
+
can use audio technology for intercepting and conveying audible signals to or from a user of the wireless communication device <part-num-ref name="wireless communication device">101.</part-num-ref>
|
| 124 |
+
The display <part-num-ref name="display">112</part-num-ref>
|
| 125 |
+
can also utilize technology such as an LCD (Liquid Crystal Display) for conveying images to the user with an optional backlight. The keypad <part-num-ref name="keypad">116</part-num-ref>
|
| 126 |
+
can be an input device coupled to the processor <part-num-ref name="processor">104</part-num-ref>
|
| 127 |
+
for intercepting tactile responses from the user and can also include its own backlight. These responses can be, for instance, tactile responses that represent telephone number dialing for accessing another end user or passwords or account numbers enabling the retrieval of licensed content. Generally speaking, the keypad <part-num-ref name="keypad">116</part-num-ref>
|
| 128 |
+
serves to control operations of the wireless communication device <part-num-ref name="wireless communication device">101</part-num-ref>
|
| 129 |
+
<boundary-data type="header">
|
| 130 |
+
<confidence value="8">6</confidence>
|
| 131 |
+
</boundary-data>
|
| 132 |
+
<page-break num="7"/>
|
| 133 |
+
<boundary-data type="header">Attorney Docket No.: CE15281JSW_Kreitzer</boundary-data>
|
| 134 |
+
<boundary-data type="header">(7463-186)</boundary-data>
|
| 135 |
+
[0017] The power supply <part-num-ref name="power supply">110</part-num-ref>
|
| 136 |
+
utilizes energy conversion technology for supply energy to the aforementioned components of the wireless communication device <part-num-ref name="wireless communication device">101.</part-num-ref>
|
| 137 |
+
The power supply <part-num-ref name="power supply">110</part-num-ref>
|
| 138 |
+
can be, for instance, a portable battery-operated supply for portable applications of the wireless communication device <part-num-ref name="wireless communication device">101.</part-num-ref>
|
| 139 |
+
</p>
|
| 140 |
+
<p id="p-21" num="21">[0018] Embodiments herein can utilize push-to-talk (PTT) or push-to- connect (PTx) (109) or messaging technologies to forward a podcast link while listening to the podcast. Furthermore, links to segments of a podcast rather than the whole can be forwarded. Also, metadata can be added to the link to convey additional information along with the podcast link.</p>
|
| 141 |
+
<p id="p-22" num="22">[0019] As previously mentioned, podcasting is a fast growing medium that allows almost anyone with a personal computer to produce radio or video shows that are posted for download over the internet. There are over <part-num-ref name="internet. There are over">5000</part-num-ref>
|
| 142 |
+
podcasts currently available including many amateur podcasts as well as professional shows from sources such as the BBC and National Public Radio. </p>
|
| 143 |
+
<p id="p-23" num="23">A typical podcast listening setup includes podcatcher software installed on a listeners personal computer which allows users to subscribe to podcasts and automatically download new shows when they are made available.</p>
|
| 144 |
+
<p id="p-24" num="24">Downloaded shows can be transferred to portable MP3 players including dedicated devices such as the iPOD or MP3-equipped mobile phones for listening on-the-go.</p>
|
| 145 |
+
<p id="p-25" num="25">[0020] While the iPod is the namesake for podcasting, mobile phones such as iDEN phones by Motorola, Inc. offer the potential for new capabilities that go beyond what today's MP3 players can do. Although other transmission technologies can by used, certain embodiments herein can leverage PTT technology to share podcasts with friends or colleagues in an easy fashion.</p>
|
| 146 |
+
<p id="p-26" num="26">[0021] Currently, podcast listeners must sort through the thousands of available podcasts using web-based directories such as PodcastAlley.com or a podcatcher with built-in directories such as iTunes or iPodder. While these directories offer search capabilities and sorting-by-subject, it's still a chore to <boundary-data type="header">
|
| 147 |
+
<confidence value="7">7</confidence>
|
| 148 |
+
</boundary-data>
|
| 149 |
+
<page-break num="8"/>
|
| 150 |
+
<boundary-data type="header">Attorney Docket No.: CE1528<confidence value="5">1</confidence>
|
| 151 |
+
JSW_Kreitzer </boundary-data>
|
| 152 |
+
<boundary-data type="header">(7463-186)</boundary-data>
|
| 153 |
+
find the shows that best suit one's interests. And, the task is made more daunting because you have to subscribe, download, and listen to shows before you can make a judgment about whether a given show is "a keeper<confidence value="68">".</confidence>
|
| 154 |
+
</p>
|
| 155 |
+
<p id="p-27" num="27">[0022] Embodiments herein enable a way to share great podcasts that users have found with their friends and colleagues while they are listening to a podcast on their mobile phone. A user can refer the podcast (or a link thereto) to another user perhaps because it is very entertaining or contains information that would be of interest to the other party.</p>
|
| 156 |
+
<p id="p-28" num="28">[0023] While listening to the podcast, a user can press the PTT button <part-num-ref name="PTT button">109</part-num-ref>
|
| 157 |
+
on the phone and select a contact from their contact list as a target. Rather than send the entire podcast, which could be quite large (30-50MB is common), the phone can send a URL link and a description of the podcast to the other party. Upon receiving the link, the other party can opt to accept or reject the recommendation. If accepted, the recipient's phone can enter the URL into a podcast subscription queue in the handset. At a later point in time, perhaps at the end of the day, the recipient <part-num-ref name="recipient">(103)</part-num-ref>
|
| 158 |
+
can likely synchronize their phone with their personal computer podcast client application (residing on their personal computer 153), sometimes called a podcatcher, to get the latest podcasts. In addition to the usual process of downloading podcasts to the phone, the podcatcher software can take the additional step of querying the podcast subscription list in the phone and can discover that the user had accepted a subscription to a new podcast. This can trigger the podcatcher to subscribe and download the new podcast. As previously noted, some wireless devices will have a high-bandwidth connection (3G, 4G) and podcatcher software built-in which can eliminate the need to synchronize with a personal computer. In such an instance, the user of the remote device can receive the link and subscribe immediately rather than having to wait to synchronize with a personal computer. </p>
|
| 159 |
+
<p id="p-29" num="29">[0024] Note, the podcast link is sent while listening to the podcast rather than as a simple email attachment that is sent at sometime other than while <boundary-data type="header">
|
| 160 |
+
<confidence value="8">8</confidence>
|
| 161 |
+
</boundary-data>
|
| 162 |
+
<page-break num="9"/>
|
| 163 |
+
<boundary-data type="header">Attorney Docket No.: CE15281JSW_Kreitzer</boundary-data>
|
| 164 |
+
<boundary-data type="header">(7463-186)</boundary-data>
|
| 165 |
+
listening. This real time transfer allows for a greater degree of collaboration between the two users and offers the potential for new services. </p>
|
| 166 |
+
<p id="p-30" num="30">[0025] Although the process of sending a link to a podcast is described so that an entire podcast can be subscribed and downloaded, other embodiments herein can send a link to a subset of a podcast. As an example, suppose an interview that was part of a longer podcast found to be interesting to the sender and likely to the recipient is all the sender wants to send to the recipient rather than the entire podcast, then the sender can add a start and stop time to the link. In other words, just a subset of a podcast can be specified. A possible usage example can enable a user listening to a podcast to bookmark a start and stop point in the podcast and forward the link to another party. As before, the party can accept the link and once they synchronize with their podcatcher client, the podcast will be downloaded and truncated so that just the specified part of the podcast is transferred to the user's phone.</p>
|
| 167 |
+
<p id="p-31" num="31">[0026] Below, are examples of URLs for standard and bookmarked podcasts:</p>
|
| 168 |
+
<p id="p-32" num="32">http:<confidence value="66">//</confidence>
|
| 169 |
+
www.host.com/podcast.xml ;standard podcast http://www.host.com/podcast.xm<confidence value="5">l</confidence>
|
| 170 |
+
, start=hhmmss, <confidence value="22222222222">stop=hhmmss</confidence>
|
| 171 |
+
;with bookmarks [0027] The bookmarks are versatile and can be used to quote just a section somewhere in the middle of the podcast. The bookmarks can also be used with only a start or only an end point in order to specify a section of a podcast that goes from the beginning to some intermediate point or from an intermediate point to the end of the podcast. </p>
|
| 172 |
+
<p id="p-33" num="33">[0028] Another aspect allows a podcast audio file to be accompanied by a sidecar file containing bookmarks that mark sections of the podcast. In this case, links that are sent via PTT to other users can contain start=#bookmark and stop=#bookmark statements that would symbolically specify start and stop points. For example:</p>
|
| 173 |
+
<p id="p-34" num="34">http:<confidence value="5">/</confidence>
|
| 174 |
+
/www.host.com/podcast.xm<confidence value="4">l</confidence>
|
| 175 |
+
, <confidence value="2222222222222222">start=#bookmarkl</confidence>
|
| 176 |
+
, stop=#bookmark2 <boundary-data type="header">
|
| 177 |
+
<confidence value="8">9</confidence>
|
| 178 |
+
</boundary-data>
|
| 179 |
+
<page-break num="10"/>
|
| 180 |
+
<boundary-data type="header">Attorney Docket No.: CE15281JSW_Kreitzer</boundary-data>
|
| 181 |
+
<boundary-data type="header">(7463-186)</boundary-data>
|
| 182 |
+
[0029] The sidecar files might be a list of bookmark names along with a time index for each bookmark. This file can be implemented in XML or any other suitable format. Furthermore, the bookmarks can be accompanied by URLs that link websites to the time-related bookmarks. This can be used by the recipient phone to access the website when a bookmark is passed during playing of a podcast. The sidecar files can also contain other objects such as images, text, or multimedia that is played in association with the podcast. </p>
|
| 183 |
+
<p id="p-35" num="35">[0030] Yet another aspect is that additional metadata can be appended to the podcast links. This appended metadata can include links to other websites or data that is sent along with the podcast link. This is useful, for example, if the sender wants the podcast link to be accompanied by a link to the senders Blog (weblog), moblog (mobile weblog), vlog (video blog), social contact site, or contact info from the sender such as a vcard record. The metadata can also include a note to the recipient perhaps explaining the reason for forwarding the podcast link. Here are examples of how the metadata could be sent:</p>
|
| 184 |
+
<p id="p-36" num="36">http:<confidence value="5">/</confidence>
|
| 185 |
+
/www.host.com/podcast.xml, metadata="www.blog.com/myBlog" http:<confidence value="5">/</confidence>
|
| 186 |
+
/www.host.com/podcast.xm<confidence value="4">l</confidence>
|
| 187 |
+
, metadata=<confidence value="5">"</confidence>
|
| 188 |
+
Check out this great podcast...Jenna" [0031] Furthermore, the metadata can also include a user rating of the podcast, or text, audio or video commentary to accompany the podcast link (obviously, audio or video metadata would occupy considerably more bandwidth, but is feasible in a high-speed link). The target address to whom the podcast link is being sent could be one of the following: </p>
|
| 189 |
+
<p id="p-37" num="37">1. UFMI, IP address or any other PTT addressing method.</p>
|
| 190 |
+
<p id="p-38" num="38">2. SMS, MMS, or similar multimedia messaging address.</p>
|
| 191 |
+
<p id="p-39" num="39">3. The target address could also include a return address (the senders address), so that the recipient can respond back with a comment, rating, or just a word of thanks.</p>
|
| 192 |
+
<boundary-data type="header">
|
| 193 |
+
<confidence value="88">10</confidence>
|
| 194 |
+
</boundary-data>
|
| 195 |
+
<boundary-data type="header">Attorney Docket No.: CE<confidence value="5">1</confidence>
|
| 196 |
+
5281JSW_Kreitzer </boundary-data>
|
| 197 |
+
<boundary-data type="header">(7463-186)</boundary-data>
|
| 198 |
+
<p id="p-40" num="40">
|
| 199 |
+
<page-break num="11"/>
|
| 200 |
+
[0032] The carrier medium for the podcast links can include any of the following: </p>
|
| 201 |
+
<p id="p-41" num="41">1. Push-to-Talk (PTT) service based on iDEN, Vo<confidence value="5">I</confidence>
|
| 202 |
+
P, or any other PTT technology. </p>
|
| 203 |
+
<p id="p-42" num="42">2. email, MMS, or any other messaging technology provided that the link is formed and sent while listening to the podcast.</p>
|
| 204 |
+
<p id="p-43" num="43">[0033] Referring to FIG. 2, a flow chart illustrating a method <part-num-ref name="method">200</part-num-ref>
|
| 205 |
+
of sharing podcast information including the step <part-num-ref name="step">202</part-num-ref>
|
| 206 |
+
of playing a podcast having associated metadata on a wireless communication device and transferring a link and the associated metadata to a remote device while playing the podcast on the wireless communication device at step <part-num-ref name="wireless communication device at step">205.</part-num-ref>
|
| 207 |
+
The method <part-num-ref name="method">200</part-num-ref>
|
| 208 |
+
can further include the optional step <part-num-ref name="optional step">203</part-num-ref>
|
| 209 |
+
of creating a hierarchy of metadata at the wireless communication device enabling a sender to mark a URL associated with the podcast, mark a starting point for a portion of the podcast, or mark an ending point for the podcast. The method <part-num-ref name="method">200</part-num-ref>
|
| 210 |
+
can further include the step <part-num-ref name="step">204</part-num-ref>
|
| 211 |
+
of creating a hierarchy of metadata at the wireless communication device enabling a sender to attach additional metadata to the associated metadata including links to other websites, links to a sender's weblog, mobile weblog, or video blog, or a sender's contact information. </p>
|
| 212 |
+
<p id="p-44" num="44">[0034] The method <part-num-ref name="method">200</part-num-ref>
|
| 213 |
+
can further include the step <part-num-ref name="step">206</part-num-ref>
|
| 214 |
+
of receiving the link and associated metadata and decoding the associated metadata at the remote device. Decoding can involve decoding constructs including at least a Universal Resource Locator (URL) for downloading the podcast, or constructs having start times for the podcast, end times for the podcast, bookmarks for portions of the podcast, digital rights management information, display description, podcast category, or relevant images. The associated metadata can include URLs for mobile blogging, a sender's weblog, a video blog, a social contact site, contact information from a sender, or a vCard record. The method <part-num-ref name="method">200</part-num-ref>
|
| 215 |
+
can further include the step <part-num-ref name="step">208</part-num-ref>
|
| 216 |
+
of coupling the remote device to a high bandwidth channel for downloading the podcast. The coupling can <boundary-data type="header">
|
| 217 |
+
<confidence value="88">11</confidence>
|
| 218 |
+
</boundary-data>
|
| 219 |
+
<page-break num="12"/>
|
| 220 |
+
<boundary-data type="header">Attorney Docket No.: CE15281JSW_Kreitzer</boundary-data>
|
| 221 |
+
<boundary-data type="header">(7463-186)</boundary-data>
|
| 222 |
+
involve placing the wireless communication device in a cradle and downloading the podcast over a secondary network serving as the high bandwidth channel. </p>
|
| 223 |
+
<p id="p-45" num="45">[0035] In light of the foregoing description, it should be recognized that embodiments in accordance with the present invention can be realized in hardware, software<confidence value="5">,</confidence>
|
| 224 |
+
or a combination of hardware and software. A network or system according to the present invention can be realized in a centralized fashion in one computer system or processor, or in a distributed fashion where different elements are spread across several interconnected computer systems or processors (such as a microprocessor and a DSP). Any kind of computer system, or other apparatus adapted for carrying out the functions described herein, is suited. A typical combination of hardware and software could be a general purpose computer system with a computer program that, when being loaded and executed, controls the computer system such that it carries out the functions described herein. </p>
|
| 225 |
+
<p id="p-46" num="46">[0036] In light of the foregoing description, it should also be recognized that embodiments in accordance with the present invention can be realized in numerous configurations contemplated to be within the scope and spirit of the claims. Additionally, the description above is intended by way of example only and is not intended to limit the present invention in any way, except as set forth in the following claims.</p>
|
| 226 |
+
<boundary-data type="header">
|
| 227 |
+
<confidence value="88">12</confidence>
|
| 228 |
+
</boundary-data>
|
| 229 |
+
</description>
|
| 230 |
+
</us-patent-application>
|
| 231 |
+
|
applicant/11357130.xml
ADDED
|
@@ -0,0 +1,30 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>11357130</doc-number>
|
| 8 |
+
<date>2008-10-20</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<p id="p-1" num="1">AMENDMENT UNDER 37 C.F.R. <confidence value="4">§</confidence>
|
| 14 |
+
1.111 Attorney Docket No.: Q93202 Application No.: 11/357,130 </p>
|
| 15 |
+
<heading id="h-1">AMENDMENTS TO THE SPECIFICATION</heading>
|
| 16 |
+
<p id="p-2" num="2">Please insert the following section heading on page <part-num-ref name="following section heading on page">3</part-num-ref>
|
| 17 |
+
after line 1: </p>
|
| 18 |
+
<heading id="h-2">BRIEF SUMMARY</heading>
|
| 19 |
+
<p id="p-3" num="3">Please insert the following section heading on page <part-num-ref name="following section heading on page">5</part-num-ref>
|
| 20 |
+
after line 20: </p>
|
| 21 |
+
<heading id="h-3">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
|
| 22 |
+
<p id="p-4" num="4">Please insert the following section heading on page <part-num-ref name="following section heading on page">6</part-num-ref>
|
| 23 |
+
after line 2: </p>
|
| 24 |
+
<heading id="h-4">DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS</heading>
|
| 25 |
+
<p id="p-5" num="5">
|
| 26 |
+
<confidence value="8">2</confidence>
|
| 27 |
+
</p>
|
| 28 |
+
</description>
|
| 29 |
+
</us-patent-application>
|
| 30 |
+
|
applicant/11368298.xml
ADDED
|
@@ -0,0 +1,31 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>11368298</doc-number>
|
| 8 |
+
<date>2009-12-02</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<heading id="h-1">IN THE SPECIFICATION:</heading>
|
| 14 |
+
<p id="p-1" num="1">Please amend the paragraph beginning on page <part-num-ref name="paragraph beginning on page">55,</part-num-ref>
|
| 15 |
+
line 10: </p>
|
| 16 |
+
<p id="p-2" num="2">Referring now to FIGURES 9-11, the novel metal alloy <part-num-ref name="novel metal alloy">40</part-num-ref>
|
| 17 |
+
of stent <part-num-ref name="of stent">20</part-num-ref>
|
| 18 |
+
includes one or more needles or micro-needles <part-num-ref name="includes one or more needles or micro-needles">200,</part-num-ref>
|
| 19 |
+
<part-num-ref name="includes one or more needles or micro-needles 200,">210,</part-num-ref>
|
| 20 |
+
<part-num-ref name="includes one or more needles or micro-needles 200, 210,">220</part-num-ref>
|
| 21 |
+
formed on the surface of the novel metal alloy. </p>
|
| 22 |
+
<p id="p-3" num="3">These needles or micro-needles can be formed by MEMS (e.g., micro-machining, etc.) technology and/or by other processes. As illustrated in FIGURES [[8-10]] 9-11, the needles or micro-needles can have a variety of shapes and sizes. The needles or micro-needles can be at least partially formed from one or more polymers and/or biological agents. It can be appreciated that the needles or micro-needles can be at least partially formed of other of additional material such as, but not limited to one or more adhesives, etc. As illustrated in FIGURE 9, the needles or micro-needles include a combination of one or more polymers <part-num-ref name="combination of one or more polymers">232</part-num-ref>
|
| 23 |
+
and/or one or more biological agents <part-num-ref name="and/or one or more biological agents">230.</part-num-ref>
|
| 24 |
+
As can be appreciated, one or more layer of one or more biological agents and/or polymers can be coated on the needles or micro-needles; however, this is not required. </p>
|
| 25 |
+
<p id="p-4" num="4">When the one or more needles or micro-needles include and/or are coated with one or more biological agents, such biological agents can include, but are not limited to, trapidil, trapidil derivatives, 5-Phenylmethimazole, 5-Phenylmethimazole derivatives, GM-CSF, GM-CSF derivatives, or combinations thereof; however other or additional biological agents can be used.</p>
|
| 26 |
+
<p id="p-5" num="5">The use of one or more biological agents to coat the top surface of the needles or micro-needles can provide a burst of biological agent in the interior of the blood vessel and/or the blood vessel itself during and/or after insertion of the stent.</p>
|
| 27 |
+
<p id="p-6" num="6">Page 2 of <part-num-ref name="of">14</part-num-ref>
|
| 28 |
+
</p>
|
| 29 |
+
</description>
|
| 30 |
+
</us-patent-application>
|
| 31 |
+
|
applicant/11391033.xml
ADDED
|
@@ -0,0 +1,560 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>11391033</doc-number>
|
| 8 |
+
<date>2006-03-28</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<boundary-data type="header">ORACLE CONFIDENTIAL</boundary-data>
|
| 14 |
+
<p id="p-1" num="1">"Express Mail" Mailing Label No. EV 836102025 US </p>
|
| 15 |
+
<heading id="h-1">PATENT APPLICATION</heading>
|
| 16 |
+
<p id="p-2" num="2">ATTORNEY DOCKET NO. <confidence value="5">O</confidence>
|
| 17 |
+
R05-18701 </p>
|
| 18 |
+
<heading id="h-2">UNITED STATES UTILITY PATENT APPLICATION</heading>
|
| 19 |
+
<heading id="h-3">FOR</heading>
|
| 20 |
+
<heading id="h-4">METHOD AND APPARATUS FOR</heading>
|
| 21 |
+
<heading id="h-5">MODIFYING A ROW IN A DATABASE TABLE</heading>
|
| 22 |
+
<heading id="h-6">TO INCLUDE META-DATA</heading>
|
| 23 |
+
<heading id="h-7">INVENTOR:</heading>
|
| 24 |
+
<p id="p-3" num="3">Daniel ManHung Wong Oracle Corporation 500 Oracle Parkway Redwood Shores, CA <part-num-ref name="Oracle Parkway Redwood Shores, CA">94065</part-num-ref>
|
| 25 |
+
<boundary-data type="header">Attorney Docket No. <confidence value="6855">OR05</confidence>
|
| 26 |
+
-18701 Inventor: Daniel ManHung Wong </boundary-data>
|
| 27 |
+
<boundary-data type="header">
|
| 28 |
+
<confidence value="85">DJ</confidence>
|
| 29 |
+
H G:\ORACLE CORPORATION\<confidence value="5">O</confidence>
|
| 30 |
+
R05\<confidence value="5">O</confidence>
|
| 31 |
+
R05-<confidence value="5">1</confidence>
|
| 32 |
+
8701\<confidence value="5">O</confidence>
|
| 33 |
+
R05-<confidence value="5">1</confidence>
|
| 34 |
+
8701 <confidence value="222222222222222">APPLICATION.DOC</confidence>
|
| 35 |
+
</boundary-data>
|
| 36 |
+
<boundary-data type="header">Oracle Matter No. OID-2005-187-0<confidence value="8">1</confidence>
|
| 37 |
+
</boundary-data>
|
| 38 |
+
<page-break num="2"/>
|
| 39 |
+
<boundary-data type="header">ORACLE CONFIDENTIAL</boundary-data>
|
| 40 |
+
</p>
|
| 41 |
+
<heading id="h-8">METHOD AND APPARATUS FOR</heading>
|
| 42 |
+
<heading id="h-9">MODIFYING A ROW IN A DATABASE TABLE</heading>
|
| 43 |
+
<heading id="h-10">TO INCLUDE META-DATA</heading>
|
| 44 |
+
<p id="p-4" num="4">
|
| 45 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 46 |
+
Inventor: Daniel ManHung Wong </p>
|
| 47 |
+
<heading id="h-11">BACKGROUND</heading>
|
| 48 |
+
<p id="p-5" num="5">Field of the Invention <boundary-data type="line-number">10 </boundary-data>
|
| 49 |
+
<confidence value="5">[</confidence>
|
| 50 |
+
0001<confidence value="5">]</confidence>
|
| 51 |
+
The present invention relates to databases. More specifically, the present invention relates to a method and an apparatus for modifying a row in a database to include meta-data. </p>
|
| 52 |
+
<p id="p-6" num="6">Related Art <boundary-data type="line-number">15 </boundary-data>
|
| 53 |
+
<confidence value="5">[</confidence>
|
| 54 |
+
0002] Database administrators and application developers often find the need to tag rows in database tables with information related to the rows. For example, an administrator may find it useful to know when data was inserted into a database table, or when a row in a database table was last updated. This information can serve various purposes, and is especially useful for facilitating <boundary-data type="line-number">20 </boundary-data>
|
| 55 |
+
auditing operations and performing security tasks. </p>
|
| 56 |
+
<p id="p-7" num="7">
|
| 57 |
+
<confidence value="5">[</confidence>
|
| 58 |
+
0003<confidence value="5">]</confidence>
|
| 59 |
+
One common method for tagging rows in a database table involves inserting an additional column into the database table. The additional column can be used to store any type of information related to rows in the table that an administrator or an organization may need. However, there is presently no easy <boundary-data type="line-number">25 </boundary-data>
|
| 60 |
+
way to ensure the integrity of the data in the additional column without a significant amount of additional effort. Any user who has access to the database <boundary-data type="header">
|
| 61 |
+
<confidence value="1">1</confidence>
|
| 62 |
+
</boundary-data>
|
| 63 |
+
<boundary-data type="header">Attorney Docket No. <confidence value="5">O</confidence>
|
| 64 |
+
R05-1870<confidence value="6">1</confidence>
|
| 65 |
+
<confidence value="6">I</confidence>
|
| 66 |
+
nventor: Daniel ManHung Wong </boundary-data>
|
| 67 |
+
<boundary-data type="header">DJH <confidence value="222222222">V:\ORACLE</confidence>
|
| 68 |
+
CORPORATION\<confidence value="5">O</confidence>
|
| 69 |
+
R05\<confidence value="5">O</confidence>
|
| 70 |
+
R05-1870<confidence value="686">1\O</confidence>
|
| 71 |
+
R05-18701 APPLICATION.DOC </boundary-data>
|
| 72 |
+
<boundary-data type="header">Oracle Matter No. <confidence value="66">OI</confidence>
|
| 73 |
+
D-2005-187-01 </boundary-data>
|
| 74 |
+
<page-break num="3"/>
|
| 75 |
+
<boundary-data type="header">ORACLE CONFIDENTIA<confidence value="8">L</confidence>
|
| 76 |
+
</boundary-data>
|
| 77 |
+
table can alter the data in the additional column, which can cause security problems that can mitigate the benefits of using the additional column. </p>
|
| 78 |
+
<p id="p-8" num="8">
|
| 79 |
+
<confidence value="5">[</confidence>
|
| 80 |
+
0004<confidence value="5">]</confidence>
|
| 81 |
+
Hence, what is needed is a method for associating information with data in a database table without the above-mentioned problems. </p>
|
| 82 |
+
<p id="p-9" num="9">
|
| 83 |
+
<boundary-data type="line-number">
|
| 84 |
+
<confidence value="8">5</confidence>
|
| 85 |
+
</boundary-data>
|
| 86 |
+
</p>
|
| 87 |
+
<heading id="h-12">SUMMARY</heading>
|
| 88 |
+
<p id="p-10" num="10">
|
| 89 |
+
<confidence value="5">[</confidence>
|
| 90 |
+
0005<confidence value="5">]</confidence>
|
| 91 |
+
One embodiment of the present invention provides a database system that facilitates modif<confidence value="8">y</confidence>
|
| 92 |
+
ing a row in a database table to include meta- data about operations performed on the row. During operation, the database receives a <boundary-data type="line-number">10 </boundary-data>
|
| 93 |
+
command to perform an operation on a row in a table of the database. The database then determines if executing the command necessitates updating an extensible row descriptor for the row, wherein the extensible row descriptor is a field in the row that contains meta-data about operations performed on the row. If so, the database updates the extensible row descriptor in a manner defined by an <boundary-data type="line-number">15 </boundary-data>
|
| 94 |
+
update rule for the extensible row descriptor. </p>
|
| 95 |
+
<p id="p-11" num="11">
|
| 96 |
+
<confidence value="5">[</confidence>
|
| 97 |
+
0006<confidence value="5">]</confidence>
|
| 98 |
+
In a variation on this embodiment, the update rule can include a set of update rules. </p>
|
| 99 |
+
<p id="p-12" num="12">
|
| 100 |
+
<confidence value="5">[</confidence>
|
| 101 |
+
0007] In a variation on this embodiment, the extensible row descriptor can only be updated by the database, and cannot be modified by a user. </p>
|
| 102 |
+
<p id="p-13" num="13">
|
| 103 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 104 |
+
<confidence value="5">[</confidence>
|
| 105 |
+
0008<confidence value="5">]</confidence>
|
| 106 |
+
In a variation on this embodiment, the update rule can be defined by an owner of the table, or a super-user. </p>
|
| 107 |
+
<p id="p-14" num="14">
|
| 108 |
+
<confidence value="5">[</confidence>
|
| 109 |
+
0009<confidence value="5">]</confidence>
|
| 110 |
+
In a variation on this embodiment, the extensible row descriptor can contain any meta-data associated with operations performed on the row that is known by the database, or that can be obtained by the database via communication <boundary-data type="line-number">25 </boundary-data>
|
| 111 |
+
with a third-party system. This can include, but is not limited to, security attributes (such as a username of a user who last updated the row), a timestamp of <boundary-data type="header">
|
| 112 |
+
<confidence value="8">2</confidence>
|
| 113 |
+
</boundary-data>
|
| 114 |
+
<boundary-data type="header">Attorney Docket No. <confidence value="5">O</confidence>
|
| 115 |
+
R05-18701 Inventor: Daniel ManHung Wong </boundary-data>
|
| 116 |
+
<boundary-data type="header">DJH V:\ORACLE CORP<confidence value="4">O</confidence>
|
| 117 |
+
RATIO<confidence value="66585664888848885858885">N\OR05\oR05-18701\OR05-</confidence>
|
| 118 |
+
18701 <confidence value="222222222222222">APPLICATION.DOC</confidence>
|
| 119 |
+
</boundary-data>
|
| 120 |
+
<boundary-data type="header">Oracle Matter No. O<confidence value="5">I</confidence>
|
| 121 |
+
D-2005-187-<confidence value="54">0l</confidence>
|
| 122 |
+
</boundary-data>
|
| 123 |
+
<page-break num="4"/>
|
| 124 |
+
<boundary-data type="header">ORACLE CONFIDENTIAL</boundary-data>
|
| 125 |
+
the last update, the System Change Number (SCN) of the last update, or the application module that performed the last update. </p>
|
| 126 |
+
<p id="p-15" num="15">
|
| 127 |
+
<confidence value="5">[</confidence>
|
| 128 |
+
0010<confidence value="5">]</confidence>
|
| 129 |
+
In a variation on this embodiment, the operation can include an update operation, an insert operation, a delete operation, or a select operation. </p>
|
| 130 |
+
<p id="p-16" num="16">
|
| 131 |
+
<boundary-data type="line-number">
|
| 132 |
+
<confidence value="8">5</confidence>
|
| 133 |
+
</boundary-data>
|
| 134 |
+
<confidence value="5">[</confidence>
|
| 135 |
+
0011<confidence value="5">]</confidence>
|
| 136 |
+
In a variation on this embodiment, determining if the command necessitates updating an extensible row descriptor involves using an update rule to determine if the extensible row descriptor needs to be updated. </p>
|
| 137 |
+
<p id="p-17" num="17">
|
| 138 |
+
<confidence value="5">[</confidence>
|
| 139 |
+
0012<confidence value="5">]</confidence>
|
| 140 |
+
In a variation on this embodiment, the system creates the table by receiving a definition for the extensible row descriptor, receiving a definition for <boundary-data type="line-number">10 </boundary-data>
|
| 141 |
+
the update rule, and incorporating the extensible row descriptor and the update rule into the table while creating the table. </p>
|
| 142 |
+
<heading id="h-13">BRIEF DESCRIPTION OF THE FIGURES</heading>
|
| 143 |
+
<p id="p-18" num="18">
|
| 144 |
+
<confidence value="5">[</confidence>
|
| 145 |
+
0013<confidence value="5">]</confidence>
|
| 146 |
+
FIG. <confidence value="4">1</confidence>
|
| 147 |
+
illustrates a computing environment in accordance with an <boundary-data type="line-number">15 </boundary-data>
|
| 148 |
+
embodiment of the present invention. </p>
|
| 149 |
+
<p id="p-19" num="19">
|
| 150 |
+
<confidence value="5">[</confidence>
|
| 151 |
+
0014<confidence value="5">]</confidence>
|
| 152 |
+
FIG. 2 illustrates an existing database table. </p>
|
| 153 |
+
<p id="p-20" num="20">
|
| 154 |
+
<confidence value="5">[</confidence>
|
| 155 |
+
0015<confidence value="5">]</confidence>
|
| 156 |
+
FIG. 3 illustrates a database table with an extensible row descriptor in accordance with an embodiment of the present invention. </p>
|
| 157 |
+
<p id="p-21" num="21">
|
| 158 |
+
<confidence value="5">[</confidence>
|
| 159 |
+
0016] FIG. 4 illustrates an update rule in accordance with an embodiment <boundary-data type="line-number">20 </boundary-data>
|
| 160 |
+
of the present invention. </p>
|
| 161 |
+
<p id="p-22" num="22">
|
| 162 |
+
<confidence value="5">[</confidence>
|
| 163 |
+
0017<confidence value="5">]</confidence>
|
| 164 |
+
FIG. 5 presents a flowchart illustrating the row modification process in accordance with an embodiment of the present invention. </p>
|
| 165 |
+
<p id="p-23" num="23">
|
| 166 |
+
<confidence value="5">[</confidence>
|
| 167 |
+
0018<confidence value="5">]</confidence>
|
| 168 |
+
FIG. 6 presents a flowchart illustrating the database table creation process in accordance with an embodiment of the present invention. </p>
|
| 169 |
+
<p id="p-24" num="24">
|
| 170 |
+
<boundary-data type="line-number">
|
| 171 |
+
<confidence value="88">25</confidence>
|
| 172 |
+
</boundary-data>
|
| 173 |
+
<boundary-data type="header">
|
| 174 |
+
<confidence value="8">3</confidence>
|
| 175 |
+
</boundary-data>
|
| 176 |
+
<boundary-data type="header">Attorney Docket No. OR<confidence value="56">05</confidence>
|
| 177 |
+
-1870<confidence value="5">1</confidence>
|
| 178 |
+
Inventor: Daniel ManHung Wong </boundary-data>
|
| 179 |
+
<boundary-data type="header">DJH V:\ORACLE CORPORATION\<confidence value="5">O</confidence>
|
| 180 |
+
R05\<confidence value="4">o</confidence>
|
| 181 |
+
R05-1870<confidence value="686">1\O</confidence>
|
| 182 |
+
R05-<confidence value="5">1</confidence>
|
| 183 |
+
8701 <confidence value="222222222222222">APPLICATION.DOC</confidence>
|
| 184 |
+
</boundary-data>
|
| 185 |
+
<boundary-data type="header">Oracle Matter No. OID-2005-187-<confidence value="66">01</confidence>
|
| 186 |
+
</boundary-data>
|
| 187 |
+
<page-break num="5"/>
|
| 188 |
+
<boundary-data type="header">ORACLE CONFIDENTIAL</boundary-data>
|
| 189 |
+
</p>
|
| 190 |
+
<heading id="h-14">DETAILED DESCRIPTION</heading>
|
| 191 |
+
<p id="p-25" num="25">
|
| 192 |
+
<confidence value="5">[</confidence>
|
| 193 |
+
0019] The following description is presented to enable any person skilled in the art to make and use the invention, and is provided in the context of a particular application and its requirements. Various modifications to the disclosed <boundary-data type="line-number">5 </boundary-data>
|
| 194 |
+
embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the present invention. Thus, the present invention is not intended to be limited to the embodiments shown, but is to be accorded the widest scope consistent with the principles and features <boundary-data type="line-number">10 </boundary-data>
|
| 195 |
+
disclosed herein. </p>
|
| 196 |
+
<p id="p-26" num="26">
|
| 197 |
+
<confidence value="5">[</confidence>
|
| 198 |
+
0020] The data structures and code described in this detailed description are typically stored on a co<confidence value="7">m</confidence>
|
| 199 |
+
puter readable storage medium, which may be any device or medium that can store code and/or data for use by a computer system. </p>
|
| 200 |
+
<p id="p-27" num="27">This includes, but is not limited to, magnetic and optical storage devices such as <boundary-data type="line-number">15 </boundary-data>
|
| 201 |
+
disk drives, magnetic tape, CDs (compact discs), and DVDs (digital versatile discs or digital video discs). </p>
|
| 202 |
+
<p id="p-28" num="28">Overview <confidence value="5">[</confidence>
|
| 203 |
+
0021<confidence value="5">]</confidence>
|
| 204 |
+
One embodiment of the present invention teaches a method for <boundary-data type="line-number">20 </boundary-data>
|
| 205 |
+
tagging a row in a database with meta-data related to operations performed on the database row. Upon creation of a database table, the database receives an extensible row descriptor definition and an update rule definition. The extensible row descriptor is a column in the database table that a user, a super-user, or an administrator cannot modify. Only the database can modify the extensible row <boundary-data type="line-number">25 </boundary-data>
|
| 206 |
+
descriptor. Hence, the extensible row descriptor is a special column type that the database manages. </p>
|
| 207 |
+
<boundary-data type="header">
|
| 208 |
+
<confidence value="8">4</confidence>
|
| 209 |
+
</boundary-data>
|
| 210 |
+
<boundary-data type="header">Attorney Docket No. <confidence value="5">O</confidence>
|
| 211 |
+
R05-18701 Inventor: Daniel ManHung Wong </boundary-data>
|
| 212 |
+
<boundary-data type="header">DJH V:\ORACLE CORPORATION\<confidence value="5">O</confidence>
|
| 213 |
+
R05\<confidence value="5">O</confidence>
|
| 214 |
+
R05-<confidence value="4">1</confidence>
|
| 215 |
+
870<confidence value="585">1\O</confidence>
|
| 216 |
+
R05-18701 APPLICATION.DOC </boundary-data>
|
| 217 |
+
<boundary-data type="header">Oracle Matter No. O<confidence value="4">I</confidence>
|
| 218 |
+
D-2005-187-<confidence value="66">01</confidence>
|
| 219 |
+
</boundary-data>
|
| 220 |
+
<boundary-data type="header">ORACLE CONFIDENTIAL</boundary-data>
|
| 221 |
+
<p id="p-29" num="29">
|
| 222 |
+
<page-break num="6"/>
|
| 223 |
+
<confidence value="5">[</confidence>
|
| 224 |
+
0022<confidence value="5">]</confidence>
|
| 225 |
+
In one embodiment of the present invention, an attempt to issue a command that modifies the extensible row descriptor results in the failed attempt being recorded within the extensible row descriptor. </p>
|
| 226 |
+
<p id="p-30" num="30">
|
| 227 |
+
<confidence value="5">[</confidence>
|
| 228 |
+
0023<confidence value="5">]</confidence>
|
| 229 |
+
In one embodiment of the present invention, the update rule <boundary-data type="line-number">5 </boundary-data>
|
| 230 |
+
defines what information is stored in the extensible row descriptor. The update rule instructs the database on how to manage the extensible row descriptor column for the user. For example, the update rule can define when and how the extensible row descriptor can be updated. </p>
|
| 231 |
+
<p id="p-31" num="31">
|
| 232 |
+
<confidence value="5">[</confidence>
|
| 233 |
+
0024<confidence value="5">]</confidence>
|
| 234 |
+
In one embodiment of the present invention, a user can perform an <boundary-data type="line-number">10 </boundary-data>
|
| 235 |
+
operation, such as a SELECT operation, on the extensible row descriptor as long as the operation does not attempt to modify the extensible row descriptor. </p>
|
| 236 |
+
<p id="p-32" num="32">
|
| 237 |
+
<confidence value="5">[</confidence>
|
| 238 |
+
0025<confidence value="5">]</confidence>
|
| 239 |
+
In one embodiment of the present invention, the database does not require the definition of an extensible row descriptor. In this embodiment the extensible row descriptor is optional. However, if an extensible row descriptor is <boundary-data type="line-number">15 </boundary-data>
|
| 240 |
+
defined, then an update rule can also be defined. </p>
|
| 241 |
+
<p id="p-33" num="33">
|
| 242 |
+
<confidence value="5">[</confidence>
|
| 243 |
+
0026<confidence value="5">]</confidence>
|
| 244 |
+
In one embodiment of the present invention, the extensible row descriptor and/or the update rule is pre-defined by an administrator. In this embodiment, upon creation of a database table, the extensible row descriptor is automatically inserted into the database table. </p>
|
| 245 |
+
<p id="p-34" num="34">
|
| 246 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 247 |
+
<confidence value="5">[</confidence>
|
| 248 |
+
0027<confidence value="5">]</confidence>
|
| 249 |
+
In one embodiment of the present invention, the extensible row descriptor and the update rule are implemented as an extension to standard Structured Query Language (SQL) syntax. </p>
|
| 250 |
+
<p id="p-35" num="35">Computin<confidence value="8">g</confidence>
|
| 251 |
+
Environment <boundary-data type="line-number">25 </boundary-data>
|
| 252 |
+
<confidence value="5">[</confidence>
|
| 253 |
+
0028<confidence value="5">]</confidence>
|
| 254 |
+
FIG. 1 illustrates a computing environment <part-num-ref name="computing environment">100</part-num-ref>
|
| 255 |
+
in accordance with an embodiment of the present invention. Computing environment <part-num-ref name="present invention. Computing environment">100</part-num-ref>
|
| 256 |
+
can <boundary-data type="header">
|
| 257 |
+
<confidence value="8">5</confidence>
|
| 258 |
+
</boundary-data>
|
| 259 |
+
<boundary-data type="header">Attorney Docket No. <confidence value="5">O</confidence>
|
| 260 |
+
R05-18701 Inventor: Daniel ManHung Wong </boundary-data>
|
| 261 |
+
<boundary-data type="header">DJH V:\ORACLE CORPORATION\OR<confidence value="56">05</confidence>
|
| 262 |
+
\OR<confidence value="568">05-</confidence>
|
| 263 |
+
1870<confidence value="686">1\O</confidence>
|
| 264 |
+
R05-<confidence value="5">1</confidence>
|
| 265 |
+
8701 <confidence value="222222222222222">APPLICATION.DOC</confidence>
|
| 266 |
+
</boundary-data>
|
| 267 |
+
<boundary-data type="header">Oracle Matter No. OID-2005-187-0 <confidence value="5">1</confidence>
|
| 268 |
+
</boundary-data>
|
| 269 |
+
<page-break num="7"/>
|
| 270 |
+
<boundary-data type="header">ORACLE CONFIDENTIAL</boundary-data>
|
| 271 |
+
generally include any type of computer system, including, but not limited to, a computer system based on a microprocessor, a mainframe computer, a digital signal processor, a portable computing device, a personal organizer, a device controller, and a computational engine within an appliance. Computing <boundary-data type="line-number">5 </boundary-data>
|
| 272 |
+
environment <part-num-ref name="appliance. Computing environment">100</part-num-ref>
|
| 273 |
+
includes client <part-num-ref name="includes client">102,</part-num-ref>
|
| 274 |
+
database <part-num-ref name="includes client 102, database">104,</part-num-ref>
|
| 275 |
+
server <part-num-ref name="includes client 102, database 104, server">106,</part-num-ref>
|
| 276 |
+
and network <part-num-ref name="includes client 102, database 104, server 106, and network">108.</part-num-ref>
|
| 277 |
+
</p>
|
| 278 |
+
<p id="p-36" num="36">Client 102 can communicate with database <part-num-ref name="can communicate with database">104</part-num-ref>
|
| 279 |
+
and server <part-num-ref name="and server">106</part-num-ref>
|
| 280 |
+
via network <part-num-ref name="via network">108.</part-num-ref>
|
| 281 |
+
</p>
|
| 282 |
+
<p id="p-37" num="37">User 110 can communicate directly with client <part-num-ref name="can communicate directly with client">102.</part-num-ref>
|
| 283 |
+
</p>
|
| 284 |
+
<p id="p-38" num="38">
|
| 285 |
+
<confidence value="5">[</confidence>
|
| 286 |
+
0029<confidence value="5">]</confidence>
|
| 287 |
+
Client 102 can generally include any node on a network including computational capability and including a mechanism for communicating across <boundary-data type="line-number">10 </boundary-data>
|
| 288 |
+
the network. </p>
|
| 289 |
+
<p id="p-39" num="39">
|
| 290 |
+
<confidence value="5">[</confidence>
|
| 291 |
+
0030<confidence value="5">]</confidence>
|
| 292 |
+
Database 104 can generally include any type of system for storing<confidence value="4">.</confidence>
|
| 293 |
+
</p>
|
| 294 |
+
<p id="p-40" num="40">data in non-volatile storage. This includes, but is not limited to, systems based upon magnetic, optical, and magneto-optical storage devices, as well as storage devices based on flash memory and/or battery-backed up memory.</p>
|
| 295 |
+
<p id="p-41" num="41">
|
| 296 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 297 |
+
<confidence value="5">[</confidence>
|
| 298 |
+
0031<confidence value="5">]</confidence>
|
| 299 |
+
Server 106 can generally include any computational node including a mechanism for servicing requests from a client for computational and/or data storage resources. </p>
|
| 300 |
+
<p id="p-42" num="42">
|
| 301 |
+
<confidence value="5">[</confidence>
|
| 302 |
+
0032] Network 108 can generally include any type of wired or wireless communication channel capable of coupling together computing nodes. This <boundary-data type="line-number">20 </boundary-data>
|
| 303 |
+
includes, but is not limited to, a local area network, a wide area network, or a combination of networks. In one embodiment of the present invention, network <part-num-ref name="present invention, network">108</part-num-ref>
|
| 304 |
+
includes the Internet. </p>
|
| 305 |
+
<p id="p-43" num="43">[0033<confidence value="5">]</confidence>
|
| 306 |
+
In one embodiment of the present invention, user <part-num-ref name="present invention, user">110</part-num-ref>
|
| 307 |
+
creates a new database table in database <part-num-ref name="new database table in database">104</part-num-ref>
|
| 308 |
+
via client <part-num-ref name="via client">102.</part-num-ref>
|
| 309 |
+
Database <part-num-ref name="via client 102. Database">104</part-num-ref>
|
| 310 |
+
then prompts user <boundary-data type="line-number">25 </boundary-data>
|
| 311 |
+
<part-num-ref name="then prompts user">110</part-num-ref>
|
| 312 |
+
to create an extensible row descriptor and an update rule for the new database table. </p>
|
| 313 |
+
<boundary-data type="header">
|
| 314 |
+
<confidence value="8">6</confidence>
|
| 315 |
+
</boundary-data>
|
| 316 |
+
<boundary-data type="header">Attorney Docket No. <confidence value="5">O</confidence>
|
| 317 |
+
R05-18701 <confidence value="5">I</confidence>
|
| 318 |
+
nventor: Daniel ManHung Wong </boundary-data>
|
| 319 |
+
<boundary-data type="header">DJH V:\ORACLE CORPORATION\<confidence value="5">O</confidence>
|
| 320 |
+
R05\<confidence value="5">O</confidence>
|
| 321 |
+
R05-<confidence value="5">1</confidence>
|
| 322 |
+
8701\<confidence value="5">O</confidence>
|
| 323 |
+
R05-18701 <confidence value="222222222222222">APPLICATION.DOC</confidence>
|
| 324 |
+
</boundary-data>
|
| 325 |
+
<boundary-data type="header">Oracle Matter No. <confidence value="51">OI</confidence>
|
| 326 |
+
D-2005-187-<confidence value="68">01</confidence>
|
| 327 |
+
</boundary-data>
|
| 328 |
+
<boundary-data type="header">ORACLE CONFIDENTIAL</boundary-data>
|
| 329 |
+
<p id="p-44" num="44">
|
| 330 |
+
<page-break num="8"/>
|
| 331 |
+
<confidence value="5">[</confidence>
|
| 332 |
+
0034<confidence value="5">1</confidence>
|
| 333 |
+
In one embodiment of the present invention, the update rule includes specifies that the database communicates with server <part-num-ref name="database communicates with server">106</part-num-ref>
|
| 334 |
+
to obtain information that is used in updating the extensible row descriptor. This information can include, but is not limited to, the organization that the user is a <boundary-data type="line-number">5 </boundary-data>
|
| 335 |
+
member of, the security level of the user, and the employee identification number of the user. This embodiment facilitates the use of information that may be readily available in another system, but that is not internally available to database <part-num-ref name="use of information that may be readily available in another system, but that is not internally available to database">104.</part-num-ref>
|
| 336 |
+
</p>
|
| 337 |
+
<p id="p-45" num="45">
|
| 338 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 339 |
+
Existing Database Table <confidence value="5">[</confidence>
|
| 340 |
+
0035<confidence value="5">1</confidence>
|
| 341 |
+
FIG. 2 illustrates an existing database table <part-num-ref name="existing database table">200.</part-num-ref>
|
| 342 |
+
Database table <part-num-ref name="existing database table 200. Database table">200</part-num-ref>
|
| 343 |
+
is an example of an existing database table. Database table <part-num-ref name="existing database table. Database table">200</part-num-ref>
|
| 344 |
+
represents a portion of an employee list. Note that in an environment where multiple users have permission to modify database table <part-num-ref name="environment where multiple users have permission to modify database table">200,</part-num-ref>
|
| 345 |
+
user <part-num-ref name="environment where multiple users have permission to modify database table 200, user">110</part-num-ref>
|
| 346 |
+
can modify <boundary-data type="line-number">15 </boundary-data>
|
| 347 |
+
database table <part-num-ref name="can modify database table">200</part-num-ref>
|
| 348 |
+
without accountability because there is no way to know which user modified database table <part-num-ref name="without accountability because there is no way to know which user modified database table">200.</part-num-ref>
|
| 349 |
+
One embodiment of the present invention solves this problem by recording which user modified database table <part-num-ref name="present invention solves this problem by recording which user modified database table">200</part-num-ref>
|
| 350 |
+
in an extensible row descriptor within the table, thus provides accountability for all database operations. </p>
|
| 351 |
+
<p id="p-46" num="46">
|
| 352 |
+
<boundary-data type="line-number">
|
| 353 |
+
<confidence value="88">20</confidence>
|
| 354 |
+
</boundary-data>
|
| 355 |
+
Database Table With Extensible Row Descriptor <confidence value="5">1</confidence>
|
| 356 |
+
0036<confidence value="5">1</confidence>
|
| 357 |
+
FIG. 3 illustrates a database table <part-num-ref name="database table">300</part-num-ref>
|
| 358 |
+
with an extensible row descriptor <part-num-ref name="extensible row descriptor">302</part-num-ref>
|
| 359 |
+
in accordance with an embodiment of the present invention. </p>
|
| 360 |
+
<p id="p-47" num="47">Extensible row descriptor 302 can only be modified by the database in a manner <boundary-data type="line-number">25 </boundary-data>
|
| 361 |
+
defined by the update rule, and cannot be modified by a user. In one embodiment of the present invention, a super-user cannot modify the update rule. </p>
|
| 362 |
+
<boundary-data type="header">
|
| 363 |
+
<confidence value="8">7</confidence>
|
| 364 |
+
</boundary-data>
|
| 365 |
+
<boundary-data type="header">Attorney Docket No. OR<confidence value="56">05</confidence>
|
| 366 |
+
-18701 Inventor: Daniel Man<confidence value="5">H</confidence>
|
| 367 |
+
ung Wong </boundary-data>
|
| 368 |
+
<boundary-data type="header">
|
| 369 |
+
<confidence value="85">DJ</confidence>
|
| 370 |
+
H V:\ORACLE <confidence value="84">CO</confidence>
|
| 371 |
+
RPORATION\<confidence value="5">O</confidence>
|
| 372 |
+
R05\<confidence value="4">o</confidence>
|
| 373 |
+
R05-18701<confidence value="86">\O</confidence>
|
| 374 |
+
R05-18701 APPLICATION.DOC </boundary-data>
|
| 375 |
+
<boundary-data type="header">Oracle Matter No. OID-2005-187-<confidence value="66">01</confidence>
|
| 376 |
+
</boundary-data>
|
| 377 |
+
<boundary-data type="header">ORACLE CONFIDENTIA<confidence value="8">L</confidence>
|
| 378 |
+
</boundary-data>
|
| 379 |
+
<p id="p-48" num="48">
|
| 380 |
+
<page-break num="9"/>
|
| 381 |
+
<confidence value="5">[</confidence>
|
| 382 |
+
0037] Note that extensible row descriptor 302 can include any meta-data associated with an operation performed on the corresponding row. This can include, but is not limited to, security attributes (such as a <confidence value="22222222">username</confidence>
|
| 383 |
+
of a user who last updated the row), a timestamp of the last update, the System Change Number <boundary-data type="line-number">5 </boundary-data>
|
| 384 |
+
(SCN) of the last update, or the application module that performed the last update. </p>
|
| 385 |
+
<p id="p-49" num="49">
|
| 386 |
+
<confidence value="5">[</confidence>
|
| 387 |
+
0038<confidence value="5">]</confidence>
|
| 388 |
+
In one embodiment of the present invention, extensible row descriptor <part-num-ref name="present invention, extensible row descriptor">302</part-num-ref>
|
| 389 |
+
can include multiple fields and/or columns. </p>
|
| 390 |
+
<p id="p-50" num="50">
|
| 391 |
+
<confidence value="5">[</confidence>
|
| 392 |
+
0039<confidence value="5">]</confidence>
|
| 393 |
+
In one embodiment of the present invention, each cell in the extensible row descriptor <part-num-ref name="extensible row descriptor">302</part-num-ref>
|
| 394 |
+
column is defined to store the name and <boundary-data type="line-number">10 </boundary-data>
|
| 395 |
+
identification number of the last user who modified a particular row within database table <part-num-ref name="particular row within database table">300.</part-num-ref>
|
| 396 |
+
For example, cell <part-num-ref name="particular row within database table 300. For example, cell">304</part-num-ref>
|
| 397 |
+
reveals that the last user to modify the first row in database table <part-num-ref name="first row in database table">300</part-num-ref>
|
| 398 |
+
was user "JO<confidence value="8">H</confidence>
|
| 399 |
+
N" whose identification number is "13579". If a problem is discovered in the information stored in the first row of database table <part-num-ref name="first row of database table">300,</part-num-ref>
|
| 400 |
+
user "JOHN" will be consulted in an attempt to restore <boundary-data type="line-number">15 </boundary-data>
|
| 401 |
+
database table <part-num-ref name="attempt to restore database table">300</part-num-ref>
|
| 402 |
+
to its proper state. However, if a discrepancy is found in conventional database table <part-num-ref name="discrepancy is found in conventional database table">200,</part-num-ref>
|
| 403 |
+
it will be much more difficult, and perhaps impossible, to identify which user caused the problem found in database table <part-num-ref name="problem found in database table">200.</part-num-ref>
|
| 404 |
+
</p>
|
| 405 |
+
<p id="p-51" num="51">
|
| 406 |
+
<confidence value="5">[</confidence>
|
| 407 |
+
0040<confidence value="5">]</confidence>
|
| 408 |
+
In one embodiment of the present invention, deleting a row in <boundary-data type="line-number">20 </boundary-data>
|
| 409 |
+
database table <part-num-ref name="row in database table">300</part-num-ref>
|
| 410 |
+
does not result in the deletion of the extensible row descriptor information as illustrated by cell <part-num-ref name="extensible row descriptor information as illustrated by cell">306.</part-num-ref>
|
| 411 |
+
This is advantageous because it facilitates in determining when a row is improperly deleted. </p>
|
| 412 |
+
<p id="p-52" num="52">
|
| 413 |
+
<confidence value="5">[</confidence>
|
| 414 |
+
0041<confidence value="5">]</confidence>
|
| 415 |
+
In one embodiment of the present invention, deleting a row in database table <part-num-ref name="row in database table">300</part-num-ref>
|
| 416 |
+
results in the deletion of the extensible row descriptor entry for <boundary-data type="line-number">25 </boundary-data>
|
| 417 |
+
the deleted row. </p>
|
| 418 |
+
<boundary-data type="header">
|
| 419 |
+
<confidence value="8">8</confidence>
|
| 420 |
+
</boundary-data>
|
| 421 |
+
<boundary-data type="header">Attorney Docket No. <confidence value="5">O</confidence>
|
| 422 |
+
R05-<confidence value="5">1</confidence>
|
| 423 |
+
8701 Inventor: Daniel ManHung Wong </boundary-data>
|
| 424 |
+
<boundary-data type="header">DJH V:\ORACLE CORPORATION\<confidence value="5">O</confidence>
|
| 425 |
+
R05\<confidence value="48568">OR05-</confidence>
|
| 426 |
+
1870<confidence value="686">1\O</confidence>
|
| 427 |
+
R05-<confidence value="5">1</confidence>
|
| 428 |
+
8701 <confidence value="222222222222222">APPLICATION.DOC</confidence>
|
| 429 |
+
</boundary-data>
|
| 430 |
+
<boundary-data type="header">Oracle Matter No. OID-2005-187-0<confidence value="5">1</confidence>
|
| 431 |
+
</boundary-data>
|
| 432 |
+
<boundary-data type="header">ORACLE CONFIDENTIAL</boundary-data>
|
| 433 |
+
<p id="p-53" num="53">
|
| 434 |
+
<page-break num="10"/>
|
| 435 |
+
Update Rule <confidence value="5">[</confidence>
|
| 436 |
+
0042<confidence value="5">]</confidence>
|
| 437 |
+
FIG. 4 illustrates an update rule <part-num-ref name="update rule">400</part-num-ref>
|
| 438 |
+
in accordance with an embodiment of the present invention. Update rule <part-num-ref name="present invention. Update rule">400</part-num-ref>
|
| 439 |
+
specifies what information should be stored in the extensible row descriptor and defines the rules that should <boundary-data type="line-number">5 </boundary-data>
|
| 440 |
+
be used to update the extensible row descriptor. Update rule <part-num-ref name="extensible row descriptor. Update rule">400</part-num-ref>
|
| 441 |
+
includes user name <part-num-ref name="includes user name">402,</part-num-ref>
|
| 442 |
+
identification number <part-num-ref name="includes user name 402, identification number">404,</part-num-ref>
|
| 443 |
+
department <part-num-ref name="includes user name 402, identification number 404, department">406,</part-num-ref>
|
| 444 |
+
and usage rules <part-num-ref name="includes user name 402, identification number 404, department 406, and usage rules">408.</part-num-ref>
|
| 445 |
+
User name <part-num-ref name="includes user name 402, identification number 404, department 406, and usage rules 408. User name">402,</part-num-ref>
|
| 446 |
+
identification number <part-num-ref name="includes user name 402, identification number 404, department 406, and usage rules 408. User name 402, identification number">404,</part-num-ref>
|
| 447 |
+
and department <part-num-ref name="includes user name 402, identification number 404, department 406, and usage rules 408. User name 402, identification number 404, and department">406</part-num-ref>
|
| 448 |
+
are all examples of possible fields that can be included as part of the value of the extensible row descriptor. </p>
|
| 449 |
+
<p id="p-54" num="54">
|
| 450 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 451 |
+
<confidence value="5">[</confidence>
|
| 452 |
+
0043<confidence value="5">]</confidence>
|
| 453 |
+
Usage rules 408 define when the extensible row descriptor should be updated. For example, usage rules <part-num-ref name="extensible row descriptor should be updated. For example, usage rules">408</part-num-ref>
|
| 454 |
+
may specify that any command resulting in modification to a row in the database table should result in the updating of the extensible row descriptor with the information specified in update rule <part-num-ref name="information specified in update rule">400.</part-num-ref>
|
| 455 |
+
Note that update rule <part-num-ref name="information specified in update rule 400. Note that update rule">400</part-num-ref>
|
| 456 |
+
merely provides an example of one possible <boundary-data type="line-number">15 </boundary-data>
|
| 457 |
+
update rule. In general, update rule <part-num-ref name="example of one possible update rule. In general, update rule">400</part-num-ref>
|
| 458 |
+
is not limited to the fields illustrated in FIG. 4. </p>
|
| 459 |
+
<p id="p-55" num="55">
|
| 460 |
+
<confidence value="5">[</confidence>
|
| 461 |
+
0044<confidence value="5">]</confidence>
|
| 462 |
+
In one embodiment of the present invention, each row can have its own update rule. </p>
|
| 463 |
+
<p id="p-56" num="56">
|
| 464 |
+
<confidence value="5">[</confidence>
|
| 465 |
+
0045<confidence value="5">]</confidence>
|
| 466 |
+
In one embodiment of the present invention, update rule <part-num-ref name="present invention, update rule">400</part-num-ref>
|
| 467 |
+
can <boundary-data type="line-number">20 </boundary-data>
|
| 468 |
+
require information that is not stored within the database. In this embodiment, update rule <part-num-ref name="database. In this embodiment, update rule">400</part-num-ref>
|
| 469 |
+
includes instructions and/or commands required to obtain the information that is stored externally to the database. </p>
|
| 470 |
+
<p id="p-57" num="57">Row Modification <boundary-data type="line-number">25 </boundary-data>
|
| 471 |
+
<confidence value="5">[</confidence>
|
| 472 |
+
0046<confidence value="5">]</confidence>
|
| 473 |
+
FIG. 5 presents a flowchart illustrating the row modification process in accordance with an embodiment of the present invention. The process <boundary-data type="header">
|
| 474 |
+
<confidence value="8">9</confidence>
|
| 475 |
+
</boundary-data>
|
| 476 |
+
<boundary-data type="header">Attorney Docket No. <confidence value="5">O</confidence>
|
| 477 |
+
R05-18701 Inventor: Daniel ManHung Wong </boundary-data>
|
| 478 |
+
<boundary-data type="header">
|
| 479 |
+
<confidence value="85">DJ</confidence>
|
| 480 |
+
H V:\ORACLE CORPORATION\OR<confidence value="5668">05\O</confidence>
|
| 481 |
+
R05-1870<confidence value="686">1\O</confidence>
|
| 482 |
+
R05-1870<confidence value="5">1</confidence>
|
| 483 |
+
<confidence value="222222222222222">APPLICATION.DOC</confidence>
|
| 484 |
+
</boundary-data>
|
| 485 |
+
<boundary-data type="header">Oracle Matter No. <confidence value="525">OID</confidence>
|
| 486 |
+
-2005-187-01 </boundary-data>
|
| 487 |
+
<page-break num="11"/>
|
| 488 |
+
<boundary-data type="header">ORACLE CONFIDENTIAL</boundary-data>
|
| 489 |
+
begins when the system receives a command to modify or select a row in a database table (step 500). Note that if the command involves modifying the extensible row descriptor then the database will reject the command. The extensible row descriptor can only be modified by the database and not by a <boundary-data type="line-number">5 </boundary-data>
|
| 490 |
+
command issued by a user. </p>
|
| 491 |
+
<p id="p-58" num="58">
|
| 492 |
+
<confidence value="5">[</confidence>
|
| 493 |
+
0047<confidence value="5">]</confidence>
|
| 494 |
+
The system checks the update rule for the table and/or row that is to be selected or modified (step 502). Next, the system determines if the command necessitates an update of the extensible row descriptor (step 504). The system then determines if an update of the extensible row descriptor is necessary <boundary-data type="line-number">10 </boundary-data>
|
| 495 |
+
by referring to the rules that were defined in the update rule for the particular table and/or row in question. If an update of the extensible row descriptor is not necessary, the system executes the command (step 512). However, if an update of the extensible row descriptor is necessary, the system determines if the update of the extensible row descriptor requires data that is stored externally to the database <boundary-data type="line-number">15 </boundary-data>
|
| 496 |
+
(step 506). If not, the system updates the extensible row descriptor following the usage rules defined in the update rule (step 510). The system then executes the command (step 512). </p>
|
| 497 |
+
<p id="p-59" num="59">
|
| 498 |
+
<confidence value="5">[</confidence>
|
| 499 |
+
0048<confidence value="5">]</confidence>
|
| 500 |
+
On the other hand, if the system does require external data to update the extensible row descriptor, the system obtains the required external data <boundary-data type="line-number">20 </boundary-data>
|
| 501 |
+
from a third-party system (step 508). The system then proceeds to update the extensible row descriptor (step 510). Finally, the system executes the command issued at the beginning of this process (step 512). </p>
|
| 502 |
+
<p id="p-60" num="60">Table Creation <boundary-data type="line-number">25 </boundary-data>
|
| 503 |
+
<confidence value="5">[</confidence>
|
| 504 |
+
0049<confidence value="5">]</confidence>
|
| 505 |
+
FIG. 6 presents a flowchart illustrating the database table creation process in accordance with an embodiment of the present invention. The process <boundary-data type="header">
|
| 506 |
+
<confidence value="88">10</confidence>
|
| 507 |
+
</boundary-data>
|
| 508 |
+
<boundary-data type="header">Attorney Docket No. <confidence value="5">O</confidence>
|
| 509 |
+
R05-18701 Inventor: Daniel ManHung Wong </boundary-data>
|
| 510 |
+
<boundary-data type="header">DJH V:\ORACLE CORPORATION\OR<confidence value="5668">05\O</confidence>
|
| 511 |
+
R05-1870<confidence value="885">1\O</confidence>
|
| 512 |
+
R05-18701 APPLICATION. DOC </boundary-data>
|
| 513 |
+
<boundary-data type="header">Oracle Matter No. O<confidence value="5">I</confidence>
|
| 514 |
+
D-2005-187-01 </boundary-data>
|
| 515 |
+
<page-break num="12"/>
|
| 516 |
+
<boundary-data type="header">ORACLE CONFIDENTIAL</boundary-data>
|
| 517 |
+
begins when a user creates a table (step 600). In doing so, the user defines an extensible row descriptor (step 602). Defining an extensible row descriptor involves defining one or more columns to store meta-data about operations performed on each row. </p>
|
| 518 |
+
<p id="p-61" num="61">
|
| 519 |
+
<boundary-data type="line-number">
|
| 520 |
+
<confidence value="8">5</confidence>
|
| 521 |
+
</boundary-data>
|
| 522 |
+
<confidence value="5">[</confidence>
|
| 523 |
+
0050<confidence value="5">]</confidence>
|
| 524 |
+
In one embodiment of the present invention, an administrator or a super-user pre-defines the extensible row descriptor. </p>
|
| 525 |
+
<p id="p-62" num="62">
|
| 526 |
+
<confidence value="5">[</confidence>
|
| 527 |
+
0051<confidence value="5">]</confidence>
|
| 528 |
+
After the extensible row descriptor has been defined, the user defines the update rule (step 604). Defining the update rule involves specifying when the extensible row descriptor should be updated, and what information <boundary-data type="line-number">10 </boundary-data>
|
| 529 |
+
should be stored in the extensible row descriptor. </p>
|
| 530 |
+
<p id="p-63" num="63">
|
| 531 |
+
<confidence value="5">[</confidence>
|
| 532 |
+
0052<confidence value="5">]</confidence>
|
| 533 |
+
In one embodiment of the present invention, an administrator or super-user pre-defines the update rule. </p>
|
| 534 |
+
<p id="p-64" num="64">
|
| 535 |
+
<confidence value="5">[</confidence>
|
| 536 |
+
0053<confidence value="5">]</confidence>
|
| 537 |
+
The foregoing descriptions of embodiments of the present invention have been presented for purposes of illustration and description only. </p>
|
| 538 |
+
<p id="p-65" num="65">
|
| 539 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 540 |
+
They are not intended to be exhaustive or to limit the present invention to the forms disclosed. Accordingly, many modifications and variations will be apparent to practitioners skilled in the art. Additionally, the above disclosure is not intended to limit the present invention. The scope of the present invention is defined by the appended claims. </p>
|
| 541 |
+
<boundary-data type="header">
|
| 542 |
+
<confidence value="88">11</confidence>
|
| 543 |
+
</boundary-data>
|
| 544 |
+
<boundary-data type="header">Attorney Docket No. <confidence value="5">O</confidence>
|
| 545 |
+
R05-18701 Inventor: Daniel ManHung Wong </boundary-data>
|
| 546 |
+
<boundary-data type="header">
|
| 547 |
+
<confidence value="8522">DJHl</confidence>
|
| 548 |
+
V:\ORACLE CORPORATION\OR<confidence value="56">05</confidence>
|
| 549 |
+
\OR<confidence value="568">05-</confidence>
|
| 550 |
+
18701<confidence value="86">\O</confidence>
|
| 551 |
+
R05<confidence value="68">-1</confidence>
|
| 552 |
+
870<confidence value="5">1</confidence>
|
| 553 |
+
<confidence value="222222222222222">APPLICATION.DOC</confidence>
|
| 554 |
+
</boundary-data>
|
| 555 |
+
<boundary-data type="header">Oracle Matter No. O<confidence value="5">I</confidence>
|
| 556 |
+
D-2005-187-<confidence value="66">01</confidence>
|
| 557 |
+
</boundary-data>
|
| 558 |
+
</description>
|
| 559 |
+
</us-patent-application>
|
| 560 |
+
|
applicant/11400595.xml
ADDED
|
@@ -0,0 +1,425 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>11400595</doc-number>
|
| 8 |
+
<date>2006-04-05</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<boundary-data type="header">8600-0032</boundary-data>
|
| 14 |
+
<boundary-data type="header">05-01589</boundary-data>
|
| 15 |
+
<heading id="h-1">VASO-OCCLUSIVE DEVICES HAVING EXPANDABLE FIBERS</heading>
|
| 16 |
+
<p id="p-1" num="1">Inventor(s):</p>
|
| 17 |
+
<p id="p-2" num="2">
|
| 18 |
+
<confidence value="865">Tri</confidence>
|
| 19 |
+
Tran Mediko Issakhani Assignee: </p>
|
| 20 |
+
<p id="p-3" num="3">Boston Scientific Scimed, Inc.</p>
|
| 21 |
+
<p id="p-4" num="4">Entity Status:</p>
|
| 22 |
+
<p id="p-5" num="5">Large <page-break num="2"/>
|
| 23 |
+
<boundary-data type="header">8600-0032</boundary-data>
|
| 24 |
+
<boundary-data type="header">05-01589</boundary-data>
|
| 25 |
+
<boundary-data type="header">PATENT</boundary-data>
|
| 26 |
+
</p>
|
| 27 |
+
<heading id="h-2">VASO-OCCLUSIVE DEVICES HAVING EXPANDABLE FIBERS</heading>
|
| 28 |
+
<heading id="h-3">FIELD OF THE INVENTION</heading>
|
| 29 |
+
<p id="p-6" num="6">
|
| 30 |
+
<confidence value="5">[</confidence>
|
| 31 |
+
0001<confidence value="5">1</confidence>
|
| 32 |
+
Compositions and methods for repair of aneurysms are described. In particular, <boundary-data type="line-number">5 </boundary-data>
|
| 33 |
+
vaso-occ<confidence value="5">l</confidence>
|
| 34 |
+
usive devices comprising shaped metallic device with attached expansile fibers are described. </p>
|
| 35 |
+
<heading id="h-4">BACKGROUND</heading>
|
| 36 |
+
<p id="p-7" num="7">
|
| 37 |
+
<confidence value="5">[</confidence>
|
| 38 |
+
0002<confidence value="5">1</confidence>
|
| 39 |
+
An aneurysm is a dilation of a blood vessel that poses a risk to health from the <boundary-data type="line-number">10 </boundary-data>
|
| 40 |
+
potential for rupture, clotting, or dissecting. Rupture of an aneurysm in the brain causes stroke, and rupture of an aneurysm in the abdomen causes shock. Cerebral aneurysms are usually detected in patients as the result of a seizure or hemorrhage and can result in significant morbidity or mortality. </p>
|
| 41 |
+
<p id="p-8" num="8">[0003<confidence value="5">]</confidence>
|
| 42 |
+
There are a variety of materials and devices which have been used for treatment <boundary-data type="line-number">15 </boundary-data>
|
| 43 |
+
of aneurysms, including platinum and stainless steel coils, polyvinyl alcohol sponges (Ivalone), and other mechanical devices. For example, vaso-occ<confidence value="5">l</confidence>
|
| 44 |
+
usion devices are surgical implements or implants that are placed within the vasculature of the human body, typically via a catheter, either to block the flow of <confidence value="2222222222222">blood.through</confidence>
|
| 45 |
+
a vessel making up that portion of the vasculature through the formation of an embolus or to form such an embolus within an aneurysm stemming from the <boundary-data type="line-number">20 </boundary-data>
|
| 46 |
+
vessel. </p>
|
| 47 |
+
<p id="p-9" num="9">[0004<confidence value="5">1</confidence>
|
| 48 |
+
One widely used vaso-occlusive device is a helical wire coil having windings which may be dimensioned to engage the walls of the vessels. (See, e.g., U.S. Patent No. </p>
|
| 49 |
+
<p id="p-10" num="10">4,994,069 to Ritchart et al.) Other less stiff helically coiled devices have been described, as well as those involving woven braids. See, e.g., U.S. Patent No. 6,299,627. Vaso-occlusive coils <boundary-data type="line-number">25 </boundary-data>
|
| 50 |
+
having attached fibrous elements are disclosed in U.S. Patent No. 5,833,705 to Ken as well as U.S. Patent No. 5,304,194 to Chee. </p>
|
| 51 |
+
<p id="p-11" num="11">[0005<confidence value="5">]</confidence>
|
| 52 |
+
U.S. Pat. No. 5,354,295 and its parent, U.S. Pat. No. 5,122,136, both to Guglie<confidence value="588">lmi</confidence>
|
| 53 |
+
et al., describe an electrolytically detachable embolic device. Vaso-occlusive coils having little <boundary-data type="header">
|
| 54 |
+
<confidence value="6">1</confidence>
|
| 55 |
+
</boundary-data>
|
| 56 |
+
<page-break num="3"/>
|
| 57 |
+
<boundary-data type="header">8600-0032</boundary-data>
|
| 58 |
+
<boundary-data type="header">05-015<confidence value="88">89</confidence>
|
| 59 |
+
</boundary-data>
|
| 60 |
+
<boundary-data type="header">PATENT</boundary-data>
|
| 61 |
+
or no inherent secondary shape have also been described. For instance, co-owned U.S. Patent Numbers 5,690,666; 5,826,587; and 6,458,119 by Berenstein et al., describes coils having little or no shape after introduction into the vascular space. U.S. Patent No. 5,382,259 describes non- expanding braids covering a primary coil structure. </p>
|
| 62 |
+
<p id="p-12" num="12">
|
| 63 |
+
<boundary-data type="line-number">
|
| 64 |
+
<confidence value="8">5</confidence>
|
| 65 |
+
</boundary-data>
|
| 66 |
+
<confidence value="5">[</confidence>
|
| 67 |
+
0006<confidence value="5">]</confidence>
|
| 68 |
+
Vaso-occlusive compositions comprising one or more expandable hydrogels have also been described. See, e.g., U.S. Patent No. 6,960,617 and 6,113,629. U.S. Patent Nos. </p>
|
| 69 |
+
<p id="p-13" num="13">6,602,261 and 6,238,403 discloses a plurality of expansible hydrogel elements disposed at spaced intervals along a filamentous carrier. U.S. Patent Nos. 6,616,617; 6,475,169; 6,168,570 and 6,159,165 disclose multi-stranded microcable devices, where one or more of the stands may <boundary-data type="line-number">10 </boundary-data>
|
| 70 |
+
be an expandable material. </p>
|
| 71 |
+
<p id="p-14" num="14">[0007] However, there remains a need for vaso-occlusive devices that combine the advantages of metallic vaso-occ<confidence value="5">l</confidence>
|
| 72 |
+
usive devices (e.g., coils) and expansile materials (e.g., hydrogels) in a single vaso-occlusive device. </p>
|
| 73 |
+
<heading id="h-5">SUMMARY</heading>
|
| 74 |
+
<p id="p-15" num="15">
|
| 75 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 76 |
+
[0008] Thus, this invention includes novel occlusive devices as well as methods of using and making these devices. </p>
|
| 77 |
+
<p id="p-16" num="16">
|
| 78 |
+
<confidence value="5">[</confidence>
|
| 79 |
+
0009<confidence value="5">]</confidence>
|
| 80 |
+
In one aspect, the invention includes a vaso-occlusive device comprising a metallic vaso-occlusive device; and one or more fibrous elements, wherein at least one of the <boundary-data type="line-number">20 </boundary-data>
|
| 81 |
+
fibrous elements comprises an expandable material. In certain embodiments, the fibrous elements comprising an expandable material comprise a polymer (e.g., PET) coated or permeated with the expandable material. In other embodiments, the expandable material comprises a hydrogel material. </p>
|
| 82 |
+
<p id="p-17" num="17">
|
| 83 |
+
<confidence value="5">[</confidence>
|
| 84 |
+
0010<confidence value="5">]</confidence>
|
| 85 |
+
In any of the devices described herein, the fibrous elements may be <boundary-data type="line-number">25 </boundary-data>
|
| 86 |
+
monofilaments or multifilaments. In certain embodiments, the fibrous elements comprise at least one monofilament. Multiple monofilaments may be structured over the vaso-occlusive device, for example to form an open-weave structure surrounding the metallic vaso-occlusive device. </p>
|
| 87 |
+
<boundary-data type="header">
|
| 88 |
+
<confidence value="8">2</confidence>
|
| 89 |
+
</boundary-data>
|
| 90 |
+
<boundary-data type="header">8600-0032</boundary-data>
|
| 91 |
+
<boundary-data type="header">05-01589</boundary-data>
|
| 92 |
+
<boundary-data type="header">PATENT</boundary-data>
|
| 93 |
+
<p id="p-18" num="18">
|
| 94 |
+
<page-break num="4"/>
|
| 95 |
+
<confidence value="5">[</confidence>
|
| 96 |
+
0011] Furthermore, in any of the devices described herein, the fibrous elements may be attached to the metallic vaso-occ<confidence value="5">l</confidence>
|
| 97 |
+
usive device at one or more locations. </p>
|
| 98 |
+
<p id="p-19" num="19">[0012] The metallic vaso-occlusive device may comprise any metal, for example a metal selected from the group consisting of nickel, titanium, platinum, gold, tungsten, iridium and <boundary-data type="line-number">5 </boundary-data>
|
| 99 |
+
alloys or combinations thereof. In certain embodiments, the metallic vaso-occ<confidence value="5">l</confidence>
|
| 100 |
+
usive device comprises nitinol and/or platinum. </p>
|
| 101 |
+
<p id="p-20" num="20">[0013] In certain embodiments, the metallic vaso-occlusive device comprises a coil shape. In other embodiments, the metallic vaso-occ<confidence value="5">l</confidence>
|
| 102 |
+
usive device comprises a tubular braid. </p>
|
| 103 |
+
<p id="p-21" num="21">
|
| 104 |
+
<confidence value="5">[</confidence>
|
| 105 |
+
0014] Any of the devices described herein may further comprise one or more additional <boundary-data type="line-number">10 </boundary-data>
|
| 106 |
+
materials, for example, at least one bioactive material. Any of the devices described herein may further comprise a severable junction detachably which may be connected to a pusher element. </p>
|
| 107 |
+
<p id="p-22" num="22">The detachment junction can be positioned anywhere on the device, for example at one or both ends of the device. In certain embodiments, the severable junction(s) are, an electrolytically detachable assembly adapted to detach by imposition of a current; a mechanically detachable <boundary-data type="line-number">15 </boundary-data>
|
| 108 |
+
assembly adapted to detach by movement or pressure; a thermally detachable assembly adapted to detach by localized delivery of heat to the junction; a radiation detachable assembly adapted to detach by delivery of electromagnetic radiation to the junction or combinations thereof. The detachment junction(s) may be attached to one or more expansile fibers material or, preferably, to one or more vaso-occ<confidence value="5">l</confidence>
|
| 109 |
+
usive devices. </p>
|
| 110 |
+
<p id="p-23" num="23">
|
| 111 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 112 |
+
[0015] In another aspect, a method of occluding a body cavity is described, the method comprising introducing any of the devices as described herein into the body cavity. In certain embodiments, the body cavity is an aneurysm. </p>
|
| 113 |
+
<p id="p-24" num="24">[0016] These and other embodiments of the subject invention will readily occur to those of skill in the art in light of the disclosure herein.</p>
|
| 114 |
+
<p id="p-25" num="25">
|
| 115 |
+
<boundary-data type="line-number">
|
| 116 |
+
<confidence value="88">25</confidence>
|
| 117 |
+
</boundary-data>
|
| 118 |
+
</p>
|
| 119 |
+
<heading id="h-6">BRIEF DESCRIPTION OF THE FIGURES</heading>
|
| 120 |
+
<p id="p-26" num="26">[0017] FIG. 1 is a side view of an exemplary device as described herein. The device comprises a metallic vaso-occlusive coil <part-num-ref name="metallic vaso-occlusive coil">10</part-num-ref>
|
| 121 |
+
and expansible fibrous elements <part-num-ref name="and expansible fibrous elements">12.</part-num-ref>
|
| 122 |
+
This <boundary-data type="header">
|
| 123 |
+
<confidence value="8">3</confidence>
|
| 124 |
+
</boundary-data>
|
| 125 |
+
<page-break num="5"/>
|
| 126 |
+
<boundary-data type="header">8600-0032</boundary-data>
|
| 127 |
+
<boundary-data type="header">05-01589</boundary-data>
|
| 128 |
+
<boundary-data type="header">PATENT</boundary-data>
|
| 129 |
+
embodiment shows a device having multiple expandable monofilaments <part-num-ref name="device having multiple expandable monofilaments">12</part-num-ref>
|
| 130 |
+
attached to various winds of the metallic vaso-occlusive coil <part-num-ref name="metallic vaso-occlusive coil">10.</part-num-ref>
|
| 131 |
+
FIG. 1 shows the device when the fibers <part-num-ref name="fibers">12</part-num-ref>
|
| 132 |
+
are not expandable. </p>
|
| 133 |
+
<p id="p-27" num="27">[0018] FIG. 2 is a side view of the exemplary device shown in FIG. 1 and shows the <boundary-data type="line-number">5 </boundary-data>
|
| 134 |
+
device after expansion of the fibrous elements <part-num-ref name="fibrous elements">12.</part-num-ref>
|
| 135 |
+
</p>
|
| 136 |
+
<p id="p-28" num="28">
|
| 137 |
+
<confidence value="5">[</confidence>
|
| 138 |
+
0019<confidence value="5">]</confidence>
|
| 139 |
+
FIG. 3 is a side view of another exemplary device as described herein. The device comprises a metallic vaso-occlusive coil <part-num-ref name="metallic vaso-occlusive coil">20</part-num-ref>
|
| 140 |
+
and expandable fibrous elements <part-num-ref name="and expandable fibrous elements">22.</part-num-ref>
|
| 141 |
+
This embodiment has at least one expansible monofilament fiber <part-num-ref name="and expandable fibrous elements 22. This embodiment has at least one expansible monofilament fiber">22</part-num-ref>
|
| 142 |
+
attached to every wind of the metallic vaso-occlusive coil <part-num-ref name="metallic vaso-occlusive coil">20.</part-num-ref>
|
| 143 |
+
FIG. 3 shows the device when the expandable material of the <boundary-data type="line-number">10 </boundary-data>
|
| 144 |
+
monofilament fibers <part-num-ref name="monofilament fibers">22</part-num-ref>
|
| 145 |
+
is not expanded. </p>
|
| 146 |
+
<p id="p-29" num="29">[0020<confidence value="5">]</confidence>
|
| 147 |
+
FIG. 4 is a side view of the exemplary device shown in FIG. 3 and shows the device after expansion of the expandable materials of the fibers <part-num-ref name="fibers">22.</part-num-ref>
|
| 148 |
+
</p>
|
| 149 |
+
<p id="p-30" num="30">[0021] FIG. 5 is a side view of another exemplary device as described herein. The device comprises a metallic vaso-occlusive coil <part-num-ref name="metallic vaso-occlusive coil">30</part-num-ref>
|
| 150 |
+
and expansible fibrous elements <part-num-ref name="and expansible fibrous elements">32.</part-num-ref>
|
| 151 |
+
The <boundary-data type="line-number">15 </boundary-data>
|
| 152 |
+
expansible fibrous elements <part-num-ref name="expansible fibrous elements">32</part-num-ref>
|
| 153 |
+
form an open-woven lattice over the metallic vaso-occlusive coil <part-num-ref name="metallic vaso-occlusive coil">30.</part-num-ref>
|
| 154 |
+
FIG. 5 shows the device when the expandable fibers <part-num-ref name="expandable fibers">32</part-num-ref>
|
| 155 |
+
are not expanded. </p>
|
| 156 |
+
<p id="p-31" num="31">[0022] FIG. 6 is a side view of the exemplary device shown in FIG. 5 and shows the device after expansion of the fibrous elements <part-num-ref name="fibrous elements">32.</part-num-ref>
|
| 157 |
+
</p>
|
| 158 |
+
<p id="p-32" num="32">[0023] FIG. 7 is a side view of another exemplary device as described herein. The <boundary-data type="line-number">20 </boundary-data>
|
| 159 |
+
device comprises a metallic vaso-occlusive coil <part-num-ref name="metallic vaso-occlusive coil">44</part-num-ref>
|
| 160 |
+
and an expandable monofilament <part-num-ref name="expandable monofilament">42</part-num-ref>
|
| 161 |
+
wrapped loosely around the metallic coil <part-num-ref name="metallic coil">44.</part-num-ref>
|
| 162 |
+
</p>
|
| 163 |
+
<p id="p-33" num="33">
|
| 164 |
+
<confidence value="5">[</confidence>
|
| 165 |
+
0024<confidence value="5">]</confidence>
|
| 166 |
+
FIG. 8 is a side view of another exemplary device as described herein. The device comprises a metallic coil <part-num-ref name="metallic coil">44</part-num-ref>
|
| 167 |
+
and two expandable monofilaments <part-num-ref name="and two expandable monofilaments">42,</part-num-ref>
|
| 168 |
+
<part-num-ref name="and two expandable monofilaments 42,">43</part-num-ref>
|
| 169 |
+
wrapped loosely around the metallic coil <part-num-ref name="metallic coil">44.</part-num-ref>
|
| 170 |
+
</p>
|
| 171 |
+
<p id="p-34" num="34">
|
| 172 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 173 |
+
[0025<confidence value="5">]</confidence>
|
| 174 |
+
It is to be understood that the drawing depicts only exemplary embodiments and are not to be considered limiting in scope. </p>
|
| 175 |
+
<boundary-data type="header">
|
| 176 |
+
<confidence value="8">4</confidence>
|
| 177 |
+
</boundary-data>
|
| 178 |
+
<boundary-data type="header">8600-0032</boundary-data>
|
| 179 |
+
<boundary-data type="header">05-01589</boundary-data>
|
| 180 |
+
<boundary-data type="header">PATENT</boundary-data>
|
| 181 |
+
<heading id="h-7">DETAILED DESCRIPTION</heading>
|
| 182 |
+
<p id="p-35" num="35">
|
| 183 |
+
<page-break num="6"/>
|
| 184 |
+
[0026] Occlusive (e.g., embolic) devices are described. The implantable devices described herein combine the advantages of platinum coils (e.g., enhanced tissue growth and healing) with the advantages of expandable materials (e.g., space-filling). Methods of making <boundary-data type="line-number">
|
| 185 |
+
<confidence value="5">5</confidence>
|
| 186 |
+
</boundary-data>
|
| 187 |
+
and using these vaso-occlusive devices also form aspects of this invention. </p>
|
| 188 |
+
<p id="p-36" num="36">
|
| 189 |
+
<confidence value="5">[</confidence>
|
| 190 |
+
0027<confidence value="5">]</confidence>
|
| 191 |
+
All documents (publications, patents and patent applications) cited herein, whether above or below, are hereby incorporated by reference in their entireties. </p>
|
| 192 |
+
<p id="p-37" num="37">
|
| 193 |
+
<confidence value="5">[</confidence>
|
| 194 |
+
0028] It must be noted that, as used in this specification and the appended claims, the singular forms <confidence value="6666">"a",</confidence>
|
| 195 |
+
<confidence value="66666">"an",</confidence>
|
| 196 |
+
and "the" include plural references unless the content clearly dictates <boundary-data type="line-number">10 </boundary-data>
|
| 197 |
+
otherwise. Thus, for example, reference to an implant comprising "an expandable fiber" includes implants comprising of two or more of such fibers. </p>
|
| 198 |
+
<p id="p-38" num="38">[0029<confidence value="5">]</confidence>
|
| 199 |
+
The implantable devices described herein comprise one or more expandable fibers. The terms "expansile," "expandable," and "expansible" are used interchangeable to refer to any material that is capable of expansion. The material may self-expandable and/or expand <boundary-data type="line-number">15 </boundary-data>
|
| 200 |
+
upon exposure to one or more stimuli (water, light, heat, etc.). </p>
|
| 201 |
+
<p id="p-39" num="39">
|
| 202 |
+
<confidence value="5">[</confidence>
|
| 203 |
+
0030] In certain embodiments, the expansible material comprises a hydrogel that expands upon contact with water. Hydrogels may be biodegradable and/or have regulated expansion. Non-crosslinked hydrogels are described, for example, in U.S. Patent Application No.11/242,981, filed October <part-num-ref name="hydrogel that expands upon contact with water. Hydrogels may be biodegradable and/or have regulated expansion. Non-crosslinked hydrogels are described, for example, in U.S. Patent Application No.11/242,981, filed October">4,</part-num-ref>
|
| 204 |
+
<part-num-ref name="hydrogel that expands upon contact with water. Hydrogels may be biodegradable and/or have regulated expansion. Non-crosslinked hydrogels are described, for example, in U.S. Patent Application No.11/242,981, filed October 4,">2005,</part-num-ref>
|
| 205 |
+
entitled "Self-Expandable Coil is Regulated Expansion," <boundary-data type="line-number">20 </boundary-data>
|
| 206 |
+
incorporated by reference herein in its entirety. </p>
|
| 207 |
+
<p id="p-40" num="40">[0031] Hydrogels are commercially available and well known those of skill in the art.</p>
|
| 208 |
+
<p id="p-41" num="41">See, e.g., U.S. Patent Nos. 6,818,018; 6,602,261; 6,238,403; 6,245,090; 5,823,198; 5,570,585;</p>
|
| 209 |
+
<p id="p-42" num="42">5,456,693; 5,258,042; and 4,663,358, describing water-swellable crosslinked hydrogels and porous hydrated polyvinyl alcohol (PVA) foam gels). Expanding hydrogels can also include, by <boundary-data type="line-number">25 </boundary-data>
|
| 210 |
+
way of example and not by way of limitation, gels formed from polysaccharides and mucopolysaccharides including, but not limited to hyaluronates, pectins, agarose, alginate; </p>
|
| 211 |
+
<p id="p-43" num="43">chitosan, chitosan derivatives such as chitosan modified with fructose, galactose and/or proteins such as collagen, gelatin and albumin; gels formed from proteins such as collagen, gelatin, <boundary-data type="header">
|
| 212 |
+
<confidence value="8">5</confidence>
|
| 213 |
+
</boundary-data>
|
| 214 |
+
<page-break num="7"/>
|
| 215 |
+
<boundary-data type="header">8600-0032</boundary-data>
|
| 216 |
+
<boundary-data type="header">05-01589</boundary-data>
|
| 217 |
+
<boundary-data type="header">PATENT</boundary-data>
|
| 218 |
+
fibronectin, fibrin, albumin, or po<confidence value="8">l</confidence>
|
| 219 |
+
y or copolypeptides; carboxy alkyl celluloses, including but not limited to carboxymethyl cellulose; partially oxidized cellulose; and gels formed from synthetic biodegradable polymers such polyphosphazenes, polyphosphoesters, polyanhydrides, polyethylene oxides, polyethylene oxide-co-polypropyleneoxide block copolymers, polylactides, <boundary-data type="line-number">5 </boundary-data>
|
| 220 |
+
polyglycolide, polycaprolactone, poly(3-hydroxy-butyric acid), polyvinyl alcohols, PEG, dextran, alginic acid and sodium alginate and others such as described in U.S. Patent No. </p>
|
| 221 |
+
<p id="p-44" num="44">4,526,938 to Chirchill, et al.; gels formed from other hydroxy acids; and/or gels formed from other biologically degradable polymers that are non-toxic or are present as metabolites in the body.</p>
|
| 222 |
+
<p id="p-45" num="45">
|
| 223 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 224 |
+
[0032] Furthermore, expansion of the hydrogels may be regulated by including a polymer composition such as the PEO/PLA or PLA-PGA-PEO ratio and/or the length of the PLA-PEO blocks in the PEO-PLA or PLA-PGA-PEO block copolymers (see, e.g., Younes et al. <part-num-ref name="Younes et al.">(1987)</part-num-ref>
|
| 225 |
+
J<confidence value="5">.</confidence>
|
| 226 |
+
</p>
|
| 227 |
+
<p id="p-46" num="46">Biomed. Mater Res 21(11):1301-1306; ) Younes et al. (1988) Biomater Art<confidence value="5">i</confidence>
|
| 228 |
+
f Cells Art<confidence value="5">i</confidence>
|
| 229 |
+
f Organs. </p>
|
| 230 |
+
<p id="p-47" num="47">16(4):705-19) or by the density of physical cross-linking achieved by variation of <boundary-data type="line-number">15 </boundary-data>
|
| 231 |
+
Polymer/Physical cross-linker such as Polymer/Ca ion ratio in Ca-alginate gels. </p>
|
| 232 |
+
<p id="p-48" num="48">[0033] Inorganic expansible materials can also be derived from, by way of example and not by way of limitation, silicones, alumina, and ferric oxide.</p>
|
| 233 |
+
<p id="p-49" num="49">[0034] Expandable materials having increased macroporosity are described, for example, in U.S. Patent Application No. 11/051,578, filed February 4, 2005, entitled "Macroporous <boundary-data type="line-number">20 </boundary-data>
|
| 234 |
+
Materials for Use in Aneurysms," and U.S. Patent Application No. 11/347,080, filed February 2, 2006, entitled "Porous Materials to Enhance Wound Healing in the Aneurysm," both of which documents are incorporated by reference herein in their entireties. </p>
|
| 235 |
+
<p id="p-50" num="50">[0035] Aneurysms treated with metallic (e.g., platinum) vaso-occlusive coils have been shown to have enhanced tissue growth inside the aneurysm as compared to aneurysms treated <boundary-data type="line-number">25 </boundary-data>
|
| 236 |
+
with non-metallic devices (e.g., hydrogels). Enhanced tissue growth promotes faster healing and, in addition, reduces the formation of scar tissue. Reducing scar tissue in turn renders the occluded vessel less susceptible to recanalization. Thus, the vaso-occlusive devices described herein combine the advantages of the healing properties of metallic devices with the <boundary-data type="header">
|
| 237 |
+
<confidence value="8">6</confidence>
|
| 238 |
+
</boundary-data>
|
| 239 |
+
<page-break num="8"/>
|
| 240 |
+
<boundary-data type="header">8600-0032</boundary-data>
|
| 241 |
+
<boundary-data type="header">05-01589</boundary-data>
|
| 242 |
+
<boundary-data type="header">PATENT</boundary-data>
|
| 243 |
+
advantageous volume (space) filling properties of expandable materials, thereby providing devices that reduce the rate of recanalization in aneurysms, particularly wide neck, large-sized and/or bifurcated aneurysms. </p>
|
| 244 |
+
<p id="p-51" num="51">
|
| 245 |
+
<confidence value="5">[</confidence>
|
| 246 |
+
0036<confidence value="5">]</confidence>
|
| 247 |
+
Thus, the devices described herein include at least one metallic vaso-occ<confidence value="5">l</confidence>
|
| 248 |
+
usive <boundary-data type="line-number">5 </boundary-data>
|
| 249 |
+
device. Although depicted in the Figures as a coil, it will be apparent that the metallic vaso- occlusive device may be of a variety of shapes or configuration including, but not limited to, braids, wires, tubes (e.g., perforated or slotted tubes), injection-molded devices, knits and/or woven structures that include at least one metal and the like. See, e.g., U.S. Patent No. 6,533,801 and International Patent Publication WO 02/096273. </p>
|
| 250 |
+
<p id="p-52" num="52">
|
| 251 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 252 |
+
<confidence value="5">[</confidence>
|
| 253 |
+
0037<confidence value="5">]</confidence>
|
| 254 |
+
The metallic vaso-occ<confidence value="5">l</confidence>
|
| 255 |
+
usive device comprise one or more metals or metal alloys, for example, Platinum Group metals, especially platinum, rhodium, palladium, rhenium, as well as tungsten, gold, silver, tantalum, stainless steel and alloys of these metals. Particularly preferred is platinum. In certain embodiments, the metallic device maintains its shape despite being subjected to high stress, for example, "super-elastic alloys" such as nickel/titanium alloys <boundary-data type="line-number">15 </boundary-data>
|
| 256 |
+
(48-58 atomic % nickel and optionally containing modest amounts of iron, also known as nitinol); copper/zinc alloys (38-42 weight % zinc); copper/zinc alloys containing 1-10 weight % of beryllium, silicon, tin, aluminum, or gallium; or nickel/aluminum alloys (36-38 atomic % aluminum). See, e.g., U.S. Pat. Nos. 3,174,851; 3,351,463; and 3,753,700. </p>
|
| 257 |
+
<p id="p-53" num="53">[0038] The metallic vaso-occlusive devices described herein may change shape upon <boundary-data type="line-number">20 </boundary-data>
|
| 258 |
+
release from the restraining member, for example change from a constrained linear form to a relaxed, three-dimensional configuration upon deployment. </p>
|
| 259 |
+
<p id="p-54" num="54">[0039<confidence value="5">]</confidence>
|
| 260 |
+
In addition to the metallic vaso-occlusive device, the devices described herein also include at least one expansible material. The expandable material can be combined with a metallic device in any suitable way. For example, in certain embodiments, the expansible <boundary-data type="line-number">25 </boundary-data>
|
| 261 |
+
material is coated directly onto the metallic device (e.g., coil) such that at least some of the metal remains exposed. Alternatively, the metallic coil and expandable materials can be delivered separately (in an order) to the aneurysm. </p>
|
| 262 |
+
<boundary-data type="header">
|
| 263 |
+
<confidence value="8">7</confidence>
|
| 264 |
+
</boundary-data>
|
| 265 |
+
<boundary-data type="header">8600-0032</boundary-data>
|
| 266 |
+
<boundary-data type="header">05-015<confidence value="88">89</confidence>
|
| 267 |
+
</boundary-data>
|
| 268 |
+
<boundary-data type="header">PATENT</boundary-data>
|
| 269 |
+
<p id="p-55" num="55">
|
| 270 |
+
<page-break num="9"/>
|
| 271 |
+
[0040] In certain preferred embodiments, one or more carriers (e.g., fibrous elements) comprising the expandable material(s) is(are) combined with a metallic device. It will be apparent that the carrier can have any dimensions so long as when it is combined with the metallic device, the metal of the metallic device is at least partially exposed. Furthermore, a <boundary-data type="line-number">5 </boundary-data>
|
| 272 |
+
single device may include carriers of different dimensions. As depicted in the drawings, the carrier for the expansible material(s) can be a fibrous element comprising one or more fibers. </p>
|
| 273 |
+
<p id="p-56" num="56">
|
| 274 |
+
<confidence value="5">[</confidence>
|
| 275 |
+
0041] It will also be apparent that any number of carriers comprising expandable materials can be used on a single device. The spacing and/or dimensions of the carriers may be regular or irregular. In addition, the device may include one or more additional filamentous <boundary-data type="line-number">10 </boundary-data>
|
| 276 |
+
materials that are not expandable. </p>
|
| 277 |
+
<p id="p-57" num="57">
|
| 278 |
+
<confidence value="5">[</confidence>
|
| 279 |
+
0042] When a carrier (e.g., fiber) comprising one or more expandable materials is used, the carrier may be coated or permeated with one or more expandable materials before or after being combined with the metallic vaso-occlusive device. Methods of coating and/or permeating fibrous elements with expandable materials such as hydrogels are known in the art. It is not <boundary-data type="line-number">15 </boundary-data>
|
| 280 |
+
required that every carrier (e.g., fibrous element) comprise expandable material(s). In addition, it will readily apparent that different carriers (e.g., fibrous elements) can comprise different expandable materials or combinations of expandable materials. </p>
|
| 281 |
+
<p id="p-58" num="58">[0043] As noted above, the carrier (e.g., fibrous element) may be combined to the metallic device by any suitable means, including, but not limited to, winding (threading) of the <boundary-data type="line-number">20 </boundary-data>
|
| 282 |
+
fibers through the device, knotting the fibers at one more locations (e.g., knotting the ends to the device), gluing, etc. See, also, U.S. Patent Nos. 5,935,145; 5,833,705; 5,549,624; 5,522,822; </p>
|
| 283 |
+
<p id="p-59" num="59">5,382,259; 5,304,194; and 5,226,911. The specific location(s) of contact (and/or attachment) is(are) not critical. The carrier (e.g., fibrous element) may make a pattern (e.g., open woven structure as shown in FIG<confidence value="5">s</confidence>
|
| 284 |
+
. 5 and 6). Furthermore, the fibrous element(s) may be fully or <boundary-data type="line-number">25 </boundary-data>
|
| 285 |
+
partially exterior and/or interior to the metallic device. </p>
|
| 286 |
+
<p id="p-60" num="60">
|
| 287 |
+
<confidence value="5">[</confidence>
|
| 288 |
+
0044] The carrier (e.g., fiber) may be made from a variety of materials, including but not limited to metals, polymers and combinations thereof, including but not limited to, stainless steel, platinum, kevlar, carbothane, cyanoacrylate, epoxy, poly(ethyleneterephthalate) (PET), <boundary-data type="header">
|
| 289 |
+
<confidence value="8">8</confidence>
|
| 290 |
+
</boundary-data>
|
| 291 |
+
<page-break num="10"/>
|
| 292 |
+
<boundary-data type="header">8600-0032</boundary-data>
|
| 293 |
+
<boundary-data type="header">05-01589</boundary-data>
|
| 294 |
+
<boundary-data type="header">PATENT</boundary-data>
|
| 295 |
+
polytetrafluoroethylene (TeflonTM), polypropylene, polyimide polyethylene, polyglycolic acid, polylactic acid, nylon, polyester, fluoropolymer, and copolymers or combinations thereof. See, e.g., U.S. Patent No. 6,585,754 and 6,280,457 for a description of various polymers. Particularly preferred is a polymer such as PET. Any one device as described herein may include multiple <boundary-data type="line-number">5 </boundary-data>
|
| 296 |
+
carriers (e.g., fibers) comprising different materials. </p>
|
| 297 |
+
<p id="p-61" num="61">
|
| 298 |
+
<confidence value="5">[</confidence>
|
| 299 |
+
0045<confidence value="5">]</confidence>
|
| 300 |
+
The carrier(s) coated and/or permeated with the expandable material may include one or more bundles of individual fibers (e.g., <part-num-ref name="">5</part-num-ref>
|
| 301 |
+
to <part-num-ref name="to">100</part-num-ref>
|
| 302 |
+
fibers per bundle, preferably <part-num-ref name="fibers per bundle, preferably">20</part-num-ref>
|
| 303 |
+
to <part-num-ref name="to">30</part-num-ref>
|
| 304 |
+
fibers per bundle) or one or more monofilaments. Furthermore, one or more bundles and/or one or more monofilaments may be combined with the same device. </p>
|
| 305 |
+
<p id="p-62" num="62">
|
| 306 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 307 |
+
[0046<confidence value="5">]</confidence>
|
| 308 |
+
FIG. 1 depicts an exemplary embodiment of the devices as described herein and depicts a design in which multiple monofilaments comprising expansible materials <part-num-ref name="design in which multiple monofilaments comprising expansible materials">12</part-num-ref>
|
| 309 |
+
are spaced randomly throughout the metallic coil <part-num-ref name="metallic coil">10.</part-num-ref>
|
| 310 |
+
As depicted, multiple monofilaments are attached to the same winds of the coil. It will be apparent that the number of monofilaments attached to particular wind of a coil can vary greatly and that different numbers of fibrous elements may be <boundary-data type="line-number">15 </boundary-data>
|
| 311 |
+
attached to any, some or all of the metallic vaso-occlusive coil. Also shown in FIG. 1 is optional end tip <part-num-ref name="is optional end tip">14.</part-num-ref>
|
| 312 |
+
FIG. 1 shows the device prior to expansion. </p>
|
| 313 |
+
<p id="p-63" num="63">[0047] FIG. 2 shows the device of FIG. 1 following expansion of the expansible fibrous elements. The overall volume taken up by the device is enhanced.</p>
|
| 314 |
+
<p id="p-64" num="64">[0048] FIG. 3 depicts another exemplary embodiment in which a single expandable <boundary-data type="line-number">20 </boundary-data>
|
| 315 |
+
filament <part-num-ref name="single expandable filament">22</part-num-ref>
|
| 316 |
+
is attached at every wind of the metallic coil <part-num-ref name="metallic coil">20.</part-num-ref>
|
| 317 |
+
Optional end cap <part-num-ref name="metallic coil 20. Optional end cap">24</part-num-ref>
|
| 318 |
+
is also shown. </p>
|
| 319 |
+
<p id="p-65" num="65">FIG. 3 shows the device prior to expansion.</p>
|
| 320 |
+
<p id="p-66" num="66">[0049] FIG. 4 shows the device of FIG. 3 after expansion of the expansible fiber.</p>
|
| 321 |
+
<p id="p-67" num="67">
|
| 322 |
+
<confidence value="5">[</confidence>
|
| 323 |
+
0050] FIG. 5 depicts yet another embodiment in which expandable fibers <part-num-ref name="depicts yet another embodiment in which expandable fibers">32</part-num-ref>
|
| 324 |
+
are braided in an open-weave configuration around a metallic coil <part-num-ref name="metallic coil">30.</part-num-ref>
|
| 325 |
+
FIG. 5 shows the device prior to <boundary-data type="line-number">25 </boundary-data>
|
| 326 |
+
expansion of the expandable materials and FIG. 6 shows the device after expansion of these materials. </p>
|
| 327 |
+
<p id="p-68" num="68">[0051<confidence value="5">]</confidence>
|
| 328 |
+
FIG. 7 shows yet another embodiment in which a single fiber comprising at least one expandable material <part-num-ref name="single fiber comprising at least one expandable material">42</part-num-ref>
|
| 329 |
+
is loosely wrapped around a metallic coil <part-num-ref name="metallic coil">44.</part-num-ref>
|
| 330 |
+
</p>
|
| 331 |
+
<boundary-data type="header">
|
| 332 |
+
<confidence value="8">9</confidence>
|
| 333 |
+
</boundary-data>
|
| 334 |
+
<boundary-data type="header">8600-0032</boundary-data>
|
| 335 |
+
<boundary-data type="header">05-01589</boundary-data>
|
| 336 |
+
<boundary-data type="header">PATENT</boundary-data>
|
| 337 |
+
<p id="p-69" num="69">
|
| 338 |
+
<page-break num="11"/>
|
| 339 |
+
[0052] FIG. 8 shows another embodiment in which two strands of fibers, each fiber comprising at least one expandable material <part-num-ref name="shows another embodiment in which two strands of fibers, each fiber comprising at least one expandable material">42,</part-num-ref>
|
| 340 |
+
<part-num-ref name="shows another embodiment in which two strands of fibers, each fiber comprising at least one expandable material 42,">43,</part-num-ref>
|
| 341 |
+
are loosely wrapped around a metallic coil <part-num-ref name="metallic coil">44.</part-num-ref>
|
| 342 |
+
</p>
|
| 343 |
+
<p id="p-70" num="70">
|
| 344 |
+
<confidence value="5">[</confidence>
|
| 345 |
+
0053] As shown in FIG<confidence value="5">s</confidence>
|
| 346 |
+
. 7 and <part-num-ref name="and">8,</part-num-ref>
|
| 347 |
+
any of the devices described herein may further <boundary-data type="line-number">5 </boundary-data>
|
| 348 |
+
comprise a detachment junction <part-num-ref name="detachment junction">50,</part-num-ref>
|
| 349 |
+
which is severable. See, e.g., U.S. Patent Nos. 5,354,295 and 5,122,136. The detachment junction may be connected to a pusher element, such as a pusher wire <part-num-ref name="pusher wire">55.</part-num-ref>
|
| 350 |
+
The detachment junction can be positioned anywhere on the device, for example at one or both ends of device. </p>
|
| 351 |
+
<p id="p-71" num="71">[0054] The severable junction(s) may be detached in a variety of ways, for example using <boundary-data type="line-number">10 </boundary-data>
|
| 352 |
+
an electrolytically detachable assembly adapted to detach by imposition of a current; a mechanically detachable assembly adapted to detach by movement or pressure; a thermally detachable assembly adapted to detach by localized delivery of heat to the junction; a radiation detachable assembly adapted to detach by delivery of electromagnetic radiation to the junction or combinations thereof. Furthermore, the detachment mechanism may be hydraulic, for example <boundary-data type="line-number">15 </boundary-data>
|
| 353 |
+
the pusher wire may be cannulated, for example to allow for saline injection through the pusher wire to push off the coil. </p>
|
| 354 |
+
<p id="p-72" num="72">[0055<confidence value="5">]</confidence>
|
| 355 |
+
The devices described herein may also comprise further additional components, such as co-solvents, plasticizers, coalescing solvents, bioactive agents, antimicrobial agents, porogens, antithrombogenic agents (e.g., heparin), antibiotics, pigments, radiopacifiers <confidence value="222222">and/or</confidence>
|
| 356 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 357 |
+
ion conductors which may be coated using any suitable method or may be incorporated into the element(s) during production. See, e.g., co-owned U.S. Patent Application Publication No. </p>
|
| 358 |
+
<p id="p-73" num="73">20050149109, published July 7, 2005; U.S. Patent No. 6,585,754 and WO 02/051460, incorporated by reference in their entireties herein. The bioactive materials can be coated onto the device (e.g., anticoagulants, growth factors, extracellular matrix components, living cells, <boundary-data type="line-number">25 </boundary-data>
|
| 359 |
+
DNA fragments, clotting stabilizers, or other materials intended to enhance or encourage wound healing) and/or can be placed in the vessel prior to, concurrently or after placement of one or more devices as described herein. </p>
|
| 360 |
+
<boundary-data type="header">
|
| 361 |
+
<confidence value="88">10</confidence>
|
| 362 |
+
</boundary-data>
|
| 363 |
+
<boundary-data type="header">8600-0032</boundary-data>
|
| 364 |
+
<boundary-data type="header">05-01589</boundary-data>
|
| 365 |
+
<boundary-data type="header">PATENT</boundary-data>
|
| 366 |
+
<p id="p-74" num="74">
|
| 367 |
+
<page-break num="12"/>
|
| 368 |
+
<confidence value="5">[</confidence>
|
| 369 |
+
0056<confidence value="5">]</confidence>
|
| 370 |
+
As noted above, one of more of the elements (e.g., metallic vaso-occ<confidence value="5">l</confidence>
|
| 371 |
+
usive device, fibers comprising expandable material, additional materials) may also be secured to each other or to the device at one or more locations. For example, to the extent that various elements are thermoplastic, they may be melted or fused to other elements of the devices. Alternatively, they <boundary-data type="line-number">5 </boundary-data>
|
| 372 |
+
may be glued or otherwise fastened. Furthermore, the various elements may be secured to each other in one or more locations. </p>
|
| 373 |
+
<heading id="h-8">MET<confidence value="8">H</confidence>
|
| 374 |
+
ODS OF USE </heading>
|
| 375 |
+
<p id="p-75" num="75">[0057] The devices described herein are often introduced into a selected site using the <boundary-data type="line-number">10 </boundary-data>
|
| 376 |
+
procedure outlined below. This procedure may be used in treating a variety of maladies. For instance in the treatment of an aneurysm, the aneurysm itself will be filled (partially or fully) with the compositions described herein. </p>
|
| 377 |
+
<p id="p-76" num="76">[0058] Conventional catheter insertion and navigational techniques involving guidewires or flow-directed devices may be used to access the site with a catheter. The mechanism will be <boundary-data type="line-number">15 </boundary-data>
|
| 378 |
+
such as to be capable of being advanced entirely through the catheter to place vaso-occlusive device at the target site but yet with a sufficient portion of the distal end of the delivery mechanism protruding from the distal end of the catheter to enable detachment of the implantable vaso-occlusive device. For use in peripheral or neural surgeries, the delivery mechanism will normally be about 100-200 cm in length, more normally 130-180 cm in length. </p>
|
| 379 |
+
<p id="p-77" num="77">
|
| 380 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 381 |
+
The diameter of the delivery mechanism is usually in the range of 0.25 to about 0.90 mm. </p>
|
| 382 |
+
<p id="p-78" num="78">Briefly, occlusive devices (and/or additional components) described herein are typically loaded into a carrier for introduction into the delivery catheter and introduced to the chosen site using the procedure outlined below. This procedure may be used in treating a variety of maladies. For instance, in treatment of an aneurysm, the aneurysm itself may be filled with the embolics (e.g.</p>
|
| 383 |
+
<p id="p-79" num="79">
|
| 384 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 385 |
+
vaso-occlusive members and/or liquid embolics and bioactive materials) which cause formation of an emboli and, at some later time, is at least partially replaced by neovascularized collagenous material formed around the implanted vaso-occlusive devices. </p>
|
| 386 |
+
<boundary-data type="header">
|
| 387 |
+
<confidence value="88">11</confidence>
|
| 388 |
+
</boundary-data>
|
| 389 |
+
<boundary-data type="header">8600-0032</boundary-data>
|
| 390 |
+
<boundary-data type="header">05-01589</boundary-data>
|
| 391 |
+
<boundary-data type="header">PATENT</boundary-data>
|
| 392 |
+
<p id="p-80" num="80">
|
| 393 |
+
<page-break num="13"/>
|
| 394 |
+
<confidence value="5">[</confidence>
|
| 395 |
+
0059<confidence value="5">1</confidence>
|
| 396 |
+
A selected site is reached through the vascular system using a collection of specifically chosen catheters and/or guide wires. It is clear that should the site be in a remote site, e.g., in the brain, methods of reaching this site are somewhat limited. One widely accepted procedure is found in U.S. Patent No. 4,994,069 to Ritchart, et al. It utilizes a fine endovascular <boundary-data type="line-number">5 </boundary-data>
|
| 397 |
+
catheter such as is found in U.S. Patent No. 4,739,768, to Engelson. First of all, a large catheter is introduced through an entry site in the vasculature. Typically, this would be through a femoral artery in the groin. Other entry sites sometimes chosen are found in the neck and are in general well known by physicians who practice this type of medicine. Once the introducer is in place, a guiding catheter is then used to provide a safe passageway from the entry site to a region near the <boundary-data type="line-number">10 </boundary-data>
|
| 398 |
+
site to be treated. For instance, in treating a site in the human brain, a guiding catheter would be chosen which would extend from the entry site at the femoral artery, up through the large arteries extending to the heart, around the heart through the aortic arch, and downstream through one of the arteries extending from the upper side of the aorta. A guidewire and neurovascular catheter such as that described in the Engelson patent are then placed through the guiding catheter. Once <boundary-data type="line-number">15 </boundary-data>
|
| 399 |
+
the distal end of the catheter is positioned at the site, often by locating its distal end through the use of radiopaque marker material and fluoroscopy, the catheter is cleared. For instance, if a guidewire has been used to position the catheter, it is withdrawn from the catheter and then the assembly, for example including the vaso-occlusive device at the distal end, is advanced through the catheter. </p>
|
| 400 |
+
<p id="p-81" num="81">
|
| 401 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 402 |
+
[0060<confidence value="5">]</confidence>
|
| 403 |
+
Once the selected site has been reached, the vaso-occlusive device is extruded, for example by loading onto a pusher wire. Preferably, the vaso-occlusive device is loaded onto the pusher wire via a mechanically or electrolytically cleavable junction (e.g., a GDC-type junction that can be severed by application of heat, electrolysis, electrodynamic activation or other means). Additionally, the vaso-occlusive device can be designed to include multiple detachment <boundary-data type="line-number">25 </boundary-data>
|
| 404 |
+
points, as described in co-owned U.S. Patent No. 6,623,493 and 6,533,801 and International Patent publication WO 02/45596. They are held in place by gravity, shape, size, volume, magnetic field or combinations thereof. </p>
|
| 405 |
+
<boundary-data type="header">
|
| 406 |
+
<confidence value="88">12</confidence>
|
| 407 |
+
</boundary-data>
|
| 408 |
+
<boundary-data type="header">8600-0032</boundary-data>
|
| 409 |
+
<boundary-data type="header">05-01589</boundary-data>
|
| 410 |
+
<boundary-data type="header">PATENT</boundary-data>
|
| 411 |
+
<p id="p-82" num="82">
|
| 412 |
+
<page-break num="14"/>
|
| 413 |
+
<confidence value="5">[</confidence>
|
| 414 |
+
0061<confidence value="5">]</confidence>
|
| 415 |
+
It will also be apparent that the operator can remove or reposition (distally or proximally) the device. For instance, the operator may choose to insert a device as described herein, before detachment, move the pusher wire to place the device in the desired location. </p>
|
| 416 |
+
<p id="p-83" num="83">
|
| 417 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 418 |
+
[0062] Modifications of the procedure and vaso-oc<confidence value="5">c</confidence>
|
| 419 |
+
lusive devices described above, and the methods of using them in keeping with this invention will be apparent to those having skill in this mechanical and surgical art. These variations are intended to be within the scope of the claims that follow. </p>
|
| 420 |
+
<boundary-data type="header">
|
| 421 |
+
<confidence value="88">13</confidence>
|
| 422 |
+
</boundary-data>
|
| 423 |
+
</description>
|
| 424 |
+
</us-patent-application>
|
| 425 |
+
|
applicant/11403031.xml
ADDED
|
@@ -0,0 +1,99 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>11403031</doc-number>
|
| 8 |
+
<date>2006-04-12</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<heading id="h-1">INTERACTIVE MOBILE WIRELESS DIGITAL TV</heading>
|
| 14 |
+
<p id="p-1" num="1">This application claims priority to U.S. provisional patent application serial no.</p>
|
| 15 |
+
<p id="p-2" num="2">60/761,731, filed January 23, 2006.</p>
|
| 16 |
+
<heading id="h-2">I. FIELD OF THE INVENTION</heading>
|
| 17 |
+
<p id="p-3" num="3">The present invention relates generally to digital televisions (DTV).</p>
|
| 18 |
+
<heading id="h-3">II. BACKGROUND OF THE INVENTION</heading>
|
| 19 |
+
<p id="p-4" num="4">TV content can be provided to <confidence value="8">m</confidence>
|
| 20 |
+
obile telephones using telecom-centric standards such as Integrated Services Digital Broadcasting (ISDB), Digital Multimedia Broadcast (DMB), Digital Video Broadcasting (DVB-<confidence value="5">H</confidence>
|
| 21 |
+
), and MediaFLOT<confidence value="4">M</confidence>
|
| 22 |
+
over a wireless telephony network such as a GSM or CDMA network. As understood herein, not only do consumers wish to view TV on their wireless phones, but they also wish to interact with TV shows. The present invention recognizes that such interactivity not only is desired by consumers, but also allows consumers to click deeply into ads to order products, benefitting content providers. As further recognized herein, there are situations in which the telephony carrier's support is not available or is not desired for receiving user interaction. The present invention understands that non- telephony wireless networks such as Wireless Fidelity (WiFi), Worldwide Interoperability for Microwave Access (the IEEE 802.16 standard colloquially known as "WiMax"), and wireless Ethernet are available non-telecom carrier networks that can be used to provide the above- mentioned interaction with TV programming. </p>
|
| 23 |
+
<boundary-data type="header">
|
| 24 |
+
<confidence value="655">50V</confidence>
|
| 25 |
+
8309.02 1 </boundary-data>
|
| 26 |
+
<heading id="h-4">SUMMARY OF THE INVENTION</heading>
|
| 27 |
+
<p id="p-5" num="5">
|
| 28 |
+
<page-break num="2"/>
|
| 29 |
+
A method for providing TV programming includes sending TV signals to a wireless<confidence value="12">*-</confidence>
|
| 30 |
+
TV device over a wireless telephony network, and at the device, receiving user input representative of user interaction with a TV program associated with the TV signals. The method also includes wirelessly transmitting signals representative of the user input from the device over a non-telephony wireless network. In non-limiting implementations the TV signals may be digital TV signals and the device can be portable. </p>
|
| 31 |
+
<p id="p-6" num="6">In non-limiting embodiments the TV signals may be received over the telephony network using Integrated Services Digital Broadcasting (<confidence value="2222">ISDB</confidence>
|
| 32 |
+
). In other embodiments the TV signals may be received over the telephony network using Digital Multimedia Broadcast (DMB), or using Digital Video Broadcasting (DVB-H), or using a CDMA DTV protocol such as, e.g., MediaFloT<confidence value="5">M</confidence>
|
| 33 |
+
. In contrast, the non-telephony wireless network may include a Wireless Fidelity (WiFi) network, or a Worldwide Interoperability for Microwave Access (WiMax) network, or a wireless Ethernet network. </p>
|
| 34 |
+
<p id="p-7" num="7">In another aspect, a wireless telephone includes a housing holding a wireless DTV receiver that receives DTV signals in Integrated Services Digital Broadcasting (<confidence value="2222">ISDB</confidence>
|
| 35 |
+
), Digital Multimedia Broadcast (DMB), Digital Video Broadcasting (DVB-H), or a CDMA-centric digital broadcasting protocol. A video display on the housing displays the DTV signals. The housing also contains a processor for receiving user input signals and causing the user input signals to be wirelessly transmitted using Wireless Fidelity (WiFi), Worldwide Interoperability for Microwave Access (WiMax), or wireless Ethernet. </p>
|
| 36 |
+
<p id="p-8" num="8">In still another aspect, a processor includes means for receiving DTV signals from a wireless telephone carrier network, and means for causing the DTV signals to be displayed on <boundary-data type="header">
|
| 37 |
+
<confidence value="654">50V</confidence>
|
| 38 |
+
8309.02 2 </boundary-data>
|
| 39 |
+
<page-break num="3"/>
|
| 40 |
+
a video display. Further, the processor includes means for receiving user signals representing user interaction with programming represented by the DTV signals. Means are provided for causing the wireless transmission of signals representing user interaction over a wireless network that is not a wireless telephone carrier network. </p>
|
| 41 |
+
<p id="p-9" num="9">The details of the present invention, both as to its structure and operation, can best be understood in reference to the accompanying drawings, in which like reference numerals refer to like parts, and in which:</p>
|
| 42 |
+
<heading id="h-5">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
|
| 43 |
+
<p id="p-10" num="10">Figure 1 is a schematic diagram of the present interactive mobile wireless digital television (DTV); and Figure 2 is a flow chart of a non-limiting example of the logic that may be implemented in whole or in part by logic circuitry within the processor the wireless telephone.</p>
|
| 44 |
+
<heading id="h-6">DETAILED DESCRIPTION OF T<confidence value="5">H</confidence>
|
| 45 |
+
E PREFERRED EMBODIMENT </heading>
|
| 46 |
+
<p id="p-11" num="11">Referring initially to Figure 1, a mobile wireless digital television (DTV) device such as a wireless telephone is shown, generally designated <part-num-ref name="wireless telephone is shown, generally designated">10.</part-num-ref>
|
| 47 |
+
The device <part-num-ref name="device">10</part-num-ref>
|
| 48 |
+
may include a portable lightweight housing <part-num-ref name="portable lightweight housing">12</part-num-ref>
|
| 49 |
+
that supports a multimedia (video and/or audio) display <part-num-ref name="multimedia (video and/or audio) display">14</part-num-ref>
|
| 50 |
+
that displays data sent to it from a processor <part-num-ref name="processor">16.</part-num-ref>
|
| 51 |
+
This data may include user-input signals from an input device <part-num-ref name="input device">17</part-num-ref>
|
| 52 |
+
such as but not limited to a keypad and also may include multimedia signals from a wireless DTV receiver <part-num-ref name="wireless DTV receiver">18</part-num-ref>
|
| 53 |
+
that communicates with the processor <part-num-ref name="processor">16</part-num-ref>
|
| 54 |
+
as shown. Also, the processor <part-num-ref name="processor">16</part-num-ref>
|
| 55 |
+
communicates with an Internet Protocol (IP) stack <part-num-ref name="Internet Protocol (IP) stack">20</part-num-ref>
|
| 56 |
+
to facilitate wirele<confidence value="88">ss</confidence>
|
| 57 |
+
communication in accordance with disclosure below with the Internet <part-num-ref name="Internet">22.</part-num-ref>
|
| 58 |
+
Wireless <boundary-data type="header">
|
| 59 |
+
<confidence value="655">50V</confidence>
|
| 60 |
+
8309.02 3 </boundary-data>
|
| 61 |
+
<page-break num="4"/>
|
| 62 |
+
communication is also afforded by means of the wireless DTV receiver <part-num-ref name="wireless DTV receiver">18</part-num-ref>
|
| 63 |
+
with a gateway <part-num-ref name="gateway">24</part-num-ref>
|
| 64 |
+
of a wireless telephony network such as but not limited to a code division multiple access (CDMA) network or Global System for Mobile Communication (GSM) network. </p>
|
| 65 |
+
<p id="p-12" num="12">Accordingly, the skilled artisan will now recognize that the device <part-num-ref name="device">10</part-num-ref>
|
| 66 |
+
can communicate with a wireless telephony network owned by a telephone carrier to receive DTV signals at the receiver <part-num-ref name="receiver">18,</part-num-ref>
|
| 67 |
+
and can also communicate with a non-telephony network using the IP stack <part-num-ref name="IP stack">20.</part-num-ref>
|
| 68 |
+
</p>
|
| 69 |
+
<p id="p-13" num="13">With the above architecture of a preferred non-limiting device <part-num-ref name="preferred non-limiting device">10</part-num-ref>
|
| 70 |
+
in mind, attention is now directed to Figure 2 for an illustration of one non-limiting way in which the device <part-num-ref name="device">10</part-num-ref>
|
| 71 |
+
can operate. Commencing at block <part-num-ref name="can operate. Commencing at block">26,</part-num-ref>
|
| 72 |
+
DTV signals are received from the telephony carrier network (e.g., from the gateway <part-num-ref name="gateway">24)</part-num-ref>
|
| 73 |
+
at the receiver <part-num-ref name="receiver">18</part-num-ref>
|
| 74 |
+
and thence at the processor <part-num-ref name="processor">16</part-num-ref>
|
| 75 |
+
in an appropriate format. In some implementations the TV signals are received using Integrated Services Digital Broadcasting (ISDB) protocol. In other implementations the TV signals can be received using Digital Multimedia Broadcast (DMB) or Digital Video Broadcasting (DVB- H). In still other implementations the TV signals may be received using a CDMA-oriented DTV protocol such as MediaFloT<confidence value="5">M</confidence>
|
| 76 |
+
. The processor <part-num-ref name="processor">16</part-num-ref>
|
| 77 |
+
causes the signals to be displayed on the display <part-num-ref name="display">14.</part-num-ref>
|
| 78 |
+
</p>
|
| 79 |
+
<p id="p-14" num="14">To make it possible for TV programs to build value added applications and services such as gaming, voting, polling, shopping, product recommendations, advertising, instant messaging, etc. without resort to the telecom carrier<confidence value="8">'</confidence>
|
| 80 |
+
s network, user input from the input device <part-num-ref name="input device">17</part-num-ref>
|
| 81 |
+
that can pertain to interactivity with a TV program being displayed on the display <part-num-ref name="display">14</part-num-ref>
|
| 82 |
+
may be wirelessly transmitted through the IP protocol stack <part-num-ref name="IP protocol stack">20</part-num-ref>
|
| 83 |
+
to the Internet <part-num-ref name="Internet">22.</part-num-ref>
|
| 84 |
+
The IP protocol stack <part-num-ref name="IP protocol stack">20</part-num-ref>
|
| 85 |
+
may include a transmission control protocol/Internet protocol (TCP/IP) connection with Wireless Fidelity (WiFi), Worldwide Interoperability for Microwave Access <boundary-data type="header">
|
| 86 |
+
<confidence value="655">50v</confidence>
|
| 87 |
+
8309.02 <confidence value="5">4</confidence>
|
| 88 |
+
</boundary-data>
|
| 89 |
+
<page-break num="5"/>
|
| 90 |
+
(WiMax), or wireless Ethernet as the physical layer, thus providing a communication channel for Internet based interaction without using a telephone carrier's network. In turn, a server associated with the broadcaster of the TV program being viewed on the display <part-num-ref name="display">14</part-num-ref>
|
| 91 |
+
can receive the interactive signals through the Internet. </p>
|
| 92 |
+
<p id="p-15" num="15">While the particular INTERACTIVE MOBILE WIRELESS DIGITAL TV as herein shown and described in detail is fully capable of attaining the above-described objects of the invention, it is to be understood that it is the presently preferred embodiment of the present invention and is thus representative of the subject matter which is broadly contemplated by the present invention, that the scope of the present invention fully encompasses other embodiments which may become obvious to those skilled in the art, and that the scope of the present invention is accordingly to be limited by nothing other than the appended claims, in which reference to an element in the singular is not intended to mean "one and only one" unless explicitly so stated, but rather "one or more". It is not necessary for a device or method to address each and every problem sought to be solved by the present invention, for it to be encompassed by the present claims. Furthermore, no element, component, or method step in the present disclosure is intended to be dedicated to the public regardless of whether the element, component, or method step is explicitly recited in the claims. Absent express definitions herein, claim terms are to be given all ordinary and accustomed meanings that are not irreconcilable with the present specification and file history.</p>
|
| 93 |
+
<boundary-data type="header">
|
| 94 |
+
<confidence value="654">50V</confidence>
|
| 95 |
+
8309.02 <confidence value="8">5</confidence>
|
| 96 |
+
</boundary-data>
|
| 97 |
+
</description>
|
| 98 |
+
</us-patent-application>
|
| 99 |
+
|
applicant/11408375.xml
ADDED
|
@@ -0,0 +1,29 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>11408375</doc-number>
|
| 8 |
+
<date>2009-06-01</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<p id="p-1" num="1">11/408,375 Knitter et al. 200502178-1 H0603AmA-9616 PATENT </p>
|
| 14 |
+
<heading id="h-1">AMENDMENT TO THE SPECIFICATION</heading>
|
| 15 |
+
<p id="p-2" num="2">After paragraph [12], please add the following new paragraph.</p>
|
| 16 |
+
<p id="p-3" num="3">[12.1<confidence value="5">]</confidence>
|
| 17 |
+
The present invention provides a method, a system, and computer-readable storage media for reconciling a web- server session state with a client web-browser state. The method involves responding to an nt<confidence value="4">"</confidence>
|
| 18 |
+
request, by reading an <confidence value="811">mt"</confidence>
|
| 19 |
+
session-state identifier included in the request, where n > m <confidence value="8">></confidence>
|
| 20 |
+
<part-num-ref name="request, where n > m >">1.</part-num-ref>
|
| 21 |
+
The server then assumes an mt<confidence value="4">h</confidence>
|
| 22 |
+
session state associated with the m<confidence value="41">th</confidence>
|
| 23 |
+
session-state identifier. </p>
|
| 24 |
+
<p id="p-4" num="4">
|
| 25 |
+
<confidence value="8">2</confidence>
|
| 26 |
+
</p>
|
| 27 |
+
</description>
|
| 28 |
+
</us-patent-application>
|
| 29 |
+
|
applicant/11421232.xml
ADDED
|
@@ -0,0 +1,15 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="UTF-8"?>
|
| 2 |
+
<pat:SpecificationDocument xmlns:pat="urn:us:gov:doc:uspto:patent" xmlns="urn:us:gov:doc:uspto:patent" xmlns:ent="urn:us:gov:doc:uspto:enterprise" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:tbl="http://www.oasis-open.org/tables/exchange/1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:com="http://www.wipo.int/standards/XMLSchema/Common/1" pat:instanceFileName="11421232.08-26-2014.HZBOUXTDPXXIFW3.SPEC.xml" pat:id="HZBOUXTDPXXIFW3" xsi:schemaLocation="urn:us:gov:doc:uspto:patent XMLSchema/V1_3/SpecificationDocument_1_0.xsd">
|
| 3 |
+
<pat:DocumentCode>SPEC</pat:DocumentCode><pat:DocumentHeaderDetails pat:id="ID-00001">
|
| 4 |
+
<pat:ApplicationHeaderDetails><pat:ApplicationNumber>11421232</pat:ApplicationNumber></pat:ApplicationHeaderDetails>
|
| 5 |
+
<pat:PageTotalQuantity>1</pat:PageTotalQuantity>
|
| 6 |
+
<pat:ParagraphTotalQuantity>2</pat:ParagraphTotalQuantity>
|
| 7 |
+
</pat:DocumentHeaderDetails>
|
| 8 |
+
<pat:MailRoomDate>2014-08-26</pat:MailRoomDate>
|
| 9 |
+
<pat:Specification pat:id="Specification">
|
| 10 |
+
<?PageStart number="1"?>
|
| 11 |
+
<pat:BoundaryData><pat:HeaderText>Serial No. 11/421,232 -<pat:OCRConfidenceData pat:levelNumber="8">2</pat:OCRConfidenceData>- Art Unit: 2453</pat:HeaderText></pat:BoundaryData>
|
| 12 |
+
<pat:P pat:id="p-1" pat:pNumber="1">In the Title:</pat:P>
|
| 13 |
+
<pat:P pat:id="p-2" pat:pNumber="2">Please delete the current title and replace it with the following substitute Title:</pat:P>
|
| 14 |
+
<pat:Heading pat:id="h-1">--SELECTIVE <pat:OCRConfidenceData pat:levelNumber="5">I</pat:OCRConfidenceData>NFORMATION SHAR<pat:OCRConfidenceData pat:levelNumber="5">I</pat:OCRConfidenceData>NG ACROSS TEAM SPACES--</pat:Heading>
|
| 15 |
+
</pat:Specification></pat:SpecificationDocument>
|
applicant/11462049.xml
ADDED
|
@@ -0,0 +1,369 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>11462049</doc-number>
|
| 8 |
+
<date>2006-08-03</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<boundary-data type="header">200501203</boundary-data>
|
| 14 |
+
<heading id="h-1">METHOD AND SYSTEM FOR MANAGING A MEETING</heading>
|
| 15 |
+
<p id="p-1" num="1">Field of the Invention <boundary-data type="line-number">
|
| 16 |
+
<confidence value="8">5</confidence>
|
| 17 |
+
</boundary-data>
|
| 18 |
+
<confidence value="66666">[0001</confidence>
|
| 19 |
+
] The invention relates generally to meeting management, and more particularly, to a method and system for managing a meeting. </p>
|
| 20 |
+
<p id="p-2" num="2">Background of the Invention <boundary-data type="line-number">10 </boundary-data>
|
| 21 |
+
<confidence value="5">[</confidence>
|
| 22 |
+
0002] Meetings, regardless of whether it is face-to-face or virtual, are generally used as a management communication tool for keeping people informed and motivated, generating new ideas or policies, and making decisions for some matters. A meeting can foster relationship among people by encouraging participation and interaction. It can also foster a person's growth and ownership in a company. Therefore, many <boundary-data type="line-number">15 </boundary-data>
|
| 23 |
+
organizations recognize the importance of meetings and schedule meetings within and outside their organizations on a regular basis. </p>
|
| 24 |
+
<p id="p-3" num="3">
|
| 25 |
+
<confidence value="5">[</confidence>
|
| 26 |
+
0003] A meeting may be managed manually by an appointed meeting coordinator. </p>
|
| 27 |
+
<p id="p-4" num="4">The meeting coordinator schedules a meeting on a certain date and sends out emails to <boundary-data type="line-number">20 </boundary-data>
|
| 28 |
+
other people to invite them to attend the meeting. The coordinator has to find out the objective of the meeting and determine the agenda. Details of the meeting, such as meeting time, venue and agenda, are normally typed into the content of the email. </p>
|
| 29 |
+
<p id="p-5" num="5">During the meeting, the chairman of the meeting goes through each item of the agenda and a person may take the minutes of the meeting. After the meeting, each <boundary-data type="line-number">25 </boundary-data>
|
| 30 |
+
person would remember their own action items and perform them accordingly. The chairman or the coordinator may also keep a record of all the action items to be performed, and sends reminders to the respective people for performing the action items. The minutes of the meeting may also be sent out subsequently after the meeting to the people who attended the meeting, or to those who have one or more <boundary-data type="line-number">30 </boundary-data>
|
| 31 |
+
action items to complete. </p>
|
| 32 |
+
<p id="p-6" num="6">[0004] The manual process for managing a meeting is feasible when the meeting involves only a few people and has few items on the agenda. However, when the meeting involves a large group of people, the coordination of the meeting becomes <page-break num="2"/>
|
| 33 |
+
<boundary-data type="header">200501203</boundary-data>
|
| 34 |
+
tedious. Moreover, if the meeting has generated many action items, it is very difficult to keep record on whether each of the action items has been performed by the respective people. </p>
|
| 35 |
+
<p id="p-7" num="7">
|
| 36 |
+
<boundary-data type="line-number">
|
| 37 |
+
<confidence value="8">5</confidence>
|
| 38 |
+
</boundary-data>
|
| 39 |
+
<confidence value="5">[</confidence>
|
| 40 |
+
0005] Electronic calendars such as Microsoft Outlook may aid the coordinator in managing the meeting by providing various options such as data fields for the coordinator to provide meeting details, adding attendees for the meeting, sending invitations to the attendees, and sending reminders to the attendees for the meeting. </p>
|
| 41 |
+
<p id="p-8" num="8">However, such electronic calendars do not help the coordinator to consolidate the <boundary-data type="line-number">10 </boundary-data>
|
| 42 |
+
actions item resulting from the meeting. The electronic calendars also do not have any post-meeting options such as tracking whether the action items are performed by the respective people, or sending minutes of the meeting to the attendees or to those who have action items to complete, regardless whether they were the attendees of the meeting. </p>
|
| 43 |
+
<p id="p-9" num="9">
|
| 44 |
+
<boundary-data type="line-number">
|
| 45 |
+
<confidence value="88">15</confidence>
|
| 46 |
+
</boundary-data>
|
| 47 |
+
Summary of the Invention [0006] In an embodiment, a computer implemented method for managing a meeting is provided. The method includes scheduling a meeting, selecting one or more <boundary-data type="line-number">20 </boundary-data>
|
| 48 |
+
participants for the scheduled meeting, sending an invitation for the scheduled meeting to the one or more participants wherein each participant is able to add a discussion item for the scheduled meeting when the participant accepts the invitation, consolidating the discussion items for the scheduled meeting added by the participant who accepted the invitation, selecting at least one discussion item from the <boundary-data type="line-number">25 </boundary-data>
|
| 49 |
+
consolidated discussion items as an item for an agenda of the scheduled meeting and informing the one or more participants on the agenda of the scheduled meeting. </p>
|
| 50 |
+
<boundary-data type="header">
|
| 51 |
+
<confidence value="8">2</confidence>
|
| 52 |
+
</boundary-data>
|
| 53 |
+
<boundary-data type="header">200501203</boundary-data>
|
| 54 |
+
<p id="p-10" num="10">
|
| 55 |
+
<page-break num="3"/>
|
| 56 |
+
Brief Description of the Drawings [0007] The embodiments of the invention will be better understood in view of the following drawings and the detailed description. </p>
|
| 57 |
+
<p id="p-11" num="11">
|
| 58 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 59 |
+
[0008] Figure 1 shows a block diagram of a system for managing a meeting according to an embodiment. </p>
|
| 60 |
+
<p id="p-12" num="12">[0009] Figure 2 shows a flow chart of a meeting management process according to an embodiment.</p>
|
| 61 |
+
<p id="p-13" num="13">[0010] Figure 3 shows a flow chart of an example of the meeting management <boundary-data type="line-number">10 </boundary-data>
|
| 62 |
+
process before the meeting according to an embodiment. </p>
|
| 63 |
+
<p id="p-14" num="14">[0011] Figure 4 shows a flow chart of an example of the meeting management process during and after the meeting according to an embodiment.</p>
|
| 64 |
+
<p id="p-15" num="15">[0012] Figure 5 shows an example of a website for logging in to access an application program hosting the system for managing the meeting according to an embodiment.</p>
|
| 65 |
+
<p id="p-16" num="16">
|
| 66 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 67 |
+
[0013] Figure 6 shows an example of a "schedule a meeting" GUI page according to an embodiment. </p>
|
| 68 |
+
<p id="p-17" num="17">[0014] Figure 7 shows an example of an invitation email sent to participants of the meeting according to an embodiment.</p>
|
| 69 |
+
<p id="p-18" num="18">[0015] Figure 8 shows an example of an agenda sent to the participants of the meeting <boundary-data type="line-number">20 </boundary-data>
|
| 70 |
+
according to an embodiment. </p>
|
| 71 |
+
<p id="p-19" num="19">[0016] Figure 9 shows an example of a page for taking attendance of the participants of the meeting according to an embodiment.</p>
|
| 72 |
+
<p id="p-20" num="20">[0017] Figure 10 shows an example of a page for updating the items of the agenda according to an embodiment.</p>
|
| 73 |
+
<p id="p-21" num="21">
|
| 74 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 75 |
+
[0018] Figure 11 shows an example of an updated list of items generated during the meeting according to an embodiment. </p>
|
| 76 |
+
<p id="p-22" num="22">[0019] Figure 12 shows an example of the meeting minutes sent to the participants of the meeting according to an embodiment.</p>
|
| 77 |
+
<p id="p-23" num="23">[0020] Figure 13 shows an example of a summary of meetings of the participants <part-num-ref name="participants">30</part-num-ref>
|
| 78 |
+
according to an embodiment. </p>
|
| 79 |
+
<boundary-data type="header">
|
| 80 |
+
<confidence value="8">3</confidence>
|
| 81 |
+
</boundary-data>
|
| 82 |
+
<boundary-data type="header">200501203</boundary-data>
|
| 83 |
+
<p id="p-24" num="24">
|
| 84 |
+
<page-break num="4"/>
|
| 85 |
+
Detailed Description of the Invention [0021] Fig.<confidence value="5">1</confidence>
|
| 86 |
+
shows a system <part-num-ref name="system">100</part-num-ref>
|
| 87 |
+
for managing a meeting according to an embodiment. The system <part-num-ref name="system">100</part-num-ref>
|
| 88 |
+
includes a computer workstation <part-num-ref name="computer workstation">101,</part-num-ref>
|
| 89 |
+
a server <part-num-ref name="server">102</part-num-ref>
|
| 90 |
+
and <boundary-data type="line-number">5 </boundary-data>
|
| 91 |
+
a database <part-num-ref name="database">103.</part-num-ref>
|
| 92 |
+
The database <part-num-ref name="database">103</part-num-ref>
|
| 93 |
+
includes various data fields which correspond to different details of the meeting. Examples of the meeting details include, but not limited to, meeting ID, date, time, duration, venue, objective, agenda review date and any documents uploaded. The server <part-num-ref name="server">102</part-num-ref>
|
| 94 |
+
includes an application program which interfaces the database <part-num-ref name="database">103</part-num-ref>
|
| 95 |
+
with the workstation <part-num-ref name="workstation">101.</part-num-ref>
|
| 96 |
+
The workstation <part-num-ref name="workstation">101</part-num-ref>
|
| 97 |
+
allows a <boundary-data type="line-number">10 </boundary-data>
|
| 98 |
+
user to interact with the application program to manage the meeting. </p>
|
| 99 |
+
<p id="p-25" num="25">[0022] The application program resided in the server <part-num-ref name="server">102</part-num-ref>
|
| 100 |
+
provides various services including business service <part-num-ref name="provides various services including business service">110,</part-num-ref>
|
| 101 |
+
alert service <part-num-ref name="provides various services including business service 110, alert service">111,</part-num-ref>
|
| 102 |
+
reports service <part-num-ref name="provides various services including business service 110, alert service 111, reports service">112,</part-num-ref>
|
| 103 |
+
web presentation service <part-num-ref name="provides various services including business service 110, alert service 111, reports service 112, web presentation service">113,</part-num-ref>
|
| 104 |
+
authentication and authorization service <part-num-ref name="provides various services including business service 110, alert service 111, reports service 112, web presentation service 113, authentication and authorization service">114,</part-num-ref>
|
| 105 |
+
and workflow <boundary-data type="line-number">15 </boundary-data>
|
| 106 |
+
service <part-num-ref name="provides various services including business service 110, alert service 111, reports service 112, web presentation service 113, authentication and authorization service 114, and workflow service">115.</part-num-ref>
|
| 107 |
+
The business service <part-num-ref name="business service">110</part-num-ref>
|
| 108 |
+
regulates the functioning of the various services and the flow of information between the user from the workstation <part-num-ref name="workstation">101,</part-num-ref>
|
| 109 |
+
the server <part-num-ref name="server">102</part-num-ref>
|
| 110 |
+
and the database <part-num-ref name="database">103.</part-num-ref>
|
| 111 |
+
When the user provides input at the work station <part-num-ref name="work station">101,</part-num-ref>
|
| 112 |
+
the business service <part-num-ref name="business service">110</part-num-ref>
|
| 113 |
+
interprets the input and instructs the other services to respond to the input accordingly. For example, if the user wants to view a summary <boundary-data type="line-number">20 </boundary-data>
|
| 114 |
+
of all meetings scheduled, the business service <part-num-ref name="business service">110</part-num-ref>
|
| 115 |
+
retrieves the information of all the meetings from the database <part-num-ref name="database">103,</part-num-ref>
|
| 116 |
+
instructs the reports service <part-num-ref name="reports service">112</part-num-ref>
|
| 117 |
+
to generate a report containing the information on all the meetings and instructs the web presentation service <part-num-ref name="web presentation service">113</part-num-ref>
|
| 118 |
+
to present the report to the user at the workstation <part-num-ref name="workstation">101.</part-num-ref>
|
| 119 |
+
</p>
|
| 120 |
+
<p id="p-26" num="26">
|
| 121 |
+
<boundary-data type="line-number">25 </boundary-data>
|
| 122 |
+
[0023] The alert service <part-num-ref name="alert service">111</part-num-ref>
|
| 123 |
+
alerts the user of any event, such as an upcoming meeting or an action which needs to be performed, by sending email reminders to the user. The reports service <part-num-ref name="reports service">112</part-num-ref>
|
| 124 |
+
generates report requested by the user. The web presentation service <part-num-ref name="web presentation service">113</part-num-ref>
|
| 125 |
+
provides a Graphical User Interface (GUI) at the workstation <part-num-ref name="workstation">101.</part-num-ref>
|
| 126 |
+
The user accesses the various services of the application through the GUI at the <boundary-data type="line-number">30 </boundary-data>
|
| 127 |
+
workstation <part-num-ref name="workstation">101.</part-num-ref>
|
| 128 |
+
Examples of the various GUI presented to the user will be described later. The authentication and authorization service <part-num-ref name="authentication and authorization service">114</part-num-ref>
|
| 129 |
+
prevents unauthorized use of the system <part-num-ref name="system">100</part-num-ref>
|
| 130 |
+
by authenticating the identity of the user. The workflow service <part-num-ref name="workflow service">115</part-num-ref>
|
| 131 |
+
controls the flow of the meeting managing process, such as the steps for scheduling a meeting. </p>
|
| 132 |
+
<boundary-data type="header">
|
| 133 |
+
<confidence value="8">4</confidence>
|
| 134 |
+
</boundary-data>
|
| 135 |
+
<boundary-data type="header">200501203</boundary-data>
|
| 136 |
+
<p id="p-27" num="27">
|
| 137 |
+
<page-break num="5"/>
|
| 138 |
+
[0024] The workstation <part-num-ref name="workstation">101</part-num-ref>
|
| 139 |
+
may be implemented using any computer and laptop. </p>
|
| 140 |
+
<p id="p-28" num="28">The workstation 101 is connected to the server <part-num-ref name="server">102</part-num-ref>
|
| 141 |
+
via the Internet in an embodiment. </p>
|
| 142 |
+
<p id="p-29" num="29">The application program is hosted on the Internet by the server <part-num-ref name="server">102.</part-num-ref>
|
| 143 |
+
The server <part-num-ref name="server">102</part-num-ref>
|
| 144 |
+
may be implemented using the Microsoft Internet Information Services (<confidence value="66">II</confidence>
|
| 145 |
+
S) server in <boundary-data type="line-number">5 </boundary-data>
|
| 146 |
+
an embodiment. It is also possible to implement the server <part-num-ref name="server">102</part-num-ref>
|
| 147 |
+
using other types of servers, for example the Apache Tomcat server, in other embodiments. The database <part-num-ref name="database">103</part-num-ref>
|
| 148 |
+
may be implemented using the Microsoft SQL Server. Since the system <part-num-ref name="system">100</part-num-ref>
|
| 149 |
+
is implemented on the Internet, the workstation <part-num-ref name="workstation">101</part-num-ref>
|
| 150 |
+
of the system <part-num-ref name="system">100</part-num-ref>
|
| 151 |
+
may include any computers or laptops which are connected to the Internet. </p>
|
| 152 |
+
<p id="p-30" num="30">
|
| 153 |
+
<boundary-data type="line-number">
|
| 154 |
+
<confidence value="88">10</confidence>
|
| 155 |
+
</boundary-data>
|
| 156 |
+
<confidence value="5">[</confidence>
|
| 157 |
+
0025] In an alternative embodiment, the workstations <part-num-ref name="workstations">101</part-num-ref>
|
| 158 |
+
may be connected directly to the server <part-num-ref name="server">102.</part-num-ref>
|
| 159 |
+
The server <part-num-ref name="server">102</part-num-ref>
|
| 160 |
+
may be a personal computer which is connected with the workstation <part-num-ref name="workstation">101</part-num-ref>
|
| 161 |
+
and the database <part-num-ref name="database">103,</part-num-ref>
|
| 162 |
+
and runs the application program for managing a meeting. In other words, the system <part-num-ref name="system">100</part-num-ref>
|
| 163 |
+
may be implemented in an <boundary-data type="line-number">15 </boundary-data>
|
| 164 |
+
offline manner. </p>
|
| 165 |
+
<p id="p-31" num="31">
|
| 166 |
+
<confidence value="5">[</confidence>
|
| 167 |
+
0026] The application residing in the server <part-num-ref name="server">102</part-num-ref>
|
| 168 |
+
is a web-based 3-tier application in an embodiment. A first layer is an application front end layer which contains Microsoft Active Server Pages (ASP). A second layer is a business logic layer which <boundary-data type="line-number">20 </boundary-data>
|
| 169 |
+
is written using Microsoft's VBScript, JScript and ASP components. A third layer is a database layer which contains Microsoft Structured Query language (SQL) server and stores the data and information. </p>
|
| 170 |
+
<p id="p-32" num="32">[0027] Fig.2 shows a flow chart of a meeting management process according to an <boundary-data type="line-number">25 </boundary-data>
|
| 171 |
+
embodiment. Step <part-num-ref name="embodiment. Step">201</part-num-ref>
|
| 172 |
+
includes scheduling a meeting. A meeting coordinator schedules the meeting by entering meeting details through a GUI page at the workstation <part-num-ref name="workstation">101.</part-num-ref>
|
| 173 |
+
As described earlier, the meeting details may include meeting date, time, duration, venue, meeting objective and/or agenda review date. Documents may also be uploaded through the GUI page at this stage. Step <part-num-ref name="GUI page at this stage. Step">202</part-num-ref>
|
| 174 |
+
includes selecting <boundary-data type="line-number">30 </boundary-data>
|
| 175 |
+
participants to attend the meeting. The participants may be selected by the coordinator from the same GUI page in step <part-num-ref name="same GUI page in step">201,</part-num-ref>
|
| 176 |
+
or through another GUI page. The participants may also be selected from a predefined list or newly added by the coordinator. </p>
|
| 177 |
+
<boundary-data type="header">
|
| 178 |
+
<confidence value="8">5</confidence>
|
| 179 |
+
</boundary-data>
|
| 180 |
+
<boundary-data type="header">200501203</boundary-data>
|
| 181 |
+
<p id="p-33" num="33">
|
| 182 |
+
<page-break num="6"/>
|
| 183 |
+
[0028] Step 203 includes sending out invitations to the selected participants. The invitation to the meeting contains the meeting details. Each participant may accept or reject the invitation to the meeting at the workstation <part-num-ref name="workstation">101.</part-num-ref>
|
| 184 |
+
More than one workstation <part-num-ref name="workstation 101. More than one workstation">101</part-num-ref>
|
| 185 |
+
may be provided in another embodiment, and the participant may use any one of <boundary-data type="line-number">5 </boundary-data>
|
| 186 |
+
the workstations <part-num-ref name="workstations">101</part-num-ref>
|
| 187 |
+
to accept or reject the invitation. Once the participant accepts the invitation, each of the participants is able to add items for discussion during the scheduled meeting. </p>
|
| 188 |
+
<p id="p-34" num="34">[0029] Step 204 includes consolidating the discussion items submitted by the <boundary-data type="line-number">10 </boundary-data>
|
| 189 |
+
participants who accepted the invitation to the scheduled meeting. Open items from the previously occurred meetings may also be added by the coordinator. Step <part-num-ref name="coordinator. Step">205</part-num-ref>
|
| 190 |
+
includes selecting one or more items from the consolidated discussion items as items for the agenda. The coordinator is able to view all the discussion items added by the participants. Depending on the objectives of the meeting or other factors, the <boundary-data type="line-number">15 </boundary-data>
|
| 191 |
+
coordinator selects one or more items for the agenda from the discussion items. Step <part-num-ref name="discussion items. Step">206</part-num-ref>
|
| 192 |
+
includes informing the participants on the items for the agenda for the scheduled meeting. Specifically, the agenda items are sent to the participants who accepted the invitation to the meeting. </p>
|
| 193 |
+
<p id="p-35" num="35">
|
| 194 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 195 |
+
[0030] During the scheduled meeting, the system <part-num-ref name="system">100</part-num-ref>
|
| 196 |
+
also allows the coordinator or a chairperson of the meeting to go through each agenda item, write meeting minutes, and update a corresponding status of agenda item. The updating of the status of each agenda items includes closure of the item or assigning a responsible owner and an expected date of closure for the item. The items which are not closed are classified as <boundary-data type="line-number">25 </boundary-data>
|
| 197 |
+
action items to be completed before the expected date of closure. After the meeting, the coordinator or the chairperson closes the meeting and the system <part-num-ref name="system">100</part-num-ref>
|
| 198 |
+
sends the meeting minutes, the action items and closing comments, if any, to the participants of the meeting. The system <part-num-ref name="system">100</part-num-ref>
|
| 199 |
+
further allows the coordinator to monitor whether the action items have been completed before their respective expected date of closure, <boundary-data type="line-number">30 </boundary-data>
|
| 200 |
+
and send reminders if they have not been completed. </p>
|
| 201 |
+
<p id="p-36" num="36">[0031] Fig.3 and Fig.4 show a flow chart of a detailed example of the meeting management process according to an embodiment. Fig.3 relates to the process before the meeting and Fig.4 relates to the process during and after the meeting. Fig.5-12 <boundary-data type="header">
|
| 202 |
+
<confidence value="8">6</confidence>
|
| 203 |
+
</boundary-data>
|
| 204 |
+
<page-break num="7"/>
|
| 205 |
+
<boundary-data type="header">200501203</boundary-data>
|
| 206 |
+
show examples of GUI pages at different stages of the process for managing the meeting. </p>
|
| 207 |
+
<p id="p-37" num="37">[0032] The meeting management process before the meeting shall now be described <boundary-data type="line-number">5 </boundary-data>
|
| 208 |
+
with reference to the flow-chart of Fig.3, and in conjunction with Figs.5-8. In Fig.3, step <part-num-ref name="flow-chart of Fig.3, and in conjunction with Figs.5-8. In Fig.3, step">301</part-num-ref>
|
| 209 |
+
includes logging on to a website which accesses the application resided in the server <part-num-ref name="server">102</part-num-ref>
|
| 210 |
+
for managing the meeting. At the website, the coordinator logs in to use the application program to schedule a meeting. Such authentication of the identity of the coordinator prevents unauthorized access to the application program. An <boundary-data type="line-number">10 </boundary-data>
|
| 211 |
+
example of a website for the coordinator to log in to access the application program is shown in Fig.5. As seen from Fig.5, the login credentials include User Name <part-num-ref name="login credentials include User Name">501</part-num-ref>
|
| 212 |
+
and Password <part-num-ref name="and Password">502.</part-num-ref>
|
| 213 |
+
After the coordinator has logged in to the application program, he or she selects a "schedule a meeting" link to load a "schedule a meeting" GUI page. </p>
|
| 214 |
+
<p id="p-38" num="38">
|
| 215 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 216 |
+
[0033] Step 302 (in Fig.3) includes entering meeting details and selecting participants for the scheduled meeting. The meeting details are entered into various data fields provided on the "schedule a meeting" GUI page. The "schedule a meeting" GUI page also includes a data field for allowing the coordinator to select the desired participants for the scheduled meeting. Fig.6 shows an example of the "schedule a meeting" GUI <boundary-data type="line-number">20 </boundary-data>
|
| 217 |
+
page. The GUI page includes a "Review Start date/time" data field <part-num-ref name=""Review Start date/time" data field">601</part-num-ref>
|
| 218 |
+
for entering the date and time of the scheduled meeting. A "Review end date/time" data field <part-num-ref name=""Review end date/time" data field">602</part-num-ref>
|
| 219 |
+
is also included for entering the date and time the meeting is scheduled to end. By comparing the entries in both the data fields <part-num-ref name="data fields">601,</part-num-ref>
|
| 220 |
+
<part-num-ref name="data fields 601,">602,</part-num-ref>
|
| 221 |
+
the duration of the meeting can be computed. </p>
|
| 222 |
+
<p id="p-39" num="39">
|
| 223 |
+
<boundary-data type="line-number">
|
| 224 |
+
<confidence value="88">25</confidence>
|
| 225 |
+
</boundary-data>
|
| 226 |
+
[0034] The GUI page of Fig.6 also includes a "Venue" data field <part-num-ref name=""Venue" data field">603</part-num-ref>
|
| 227 |
+
for entering the venue of the scheduled meeting. The objective or purpose of the meeting can also be entered into a "Remarks if any" data field <part-num-ref name=""Remarks if any" data field">604.</part-num-ref>
|
| 228 |
+
A "Agenda review date" data field <part-num-ref name=""Agenda review date" data field">605</part-num-ref>
|
| 229 |
+
is also included for the coordinator to enter a date when the items for the agenda <boundary-data type="line-number">30 </boundary-data>
|
| 230 |
+
of the meeting has to be finalized. A document may also be uploaded to the server <part-num-ref name="server">102</part-num-ref>
|
| 231 |
+
by clicking on the "Browse" button <part-num-ref name=""Browse" button">606,</part-num-ref>
|
| 232 |
+
and selecting the desired document to be uploaded. </p>
|
| 233 |
+
<boundary-data type="header">
|
| 234 |
+
<confidence value="8">7</confidence>
|
| 235 |
+
</boundary-data>
|
| 236 |
+
<boundary-data type="header">200501203</boundary-data>
|
| 237 |
+
<p id="p-40" num="40">
|
| 238 |
+
<page-break num="8"/>
|
| 239 |
+
[0035] The coordinator selects the participants for the scheduled meeting from a drop down menu <part-num-ref name="drop down menu">607</part-num-ref>
|
| 240 |
+
provided in the "schedule a meeting" GUI page as shown in Fig.6. If a desired participant is not found from the drop down menu <part-num-ref name="drop down menu">607,</part-num-ref>
|
| 241 |
+
the coordinator may add the desired participant by typing the email address of the desired participant in a <boundary-data type="line-number">5 </boundary-data>
|
| 242 |
+
"Others Specify" data field <part-num-ref name=""Others Specify" data field">608</part-num-ref>
|
| 243 |
+
and clicking on a "Add To List" button <part-num-ref name=""Add To List" button">609.</part-num-ref>
|
| 244 |
+
The selected participants are displayed in a data field <part-num-ref name="data field">610.</part-num-ref>
|
| 245 |
+
Any one of the selected participants may be deleted by highlighting the participant to be desired to be deleted, and clicking on a "Delete From List" button <part-num-ref name=""Delete From List" button">611.</part-num-ref>
|
| 246 |
+
</p>
|
| 247 |
+
<p id="p-41" num="41">
|
| 248 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 249 |
+
[0036<confidence value="5">]</confidence>
|
| 250 |
+
Step 303 (Fig.3) includes sending an invitation to each of the participants for the scheduled meeting. The invitation is sent to the participants by clicking on a "Submit" button <part-num-ref name=""Submit" button">612</part-num-ref>
|
| 251 |
+
provided in the "schedule a meeting" GUI page of Fig.6. The coordinator may also preview the contents of the meeting by clicking on a "Preview" button <part-num-ref name=""Preview" button">613,</part-num-ref>
|
| 252 |
+
before sending the invitation to the participants. The invitation sent out to <boundary-data type="line-number">15 </boundary-data>
|
| 253 |
+
the participants includes the meeting details entered in Step <part-num-ref name="meeting details entered in Step">302.</part-num-ref>
|
| 254 |
+
Fig.7 shows an example of the invitation sent to the participants. The invitation is sent in a form of an email. In addition to the meeting details, the invitation also includes a meeting ID <part-num-ref name="meeting ID">
|
| 255 |
+
<confidence value="885">701</confidence>
|
| 256 |
+
</part-num-ref>
|
| 257 |
+
and a URL <part-num-ref name="URL">702</part-num-ref>
|
| 258 |
+
of the website for accessing the application. </p>
|
| 259 |
+
<p id="p-42" num="42">
|
| 260 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 261 |
+
[0037] Step 304 (Fig.3) includes determining whether each of the participants accepts the invitation to the meeting. After the participants received the meeting invitation, they may accept or reject the invitation with appropriate comments, if any. The participants log on to the website to accept or reject the meeting associated with the meeting ID. Each participant is able to add items for discussion in Step <part-num-ref name="meeting ID. Each participant is able to add items for discussion in Step">305</part-num-ref>
|
| 262 |
+
after <boundary-data type="line-number">25 </boundary-data>
|
| 263 |
+
accepting the invitation. </p>
|
| 264 |
+
<p id="p-43" num="43">[0038] Step 306 includes receiving a consolidated list of all the discussion items added by the participants who accepted the invitation. In addition, the coordinator also receives a list of participants who accepted or rejected the invitation. The <boundary-data type="line-number">30 </boundary-data>
|
| 265 |
+
coordinator may also log on to the website and view the list of the participants who accepted or rejected the invitation, and the consolidated list of the discussion items. </p>
|
| 266 |
+
<p id="p-44" num="44">The coordinator decides whether to proceed with the meeting depending on the attendance of the participants and the consolidated items for discussions in Step <part-num-ref name="consolidated items for discussions in Step">307.</part-num-ref>
|
| 267 |
+
</p>
|
| 268 |
+
<boundary-data type="header">
|
| 269 |
+
<confidence value="8">8</confidence>
|
| 270 |
+
</boundary-data>
|
| 271 |
+
<boundary-data type="header">200501203</boundary-data>
|
| 272 |
+
<p id="p-45" num="45">
|
| 273 |
+
<page-break num="9"/>
|
| 274 |
+
If the coordinator decides not to proceed with the meeting, the meeting is cancelled in Step <part-num-ref name="meeting is cancelled in Step">308,</part-num-ref>
|
| 275 |
+
and comments are sent out in an email to the participants. </p>
|
| 276 |
+
<p id="p-46" num="46">[0039] If the coordinator decides to proceed with the meeting, the coordinator selects <boundary-data type="line-number">5 </boundary-data>
|
| 277 |
+
items for the agenda from the consolidate discussion items in Step <part-num-ref name="consolidate discussion items in Step">309.</part-num-ref>
|
| 278 |
+
Discussion items which are not selected as items for the agenda are put under an Open Items List. </p>
|
| 279 |
+
<p id="p-47" num="47">Items under the Open Items List are available to be selected as items for the agenda of subsequent meetings. Step <part-num-ref name="agenda of subsequent meetings. Step">310</part-num-ref>
|
| 280 |
+
includes sending the agenda to the participants. Fig.8 shows an example of the agenda sent to the participants. </p>
|
| 281 |
+
<p id="p-48" num="48">
|
| 282 |
+
<boundary-data type="line-number">
|
| 283 |
+
<confidence value="88">10</confidence>
|
| 284 |
+
</boundary-data>
|
| 285 |
+
[0040] The coordinator may invite additional participants to the meeting in Step <part-num-ref name="meeting in Step">311.</part-num-ref>
|
| 286 |
+
</p>
|
| 287 |
+
<p id="p-49" num="49">If additional participants are to be invited, invitations are sent to the additional participants in Step <part-num-ref name="additional participants in Step">312.</part-num-ref>
|
| 288 |
+
The agenda may also be sent to the additional participants together with the invitation, or in a separate email. Although the additional <boundary-data type="line-number">15 </boundary-data>
|
| 289 |
+
participants are invited only after the agenda has been finalized in the example shown in the flow-chart of Fig.3, it is possible to invite additional participants any time before the meeting. If the additional participants are invited before the items for the agenda are finalized, the additional participants are also able to add items for discussion. </p>
|
| 290 |
+
<p id="p-50" num="50">
|
| 291 |
+
<boundary-data type="line-number">
|
| 292 |
+
<confidence value="88">20</confidence>
|
| 293 |
+
</boundary-data>
|
| 294 |
+
[0041] The meeting management process during and after the meeting shall now be described with reference to Fig.4, and in conjunction with Figs.9-12. The coordinator or a chairperson of the meeting may start the meeting by taking the attendance of the participants. An example of a GUI page for taking the attendance of the participants <boundary-data type="line-number">25 </boundary-data>
|
| 295 |
+
is shown in Fig.9. In the example shown in Fig.9, the coordinator click the check box <part-num-ref name="check box">901</part-num-ref>
|
| 296 |
+
beside each participant <part-num-ref name="beside each participant">902,</part-num-ref>
|
| 297 |
+
and click the "Update" button <part-num-ref name=""Update" button">903</part-num-ref>
|
| 298 |
+
to take the attendance of the participants. </p>
|
| 299 |
+
<p id="p-51" num="51">[0042] Step 401 of Fig.4 includes reviewing each item of the agenda and updating the <boundary-data type="line-number">30 </boundary-data>
|
| 300 |
+
item accordingly. The updating of the item includes closing the item, or defining the item as an action item with an expected date of closure and assigning a person responsible for closing the item before the expected date of closure. After all the items of the agenda have been reviewed, the chairperson may add new items for discussion in Step <part-num-ref name="chairperson may add new items for discussion in Step">402.</part-num-ref>
|
| 301 |
+
Any new items added are reviewed and updated accordingly <boundary-data type="header">
|
| 302 |
+
<confidence value="8">9</confidence>
|
| 303 |
+
</boundary-data>
|
| 304 |
+
<page-break num="10"/>
|
| 305 |
+
<boundary-data type="header">200501203</boundary-data>
|
| 306 |
+
in Step <part-num-ref name="chairperson may add new items for discussion in Step 402. Any new items added are reviewed and updated accordingly in Step">401.</part-num-ref>
|
| 307 |
+
The reviewed and updated items of agenda form the minutes of the meeting. </p>
|
| 308 |
+
<p id="p-52" num="52">[0043] Fig.10 shows an example of a page for updating the agenda item by defining <boundary-data type="line-number">5 </boundary-data>
|
| 309 |
+
the item as an action item with an expected date of closure and assigning a person responsible for closing the action item. Appropriate comments may be inserted into a "conclusion/path forward" data field <part-num-ref name=""conclusion/path forward" data field">1001.</part-num-ref>
|
| 310 |
+
The responsible owner for the action item is assigned by entering the name and email address of the owner into an "Owner" data field <part-num-ref name=""Owner" data field">1002</part-num-ref>
|
| 311 |
+
and an "Email" data field <part-num-ref name=""Email" data field">1003,</part-num-ref>
|
| 312 |
+
respectively. The expected date of closure <boundary-data type="line-number">10 </boundary-data>
|
| 313 |
+
is entered into the "Review Date" data field <part-num-ref name=""Review Date" data field">1004.</part-num-ref>
|
| 314 |
+
A document may also be uploaded onto the server <part-num-ref name="server">102</part-num-ref>
|
| 315 |
+
by clicking on the "Browse" button <part-num-ref name=""Browse" button">1005.</part-num-ref>
|
| 316 |
+
The action item may also be forwarded to another person by clicking on the "Forward" button <part-num-ref name=""Forward" button">1006.</part-num-ref>
|
| 317 |
+
</p>
|
| 318 |
+
<p id="p-53" num="53">[0044] After all the items of the agenda have been reviewed, the coordinator or the <boundary-data type="line-number">15 </boundary-data>
|
| 319 |
+
chairperson may close the meeting with closing comments in Step <part-num-ref name="meeting with closing comments in Step">403.</part-num-ref>
|
| 320 |
+
Fig. <confidence value="22">l1</confidence>
|
| 321 |
+
shows an example of an updated list of items during the meeting. The status of the items may be modified by clicking the "View" button <part-num-ref name=""View" button">1101.</part-num-ref>
|
| 322 |
+
New items can be added for discussion during the meeting as described in Step <part-num-ref name="meeting as described in Step">402</part-num-ref>
|
| 323 |
+
by clicking the "Add Item" button <part-num-ref name=""Add Item" button">1102.</part-num-ref>
|
| 324 |
+
The coordinator may also close the meeting by clicking the "Close <boundary-data type="line-number">20 </boundary-data>
|
| 325 |
+
Meeting & Send Minutes" button <part-num-ref name=""Close Meeting & Send Minutes" button">1103</part-num-ref>
|
| 326 |
+
as described in Step <part-num-ref name="as described in Step">403.</part-num-ref>
|
| 327 |
+
</p>
|
| 328 |
+
<p id="p-54" num="54">[0045] Step 404 includes allowing the coordinator or the chairperson to select a date for a next meeting. If the date for the next meeting is selected, the date of the next meeting is included in the minutes of the meeting in Step <part-num-ref name="meeting in Step">405.</part-num-ref>
|
| 329 |
+
The meeting minutes <boundary-data type="line-number">25 </boundary-data>
|
| 330 |
+
with the date of the next meeting are sent out to the participants in Step <part-num-ref name="participants in Step">406.</part-num-ref>
|
| 331 |
+
If the date of the next meeting is not selected, the meeting minutes are sent out to the participants in Step <part-num-ref name="participants in Step">406</part-num-ref>
|
| 332 |
+
without the date of the next meeting. Fig.12 shows an example of the meeting minutes sent to the participants. It is also possible to send the meeting minutes to one or more persons who are not participants of the meeting, but <boundary-data type="line-number">30 </boundary-data>
|
| 333 |
+
have been assigned as the person responsible for closing one of the action items. </p>
|
| 334 |
+
<p id="p-55" num="55">[0046] Once the meeting is over, a status of the meeting corresponding to the meeting ID is reflected as "occurred". The next meeting has a corresponding status of "planned". The coordinator or the person responsible for closing one of the action <boundary-data type="header">
|
| 335 |
+
<confidence value="88">10</confidence>
|
| 336 |
+
</boundary-data>
|
| 337 |
+
<page-break num="11"/>
|
| 338 |
+
<boundary-data type="header">200501203</boundary-data>
|
| 339 |
+
items may log on to the website to update the action items with appropriate comments. Updating of action items include entering comments, postponing the expected date of closure, closing the action items, or forwarding the action item to another person. Step <part-num-ref name="action item to another person. Step">407</part-num-ref>
|
| 340 |
+
includes determining whether any of the action items are <boundary-data type="line-number">5 </boundary-data>
|
| 341 |
+
closed by the expected date of closure. If one of the action items is not close by the expected date of closure, a reminder is sent to the person responsible for closing that action item in Step <part-num-ref name="person responsible for closing that action item in Step">408.</part-num-ref>
|
| 342 |
+
</p>
|
| 343 |
+
<p id="p-56" num="56">[0047] All the items under the Open Items List (those which were not selected as <boundary-data type="line-number">10 </boundary-data>
|
| 344 |
+
agenda items) and the action items which are not closed are reflected to the coordinator when planning for the next meeting. Even agenda items which are not reviewed during previous meetings may be reflected to the coordinator. Any previously closed agenda items or action items may be re-opened by the coordinator if he or she feels that the items have not been completed. </p>
|
| 345 |
+
<p id="p-57" num="57">
|
| 346 |
+
<boundary-data type="line-number">
|
| 347 |
+
<confidence value="88">15</confidence>
|
| 348 |
+
</boundary-data>
|
| 349 |
+
[0048] The meeting management system described above allows the coordinator to schedule and manage a meeting which takes place on a later date as described in the flow-charts of Fig.3 and Fig.4 according to an embodiment. It is also possible to use the meeting management system to schedule a meeting immediately, and manages the <boundary-data type="line-number">20 </boundary-data>
|
| 350 |
+
meeting progress according to another embodiment. In this embodiment, the coordinator or the chairperson adds new items for discussion during the meeting, and updates the status according to Steps <part-num-ref name="status according to Steps">401</part-num-ref>
|
| 351 |
+
to <part-num-ref name="to">408</part-num-ref>
|
| 352 |
+
in Fig.4. </p>
|
| 353 |
+
<p id="p-58" num="58">[0049] The meeting management system according to the embodiment allows the <boundary-data type="line-number">25 </boundary-data>
|
| 354 |
+
coordinator to have a summary of all the meetings of the participants and their availability. An example of the summary of meetings is shown in Fig.13. The coordinator is also able to generate a complete report of all the action items for a particular participant or for all the participants. Thus, the coordinator is able to efficiently track the action items resulted from the meeting for closure. The summary <boundary-data type="line-number">30 </boundary-data>
|
| 355 |
+
of meetings, action items and their statuses can also be exported to an external program, such as Microsoft Excel, for offline viewing or send to management as updates. </p>
|
| 356 |
+
<boundary-data type="header">
|
| 357 |
+
<confidence value="88">11</confidence>
|
| 358 |
+
</boundary-data>
|
| 359 |
+
<boundary-data type="header">200501203</boundary-data>
|
| 360 |
+
<p id="p-59" num="59">
|
| 361 |
+
<page-break num="12"/>
|
| 362 |
+
[0050] Although the present invention has been described in accordance with the embodiments as shown, one of ordinary skill in the art will readily recognize that there could be variations to the embodiments and those variations would be within the spirit and scope of the present invention. Accordingly, many modifications may be <boundary-data type="line-number">5 </boundary-data>
|
| 363 |
+
made by one of ordinary skill in the art without departing from the spirit and scope of the appended claims. </p>
|
| 364 |
+
<boundary-data type="header">
|
| 365 |
+
<confidence value="88">12</confidence>
|
| 366 |
+
</boundary-data>
|
| 367 |
+
</description>
|
| 368 |
+
</us-patent-application>
|
| 369 |
+
|
applicant/11499183.xml
ADDED
|
@@ -0,0 +1,870 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>11499183</doc-number>
|
| 8 |
+
<date>2006-08-03</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<heading id="h-1">UNITED STATES PATENT APPLICATION</heading>
|
| 14 |
+
<heading id="h-2">FOR</heading>
|
| 15 |
+
<heading id="h-3">MULTIMEDIA MAIL SYSTEM</heading>
|
| 16 |
+
<p id="p-1" num="1">Inventor:</p>
|
| 17 |
+
<p id="p-2" num="2">Srikanth Pa<confidence value="886">lli</confidence>
|
| 18 |
+
Prepared by: </p>
|
| 19 |
+
<p id="p-3" num="3">
|
| 20 |
+
<boundary-data type="line-number">Schwegman, </boundary-data>
|
| 21 |
+
Lundberg, Woessner & K<confidence value="5">l</confidence>
|
| 22 |
+
uth <boundary-data type="line-number">1600 </boundary-data>
|
| 23 |
+
TCF Tower 121 South Eighth Street Minneapolis, MN <part-num-ref name="South Eighth Street Minneapolis, MN">55402</part-num-ref>
|
| 24 |
+
<part-num-ref name="">(612)</part-num-ref>
|
| 25 |
+
373-6900 <boundary-data type="header">Attorney's Docket No. 2055.046U<confidence value="5">S</confidence>
|
| 26 |
+
<confidence value="8">1</confidence>
|
| 27 |
+
</boundary-data>
|
| 28 |
+
Recipient Ref. No.: B277 <page-break num="2"/>
|
| 29 |
+
</p>
|
| 30 |
+
<heading id="h-4">MULTIMEDIA MAIL SYSTEM</heading>
|
| 31 |
+
<heading id="h-5">FIELD</heading>
|
| 32 |
+
<p id="p-4" num="4">
|
| 33 |
+
<confidence value="5">[</confidence>
|
| 34 |
+
0001] This application relates to data communications and, in one example embodiment, to methods and systems to initiate streaming of a multimedia content message. </p>
|
| 35 |
+
<heading id="h-6">BACKGROUND</heading>
|
| 36 |
+
<p id="p-5" num="5">[0002<confidence value="5">]</confidence>
|
| 37 |
+
A user that sends a multimedia content file that contains audio data and video data over a network may encounter problems. One problem may be that the multimedia content file is not delivered because of its size. For example, the user may compose the multimedia content file at a client machine, attach the multimedia content file to an email, and send the email, with the attached multimedia content file, to a recipient client machine. However, the recipient client machine may not receive the multimedia content file because the recipient's inbox may impose a size limitation that prevents processing the attachment. Another problem may be that the software that generates the multimedia content file may require the client machine to provide substantial storage capacity (e.g., memory) and processing power. </p>
|
| 38 |
+
<p id="p-6" num="6">Consequently, some client machines may not be able to generate a multimedia content file because they lack sufficient memory and processing power.</p>
|
| 39 |
+
<boundary-data type="header">
|
| 40 |
+
<confidence value="8">2</confidence>
|
| 41 |
+
</boundary-data>
|
| 42 |
+
<boundary-data type="header">Atty. Dkt. No. 2055.046US<confidence value="4">1</confidence>
|
| 43 |
+
Recipient Ref. No.: B277 </boundary-data>
|
| 44 |
+
<heading id="h-7">BRIEF DESCRIPTION OF DRAWINGS</heading>
|
| 45 |
+
<p id="p-7" num="7">
|
| 46 |
+
<page-break num="3"/>
|
| 47 |
+
[0003] The present invention is illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements and in which: </p>
|
| 48 |
+
<p id="p-8" num="8">[0004] Figure 1 is a block diagram of a system used in an example embodiment of the present disclosure;</p>
|
| 49 |
+
<p id="p-9" num="9">
|
| 50 |
+
<confidence value="5">[</confidence>
|
| 51 |
+
0005] Figure 2 is a block diagram of a client machine used in an example embodiment of the present disclosure; </p>
|
| 52 |
+
<p id="p-10" num="10">[0006] Figure 3 is a block diagram of a client machine used in an example embodiment of the present disclosure;</p>
|
| 53 |
+
<p id="p-11" num="11">[0007] Figure 4 is a block diagram of a multimedia content message used in an example embodiment of the present disclosure;</p>
|
| 54 |
+
<p id="p-12" num="12">[0008] Figure 5 is a block diagram of a multimedia metadata message used in an example embodiment of the present disclosure;</p>
|
| 55 |
+
<p id="p-13" num="13">
|
| 56 |
+
<confidence value="5">[</confidence>
|
| 57 |
+
0009<confidence value="5">]</confidence>
|
| 58 |
+
Figure 6 is a block diagram of a recipient list used in an example embodiment of the present disclosure; </p>
|
| 59 |
+
<p id="p-14" num="14">[0010] Figure 7 is a block diagram of a multimedia table used in an example embodiment of the present disclosure;</p>
|
| 60 |
+
<p id="p-15" num="15">[0011] Figure 8 is a block diagram of a multimedia retrieval message used in an example embodiment of the present disclosure;</p>
|
| 61 |
+
<p id="p-16" num="16">[0012] Figure 9 is a block diagram of a multimedia content message identifier used in an example embodiment of the present disclosure;</p>
|
| 62 |
+
<p id="p-17" num="17">[0013] Figure 10 is a flow chart of a method used in an example embodiment of the present disclosure;</p>
|
| 63 |
+
<p id="p-18" num="18">[0014] Figure 11-14 are representations of user interfaces used in an example embodiment of the present disclosure;</p>
|
| 64 |
+
<p id="p-19" num="19">[0015<confidence value="5">]</confidence>
|
| 65 |
+
Figure 15 is a block diagram of a machine, according to an example embodiment, including instructions to perform any one or more of the methodologies described herein. </p>
|
| 66 |
+
<boundary-data type="header">
|
| 67 |
+
<confidence value="8">3</confidence>
|
| 68 |
+
</boundary-data>
|
| 69 |
+
<boundary-data type="header">Atty. Dkt. No. 2055.046US1 Recipient Ref. No.: B277</boundary-data>
|
| 70 |
+
<heading id="h-8">DETAILED DESCRIPTION</heading>
|
| 71 |
+
<p id="p-20" num="20">
|
| 72 |
+
<page-break num="4"/>
|
| 73 |
+
<confidence value="5">[</confidence>
|
| 74 |
+
0016] In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of an embodiment of the present invention. It will be evident, however, to one skilled in the art that the present invention may be practiced without these specific details. </p>
|
| 75 |
+
<p id="p-21" num="21">[0017] Figure 1 is a block diagram of a system <part-num-ref name="system">10</part-num-ref>
|
| 76 |
+
used in an example embodiment of the present disclosure. The system <part-num-ref name="system">10</part-num-ref>
|
| 77 |
+
is shown to include an application server machine <part-num-ref name="application server machine">12</part-num-ref>
|
| 78 |
+
(e.g., Flash<confidence value="4">®</confidence>
|
| 79 |
+
media server), a client machine <part-num-ref name="client machine">14</part-num-ref>
|
| 80 |
+
(e.g., sending machine), a client machine <part-num-ref name="client machine">16</part-num-ref>
|
| 81 |
+
(e.g., receiving machine), and a mail server machine <part-num-ref name="mail server machine">18</part-num-ref>
|
| 82 |
+
that communicate over a network <part-num-ref name="network">20.</part-num-ref>
|
| 83 |
+
</p>
|
| 84 |
+
<p id="p-22" num="22">
|
| 85 |
+
<confidence value="5">[</confidence>
|
| 86 |
+
0018<confidence value="4">]</confidence>
|
| 87 |
+
The client machine <part-num-ref name="client machine">14,</part-num-ref>
|
| 88 |
+
in the present embodiment, may be a sending machine that is utilized to send multimedia mail and/or email (e.g., electronic messages) and may be embodied as a personal computer, a personal video recorder, a set top box, a cell phone, or any other device capable of sending and receiving email and streaming multimedia. For example, the client machine <part-num-ref name="client machine">14</part-num-ref>
|
| 89 |
+
may include a microphone and camera that may be utilized by a user to stream a multimedia content message that includes audio data and video data over the network <part-num-ref name="network">20</part-num-ref>
|
| 90 |
+
to the application server machine <part-num-ref name="application server machine">12.</part-num-ref>
|
| 91 |
+
Multimedia content is defined as content that includes two or more media (e.g., text, audio, graphics, animation, video, etc.). </p>
|
| 92 |
+
<p id="p-23" num="23">[0019<confidence value="5">]</confidence>
|
| 93 |
+
In one example embodiment, the client machine <part-num-ref name="client machine">14</part-num-ref>
|
| 94 |
+
may use the Real Time Messaging Protocol (RTMP) to stream the multimedia content message from the client machine <part-num-ref name="client machine">14</part-num-ref>
|
| 95 |
+
to the application server machine <part-num-ref name="application server machine">12.</part-num-ref>
|
| 96 |
+
The RTMP is a proprietary protocol by Adobe Systems Inc. of San Jose, California used for accessing streaming multimedia and for elementary remote function calls. Other embodiments may use the RTMPT or the RTMPS protocols that use tunneling via the HTTP and H<confidence value="5">T</confidence>
|
| 97 |
+
TPS protocols respectively. Further the client machine <part-num-ref name="client machine">14</part-num-ref>
|
| 98 |
+
may be utilized by the user to communicate a recipient list that may identify the recipients of the multimedia content message and a multimedia metadata message (e.g., including XML content) that may include metadata for the multimedia content message. For example, in one example embodiment the client machine <part-num-ref name="client machine">14</part-num-ref>
|
| 99 |
+
may <boundary-data type="header">
|
| 100 |
+
<confidence value="8">4</confidence>
|
| 101 |
+
</boundary-data>
|
| 102 |
+
<boundary-data type="header">Atty. Dkt. No. 2055.046US1 Recipient Ref. No.: <confidence value="5">B</confidence>
|
| 103 |
+
277 </boundary-data>
|
| 104 |
+
<page-break num="5"/>
|
| 105 |
+
utilize the Simple Mail Transfer Protocol (SMTP) to commuincate the recipient list and the multimedia metadata message. </p>
|
| 106 |
+
<p id="p-24" num="24">[0020] The application server machine <part-num-ref name="application server machine">12</part-num-ref>
|
| 107 |
+
is shown to include a receiving module <part-num-ref name="receiving module">22</part-num-ref>
|
| 108 |
+
and a multimedia module <part-num-ref name="multimedia module">24</part-num-ref>
|
| 109 |
+
and is coupled to a database <part-num-ref name="database">26.</part-num-ref>
|
| 110 |
+
The receiving module <part-num-ref name="receiving module">22</part-num-ref>
|
| 111 |
+
may receive the streamed multimedia content message, the recipient list and the multimedia metadata message. Further, the receiving module <part-num-ref name="receiving module">22</part-num-ref>
|
| 112 |
+
may store the multimedia content message as a multimedia content file (e.g., Flas<confidence value="7">h</confidence>
|
| 113 |
+
video file) in a multimedia table <part-num-ref name="multimedia table">28</part-num-ref>
|
| 114 |
+
in the database <part-num-ref name="database">26</part-num-ref>
|
| 115 |
+
and the multimedia metadata message in the multimedia table <part-num-ref name="multimedia table">28</part-num-ref>
|
| 116 |
+
in the database <part-num-ref name="database">26.</part-num-ref>
|
| 117 |
+
Further, the multimedia module <part-num-ref name="multimedia module">24</part-num-ref>
|
| 118 |
+
may generate a multimedia retrieval message(s) based on the recipient list and communicate the multimedia retrieval message(s) over the network <part-num-ref name="network">20</part-num-ref>
|
| 119 |
+
to the mail server machine(s) <part-num-ref name="mail server machine(s)">18</part-num-ref>
|
| 120 |
+
identified by the recipient list. The multimedia retrieval message may include a multimedia message identifier that is utilized to identify the location of the Flash<confidence value="5">@</confidence>
|
| 121 |
+
video file. Further, the multimedia retrieval message may be compliant with the Multipurpose Internet Mail Extension (MIME), an Internet standard specif<confidence value="8">y</confidence>
|
| 122 |
+
ing message formats for transmission of different types of data by electronic mail. </p>
|
| 123 |
+
<p id="p-25" num="25">[0021] The mail server machine <part-num-ref name="mail server machine">18</part-num-ref>
|
| 124 |
+
is shown to be coupled to a database <part-num-ref name="database">30</part-num-ref>
|
| 125 |
+
that may be used to store multimedia retrieval messages <part-num-ref name="that may be used to store multimedia retrieval messages">32</part-num-ref>
|
| 126 |
+
and email messages (e.g., electronic messages) in the database <part-num-ref name="database">30.</part-num-ref>
|
| 127 |
+
The mail server machine <part-num-ref name="mail server machine">18</part-num-ref>
|
| 128 |
+
may respond to requests from the client machine <part-num-ref name="client machine">16</part-num-ref>
|
| 129 |
+
to retrieve multimedia retrieval messages <confidence value="5">.</confidence>
|
| 130 |
+
and email messages. </p>
|
| 131 |
+
<p id="p-26" num="26">[0022] The client machine <part-num-ref name="client machine">16,</part-num-ref>
|
| 132 |
+
in the example embodiment, may be a receiving machine to receive a multimedia mail and may be embodied as the client machine <part-num-ref name="client machine">14</part-num-ref>
|
| 133 |
+
described above. The client machine <part-num-ref name="client machine">16</part-num-ref>
|
| 134 |
+
may be utilized by a user to receive the multimedia mail. For example, the user may retrieve the multimedia retrieval message and/or email (e.g., electronic messages) from the mail server machine <part-num-ref name="mail server machine">18</part-num-ref>
|
| 135 |
+
and select a multimedia retrieval message to initiate streaming. In one example embodiment, the client machine <part-num-ref name="client machine">16</part-num-ref>
|
| 136 |
+
may use the Plain Old Post Office Version <part-num-ref name="Plain Old Post Office Version">3</part-num-ref>
|
| 137 |
+
(POP3) protocol to retrieve the multimedia retrieval message and or email from the mail server machine <part-num-ref name="mail server machine">18.</part-num-ref>
|
| 138 |
+
The POP3 protocol is an application-layer Internet <boundary-data type="header">
|
| 139 |
+
<confidence value="8">5</confidence>
|
| 140 |
+
</boundary-data>
|
| 141 |
+
<boundary-data type="header">Atty. Dkt. No. 2055.046US1 Recipient Ref. No.: B277</boundary-data>
|
| 142 |
+
<page-break num="6"/>
|
| 143 |
+
standard protocol to retrieve e-mail from a remote server over a TCP/IP connection. </p>
|
| 144 |
+
<p id="p-27" num="27">Accordingly, the user may select the multimedia retrieval message to cause the client machine <part-num-ref name="client machine">16</part-num-ref>
|
| 145 |
+
to utilize the associated multimedia content message identifier to initiate streaming of the multimedia content message, over the network <part-num-ref name="network">20</part-num-ref>
|
| 146 |
+
(e.g., RTMP, RTMPT, RTMPS), for play on the client machine <part-num-ref name="client machine">16.</part-num-ref>
|
| 147 |
+
</p>
|
| 148 |
+
<p id="p-28" num="28">[0023<confidence value="5">1</confidence>
|
| 149 |
+
The network <part-num-ref name="network">20</part-num-ref>
|
| 150 |
+
may be any network capable of communicating text and/or video and/or audio and/or graphics, and/or animation, etc., and may include the Internet, Digital Subscriber Line (DSL), satellite, cable, digital, terrestrial, X<confidence value="5">M</confidence>
|
| 151 |
+
satellite, Local Area Networks (LAN), radio, etc. It will be appreciated that while the client machine <part-num-ref name="client machine">14</part-num-ref>
|
| 152 |
+
is described above as sending the multimedia mail and the client machine <part-num-ref name="client machine">16</part-num-ref>
|
| 153 |
+
is described above as receiving the multimedia mail that such a description is merely for the purpose of clarity and that the client machines <part-num-ref name="client machines">14,</part-num-ref>
|
| 154 |
+
<part-num-ref name="client machines 14,">16</part-num-ref>
|
| 155 |
+
may both send and receive the multimedia mail. Further, while the system <part-num-ref name="system">10</part-num-ref>
|
| 156 |
+
is shown in Figure 1 to employ a client-server architecture, the present disclosure is of course not limited to such an architecture, and could equally well find application in other architectures. Embodiments may, for example, be implemented as a standalone application (e.g., without any network capabilities), a client-server application or a peer-to-peer (or distributed) application. Embodiments may, for example, be deployed by Software as a Service (SaaS), Application Service Provider (ASP), or utility computing providers, in addition to being sold or licensed via traditional channels. </p>
|
| 157 |
+
<p id="p-29" num="29">
|
| 158 |
+
<confidence value="5">[</confidence>
|
| 159 |
+
0024<confidence value="5">1</confidence>
|
| 160 |
+
Figure 2 is a block diagram of the client machine <part-num-ref name="client machine">14,</part-num-ref>
|
| 161 |
+
<part-num-ref name="client machine 14,">16</part-num-ref>
|
| 162 |
+
that may be used in an example embodiment of the present disclosure. The client machine <part-num-ref name="client machine">14,</part-num-ref>
|
| 163 |
+
<part-num-ref name="client machine 14,">16</part-num-ref>
|
| 164 |
+
is shown to include a mail module <part-num-ref name="mail module">40,</part-num-ref>
|
| 165 |
+
a local multimedia inbox <part-num-ref name="local multimedia inbox">45,</part-num-ref>
|
| 166 |
+
a local email inbox <part-num-ref name="local email inbox">47</part-num-ref>
|
| 167 |
+
and shown to be coupled to communication devices <part-num-ref name="and shown to be coupled to communication devices">42.</part-num-ref>
|
| 168 |
+
In one example embodiment, the mail module <part-num-ref name="mail module">40</part-num-ref>
|
| 169 |
+
may be embodied as Microsoft Outlook created by Microsoft Inc. of Redmond, Washington State and may be utilized to generate and retrieve email. The mail module <part-num-ref name="mail module">40</part-num-ref>
|
| 170 |
+
is further shown to include a multimedia mail module <part-num-ref name="multimedia mail module">44</part-num-ref>
|
| 171 |
+
that, in one example embodiment, may be a plugin to the mail module <part-num-ref name="mail module">40.</part-num-ref>
|
| 172 |
+
In general, a plugin (or plug-in) is a computer program that interacts with a main application (a web browser or an email program, for example) to provide a certain, <boundary-data type="header">
|
| 173 |
+
<confidence value="8">6</confidence>
|
| 174 |
+
</boundary-data>
|
| 175 |
+
<boundary-data type="header">Atty. Dkt. No. 2055.046US1 Recipient Ref. No.: B277</boundary-data>
|
| 176 |
+
<page-break num="7"/>
|
| 177 |
+
usually very specific, function. The multimedia mail module <part-num-ref name="multimedia mail module">44</part-num-ref>
|
| 178 |
+
may be utilized to provide multimedia mail services by enabling the publication of a recorded media stream to the application server machine <part-num-ref name="application server machine">12</part-num-ref>
|
| 179 |
+
and by enabling the reception of a media stream from the application server machine <part-num-ref name="application server machine">12</part-num-ref>
|
| 180 |
+
that may be played by the multimedia mail module <part-num-ref name="multimedia mail module">44.</part-num-ref>
|
| 181 |
+
The multimedia mail services may further include communicating a multimedia metadata message to the application server machine <part-num-ref name="application server machine">12,</part-num-ref>
|
| 182 |
+
communicating a recipient list to the application server machine <part-num-ref name="application server machine">12,</part-num-ref>
|
| 183 |
+
retrieving a multimedia retrieval message, and enabling the initiation of streaming of the multimedia content message from the application server machine <part-num-ref name="application server machine">12</part-num-ref>
|
| 184 |
+
to the client machine <part-num-ref name="client machine">14,</part-num-ref>
|
| 185 |
+
<part-num-ref name="client machine 14,">16.</part-num-ref>
|
| 186 |
+
Accordingly, the mail module <part-num-ref name="mail module">40</part-num-ref>
|
| 187 |
+
and the multimedia mail module <part-num-ref name="multimedia mail module">44</part-num-ref>
|
| 188 |
+
may be utilized to generate and retrieve email and multimedia mail. Further, the multimedia mail module <part-num-ref name="multimedia mail module">44</part-num-ref>
|
| 189 |
+
may be said to be a thin client rather than a thick client. </p>
|
| 190 |
+
<p id="p-30" num="30">For example, a thin client may include logic necessary to connect to the application server machine <part-num-ref name="application server machine">12</part-num-ref>
|
| 191 |
+
and publish a recorded media stream to the application server machine <part-num-ref name="application server machine">12.</part-num-ref>
|
| 192 |
+
In contrast, a thick client may require logic to sufficient generate a multimedia (e.g., Adobe Flash<confidence value="5">@</confidence>
|
| 193 |
+
Video) file at the client machine <part-num-ref name="client machine">14.</part-num-ref>
|
| 194 |
+
Also, for example, a thin client may include logic to connect to the application server machine <part-num-ref name="application server machine">12,</part-num-ref>
|
| 195 |
+
receive a media stream from the application server machine <part-num-ref name="application server machine">12,</part-num-ref>
|
| 196 |
+
and play the media stream at the client machine <part-num-ref name="client machine">16.</part-num-ref>
|
| 197 |
+
A thick client may require downloading the entire multimedia (e.g., Flash<confidence value="2">®</confidence>
|
| 198 |
+
file) from the application server machine <part-num-ref name="application server machine">12</part-num-ref>
|
| 199 |
+
before playing the multimedia file at the receiving machine (e.g., client machine 16). The local multimedia inbox <part-num-ref name="local multimedia inbox">45</part-num-ref>
|
| 200 |
+
may be utilized to store multimedia retrieval messages that may be retrieved by the receiving machine (e.g., client machine <part-num-ref name="client machine">16)</part-num-ref>
|
| 201 |
+
from the mail server machine <part-num-ref name="mail server machine">18.</part-num-ref>
|
| 202 |
+
The local email inbox <part-num-ref name="local email inbox">47</part-num-ref>
|
| 203 |
+
may be utilized to store email messages that may be retrieved by the receiving machine (e.g., client machine <part-num-ref name="client machine">16)</part-num-ref>
|
| 204 |
+
from the mail server machine <part-num-ref name="mail server machine">18.</part-num-ref>
|
| 205 |
+
</p>
|
| 206 |
+
<p id="p-31" num="31">
|
| 207 |
+
<confidence value="5">[</confidence>
|
| 208 |
+
0025<confidence value="5">]</confidence>
|
| 209 |
+
The communication devices <part-num-ref name="communication devices">42</part-num-ref>
|
| 210 |
+
are shown to include input devices <part-num-ref name="are shown to include input devices">46</part-num-ref>
|
| 211 |
+
and output devices <part-num-ref name="and output devices">48.</part-num-ref>
|
| 212 |
+
The input devices <part-num-ref name="input devices">46</part-num-ref>
|
| 213 |
+
may include a sound input device <part-num-ref name="sound input device">54</part-num-ref>
|
| 214 |
+
for recording audio data and a display input device <part-num-ref name="display input device">56</part-num-ref>
|
| 215 |
+
for recording video data. The output devices <part-num-ref name="output devices">48</part-num-ref>
|
| 216 |
+
may include a sound output device <part-num-ref name="sound output device">50</part-num-ref>
|
| 217 |
+
for presenting audio data and a display output device <part-num-ref name="display output device">52</part-num-ref>
|
| 218 |
+
for presenting video data; however, it will be <boundary-data type="header">
|
| 219 |
+
<confidence value="8">7</confidence>
|
| 220 |
+
</boundary-data>
|
| 221 |
+
<boundary-data type="header">Atty. Dkt. No. 2055.046US1 Recipient Ref. No.: B277</boundary-data>
|
| 222 |
+
<page-break num="8"/>
|
| 223 |
+
appreciated by those skilled in the art that the output devices <part-num-ref name="output devices">48</part-num-ref>
|
| 224 |
+
may also include a machine device to communicate machine interface information (e.g., SGML) to a machine (e.g., client, server, peer to peer). The sound input device <part-num-ref name="sound input device">54</part-num-ref>
|
| 225 |
+
may be embodied as a microphone and the display input device <part-num-ref name="display input device">56</part-num-ref>
|
| 226 |
+
may be embodied as a camera or a web cam. The sound output device <part-num-ref name="sound output device">50</part-num-ref>
|
| 227 |
+
may be embodied as a speaker or headphones and the display output device <part-num-ref name="display output device">52</part-num-ref>
|
| 228 |
+
may be embodied as a monitor, a television screen, etc... The communication devices <part-num-ref name="communication devices">42</part-num-ref>
|
| 229 |
+
may be utilized to transmit and receive video and audio data by utilizing various technologies supported by the client machine <part-num-ref name="client machine">14,</part-num-ref>
|
| 230 |
+
<part-num-ref name="client machine 14,">16</part-num-ref>
|
| 231 |
+
including lossy compression, variable frame resolution and variable frame rates. </p>
|
| 232 |
+
<p id="p-32" num="32">
|
| 233 |
+
<confidence value="5">[</confidence>
|
| 234 |
+
0026] Figure 3 is a block diagram of a client machine <part-num-ref name="client machine">14,</part-num-ref>
|
| 235 |
+
<part-num-ref name="client machine 14,">16</part-num-ref>
|
| 236 |
+
used in an example embodiment of the present disclosure. The client machine <part-num-ref name="client machine">14,</part-num-ref>
|
| 237 |
+
<part-num-ref name="client machine 14,">16</part-num-ref>
|
| 238 |
+
is shown to include the multimedia mail module <part-num-ref name="multimedia mail module">44</part-num-ref>
|
| 239 |
+
embodied as a stand-alone version and not a plug in. For example, the multimedia mail module <part-num-ref name="multimedia mail module">44</part-num-ref>
|
| 240 |
+
may provide email services in addition to the previously described multimedia (e.g., Flash Video<confidence value="28">®)</confidence>
|
| 241 |
+
services. </p>
|
| 242 |
+
<p id="p-33" num="33">[0027<confidence value="4">]</confidence>
|
| 243 |
+
Figure 4 is a block diagram of a multimedia content message <part-num-ref name="multimedia content message">60</part-num-ref>
|
| 244 |
+
used in an example embodiment of the present disclosure. The multimedia content message <part-num-ref name="multimedia content message">60,</part-num-ref>
|
| 245 |
+
for example, may be streamed from a sending machine (e.g., client machine <part-num-ref name="client machine">14)</part-num-ref>
|
| 246 |
+
to the application server machine <part-num-ref name="application server machine">12</part-num-ref>
|
| 247 |
+
and/or from the application server machine <part-num-ref name="application server machine">12</part-num-ref>
|
| 248 |
+
to a receiving machine (e.g., client machine 16). The multimedia content message <part-num-ref name="multimedia content message">60</part-num-ref>
|
| 249 |
+
is shown to include video data <part-num-ref name="is shown to include video data">64,</part-num-ref>
|
| 250 |
+
and audio data <part-num-ref name="is shown to include video data 64, and audio data">66.</part-num-ref>
|
| 251 |
+
Other embodiments of the multimedia content message <part-num-ref name="multimedia content message">60</part-num-ref>
|
| 252 |
+
may include video data <part-num-ref name="may include video data">64</part-num-ref>
|
| 253 |
+
and/or audio data <part-num-ref name="and/or audio data">66</part-num-ref>
|
| 254 |
+
and/or graphic data and/or text data and/or alphanumeric data and/or still image data, etc. </p>
|
| 255 |
+
<p id="p-34" num="34">
|
| 256 |
+
<confidence value="5">[</confidence>
|
| 257 |
+
0028<confidence value="5">]</confidence>
|
| 258 |
+
Figure 5 is a block diagram of a multimedia metadata message <part-num-ref name="multimedia metadata message">68</part-num-ref>
|
| 259 |
+
used in an example embodiment of the present disclosure. The multimedia metadata message <part-num-ref name="multimedia metadata message">68</part-num-ref>
|
| 260 |
+
is shown to include a sender network address <part-num-ref name="sender network address">70</part-num-ref>
|
| 261 |
+
that may be utilized to identify the sending machine, a subject <part-num-ref name="subject">72</part-num-ref>
|
| 262 |
+
and a stream name <part-num-ref name="stream name">74</part-num-ref>
|
| 263 |
+
that may be utilized to identify the associated multimedia content message <part-num-ref name="associated multimedia content message">60.</part-num-ref>
|
| 264 |
+
The sender network address <part-num-ref name="sender network address">70</part-num-ref>
|
| 265 |
+
may be automatically entered into the multimedia metadata <boundary-data type="header">
|
| 266 |
+
<confidence value="8">8</confidence>
|
| 267 |
+
</boundary-data>
|
| 268 |
+
<boundary-data type="header">Atty. Dkt. No. 2055.046US1 Recipient Ref. No.: B277</boundary-data>
|
| 269 |
+
<page-break num="9"/>
|
| 270 |
+
message <part-num-ref name="multimedia metadata message">68</part-num-ref>
|
| 271 |
+
by the multimedia mail module <part-num-ref name="multimedia mail module">44</part-num-ref>
|
| 272 |
+
responsive to the user composing multimedia mail. The subject <part-num-ref name="subject">72</part-num-ref>
|
| 273 |
+
may be entered by the user (e.g., sender) operating a keyboard at the client machine <part-num-ref name="client machine">14.</part-num-ref>
|
| 274 |
+
In one example embodiment, the stream name <part-num-ref name="stream name">74</part-num-ref>
|
| 275 |
+
may be automatically generated by the multimedia mail module <part-num-ref name="multimedia mail module">44.</part-num-ref>
|
| 276 |
+
In another embodiment, the stream name <part-num-ref name="stream name">74</part-num-ref>
|
| 277 |
+
may automatically generated by the multimedia module <part-num-ref name="multimedia module">24</part-num-ref>
|
| 278 |
+
at the application server machine <part-num-ref name="application server machine">12.</part-num-ref>
|
| 279 |
+
Yet in another embodiment, the stream name <part-num-ref name="stream name">74</part-num-ref>
|
| 280 |
+
may entered by the user (e.g., sender) operating a keyboard at the client machine <part-num-ref name="client machine">14.</part-num-ref>
|
| 281 |
+
In one embodiment the sender network address <part-num-ref name="sender network address">70</part-num-ref>
|
| 282 |
+
the subject <part-num-ref name="subject">72</part-num-ref>
|
| 283 |
+
and the stream name <part-num-ref name="stream name">74</part-num-ref>
|
| 284 |
+
may be described by using Extensible Markup Language (XML). XML is a W<confidence value="66">3C</confidence>
|
| 285 |
+
-recommended general-purpose markup language for creating special-purpose markup languages and is used to describe data and the meaning of such data. </p>
|
| 286 |
+
<p id="p-35" num="35">
|
| 287 |
+
<confidence value="5">[</confidence>
|
| 288 |
+
0029<confidence value="5">]</confidence>
|
| 289 |
+
Figure 6 is a block diagram of a recipient list <part-num-ref name="recipient list">80</part-num-ref>
|
| 290 |
+
used in an example embodiment of the present disclosure. The recipient list <part-num-ref name="recipient list">80</part-num-ref>
|
| 291 |
+
is shown to include multiple recipient network addresses <part-num-ref name="is shown to include multiple recipient network addresses">82</part-num-ref>
|
| 292 |
+
including a first recipient. The recipient network addresses <part-num-ref name="recipient network addresses">82</part-num-ref>
|
| 293 |
+
may be used to identify the network address of the recipients of a corresponding multimedia mail. The recipient list <part-num-ref name="recipient list">80</part-num-ref>
|
| 294 |
+
may be entered by the user at the sending machine (e.g., client machine <part-num-ref name="client machine">14)</part-num-ref>
|
| 295 |
+
and communicated over the network <part-num-ref name="network">20</part-num-ref>
|
| 296 |
+
to the application server machine <part-num-ref name="application server machine">12.</part-num-ref>
|
| 297 |
+
The recipient list <part-num-ref name="recipient list">80</part-num-ref>
|
| 298 |
+
may be used by the application server machine <part-num-ref name="application server machine">12</part-num-ref>
|
| 299 |
+
to generate multimedia retrieval messages that are communicated to the mail server machines <part-num-ref name="mail server machines">18</part-num-ref>
|
| 300 |
+
from which the receiving machines (e.g., client machine <part-num-ref name="client machine">16)</part-num-ref>
|
| 301 |
+
may respectively retrieve the multimedia retrieval messages. </p>
|
| 302 |
+
<p id="p-36" num="36">[0030<confidence value="5">]</confidence>
|
| 303 |
+
Figure 7 is a block diagram of a multimedia table <part-num-ref name="multimedia table">28</part-num-ref>
|
| 304 |
+
used in an example embodiment of the present disclosure. The multimedia table <part-num-ref name="multimedia table">28</part-num-ref>
|
| 305 |
+
may be stored within the database <part-num-ref name="database">26</part-num-ref>
|
| 306 |
+
that may be coupled to the application server machine <part-num-ref name="application server machine">12</part-num-ref>
|
| 307 |
+
and is shown to include multiple inboxes <part-num-ref name="and is shown to include multiple inboxes">90.</part-num-ref>
|
| 308 |
+
For example, respective inboxes <part-num-ref name="and is shown to include multiple inboxes 90. For example, respective inboxes">90</part-num-ref>
|
| 309 |
+
may correspond to the recipient network addresses <part-num-ref name="recipient network addresses">82</part-num-ref>
|
| 310 |
+
previously described. Each inbox <part-num-ref name="previously described. Each inbox">90</part-num-ref>
|
| 311 |
+
may include one or more multimedia files <part-num-ref name="may include one or more multimedia files">91</part-num-ref>
|
| 312 |
+
that respectively include the multimedia content file <part-num-ref name="multimedia content file">92,</part-num-ref>
|
| 313 |
+
and the multimedia metadata file <part-num-ref name="multimedia metadata file">93.</part-num-ref>
|
| 314 |
+
The multimedia content file <part-num-ref name="multimedia content file">92</part-num-ref>
|
| 315 |
+
may be generated and stored in the multimedia file <part-num-ref name="multimedia file">91</part-num-ref>
|
| 316 |
+
by the <boundary-data type="header">
|
| 317 |
+
<confidence value="8">9</confidence>
|
| 318 |
+
</boundary-data>
|
| 319 |
+
<boundary-data type="header">Atty. Dkt. No. 2055.046US1 Recipient Ref. No.: B277</boundary-data>
|
| 320 |
+
<page-break num="10"/>
|
| 321 |
+
receiving module <part-num-ref name="receiving module">22,</part-num-ref>
|
| 322 |
+
responsive to receipt of the multimedia content message <part-num-ref name="multimedia content message">60</part-num-ref>
|
| 323 |
+
and containing the multimedia content message <part-num-ref name="multimedia content message">60</part-num-ref>
|
| 324 |
+
(e.g., the multimedia content file <part-num-ref name="multimedia content file">92</part-num-ref>
|
| 325 |
+
may include video data <part-num-ref name="may include video data">64</part-num-ref>
|
| 326 |
+
and/or audio data <part-num-ref name="and/or audio data">66</part-num-ref>
|
| 327 |
+
and/or graphic data). The multimedia metadata file <part-num-ref name="multimedia metadata file">93</part-num-ref>
|
| 328 |
+
may be generated and stored in the multimedia file <part-num-ref name="multimedia file">91</part-num-ref>
|
| 329 |
+
by the receiving module <part-num-ref name="receiving module">22</part-num-ref>
|
| 330 |
+
responsive to receipt of the multimedia metadata message <part-num-ref name="multimedia metadata message">68.</part-num-ref>
|
| 331 |
+
For example, the multimedia metadata file <part-num-ref name="multimedia metadata file">93</part-num-ref>
|
| 332 |
+
may contain the multimedia metadata message <part-num-ref name="multimedia metadata message">68.</part-num-ref>
|
| 333 |
+
</p>
|
| 334 |
+
<p id="p-37" num="37">[0031<confidence value="5">1</confidence>
|
| 335 |
+
Figure 8 is a block diagram of a multimedia retrieval message <part-num-ref name="multimedia retrieval message">94</part-num-ref>
|
| 336 |
+
used in an example embodiment of the present disclosure. The multimedia retrieval message <part-num-ref name="multimedia retrieval message">94</part-num-ref>
|
| 337 |
+
may be generated by the application server machine <part-num-ref name="application server machine">12</part-num-ref>
|
| 338 |
+
responsive to receipt of the multimedia metadata message <part-num-ref name="multimedia metadata message">68</part-num-ref>
|
| 339 |
+
and/or the recipient list <part-num-ref name="recipient list">80,</part-num-ref>
|
| 340 |
+
and communicated to the mail server machine <part-num-ref name="mail server machine">18</part-num-ref>
|
| 341 |
+
where it may be retrieved by the receiving machine (e.g., client machine 16). The multimedia retrieval message <part-num-ref name="multimedia retrieval message">94</part-num-ref>
|
| 342 |
+
may be displayed on and selected from a user interface by a user operating the receiving machine (e.g., client machine <part-num-ref name="client machine">16)</part-num-ref>
|
| 343 |
+
to initiate streaming of the corresponding multimedia content message <part-num-ref name="corresponding multimedia content message">60</part-num-ref>
|
| 344 |
+
to the receiving machine (e.g., client machine 16). The multimedia retrieval message <part-num-ref name="multimedia retrieval message">94</part-num-ref>
|
| 345 |
+
is shown to include multimedia retrieval information <part-num-ref name="is shown to include multimedia retrieval information">94</part-num-ref>
|
| 346 |
+
that may, for example, be described with <confidence value="5">X</confidence>
|
| 347 |
+
ML. The multimedia retrieval information <part-num-ref name="multimedia retrieval information">94</part-num-ref>
|
| 348 |
+
includes the sender network address <part-num-ref name="sender network address">70,</part-num-ref>
|
| 349 |
+
the recipient network address <part-num-ref name="recipient network address">82,</part-num-ref>
|
| 350 |
+
the subject <part-num-ref name="subject">72,</part-num-ref>
|
| 351 |
+
a timestamp <part-num-ref name="timestamp">73</part-num-ref>
|
| 352 |
+
and a multimedia content message identifier <part-num-ref name="multimedia content message identifier">96.</part-num-ref>
|
| 353 |
+
The multimedia retrieval message <part-num-ref name="multimedia retrieval message">94</part-num-ref>
|
| 354 |
+
may be generated for and communicated to a recipient network address <part-num-ref name="recipient network address">82</part-num-ref>
|
| 355 |
+
included in the recipient list <part-num-ref name="recipient list">80.</part-num-ref>
|
| 356 |
+
Multiple recipient network addresses <part-num-ref name="recipient list 80. Multiple recipient network addresses">82</part-num-ref>
|
| 357 |
+
in the recipient list <part-num-ref name="recipient list">80</part-num-ref>
|
| 358 |
+
may result in the application server machine <part-num-ref name="application server machine">12</part-num-ref>
|
| 359 |
+
generating and communicating multiple multimedia retrieval messages <part-num-ref name="generating and communicating multiple multimedia retrieval messages">94.</part-num-ref>
|
| 360 |
+
The multimedia retrieval message <part-num-ref name="multimedia retrieval message">94</part-num-ref>
|
| 361 |
+
may be displayed at the receiving machine (e.g., client machine <part-num-ref name="client machine">16)</part-num-ref>
|
| 362 |
+
where the user may select the multimedia retrieval message <part-num-ref name="multimedia retrieval message">94</part-num-ref>
|
| 363 |
+
to cause the receiving machine (e.g., client machine <part-num-ref name="client machine">16)</part-num-ref>
|
| 364 |
+
to request the application server machine <part-num-ref name="application server machine">12</part-num-ref>
|
| 365 |
+
to initiate streaming of the multimedia content message <part-num-ref name="multimedia content message">60</part-num-ref>
|
| 366 |
+
from the application server machine <part-num-ref name="application server machine">12</part-num-ref>
|
| 367 |
+
to the receiving machine (e.g., client machine 16). For example, the receiving machine may utilize the multimedia content message identifier <part-num-ref name="multimedia content message identifier">96</part-num-ref>
|
| 368 |
+
included in the multimedia <boundary-data type="header">
|
| 369 |
+
<confidence value="88">10</confidence>
|
| 370 |
+
</boundary-data>
|
| 371 |
+
<boundary-data type="header">Atty. Dkt. No. 2055.046US1 Recipient Ref. No.: B277</boundary-data>
|
| 372 |
+
<page-break num="11"/>
|
| 373 |
+
retrieval message <part-num-ref name="multimedia retrieval message">94</part-num-ref>
|
| 374 |
+
to identify the location of the application server machine <part-num-ref name="application server machine">12</part-num-ref>
|
| 375 |
+
on the network <part-num-ref name="network">20</part-num-ref>
|
| 376 |
+
and the corresponding multimedia content file <part-num-ref name="corresponding multimedia content file">92</part-num-ref>
|
| 377 |
+
on the database <part-num-ref name="database">26</part-num-ref>
|
| 378 |
+
coupled to the application server machine <part-num-ref name="application server machine">12.</part-num-ref>
|
| 379 |
+
</p>
|
| 380 |
+
<p id="p-38" num="38">
|
| 381 |
+
<confidence value="5">[</confidence>
|
| 382 |
+
0032<confidence value="5">]</confidence>
|
| 383 |
+
Figure 9 is a block diagram of a multimedia content message identifier <part-num-ref name="multimedia content message identifier">96</part-num-ref>
|
| 384 |
+
(e.g., stream identifier) used in an example embodiment of the present disclosure. The multimedia content message identifier <part-num-ref name="multimedia content message identifier">96</part-num-ref>
|
| 385 |
+
is shown to include an application server network address <part-num-ref name="application server network address">100</part-num-ref>
|
| 386 |
+
and the previously described stream name <part-num-ref name="previously described stream name">74.</part-num-ref>
|
| 387 |
+
The application server network address <part-num-ref name="application server network address">100</part-num-ref>
|
| 388 |
+
may for example include the network address of the application server machine <part-num-ref name="application server machine">12</part-num-ref>
|
| 389 |
+
(e.g., multimedia server) on the network <part-num-ref name="network">20.</part-num-ref>
|
| 390 |
+
The stream name <part-num-ref name="stream name">74</part-num-ref>
|
| 391 |
+
may be communicated to and utilized by the application server machine <part-num-ref name="application server machine">12</part-num-ref>
|
| 392 |
+
to identify the appropriate multimedia content file <part-num-ref name="appropriate multimedia content file">92</part-num-ref>
|
| 393 |
+
in the database <part-num-ref name="database">26</part-num-ref>
|
| 394 |
+
and to initiate streaming of the multimedia content message <part-num-ref name="multimedia content message">60</part-num-ref>
|
| 395 |
+
contained by the multimedia content file <part-num-ref name="multimedia content file">92.</part-num-ref>
|
| 396 |
+
</p>
|
| 397 |
+
<p id="p-39" num="39">[0033] Figure 10 is a flow chart of a method <part-num-ref name="method">110,</part-num-ref>
|
| 398 |
+
used in an example embodiment of the present disclosure. Illustrated on the right is the client machine <part-num-ref name="client machine">14</part-num-ref>
|
| 399 |
+
(e.g., sending machine) and illustrated on the left is the client machine <part-num-ref name="client machine">16</part-num-ref>
|
| 400 |
+
(e.g., receiving machine). Illustrated on the center right is the application server machine <part-num-ref name="application server machine">12</part-num-ref>
|
| 401 |
+
and illustrated on the center left is the mail server machine <part-num-ref name="mail server machine">18.</part-num-ref>
|
| 402 |
+
The method <part-num-ref name="method">110</part-num-ref>
|
| 403 |
+
commences at operation <part-num-ref name="commences at operation">112</part-num-ref>
|
| 404 |
+
with the user, at the client machine <part-num-ref name="client machine">14,</part-num-ref>
|
| 405 |
+
selecting a compose button from a user interface to initiate composition a multimedia mail. In response, the multimedia mail module <part-num-ref name="multimedia mail module">44</part-num-ref>
|
| 406 |
+
may request the application server machine <part-num-ref name="application server machine">12</part-num-ref>
|
| 407 |
+
to establish a persistent connection between the client machine <part-num-ref name="client machine">14</part-num-ref>
|
| 408 |
+
and the application server machine <part-num-ref name="application server machine">12</part-num-ref>
|
| 409 |
+
and display a user interface at the client machine <part-num-ref name="client machine">14</part-num-ref>
|
| 410 |
+
that enables the user to compose the multimedia mail. </p>
|
| 411 |
+
<p id="p-40" num="40">[0034] At operation 114, at the application server machine <part-num-ref name="application server machine">12,</part-num-ref>
|
| 412 |
+
the receiving module <part-num-ref name="receiving module">22</part-num-ref>
|
| 413 |
+
receives the request and establishes the persistent connection. </p>
|
| 414 |
+
<p id="p-41" num="41">[0035<confidence value="5">]</confidence>
|
| 415 |
+
At operation 116, at the client machine <part-num-ref name="client machine">14,</part-num-ref>
|
| 416 |
+
the user selects a record button from the user interface to initiate communicating or streaming of the multimedia content message <part-num-ref name="multimedia content message">60.</part-num-ref>
|
| 417 |
+
For example, the client machine <part-num-ref name="client machine">14</part-num-ref>
|
| 418 |
+
may utilize the sound input device <part-num-ref name="sound input device">54</part-num-ref>
|
| 419 |
+
to record audio data that may be streamed over the persistent connection to the application server machine <part-num-ref name="application server machine">12</part-num-ref>
|
| 420 |
+
and the display input device <part-num-ref name="display input device">56</part-num-ref>
|
| 421 |
+
to <boundary-data type="header">
|
| 422 |
+
<confidence value="88">11</confidence>
|
| 423 |
+
</boundary-data>
|
| 424 |
+
<boundary-data type="header">Atty. Dkt. No. 2055.046US1 Recipient Ref. No.: B277</boundary-data>
|
| 425 |
+
<page-break num="12"/>
|
| 426 |
+
record video data <part-num-ref name="to record video data">64</part-num-ref>
|
| 427 |
+
that may be streamed over the persistent connection to the application server machine <part-num-ref name="application server machine">12.</part-num-ref>
|
| 428 |
+
The user may complete the communicating or streaming of the multimedia content message <part-num-ref name="multimedia content message">60</part-num-ref>
|
| 429 |
+
by selecting a stop button on the user interface. </p>
|
| 430 |
+
<p id="p-42" num="42">[0036<confidence value="5">]</confidence>
|
| 431 |
+
At operation 118, at the application server machine <part-num-ref name="application server machine">12,</part-num-ref>
|
| 432 |
+
the receiving module <part-num-ref name="receiving module">22</part-num-ref>
|
| 433 |
+
receives the multimedia content message <part-num-ref name="multimedia content message">60</part-num-ref>
|
| 434 |
+
that may include the audio and video data. For example, the receiving module <part-num-ref name="receiving module">22</part-num-ref>
|
| 435 |
+
may receive the streamed audio and video data. </p>
|
| 436 |
+
<p id="p-43" num="43">[0037<confidence value="5">]</confidence>
|
| 437 |
+
At operation 119, at the client machine <part-num-ref name="client machine">14,</part-num-ref>
|
| 438 |
+
the user enters the subject <part-num-ref name="subject">72</part-num-ref>
|
| 439 |
+
of the multimedia mail into an input box on a user interface and recipient network addresses <part-num-ref name="user interface and recipient network addresses">82</part-num-ref>
|
| 440 |
+
into an input box on a user interface. Next, the user may to cause the client machine <part-num-ref name="client machine">14</part-num-ref>
|
| 441 |
+
to generate a multimedia metadata message <part-num-ref name="multimedia metadata message">69</part-num-ref>
|
| 442 |
+
and a recipient list <part-num-ref name="recipient list">80</part-num-ref>
|
| 443 |
+
and to communicate the multimedia metadata message <part-num-ref name="multimedia metadata message">69</part-num-ref>
|
| 444 |
+
and the recipient list <part-num-ref name="recipient list">80</part-num-ref>
|
| 445 |
+
to the application server machine <part-num-ref name="application server machine">12</part-num-ref>
|
| 446 |
+
(e.g., by selecting a send button on the user interface). </p>
|
| 447 |
+
<p id="p-44" num="44">[0038<confidence value="5">]</confidence>
|
| 448 |
+
At operation 120, at the application server machine <part-num-ref name="application server machine">12,</part-num-ref>
|
| 449 |
+
the receiving module <part-num-ref name="receiving module">22</part-num-ref>
|
| 450 |
+
receives the recipient list <part-num-ref name="recipient list">80</part-num-ref>
|
| 451 |
+
and the multimedia metadata message <part-num-ref name="multimedia metadata message">68.</part-num-ref>
|
| 452 |
+
</p>
|
| 453 |
+
<p id="p-45" num="45">[0039] At operation 122, the multimedia module <part-num-ref name="multimedia module">24</part-num-ref>
|
| 454 |
+
stores the multimedia file <part-num-ref name="multimedia file">91</part-num-ref>
|
| 455 |
+
in the multimedia table <part-num-ref name="multimedia table">28.</part-num-ref>
|
| 456 |
+
For example, the multimedia module <part-num-ref name="multimedia module">24</part-num-ref>
|
| 457 |
+
may store the multimedia content message <part-num-ref name="multimedia content message">60</part-num-ref>
|
| 458 |
+
(e.g., stream) as the multimedia content file <part-num-ref name="multimedia content file">92</part-num-ref>
|
| 459 |
+
in the multimedia table <part-num-ref name="multimedia table">28</part-num-ref>
|
| 460 |
+
and the multimedia metadata message <part-num-ref name="multimedia metadata message">68</part-num-ref>
|
| 461 |
+
as the multimedia metadata file <part-num-ref name="multimedia metadata file">93</part-num-ref>
|
| 462 |
+
in the multimedia table <part-num-ref name="multimedia table">2<confidence value="5">8</confidence>
|
| 463 |
+
. </part-num-ref>
|
| 464 |
+
The multimedia module <part-num-ref name="multimedia module">24</part-num-ref>
|
| 465 |
+
may store the multimedia file <part-num-ref name="multimedia file">91</part-num-ref>
|
| 466 |
+
in an inbox <part-num-ref name="inbox">90</part-num-ref>
|
| 467 |
+
in the multimedia table <part-num-ref name="multimedia table">28</part-num-ref>
|
| 468 |
+
that corresponds to a recipient network address <part-num-ref name="recipient network address">82</part-num-ref>
|
| 469 |
+
in the recipient list <part-num-ref name="recipient list">80.</part-num-ref>
|
| 470 |
+
The multimedia module <part-num-ref name="multimedia module">24</part-num-ref>
|
| 471 |
+
may store multiple copies of the multimedia file <part-num-ref name="multimedia file">91</part-num-ref>
|
| 472 |
+
in multiple corresponding inboxes <part-num-ref name="in multiple corresponding inboxes">90</part-num-ref>
|
| 473 |
+
based on multiple recipient network addresses <part-num-ref name="based on multiple recipient network addresses">82</part-num-ref>
|
| 474 |
+
in the recipient list. </p>
|
| 475 |
+
<p id="p-46" num="46">
|
| 476 |
+
<confidence value="5">[</confidence>
|
| 477 |
+
0040] At operation 124, the multimedia module <part-num-ref name="multimedia module">24</part-num-ref>
|
| 478 |
+
generates a multimedia retrieval message <part-num-ref name="multimedia retrieval message">94</part-num-ref>
|
| 479 |
+
that respectively include multimedia retrieval information <part-num-ref name="that respectively include multimedia retrieval information">95</part-num-ref>
|
| 480 |
+
(e.g., XML content) for each recipient network address <part-num-ref name="XML content) for each recipient network address">82</part-num-ref>
|
| 481 |
+
in the recipient list <part-num-ref name="recipient list">80.</part-num-ref>
|
| 482 |
+
</p>
|
| 483 |
+
<p id="p-47" num="47">Each of the multimedia retrieval messages <part-num-ref name="multimedia retrieval messages">94</part-num-ref>
|
| 484 |
+
includes a multimedia message <boundary-data type="header">
|
| 485 |
+
<confidence value="88">12</confidence>
|
| 486 |
+
</boundary-data>
|
| 487 |
+
<boundary-data type="header">Atty. Dkt. No. 2055.046US1 Recipient Ref. No.: B277</boundary-data>
|
| 488 |
+
<page-break num="13"/>
|
| 489 |
+
identifier (e.g., stream identifier). Further, in one embodiment, the multimedia module <part-num-ref name="multimedia module">24</part-num-ref>
|
| 490 |
+
may generate and insert the timestamp <part-num-ref name="timestamp">73</part-num-ref>
|
| 491 |
+
into the multimedia retrieval message <part-num-ref name="multimedia retrieval message">94.</part-num-ref>
|
| 492 |
+
</p>
|
| 493 |
+
<p id="p-48" num="48">[0041] At operation 126, the multimedia module <part-num-ref name="multimedia module">24</part-num-ref>
|
| 494 |
+
communicates the multimedia retrieval messages <part-num-ref name="multimedia retrieval messages">94</part-num-ref>
|
| 495 |
+
to a mailbox that may be identified with the recipient network address <part-num-ref name="recipient network address">82.</part-num-ref>
|
| 496 |
+
For example, the recipient network address <part-num-ref name="recipient network address">82</part-num-ref>
|
| 497 |
+
may identify a mail server machine <part-num-ref name="mail server machine">18</part-num-ref>
|
| 498 |
+
on the network <part-num-ref name="network">20</part-num-ref>
|
| 499 |
+
and a specific mailbox on the mail server machine <part-num-ref name="mail server machine">18</part-num-ref>
|
| 500 |
+
that may be used to temporarily store a multimedia retrieval message <part-num-ref name="multimedia retrieval message">94</part-num-ref>
|
| 501 |
+
for a receiving machine (e.g., client machines 16). It will further be appreciated that the mailbox at the mail server machine <part-num-ref name="mail server machine">18</part-num-ref>
|
| 502 |
+
may also be utilized to store an email for the same receiving machine (e.g., client machine 16). </p>
|
| 503 |
+
<p id="p-49" num="49">[0042] At operation 128, the mail server machine <part-num-ref name="mail server machine">18</part-num-ref>
|
| 504 |
+
receives and stores the multimedia retrieval message <part-num-ref name="multimedia retrieval message">94</part-num-ref>
|
| 505 |
+
in a mailbox corresponding to the identified recipient network address <part-num-ref name="identified recipient network address">82</part-num-ref>
|
| 506 |
+
in the multimedia retrieval message <part-num-ref name="multimedia retrieval message">94.</part-num-ref>
|
| 507 |
+
</p>
|
| 508 |
+
<p id="p-50" num="50">[0043] At operation 130, the receiving machine (e.g., client machine <part-num-ref name="client machine">16)</part-num-ref>
|
| 509 |
+
communicates a request to retrieve email and multimedia retrieval messages <part-num-ref name="request to retrieve email and multimedia retrieval messages">94</part-num-ref>
|
| 510 |
+
from the mail server machine <part-num-ref name="mail server machine">18.</part-num-ref>
|
| 511 |
+
For example, in one example embodiment, the client machine <part-num-ref name="client machine">16</part-num-ref>
|
| 512 |
+
may utilize the POP3 protocol to request the email and the multimedia retrieval messages <part-num-ref name="multimedia retrieval messages">94</part-num-ref>
|
| 513 |
+
from the appropriate mailbox at mail server machine <part-num-ref name="appropriate mailbox at mail server machine">18.</part-num-ref>
|
| 514 |
+
</p>
|
| 515 |
+
<p id="p-51" num="51">
|
| 516 |
+
<confidence value="5">[</confidence>
|
| 517 |
+
0044<confidence value="5">]</confidence>
|
| 518 |
+
At operation 132, the mail server machine <part-num-ref name="mail server machine">18</part-num-ref>
|
| 519 |
+
may receive the request to retrieve email and multimedia retrieval messages <part-num-ref name="request to retrieve email and multimedia retrieval messages">94</part-num-ref>
|
| 520 |
+
from the receiving machine. </p>
|
| 521 |
+
<p id="p-52" num="52">For example, the user operating the receiving machine (e.g., client machine <part-num-ref name="client machine">16)</part-num-ref>
|
| 522 |
+
may retrieve email and multimedia retrieval messages <part-num-ref name="may retrieve email and multimedia retrieval messages">94</part-num-ref>
|
| 523 |
+
that may be addressed to the user. In one example embodiment the user may identify his or herself to the multimedia mail module <part-num-ref name="multimedia mail module">44</part-num-ref>
|
| 524 |
+
by providing a user name and password to the multimedia mail module <part-num-ref name="multimedia mail module">44</part-num-ref>
|
| 525 |
+
that may restrict access to email and multimedia retrieval messages <part-num-ref name="that may restrict access to email and multimedia retrieval messages">94</part-num-ref>
|
| 526 |
+
addressed to the user corresponding to the user name and password. </p>
|
| 527 |
+
<p id="p-53" num="53">[0045<confidence value="4">]</confidence>
|
| 528 |
+
At operation 134, the mail server machine <part-num-ref name="mail server machine">18</part-num-ref>
|
| 529 |
+
may communicate the email and the multimedia retrieval messages <part-num-ref name="multimedia retrieval messages">94</part-num-ref>
|
| 530 |
+
to the receiving machine (e.g., <boundary-data type="header">
|
| 531 |
+
<confidence value="88">13</confidence>
|
| 532 |
+
</boundary-data>
|
| 533 |
+
<boundary-data type="header">Atty. Dkt. No. 2055.046US1 Recipient Ref. No.: B277</boundary-data>
|
| 534 |
+
<page-break num="14"/>
|
| 535 |
+
client machine <part-num-ref name="client machine">16)</part-num-ref>
|
| 536 |
+
based on the request to retrieve email and multimedia retrieval messages <part-num-ref name="request to retrieve email and multimedia retrieval messages">94.</part-num-ref>
|
| 537 |
+
</p>
|
| 538 |
+
<p id="p-54" num="54">[0046] At operation 136, the client machine <part-num-ref name="client machine">16</part-num-ref>
|
| 539 |
+
may receive the messages, scan the messages and move the messages. For example, the client machine <part-num-ref name="client machine">16</part-num-ref>
|
| 540 |
+
may receive the email and multimedia retrieval messages <part-num-ref name="email and multimedia retrieval messages">94</part-num-ref>
|
| 541 |
+
from the mail server machine <part-num-ref name="mail server machine">18,</part-num-ref>
|
| 542 |
+
scans the email and multimedia retrieval messages <part-num-ref name="email and multimedia retrieval messages">94,</part-num-ref>
|
| 543 |
+
and move the email to the local email inbox <part-num-ref name="local email inbox">47</part-num-ref>
|
| 544 |
+
and the multimedia retrieval messages <part-num-ref name="multimedia retrieval messages">94</part-num-ref>
|
| 545 |
+
to local multimedia inbox <part-num-ref name="to local multimedia inbox">45.</part-num-ref>
|
| 546 |
+
In one embodiment, the multimedia mail module <part-num-ref name="multimedia mail module">44</part-num-ref>
|
| 547 |
+
(e.g., standalone and plug-in version) may be utilized, for example, to process the multimedia retrieval information <part-num-ref name="multimedia retrieval information">95</part-num-ref>
|
| 548 |
+
(e.g., XML content) in the multimedia retrieval message <part-num-ref name="multimedia retrieval message">94.</part-num-ref>
|
| 549 |
+
</p>
|
| 550 |
+
<p id="p-55" num="55">[0047] At operation 137, at the client machine <part-num-ref name="client machine">16,</part-num-ref>
|
| 551 |
+
the user operating the client machine <part-num-ref name="client machine">16</part-num-ref>
|
| 552 |
+
may examine the incoming email and the incoming multimedia retrieval messages <part-num-ref name="incoming multimedia retrieval messages">94.</part-num-ref>
|
| 553 |
+
For example, the user may utilize a user interface to display the multimedia retrieval messages <part-num-ref name="multimedia retrieval messages">94.</part-num-ref>
|
| 554 |
+
In addition, the user may select a particular multimedia retrieval message <part-num-ref name="particular multimedia retrieval message">94</part-num-ref>
|
| 555 |
+
from the user interface. </p>
|
| 556 |
+
<p id="p-56" num="56">
|
| 557 |
+
<confidence value="5">[</confidence>
|
| 558 |
+
0048<confidence value="5">]</confidence>
|
| 559 |
+
At operation 138, the client machine <part-num-ref name="client machine">16</part-num-ref>
|
| 560 |
+
may respond to the selection of the particular multimedia retrieval message <part-num-ref name="particular multimedia retrieval message">94</part-num-ref>
|
| 561 |
+
by utilizing the multimedia content message identifier <part-num-ref name="multimedia content message identifier">96</part-num-ref>
|
| 562 |
+
included in the selected multimedia retrieval message <part-num-ref name="selected multimedia retrieval message">94</part-num-ref>
|
| 563 |
+
to identif<confidence value="8">y</confidence>
|
| 564 |
+
the appropriate application server machine <part-num-ref name="appropriate application server machine">12</part-num-ref>
|
| 565 |
+
and to request the application server machine <part-num-ref name="application server machine">12</part-num-ref>
|
| 566 |
+
to establish a persistent connection between the application server machine <part-num-ref name="application server machine">12</part-num-ref>
|
| 567 |
+
and the client machine <part-num-ref name="client machine">16.</part-num-ref>
|
| 568 |
+
For example, the client machine <part-num-ref name="client machine">16</part-num-ref>
|
| 569 |
+
may identify the appropriate application server machine <part-num-ref name="appropriate application server machine">12</part-num-ref>
|
| 570 |
+
on the network <part-num-ref name="network">20</part-num-ref>
|
| 571 |
+
based on the application server network address <part-num-ref name="application server network address">100</part-num-ref>
|
| 572 |
+
in the multimedia content message identifier <part-num-ref name="multimedia content message identifier">96</part-num-ref>
|
| 573 |
+
in the multimedia retrieval message <part-num-ref name="multimedia retrieval message">94.</part-num-ref>
|
| 574 |
+
In addition, the client machine <part-num-ref name="client machine">16</part-num-ref>
|
| 575 |
+
may respond to the selection of the particular multimedia retrieval message by displaying a user interface on the display output device <part-num-ref name="display output device">52</part-num-ref>
|
| 576 |
+
that may enable the user to play the associated multimedia content message <part-num-ref name="associated multimedia content message">60.</part-num-ref>
|
| 577 |
+
</p>
|
| 578 |
+
<p id="p-57" num="57">[0049<confidence value="4">]</confidence>
|
| 579 |
+
At operation 140, the application server machine <part-num-ref name="application server machine">12</part-num-ref>
|
| 580 |
+
may receive the request to establish a persistent connection and accordingly establish a persistent <boundary-data type="header">
|
| 581 |
+
<confidence value="88">14</confidence>
|
| 582 |
+
</boundary-data>
|
| 583 |
+
<boundary-data type="header">Atty. Dkt. No. 2055.046US1 Recipient Ref. No.: B277</boundary-data>
|
| 584 |
+
<page-break num="15"/>
|
| 585 |
+
connection between the receiving machine (e.g., client machine <part-num-ref name="client machine">16)</part-num-ref>
|
| 586 |
+
and the application server machine <part-num-ref name="application server machine">12.</part-num-ref>
|
| 587 |
+
</p>
|
| 588 |
+
<p id="p-58" num="58">[0050] At operation 142, the user may initiate streaming of the multimedia content message <part-num-ref name="multimedia content message">60</part-num-ref>
|
| 589 |
+
(e.g., for example by selecting a play button). </p>
|
| 590 |
+
<p id="p-59" num="59">
|
| 591 |
+
<confidence value="5">[</confidence>
|
| 592 |
+
0051<confidence value="4">]</confidence>
|
| 593 |
+
At operation 144, the multimedia mail module <part-num-ref name="multimedia mail module">44</part-num-ref>
|
| 594 |
+
may request streaming of the multimedia content message <part-num-ref name="multimedia content message">60</part-num-ref>
|
| 595 |
+
from the application server machine <part-num-ref name="application server machine">12.</part-num-ref>
|
| 596 |
+
For example, the multimedia mail module <part-num-ref name="multimedia mail module">44</part-num-ref>
|
| 597 |
+
may communicate the stream name <part-num-ref name="stream name">74</part-num-ref>
|
| 598 |
+
in the multimedia content message identifier <part-num-ref name="multimedia content message identifier">96</part-num-ref>
|
| 599 |
+
in the multimedia retrieval message <part-num-ref name="multimedia retrieval message">94</part-num-ref>
|
| 600 |
+
to the identified application server machine <part-num-ref name="identified application server machine">12.</part-num-ref>
|
| 601 |
+
</p>
|
| 602 |
+
<p id="p-60" num="60">[0052<confidence value="5">]</confidence>
|
| 603 |
+
At operation 146, at the application server machine <part-num-ref name="application server machine">12,</part-num-ref>
|
| 604 |
+
the receiving module <part-num-ref name="receiving module">22</part-num-ref>
|
| 605 |
+
may receive the request to initiate streaming of the identified multimedia content file <part-num-ref name="identified multimedia content file">92.</part-num-ref>
|
| 606 |
+
For example, the multimedia content file <part-num-ref name="multimedia content file">92</part-num-ref>
|
| 607 |
+
may be identified based on the received stream name <part-num-ref name="received stream name">74.</part-num-ref>
|
| 608 |
+
</p>
|
| 609 |
+
<p id="p-61" num="61">[0053<confidence value="5">]</confidence>
|
| 610 |
+
At operation 148, the multimedia module <part-num-ref name="multimedia module">24</part-num-ref>
|
| 611 |
+
at the application server machine <part-num-ref name="application server machine">12</part-num-ref>
|
| 612 |
+
reads the multimedia content file <part-num-ref name="multimedia content file">92</part-num-ref>
|
| 613 |
+
corresponding to the received stream name <part-num-ref name="received stream name">74</part-num-ref>
|
| 614 |
+
and streams or communicates the multimedia content message <part-num-ref name="multimedia content message">60</part-num-ref>
|
| 615 |
+
based on the contents of the multimedia content file <part-num-ref name="multimedia content file">92.</part-num-ref>
|
| 616 |
+
</p>
|
| 617 |
+
<p id="p-62" num="62">[0054<confidence value="5">]</confidence>
|
| 618 |
+
At operation 150, the receiving machine (e.g., client machine 16), receives the multimedia content message <part-num-ref name="multimedia content message">60</part-num-ref>
|
| 619 |
+
and plays (or otherwise presents) the multimedia content message <part-num-ref name="multimedia content message">60</part-num-ref>
|
| 620 |
+
on the output device <part-num-ref name="output device">48.</part-num-ref>
|
| 621 |
+
For example, the client machine <part-num-ref name="client machine">16</part-num-ref>
|
| 622 |
+
may receive the stream of the multimedia content message <part-num-ref name="multimedia content message">60</part-num-ref>
|
| 623 |
+
and play out the stream on the sound output device <part-num-ref name="sound output device">50</part-num-ref>
|
| 624 |
+
and the display output device <part-num-ref name="display output device">52.</part-num-ref>
|
| 625 |
+
</p>
|
| 626 |
+
<p id="p-63" num="63">
|
| 627 |
+
<confidence value="5">[</confidence>
|
| 628 |
+
0055] Figure 11 is a representation of a user interface <part-num-ref name="user interface">160</part-num-ref>
|
| 629 |
+
used in an example embodiment of the present disclosure, to compose multimedia mail. The user interface <part-num-ref name="user interface">160</part-num-ref>
|
| 630 |
+
may be utilized by the plug-in version of the multimedia mail module <part-num-ref name="multimedia mail module">44</part-num-ref>
|
| 631 |
+
and is shown to include an input boxes <part-num-ref name="input boxes">162,</part-num-ref>
|
| 632 |
+
<part-num-ref name="input boxes 162,">164,</part-num-ref>
|
| 633 |
+
an inbox button <part-num-ref name="inbox button">166,</part-num-ref>
|
| 634 |
+
a compose button <part-num-ref name="compose button">170,</part-num-ref>
|
| 635 |
+
an address book button <part-num-ref name="address book button">172,</part-num-ref>
|
| 636 |
+
a settings button <part-num-ref name="settings button">178,</part-num-ref>
|
| 637 |
+
a calendar button <part-num-ref name="calendar button">180,</part-num-ref>
|
| 638 |
+
a help button <part-num-ref name="help button">182,</part-num-ref>
|
| 639 |
+
a record button <part-num-ref name="record button">183,</part-num-ref>
|
| 640 |
+
a send button <part-num-ref name="send button">184,</part-num-ref>
|
| 641 |
+
a stop button <part-num-ref name="stop button">186</part-num-ref>
|
| 642 |
+
and a reset button <part-num-ref name="reset button">188.</part-num-ref>
|
| 643 |
+
The user interface <part-num-ref name="user interface">160</part-num-ref>
|
| 644 |
+
may be displayed on the display output device <part-num-ref name="display output device">52</part-num-ref>
|
| 645 |
+
in response to selection of the compose button <part-num-ref name="compose button">170.</part-num-ref>
|
| 646 |
+
</p>
|
| 647 |
+
<boundary-data type="header">
|
| 648 |
+
<confidence value="88">15</confidence>
|
| 649 |
+
</boundary-data>
|
| 650 |
+
<boundary-data type="header">Atty. Dkt. No. 2055.046US1 Recipient Ref. No.: B277</boundary-data>
|
| 651 |
+
<p id="p-64" num="64">
|
| 652 |
+
<page-break num="16"/>
|
| 653 |
+
<confidence value="5">[</confidence>
|
| 654 |
+
0056] The input box <part-num-ref name="input box">162</part-num-ref>
|
| 655 |
+
may be utilized by the user to enter one or more recipient network addresses <part-num-ref name="user to enter one or more recipient network addresses">82.</part-num-ref>
|
| 656 |
+
For example, the input box <part-num-ref name="input box">162</part-num-ref>
|
| 657 |
+
is shown to contain an example recipient network address <part-num-ref name="example recipient network address">82</part-num-ref>
|
| 658 |
+
"joe@abc.com" that may have been entered by the user. The input box <part-num-ref name="input box">164</part-num-ref>
|
| 659 |
+
may be used by the user to enter the subject of a multimedia mail. For example, the input box <part-num-ref name="input box">164</part-num-ref>
|
| 660 |
+
is shown to contain a subject "Multimedia Mail" that may have been entered by the user. </p>
|
| 661 |
+
<p id="p-65" num="65">[0057] The inbox box button <part-num-ref name="inbox box button">166</part-num-ref>
|
| 662 |
+
may be selected to display a user interface on the display output device <part-num-ref name="display output device">52</part-num-ref>
|
| 663 |
+
that presents multimedia mail (e.g., multimedia retrieval message <part-num-ref name="multimedia retrieval message">94)</part-num-ref>
|
| 664 |
+
and email that have been retrieved by the client machine <part-num-ref name="client machine">16</part-num-ref>
|
| 665 |
+
from the mail server machine <part-num-ref name="mail server machine">18.</part-num-ref>
|
| 666 |
+
The compose button <part-num-ref name="compose button">170</part-num-ref>
|
| 667 |
+
may be selected to display a user interface to compose a multimedia mail. In addition, selection of the compose button <part-num-ref name="compose button">170</part-num-ref>
|
| 668 |
+
may cause the client machine <part-num-ref name="client machine">14</part-num-ref>
|
| 669 |
+
to request the application server machine <part-num-ref name="application server machine">12</part-num-ref>
|
| 670 |
+
to establish a persistent connection between the client machine <part-num-ref name="client machine">14</part-num-ref>
|
| 671 |
+
and the application server machine <part-num-ref name="application server machine">12.</part-num-ref>
|
| 672 |
+
The persistent connection may be utilized by the client machine <part-num-ref name="client machine">14</part-num-ref>
|
| 673 |
+
to stream video data <part-num-ref name="to stream video data">64</part-num-ref>
|
| 674 |
+
and audio data <part-num-ref name="and audio data">66</part-num-ref>
|
| 675 |
+
to the application server machine <part-num-ref name="application server machine">12.</part-num-ref>
|
| 676 |
+
The address book button <part-num-ref name="address book button">172</part-num-ref>
|
| 677 |
+
may be selected to display a user interface that presents names, addresses, telephone numbers, fax numbers and email addresses for users and organizations. The settings button <part-num-ref name="settings button">178</part-num-ref>
|
| 678 |
+
may be utilized to display a user interface to configure multimedia mail parameters utilized by the multimedia mail module <part-num-ref name="multimedia mail module">44.</part-num-ref>
|
| 679 |
+
For example, the user interface may enable configuration of multimedia mail parameters including host names that communicate with the multimedia mail module <part-num-ref name="multimedia mail module">44,</part-num-ref>
|
| 680 |
+
port numbers, communication protocols, etc. The calendar button <part-num-ref name="calendar button">180</part-num-ref>
|
| 681 |
+
may be utilized to display a user interface that may enable viewing and configuring a calendar. The help button <part-num-ref name="help button">182</part-num-ref>
|
| 682 |
+
may be utilized to retrieve help information regarding the multimedia mail feature. </p>
|
| 683 |
+
<p id="p-66" num="66">
|
| 684 |
+
<confidence value="5">[</confidence>
|
| 685 |
+
0058] The record button <part-num-ref name="record button">183</part-num-ref>
|
| 686 |
+
may be utilized to start communicating or streaming the multimedia content message <part-num-ref name="multimedia content message">60</part-num-ref>
|
| 687 |
+
that may include the video data <part-num-ref name="video data">64</part-num-ref>
|
| 688 |
+
and the audio data <part-num-ref name="audio data">66.</part-num-ref>
|
| 689 |
+
For example, the multimedia content message <part-num-ref name="multimedia content message">60</part-num-ref>
|
| 690 |
+
may be communicated or streamed from the input device <part-num-ref name="input device">46</part-num-ref>
|
| 691 |
+
at the client machine <part-num-ref name="client machine">14</part-num-ref>
|
| 692 |
+
to the application server machine <part-num-ref name="application server machine">12.</part-num-ref>
|
| 693 |
+
The stop button <part-num-ref name="stop button">186</part-num-ref>
|
| 694 |
+
may be utilized to stop streaming or communicating the multimedia content message <part-num-ref name="multimedia content message">60.</part-num-ref>
|
| 695 |
+
The reset button <boundary-data type="header">
|
| 696 |
+
<confidence value="88">16</confidence>
|
| 697 |
+
</boundary-data>
|
| 698 |
+
<boundary-data type="header">Atty. Dkt. No. 2055.046US1 Recipient Ref. No.: B277</boundary-data>
|
| 699 |
+
<page-break num="17"/>
|
| 700 |
+
<part-num-ref name="reset button">188</part-num-ref>
|
| 701 |
+
may be utilized to restart streaming or communication of the multimedia content message <part-num-ref name="multimedia content message">60</part-num-ref>
|
| 702 |
+
to the application server machine <part-num-ref name="application server machine">12</part-num-ref>
|
| 703 |
+
thereby causing deletion of the previously communicated or streamed multimedia content message <part-num-ref name="previously communicated or streamed multimedia content message">60</part-num-ref>
|
| 704 |
+
at the application server machine <part-num-ref name="application server machine">12.</part-num-ref>
|
| 705 |
+
The send button <part-num-ref name="send button">184</part-num-ref>
|
| 706 |
+
may be utilized to communicate the recipient list <part-num-ref name="recipient list">80</part-num-ref>
|
| 707 |
+
and the multimedia metadata message <part-num-ref name="multimedia metadata message">68</part-num-ref>
|
| 708 |
+
from the client machine <part-num-ref name="client machine">14</part-num-ref>
|
| 709 |
+
to the application server machine <part-num-ref name="application server machine">12</part-num-ref>
|
| 710 |
+
thereby triggering the application server machine <part-num-ref name="application server machine">12</part-num-ref>
|
| 711 |
+
to generate and communicate multimedia retrieval messages for each named recipient network addresses <part-num-ref name="to generate and communicate multimedia retrieval messages for each named recipient network addresses">82</part-num-ref>
|
| 712 |
+
in the recipient list <part-num-ref name="recipient list">80.</part-num-ref>
|
| 713 |
+
</p>
|
| 714 |
+
<p id="p-67" num="67">
|
| 715 |
+
<confidence value="5">[</confidence>
|
| 716 |
+
0059] Another embodiment of the above described user interface <part-num-ref name="above described user interface">160</part-num-ref>
|
| 717 |
+
may be utilized by the stand-alone version of the multimedia mail module <part-num-ref name="multimedia mail module">44.</part-num-ref>
|
| 718 |
+
The stand- alone version of the user interface <part-num-ref name="user interface">160</part-num-ref>
|
| 719 |
+
may further include an outbox button that may be utilized to display multimedia mail and email that have not yet been communicated from the client machine <part-num-ref name="client machine">16</part-num-ref>
|
| 720 |
+
to the application server machine <part-num-ref name="application server machine">12</part-num-ref>
|
| 721 |
+
and an outbox send button that may be utilized to communicate the recipient lists <part-num-ref name="recipient lists">80,</part-num-ref>
|
| 722 |
+
corresponding multimedia metadata message <part-num-ref name="recipient lists 80, corresponding multimedia metadata message">68,</part-num-ref>
|
| 723 |
+
and emails that may be in the outbox of the client machine <part-num-ref name="client machine">14.</part-num-ref>
|
| 724 |
+
Further, the compose button <part-num-ref name="compose button">170</part-num-ref>
|
| 725 |
+
may operate differently from the plug-in version by further requesting the user to specify whether the user intends to compose email or multimedia mail. </p>
|
| 726 |
+
<p id="p-68" num="68">
|
| 727 |
+
<confidence value="5">[</confidence>
|
| 728 |
+
0060] Figure 12 is a representation of a user interface <part-num-ref name="user interface">200</part-num-ref>
|
| 729 |
+
using an example embodiment of the present disclosure, to display multimedia retrieval messages. The user interface <part-num-ref name="user interface">200</part-num-ref>
|
| 730 |
+
is shown to display multiple multimedia retrieval messages <part-num-ref name="is shown to display multiple multimedia retrieval messages">94</part-num-ref>
|
| 731 |
+
that may have been retrieved from the mail server machine <part-num-ref name="mail server machine">18</part-num-ref>
|
| 732 |
+
by the receiving machine (e.g., client machine <part-num-ref name="client machine">14)</part-num-ref>
|
| 733 |
+
and stored in the local multimedia inbox <part-num-ref name="local multimedia inbox">45.</part-num-ref>
|
| 734 |
+
Each multimedia retrieval messages <part-num-ref name="local multimedia inbox 45. Each multimedia retrieval messages">94</part-num-ref>
|
| 735 |
+
is shown to include a sender network address <part-num-ref name="sender network address">70,</part-num-ref>
|
| 736 |
+
a subject <part-num-ref name="subject">72,</part-num-ref>
|
| 737 |
+
and a date <part-num-ref name="date">202.</part-num-ref>
|
| 738 |
+
In one example embodiment, the date <part-num-ref name="date">202</part-num-ref>
|
| 739 |
+
may be the date on which the multimedia content message <part-num-ref name="multimedia content message">60</part-num-ref>
|
| 740 |
+
may have been streamed or communicated to application serve machine <part-num-ref name="may have been streamed or communicated to application serve machine">12.</part-num-ref>
|
| 741 |
+
The user at the receiving machine (e.g., client machine) may select a specific multimedia retrieval message <part-num-ref name="specific multimedia retrieval message">94</part-num-ref>
|
| 742 |
+
(e.g., Subject: Multimedia Mail) from the user interface <part-num-ref name="user interface">200</part-num-ref>
|
| 743 |
+
to cause the client machine <part-num-ref name="client machine">14</part-num-ref>
|
| 744 |
+
to request the appropriate application server machine <part-num-ref name="appropriate application server machine">12</part-num-ref>
|
| 745 |
+
to establish a persistent connection between the receiving machine (e.g., client <boundary-data type="header">
|
| 746 |
+
<confidence value="88">17</confidence>
|
| 747 |
+
</boundary-data>
|
| 748 |
+
<boundary-data type="header">Atty. Dkt. No. 2055.046<confidence value="68">US</confidence>
|
| 749 |
+
1 Recipient Ref. No.: B277 </boundary-data>
|
| 750 |
+
<page-break num="18"/>
|
| 751 |
+
machine <part-num-ref name="client machine">16)</part-num-ref>
|
| 752 |
+
and the application server machine <part-num-ref name="application server machine">12</part-num-ref>
|
| 753 |
+
in preparation of streaming or communicating the corresponding multimedia content message <part-num-ref name="corresponding multimedia content message">60</part-num-ref>
|
| 754 |
+
to the receiving machine. In addition, selection of the specific multimedia retrieval message <part-num-ref name="specific multimedia retrieval message">94</part-num-ref>
|
| 755 |
+
may result in displaying a user interface on the display output device <part-num-ref name="display output device">52</part-num-ref>
|
| 756 |
+
at the receiving machine (e.g., client machine <part-num-ref name="client machine">16)</part-num-ref>
|
| 757 |
+
that may be utilized by the user to play the flash media mail (e.g., multimedia content message <part-num-ref name="multimedia content message">60)</part-num-ref>
|
| 758 |
+
associated with the selected multimedia retrieval message <part-num-ref name="selected multimedia retrieval message">94.</part-num-ref>
|
| 759 |
+
</p>
|
| 760 |
+
<p id="p-69" num="69">[0061<confidence value="2">]</confidence>
|
| 761 |
+
Figure 13 is a representation of a user interface <part-num-ref name="user interface">210</part-num-ref>
|
| 762 |
+
used in an example embodiment of the present disclosure, to play a multimedia mail (e.g., multimedia content file 92). The user interface <part-num-ref name="user interface">210</part-num-ref>
|
| 763 |
+
is shown to include a "From"" line <part-num-ref name=""From"" line">212,</part-num-ref>
|
| 764 |
+
a "Subject:" line <part-num-ref name=""Subject:" line">214,</part-num-ref>
|
| 765 |
+
a play button <part-num-ref name="play button">216,</part-num-ref>
|
| 766 |
+
a stop button <part-num-ref name="stop button">218,</part-num-ref>
|
| 767 |
+
a fast forward button <part-num-ref name="fast forward button">220</part-num-ref>
|
| 768 |
+
and a rewind button <part-num-ref name="rewind button">224.</part-num-ref>
|
| 769 |
+
The "From:" line <part-num-ref name=""From:" line">212</part-num-ref>
|
| 770 |
+
may be used to display the sender network address <part-num-ref name="sender network address">70.</part-num-ref>
|
| 771 |
+
For example, the sender network address <part-num-ref name="sender network address">70</part-num-ref>
|
| 772 |
+
may include the network address of the sending machine (e.g., client machine 14). The "Subject:" line <part-num-ref name=""Subject:" line">214</part-num-ref>
|
| 773 |
+
may include the subject <part-num-ref name="subject">72</part-num-ref>
|
| 774 |
+
as input by the user operating the sending machine (e.g., client machine 14). The play button <part-num-ref name="play button">216</part-num-ref>
|
| 775 |
+
may be utilized by the user operating the client machine <part-num-ref name="client machine">16</part-num-ref>
|
| 776 |
+
to play the multimedia mail. For example, in response to selection of the play button <part-num-ref name="play button">216,</part-num-ref>
|
| 777 |
+
the receiving machine (e.g., client machine <part-num-ref name="client machine">16)</part-num-ref>
|
| 778 |
+
may request the appropriate application server machine <part-num-ref name="appropriate application server machine">12</part-num-ref>
|
| 779 |
+
to begin streaming or communicating the multimedia content file <part-num-ref name="multimedia content file">92</part-num-ref>
|
| 780 |
+
to the output devices <part-num-ref name="output devices">48</part-num-ref>
|
| 781 |
+
including the sound output device <part-num-ref name="sound output device">50</part-num-ref>
|
| 782 |
+
and the display output device <part-num-ref name="display output device">52.</part-num-ref>
|
| 783 |
+
The stop button <part-num-ref name="stop button">218</part-num-ref>
|
| 784 |
+
may be utilized by the user to stop playing the multimedia content file <part-num-ref name="multimedia content file">92.</part-num-ref>
|
| 785 |
+
The fast forward button <part-num-ref name="fast forward button">220</part-num-ref>
|
| 786 |
+
may be utilized by the user to request the application server machine <part-num-ref name="application server machine">12</part-num-ref>
|
| 787 |
+
to fast forward the multimedia content file <part-num-ref name="multimedia content file">92</part-num-ref>
|
| 788 |
+
and the rewind button <part-num-ref name="rewind button">224</part-num-ref>
|
| 789 |
+
may be utilized by the user to request the application server machine <part-num-ref name="application server machine">12</part-num-ref>
|
| 790 |
+
to rewind the multimedia mail. </p>
|
| 791 |
+
<p id="p-70" num="70">[0062<confidence value="5">]</confidence>
|
| 792 |
+
Figure 14 is a representation of a user interface <part-num-ref name="user interface">230</part-num-ref>
|
| 793 |
+
used in an example embodiment of the present disclosure, to configure multimedia mail parameters. The user interface <part-num-ref name="user interface">230</part-num-ref>
|
| 794 |
+
is shown to include input boxes <part-num-ref name="is shown to include input boxes">232,</part-num-ref>
|
| 795 |
+
<part-num-ref name="is shown to include input boxes 232,">234,</part-num-ref>
|
| 796 |
+
<part-num-ref name="is shown to include input boxes 232, 234,">236,</part-num-ref>
|
| 797 |
+
<part-num-ref name="is shown to include input boxes 232, 234, 236,">238,</part-num-ref>
|
| 798 |
+
and <part-num-ref name="is shown to include input boxes 232, 234, 236, 238, and">240.</part-num-ref>
|
| 799 |
+
The input box <part-num-ref name="input box">232</part-num-ref>
|
| 800 |
+
may be used by the user to enter a user name and the input box <part-num-ref name="input box">234</part-num-ref>
|
| 801 |
+
may be used by the user to enter a password. The multimedia mail <boundary-data type="header">
|
| 802 |
+
<confidence value="88">18</confidence>
|
| 803 |
+
</boundary-data>
|
| 804 |
+
<boundary-data type="header">Atty. Dkt. No. 2055.046US1 Recipient Ref. No.: B277</boundary-data>
|
| 805 |
+
<page-break num="19"/>
|
| 806 |
+
module <part-num-ref name="multimedia mail module">44</part-num-ref>
|
| 807 |
+
may restrict access to the multimedia mail feature including multimedia mail unless a user provides the entered user name and password. The input box <part-num-ref name="input box">236</part-num-ref>
|
| 808 |
+
may be used to enter the POP3 host name. For example, the user may enter the name of the network address of the mail server machine <part-num-ref name="mail server machine">18.</part-num-ref>
|
| 809 |
+
The input box <part-num-ref name="input box">238</part-num-ref>
|
| 810 |
+
may be used enter the SMTP host name. For example, in the present embodiment, the user may enter the name of the mail server machine <part-num-ref name="mail server machine">18.</part-num-ref>
|
| 811 |
+
The input box <part-num-ref name="input box">240</part-num-ref>
|
| 812 |
+
may be used by the user to identify the multimedia server. For example, in the present embodiment, the user may enter the name of the application server machine <part-num-ref name="application server machine">12.</part-num-ref>
|
| 813 |
+
</p>
|
| 814 |
+
<p id="p-71" num="71">
|
| 815 |
+
<confidence value="5">[</confidence>
|
| 816 |
+
0063<confidence value="5">]</confidence>
|
| 817 |
+
Figure 15 shows a diagrammatic representation of machine in the example form of a computer system <part-num-ref name="computer system">1000</part-num-ref>
|
| 818 |
+
within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed. In alternative embodiments, the machine operates as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine may operate in the capacity of a server or a recipient in server-recipient network environment, or as a peer machine in a peer-to- peer (or distributed) network environment. The machine may be a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a cellular telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term "machine" shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein. </p>
|
| 819 |
+
<p id="p-72" num="72">[0064<confidence value="5">]</confidence>
|
| 820 |
+
The example computer system <part-num-ref name="example computer system">1000</part-num-ref>
|
| 821 |
+
includes a processor <part-num-ref name="processor">1002</part-num-ref>
|
| 822 |
+
(e.g., a central processing unit (CPU), a graphics processing unit (GPU) or both), a main memory <part-num-ref name="main memory">1004</part-num-ref>
|
| 823 |
+
and a static memory <part-num-ref name="static memory">1006,</part-num-ref>
|
| 824 |
+
which communicate with each other via a bus <part-num-ref name="bus">1008.</part-num-ref>
|
| 825 |
+
The computer system <part-num-ref name="computer system">1000</part-num-ref>
|
| 826 |
+
may further include a video display unit <part-num-ref name="video display unit">1010</part-num-ref>
|
| 827 |
+
(e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)). The computer system <part-num-ref name="computer system">1000</part-num-ref>
|
| 828 |
+
also includes an alphanumeric input device <part-num-ref name="alphanumeric input device">1012</part-num-ref>
|
| 829 |
+
(e.g., a keyboard), a user interface (UI) navigation device <part-num-ref name="user interface (UI) navigation device">1014</part-num-ref>
|
| 830 |
+
(e.g., a mouse or cursor control device), a <boundary-data type="header">
|
| 831 |
+
<confidence value="88">19</confidence>
|
| 832 |
+
</boundary-data>
|
| 833 |
+
<boundary-data type="header">Atty. Dkt. No. 2055.046US1 Recipient Ref. No.: B277</boundary-data>
|
| 834 |
+
<page-break num="20"/>
|
| 835 |
+
disk drive unit <part-num-ref name="disk drive unit">1016,</part-num-ref>
|
| 836 |
+
a signal generation device <part-num-ref name="signal generation device">1018</part-num-ref>
|
| 837 |
+
(e.g., a speaker) and a network interface device <part-num-ref name="network interface device">1020.</part-num-ref>
|
| 838 |
+
</p>
|
| 839 |
+
<p id="p-73" num="73">[0065<confidence value="5">]</confidence>
|
| 840 |
+
The disk drive unit <part-num-ref name="disk drive unit">1016</part-num-ref>
|
| 841 |
+
includes a machine-readable medium <part-num-ref name="machine-readable medium">1022</part-num-ref>
|
| 842 |
+
on which is stored one or more sets of instructions and data structures (e.g., software <part-num-ref name="software">1024)</part-num-ref>
|
| 843 |
+
embodying or utilized by any one or more of the methodologies or functions described herein. The software <part-num-ref name="software">1024</part-num-ref>
|
| 844 |
+
may also reside, completely or at least partially, within the main memory <part-num-ref name="main memory">1004</part-num-ref>
|
| 845 |
+
and/or within the processor <part-num-ref name="processor">1002</part-num-ref>
|
| 846 |
+
during execution thereof by the computer system <part-num-ref name="computer system">1000,</part-num-ref>
|
| 847 |
+
the main memory <part-num-ref name="main memory">1004</part-num-ref>
|
| 848 |
+
and the processor <part-num-ref name="processor">1002</part-num-ref>
|
| 849 |
+
also constituting machine-readable media. </p>
|
| 850 |
+
<p id="p-74" num="74">[00<confidence value="885">66]</confidence>
|
| 851 |
+
The software <part-num-ref name="software">1024</part-num-ref>
|
| 852 |
+
may further be transmitted or received over a network <part-num-ref name="network">1026</part-num-ref>
|
| 853 |
+
via the network interface device <part-num-ref name="network interface device">1020</part-num-ref>
|
| 854 |
+
utilizing any one of a number of well-known transfer protocols (e.g., HT<confidence value="5">T</confidence>
|
| 855 |
+
P). </p>
|
| 856 |
+
<p id="p-75" num="75">[0067<confidence value="5">]</confidence>
|
| 857 |
+
While the machine-readable medium <part-num-ref name="machine-readable medium">1022</part-num-ref>
|
| 858 |
+
is shown in an example embodiment to be a single medium, the term "machine-readable medium" should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term "machine-readable medium" shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the present invention, or that is capable of storing, encoding or carrying data structures utilized by or associated with such a set of instructions. The term "machine-readable medium" shall accordingly be taken to include, but not be limited to, solid-state memories, optical and magnetic media, and carrier wave signals. </p>
|
| 859 |
+
<p id="p-76" num="76">
|
| 860 |
+
<confidence value="5">[</confidence>
|
| 861 |
+
0068<confidence value="5">]</confidence>
|
| 862 |
+
Although an embodiment of the present invention has been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader spirit and scope of the invention. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. </p>
|
| 863 |
+
<boundary-data type="header">
|
| 864 |
+
<confidence value="88">20</confidence>
|
| 865 |
+
</boundary-data>
|
| 866 |
+
<boundary-data type="header">Atty. Dkt. No. 2055.046US1 Recipient Ref. No.: <confidence value="5">B</confidence>
|
| 867 |
+
277 </boundary-data>
|
| 868 |
+
</description>
|
| 869 |
+
</us-patent-application>
|
| 870 |
+
|
applicant/11505207.xml
ADDED
|
@@ -0,0 +1,366 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>11505207</doc-number>
|
| 8 |
+
<date>2006-08-16</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<heading id="h-1">UNITED STATES PATENT APPLICATION</heading>
|
| 14 |
+
<heading id="h-2">
|
| 15 |
+
<confidence value="88">OF</confidence>
|
| 16 |
+
</heading>
|
| 17 |
+
<p id="p-1" num="1">Frank J. Wroblewski </p>
|
| 18 |
+
<heading id="h-3">FOR</heading>
|
| 19 |
+
<heading id="h-4">HOVER-BUTTONS FOR USER INTERFACES</heading>
|
| 20 |
+
<boundary-data type="header">0320-08<confidence value="8">1</confidence>
|
| 21 |
+
</boundary-data>
|
| 22 |
+
<heading id="h-5">HOVER-BUTTONS FOR USER INTERFACES</heading>
|
| 23 |
+
<heading id="h-6">RELATED APPLICATION</heading>
|
| 24 |
+
<p id="p-2" num="2">
|
| 25 |
+
<page-break num="2"/>
|
| 26 |
+
[0001] This application is related to, and claims priority from, U.S. Provisional Patent Application Serial No. 60/708,851 filed on August 17, 2005, entitled "Hover- Buttons for a Zoomable Interface", the disclosure of which is incorporated here by reference. </p>
|
| 27 |
+
<heading id="h-7">BACKGROUND</heading>
|
| 28 |
+
<p id="p-3" num="3">[0002] This application describes, among other things, user interface objects as well as, systems and devices associated with user interfaces which employ such user interface objects.</p>
|
| 29 |
+
<p id="p-4" num="4">[0003] Technologies associated with the communication of information have evolved rapidly over the last several decades. Television, cellular telephony, the Internet and optical communication techniques (to name just a few things) combine to inundate consumers with available information and entertainment options. Taking television as an example, the last three decades have seen the introduction of cable television service, satellite television service, pay-per-view movies and video-on- demand. Whereas television viewers of the 1960s could typically receive perhaps four or five over-the-air TV channels on their television sets, today's TV watchers have the opportunity to select from hundreds, thousands, and potentially millions of channels of shows and information. Video-on-demand technology, currently used primarily in hotels <boundary-data type="header">-2-</boundary-data>
|
| 30 |
+
<page-break num="3"/>
|
| 31 |
+
<boundary-data type="header">0320-081</boundary-data>
|
| 32 |
+
and the like, provides the potential for in-home entertainment selection from among thousands of movie titles. </p>
|
| 33 |
+
<p id="p-5" num="5">[0004] The technological ability to provide so much information and content to end users provides both opportunities and challenges to system designers and service providers. One challenge is that while end users typically prefer having more choices rather than fewer, this preference is counterweighted by their desire that the selection process be both fast and simple. Unfortunately, the development of the systems and interfaces by which end users access media items has resulted in selection processes which are neither fast nor simple. Consider again the example of television programs.</p>
|
| 34 |
+
<p id="p-6" num="6">When television was in its infancy, determining which program to watch was a relatively simple process primarily due to the small number of choices. One would consult a printed guide which was formatted, for example, as series of columns and rows which showed the correspondence between <part-num-ref name="correspondence between">(1)</part-num-ref>
|
| 35 |
+
nearby television channels, <part-num-ref name="nearby television channels,">(2)</part-num-ref>
|
| 36 |
+
programs being transmitted on those channels and <part-num-ref name="programs being transmitted on those channels and">(3)</part-num-ref>
|
| 37 |
+
date and time. The television was tuned to the desired channel by adjusting a tuner knob and the viewer watched the selected program. Later, remote control devices were introduced that permitted viewers to tune the television from a distance. This addition to the user-television interface created the phenomenon known as "channel surfing" whereby a viewer could rapidly view short segments being broadcast on a number of channels to quickly learn what programs were available at any given time. </p>
|
| 38 |
+
<p id="p-7" num="7">[0005] Despite the fact that the number of channels and amount of viewable content has dramatically increased, the generally available user interface, control device <boundary-data type="header">-3-</boundary-data>
|
| 39 |
+
<page-break num="4"/>
|
| 40 |
+
<boundary-data type="header">0320-08<confidence value="8">1</confidence>
|
| 41 |
+
</boundary-data>
|
| 42 |
+
options and frameworks for televisions has not changed much over the last <part-num-ref name="last">30</part-num-ref>
|
| 43 |
+
years. </p>
|
| 44 |
+
<p id="p-8" num="8">Printed guides are still the most prevalent mechanism for conveying programming information. The multiple button remote control with up and down arrows is still the most prevalent channel/content selection mechanism. The reaction of those who design and implement the TV user interface to the increase in available media content has been a straightforward extension of the existing selection procedures and interface objects. Thus, the number of rows in the printed guides has been increased to accommodate more channels. The number of buttons on the remote control devices has been increased to support additional functionality and content handling, e.g., as shown in Figure 1. However, this approach has significantly increased both the time required for a viewer to review the available information and the complexity of actions required to implement a selection. Arguably, the cumbersome nature of the existing interface has hampered commercial implementation of some services, e.g., video-on- demand, since consumers are resistant to new services that will add complexity to an interface that they view as already too slow and complex.</p>
|
| 45 |
+
<p id="p-9" num="9">[0006] In addition to increases in bandwidth and content, the user interface bottleneck problem is being exacerbated by the aggregation of technologies.</p>
|
| 46 |
+
<p id="p-10" num="10">Consumers are reacting positively to having the option of buying integrated systems rather than a number of segregable components. An example of this trend is the combination televisionNCR/DVD in which three previously independent components are frequently sold today as an integrated unit. This trend is likely to continue, potentially with an end result that most if not all of the communication devices currently <boundary-data type="header">-4-</boundary-data>
|
| 47 |
+
<page-break num="5"/>
|
| 48 |
+
<boundary-data type="header">0320-08<confidence value="8">1</confidence>
|
| 49 |
+
</boundary-data>
|
| 50 |
+
found in the household will be packaged together as an integrated unit, e.g., a television<confidence value="5">N</confidence>
|
| 51 |
+
CR/DVD/internet access/radio/stereo unit. Even those who continue to buy separate components will likely desire seamless control of, and interworking between, the separate components. With this increased aggregation comes the potential for more complexity in the user interface. For example, when so-called "universal" remote units were introduced, e.g., to combine the functionality of TV remote units and VCR remote units, the number of buttons on these universal remote units was typically more than the number of buttons on either the TV remote unit or VCR remote unit individually. </p>
|
| 52 |
+
<p id="p-11" num="11">This added number of buttons and functionality makes it very difficult to control anything but the simplest aspects of a TV or VCR without hunting for exactly the right button on the remote. Many times, these universal remotes do not provide enough buttons to access many levels of control or features unique to certain TVs. In these cases, the original device remote unit is still needed, and the original hassle of handling multiple remotes remains due to user interface issues arising from the complexity of aggregation. Some remote units have addressed this problem by adding "soft" buttons that can be programmed with the expert commands. These soft buttons sometimes have accompanying LCD displays to indicate their action. These too have the flaw that they are difficult to use without looking away from the TV to the remote control. Yet another flaw in these remote units is the use of modes in an attempt to reduce the number of buttons. In these "moded" universal remote units, a special button exists to select whether the remote should communicate with the TV, DVD player, cable set-top box, VCR, etc. This causes many usability issues including sending commands to the <boundary-data type="header">-5-</boundary-data>
|
| 53 |
+
<page-break num="6"/>
|
| 54 |
+
<boundary-data type="header">0320-08<confidence value="8">1</confidence>
|
| 55 |
+
</boundary-data>
|
| 56 |
+
wrong device, forcing the user to look at the remote to make sure that it is in the right mode, and it does not provide any simplification to the integration of multiple devices. </p>
|
| 57 |
+
<p id="p-12" num="12">The most advanced of these universal remote units provide some integration by allowing the user to program sequences of commands to multiple devices into the remote. This is such a difficult task that many users hire professional installers to program their universal remote units.</p>
|
| 58 |
+
<p id="p-13" num="13">[0007] Some attempts have also been made to modernize the screen interface between end users and media systems. However, these attempts typically suffer from, among other drawbacks, an inability to easily scale between large collections of media items and small collections of media items. For example, interfaces which rely on lists of items may work well for small collections of media items, but are tedious to browse for large collections of media items. Interfaces which rely on hierarchical navigation (e.g., tree structures) may be speedier to traverse than list interfaces for large collections of media items, but are not readily adaptable to small collections of media items. Additionally, users tend to lose interest in selection processes wherein the user has to move through three or more layers in a tree structure. For all of these cases, current remote units make this selection processor even more tedious by forcing the user to repeatedly depress the up and down buttons to navigate the list or hierarchies.</p>
|
| 59 |
+
<p id="p-14" num="14">When selection skipping controls are available such as page up and page down, the user usually has to look at the remote to find these special buttons or be trained to know that they even exist. Accordingly, organizing frameworks, techniques and systems which simplify the control and screen interface between users and media systems as <boundary-data type="header">-6-</boundary-data>
|
| 60 |
+
<page-break num="7"/>
|
| 61 |
+
<boundary-data type="header">0320-081</boundary-data>
|
| 62 |
+
well as accelerate the selection process, while at the same time permitting service providers to take advantage of the increases in available bandwidth to end user equipment by facilitating the supply of a large number of media items and new services to the user have been proposed in U.S. Patent Application Serial No. 10/768,432, filed on January <part-num-ref name="user have been proposed in U.S. Patent Application Serial No. 10/768,432, filed on January">30,</part-num-ref>
|
| 63 |
+
<part-num-ref name="user have been proposed in U.S. Patent Application Serial No. 10/768,432, filed on January 30,">2004,</part-num-ref>
|
| 64 |
+
entitled "A Control Framework with a Zoomable Graphical User Interface for Organizing, Selecting and Launching Media <confidence value="5">I</confidence>
|
| 65 |
+
tems", the disclosure of which is incorporated here by reference. </p>
|
| 66 |
+
<p id="p-15" num="15">[0008] As mentioned in the above-incorporated application, various different types of remote devices can be used with such frameworks including, for example, trackballs, "mouse"-type pointing devices, light pens, etc. However, another category of remote devices which can be used with such frameworks (and other applications) is 3D pointing devices with scroll wheels. The phrase "3D pointing" is used in this specification to refer to the ability of an input device to move in three (or more) dimensions in the air in front of, e.g., a display screen, and the corresponding ability of the user interface to translate those motions directly into user interface commands, e.g., movement of a cursor on the display screen. The transfer of data between the 3D pointing device may be performed wirelessly or via a wire connecting the 3D pointing device to another device. Thus "3D pointing" differs from, e.g., conventional computer mouse pointing techniques which use a surface, e.g., a desk surface or mousepad, as a proxy surface from which relative movement of the mouse is translated into cursor movement on the computer display screen. An example of a 3D pointing device can be <boundary-data type="header">-7-</boundary-data>
|
| 67 |
+
<page-break num="8"/>
|
| 68 |
+
<boundary-data type="header">0320-08<confidence value="8">1</confidence>
|
| 69 |
+
</boundary-data>
|
| 70 |
+
found in U.S. Patent Application Serial No. 11/119,663, the disclosure of which is incorporated here by reference. </p>
|
| 71 |
+
<p id="p-16" num="16">[0009] Of particular interest for this specification is how these remote devices interact with information and objects in a graphical user interface (GUI). A currently popular mechanism for interacting with objects in a GUI is the dropdown list. Typically a remote device moves a cursor over an object of interest and a dropdown list <part-num-ref name="dropdown list">200</part-num-ref>
|
| 72 |
+
appears as shown in Figure 2. However, when working with a visual interface where it is desirable to be able to interact with any object at any time, these dropdown lists have certain drawbacks. </p>
|
| 73 |
+
<p id="p-17" num="17">[0010] Firstly, a visual browser (or bookshelf view as seen in Figure 3) maximizes the available space by displaying as many images as possible on a single user interface screen. In such a layout when a standard dropdown list becomes visible it can obscure substantial portions of the objects. This can hinder the user in being able to easily point and click to select the obscured objects, e.g., the object <part-num-ref name="object">210</part-num-ref>
|
| 74 |
+
located "behind" the dropdown list <part-num-ref name="dropdown list">200</part-num-ref>
|
| 75 |
+
in Figure 2. Secondly, a typical dropdown list consists of items that are vertically short and packed together, however, when using a 3D pointing device to access dropdown lists, it is easy to over shoot the desired choice and instead accidentally select an undesired option. This can increase user frustration. Thirdly, a dropdown list typically requires a click to become visible. If a user changes his or her mind, it requires another click to make the dropdown list become invisible. The number of times a user clicks can become high and detract from the goal of having a simple user interface. Fourthly, dropdown lists are sometimes located in a menu bar separate <boundary-data type="header">-8-</boundary-data>
|
| 76 |
+
<page-break num="9"/>
|
| 77 |
+
<boundary-data type="header">0320-08<confidence value="8">1</confidence>
|
| 78 |
+
</boundary-data>
|
| 79 |
+
from the object of interest. To select an object and then move the cursor off the object to a menu could require a selection state option to be added to the interface. This addition of a selection state option is not desirable in a zoomable interface since it adds undesirable complications to the user interface. Lastly, dropdown lists are hidden by definition. Therefore the user has to be trained regarding the existence of these dropdown lists in the interface and to which objects these dropdown lists apply. All of these drawbacks tend to complicate the interface and create a higher learning curve than desired for new users. </p>
|
| 80 |
+
<p id="p-18" num="18">[0011] Thus, these drawbacks demonstrate that there is significant room for improvement in the area of handheld device interactions with GU<confidence value="4">I</confidence>
|
| 81 |
+
s, generally, and interactions between 3D pointers with zoomable GU<confidence value="5">I</confidence>
|
| 82 |
+
s using hover-buttons specifically. </p>
|
| 83 |
+
<boundary-data type="header">-9-</boundary-data>
|
| 84 |
+
<boundary-data type="header">0320-081</boundary-data>
|
| 85 |
+
<heading id="h-8">SUMMARY</heading>
|
| 86 |
+
<p id="p-19" num="19">
|
| 87 |
+
<page-break num="10"/>
|
| 88 |
+
[0012] Systems and methods according to the present invention address these needs and others by providing systems and methods for interacting with user-selectable objects in a graphical user interface. </p>
|
| 89 |
+
<p id="p-20" num="20">[0013] According to one exemplary embodiment of the present invention, a method for interacting with primary and secondary user-selectable objects in a graphical user interface comprising the steps of: associating secondary user-selectable objects with primary user-selectable objects; displaying secondary user-selectable objects associated with a respective primary user-selectable object when the respective primary user-selectable object is selected; and selecting one of the secondary user-selectable objects when a cursor is proximate of the one of the secondary user-selectable objects.</p>
|
| 90 |
+
<p id="p-21" num="21">[0014] According to another exemplary embodiment of the present invention, a user interface for interfacing with primary and secondary user-selectable objects comprising: primary and secondary user-selectable objects, wherein the secondary user-selectable objects are associated with a respective primary user-selectable objects; a display, wherein the secondary user-selectable objects associated with a respective primary user-selectable object are displayed upon the display when the respective primary user-selectable object is selected; and a cursor, wherein when the cursor is proximate of the secondary user-selectable object, the secondary user- selectable object is selected.</p>
|
| 91 |
+
<boundary-data type="header">-10-</boundary-data>
|
| 92 |
+
<boundary-data type="header">0320-08<confidence value="8">1</confidence>
|
| 93 |
+
</boundary-data>
|
| 94 |
+
<heading id="h-9">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
|
| 95 |
+
<p id="p-22" num="22">
|
| 96 |
+
<page-break num="11"/>
|
| 97 |
+
[0015] The accompanying drawings illustrate exemplary embodiments of the present invention, wherein: </p>
|
| 98 |
+
<p id="p-23" num="23">[0016] Figure 1 depicts a conventional remote control unit for an entertainment system<confidence value="5">;</confidence>
|
| 99 |
+
</p>
|
| 100 |
+
<p id="p-24" num="24">[0017] Figure 2 shows a typical drop down menu covering objects in a bookshelf view;</p>
|
| 101 |
+
<p id="p-25" num="25">[0018] Figure 3 shows a bookshelf view according to exemplary embodiments of the present invention;</p>
|
| 102 |
+
<p id="p-26" num="26">[0019] Figure 4 depicts an exemplary media system in which exemplary embodiments of the present invention can be implemented;</p>
|
| 103 |
+
<p id="p-27" num="27">[0020] Figure 5 shows a 3D pointing device according to an exemplary embodiment of the present invention;</p>
|
| 104 |
+
<p id="p-28" num="28">[0021] Figure 6 depicts an object with hover-buttons visible in a bookshelf view according to an exemplary embodiment of the present invention;</p>
|
| 105 |
+
<p id="p-29" num="29">[0022] Figures 7A - 7D depict an animation sequence for hover-buttons according to an exemplary embodiment of the present invention;</p>
|
| 106 |
+
<p id="p-30" num="30">[0023] Figures 8A - 8<confidence value="5">C</confidence>
|
| 107 |
+
illustrate an animation sequence for hover-buttons associated with a text object according to an exemplary embodiment of the present invention; </p>
|
| 108 |
+
<boundary-data type="header">-11-</boundary-data>
|
| 109 |
+
<boundary-data type="header">0320-081</boundary-data>
|
| 110 |
+
<p id="p-31" num="31">
|
| 111 |
+
<page-break num="12"/>
|
| 112 |
+
[0024] Figures 9A - 9G illustrate an animation sequence for hover-buttons where a hover-button has a sub-menu according to an exemplary embodiment of the present invention; </p>
|
| 113 |
+
<p id="p-32" num="32">[0025] Figure 10 depicts thresholds associated with hover-buttons according to an exemplary embodiment of the present invention.</p>
|
| 114 |
+
<heading id="h-10">DETAILED DESCRIPTION</heading>
|
| 115 |
+
<p id="p-33" num="33">[0026] The following detailed description of the invention refers to the accompanying drawings. The same reference numbers in different drawings identify the same or similar elements. Also, the following detailed description does not limit the invention. Instead, the scope of the invention is defined by the appended claims.</p>
|
| 116 |
+
<p id="p-34" num="34">[0027] In order to provide some context for this discussion, an exemplary aggregated media system <part-num-ref name="exemplary aggregated media system">400</part-num-ref>
|
| 117 |
+
in which the present invention can be implemented will first be described with respect to Figure 4. Those skilled in the art will appreciate, however, that the present invention is not restricted to implementation in this type of media system and that more or fewer components can be included therein. Therein, an input/output (<confidence value="586">1/O</confidence>
|
| 118 |
+
) bus <part-num-ref name="input/output (1/O) bus">410</part-num-ref>
|
| 119 |
+
connects the system components in the media system <part-num-ref name="media system">400</part-num-ref>
|
| 120 |
+
together. The <confidence value="286">1/O</confidence>
|
| 121 |
+
bus <part-num-ref name="1/O bus">410</part-num-ref>
|
| 122 |
+
represents any of a number of different of mechanisms and techniques for routing signals between the media system components. For example, the <confidence value="586">I/O</confidence>
|
| 123 |
+
bus <part-num-ref name="I/O bus">410</part-num-ref>
|
| 124 |
+
may include an appropriate number of independent audio "patch" cables that route audio signals, coaxial cables that route video signals, two-wire serial lines or infrared or radio frequency transceivers that route control signals, optical fiber or <boundary-data type="header">-12-</boundary-data>
|
| 125 |
+
<page-break num="13"/>
|
| 126 |
+
<boundary-data type="header">0320-081</boundary-data>
|
| 127 |
+
any other routing mechanisms that route other types of signals. </p>
|
| 128 |
+
<p id="p-35" num="35">[0028] In this exemplary embodiment, the media system <part-num-ref name="media system">400</part-num-ref>
|
| 129 |
+
includes a television/monitor <part-num-ref name="television/monitor">412,</part-num-ref>
|
| 130 |
+
a video cassette recorder (VCR) <part-num-ref name="video cassette recorder (VCR)">414,</part-num-ref>
|
| 131 |
+
digital video disk (DVD) recorder/playback device <part-num-ref name="video cassette recorder (VCR) 414, digital video disk (DVD) recorder/playback device">416,</part-num-ref>
|
| 132 |
+
audio/video tuner <part-num-ref name="video cassette recorder (VCR) 414, digital video disk (DVD) recorder/playback device 416, audio/video tuner">418</part-num-ref>
|
| 133 |
+
and compact disk player <part-num-ref name="and compact disk player">420</part-num-ref>
|
| 134 |
+
coupled to the <confidence value="585">1/O</confidence>
|
| 135 |
+
bus <part-num-ref name="1/O bus">410.</part-num-ref>
|
| 136 |
+
The VCR <part-num-ref name="VCR">414,</part-num-ref>
|
| 137 |
+
DVD <part-num-ref name="VCR 414, DVD">416</part-num-ref>
|
| 138 |
+
and compact disk player <part-num-ref name="and compact disk player">420</part-num-ref>
|
| 139 |
+
may be single disk or single cassette devices, or alternatively may be multiple disk or multiple cassette devices. They may be independent units or integrated together. In addition, the media system <part-num-ref name="media system">400</part-num-ref>
|
| 140 |
+
includes a microphone/speaker system <part-num-ref name="microphone/speaker system">422,</part-num-ref>
|
| 141 |
+
video camera <part-num-ref name="microphone/speaker system 422, video camera">424</part-num-ref>
|
| 142 |
+
and a wireless <confidence value="586">1/O</confidence>
|
| 143 |
+
control device <part-num-ref name="wireless 1/O control device">426.</part-num-ref>
|
| 144 |
+
According to exemplary embodiments of the present invention, the wireless <confidence value="586">I/O</confidence>
|
| 145 |
+
control device <part-num-ref name="wireless I/O control device">426</part-num-ref>
|
| 146 |
+
is a 3D pointing device although the present invention is not limited thereto. The wireless <confidence value="286">I/O</confidence>
|
| 147 |
+
control device <part-num-ref name="wireless I/O control device">426</part-num-ref>
|
| 148 |
+
can communicate with the entertainment system <part-num-ref name="entertainment system">400</part-num-ref>
|
| 149 |
+
using, e.g., an IR or RF transmitter or transceiver. Alternatively, the <confidence value="586">1/O</confidence>
|
| 150 |
+
control device can be connected to the entertainment system <part-num-ref name="entertainment system">400</part-num-ref>
|
| 151 |
+
via a wire. </p>
|
| 152 |
+
<p id="p-36" num="36">[0029] The entertainment system <part-num-ref name="entertainment system">400</part-num-ref>
|
| 153 |
+
also includes a system controller <part-num-ref name="system controller">428.</part-num-ref>
|
| 154 |
+
</p>
|
| 155 |
+
<p id="p-37" num="37">According to one exemplary embodiment of the present invention, the system controller <part-num-ref name="system controller">428</part-num-ref>
|
| 156 |
+
operates to store and display entertainment system data available from a plurality of entertainment system data sources and to control a wide variety of features associated with each of the system components. As shown in Figure 4, system controller <part-num-ref name="system components. As shown in Figure 4, system controller">428</part-num-ref>
|
| 157 |
+
is coupled, either directly or indirectly, to each of the system components, as necessary, through <confidence value="586">1/O</confidence>
|
| 158 |
+
bus <part-num-ref name="system components, as necessary, through 1/O bus">410.</part-num-ref>
|
| 159 |
+
In one exemplary embodiment, in addition to or in place of <confidence value="586">1/O</confidence>
|
| 160 |
+
bus <part-num-ref name="system components, as necessary, through 1/O bus 410. In one exemplary embodiment, in addition to or in place of 1/O bus">410,</part-num-ref>
|
| 161 |
+
system controller <part-num-ref name="system components, as necessary, through 1/O bus 410. In one exemplary embodiment, in addition to or in place of 1/O bus 410, system controller">428</part-num-ref>
|
| 162 |
+
is configured with a wireless communication <boundary-data type="header">-13-</boundary-data>
|
| 163 |
+
<page-break num="14"/>
|
| 164 |
+
<boundary-data type="header">0320-081</boundary-data>
|
| 165 |
+
transmitter (or transceiver), which is capable of communicating with the system components via IR signals or R<confidence value="5">F</confidence>
|
| 166 |
+
signals. Regardless of the control medium, the system controller <part-num-ref name="system controller">428</part-num-ref>
|
| 167 |
+
is configured to control the media components of the media system <part-num-ref name="media system">400</part-num-ref>
|
| 168 |
+
via a graphical user interface as described below. </p>
|
| 169 |
+
<p id="p-38" num="38">[0030] As further illustrated in Figure 4, media system 400 may be configured to receive media items from various media sources and service providers. In this exemplary embodiment, media system <part-num-ref name="may be configured to receive media items from various media sources and service providers. In this exemplary embodiment, media system">400</part-num-ref>
|
| 170 |
+
receives media input from and, optionally, sends information to, any or all of the following sources: cable broadcast <part-num-ref name="following sources: cable broadcast">430,</part-num-ref>
|
| 171 |
+
satellite broadcast <part-num-ref name="following sources: cable broadcast 430, satellite broadcast">432</part-num-ref>
|
| 172 |
+
(e.g., via a satellite dish), very high frequency (VHF) or ultra high frequency (UHF) radio frequency communication of the broadcast television networks <part-num-ref name="broadcast television networks">434</part-num-ref>
|
| 173 |
+
(e.g., via an aerial antenna), telephone network <part-num-ref name="aerial antenna), telephone network">436</part-num-ref>
|
| 174 |
+
and cable modem <part-num-ref name="and cable modem">438</part-num-ref>
|
| 175 |
+
(or another source of Internet content). Those skilled in the art will appreciate that the media components and media sources illustrated and described with respect to Figure 4 are purely exemplary and that media system <part-num-ref name="are purely exemplary and that media system">400</part-num-ref>
|
| 176 |
+
may include more or fewer of both. </p>
|
| 177 |
+
<p id="p-39" num="39">For example, other types of inputs to the system include AM/FM radio and satellite radio.</p>
|
| 178 |
+
<p id="p-40" num="40">[0031] More details regarding this exemplary entertainment system and frameworks associated therewith can be found in the above-incorporated by reference U.S. Patent Application entitled "A Control Framework with a Zoomable Graphical User Interface for Organizing, Selecting and Launching Media Items". Alternatively, remote devices in accordance with the present invention can be used in conjunction with other <boundary-data type="header">-14-</boundary-data>
|
| 179 |
+
<page-break num="15"/>
|
| 180 |
+
<boundary-data type="header">0320-081</boundary-data>
|
| 181 |
+
systems, for example computer systems including, e.g., a display, a processor and a memory system or with various other systems and applications. </p>
|
| 182 |
+
<p id="p-41" num="41">[0032] 3D pointing devices enable the translation of movement, e.g., gestures, into commands to a user interface. An exemplary 3D pointing device <part-num-ref name="exemplary 3D pointing device">500</part-num-ref>
|
| 183 |
+
is depicted in Figure 5. Therein, user movement of the 3D pointing can be defined, for example, in terms of a combination of x-axis attitude (roll), y-axis elevation (pitch) and/or z-axis heading (yaw) motion of the 3D pointing device <part-num-ref name="3D pointing device">500.</part-num-ref>
|
| 184 |
+
In addition, some exemplary embodiments of the present invention can also measure linear movement of the 3D pointing device <part-num-ref name="3D pointing device">500</part-num-ref>
|
| 185 |
+
along the x, y, and z axes to generate cursor movement or other user interface commands. In the exemplary embodiment of Figure 5, the 3D pointing device <part-num-ref name="3D pointing device">500</part-num-ref>
|
| 186 |
+
includes two buttons <part-num-ref name="includes two buttons">502</part-num-ref>
|
| 187 |
+
and <part-num-ref name="and">504</part-num-ref>
|
| 188 |
+
as well as a scroll wheel <part-num-ref name="scroll wheel">506</part-num-ref>
|
| 189 |
+
(scroll wheel <part-num-ref name="(scroll wheel">506</part-num-ref>
|
| 190 |
+
can also act as a button), although other exemplary embodiments will include other physical configurations. According to exemplary embodiments of the present invention, it is anticipated that 3D pointing device <part-num-ref name="present invention, it is anticipated that 3D pointing device">500</part-num-ref>
|
| 191 |
+
will be held by a user in front of a display <part-num-ref name="display">508</part-num-ref>
|
| 192 |
+
and that motion of the 3D pointing device <part-num-ref name="3D pointing device">500</part-num-ref>
|
| 193 |
+
will be translated by the 3D pointing device into output which is usable to interact with the information displayed on display <part-num-ref name="information displayed on display">508,</part-num-ref>
|
| 194 |
+
e.g., to move the cursor <part-num-ref name="cursor">510</part-num-ref>
|
| 195 |
+
on the display <part-num-ref name="display">508.</part-num-ref>
|
| 196 |
+
For example, rotation of the 3D pointing device <part-num-ref name="3D pointing device">500</part-num-ref>
|
| 197 |
+
about the y-axis can be sensed by the 3D pointing device <part-num-ref name="3D pointing device">500</part-num-ref>
|
| 198 |
+
and translated into an output usable by the system to move cursor <part-num-ref name="system to move cursor">510</part-num-ref>
|
| 199 |
+
along the y2 axis of the display <part-num-ref name="display">508.</part-num-ref>
|
| 200 |
+
Likewise, rotation of the 3D pointing device <part-num-ref name="3D pointing device">508</part-num-ref>
|
| 201 |
+
about the z-axis can be sensed by the 3D pointing device <part-num-ref name="3D pointing device">500</part-num-ref>
|
| 202 |
+
and translated into an output usable by the system to move cursor <part-num-ref name="system to move cursor">510</part-num-ref>
|
| 203 |
+
along the x2 axis of the display <part-num-ref name="display">508.</part-num-ref>
|
| 204 |
+
It will be appreciated <boundary-data type="header">-15-</boundary-data>
|
| 205 |
+
<page-break num="16"/>
|
| 206 |
+
<boundary-data type="header">0320-081</boundary-data>
|
| 207 |
+
that the output of 3D pointing device <part-num-ref name="output of 3D pointing device">500</part-num-ref>
|
| 208 |
+
can be used to interact with the display <part-num-ref name="display">508</part-num-ref>
|
| 209 |
+
in a number of ways other than (or in addition to) cursor movement, for example it can control cursor fading, volume or media transport (play, pause, fast-forward and rewind). </p>
|
| 210 |
+
<p id="p-42" num="42">Input commands may include operations in addition to cursor movement, for example, a zoom in or zoom out on a particular region of a display. A cursor may or may not be visible. Similarly, rotation of the 3D pointing device <part-num-ref name="3D pointing device">500</part-num-ref>
|
| 211 |
+
sensed about the x-axis of 3D pointing device <part-num-ref name="x-axis of 3D pointing device">500</part-num-ref>
|
| 212 |
+
can be used in addition to, or as an alternative to, y-axis and/or z- axis rotation to provide input to a user interface. The above described 3D pointing device system can be used in a GUI that uses hover-buttons as described below. </p>
|
| 213 |
+
<p id="p-43" num="43">Hover-Buttons [0033] Exemplary embodiments of the present invention describe how to improve interacting with objects in a graphical user interface (GU<confidence value="5">I</confidence>
|
| 214 |
+
) through the use of secondary user-selectable objects, some of which are referred to herein as "hover-buttons". </p>
|
| 215 |
+
<p id="p-44" num="44">[0034] Prior to describing specific details of these secondary user-selectable objects regarding, a brief description of an exemplary GUI in which they can be deployed is presented. The GUI contains one or more target objects (also referred to herein as graphical objects or primary user-selectable objects). The target objects can be presented and organized in many different ways on a display such as: <part-num-ref name="display such as:">(1)</part-num-ref>
|
| 216 |
+
single buttons or zoomable objects arbitrarily positioned on the screen, <part-num-ref name="screen,">(2)</part-num-ref>
|
| 217 |
+
one dimensional lists of buttons or zoomable objects which may be scrollable, <part-num-ref name="one dimensional lists of buttons or zoomable objects which may be scrollable,">(3)</part-num-ref>
|
| 218 |
+
two dimensional grids of objects possibly scrollable and pannable, <part-num-ref name="two dimensional grids of objects possibly scrollable and pannable,">(4)</part-num-ref>
|
| 219 |
+
three dimensional matrices of objects possibly scrollable and <part-num-ref name="three dimensional matrices of objects possibly scrollable and">(5)</part-num-ref>
|
| 220 |
+
various combinations of the above. It may be desirable for <boundary-data type="header">-16-</boundary-data>
|
| 221 |
+
<page-break num="17"/>
|
| 222 |
+
<boundary-data type="header">0320-08<confidence value="8">1</confidence>
|
| 223 |
+
</boundary-data>
|
| 224 |
+
some GUI objects to be immediately available at all times because of their functionality. </p>
|
| 225 |
+
<p id="p-45" num="45">In the exemplary GU<confidence value="5">I</confidence>
|
| 226 |
+
s described herein, objects with hover-buttons are presented in a bookshelf format, however as described above other presentations are possible. </p>
|
| 227 |
+
<p id="p-46" num="46">[0035] According to exemplary embodiments of the present invention, a cursor is used to indicate the current location of interest in the user interface associated with movement of a corresponding pointing device. When the cursor enters the area occupied by a target object and hovers within the area for a predetermined amount of time, such as <confidence value="655">100</confidence>
|
| 228 |
+
ms to <confidence value="6555">1000</confidence>
|
| 229 |
+
ms, that object is highlighted. Note that hovering includes, but is not limited to pausing, such that the cursor can still be moving and trigger a change in object focus. Highlighting is visible through a color change, a hover-zoom effect, enlargement or any other visual method that makes the object over which the cursor has paused distinguishable from other objects on the display. The highlighted object is the object on the GUI that has the focus of both the user and the system. </p>
|
| 230 |
+
<p id="p-47" num="47">Hover-button(s) can be associated and attached to the currently highlighted (or focused) object to enable the user to actuate, or otherwise further interact with, that object.</p>
|
| 231 |
+
<p id="p-48" num="48">These attached hover-buttons make it clear to a user which object the hover-buttons are associated with.</p>
|
| 232 |
+
<p id="p-49" num="49">[0036] In this specification, an object can gain the focus of the system and the user, e.g., by having a cursor hover thereover, which may be different from selection of that object. Selecting an object typically involves some form of actuation which can, for example, execute a function related to the object which currently has the focus of the system. According to some exemplary embodiments described herein, a cursor moves <boundary-data type="header">-17-</boundary-data>
|
| 233 |
+
<page-break num="18"/>
|
| 234 |
+
<boundary-data type="header">0320-08<confidence value="8">1</confidence>
|
| 235 |
+
</boundary-data>
|
| 236 |
+
over an object and the object enlarges, or otherwise provides feedback to the user that that object has gained focus (e.g., it is highlighted). The user may then perform an action such as, for example, "clicking" on the object. This clicking selects the object and activates a function associated with the object. For example, if the focused object was a movie cover, and the user clicked on the focused object an action such as playing the movie could occur. Alternatively, a user may change the system's focus to another object on the user interface without selecting or actuating the object which previously had the user and the system's focus. </p>
|
| 237 |
+
<p id="p-50" num="50">[0037] Prior to describing examples using hover-buttons with user-selectable objects, a description of some of the exemplary features of hover-buttons is presented.</p>
|
| 238 |
+
<p id="p-51" num="51">According to exemplary embodiments of the present invention, hover-buttons are a type of secondary user-selectable object that are associated with, and often geographically attached to, a primary user-selectable object, such as a picture in a picture organizing portion of a user interface. Hover-buttons can be geographically disbursed around the edge of the associated target object in order to increase the distance between the hover-buttons associated with the same target object so that it is easier for a user to point and gain the focus of one hover-button over another hover-button. To achieve this geographical disbursement, hover-buttons can, for example, be located at geographic corners on the edge of an object. A typical pattern of cursor movement is from the center of the hovered target object to one of the corners where a hover-button is located. The effect generated is a single vector movement in one of four directions relative to the hovered object. These same relative movements towards corners of <boundary-data type="header">-18-</boundary-data>
|
| 239 |
+
<page-break num="19"/>
|
| 240 |
+
<boundary-data type="header">0320-08<confidence value="8">1</confidence>
|
| 241 |
+
</boundary-data>
|
| 242 |
+
target objects tend to become a habit forming gesture that simplifies using the GUI. </p>
|
| 243 |
+
<p id="p-52" num="52">Another exemplary feature of hover-buttons is that hover-buttons can become visible only when the object to which they are attached has the focus. Upon losing the focus of the object, the hover-buttons then become invisible. Also as a cursor comes near a hover-button, the hover-button enlarges and upon the cursor moving away from the hover-button, the hover button shrinks in size to allow the associated object to become clearly visible. Additionally, only one hover-button tends to be enlarged at a time to increase the ease of selection for a user. Using combinations of these exemplary features of hover-buttons, examples of using hover-buttons are presented below.</p>
|
| 244 |
+
<p id="p-53" num="53">[0038] According to exemplary embodiments of the present invention, hover- buttons can be associated with objects in a GUI. As shown in Figure 3, objects <part-num-ref name="GUI. As shown in Figure 3, objects">302,</part-num-ref>
|
| 245 |
+
<part-num-ref name="GUI. As shown in Figure 3, objects 302,">304,</part-num-ref>
|
| 246 |
+
<part-num-ref name="GUI. As shown in Figure 3, objects 302, 304,">306,</part-num-ref>
|
| 247 |
+
<part-num-ref name="GUI. As shown in Figure 3, objects 302, 304, 306,">308,</part-num-ref>
|
| 248 |
+
<part-num-ref name="GUI. As shown in Figure 3, objects 302, 304, 306, 308,">310</part-num-ref>
|
| 249 |
+
and <part-num-ref name="and">312,</part-num-ref>
|
| 250 |
+
in this example images of pictures, are presented in a bookshelf view. None of these objects <part-num-ref name="bookshelf view. None of these objects">302,</part-num-ref>
|
| 251 |
+
<part-num-ref name="bookshelf view. None of these objects 302,">304,</part-num-ref>
|
| 252 |
+
<part-num-ref name="bookshelf view. None of these objects 302, 304,">306,</part-num-ref>
|
| 253 |
+
<part-num-ref name="bookshelf view. None of these objects 302, 304, 306,">308,</part-num-ref>
|
| 254 |
+
<part-num-ref name="bookshelf view. None of these objects 302, 304, 306, 308,">310</part-num-ref>
|
| 255 |
+
and <part-num-ref name="and">312</part-num-ref>
|
| 256 |
+
currently have the focus of the system or the user. When a cursor (not shown) is moved over an object, the object is enlarged and the associated hover-buttons become visible. This can be seen in Figure 6, where object <part-num-ref name="associated hover-buttons become visible. This can be seen in Figure 6, where object">304</part-num-ref>
|
| 257 |
+
has gained the focus by a cursor (not shown) hovering over object <part-num-ref name="cursor (not shown) hovering over object">304</part-num-ref>
|
| 258 |
+
and is therefore enlarged as a result of a hover-zoom animation. Additionally, four hover-buttons <part-num-ref name="hover-zoom animation. Additionally, four hover-buttons">602,</part-num-ref>
|
| 259 |
+
<part-num-ref name="hover-zoom animation. Additionally, four hover-buttons 602,">604,</part-num-ref>
|
| 260 |
+
<part-num-ref name="hover-zoom animation. Additionally, four hover-buttons 602, 604,">606</part-num-ref>
|
| 261 |
+
and <part-num-ref name="and">608</part-num-ref>
|
| 262 |
+
are now visible and appear attached to object <part-num-ref name="are now visible and appear attached to object">304.</part-num-ref>
|
| 263 |
+
In this exemplary embodiment, when hover-buttons initially become visible they are in a minimized format so as to not obscure the object <part-num-ref name="object">304</part-num-ref>
|
| 264 |
+
to which they are attached, and to minimize obscuring other objects in the GUI. </p>
|
| 265 |
+
<boundary-data type="header">-19-</boundary-data>
|
| 266 |
+
<boundary-data type="header">0320-081</boundary-data>
|
| 267 |
+
<p id="p-54" num="54">
|
| 268 |
+
<page-break num="20"/>
|
| 269 |
+
[0039] According to an exemplary embodiment of the present invention, an animation sequence is used to illustrate the flow of actions from having an object on the screen to enabling or actuating a hover-button. This exemplary animation sequence is illustrated in Figures 7A - 7D. Initially, as shown in Figure 7A, there is an object <part-num-ref name="object">702.</part-num-ref>
|
| 270 |
+
</p>
|
| 271 |
+
<p id="p-55" num="55">When cursor 704 is moved over object <part-num-ref name="is moved over object">702</part-num-ref>
|
| 272 |
+
and hovers, object <part-num-ref name="and hovers, object">702</part-num-ref>
|
| 273 |
+
becomes enlarged and the hover-buttons <part-num-ref name="hover-buttons">(706,</part-num-ref>
|
| 274 |
+
<part-num-ref name="hover-buttons (706,">708,</part-num-ref>
|
| 275 |
+
<part-num-ref name="hover-buttons (706, 708,">710</part-num-ref>
|
| 276 |
+
and <part-num-ref name="and">712)</part-num-ref>
|
| 277 |
+
become visible as shown in Figure 7B. </p>
|
| 278 |
+
<p id="p-56" num="56">As cursor 704 moves toward a particular hover-button, that hover-button will enlarge.</p>
|
| 279 |
+
<p id="p-57" num="57">For example, as shown in Figure 7C, when cursor 704 is moved towards hover-button <part-num-ref name="is moved towards hover-button">706,</part-num-ref>
|
| 280 |
+
hover-button <part-num-ref name="is moved towards hover-button 706, hover-button">706</part-num-ref>
|
| 281 |
+
enlarges. This enlarged hover-button <part-num-ref name="enlarges. This enlarged hover-button">706</part-num-ref>
|
| 282 |
+
can be seen by comparing Figure 7B to Figure 7C. In Figure 7<confidence value="5">B</confidence>
|
| 283 |
+
, hover-button <part-num-ref name="can be seen by comparing Figure 7B to Figure 7C. In Figure 7B, hover-button">706</part-num-ref>
|
| 284 |
+
is a relatively small, square shaped button showing the letter "E". Upon expansion, as shown in Figure 7C, the hover-button <part-num-ref name="hover-button">706</part-num-ref>
|
| 285 |
+
is a larger rectangular shaped button displaying the word "Edit". </p>
|
| 286 |
+
<p id="p-58" num="58">The hover-button 706 gains the focus upon moving cursor <part-num-ref name="focus upon moving cursor">704</part-num-ref>
|
| 287 |
+
over top of hover-button <part-num-ref name="over top of hover-button">706</part-num-ref>
|
| 288 |
+
as shown in Figure 7D. One method for triggering graphic feedback and/or execution of a function associated with hover-button <part-num-ref name="function associated with hover-button">706</part-num-ref>
|
| 289 |
+
is to click hover-button <part-num-ref name="is to click hover-button">706</part-num-ref>
|
| 290 |
+
with the pointing device. Additionally, if hover-button <part-num-ref name="pointing device. Additionally, if hover-button">706</part-num-ref>
|
| 291 |
+
itself had hover-buttons associated with it, these new hover-buttons would become visible once the cursor was over top hover-button <part-num-ref name="cursor was over top hover-button">706.</part-num-ref>
|
| 292 |
+
In this exemplary embodiment, only one object is shown for simplification, whereas in most applications, there will be many objects in the bookshelf view. </p>
|
| 293 |
+
<p id="p-59" num="59">[0040] According to another exemplary embodiment of the present invention, hover-buttons can be applied to text objects as shown in Figures 8A - 8C. Figures 8A - <boundary-data type="header">-20-</boundary-data>
|
| 294 |
+
<page-break num="21"/>
|
| 295 |
+
<boundary-data type="header">0320-081</boundary-data>
|
| 296 |
+
<confidence value="86">8C</confidence>
|
| 297 |
+
additionally show an exemplary animation sequence involved in text object <part-num-ref name="exemplary animation sequence involved in text object">802</part-num-ref>
|
| 298 |
+
gaining the focus and activating a hover-button. Figure 8A shows an exemplary text object <part-num-ref name="exemplary text object">802.</part-num-ref>
|
| 299 |
+
In Figure 8B text object <part-num-ref name="exemplary text object 802. In Figure 8B text object">802</part-num-ref>
|
| 300 |
+
has gained the focus by moving a cursor (not shown) which makes hover-buttons <part-num-ref name="cursor (not shown) which makes hover-buttons">(804,</part-num-ref>
|
| 301 |
+
<part-num-ref name="cursor (not shown) which makes hover-buttons (804,">806</part-num-ref>
|
| 302 |
+
and <part-num-ref name="and">808)</part-num-ref>
|
| 303 |
+
visible. By moving the cursor (not shown) toward hover-button <part-num-ref name="cursor (not shown) toward hover-button">804,</part-num-ref>
|
| 304 |
+
hover-button <part-num-ref name="cursor (not shown) toward hover-button 804, hover-button">804</part-num-ref>
|
| 305 |
+
expands as shown in Figure <confidence value="86">8C</confidence>
|
| 306 |
+
, revealing the "Delete" hover-button label. Additionally, according to an exemplary embodiment of the present invention, the background coloration of a hover-button can be either transparent or translucent to minimize obscuring information. Note that in this exemplary embodiment of the present invention, when the target object gains the focus, i.e., text object <part-num-ref name="text object">802,</part-num-ref>
|
| 307 |
+
a graphical selection effect (outline <part-num-ref name="graphical selection effect (outline">810)</part-num-ref>
|
| 308 |
+
is displayed rather than enlargement of the target object as in the embodiment of Figure 7B. </p>
|
| 309 |
+
<p id="p-60" num="60">[0041] One benefit of the afore-described techniques is to create a simple GUI.</p>
|
| 310 |
+
<p id="p-61" num="61">One expectation of a simple GUI is to have a reduced set of needed functions for use in the simple GUI. Accordingly, in one exemplary embodiment of the present invention, an object will have a maximum of four hover-buttons associated with each target object.</p>
|
| 311 |
+
<p id="p-62" num="62">Each hover button corresponds to a different function that can be performed in association with the object.</p>
|
| 312 |
+
<p id="p-63" num="63">[0042] According to other exemplary embodiments of the present invention more than four functions can be associated with an object. To achieve this functionality, an exemplary embodiment of the present invention allows a hover-button to have a sub- menu. An exemplary animation sequence involving a hover-button with a sub-menu is shown in Figures 9A - 9G. Figure 9A shows an image object <part-num-ref name="image object">902</part-num-ref>
|
| 313 |
+
that does not have <boundary-data type="header">-21-</boundary-data>
|
| 314 |
+
<page-break num="22"/>
|
| 315 |
+
<boundary-data type="header">0320-08<confidence value="8">1</confidence>
|
| 316 |
+
</boundary-data>
|
| 317 |
+
the focus and a cursor <part-num-ref name="cursor">904.</part-num-ref>
|
| 318 |
+
In Figure 9<confidence value="5">B</confidence>
|
| 319 |
+
, the cursor <part-num-ref name="cursor">904</part-num-ref>
|
| 320 |
+
is hovering over the now focused upon image object <part-num-ref name="now focused upon image object">902,</part-num-ref>
|
| 321 |
+
which results in the hover-buttons <part-num-ref name="hover-buttons">(906,</part-num-ref>
|
| 322 |
+
<part-num-ref name="hover-buttons (906,">908,</part-num-ref>
|
| 323 |
+
<part-num-ref name="hover-buttons (906, 908,">910</part-num-ref>
|
| 324 |
+
and <part-num-ref name="and">912)</part-num-ref>
|
| 325 |
+
becoming visible. Figure 9C shows the cursor <part-num-ref name="cursor">904</part-num-ref>
|
| 326 |
+
moving towards the upper right corner of image object <part-num-ref name="upper right corner of image object">902</part-num-ref>
|
| 327 |
+
which causes hover-button <part-num-ref name="which causes hover-button">906</part-num-ref>
|
| 328 |
+
to enlarge. As the cursor <part-num-ref name="cursor">904</part-num-ref>
|
| 329 |
+
gets closer to hover-button <part-num-ref name="gets closer to hover-button">906,</part-num-ref>
|
| 330 |
+
the sub-menu becomes visible as seen in Figure 9D, i.e., the new hover-buttons <part-num-ref name="new hover-buttons">(914,</part-num-ref>
|
| 331 |
+
<part-num-ref name="new hover-buttons (914,">916,</part-num-ref>
|
| 332 |
+
<part-num-ref name="new hover-buttons (914, 916,">918</part-num-ref>
|
| 333 |
+
and <part-num-ref name="and">920)</part-num-ref>
|
| 334 |
+
for the sub-menu become visible. Additionally as shown in Figure 9D, when the sub-menu becomes visible, the sub-menu name "Modify List" <part-num-ref name="sub-menu name "Modify List"">922</part-num-ref>
|
| 335 |
+
moves just above the object <part-num-ref name="object">902</part-num-ref>
|
| 336 |
+
to remind the user that he or she is in a sub-menu. Since the cursor <part-num-ref name="cursor">904</part-num-ref>
|
| 337 |
+
is close to hover-button <part-num-ref name="is close to hover-button">914,</part-num-ref>
|
| 338 |
+
hover-button <part-num-ref name="is close to hover-button 914, hover-button">914</part-num-ref>
|
| 339 |
+
is enlarged as seen in Figure 9D. Figures 9E - 9G show the enlarged, sub-menu hover-buttons located near each corner of object <part-num-ref name="enlarged, sub-menu hover-buttons located near each corner of object">902</part-num-ref>
|
| 340 |
+
when cursor <part-num-ref name="when cursor">904</part-num-ref>
|
| 341 |
+
is in proximity to the hover-button, as well as the shrinking of a hover-button when cursor <part-num-ref name="hover-button when cursor">904</part-num-ref>
|
| 342 |
+
moves away from the hover-button. </p>
|
| 343 |
+
<p id="p-64" num="64">[0043] According to another exemplary embodiment of the present invention, instead of using the animation sequence described above, a hover-button can reach its maximum or minimum size instantaneously based upon the cursor's location.</p>
|
| 344 |
+
<p id="p-65" num="65">[0044] As described above, hover-buttons can become enlarged when a cursor moves towards a hover-button. Hover-buttons can have associated area thresholds that, when crossed, trigger actions related to the hover-button. As illustrated in Figure 10, hover-button <part-num-ref name="hover-button. As illustrated in Figure 10, hover-button">1002</part-num-ref>
|
| 345 |
+
has two area thresholds (typically not visible to the GUI user) <part-num-ref name="GUI user)">(1004</part-num-ref>
|
| 346 |
+
and <part-num-ref name="and">1006)</part-num-ref>
|
| 347 |
+
associated with it. When a cursor (not shown) crosses over any portion of threshold <part-num-ref name="cursor (not shown) crosses over any portion of threshold">1006,</part-num-ref>
|
| 348 |
+
the sub-menu associated with hover-button <part-num-ref name="sub-menu associated with hover-button">1002</part-num-ref>
|
| 349 |
+
gains the <boundary-data type="header">-22-</boundary-data>
|
| 350 |
+
<page-break num="23"/>
|
| 351 |
+
<boundary-data type="header">0320-08<confidence value="8">1</confidence>
|
| 352 |
+
</boundary-data>
|
| 353 |
+
focus and enlarges. When the cursor (not shown) crosses over any portion of threshold <part-num-ref name="cursor (not shown) crosses over any portion of threshold">1004,</part-num-ref>
|
| 354 |
+
hover-button <part-num-ref name="cursor (not shown) crosses over any portion of threshold 1004, hover-button">1002</part-num-ref>
|
| 355 |
+
(if any) is displayed. Similar thresholds are associated with the other hover-buttons. In order to leave the submenu, the user needs to move the cursor outside of the primary object's boundaries. </p>
|
| 356 |
+
<p id="p-66" num="66">[0045] According to other exemplary embodiments of the present invention, hover-buttons can gain focus based on a movement gesture made by the user depicted by the cursor motion on the screen. For example, after an object has gained the focus, when the cursor is moved towards a hover-button, that hover-button gains the focus and becomes enlarged.</p>
|
| 357 |
+
<p id="p-67" num="67">[0046] According to another exemplary embodiment, scrolling can be used in conjunction with hover-buttons. Each primary user-selectable object in, e.g., a bookshelf view would have a scrolling order number assigned to it, with one of the objects in each view being considered the starting object for scrolling. Additionally, the hover-buttons associated with each object in the bookshelf view would be part of the predetermined scrolling sequence. In an exemplary scrolling order, the scrolling order would be to visit the primary object then visit each hover-button associated with the primary object followed by moving to the next primary object. The next object in the scrolling order would gain the focus of the system and the user with one index rotation of the scroll-wheel.</p>
|
| 358 |
+
<p id="p-68" num="68">[0047] Numerous variations of the afore-described exemplary embodiments are contemplated. The above-described exemplary embodiments are intended to be illustrative in all respects, rather than restrictive, of the present invention. Thus the <boundary-data type="header">-23-</boundary-data>
|
| 359 |
+
<page-break num="24"/>
|
| 360 |
+
<boundary-data type="header">0320-081</boundary-data>
|
| 361 |
+
present invention is capable of many variations in detailed implementation that can be derived from the description contained herein by a person skilled in the art. All such variations and modifications are considered to be within the scope and spirit of the present invention as defined by the following claims. No element, act, or instruction used in the description of the present application should be construed as critical or essential to the invention unless explicitly described as such. Also, used herein, the article <confidence value="666">"a"</confidence>
|
| 362 |
+
is intended to include one or more items. </p>
|
| 363 |
+
<boundary-data type="header">-24-</boundary-data>
|
| 364 |
+
</description>
|
| 365 |
+
</us-patent-application>
|
| 366 |
+
|
applicant/11536285.xml
ADDED
|
@@ -0,0 +1,290 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>11536285</doc-number>
|
| 8 |
+
<date>2006-09-28</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<heading id="h-1">APPARATUS OF CENTRIFUGAL FAN AND A DUST-</heading>
|
| 14 |
+
<heading id="h-2">COLLECTING MODULE USING THE SAME</heading>
|
| 15 |
+
<heading id="h-3">FIELD OF THE INVENTION</heading>
|
| 16 |
+
<p id="p-1" num="1">
|
| 17 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 18 |
+
[0001] The present invention relates to a centrifugal fan apparatus, and more particularly, to a low noise, high flow rate centrifugal fan apparatus with asymmetry fan housing design, which has an uniform airflow channel formed between the rim of its impeller and its housing, and is applicable to a dust-collecting module. </p>
|
| 19 |
+
<p id="p-2" num="2">
|
| 20 |
+
<boundary-data type="line-number">
|
| 21 |
+
<confidence value="88">10</confidence>
|
| 22 |
+
</boundary-data>
|
| 23 |
+
</p>
|
| 24 |
+
<heading id="h-4">BACKGROUND OF THE INVENTION</heading>
|
| 25 |
+
<p id="p-3" num="3">[0002] An autonomous vacuum cleaner, being a fully automated cleaning device, is a renovating device different from those conventionally vacuum cleaners and other sweeping devices, that is can <boundary-data type="line-number">15 </boundary-data>
|
| 26 |
+
clean a specific area autonomously without any human attention and thus is foreseen to be the future cleaning device replacing those conventional manual-operated vacuum cleaners and other cleaning devices. After the operation mode is set, an autonomous vacuum cleaner is able to maneuver around obstacles while performing a ground cleaning operation, even <boundary-data type="line-number">20 </boundary-data>
|
| 27 |
+
cleaning those usually considered as the dead spots of cleaning. </p>
|
| 28 |
+
<p id="p-4" num="4">[0003] Although the autonomous vacuum cleaner is a great help to daily household cleaning, its function is limited by its power source, which is not an alternating current (A<confidence value="66">C)</confidence>
|
| 29 |
+
power source, and by its own interior space, which limited the same from adopting those air <boundary-data type="line-number">25 </boundary-data>
|
| 30 |
+
compressors used in those conventional vacuum cleaners. Therefore, as the autonomous vacuum cleaner only has limited power supply, a good centrifugal fan is essential for enabling the same to have good <boundary-data type="header">
|
| 31 |
+
<confidence value="8">1</confidence>
|
| 32 |
+
</boundary-data>
|
| 33 |
+
<page-break num="2"/>
|
| 34 |
+
performance. Nonetheless, the centrifugal fan is beneficial for its operating noise is lower than those conventional air compressors. </p>
|
| 35 |
+
<p id="p-5" num="5">[0004] It is noted that current design of a centrifugal fan is focusing on low noise, high pressure difference and large flow rate while maintaining <boundary-data type="line-number">5 </boundary-data>
|
| 36 |
+
smooth operation. One such design is disclosed in <confidence value="5">T</confidence>
|
| 37 |
+
W Pat. No. M246471, which shows a centrifugal fan device and a vacuum cleaner adopting the same. However, as the housing of the aforesaid centrifugal fan device is not improved while no proper deflector is available in the airflow channel, it is prone to generate noise. Another such design is disclosed in EPC Pat. </p>
|
| 38 |
+
<p id="p-6" num="6">
|
| 39 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 40 |
+
No. EP<confidence value="4">0</confidence>
|
| 41 |
+
943808, in which its casing is designed for enabling its air pressure cavity to run spirally to an outflow aperture whereas its casing tongue is made with a through curvature for separating the airflow of the intake end from that of the outflow end so that the efficiency of the aforesaid centrifugal fan device can be improved as turbulence is avoided. </p>
|
| 42 |
+
<p id="p-7" num="7">
|
| 43 |
+
<boundary-data type="line-number">15 </boundary-data>
|
| 44 |
+
[0005] Generally, in those disclosed centrifugal fan devices, the convenience of attaching a dust-collecting box upon a centrifugal fan device is mostly cancelled out by the blocking of the smoothness of air flow in the centrifugal fan device's airflow channel. </p>
|
| 45 |
+
<p id="p-8" num="8">[0006] Therefore, it is in need of an improved centrifugal fan apparatus <boundary-data type="line-number">20 </boundary-data>
|
| 46 |
+
and a dust-collecting module that are freed from the foregoing drawbacks. </p>
|
| 47 |
+
<heading id="h-5">SUMMARY OF THE INVENTION</heading>
|
| 48 |
+
<p id="p-9" num="9">[0007] It is the primary object of the present invention to provide a low noise, high flow rate centrifugal fan apparatus with asymmetry fan <boundary-data type="line-number">25 </boundary-data>
|
| 49 |
+
housing design, which has an uniform airflow channel formed between the rim of its impeller and its housing, and is applicable to a dust-collecting module. </p>
|
| 50 |
+
<boundary-data type="header">
|
| 51 |
+
<confidence value="8">2</confidence>
|
| 52 |
+
</boundary-data>
|
| 53 |
+
<p id="p-10" num="10">
|
| 54 |
+
<page-break num="3"/>
|
| 55 |
+
[0008] Another object of the invention is to provide a dust-collecting module capable of utilizing it specially designed casing to assemble a centrifugal fan apparatus of the invention so as to be able to pe<confidence value="8">r</confidence>
|
| 56 |
+
form a dust-collecting operation while maintaining the smoothness of airflow in <boundary-data type="line-number">5 </boundary-data>
|
| 57 |
+
the centrifugal fan apparatus. </p>
|
| 58 |
+
<p id="p-11" num="11">[0009] To achieve the above objects, the present invention provides a centrifugal fan apparatus, comprising: a housing with an accommodating space, having an intake hole and an outflow hole; an impeller, arranging in the accommodating space while enabling an airflow channel of uniform <boundary-data type="line-number">10 </boundary-data>
|
| 59 |
+
width to be formed between a rim of the impeller and a side wall of the housing; and a driving device, connected to the impeller for driving the same to rotate. </p>
|
| 60 |
+
<p id="p-12" num="12">[0010] Preferably, the accommodating space is divided into a first space and a second space by a virtual cross section passing the axial center <boundary-data type="line-number">15 </boundary-data>
|
| 61 |
+
of the impeller, referring as axial cross section hereinafter, whereas the first space is asymmetrical to the second space. Moreover, a helical airflow channel is extending from the second space and channeling to the outflow hole; and the sectional area of the helical airflow channel is increasing progressively from the beginning thereof to the outflow hole. </p>
|
| 62 |
+
<p id="p-13" num="13">
|
| 63 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 64 |
+
[0011] Preferably, the housing further is composed of: a top shell, having the intake hole formed thereon; and a bottom shell, having the outflow hole formed therein, being connected to the top shell. </p>
|
| 65 |
+
<p id="p-14" num="14">[0012] Preferably, each blade used in the impeller is a blade selected from the group consisting of airfoil blades of signal-blade design and <boundary-data type="line-number">25 </boundary-data>
|
| 66 |
+
airfoil blades of dual-blade design. </p>
|
| 67 |
+
<p id="p-15" num="15">[0013] In a preferred aspect, to achieve the above objects, the present invention provides a centrifugal fan apparatus, comprising: a housing with an accommodating space, having an intake hole and an outflow hole; an impeller, arranging in the accommodating space while enabling the <boundary-data type="header">
|
| 68 |
+
<confidence value="7">3</confidence>
|
| 69 |
+
</boundary-data>
|
| 70 |
+
<page-break num="4"/>
|
| 71 |
+
accommodating space to be divided into a first space and a second space by a virtual cross section passing the axial center of the impeller, referring as axial cross section hereinafter, whereas the first space is asymmetrical to the second space; and a driving device, connected to the impeller for <boundary-data type="line-number">5 </boundary-data>
|
| 72 |
+
driving the same to rotate. </p>
|
| 73 |
+
<p id="p-16" num="16">[0014] In addition, the present invention further provides a ducts- collecting module, comprising: a case, having a recess and a through hole channeling to the recess, and a side thereof being arranged with a groove hole channeling to the recess; a dust-collecting lid, connected to the <boundary-data type="line-number">
|
| 74 |
+
<confidence value="66">10</confidence>
|
| 75 |
+
</boundary-data>
|
| 76 |
+
groove hole; a box with a dust-collecting space, capable of being received in the recess for enabling the duct-collecting space to channel with the through hole and the groove hole; and a centrifugal fan apparatus, arranged upon the case, further comprising: a housing with an accommodating space formed therein, having an intake hole connected to <boundary-data type="line-number">15 </boundary-data>
|
| 77 |
+
the through hole and an outflow hole; an impeller, arranging in the accommodating space while enabling an airflow channel of uniform width to be formed between a rim of the impeller and a side wall of the housing; </p>
|
| 78 |
+
<p id="p-17" num="17">and a driving device, connected to the impeller for driving the same to rotate.</p>
|
| 79 |
+
<p id="p-18" num="18">
|
| 80 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 81 |
+
[0015] Preferably, a filtering device is arranged between the centrifugal fan apparatus and the through hole. </p>
|
| 82 |
+
<p id="p-19" num="19">[0016] Preferably, the dust-collecting lid is further comprised of a roller with brush formed thereon.</p>
|
| 83 |
+
<p id="p-20" num="20">[0017] Preferably, a plurality of sliding grooves are formed on two <boundary-data type="line-number">25 </boundary-data>
|
| 84 |
+
side walls of the recess for enabling a plurality of protrusions formed on two sides of the box, corresponding to the two side wall of the recess, to abut against thereupon and thus enabling the box to slide in and out the recess. </p>
|
| 85 |
+
<p id="p-21" num="21">[0018] Yet, the present invention further provides a dust-collecting <boundary-data type="header">
|
| 86 |
+
<confidence value="8">4</confidence>
|
| 87 |
+
</boundary-data>
|
| 88 |
+
<page-break num="5"/>
|
| 89 |
+
module, which comprises: a case, a case, having a recess and a through hole channeling to the recess, and a side thereof being arranged with a groove hole channeling to the recess; a dust-collecting lid, connected to the groove hole; a box with a dust-collecting space, capable of being <boundary-data type="line-number">5 </boundary-data>
|
| 90 |
+
received in the recess for enabling the duct-collecting space to channel with the through hole and the groove hole; and a centrifugal fan apparatus, arranged upon the case, further comprising: a housing with an accommodating space formed therein, having an intake hole connected to the through hole and an outflow hole; an impeller, an impeller, arranging <boundary-data type="line-number">10 </boundary-data>
|
| 91 |
+
in the accommodating space while enabling the accommodating space to be divided into a first space and a second space by a virtual cross section passing the axial center of the impeller, referring as axial cross section hereinafter, whereas the first space is asymmetrical to the second space; </p>
|
| 92 |
+
<p id="p-22" num="22">and a driving device, connected to the impeller for driving the same to <boundary-data type="line-number">15 </boundary-data>
|
| 93 |
+
rotate. </p>
|
| 94 |
+
<p id="p-23" num="23">[0019] Other aspects and advantages of the present invention will become apparent from the following detailed description, taken in conjunction with the accompanying drawings, illustrating by way of example the principles of the present invention.</p>
|
| 95 |
+
<p id="p-24" num="24">
|
| 96 |
+
<boundary-data type="line-number">
|
| 97 |
+
<confidence value="88">20</confidence>
|
| 98 |
+
</boundary-data>
|
| 99 |
+
</p>
|
| 100 |
+
<heading id="h-6">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
|
| 101 |
+
<p id="p-25" num="25">[0020] FIG. <confidence value="2">1</confidence>
|
| 102 |
+
A is an exploded diagram illustrating a centrifugal fan apparatus according to a preferred embodiment of the invention. </p>
|
| 103 |
+
<p id="p-26" num="26">[0021] FIG. <confidence value="5">1</confidence>
|
| 104 |
+
B is a schematic diagram showing a centrifugal fan <boundary-data type="line-number">25 </boundary-data>
|
| 105 |
+
apparatus of the invention. </p>
|
| 106 |
+
<p id="p-27" num="27">[0022] FIG. 2A is a top view of an impeller having airfoil blades of signal-blade design according to the present invention.</p>
|
| 107 |
+
<boundary-data type="header">
|
| 108 |
+
<confidence value="8">5</confidence>
|
| 109 |
+
</boundary-data>
|
| 110 |
+
<p id="p-28" num="28">
|
| 111 |
+
<page-break num="6"/>
|
| 112 |
+
[0023] FIG. 2B is a top view of an impeller having airfoil blades of dual-blade design according to the present invention. </p>
|
| 113 |
+
<p id="p-29" num="29">[0024] FIG. 3A is a top view of a centrifugal fan apparatus according to the present invention.</p>
|
| 114 |
+
<p id="p-30" num="30">
|
| 115 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 116 |
+
[0025] FIG. 3B is a cross sectional view of a centrifugal fan apparatus according to the present invention. </p>
|
| 117 |
+
<p id="p-31" num="31">[0026] FIG. 4 is a P-Q curve diagram illustrating the comparison between a centrifugal fan apparatus of the invention and other conventional centrifugal fan apparatuses.</p>
|
| 118 |
+
<p id="p-32" num="32">
|
| 119 |
+
<boundary-data type="line-number">10 </boundary-data>
|
| 120 |
+
[0027] FIG. 5 is a schematic diagram showing a dust-collecting module according to a preferred embodiment of the invention. </p>
|
| 121 |
+
<p id="p-33" num="33">[0028] FIG. 6A is a schematic diagram showing a case of a ducts- collecting module according to a preferred embodiment of the invention.</p>
|
| 122 |
+
<p id="p-34" num="34">[0029] FIG. 6B is an exploded diagram depicting a case of a ducts- <boundary-data type="line-number">15 </boundary-data>
|
| 123 |
+
collecting module according to a preferred embodiment of the invention. </p>
|
| 124 |
+
<p id="p-35" num="35">[0030] FIG. 7 is a schematic diagram showing a dust-collect lid according to a preferred embodiment of the invention.</p>
|
| 125 |
+
<heading id="h-7">DESCRIPTION OF THE PREFERRED EMBODIMENT</heading>
|
| 126 |
+
<p id="p-36" num="36">
|
| 127 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 128 |
+
[0031] For your esteemed members of reviewing committee to further understand and recognize the fulfilled functions and structural characteristics of the invention, several preferable embodiments cooperating with detailed description are presented as the follows. </p>
|
| 129 |
+
<boundary-data type="header">
|
| 130 |
+
<confidence value="8">6</confidence>
|
| 131 |
+
</boundary-data>
|
| 132 |
+
<p id="p-37" num="37">
|
| 133 |
+
<page-break num="7"/>
|
| 134 |
+
[0032] Please refer to FIG. <confidence value="2">1</confidence>
|
| 135 |
+
A and FIG. <confidence value="686">1B,</confidence>
|
| 136 |
+
which are respectively an exploded view and a pictorial view of a centrifugal fan apparatus according to a preferred embodiment of the invention. As seen in FIG. <confidence value="28">1A</confidence>
|
| 137 |
+
and FIG. <confidence value="686">1B,</confidence>
|
| 138 |
+
the centrifugal fan apparatus <part-num-ref name="centrifugal fan apparatus">1</part-num-ref>
|
| 139 |
+
is comprised of a housing <part-num-ref name="housing">10,</part-num-ref>
|
| 140 |
+
<boundary-data type="line-number">5 </boundary-data>
|
| 141 |
+
an impeller <part-num-ref name="impeller">11</part-num-ref>
|
| 142 |
+
and a driving device <part-num-ref name="driving device">14,</part-num-ref>
|
| 143 |
+
in which the housing is further composed of a top shell <part-num-ref name="top shell">101</part-num-ref>
|
| 144 |
+
and a bottom shell <part-num-ref name="bottom shell">102.</part-num-ref>
|
| 145 |
+
Apart from the helical casing, as that disclosed in EPC Pat. No. EP<confidence value="4">0</confidence>
|
| 146 |
+
943808, the axial cross section of an accommodating space formed by the assembling of the top shell <part-num-ref name="top shell">101</part-num-ref>
|
| 147 |
+
and the bottom shell <part-num-ref name="bottom shell">102</part-num-ref>
|
| 148 |
+
is shaped as a disc, which is <boundary-data type="line-number">10 </boundary-data>
|
| 149 |
+
different from those of prior arts, whereas an intake hole <part-num-ref name="intake hole">1011</part-num-ref>
|
| 150 |
+
is formed at the center of the top shell 101; and an outflow hole <part-num-ref name="outflow hole">1021</part-num-ref>
|
| 151 |
+
is formed at a side of the bottom shell <part-num-ref name="bottom shell">102.</part-num-ref>
|
| 152 |
+
</p>
|
| 153 |
+
<p id="p-38" num="38">[0033] Moreover, the impeller <part-num-ref name="impeller">11</part-num-ref>
|
| 154 |
+
is disposed inside the accommodating space, which is composed of: a back panel 110; a <boundary-data type="line-number">15 </boundary-data>
|
| 155 |
+
plurality of blades <part-num-ref name="plurality of blades">113,</part-num-ref>
|
| 156 |
+
arranged on the back panel 110; and a top panel <part-num-ref name="top panel">112,</part-num-ref>
|
| 157 |
+
arranged over the plural blades <part-num-ref name="plural blades">113.</part-num-ref>
|
| 158 |
+
The plural blades <part-num-ref name="plural blades">113</part-num-ref>
|
| 159 |
+
can be arranged on the back panel <part-num-ref name="back panel">111</part-num-ref>
|
| 160 |
+
by manner as those illustrated in FIG. 2A and FIG. 2B. However, it is only used as illustration and is not limited thereby. In FIG. 2A, the plural blades <part-num-ref name="plural blades">113</part-num-ref>
|
| 161 |
+
are radially arranged while each <boundary-data type="line-number">20 </boundary-data>
|
| 162 |
+
blade <part-num-ref name="are radially arranged while each blade">113</part-num-ref>
|
| 163 |
+
used in the impeller <part-num-ref name="impeller">11</part-num-ref>
|
| 164 |
+
is an airfoil blade of signal-blade design. </p>
|
| 165 |
+
<p id="p-39" num="39">In FIG. 2<confidence value="5">B</confidence>
|
| 166 |
+
, the plural blades 1<confidence value="885">13a</confidence>
|
| 167 |
+
, 113b are radially arranged while each blade used in the impeller <part-num-ref name="impeller">
|
| 168 |
+
<confidence value="5">1</confidence>
|
| 169 |
+
</part-num-ref>
|
| 170 |
+
<confidence value="5">l</confidence>
|
| 171 |
+
a are two offset airfoil blades 113a, 113b, i.e. </p>
|
| 172 |
+
<p id="p-40" num="40">blade of dual-blade design. In addition, the driving device <part-num-ref name="driving device">14</part-num-ref>
|
| 173 |
+
is connected to the impeller <part-num-ref name="impeller">11</part-num-ref>
|
| 174 |
+
by a pin <part-num-ref name="pin">12</part-num-ref>
|
| 175 |
+
and an interfacing panel <part-num-ref name="interfacing panel">13</part-num-ref>
|
| 176 |
+
so that the <boundary-data type="line-number">25 </boundary-data>
|
| 177 |
+
impeller <part-num-ref name="impeller">11</part-num-ref>
|
| 178 |
+
can be driven to rotate by the driving device <part-num-ref name="driving device">14.</part-num-ref>
|
| 179 |
+
</p>
|
| 180 |
+
<p id="p-41" num="41">[0034] Please refer to FIG. 3A, which is a top view of a centrifugal fan apparatus according to the present invention. In FIG. 3A, the manner that the impeller <part-num-ref name="impeller">11</part-num-ref>
|
| 181 |
+
is being arranged inside the housing <part-num-ref name="housing">10</part-num-ref>
|
| 182 |
+
is illustrated. As the axial cross section of the accommodating space of the housing <part-num-ref name="housing">10</part-num-ref>
|
| 183 |
+
is <boundary-data type="line-number">30 </boundary-data>
|
| 184 |
+
shaped like a disc, an airflow channel <part-num-ref name="airflow channel">103</part-num-ref>
|
| 185 |
+
of uniform width D can be formed between a rim of the impeller <part-num-ref name="impeller">11</part-num-ref>
|
| 186 |
+
and a side wall of the housing <part-num-ref name="housing">10.</part-num-ref>
|
| 187 |
+
</p>
|
| 188 |
+
<p id="p-42" num="42">Please refer to FIG. 3<confidence value="5">B</confidence>
|
| 189 |
+
, which is a cross sectional view of a centrifugal <boundary-data type="header">
|
| 190 |
+
<confidence value="8">7</confidence>
|
| 191 |
+
</boundary-data>
|
| 192 |
+
<page-break num="8"/>
|
| 193 |
+
fan apparatus according to the present invention. In FIG. 3<confidence value="5">B</confidence>
|
| 194 |
+
, the accommodating space is being divided into a first space A<confidence value="2">l</confidence>
|
| 195 |
+
and a second space A2 by a virtual cross section <part-num-ref name="virtual cross section">8</part-num-ref>
|
| 196 |
+
passing the axial center of the impeller <part-num-ref name="impeller">11</part-num-ref>
|
| 197 |
+
while enabling the first space A<confidence value="2">l</confidence>
|
| 198 |
+
to be asymmetrical to the <boundary-data type="line-number">5 </boundary-data>
|
| 199 |
+
second space A2. As seen in FIG. <confidence value="5">1</confidence>
|
| 200 |
+
B and FIG. 3<confidence value="5">B</confidence>
|
| 201 |
+
, a helical airflow channel <part-num-ref name="helical airflow channel">1022</part-num-ref>
|
| 202 |
+
is formed in the second space A2 by the bottom shell <part-num-ref name="bottom shell">102</part-num-ref>
|
| 203 |
+
whereas the sectional area of the helical airflow channel <part-num-ref name="helical airflow channel">1022</part-num-ref>
|
| 204 |
+
is increasing progressively from the beginning thereof to the outflow hole <part-num-ref name="outflow hole">1021.</part-num-ref>
|
| 205 |
+
In FIG. 3<confidence value="5">B</confidence>
|
| 206 |
+
, two sections 1022a, 1022b are shown whereas the <boundary-data type="line-number">10 </boundary-data>
|
| 207 |
+
section 1022a is at a position near the outflow hole <part-num-ref name="outflow hole">1021</part-num-ref>
|
| 208 |
+
and the section 1022b is at a position near the beginning thereof, in which the area of the section 1022a is larger than that of the section 1022b. </p>
|
| 209 |
+
<p id="p-43" num="43">[0035] As there will be no obvious casing tongue by the housing design of the invention, most of the air flow will be discharged from the <boundary-data type="line-number">15 </boundary-data>
|
| 210 |
+
portion of the airflow channel under the impeller <part-num-ref name="impeller">11</part-num-ref>
|
| 211 |
+
so that no backflow will be generated between the intake and outflow and thus noise is reduced. Please refer to FIG. 4, which is a P-Q curve diagram illustrating the comparison between a centrifugal fan apparatus of the invention and other conventional centrifugal fan apparatuses. In FIG. 4, curve <part-num-ref name="invention and other conventional centrifugal fan apparatuses. In FIG. 4, curve">90</part-num-ref>
|
| 212 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 213 |
+
represents the P-Q curve of a centrifugal fan apparatus of the invention, marked as MSL II; curve <part-num-ref name="invention, marked as MSL II; curve">91</part-num-ref>
|
| 214 |
+
represent the P-Q curve of a centrifugal fan apparatus disclosed in TW Pat. No. M246471, marked as RV-10; and curve <part-num-ref name="centrifugal fan apparatus disclosed in TW Pat. No. M246471, marked as RV-10; and curve">92</part-num-ref>
|
| 215 |
+
represent the P-Q curve of a centrifugal fan apparatus disclosed in EP<confidence value="4">0</confidence>
|
| 216 |
+
943808, marked as Karcher; and curve <part-num-ref name="centrifugal fan apparatus disclosed in EP0943808, marked as Karcher; and curve">93</part-num-ref>
|
| 217 |
+
represent the P-Q curve <boundary-data type="line-number">25 </boundary-data>
|
| 218 |
+
of a centrifugal fan apparatus of a current product, i.e. I-robot. As seen in FIG. 4, the performance of the centrifugal fan device of the invention is better than those other conventional centrifugal fan apparatuses, as the curve <part-num-ref name="curve">90</part-num-ref>
|
| 219 |
+
is outperforming the curves <part-num-ref name="curves">91,</part-num-ref>
|
| 220 |
+
<part-num-ref name="curves 91,">92,</part-num-ref>
|
| 221 |
+
<part-num-ref name="curves 91, 92,">93.</part-num-ref>
|
| 222 |
+
In addition, the overall noise of the invention is about the same as that of Karcher, but is much <boundary-data type="line-number">30 </boundary-data>
|
| 223 |
+
better than that of RV-10 by about <confidence value="66">10</confidence>
|
| 224 |
+
dB. Hence, the centrifugal fan apparatus of the invention is considered to be a low noise, high flow rate centrifugal fan apparatus. </p>
|
| 225 |
+
<boundary-data type="header">
|
| 226 |
+
<confidence value="8">8</confidence>
|
| 227 |
+
</boundary-data>
|
| 228 |
+
<p id="p-44" num="44">
|
| 229 |
+
<page-break num="9"/>
|
| 230 |
+
[0036] As the aforesaid centrifugal fan apparatus of the invention is capable of providing high flow rate while maintaining high pressure difference, the centrifugal fan apparatus is suitable to be adapted for a duct-collecting module. Please refer to FIG. 5, which is a schematic <boundary-data type="line-number">5 </boundary-data>
|
| 231 |
+
diagram showing a dust-collecting module according to a preferred embodiment of the invention. The duct-collecting module <part-num-ref name="duct-collecting module">2</part-num-ref>
|
| 232 |
+
is composed of a centrifugal fan apparatus <part-num-ref name="centrifugal fan apparatus">20</part-num-ref>
|
| 233 |
+
and a dust-collecting case <part-num-ref name="dust-collecting case">21,</part-num-ref>
|
| 234 |
+
in which the centrifugal fan apparatus <part-num-ref name="centrifugal fan apparatus">20</part-num-ref>
|
| 235 |
+
can be the one disclosed hereinbefore. </p>
|
| 236 |
+
<p id="p-45" num="45">Please refer to FIG. 6A and FIG. 6<confidence value="5">B</confidence>
|
| 237 |
+
, which are respectively a schematic <boundary-data type="line-number">10 </boundary-data>
|
| 238 |
+
diagram and an exploded diagram showing a case of a ducts-collecting module according to a preferred embodiment of the invention. The ducts- collecting case <part-num-ref name="ducts- collecting case">21</part-num-ref>
|
| 239 |
+
further comprises: a case <part-num-ref name="case">210,</part-num-ref>
|
| 240 |
+
having a recess <part-num-ref name="recess">2104</part-num-ref>
|
| 241 |
+
and a through hole <part-num-ref name="through hole">2101</part-num-ref>
|
| 242 |
+
channeling to the recess 2104; a dust-collecting lid 212; and a box 211; wherein, a side of the case <part-num-ref name="case">210</part-num-ref>
|
| 243 |
+
is arranged with a <boundary-data type="line-number">15 </boundary-data>
|
| 244 |
+
groove hole <part-num-ref name="groove hole">2102</part-num-ref>
|
| 245 |
+
channeling to the recess 2104; the through hole is channeled to the intake hole of the centrifugal fan apparatus <part-num-ref name="centrifugal fan apparatus">20</part-num-ref>
|
| 246 |
+
while an extractable filtering device is arranged between the through hole <part-num-ref name="through hole">2102</part-num-ref>
|
| 247 |
+
and the centrifugal fan apparatus <part-num-ref name="centrifugal fan apparatus">20.</part-num-ref>
|
| 248 |
+
</p>
|
| 249 |
+
<p id="p-46" num="46">[0037] The box <part-num-ref name="box">211</part-num-ref>
|
| 250 |
+
is formed with a dust-collecting space <part-num-ref name="dust-collecting space">2110,</part-num-ref>
|
| 251 |
+
<boundary-data type="line-number">20 </boundary-data>
|
| 252 |
+
which is capable of being received in the recess <part-num-ref name="recess">2104</part-num-ref>
|
| 253 |
+
as a drawer while enabling the duct-collecting space to channel with the through hole <part-num-ref name="through hole">2102</part-num-ref>
|
| 254 |
+
and the groove hole <part-num-ref name="groove hole">2101.</part-num-ref>
|
| 255 |
+
By which, a duct-collecting bag received in the duct-collecting space can be easily accessed and replaced as the box <part-num-ref name="box">211</part-num-ref>
|
| 256 |
+
can be easily pulled out of the recess <part-num-ref name="recess">2104.</part-num-ref>
|
| 257 |
+
Please refer to FIG. 7, which is <boundary-data type="line-number">25 </boundary-data>
|
| 258 |
+
a schematic diagram showing a dust-collect lid according to a preferred embodiment of the invention. As seen in FIG. 7, an intake <part-num-ref name="intake">2121</part-num-ref>
|
| 259 |
+
and an outflow <part-num-ref name="outflow">2120</part-num-ref>
|
| 260 |
+
are formed on the dust-collecting lid <part-num-ref name="dust-collecting lid">212</part-num-ref>
|
| 261 |
+
while the intake <part-num-ref name="intake">2121</part-num-ref>
|
| 262 |
+
is channeled with the groove hole <part-num-ref name="groove hole">2101</part-num-ref>
|
| 263 |
+
of the case <part-num-ref name="case">210.</part-num-ref>
|
| 264 |
+
In addition, a roller, preferred formed with brush, can be arranged at the intake <part-num-ref name="intake">2121</part-num-ref>
|
| 265 |
+
<boundary-data type="line-number">30 </boundary-data>
|
| 266 |
+
of the dust-collecting lid <part-num-ref name="dust-collecting lid">212.</part-num-ref>
|
| 267 |
+
</p>
|
| 268 |
+
<p id="p-47" num="47">[0038] In this preferred embodiment of the invention, for enabling air flow to flow smoothly in its airflow channel, the intake hole of its <boundary-data type="header">
|
| 269 |
+
<confidence value="8">9</confidence>
|
| 270 |
+
</boundary-data>
|
| 271 |
+
<page-break num="10"/>
|
| 272 |
+
centrifugal fan apparatus is connected to the dust-collecting case <part-num-ref name="dust-collecting case">212</part-num-ref>
|
| 273 |
+
through the dust-collecting lid <part-num-ref name="dust-collecting lid">212</part-num-ref>
|
| 274 |
+
while arranging the opening of the groove hole <part-num-ref name="groove hole">2101</part-num-ref>
|
| 275 |
+
of the case <part-num-ref name="case">210</part-num-ref>
|
| 276 |
+
at a side thereof instead of at the bottom thereof, by which the airflow channel is not twist for the consideration of <boundary-data type="line-number">5 </boundary-data>
|
| 277 |
+
improving dust-collecting efficiency and thus noise is reduced. Moreover, as the case <part-num-ref name="case">210</part-num-ref>
|
| 278 |
+
and the box <part-num-ref name="box">211</part-num-ref>
|
| 279 |
+
are structured as a drawer that the box <part-num-ref name="box">211</part-num-ref>
|
| 280 |
+
can be pull out of the case easily, not only it is good for noise reduction, but also it is good for dust cleaning and filer replacing. </p>
|
| 281 |
+
<p id="p-48" num="48">[0039] To sum up, the invention can provide a dust-collecting module <boundary-data type="line-number">10 </boundary-data>
|
| 282 |
+
capable of utilizing it specially designed casing to assemble a low noise, high flow rate centrifugal fan apparatus so as to be able to perform a dust- collecting operation while maintaining the smoothness of airflow in the centrifugal fan apparatus. </p>
|
| 283 |
+
<p id="p-49" num="49">[0040] While the preferred embodiment of the invention has been set <boundary-data type="line-number">15 </boundary-data>
|
| 284 |
+
forth for the purpose of disclosure, modifications of the disclosed embodiment of the invention as well as other embodiments thereof may occur to those skilled in the art. Accordingly, the appended claims are intended to cover all embodiments which do not depart from the spirit and scope of the invention. </p>
|
| 285 |
+
<boundary-data type="header">
|
| 286 |
+
<confidence value="88">10</confidence>
|
| 287 |
+
</boundary-data>
|
| 288 |
+
</description>
|
| 289 |
+
</us-patent-application>
|
| 290 |
+
|
applicant/11538824.xml
ADDED
|
@@ -0,0 +1,37 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>11538824</doc-number>
|
| 8 |
+
<date>2010-08-23</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<p id="p-1" num="1">Amendments to the Specification <part-num-ref name="Specification">(1)</part-num-ref>
|
| 14 |
+
Please replace paragraph [0024] on pages 9-10 of the specification with the following amended paragraph: </p>
|
| 15 |
+
<p id="p-2" num="2">[0024] One embodiment of the invention, the permanent hydrophilic coating comprising nanoparticles comprising <part-num-ref name="permanent hydrophilic coating comprising nanoparticles comprising">10</part-num-ref>
|
| 16 |
+
to <part-num-ref name="to">90</part-num-ref>
|
| 17 |
+
weight percent inorganic structures, <part-num-ref name="weight percent inorganic structures,">5</part-num-ref>
|
| 18 |
+
to <part-num-ref name="to">70</part-num-ref>
|
| 19 |
+
weigh percent hydrophilic side chains, and <part-num-ref name="weigh percent hydrophilic side chains, and">0</part-num-ref>
|
| 20 |
+
to <part-num-ref name="to">50</part-num-ref>
|
| 21 |
+
weight percent organic side chains having at least one functional group. </p>
|
| 22 |
+
<p id="p-3" num="3">In one embodiment of the invention the hydrophilic side chains that are amino, sulfonate, sulfate, sulfite, sulfona<confidence value="8">m</confidence>
|
| 23 |
+
ide, sulfoxide, carboxylate, polyol, polyether, phosphate, or phosphonate groups. </p>
|
| 24 |
+
<p id="p-4" num="4">(2) Please replace paragraph [0036] on page 13 of the specification with the following amended paragraph:</p>
|
| 25 |
+
<p id="p-5" num="5">
|
| 26 |
+
<confidence value="5">[</confidence>
|
| 27 |
+
0036] In one embodiment of the invention the second coating material includes a Si-O group and an Si-R group wherein R includes a saturated or unsaturated carbon chain, and wherein the molar ratio of Si-R groups to Si-O groups ranges from 1/8 to <confidence value="66">1/</confidence>
|
| 28 |
+
2 [[<confidence value="665">/2]</confidence>
|
| 29 |
+
], preferably <confidence value="66">1/</confidence>
|
| 30 |
+
4 [[<confidence value="2">%</confidence>
|
| 31 |
+
]] to 1/2. In another embodiment of the invention the second coating material further includes hydroxyl groups to improve the hydrophilicity of the coating. </p>
|
| 32 |
+
<p id="p-6" num="6">
|
| 33 |
+
<confidence value="8">2</confidence>
|
| 34 |
+
</p>
|
| 35 |
+
</description>
|
| 36 |
+
</us-patent-application>
|
| 37 |
+
|
applicant/11539522.xml
ADDED
|
@@ -0,0 +1,39 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>11539522</doc-number>
|
| 8 |
+
<date>2009-06-05</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<heading id="h-1">PATENT</heading>
|
| 14 |
+
<p id="p-1" num="1">Amendments to the Specification:</p>
|
| 15 |
+
<p id="p-2" num="2">Please replace paragraph [0021] with the following amended paragraph (Added matter is underlined and deleted matter is shown using <confidence value="222222222222288">strikethfough):</confidence>
|
| 16 |
+
</p>
|
| 17 |
+
<p id="p-3" num="3">[0021<confidence value="5">]</confidence>
|
| 18 |
+
At a first block <part-num-ref name="first block">201,</part-num-ref>
|
| 19 |
+
it is queried whether PSF is zero. If so, operation is in full power mode as indicated at block <part-num-ref name="first block 201, it is queried whether PSF is zero. If so, operation is in full power mode as indicated at block">203</part-num-ref>
|
| 20 |
+
in which all prioritized tools remain fully active. </p>
|
| 21 |
+
<p id="p-4" num="4">Operation remains fully active while P<confidence value="68">-S</confidence>
|
| 22 |
+
T PSF = 0. When P<confidence value="68">-S</confidence>
|
| 23 |
+
T PSF increases above zero, operation follows any one of several paths depending upon the value of P<confidence value="68">-S</confidence>
|
| 24 |
+
T PSF. When <confidence value="868">P-S</confidence>
|
| 25 |
+
T PSF = <part-num-ref name="value of P-ST PSF. When P-ST PSF =">1</part-num-ref>
|
| 26 |
+
as indicated at block <part-num-ref name="as indicated at block">205,</part-num-ref>
|
| 27 |
+
then the prediction error adjustment circuit <part-num-ref name="prediction error adjustment circuit">107</part-num-ref>
|
| 28 |
+
conducts prediction error adjustment as indicated at block <part-num-ref name="conducts prediction error adjustment as indicated at block">207.</part-num-ref>
|
| 29 |
+
As further described below, during prediction error adjustment, the prediction error adjustment circuit <part-num-ref name="prediction error adjustment circuit">107</part-num-ref>
|
| 30 |
+
adjusts the PEA signal to control the level of sub-pixel (half and quarter) interpolation based on the values of PSF, QP and the BF signal to reduce computation complexity. </p>
|
| 31 |
+
<p id="p-5" num="5">Although PSF is no longer zero, since it is only one and thus relatively low, more information is selected for sub-pixel interpolation as compared with higher PSF values and further depending upon the values of QP and BF. Operation loops back to block <part-num-ref name="values of QP and BF. Operation loops back to block">201</part-num-ref>
|
| 32 |
+
and continues to loop back to blocks <part-num-ref name="and continues to loop back to blocks">205</part-num-ref>
|
| 33 |
+
and <part-num-ref name="and">207</part-num-ref>
|
| 34 |
+
as long as PSF = <part-num-ref name="as long as PSF =">1.</part-num-ref>
|
| 35 |
+
In this manner, the value of PSF is constantly monitored since it may change in a dynamic coding environment. </p>
|
| 36 |
+
<p id="p-6" num="6">- Page 2 - </p>
|
| 37 |
+
</description>
|
| 38 |
+
</us-patent-application>
|
| 39 |
+
|
applicant/11578424.xml
ADDED
|
@@ -0,0 +1,144 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>11578424</doc-number>
|
| 8 |
+
<date>2006-10-13</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<p id="p-1" num="1">
|
| 14 |
+
<confidence value="8854">11/5</confidence>
|
| 15 |
+
784<confidence value="68">24</confidence>
|
| 16 |
+
<confidence value="88888888">P804922/</confidence>
|
| 17 |
+
<confidence value="88">WO</confidence>
|
| 18 |
+
<confidence value="88">/1</confidence>
|
| 19 |
+
<confidence value="4">I</confidence>
|
| 20 |
+
AP17Rec<confidence value="58">'d</confidence>
|
| 21 |
+
<confidence value="2222222">PCTIPTO</confidence>
|
| 22 |
+
<confidence value="88">13</confidence>
|
| 23 |
+
<confidence value="68">OC</confidence>
|
| 24 |
+
T <part-num-ref name="OCT">2<confidence value="66">00</confidence>
|
| 25 |
+
</part-num-ref>
|
| 26 |
+
DaimlerChrysler AG Method for actuating a vehicle occupant protection means in a vehicle and a vehicle occupant protection system The invention relates to a method for actuating a vehicle occupant protection means in a vehicle according to the preamble of patent claim <part-num-ref name="preamble of patent claim">1,</part-num-ref>
|
| 27 |
+
and to a vehicle occupant protection system for carrying out the method according to the preamble of patent claim <part-num-ref name="preamble of patent claim">10<confidence value="8">.</confidence>
|
| 28 |
+
</part-num-ref>
|
| 29 |
+
</p>
|
| 30 |
+
<p id="p-2" num="2">In addition to the contemporary restraint means such as an airbag and a seatbelt with a seatbelt pretensioner there are a series of other controllable vehicle occupant protection means in vehicles which bring about a restraining effect and/or an energy-absorbing effect in order to protect a vehicle occupant in the event of a collision. Examples of such vehicle occupant protection means are displaceable impact elements, cushions and headrests whose size, hardness, shape and position can be changed by means of an actuation system. In addition to these vehicle occupant protection means it is possible to provide further controllable protection means for avoiding the severity of an accident, which protection means reduce the consequences of an accident for a vehicle occupant by positioning the vehicle occupant, i.e. the vehicle occupant is moved into a position which is favorable in terms of an accident. Means for positioning the vehicle occupant are, for example, an electric seat adjustment system, a head rest adjustment system, seat belt pretensioners and movable upholstered elements.</p>
|
| 31 |
+
<p id="p-3" num="3">When vehicle occupant protection means are actuated in order to avoid the consequences of the accident in road traffic it is possible to distinguish between preventative measures which are taken before an <page-break num="2"/>
|
| 32 |
+
<boundary-data type="header">P804922/WO/<confidence value="4">l</confidence>
|
| 33 |
+
- 2 - </boundary-data>
|
| 34 |
+
accident, and acute measures which are taken after an accident has been detected. The invention relates to actuation of a protection means as a preventative measure, i.e. as a preventative protective measure. </p>
|
| 35 |
+
<p id="p-4" num="4">DE 101 <part-num-ref name="">21</part-num-ref>
|
| 36 |
+
<part-num-ref name="">386</part-num-ref>
|
| 37 |
+
C<confidence value="5">1</confidence>
|
| 38 |
+
has disclosed a method for actuating a reversible vehicle occupant protection means in a motor vehicle having a driving state sensor system and a reversible vehicle occupant protection means. The reversible vehicle occupant protection means can be triggered before the time of a collision and thus moved into an operative position. For this purpose the driving state data is monitored with respect to a state of emergency braking, and when the state of emergency braking is detected the vehicle occupant protection system which comprises the vehicle occupant protection means is actuated. In addition, the state of oversteering and the state of understeering are determined by a data processing device. If the state of emergency braking and/or the state of oversteering and/or the state of understeering are detected by the data processing device, the reversible vehicle occupant protection system is actuated. </p>
|
| 39 |
+
<p id="p-5" num="5">DE 100 <part-num-ref name="">47</part-num-ref>
|
| 40 |
+
<part-num-ref name="">048</part-num-ref>
|
| 41 |
+
Al has disclosed a method for automatically setting the speed in a vehicle. Here, the distance and the relative speed between the vehicle and an obstacle are served by sensor means and used as the basis for calculating a braking torque or drive torque to be produced independently of the driver. If the distance from the vehicle drops below a minimum value, braking takes place automatically. There is provision here that in the case of automatic braking the deceleration of the vehicle follows a set point deceleration which is composed additively from three deceleration components which are detected according to different rules. </p>
|
| 42 |
+
<p id="p-6" num="6">
|
| 43 |
+
<page-break num="3"/>
|
| 44 |
+
P804922/WO/<confidence value="4">1</confidence>
|
| 45 |
+
- 3 - DE <part-num-ref name="- DE">197</part-num-ref>
|
| 46 |
+
<part-num-ref name="">38</part-num-ref>
|
| 47 |
+
<part-num-ref name="">690</part-num-ref>
|
| 48 |
+
Al has disclosed a method for controlling the brake system of a vehicle. In addition to the values predefined by the driver, braking force is increased or decreased at the wheel brakes, with an automatic braking process being triggered when at least one signal, which represents the activation of the brake control element, exceeds at least one predefined threshold value. The at least one threshold value is changed as a function of at least one operational variable which indicates a hazard situation, the triggering of the automatic braking process becoming more sensitive as the hazard potential increases. There is provision here for the at least one operational variable to be a variable which is derived from the distance from an obstacle which is located in front of the vehicle. </p>
|
| 49 |
+
<p id="p-7" num="7">DE 101 <part-num-ref name="">21</part-num-ref>
|
| 50 |
+
<part-num-ref name="">956</part-num-ref>
|
| 51 |
+
C<confidence value="5">1</confidence>
|
| 52 |
+
discloses a method for actuating a vehicle occupant protection system for a vehicle in which, when an obstacle is detected in front of the vehicle, a braking deceleration which is required to bring the vehicle to a standstill still in front of the obstacle is determined, in which method also the determined necessary braking deceleration is compared with a maximum possible braking deceleration which is dependent on weather conditions, and in which method a vehicle occupant protection means is activated as soon as the necessary braking deceleration has exceeded the maximum possible braking deceleration. </p>
|
| 53 |
+
<p id="p-8" num="8">The object of the present invention is to make available a method for actuating a vehicle occupant protection means with which the functionality of vehicle occupant protection means is extended. The invention is also based on the object of specifying a vehicle occupant protection system for carrying out the method.</p>
|
| 54 |
+
<boundary-data type="header">P804922/WO/<confidence value="4">l</confidence>
|
| 55 |
+
- 4 - </boundary-data>
|
| 56 |
+
<p id="p-9" num="9">
|
| 57 |
+
<page-break num="4"/>
|
| 58 |
+
The object is achieved by means of the features of patent claim <part-num-ref name="features of patent claim">1</part-num-ref>
|
| 59 |
+
or by means of the features of patent claim <part-num-ref name="features of patent claim">10.</part-num-ref>
|
| 60 |
+
</p>
|
| 61 |
+
<p id="p-10" num="10">Advantageous refinements and developments of the invention emerge from the subclaims.</p>
|
| 62 |
+
<p id="p-11" num="11">According to the invention, in a method of the type mentioned at the beginning the distance between the vehicle and an obstacle is sensed, a braking deceleration which is necessary to avoid a collision with the obstacle is determined and the determined braking deceleration is used to discover whether a predefined event has occurred, and when the event occurs the vehicle occupant protection means is actuated. The necessary braking deceleration is determined here, or the determined necessary braking deceleration is evaluated with respect to the occurrence of the predefined event, only if a driver of the vehicle has initiated a braking operation by activating a brake control element. The actuation of the vehicle occupant protection means triggers the latter or activates it for the purpose of triggering, i.e. places it in a triggerable state, in which case triggering it places it in an operative state in which it protects the vehicle occupants, i.e. reduces the loading on the vehicle occupants in the case of a collision.</p>
|
| 63 |
+
<p id="p-12" num="12">The necessary braking deceleration can be sensed by sensing the distance from an object or obstacle and by sensing the absolute speed of the vehicle. This is advantageous in particular in the case of a stationary obstacle. Alternatively or additionally, the change in the distance of the vehicle from the obstacle or object, for example a vehicle traveling in front or the relative speed from the object can be determined therefrom. The braking deceleration which is necessary <page-break num="5"/>
|
| 64 |
+
P804922/W<confidence value="682">O/1</confidence>
|
| 65 |
+
- <part-num-ref name="braking deceleration which is necessary P804922/WO/1 -">5</part-num-ref>
|
| 66 |
+
- to avoid a collision can be determined therefrom. </p>
|
| 67 |
+
<p id="p-13" num="13">The braking deceleration is preferably determined in such a way that the vehicle would come to a standstill at a safety distance of, for example, 0.5 m from the obstacle if the physical peripheral conditions, for example a dry carriageway, permitted. The advantage of the method comes into play in particular if the physical peripheral conditions do not allow the vehicle to be braked in such a way that a collision is prevented. This may be the case in particular on a wet carriageway or on a carriageway which is slippery due to snow or ice. In such cases it is nevertheless possible for a collision to occur even though sufficient braking deceleration has been determined.</p>
|
| 68 |
+
<p id="p-14" num="14">Furthermore, a collision may occur even if there are control interventions by the driver who attempts to avoid an obstacle and inadvertently heads for another obstacle while making the avoidance maneuver.</p>
|
| 69 |
+
<p id="p-15" num="15">The predefined event is preferably assessed as having occurred if it is no longer possible to avoid a collision with the obstacle owing to the necessary braking deceleration. The vehicle occupant protection means is thus actuated if the result of the determined necessary braking deceleration is that a collision can no longer be prevented. If, for example, another vehicle unexpectedly intersects the direction of travel, it may no longer be possible to bring the vehicle to a standstill in order to prevent a collision. This can be determined by reference to the detected distance from the obstacle and with the knowledge of the maximum possible braking deceleration of the vehicle. In order to nevertheless protect the vehicle occupants in the event of an imminent collision, in such a case the vehicle occupant protection means can be actuated. A reversible vehicle occupant protection means is a means whose purpose is <page-break num="6"/>
|
| 70 |
+
<boundary-data type="header">P804922/WO/<confidence value="4">l</confidence>
|
| 71 |
+
- 6 - </boundary-data>
|
| 72 |
+
to reduce the load on a vehicle occupant in the case of a collision, it being possible to place the protection means repeatedly in an operative state from the initial state, and to return said means to its initial state from the operative state. An electric seat adjustment device and/or an electric adjustment device for vehicle openings and/or a reversible seatbelt pretensioner and/or an electrically adjustable impact protection device can be provided as vehicle occupant protection means. An electric seat adjustment device and electric adjustment devices for vehicle openings such as, for example, the electrically adjustable sun roof and electrically adjustable window lifter, are present at least in certain cases in contemporary vehicles and can additionally be utilized to precondition the vehicle occupants or the vehicle at low cost. All the electrically adjustable vehicle occupant protection means have the advantage that the energy supply via the on-board electrical system is simple in design, in particular electro-motor drives make it possible to reverse the vehicle occupant protection means easily. </p>
|
| 73 |
+
<p id="p-16" num="16">As a result it is possible to trigger the protection means, while taking into account their effect on drivers and vehicle occupants, even if a hazardous situation is determined which does not have a high degree of probability of leading to a collision but rather only a certain predefinable probability of leading to a collision.</p>
|
| 74 |
+
<p id="p-17" num="17">In one refinement of the method it is possible to provide for the predefined event to be assessed as having occurred if the necessary braking deceleration is above a first threshold value. The vehicle occupant protection means is thus actuated if the necessary braking deceleration is above the predefined first threshold value. This threshold value of the necessary braking deceleration is an indication of how probable a collision is. If a very high necessary braking <page-break num="7"/>
|
| 75 |
+
P804922/WO/<confidence value="4">l</confidence>
|
| 76 |
+
- <part-num-ref name="very high necessary braking P804922/WO/l -">7</part-num-ref>
|
| 77 |
+
- deceleration, for example greater than 0.7 G (braking deceleration expressed as a multiple of G, the acceleration due to gravity) is correspondingly determined, this is an indication that a collision could occur. The situation can therefore be defined as an event at which the vehicle occupant protection means is actuated in order to place it in an operative state. </p>
|
| 78 |
+
<p id="p-18" num="18">In a method variant it is possible to provide for the braking deceleration which is initiated by a driver to be determined and compared with the determined necessary braking deceleration and for the vehicle occupant protection means to be actuated or activated if the difference between the braking decelerations is above a predefined second threshold value. If, for example, it is determined that the braking deceleration initiated by the driver is 0.2 G, the necessary braking deceleration to bring the vehicle to a standstill at a distance from an obstacle is however 0.8 G, the difference between the braking decelerations is 0.6 G.</p>
|
| 79 |
+
<p id="p-19" num="19">If a second threshold value of, for example, 0.4 G is predefined for the difference, the vehicle occupant protection means is actuated since a collision is to be feared if the driver does not increase the braking deceleration. The exceeding of the difference can be defined as a further event during which the vehicle occupant protection means is actuated.</p>
|
| 80 |
+
<p id="p-20" num="20">In one preferred development of the method, it is possible to provide for the braking force or the braking pressure to be increased automatically for target braking if the difference between the braking decelerations exceeds the second threshold value.</p>
|
| 81 |
+
<p id="p-21" num="21">Target braking is understood here to be braking at a predefined distance from the object, i.e. the vehicle comes to a standstill at a distance from a stationary object or a distance from a slower object moving in the same direction does not become shorter than a certain <page-break num="8"/>
|
| 82 |
+
<boundary-data type="header">P804922/WO/<confidence value="4">l</confidence>
|
| 83 |
+
- 8 - </boundary-data>
|
| 84 |
+
value<confidence value="8">.</confidence>
|
| 85 |
+
</p>
|
| 86 |
+
<p id="p-22" num="22">If the necessary braking deceleration is determined only when the driver activates a brake control, the method does not operate autonomously but rather only when the brake control is activated. As a result, the driver is not surprised or disturbed by the activation of the vehicle occupant protection means. This measure increases the protection of the vehicle. If the necessary braking deceleration is not calculated, it is also not possible to detect an event which is dependent thereon and no preventative protective measures can be initiated.</p>
|
| 87 |
+
<p id="p-23" num="23">It is particularly preferred if the necessary braking deceleration is determined at the start of braking. As a result, at the start of braking it is already possible to determine whether the braking deceleration value which has been set by the driver is sufficient to brake the vehicle without a collision. If this is not the case, the one or more vehicle occupant protection means can already be activated by way of precaution.</p>
|
| 88 |
+
<p id="p-24" num="24">This ensures that the vehicle occupant protection means is actuated in good time. In particular, preventative protection measures can be taken if a braking assistant, i.e. automatic braking to boost the braking initiated by the driver, has not been triggered, but nevertheless there is a critical driving state owing to the rapid approaching of an object. A braking assistant is triggered, for example, if a brake control speed exceeds a predefined threshold value. This means that the function of the braking assistant and the actuation of vehicle occupant protection means can be decoupled.</p>
|
| 89 |
+
<p id="p-25" num="25">In one preferred refinement of the method it is possible to provide that a braking force which is necessary for target braking is produced at the same time as the actuation of the vehicle occupant <page-break num="9"/>
|
| 90 |
+
P804922/W<confidence value="682">O/1</confidence>
|
| 91 |
+
- <part-num-ref name="vehicle occupant P804922/WO/1 -">9</part-num-ref>
|
| 92 |
+
- protection means and the wheels are correspondingly braked. This measure decelerates the vehicle to an optimum degree. If the distance from the obstacle is not sufficient to prevent a collision, the collision is at least attenuated by increasing the braking pressure or by applying a braking pressure if the driver does not brake automatically. If, on the other hand, it is detected that the braking deceleration which is initiated by the driver is not sufficient, the braking force or the braking pressure is adjusted in such a way that target braking can be carried out if the physical peripheral conditions permit it. If the physical peripheral conditions do not permit it, the driver or the other occupants are nevertheless protected to an optimum degree since the vehicle occupant protection means is actuated at the same time. </p>
|
| 93 |
+
<p id="p-26" num="26">In one alternative method variant it is possible to provide that different threshold values are predefined for the actuation of the vehicle occupant protection means and the application of the braking force which is necessary for target braking. It is thus possible, for example, for the vehicle occupant protection means to already be actuated when the braking assistant has not yet adjusted the braking deceleration for target braking since the driver possibly still has sufficient time to increase the braking force or the braking pressure himself in order to avoid a collision.</p>
|
| 94 |
+
<p id="p-27" num="27">The vehicle occupant protection means is advantageously deactivated when an abort condition occurs. If a critical situation is no longer present, the vehicle occupant protection means can also be deactivated. An abort condition can be present, for example, if the driver continues to activate the accelerator pedal or activates it again. Furthermore, an abort condition may be if the brake is released again by the driver.</p>
|
| 95 |
+
<p id="p-28" num="28">Furthermore, the vehicle occupant protection means can <page-break num="10"/>
|
| 96 |
+
<boundary-data type="header">P804922/W<confidence value="666">O/1</confidence>
|
| 97 |
+
- 10 - </boundary-data>
|
| 98 |
+
be deactivated again if the vehicle is stationary. </p>
|
| 99 |
+
<p id="p-29" num="29">The object is also achieved by means of a vehicle occupant protection system having a vehicle occupant protection means which is activated by a control device, in particular in order to carry out the abovementioned method. Here, an environment sensor system is provided which comprises distance sensors for determining the distance of the vehicle from an obstacle, means for determining the relative speed with respect to the obstacle being provided and the control device having a braking deceleration determining direction which determines the necessary braking deceleration to avoid a collision from the distance and the relative speed. Whereas in vehicle occupant protection systems which are known from the prior art the vehicle occupant protection means are actuated if a particular vehicle state, in particular a particular vehicle movement dynamics state, applies or if the braking assistant is activated owing to the detection of a driver's braking request, the vehicle occupant protection means of the vehicle occupant protection system is activated as a function of an environment sensor system. This measure allows the vehicle occupant protection means to be actuated or activated at an earlier time. Owing to the environment sensor system it is possible to detect a hazardous situation even if the driver has not yet realized this himself, and the vehicle occupant protection means can be activated accordingly.</p>
|
| 100 |
+
<p id="p-30" num="30">The activation can also be improved if in addition a driving state sensor system is provided. In particular, the longitudinal speed of the vehicle can be sensed by means of the driving state sensor system and taken into account in determining the necessary<confidence value="5">.</confidence>
|
| 101 |
+
braking deceleration. </p>
|
| 102 |
+
<p id="p-31" num="31">
|
| 103 |
+
<page-break num="11"/>
|
| 104 |
+
P804922/WO/1 - 11 - Further features and advantages of the invention emerge from the following description of an exemplary embodiment of the invention by reference to the figure in the drawing which shows details which are essential to the invention, and from the claims. The individual features can each be implemented individually in themselves or in any desired combination in a variant of the invention. </p>
|
| 105 |
+
<p id="p-32" num="32">The single figure shows a schematic illustration of a vehicle occupant protection means.</p>
|
| 106 |
+
<p id="p-33" num="33">In the single figure a vehicle occupant protection system <part-num-ref name="vehicle occupant protection system">1</part-num-ref>
|
| 107 |
+
is illustrated in a highly schematic fashion. </p>
|
| 108 |
+
<p id="p-34" num="34">The vehicle occupant protection system has a vehicle occupant protection means <part-num-ref name="vehicle occupant protection means">2</part-num-ref>
|
| 109 |
+
which is activated if a collision is to be feared. The vehicle occupant protection means is activated or actuated by means of a control device <part-num-ref name="control device">3.</part-num-ref>
|
| 110 |
+
The control device <part-num-ref name="control device">3</part-num-ref>
|
| 111 |
+
can detect an event during which the vehicle occupant detection means <part-num-ref name="vehicle occupant detection means">2</part-num-ref>
|
| 112 |
+
has to be activated. An environment sensor system <part-num-ref name="environment sensor system">4</part-num-ref>
|
| 113 |
+
which comprises distance sensors <part-num-ref name="which comprises distance sensors">5</part-num-ref>
|
| 114 |
+
can detect distances from objects in the surroundings of a vehicle. </p>
|
| 115 |
+
<p id="p-35" num="35">Furthermore, relative speeds of the vehicle in which the vehicle occupant protection system <part-num-ref name="vehicle occupant protection system">1</part-num-ref>
|
| 116 |
+
is installed can be determined with respect to a detected object by means <confidence value="4">6</confidence>
|
| 117 |
+
a for determining the relative speed. The environment sensor system <part-num-ref name="environment sensor system">4</part-num-ref>
|
| 118 |
+
is connected to a braking deceleration determining device <part-num-ref name="braking deceleration determining device">6</part-num-ref>
|
| 119 |
+
of the control device <part-num-ref name="control device">3.</part-num-ref>
|
| 120 |
+
In the braking deceleration determining device <part-num-ref name="braking deceleration determining device">6</part-num-ref>
|
| 121 |
+
the necessary braking deceleration to brake a vehicle in such a way that a collision does not occur with an object sensed by the surroundings sensor system <part-num-ref name="surroundings sensor system">4</part-num-ref>
|
| 122 |
+
is determined. In this context it is possible to provide that in the case of a stationary object the braking deceleration is determined in such a way that the vehicle comes to a standstill before the object. If the <page-break num="12"/>
|
| 123 |
+
<boundary-data type="header">P804922/WO/<confidence value="4">l</confidence>
|
| 124 |
+
- 12 - </boundary-data>
|
| 125 |
+
object is a moving object, the braking deceleration can be determined in such a way that the vehicle is braked to a predefined distance from the object. </p>
|
| 126 |
+
<p id="p-36" num="36">Furthermore, a driving state sensor system <part-num-ref name="driving state sensor system">7</part-num-ref>
|
| 127 |
+
can be provided which is connected, for example, to a wheel speed sensor <part-num-ref name="wheel speed sensor">
|
| 128 |
+
<confidence value="5">8</confidence>
|
| 129 |
+
. </part-num-ref>
|
| 130 |
+
The vehicle speed can be determined from the signals of the sensor <part-num-ref name="sensor">8.</part-num-ref>
|
| 131 |
+
Said speed can be taken into account in determining the braking deceleration or in the actuation of the vehicle occupant protection means <part-num-ref name="vehicle occupant protection means">2.</part-num-ref>
|
| 132 |
+
The control device <part-num-ref name="control device">3</part-num-ref>
|
| 133 |
+
can furthermore be connected to a brake system <part-num-ref name="brake system">9</part-num-ref>
|
| 134 |
+
which can be actuated by a brake assistance system. In particular it is possible to provide that a brake pressure is applied automatically to the brake system <part-num-ref name="brake system">9</part-num-ref>
|
| 135 |
+
if it detected that the braking deceleration which is determined by the braking deceleration determining device <part-num-ref name="braking deceleration determining device">6</part-num-ref>
|
| 136 |
+
is significantly higher than the braking deceleration which is applied by a driver by means of a brake control <part-num-ref name="brake control">10.</part-num-ref>
|
| 137 |
+
</p>
|
| 138 |
+
<p id="p-37" num="37">The control device 3 can comprise a comparison device <part-num-ref name="comparison device">11</part-num-ref>
|
| 139 |
+
in which the determined necessary braking deceleration is compared with the braking deceleration applied by the driver. If a deviation occurs which exceeds a predefined threshold value it is possible to provide that both the auxiliary braking means <part-num-ref name="auxiliary braking means">2</part-num-ref>
|
| 140 |
+
and the brake system <part-num-ref name="brake system">9</part-num-ref>
|
| 141 |
+
are actuated. </p>
|
| 142 |
+
</description>
|
| 143 |
+
</us-patent-application>
|
| 144 |
+
|
applicant/11593029.xml
ADDED
|
@@ -0,0 +1,520 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>11593029</doc-number>
|
| 8 |
+
<date>2006-11-06</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<heading id="h-1">
|
| 14 |
+
<confidence value="88">PA</confidence>
|
| 15 |
+
TENT </heading>
|
| 16 |
+
<p id="p-1" num="1">
|
| 17 |
+
<confidence value="8">A</confidence>
|
| 18 |
+
TTORNEY DOCKET NO.: 065543-5009 </p>
|
| 19 |
+
<heading id="h-2">UNITED STATES PATENT APPLICATION</heading>
|
| 20 |
+
<heading id="h-3">
|
| 21 |
+
<confidence value="88">OF</confidence>
|
| 22 |
+
</heading>
|
| 23 |
+
<heading id="h-4">
|
| 24 |
+
<confidence value="66">KI</confidence>
|
| 25 |
+
DUK KIM </heading>
|
| 26 |
+
<heading id="h-5">AND</heading>
|
| 27 |
+
<heading id="h-6">JAE KYEONG <confidence value="588">YUN</confidence>
|
| 28 |
+
</heading>
|
| 29 |
+
<heading id="h-7">FOR</heading>
|
| 30 |
+
<heading id="h-8">LIQUID CRYSTAL DISPLAY AND METHOD FOR DRIVING THE SAME</heading>
|
| 31 |
+
<boundary-data type="header">
|
| 32 |
+
<confidence value="68885">1-WA/</confidence>
|
| 33 |
+
2607556.2 <confidence value="5">1</confidence>
|
| 34 |
+
</boundary-data>
|
| 35 |
+
<p id="p-2" num="2">
|
| 36 |
+
<page-break num="2"/>
|
| 37 |
+
<confidence value="5">[</confidence>
|
| 38 |
+
0001<confidence value="5">]</confidence>
|
| 39 |
+
This application claims the benefit of the Korean Patent Application No. </p>
|
| 40 |
+
<p id="p-3" num="3">2005-0132131 filed on December 28, 2005, which is hereby incorporated by reference.</p>
|
| 41 |
+
<heading id="h-9">BACKGROUND OF THE INVENTION</heading>
|
| 42 |
+
<heading id="h-10">FIELD OF THE INVENTION</heading>
|
| 43 |
+
<p id="p-4" num="4">
|
| 44 |
+
<confidence value="5">[</confidence>
|
| 45 |
+
0002<confidence value="2">1</confidence>
|
| 46 |
+
The present invention relates to a liquid crystal display and a method for driving the same and, more specifically, a liquid crystal display and a method for driving the same with improved display characteristics. </p>
|
| 47 |
+
<heading id="h-11">DESCRIPTION OF THE RELATED ART</heading>
|
| 48 |
+
<p id="p-5" num="5">
|
| 49 |
+
<confidence value="5">[</confidence>
|
| 50 |
+
0003<confidence value="5">]</confidence>
|
| 51 |
+
Generally, a liquid crystal display (LCD) is a display device in which liquid crystal material with an anisotropic dielectric constant is injected between an upper transparent insulating substrate and a lower transparent insulating substrate. Molecular arrangement of the liquid crystal material is changed by the intensity of the electric field applied to the liquid crystal material such that the amount of light, which is generated from a backlight unit, transmitted through the transparent insulating substrates may be controlled, and thereby a desired image may be displayed. A thin film transistor liquid crystal display (TFT LCD) using a TFT as a switching device is a type of LCD that is widely used. </p>
|
| 52 |
+
<p id="p-6" num="6">[0004<confidence value="5">]</confidence>
|
| 53 |
+
In a liquid crystal display, a plurality of gate lines are arranged in a first direction, and a plurality of data lines are arranged in a second direction which is substantially perpendicular to the first direction. A thin film transistor and a pixel <boundary-data type="header">
|
| 54 |
+
<confidence value="58685">1-WA/</confidence>
|
| 55 |
+
2607556.2 <confidence value="6">2</confidence>
|
| 56 |
+
</boundary-data>
|
| 57 |
+
<page-break num="3"/>
|
| 58 |
+
electrode are arranged in a region where a gate line and a data line intersect each other, and a liquid crystal capacitor and a storage capacitor are arranged in the region. </p>
|
| 59 |
+
<p id="p-7" num="7">
|
| 60 |
+
<confidence value="5">[</confidence>
|
| 61 |
+
0005<confidence value="5">]</confidence>
|
| 62 |
+
When the thin film transistor is turned on in response to a scan pulse applied to a gate line, a gamma voltage corresponding to video data is applied from the data lines to each of the pixels corresponding to the gate line. The video data correspond to a digital signal representing a gray level. For example, the gray level may be between <part-num-ref name="gray level may be between">0</part-num-ref>
|
| 63 |
+
and <part-num-ref name="and">255.</part-num-ref>
|
| 64 |
+
</p>
|
| 65 |
+
<p id="p-8" num="8">
|
| 66 |
+
<confidence value="5">[</confidence>
|
| 67 |
+
0006<confidence value="5">]</confidence>
|
| 68 |
+
Thus, an electric field is generated due to a voltage difference between the gamma voltage applied to a pixel electrode and a common voltage applied to the common electrode. The electric field is applied to a liquid crystal layer such that the light, e.g., from the backlight unit, is transmitted through the liquid crystal. The transmittance of the light is determined by the intensity of the applied electric field. Furthermore, the storage capacitor maintains the gamma voltage applied to the pixel electrode during one frame so that an image is maintained in the pixel for one frame. </p>
|
| 69 |
+
<p id="p-9" num="9">
|
| 70 |
+
<confidence value="5">[</confidence>
|
| 71 |
+
0007<confidence value="5">]</confidence>
|
| 72 |
+
When the liquid crystal display is driven as detailed above, an over-driving method may be used. In the over-driving method, the video data having a higher value than a normal value are applied to each of the pixels so as to compensate for a delayed (or slow) response of the liquid crystal. </p>
|
| 73 |
+
<p id="p-10" num="10">[0008<confidence value="5">]</confidence>
|
| 74 |
+
FIG. 1 illustrates graphs showing light-transmission characteristics of liquid crystal and final light-transmission characteristics of a liquid crystal display according to a related art. As shown in FIG. 1, graphs (a) and (b) respectively illustrate a normal driving method and an over-driving method. In FIG. <confidence value="28">I,</confidence>
|
| 75 |
+
light-transmission characteristics <boundary-data type="header">
|
| 76 |
+
<confidence value="6">I</confidence>
|
| 77 |
+
<confidence value="8885">-WA/</confidence>
|
| 78 |
+
2607556.2 3 </boundary-data>
|
| 79 |
+
<page-break num="4"/>
|
| 80 |
+
of liquid crystal and final light-transmission characteristics of a liquid crystal display are shown in a unit frame when a backlight driving pulse <confidence value="55">G1</confidence>
|
| 81 |
+
and a liquid crystal driving pulse G2 are applied to the liquid crystal display. </p>
|
| 82 |
+
<p id="p-11" num="11">
|
| 83 |
+
<confidence value="5">[</confidence>
|
| 84 |
+
0009 When the liquid crystal display is driven by the normal driving method, the light-transmission characteristics G3 of the liquid crystal and the final light-transmission characteristics G4 of the liquid crystal display are shown in the graph (a) due to the response time of the liquid crystal. When the liquid crystal display is driven by the over- driving method, the light-transmission characteristics <confidence value="5">G</confidence>
|
| 85 |
+
3 of the liquid crystal and the final light-transmission characteristics G4 of the liquid crystal display are improved as shown in the graph (b) due to a faster response time of the liquid crystal. </p>
|
| 86 |
+
<p id="p-12" num="12">
|
| 87 |
+
<confidence value="5">[</confidence>
|
| 88 |
+
0010<confidence value="5">]</confidence>
|
| 89 |
+
When a gamma voltage applied to the liquid crystal changes rapidly due to a large difference in pixel data between two consecutive frames, it is difficult to stabilize the voltage level of the gamma voltage within one frame due to the delayed response of the liquid crystal. Accordingly, the response time of the liquid crystal may be improved by using the over-driving method. However, in case of the over-driving method according to the related art, electromagnetic interference increases, and power consumption increases. </p>
|
| 90 |
+
<heading id="h-12">SUMMARY OF THE INVENTION</heading>
|
| 91 |
+
<p id="p-13" num="13">
|
| 92 |
+
<confidence value="5">[</confidence>
|
| 93 |
+
0011<confidence value="2">1</confidence>
|
| 94 |
+
Accordingly, the present invention is directed to a liquid crystal display device and method for driving the same that substantially obviate one or more of the problems due to limitations and disadvantages of the related art. </p>
|
| 95 |
+
<boundary-data type="header">
|
| 96 |
+
<confidence value="28884">1-WA1</confidence>
|
| 97 |
+
2607<confidence value="5">5</confidence>
|
| 98 |
+
56.2 4 </boundary-data>
|
| 99 |
+
<p id="p-14" num="14">
|
| 100 |
+
<page-break num="5"/>
|
| 101 |
+
<confidence value="2">1</confidence>
|
| 102 |
+
0012<confidence value="5">]</confidence>
|
| 103 |
+
The present invention is directed to a liquid crystal display that effectively enhances the response characteristics and brightness of the liquid crystal display. The present invention is also directed to a method for effectively driving the above liquid crystal display. </p>
|
| 104 |
+
<p id="p-15" num="15">[0013<confidence value="4">]</confidence>
|
| 105 |
+
Additional advantages, objects, and features of the invention will be set forth in part in the description which follows and in part will become apparent to those having ordinary skill in the art upon examination of the following or may be learned from practice of the invention. The objectives and other advantages of the invention may be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings. </p>
|
| 106 |
+
<p id="p-16" num="16">
|
| 107 |
+
<confidence value="5">[</confidence>
|
| 108 |
+
0014<confidence value="5">]</confidence>
|
| 109 |
+
To achieve these objects and other advantages and in accordance with the purpose of the invention, as embodied and broadly described herein, a liquid crystal display includes a driver circuit configured to generate at least one liquid crystal driving pulse and at least one backlight driving pulse, wherein the liquid crystal driving pulse includes a normal data signal and a blanking signal, and the backlight driving pulse includes an active signal and a reference signal; a backlight unit configured to generate light in response to the backlight driving pulse; and a liquid crystal panel configured to display an image having a light transmittance that varies depending upon the liquid crystal driving pulse and the backlight driving pulse. </p>
|
| 110 |
+
<p id="p-17" num="17">
|
| 111 |
+
<confidence value="5">[</confidence>
|
| 112 |
+
0015<confidence value="5">]</confidence>
|
| 113 |
+
In another aspect of the present invention, a method for driving a liquid crystal display includes generating at least one liquid crystal driving pulse, wherein the liquid driving pulse includes a normal data signal and a blanking signal; generating at least one <boundary-data type="header">
|
| 114 |
+
<confidence value="28885">1-WA/</confidence>
|
| 115 |
+
2607556.2 5 </boundary-data>
|
| 116 |
+
<page-break num="6"/>
|
| 117 |
+
backlight driving pulse, wherein the backlight driving pulse includes an active signal and a reference signal; and displaying an image on the liquid crystal display having a light transmittance that varies depending upon the liquid crystal driving pulse and the backlight driving pulse. </p>
|
| 118 |
+
<p id="p-18" num="18">[0016<confidence value="5">]</confidence>
|
| 119 |
+
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are intended to provide further explanation of the invention as claimed. </p>
|
| 120 |
+
<heading id="h-13">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
|
| 121 |
+
<p id="p-19" num="19">[0017<confidence value="5">]</confidence>
|
| 122 |
+
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the principles of the invention. In the drawings: </p>
|
| 123 |
+
<p id="p-20" num="20">
|
| 124 |
+
<confidence value="5">[</confidence>
|
| 125 |
+
0018<confidence value="5">]</confidence>
|
| 126 |
+
FIG. 1 illustrates graphs showing light-transmission characteristics of liquid crystal and final light-transmission characteristics in a related art liquid crystal display; </p>
|
| 127 |
+
<p id="p-21" num="21">
|
| 128 |
+
<confidence value="5">[</confidence>
|
| 129 |
+
0019<confidence value="5">]</confidence>
|
| 130 |
+
FIG. 2 illustrates a liquid crystal display according to an embodiment of the present invention; </p>
|
| 131 |
+
<p id="p-22" num="22">
|
| 132 |
+
<confidence value="5">[</confidence>
|
| 133 |
+
0020] FIG. 3 illustrates graphs showing light-transmission characteristics of liquid crystal and final light-transmission characteristics of a liquid crystal display according to an embodiment of the present invention; </p>
|
| 134 |
+
<p id="p-23" num="23">
|
| 135 |
+
<confidence value="5">[</confidence>
|
| 136 |
+
0021<confidence value="5">]</confidence>
|
| 137 |
+
FIGs. 4 and <part-num-ref name="and">5</part-num-ref>
|
| 138 |
+
illustrate graphs showing examples of a reference signal and an active signal of the backlight driving pulse of FIG. 3; </p>
|
| 139 |
+
<boundary-data type="header">
|
| 140 |
+
<confidence value="5">1</confidence>
|
| 141 |
+
-WA<confidence value="5">/</confidence>
|
| 142 |
+
2607556.2 6 </boundary-data>
|
| 143 |
+
<p id="p-24" num="24">
|
| 144 |
+
<page-break num="7"/>
|
| 145 |
+
[0022] FIG. 6 illustrates graphs showing light-transmission characteristics of liquid crystal and final light-transmission characteristics of a liquid crystal display according to another embodiment of the present invention; </p>
|
| 146 |
+
<p id="p-25" num="25">[0023<confidence value="5">]</confidence>
|
| 147 |
+
FIGs. 7 and <part-num-ref name="and">8</part-num-ref>
|
| 148 |
+
illustrate graphs showing examples of a reference signal and an active signal of the backlight driving pulse of FIG. 6; and [0024<confidence value="5">]</confidence>
|
| 149 |
+
FIG. 9 illustrates a flow chart showing a method for driving a liquid crystal display according to an embodiment of the present invention. </p>
|
| 150 |
+
<heading id="h-14">DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS</heading>
|
| 151 |
+
<p id="p-26" num="26">
|
| 152 |
+
<confidence value="5">[</confidence>
|
| 153 |
+
0025] Reference will now be made in detail to the embodiments of the present invention, examples of which are illustrated in the accompanying drawings. </p>
|
| 154 |
+
<p id="p-27" num="27">
|
| 155 |
+
<confidence value="5">[</confidence>
|
| 156 |
+
0026<confidence value="5">]</confidence>
|
| 157 |
+
FIG. 2 illustrates a liquid crystal display according to an embodiment of the present invention. As shown in FIG. 2, the liquid crystal display includes a liquid crystal display panel <part-num-ref name="liquid crystal display panel">100,</part-num-ref>
|
| 158 |
+
a driver circuit <part-num-ref name="driver circuit">200</part-num-ref>
|
| 159 |
+
for driving the liquid crystal display panel <part-num-ref name="liquid crystal display panel">100,</part-num-ref>
|
| 160 |
+
and a backlight unit <part-num-ref name="backlight unit">300</part-num-ref>
|
| 161 |
+
for providing light to the liquid crystal display panel <part-num-ref name="liquid crystal display panel">100.</part-num-ref>
|
| 162 |
+
</p>
|
| 163 |
+
<p id="p-28" num="28">
|
| 164 |
+
<confidence value="5">[</confidence>
|
| 165 |
+
0027<confidence value="5">]</confidence>
|
| 166 |
+
The liquid crystal display panel <part-num-ref name="liquid crystal display panel">100</part-num-ref>
|
| 167 |
+
includes a plurality of pixels having a matrix arrangement. A plurality of gate lines GL are arranged in a first direction, and a plurality of data lines DL are arranged in a second direction substantially perpendicular to the first direction. A pixel is coupled to a gate line GL and a data line. The pixels display an image in response to a plurality of scan pulses that are applied through the gate lines GL and a plurality of liquid crystal driving pulses that are applied through the data lines DL. </p>
|
| 168 |
+
<boundary-data type="header">
|
| 169 |
+
<confidence value="5">1</confidence>
|
| 170 |
+
-WA<confidence value="4">1</confidence>
|
| 171 |
+
2607556.2 7 </boundary-data>
|
| 172 |
+
<p id="p-29" num="29">
|
| 173 |
+
<page-break num="8"/>
|
| 174 |
+
[0028] A thin film transistor, a liquid crystal capacitor, and a storage capacitor are arranged in a region where a gate line and a data line intersect each other. Each pixel includes a thin film transistor, a liquid crystal capacitor, and a storage capacitor. </p>
|
| 175 |
+
<p id="p-30" num="30">[0029] The driver circuit <part-num-ref name="driver circuit">200</part-num-ref>
|
| 176 |
+
includes a gate driver <part-num-ref name="gate driver">210,</part-num-ref>
|
| 177 |
+
a source driver <part-num-ref name="source driver">220,</part-num-ref>
|
| 178 |
+
a timing controller <part-num-ref name="timing controller">230,</part-num-ref>
|
| 179 |
+
a power supply <part-num-ref name="power supply">240,</part-num-ref>
|
| 180 |
+
a gamma voltage provider <part-num-ref name="gamma voltage provider">250,</part-num-ref>
|
| 181 |
+
and a light source controller <part-num-ref name="light source controller">260.</part-num-ref>
|
| 182 |
+
</p>
|
| 183 |
+
<p id="p-31" num="31">
|
| 184 |
+
<confidence value="5">[</confidence>
|
| 185 |
+
0030<confidence value="5">]</confidence>
|
| 186 |
+
The gate driver <part-num-ref name="gate driver">210</part-num-ref>
|
| 187 |
+
generates a plurality of scan pulses sequentially applied to the gate lines GL in response to the gate control signal GDC provided from the timing controller <part-num-ref name="timing controller">230.</part-num-ref>
|
| 188 |
+
The source driver <part-num-ref name="source driver">220</part-num-ref>
|
| 189 |
+
generates a plurality of liquid crystal driving pulses which, in each frame period, includes a normal data signal and a blanking signal. </p>
|
| 190 |
+
<p id="p-32" num="32">[0031] The normal data signal represents a gamma voltage corresponding to red (R), green (G), and blue (B) video data. The gamma voltage provider <part-num-ref name="gamma voltage provider">250</part-num-ref>
|
| 191 |
+
provides the gamma voltages. The blanking signal represents a gamma voltage having a black level corresponding to black data. </p>
|
| 192 |
+
<p id="p-33" num="33">[0032] The source driver <part-num-ref name="source driver">220</part-num-ref>
|
| 193 |
+
selects a gamma voltage corresponding to the red (R), green (G), and blue (B) video data, and generates the liquid crystal driving pulse which includes the selected gamma voltage and the gamma voltage having the black level. The source driver <part-num-ref name="source driver">220</part-num-ref>
|
| 194 |
+
provides the liquid crystal driving pulse to the data lines DL of the liquid crystal panel <part-num-ref name="liquid crystal panel">100.</part-num-ref>
|
| 195 |
+
</p>
|
| 196 |
+
<p id="p-34" num="34">[0033<confidence value="5">]</confidence>
|
| 197 |
+
The timing controller <part-num-ref name="timing controller">230</part-num-ref>
|
| 198 |
+
generates a gate control signal GDC for controlling the gate driver <part-num-ref name="gate driver">210</part-num-ref>
|
| 199 |
+
and a data control signal DDC for controlling the source driver <part-num-ref name="source driver">220</part-num-ref>
|
| 200 |
+
based on the video data (R, G, B) provided from an external system (SYS). The timing <boundary-data type="header">
|
| 201 |
+
<confidence value="4">i</confidence>
|
| 202 |
+
<confidence value="8486">-wA/</confidence>
|
| 203 |
+
2607556.2 <confidence value="6">8</confidence>
|
| 204 |
+
</boundary-data>
|
| 205 |
+
<page-break num="9"/>
|
| 206 |
+
controller <part-num-ref name="timing controller">230</part-num-ref>
|
| 207 |
+
also generates a horizontal synchronization signal H, a vertical synchronization signal V, and clock signal CLK. Additionally, the timing controller <part-num-ref name="timing controller">230</part-num-ref>
|
| 208 |
+
provides a light source control signal BDC to the light source controller <part-num-ref name="light source controller">260</part-num-ref>
|
| 209 |
+
for controlling the backlight unit <part-num-ref name="backlight unit">300.</part-num-ref>
|
| 210 |
+
</p>
|
| 211 |
+
<p id="p-35" num="35">
|
| 212 |
+
<confidence value="5">[</confidence>
|
| 213 |
+
0034<confidence value="5">]</confidence>
|
| 214 |
+
The gate control signal GDC includes a gate start pulse GSP, a gate shift clock signal GSC, and a gate output enable signal GOE. The data control signal DDC includes a source start pulse SSP, a source shift clock signal SSC, a source output enable signal SOC, and a polarity signal POL. </p>
|
| 215 |
+
<p id="p-36" num="36">
|
| 216 |
+
<confidence value="5">[</confidence>
|
| 217 |
+
0035<confidence value="5">]</confidence>
|
| 218 |
+
The power supply <part-num-ref name="power supply">240</part-num-ref>
|
| 219 |
+
receives power supply voltage VCC from the external system (SYS) and generates driving voltages having various voltage levels, including a gate high voltage VGH, a gate low voltage VGL, a common voltage Vcom, and a constant voltage VDD. </p>
|
| 220 |
+
<p id="p-37" num="37">
|
| 221 |
+
<confidence value="5">[</confidence>
|
| 222 |
+
0036<confidence value="5">]</confidence>
|
| 223 |
+
The gamma voltage provider <part-num-ref name="gamma voltage provider">250</part-num-ref>
|
| 224 |
+
receives a voltage from the power supply <part-num-ref name="power supply">240,</part-num-ref>
|
| 225 |
+
generates gamma voltages (i.e., reference voltages), and provides the gamma voltages to the source driver <part-num-ref name="source driver">220.</part-num-ref>
|
| 226 |
+
The source driver <part-num-ref name="source driver">220</part-num-ref>
|
| 227 |
+
performs a digital-to-analog conversion based on the gamma voltages. The voltage levels of the generated gamma voltages include a plurality of gray levels, a white level, and a black level. </p>
|
| 228 |
+
<p id="p-38" num="38">[0037<confidence value="5">]</confidence>
|
| 229 |
+
The light source controller <part-num-ref name="light source controller">260</part-num-ref>
|
| 230 |
+
generates a backlight driving pulse that is synchronized with the liquid crystal driving pulse based on the light source control signal BDC so as to drive the lamp or lamps in the backlight unit <part-num-ref name="backlight unit">300</part-num-ref>
|
| 231 |
+
according to an embodiment of the present invention. The backlight driving pulse includes an active signal and a reference signal. </p>
|
| 232 |
+
<boundary-data type="header">
|
| 233 |
+
<confidence value="2">1</confidence>
|
| 234 |
+
-WA<confidence value="5">/</confidence>
|
| 235 |
+
2607556.2 9 </boundary-data>
|
| 236 |
+
<p id="p-39" num="39">
|
| 237 |
+
<page-break num="10"/>
|
| 238 |
+
<confidence value="5">[</confidence>
|
| 239 |
+
0038<confidence value="5">]</confidence>
|
| 240 |
+
FIG. 3 illustrates graphs showing light-transmission characteristics of liquid crystal and final light-transmission characteristics of a liquid crystal display of FIG. 2 that is driven based on the active lamp method according to an embodiment of the present invention. In particular, FIG. 3 illustrates graphs of light-transmission characteristics of liquid crystal and final light-transmission characteristics of a liquid crystal display that is driven based on active lamp method and a black-data insertion method according to an embodiment of the present invention, in which the brightness of the light source in the backlight unit <part-num-ref name="backlight unit">300</part-num-ref>
|
| 241 |
+
is actively controlled so that it is periodically increased or decreased. </p>
|
| 242 |
+
<p id="p-40" num="40">
|
| 243 |
+
<confidence value="5">[</confidence>
|
| 244 |
+
0039 Graph (a) of FIG. 3 shows the light-transmission characteristics of liquid crystal depending upon a liquid crystal driving pulse G2 when the video data (R, G, and B) have a given value. Graph (b) of FIG. 3 shows a backlight driving pulse G<confidence value="1">I</confidence>
|
| 245 |
+
when the active lamp method is used. Graph (c) of FIG. 3 shows the final light-transmission characteristics G4 of the liquid crystal display when conditions of the graphs (a) and (b) are provided. </p>
|
| 246 |
+
<p id="p-41" num="41">
|
| 247 |
+
<confidence value="5">[</confidence>
|
| 248 |
+
0040<confidence value="5">]</confidence>
|
| 249 |
+
Each frame period of the liquid crystal driving pulse G2 is divided into a data period (T<confidence value="4">l</confidence>
|
| 250 |
+
) and a blanking period (T2). The driver circuit <part-num-ref name="driver circuit">220</part-num-ref>
|
| 251 |
+
outputs the normal data signal during the data period (T<confidence value="4">l</confidence>
|
| 252 |
+
) and the blanking signal during the blanking period (T2). </p>
|
| 253 |
+
<p id="p-42" num="42">The light source controller 260 controls the backlight driving pulse G<confidence value="1">I</confidence>
|
| 254 |
+
based on the light source control signal BDC so that the active signal of the backlight driving pulse G <part-num-ref name="backlight driving pulse G">
|
| 255 |
+
<confidence value="2">1</confidence>
|
| 256 |
+
</part-num-ref>
|
| 257 |
+
is output during the data period (T<confidence value="488">l).</confidence>
|
| 258 |
+
</p>
|
| 259 |
+
<p id="p-43" num="43">
|
| 260 |
+
<confidence value="5">[</confidence>
|
| 261 |
+
0041<confidence value="5">]</confidence>
|
| 262 |
+
Each frame period of the backlight driving pulse G<confidence value="5">1</confidence>
|
| 263 |
+
is divided into an active period (T3) and a reference period (T4). The light source controller <part-num-ref name="light source controller">260</part-num-ref>
|
| 264 |
+
outputs the <boundary-data type="header">
|
| 265 |
+
<confidence value="5">I</confidence>
|
| 266 |
+
-WA<confidence value="5">/</confidence>
|
| 267 |
+
2607556.2 1<confidence value="2">0</confidence>
|
| 268 |
+
</boundary-data>
|
| 269 |
+
<page-break num="11"/>
|
| 270 |
+
active signal and the reference signal during the active period (<confidence value="5">T</confidence>
|
| 271 |
+
3) and the reference signal during the reference period (T4). The light source control signal BDC allows the active period (T3) of the backlight driving pulse G2 to be within the data period (T<confidence value="588">1).</confidence>
|
| 272 |
+
</p>
|
| 273 |
+
<p id="p-44" num="44">
|
| 274 |
+
<confidence value="5">[</confidence>
|
| 275 |
+
0042<confidence value="5">]</confidence>
|
| 276 |
+
The driver circuit <part-num-ref name="driver circuit">200</part-num-ref>
|
| 277 |
+
divides each frame into first and second periods at a given ratio (for example, 5:5, 6:4, 7:3, etc.), where the first period represents the data period (T<confidence value="4">l</confidence>
|
| 278 |
+
) during which the gamma voltage (i.e., the normal data signal) corresponding to the video data (R, G, and B) is output, and the second period represents the blanking period (<confidence value="5">T</confidence>
|
| 279 |
+
2) during which the gamma voltage having the black level is output. </p>
|
| 280 |
+
<p id="p-45" num="45">
|
| 281 |
+
<confidence value="5">[</confidence>
|
| 282 |
+
0043<confidence value="5">]</confidence>
|
| 283 |
+
The backlight unit <part-num-ref name="backlight unit">300</part-num-ref>
|
| 284 |
+
is driven according to the active lamp method based on the backlight driving pulse G<confidence value="4">l</confidence>
|
| 285 |
+
. The brightness of the light source in the backlight unit is periodically increased or decreased. Each frame period of the backlight driving pulse G<confidence value="2">l</confidence>
|
| 286 |
+
is divided into an active period (T3), during which the active signal and the reference signal are output, and a reference period (T4), during which the reference signal is output. </p>
|
| 287 |
+
<p id="p-46" num="46">
|
| 288 |
+
<confidence value="5">[</confidence>
|
| 289 |
+
0044<confidence value="5">]</confidence>
|
| 290 |
+
The active period (T3) of the backlight driving pulse G<confidence value="5">1</confidence>
|
| 291 |
+
corresponds to the data period (T<confidence value="4">l</confidence>
|
| 292 |
+
) of the liquid crystal driving pulse G2. The width of the active period (T3) of the backlight driving pulse G<confidence value="4">l</confidence>
|
| 293 |
+
is narrower than width of the data period (T<confidence value="2">i</confidence>
|
| 294 |
+
) of the liquid crystal driving pulse G2. In particular, the start point and the end point of the active period (<confidence value="5">T</confidence>
|
| 295 |
+
3) of the backlight driving pulse G<confidence value="5">1</confidence>
|
| 296 |
+
are within the data period (T<confidence value="2">i</confidence>
|
| 297 |
+
) of the liquid crystal driving pulse G2. </p>
|
| 298 |
+
<p id="p-47" num="47">
|
| 299 |
+
<confidence value="5">[</confidence>
|
| 300 |
+
0045<confidence value="5">]</confidence>
|
| 301 |
+
When the active lamp method is used, the light transmittance of the liquid crystal display at the rising edges of the liquid crystal driving pulse G2 improves, and therefore, the brightness of the display improves. On the other hand, with only the active <boundary-data type="header">
|
| 302 |
+
<confidence value="68686">1-WA/</confidence>
|
| 303 |
+
2607556.2 1<confidence value="8">1</confidence>
|
| 304 |
+
</boundary-data>
|
| 305 |
+
<page-break num="12"/>
|
| 306 |
+
lamp method, the light transmittance of the liquid crystal display at the falling edges of the liquid crystal driving pulse G2 may also increase, which can deteriorate the image quality. Thus, the black-data insertion method as the liquid crystal driving method may be simultaneously used with the active lamp method so that the active lamp method increases the final light transmittance of the liquid crystal display at the rising edges of the liquid crystal driving pulse G2 without increasing the response time or the light transmittance at the falling edges. </p>
|
| 307 |
+
<p id="p-48" num="48">[0046<confidence value="5">]</confidence>
|
| 308 |
+
The time at which the light source controller <part-num-ref name="light source controller">260</part-num-ref>
|
| 309 |
+
outputs the active signal may not necessarily correspond to the start point of the data period (T<confidence value="2">i</confidence>
|
| 310 |
+
). The active period (T3) may be experimentally determined by measuring the optimal light efficiency based on when the active signal is provided by the light source controller <part-num-ref name="light source controller">260</part-num-ref>
|
| 311 |
+
during the data period (T<confidence value="488">l).</confidence>
|
| 312 |
+
</p>
|
| 313 |
+
<p id="p-49" num="49">
|
| 314 |
+
<confidence value="5">[</confidence>
|
| 315 |
+
0047<confidence value="2">]</confidence>
|
| 316 |
+
The start point and the end point of the active period (T3) may be determined based on two considerations. First, the display quality should not deteriorate at the falling edges of the liquid crystal driving pulse G2. Second, the brightness of the light source should be optimally controlled in view of the light transmittance characteristics of the liquid crystal. Thus, the start point and the end point of the active period (T3) should be located within the data period (T<confidence value="288">1).</confidence>
|
| 317 |
+
</p>
|
| 318 |
+
<p id="p-50" num="50">
|
| 319 |
+
<confidence value="5">[</confidence>
|
| 320 |
+
0048<confidence value="5">]</confidence>
|
| 321 |
+
If the black-data insertion method is simultaneously used with the active lamp method, when the blanking signal having the black level is inserted and the backlight driving pulse G<confidence value="5">1</confidence>
|
| 322 |
+
is output during the blanking period (T2) of the present frame of the liquid crystal driving pulse G2, the light transmittance of the liquid crystal display at the <boundary-data type="header">
|
| 323 |
+
<confidence value="4">i</confidence>
|
| 324 |
+
-WA<confidence value="5">/</confidence>
|
| 325 |
+
2607556.2 <confidence value="68">12</confidence>
|
| 326 |
+
</boundary-data>
|
| 327 |
+
<page-break num="13"/>
|
| 328 |
+
rising edge of the liquid crystal driving pulse G2 may improve without an increase in the light transmittance at the falling edge. This is because the liquid crystal driving pulse G2 falls to a zero gray level in the present frame and rises from the zero gray level in the next frame as shown in graph (a) of FIG. 3. The response time at the falling edges decreases because the difference between the data voltage and the blanking data is large. Therefore, the data voltage of the present frame may be prevented from affecting the data voltage of the next frame. This can result in preventing motion blur and improving the image quality of the liquid crystal display. </p>
|
| 329 |
+
<p id="p-51" num="51">
|
| 330 |
+
<confidence value="5">[</confidence>
|
| 331 |
+
0049<confidence value="5">]</confidence>
|
| 332 |
+
The liquid crystal panel <part-num-ref name="liquid crystal panel">100</part-num-ref>
|
| 333 |
+
displays an image having a light transmittance that varies depending upon the liquid crystal driving pulse G2 and the backlight driving pulse G<confidence value="2">l</confidence>
|
| 334 |
+
. The final light-transmission characteristics G4 of the liquid crystal display may be shown as graph (c) of FIG. 3 when the liquid crystal has the light-transmission characteristics G3 based on the liquid crystal driving pulse G2 of graph (a) of FIG. 3 and the brightness of the backlight unit <part-num-ref name="backlight unit">300</part-num-ref>
|
| 335 |
+
varies according to the backlight driving pulse G<confidence value="4">l</confidence>
|
| 336 |
+
of graph (b) of FIG. 3. </p>
|
| 337 |
+
<p id="p-52" num="52">
|
| 338 |
+
<confidence value="86">[0</confidence>
|
| 339 |
+
050<confidence value="5">]</confidence>
|
| 340 |
+
When the light-transmission characteristics G3 based on the liquid crystal driving pulse G2 of graph (a) of FIG. 3 are compared with the final light-transmission characteristics G4 of graph (c) of FIG. 3 where the backlight driving pulse G<confidence value="5">1</confidence>
|
| 341 |
+
is applied, the response time of the liquid crystal display at the rising edge of the final light- transmission characteristics G4 is reduced (i.e., enhanced) due to the backlight driving pulse G<confidence value="4">l</confidence>
|
| 342 |
+
of the active lamp method. </p>
|
| 343 |
+
<boundary-data type="header">
|
| 344 |
+
<confidence value="5">1</confidence>
|
| 345 |
+
-WA<confidence value="5">/</confidence>
|
| 346 |
+
2607556.2 <confidence value="68">13</confidence>
|
| 347 |
+
</boundary-data>
|
| 348 |
+
<p id="p-53" num="53">
|
| 349 |
+
<page-break num="14"/>
|
| 350 |
+
<confidence value="5">[</confidence>
|
| 351 |
+
0051<confidence value="5">]</confidence>
|
| 352 |
+
In addition, if the liquid crystal driving pulse G2 is applied to the liquid crystal display according to the black-data insertion method, the falling edge of the final light-transmission characteristics G4 is not affected by the backlight driving pulse G<confidence value="28">1.</confidence>
|
| 353 |
+
</p>
|
| 354 |
+
<p id="p-54" num="54">Accordingly, the final light transmittance of the liquid crystal display at the falling edge decreases. This results in a decreased response time of the liquid crystal display at the falling edges of the final light transmission characteristics G4. Thus, the data voltage of the present frame can be prevented from affecting the data voltage of the next frame, thereby preventing motion blur.</p>
|
| 355 |
+
<p id="p-55" num="55">[0052<confidence value="5">]</confidence>
|
| 356 |
+
FIGs. 4 and <part-num-ref name="and">5</part-num-ref>
|
| 357 |
+
illustrate graphs showing examples of a reference signal and an active signal of the backlight driving pulse of FIG. 3. In the active lamp method, the backlight driving pulse G<confidence value="5">1</confidence>
|
| 358 |
+
includes the reference signal P1 for turning on the backlight unit <part-num-ref name="backlight unit">300</part-num-ref>
|
| 359 |
+
and the active signal P2. </p>
|
| 360 |
+
<p id="p-56" num="56">
|
| 361 |
+
<confidence value="5">[</confidence>
|
| 362 |
+
0053<confidence value="5">]</confidence>
|
| 363 |
+
FIG. 4 shows an example in which the reference signal P1 has a DC (Direct Current) level Vref and the active signal P2 has a saw-tooth waveform. FIG. 5 shows another example in which the reference signal P<confidence value="5">1</confidence>
|
| 364 |
+
has the DC level Vref and the active signal P2 has a rectangular waveform. The active signal P2 of the backlight driving pulse <confidence value="8">G</confidence>
|
| 365 |
+
<part-num-ref name="backlight driving pulse G">1</part-num-ref>
|
| 366 |
+
may be generated by generating the saw-tooth wave signal or the rectangular wave signal, whose width is substantially narrower than a typical period (e.g., about 16.7 <confidence value="588">ms)</confidence>
|
| 367 |
+
of one frame. </p>
|
| 368 |
+
<p id="p-57" num="57">
|
| 369 |
+
<confidence value="5">[</confidence>
|
| 370 |
+
0054 FIG. 6 illustrates graphs showing light-transmission characteristics of liquid crystal and final light-transmission characteristics of a liquid crystal display according to another embodiment of the present invention. In this embodiment, an active lamp <boundary-data type="header">
|
| 371 |
+
<confidence value="58685">1-WA/</confidence>
|
| 372 |
+
2607556.2 14 </boundary-data>
|
| 373 |
+
<page-break num="15"/>
|
| 374 |
+
method and a scanning backlight method, in which the backlight unit <part-num-ref name="backlight unit">300</part-num-ref>
|
| 375 |
+
is periodically turned on and off, are used as a backlight driving method, and a black-data insertion method is used as a liquid crystal driving method at the same time. </p>
|
| 376 |
+
<p id="p-58" num="58">[0055<confidence value="5">]</confidence>
|
| 377 |
+
Graph (a) of FIG. 6 shows light-transmission characteristics G3 of liquid crystal based on a liquid crystal driving pulse G2 when the video data (R, G, and B<confidence value="5">)</confidence>
|
| 378 |
+
have a given value. Graph (b) of FIG. 6 shows a backlight driving pulse G<confidence value="5">1</confidence>
|
| 379 |
+
when the scanning backlight method is used. Graph (c) of FIG. 6 shows final light-transmission characteristics G4 of the liquid crystal display when conditions of the graphs (a) and (b) are provided. The response time of the liquid crystal display at the rising edge of the final light transmission characteristics G4 of FIG. 6 is shorter (i.e., better) than that at the rising edge of the light-transmission characteristics G3 of FIG. 6. </p>
|
| 380 |
+
<p id="p-59" num="59">
|
| 381 |
+
<confidence value="5">[</confidence>
|
| 382 |
+
0056<confidence value="5">]</confidence>
|
| 383 |
+
FIGs. 7 and <part-num-ref name="and">8</part-num-ref>
|
| 384 |
+
illustrate graphs showing examples of a reference signal and an active signal of the backlight driving pulse of FIG. 6. The reference signal P1 of the backlight driving pulse G<confidence value="5">1</confidence>
|
| 385 |
+
is an AC (Alternating Current) signal in which a high voltage level and a low voltage level are alternatively repeated. </p>
|
| 386 |
+
<p id="p-60" num="60">
|
| 387 |
+
<confidence value="5">[</confidence>
|
| 388 |
+
0057<confidence value="5">]</confidence>
|
| 389 |
+
FIG. 7 shows an example in which the active signal P2 of the backlight driving pulse G<confidence value="5">1</confidence>
|
| 390 |
+
has a saw-tooth waveform. FIG. 8 shows an example in which the active signal P2 of the backlight driving pulse G<confidence value="5">1</confidence>
|
| 391 |
+
has a rectangular waveform. </p>
|
| 392 |
+
<p id="p-61" num="61">
|
| 393 |
+
<confidence value="68888">[0058</confidence>
|
| 394 |
+
FIG. 9 illustrates a flow chart showing a method for driving a liquid crystal display according to an embodiment of the present invention. As shown in FIG. 9, the method for driving a liquid crystal display includes a step <part-num-ref name="step">
|
| 395 |
+
<confidence value="5">5</confidence>
|
| 396 |
+
100 </part-num-ref>
|
| 397 |
+
during which the driver circuit <part-num-ref name="driver circuit">200</part-num-ref>
|
| 398 |
+
generates the liquid crystal driving pulse G2, a step S<confidence value="4">l</confidence>
|
| 399 |
+
<part-num-ref name="step Sl">10</part-num-ref>
|
| 400 |
+
during which the <boundary-data type="header">
|
| 401 |
+
<confidence value="5">1</confidence>
|
| 402 |
+
-WA<confidence value="5">/</confidence>
|
| 403 |
+
2607556.2 15 </boundary-data>
|
| 404 |
+
<page-break num="16"/>
|
| 405 |
+
backlight unit <part-num-ref name="backlight unit">300</part-num-ref>
|
| 406 |
+
generates the backlight driving pulse G<confidence value="5">1</confidence>
|
| 407 |
+
, and a step S<confidence value="5">1</confidence>
|
| 408 |
+
20 during which an image is displayed on the liquid crystal panel <part-num-ref name="liquid crystal panel">100.</part-num-ref>
|
| 409 |
+
</p>
|
| 410 |
+
<p id="p-62" num="62">
|
| 411 |
+
<confidence value="5">[</confidence>
|
| 412 |
+
0059<confidence value="5">]</confidence>
|
| 413 |
+
In the step S <part-num-ref name="step S">100,</part-num-ref>
|
| 414 |
+
the driver circuit <part-num-ref name="driver circuit">200</part-num-ref>
|
| 415 |
+
generates the liquid crystal driving pulse which, in each frame period, includes a normal data signal and a blanking signal. </p>
|
| 416 |
+
<p id="p-63" num="63">The step S100 may be divided into steps S<confidence value="555">1O1</confidence>
|
| 417 |
+
through <confidence value="5">S</confidence>
|
| 418 |
+
103. </p>
|
| 419 |
+
<p id="p-64" num="64">
|
| 420 |
+
<confidence value="5">[</confidence>
|
| 421 |
+
0060<confidence value="5">]</confidence>
|
| 422 |
+
First, in step S101, the timing controller <part-num-ref name="timing controller">230</part-num-ref>
|
| 423 |
+
provides a gate control signal GDC to control the gate driver <part-num-ref name="gate driver">210</part-num-ref>
|
| 424 |
+
and a data control signal DDC to control the source driver <part-num-ref name="source driver">220.</part-num-ref>
|
| 425 |
+
The timing controller <part-num-ref name="timing controller">230</part-num-ref>
|
| 426 |
+
also provides the video data (R, G, B) to the source driver <part-num-ref name="source driver">220.</part-num-ref>
|
| 427 |
+
In addition, the timing controller <part-num-ref name="timing controller">230</part-num-ref>
|
| 428 |
+
generates the light source control signal BDC to control the backlight unit <part-num-ref name="backlight unit">300</part-num-ref>
|
| 429 |
+
based on the active lamp method or the scanning backlight method. </p>
|
| 430 |
+
<p id="p-65" num="65">[0061] Next, in step S102, the gate driver <part-num-ref name="gate driver">210</part-num-ref>
|
| 431 |
+
provides a plurality of scan pluses to the gate lines GL of the liquid crystal panel <part-num-ref name="liquid crystal panel">100</part-num-ref>
|
| 432 |
+
in response to the gate control signal GDC from the timing controller <part-num-ref name="timing controller">230.</part-num-ref>
|
| 433 |
+
</p>
|
| 434 |
+
<p id="p-66" num="66">[0062] Next, in step S 103, the source driver <part-num-ref name="source driver">220</part-num-ref>
|
| 435 |
+
generates the liquid crystal driving pulse which, in each frame period, includes the normal data signal and the blanking signal. The source driver <part-num-ref name="source driver">220</part-num-ref>
|
| 436 |
+
provides the liquid crystal driving pulse to the data lines DL of the liquid crystal panel <part-num-ref name="liquid crystal panel">100</part-num-ref>
|
| 437 |
+
in response to the data control signal DDC from the timing controller <part-num-ref name="timing controller">230.</part-num-ref>
|
| 438 |
+
</p>
|
| 439 |
+
<p id="p-67" num="67">
|
| 440 |
+
<confidence value="5">[</confidence>
|
| 441 |
+
0063<confidence value="5">]</confidence>
|
| 442 |
+
The normal data signal represents a gamma voltage corresponding to red (R), green (G), and blue (B) video data. The blanking signal represents a gamma voltage having a black level corresponding to black video data. </p>
|
| 443 |
+
<boundary-data type="header">
|
| 444 |
+
<confidence value="6">I</confidence>
|
| 445 |
+
-WA/2607556.2 16 </boundary-data>
|
| 446 |
+
<p id="p-68" num="68">
|
| 447 |
+
<page-break num="17"/>
|
| 448 |
+
[0064<confidence value="5">]</confidence>
|
| 449 |
+
Each frame period of the liquid crystal driving pulse includes a data period <confidence value="884">(Tl</confidence>
|
| 450 |
+
) and a blanking period (T2) as shown, for example, in FIG. 3. The normal data signal is output as the liquid crystal driving pulse during the data period (T<confidence value="2">i</confidence>
|
| 451 |
+
) and the blanking signal is output as the liquid crystal driving pulse during the blanking period (T2). </p>
|
| 452 |
+
<p id="p-69" num="69">
|
| 453 |
+
<confidence value="5">[</confidence>
|
| 454 |
+
0065<confidence value="2">1</confidence>
|
| 455 |
+
In the step S<confidence value="2">i</confidence>
|
| 456 |
+
<part-num-ref name="step Si">
|
| 457 |
+
<confidence value="8">1</confidence>
|
| 458 |
+
0, </part-num-ref>
|
| 459 |
+
the light source controller <part-num-ref name="light source controller">260</part-num-ref>
|
| 460 |
+
generates the backlight driving pulse G<confidence value="5">1</confidence>
|
| 461 |
+
synchronized with the liquid crystal driving pulse G2 as shown, for example, in FIG. 3. The backlight driving pulse includes an active signal and a reference signal. Each frame period of the backlight driving pulse is divided into an active period (T3) and a reference period (T4). The backlight unit <part-num-ref name="backlight unit">300</part-num-ref>
|
| 462 |
+
maintains a substantially constant brightness level with the backlight driving pulse G<confidence value="5">1</confidence>
|
| 463 |
+
as shown, for example, in FIG. 3, or alternatively uses the scanning backlight method to turn on and off periodically as shown, for example, in FIG. 6. </p>
|
| 464 |
+
<p id="p-70" num="70">
|
| 465 |
+
<confidence value="5">[</confidence>
|
| 466 |
+
0066<confidence value="5">]</confidence>
|
| 467 |
+
The driver circuit <part-num-ref name="driver circuit">200</part-num-ref>
|
| 468 |
+
outputs the active signal and the reference signal of the backlight driving pulse. The active signal should be output within the data period (T<confidence value="2">i</confidence>
|
| 469 |
+
) of the liquid crystal driving pulse G2. In addition, the active period (T3) during which the active signal is output should be within the data period (T<confidence value="2">i</confidence>
|
| 470 |
+
). Since the light transmission characteristics at the falling edges of the liquid crystal driving pulse G2 may deteriorate if the active signal is output at the falling edges, the active period (T3) should be narrow enough to be included within the data period (T<confidence value="288">i).</confidence>
|
| 471 |
+
</p>
|
| 472 |
+
<boundary-data type="header">
|
| 473 |
+
<confidence value="5">1</confidence>
|
| 474 |
+
-WA<confidence value="4">1</confidence>
|
| 475 |
+
2607556.2 <confidence value="5">1</confidence>
|
| 476 |
+
<confidence value="8">7</confidence>
|
| 477 |
+
</boundary-data>
|
| 478 |
+
<p id="p-71" num="71">
|
| 479 |
+
<page-break num="18"/>
|
| 480 |
+
<confidence value="5">[</confidence>
|
| 481 |
+
0067<confidence value="5">]</confidence>
|
| 482 |
+
The active signal of the backlight driving pulse may include a saw-tooth wave as shown, for example in FIG. 4, or a rectangular wave as shown, for example in FIG. 5. </p>
|
| 483 |
+
<p id="p-72" num="72">The width of the active signal is substantially narrower than one frame period.</p>
|
| 484 |
+
<p id="p-73" num="73">
|
| 485 |
+
<confidence value="5">[</confidence>
|
| 486 |
+
0068<confidence value="5">]</confidence>
|
| 487 |
+
In the step S <part-num-ref name="step S">
|
| 488 |
+
<confidence value="6">1</confidence>
|
| 489 |
+
20, </part-num-ref>
|
| 490 |
+
an image, which has a light transmittance that varies depending upon the liquid crystal driving pulse and the backlight driving pulse, is displayed on the liquid crystal panel <part-num-ref name="liquid crystal panel">100.</part-num-ref>
|
| 491 |
+
</p>
|
| 492 |
+
<p id="p-74" num="74">
|
| 493 |
+
<confidence value="5">[</confidence>
|
| 494 |
+
0069<confidence value="5">]</confidence>
|
| 495 |
+
Thus, the backlight unit <part-num-ref name="backlight unit">300</part-num-ref>
|
| 496 |
+
of the liquid crystal display, into which the black data are inserted, is controlled with the backlight driving pulse. The backlight driving pulse can alternatively activate the backlight unit <part-num-ref name="backlight unit">300</part-num-ref>
|
| 497 |
+
or turn the backlight unit <part-num-ref name="backlight unit">300</part-num-ref>
|
| 498 |
+
on and off within one frame period. The light source in the backlight unit <part-num-ref name="backlight unit">300</part-num-ref>
|
| 499 |
+
is controlled based on the response characteristics of the liquid crystal. Thus, the deterioration of the brightness due to the black-data insertion method may be prevented, and the response time of the liquid crystal may be improved. Specifically, the response time at the rising edges may be enhanced, and the lagging (or increase) of the response time at the falling edges may be prevented. </p>
|
| 500 |
+
<p id="p-75" num="75">[0070<confidence value="5">]</confidence>
|
| 501 |
+
The liquid crystal display according to the example embodiments of the present invention adopts both a backlight driving method, by which the brightness of the backlight unit is actively controlled, and the black-data insertion method. As a result, the brightness and the response time of the liquid crystal display are enhanced. In addition, the method for driving the liquid crystal display according to an example embodiment of the present invention may drive the liquid crystal display more efficiently and effectively. </p>
|
| 502 |
+
<boundary-data type="header">
|
| 503 |
+
<confidence value="5">I</confidence>
|
| 504 |
+
<confidence value="8685">-WA/</confidence>
|
| 505 |
+
2607556.2 <confidence value="5">1</confidence>
|
| 506 |
+
<confidence value="6">g</confidence>
|
| 507 |
+
</boundary-data>
|
| 508 |
+
<p id="p-76" num="76">
|
| 509 |
+
<page-break num="19"/>
|
| 510 |
+
<confidence value="5">[</confidence>
|
| 511 |
+
0071<confidence value="5">]</confidence>
|
| 512 |
+
It will be apparent to those skilled in the art that various modifications and variations can be made in the liquid crystal display and a method for driving the same according to the present invention without departing from the spirit or scope of the invention. Thus, it is intended that the present invention cover the modifications and variations of this invention provided they come within the scope of the appended claims and their equivalents. </p>
|
| 513 |
+
<boundary-data type="header">
|
| 514 |
+
<confidence value="4">i</confidence>
|
| 515 |
+
<confidence value="8665888888">-WA1260755</confidence>
|
| 516 |
+
6.2 1<confidence value="5">9</confidence>
|
| 517 |
+
</boundary-data>
|
| 518 |
+
</description>
|
| 519 |
+
</us-patent-application>
|
| 520 |
+
|
applicant/11606289.xml
ADDED
|
@@ -0,0 +1,516 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>11606289</doc-number>
|
| 8 |
+
<date>2006-11-30</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<boundary-data type="header">V003 DS - Patent Applica<confidence value="6688">tion</confidence>
|
| 14 |
+
</boundary-data>
|
| 15 |
+
<heading id="h-1">APPARATUS AND METHOD FOR AUTOMATED INVENTORY</heading>
|
| 16 |
+
<heading id="h-2">TRACKING AND AUTHENTICATION</heading>
|
| 17 |
+
<p id="p-1" num="1">Field of the <confidence value="5">I</confidence>
|
| 18 |
+
nvention [0001] The invention is related to the fields of inventory management and telecommunication devices and services and more specifically, the invention is directed to an apparatus and method for tracking inventory of telecommunica- tions components and authenticating same prior to connection to a tele- communications service. </p>
|
| 19 |
+
<p id="p-2" num="2">Back<confidence value="8">g</confidence>
|
| 20 |
+
round of the <confidence value="5">I</confidence>
|
| 21 |
+
nvention [0002] Voice over IP (Vo<confidence value="5">I</confidence>
|
| 22 |
+
P) is a recent technological development in the field of telecommunications that is utilized to transmit voice over a broadband data network using the <confidence value="5">I</confidence>
|
| 23 |
+
nternet Protocol (IP) rather than the existing Public Switched Telephone Network (PSTN) or Plain Old Telephone Service (POTS). Internet Protocol is a part of the Transmission Control Protocol/Internet Protocol (TCP/IP) family of protocols described in software that tracks the Internet address of nodes, routes outgoing messages, and recognizes incoming messages. Such a data network may be the Internet or a corporate intranet, or any other TCP/IP network. Subscribers (either businesses or individuals) use Vo<confidence value="5">l</confidence>
|
| 24 |
+
P by purchasing and installing the necessary equipment to access a Vo<confidence value="5">I</confidence>
|
| 25 |
+
P service provider at their broadband-equipped location. Such Vo<confidence value="5">l</confidence>
|
| 26 |
+
P equipment would include, in one example, an adapter connected between the subscriber's PSTN phone and a broadband connection point (i.e., cable modem). </p>
|
| 27 |
+
<p id="p-3" num="3">[0003] The aforementioned Vo<confidence value="5">l</confidence>
|
| 28 |
+
P equipment is available from a few different sources including shipment (via a third party supplier) from a Vo<confidence value="5">l</confidence>
|
| 29 |
+
P service provider such as Vonage of Holmdel, New Jersey or direct purchase from a retail establishment specializing in consumer electronics and telecommunications <confidence value="2114">raFS</confidence>
|
| 30 |
+
T AVAILABLE COPY <page-break num="2"/>
|
| 31 |
+
<boundary-data type="header">V003 DS - Patent Application <confidence value="6">-</confidence>
|
| 32 |
+
</boundary-data>
|
| 33 |
+
devices. Since the supply chain for such Vo<confidence value="5">l</confidence>
|
| 34 |
+
P equipment varies, it is possible that such equipment may be lost, stolen or otherwise inappropriately distributed to a potential subscriber. If such "inappropriate" equipment were subsequently connected to a broadband connection and/or <confidence value="5">"</confidence>
|
| 35 |
+
hacked<confidence value="5">"</confidence>
|
| 36 |
+
to appear as legitimately obtained equipment, there is a potential for lost revenue due to the lack of sale of the Vo<confidence value="5">l</confidence>
|
| 37 |
+
P equipment as well as the subsequent use of same in a subscriber- based business model. </p>
|
| 38 |
+
<p id="p-4" num="4">[0004] Therefore, there is a need in the art for an apparatus and method that provides for controlled access to an inventory control system (ICS) that mitigates the aforementioned problems of inventory theft and loss of services.</p>
|
| 39 |
+
<p id="p-5" num="5">Summary of the <confidence value="5">I</confidence>
|
| 40 |
+
nvention [0005] The present invention generally relates to a method and apparatus for automated inventory tracking and device authentication using device identity- containing information associated with at least one device that is part of an inventory. In one embodiment of the invention, the method includes accepting initial device identity-containing information from an inventory origination point to a first sales distribution point and accepting additional device identity-containing inventory from each instance of a new and successive sales distribution point as inventory moves through a supply chain. This information is stored and then later compared to a device ID of the at least one device. In this way, an authentication action is performed upon the at least one device based upon said accepted initial and additional information. In one embodiment of the invention, the device identity-containing information includes MAC address information, device serial number information. </p>
|
| 41 |
+
<p id="p-6" num="6">[0006] Authentication includes successfully registering the device to access a service (such as a telecommunications service and most preferably a Vo<confidence value="68">lP</confidence>
|
| 42 |
+
service). Alternately, authentication includes confirming that the device is at a <page-break num="3"/>
|
| 43 |
+
<boundary-data type="header">V003 DS - Patent Application</boundary-data>
|
| 44 |
+
proper location in <confidence value="1">t</confidence>
|
| 45 |
+
he supply chain (such action preferably performed by an inventory control manager). Authentication is not performed if the device is found to be stolen, tampered or otherwise improperly obtained or used. Authentication is performed if the device ID associated with the at least one device matches device identity-containing information provided through the supply chain movement. </p>
|
| 46 |
+
<p id="p-7" num="7">[0007] In one embodiment of the invention, accepting of the initial and additional device identity-containing information occurs after delivery of the inventory from the origination point and each instance of the new and successive sales distribution point respectively. Regardless of which point, the accepting of said initial device identity-containing information occurs within <part-num-ref name="accepting of said initial device identity-containing information occurs within">24</part-num-ref>
|
| 47 |
+
hours after delivery of the inventory. </p>
|
| 48 |
+
<p id="p-8" num="8">[0008] In another embodiment of the invention, a system for tracking inventory and performing device authentication using device identity-containing information associated with at least one device that is part of an inventory is provided. The system includes means for accepting initial device identity-containing information from an inventory origination point to a first sales distribution point and additional device identity-containing inventory from each instance of a new and successive sales distribution point as inventory moves through a supply chain, means for storing said initial and additional device identity-containing information and means for authenticating said at least one device based upon said accepted initial and additional information.</p>
|
| 49 |
+
<p id="p-9" num="9">Brief Descri<confidence value="5">p</confidence>
|
| 50 |
+
tion of the FIGURES [0009] So that the manner in which the above recited features of the present invention are attained and can be understood in detail, a more particular description of the invention, briefly summarized above, may be had by reference to the embodiments thereof which are illustrated in the appended drawings. </p>
|
| 51 |
+
<boundary-data type="header">V003 DS - Patent Application</boundary-data>
|
| 52 |
+
<p id="p-10" num="10">
|
| 53 |
+
<page-break num="4"/>
|
| 54 |
+
[0010] It is to be noted, however, that the appended drawings illustrate only typical embodiments of this invention and are therefore not to be considered limiting of its scope, for the invention may admit to other equally effective embodiments. </p>
|
| 55 |
+
<p id="p-11" num="11">[0011<confidence value="5">]</confidence>
|
| 56 |
+
FIGURE 1 depicts a block diagram of an inventory control system in accordance with the subject invention; </p>
|
| 57 |
+
<p id="p-12" num="12">[0012<confidence value="5">]</confidence>
|
| 58 |
+
FIGURE 2 depicts a series of method steps for practicing a first embodiment of an inventory control and device authentication operation in accordance with the subject invention; </p>
|
| 59 |
+
<p id="p-13" num="13">[0013] FIGURE 3 depicts a schematic diagram of a controller that may <confidence value="88">be</confidence>
|
| 60 |
+
used to practice one or more embodiments of the present invention; </p>
|
| 61 |
+
<p id="p-14" num="14">[0014] FIGURE 4 depicts a series of method steps for practicing a second embodiment of an inventory control and device authentication operation in accordance with the subject invention; and [0015] FIGURE 5 depicts a series of method steps for practicing an error checking subrountine component of an inventory control and device authentication operation in accordance with the subject invention.</p>
|
| 62 |
+
<p id="p-15" num="15">[0016] To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures.</p>
|
| 63 |
+
<boundary-data type="header">V003 DS - Patent Application</boundary-data>
|
| 64 |
+
<p id="p-16" num="16">
|
| 65 |
+
<page-break num="5"/>
|
| 66 |
+
Detailed Descri<confidence value="5">p</confidence>
|
| 67 |
+
tion [0017] To achieve the desired objectives, the subject invention provides for an apparatus and method that provides for controlled access to an inventory control system (ICS). Such ICS is adapted to receive inventory information that allows for the authentication of individual members (or pieces) of the inventory as such pieces move through a supply chain starting at the piece manufacturer and ending at a retailer. Authentication of the inventory assures that the pieces moved properly through the supply chain and are available to provide the function(s) for which they were intended. Lack of authentication of a piece of inventory indicates that the piece may have been inappropriately handled (i.e., lost, stolen, improperly returned or the like) at some point in the supply chain and is no longer available to provide its intended function such as providing telecommunication services to a user. </p>
|
| 68 |
+
<p id="p-17" num="17">[0018] FIG. <confidence value="5">1</confidence>
|
| 69 |
+
depicts a system level block diagram of an inventory management environment <part-num-ref name="inventory management environment">100</part-num-ref>
|
| 70 |
+
in which the subject invention may be practiced. </p>
|
| 71 |
+
<p id="p-18" num="18">Particularly, the inventory management environment <part-num-ref name="inventory management environment">100</part-num-ref>
|
| 72 |
+
comprises an ICS <part-num-ref name="ICS">108,</part-num-ref>
|
| 73 |
+
a plurality of inventory information locations <part-num-ref name="plurality of inventory information locations">(110</part-num-ref>
|
| 74 |
+
and 116), at least one point of sa<confidence value="8">l</confidence>
|
| 75 |
+
e location (e.g., retailer) <part-num-ref name="retailer)">122,</part-num-ref>
|
| 76 |
+
one or more inventory end users <part-num-ref name="retailer) 122, one or more inventory end users">112</part-num-ref>
|
| 77 |
+
and optionally one or more ICS managers <part-num-ref name="and optionally one or more ICS managers">114.</part-num-ref>
|
| 78 |
+
The ICS <part-num-ref name="ICS">108</part-num-ref>
|
| 79 |
+
accepts inventory management information (as explained in greater detail below) from the plurality of inventory information locations <part-num-ref name="plurality of inventory information locations">(110</part-num-ref>
|
| 80 |
+
and <part-num-ref name="and">116)</part-num-ref>
|
| 81 |
+
as inventory moves through a supply chain. At some point in time, a piece of the inventory is sold (e.g., from a retailer <part-num-ref name="retailer">122)</part-num-ref>
|
| 82 |
+
to a end user (i.e., consumer) <part-num-ref name="consumer)">112.</part-num-ref>
|
| 83 |
+
The end user <part-num-ref name="end user">112</part-num-ref>
|
| 84 |
+
then accesses the ICS <part-num-ref name="ICS">108</part-num-ref>
|
| 85 |
+
(either directly or indirectly) as part of a procedure for registering and/or authenticating the inventory piece. Depending upon the inventory management information that the ICS <part-num-ref name="ICS">108</part-num-ref>
|
| 86 |
+
has accepted from the plurality of inventory information locations <part-num-ref name="plurality of inventory information locations">110</part-num-ref>
|
| 87 |
+
and 116), the inventory piece may pass or fail the registration and/or authentication procedure. </p>
|
| 88 |
+
<boundary-data type="header">V003 <confidence value="66">DS</confidence>
|
| 89 |
+
- Patent Application </boundary-data>
|
| 90 |
+
<p id="p-19" num="19">
|
| 91 |
+
<page-break num="6"/>
|
| 92 |
+
[0019] I<confidence value="5">n</confidence>
|
| 93 |
+
one embodiment of the invention, the ICS <part-num-ref name="ICS">108</part-num-ref>
|
| 94 |
+
further comprises a database <part-num-ref name="database">104,</part-num-ref>
|
| 95 |
+
one or more servers <part-num-ref name="database 104, one or more servers">102</part-num-ref>
|
| 96 |
+
and one or more interfaces (106<confidence value="88">).</confidence>
|
| 97 |
+
</p>
|
| 98 |
+
<p id="p-20" num="20">Specifically, the database <part-num-ref name="database">104</part-num-ref>
|
| 99 |
+
organizes and holds the inventory management information that is received from the plurality of inventory information locations <part-num-ref name="plurality of inventory information locations">(110</part-num-ref>
|
| 100 |
+
and 116). The database may be any assembly, collection or construction of hardware and or software configured to accept data and such a database is well known in the art. The database <part-num-ref name="database">104</part-num-ref>
|
| 101 |
+
is connected to at least one ICS server <part-num-ref name="is connected to at least one ICS server">102</part-num-ref>
|
| 102 |
+
that is adapted to control input/output functions including queries to the database <part-num-ref name="database">104</part-num-ref>
|
| 103 |
+
and receiving and organizing inventory management information. </p>
|
| 104 |
+
<p id="p-21" num="21">[0020] <confidence value="5">I</confidence>
|
| 105 |
+
n one embodiment of the invention, depicted in FIG. 1, there are two ICS servers <part-num-ref name="invention, depicted in FIG. 1, there are two ICS servers">102</part-num-ref>
|
| 106 |
+
each having a dedicated purpose. For example, in the depicted embodiment, a first ICS server <part-num-ref name="first ICS server">102<confidence value="2">1</confidence>
|
| 107 |
+
</part-num-ref>
|
| 108 |
+
controls input/output functions of inventory management information from the plurality of inventory information locations <part-num-ref name="plurality of inventory information locations">(110</part-num-ref>
|
| 109 |
+
and <part-num-ref name="and">116)</part-num-ref>
|
| 110 |
+
and a second ICS server <part-num-ref name="second ICS server">1022</part-num-ref>
|
| 111 |
+
controls input/output functions regarding registration/authentication of individual inventory members. The authentication procedure, in one embodiment of the invention, may be conducted by entities selected from the group consisting of one or more end users of inventory <part-num-ref name="group consisting of one or more end users of inventory">112</part-num-ref>
|
| 112 |
+
and ICS manager(s) <part-num-ref name="and ICS manager(s)">114.</part-num-ref>
|
| 113 |
+
In the depicted embodiment, each of the ICS servers <part-num-ref name="ICS servers">102</part-num-ref>
|
| 114 |
+
is connected to an interface <part-num-ref name="interface">106</part-num-ref>
|
| 115 |
+
adapted to provide communication between the ICS <part-num-ref name="ICS">108</part-num-ref>
|
| 116 |
+
and the rest of the environment <part-num-ref name="environment">100.</part-num-ref>
|
| 117 |
+
Specifically in the depicted embodiment, a first interface <part-num-ref name="first interface">
|
| 118 |
+
<confidence value="5882">1061</confidence>
|
| 119 |
+
</part-num-ref>
|
| 120 |
+
provides communication between the first ICS server <part-num-ref name="first ICS server">
|
| 121 |
+
<confidence value="6682">1021</confidence>
|
| 122 |
+
</part-num-ref>
|
| 123 |
+
and the plurality of inventory information locations <part-num-ref name="plurality of inventory information locations">(110</part-num-ref>
|
| 124 |
+
and <part-num-ref name="and">116)</part-num-ref>
|
| 125 |
+
and a second interface <part-num-ref name="second interface">1062</part-num-ref>
|
| 126 |
+
provides communication between the second ICS server <part-num-ref name="second ICS server">1022</part-num-ref>
|
| 127 |
+
and one or more end users of inventory <part-num-ref name="and one or more end users of inventory">112</part-num-ref>
|
| 128 |
+
and/or ICS manager(s) <part-num-ref name="and/or ICS manager(s)">114.</part-num-ref>
|
| 129 |
+
</p>
|
| 130 |
+
<p id="p-22" num="22">The interfaces 106 are any typical network-oriented interface that are capable of providing <confidence value="5">I</confidence>
|
| 131 |
+
nternet-based communications to/from the ICS server(s) <part-num-ref name="ICS server(s)">102</part-num-ref>
|
| 132 |
+
and are known to those skilled in the art. </p>
|
| 133 |
+
<p id="p-23" num="23">[0021] As presented earlier, the ICS <part-num-ref name="ICS">108</part-num-ref>
|
| 134 |
+
accepts inventory management information from the plurality of inventory information locations <part-num-ref name="plurality of inventory information locations">(110</part-num-ref>
|
| 135 |
+
and <part-num-ref name="and">116)</part-num-ref>
|
| 136 |
+
as <page-break num="7"/>
|
| 137 |
+
<boundary-data type="header">V003 DS - Patent Application</boundary-data>
|
| 138 |
+
inventory moves through a supply chain. The following description provides an example of the flow of this information with regard to a telecommunication device <part-num-ref name="telecommunication device">118</part-num-ref>
|
| 139 |
+
being the above-introduced inventory member or piece. Accordingly, this exemplary description is not intended to limit the scope of the subject invention, as the overall method and attendant apparatus for practicing the method are applicable to a variety of different inventory members where security, authentication or general desire to track inventory to prevent loss, theft or other undesirable business conditions will be known to those skilled in the art. </p>
|
| 140 |
+
<p id="p-24" num="24">[0022] In detail, inventory management information is passed from the inventory information locations <part-num-ref name="inventory information locations">(110</part-num-ref>
|
| 141 |
+
and <part-num-ref name="and">116)</part-num-ref>
|
| 142 |
+
to the ICS <part-num-ref name="ICS">108</part-num-ref>
|
| 143 |
+
via a plurality of inventory file paths <part-num-ref name="plurality of inventory file paths">(150,</part-num-ref>
|
| 144 |
+
152). Depending on the type of file and type of inventory information location, a particular file is created and passed along a particular file path. As such, information that indicates which inventory members (i.e., devices <part-num-ref name="devices">118)</part-num-ref>
|
| 145 |
+
are at which inventory information location <part-num-ref name="are at which inventory information location">(110,</part-num-ref>
|
| 146 |
+
<part-num-ref name="are at which inventory information location (110,">116)</part-num-ref>
|
| 147 |
+
or a point of sale location <part-num-ref name="point of sale location">122</part-num-ref>
|
| 148 |
+
is accurately and securely forwarded to the database <part-num-ref name="database">104</part-num-ref>
|
| 149 |
+
for updating. A first occurrence of inventory movement is identified by first inventory movement path <part-num-ref name="first occurrence of inventory movement is identified by first inventory movement path">120.</part-num-ref>
|
| 150 |
+
In this first occurrence, devices <part-num-ref name="first occurrence of inventory movement is identified by first inventory movement path 120. In this first occurrence, devices">118</part-num-ref>
|
| 151 |
+
are shipped from a device manufacturer <part-num-ref name="device manufacturer">110</part-num-ref>
|
| 152 |
+
(or other similar point of origination) to a manufacturer<confidence value="8">'</confidence>
|
| 153 |
+
s distributor <part-num-ref name="manufacturer's distributor">
|
| 154 |
+
<confidence value="6682">1161</confidence>
|
| 155 |
+
</part-num-ref>
|
| 156 |
+
along a first inventory movement first subpath <part-num-ref name="first inventory movement first subpath">
|
| 157 |
+
<confidence value="6866">1201</confidence>
|
| 158 |
+
, </part-num-ref>
|
| 159 |
+
then from the manufacturer<confidence value="8">'</confidence>
|
| 160 |
+
s distributor <part-num-ref name="manufacturer's distributor">
|
| 161 |
+
<confidence value="6682">1161</confidence>
|
| 162 |
+
</part-num-ref>
|
| 163 |
+
to a regional distributor <part-num-ref name="regional distributor">
|
| 164 |
+
<confidence value="5885">1162</confidence>
|
| 165 |
+
</part-num-ref>
|
| 166 |
+
along a first inventory movement second subpath <part-num-ref name="first inventory movement second subpath">1202</part-num-ref>
|
| 167 |
+
and finally from the regional distributor <part-num-ref name="regional distributor">1162</part-num-ref>
|
| 168 |
+
to a retail location <part-num-ref name="retail location">122</part-num-ref>
|
| 169 |
+
along a first inventory movement third subpath <part-num-ref name="first inventory movement third subpath">1203.</part-num-ref>
|
| 170 |
+
</p>
|
| 171 |
+
<p id="p-25" num="25">[0023<confidence value="5">]</confidence>
|
| 172 |
+
After devices 118 have moved along a first inventory movement first subpath <part-num-ref name="first inventory movement first subpath">120<confidence value="5">1</confidence>
|
| 173 |
+
, </part-num-ref>
|
| 174 |
+
inventory management information in the form of a Manufacturer<confidence value="68">'s</confidence>
|
| 175 |
+
Comma Separated Value File is sent along a manufacturer<confidence value="8">'</confidence>
|
| 176 |
+
s file path (MFP) <part-num-ref name="manufacturer's file path (MFP)">150</part-num-ref>
|
| 177 |
+
to the ICS <part-num-ref name="ICS">108.</part-num-ref>
|
| 178 |
+
More specifically, once the manufacturer <part-num-ref name="manufacturer">110</part-num-ref>
|
| 179 |
+
has shipped one or more devices <part-num-ref name="has shipped one or more devices">118,</part-num-ref>
|
| 180 |
+
the Manufacturer's Comma Separated Value File is sent along a MFP <part-num-ref name="MFP">150</part-num-ref>
|
| 181 |
+
to the interface <part-num-ref name="interface">106<confidence value="5">1</confidence>
|
| 182 |
+
. </part-num-ref>
|
| 183 |
+
The interface <part-num-ref name="interface">106<confidence value="2">1</confidence>
|
| 184 |
+
</part-num-ref>
|
| 185 |
+
then passes the file to <page-break num="8"/>
|
| 186 |
+
<boundary-data type="header">V003 DS - Patent Application</boundary-data>
|
| 187 |
+
the first <confidence value="222222">seryer</confidence>
|
| 188 |
+
<part-num-ref name="first seryer">102<confidence value="2">1</confidence>
|
| 189 |
+
</part-num-ref>
|
| 190 |
+
which then (after executing a security function such as a User ID and password matching process) passes the file to the database <part-num-ref name="database">104</part-num-ref>
|
| 191 |
+
where the inventory information contained therein is updated according to the data in the file. In one embodiment of the invention, the security function introduced above and subsequently referenced below is performed over a secure website access environment (i.e., using the https protocol). Preferably, all entities that are required to send inventory control information to the ICS <part-num-ref name="ICS">108</part-num-ref>
|
| 192 |
+
provide at least one IP address in order to access the ICS <part-num-ref name="ICS">108.</part-num-ref>
|
| 193 |
+
</p>
|
| 194 |
+
<p id="p-26" num="26">[0024] After devices 118 have moved along a first inventory movement second subpath <part-num-ref name="first inventory movement second subpath">1202,</part-num-ref>
|
| 195 |
+
inventory management information in the form of a Ship Out Comma Separated Value File is sent along a first ship out file path (SOFP) <part-num-ref name="first ship out file path (SOFP)">
|
| 196 |
+
<confidence value="5882">1521</confidence>
|
| 197 |
+
</part-num-ref>
|
| 198 |
+
to the ICS <part-num-ref name="ICS">108.</part-num-ref>
|
| 199 |
+
More specifically, once the manufacturer's distributor <part-num-ref name="manufacturer's distributor">11<confidence value="82">61</confidence>
|
| 200 |
+
</part-num-ref>
|
| 201 |
+
has shipped one or more devices <part-num-ref name="has shipped one or more devices">118,</part-num-ref>
|
| 202 |
+
the Ship Out Comma Separated Value File is sent along the first SOFP <part-num-ref name="first SOFP">152<confidence value="2">1</confidence>
|
| 203 |
+
</part-num-ref>
|
| 204 |
+
to the interface <part-num-ref name="interface">106<confidence value="5">1</confidence>
|
| 205 |
+
. </part-num-ref>
|
| 206 |
+
The interface <part-num-ref name="interface">
|
| 207 |
+
<confidence value="5882">1061</confidence>
|
| 208 |
+
</part-num-ref>
|
| 209 |
+
then passes the file to the first server <part-num-ref name="first server">
|
| 210 |
+
<confidence value="6682">1021</confidence>
|
| 211 |
+
</part-num-ref>
|
| 212 |
+
which then (after executing a security function such as a User ID and password matching process) passes the file to the database <part-num-ref name="database">104</part-num-ref>
|
| 213 |
+
where the inventory information contained therein is updated according to the data in the file. </p>
|
| 214 |
+
<p id="p-27" num="27">[0025] After devices 118 have moved along a first inventory movement third subpath <part-num-ref name="first inventory movement third subpath">1203,</part-num-ref>
|
| 215 |
+
inventory management information in the form of a Ship Out Comma Separated Value File is sent along a second SOFP <part-num-ref name="second SOFP">1522</part-num-ref>
|
| 216 |
+
to the ICS <part-num-ref name="ICS">108.</part-num-ref>
|
| 217 |
+
</p>
|
| 218 |
+
<p id="p-28" num="28">More specifically, once the distributor <part-num-ref name="distributor">1162</part-num-ref>
|
| 219 |
+
has shipped one or more devices <part-num-ref name="has shipped one or more devices">118,</part-num-ref>
|
| 220 |
+
the Ship Out Comma Separated Value File is sent along the second SOFP <part-num-ref name="second SOFP">1522</part-num-ref>
|
| 221 |
+
to the interface <part-num-ref name="interface">
|
| 222 |
+
<confidence value="6686">1061</confidence>
|
| 223 |
+
. </part-num-ref>
|
| 224 |
+
The interface <part-num-ref name="interface">
|
| 225 |
+
<confidence value="5882">1061</confidence>
|
| 226 |
+
</part-num-ref>
|
| 227 |
+
then passes the file to the first server <part-num-ref name="first server">
|
| 228 |
+
<confidence value="6682">1021</confidence>
|
| 229 |
+
</part-num-ref>
|
| 230 |
+
which then (after executing a security function such as a User ID and password matching process) passes the file to the database <part-num-ref name="database">104</part-num-ref>
|
| 231 |
+
where the inventory information contained therein is updated according to the data in the file. </p>
|
| 232 |
+
<boundary-data type="header">V003 DS - Patent Application</boundary-data>
|
| 233 |
+
<p id="p-29" num="29">
|
| 234 |
+
<page-break num="9"/>
|
| 235 |
+
[0026] A second occurrence of inventory movement is identified by a second inventory movement path <part-num-ref name="second inventory movement path">130.</part-num-ref>
|
| 236 |
+
In this second occurrence, devices <part-num-ref name="second inventory movement path 130. In this second occurrence, devices">118</part-num-ref>
|
| 237 |
+
are shipped from the device manufacturer <part-num-ref name="device manufacturer">110</part-num-ref>
|
| 238 |
+
(or other similar point of origination) directly to the retailer <part-num-ref name="retailer">122.</part-num-ref>
|
| 239 |
+
After devices <part-num-ref name="retailer 122. After devices">118</part-num-ref>
|
| 240 |
+
have moved along the second inventory movement path <part-num-ref name="second inventory movement path">130,</part-num-ref>
|
| 241 |
+
inventory management information in the form of a Manufacturer's Comma Separated Value File is sent along the MFP <part-num-ref name="MFP">150</part-num-ref>
|
| 242 |
+
to the ICS <part-num-ref name="ICS">108.</part-num-ref>
|
| 243 |
+
More specifically and similar to the description with respect to the first inventory movement path <part-num-ref name="first inventory movement path">120,</part-num-ref>
|
| 244 |
+
once the manufacturer <part-num-ref name="manufacturer">110</part-num-ref>
|
| 245 |
+
has shipped one or more devices <part-num-ref name="has shipped one or more devices">118,</part-num-ref>
|
| 246 |
+
the Manufacturer<confidence value="5">'</confidence>
|
| 247 |
+
s Comma Separated Value File is sent along the MFP <part-num-ref name="MFP">150</part-num-ref>
|
| 248 |
+
to the interface <part-num-ref name="interface">106<confidence value="5">1</confidence>
|
| 249 |
+
. </part-num-ref>
|
| 250 |
+
The interface <part-num-ref name="interface">
|
| 251 |
+
<confidence value="5882">1061</confidence>
|
| 252 |
+
</part-num-ref>
|
| 253 |
+
then passes the file to the first server <part-num-ref name="first server">
|
| 254 |
+
<confidence value="6682">1021</confidence>
|
| 255 |
+
</part-num-ref>
|
| 256 |
+
which then (after executing a security function such as a User ID and password matching process) passes the file to the database <part-num-ref name="database">104</part-num-ref>
|
| 257 |
+
where the inventory information contained therein is updated according to the data in the file. In this scenario, no Ship Out Comma Separated Value Files are used. </p>
|
| 258 |
+
<p id="p-30" num="30">[0027] A third occurrence of inventory movement is identified by third inventory movement path <part-num-ref name="third occurrence of inventory movement is identified by third inventory movement path">140.</part-num-ref>
|
| 259 |
+
In this third occurrence, devices <part-num-ref name="third occurrence of inventory movement is identified by third inventory movement path 140. In this third occurrence, devices">118</part-num-ref>
|
| 260 |
+
are shipped from a device manufacturer <part-num-ref name="device manufacturer">110</part-num-ref>
|
| 261 |
+
(or other similar point of origination) to a manufacturer's distributor <part-num-ref name="manufacturer's distributor">11<confidence value="86">61</confidence>
|
| 262 |
+
</part-num-ref>
|
| 263 |
+
along a third inventory movement first subpath <part-num-ref name="third inventory movement first subpath">
|
| 264 |
+
<confidence value="6862">1401</confidence>
|
| 265 |
+
</part-num-ref>
|
| 266 |
+
(which is identical to first inventory movement first subpath <confidence value="6866">1201</confidence>
|
| 267 |
+
), then from the manufacturer's distributor <part-num-ref name="manufacturer's distributor">116<confidence value="2">1</confidence>
|
| 268 |
+
</part-num-ref>
|
| 269 |
+
to a retailer <part-num-ref name="retailer">122</part-num-ref>
|
| 270 |
+
along a third inventory movement second subpath <part-num-ref name="third inventory movement second subpath">1402<confidence value="5">.</confidence>
|
| 271 |
+
</part-num-ref>
|
| 272 |
+
</p>
|
| 273 |
+
<p id="p-31" num="31">[0028<confidence value="5">]</confidence>
|
| 274 |
+
After devices 118 have moved along the third inventory movement first subpath <part-num-ref name="third inventory movement first subpath">140<confidence value="5">1</confidence>
|
| 275 |
+
, </part-num-ref>
|
| 276 |
+
inventory management information in the form of a Manufacturer<confidence value="68">'s</confidence>
|
| 277 |
+
Comma Separated Value File is sent along the MFP <part-num-ref name="MFP">150</part-num-ref>
|
| 278 |
+
to the ICS <part-num-ref name="ICS">108.</part-num-ref>
|
| 279 |
+
More specifically, once the manufacturer <part-num-ref name="manufacturer">110</part-num-ref>
|
| 280 |
+
has shipped one or more devices <part-num-ref name="has shipped one or more devices">118,</part-num-ref>
|
| 281 |
+
the Manufacturer's Comma Separated Value File is sent along the MFP <part-num-ref name="MFP">150</part-num-ref>
|
| 282 |
+
to the interface <part-num-ref name="interface">106<confidence value="5">1</confidence>
|
| 283 |
+
. </part-num-ref>
|
| 284 |
+
The interface <part-num-ref name="interface">106<confidence value="2">1</confidence>
|
| 285 |
+
</part-num-ref>
|
| 286 |
+
then passes the file to the first server <part-num-ref name="first server">102<confidence value="5">,</confidence>
|
| 287 |
+
</part-num-ref>
|
| 288 |
+
which then (after executing a security function such as a User ID and password <page-break num="10"/>
|
| 289 |
+
<boundary-data type="header">V003 DS - Patent Application</boundary-data>
|
| 290 |
+
matching process) passes the file to the database <part-num-ref name="database">104</part-num-ref>
|
| 291 |
+
where the inventory information contained therein is updated according to the data in the file. </p>
|
| 292 |
+
<p id="p-32" num="32">[0029] After devices 118 have moved along the third inventory movement second subpath <part-num-ref name="third inventory movement second subpath">1402,</part-num-ref>
|
| 293 |
+
inventory management information in the form of a Ship Out Comma Separated Value File is sent along a first SOFP <part-num-ref name="first SOFP">
|
| 294 |
+
<confidence value="5882">1521</confidence>
|
| 295 |
+
</part-num-ref>
|
| 296 |
+
to the ICS <part-num-ref name="ICS">108.</part-num-ref>
|
| 297 |
+
</p>
|
| 298 |
+
<p id="p-33" num="33">More specifically, once the manufacturer's distributor <part-num-ref name="manufacturer's distributor">
|
| 299 |
+
<confidence value="6686">1161</confidence>
|
| 300 |
+
</part-num-ref>
|
| 301 |
+
has shipped one or more devices <part-num-ref name="has shipped one or more devices">118,</part-num-ref>
|
| 302 |
+
the Ship Out Comma Separated Value File is sent along the first SOFP <part-num-ref name="first SOFP">152<confidence value="2">1</confidence>
|
| 303 |
+
</part-num-ref>
|
| 304 |
+
to the interface <part-num-ref name="interface">106<confidence value="5">1</confidence>
|
| 305 |
+
. </part-num-ref>
|
| 306 |
+
The interface <part-num-ref name="interface">106<confidence value="2">1</confidence>
|
| 307 |
+
</part-num-ref>
|
| 308 |
+
then passes the file to the first server <part-num-ref name="first server">
|
| 309 |
+
<confidence value="6682">1021</confidence>
|
| 310 |
+
</part-num-ref>
|
| 311 |
+
which then (after executing a security function such as a User ID and password matching process) passes the file to the database <part-num-ref name="database">104</part-num-ref>
|
| 312 |
+
where the inventory information contained therein is updated according to the data in the file. In each occurrence of inventory movement described above, the point of sale location or retailer <part-num-ref name="point of sale location or retailer">122</part-num-ref>
|
| 313 |
+
does not send any inventory management information to the ICS <part-num-ref name="ICS">108</part-num-ref>
|
| 314 |
+
for the above-described purposes. Additionally and for sake of clarity, there can be only one Manufacturer's Comma Separated Value File entry for any given device <part-num-ref name="above-described purposes. Additionally and for sake of clarity, there can be only one Manufacturer's Comma Separated Value File entry for any given device">118</part-num-ref>
|
| 315 |
+
as it enters the supply chain. However, there can be multiple Ship Out Comma Separated Value File entries for any given device as such entries are generated every time a device moves along the supply chain after leaving the originating point. </p>
|
| 316 |
+
<p id="p-34" num="34">[0030] According to the described inventory movement pathways, eventually all inventory members (i.e., devices <part-num-ref name="devices">118)</part-num-ref>
|
| 317 |
+
should arrive at a retailer <part-num-ref name="retailer">122</part-num-ref>
|
| 318 |
+
where they are subsequently purchased by an end user. The end user will then bring the device home, connect the device to a broadband access point and attempt to activate/register the device <part-num-ref name="device">118</part-num-ref>
|
| 319 |
+
(or a service associated therewith) by interacting with a web-based authentication process. The authentication process will compare information exclusive to and associated with the device <part-num-ref name="device">118</part-num-ref>
|
| 320 |
+
with information in the database <part-num-ref name="database">104.</part-num-ref>
|
| 321 |
+
In making this comparison, the ICS <part-num-ref name="ICS">108</part-num-ref>
|
| 322 |
+
can make a determination as to whether the device has properly moved through the supply chain and it (or the service associated therewith) should be activated. </p>
|
| 323 |
+
<boundary-data type="header">V003 DS - Patent Application</boundary-data>
|
| 324 |
+
<p id="p-35" num="35">
|
| 325 |
+
<page-break num="11"/>
|
| 326 |
+
[0031] In one embodiment of this authentication process, the device <part-num-ref name="device">118</part-num-ref>
|
| 327 |
+
is connected to a consumer<confidence value="8">'</confidence>
|
| 328 |
+
s computer <part-num-ref name="consumer's computer">112</part-num-ref>
|
| 329 |
+
and the computer <part-num-ref name="computer">112</part-num-ref>
|
| 330 |
+
connects to the ICS <part-num-ref name="ICS">108</part-num-ref>
|
| 331 |
+
via the second interface <part-num-ref name="second interface">1062</part-num-ref>
|
| 332 |
+
(<confidence value="66">i.</confidence>
|
| 333 |
+
e, an authentication interface). The second interface <part-num-ref name="second interface">1062</part-num-ref>
|
| 334 |
+
provides communication between the second ICS server <part-num-ref name="second ICS server">1022</part-num-ref>
|
| 335 |
+
and one or more end users of inventory <part-num-ref name="and one or more end users of inventory">112</part-num-ref>
|
| 336 |
+
and/or ICS manager(s) <part-num-ref name="and/or ICS manager(s)">114.</part-num-ref>
|
| 337 |
+
</p>
|
| 338 |
+
<p id="p-36" num="36">The authentication process reads an identifier selected from the group consisting of a device serial number and a MAC address and compares same to the information in the database <part-num-ref name="database">104.</part-num-ref>
|
| 339 |
+
If the information specific to the device <part-num-ref name="device">118</part-num-ref>
|
| 340 |
+
is valid (i.e., the information has been passed (via different files) through the complete supply chain), then the device or the service associated therewith is registered and activated. If the information specific to the device <part-num-ref name="device">118</part-num-ref>
|
| 341 |
+
is not valid (i.e., the information was not passed through the complete supply chain), then at some point, the device was improperly removed from the supply chain and it or the service associated therewith cannot be registered or activated. </p>
|
| 342 |
+
<p id="p-37" num="37">[0032] In a second embodiment of the invention, one or more ICS manager(s) <part-num-ref name="invention, one or more ICS manager(s)">114</part-num-ref>
|
| 343 |
+
access the ICS <part-num-ref name="ICS">108</part-num-ref>
|
| 344 |
+
via the second interface <part-num-ref name="second interface">1062.</part-num-ref>
|
| 345 |
+
Specifically, if an ICS manager <part-num-ref name="ICS manager">114</part-num-ref>
|
| 346 |
+
wants to conduct inventory <confidence value="5">"</confidence>
|
| 347 |
+
spot checks<confidence value="5">"</confidence>
|
| 348 |
+
at various points in the supply chain or has a specific inquiry about a particular device <part-num-ref name="particular device">118,</part-num-ref>
|
| 349 |
+
the ICS manager <part-num-ref name="ICS manager">114</part-num-ref>
|
| 350 |
+
can access the ICS <part-num-ref name="ICS">108</part-num-ref>
|
| 351 |
+
and run a manager's security process that is similar to the end user's device authentication process. For example, the ICS manager <part-num-ref name="ICS manager">114</part-num-ref>
|
| 352 |
+
can access the database <part-num-ref name="database">104</part-num-ref>
|
| 353 |
+
via an access point such as a computer terminal in the ICS <part-num-ref name="ICS">108</part-num-ref>
|
| 354 |
+
or a hand held wireless device capable of interfacing with the ICS <part-num-ref name="ICS">108</part-num-ref>
|
| 355 |
+
and key in a query with the information specific to the device in question. The results of the query are displayed for the ICS manager <part-num-ref name="ICS manager">114</part-num-ref>
|
| 356 |
+
to review and confirm if the device in question is at a proper location in the supply chain. </p>
|
| 357 |
+
<p id="p-38" num="38">[0033<confidence value="5">]</confidence>
|
| 358 |
+
FIG. 2 depicts a series of method steps <part-num-ref name="series of method steps">200</part-num-ref>
|
| 359 |
+
for practicing the inventory control (security) and device authentication operation in accordance with the <page-break num="12"/>
|
| 360 |
+
<boundary-data type="header">V003 DS - Patent Application</boundary-data>
|
| 361 |
+
subject invention as introduced above. Specifically, the method <part-num-ref name="method">200</part-num-ref>
|
| 362 |
+
starts at step <part-num-ref name="starts at step">202</part-num-ref>
|
| 363 |
+
and proceeds to step <part-num-ref name="and proceeds to step">204</part-num-ref>
|
| 364 |
+
where device identity-containing inventory management information for use in an inventory control system is accepted from an inventory origination point to a first sales distribution point. The inventory origination point is, in one embodiment, a device manufacturer. The first sales distribution point is, in one embodiment, selected from the group consisting of a manufacturer<confidence value="8">'</confidence>
|
| 365 |
+
s distributor, a regional distributor and a retail location. In one embodiment of the invention, the device identity-containing information is selected from the group consisting of a device serial number and a MAC address that is accepted into a database for storage and reference at a later time. </p>
|
| 366 |
+
<p id="p-39" num="39">Preferably, the information is accepted after delivery of the inventory from the inventory origination point to the first sales distribution point. Most preferably, the information is accepted within <part-num-ref name="information is accepted within">24</part-num-ref>
|
| 367 |
+
hours after delivery of the inventory. </p>
|
| 368 |
+
<p id="p-40" num="40">[0034] After step 204, the method proceeds to step <part-num-ref name="method proceeds to step">206</part-num-ref>
|
| 369 |
+
where device identity- containing inventory management information is accepted in the ICS from each new successive sales distribution point as inventory moves through a supply chain. That is, in some occurrences (such as the first and third occurrences presented above), inventory will move from the origination point to a retail location in more than one step. For each such intermediate step, inventory information is accepted in the ICS at each occurrence of the intermediate sales distribution point as inventory moves through a supply chain. In one embodiment, the intermediate sales distribution point is selected from the group consisting of a regional distributor and a retailer. Similar to the conditions under which step <part-num-ref name="conditions under which step">204</part-num-ref>
|
| 370 |
+
is practiced, in one embodiment of the invention, the device identity-containing information is selected from the group consisting of a device serial number and a MAC address, that is accepted into a database for storage and reference at a later time. Preferably, the information is accepted after delivery of the inventory from the inventory origination point to the first sales distribution point. Most preferably, the information is accepted within <part-num-ref name="information is accepted within">24</part-num-ref>
|
| 371 |
+
hours after delivery of the inventory. </p>
|
| 372 |
+
<boundary-data type="header">V003 DS - Patent Application</boundary-data>
|
| 373 |
+
<p id="p-41" num="41">
|
| 374 |
+
<page-break num="13"/>
|
| 375 |
+
[0035<confidence value="5">]</confidence>
|
| 376 |
+
After step 206, the method proceeds to step <part-num-ref name="method proceeds to step">208</part-num-ref>
|
| 377 |
+
where device identity- containing inventory information of at least one of the members of the inventory (i.e., devices <part-num-ref name="devices">118)</part-num-ref>
|
| 378 |
+
are compared to the accepted inventory management information. During the comparison, the device identity-containing information including, but not limited to the information presented above of the at least one inventory member is attemptedly matched up against the inventory management information that had been accepted (by the ICS <part-num-ref name="ICS">108)</part-num-ref>
|
| 379 |
+
during previously forwarded inventory movements as described above<confidence value="5">.</confidence>
|
| 380 |
+
If the comparison reveals that the at least one inventory member has properly moved through the supply chain, then the inventory member is authenticated; if not, the inventory member is not authenticated. Examples of proper movement through the supply chain is selected from the group consisting of the inventory member moving completely from the manufacturer to a retail location and being registered by a end user and the inventory member moving partially through the supply chain from the manufacturer to an intermediate sales distribution point and being confirmed as by an inventory manager as being at a proper location in the supply chain. The method ends at step <part-num-ref name="method ends at step">210.</part-num-ref>
|
| 381 |
+
</p>
|
| 382 |
+
<p id="p-42" num="42">[0036<confidence value="5">]</confidence>
|
| 383 |
+
FIG. 3 depicts a schematic diagram of a controller <part-num-ref name="controller">300</part-num-ref>
|
| 384 |
+
that may be used to practice the present invention. The controller <part-num-ref name="controller">300</part-num-ref>
|
| 385 |
+
may be used to manage inventory and secure, register or otherwise authenticate inventory members or associated services as described above. The controller <part-num-ref name="controller">300</part-num-ref>
|
| 386 |
+
may be one of any form of a general purpose computer processor used in accessing an IP-based network such as the Internet. The controller <part-num-ref name="controller">300</part-num-ref>
|
| 387 |
+
comprises a central processing unit (CPU) <part-num-ref name="central processing unit (CPU)">302,</part-num-ref>
|
| 388 |
+
a memory <part-num-ref name="memory">304,</part-num-ref>
|
| 389 |
+
and support circuits <part-num-ref name="memory 304, and support circuits">306</part-num-ref>
|
| 390 |
+
for the CPU <part-num-ref name="CPU">302</part-num-ref>
|
| 391 |
+
and provisions 308/310 for connecting the control<confidence value="8">l</confidence>
|
| 392 |
+
er <part-num-ref name="controller">300</part-num-ref>
|
| 393 |
+
to other ICS components and an IP-based network as described above and input/output devices related to the controller <part-num-ref name="controller">300</part-num-ref>
|
| 394 |
+
respectively. The memory <part-num-ref name="memory">304</part-num-ref>
|
| 395 |
+
is coupled to the CPU <part-num-ref name="CPU">302.</part-num-ref>
|
| 396 |
+
The memory <part-num-ref name="memory">304,</part-num-ref>
|
| 397 |
+
or computer-readable medium, may be one or more of readily available memory such as random access memory (RAM), read <page-break num="14"/>
|
| 398 |
+
<boundary-data type="header">V003 DS - Patent Application</boundary-data>
|
| 399 |
+
only memory (ROM), floppy disk, hard disk, flash memory or any other form of digital storage, local or re<confidence value="8">m</confidence>
|
| 400 |
+
ote. The support circuits <part-num-ref name="support circuits">306</part-num-ref>
|
| 401 |
+
are coupled to the CPU <part-num-ref name="CPU">302</part-num-ref>
|
| 402 |
+
for supporting the processor in a conventional manner. These circuits include cache, power supplies, clock circuits, input/output circuitry and subsystems, and the like. A software routine <part-num-ref name="software routine">312,</part-num-ref>
|
| 403 |
+
when executed by the CPU <part-num-ref name="CPU">302,</part-num-ref>
|
| 404 |
+
causes the controller <part-num-ref name="controller">300</part-num-ref>
|
| 405 |
+
to perform processes of the present invention (such as but not limited to the method <part-num-ref name="method">200</part-num-ref>
|
| 406 |
+
described above) and is generally stored in the memory <part-num-ref name="memory">304.</part-num-ref>
|
| 407 |
+
The software routine <part-num-ref name="software routine">312</part-num-ref>
|
| 408 |
+
may also be stored and/or executed by a second CPU (not shown) that is remotely located from the hardware being controlled by the CPU <part-num-ref name="CPU">302.</part-num-ref>
|
| 409 |
+
For example, the control<confidence value="8">l</confidence>
|
| 410 |
+
er <part-num-ref name="controller">300</part-num-ref>
|
| 411 |
+
may be part of either or both servers <part-num-ref name="may be part of either or both servers">102</part-num-ref>
|
| 412 |
+
of FIG. <confidence value="5">1</confidence>
|
| 413 |
+
or other ICS <part-num-ref name="or other ICS">108</part-num-ref>
|
| 414 |
+
component and the software routine <part-num-ref name="software routine">312</part-num-ref>
|
| 415 |
+
may be stored in a memory of part or both servers <part-num-ref name="memory of part or both servers">102</part-num-ref>
|
| 416 |
+
of FIG. <confidence value="5">1</confidence>
|
| 417 |
+
or other ICS <part-num-ref name="or other ICS">108</part-num-ref>
|
| 418 |
+
component. </p>
|
| 419 |
+
<p id="p-43" num="43">[0037] The software routine <part-num-ref name="software routine">312</part-num-ref>
|
| 420 |
+
is executed after delivery of the inventory from a point discussed above and such point attempts to accesses the ICS <part-num-ref name="ICS">108.</part-num-ref>
|
| 421 |
+
The software routine <part-num-ref name="software routine">312,</part-num-ref>
|
| 422 |
+
when executed by the CPU <part-num-ref name="CPU">302,</part-num-ref>
|
| 423 |
+
transforms the general purpose computer into a specific purpose computer (controller) <part-num-ref name="specific purpose computer (controller)">300</part-num-ref>
|
| 424 |
+
that controls the automated inventory management process. As such, the process tracks and authenticates inventory as discussed above. Although the process of the present invention is discussed as being implemented as a software routine, some of the method steps that are disclosed therein may be performed in hardware as well as by the software controller. As such, the invention may be implemented in software as executed upon a computer system, in hardware as an application specific integrated circuit or other type of hardware implementation, or a combination of software and hardware. </p>
|
| 425 |
+
<p id="p-44" num="44">[0038] The software routine <part-num-ref name="software routine">312</part-num-ref>
|
| 426 |
+
of the present invention is capable of being executed on computer operating systems including but not limited to Microsoft Windows <part-num-ref name="present invention is capable of being executed on computer operating systems including but not limited to Microsoft Windows">98,</part-num-ref>
|
| 427 |
+
Microsoft Windows XP, Apple OS X and Linux. Similarly, the software routine <part-num-ref name="software routine">312</part-num-ref>
|
| 428 |
+
of the present invention is capable of being performed using <page-break num="15"/>
|
| 429 |
+
<boundary-data type="header">V003 DS - Patent Application</boundary-data>
|
| 430 |
+
CPU architectures including but not limited to Apple Power PC, Intel x86, Sun SPARC and Intel ARM. </p>
|
| 431 |
+
<p id="p-45" num="45">[0039] FIG. 4 depicts a series of method steps <part-num-ref name="series of method steps">400</part-num-ref>
|
| 432 |
+
for practicing a second embodiment of the inventory control (security) and device authentication operation in accordance with the subject invention. Specifically, the method <part-num-ref name="method">400</part-num-ref>
|
| 433 |
+
starts at step <part-num-ref name="starts at step">402</part-num-ref>
|
| 434 |
+
and proceeds to step <part-num-ref name="and proceeds to step">404</part-num-ref>
|
| 435 |
+
in which a secure, web-accessible inventory control system is provided. The inventory control system may be the ICS <part-num-ref name="ICS">108</part-num-ref>
|
| 436 |
+
as seen in FIG. <confidence value="5">1</confidence>
|
| 437 |
+
or any other such system capable of performing the described steps via interaction with a public access network such as, but not limited to, the Internet. </p>
|
| 438 |
+
<p id="p-46" num="46">[0040] At step 406, inventory control information is accepted from one or more qualified inventory control systems users via one or more web-based transactions. Particularly, inventory control information, such as, but not limited to the files containing the identifiers described above, is accepted by the inventory control system from at least one selected from the group consisting of an inventory origination point to one or more sales distribution points, between two such distribution points and between one such distribution point and a point of sale location such as a retailer. Preferably, the information is accepted via web-based authentication process such as a user ID/password protocol after delivery of the inventory. Most preferably, the information is accepted within <part-num-ref name="information is accepted within">24</part-num-ref>
|
| 439 |
+
hours after delivery of the inventory. </p>
|
| 440 |
+
<p id="p-47" num="47">[0041<confidence value="5">]</confidence>
|
| 441 |
+
After step 406, the method proceeds to step <part-num-ref name="method proceeds to step">408</part-num-ref>
|
| 442 |
+
where members of the inventory (represented by the inventory control information) are authenticated via a web-based query. Particularly, inventory control information of at least one of the members of the inventory (i.e., devices <part-num-ref name="devices">118)</part-num-ref>
|
| 443 |
+
is compared to the accepted inventory management information occurs as a result of one selected from the group consisting of a registration/authentication query initiated by a end user and an authentication/security confirmation query initiated by an inventory manager. </p>
|
| 444 |
+
<boundary-data type="header">V003 DS - Patent Application</boundary-data>
|
| 445 |
+
<p id="p-48" num="48">
|
| 446 |
+
<page-break num="16"/>
|
| 447 |
+
These queries pr<confidence value="8">e</confidence>
|
| 448 |
+
ferably occur over the Inte<confidence value="65">rn</confidence>
|
| 449 |
+
et or other type of network where end users and inventory managers can access the inventory control system. The method ends at step <part-num-ref name="method ends at step">410.</part-num-ref>
|
| 450 |
+
</p>
|
| 451 |
+
<p id="p-49" num="49">[0042<confidence value="5">]</confidence>
|
| 452 |
+
FIG. 5 depicts an error checking subroutine that is executed inside of each accepting step of the subject invention such as accepting steps <part-num-ref name="subject invention such as accepting steps">204,</part-num-ref>
|
| 453 |
+
<part-num-ref name="subject invention such as accepting steps 204,">206</part-num-ref>
|
| 454 |
+
and <part-num-ref name="and">406.</part-num-ref>
|
| 455 |
+
That is, it is important that the inventory control information that is passed to the ICS <part-num-ref name="ICS">108</part-num-ref>
|
| 456 |
+
be of a specific format and content such that the database <part-num-ref name="database">104</part-num-ref>
|
| 457 |
+
can accept the information and proper update inventory records. As such, a series of method steps <part-num-ref name="series of method steps">500</part-num-ref>
|
| 458 |
+
is provided for accomplishing this task. Specifically, the method starts at step <part-num-ref name="method starts at step">502</part-num-ref>
|
| 459 |
+
and proceeds to step <part-num-ref name="and proceeds to step">504</part-num-ref>
|
| 460 |
+
where inventory control information is received from one of the aforementioned inventory information locations 110/116. Preferably, the inventory control information is provided as a comma separated value file, but other formats are possible and considered within the scope of the invention. </p>
|
| 461 |
+
<p id="p-50" num="50">[0043] At step 506, a decision is made as to whether or not the information in the file contains errors. For example, should the formatting of the inventory control information or other similar error be found, the file cannot be accepted into the database for updating purposes. Accordingly, if the file is found to contain at least one error, the method proceeds to step <part-num-ref name="method proceeds to step">510</part-num-ref>
|
| 462 |
+
where an error message is sent to the entity attempting to send the file. In one embodiment of the invention, the error message is provided on a screen or other type of interface that the entity sending the file is using to access the ICS <part-num-ref name="ICS">108.</part-num-ref>
|
| 463 |
+
If the file is rejected in this manner and the error message sent, the entity will have a time window in which to correct the erroneous file and resend the inventory control information in order to comply with inventory management requirements. In one embodiment of the invention, the time window is no more than six <part-num-ref name="time window is no more than six">(6)</part-num-ref>
|
| 464 |
+
hours from the time of the original upload attempt. </p>
|
| 465 |
+
<boundary-data type="header">V003 DS - Patent Application</boundary-data>
|
| 466 |
+
<p id="p-51" num="51">
|
| 467 |
+
<page-break num="17"/>
|
| 468 |
+
[0044] If the fi<confidence value="44">lI</confidence>
|
| 469 |
+
does not contain any errors, the method proceeds to step <part-num-ref name="method proceeds to step">508</part-num-ref>
|
| 470 |
+
where the file is uploaded to the database <part-num-ref name="database">104.</part-num-ref>
|
| 471 |
+
Upon successful uploading of the file, a confirmation message indicating such condition is sent to the entity attempting to send the file. In one embodiment of the invention, the confirmation message is provided on a screen or other type of interface that the entity sending the file is using to access the ICS <part-num-ref name="ICS">108.</part-num-ref>
|
| 472 |
+
The method <part-num-ref name="method">500</part-num-ref>
|
| 473 |
+
ends at step <part-num-ref name="ends at step">512.</part-num-ref>
|
| 474 |
+
</p>
|
| 475 |
+
<p id="p-52" num="52">[0045] While foregoing is directed to embodiments of the present invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof, and the scope thereof.</p>
|
| 476 |
+
<p id="p-53" num="53">
|
| 477 |
+
<page-break num="18"/>
|
| 478 |
+
This Page is Inserted by IFW Indexing and Scanning Operations and is not part of the Official Record </p>
|
| 479 |
+
<heading id="h-3">BEST AVAILABLE IMAGES</heading>
|
| 480 |
+
<p id="p-54" num="54">Defective images within this document are accurate representations of the original documents submitted by the applicant.</p>
|
| 481 |
+
<p id="p-55" num="55">Defects in the images include but are not limited to the items checked:</p>
|
| 482 |
+
<heading id="h-4">
|
| 483 |
+
<confidence value="5">Q</confidence>
|
| 484 |
+
BLACK BORDERS </heading>
|
| 485 |
+
<heading id="h-5">
|
| 486 |
+
<confidence value="5">Q</confidence>
|
| 487 |
+
IMAGE CUT OFF AT TOP, BOTTOM OR SIDES </heading>
|
| 488 |
+
<heading id="h-6">
|
| 489 |
+
<confidence value="5">Q</confidence>
|
| 490 |
+
FADED TEXT OR DRAWING </heading>
|
| 491 |
+
<heading id="h-7">
|
| 492 |
+
<confidence value="2">Q</confidence>
|
| 493 |
+
BLURRED OR ILLEGIBLE TEXT OR DRAWING </heading>
|
| 494 |
+
<heading id="h-8">
|
| 495 |
+
<confidence value="5">Q</confidence>
|
| 496 |
+
SKEWED/SLANTED IMAGES </heading>
|
| 497 |
+
<heading id="h-9">
|
| 498 |
+
<confidence value="4">Q</confidence>
|
| 499 |
+
COLOR OR BLACK AND WHITE PHOTOGRAPHS </heading>
|
| 500 |
+
<heading id="h-10">
|
| 501 |
+
<confidence value="5">Q</confidence>
|
| 502 |
+
GRAY SCALE DOCUMENTS </heading>
|
| 503 |
+
<p id="p-56" num="56">
|
| 504 |
+
<confidence value="11">(2</confidence>
|
| 505 |
+
LINES OR MARKS ON ORIGINAL DOCUMENT </p>
|
| 506 |
+
<heading id="h-11">
|
| 507 |
+
<confidence value="4">Q</confidence>
|
| 508 |
+
REFERENCE(S) OR EXHIBIT(S) SUBMITTED ARE POOR QUALITY </heading>
|
| 509 |
+
<heading id="h-12">
|
| 510 |
+
<confidence value="5">Q</confidence>
|
| 511 |
+
OTHER: </heading>
|
| 512 |
+
<heading id="h-13">IMAGES ARE BEST AVAILABLE COPY.</heading>
|
| 513 |
+
<p id="p-57" num="57">As rescanning these documents will not correct the image problems checked, please do not report these problems to the IFW Image Problem Mailbox.</p>
|
| 514 |
+
</description>
|
| 515 |
+
</us-patent-application>
|
| 516 |
+
|
applicant/11614238.xml
ADDED
|
@@ -0,0 +1,2 @@
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?><uspat:SpecificationDocument xmlns:uscom="urn:us:gov:doc:uspto:common" xmlns:uspat="urn:us:gov:doc:uspto:patent" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:com="http://www.wipo.int/standards/XMLSchema/ST96/Common" xmlns:pat="http://www.wipo.int/standards/XMLSchema/ST96/Patent" uscom:vendorName="VASTEC" uscom:createDateTime="2019-03-27T10:59:14Z" com:st96Version="V2_1" com:ipoVersion="US_V7_1" xsi:schemaLocation="urn:us:gov:doc:uspto:patent Patent/V7_1/Schema/USPatent/Document/SpecificationDocument_V7_1.xsd" com:documentFileName="11614238.03-25-2019.JTR2MT49LXEAPX4.SPEC.XML" com:id="JTR2MT49LXEAPX4">
|
| 2 |
+
<uspat:DocumentMetadata com:id="ID0000001"><uscom:DocumentCode>SPEC</uscom:DocumentCode><uscom:ApplicationNumberText uscom:electronicText="11614238">11614238</uscom:ApplicationNumberText><com:PageTotalQuantity>1</com:PageTotalQuantity><uscom:ParagraphTotalQuantity>4</uscom:ParagraphTotalQuantity><uscom:OfficialDate>2019-03-25</uscom:OfficialDate></uspat:DocumentMetadata><?PageStart number='1'?><uscom:Heading com:id="h-1">AMENDMENTS TO THE SPECIFICAITON</uscom:Heading><uscom:P com:pNumber="1" com:id="p-1" uscom:indentationLevelNumber="L1">Please amend the specification as follows:</uscom:P><uscom:P com:pNumber="2" com:id="p-2">[0015<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> The present invention further includes using the computer-generated images to precisely custom-fit a tissue heart component such as a valve to the area in which the component is to be placed in the patient. If a valve is being replaced, the valve may be any type of heart valve, including but not limited to the aortic valve and the mitral valve, and repairs to the soft tissue around the valves. <com:U>An o</com:U><uscom:OCRConfidenceData uscom:ocrConfidenceCode="5"><com:U>p</com:U></uscom:OCRConfidenceData><com:U>en-heart surgical </com:U><uscom:OCRConfidenceData uscom:ocrConfidenceCode="5"><com:U>p</com:U></uscom:OCRConfidenceData><com:U>rocedure is a </com:U><uscom:OCRConfidenceData uscom:ocrConfidenceCode="5"><com:U>p</com:U></uscom:OCRConfidenceData><com:U>referred technique for removing heart com</com:U><uscom:OCRConfidenceData uscom:ocrConfidenceCode="5"><com:U>p</com:U></uscom:OCRConfidenceData><com:U>onents to be re</com:U><uscom:OCRConfidenceData uscom:ocrConfidenceCode="5"><com:U>p</com:U></uscom:OCRConfidenceData><com:U>laced and installing re</com:U><uscom:OCRConfidenceData uscom:ocrConfidenceCode="5"><com:U>p</com:U></uscom:OCRConfidenceData><com:U>lacement heart components.</com:U></uscom:P><uscom:P com:pNumber="3" com:id="p-3" uscom:indentationMeasureUnitCode="In" uscom:firstLineIndentationNumber="0.53">A clean copy of the amended paragraph of the specification is presented: [0015<uscom:OCRConfidenceData uscom:ocrConfidenceCode="5">]</uscom:OCRConfidenceData> The present invention further includes using the computer-generated images to precisely custom-fit a tissue heart component such as a valve to the area in which the component is to be placed in the patient. If a valve is being replaced, the valve may be any type of heart valve, including but not limited to the aortic valve and the mitral valve, and repairs to the soft tissue around the valves. An open-heart surgical procedure is a preferred technique for removing heart components to be replaced and installing replacement heart components.</uscom:P><uscom:P com:pNumber="4" com:id="p-4" uscom:indentationLevelNumber="L2">-2-</uscom:P></uspat:SpecificationDocument>
|
applicant/11618162.xml
ADDED
|
@@ -0,0 +1 @@
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?><pat:SpecificationDocument xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:pat="urn:us:gov:doc:uspto:patent" xmlns:ent="urn:us:gov:doc:uspto:enterprise" xmlns="urn:us:gov:doc:uspto:patent" xmlns:tbl="http://www.oasis-open.org/tables/exchange/1.0" xmlns:com="http://www.wipo.int/standards/XMLSchema/Common/1" xsi:schemaLocation="urn:us:gov:doc:uspto:patent XML_SCHEMAS/V1_3/SpecificationDocument_1_0.xsd" pat:instanceFileName="11618162.01-03-2014.HQ453JFXPXXIFW2.SPEC.XML" pat:id="HQ453JFXPXXIFW2"><pat:DocumentCode>SPEC</pat:DocumentCode><pat:DocumentHeaderDetails pat:id="ID-00001"><pat:ApplicationHeaderDetails><pat:ApplicationNumber>11618162</pat:ApplicationNumber></pat:ApplicationHeaderDetails><pat:PageTotalQuantity>2</pat:PageTotalQuantity><pat:ParagraphTotalQuantity>8</pat:ParagraphTotalQuantity></pat:DocumentHeaderDetails><pat:MailRoomDate>2014-01-03</pat:MailRoomDate><pat:DocumentCreateDateText>2014-08-08</pat:DocumentCreateDateText><pat:DocumentTitle>SPECIFICATION DOCUMENT</pat:DocumentTitle><pat:Specification><?PageStart number='1'?><pat:P pat:pNumber="1" pat:id="p-1"><pat:BoundaryData><pat:HeaderText>Application No.: 11/618,162</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>Filed: 12/29/2006</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>Attorney Docket No.: CAM920060142US1 (7321-166U)</pat:HeaderText></pat:BoundaryData></pat:P><pat:Heading pat:id="h-1">AMENDMENTS TO THE SPECIFICATION</pat:Heading><pat:P pat:pNumber="2" pat:id="p-2">Please amend paragraph [0021] of Applicants' originally filed specification: </pat:P><pat:P pat:pNumber="3" pat:id="p-3">[0021] Turning now to Figure 2, a pictorial illustration of a context browser configured for navigation of pivotally related information for a document is shown. </pat:P><pat:P pat:pNumber="4" pat:id="p-4">The <pat:PartName pat:idref='PN-00001'>context browser</pat:PartName> <pat:PartNumber pat:id='PN-00001'>200</pat:PartNumber> can provide an <pat:PartName pat:idref='PN-00002'>object view</pat:PartName> <pat:PartNumber pat:id='PN-00002'>210</pat:PartNumber> for a selected activity object in an activity. <pat:PartName pat:idref='PN-00003'>Those related activity objects</pat:PartName> <pat:PartNumber pat:id='PN-00003'>220</pat:PartNumber>,230,240,250,260 that are directly associated with the selected activity object in the <pat:PartName pat:idref='PN-00004'>object view</pat:PartName> <pat:PartNumber pat:id='PN-00004'>210</pat:PartNumber> can be listed separately in the <pat:PartName pat:idref='PN-00005'>context browser</pat:PartName> <pat:PartNumber pat:id='PN-00005'>200</pat:PartNumber> according to activity object type. Each of the <pat:PartName pat:idref='PN-00006'>related activity objects</pat:PartName> <pat:PartNumber pat:id='PN-00006'>220</pat:PartNumber>,230,240,250,260 further can be enabled for selection and activation. Responsive to the activation of any of the <pat:PartName pat:idref='PN-00007'>related activity objects</pat:PartName> <pat:PartNumber pat:id='PN-00007'>220</pat:PartNumber>,230,240,250,260, the activated one of the <pat:PartName pat:idref='PN-00008'>related activity objects</pat:PartName> <pat:PartNumber pat:id='PN-00008'>220</pat:PartNumber>,230,240,250,260 can be displayed in the <pat:PartName pat:idref='PN-00009'>object view</pat:PartName> <pat:PartNumber pat:id='PN-00009'>210</pat:PartNumber> and a <pat:PartName pat:idref='PN-00010'>new listing of related activity objects</pat:PartName> <pat:PartNumber pat:id='PN-00010'>220</pat:PartNumber>,230,240,250, 260 can be provided for <pat:OCRConfidenceData pat:levelNumber='5'>t</pat:OCRConfidenceData>he activated one of the <pat:PartName pat:idref='PN-00011'>related activity objects</pat:PartName> <pat:PartNumber pat:id='PN-00011'>220</pat:PartNumber>,230,240,250, 260. </pat:P><pat:P pat:pNumber="5" pat:id="p-5">Please amend paragraph [0032] of Applicants' originally filed specification: </pat:P><pat:P pat:pNumber="6" pat:id="p-6">[0032] For the purposes of this description, a computer-usable or computer readable storage medium can be any apparatus that can contain, store, communicate, p<pat:OCRConfidenceData pat:levelNumber='24'>re</pat:OCRConfidenceData> <pat:OCRConfidenceData pat:levelNumber='1'>t</pat:OCRConfidenceData> or transport the program for use by or in connection with <pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>3</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData><?PageStart number='2'?><pat:BoundaryData><pat:HeaderText>Application No.: 11/618,162</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>Filed: 12/29/2006</pat:HeaderText></pat:BoundaryData><pat:BoundaryData><pat:HeaderText>Attorney Docket No.: CAM920060142US1 (7321-166U)</pat:HeaderText></pat:BoundaryData>the instruction execution system, apparatus, or device. The storage medium can be an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system (or apparatus or device)<pat:OCRConfidenceData pat:levelNumber='26'>o.</pat:OCRConfidenceData> Examples of a computer-readable (usable stor<pat:OCRConfidenceData pat:levelNumber='6666'>age)</pat:OCRConfidenceData> medium include a semiconductor or solid state memory, magnetic tape, a removable computer diskette, a random access memory (RAM), a read-only memory (ROM), a rigid magnetic disk and an optical disk. </pat:P><pat:P pat:pNumber="7" pat:id="p-7">Current examples of optical disks include compact disk - read only memory (CD- ROM), compact disk - read/write (CD-R<pat:OCRConfidenceData pat:levelNumber='5'>/</pat:OCRConfidenceData>W) and DVD. With specific reference to a computer usable (readable) storage medium, it is to be understood that a storage medium excludes transitory media such as transitory signals and other propa<pat:OCRConfidenceData pat:levelNumber='68'>ga</pat:OCRConfidenceData>tion media. </pat:P><pat:P pat:pNumber="8" pat:id="p-8"><pat:BoundaryData><pat:HeaderText><pat:OCRConfidenceData pat:levelNumber='8'>4</pat:OCRConfidenceData></pat:HeaderText></pat:BoundaryData></pat:P></pat:Specification></pat:SpecificationDocument>
|
applicant/11624634.xml
ADDED
|
The diff for this file is too large to render.
See raw diff
|
|
|
applicant/11647425.xml
ADDED
|
@@ -0,0 +1,200 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>11647425</doc-number>
|
| 8 |
+
<date>2006-12-29</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<p id="p-1" num="1">Node Selection Function for Multipoint Radio Network Configurations Field of the Invention [0001] The present invention relates to an apparatus, a system and a method which are suitable for enhancing the resiliency in a communication network.</p>
|
| 14 |
+
<p id="p-2" num="2">Related Back<confidence value="8">g</confidence>
|
| 15 |
+
round Art [0002] The mobile switching center server (MSC server - MSS) architecture is an enhancement on top of traditional circuit switched networks where both switching of actual user plane traffic (i.e. speech, data and facsimile) as well as control plane traffic (i.e. call and non-call related signaling) has been split into separate physical (and logical) entities which are called as media gateway (MGW) and MSC Server<confidence value="8">.</confidence>
|
| 16 |
+
</p>
|
| 17 |
+
<p id="p-3" num="3">[0003] This split enables multiple different benefits for the network operator compared to a situation where traditional MSC network elements are used instead. For instance, the MSC server system makes it possible to use an <confidence value="8">i</confidence>
|
| 18 |
+
nternet protocol (IP), asynchronous transfer mode (ATM) or time divisional multiple access (TDM) transmission to transport signaling and user plane traffic the standardized way. This has not been possible in earlier occasions, even though there have been some vendor specific solutions. </p>
|
| 19 |
+
<p id="p-4" num="4">Another benefit is the more optimal use of core network resources. For instance, the MSC server capacity i.e. call control, charging and services capacity can be obtained and <page-break num="2"/>
|
| 20 |
+
<confidence value="2">\</confidence>
|
| 21 |
+
2/26 controlled separately from the switching capacity needed for connecting calls (e.g. speech connections). This makes it more easier for an operator to design the network topology and place MGW network elements into locations that are more optimal for actual switching process, whereas the call control can be centralized within the network into a smaller number of central office sites. </p>
|
| 22 |
+
<p id="p-5" num="5">
|
| 23 |
+
<confidence value="5">[</confidence>
|
| 24 |
+
0004<confidence value="5">]</confidence>
|
| 25 |
+
In addition to previously mentioned benefits, the use of MSC server system is expected to allow more freedom to design more advanced solutions for network resiliency. </p>
|
| 26 |
+
<p id="p-6" num="6">At present, this particular area has not been known yet to be studied in greater detail by the 3rd generation partnership project. However, when in principle traditional (non-split) MSC have been present in existing mobile networks, network resiliency has conventionally been done for signaling connections and in rare cases by dedicating some MSC into the network which is able to take traffic from a faulty network element, in case failure occurs at the network. This procedure is by no means simple to execute and has many possibilities to fail. Therefore, operators have not used it, but instead moved only individual radio network configurations (manually, not automatically) from faulty MSC to other MSC, if the failure is estimated to last long enough. Fact is that network operators are expecting to have better network element and even network level resiliency solutions from their equipment vendors, because the network element sizes are constantly increasing (handling even millions of subscribers within a single network element), and in case of a failure thus having a catastrophic magnitude, the <page-break num="3"/>
|
| 27 |
+
</p>
|
| 28 |
+
<heading id="h-1">
|
| 29 |
+
<confidence value="2">{</confidence>
|
| 30 |
+
</heading>
|
| 31 |
+
<p id="p-7" num="7">3/26 income losses together with a hit to the overall image of an operator's business can be very significant.</p>
|
| 32 |
+
<p id="p-8" num="8">[0005<confidence value="5">]</confidence>
|
| 33 |
+
In principle, this situation is the same in case of using a MSC server. However, because the MSC server system consists of multiple MSC servers that are responsible of actual call routing etc., as well as of media gateways (MGW) that are responsible of user plane switching, it is possible that MGW and/or MSC server or connections between them can be lost, resulting in a lack of communication capabilities for a certain part of overall traffic. In both specifications 3GPP TS 29.232 and TS 29.332 of MGW, individual physical MGW can be split into multiple virtual MGW each having its own share of responsibility for switching the total traffic of physical MGW. Virtual MGW are controlled by individual MSC server entities. A single physical MSC server can control multiple virtual MGW (even from the same physical MGW). Each virtual MGW is nominated to be responsible of individual TDM circuits (pulse code modulated (PCM) timeslots), but ATM and IP resources are freely usable for all virtual MGW located within the same physical MGW. Because of this restriction, for instance in case the connection between a specific virtual MGW and the MSC server that controls it is down, those TDM resources (PCM timeslots) that have been designated to that particular virtual MGW are out-of-use until the situation is restored back into normal or the resource ownership of those resources is moved into another (working) virtual MGW - MSC server pair. Therefore, also within the MSC server system (if overall network level resiliency enhancements are considered) manual re-homing of both radio network resources (in case of MSC server <page-break num="4"/>
|
| 34 |
+
4/26 failure) and TDM-resources is typically the only possible solution to provide network level resiliency in case for some reason the MSC server or virtual MGW responsible of those resources cannot be used. </p>
|
| 35 |
+
<p id="p-9" num="9">
|
| 36 |
+
<confidence value="5">[</confidence>
|
| 37 |
+
0006] GSM (global system for mobile communication) /GPRS (general packet radio service)/EDGE (enhanced data rates for GSM evolution) and UMTS (universal mobile telecommunications service) radio access network configurations are typically in today's networks dedicated for single MSC or MSC server. The MSC server knows the radio network assigned to it, but in addition to this it also has information about the neighbor radio network configuration of other neighbor MSC or MSC server network elements. Due this fact that no single radio network controller (RNC) or base station controller (BSC) is controlled by more than one circuit switched core network and packet switched core network element (MSC/MSC server and SGSN), it will cause situations where the loss of a core network element or connection towards core network from RNC/BSC seizes the communication from that radio network controlled by a particular RNC/BSC. </p>
|
| 38 |
+
<p id="p-10" num="10">Summary of the Invention [0007] Therefore, it is an object of the present invention to overcome respective shortcomings of the prior art. Specifically, the present invention aims at enhancing the resiliency of a communication network.</p>
|
| 39 |
+
<p id="p-11" num="11">
|
| 40 |
+
<page-break num="5"/>
|
| 41 |
+
5/26 [0008<confidence value="5">]</confidence>
|
| 42 |
+
According to a first aspect of the present invention, there is provided an apparatus configured to be operably connected to an access network controller device; </p>
|
| 43 |
+
<p id="p-12" num="12">and to be operably connected to a pool of network elements which all comprise the same radio network configuration;</p>
|
| 44 |
+
<p id="p-13" num="13">the apparatus further comprising a selection functionality configured to select and connect one or more of the network elements with the access network controller device.</p>
|
| 45 |
+
<p id="p-14" num="14">[0009] Modifications of the first aspect of the present invention may be as follows.</p>
|
| 46 |
+
<p id="p-15" num="15">[0010] The selection functionality can be a non-access stratum node selection functionality.</p>
|
| 47 |
+
<p id="p-16" num="16">[0011] The apparatus according to the first aspect can be further configured to be operably connected to a radio network controller and a base station controller.</p>
|
| 48 |
+
<p id="p-17" num="17">[0012] The network elements can be selected from a group comprising serving GPRS support nodes and mobile switching center server.</p>
|
| 49 |
+
<p id="p-18" num="18">[0013] The apparatus according to the first aspect can be further configured to be operably connected to a pool of network elements over a multipoint interface.</p>
|
| 50 |
+
<p id="p-19" num="19">[0014] The apparatus according to the first aspect can be further configured to process protocol parameter out of the group comprising temporary mobile station identity, <page-break num="6"/>
|
| 51 |
+
6/26 international mobile subscriber identity, and intra domain non-access stratum node selector at level <part-num-ref name="group comprising temporary mobile station identity, 6/26 international mobile subscriber identity, and intra domain non-access stratum node selector at level">3</part-num-ref>
|
| 52 |
+
signaling. </p>
|
| 53 |
+
<p id="p-20" num="20">[0015<confidence value="5">]</confidence>
|
| 54 |
+
The apparatus according to the first aspect can be further configured to support one or more of the group comprising radio access network application part, base station system application part, and base station system GPRS protocol. </p>
|
| 55 |
+
<p id="p-21" num="21">[0016] According to a second aspect of the present invention, there is provided a system comprising an access network controller device; a pool of network elements which all comprise the same radio network configuration; and a gateway, configured to be operably connected to the access network controller device, as well as to the pool of <confidence value="6">-</confidence>
|
| 56 |
+
network elements, wherein the gateway further comprises a selection functionality configured to select and connect one or more of the network elements with the access network controller device. </p>
|
| 57 |
+
<p id="p-22" num="22">[0017] Modifications of the second aspect of the present invention can be as follows.</p>
|
| 58 |
+
<p id="p-23" num="23">[0018] The selection functionality can be a non-access stratum node selection functionality.</p>
|
| 59 |
+
<p id="p-24" num="24">[0019] The gateway can be further configured to be operably connected to a radio network controller and a base station controller.</p>
|
| 60 |
+
<p id="p-25" num="25">
|
| 61 |
+
<page-break num="7"/>
|
| 62 |
+
7/26 [0020<confidence value="5">]</confidence>
|
| 63 |
+
The network elements can be selected from a group comprising serving GPRS support nodes and mobile switching center server. </p>
|
| 64 |
+
<p id="p-26" num="26">[0021<confidence value="5">]</confidence>
|
| 65 |
+
The gateway can be further configured to be operably connected to a pool of network elements over a multipoint interface. </p>
|
| 66 |
+
<p id="p-27" num="27">
|
| 67 |
+
<confidence value="26">--</confidence>
|
| 68 |
+
[0022] The gateway can be further configured to process protocol parameter out of the group comprising temporary mobile station identity, international mobile subscriber identity, and intra domain non-access stratum node selector at level <part-num-ref name="group comprising temporary mobile station identity, international mobile subscriber identity, and intra domain non-access stratum node selector at level">3</part-num-ref>
|
| 69 |
+
signaling. </p>
|
| 70 |
+
<p id="p-28" num="28">[0023] The gateway can be further configured to support one or more of the group comprising radio access network application part, base station system application part, and base station system GPRS protocol.</p>
|
| 71 |
+
<p id="p-29" num="29">[0024] The system according to the second aspect can comprise at least two gateways, each of which is configured to be operably connected to the access network controller device, as well as to the pool of network elements, and each of which comprises a selection functionality configured to select and connect one or more of the network elements with the access network controller device.</p>
|
| 72 |
+
<p id="p-30" num="30">[0025] According to a third aspect of the present invention, there is provided a method comprising selecting <page-break num="8"/>
|
| 73 |
+
<part-num-ref name="method comprising selecting">
|
| 74 |
+
<confidence value="1">6</confidence>
|
| 75 |
+
</part-num-ref>
|
| 76 |
+
8/26 one or more network elements out of a pool of network elements which all comprise the same radio network configuration; and connecting the selected one or more network elements with an access network controller device via a gateway. </p>
|
| 77 |
+
<p id="p-31" num="31">[0026] Modifications of the third aspect of the present invention can be as follows.</p>
|
| 78 |
+
<p id="p-32" num="32">[0027] The selecting of one or more network elements can involve a non-access stratum node selection functionality.</p>
|
| 79 |
+
<p id="p-33" num="33">[0028] The access network controller device can be one of a radio network controller and a base station controller.</p>
|
| 80 |
+
<p id="p-34" num="34">[0029] The selecting of network elements can include selecting core network elements from a group comprising serving GPRS support nodes and mobile switching center server.</p>
|
| 81 |
+
<p id="p-35" num="35">[0030] The connecting of the selected one or more network elements can include connecting to a pool of core network elements over a multipoint interface.</p>
|
| 82 |
+
<p id="p-36" num="36">[0031] The method according to the third aspect can further comprise processing, by the gateway, protocol parameter out of the group comprising temporary mobile station identity, international mobile subscriber identity, <page-break num="9"/>
|
| 83 |
+
9/26 and intra domain non-access stratum node selector at level <part-num-ref name="group comprising temporary mobile station identity, international mobile subscriber identity, 9/26 and intra domain non-access stratum node selector at level">3</part-num-ref>
|
| 84 |
+
signaling. </p>
|
| 85 |
+
<p id="p-37" num="37">[0032] The method according to the third aspect can further comprise supporting, by the gateway, one or more of the group comprising radio access network application part, base station system application part, and base station system GPRS protocol.</p>
|
| 86 |
+
<p id="p-38" num="38">[0033<confidence value="5">]</confidence>
|
| 87 |
+
The method according to the third aspect can further comprise providing at least two gateways, each of which is configured to be operably connected to the access network controller device, as well as to the pool of network elements, and each of which comprises a selection functionality configured to select and connect one or more <confidence value="26">--</confidence>
|
| 88 |
+
of the network elements with the access network controller device. </p>
|
| 89 |
+
<p id="p-39" num="39">[0034] According to a fourth aspect of the present invention, there is provided an apparatus, comprising means for operably connecting to an access network controller device; means for operably connecting to a pool of network elements which all comprise the same radio network configuration; and means for selecting and connecting one or more of the network elements with the access network controller device.</p>
|
| 90 |
+
<p id="p-40" num="40">
|
| 91 |
+
<confidence value="5">[</confidence>
|
| 92 |
+
0035] According to a fifth aspect of the present invention, there is provided a system comprising means for providing access network control; a plurality of means for providing network services which all comprise the same <page-break num="10"/>
|
| 93 |
+
10/26 radio network configuration; and gateway means for connecting to the means for providing access network control, as well as to the plurality of means for providing core network services, wherein the gateway means comprise means for selecting and connecting one or more of means for providing network services with means for providing access network control. </p>
|
| 94 |
+
<p id="p-41" num="41">[0036] According to a sixth aspect of the present invention, there is provided a computer program product embodied on a computer-readable medium, the computer program product configured to provide a method comprising selecting one or more network elements out of a pool of network elements which all comprise the same radio network configuration; and connecting the selected one or more network elements with an access network controller device via the media gateway.</p>
|
| 95 |
+
<p id="p-42" num="42">Brief Description of the Drawin<confidence value="68">gs</confidence>
|
| 96 |
+
[0037] The above and further aspects, features, and advantages of the present invention will become readily apparent from the following description of its preferred embodiments which is to be taken in conjunction with the appended drawings, in which: </p>
|
| 97 |
+
<p id="p-43" num="43">[0038] Fig. 1 shows multipoint A/Gb and Iu interface features as defined by the 3GPP;</p>
|
| 98 |
+
<p id="p-44" num="44">
|
| 99 |
+
<confidence value="5">[</confidence>
|
| 100 |
+
0039] Fig. 2 shows enhancements according to an embodiment of the present invention with respect to the <page-break num="11"/>
|
| 101 |
+
11/26 previous architecture which provide MSC server level resiliency; and [0040] Fig. 3 shows an additional enhancement according to another embodiment of the present invention in order to achieve MGW-level resiliency. </p>
|
| 102 |
+
<p id="p-45" num="45">Detailed Description of the preferred Embodiments <confidence value="6">-</confidence>
|
| 103 |
+
[0041] The preferred embodiments described in the following serve to illustrate the applicability and enablement of the present invention, but it is to be expressly understood that these embodiments are meant to serve as illustrative examples only, and that they are by no means to be construed as limiting the present invention to the described particularities. </p>
|
| 104 |
+
<p id="p-46" num="46">[0042] The technical specification 23.236 of the 3GPP ("Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes") introduces a so-called multipoint A or multipoint <confidence value="5">I</confidence>
|
| 105 |
+
u-interface, which enables a RNC or BSC to be connected to multiple core network elements (both MSC/MSC server as well as SGSN)<confidence value="5">.</confidence>
|
| 106 |
+
</p>
|
| 107 |
+
<p id="p-47" num="47">Accordingly, the resiliency of the network is enhanced in case a fatal failure situation occurs towards specific core network elements. The main principle of these features is that RNC/BSC is configured to communicate towards a pool of network elements (with individual pools for both circuit switched (CS) and packet switched (PS) traffic), where core network elements within the same pool are configured with <page-break num="12"/>
|
| 108 |
+
12/26 the same radio network configuration i.e. are able to handle traffic from that particular RNC/BSC. </p>
|
| 109 |
+
<p id="p-48" num="48">[0043] Both RNC and BSC that support multipoint A or multipoint Iu interface features have to have a so-called non access stratum (NAS) node selection function (NSF)<confidence value="5">.</confidence>
|
| 110 |
+
</p>
|
| 111 |
+
<p id="p-49" num="49">This function is the key to select the proper core network element to be used to provide services for a particular terminal, and it is executed when this terminal contacts the RNC/BSC the first time without already providing any information about a possibly selected core network element.</p>
|
| 112 |
+
<p id="p-50" num="50">When the RNC/BSC notices that the terminal has not yet been nominated to any specific core network element within a respective pool, then it will nominate the network element based on some non-standardized algorithm (e.g. round-robin or even something more sophisticated that takes into account the load of individual elements within a pool) and forwards the messages from the terminal to the selected core network element. The core network element then will check whether or not the terminal/subscriber is entitled to use services from the core network, and allocate a temporary mobile station identity (TMSI) to the terminal including a so-called network resource identifier (NRI) value embedded within the TMSI value. The TMSI is received by the terminal from the network and stored normally for further use. It needs to be highlighted that the terminal does not have to understand about the NRI value embedded within the stored TMSI. It only needs to use that TMSI for further communication towards the network.</p>
|
| 113 |
+
<p id="p-51" num="51">[0044] The NRI value, which is embedded into the TMSI, is received later by the RNC/BSC and analyzed in order to <page-break num="13"/>
|
| 114 |
+
<confidence value="1">.</confidence>
|
| 115 |
+
<confidence value="11">.3</confidence>
|
| 116 |
+
13/26 find out which core network element is dedicated for the C<confidence value="5">S</confidence>
|
| 117 |
+
and for the PS traffic (both CS and PS may have individual, i.e. different, <confidence value="4">N</confidence>
|
| 118 |
+
RI values and therefore need to be handled separately). The RNC/BSC forwards the message to the corresponding core network element and thus the logical communication path between terminal and the core network is maintained as long as the terminal stays within the area of a same pool. It should also be remarked that during a time period when the terminal stays within a same pool area, the same CS and PS core network elements remain to be responsible of the terminal. This means that e.g. no inter- MSC/MSC Server handovers are executed. This also reduces the overall signaling traffic and the handover processing needed for handovers compared to the traditional configuration where movement from the area of one core network element to another caused an immediate handover. </p>
|
| 119 |
+
<p id="p-52" num="52">[0045] In case the terminal moves to the area controlled by another pool of core network elements, then the NRI allocation process is re-executed again between the terminal and the core network. Similarly, when the RNC/BSC notices that a RANAP (radio access network application part) or BSSAP (base station system application part) connection towards a specific core network element for some reason within a pool has been lost, it is possible for the RNC/BSC to forward signaling traffic from the terminal towards another core network element within the same pool.</p>
|
| 120 |
+
<p id="p-53" num="53">This way it is possible to increase the overall network level resiliency with the introduction of the multipoint interface features.</p>
|
| 121 |
+
<p id="p-54" num="54">
|
| 122 |
+
<page-break num="14"/>
|
| 123 |
+
<confidence value="21">"i</confidence>
|
| 124 |
+
14/26 <confidence value="2">[</confidence>
|
| 125 |
+
0046<confidence value="5">]</confidence>
|
| 126 |
+
However, when the multipoint A or Iu interface features are taken into use, the configuration of the radio network becomes a very critical issue. Thus, for the location area, the cell identifier, the RNC/BSC, the service area, the base station etc., the radio network configuration at core network side has to be same in all network elements belonging to a same pool. In addition to this, each core network element has to have its own unique NRI configuration. One network element can have one or more NRI values, which are then embedded within allocated TMSI. </p>
|
| 127 |
+
<p id="p-55" num="55">
|
| 128 |
+
<confidence value="6">-</confidence>
|
| 129 |
+
The number of NRI values owned by a single core network element can be used to fine-tune how terminals are divided within a pool (a network element having more NRI values may be selected more often to handle terminals than a network element having less NRI values). Each core network element also needs to be aware of NRI values of other network <confidence value="6">-</confidence>
|
| 130 |
+
elements within the same pool in order to forward signaling messages to a correct network element, if so needed. </p>
|
| 131 |
+
<p id="p-56" num="56">[0047] The RNC/BSC also needs to be able to determine which core network element (CS and PS) corresponds to which NRI value. These values are statically pre-configured into RNC/BSC network elements and used by the RNC/BSC to route signaling messages to a correct network element from the terminal. In case the RNC/BSC receives a value that it does not recognize (i.e. a NRI belonging to some other pool), then the RNC/BSC need to act as if no NRI value has been received, and consequently, to use the NAS node selection function to select a new core network element from the pool that it can communicate with. The RNC/BSC is assumed not to maintain any subscriber/terminal specific information due to the multipoint A or Iu interface features, and all <page-break num="15"/>
|
| 132 |
+
15/26 signaling transactions between the terminal and the core network can be executed with simple lookups into a NRI/core network element correspondence database. </p>
|
| 133 |
+
<p id="p-57" num="57">[0048] However, the above described multipoint interface features are still problematical because those require support from radio network controllers (RNC/BSC), core network elements (MSC or MSC Servers and SGSN) as well as network management systems (N<confidence value="5">M</confidence>
|
| 134 |
+
S) in order to configure a whole feature into use with a reasonable amount of time and risk. </p>
|
| 135 |
+
<p id="p-58" num="58">
|
| 136 |
+
<confidence value="5">[</confidence>
|
| 137 |
+
0049] For instance, core network elements may already support multipoint features, but a feature support might be missing from the radio network and NMS parts. </p>
|
| 138 |
+
<p id="p-59" num="59">
|
| 139 |
+
<confidence value="5">[</confidence>
|
| 140 |
+
0050] An embodiment of the present invention is to offer an alternative way to overcome the problem related to lack of support at the radio network side which may be considered as being relatively harmful, because such lack of support will completely prevent use of the above described multipoint interface features. </p>
|
| 141 |
+
<p id="p-60" num="60">[0051] According to this embodiment, the NAS node selection function and the intelligence related to the routing of signaling messages towards a correct core network element based on a NRI value used by the RNC/BSC network elements (i.e. radio network) may be implemented into a media gateway (MGW) network element as introduced with the MSC server system.</p>
|
| 142 |
+
<p id="p-61" num="61">
|
| 143 |
+
<page-break num="16"/>
|
| 144 |
+
16/26 [0052] For comparison purposes, Fig. 1 shows the above described situation where the NAS node selection function (NAS-NSF) is located in the RNC or BSC and the RNC/BSC has connections to multiple C<confidence value="5">S</confidence>
|
| 145 |
+
(<confidence value="22222">MSS_1</confidence>
|
| 146 |
+
, MSS<confidence value="5">_</confidence>
|
| 147 |
+
2) and PS (<confidence value="2222228">SGSN_1,</confidence>
|
| 148 |
+
<confidence value="222222">SGSN_2</confidence>
|
| 149 |
+
) network elements that are pooled (within a so-called pool area)<confidence value="5">.</confidence>
|
| 150 |
+
</p>
|
| 151 |
+
<p id="p-62" num="62">[0053] Fig. 2 shows the situation according to the present embodiment. The present embodiment includes that there is a MSC server system or 2G/3G packet switched core network having support for an appropriate multipoint interface feature (A or <confidence value="5">I</confidence>
|
| 152 |
+
u) . However, no support is needed for this feature from RNC or BSC, which is an important benefit of the present embodiment. </p>
|
| 153 |
+
<p id="p-63" num="63">[0054] Thus, the effect of the network having enhanced resiliency against MSC server-level outages (or an outage of connection between the MSC server and the MGW) is achieved according to the present embodiment<confidence value="8">.</confidence>
|
| 154 |
+
</p>
|
| 155 |
+
<p id="p-64" num="64">[0055] Moreover, a further embodiment of the present invention considers having resiliency against MGW-level outages. This may be achieved by defining multiple MGW with same NAS-NSF capability and same signaling point code as well as showing global network identifier towards RNC/BSC.</p>
|
| 156 |
+
<p id="p-65" num="65">[0056] An implementation example would be to enhance the signaling point management cluster (SPMC) such as is defined by the IETF in document RFC3332 to support multiple signaling gateway entities within a single SPMC cluster.</p>
|
| 157 |
+
<p id="p-66" num="66">
|
| 158 |
+
<page-break num="17"/>
|
| 159 |
+
17/26 [0057] This further embodiment is depicted in Fig. 3 by means of an example including two MGW, MGW_1 and MGW_2. </p>
|
| 160 |
+
<p id="p-67" num="67">Accordingly, network resiliency architecture is provided at the MGW level<confidence value="8">.</confidence>
|
| 161 |
+
</p>
|
| 162 |
+
<p id="p-68" num="68">[0058] In the following, the description is limited to the above described embodiment shown in Fig. 2 which provides a MSC server-level resiliency, whereas no detailed description is further provided about the MGW-level resiliency shown in Fig. 3. However, it is apparent that a similar description applies to the case shown in Fig. 3.</p>
|
| 163 |
+
<p id="p-69" num="69">[0059<confidence value="5">]</confidence>
|
| 164 |
+
It is to be noted that due to the fact that neither RNC nor BSC need to have a functionality implemented about the pool concept or NRI, the MGW having the built-in NAS-NSF has to be able to act as a router for both RANAP and BSSAP level protocol messages between the correct core network element and the RNC/BSC. </p>
|
| 165 |
+
<p id="p-70" num="70">[0060] It is an option that a pool is configured for a MGW with more than two core network elements (MSC server or SGSN)<confidence value="6">.</confidence>
|
| 166 |
+
However, some maximum limitation of pool size can be implemented. Typically, such value can be e.g. that a single pool has a maximum of ten different network elements for circuit switched and ten for packet switched networks. </p>
|
| 167 |
+
<p id="p-71" num="71">An advantage would be to provide the needed capacity requirements for the internal database structure of the MGW which is required for storing the relationship between the NRI and the core network element.</p>
|
| 168 |
+
<p id="p-72" num="72">
|
| 169 |
+
<page-break num="18"/>
|
| 170 |
+
<confidence value="22">f'</confidence>
|
| 171 |
+
<confidence value="8">I</confidence>
|
| 172 |
+
18/2<confidence value="8">6</confidence>
|
| 173 |
+
[0061] In the MSC server system, the MGW is the network element that has the physical connectivity from RNC/BSC and also acts as signaling gateway for signaling traffic between the radio network and the circuit switched core network. In some cases, the MGW can be also used to act as transmission multiplexer for <confidence value="5">I</confidence>
|
| 174 |
+
u-PS and Gb traffic (if over frame relay) as well. Accordingly, the need for separate transmission cabling from RNC/BSC towards both MGW and SGSN can be reduced. Moreover, the MGW also can be responsible of switching actual user plane connections between the radio access network and the core network. Further, in case the speech codecs which are used at the radio network side and at the core network side are different, the MGW also can be responsible of speech transcoding between speech codecs. The MGW performs the control on the basis of H.248 commands received from the MSC server. In case a specific MSC server becomes unavailable for traffic, then the MGW notices the situation from events caused by an H.248 protocol entity within MGW, before anything unusual is noticed by RANAP or BSSAP entities and the NAS-NSF of the MGW. In this case, one option is that the NAS-NSF located at the MGW does not try to reselect another core network element, but instead waits for loss of connectivity-events that occur at RANAP or BSSAP level towards the core network element<confidence value="8">.</confidence>
|
| 175 |
+
</p>
|
| 176 |
+
<p id="p-73" num="73">[0062] According to an implementation example, the MGW is enhanced with a specific understanding about the required protocol parameters (TMSI, IMSI (international mobile subscriber identity) and IDNSS (intra domain NAS node selector) at level <part-num-ref name="required protocol parameters (TMSI, IMSI (international mobile subscriber identity) and IDNSS (intra domain NAS node selector) at level">3</part-num-ref>
|
| 177 |
+
(L3) signaling) in order to <page-break num="19"/>
|
| 178 |
+
<confidence value="1">.</confidence>
|
| 179 |
+
<confidence value="8">J</confidence>
|
| 180 |
+
<confidence value="1">i</confidence>
|
| 181 |
+
19/2<confidence value="8">6</confidence>
|
| 182 |
+
behave correctly, i.e. to be able to route the signaling messages to the correct network elements (i.e. to use NRI), and to allocate the proper core network element, if no specific core network element has been yet nominated for that terminal from the given pool. Therefore, the MGW investigates RANAP or BSSAP level information and thus supports required parts of RANAP and BSSAP protocols which are implemented into the MGW. </p>
|
| 183 |
+
<p id="p-74" num="74">[0063] In order to support packet switched multipoint interface features in addition, also BSSGP (bas station system GPRS protocol) and RANAP according to the Iu PS interface are supported within the MGW.</p>
|
| 184 |
+
<p id="p-75" num="75">[0064] Furthermore, the MGW can also be enabled to <confidence value="26">--</confidence>
|
| 185 |
+
separate both PS and CS level signaling and to have knowledge of the relationship between a NRI and a particular PS or CS network element as pre-configured by the network operator, i.e. to have individual pools for both CS and PS network sides. </p>
|
| 186 |
+
<p id="p-76" num="76">[0065] It is to be noted, however, that it is a possible implementation option that only CS side traffic is handled as multipoint traffic and the PS side traffic is handled normally such as between RNC/BSC and only a single SGSN.</p>
|
| 187 |
+
<p id="p-77" num="77">[0066] Still another implementation example is to introduce M3UA (message transfer part 3 user adaptation) /SIGTRAN procedures into the integrated signaling gateway functionality of the MGW to cope automatic changes within the M3UA network topology (i.e.</p>
|
| 188 |
+
<p id="p-78" num="78">
|
| 189 |
+
<page-break num="20"/>
|
| 190 |
+
20/26 events such as loss of connection towards individual application server processes (ASP) etc.)<confidence value="5">.</confidence>
|
| 191 |
+
</p>
|
| 192 |
+
<p id="p-79" num="79">[0067<confidence value="5">]</confidence>
|
| 193 |
+
According to the above described embodiments, the MSC server system can be enhanced in order to make multipoint Iu or A interface features available, regardless of an availability of these features at the radio network side. It is another advantage of the above described embodiments that the MSC server level improvement can be implemented independently of a later support of MGW-level resiliency. </p>
|
| 194 |
+
<p id="p-80" num="80">[0068<confidence value="5">]</confidence>
|
| 195 |
+
Thus, according to embodiments of the present invention, an apparatus is configured to be operably connected to an access network controller device as well as <confidence value="26">--</confidence>
|
| 196 |
+
to a pool of network elements which all comprise the same radio network configuration. The apparatus further comprises a selection functionality configured to select and connect one or more of the network elements with the access network controller device. </p>
|
| 197 |
+
<p id="p-81" num="81">[0069] What has been described above is what is presently considered to be preferred embodiments of the present invention. However, as is apparent to the skilled reader, these are provided for illustrative purposes only and are in no way intended to that the present invention is restricted thereto. Rather, it is the intention that all variations and modifications be included which fall within the spirit and scope of the appended claims.</p>
|
| 198 |
+
</description>
|
| 199 |
+
</us-patent-application>
|
| 200 |
+
|
applicant/11672562.xml
ADDED
|
@@ -0,0 +1,74 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>11672562</doc-number>
|
| 8 |
+
<date>2011-01-04</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<boundary-data type="header">Applicant <confidence value="6">:</confidence>
|
| 14 |
+
Doron Harle<confidence value="5">v</confidence>
|
| 15 |
+
et a<confidence value="4">l</confidence>
|
| 16 |
+
. Attorney's Docket No.: 20240-0006001 / RM-INVD-2 </boundary-data>
|
| 17 |
+
<boundary-data type="header">Serial No. <confidence value="6">:</confidence>
|
| 18 |
+
11/672,562 </boundary-data>
|
| 19 |
+
<boundary-data type="header">Filed <confidence value="6">:</confidence>
|
| 20 |
+
February 8, 2007 </boundary-data>
|
| 21 |
+
<boundary-data type="header">Page <confidence value="6">:</confidence>
|
| 22 |
+
<confidence value="8">2</confidence>
|
| 23 |
+
<confidence value="88">of</confidence>
|
| 24 |
+
<confidence value="88">19</confidence>
|
| 25 |
+
</boundary-data>
|
| 26 |
+
<p id="p-1" num="1">Amendments to the Specification:</p>
|
| 27 |
+
<p id="p-2" num="2">Please replace the paragraph beginning at page <part-num-ref name="paragraph beginning at page">11,</part-num-ref>
|
| 28 |
+
line <part-num-ref name="paragraph beginning at page 11, line">21</part-num-ref>
|
| 29 |
+
to page <part-num-ref name="to page">12,</part-num-ref>
|
| 30 |
+
line <part-num-ref name="to page 12, line">5</part-num-ref>
|
| 31 |
+
as with the following amended paragraph: </p>
|
| 32 |
+
<p id="p-3" num="3">Embodiments disclosed herein include a method and system for determining the position of a catheter in a patient's heart cavity. For example, the catheter may be configured with multiple electrodes and used for cardiac mapping, such as described in commonly owned patent application serial no. 11/451,898 now U.S. Pat. No. 7,515,954, entitled "NON-CONTACT </p>
|
| 33 |
+
<heading id="h-1">CARDIAC MAPP<confidence value="8">I</confidence>
|
| 34 |
+
NG, INCLUDING MOVING CATHETER AN<confidence value="5">D</confidence>
|
| 35 |
+
MULTI-BEAT </heading>
|
| 36 |
+
<p id="p-4" num="4">INTEGRATION" and filed June 13, 2006, application serial no. 11/451,908 now U.S. Pat. No.</p>
|
| 37 |
+
<p id="p-5" num="5">
|
| 38 |
+
<confidence value="6686866">7,505,8</confidence>
|
| 39 |
+
10, entitled "NON-CONTACT CARDIAC MAPPING, INCLUDING PREPROCESSING" and filed June 13, 2006, and application serial no. 11/451,871 now U.S. </p>
|
| 40 |
+
<p id="p-6" num="6">Pat. No. 7,729<confidence value="5">,</confidence>
|
| 41 |
+
752 entitled "NON-CONTACT CARDIAC MAPPING, INCLUDING RESOLUTION MAP" and filed June 13, 2006, the contents of which are incorporated herein by reference. Generally, cardiac mapping involves determining information about the electrical activity of a patients heart (e.g., at different locations of the endocardium surface) based on electrical signals measured by the multiple electrodes of the catheter. To perform such cardiac mapping, the position of the catheter (or more generally the positions of the catheter electrodes) within the heart cavity should be known. </p>
|
| 42 |
+
<p id="p-7" num="7">Please replace the paragraph beginning at page <part-num-ref name="paragraph beginning at page">19,</part-num-ref>
|
| 43 |
+
line <part-num-ref name="paragraph beginning at page 19, line">24</part-num-ref>
|
| 44 |
+
to page <part-num-ref name="to page">20,</part-num-ref>
|
| 45 |
+
line <part-num-ref name="to page 20, line">3</part-num-ref>
|
| 46 |
+
as with the following amended paragraph: </p>
|
| 47 |
+
<p id="p-8" num="8">As noted above, the PMEs on catheter <part-num-ref name="PMEs on catheter">110</part-num-ref>
|
| 48 |
+
can also used for cardiac mapping, such as that described in commonly owned patent application no. 11/451,898 now U.S. Pat. No. </p>
|
| 49 |
+
<p id="p-9" num="9">
|
| 50 |
+
<confidence value="6668666">7,515,9</confidence>
|
| 51 |
+
54, entitled "NON-CONTACT CARDIAC MAPPING, INCLUDING MOVING CATHETER AND MULTI-BEAT INTEGRATION" and filed June 13, 2006, the contents of which are incorporated herein by reference. As also noted above, because the frequency of the current injected by CIEs (e.g., <part-num-ref name="">10</part-num-ref>
|
| 52 |
+
kHz) is much higher than the frequency of the electrical activity of the patient's heart, the signal acquisition module can separate signals measured by the PMEs based on frequency to distinguish registration signals from cardiac mapping signals (e.g., <page-break num="2"/>
|
| 53 |
+
<boundary-data type="header">Applicant Doron Ha<confidence value="6686">rlev</confidence>
|
| 54 |
+
et al. Attorney's Docket No.: 20240-0006001 / RM-INVD-2 </boundary-data>
|
| 55 |
+
<boundary-data type="header">Serial No. : 11/672,562</boundary-data>
|
| 56 |
+
<boundary-data type="header">Filed <confidence value="6">:</confidence>
|
| 57 |
+
February 8, 2007 </boundary-data>
|
| 58 |
+
<boundary-data type="header">Page <confidence value="6">:</confidence>
|
| 59 |
+
<confidence value="8">3</confidence>
|
| 60 |
+
<confidence value="88">of</confidence>
|
| 61 |
+
<confidence value="88">19</confidence>
|
| 62 |
+
</boundary-data>
|
| 63 |
+
frequencies higher than <part-num-ref name="frequencies higher than">1</part-num-ref>
|
| 64 |
+
kHz, and lower than 1kHz, respectively.) Furthermore, in additional embodiments, catheter <part-num-ref name="kHz, and lower than 1kHz, respectively.) Furthermore, in additional embodiments, catheter">110</part-num-ref>
|
| 65 |
+
may include separate electrodes used only for cardiac mapping. </p>
|
| 66 |
+
<p id="p-10" num="10">Please replace the paragraph beginning at page <part-num-ref name="paragraph beginning at page">42,</part-num-ref>
|
| 67 |
+
lines 15-23 as with the following amended paragraph: </p>
|
| 68 |
+
<p id="p-11" num="11">Once the registration procedure is completed, the cardiac mapping (e.g., non-contact mapping) of electro-physiological information about the endocardium surface, as well as other post-registration operations may be performed. A description of the mapping and other post- operations procedures that may be performed are provided for example, in application serial No.</p>
|
| 69 |
+
<p id="p-12" num="12">11/451,871 now U.S. Pat. No. 7,729,752, entitled "NON-CONTACT CARDIAC MAPPING, INCLUDING RESOLUTION MAP," and filed June 13, 2006, the content of which is hereby incorporated by reference in its entirety, as well as application serial Nos. 11/451,898 now U.S.</p>
|
| 70 |
+
<p id="p-13" num="13">Pat. No. 7,515,954, and 11/451,908 now U.S. Pat. No. 7,505<confidence value="5">,</confidence>
|
| 71 |
+
810, referred to above. </p>
|
| 72 |
+
</description>
|
| 73 |
+
</us-patent-application>
|
| 74 |
+
|
applicant/11685894.xml
ADDED
|
@@ -0,0 +1,540 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>11685894</doc-number>
|
| 8 |
+
<date>2007-03-14</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<boundary-data type="header">Atty Dkt No. 016689.00074</boundary-data>
|
| 14 |
+
<heading id="h-1">WATER-BASED INK FOR INK-JET RECORDING</heading>
|
| 15 |
+
<heading id="h-2">CROSS REFERENCE TO RELATED APPLICATION</heading>
|
| 16 |
+
<p id="p-1" num="1">[01] This application claims priority to Japanese Patent Application No.</p>
|
| 17 |
+
<p id="p-2" num="2">2006-87562, filed March 28, 2006, which is incorporated herein by reference.</p>
|
| 18 |
+
<heading id="h-3">BACKGROUND</heading>
|
| 19 |
+
<p id="p-3" num="3">[02] An ink-jet recording apparatus has an ink-jet head with an ink ejection portion that ejects fine ink droplets of a water-based ink on a recording material.</p>
|
| 20 |
+
<p id="p-4" num="4">Several different systems can be used for ink ejection, such as an electrostatic attraction system, a drop-on-demand system, or a thermal ink-jet system. The ink ejection portion often has thin sheets of nickel or an iron-nickel alloy stacked one on top of another in a lamination structure. When the metal is continuously in contact with the water-based ink for ink-jet recording, corrosion can be generated in the metal. Metal rust powder resulting from the corrosion can be scattered in the ink, which can lead to ink ejection failure due to, for example, clogging of a nozzle. To avoid this problem, a benzotriazole type compound, specifically 1,2,3-benzotriazole, has been added to the ink as an anticorrosive (see U.S. Patents 6,648,463 and 6,938,999).</p>
|
| 21 |
+
<p id="p-5" num="5">[03] Coloring agents having a divalent metal, for example a phthalocyanine type dye and the like, are widely used in water-based inks for ink-jet recording. A benzotriazole type compound often is added as an anticorrosive to inks having such coloring agents. Although generation of rust can be suppressed, the divalent metal contained in the coloring agent and the benzotriazole type compound can react with each other such that a precipitate is generated. For controlling the amount of a metal ion such as a calcium ion, a copper ion, a magnesium ion, or an iron ion, a sequestering agent such as ethylene diamine tetraacetic acid has been added to the ink (see U.S. Patent 6,514,330).</p>
|
| 22 |
+
<p id="p-6" num="6">[04] As described in U.S. Patent 6,514,330, the sequestering agent is effective for suppressing the generation of a precipitate by reaction between the coloring agent and the benzotriazole type compound. However, the sequestering agent <boundary-data type="header">
|
| 23 |
+
<confidence value="8">1</confidence>
|
| 24 |
+
</boundary-data>
|
| 25 |
+
<page-break num="2"/>
|
| 26 |
+
<boundary-data type="header">Atty Dkt No. 016689.00074</boundary-data>
|
| 27 |
+
can promote elution of an adhesive between adjacent layers of a lamination structure in an ink ejection portion of the ink-jet head, thereby decreasing the bonding strength of the lamination structure. Therefore, it would be desirable to avoid the need for using a sequestering agent when an ink ejection portion of the ink-jet head contains a metal member in a lamination structure. </p>
|
| 28 |
+
<heading id="h-4">SUMMARY</heading>
|
| 29 |
+
<p id="p-7" num="7">[05] In one aspect, a water-based ink for ink-jet recording has a coloring agent containing a divalent metal in a structure thereof, a benzotriazole type compound, and a polymer containing a polymerization unit having at least two carboxyl groups in an ethylene chain unit.</p>
|
| 30 |
+
<p id="p-8" num="8">[06] In another aspect, an ink-jet recording apparatus may be configured to have an ink cartridge filled with the above-described water-based ink for ink-jet recording. An ink-jet head contains an ink ejection portion which communicates with the ink cartridge. The ink ejection portion contains a metal member made of nickel or a nickel-containing alloy.</p>
|
| 31 |
+
<heading id="h-5">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
|
| 32 |
+
<p id="p-9" num="9">[07] FIG. 1 shows a schematic perspective view of a configuration of an ink-jet recording apparatus; and [08] FIG. 2 shows a schematic view of an anodic polarization measurement.</p>
|
| 33 |
+
<heading id="h-6">DETAILED DESCRIPTION</heading>
|
| 34 |
+
<p id="p-10" num="10">General Overview [09] In one aspect, a water-based ink for ink-jet recording includes a coloring agent having a divalent metal in a structure thereof, a benzotriazole type compound, and a polymer containing a polymerization unit (repeating unit) having at least two carboxyl groups in an ethylene chain unit. The benzotriazole type compound may prevent corrosion of a metal in an ink ejection portion of an ink-jet head. The polymer may be effective for suppressing generation of a precipitate by reaction between the divalent metal and the benzotriazole type <boundary-data type="header">
|
| 35 |
+
<confidence value="8">2</confidence>
|
| 36 |
+
</boundary-data>
|
| 37 |
+
<page-break num="3"/>
|
| 38 |
+
<boundary-data type="header">Atty Dkt No. 016689.00074</boundary-data>
|
| 39 |
+
compound without using a sequestering agent. The ink may have an excellent corrosion inhibiting effect and an ink ejection stability effect. </p>
|
| 40 |
+
<p id="p-11" num="11">[10] The ink provides both a corrosion inhibiting effect and an ink ejection stability effect. Although the ink contains a coloring agent having a divalent metal in the structure thereof and a benzotriazole type compound, generation of a precipitate by reaction between the divalent metal and the benzotriazole type compound may be effectively prevented. As a result, a corrosion inhibiting effect against the ink ejection portion of the ink-jet head may be accomplished while ink ejection failure may be suppressed to a great extent.</p>
|
| 41 |
+
<p id="p-12" num="12">Illustrative Aspects of the Invention [11] A water-based ink for ink-jet recording (hereinafter sometimes "ink") according to aspects of the invention includes a coloring agent containing a divalent metal in a structure thereof, a benzotriazole type compound, and a polymer containing a polymerization unit having at least two carboxyl groups in an ethylene chain unit. The ink also typically includes water and, optionally, water-soluble organic solvents as a humectant and/or a penetrant.</p>
|
| 42 |
+
<p id="p-13" num="13">[12] The polymer may prevent generation of a precipitate from the reaction between the divalent metal in the coloring agent and the benzotriazole type compound.</p>
|
| 43 |
+
<p id="p-14" num="14">Although not wanting to be bound by theory, it is believed that the polymer becomes a polymer ion having a multivalent negative charge in the ink. In particular, each of the carboxyl groups of the polymer becomes a carboxylato (multivalent minus polymer ion) negatively charged, to thereby form a strong negative electric field. It is believed that the thus-formed electric field strongly attracts the divalent metal, which has a positive charge, and interferes with a chemical reaction between the divalent metal and the benzotriazole type compound.</p>
|
| 44 |
+
<p id="p-15" num="15">[13] It is believed that the polymer does not form a chelate ring against the divalent metal in the ink. Although forming a chelate ring having a 5- or 6-member ring structure may be favorable from the standpoint of energy, a chelate ring having a 7-member ring structure is generally disadvantageous from the standpoint of energy. When a sodium salt of a carboxyl group of the polymer <boundary-data type="header">
|
| 45 |
+
<confidence value="8">3</confidence>
|
| 46 |
+
</boundary-data>
|
| 47 |
+
<page-break num="4"/>
|
| 48 |
+
<boundary-data type="header">Atty Dkt No. 016689.00074</boundary-data>
|
| 49 |
+
chelates the divalent metal, the carboxylato which is hydrophilic decreases in amount, and the water-solubility thereof is decreased. As a result, a precipitate may form. </p>
|
| 50 |
+
<p id="p-16" num="16">[14] In the polymer, the number of the carboxyl groups per ethylene chain unit is usually two or more, and often is two. When the number of carboxyl group is <part-num-ref name="number of carboxyl group is">1,</part-num-ref>
|
| 51 |
+
the strength to attract the divalent metal is electrically not sufficient. Even when the divalent metal is attracted, free hydrophilic carboxylato becomes small in amount. Therefore, water solubility of the polymer tends to decrease. </p>
|
| 52 |
+
<p id="p-17" num="17">The reason why the polymer is used instead of a compound containing a low-molecular carboxyl group, such as ethylene diamine tetraacetic acid, is that problems associated with decreasing bonding strength of the lamination structure of the ink ejection portion of the ink-jet head may be avoided.</p>
|
| 53 |
+
<p id="p-18" num="18">[15] For purposes of suppressing the generation of the precipitate derived from the reaction between the divalent metal and the benzotriazole type compound, at least about 75% of the polymer unit configuring the polymer should be the polymer unit having at least two carboxyl groups in the ethylene chain unit.</p>
|
| 54 |
+
<p id="p-19" num="19">Up to 100% of the polymer units may be the polymer unit having at least two carboxyl groups in the ethylene chain unit.</p>
|
| 55 |
+
<p id="p-20" num="20">[16] Examples of compounds (monomers) which may be the polymerization unit (repeating unit) having at least two carboxyl groups in the ethylene chain unit include maleic acid, fumaric acid, itaconic acid, citraconic acid, mesaconic acid, sodium salts of these acids, and the like. A copolymer may include two or more of these compounds. Of these, itaconic acid and sodium itaconate each have a localized and strong negative charge. These monomers may be used to prepare polymers of polyitaconic acid and sodium polyitaconate. In addition to the monomers mentioned, other monomers such as acrylic acid, and methacrylic acid, may be used within the range of not impairing the effect of the polymer.</p>
|
| 56 |
+
<p id="p-21" num="21">[17] When the molecular weight of the polymer is unduly small, it may be necessary to increase the amount thereof to where ink ejection properties may be adversely affected. When the molecular weight is unduly high, the viscosity of the ink may increase undesirably. Given these considerations, the weight- <boundary-data type="header">
|
| 57 |
+
<confidence value="8">4</confidence>
|
| 58 |
+
</boundary-data>
|
| 59 |
+
<page-break num="5"/>
|
| 60 |
+
<boundary-data type="header">Atty Dkt No. 016689.00074</boundary-data>
|
| 61 |
+
average molecular weight is usually from about <part-num-ref name="weight- average molecular weight is usually from about">5000</part-num-ref>
|
| 62 |
+
to about <part-num-ref name="to about">15000,</part-num-ref>
|
| 63 |
+
and often from about <part-num-ref name="to about 15000, and often from about">6000</part-num-ref>
|
| 64 |
+
to about <part-num-ref name="to about">9000.</part-num-ref>
|
| 65 |
+
</p>
|
| 66 |
+
<p id="p-22" num="22">[18] The amount of the polymer in the ink usually ranges from a minimum amount below which the effect of preventing precipitation is not achieved, to a maximum amount above which the viscosity of the ink is increased and ink ejection stability may be decreased. Given these considerations, the amount of polymer usually ranges from about 0.05 wt% to about <part-num-ref name="amount of polymer usually ranges from about 0.05 wt% to about">5</part-num-ref>
|
| 67 |
+
wt%, and often from about 0.1 wt% to about <part-num-ref name="wt%, and often from about 0.1 wt% to about">4</part-num-ref>
|
| 68 |
+
wt%, based on the total weight of the ink. </p>
|
| 69 |
+
<p id="p-23" num="23">[19] The ink includes one or more coloring agents having a divalent metal in the structure thereof. Non-limiting examples of coloring agents include dyes such as direct dyes, acid dyes, basic dyes, and the like, and pigments such as dispersant-using type pigments, self-dispersing type pigments, and the like.</p>
|
| 70 |
+
<p id="p-24" num="24">When the amount of coloring agent(s) in the ink is unduly small, a desired print density may not be achieved. When the amount of coloring agent(s) is unduly large, a precipitate may be generated when the ink is dried that may cause clogging of a nozzle or the like. Given these considerations, the amount of coloring agent usually ranges from about 0.2 wt% to about <part-num-ref name="amount of coloring agent usually ranges from about 0.2 wt% to about">10</part-num-ref>
|
| 71 |
+
wt%, and often from about 0.3 wt% to about <part-num-ref name="wt%, and often from about 0.3 wt% to about">5</part-num-ref>
|
| 72 |
+
wt%, based on the total weight of the ink. </p>
|
| 73 |
+
<p id="p-25" num="25">[20] The divalent metals in the coloring agents may be, for example, copper, nickel, chromium, and the like. Examples of the coloring agents having a divalent metal in the structure thereof include, but are not limited to, complex type dyes such as metal phthalocyanine type dyes, monoazo complex type dyes and the like. In particular, copper complex dyes, particularly, copper phthalocyanine type dyes may be used.</p>
|
| 74 |
+
<p id="p-26" num="26">[21] Specific examples of the copper phthalocyanine type dyes include compounds represented by the following chemical formulas <part-num-ref name="following chemical formulas">(1)</part-num-ref>
|
| 75 |
+
to (5). In the chemical formulas <part-num-ref name="chemical formulas">(1)</part-num-ref>
|
| 76 |
+
to (5), Pc (Cu) represents a copper phthalocyanine nucleus represented by the general formula (1), and at least one of R1, R<confidence value="5">2</confidence>
|
| 77 |
+
, R3, and R4 is presented in each of four benzene rings A, B, C, and D in the copper phthalocyanine nucleus represented by the general formula (1): </p>
|
| 78 |
+
<p id="p-27" num="27">(Chemical formula (1));</p>
|
| 79 |
+
<boundary-data type="header">
|
| 80 |
+
<confidence value="8">5</confidence>
|
| 81 |
+
</boundary-data>
|
| 82 |
+
<boundary-data type="header">Atty Dkt No. 016689.00074</boundary-data>
|
| 83 |
+
<p id="p-28" num="28">
|
| 84 |
+
<page-break num="6"/>
|
| 85 |
+
(R1)3 Pc(Cu<confidence value="51">)7</confidence>
|
| 86 |
+
(R2) R1= <confidence value="85885">S02(C</confidence>
|
| 87 |
+
H2)3SO3Li <confidence value="666">R2=</confidence>
|
| 88 |
+
<confidence value="285885">-S02(C</confidence>
|
| 89 |
+
H2)3SO2N<confidence value="8">H</confidence>
|
| 90 |
+
CH2CHCH3 </p>
|
| 91 |
+
<heading id="h-7">
|
| 92 |
+
<confidence value="88">OH</confidence>
|
| 93 |
+
</heading>
|
| 94 |
+
<p id="p-29" num="29">(Chemical formula (2));</p>
|
| 95 |
+
<p id="p-30" num="30">(R1)3 Pc(Cu<confidence value="51">)7</confidence>
|
| 96 |
+
(R2) R1= <confidence value="85885">S02(C</confidence>
|
| 97 |
+
H2)3SO3Li <confidence value="666">R2=</confidence>
|
| 98 |
+
<confidence value="285885">-S02(C</confidence>
|
| 99 |
+
H2)3SO2N<confidence value="8">H</confidence>
|
| 100 |
+
<confidence value="2222222">CHCH2OH</confidence>
|
| 101 |
+
<confidence value="588">CH3</confidence>
|
| 102 |
+
(Chemical formula (3)); </p>
|
| 103 |
+
<p id="p-31" num="31">(R1)3 Pc(Cu<confidence value="51">)7</confidence>
|
| 104 |
+
(R2) <confidence value="656">R1=</confidence>
|
| 105 |
+
<confidence value="285885">-S02(C</confidence>
|
| 106 |
+
H2)3SO3Li <confidence value="666">R2=</confidence>
|
| 107 |
+
<confidence value="86">SO</confidence>
|
| 108 |
+
2(CH2)3SO2N <confidence value="855514">C2H40H</confidence>
|
| 109 |
+
(Chemical formula (4)); </p>
|
| 110 |
+
<p id="p-32" num="32">
|
| 111 |
+
<confidence value="1">/</confidence>
|
| 112 |
+
(R1)2 Pc(Cu) (R2) (R3) <confidence value="656285885">R1=-S02(C</confidence>
|
| 113 |
+
H2)3SO3Li <boundary-data type="header">
|
| 114 |
+
<confidence value="8">6</confidence>
|
| 115 |
+
</boundary-data>
|
| 116 |
+
<page-break num="7"/>
|
| 117 |
+
<boundary-data type="header">Atty Dkt No. 016689.00074</boundary-data>
|
| 118 |
+
<confidence value="666285885">R2=-S02(C</confidence>
|
| 119 |
+
H2)3SO2NHCH2CHCH3 </p>
|
| 120 |
+
<heading id="h-8">
|
| 121 |
+
<confidence value="88">OH</confidence>
|
| 122 |
+
</heading>
|
| 123 |
+
<p id="p-33" num="33">
|
| 124 |
+
<confidence value="666">R3=</confidence>
|
| 125 |
+
<confidence value="285885">-S02(C</confidence>
|
| 126 |
+
H2)3SO2NH <confidence value="2222222">CHCH2OH</confidence>
|
| 127 |
+
<confidence value="588">CH3</confidence>
|
| 128 |
+
(Chemical formula (5)); </p>
|
| 129 |
+
<p id="p-34" num="34">(R1) Pc(Cu) (R3) (R4) <confidence value="858">R1=</confidence>
|
| 130 |
+
<confidence value="85885">S02(C</confidence>
|
| 131 |
+
H2)3SO3Li <confidence value="666">R2=</confidence>
|
| 132 |
+
<confidence value="285885">-S02(C</confidence>
|
| 133 |
+
H2)3<confidence value="66">CO</confidence>
|
| 134 |
+
2Li <confidence value="666">R3=</confidence>
|
| 135 |
+
<confidence value="285885">-S02(C</confidence>
|
| 136 |
+
H2)3SO2N<confidence value="858868588">HCH2CHCH3</confidence>
|
| 137 |
+
</p>
|
| 138 |
+
<heading id="h-9">
|
| 139 |
+
<confidence value="88">OH</confidence>
|
| 140 |
+
</heading>
|
| 141 |
+
<p id="p-35" num="35">
|
| 142 |
+
<confidence value="666">R4=</confidence>
|
| 143 |
+
<confidence value="285885">-S02(C</confidence>
|
| 144 |
+
H2)3SO2N<confidence value="8">H</confidence>
|
| 145 |
+
<confidence value="2222222">CHCH2OH</confidence>
|
| 146 |
+
<confidence value="588">CH3</confidence>
|
| 147 |
+
and (General formula (1)). </p>
|
| 148 |
+
<boundary-data type="header">
|
| 149 |
+
<confidence value="8">7</confidence>
|
| 150 |
+
</boundary-data>
|
| 151 |
+
<boundary-data type="header">Atty Dkt No. 016689.00074</boundary-data>
|
| 152 |
+
<heading id="h-10">
|
| 153 |
+
<confidence value="8">H</confidence>
|
| 154 |
+
<confidence value="6">D</confidence>
|
| 155 |
+
<confidence value="5">H</confidence>
|
| 156 |
+
</heading>
|
| 157 |
+
<heading id="h-11">H N <confidence value="22">\N</confidence>
|
| 158 |
+
<confidence value="8">N</confidence>
|
| 159 |
+
<confidence value="8">H</confidence>
|
| 160 |
+
</heading>
|
| 161 |
+
<heading id="h-12">
|
| 162 |
+
<confidence value="2">I</confidence>
|
| 163 |
+
<confidence value="8">N</confidence>
|
| 164 |
+
</heading>
|
| 165 |
+
<p id="p-36" num="36">
|
| 166 |
+
<page-break num="8"/>
|
| 167 |
+
<confidence value="5">C</confidence>
|
| 168 |
+
<confidence value="2">|</confidence>
|
| 169 |
+
<confidence value="8">N</confidence>
|
| 170 |
+
Cu N A </p>
|
| 171 |
+
<heading id="h-13">H N <confidence value="6">N</confidence>
|
| 172 |
+
<confidence value="5">-</confidence>
|
| 173 |
+
<confidence value="8">N</confidence>
|
| 174 |
+
<confidence value="8">H</confidence>
|
| 175 |
+
</heading>
|
| 176 |
+
<heading id="h-14">
|
| 177 |
+
<confidence value="8">H</confidence>
|
| 178 |
+
<confidence value="6">B</confidence>
|
| 179 |
+
<confidence value="5">H</confidence>
|
| 180 |
+
</heading>
|
| 181 |
+
<p id="p-37" num="37">[22] The ink also includes water. Water of high purity usually is used, such as deionized water, distilled water, or the like. The amount of water usually ranges from about <part-num-ref name="amount of water usually ranges from about">10</part-num-ref>
|
| 182 |
+
wt% to <part-num-ref name="wt% to">98</part-num-ref>
|
| 183 |
+
wt%, and often from about <part-num-ref name="wt%, and often from about">30</part-num-ref>
|
| 184 |
+
wt% to about <part-num-ref name="wt% to about">95</part-num-ref>
|
| 185 |
+
wt%, based on the total weight of the ink. </p>
|
| 186 |
+
<p id="p-38" num="38">[23] The ink according to aspects of the invention may further include a water-soluble organic solvent. Such water-soluble organic solvents are principally classified into humectants, which each have an effect of preventing the ink from being dried at a tip end portion of the ink-jet head, and penetrants, which accelerate a drying speed of the ink on a paper surface.</p>
|
| 187 |
+
<p id="p-39" num="39">[24] Examples of humectants include, but are not limited to, lower alcohols such as methyl alcohol, ethyl alcohol, n-propyl alcohol, isopropyl alcohol, n-butyl alcohol, sec-butyl alcohol, tert-butyl alcohol and the like; amides such as dimethylformamide, dimethylacetamide and the like; ketones or keto-alcohols such as acetone, diacetone alcohol and the like; ethers such as tetrahydrofuran, dioxane and the like; polyalkylene glycols such as polyethylene glycol, <boundary-data type="header">
|
| 188 |
+
<confidence value="8">8</confidence>
|
| 189 |
+
</boundary-data>
|
| 190 |
+
<page-break num="9"/>
|
| 191 |
+
<boundary-data type="header">Atty Dkt No. 016689.00074</boundary-data>
|
| 192 |
+
polypropylene glycol and the like; alkylene glycols such as ethylene glycol, propylene glycol, butylene glycol, diethylene glycol, triethylene glycol, dipropylene glycol, tripropylene glycol, thiodiglycol, hexylene glycol and the like; glycerin; 2-pyrrolidone; N-methyl-2-pyrrolidone; 1,3-dimethyl-2- imidazolidinone; and the like; and combinations thereof. Polyvalent alcohols such as alkylene glycols, glycerin and the like, are often used. </p>
|
| 193 |
+
<p id="p-40" num="40">[25] The amount of humectant in the ink is usually from <part-num-ref name="ink is usually from">0</part-num-ref>
|
| 194 |
+
wt% to about <part-num-ref name="wt% to about">95</part-num-ref>
|
| 195 |
+
wt%, often from about <part-num-ref name="wt%, often from about">10</part-num-ref>
|
| 196 |
+
wt% to about <part-num-ref name="wt% to about">80</part-num-ref>
|
| 197 |
+
wt%, and more often from about <part-num-ref name="wt%, and more often from about">10</part-num-ref>
|
| 198 |
+
wt% to about <part-num-ref name="wt% to about">50</part-num-ref>
|
| 199 |
+
wt%, based on the total weight of the ink. </p>
|
| 200 |
+
<p id="p-41" num="41">[26] Examples of penetrants include, but are not limited to, ethylene glycol type ethers such as ethylene glycol methyl ether, ethylene glycol ethyl ether, ethylene glycol propyl ether, ethylene glycol butyl ether, diethylene glycol methyl ether, diethylene glycol ethyl ether, diethylene glycol propyl ether, diethylene glycol butyl ether, triethylene glycol methyl ether, triethylene glycol ethyl ether, triethylene glycol propyl ether, triethylene glycol butyl ether, propylene glycol methyl ether, and the like; propylene glycol type ethers such as propylene glycol ethyl ether, propylene glycol propyl ether, propylene glycol butyl ether, dipropylene glycol methyl ether, dipropylene glycol ethyl ether, dipropylene glycol propyl ether, dipropylene glycol butyl ether, tripropylene glycol methyl ether, tripropylene glycol ethyl ether, tripropylene glycol propyl ether, tripropylene glycol butyl ether, and the like; and combinations thereof.</p>
|
| 201 |
+
<p id="p-42" num="42">[27] The amount of penetrant in the ink is usually from <part-num-ref name="ink is usually from">0</part-num-ref>
|
| 202 |
+
wt% to about <part-num-ref name="wt% to about">20</part-num-ref>
|
| 203 |
+
wt%, often from about 0.1 wt% to about <part-num-ref name="wt%, often from about 0.1 wt% to about">15</part-num-ref>
|
| 204 |
+
wt%, and more often from about 0.5 wt% to about <part-num-ref name="wt%, and more often from about 0.5 wt% to about">10</part-num-ref>
|
| 205 |
+
wt%, based on the total weight of the ink. When the amount is excessive, penetrability of the ink into recording paper may become unduly high and blurring may sometimes occur. </p>
|
| 206 |
+
<p id="p-43" num="43">[28] The ink also may include known additives, such as various types of surfactants, viscosity-adjusting agents, surface tension modifiers, pH modifiers, preservatives, mildewproofing agents, and the like.</p>
|
| 207 |
+
<p id="p-44" num="44">[29] The ink may be prepared by uniformly mixing the coloring agent containing the divalent metal in the structure thereof, the benzotriazole type compound, the polymer containing the polymerization unit having at least two carboxyl groups <boundary-data type="header">
|
| 208 |
+
<confidence value="8">9</confidence>
|
| 209 |
+
</boundary-data>
|
| 210 |
+
<page-break num="10"/>
|
| 211 |
+
<boundary-data type="header">Atty Dkt No. 016689.00074</boundary-data>
|
| 212 |
+
in the ethylene chain unit, water, and various types of additives as needed, in accordance with conventional techniques. </p>
|
| 213 |
+
<p id="p-45" num="45">[30] The ink as described above may be filled in a known ink-jet cartridge which may be detachably attached to an ink-jet recording apparatus of known configuration. The ink-jet recording apparatus typically has an ink-jet head having an ink discharge portion which communicates with the cartridge. Even when the ink ejection portion contains a metal member, e.g., made of nickel or the nickel-containing alloy, generation of rust may be suppressed. Even though a coloring agent containing a divalent metal in the structure thereof and a benzotriazole type compound are contained in the ink, generation of a precipitate by the reaction between the divalent metal and the benzotriazole type compound may be minimized or prevented. As a result, the apparatus provides excellent ink ejection stability.</p>
|
| 214 |
+
<p id="p-46" num="46">[31] A schematic perspective view of a configuration of an ink-jet recording apparatus according to aspects of the invention is shown in FIG. 1.</p>
|
| 215 |
+
<p id="p-47" num="47">[32] This ink-jet recording apparatus 1 includes ink cartridges <part-num-ref name="includes ink cartridges">2</part-num-ref>
|
| 216 |
+
which contain <part-num-ref name="which contain">4</part-num-ref>
|
| 217 |
+
color inks, typically cyan, magenta, yellow and black inks, respectively, a head unit <part-num-ref name="head unit">4</part-num-ref>
|
| 218 |
+
having an ink-jet head <part-num-ref name="ink-jet head">3</part-num-ref>
|
| 219 |
+
for performing print on a recording medium P such as recording paper, a carriage <part-num-ref name="carriage">5</part-num-ref>
|
| 220 |
+
on which the ink cartridges <part-num-ref name="ink cartridges">2</part-num-ref>
|
| 221 |
+
and the head unit <part-num-ref name="head unit">4</part-num-ref>
|
| 222 |
+
are mounted, a drive unit <part-num-ref name="drive unit">6</part-num-ref>
|
| 223 |
+
that reciprocates the carriage <part-num-ref name="carriage">5</part-num-ref>
|
| 224 |
+
in a straight line direction, a platen roller <part-num-ref name="platen roller">7</part-num-ref>
|
| 225 |
+
that extends in a reciprocating direction of the carriage <part-num-ref name="carriage">5</part-num-ref>
|
| 226 |
+
and is disposed opposite to the ink-jet head <part-num-ref name="ink-jet head">3,</part-num-ref>
|
| 227 |
+
and a purge unit <part-num-ref name="purge unit">
|
| 228 |
+
<confidence value="68">8.</confidence>
|
| 229 |
+
</part-num-ref>
|
| 230 |
+
</p>
|
| 231 |
+
<p id="p-48" num="48">[33] The four filled ink cartridges <part-num-ref name="four filled ink cartridges">2</part-num-ref>
|
| 232 |
+
are arranged on a placing portion 4a of the head unit <part-num-ref name="head unit">4</part-num-ref>
|
| 233 |
+
between a pair of side covers 4b formed at both sides of the placing portion 4a. </p>
|
| 234 |
+
<p id="p-49" num="49">[34] The drive unit <part-num-ref name="drive unit">6</part-num-ref>
|
| 235 |
+
includes a carriage shaft <part-num-ref name="carriage shaft">9</part-num-ref>
|
| 236 |
+
that is disposed at a lower end portion of the carriage <part-num-ref name="carriage">5</part-num-ref>
|
| 237 |
+
and extends in parallel with the platen roller <part-num-ref name="platen roller">7,</part-num-ref>
|
| 238 |
+
a guide plate <part-num-ref name="guide plate">10</part-num-ref>
|
| 239 |
+
that is disposed at an upper end portion of the carriage <part-num-ref name="carriage">5</part-num-ref>
|
| 240 |
+
and extends in parallel with the carriage shaft <part-num-ref name="carriage shaft">9,</part-num-ref>
|
| 241 |
+
two pulleys <part-num-ref name="carriage shaft 9, two pulleys">11</part-num-ref>
|
| 242 |
+
and <part-num-ref name="and">12</part-num-ref>
|
| 243 |
+
that are disposed at both end portions of the carriage shaft <part-num-ref name="carriage shaft">9</part-num-ref>
|
| 244 |
+
and between the carriage shaft <part-num-ref name="carriage shaft">9</part-num-ref>
|
| 245 |
+
and the guide plate <part-num-ref name="guide plate">10,</part-num-ref>
|
| 246 |
+
and an endless belt <part-num-ref name="endless belt">13</part-num-ref>
|
| 247 |
+
that is stretched between the pulleys <part-num-ref name="pulleys">11</part-num-ref>
|
| 248 |
+
and <part-num-ref name="and">12.</part-num-ref>
|
| 249 |
+
</p>
|
| 250 |
+
<boundary-data type="header">
|
| 251 |
+
<confidence value="88">10</confidence>
|
| 252 |
+
</boundary-data>
|
| 253 |
+
<boundary-data type="header">Atty Dkt No. 016689.00074</boundary-data>
|
| 254 |
+
<p id="p-50" num="50">
|
| 255 |
+
<page-break num="11"/>
|
| 256 |
+
[35] As the pulley <part-num-ref name="pulley">11</part-num-ref>
|
| 257 |
+
out of the two is rotated in normal and reverse directions by a carriage motor <part-num-ref name="carriage motor">101,</part-num-ref>
|
| 258 |
+
the carriage <part-num-ref name="carriage">5</part-num-ref>
|
| 259 |
+
that is connected to the endless belt <part-num-ref name="endless belt">13</part-num-ref>
|
| 260 |
+
is reciprocated in the straight line direction, along the carriage shaft <part-num-ref name="carriage shaft">9</part-num-ref>
|
| 261 |
+
and the guide plate <part-num-ref name="guide plate">10,</part-num-ref>
|
| 262 |
+
in accordance with the normal and reverse rotation of the pulley <part-num-ref name="pulley">11.</part-num-ref>
|
| 263 |
+
</p>
|
| 264 |
+
<p id="p-51" num="51">[36] The recording medium P is supplied from a sheet supply cassette (not shown) provided on a side of or under the ink-jet recording apparatus <part-num-ref name="ink-jet recording apparatus">1,</part-num-ref>
|
| 265 |
+
fed between the ink-jet head <part-num-ref name="ink-jet head">3</part-num-ref>
|
| 266 |
+
and the platen roller <part-num-ref name="platen roller">7,</part-num-ref>
|
| 267 |
+
subjected to predetermined printing by the ink ejected from the ink-jet head <part-num-ref name="ink-jet head">3,</part-num-ref>
|
| 268 |
+
and then discharged to the outside. A sheet feeding mechanism and a sheet discharging mechanism of the recording medium P are omitted from FIG. 1. </p>
|
| 269 |
+
<p id="p-52" num="52">[37] The purge unit <part-num-ref name="purge unit">
|
| 270 |
+
<confidence value="5">8</confidence>
|
| 271 |
+
</part-num-ref>
|
| 272 |
+
is provided on a side of the platen roller <part-num-ref name="platen roller">7.</part-num-ref>
|
| 273 |
+
The purge unit <part-num-ref name="purge unit">
|
| 274 |
+
<confidence value="5">8</confidence>
|
| 275 |
+
</part-num-ref>
|
| 276 |
+
is disposed such that it is opposed to the ink-jet head <part-num-ref name="ink-jet head">3</part-num-ref>
|
| 277 |
+
when the head unit <part-num-ref name="head unit">4</part-num-ref>
|
| 278 |
+
is placed in a reset position. The purge unit <part-num-ref name="purge unit">
|
| 279 |
+
<confidence value="5">8</confidence>
|
| 280 |
+
</part-num-ref>
|
| 281 |
+
includes a purge cap <part-num-ref name="purge cap">14</part-num-ref>
|
| 282 |
+
that covers with opening portions of nozzles such that it covers a plurality of nozzles (not shown) formed in the ink-jet head <part-num-ref name="ink-jet head">3,</part-num-ref>
|
| 283 |
+
a pump <part-num-ref name="pump">15,</part-num-ref>
|
| 284 |
+
a cam <part-num-ref name="cam">16,</part-num-ref>
|
| 285 |
+
and an ink reservoir <part-num-ref name="ink reservoir">17.</part-num-ref>
|
| 286 |
+
When the head unit <part-num-ref name="head unit">4</part-num-ref>
|
| 287 |
+
is placed in the reset position, the nozzles in the ink-jet head <part-num-ref name="ink-jet head">3</part-num-ref>
|
| 288 |
+
are covered with the purge cap <part-num-ref name="purge cap">14</part-num-ref>
|
| 289 |
+
to suck defect ink, containing air bubbles trapped inside the ink-jet head <part-num-ref name="ink-jet head">3,</part-num-ref>
|
| 290 |
+
by the pump <part-num-ref name="pump">15</part-num-ref>
|
| 291 |
+
driven by the cam <part-num-ref name="cam">16,</part-num-ref>
|
| 292 |
+
to thereby aim for recovering the ink-jet head <part-num-ref name="ink-jet head">3.</part-num-ref>
|
| 293 |
+
The sucked defect ink is stored in the ink reservoir <part-num-ref name="ink reservoir">17.</part-num-ref>
|
| 294 |
+
</p>
|
| 295 |
+
<p id="p-53" num="53">[38] A wiper member <part-num-ref name="wiper member">20</part-num-ref>
|
| 296 |
+
is provided adjacent to the purge unit <part-num-ref name="purge unit">
|
| 297 |
+
<confidence value="5">8</confidence>
|
| 298 |
+
</part-num-ref>
|
| 299 |
+
in a position at the side of the platen roller <part-num-ref name="platen roller">7</part-num-ref>
|
| 300 |
+
in the purge unit <part-num-ref name="purge unit">
|
| 301 |
+
<confidence value="5">8</confidence>
|
| 302 |
+
. </part-num-ref>
|
| 303 |
+
The wiper member <part-num-ref name="wiper member">20</part-num-ref>
|
| 304 |
+
is shaped in a spatula and wipes a nozzle-formed face of the ink-jet head <part-num-ref name="ink-jet head">3</part-num-ref>
|
| 305 |
+
along the displacement of the carriage <part-num-ref name="carriage">5.</part-num-ref>
|
| 306 |
+
In order to prevent the ink from being dried, the cap <part-num-ref name="cap">1<confidence value="5">8</confidence>
|
| 307 |
+
</part-num-ref>
|
| 308 |
+
is provided to cover a plurality of nozzles in the ink-jet head <part-num-ref name="ink-jet head">3</part-num-ref>
|
| 309 |
+
which returns to the reset position after printing. </p>
|
| 310 |
+
<p id="p-54" num="54">Examples 1 to <part-num-ref name="to">12</part-num-ref>
|
| 311 |
+
and Comparative Examples <part-num-ref name="and Comparative Examples">1</part-num-ref>
|
| 312 |
+
to <part-num-ref name="to">6</part-num-ref>
|
| 313 |
+
[39] Hereinafter, the present invention will be described in detail with reference to examples of water-based ink for ink-jet recording. However, these examples <boundary-data type="header">
|
| 314 |
+
<confidence value="88">11</confidence>
|
| 315 |
+
</boundary-data>
|
| 316 |
+
<page-break num="12"/>
|
| 317 |
+
<boundary-data type="header">Atty Dkt No. 016689.00074</boundary-data>
|
| 318 |
+
are illustrative and should not be interpreted as limiting the invention in any way. </p>
|
| 319 |
+
<p id="p-55" num="55">(a) Preparation of water-based ink for ink-jet recording [40] Components of ink compositions in Table 1 were mixed and stirred. The resultant mixture was allowed to pass through a hydrophilic PTFE (polytetrafluoroethylene) type membrane filter (produced by Toyo Roshi Kaisha, Ltd.) having a pore diameter of 0.2 <confidence value="2">p</confidence>
|
| 320 |
+
m (except a pore diameter of 1.0 <confidence value="2">p</confidence>
|
| 321 |
+
m was used for Example 12), to thereby obtain water-based inks for ink-jet recording. Each of the inks in examples <part-num-ref name="inks in examples">1</part-num-ref>
|
| 322 |
+
to <part-num-ref name="to">12</part-num-ref>
|
| 323 |
+
contains a polymer containing a polymerization unit having at least two carboxyl groups in an ethylene chain unit thereof. The inks in Comparative Examples <part-num-ref name="inks in Comparative Examples">1</part-num-ref>
|
| 324 |
+
to <part-num-ref name="to">6</part-num-ref>
|
| 325 |
+
do not contain such a polymer. </p>
|
| 326 |
+
<p id="p-56" num="56">[41] Dyes (1) to <part-num-ref name="to">(5)</part-num-ref>
|
| 327 |
+
used in Examples and Comparative Examples correspond to compounds to chemical formulas <part-num-ref name="used in Examples and Comparative Examples correspond to compounds to chemical formulas">(1)</part-num-ref>
|
| 328 |
+
to (5), respectively. </p>
|
| 329 |
+
<p id="p-57" num="57">(b) Ink ejection performance test [42] The thus-obtained water-based inks for ink-jet recording were filled in desired cartridges, and then the ink cartridges thus filled with the inks were attached to a digital multifunction device equipped with an ink-jet printer DCP-1<confidence value="88">10</confidence>
|
| 330 |
+
(produced by Brother Industries, Ltd.). The inks were then subjected to a 300-sheet continuous printing test, and thereafter the number of pins showing any dropout, or any ejection curvature were measured. The test result was evaluated in accordance with the criteria as described below and the obtained results are shown in Table <part-num-ref name="obtained results are shown in Table">1.</part-num-ref>
|
| 331 |
+
As a practical matter, an evaluation "A" or "B" is needed for commercial feasibility. </p>
|
| 332 |
+
<p id="p-58" num="58">A: no pin showing the dropout or the ejection curvature B: from <part-num-ref name="ejection curvature B: from">1</part-num-ref>
|
| 333 |
+
to <part-num-ref name="to">5</part-num-ref>
|
| 334 |
+
pins showing the dropout or the ejection curvature C: from <part-num-ref name="ejection curvature C: from">6</part-num-ref>
|
| 335 |
+
to <part-num-ref name="to">10</part-num-ref>
|
| 336 |
+
pins showing the dropout or the ejection curvature D: <part-num-ref name="ejection curvature D:">11</part-num-ref>
|
| 337 |
+
or more pins showing the dropout or the ejection curvature <boundary-data type="header">
|
| 338 |
+
<confidence value="88">12</confidence>
|
| 339 |
+
</boundary-data>
|
| 340 |
+
<page-break num="13"/>
|
| 341 |
+
<boundary-data type="header">Atty Dkt No. 016689.00074</boundary-data>
|
| 342 |
+
(c) Filtration evaluation test [43] <part-num-ref name="ejection curvature (c) Filtration evaluation test [43]">120</part-num-ref>
|
| 343 |
+
g of the thus-obtained inks were subjected to an accelerated test for <part-num-ref name="accelerated test for">2</part-num-ref>
|
| 344 |
+
weeks at 60<confidence value="1">°</confidence>
|
| 345 |
+
C in a sealed condition, and then allowed to pass through a hydrophilic PTFE (polytetrafluoroethylene) type membrane filter (produced by Toyo Roshi Kaisha, Ltd.) having a diameter of 47 mm and a pore diameter of 0.2 <confidence value="2">p</confidence>
|
| 346 |
+
m (except a pore diameter of 1.0 <confidence value="2">p</confidence>
|
| 347 |
+
m was used for Example <part-num-ref name="pore diameter of 1.0 pm was used for Example">12)</part-num-ref>
|
| 348 |
+
under a reduced pressure. </p>
|
| 349 |
+
<p id="p-59" num="59">Thereafter, the weight of the ink passed through the membrane filter was measured and evaluated in accordance with the criteria as described below.</p>
|
| 350 |
+
<p id="p-60" num="60">The obtained results are shown in Table 1. As a practical matter, an evaluation "A" or "B" is needed for commercial feasibility.</p>
|
| 351 |
+
<p id="p-61" num="61">A: 100 g or more of ink passed through the membrane filter B: from <part-num-ref name="membrane filter B: from">80</part-num-ref>
|
| 352 |
+
g to less than <part-num-ref name="g to less than">100</part-num-ref>
|
| 353 |
+
g of ink passed through the membrane filter C: from <part-num-ref name="membrane filter C: from">50</part-num-ref>
|
| 354 |
+
g to less than <part-num-ref name="g to less than">80</part-num-ref>
|
| 355 |
+
g of ink passed through the membrane filter D: less than <part-num-ref name="membrane filter D: less than">50</part-num-ref>
|
| 356 |
+
g of ink passed through the membrane filter (d) Anodic polarization measurement [44] In an electrochemical measuring system HZ-3000 (produced by Hokuto Denko Corporation), an anodic polarization measurement was performed by a configuration shown in FIG. 2, which used an electrode as shown in Table <part-num-ref name="electrode as shown in Table">2.</part-num-ref>
|
| 357 |
+
</p>
|
| 358 |
+
<p id="p-62" num="62">An iron-nickel alloy as shown in Table 2 denotes a nickel-iron alloy containing 42% nickel, namely, a so-called <part-num-ref name="so-called">42</part-num-ref>
|
| 359 |
+
alloy. </p>
|
| 360 |
+
<p id="p-63" num="63">[45] A method for the anodic polarization measurement was used as follows: <part-num-ref name="anodic polarization measurement was used as follows:">(1)</part-num-ref>
|
| 361 |
+
an ink <part-num-ref name="ink">40</part-num-ref>
|
| 362 |
+
was introduced into a beaker <part-num-ref name="beaker">41,</part-num-ref>
|
| 363 |
+
and the beaker <part-num-ref name="beaker">41</part-num-ref>
|
| 364 |
+
was immersed for <part-num-ref name="was immersed for">30</part-num-ref>
|
| 365 |
+
to <part-num-ref name="to">60</part-num-ref>
|
| 366 |
+
minutes in a thermostatic bath <part-num-ref name="thermostatic bath">39</part-num-ref>
|
| 367 |
+
set to a temperature of 60<confidence value="1">°</confidence>
|
| 368 |
+
C such that the temperature of the ink <part-num-ref name="ink">40</part-num-ref>
|
| 369 |
+
was allowed to be 60<confidence value="1">°</confidence>
|
| 370 |
+
C; <part-num-ref name="was allowed to be 60°C;">(2)</part-num-ref>
|
| 371 |
+
a metal piece, which was used for a working electrode <part-num-ref name="working electrode">33,</part-num-ref>
|
| 372 |
+
was immersed for <part-num-ref name="working electrode 33, was immersed for">5</part-num-ref>
|
| 373 |
+
minutes in an alkaline washing solution ACE CLEAN <part-num-ref name="alkaline washing solution ACE CLEAN">850</part-num-ref>
|
| 374 |
+
(produced by Okuno Chemical Industries Co., Ltd.) at 60<confidence value="1">°</confidence>
|
| 375 |
+
C, and then the metal piece was washed with purified water; <part-num-ref name="metal piece was washed with purified water;">(3)</part-num-ref>
|
| 376 |
+
the metal piece to be used as the working electrode <part-num-ref name="working electrode">33</part-num-ref>
|
| 377 |
+
and a platinum plate to be used as a counter electrode <part-num-ref name="counter electrode">34,</part-num-ref>
|
| 378 |
+
which were electrically connected to a main apparatus body <part-num-ref name="main apparatus body">31,</part-num-ref>
|
| 379 |
+
were immersed in the ink <part-num-ref name="ink">40</part-num-ref>
|
| 380 |
+
introduced into the beaker 41; </p>
|
| 381 |
+
<boundary-data type="header">
|
| 382 |
+
<confidence value="88">13</confidence>
|
| 383 |
+
</boundary-data>
|
| 384 |
+
<boundary-data type="header">Atty Dkt No. 016689.00074</boundary-data>
|
| 385 |
+
<p id="p-64" num="64">
|
| 386 |
+
<page-break num="14"/>
|
| 387 |
+
(4) a silver/silver chloride plate to be used as the reference electrode <part-num-ref name="reference electrode">32,</part-num-ref>
|
| 388 |
+
which was electrically connected to the main apparatus body <part-num-ref name="main apparatus body">31,</part-num-ref>
|
| 389 |
+
was immersed in the saturated potassium chloride solution <part-num-ref name="saturated potassium chloride solution">37</part-num-ref>
|
| 390 |
+
introduced into the reference electrode bath <part-num-ref name="reference electrode bath">36</part-num-ref>
|
| 391 |
+
connected to the ink <part-num-ref name="ink">40</part-num-ref>
|
| 392 |
+
introduced into the beaker <part-num-ref name="beaker">41</part-num-ref>
|
| 393 |
+
by the potassium chloride salt bridge 35; and <part-num-ref name="potassium chloride salt bridge 35; and">(5)</part-num-ref>
|
| 394 |
+
the electric potential is continuously changed within an electric potential range of from -600 to +300 mV to measure a current density. </p>
|
| 395 |
+
<p id="p-65" num="65">[46] Measurement results were evaluated in accordance with criteria as described below. The obtained results are shown in Table <part-num-ref name="obtained results are shown in Table">1.</part-num-ref>
|
| 396 |
+
As a practical matter, an evaluation "A" is needed for commercial feasibility. </p>
|
| 397 |
+
<p id="p-66" num="66">A: current density in the electric potential range from -600 to +300 mV is <part-num-ref name="electric potential range from -600 to +300 mV is">100</part-num-ref>
|
| 398 |
+
<confidence value="266885">pA/cm2</confidence>
|
| 399 |
+
or less C: current density in the electric potential range from -600 to +300 mV is more than <part-num-ref name="electric potential range from -600 to +300 mV is more than">100</part-num-ref>
|
| 400 |
+
<confidence value="566885">pA/cm2</confidence>
|
| 401 |
+
<boundary-data type="header">
|
| 402 |
+
<confidence value="88">14</confidence>
|
| 403 |
+
</boundary-data>
|
| 404 |
+
<page-break num="15"/>
|
| 405 |
+
<boundary-data type="header">Atty Dkt No. 016689.00074</boundary-data>
|
| 406 |
+
Table <part-num-ref name="pA/cm2 Table">1</part-num-ref>
|
| 407 |
+
Example Co<confidence value="5">m</confidence>
|
| 408 |
+
parative Example <part-num-ref name="Example Comparative Example">1</part-num-ref>
|
| 409 |
+
<part-num-ref name="">2</part-num-ref>
|
| 410 |
+
<part-num-ref name="">3</part-num-ref>
|
| 411 |
+
<part-num-ref name="">4</part-num-ref>
|
| 412 |
+
<part-num-ref name="">5</part-num-ref>
|
| 413 |
+
<part-num-ref name="">6</part-num-ref>
|
| 414 |
+
<part-num-ref name="">7</part-num-ref>
|
| 415 |
+
<part-num-ref name="">8</part-num-ref>
|
| 416 |
+
<part-num-ref name="">9</part-num-ref>
|
| 417 |
+
<part-num-ref name="">10</part-num-ref>
|
| 418 |
+
<part-num-ref name="">11</part-num-ref>
|
| 419 |
+
<part-num-ref name="">12</part-num-ref>
|
| 420 |
+
<part-num-ref name="">1</part-num-ref>
|
| 421 |
+
<part-num-ref name="">2</part-num-ref>
|
| 422 |
+
<part-num-ref name="">3</part-num-ref>
|
| 423 |
+
<part-num-ref name="">4</part-num-ref>
|
| 424 |
+
<part-num-ref name="">5</part-num-ref>
|
| 425 |
+
<part-num-ref name="">6</part-num-ref>
|
| 426 |
+
Dye <part-num-ref name="Dye">(1)</part-num-ref>
|
| 427 |
+
2.0 - - - - - - - - - - - 2.0 - - - - - Dye <part-num-ref name="2.0 - - - - - - - - - - - 2.0 - - - - - Dye">(2)</part-num-ref>
|
| 428 |
+
- 3.0 - - - - - - - - - - - 3.0 - - - - Dye <part-num-ref name="- 3.0 - - - - - - - - - - - 3.0 - - - - Dye">(3)</part-num-ref>
|
| 429 |
+
- - 3.5 - - - - - - - - - - - 3.5 - - - Dye <part-num-ref name="- - 3.5 - - - - - - - - - - - 3.5 - - - Dye">(4)</part-num-ref>
|
| 430 |
+
- - - 4.0 - - - - - - - - - - - 4.0 - - Dye <part-num-ref name="- - - 4.0 - - - - - - - - - - - 4.0 - - Dye">(5)</part-num-ref>
|
| 431 |
+
- - - - 3.0 - - - - - - - - - - - 3.0 - <confidence value="88">C.</confidence>
|
| 432 |
+
<confidence value="5">.</confidence>
|
| 433 |
+
Direct Blue <part-num-ref name="- - - - 3.0 - - - - - - - - - - - 3.0 - C. . Direct Blue">
|
| 434 |
+
<confidence value="6">1</confidence>
|
| 435 |
+
99 </part-num-ref>
|
| 436 |
+
- - - - - 3.0 3.0 3.0 3.0 - - - - - - - - 3.0 <confidence value="8825">C.I.</confidence>
|
| 437 |
+
DirectBlue86 - - - - - - - - - 3.0 - - - - - - - - <boundary-data type="line-number">
|
| 438 |
+
<confidence value="1">3</confidence>
|
| 439 |
+
</boundary-data>
|
| 440 |
+
<confidence value="8825">C.I.</confidence>
|
| 441 |
+
ReactiveRed23 - - - - - - - - - - 2.0 - - - - - - - <confidence value="1">o</confidence>
|
| 442 |
+
C. <confidence value="22">L.</confidence>
|
| 443 |
+
Pigment Blue<confidence value="22">20</confidence>
|
| 444 |
+
<confidence value="2">C</confidence>
|
| 445 |
+
<confidence value="222">IPg</confidence>
|
| 446 |
+
<confidence value="22">et</confidence>
|
| 447 |
+
<confidence value="22">le</confidence>
|
| 448 |
+
- - - - - - - - - - - 2.0 - - - - - - 15:3 <confidence value="1">o</confidence>
|
| 449 |
+
Sodium <confidence value="255">Soi</confidence>
|
| 450 |
+
<confidence value="22">um</confidence>
|
| 451 |
+
0.5 0.5 0.5 0.5 0.5 0.05 0.1 4.0 5.0 4.0 1.0 1.0 - - - - - - polyitaconate 1,2,3-benzotriazole 0.1 0.1 0.1 0.3 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.3 0.1 - 85% aqueous glycerin solution 27.0 27.0 27.0 27.0 27.0 27.0 27.0 27.0 27.0 27.0 27.0 25.0 27.0 27.0 27.0 27.0 27.0 27.0 <confidence value="2222222222">Diethylene</confidence>
|
| 452 |
+
glycol <confidence value="666">6.0</confidence>
|
| 453 |
+
<confidence value="666">6.0</confidence>
|
| 454 |
+
<confidence value="666">6.0</confidence>
|
| 455 |
+
<confidence value="666">6.0</confidence>
|
| 456 |
+
<confidence value="666">6.0</confidence>
|
| 457 |
+
<confidence value="666">6.0</confidence>
|
| 458 |
+
<confidence value="666">6.0</confidence>
|
| 459 |
+
<confidence value="666">6.0</confidence>
|
| 460 |
+
<confidence value="666">6.0</confidence>
|
| 461 |
+
<confidence value="666">6.0</confidence>
|
| 462 |
+
<confidence value="666">6.0</confidence>
|
| 463 |
+
<confidence value="666">6.0</confidence>
|
| 464 |
+
<confidence value="666">6.0</confidence>
|
| 465 |
+
<confidence value="666">6.0</confidence>
|
| 466 |
+
<confidence value="666">6.0</confidence>
|
| 467 |
+
<confidence value="666">6.0</confidence>
|
| 468 |
+
<confidence value="666">6.0</confidence>
|
| 469 |
+
<confidence value="666">6.0</confidence>
|
| 470 |
+
<confidence value="22222222222">Triethylene</confidence>
|
| 471 |
+
glycol <confidence value="5">3</confidence>
|
| 472 |
+
.0 <confidence value="5">3</confidence>
|
| 473 |
+
.0 <confidence value="5">3</confidence>
|
| 474 |
+
.0 <confidence value="5">3</confidence>
|
| 475 |
+
.0 <confidence value="5">3</confidence>
|
| 476 |
+
.0 <confidence value="5">3</confidence>
|
| 477 |
+
.0 <confidence value="5">3</confidence>
|
| 478 |
+
.0 <confidence value="5">3</confidence>
|
| 479 |
+
.0 <confidence value="5">3</confidence>
|
| 480 |
+
.0 <confidence value="5">3</confidence>
|
| 481 |
+
.0 <confidence value="5">3</confidence>
|
| 482 |
+
.0 <confidence value="5">3</confidence>
|
| 483 |
+
.0 <confidence value="5">3</confidence>
|
| 484 |
+
.0 <confidence value="5">3</confidence>
|
| 485 |
+
.0 <confidence value="5">3</confidence>
|
| 486 |
+
.0 <confidence value="5">3</confidence>
|
| 487 |
+
.0 <confidence value="5">3</confidence>
|
| 488 |
+
.0 <confidence value="588">3.0</confidence>
|
| 489 |
+
butyl ether Proxel GXL(S)<confidence value="21">*'</confidence>
|
| 490 |
+
0.2 0.2 0.2 0.2 0.2 0.2 0.2 0.2 0.2 0.2 0.2 0.2 0.2 0.2 0.2 0.2 0.2 0.2 Purified water Bal. Bal. Bal. Bal. Bal. Bal. Bal. Bal. Bal. Bal. Bal. Bal. Bal. Bal. Bal. Bal. Bal. Bal. </p>
|
| 491 |
+
<p id="p-67" num="67">Ink ejection A A A B A B A A B A A A C C C D C C Evalua- performance test tion Filtration evaluation A A A B A B A A A A A A C C C D C A <confidence value="26666">1test</confidence>
|
| 492 |
+
<boundary-data type="header">
|
| 493 |
+
<confidence value="88">15</confidence>
|
| 494 |
+
</boundary-data>
|
| 495 |
+
<page-break num="16"/>
|
| 496 |
+
<boundary-data type="header">Atty Dkt No. 016689.00074</boundary-data>
|
| 497 |
+
Anodic <confidence value="6">I</confidence>
|
| 498 |
+
ron-nickel A A A A A A A A A A A A A A A A A C polari- alloy zation Nickel A A A A A A A A A A A A A A A A A C test <confidence value="8">*</confidence>
|
| 499 |
+
1: Aqueous dipropylene glycol solution containing 1,2-benzisothiazolin-3-one <part-num-ref name="C test *1: Aqueous dipropylene glycol solution containing 1,2-benzisothiazolin-3-one">(20</part-num-ref>
|
| 500 |
+
wt%) produced by Arch Chemicals Japan, Inc. </p>
|
| 501 |
+
<boundary-data type="header">
|
| 502 |
+
<confidence value="88">16</confidence>
|
| 503 |
+
</boundary-data>
|
| 504 |
+
<boundary-data type="header">Atty Dkt No. 016689.00074</boundary-data>
|
| 505 |
+
<p id="p-68" num="68">
|
| 506 |
+
<page-break num="17"/>
|
| 507 |
+
Table 2 Electrode Type Name Maker Size L(mm)xW(mm)<confidence value="5">x</confidence>
|
| 508 |
+
T(mm) Reference Silver/silver Reference <confidence value="8885888">DKK-TOA</confidence>
|
| 509 |
+
electrode chloride <confidence value="515666">H5205C</confidence>
|
| 510 |
+
Corp. </p>
|
| 511 |
+
<p id="p-69" num="69">Counter Pure Tanaka <confidence value="52666">elect</confidence>
|
| 512 |
+
Platinum platinum Kikinzoku 40x2<confidence value="68685">0x0.1</confidence>
|
| 513 |
+
plate Kogyo K.K. </p>
|
| 514 |
+
<p id="p-70" num="70">Iron-nickel Yamaha <confidence value="252">ron</confidence>
|
| 515 |
+
42 alloy Me<confidence value="66666">tanic</confidence>
|
| 516 |
+
s 4<confidence value="68868688">0x10x0.1</confidence>
|
| 517 |
+
<confidence value="2222222222">Workialloy</confidence>
|
| 518 |
+
Corporation electrode Pure nickel <confidence value="22222222">electrod</confidence>
|
| 519 |
+
(Ni) for <part-num-ref name="alloy Metanics 40x10x0.1 Workialloy Corporation electrode Pure nickel electrod (Ni) for">
|
| 520 |
+
<confidence value="11111">4010.</confidence>
|
| 521 |
+
</part-num-ref>
|
| 522 |
+
</p>
|
| 523 |
+
<p id="p-71" num="71">Nickel industr<confidence value="8">i</confidence>
|
| 524 |
+
al <confidence value="6">-</confidence>
|
| 525 |
+
use [47] As evident from Table 1, the ink in each of Examples <part-num-ref name="ink in each of Examples">
|
| 526 |
+
<confidence value="5">1</confidence>
|
| 527 |
+
</part-num-ref>
|
| 528 |
+
to <part-num-ref name="to">12</part-num-ref>
|
| 529 |
+
provided excellent ink ejection performance results (the number of pins showing any dropout or any ejection curvature was small) compared with the inks of Comparative Examples <part-num-ref name="inks of Comparative Examples">1</part-num-ref>
|
| 530 |
+
to <part-num-ref name="to">6.</part-num-ref>
|
| 531 |
+
The inks of each of Examples <part-num-ref name="inks of each of Examples">1</part-num-ref>
|
| 532 |
+
to <part-num-ref name="to">12</part-num-ref>
|
| 533 |
+
also were excellent in the filtration evaluation test result (the quantity of each of the water-based inks which have passed through the membrane filter was large), and further excellent in the anodic polarization evaluation result (the current density at the time the electric potential was continuously changed within an electric potential range of from -600 to +300 mV was low). </p>
|
| 534 |
+
<p id="p-72" num="72">[48] The invention is not limited to the embodiments described in the Examples, which are provided for illustrative purposes only. It will be apparent that various modifications can be made without departing from the spirit and the scope of the invention as described and claimed herein.</p>
|
| 535 |
+
<boundary-data type="header">
|
| 536 |
+
<confidence value="88">17</confidence>
|
| 537 |
+
</boundary-data>
|
| 538 |
+
</description>
|
| 539 |
+
</us-patent-application>
|
| 540 |
+
|
applicant/11706040.xml
ADDED
|
@@ -0,0 +1,336 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>11706040</doc-number>
|
| 8 |
+
<date>2007-02-12</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<boundary-data type="header">
|
| 14 |
+
<confidence value="8866">ADOO</confidence>
|
| 15 |
+
7-002(B423) </boundary-data>
|
| 16 |
+
<p id="p-1" num="1">Patent Application Chapin Intellectual Property Law LLC/BWC/RVF Certificate of Ex<confidence value="5">p</confidence>
|
| 17 |
+
ress Mailin<confidence value="5">g</confidence>
|
| 18 |
+
Under 37 C.F.R. <confidence value="4">4</confidence>
|
| 19 |
+
1.10 <confidence value="4">I</confidence>
|
| 20 |
+
hereby certify that this correspondence is being deposited with the United States Postal Service with sufficient postage as Express Mail in an envelope addressed to Commissioner for Patents, P<confidence value="5">O</confidence>
|
| 21 |
+
Box <part-num-ref name="envelope addressed to Commissioner for Patents, PO Box">1450,</part-num-ref>
|
| 22 |
+
Alexandria, VA 22313-1450: </p>
|
| 23 |
+
<p id="p-2" num="2">Date: February 12, Mailing Label No.: EV 832 <part-num-ref name="">579</part-num-ref>
|
| 24 |
+
089 US Signature: </p>
|
| 25 |
+
<p id="p-3" num="3">Typed or Printed Name: Penny A. oe o Inventors: Geoffrey King Baum, Lalit Balchandani and Daniel Ha<confidence value="5">i</confidence>
|
| 26 |
+
Attorney Docket No.: AD<confidence value="54">O0</confidence>
|
| 27 |
+
7-002(B423) </p>
|
| 28 |
+
<heading id="h-1">METHODS AND APPARATUS FOR PROCESSING EDITS TO ONLINE VIDEO</heading>
|
| 29 |
+
<heading id="h-2">BACKGROUND</heading>
|
| 30 |
+
<p id="p-4" num="4">Conventional desktop software applications operate on computer systems to allow for users, known as film or video editors, to edit digital video content. In particular, non-linear editing is a non-destructive editing method that involves being able to access any frame in a video clip with the same ease as any other. Initially, video and audio data from a media source file can be digitized and recorded directly to a storage device that is local to the computer system, like a desktop personal computer. The media source file can then be edited on the computer using any of a wide range of video editing software. Example edits that can be made to the video include splicing video segments together, applying effects to video, adding subtitles, and the like.</p>
|
| 31 |
+
<boundary-data type="header">
|
| 32 |
+
<confidence value="5">1</confidence>
|
| 33 |
+
</boundary-data>
|
| 34 |
+
<boundary-data type="header">
|
| 35 |
+
<confidence value="8854">ADO0</confidence>
|
| 36 |
+
7-002(<confidence value="5">B</confidence>
|
| 37 |
+
423) </boundary-data>
|
| 38 |
+
<heading id="h-3">SUMMARY</heading>
|
| 39 |
+
<p id="p-5" num="5">
|
| 40 |
+
<page-break num="2"/>
|
| 41 |
+
In conventional non-linear editing, the media source file is not lost or modified during editing. Instead, during the edit process, the conventional desktop software records the decisions of the film editor to create an Edit Decision List. An Edit Decision List is a way of representing a video edit. It can contain an ordered list of reel and timecode data representing how to manipulate the locally stored media source file in order to properly render the edited video. In other words, the Edit Decision List can describe the editing steps the conventional desktop software application must perform on the locally stored media source file in order to completely generate and store a complete full version of the edited video file prior to playing the edited video. Many generations and variations of the locally stored media source file can exist in storage by creating and storing different Edit Decisions Lists. An Edit Decision List also makes it easy to change, delete and undo previous decisions simply by changing parts of the Edit Decision List. Compared to the linear method of tape-to-tape editing, non-linear editing offers the flexibility of film editing coupled with random access and easy project organization. </p>
|
| 42 |
+
<p id="p-6" num="6">Conventional techniques for non-linear editing suffer from a variety of deficiencies <confidence value="5">I</confidence>
|
| 43 |
+
n particular, conventional techniques that provide non-linear editing incur rendering and processing costs associated with rendering the edited video file via executing the Edit Decision List upon the locally stored media source file to produce a new edited version of the video. In addition, file storage costs are also incurred as such conventional techniques do not operate in a hosted or online (e.g. networked) environment but are rather desktop applications that edit local video sources. That is, the media source file, the file for the fully-rendered edited video and the Edit Decision List must all reside on the same desktop computer system. Another deficiency involves sharing the fully-rendered edited video. In conventional systems, the film editor must completely render an entire edited video file before sharing it with an associate. If the video editor wants to preview a number of edit options for a single media source file, then he is required to fully render and share an edited video file for each option. That is, using conventional edit decision lists, to watch or render the edited video, the video <boundary-data type="header">
|
| 44 |
+
<confidence value="8">2</confidence>
|
| 45 |
+
</boundary-data>
|
| 46 |
+
<page-break num="3"/>
|
| 47 |
+
<boundary-data type="header">
|
| 48 |
+
<confidence value="8844">ADO0</confidence>
|
| 49 |
+
7-002(<confidence value="5">B</confidence>
|
| 50 |
+
423) </boundary-data>
|
| 51 |
+
editing software first produces and stores a secondary copy of the original video that includes the edits from the edit decision list. This secondary copy is then played for the viewing user. One problem with this is that the secondary copy consumes significant storage. </p>
|
| 52 |
+
<p id="p-7" num="7">Embodiments disclosed herein significantly overcome such deficiencies and provide mechanisms and techniques that allow for real-time edit decision list execution on streaming video to play back an edited video in an online environment without having to produce and store (for playback) a full version of the edited video. In particular, such embodiments can be implemented without requiring creation of a fully-rendered (or renderable) file of the edited video. Additionally, the system disclosed herein operates over a network to allow a user to create an edit decision list that defines and descrbes edits to be made to an original or source set of video(s). The edit decision list can then be shared with others via a network server such as a web server, and no version of the edited video needs to be stored. For example, upon request, a client can receive (i.e.</p>
|
| 53 |
+
<p id="p-8" num="8">can request and obtain) an edit decision list from a server system, that is related to a digital media presentation. The edit decision list can be an XML-based text file that contains instructions and information for a client and server as to video edits, video sequencing, file layering and audio data that can be applied to media base data (i.e. the original video) to ultimately present an edited version of the original video to the user.</p>
|
| 54 |
+
<p id="p-9" num="9">The system never needs to persistently store the edited version (the digital media presentation), but only needs to have the original unedited video, and the edit decision list that indicates what edits are to be made, in real-time, to the original video to reproduce the edited version during real time application of the edit decision list to the original video. The digital media presentation thus represents application of the edit decision list to parts of media base data that are rendered in real-time and thus never exists in its complete form in persistent storage. The edit decision list can be a hyperlink or include many hyperlinks to resources (e.g. such as video clips, editing effects, and the like) that reside on a network such as the Internet. In addition to the edit decision list, the user can also receive a media effects set that can include effects, graphics and transitions that can be applied to the media base data. Both the edit <boundary-data type="header">
|
| 55 |
+
<confidence value="8">3</confidence>
|
| 56 |
+
</boundary-data>
|
| 57 |
+
<page-break num="4"/>
|
| 58 |
+
<boundary-data type="header">
|
| 59 |
+
<confidence value="8866">ADOO</confidence>
|
| 60 |
+
7-002(B423) </boundary-data>
|
| 61 |
+
decision list and media effects set can be forwarded to the user via application programming interfaces that operate between a client such as a web browser equipped with an editing and video playback process and the server. </p>
|
| 62 |
+
<p id="p-10" num="10">The edit decision list can be interprested by the client or can be sent to the server to instruct the server to stream media base data to the client-user. The media base data can be an aggregate of individual video, audio, and graphics files stitched together into a continuous video as defined by the edits encoded into the edit decision list. Such files can each reside at universal resource locators (U.R.<confidence value="66">L)</confidence>
|
| 63 |
+
. within an asset management system (e.g., digital library) related to the server or even throughout many different computer systems on the Internet. Hence, the edit decision list can instruct the server to locate and to collect video, audio, and graphics files and to further sequence and layer the files accordingly. </p>
|
| 64 |
+
<p id="p-11" num="11">As the media base data, such as a stitched continuous video, gets streamed to the client-user, it is received and processed at a player local to the client in order to present the video in an edited version. However, no actual file of this edited version is required to be fully rendered, constructed and saved at the client. Instead, both the edit decision list and media effects set are executed in real-time upon the streaming media base data. The media base data is thus the original video and the client player obtains the edit decision list and "executes" the edit instuctions contained therein upon the media base data. Segments of the edit decision list may be sent to the server of the media base data and the server can determine the order at which to serve which segments of the media base data. Therefore, performance, storage and rendering costs are substantially lowered because the edited video is presented by executing the edit decision list and media effects set with the streaming media base data. Because such execution occurs in real-time, there is no requirement to transcode the edited video at the end of an editing session and to store files (i.e. a single new edited file) that are edited versions of the media base data.</p>
|
| 65 |
+
<p id="p-12" num="12">More specifically, embodiments disclosed herein provide for an online media player that can request a digital media presentation from at least one server. A client can receive an edit decision list and a media effects set from the server, where the edit <boundary-data type="header">
|
| 66 |
+
<confidence value="8">4</confidence>
|
| 67 |
+
</boundary-data>
|
| 68 |
+
<page-break num="5"/>
|
| 69 |
+
<boundary-data type="header">
|
| 70 |
+
<confidence value="8866">ADOO</confidence>
|
| 71 |
+
7-002(<confidence value="5">B</confidence>
|
| 72 |
+
423) </boundary-data>
|
| 73 |
+
decision list and the media effects set (e.g. media effects) are associated with the digital media presentation. The online media player allows for the server to stream media base data, associated with the digital media presentation, from the server to the client. </p>
|
| 74 |
+
<p id="p-13" num="13">The client executes the edit decision list and the media effects set upon the streaming media base data in real-time to play the digital media presentation. Hence, the edit decision list can instruct both the client and server to perform appropriate edits at certain times upon the media base data as it is streaming.</p>
|
| 75 |
+
<p id="p-14" num="14">Other embodiments disclosed herein include any type of computerized device, workstation, handheld or laptop computer, or the like configured with software and/or circuitry (e.g., a processor) to process any or all of the method operations disclosed herein. In other words, a computerized device such as a computer or a data communications device or any type of processor that is programmed or configured to operate as explained herein is considered an embodiment disclosed herein. Other embodiments disclosed herein include software programs to perform the steps and operations summarized above and disclosed in detail below. One such embodiment comprises a computer program product that has a computer-readable medium including computer program logic encoded thereon that, when performed in a computerized device having a coupling of a memory and a processor, programs the processor to perform the operations disclosed herein. Such arrangements are typically provided as software, code and/or other data (e.g., data structures) arranged or encoded on a computer readable medium such as an optical medium (e.g., CD-ROM), floppy or hard disk or other a medium such as firmware or microcode in one or more ROM or RAM or PROM chips or as an Application Specific Integrated Circuit (ASIC). The software or firmware or other such configurations can be installed onto a computerized device to cause the computerized device to perform the techniques explained as embodiments disclosed herein.</p>
|
| 76 |
+
<p id="p-15" num="15">It is to be understood that the system disclosed herein may be embodied strictly as a software program, as software and hardware, or as hardware alone. The embodiments disclosed herein, may be employed in data communications devices and other computerized devices and software systems for such devices such as those <boundary-data type="header">
|
| 77 |
+
<confidence value="8">5</confidence>
|
| 78 |
+
</boundary-data>
|
| 79 |
+
<page-break num="6"/>
|
| 80 |
+
<boundary-data type="header">
|
| 81 |
+
<confidence value="8866">ADOO</confidence>
|
| 82 |
+
7-002(<confidence value="5">B</confidence>
|
| 83 |
+
423) </boundary-data>
|
| 84 |
+
manufactured by Adobe Systems Incorporated of San Jose, California, U.S.A., herein after referred to as "Adobe" and "Adobe Systems." </p>
|
| 85 |
+
<heading id="h-4">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
|
| 86 |
+
<p id="p-16" num="16">The foregoing and other objects, features and advantages of the invention will be apparent from the following more particular description of embodiments of the methods and apparatus for executing an edit decision list and a media effects set on streaming media base data, as illustrated in the accompanying drawings and figures in which like reference characters refer to the same parts throughout the different views. The drawings are not necessarily to scale, with emphasis instead being placed upon illustrating the embodiments, principles and concepts of the methods and apparatus in accordance with the invention.</p>
|
| 87 |
+
<p id="p-17" num="17">Figure 1 is a block diagram of a computerized system configured with an application including an online media player in accordance with one embodiment of the invention.</p>
|
| 88 |
+
<p id="p-18" num="18">Figure 2 is another block diagram of an online media player implemented via a computer network system in accordance with one embodiment of the invention.</p>
|
| 89 |
+
<p id="p-19" num="19">Figure 3 is a flow chart of processing steps that show high-level processing operations performed by an online media player to execute an edit decision list and a media effects set upon streaming media base data in real-time to play a digital media presentation.</p>
|
| 90 |
+
<p id="p-20" num="20">Figure 4 is a flow chart of processing steps that show high-level processing operations performed by an online media player to receive an edit decision list from a server.</p>
|
| 91 |
+
<p id="p-21" num="21">Figure 5 is a flow chart of processing steps that show high-level processing operations performed by an online media player to receive a media effects set from a server.</p>
|
| 92 |
+
<p id="p-22" num="22">Figure 6 is a flow chart of processing steps that show high-level processing operations performed by an online media player to stream media base data from a server.</p>
|
| 93 |
+
<boundary-data type="header">
|
| 94 |
+
<confidence value="8">6</confidence>
|
| 95 |
+
</boundary-data>
|
| 96 |
+
<boundary-data type="header">
|
| 97 |
+
<confidence value="8854">ADO0</confidence>
|
| 98 |
+
7-002(<confidence value="5">B</confidence>
|
| 99 |
+
423) </boundary-data>
|
| 100 |
+
<p id="p-23" num="23">
|
| 101 |
+
<page-break num="7"/>
|
| 102 |
+
Figure 7 is a flow chart of processing steps that show high-level processing operations performed by an online media player to aggregate at least one of a video base file, a image base file and an audio base file. </p>
|
| 103 |
+
<p id="p-24" num="24">Figure 8 is a flow chart of processing steps that show high-level processing operations performed by an online media player to request a digital media presentation from a server.</p>
|
| 104 |
+
<heading id="h-5">DETAILED DESCRIPTION</heading>
|
| 105 |
+
<p id="p-25" num="25">Embodiments disclosed herein include methods, software and a computer system that provides an online rich media player, such as a Flash Player for example, that allows for real-time execution or application of an edit decision list on streaming video to play back an edited version of the original video in an online environment without requiring storage of the edited version. The system disclosed herein can be utilized within a rich media player and server such as a Flash Player and Flash Media Sever which are software products made by Adobe Systems Incorporated of San Jose, CA, USA. Using the system disclosed herein, when original video content (referred to herein as media base data) is edited, enhanced or remixed, such edits don't modify the media base data. Instead, all edits or changes made are be saved in an XML-based text file as an edit decision list that is associated with the media base data used in the editing session. After the edit decision list has been saved, an online user can operate the client (e.g. rich media player) to request the edited version of the video. As an example, the user may operate a web browser equipped with a rich media player plugin, such as a Flash plugin. When visiting a web site containing video content, the user may select a video for playback within that user's browser via the Flash player.</p>
|
| 106 |
+
<p id="p-26" num="26">Upon such a request, instead of obtaining an edited verison of video, the rich media player requests and can receive the edit decision list from a server system operating a rich media server (such as the Flash media server). The edit decision list is related to a digital media presentation (i.e. the requested video along with the edits applied). The edit decision list contains instructions and information for a client (e.g.</p>
|
| 107 |
+
<p id="p-27" num="27">Flash player) and server (e.g. Flash media server) as to video edits, video sequencing, <boundary-data type="header">
|
| 108 |
+
<confidence value="8">7</confidence>
|
| 109 |
+
</boundary-data>
|
| 110 |
+
<page-break num="8"/>
|
| 111 |
+
<boundary-data type="header">
|
| 112 |
+
<confidence value="8866">ADOO</confidence>
|
| 113 |
+
7-002(B423) </boundary-data>
|
| 114 |
+
file layering and audio data that can be applied to media base data (e.g. original unedited video) in order to ultimately present an edited presentation of the original video to the user. The edit decision list can include many hyperlinks to media resources (e.g. </p>
|
| 115 |
+
<p id="p-28" num="28">media server and specific media bases data) that reside on a network such as the Internet. In addition to the edit decision list, the client's rich media player can also receive a media effects set that can include effects, graphics and transitions that can be applied to the media base data. Both the edit decision list and media effects set can be requested and received by the client (e.g. flash player or other rich media player) via application programming interfaces related to the server. In some embodiments, once the client has received the edit decision list, portions of the edit decision list may be sent to the server to allow the server to assemble and stream the base media data back to the client.</p>
|
| 116 |
+
<p id="p-29" num="29">The edit decision list can thus instruct the server to stream media base data to the client. The media base data can be an aggregate of individual video, audio, and graphics files stitched together into a continuous video. Such files can each reside at universal resource locators (U.R.<confidence value="66">L)</confidence>
|
| 117 |
+
. within an asset management system (e.g., digital library) accessible by the server throughout the Internet. Hence, the edit decision list can instruct the server to locate, collect and stream video, audio, and graphics files and to further sequence and layer the files accordingly. </p>
|
| 118 |
+
<p id="p-30" num="30">As the media base data, such as a stitched continuous video, gets streamed to the client-user, it is received and processed at a rich media player local to the client in order to present the video in an edited version. However, no actual file of this edited version is required to be fully rendered and saved at the client or server. Instead, both the edit decision list and media effects set are executed or applied in real-time upon the streaming media base data. Therefore, performance, storage and rendering costs are substantially lowered because the edited video is presented by combining the edit decision list and media effects set with the streaming media base data. Since this occurs in real-time, there is no requirement to transcode the edited video at the end of an editing session and to store files that are edited versions of the media base data.</p>
|
| 119 |
+
<boundary-data type="header">
|
| 120 |
+
<confidence value="8">8</confidence>
|
| 121 |
+
</boundary-data>
|
| 122 |
+
<boundary-data type="header">
|
| 123 |
+
<confidence value="8866">ADOO</confidence>
|
| 124 |
+
7-002(<confidence value="5">B</confidence>
|
| 125 |
+
423) </boundary-data>
|
| 126 |
+
<p id="p-31" num="31">
|
| 127 |
+
<page-break num="9"/>
|
| 128 |
+
FIG. 1 is a block diagram illustrating example architecture of a computer system <part-num-ref name="computer system">110</part-num-ref>
|
| 129 |
+
that executes, runs, interprets, operates or otherwise performs a online media player application 150-1 (e.g., a rich media player such as a Flash Player) and online media player process 150-2 (e.g. an executing version of the application 150-1 controlled by user <part-num-ref name="application 150-1 controlled by user">108)</part-num-ref>
|
| 130 |
+
configured in accordance with embodiments of the invention to produce, in real-time, a rendered edited video <part-num-ref name="rendered edited video">160.</part-num-ref>
|
| 131 |
+
The computer system <part-num-ref name="computer system">110</part-num-ref>
|
| 132 |
+
may be any type of computerized device such as a personal computer, workstation, portable computing device, console, laptop, network terminal or the like. As shown in this example, the computer system <part-num-ref name="computer system">110</part-num-ref>
|
| 133 |
+
includes an interconnection mechanism <part-num-ref name="interconnection mechanism">111</part-num-ref>
|
| 134 |
+
such as a data bus, motherboard or other circuitry that couples a memory system <part-num-ref name="memory system">112,</part-num-ref>
|
| 135 |
+
a processor <part-num-ref name="processor">113,</part-num-ref>
|
| 136 |
+
an input/output interface <part-num-ref name="input/output interface">114,</part-num-ref>
|
| 137 |
+
and a communications interface <part-num-ref name="communications interface">115</part-num-ref>
|
| 138 |
+
that can interact with a network <part-num-ref name="network">220</part-num-ref>
|
| 139 |
+
to receive streaming media data from a server that can also implement aspects of the online rich media player application 150-1 and process 150-2. An input device <part-num-ref name="input device">116</part-num-ref>
|
| 140 |
+
(e.g., one or more user/developer controlled devices such as a keyboard, mouse, touch pad, etc.) couples to the computer system <part-num-ref name="computer system">110</part-num-ref>
|
| 141 |
+
and processor <part-num-ref name="and processor">113</part-num-ref>
|
| 142 |
+
through an input / output (<confidence value="686">1/0</confidence>
|
| 143 |
+
) interface <part-num-ref name="input / output (1/0) interface">114.</part-num-ref>
|
| 144 |
+
</p>
|
| 145 |
+
<p id="p-32" num="32">The memory system 112 is any type of computer readable medium and in this example is encoded with an online media player application 150-1 that supports generation, display, and implementation of functional operations as explained herein.</p>
|
| 146 |
+
<p id="p-33" num="33">During operation of the computer system <part-num-ref name="computer system">110,</part-num-ref>
|
| 147 |
+
the processor <part-num-ref name="processor">113</part-num-ref>
|
| 148 |
+
accesses the memory system <part-num-ref name="memory system">112</part-num-ref>
|
| 149 |
+
via the interconnect <part-num-ref name="interconnect">111</part-num-ref>
|
| 150 |
+
in order to launch, run, execute, interpret or otherwise perform the logic instructions of the online media player application 150-1. </p>
|
| 151 |
+
<p id="p-34" num="34">Execution of the online media player application 150-1 in this manner produces processing functionality in a online media player process 150-2. In other words, the process 150-2 represents one or more portions or runtime instances of the application 150-1 (or the entire application 150-1) performing or executing within or upon the processor <part-num-ref name="processor">113</part-num-ref>
|
| 152 |
+
in the computerized device <part-num-ref name="computerized device">110</part-num-ref>
|
| 153 |
+
at runtime. </p>
|
| 154 |
+
<p id="p-35" num="35">Further details of configurations explained herein will now be provided with respect to flow charts of processing steps that show the high level operations disclosed herein to perform the online media player process 150-2, as well as graphical <boundary-data type="header">
|
| 155 |
+
<confidence value="8">9</confidence>
|
| 156 |
+
</boundary-data>
|
| 157 |
+
<page-break num="10"/>
|
| 158 |
+
<boundary-data type="header">
|
| 159 |
+
<confidence value="8855">AD00</confidence>
|
| 160 |
+
7-002(<confidence value="5">B</confidence>
|
| 161 |
+
423) </boundary-data>
|
| 162 |
+
representations that illustrate implementations of the various configurations of the online media player process 150-2. </p>
|
| 163 |
+
<p id="p-36" num="36">FIG. 2 is another block diagram of an online media player <part-num-ref name="online media player">150</part-num-ref>
|
| 164 |
+
such as a Flash Player or other rich media player (or video or other media player <confidence value="5">/</confidence>
|
| 165 |
+
editor combination) implemented via a computer network system in accordance with one embodiment of the invention. A user can utilize the online media player <part-num-ref name="online media player">150</part-num-ref>
|
| 166 |
+
to produce and play a digital media presentation. For example, the user can control the online media player <part-num-ref name="online media player">150</part-num-ref>
|
| 167 |
+
to access the server's asset management system <part-num-ref name="server's asset management system">225</part-num-ref>
|
| 168 |
+
to select two individual video clips (e.g. base media data 335). Using the online media player <part-num-ref name="online media player">150,</part-num-ref>
|
| 169 |
+
the user can sequence the two video clips into one continuous video. Further, the user can add an opening title screen with a transition to the initial frame of the edited video. Also, the user can add Spanish subtitles throughout the frames of the edited video wherever dialogue occurs. </p>
|
| 170 |
+
<p id="p-37" num="37">Other special effects can be inserted as well. For instance, a few video frames can be converted to 'black-and-white<confidence value="5">,</confidence>
|
| 171 |
+
' and some frames can be enhanced with audio effects. </p>
|
| 172 |
+
<p id="p-38" num="38">As all such edits, effects, and enhancements are selected and applied, the online media player <part-num-ref name="online media player">150</part-num-ref>
|
| 173 |
+
creates an edit decision list <part-num-ref name="edit decision list">336</part-num-ref>
|
| 174 |
+
and a media effects set <part-num-ref name="media effects set">334</part-num-ref>
|
| 175 |
+
that are stored by the server <part-num-ref name="server">210</part-num-ref>
|
| 176 |
+
within an asset management system <part-num-ref name="asset management system">225.</part-num-ref>
|
| 177 |
+
As an example, the edit decision list <part-num-ref name="edit decision list">336</part-num-ref>
|
| 178 |
+
can represent the sequencing of the two individual video clips <part-num-ref name="two individual video clips">335</part-num-ref>
|
| 179 |
+
and the title screen. The edit decision list <part-num-ref name="edit decision list">336</part-num-ref>
|
| 180 |
+
can also include indications of where certain effects and enhancements need to occur. The media effects set <part-num-ref name="media effects set">334</part-num-ref>
|
| 181 |
+
contains effects to create the text of the title, the Spanish subtitles, the audio effects, and the 'black-and-white' frame effects. The edit decision list and the media effects set can be stored at the server <part-num-ref name="server">210</part-num-ref>
|
| 182 |
+
and the asset management system <part-num-ref name="asset management system">225</part-num-ref>
|
| 183 |
+
for future access and for sharing among other users. No actual file for the edited video is fully-rendered or stored prior to playing the edited video. The "edited" video is thus a combination of the edit decision list <part-num-ref name="edit decision list">336</part-num-ref>
|
| 184 |
+
and the available original base media data <part-num-ref name="available original base media data">335</part-num-ref>
|
| 185 |
+
that the client player <part-num-ref name="client player">150</part-num-ref>
|
| 186 |
+
and rich media server <part-num-ref name="and rich media server">240</part-num-ref>
|
| 187 |
+
utilize to create, in real-time, an edited rendition of the original base media data (with edits) within the player <part-num-ref name="player">150.</part-num-ref>
|
| 188 |
+
This edited version is never statically stored persistently. </p>
|
| 189 |
+
<boundary-data type="header">
|
| 190 |
+
<confidence value="88">10</confidence>
|
| 191 |
+
</boundary-data>
|
| 192 |
+
<boundary-data type="header">
|
| 193 |
+
<confidence value="8866">ADOO</confidence>
|
| 194 |
+
7-002(<confidence value="5">B</confidence>
|
| 195 |
+
423) </boundary-data>
|
| 196 |
+
<p id="p-39" num="39">
|
| 197 |
+
<page-break num="11"/>
|
| 198 |
+
The user can then share a link to the edited video (i.e. a link to the edit decision list <part-num-ref name="edit decision list">336)</part-num-ref>
|
| 199 |
+
with the other users. Upon activating the link to the "edited video", the server <part-num-ref name="server">210</part-num-ref>
|
| 200 |
+
can send the edit decision list <part-num-ref name="edit decision list">336</part-num-ref>
|
| 201 |
+
and the media effects set <part-num-ref name="media effects set">334</part-num-ref>
|
| 202 |
+
(if required) to a second user operating another client via an application programming interface <part-num-ref name="application programming interface">230,</part-num-ref>
|
| 203 |
+
<part-num-ref name="application programming interface 230,">235</part-num-ref>
|
| 204 |
+
related to the server <part-num-ref name="server">210.</part-num-ref>
|
| 205 |
+
The edit decision list can send instructions back to the server <part-num-ref name="server">210</part-num-ref>
|
| 206 |
+
to retrieve the two individual video clips previously used in the editing session. The server <part-num-ref name="server">210</part-num-ref>
|
| 207 |
+
searches the asset management system <part-num-ref name="asset management system">225</part-num-ref>
|
| 208 |
+
for the particular video clips and begins streaming the two video clips, via a rich media server such as Flash Media Server <part-num-ref name="rich media server such as Flash Media Server">240,</part-num-ref>
|
| 209 |
+
in a sequence according to instructions of the edit decision list. At the client computer<confidence value="666">110</confidence>
|
| 210 |
+
, a Flash Player <part-num-ref name="Flash Player">150</part-num-ref>
|
| 211 |
+
interacts with (e.g. interprets) the edit decision list <part-num-ref name="edit decision list">336</part-num-ref>
|
| 212 |
+
and the media effects set as it receives the properly-sequenced video from the server <part-num-ref name="server">210</part-num-ref>
|
| 213 |
+
to apply edits and media effects in real-time to the incoming streaming video (base media data 335). Thus, it is understood that various processing of the online media player <part-num-ref name="online media player">150,</part-num-ref>
|
| 214 |
+
such as the application 150-1 and process 150-2, can be distributed and implemented between the client <part-num-ref name="client">215</part-num-ref>
|
| 215 |
+
and the server <part-num-ref name="server">210.</part-num-ref>
|
| 216 |
+
Further, the Flash Media Player <part-num-ref name="Flash Media Player">245</part-num-ref>
|
| 217 |
+
can also be part of a browser (or interact with a browser) on the client computer <part-num-ref name="client computer">110.</part-num-ref>
|
| 218 |
+
</p>
|
| 219 |
+
<p id="p-40" num="40">The edit decision list and the media effects set are executed upon the streaming video in real-time. Using the edit decision list, the player <part-num-ref name="player">150</part-num-ref>
|
| 220 |
+
generates the title screen and the transition in proper sequence with the streaming incoming video media base data <part-num-ref name="streaming incoming video media base data">335.</part-num-ref>
|
| 221 |
+
The player <part-num-ref name="player">150</part-num-ref>
|
| 222 |
+
pulls the Spanish subtitles, the audio effects, and the 'black- and-white' effect from the media effects set <part-num-ref name="media effects set">334</part-num-ref>
|
| 223 |
+
and applies such effect at the frames indicated in the edit decision list <part-num-ref name="edit decision list">336.</part-num-ref>
|
| 224 |
+
Thus, the "edited video" created in the editing session by the first user (the editor) is presented to the second user in an online environment in real-time (i.e., the edits are applied as the streaming video arrives and is rendered for the second user) without incurring the storage costs associated with creating a separate stored file of the edited video. </p>
|
| 225 |
+
<p id="p-41" num="41">Turning now to FIG. 3, a flow chart of processing steps 300-303 is presented to show high-level processing operations performed by an online media player <part-num-ref name="online media player">150</part-num-ref>
|
| 226 |
+
such as a Flash Player or other rich media player (or video or other media player <confidence value="5">/</confidence>
|
| 227 |
+
editor <boundary-data type="header">
|
| 228 |
+
<confidence value="88">11</confidence>
|
| 229 |
+
</boundary-data>
|
| 230 |
+
<page-break num="12"/>
|
| 231 |
+
<boundary-data type="header">
|
| 232 |
+
<confidence value="8855">AD00</confidence>
|
| 233 |
+
7-002(<confidence value="5">B</confidence>
|
| 234 |
+
423) </boundary-data>
|
| 235 |
+
combination) to execute an edit decision list and a media effects set upon streaming media base data in real-time to play a digital media presentation. </p>
|
| 236 |
+
<p id="p-42" num="42">In step 300, the online media player <part-num-ref name="online media player">150</part-num-ref>
|
| 237 |
+
requests a digital media presentation from at <confidence value="222222222">least'one</confidence>
|
| 238 |
+
server <part-num-ref name="digital media presentation from at least'one server">210.</part-num-ref>
|
| 239 |
+
For example, a user can click a hyperlink that includes a reference to the digital media presentation. Such a reference can describe an edit decision list <part-num-ref name="edit decision list">336</part-num-ref>
|
| 240 |
+
and a media effects set <part-num-ref name="media effects set">335</part-num-ref>
|
| 241 |
+
to be sent from the server <part-num-ref name="server">210</part-num-ref>
|
| 242 |
+
to the user at a client computer <part-num-ref name="client computer">110.</part-num-ref>
|
| 243 |
+
In step <part-num-ref name="client computer 110. In step">301,</part-num-ref>
|
| 244 |
+
the online media player <part-num-ref name="online media player">150</part-num-ref>
|
| 245 |
+
receives the edit decision list and the media effects set from the server, the edit decision list and the media effects set associated with the digital media presentation. </p>
|
| 246 |
+
<p id="p-43" num="43">In step 302, the online media player <part-num-ref name="online media player">150</part-num-ref>
|
| 247 |
+
streams media base data <part-num-ref name="streams media base data">335</part-num-ref>
|
| 248 |
+
from the server(s), the media base data <part-num-ref name="media base data">335</part-num-ref>
|
| 249 |
+
associated with the digital media presentation. It is understood that streaming media base data can be media (e.g., video files, audio files, graphics files, still image files) that is continuously received by, and normally displayed to, the end-user whilst it is being delivered by a provider. </p>
|
| 250 |
+
<p id="p-44" num="44">In step 303, the online media player <part-num-ref name="online media player">150</part-num-ref>
|
| 251 |
+
executes the edit decision list and the media effects set upon the streaming media base data in real-time to play the digital media presentation. A person having ordinary skill in the art would recognize that real- time can be a level of computer responsiveness that the user senses as sufficiently immediate or that enables the computer to keep in time with some external process, such as media streaming. </p>
|
| 252 |
+
<p id="p-45" num="45">Regarding FIG. 4, a flow chart for processing steps 304-305 shows high-level processing operations performed by an online media player <part-num-ref name="online media player">150</part-num-ref>
|
| 253 |
+
to receive an edit decision list from a server. In step <part-num-ref name="server. In step">304,</part-num-ref>
|
| 254 |
+
the online media player <part-num-ref name="online media player">150</part-num-ref>
|
| 255 |
+
receives an XML- based text file that represents modifications to be applied to the streaming media base data. The modifications represented in the XML-based text file can be all the edits recorded during a previous editing session made to the media base data. Thus, the XML-based text file can act as an instruction set to mimic or recreate the recorded edits from the previous editing session. In step <part-num-ref name="previous editing session. In step">305,</part-num-ref>
|
| 256 |
+
the online media player <part-num-ref name="online media player">150</part-num-ref>
|
| 257 |
+
loads the edit decision list to a Flash Player at a client. It is understood that the entire edit decision list need not be loaded to the Flash Player. Hence, portions of the edit <boundary-data type="header">
|
| 258 |
+
<confidence value="88">12</confidence>
|
| 259 |
+
</boundary-data>
|
| 260 |
+
<page-break num="13"/>
|
| 261 |
+
<boundary-data type="header">
|
| 262 |
+
<confidence value="8866">ADOO</confidence>
|
| 263 |
+
7-002(<confidence value="5">B</confidence>
|
| 264 |
+
423) </boundary-data>
|
| 265 |
+
decision list can be loaded to the Flash Player and other portions of the edit decision list can reside within the client and still interact with the Flash Player or with a browser. The Flash Player is a multimedia and application player created and distributed by Adobe. </p>
|
| 266 |
+
<p id="p-46" num="46">The Flash Player runs SWF files that can be created by the Adobe Flash authoring tool, Adobe Flex or a number of other Adobe and third party tools. Adobe Flash can refer to both a multimedia authoring program and the Flash Player, written and distributed by Adobe, that uses vector and raster graphics, a native scripting language called ActionScript and bidirectional streaming of video and audio. Adobe Flash can also relate to the authoring environment and Flash Player is the virtual machine used to run the Flash files. Thus, "Flash" can mean either the authoring environment, the player, or the application files. It is also noted that the online media player <part-num-ref name="online media player">150</part-num-ref>
|
| 267 |
+
is not limited to using only a Flash Player. </p>
|
| 268 |
+
<p id="p-47" num="47">Referring to FIG. 5, a flow chart of processing steps 306-307 shows high-level processing operations performed by an online media player <part-num-ref name="online media player">150</part-num-ref>
|
| 269 |
+
to receive a media effects set from a server. In step <part-num-ref name="server. In step">306,</part-num-ref>
|
| 270 |
+
the online media player <part-num-ref name="online media player">150</part-num-ref>
|
| 271 |
+
receives at least one of an extensible graphical effect, an extensible video transition effect and an extensible audio effect to be applied to the media base data. A person having ordinary skill in the art would recognize that extensibility is a system design principle where the implementation takes into consideration future modifcation and enhancement. </p>
|
| 272 |
+
<p id="p-48" num="48">Extensions can be through the addition of new functionality or through the modification of existing functionality while minimizing the impact to existing system functions.</p>
|
| 273 |
+
<p id="p-49" num="49">Extensibility can also mean that a system has been so architected that the design includes mechanisms for expanding/enhancing the system with new capabilities without having to make major changes to the system infrastructure. Extensibility can also mean that a software system's behavior is modifiable at runtime, without recompiling or changing the original source code. Thus, an extensible graphical effect from a previous editing session can be automatically updated to a more current version of the graphical effect and included in the media effects set. In step <part-num-ref name="media effects set. In step">307,</part-num-ref>
|
| 274 |
+
the online media player <part-num-ref name="online media player">150</part-num-ref>
|
| 275 |
+
loads the media effects set to the Flash Player at the client. </p>
|
| 276 |
+
<boundary-data type="header">
|
| 277 |
+
<confidence value="88">13</confidence>
|
| 278 |
+
</boundary-data>
|
| 279 |
+
<boundary-data type="header">
|
| 280 |
+
<confidence value="8866">ADOO</confidence>
|
| 281 |
+
7-002(<confidence value="5">B</confidence>
|
| 282 |
+
423) </boundary-data>
|
| 283 |
+
<p id="p-50" num="50">
|
| 284 |
+
<page-break num="14"/>
|
| 285 |
+
According to FIG. 6, a flow chart of processing steps 308-309 illustrates high- level processing operations performed by an online media player <part-num-ref name="online media player">150</part-num-ref>
|
| 286 |
+
to stream media base data from a server. In step <part-num-ref name="server. In step">308,</part-num-ref>
|
| 287 |
+
the online media player <part-num-ref name="online media player">150</part-num-ref>
|
| 288 |
+
requests the media base data from the server according to the edit decision list. For example, the edit decision list can send information to the server regarding which files were previously used to make the digital media presentation. In step <part-num-ref name="digital media presentation. In step">309,</part-num-ref>
|
| 289 |
+
the online media player <part-num-ref name="online media player">150</part-num-ref>
|
| 290 |
+
aggregates at least one of a video base file, an image base file and an audio base file according to the edit decision list in order to generate the media base data. </p>
|
| 291 |
+
<p id="p-51" num="51">Regarding FIG. 7, a flow chart of processing steps 310-312 shows high-level processing operations performed by an online media player <part-num-ref name="online media player">150</part-num-ref>
|
| 292 |
+
to aggregate at least one of a video base file, a image base file and an audio base file. In step <part-num-ref name="audio base file. In step">310,</part-num-ref>
|
| 293 |
+
the online media player <part-num-ref name="online media player">150</part-num-ref>
|
| 294 |
+
collects at least one of the video base file, the image base file and the audio base file from at least one universal resource locator (URL). Any URL on the Internet can be used to locate and collect the files. Specifically, the online media player <part-num-ref name="online media player">150</part-num-ref>
|
| 295 |
+
can execute instructions related to the edit decision list from the server to locate media files and media data from any given URL(s) that can be used for the media base data. In the alternative, such files and data can already be stored in a digital library or digital asset management system related to the server. In step <part-num-ref name="server. In step">311,</part-num-ref>
|
| 296 |
+
the online media player <part-num-ref name="online media player">150</part-num-ref>
|
| 297 |
+
sequences at least one of the video base file, the image base file and the audio base file according to the edit decision list. Thus, the edit decision list can provide the server with information regarding how to order the various video, image, and audio files to make up the media base data. It is also understood that sequencing can include inserting one file at a certain point within another file. In other words, an image file can be sequenced to appear half way into a video file. </p>
|
| 298 |
+
<p id="p-52" num="52">In step 312, the online media player <part-num-ref name="online media player">150</part-num-ref>
|
| 299 |
+
layers at least one of the video base file, the image base file and the audio base file according to the edit decision list. Here, rather than simply sequencing files, the edit decision list can provide the server with information regarding how to further place the files in relation to one another. For example, an audio file can be layered over a video file to stream simultaneously for a certain amount of time. </p>
|
| 300 |
+
<boundary-data type="header">
|
| 301 |
+
<confidence value="88">14</confidence>
|
| 302 |
+
</boundary-data>
|
| 303 |
+
<boundary-data type="header">
|
| 304 |
+
<confidence value="8866">ADOO</confidence>
|
| 305 |
+
7-002(<confidence value="5">B</confidence>
|
| 306 |
+
423) </boundary-data>
|
| 307 |
+
<p id="p-53" num="53">
|
| 308 |
+
<page-break num="15"/>
|
| 309 |
+
In step 313<confidence value="5">,</confidence>
|
| 310 |
+
the online media player <part-num-ref name="online media player">150</part-num-ref>
|
| 311 |
+
includes a Flash Player that receives the streaming media base data from a Flash Media Server. The Flash Media Server is an enterprise-grade data and media server from Adobe Systems Inc. The Flash Media Server can work together with the Flash Player during runtime and streaming to create media driven, multiuser RIA (Rich Internet Applications). </p>
|
| 312 |
+
<p id="p-54" num="54">Referring now to FIG. 8, a flow chart of processing steps 314-316 shows high- level processing operations performed by an online media player <part-num-ref name="online media player">150</part-num-ref>
|
| 313 |
+
to request a digital media presentation from a server. In step <part-num-ref name="server. In step">314,</part-num-ref>
|
| 314 |
+
the online media player <part-num-ref name="online media player">150</part-num-ref>
|
| 315 |
+
transmits a reference to the digital media presentation from the client to the server. In step <part-num-ref name="server. In step">315,</part-num-ref>
|
| 316 |
+
the online media player <part-num-ref name="online media player">150</part-num-ref>
|
| 317 |
+
accesses the edit decision list and the media effects set stored in an asset management system related to the server. Such an asset management system can be utilized for managing content for the web. The asset management system can manage content (text, graphics, links, etc.) for distribution on a web server. Thus, the asset management system can also include software where users can create, edit, store and manage content with relative ease of use. Such an asset management system can use a database, for example, to hold content, and a presentation layer displays the content to regular website visitors based on a set of templates. In step <part-num-ref name="set of templates. In step">316,</part-num-ref>
|
| 318 |
+
the online media player <part-num-ref name="online media player">150</part-num-ref>
|
| 319 |
+
forwards the edit decision list and the media effects set from the asset management system to the client via at least one application programming interface (API) related to the server. </p>
|
| 320 |
+
<p id="p-55" num="55">Note again that techniques herein are well suited to allow for real-time edit decision list execution on streaming video to play back an edited video in an online environment via an online media player. However, it should be noted that the online media player can be part of a software system that provides edit decision list creation capabilities and can be implemented independently. Further, embodiments herein are not limited to use in such applications and that the techniques discussed herein are well suited for other applications as well.</p>
|
| 321 |
+
<p id="p-56" num="56">While this invention has been particularly shown and described with references to preferred embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the <boundary-data type="header">
|
| 322 |
+
<confidence value="88">15</confidence>
|
| 323 |
+
</boundary-data>
|
| 324 |
+
<page-break num="16"/>
|
| 325 |
+
<boundary-data type="header">
|
| 326 |
+
<confidence value="8866">ADOO</confidence>
|
| 327 |
+
7-002(<confidence value="5">B</confidence>
|
| 328 |
+
423) </boundary-data>
|
| 329 |
+
spirit and scope of the present application as defined by the appended claims. Such variations are intended to be covered by the scope of this present application. As such<confidence value="5">,</confidence>
|
| 330 |
+
the foregoing description of embodiments of the present application is not intended to be limiting. Rather, any limitations to the invention are presented in the following claims. </p>
|
| 331 |
+
<boundary-data type="header">
|
| 332 |
+
<confidence value="88">16</confidence>
|
| 333 |
+
</boundary-data>
|
| 334 |
+
</description>
|
| 335 |
+
</us-patent-application>
|
| 336 |
+
|
applicant/11719508.xml
ADDED
|
@@ -0,0 +1,31 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US" file="11719508.2012-11-02.H91KWIWSPXXIFW3.SPEC.XML">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>11719508</doc-number>
|
| 8 |
+
<date>2012-11-02</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<p id="p-1" num="1">Amendments In the Specification:</p>
|
| 14 |
+
<p id="p-2" num="2">Please amend paragraph at page <part-num-ref name="page">55,</part-num-ref>
|
| 15 |
+
lines 3-17, as follows: </p>
|
| 16 |
+
<p id="p-3" num="3">To evaluate whether Au-phage-based networks could be efficiently used to study peptide ligand binding to receptors on the cell surface as well as receptor-mediated properties such as phage internalization, immunofluorescence-staining assays were performed with antibodies directed to the phage capsid. Melanoma cells were chosen because they express high levels of <confidence value="5">a</confidence>
|
| 17 |
+
v integrins (Albelda et a<confidence value="5">l</confidence>
|
| 18 |
+
., <part-num-ref name="av integrins (Albelda et al.,">1990)</part-num-ref>
|
| 19 |
+
the cell surface receptor for a well characterized phage displaying the peptide CDCRGDCFC (S<confidence value="66">EQ</confidence>
|
| 20 |
+
ID NO:64<confidence value="5">;</confidence>
|
| 21 |
+
termed RGD-4C) (Arap et a<confidence value="5">l</confidence>
|
| 22 |
+
., 1998). </p>
|
| 23 |
+
<p id="p-4" num="4">Here it is shown that the targeting and receptor-mediated internalization capabilities of the RGD- 4C peptide remained intact within the Au-RGD-4C networks. Accordingly, internalization was inhibited (Chen et a<confidence value="5">l</confidence>
|
| 24 |
+
., <part-num-ref name="Au-RGD-4C networks. Accordingly, internalization was inhibited (Chen et al.,">2004)</part-num-ref>
|
| 25 |
+
in a dose-dependent manner when cells were pre-incubated with the RGD-4C synthetic peptide prior to incubation with Au-RGD-4C networks. The likely synergy between the receptor-mediated phage internalization and electromagnetically-induced surface enhancement of the Au nanoparticles (Kneipp et a<confidence value="5">l</confidence>
|
| 26 |
+
., <part-num-ref name="Au nanoparticles (Kneipp et al.,">1999)</part-num-ref>
|
| 27 |
+
resulted in an increase in the enhanced fluorescence for the targeted Au-RGD-4C networks relative to those observed for the RGD-4C phage alone. Negative controls show only background signal. </p>
|
| 28 |
+
<p id="p-5" num="5">{00017585} 2 </p>
|
| 29 |
+
</description>
|
| 30 |
+
</us-patent-application>
|
| 31 |
+
|
applicant/11722809.xml
ADDED
|
@@ -0,0 +1,15 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="UTF-8"?>
|
| 2 |
+
<pat:SpecificationDocument xmlns:pat="urn:us:gov:doc:uspto:patent" xmlns="urn:us:gov:doc:uspto:patent" xmlns:ent="urn:us:gov:doc:uspto:enterprise" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:tbl="http://www.oasis-open.org/tables/exchange/1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:com="http://www.wipo.int/standards/XMLSchema/Common/1" pat:instanceFileName="11722809.02-24-2017.IZPGTIGVPXXIFW1.SPEC.xml" pat:id="IZPGTIGVPXXIFW1" xsi:schemaLocation="urn:us:gov:doc:uspto:patent XMLSchema/V1_3/SpecificationDocument_1_0.xsd">
|
| 3 |
+
<pat:DocumentCode>SPEC</pat:DocumentCode><pat:DocumentHeaderDetails pat:id="ID-00001">
|
| 4 |
+
<pat:ApplicationHeaderDetails><pat:ApplicationNumber>11722809</pat:ApplicationNumber></pat:ApplicationHeaderDetails>
|
| 5 |
+
<pat:PageTotalQuantity>1</pat:PageTotalQuantity>
|
| 6 |
+
<pat:ParagraphTotalQuantity>3</pat:ParagraphTotalQuantity>
|
| 7 |
+
</pat:DocumentHeaderDetails>
|
| 8 |
+
<pat:MailRoomDate>2017-02-24</pat:MailRoomDate>
|
| 9 |
+
<pat:Specification pat:id="Specification">
|
| 10 |
+
<?PageStart number="1"?>
|
| 11 |
+
<pat:P pat:id="p-1" pat:pNumber="1"><pat:U>Amendments to the Specification:</pat:U></pat:P>
|
| 12 |
+
<pat:P pat:id="p-2" pat:pNumber="2">Please replace the <pat:PartName pat:idref="PN-00001">paragraph beginning on page </pat:PartName><pat:PartNumber pat:id="PN-00001">2</pat:PartNumber>, <pat:PartName pat:idref="PN-00002">line </pat:PartName><pat:PartNumber pat:id="PN-00002">11</pat:PartNumber>, with the following paragraph:</pat:P>
|
| 13 |
+
<pat:P pat:id="p-3" pat:pNumber="3">This object is achieved by a gas discharge lamp as claimed in claim <pat:OCRConfidenceData pat:levelNumber="9">1</pat:OCRConfidenceData> and a method for operation of a gas discharge lamp as claimed in claim <pat:OCRConfidenceData pat:levelNumber="99">11</pat:OCRConfidenceData>.</pat:P>
|
| 14 |
+
<pat:BoundaryData><pat:HeaderText>-2-</pat:HeaderText></pat:BoundaryData>
|
| 15 |
+
</pat:Specification></pat:SpecificationDocument>
|
applicant/11735531.xml
ADDED
|
@@ -0,0 +1,24 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>11735531</doc-number>
|
| 8 |
+
<date>2010-01-04</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<heading id="h-1">AMENDMENTS TO THE SPECIFICATION</heading>
|
| 14 |
+
<p id="p-1" num="1">Please replace the paragraph beginning on Page <part-num-ref name="paragraph beginning on Page">3,</part-num-ref>
|
| 15 |
+
line <part-num-ref name="paragraph beginning on Page 3, line">12</part-num-ref>
|
| 16 |
+
with the following amended paragraph: </p>
|
| 17 |
+
<p id="p-2" num="2">More specifically, an information handling system has plural processing components, at least some of which interface through a PCI Express link managed by a PCI Express controller. The PCI Express controller detects non-fatal errors for communications sent through the link and, upon detection of a non-fatal error, issues an interrupt. An SMI ("System Management Interrupt"<confidence value="5">)</confidence>
|
| 18 |
+
error handler associated with the BIOS firmware of the information handling system receives the interrupt and queries the error event source to determine the end point component interfaced with the PCI Express link that is associated with the error. A non-fatal error monitor, such as firmware associated with the SMI error handler, tracks the number of non-fatal errors and their association with components. If a predetermined condition exists, such as a predetermined number of non-fatal errors associated with a component, then the non-fatal error monitor issues an error message. For example, an error message issued to the operating system is presented at a display of the information handling system. As another example, an error message is forwarded to a BMC to provide notice of the non- fatal error to a management application interfaced through a network. </p>
|
| 19 |
+
<p id="p-3" num="3">
|
| 20 |
+
<confidence value="8">2</confidence>
|
| 21 |
+
</p>
|
| 22 |
+
</description>
|
| 23 |
+
</us-patent-application>
|
| 24 |
+
|
applicant/11736661.xml
ADDED
|
@@ -0,0 +1,190 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>11736661</doc-number>
|
| 8 |
+
<date>2007-04-18</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<boundary-data type="header">
|
| 14 |
+
<confidence value="8">L</confidence>
|
| 15 |
+
VM 254267 </boundary-data>
|
| 16 |
+
<boundary-data type="header">
|
| 17 |
+
<confidence value="6">1</confidence>
|
| 18 |
+
</boundary-data>
|
| 19 |
+
<heading id="h-1">TRUST PROGRAM FOR PROVIDING INTEGRATED SERVICES FOR PERSONAL</heading>
|
| 20 |
+
<heading id="h-2">INJURY SETTLEMENT CLIENTS</heading>
|
| 21 |
+
<heading id="h-3">CROSS-REFERENCE TO RELATED APPLICATIONS</heading>
|
| 22 |
+
<p id="p-1" num="1">
|
| 23 |
+
<confidence value="5">[</confidence>
|
| 24 |
+
0001<confidence value="4">]</confidence>
|
| 25 |
+
This patent application claims the benefit of priority to U.S. Provisional Patent Application No. 60/792,726, filed on April <part-num-ref name="benefit of priority to U.S. Provisional Patent Application No. 60/792,726, filed on April">18,</part-num-ref>
|
| 26 |
+
<part-num-ref name="benefit of priority to U.S. Provisional Patent Application No. 60/792,726, filed on April 18,">2006,</part-num-ref>
|
| 27 |
+
which is incorporated in its entirety herein by this reference. </p>
|
| 28 |
+
<heading id="h-4">FIELD OF THE INVENTION</heading>
|
| 29 |
+
<p id="p-2" num="2">[0002] This invention relates generally to settlement payments, and more particularly to a program for assisting victims of personal injuries to handle their settlement payments and help to manage their lives after injury.</p>
|
| 30 |
+
<heading id="h-5">BACKGROUND OF THE INVENTION</heading>
|
| 31 |
+
<p id="p-3" num="3">[0003<confidence value="4">]</confidence>
|
| 32 |
+
Personal injury lawsuits are often settled with some portion of the settlement being paid out through a structured or periodic stream of payments. A structured settlement is a stream of periodic payments tailored to meet the anticipated future medical expenses, basic living needs and other expected expenses of the injured person. These periodic payments are funded through the issuance of an annuity from an insurance company. A long-term structured settlement payment program is often a better option than a lump sum payment, because it provides guaranteed long-term income for the victim and his/her family, and gives them the ability to adapt or recuperate from the injury and associated losses without the need to actively manage the investment of the lump sum payment. There are, however, other aspects of the life of a personal injury victim that are not adequately addressed by a structured settlement. </p>
|
| 33 |
+
<heading id="h-6">BRIEF SUMMARY OF THE INVENTION</heading>
|
| 34 |
+
<p id="p-4" num="4">[0004<confidence value="5">]</confidence>
|
| 35 |
+
In view of the foregoing, the present invention, known as a Comprehensive Life Needs Trust Program ("CLNT Program<confidence value="5">"</confidence>
|
| 36 |
+
or "trust program"), provides personal injury victims who are entitled to receive structured settlement payments through a settlement agreement or <page-break num="2"/>
|
| 37 |
+
<boundary-data type="header">
|
| 38 |
+
<confidence value="8">L</confidence>
|
| 39 |
+
VM 254267 </boundary-data>
|
| 40 |
+
<boundary-data type="header">
|
| 41 |
+
<confidence value="8">2</confidence>
|
| 42 |
+
</boundary-data>
|
| 43 |
+
verdict with access to trust and other vendor services. The CLNT Program addresses the unique physical and financial concerns of the personal injury settlement client by providing access to the management of not only the assets received by a client, but also to vendor goods and services to assist them in managing their lives after injury, thereby providing additional goods and services. </p>
|
| 44 |
+
<p id="p-5" num="5">Accordingly, in one embodiment of the present invention, a CLNT Program provides access to appropriate strategies to manage and protect settlement proceeds and also offers comprehensive life management tools to facilitate the day-to-day needs of the injured. These life management tools include access to goods and services associated with prescription drugs, home healthcare, medical equipment and durable goods, home services such as mortgages, and/or additional consumer discounts on electronics, cellular phones, restaurant and clothing stores, travel and leisure, and entertainment. In another embodiment of the present invention, life management tools include access to goods and services provided for health, nursing, and handicap needs.</p>
|
| 45 |
+
<p id="p-6" num="6">[0005] In yet another embodiment of the invention, a method of assisting a personal injury client is provided that includes the steps of setting up a trust program; transferring assets from a settlement for compensating a personal injury client to the trust program; managing, by the trust program, a structured payment program for the personal injury client; and providing additional services or goods. Additional services or goods can include at least one or more of the following:</p>
|
| 46 |
+
<p id="p-7" num="7">home health care services or goods, durable products for the disabled and/or for medical treatment, prescription drug program services, architectural services, home maintenance services, life care planning services, and/or guaranteed-issue health insurance.</p>
|
| 47 |
+
<p id="p-8" num="8">[0006] Additional features, embodiments, and details of this invention can be obtained from the following detailed description of embodiments of the invention.</p>
|
| 48 |
+
<heading id="h-7">DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION</heading>
|
| 49 |
+
<p id="p-9" num="9">[0007] A study by the Tilinghast-Towers ePerrin Report, U.S. Tort Costs: <part-num-ref name="Tilinghast-Towers ePerrin Report, U.S. Tort Costs:">2004</part-num-ref>
|
| 50 |
+
update, states that the cost of tort settlements in the United States alone was $246 billion, and the patent applicant estimates that $40 billion went to compensating victims or personal injuries. About 80% of the $40 billion was distributed in cash to the claimants, who may use or invest the cash payments. When a plaintiff requires government assistance such as Supplementary Security <page-break num="3"/>
|
| 51 |
+
<boundary-data type="header">
|
| 52 |
+
<confidence value="888">LVM</confidence>
|
| 53 |
+
254267 </boundary-data>
|
| 54 |
+
<boundary-data type="header">
|
| 55 |
+
<confidence value="8">3</confidence>
|
| 56 |
+
</boundary-data>
|
| 57 |
+
Income and Medicaid as a result of their injuries, special-needs trusts are often the best vehicle to protect the award while ensuring the plaintiff remains eligible for the government assistance. </p>
|
| 58 |
+
<p id="p-10" num="10">Increasingly, arguments are made for settlement proceeds in the form of cash. Many investment alternatives are now available through financial planners, stockbrokers, bank trust departments, and other vendors.</p>
|
| 59 |
+
<p id="p-11" num="11">[0008<confidence value="5">]</confidence>
|
| 60 |
+
A CLNT Program of the present invention is a way to add new features and benefits to the settlement process: access to continuous trust management and professional experience, investment management, safety, continuity of management if the claimant becomes incapacitated, estate planning and flexible comprehensive solutions tailored to the claimants needs. Surveys and research into possible needs indicate that health, wealth, and maintaining lifestyle are major concerns to claimants. </p>
|
| 61 |
+
<p id="p-12" num="12">[0009<confidence value="5">]</confidence>
|
| 62 |
+
Property and casualty carriers and corporations that self insure nationwide want to settle cases favorably. From their perspective, any settlement method that improves case management is a benefit. The CLNT Program of the invention provides a way to resolve settlement issues that can be used separately or in combination with the core structured settlement annuity. The CLNT Program of the invention now has a greater opportunity to define solutions that can speed the settlement process. </p>
|
| 63 |
+
<p id="p-13" num="13">[0010<confidence value="5">1</confidence>
|
| 64 |
+
A trust account provides professional management of assets and a means for protecting those assets from creditors, persons who would advise dubious investments, inexperienced or imprudent beneficiaries. Trusts serve the needs of physically challenged beneficiaries and meeting the goals of the trustor such as education, retirement income and contingent medical needs, as well as offering complete financial records and accurate tax information. </p>
|
| 65 |
+
<p id="p-14" num="14">[0011<confidence value="5">1</confidence>
|
| 66 |
+
It is helpful to understand the concept of a typical claims lifecycle to fully understand the need for providing access to trust services to manage a structured settlement. In any particular case involving a physical injury, the plaintiff alleging a wrong can file a lawsuit or claim. The defendant typically hires an attorney to defend its position and the negotiations begin. </p>
|
| 67 |
+
<p id="p-15" num="15">The parties may agree to a negotiated settlement, or, if they do not agree, the lawsuit goes to trial and a verdict is decided in court.</p>
|
| 68 |
+
<boundary-data type="header">
|
| 69 |
+
<confidence value="8">L</confidence>
|
| 70 |
+
<confidence value="88">VM</confidence>
|
| 71 |
+
254267 </boundary-data>
|
| 72 |
+
<boundary-data type="header">
|
| 73 |
+
<confidence value="8">4</confidence>
|
| 74 |
+
</boundary-data>
|
| 75 |
+
<p id="p-16" num="16">
|
| 76 |
+
<page-break num="4"/>
|
| 77 |
+
[0012<confidence value="5">1</confidence>
|
| 78 |
+
Once the claim/lawsuit has been resolved, the claimant must decide how to accept the settlement proceeds. They must choose to take the settlement all in cash, all in a structured annuity, or a combination of the two. Frequently, as part of the negotiation or per the court's decision, the choice of how the settlement is to be paid is pre-determined. For example: in the case of an injured minor, the court may require that a certain amount of the settlement proceeds be placed into a Special Needs Trust. </p>
|
| 79 |
+
<p id="p-17" num="17">[0013<confidence value="5">1</confidence>
|
| 80 |
+
A trust services component of the CLNT Program invention can be provided by a nationally chartered trust company authorized to administer trusts from all fifty states. The company can adhere to the philosophy to operate with a firm commitment to personalized relationships by offering a robust portfolio of products. The financial strength of the company providing the trust service component of the CLNT Program can be expected to be strong to ensure the highest quality trust service for its clients. The trust program can build relationships with its clients, the injured claimants and their caregivers, and the trust program can function as a partner, taking an active role in serving as a reliable resource in helping its clients build and maintain better lives and providing professional management of settlement recoveries. </p>
|
| 81 |
+
<p id="p-18" num="18">[0014<confidence value="5">]</confidence>
|
| 82 |
+
Generally, a trust is a legal relationship in which the grantor (creator of the trust) transfers property to a trustee (an individual or an institution) a trust company) to hold and manage for the benefit of one or more beneficiaries. The trust document, drafted by an attorney, sets forth the grantor's desires as to the duration of the trust, the powers and duties to be given the trustee, the time and manner of the distribution of the trust income and principle, and the rights of the beneficiaries. The grantor gives the trustee legal title to the trust property and the trustee is legally bound to manage, invest, and disburse that property in the manner described in the trust document and in accordance with the current law. </p>
|
| 83 |
+
<p id="p-19" num="19">[0015<confidence value="5">]</confidence>
|
| 84 |
+
A special needs trust is designed to allow a disabled beneficiary to retain assets without disqualifying him or her from government benefits, such as Supplementary Security Income (SSI) and Medicaid. This allows the beneficiary to continue to receive the valuable government benefits available while using the trust to supplement his or her needs. Without a special needs trust, a person may not qualify for government benefits and may be required to spend the money in the trust before qualifying for government assistance. Also, depending on the <page-break num="5"/>
|
| 85 |
+
<boundary-data type="header">
|
| 86 |
+
<confidence value="8">L</confidence>
|
| 87 |
+
VM 254267 </boundary-data>
|
| 88 |
+
<boundary-data type="header">
|
| 89 |
+
<confidence value="8">5</confidence>
|
| 90 |
+
</boundary-data>
|
| 91 |
+
type of special needs trust; there may be provisions that require the repayment of state Medicaid money upon the death of the beneficiary or at the termination of the trust. Under current conditions, the trust must be deemed irrevocable to qualify as a special needs trust. </p>
|
| 92 |
+
<p id="p-20" num="20">[0016<confidence value="4">]</confidence>
|
| 93 |
+
An irrevocable trust cannot be amended, revoked or terminated. A permanent election was made by a person of proper authority to change the legal title of the assets to that of the trustee when they are placed in an irrevocable trust. This permanent relinquishment of control over the trust assets may give the trust the power to control potential estate taxes and possibly protect the assets from the claims of future creditors and/or in the case of divorce. </p>
|
| 94 |
+
<p id="p-21" num="21">[0017<confidence value="5">]</confidence>
|
| 95 |
+
Whether a trust is irrevocable or revocable, two aspects of creating a trust are asset management and disability planning. Creating a trust can help ensure assets are managed pursuant to the terms of the trust. </p>
|
| 96 |
+
<p id="p-22" num="22">[0018] A vendor services component of a CLNT Program is a distinguishing feature of the invention in that it can offer access to various product and service distribution channels for health, nursing, handicap needs and more that are tailored to assisting clients of personal injury settlements. It differentiates itself not only through providing access to money management, but also through innovative product design and comprehensive life need tools. It can become the cornerstone of the recipient's daily routine. To that end, the CLNT Program has identified and continues to identify products and services designed specifically for its client's needs as victims of physical injury.</p>
|
| 97 |
+
<p id="p-23" num="23">[0019] A trust services component of the CLNT Program is based on the understanding that individuals who receive settlements have unique circumstances. Its goal is to understand those individual needs and provide an array of products and services to help manage those daily- specialized needs. These preferably can all be contained in a single-source order and delivery environment created by the trust program and investment portfolio designed to meet those needs.</p>
|
| 98 |
+
<p id="p-24" num="24">The CLNT Program can be a provider of global financial solutions for the investment management, asset administration, fiduciary and banking needs of physical injury recipients.</p>
|
| 99 |
+
<p id="p-25" num="25">[0020] Some products and services channels suitable for use with a CLNT Program of the present invention are described below.</p>
|
| 100 |
+
<boundary-data type="header">
|
| 101 |
+
<confidence value="888">LVM</confidence>
|
| 102 |
+
254267 </boundary-data>
|
| 103 |
+
<boundary-data type="header">
|
| 104 |
+
<confidence value="8">6</confidence>
|
| 105 |
+
</boundary-data>
|
| 106 |
+
<p id="p-26" num="26">
|
| 107 |
+
<page-break num="6"/>
|
| 108 |
+
1. Nursing/Attendant Care/Home Health Care Services: Health care today is based on a professional health care team working toward a common goal. Today, home health care may be considered for patients who are recovering from an illness, undergoing treatment, disabled, chronically ill, or terminally ill. Home health care can be categorized into two groups: <part-num-ref name="illness, undergoing treatment, disabled, chronically ill, or terminally ill. Home health care can be categorized into two groups:">(1)</part-num-ref>
|
| 109 |
+
standard home health care, and <part-num-ref name="standard home health care, and">(2)</part-num-ref>
|
| 110 |
+
hospice care - provided for terminally ill patients who prefer peace, comfort, and dignity of being at home. The trust program can work with those who need home health care and give them support by referring them to service providers such as: home health agencies, homemaker and home care aide agencies, pharmaceutical and infusion therapy companies, durable medical equipment dealers, staffing registries and private duty agencies, and independent providers, for example. </p>
|
| 111 |
+
<p id="p-27" num="27">2. The trust program can also direct its trust clients to sources that help them pay for home health care, such as, Medicare, Medicaid, Veteran's Administration, Social Services Block Grants, Community Organizations, Commercial Health Insurance, Civilian Health and Medical Program of the Uniformed Services (CHAMPUS), worker's compensation, and Managed Care Organizations, for example. The trust program can refer to resources that facilitate an intake checklist to determine the quality of provider(s) a patient/client is looking to use. The checklist can include Licensure, Bonding, Certification and Accreditation considerations, for example.</p>
|
| 112 |
+
<p id="p-28" num="28">3. Durable Products: The trust program can offer durable goods products by partnering with suppliers to attain discounted prices. Durable goods can include devices to help disabled clients and/or to provide medical treatment such as: wheelchairs, diabetic shoes, bed and bath products, walkers, rollators, power scooters, oxygen therapy, lift chairs, electrotherapy, syringes, and daily living aids, etc.</p>
|
| 113 |
+
<p id="p-29" num="29">4. Life Care Planning: Catastrophic injury and chronic illness can be a devastating event that affects not only the individual and family, but also those who provide the care.</p>
|
| 114 |
+
<p id="p-30" num="30">Specialized services may be required for the remainder of a person's lifetime. Due to advances in medical research and technology, people are living longer; consequently <page-break num="7"/>
|
| 115 |
+
<boundary-data type="header">
|
| 116 |
+
<confidence value="8">L</confidence>
|
| 117 |
+
VM 254267 </boundary-data>
|
| 118 |
+
<boundary-data type="header">
|
| 119 |
+
<confidence value="8">7</confidence>
|
| 120 |
+
</boundary-data>
|
| 121 |
+
the need for long term care has increased. A Life Care Plan is a dynamic document based upon published standards and practices. It can include a comprehensive assessment, data analysis and research that provide an organized, concise plan for current and f<confidence value="8">u</confidence>
|
| 122 |
+
ture needs, with associated costs, for an individual who has experienced catastrophic injury or has chronic health care needs. The Life Care Plan can: </p>
|
| 123 |
+
<p id="p-31" num="31">
|
| 124 |
+
<confidence value="86">a.</confidence>
|
| 125 |
+
Provide education as to functional impact of disabilities b. Assess future health, medical, equipment, and supportive care needs utilizing a multiple disciplinary approach c. Develop options and alternatives that may become necessary d. Provide a comprehensive detailed plan outlining specific, current and future needs, services, frequencies, duration and costs e. Educate and provide a working guideline and a reference for the disabled person, the family, and all third parties (i.e. attorneys, insurance carriers, and judicial system) <confidence value="5">f</confidence>
|
| 126 |
+
Increase the awareness of, and reduce the likelihood of potential complications. </p>
|
| 127 |
+
<p id="p-32" num="32">5. The trust program can refer, and establish relationships with, personal Life Care Planners for trust clients by working through organizations such as the American Association of Nurse Life Care Planners, Gisclair and Associates, Durable Medical Equipment, Inc., for example and through various licensed planners or vendors located across the United States.</p>
|
| 128 |
+
<p id="p-33" num="33">6. Guaranteed-Issue Health Insurance: The trust program can work with clients to help find plans that can enable most to obtain some level of insurance coverage for medical expenses. One such plan for instance is in Ohio, where the guarantee issue Basic Plan <part-num-ref name="guarantee issue Basic Plan">400</part-num-ref>
|
| 129 |
+
includes; daily hospital benefits, intensive care benefits, initial hospitalization rider, accident benefit, outpatient sickness, prescriptions, and surgical & anesthesia benefits. </p>
|
| 130 |
+
<p id="p-34" num="34">7. Home Maintenance and <confidence value="66">/o</confidence>
|
| 131 |
+
r Architectural Services for Handicapped Needs: The preservation of quality of life and independence can be greatly affected when homes are not adequately designed or renovated to allow mobility and accessibility for <page-break num="8"/>
|
| 132 |
+
<boundary-data type="header">
|
| 133 |
+
<confidence value="888">LVM</confidence>
|
| 134 |
+
254267 </boundary-data>
|
| 135 |
+
<boundary-data type="header">
|
| 136 |
+
<confidence value="8">8</confidence>
|
| 137 |
+
</boundary-data>
|
| 138 |
+
handicapped individuals. The choices and problems involved in any architectural project can be bewildering and complex. The services and consulting that these companies have uniquely tailored for handicap redesign and new construction can greatly benefit our clients. The trust program can work diligently with these companies to provide not only referral services, but price discounts as well. </p>
|
| 139 |
+
<p id="p-35" num="35">8. Mail Order Prescription Drug Service: A prescription discount program, such as from Medco Health, can give clients freedom and convenience when purchasing prescriptions, as well as, offering discounts. Further, if medicines ordered on a regular basis are purchased through a home delivery pharmacy service<confidence value="66">,,</confidence>
|
| 140 |
+
such as the one offered by Medco, for example, clients can receive greater discounts. The prescription discount program is available to all Medicare beneficiaries nationwide, except those who have prescription drug coverage under their state's Medicaid program or those who are enrolled in a Medicare managed care plan that offers its own exclusive Medicare-approved drug discount card. The program is approved by Medicare, but it is not a Medicare benefit, and is not intended to replace prescription drug benefits obtained through participation in insurance plans including a Medicare+choice plan, a Medigap policy, Medicaid, or an employer plan. The trust program can deepen and strengthen its relationship with its clients and their advisors by offering referrals and support to these plans. </p>
|
| 141 |
+
<p id="p-36" num="36">9. Trust Services: Settlement trusts are becoming ever popular as an alternative for, or at least a complement with, annuity-based structured settlements. The trust program can offer the services typically provided by trusts of the following types:</p>
|
| 142 |
+
<p id="p-37" num="37">a. Special Needs Trust - These vehicles can be used to administer tort recoveries for plaintiffs who want to maintain their eligibility for public assistance. A fundamental objective of using a Special Needs Trust is to leverage the beneficiary's health-care costs, first from available public-benefit funds and only then from the discretionary trust. The grantor's intent is to use trust income and principal as a supplement to benefits and support provided by governmental <page-break num="9"/>
|
| 143 |
+
<boundary-data type="header">
|
| 144 |
+
<confidence value="8">L</confidence>
|
| 145 |
+
VM 254267 </boundary-data>
|
| 146 |
+
<boundary-data type="header">
|
| 147 |
+
<confidence value="8">9</confidence>
|
| 148 |
+
</boundary-data>
|
| 149 |
+
programs, and is intended to preserve a disabled beneficiary's eligibility for Medicaid and Supplemental Security Income (SSI). </p>
|
| 150 |
+
<p id="p-38" num="38">b. Medicare Set-Aside ("MSA") Trust - An MSA allocation can be set up with funds from a settlement to be used for the sole purpose of paying for Medicare- allowable medical expenses. The funds are to be used specifically for those expenses relating to injury that would otherwise be covered by Medicare. There is a special point of emphasis that claimants must adhere to maintain their MSA, created by the Centers for Medicare and Medicaid Services (CMS). The comprehensive trust program can be a beneficial part of a client's settlement by helping monitor, preserve, and protect their MSA through the trust services.</p>
|
| 151 |
+
<p id="p-39" num="39">10. Handicap Camp Referral Services: The trust program can further strengthen its relationship with clients and their advisors by taking an integral part in the referral of those with disabilities to camps that offer a positive experience. Programs such as the Texas Lions Camp and Camp Prospects provide outdoor camping experiences to handicapped children, letting them enjoy many activities including; swimming, horsemanship, ropes courses, arts & crafts, nature studies, animal science and horticulture, music, drama, recreation and athletics, shooting sports and <confidence value="22222222222222222">overnight/outdoor</confidence>
|
| 152 |
+
campouts. </p>
|
| 153 |
+
<p id="p-40" num="40">11. Handicap Van/Auto Conversion: Along with handicap camp referrals, the trust program can refer resource needs for handicap auto/van conversions by companies such as IMS, which manufactures mobility vans and Rollx Vans which can provide a conversion for an existing van. The <confidence value="25">IM</confidence>
|
| 154 |
+
S Rampvan offers superior engineering and design. It's the first to be crash tested, offer the most carrying capacity, more headroom, more interior space and the fastest ramp deployment and retraction. Rollx Vans specializes in handicap van conversions. </p>
|
| 155 |
+
<p id="p-41" num="41">[0021] In another embodiment of the invention, a CLNT Program includes a method of delivering preferred price goods and services through a convenient mail-order, fax, telephone, or internet type system capable of providing access to discounted life enhancement goods and services. The CLNT Program also includes access to direct durable medical equipment, medical services companies, a prescription drug service, and connections for home maintenance. The <page-break num="10"/>
|
| 156 |
+
<boundary-data type="header">
|
| 157 |
+
<confidence value="8">L</confidence>
|
| 158 |
+
VM 254267 </boundary-data>
|
| 159 |
+
<boundary-data type="header">
|
| 160 |
+
<confidence value="88">10</confidence>
|
| 161 |
+
</boundary-data>
|
| 162 |
+
trust also includes access to a trust bank for conventional trust services including investment management, client communications and trust fiduciary and administration services. </p>
|
| 163 |
+
<p id="p-42" num="42">Accordingly, the invention provides both conventional trust services and comprehensive life need services to settlement recipients.</p>
|
| 164 |
+
<p id="p-43" num="43">[0022<confidence value="4">]</confidence>
|
| 165 |
+
In one embodiment of the invention, a CLNT Program is accessed through a secure internet web provider with effectively personalized and advantaged concierge-like services that can also be accessed by phone, fax and/or regular mail, such that preferred prices are provided on health savings, clothing, entertainment, dining, travel, airlines, hotels, office goods, internet services, package delivery services, etc. For convenience, this aspect is described as a "web provider" and it should be noted that this term is intended to encompass any means, channel, and/or method of providing access to the trust including internet, phone, fax, and/or mail techniques known to those of ordinary skill in the art of the invention. The web provider can also access a direct durable medical equipment provider billed at preferred pricing that can offer medical equipment such as ambulation aids, bathroom aids, exercise equipment, diabetic supplies, home modification devices (such as ramps, showers, facilities, chair lifts, cabinets, countertops, bathtubs, shower grab bars, toilets, mirrors, and storage), vehicle modification devices (such as custom vans, van conversions, wheelchair lifts, hand controls), etc. The web provider can also access a home health/medical services provider billed at preferred pricing to provide local or national home nursing care, including access to RN, LPN, nurse-care case coordinators, medical assistance<confidence value="5">/</confidence>
|
| 166 |
+
home health aides, companion services (for eating, dressing, shopping etc.), and licensed therapists (for physical, speech, or occupational needs). The web provider can also access a discounted prescription drug service, including access to tailored prescription plans to help clients reduce overall drug costs and insurance requirements. The web provider can also access a home maintenance service including a broad coverage of contractors providing home services such as maid services, handyman services, lawn care, pest care, heating and air conditioning repair, home security, etc. Home services can also include home buying and selling, moving services, utility connections, temporary living arrangements, and home protections (insurance, warranty, mortgage protection, locksmith, inspection, etc.). </p>
|
| 167 |
+
<boundary-data type="header">
|
| 168 |
+
<confidence value="8">L</confidence>
|
| 169 |
+
VM 254267 </boundary-data>
|
| 170 |
+
<boundary-data type="header">
|
| 171 |
+
<confidence value="88">11</confidence>
|
| 172 |
+
</boundary-data>
|
| 173 |
+
<p id="p-44" num="44">
|
| 174 |
+
<page-break num="11"/>
|
| 175 |
+
<confidence value="5">[</confidence>
|
| 176 |
+
0023<confidence value="5">]</confidence>
|
| 177 |
+
In another embodiment of the invention, by utilizing renowned money managers with years of investment experience, a CLNT Program for settlement recipients and its custodian, the trust services component of the CLNT program, can manage trusts and custodial accounts with safe, high quality and cost efficient trust administration service. The CLNT Program for settlement recipients can provide access to the infrastructure, specialized computer support and processing systems needed to properly manage and service personal injury settlement trusts including Special Needs Trusts and Medicare Set-Aside Trusts. Additional types of trusts can be created as particular investment vehicles to support conventional trust needs and objectives as understood by those of ordinary skill in the relevant art. Accordingly, in this aspect of the invention a customized structured payment program can be created for a personal injury client, which bolsters other aspects of the comprehensive trust related to managing the client's daily life after injury with provisions of additional goods and services. </p>
|
| 178 |
+
<p id="p-45" num="45">[0024] All references, including publications, patent applications, and patents, cited herein are hereby incorporated by reference to the same extent as if each reference were individually and specifically indicated to be incorporated by reference and were set forth in its entirety herein.</p>
|
| 179 |
+
<p id="p-46" num="46">[0025] The use of the terms "a" and "an" and "the" and similar referents in the context of describing the invention (especially in the context of the following claims) are to be construed to cover both the singular and the plural, unless otherwise indicated herein or clearly contradicted by context. The terms "comprising," "having," "including," and "containing" are to be construed as open-ended terms (i.e., meaning "including, but not limited to,") unless otherwise noted.</p>
|
| 180 |
+
<p id="p-47" num="47">Recitation of ranges of values herein are merely intended to serve as a shorthand method of referring individually to each separate value falling within the range, unless otherwise indicated herein, and each separate value is incorporated into the specification as if it were individually recited herein. All methods described herein can be performed in any suitable order unless otherwise indicated herein or otherwise clearly contradicted by context. The use of any and all examples, or exemplary language (e.g., "such as") provided herein, is intended merely to better illuminate the invention and does not pose a limitation on the scope of the invention unless otherwise claimed. No language in the specification should be construed as indicating any non- claimed element as essential to the practice of the invention.</p>
|
| 181 |
+
<boundary-data type="header">LVM 254267</boundary-data>
|
| 182 |
+
<boundary-data type="header">
|
| 183 |
+
<confidence value="88">12</confidence>
|
| 184 |
+
</boundary-data>
|
| 185 |
+
<p id="p-48" num="48">
|
| 186 |
+
<page-break num="12"/>
|
| 187 |
+
[0026] Preferred embodiments of this invention are described herein, including the best mode known to the inventors for carrying out the invention. Variations of those preferred embodiments may become apparent to those of ordinary skill in the art upon reading the foregoing description. The inventors expect skilled artisans to employ such variations as appropriate, and the inventors intend for the invention to be practiced otherwise than as specifically described herein. Accordingly, this invention includes all modifications and equivalents of the subject matter recited in the claims appended hereto as permitted by applicable law. Moreover, any combination of the above-described elements in all possible variations thereof is encompassed by the invention unless otherwise indicated herein or otherwise clearly contradicted by context. </p>
|
| 188 |
+
</description>
|
| 189 |
+
</us-patent-application>
|
| 190 |
+
|
applicant/11736899.xml
ADDED
|
@@ -0,0 +1,367 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>11736899</doc-number>
|
| 8 |
+
<date>2007-04-18</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<boundary-data type="header">Attorney Docket No. 279.D42US<confidence value="8">1</confidence>
|
| 14 |
+
</boundary-data>
|
| 15 |
+
<heading id="h-1">METHODS FOR ANTI-ATHEROSCLEROTIC THERAPY</heading>
|
| 16 |
+
<heading id="h-2">CROSS-REFERENCE TO RELATED APPLICATION</heading>
|
| 17 |
+
<p id="p-1" num="1">[0001] This application is a continuation-in-pa<confidence value="66">rt</confidence>
|
| 18 |
+
(CIP) of U.S. Application Serial No. 11/284,370, filed November <part-num-ref name="continuation-in-part (CIP) of U.S. Application Serial No. 11/284,370, filed November">21,</part-num-ref>
|
| 19 |
+
<part-num-ref name="continuation-in-part (CIP) of U.S. Application Serial No. 11/284,370, filed November 21,">2005,</part-num-ref>
|
| 20 |
+
which is incorporated herein by reference. </p>
|
| 21 |
+
<heading id="h-3">TECHNICAL FIELD</heading>
|
| 22 |
+
<p id="p-2" num="2">[0002<confidence value="5">]</confidence>
|
| 23 |
+
This disclosure relates generally to medical treatment, and more particularly to methods for anti-atherosclerotic therapy. </p>
|
| 24 |
+
<heading id="h-4">BACKGROUND</heading>
|
| 25 |
+
<p id="p-3" num="3">[0003] Neural stimulation has been the subject of a number of studies and has been proposed for several therapies. The autonomic system controls physiological activities of the body and the imbalance of autonomic tone is related to many diseases and conditions. Reduced autonomic balance (increase in sympathetic and decrease in parasympathetic cardiac tone) during heart failure has been shown to be associated with left ventricular dysfunction and increased mortality. Sympathetic inhibition, as well as parasympathetic activation, have been associated with reduced arrhythmia vulnerability following a myocardial infarction. Vagus nerve stimulation has been proposed to treat sleep disorders, gastrointestinal motility, eating disorders, obesity, anorexia, gastrointestinal tract disorders, hypertension, coma, and epilepsy. Direct electrical stimulation of parasympathetic nerves can activate the baroreflex, inducing a reduction of sympathetic nerve activity and reducing blood pressure by decreasing vascular resistance. Direct stimulation of the vagal parasympathetic fibers has been shown to reduce heart rate via the sympathetic nervous system. In addition, some research indicates that chronic stimulation of the vagus nerve may be of protective myocardial benefit following cardiac ischemic insult.</p>
|
| 26 |
+
<p id="p-4" num="4">[0004] Atherosclerosis begins with the appearance of cholesterol-laden macrophages (foam cells) in the intima of an artery. Smooth muscle cells respond to the presence of lipid by proliferating, under the influence of platelet factors. A plaque <boundary-data type="header">
|
| 27 |
+
<confidence value="6">1</confidence>
|
| 28 |
+
</boundary-data>
|
| 29 |
+
<page-break num="2"/>
|
| 30 |
+
<boundary-data type="header">Attorney Docket No. 279.D42US<confidence value="5">1</confidence>
|
| 31 |
+
</boundary-data>
|
| 32 |
+
forms at the site, consisting of smooth muscle cells, leukocytes, and further deposition of lipid; in time the plaque becomes fibrotic and may calcify. Expansion of an atherosclerotic plaque leads to gradually increasing obstruction of the artery and ischemia of tissues supplied by it. Ulceration, thrombosis, or embolization of a plaque, or intimal hemorrhage and dissection, can cause more acute and severe impairment of blood flow, with the risk of infarction. </p>
|
| 33 |
+
<p id="p-5" num="5">[0005] Treatment of atherosclerosis includes balloon stretching, laser ablation, or surgical removal of plaques, and various bypass and grafting procedures. Current preventive measures for atherosclerosis include regular vigorous exercise, a diet low in fat and cholesterol, maintenance of a healthful weight, avoidance of tobacco, and use of pharmacologic agents as indicated.</p>
|
| 34 |
+
<heading id="h-5">SUMMARY</heading>
|
| 35 |
+
<p id="p-6" num="6">[0006] Disclosed herein, among other things, is a method for anti-atherosclerotic therapy. According to an embodiment, a patient is identified who could benefit from anti-atherosclerotic therapy. Therapy for atherosclerotic plaques is delivered to the patient, including neural stimulation to elicit a parasympathetic response.</p>
|
| 36 |
+
<p id="p-7" num="7">[0007] Disclosed herein, among other things, is a method for identifying a patient for anti-atherosclerotic therapy and delivering therapy. According to an embodiment, at least one diagnostic test is performed to determine if a patient is indicated for anti- atherosclerotic therapy. At least one parameter indicative of circulatory health is sensed as part of the diagnostic test, in an embodiment. Anti-atherosclerotic therapy is provided to the patient if the patient is indicated for anti-atherosclerotic therapy. In various embodiments, a neural target is stimulated as part of the therapy, using a predetermined stimulation schedule to inhibit vascular inflammation.</p>
|
| 37 |
+
<p id="p-8" num="8">[0008] Disclosed herein, among other things, is a method for anti-atherosclerotic therapy using an implanted device. According to an embodiment, at least one diagnostic test is performed to determine if a patient is indicated for anti- atherosclerotic therapy. If the patient is indicated for anti-atherosclerotic therapy, an implantable neural stimulator is implanted. Implanting a stimulator includes <boundary-data type="header">
|
| 38 |
+
<confidence value="8">2</confidence>
|
| 39 |
+
</boundary-data>
|
| 40 |
+
<page-break num="3"/>
|
| 41 |
+
<boundary-data type="header">Attorney Docket No. 279.D42US<confidence value="5">1</confidence>
|
| 42 |
+
</boundary-data>
|
| 43 |
+
positioning at least one electrode for use in stimulating a vagus nerve of the patient, according to an embodiment. Neural stimulation is delivered to the vagus nerve using the implantable neural stimulator according to a programmed stimulation schedule to inhibit vascular inflammation. </p>
|
| 44 |
+
<p id="p-9" num="9">[0009] This Summary is an overview of some of the teachings of the present application and not intended to be an exclusive or exhaustive treatment of the present subject matter. Further details about the present subject matter are found in the detailed description and appended claims. The scope of the present invention is defined by the appended claims and their legal equivalents.</p>
|
| 45 |
+
<heading id="h-6">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
|
| 46 |
+
<p id="p-10" num="10">
|
| 47 |
+
<confidence value="5">[</confidence>
|
| 48 |
+
0010<confidence value="5">]</confidence>
|
| 49 |
+
FIG. <confidence value="4">1</confidence>
|
| 50 |
+
A illustrates a system for applying neural stimulation therapy for atherosclerotic plaques including a medical device, according to one embodiment. </p>
|
| 51 |
+
<p id="p-11" num="11">
|
| 52 |
+
<confidence value="5">[</confidence>
|
| 53 |
+
0011<confidence value="5">]</confidence>
|
| 54 |
+
FIG. <confidence value="4">1</confidence>
|
| 55 |
+
B illustrates a system for applying neural stimulation therapy for atherosclerotic plaques including an external medical device, according to one embodiment. </p>
|
| 56 |
+
<p id="p-12" num="12">
|
| 57 |
+
<confidence value="5">[</confidence>
|
| 58 |
+
0012] FIG. 1 C illustrates a system for applying neural stimulation therapy for atherosclerotic plaques including an implantable medical device (IMD), according to one embodiment. </p>
|
| 59 |
+
<p id="p-13" num="13">[0013] FIG. 2 illustrates a system for applying neural stimulation therapy for atherosclerotic plaques including a sensing circuit, according to one embodiment.</p>
|
| 60 |
+
<p id="p-14" num="14">[0014] FIG. 3 illustrates an <confidence value="5">I</confidence>
|
| 61 |
+
MD for applying neural stimulation therapy for atherosclerotic plaques including a pacing circuit, according to one embodiment. </p>
|
| 62 |
+
<p id="p-15" num="15">[0015] FIG. 4 is a schematic illustration of an implantable system for neural stimulation therapy for atherosclerotic plaques, according to one embodiment.</p>
|
| 63 |
+
<p id="p-16" num="16">[0016] FIG. 5 illustrates a programmer such as illustrated in the system of FIG. 4 or other external device to communicate with the implantable medical device(s), according to one embodiment.</p>
|
| 64 |
+
<p id="p-17" num="17">[0017] FIG. 6 illustrates a flow diagram of a method of neural stimulation therapy for atherosclerotic plaques, according to one embodiment.</p>
|
| 65 |
+
<boundary-data type="header">
|
| 66 |
+
<confidence value="8">3</confidence>
|
| 67 |
+
</boundary-data>
|
| 68 |
+
<boundary-data type="header">Attorney Docket No. 279.D42US<confidence value="8">1</confidence>
|
| 69 |
+
</boundary-data>
|
| 70 |
+
<p id="p-18" num="18">
|
| 71 |
+
<page-break num="4"/>
|
| 72 |
+
<confidence value="5">[</confidence>
|
| 73 |
+
0018] FIG. 7 illustrates a flow diagram of a method for anti-atherosclerotic therapy, according to one embodiment. </p>
|
| 74 |
+
<p id="p-19" num="19">[0019<confidence value="5">]</confidence>
|
| 75 |
+
FIG. 8 illustrates a flow diagram of a method for identifying a patient for anti-atherosclerotic therapy and delivering therapy, according to one embodiment. </p>
|
| 76 |
+
<p id="p-20" num="20">[0020<confidence value="5">]</confidence>
|
| 77 |
+
FIG. 9 illustrates a flow diagram of a method for anti-atherosclerotic therapy using an implanted device, according to one embodiment. </p>
|
| 78 |
+
<heading id="h-7">DETAILED DESCRIPTION</heading>
|
| 79 |
+
<p id="p-21" num="21">
|
| 80 |
+
<confidence value="5">[</confidence>
|
| 81 |
+
0021] The following detailed description of the present subject matter refers to subject matter in the accompanying drawings which show, by way of illustration, specific aspects and embodiments in which the present subject matter may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the present subject matter. References to "an<confidence value="5">"</confidence>
|
| 82 |
+
, "one<confidence value="5">"</confidence>
|
| 83 |
+
, or "various" embodiments in this disclosure are not necessarily to the same embodiment, and such references contemplate more than one embodiment. The following detailed description is demonstrative and not to be taken in a limiting sense. The scope of the present subject matter is defined by the appended claims, along with the full scope of legal equivalents to which such claims are entitled. </p>
|
| 84 |
+
<p id="p-22" num="22">Neural Stimulation [0022] A brief discussion of the physiology related to neurology is provided to assist the reader with understanding this disclosure. The automatic nervous system (ANS) regulates "involuntary" organs. The ANS includes the sympathetic nervous system and the parasympathetic nervous system. The sympathetic nervous system is affiliated with stress and the "fight or flight response" to emergencies. The parasympathetic nervous system is affiliated with relaxation and the "rest and digest response." The ANS maintains normal internal f<confidence value="8">u</confidence>
|
| 85 |
+
nction and works with the somatic nervous system. Autonomic balance reflects the relationship between parasympathetic and sympathetic activity. A change in autonomic balance is reflected in changes in <boundary-data type="header">
|
| 86 |
+
<confidence value="8">4</confidence>
|
| 87 |
+
</boundary-data>
|
| 88 |
+
<page-break num="5"/>
|
| 89 |
+
<boundary-data type="header">Attorney Docket No. 279.D42US<confidence value="8">1</confidence>
|
| 90 |
+
</boundary-data>
|
| 91 |
+
heart rate, heart rhythm, contractility, remodeling, inflammation and blood pressure. </p>
|
| 92 |
+
<p id="p-23" num="23">Changes in autonomic balance can also be seen in other physiological changes, such as changes in abdominal pain, appetite, stamina, emotions, personality, muscle tone, sleep, and allergies, for example.</p>
|
| 93 |
+
<p id="p-24" num="24">[0023] An example of neural stimulation is baroreflex stimulation. Baroreflex is a reflex triggered by stimulation of a baroreceptor. A baroreceptor includes any sensor of pressure changes, such as sensory nerve endings in the wall of the auricles of the heart, vena cava, aortic arch and carotid sinus, that is sensitive to stretching of the wall resulting from increased pressure from within, and that functions as the receptor of the central reflex mechanism that tends to reduce that pressure. Afferent nerve trunks, such as the vagus, aortic and carotid nerves, leading from the sensory nerve endings also form part of a baroreflex pathway. Stimulating a baroreflex pathway and/or baroreceptors inhibits sympathetic nerve activity, stimulates the parasympathetic nervous system and reduces systemic arterial pressure by decreasing peripheral vascular resistance and cardiac contractility. Baroreceptors are naturally stimulated by internal pressure and the stretching of vessel wall (e.g. arterial wall). Neural stimulation of other neural targets is within the scope of the present disclosure, including stimulation of efferent and afferent pathways for parasympathetic and sympathetic nerves.</p>
|
| 94 |
+
<p id="p-25" num="25">[0024<confidence value="5">]</confidence>
|
| 95 |
+
A neural stimulation lead is a lead for delivering neural stimulation therapy, and can be placed in a number of appropriate locations. For example, various lead embodiments to stimulate a baroreflex are expandable, and are adapted to be placed in the pulmonary artery in the proximity of a high concentration of baroreceptors. Various lead embodiments are adapted to stimulate nerve endings in cardiac fat pads. Some lead embodiments are transvascular leads placed proximal to a cardiac fat pad. Some lead embodiments place an epicardial lead in a cardiac fat pad. </p>
|
| 96 |
+
<p id="p-26" num="26">Various lead embodiments include a cuff electrode adapted to be placed around a nerve, such as the aortic, carotid or vagus nerve. A nerve cuff refers to any lead configuration that is placed around a nerve trunk, including configurations placed around a sheath containing a nerve trunk. Some lead embodiments include a <boundary-data type="header">
|
| 97 |
+
<confidence value="8">5</confidence>
|
| 98 |
+
</boundary-data>
|
| 99 |
+
<page-break num="6"/>
|
| 100 |
+
<boundary-data type="header">Attorney Docket No. 279.D42US1</boundary-data>
|
| 101 |
+
transvascular lead placed proximal to a nerve, such as the vagus, aortic, or carotid nerve. Other leads can be placed in other neural stimulation and neural sensing locations to perform baroreflex or other therapy. </p>
|
| 102 |
+
<p id="p-27" num="27">Atherosclerosis [0025<confidence value="5">]</confidence>
|
| 103 |
+
In general, atherosclerosis is a cardiovascular disease in which the vessel wall is remodeled, compromising the lumen of the vessel. The atherosclerotic remodeling process involves accumulation of cells, both smooth muscle cells and monocyte/macrophage inflammatory cells, in the intima of the vessel wall. These cells take up lipid, likely from the circulation, to form a mature atherosclerotic lesion. </p>
|
| 104 |
+
<p id="p-28" num="28">Although the formation of these lesions is a chronic process, occurring over decades of an adult human life, the majority of the morbidity associated with atherosclerosis occurs when a lesion ruptures, releasing thrombogenic debris that rapidly occludes the artery. When such an acute event occurs in the coronary artery, myocardial infarction can ensue, and in the worst case, can result in death.</p>
|
| 105 |
+
<p id="p-29" num="29">[0026<confidence value="4">]</confidence>
|
| 106 |
+
Atherosclerosis is a serious health problem affecting millions of humans. </p>
|
| 107 |
+
<p id="p-30" num="30">Preventing the formation and rupture of atherosclerotic plaque would be of significant clinical benefit.</p>
|
| 108 |
+
<p id="p-31" num="31">[0027] The present system provides a medical device for applying neural stimulation therapy to patients with atherosclerosis. In various embodiments, systemic or local neural stimulation is applied intermittently to inhibit inflammatory response, preventing or reducing plaque formation and increasing the stability of existing plaques, thereby decreasing the severity of atherosclerosis.</p>
|
| 109 |
+
<p id="p-32" num="32">Medical Devices <confidence value="5">[</confidence>
|
| 110 |
+
0028] FIG. <confidence value="5">1</confidence>
|
| 111 |
+
A illustrates a system for applying neural stimulation therapy for atherosclerotic plaques including a medical device, according to one embodiment. </p>
|
| 112 |
+
<p id="p-33" num="33">The system 100 includes at least one neural stimulation lead <part-num-ref name="includes at least one neural stimulation lead">110</part-num-ref>
|
| 113 |
+
having a proximal portion <part-num-ref name="proximal portion">112</part-num-ref>
|
| 114 |
+
and a distal portion <part-num-ref name="distal portion">114.</part-num-ref>
|
| 115 |
+
The system also includes a plurality of electrodes <part-num-ref name="plurality of electrodes">120</part-num-ref>
|
| 116 |
+
along the distal portion of the at least one lead. In addition, the system <boundary-data type="header">
|
| 117 |
+
<confidence value="8">6</confidence>
|
| 118 |
+
</boundary-data>
|
| 119 |
+
<page-break num="7"/>
|
| 120 |
+
<boundary-data type="header">Attorney Docket No. 279.D42US<confidence value="8">1</confidence>
|
| 121 |
+
</boundary-data>
|
| 122 |
+
includes a medical device <part-num-ref name="medical device">102</part-num-ref>
|
| 123 |
+
coupled to the proximal portion of the at least one lead. </p>
|
| 124 |
+
<p id="p-34" num="34">The device includes a neural stimulator <part-num-ref name="neural stimulator">104</part-num-ref>
|
| 125 |
+
adapted to deliver an electrical signal through at least one electrode to an autonomic neural target. The device also includes a controller <part-num-ref name="controller">106</part-num-ref>
|
| 126 |
+
to control the neural stimulator to provide a therapy for atherosclerotic plaques. The neural stimulator delivers electrical signals with waveform parameters based on sensed arterial blockage levels, according to various embodiments. </p>
|
| 127 |
+
<p id="p-35" num="35">Examples of waveform parameters which can be modulated based on sensed arterial blockage levels include frequency, amplitude and phase of the waveform. According to various embodiments, the stimulation is applied to an autonomic parasympathetic target to attenuate systemic inflammation associated with atherosclerosis.</p>
|
| 128 |
+
<p id="p-36" num="36">[0029] FIG. 1B illustrates a system for applying neural stimulation therapy for atherosclerotic plaques including an external medical device <part-num-ref name="external medical device">152,</part-num-ref>
|
| 129 |
+
according to one embodiment. In this embodiment, neural stimulation therapy is delivered from the device <part-num-ref name="device">152</part-num-ref>
|
| 130 |
+
external to a human body <part-num-ref name="human body">150</part-num-ref>
|
| 131 |
+
transcutaneously to provide therapy for atherosclerotic plaques. An external lead <part-num-ref name="external lead">154</part-num-ref>
|
| 132 |
+
and electrode <part-num-ref name="and electrode">156</part-num-ref>
|
| 133 |
+
are included in an embodiment. </p>
|
| 134 |
+
<p id="p-37" num="37">
|
| 135 |
+
<confidence value="5">[</confidence>
|
| 136 |
+
0030] FIG. 1 C illustrates a system for applying neural stimulation therapy for atherosclerotic plaques including an implantable medical device (<confidence value="5">I</confidence>
|
| 137 |
+
MD) <part-num-ref name="implantable medical device (IMD)">162,</part-num-ref>
|
| 138 |
+
according to one embodiment. In this embodiment, neural stimulation therapy is delivered from the device <part-num-ref name="device">162</part-num-ref>
|
| 139 |
+
implanted in a human body <part-num-ref name="human body">150.</part-num-ref>
|
| 140 |
+
</p>
|
| 141 |
+
<p id="p-38" num="38">
|
| 142 |
+
<confidence value="5">[</confidence>
|
| 143 |
+
0031] Referring to FIG. <confidence value="2">1</confidence>
|
| 144 |
+
A, the plurality of electrodes <part-num-ref name="plurality of electrodes">120</part-num-ref>
|
| 145 |
+
includes an expandable, stent-type electrode adapted to provide mechanical and electrical anti- atherosclerotic therapy according to an embodiment. For example, the stent-type electrode can be used to provide structural support during electrical stimulation to target local inflammation. The device <part-num-ref name="device">102</part-num-ref>
|
| 146 |
+
includes a pacemaker, according to various embodiments. Thus, neural stimulation therapy can be delivered in conjunction with cardiac pacing, allowing for maintained cardiac output if autonomic stimulation has cardiac effect, such as bradycardia or asystole. </p>
|
| 147 |
+
<p id="p-39" num="39">
|
| 148 |
+
<confidence value="5">[</confidence>
|
| 149 |
+
0032<confidence value="4">]</confidence>
|
| 150 |
+
The neural stimulator <part-num-ref name="neural stimulator">104</part-num-ref>
|
| 151 |
+
delivers electrical signals intermittently, according to various embodiments. For example, the electrical signals may be <boundary-data type="header">
|
| 152 |
+
<confidence value="8">7</confidence>
|
| 153 |
+
</boundary-data>
|
| 154 |
+
<page-break num="8"/>
|
| 155 |
+
<boundary-data type="header">Attorney Docket No. 279.D42US<confidence value="8">1</confidence>
|
| 156 |
+
</boundary-data>
|
| 157 |
+
delivered in bursts for several seconds, with several seconds delay between bursts. </p>
|
| 158 |
+
<p id="p-40" num="40">The bursts and delays may be of the same or different duration, and can be adjusted by the controller based on sensor feedback, according to various embodiments.</p>
|
| 159 |
+
<p id="p-41" num="41">[0033] In various embodiments, the at least one lead <part-num-ref name="at least one lead">110</part-num-ref>
|
| 160 |
+
includes a lead with an expandable portion. In one embodiment, the lead with the expandable portion is placed in a pulmonary artery in proximity of a high concentration of baroreceptors. In various embodiments, the at least one lead <part-num-ref name="at least one lead">110</part-num-ref>
|
| 161 |
+
includes a transvascular lead. In one embodiment, the transvascular lead is placed proximal to a cardiac fat pad. The transvascular lead is placed proximal to an aortic nerve, in an embodiment. In an embodiment, the transvascular lead is placed proximal to a carotid nerve. The transvascular lead is placed proximal to a vagus nerve, in an embodiment. In various embodiments, the at least one lead <part-num-ref name="at least one lead">110</part-num-ref>
|
| 162 |
+
includes an epicardial lead. The epicardial lead is placed in a cardiac fat pad, in one embodiment. </p>
|
| 163 |
+
<p id="p-42" num="42">
|
| 164 |
+
<confidence value="5">[</confidence>
|
| 165 |
+
0034<confidence value="4">]</confidence>
|
| 166 |
+
Neural stimulation lead placement may be determined by the site of atherosclerosis. For example, in the case of coronary artery disease, local cardiac autonomic therapy may be provided via stimulation of cardiac branches of the vagus nerve or cardiac fat pads. Alternatively, the neural stimulation lead could be placed directly in the vicinity of an existing atherosclerotic plaque. </p>
|
| 167 |
+
<p id="p-43" num="43">[0035] In various embodiments, the plurality of electrodes <part-num-ref name="plurality of electrodes">120</part-num-ref>
|
| 168 |
+
includes at least one cuff electrode. The cuff electrode is placed around an aortic nerve, in one embodiment. In an embodiment, the cuff electrode is placed around a carotid nerve. </p>
|
| 169 |
+
<p id="p-44" num="44">The cuff electrode is placed around a vagus nerve, in one embodiment. According to various embodiments, the plurality of electrodes includes at least one satellite electrode having its own power supply and which is capable of wireless communication with the medical device. An example of a satellite electrode is described in U.S. patent application Serial No. 10/079,056, filed on February <part-num-ref name="satellite electrode is described in U.S. patent application Serial No. 10/079,056, filed on February">19,</part-num-ref>
|
| 170 |
+
<part-num-ref name="satellite electrode is described in U.S. patent application Serial No. 10/079,056, filed on February 19,">2002,</part-num-ref>
|
| 171 |
+
assigned to Cardiac Pacemaker, Inc. The plurality of electrodes includes at least one electrode on or in the medical device itself, according to various embodiments. </p>
|
| 172 |
+
<p id="p-45" num="45">[0036] Another aspect of the system includes means for monitoring blood pressure in a vessel to determine extent of blockage. According to various embodiments, <boundary-data type="header">
|
| 173 |
+
<confidence value="8">8</confidence>
|
| 174 |
+
</boundary-data>
|
| 175 |
+
<page-break num="9"/>
|
| 176 |
+
<boundary-data type="header">Attorney Docket No. 279.D42US<confidence value="5">1</confidence>
|
| 177 |
+
</boundary-data>
|
| 178 |
+
monitoring means include sensors as discussed in FIG. 2 below, among others. The system also includes means for applying neural stimulation based on the extent of blockage, where the stimulation adapted to provide a therapy for atherosclerotic plaques. According to various embodiments, stimulating means include, for example, a neural stimulator as discussed in FIG. <confidence value="2">l</confidence>
|
| 179 |
+
A above, among others. According to an embodiment, the means for applying neural stimulation includes at least one lead. The lead or leads are placed in a location known to activate the parasympathetic nervous system, in an embodiment. The lead or leads are placed in proximity to a site of atherosclerosis, in another embodiment. According to various embodiments, therapy for atherosclerotic plaques includes electrically stimulating an autonomic neural target to reduce inflammatory response of atherosclerosis, prevent plaque formation, and promote stability of existing plaque. </p>
|
| 180 |
+
<p id="p-46" num="46">[0037] According to an embodiment, the system also includes means for applying cardiac rhythm management (CRM) therapy. According to various embodiments, CRM therapy means includes a pacemaker or pulse generator as discussed in FIG. 3 below, among others. In an embodiment, the system also includes means for monitoring blood flow in a vessel to determine extent of blockage.</p>
|
| 181 |
+
<p id="p-47" num="47">[0038<confidence value="5">]</confidence>
|
| 182 |
+
FIG. 2 illustrates a system for applying neural stimulation therapy for atherosclerotic plaques including a sensing circuit, according to one embodiment. The depicted system <part-num-ref name="depicted system">200</part-num-ref>
|
| 183 |
+
includes a medical device <part-num-ref name="medical device">202</part-num-ref>
|
| 184 |
+
and at least one sensor <part-num-ref name="and at least one sensor">209.</part-num-ref>
|
| 185 |
+
The device <part-num-ref name="device">202</part-num-ref>
|
| 186 |
+
includes a sensing circuit <part-num-ref name="sensing circuit">208</part-num-ref>
|
| 187 |
+
to receive sensed signals representative of blood flow in a vessel to determine extent of blockage. The device also includes a neural stimulator <part-num-ref name="neural stimulator">204</part-num-ref>
|
| 188 |
+
adapted to deliver an electrical signal through at least one electrode to an autonomic neural target. The device further includes a controller <part-num-ref name="controller">206</part-num-ref>
|
| 189 |
+
to communicate with the sensing circuit and to control the neural stimulator to provide a therapy for atherosclerotic plaques. </p>
|
| 190 |
+
<p id="p-48" num="48">
|
| 191 |
+
<confidence value="5">[</confidence>
|
| 192 |
+
0039<confidence value="5">]</confidence>
|
| 193 |
+
According to various embodiments, the sensor <part-num-ref name="sensor">209</part-num-ref>
|
| 194 |
+
includes a mechanical sensor to detect blood flow. According to various embodiments, the sensor includes a device to sense blood pressure. The sensor allows therapy application to be controlled with a closed-loop feedback system. In an embodiment, the sensor includes a Doppler <boundary-data type="header">
|
| 195 |
+
<confidence value="8">9</confidence>
|
| 196 |
+
</boundary-data>
|
| 197 |
+
<page-break num="10"/>
|
| 198 |
+
<boundary-data type="header">Attorney Docket No. 279.D42US<confidence value="4">1</confidence>
|
| 199 |
+
</boundary-data>
|
| 200 |
+
flow meter placed at or near an appropriate vessel to transvascularly monitor blood flow and allow the controller to modulate therapy based on the extent of arterial blockage. The neural stimulator is adapted to connect to at least one neural stimulation lead, according to an embodiment. </p>
|
| 201 |
+
<p id="p-49" num="49">[0040] FIG. 3 illustrates an <confidence value="5">M</confidence>
|
| 202 |
+
D for applying neural stimulation therapy for atherosclerotic plaques including a pacing circuit, according to one embodiment. The <confidence value="5">I</confidence>
|
| 203 |
+
MD <part-num-ref name="IMD">302</part-num-ref>
|
| 204 |
+
includes a sensing circuit <part-num-ref name="sensing circuit">308</part-num-ref>
|
| 205 |
+
to receive sensed signals representative of blood flow in a vessel to determine extent of blockage. The device also includes a neural stimulator <part-num-ref name="neural stimulator">304</part-num-ref>
|
| 206 |
+
adapted to deliver an electrical signal th<confidence value="8">r</confidence>
|
| 207 |
+
ough at least one electrode to an autonomic neural target. The device f<confidence value="8">u</confidence>
|
| 208 |
+
rther includes a controller <part-num-ref name="controller">306</part-num-ref>
|
| 209 |
+
to communicate with the sensing circuit and to control the neural stimulator to provide a therapy for atherosclerotic plaques. A pacing circuit <part-num-ref name="pacing circuit">311</part-num-ref>
|
| 210 |
+
is included in the <confidence value="5">I</confidence>
|
| 211 |
+
MD in various embodiments. The pacing circuit is adapted to provide cardiac rhythm management therapy in conjunction with the described neural stimulation therapy. </p>
|
| 212 |
+
<p id="p-50" num="50">Combining Thera<confidence value="66">py</confidence>
|
| 213 |
+
for Atherosclerotic Plaques with Cardiac Conditioning [0041] The <confidence value="66">IM</confidence>
|
| 214 |
+
D <part-num-ref name="IMD">302</part-num-ref>
|
| 215 |
+
depicted in FIG. 3 can be implanted in patients with artery disease. These patients likely have an elevated risk for a myocardial infarction. </p>
|
| 216 |
+
<p id="p-51" num="51">According to various embodiments, the <confidence value="66">IM</confidence>
|
| 217 |
+
D is adapted to deliver therapy for atherosclerotic plaques (as described above) and is also adapted to deliver cardiac preconditioning therapy. The <confidence value="86">IM</confidence>
|
| 218 |
+
D delivers atherosclerosis therapy in combination with cardiac preconditioning therapy, according to an embodiment. According to various embodiments, the <confidence value="86">IM</confidence>
|
| 219 |
+
D begins applying preconditioning therapy when sensed arterial blockage reaches a predefined threshold. In addition, atherosclerosis therapy and preconditioning therapy are independently delivered and controlled within the IMD <part-num-ref name="IMD">302,</part-num-ref>
|
| 220 |
+
according to an embodiment. </p>
|
| 221 |
+
<p id="p-52" num="52">[0042] Cardiac preconditioning is defined herein as intermittent pacing or neural stimulation to provide prophylactic protection from potential subsequent ischemia or ischemia/reperfusion injury. Types of pacing used in cardiac preconditioning include intermittent ventricular pacing or intermittent modulation of ventricular pacing.</p>
|
| 222 |
+
<boundary-data type="header">
|
| 223 |
+
<confidence value="88">10</confidence>
|
| 224 |
+
</boundary-data>
|
| 225 |
+
<boundary-data type="header">Attorney Docket No. 279.D42US<confidence value="5">1</confidence>
|
| 226 |
+
</boundary-data>
|
| 227 |
+
<p id="p-53" num="53">
|
| 228 |
+
<page-break num="11"/>
|
| 229 |
+
Preconditioning has two phases: an early phase lasting between <part-num-ref name="early phase lasting between">5</part-num-ref>
|
| 230 |
+
minutes and <part-num-ref name="minutes and">2</part-num-ref>
|
| 231 |
+
hours after an applied stimulus; and a late phase (or second window of protection) lasting between <part-num-ref name="late phase (or second window of protection) lasting between">24</part-num-ref>
|
| 232 |
+
hours and <part-num-ref name="hours and">3</part-num-ref>
|
| 233 |
+
days after the stimulus. According to an embodiment, a sequence of pacing for maintained preconditioning includes <part-num-ref name="sequence of pacing for maintained preconditioning includes">1</part-num-ref>
|
| 234 |
+
to <part-num-ref name="to">4</part-num-ref>
|
| 235 |
+
cycles of <part-num-ref name="cycles of">3</part-num-ref>
|
| 236 |
+
to <part-num-ref name="to">20</part-num-ref>
|
| 237 |
+
minutes of pacing applied every <part-num-ref name="minutes of pacing applied every">1</part-num-ref>
|
| 238 |
+
to <part-num-ref name="to">3</part-num-ref>
|
| 239 |
+
days. Cardiac preconditioning may reduce infar<confidence value="7">c</confidence>
|
| 240 |
+
t size and contribute to the prevention and attenuation of heart failure. </p>
|
| 241 |
+
<p id="p-54" num="54">[0043<confidence value="5">]</confidence>
|
| 242 |
+
According to various embodiments, the device is adapted to deliver therapy for atherosclerotic plaques and is also adapted to deliver cardiac postconditioning therapy. The device delivers atherosclerosis therapy in combination with cardiac postconditioning therapy, according to an embodiment. According to various embodiments, the <confidence value="66">IM</confidence>
|
| 243 |
+
D begins applying postconditioning therapy when sensed arterial blockage reaches a predefined threshold. In addition, atherosclerosis therapy and postconditioning therapy are independently delivered and controlled within the <confidence value="668">IMD</confidence>
|
| 244 |
+
<part-num-ref name="IMD">302,</part-num-ref>
|
| 245 |
+
according to an embodiment. </p>
|
| 246 |
+
<p id="p-55" num="55">[0044] Cardiac postconditioning is defined herein as intermittent pacing or neural stimulation after ischemic injury to protect the heart against further damage from <confidence value="22222222222222222222">ischemia/reperfusion</confidence>
|
| 247 |
+
injury. Short intervals of ischemia during the <confidence value="22222222222">reperfision</confidence>
|
| 248 |
+
phase can provide a significant reduction in subsequent infarct size. According to an embodiment, a sequence of pacing for postconditioning commences no later than <part-num-ref name="sequence of pacing for postconditioning commences no later than">2</part-num-ref>
|
| 249 |
+
minutes after the institution of reperfusion and includes <part-num-ref name="institution of reperfusion and includes">4</part-num-ref>
|
| 250 |
+
to <part-num-ref name="to">10</part-num-ref>
|
| 251 |
+
cycles of <part-num-ref name="cycles of">10</part-num-ref>
|
| 252 |
+
seconds to <part-num-ref name="seconds to">1</part-num-ref>
|
| 253 |
+
minute of pacing. </p>
|
| 254 |
+
<p id="p-56" num="56">System for Applying Neural Stimulation Therapy for Atherosclerotic Pla<confidence value="5">q</confidence>
|
| 255 |
+
ues [0045] FIG. 4 is a schematic illustration of an implantable system for neural stimulation therapy for atherosclerotic plaques, according to one embodiment. The system includes an <confidence value="66">IM</confidence>
|
| 256 |
+
D <part-num-ref name="IMD">401,</part-num-ref>
|
| 257 |
+
an electrical lead <part-num-ref name="electrical lead">420</part-num-ref>
|
| 258 |
+
coupled to the IMD <part-num-ref name="IMD">401,</part-num-ref>
|
| 259 |
+
and at least one electrode <part-num-ref name="IMD 401, and at least one electrode">425.</part-num-ref>
|
| 260 |
+
The <confidence value="66">IM</confidence>
|
| 261 |
+
D includes a controller circuit <part-num-ref name="controller circuit">405,</part-num-ref>
|
| 262 |
+
a memory circuit <part-num-ref name="memory circuit">410,</part-num-ref>
|
| 263 |
+
a telemetry circuit <part-num-ref name="telemetry circuit">415,</part-num-ref>
|
| 264 |
+
and a neural stimulation circuit <part-num-ref name="neural stimulation circuit">435.</part-num-ref>
|
| 265 |
+
The controller circuit <part-num-ref name="controller circuit">405</part-num-ref>
|
| 266 |
+
is operable on instructions stored in the memory circuit to deliver an electrical neural stimulation therapy. Therapy is delivered by the neural stimulation <boundary-data type="header">
|
| 267 |
+
<confidence value="88">11</confidence>
|
| 268 |
+
</boundary-data>
|
| 269 |
+
<page-break num="12"/>
|
| 270 |
+
<boundary-data type="header">Attorney Docket No. 279.D42US<confidence value="8">1</confidence>
|
| 271 |
+
</boundary-data>
|
| 272 |
+
circuit <part-num-ref name="neural stimulation circuit">435</part-num-ref>
|
| 273 |
+
through the lead <part-num-ref name="lead">420</part-num-ref>
|
| 274 |
+
and the electrode(s) <part-num-ref name="electrode(s)">425.</part-num-ref>
|
| 275 |
+
The telemetry circuit <part-num-ref name="telemetry circuit">415</part-num-ref>
|
| 276 |
+
allows communication with an external programmer <part-num-ref name="external programmer">430.</part-num-ref>
|
| 277 |
+
The programmer <part-num-ref name="programmer">430</part-num-ref>
|
| 278 |
+
can be used to adjust the programmed therapy provided by the IMD <part-num-ref name="IMD">401,</part-num-ref>
|
| 279 |
+
and the IMD can report device data (such as battery and lead resistance) and therapy data (such as sense and stimulation data) to the programmer using radio telemetry, for example. </p>
|
| 280 |
+
<p id="p-57" num="57">According to various embodiments, the <confidence value="66">IM</confidence>
|
| 281 |
+
D <part-num-ref name="IMD">401</part-num-ref>
|
| 282 |
+
senses one or more physiological parameters and delivers neural stimulation therapy as disclosed in the method depicted in FIG. 6, described below. The illustrated system also includes sensor circuitry <part-num-ref name="illustrated system also includes sensor circuitry">440</part-num-ref>
|
| 283 |
+
that is coupled to at least one sensor <part-num-ref name="that is coupled to at least one sensor">445.</part-num-ref>
|
| 284 |
+
The controller circuit <part-num-ref name="controller circuit">405</part-num-ref>
|
| 285 |
+
processes sensor data from the sensor circuitry and delivers a therapy responsive to the sensor data. </p>
|
| 286 |
+
<p id="p-58" num="58">[0046] FIG. 5 illustrates a programmer <part-num-ref name="programmer">522,</part-num-ref>
|
| 287 |
+
such as the programmer <part-num-ref name="programmer">430</part-num-ref>
|
| 288 |
+
illustrated in the system of FIG. 4 or other external device to communicate with the implantable medical device(s), according to one embodiment. An example of another external device includes Personal Digital Assistants (PDAs) or personal laptop and desktop computers in an Advanced Patient Management (APM) system. The illustrated device <part-num-ref name="illustrated device">522</part-num-ref>
|
| 289 |
+
includes controller circuitry <part-num-ref name="includes controller circuitry">545</part-num-ref>
|
| 290 |
+
and a memory <part-num-ref name="memory">546.</part-num-ref>
|
| 291 |
+
The controller circuitry <part-num-ref name="controller circuitry">545</part-num-ref>
|
| 292 |
+
is capable of being implemented using hardware, software, and combinations of hardware and software. For example, according to various embodiments, the controller circuitry <part-num-ref name="controller circuitry">545</part-num-ref>
|
| 293 |
+
includes a processor to perform instructions embedded in the memory <part-num-ref name="memory">546</part-num-ref>
|
| 294 |
+
to perform a number of functions, including communicating data and/or programming instructions to the implantable devices. The illustrated device <part-num-ref name="illustrated device">522</part-num-ref>
|
| 295 |
+
further includes a transceiver <part-num-ref name="transceiver">547</part-num-ref>
|
| 296 |
+
and associated circuitry for use to communicate with an implantable device. Various embodiments have wireless communication capabilities. For example, various embodiments of the transceiver <part-num-ref name="transceiver">547</part-num-ref>
|
| 297 |
+
and associated circuitry include a telemetry coil for use to wirelessly communicate with an implantable device. The illustrated device <part-num-ref name="illustrated device">522</part-num-ref>
|
| 298 |
+
further includes a display <part-num-ref name="display">548,</part-num-ref>
|
| 299 |
+
input/output (I/O) devices <part-num-ref name="display 548, input/output (I/O) devices">549</part-num-ref>
|
| 300 |
+
such as a keyboard or mouse/pointer, and a communications interface <part-num-ref name="communications interface">550</part-num-ref>
|
| 301 |
+
for use to communicate with other devices, such as over a communication network. </p>
|
| 302 |
+
<boundary-data type="header">
|
| 303 |
+
<confidence value="88">12</confidence>
|
| 304 |
+
</boundary-data>
|
| 305 |
+
<boundary-data type="header">Attorney Docket No. 279.D42US<confidence value="8">1</confidence>
|
| 306 |
+
</boundary-data>
|
| 307 |
+
<p id="p-59" num="59">
|
| 308 |
+
<page-break num="13"/>
|
| 309 |
+
Methods [0047<confidence value="5">]</confidence>
|
| 310 |
+
FIG. 6 illustrates a flow diagram of a method of neural stimulation therapy for atherosclerotic plaques, according to one embodiment. The method <part-num-ref name="method">600</part-num-ref>
|
| 311 |
+
includes monitoring blood flow in a vessel to determine extent of blockage, at <part-num-ref name="vessel to determine extent of blockage, at">602.</part-num-ref>
|
| 312 |
+
The method also includes applying neural stimulation based on the extent of blockage, the stimulation adapted to provide a therapy for atherosclerotic plaques, at <part-num-ref name="therapy for atherosclerotic plaques, at">604.</part-num-ref>
|
| 313 |
+
</p>
|
| 314 |
+
<p id="p-60" num="60">According to an embodiment, the method also includes monitoring blood pressure in a vessel to determine extent of blockage. The method further includes applying cardiac rhythm management therapy in conjunction with neural stimulation therapy, according to various embodiments.</p>
|
| 315 |
+
<p id="p-61" num="61">
|
| 316 |
+
<confidence value="5">[</confidence>
|
| 317 |
+
0048<confidence value="5">]</confidence>
|
| 318 |
+
According to an embodiment, the method also includes applying cardiac preconditioning therapy in conjunction with neural stimulation therapy. The method further includes applying cardiac postconditioning therapy in conjunction with neural stimulation therapy, in an embodiment. According to various embodiments, preconditioning therapy is applied when the extent of blockage reaches a predefined threshold. <confidence value="2222222222222222">Postconditioning</confidence>
|
| 319 |
+
therapy is applied when the extent of blockage reaches a predefined threshold, according to an embodiment. </p>
|
| 320 |
+
<p id="p-62" num="62">[0049] According to various embodiments, applying neural stimulation includes applying electrical signals proximate a site of atherosclerosis. Applying neural stimulation includes stimulating an autonomic neural target, according to various embodiments. According to various embodiments, providing therapy for atherosclerotic plaques includes electrically stimulating an autonomic neural target to reduce inflammatory response of atherosclerosis, prevent plaque formation, and promote stability of existing plaque.</p>
|
| 321 |
+
<p id="p-63" num="63">[0050] FIG. 7 illustrates a flow diagram of a method <part-num-ref name="method">700</part-num-ref>
|
| 322 |
+
for anti-atherosclerotic therapy, according to one embodiment. According to an embodiment, a patient is identified who could benefit from anti-atherosclerotic therapy, at <part-num-ref name="patient is identified who could benefit from anti-atherosclerotic therapy, at">702.</part-num-ref>
|
| 323 |
+
Therapy for atherosclerotic plaques is delivered to the patient, including neural stimulation to elicit a parasympathetic response, at <part-num-ref name="parasympathetic response, at">704.</part-num-ref>
|
| 324 |
+
</p>
|
| 325 |
+
<boundary-data type="header">
|
| 326 |
+
<confidence value="88">13</confidence>
|
| 327 |
+
</boundary-data>
|
| 328 |
+
<boundary-data type="header">Attorney Docket No. 279.D42US<confidence value="8">1</confidence>
|
| 329 |
+
</boundary-data>
|
| 330 |
+
<p id="p-64" num="64">
|
| 331 |
+
<page-break num="14"/>
|
| 332 |
+
[0051] According to various embodiments, neural stimulation is delivered to a vagus nerve. Other neural targets can be used to elicit a parasympathetic response without departing from the scope of this disclosure. Examples of neural targets to provide parasympathetic stimulation and/or sympathetic inhibition include, but are not limited to: sympathetic ganglia, cardiac sympathetic nerves, cardiac fat pads aortic nerve and carotid sinus nerve. Neural stimulation is delivered to a vagus nerve for restenosis inhibition, plaque regression, and/or prevention of late stage thrombosis, according to various embodiments. Identifying a patient who could benefit from anti- atherosclerotic therapy includes identifying a patient with coronary artery disease and/or peripheral artery disease, such as vulnerable plaque, according to various embodiments. </p>
|
| 333 |
+
<p id="p-65" num="65">[0052<confidence value="5">]</confidence>
|
| 334 |
+
FIG. 8 illustrates a flow diagram of a method <part-num-ref name="method">800</part-num-ref>
|
| 335 |
+
for identifying a patient for anti-atherosclerotic therapy and delivering therapy, according to one embodiment. </p>
|
| 336 |
+
<p id="p-66" num="66">According to an embodiment, at least one diagnostic test is performed to determine if a patient is indicated for anti-atherosclerotic therapy, at <part-num-ref name="patient is indicated for anti-atherosclerotic therapy, at">802.</part-num-ref>
|
| 337 |
+
At least one parameter indicative of circulatory health is sensed as part of the diagnostic test, in an embodiment. Anti-atherosclerotic therapy is provided to the patient if the patient is indicated for anti-atherosclerotic therapy, at <part-num-ref name="patient is indicated for anti-atherosclerotic therapy, at">804.</part-num-ref>
|
| 338 |
+
In various embodiments, a neural target is stimulated as part of the therapy, using a predetermined stimulation schedule to inhibit vascular inflammation. </p>
|
| 339 |
+
<p id="p-67" num="67">
|
| 340 |
+
<confidence value="5">[</confidence>
|
| 341 |
+
0053<confidence value="5">]</confidence>
|
| 342 |
+
According to various embodiments, a vagal nerve is stimulated to provide therapy. Other neural targets can be used to elicit a parasympathetic response without departing from the scope of this disclosure. The neural target is stimulated using a cuff electrode, in an embodiment. In one embodiment, the neural target is stimulated transvascularly using an electrode positioned proximal the neural target in an adjacent blood vessel. In various embodiments, parasympathetic nerve traffic is stimulated and/or sympathetic nerve traffic is inhibited. The neural target is stimulated continuously, periodically, and/or intermittently, in various embodiments. </p>
|
| 343 |
+
<p id="p-68" num="68">
|
| 344 |
+
<confidence value="5">[</confidence>
|
| 345 |
+
0054] FIG. 9 illustrates a flow diagram of a method <part-num-ref name="method">900</part-num-ref>
|
| 346 |
+
for anti-atherosclerotic therapy using an implanted device, according to one embodiment. According to an <boundary-data type="header">
|
| 347 |
+
<confidence value="88">14</confidence>
|
| 348 |
+
</boundary-data>
|
| 349 |
+
<page-break num="15"/>
|
| 350 |
+
<boundary-data type="header">Attorney Docket No. 279.D42US<confidence value="8">1</confidence>
|
| 351 |
+
</boundary-data>
|
| 352 |
+
embodiment, at least one diagnostic test is performed to determine if a patient is indicated for anti-atherosclerotic therapy, at <part-num-ref name="patient is indicated for anti-atherosclerotic therapy, at">902.</part-num-ref>
|
| 353 |
+
If the patient is indicated for anti- atherosclerotic therapy, an implantable neural stimulator is implanted, at <part-num-ref name="implantable neural stimulator is implanted, at">904.</part-num-ref>
|
| 354 |
+
</p>
|
| 355 |
+
<p id="p-69" num="69">Implanting a stimulator includes positioning at least one electrode for use in stimulating a vagus nerve of the patient, according to an embodiment. Neural stimulation is delivered to the vagus nerve using the implantable neural stimulator according to a programmed stimulation schedule to inhibit vascular inflammation, at <part-num-ref name="programmed stimulation schedule to inhibit vascular inflammation, at">906.</part-num-ref>
|
| 356 |
+
</p>
|
| 357 |
+
<p id="p-70" num="70">
|
| 358 |
+
<confidence value="5">[</confidence>
|
| 359 |
+
0055] According to various embodiments, a number of diagnostic tests can be used to determine if a patient is indicated for anti-atherosclerotic therapy. Examples include, but are not limited to: a blood test, a cardiac perfusion scan, a coronary angiogram, an echocardiogram, a stress echocardiogram, an electrocardiogram, a stress electrocardiogram, or a chest x-ray. According to various embodiments, anti- atherosclerotic neural stimulation is delivered in conjunction with an additional therapy. Examples of additional therapy include, but are not limited to, angioplasty or stent placement. </p>
|
| 360 |
+
<p id="p-71" num="71">[0056<confidence value="5">]</confidence>
|
| 361 |
+
Although specific embodiments have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art that any arrangement which is calculated to achieve the same purpose may be substituted for the specific embodiment shown. It is to be understood that the above description is intended to be illustrative, and not restrictive. The scope of the present subject matter should be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled. </p>
|
| 362 |
+
<boundary-data type="header">
|
| 363 |
+
<confidence value="88">15</confidence>
|
| 364 |
+
</boundary-data>
|
| 365 |
+
</description>
|
| 366 |
+
</us-patent-application>
|
| 367 |
+
|
applicant/11742378.xml
ADDED
|
@@ -0,0 +1,1009 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>11742378</doc-number>
|
| 8 |
+
<date>2007-04-30</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<boundary-data type="header">20724</boundary-data>
|
| 14 |
+
<heading id="h-1">ENGINE-DRIVEN AIR COMPRESSOR LOAD CONTROL</heading>
|
| 15 |
+
<heading id="h-2">SYSTEM AND METHOD</heading>
|
| 16 |
+
<heading id="h-3">BACKGROUND</heading>
|
| 17 |
+
<p id="p-1" num="1">
|
| 18 |
+
<confidence value="5">[</confidence>
|
| 19 |
+
0001<confidence value="5">]</confidence>
|
| 20 |
+
The invention relates generally to welding systems and more particularly to welding systems utilizing an engine coupled to an air compressor and welding generator in a single unit. </p>
|
| 21 |
+
<p id="p-2" num="2">
|
| 22 |
+
<confidence value="5">[</confidence>
|
| 23 |
+
0002<confidence value="5">1</confidence>
|
| 24 |
+
Welding systems generally use an electrical current (e.g., welding current) to perform welding. The electrical current may be provided by an electrical power source (such as a power grid or battery) or an electrical generator coupled to a mechanical power source. Examples of mechanical power sources include engines that output power via a rotating drive shaft<confidence value="5">.</confidence>
|
| 25 |
+
Typically, the drive shaft is coupled to other devices that consume the energy provided by the rotating drive. For instance, welding systems often include internal combustion engines (such as gas or diesel engines) and an alternator or generator configured to convert the mechanical energy generated by the engine into electrical energy (e.g., electrical current). These systems are often referred to as engine-driven welding generators. An advantage of an engine- driven system is the potential portability of the system. For instance, welding systems that employ a generator coupled to an engine are typically configured as standalone units that do not have connections to a supplemental power source, such as a power grid. This may be useful for systems that are traditionally operated at remote worksites. </p>
|
| 26 |
+
<p id="p-3" num="3">
|
| 27 |
+
<confidence value="5">[</confidence>
|
| 28 |
+
0003<confidence value="5">1</confidence>
|
| 29 |
+
In addition to needing a source of welding current at a worksite, welding operators often desire other outputs to more efficiently complete a job. For example, a welding operator may also use compressed air to operate plasma cutters, air tools and the like. Typically, compressed air is provided via a standalone air supply. <confidence value="8">T</confidence>
|
| 30 |
+
hus<confidence value="5">,</confidence>
|
| 31 |
+
a welding operator may use, both, a standalone engine-driven welding generator and a standalone air supply. The independence of the two units may increase the amount of time and labor involved with setup, transportation, and so forth. In addition, the independence of the two units may result in an increased amount of maintenance and repair costs due to duplication of parts. Unfortunately, existing welding generators <boundary-data type="header">
|
| 32 |
+
<confidence value="7">1</confidence>
|
| 33 |
+
</boundary-data>
|
| 34 |
+
<page-break num="2"/>
|
| 35 |
+
<boundary-data type="header">
|
| 36 |
+
<confidence value="88">20</confidence>
|
| 37 |
+
724 </boundary-data>
|
| 38 |
+
may not perform properly with the addition of an air compressor due to the increased load on the engine. For example, the increased <confidence value="8">l</confidence>
|
| 39 |
+
oad due to an air compressor may result in a drop in power output to a welding torch, which can cause problems with the welding process<confidence value="5">.</confidence>
|
| 40 |
+
</p>
|
| 41 |
+
<heading id="h-4">BRIEF DESCRIPTION</heading>
|
| 42 |
+
<p id="p-4" num="4">
|
| 43 |
+
<confidence value="5">[</confidence>
|
| 44 |
+
0004<confidence value="5">]</confidence>
|
| 45 |
+
A system, in one embodiment, includes an engine, a generator coupled to the engine, a compressor coupled to the engine, and a controller configured to soft start the compressor. A method, in another embodiment, includes soft starting an air compressor in a portable welding unit having the air compressor, an engine coupled to the air compressor, and a welding generator coupled to the engine<confidence value="5">.</confidence>
|
| 46 |
+
</p>
|
| 47 |
+
<heading id="h-5">DRAWINGS</heading>
|
| 48 |
+
<p id="p-5" num="5">[000<confidence value="52">5]</confidence>
|
| 49 |
+
These and other features, aspects, and advantages of the present invention will become better understood when the following detailed description is read with reference to the accompanying drawings in which like characters represent like parts throughout the drawings, wherein: </p>
|
| 50 |
+
<p id="p-6" num="6">[0006<confidence value="5">1</confidence>
|
| 51 |
+
FIG. 1 is a partial perspective view of an exemplary engine-driven welding generator/compressor system, wherein two top access panels are rotated to open positions and a side access panel is removed to reveal various internal features in accordance with embodiments of the present invention; </p>
|
| 52 |
+
<p id="p-7" num="7">
|
| 53 |
+
<confidence value="5">[</confidence>
|
| 54 |
+
0007<confidence value="5">]</confidence>
|
| 55 |
+
FIG. 2 is another partial perspective view of the welding generator/compressor system as illustrated in F<confidence value="5">I</confidence>
|
| 56 |
+
G. 1, wherein an entire top access panel assembly is removed to further illustrate various internal features in accordance with embodiments of the present invention; </p>
|
| 57 |
+
<p id="p-8" num="8">
|
| 58 |
+
<confidence value="5">[</confidence>
|
| 59 |
+
0008<confidence value="5">1</confidence>
|
| 60 |
+
FIG. 3 is a side view of the welding generator/compressor system as illustrated in FIG. 1, wherein the two top access panels are rotated to closed positions and the side access panel is removed to further illustrate various internal features in accordance with embodiments of the present invention; </p>
|
| 61 |
+
<boundary-data type="header">
|
| 62 |
+
<confidence value="8">2</confidence>
|
| 63 |
+
</boundary-data>
|
| 64 |
+
<boundary-data type="header">20724</boundary-data>
|
| 65 |
+
<p id="p-9" num="9">
|
| 66 |
+
<page-break num="3"/>
|
| 67 |
+
<confidence value="4">1</confidence>
|
| 68 |
+
0009<confidence value="5">]</confidence>
|
| 69 |
+
FIG. 4 is a schematic o<confidence value="5">f</confidence>
|
| 70 |
+
an exemplary embodiment of the welding generator/compressor system as illustrated in FIGS. 1-3; and <confidence value="5">[</confidence>
|
| 71 |
+
0010<confidence value="5">1</confidence>
|
| 72 |
+
<confidence value="8586">FTG.</confidence>
|
| 73 |
+
<part-num-ref name="welding generator/compressor system as illustrated in FIGS. 1-3; and [00101 FTG.">5</part-num-ref>
|
| 74 |
+
is a flowchart il<confidence value="8">l</confidence>
|
| 75 |
+
ustrating an exemplary method of operating the engine-driven welding generator/compressor system as illustrated in FIGS. 1-3. </p>
|
| 76 |
+
<heading id="h-6">DETAILED DESCRIPTION</heading>
|
| 77 |
+
<p id="p-10" num="10">
|
| 78 |
+
<confidence value="5">[</confidence>
|
| 79 |
+
0011<confidence value="5">1</confidence>
|
| 80 |
+
Referring now to the drawings, FIGS. 1-3 illustrate an engine-driven welding generator/compressor system <part-num-ref name="engine-driven welding generator/compressor system">10</part-num-ref>
|
| 81 |
+
having an engine <part-num-ref name="engine">12</part-num-ref>
|
| 82 |
+
drivingly coupled to a welding generator <part-num-ref name="welding generator">14</part-num-ref>
|
| 83 |
+
and an air compressor <part-num-ref name="air compressor">16</part-num-ref>
|
| 84 |
+
in a single enclosure <part-num-ref name="single enclosure">
|
| 85 |
+
<confidence value="65">18</confidence>
|
| 86 |
+
</part-num-ref>
|
| 87 |
+
in accordance with an exemplary embodiment of the present technique. FIG. <confidence value="4">1</confidence>
|
| 88 |
+
is a partial perspective view of the system <part-num-ref name="system">10</part-num-ref>
|
| 89 |
+
with side access panels removed and top access panels or hatches rotated to open positions<confidence value="5">.</confidence>
|
| 90 |
+
FIG<confidence value="5">.</confidence>
|
| 91 |
+
2 is another partial perspective view of the system <part-num-ref name="system">10</part-num-ref>
|
| 92 |
+
as illustrated in FIG. 1, wherein the entire top access panel assembly is removed to provide a better view of the internal features of the system <part-num-ref name="system">10.</part-num-ref>
|
| 93 |
+
FIG. 3 is a side view of the system <part-num-ref name="system">10</part-num-ref>
|
| 94 |
+
as illustrated in FIGS. I and <part-num-ref name="as illustrated in FIGS. I and">2.</part-num-ref>
|
| 95 |
+
As depicted, the system <part-num-ref name="system">10</part-num-ref>
|
| 96 |
+
is configured to provide multiple outputs, including welding current, alternating current (AC) power, and compressed air. </p>
|
| 97 |
+
<p id="p-11" num="11">[0012<confidence value="5">]</confidence>
|
| 98 |
+
As discussed in detail below<confidence value="5">,</confidence>
|
| 99 |
+
the illustrated system includes a variety of features to improve serviceability, reliability, controllability, and integration of the air compressor <part-num-ref name="air compressor">16</part-num-ref>
|
| 100 |
+
within the single enclosure <part-num-ref name="single enclosure">18</part-num-ref>
|
| 101 |
+
of the system <part-num-ref name="system">10<confidence value="5">,</confidence>
|
| 102 |
+
</part-num-ref>
|
| 103 |
+
For example, the illustrated system <part-num-ref name="illustrated system">10</part-num-ref>
|
| 104 |
+
may include a top side oil fill to enable access at the top of the system <part-num-ref name="system">10,</part-num-ref>
|
| 105 |
+
rather than a lower or more inaccessible oil fill location. The illustrated system <part-num-ref name="illustrated system">10</part-num-ref>
|
| 106 |
+
also may include unique control features, such as a load priority control configured to monitor various loads (e.g., generator <part-num-ref name="generator">14,</part-num-ref>
|
| 107 |
+
compressor <part-num-ref name="generator 14, compressor">
|
| 108 |
+
<confidence value="66">16</confidence>
|
| 109 |
+
, </part-num-ref>
|
| 110 |
+
external loads, etc.) on the engine <part-num-ref name="engine">12,</part-num-ref>
|
| 111 |
+
identify possible overload conditions, and adjust the various loads based on priority levels. The control features also may include a specific air compressor load control, which may be configured to reduce the engine speed and/or gradually engage (e.g., via a clutch) the air compressor <part-num-ref name="air compressor">
|
| 112 |
+
<confidence value="66">16</confidence>
|
| 113 |
+
</part-num-ref>
|
| 114 |
+
during start up (e<confidence value="5885">.g.,</confidence>
|
| 115 |
+
a soft start control). Furthermore, the control features may include a specific air compressor control regulator, which may be mounted directly on a control panel (e.g., a front <boundary-data type="header">
|
| 116 |
+
<confidence value="8">3</confidence>
|
| 117 |
+
</boundary-data>
|
| 118 |
+
<page-break num="4"/>
|
| 119 |
+
<boundary-data type="header">
|
| 120 |
+
<confidence value="88568">20724</confidence>
|
| 121 |
+
</boundary-data>
|
| 122 |
+
panel) of the system <part-num-ref name="system">10</part-num-ref>
|
| 123 |
+
rather than being in an inaccessible position well within the system <part-num-ref name="system">10.</part-num-ref>
|
| 124 |
+
The system <part-num-ref name="system">10</part-num-ref>
|
| 125 |
+
also may include a battery and/or a battery charge system, which may include features to monitor conditions of the battery (e.g., internal or external to the system <part-num-ref name="system">10)</part-num-ref>
|
| 126 |
+
and to adjust the characteristics of the charge (e.g., variable output level, duration, etc.). </p>
|
| 127 |
+
<p id="p-12" num="12">
|
| 128 |
+
<confidence value="5">(</confidence>
|
| 129 |
+
0013<confidence value="5">1</confidence>
|
| 130 |
+
In an embodiment, discussed in greater detail below, the system <part-num-ref name="system">10</part-num-ref>
|
| 131 |
+
includes an electric clutch coupled to the compressor <part-num-ref name="compressor">16</part-num-ref>
|
| 132 |
+
drive shaft and an electronic governor configured to control the speed o<confidence value="5">f</confidence>
|
| 133 |
+
the engine <part-num-ref name="engine">12<confidence value="5">.</confidence>
|
| 134 |
+
</part-num-ref>
|
| 135 |
+
As depicted, the electric clutch and the governor are both controlled by an electronic control<confidence value="5">.</confidence>
|
| 136 |
+
During operation of the system <part-num-ref name="system">10,</part-num-ref>
|
| 137 |
+
the electronic control provides signals to coordinate the operating speed of the engine <part-num-ref name="engine">12</part-num-ref>
|
| 138 |
+
and the operation of the air compressor <part-num-ref name="air compressor">16.</part-num-ref>
|
| 139 |
+
For example, as discussed below, the electronic control may direct the electronic governor to reduce the engine speed before engaging the electric clutch. Thus, the startup of the air compressor <part-num-ref name="air compressor">16</part-num-ref>
|
| 140 |
+
may be accomplished during operation at lower engine speeds to prevent the shock- loading that may otherwise be present if the air compressor <part-num-ref name="air compressor">16</part-num-ref>
|
| 141 |
+
is engaged while the engine <part-num-ref name="engine">12</part-num-ref>
|
| 142 |
+
is operating at an increased operating speed. Further, embodiments discussed below include multiple control schemes and user inputs that may be employed to increase performance and the functionality of the system <part-num-ref name="system">10.</part-num-ref>
|
| 143 |
+
</p>
|
| 144 |
+
<p id="p-13" num="13">[0014<confidence value="2">]</confidence>
|
| 145 |
+
In certain embodiments, the system <part-num-ref name="system">10</part-num-ref>
|
| 146 |
+
may be described as an air pack welding system (e.g<confidence value="5">.</confidence>
|
| 147 |
+
, A<confidence value="4">I</confidence>
|
| 148 |
+
RPAK). The engine <part-num-ref name="engine">12</part-num-ref>
|
| 149 |
+
provides output power (e<confidence value="686">.g.</confidence>
|
| 150 |
+
, a mechanical output) to drive both the welding generator <part-num-ref name="welding generator">14</part-num-ref>
|
| 151 |
+
and the air compressor <part-num-ref name="air compressor">16<confidence value="5">,</confidence>
|
| 152 |
+
</part-num-ref>
|
| 153 |
+
<confidence value="5">I</confidence>
|
| 154 |
+
n the illustrated embodiment, the generator <part-num-ref name="generator">14</part-num-ref>
|
| 155 |
+
is coupled to one side of the engine <part-num-ref name="engine">12,</part-num-ref>
|
| 156 |
+
while the compressor <part-num-ref name="compressor">16</part-num-ref>
|
| 157 |
+
is independently coupled to an opposite side of the engine <part-num-ref name="engine">12.</part-num-ref>
|
| 158 |
+
Thus, the engine <part-num-ref name="engine">12</part-num-ref>
|
| 159 |
+
is sandwiched between the generator <part-num-ref name="generator">14</part-num-ref>
|
| 160 |
+
and the compressor <part-num-ref name="compressor">16.</part-num-ref>
|
| 161 |
+
In addition, the engine <part-num-ref name="engine">12</part-num-ref>
|
| 162 |
+
may be mounted independently from the compressor <part-num-ref name="compressor">16,</part-num-ref>
|
| 163 |
+
such that the two are mechanically isolated from one another. As discussed in further detail below, the isolation between the compressor <part-num-ref name="compressor">16</part-num-ref>
|
| 164 |
+
and the engine <part-num-ref name="engine">12</part-num-ref>
|
| 165 |
+
may be addressed with a suitable engine-to-compressor coupling system, such as a geometrically adjustable coupling. The geometrically adjustable coupling may include a tensioning system coupled to a belt and pulley system, a special resilient or spring-like belt, a clutch, or a combination thereof, to provide some degree <boundary-data type="header">
|
| 166 |
+
<confidence value="8">4</confidence>
|
| 167 |
+
</boundary-data>
|
| 168 |
+
<page-break num="5"/>
|
| 169 |
+
<boundary-data type="header">20724</boundary-data>
|
| 170 |
+
of flexibility, positional adjustability, or play. Thus, the geometrically adjustable coupling is configured to maintain a connection between the compressor <part-num-ref name="compressor">16</part-num-ref>
|
| 171 |
+
and the engine <part-num-ref name="engine">12</part-num-ref>
|
| 172 |
+
despite variations in distance, vibrations, and so forth. In other words, the geometrically adjustable coupling provides a resilient or distance adjustable connection between the engine <part-num-ref name="engine">12</part-num-ref>
|
| 173 |
+
and the compressor <part-num-ref name="compressor">16</part-num-ref>
|
| 174 |
+
<confidence value="5">[</confidence>
|
| 175 |
+
0015<confidence value="5">]</confidence>
|
| 176 |
+
As described below, the power from the engine <part-num-ref name="engine">12</part-num-ref>
|
| 177 |
+
operates both the generator <part-num-ref name="generator">14</part-num-ref>
|
| 178 |
+
and the air compressor <part-num-ref name="air compressor">16</part-num-ref>
|
| 179 |
+
via a <confidence value="8">f</confidence>
|
| 180 |
+
irst shaft <part-num-ref name="first shaft">20</part-num-ref>
|
| 181 |
+
and a second shaft <part-num-ref name="second shaft">22</part-num-ref>
|
| 182 |
+
(e.g., stub shaft), respectively. In some embodiments, these shafts <part-num-ref name="stub shaft), respectively. In some embodiments, these shafts">20</part-num-ref>
|
| 183 |
+
and <part-num-ref name="and">22</part-num-ref>
|
| 184 |
+
may be independent from one another, while in other embodiments shafts <part-num-ref name="may be independent from one another, while in other embodiments shafts">20</part-num-ref>
|
| 185 |
+
and <part-num-ref name="and">22</part-num-ref>
|
| 186 |
+
may be part of a single shaft extending through the engine <part-num-ref name="engine">12.</part-num-ref>
|
| 187 |
+
As illustrated, the shafts <part-num-ref name="shafts">20</part-num-ref>
|
| 188 |
+
and <part-num-ref name="and">22</part-num-ref>
|
| 189 |
+
extend out of opposite sides of the engine <part-num-ref name="engine">12.</part-num-ref>
|
| 190 |
+
These shafts <part-num-ref name="engine 12. These shafts">20</part-num-ref>
|
| 191 |
+
and <part-num-ref name="and">22</part-num-ref>
|
| 192 |
+
may be directly or indirectly coupled to one or more driven mechanisms. For example, an indirect coupling may include a belt and pulley system, a gear system, or a chain and sprocket system. In the present embodiment, the first shaft <part-num-ref name="first shaft">20</part-num-ref>
|
| 193 |
+
couples directly to the generator <part-num-ref name="generator">14,</part-num-ref>
|
| 194 |
+
while the second stub shaft <part-num-ref name="second stub shaft">22</part-num-ref>
|
| 195 |
+
couples indirectly to the compressor <part-num-ref name="compressor">16.</part-num-ref>
|
| 196 |
+
</p>
|
| 197 |
+
<p id="p-14" num="14">However, either arrangement can be used for the connection between the engine <part-num-ref name="engine">12</part-num-ref>
|
| 198 |
+
and the generator <part-num-ref name="generator">14</part-num-ref>
|
| 199 |
+
and/or the compressor <part-num-ref name="compressor">
|
| 200 |
+
<confidence value="668">16.</confidence>
|
| 201 |
+
</part-num-ref>
|
| 202 |
+
</p>
|
| 203 |
+
<p id="p-15" num="15">[0016<confidence value="4">]</confidence>
|
| 204 |
+
For example, as will be discussed in greater detail below, the engine <part-num-ref name="engine">12</part-num-ref>
|
| 205 |
+
is coupled to the compressor <part-num-ref name="compressor">16</part-num-ref>
|
| 206 |
+
via a belt and pulley system including the stub shaft <part-num-ref name="stub shaft">22,</part-num-ref>
|
| 207 |
+
a pulley <part-num-ref name="pulley">24</part-num-ref>
|
| 208 |
+
coupled to the shaft <part-num-ref name="shaft">22,</part-num-ref>
|
| 209 |
+
a compressor drive shaft <part-num-ref name="compressor drive shaft">26</part-num-ref>
|
| 210 |
+
coupled to the compressor <part-num-ref name="compressor">16,</part-num-ref>
|
| 211 |
+
a compressor pulley <part-num-ref name="compressor pulley">28</part-num-ref>
|
| 212 |
+
coupled to the shaft <part-num-ref name="shaft">26,</part-num-ref>
|
| 213 |
+
and a drive belt <part-num-ref name="drive belt">30</part-num-ref>
|
| 214 |
+
extending about the pulleys <part-num-ref name="pulleys">24</part-num-ref>
|
| 215 |
+
and <part-num-ref name="and">28<confidence value="5">.</confidence>
|
| 216 |
+
</part-num-ref>
|
| 217 |
+
Therefore, the engine <part-num-ref name="engine">12</part-num-ref>
|
| 218 |
+
is capable of providing power to the generator <part-num-ref name="generator">14</part-num-ref>
|
| 219 |
+
and the air compressor <part-num-ref name="air compressor">16</part-num-ref>
|
| 220 |
+
simultaneously. In the illustrated embodiment, the engine <part-num-ref name="engine">12</part-num-ref>
|
| 221 |
+
rotates the stub shaft <part-num-ref name="stub shaft">22</part-num-ref>
|
| 222 |
+
to transmit rotation and torque via the pulleys <part-num-ref name="pulleys">24</part-num-ref>
|
| 223 |
+
and <part-num-ref name="and">28</part-num-ref>
|
| 224 |
+
and drive belt <part-num-ref name="and drive belt">30</part-num-ref>
|
| 225 |
+
to the compressor drive shaft <part-num-ref name="compressor drive shaft">26</part-num-ref>
|
| 226 |
+
coupled to the air compressor <part-num-ref name="air compressor">16.</part-num-ref>
|
| 227 |
+
Accordingly, the mechanical energy generated by the engine <part-num-ref name="engine">12</part-num-ref>
|
| 228 |
+
operates the air compressor <part-num-ref name="air compressor">16<confidence value="5">,</confidence>
|
| 229 |
+
</part-num-ref>
|
| 230 |
+
As discussed in detail below, in certain embodiments, the air compressor <part-num-ref name="air compressor">16</part-num-ref>
|
| 231 |
+
includes a rotary screw compressor. Thus, the air compressor <part-num-ref name="air compressor">16</part-num-ref>
|
| 232 |
+
and the system <part-num-ref name="system">10</part-num-ref>
|
| 233 |
+
may be capable of continuously providing large volumes of compressed air <part-num-ref name="may be capable of continuously providing large volumes of compressed air">16</part-num-ref>
|
| 234 |
+
to a desired application, such as a welding application, without any need for an intermediate storage tank. </p>
|
| 235 |
+
<boundary-data type="header">
|
| 236 |
+
<confidence value="8">5</confidence>
|
| 237 |
+
</boundary-data>
|
| 238 |
+
<boundary-data type="header">20724</boundary-data>
|
| 239 |
+
<p id="p-16" num="16">
|
| 240 |
+
<page-break num="6"/>
|
| 241 |
+
<confidence value="5">[</confidence>
|
| 242 |
+
0017<confidence value="4">]</confidence>
|
| 243 |
+
The engine <part-num-ref name="engine">12</part-num-ref>
|
| 244 |
+
includes a power source configured to provide power to the generator <part-num-ref name="generator">14</part-num-ref>
|
| 245 |
+
and the air compressor <part-num-ref name="air compressor">16.</part-num-ref>
|
| 246 |
+
In an embodiment, the engine <part-num-ref name="engine">12</part-num-ref>
|
| 247 |
+
may include a combustion engine powered by gas, diesel, LP fuel, natural gas, or other fuels, and driving one or more drive shafts, e<confidence value="6865">.g.,</confidence>
|
| 248 |
+
<part-num-ref name="">20</part-num-ref>
|
| 249 |
+
a<confidence value="5">n</confidence>
|
| 250 |
+
d <part-num-ref name="and">22.</part-num-ref>
|
| 251 |
+
For example, the engine <part-num-ref name="engine">12</part-num-ref>
|
| 252 |
+
may include an industrial gas/diesel engine configured to output anywhere from about <part-num-ref name="industrial gas/diesel engine configured to output anywhere from about">24</part-num-ref>
|
| 253 |
+
horsepower (Hp) to about <part-num-ref name="horsepower (Hp) to about">64</part-num-ref>
|
| 254 |
+
<confidence value="222">i-i</confidence>
|
| 255 |
+
p. Generally, the weight of such an engine <part-num-ref name="engine">12</part-num-ref>
|
| 256 |
+
may vary with the size and Hp rating of the engine. For example, a <part-num-ref name="">64</part-num-ref>
|
| 257 |
+
Hp diesel engine driven unit may weigh approximately <part-num-ref name="Hp diesel engine driven unit may weigh approximately">1900</part-num-ref>
|
| 258 |
+
lbs., whereas a similar <part-num-ref name="similar">24</part-num-ref>
|
| 259 |
+
Hp gasoline engine driven unit may weigh less than approximately <part-num-ref name="Hp gasoline engine driven unit may weigh less than approximately">1000</part-num-ref>
|
| 260 |
+
lbs. Thus, the portable system <part-num-ref name="portable system">10</part-num-ref>
|
| 261 |
+
may benefit from the use of a smaller engine <part-num-ref name="smaller engine">12.</part-num-ref>
|
| 262 |
+
</p>
|
| 263 |
+
<p id="p-17" num="17">[0018] As discussed previously, embodiments may include a generator <part-num-ref name="generator">14</part-num-ref>
|
| 264 |
+
coupled to the engine <part-num-ref name="engine">12.</part-num-ref>
|
| 265 |
+
Thus, the generator <part-num-ref name="generator">14</part-num-ref>
|
| 266 |
+
may convert the power output (e.g., mechanical energy) of the engine <part-num-ref name="engine">12</part-num-ref>
|
| 267 |
+
to electrical power<confidence value="5">.</confidence>
|
| 268 |
+
Generally, the generator <part-num-ref name="generator">1<confidence value="8">4</confidence>
|
| 269 |
+
</part-num-ref>
|
| 270 |
+
includes a device configured to convert a rotating magnetic field into an electrical current (e.g., AC generator)<confidence value="4">,</confidence>
|
| 271 |
+
The generator <part-num-ref name="generator">14</part-num-ref>
|
| 272 |
+
includes a rotor (rotating portion of the generator) and a stator (the stationary portion of the generator). For example, the rotor of the generator <part-num-ref name="generator">14</part-num-ref>
|
| 273 |
+
may include the rotating drive shaft <part-num-ref name="rotating drive shaft">20</part-num-ref>
|
| 274 |
+
disposed in a single stator configured to create an electrical current (e.g., welding current) from the rotation of the magnetic field. In an embodiment, the generator may include a four- pole rotor and three-phase weld output configured to provide beneficial welding characteristics. Further, the generator <part-num-ref name="generator">14</part-num-ref>
|
| 275 |
+
may include a plurality of independent winding sections in the rotors and/or stators, such that the generator <part-num-ref name="generator">14</part-num-ref>
|
| 276 |
+
is configured to output multiple electrical outputs having different characteristics<confidence value="5">.</confidence>
|
| 277 |
+
For example<confidence value="5">,</confidence>
|
| 278 |
+
the generator <part-num-ref name="generator">14</part-num-ref>
|
| 279 |
+
may include a first section configured to drive a welding current to a welder and a second section configured to drive a current for other AC outputs. As suggested above, multiple generators <part-num-ref name="current for other AC outputs. As suggested above, multiple generators">14</part-num-ref>
|
| 280 |
+
may be connected to the drive shaft <part-num-ref name="drive shaft">20</part-num-ref>
|
| 281 |
+
or stub shaft <part-num-ref name="or stub shaft">22.</part-num-ref>
|
| 282 |
+
</p>
|
| 283 |
+
<p id="p-18" num="18">
|
| 284 |
+
<confidence value="5">1</confidence>
|
| 285 |
+
0019<confidence value="5">1</confidence>
|
| 286 |
+
Also coupled to the engine <part-num-ref name="engine">12,</part-num-ref>
|
| 287 |
+
the air compressor <part-num-ref name="air compressor">16</part-num-ref>
|
| 288 |
+
may provide a continuous source of compressed air for use in plasma cutting, pneumatic tools, inflating a tire, blowing-off/cleaning a work piece, and the like. For example<confidence value="5">,</confidence>
|
| 289 |
+
<confidence value="8">a</confidence>
|
| 290 |
+
welding operator may use compressed air as a high speed gas ejected from the nozzle <boundary-data type="header">
|
| 291 |
+
<confidence value="8">6</confidence>
|
| 292 |
+
</boundary-data>
|
| 293 |
+
<page-break num="7"/>
|
| 294 |
+
<boundary-data type="header">20724</boundary-data>
|
| 295 |
+
of a plasma torch, or may use compressed air to operate tools, such as pneumatic impact wrenches, pneumatic spray guns, pneumatic lifts, and pneumatic air chisels. </p>
|
| 296 |
+
<p id="p-19" num="19">In the illustrated embodiment, the air compressor <part-num-ref name="air compressor">16</part-num-ref>
|
| 297 |
+
may be described as a continuous air supply compressor, an indirect mount air compressor, or both<confidence value="5">.</confidence>
|
| 298 |
+
For example, certain embodiments of the system <part-num-ref name="system">10</part-num-ref>
|
| 299 |
+
use a type of the compressor <part-num-ref name="compressor">16</part-num-ref>
|
| 300 |
+
that is not a piston-type air compressor mounted directly to the engine <part-num-ref name="engine">12.</part-num-ref>
|
| 301 |
+
In an embodiment, the air compressor <part-num-ref name="air compressor">16</part-num-ref>
|
| 302 |
+
may include a rotary screw compressor or another suitable compressor <part-num-ref name="rotary screw compressor or another suitable compressor">16</part-num-ref>
|
| 303 |
+
configured to supply a continuous flow of compressed air without the need for an intermediate storage tank<confidence value="5">,</confidence>
|
| 304 |
+
[0020<confidence value="2">j</confidence>
|
| 305 |
+
Rotary screw compressors may include a type of gas compressor that has a rotary type positive displacement mechanism. The rotary screw compressor typically includes one or more screws, which rotate within an enclosure to gradually shrink a series of passages defined by threads of the screws and the surrounding enclosure<confidence value="5">.</confidence>
|
| 306 |
+
</p>
|
| 307 |
+
<p id="p-20" num="20">For example, the rotary screw compressor may include a plurality (e.g., pair) of counter rotating screws, which <confidence value="222222222">intermesh</confidence>
|
| 308 |
+
with one another to progressively reduce air volumes between the intermeshed threads (e.g., a series of shrinking volumes of air). </p>
|
| 309 |
+
<p id="p-21" num="21">For example, air is drawn in through an inlet port in the enclosure, the gas is captured in a cavity, the gas is compressed as the cavity reduces in volume, and the gas is finally discharged through another port in the enclosure. The design of a rotary screw air compressor <part-num-ref name="rotary screw air compressor">16</part-num-ref>
|
| 310 |
+
generally provides for high volumes of compressed gas in a continuous manner without the need for an intermediate storage tank. </p>
|
| 311 |
+
<p id="p-22" num="22">[0021<confidence value="5">1</confidence>
|
| 312 |
+
Accordingly, the rotary screw air compressor <part-num-ref name="rotary screw air compressor">16</part-num-ref>
|
| 313 |
+
may provide a direct supply of compressed air on-demand to a desired application. For example, a plasma cutter may consume air directly from the unit without the air being compressed into a tank, as generally done by piston-driven air compressors. However, an embodiment including a rotary screw air compressor <part-num-ref name="rotary screw air compressor">16</part-num-ref>
|
| 314 |
+
may include an air tank configured to store the compressed air. For example, a user may want to generate air for a given period and store the compressed air for a later use. </p>
|
| 315 |
+
<p id="p-23" num="23">
|
| 316 |
+
<confidence value="25">10</confidence>
|
| 317 |
+
022] Further, the rotary screw air compressor <part-num-ref name="rotary screw air compressor">16</part-num-ref>
|
| 318 |
+
may be configured to operate at high speeds and, thus, may use less gearing and space to couple the rotary screw air <boundary-data type="header">
|
| 319 |
+
<confidence value="8">7</confidence>
|
| 320 |
+
</boundary-data>
|
| 321 |
+
<page-break num="8"/>
|
| 322 |
+
<boundary-data type="header">20724</boundary-data>
|
| 323 |
+
compressor <part-num-ref name="rotary screw air compressor">16</part-num-ref>
|
| 324 |
+
to the engine <part-num-ref name="engine">12.</part-num-ref>
|
| 325 |
+
For example, in an embodiment, the system <part-num-ref name="system">10</part-num-ref>
|
| 326 |
+
may include a rotary screw air compressor <part-num-ref name="rotary screw air compressor">16</part-num-ref>
|
| 327 |
+
operating at speed near the engine speed, such as <part-num-ref name="engine speed, such as">4000</part-num-ref>
|
| 328 |
+
rpm<confidence value="5">.</confidence>
|
| 329 |
+
Thus, the pulley <part-num-ref name="pulley">24</part-num-ref>
|
| 330 |
+
and the compressor pulley <part-num-ref name="compressor pulley">18</part-num-ref>
|
| 331 |
+
may include similar <confidence value="4">I</confidence>
|
| 332 |
+
to <part-num-ref name="may include similar I to">1</part-num-ref>
|
| 333 |
+
ratios and not use a sign<confidence value="8">i</confidence>
|
| 334 |
+
ficantly larger compressor pulley <part-num-ref name="significantly larger compressor pulley">28</part-num-ref>
|
| 335 |
+
to step down the engine speed to accommodate the air compressor <part-num-ref name="air compressor">16.</part-num-ref>
|
| 336 |
+
</p>
|
| 337 |
+
<p id="p-24" num="24">
|
| 338 |
+
<confidence value="2">{</confidence>
|
| 339 |
+
0023] The system <part-num-ref name="system">10</part-num-ref>
|
| 340 |
+
may also have an oil fill assembly <part-num-ref name="oil fill assembly">31</part-num-ref>
|
| 341 |
+
that enables a user to perform regular maintenance on the air compressor <part-num-ref name="air compressor">16.</part-num-ref>
|
| 342 |
+
For example, as depicted, the oil fill assembly <part-num-ref name="oil fill assembly">31</part-num-ref>
|
| 343 |
+
may include a configuration to provide improved access to components of the air compressor <part-num-ref name="air compressor">16</part-num-ref>
|
| 344 |
+
that may otherwise be obscured by other devices within the system <part-num-ref name="system">10.</part-num-ref>
|
| 345 |
+
Accordingly a user may easily check and add fluids to the air compressor <part-num-ref name="air compressor">16.</part-num-ref>
|
| 346 |
+
For example, the oil fill assembly <part-num-ref name="oil fill assembly">31</part-num-ref>
|
| 347 |
+
may be described as an extension, add-on, or retrofit system configured to relocate the oil fill location from well within the system <part-num-ref name="system">10</part-num-ref>
|
| 348 |
+
to a top access location<confidence value="5">.</confidence>
|
| 349 |
+
</p>
|
| 350 |
+
<p id="p-25" num="25">
|
| 351 |
+
<confidence value="5">[</confidence>
|
| 352 |
+
0024<confidence value="2">1</confidence>
|
| 353 |
+
The system <part-num-ref name="system">10</part-num-ref>
|
| 354 |
+
may also include control circuitry to coordinat<confidence value="8">e</confidence>
|
| 355 |
+
functions of a plurality of devices. For example, as depicted in FIGS. 1-3, the system <part-num-ref name="system">10</part-num-ref>
|
| 356 |
+
includes control circuitry <part-num-ref name="includes control circuitry">32</part-num-ref>
|
| 357 |
+
in the vicinity of a control panel <part-num-ref name="control panel">34.</part-num-ref>
|
| 358 |
+
In an embodiment, the control circuitry <part-num-ref name="control circuitry">32</part-num-ref>
|
| 359 |
+
may include a processor, memory, and software code configured to control and or coordinate operation of the system <part-num-ref name="system">10.</part-num-ref>
|
| 360 |
+
For example, the control circuitry <part-num-ref name="control circuitry">32</part-num-ref>
|
| 361 |
+
may monitor and control the speed and load on the engine <part-num-ref name="engine">12,</part-num-ref>
|
| 362 |
+
the electrical output and loads on the generator <part-num-ref name="generator">14,</part-num-ref>
|
| 363 |
+
the air output and loads on the compressor <part-num-ref name="compressor">16,</part-num-ref>
|
| 364 |
+
the startup procedures (e.g., soft start of compressor 16), and/or the like. For example, as mentioned above, the control circuitry <part-num-ref name="control circuitry">32</part-num-ref>
|
| 365 |
+
may identify an overload condition in response to sensed data, and then reduce the output to protect the system <part-num-ref name="system">10<confidence value="5">.</confidence>
|
| 366 |
+
</part-num-ref>
|
| 367 |
+
The control circuitry <part-num-ref name="control circuitry">32</part-num-ref>
|
| 368 |
+
also may reduce the engine speed, gradually increase the engine speed, and/or gradually engage a clutch during start up of the compressor <part-num-ref name="compressor">16.</part-num-ref>
|
| 369 |
+
The control circuitry <part-num-ref name="control circuitry">32</part-num-ref>
|
| 370 |
+
also may automatically adjust the outputs (e.g., compressed air output or electrical output) based on default or user defined priority levels, minimum workout output levels, maximum output levels, safety features, and so forth. The control circuitry <part-num-ref name="control circuitry">32</part-num-ref>
|
| 371 |
+
also may adjust output levels (e.g., compressed air output or electrical output) based on a particular application, sensed feedback, and other closed-loop controls. For example, the control circuitry <part-num-ref name="control circuitry">32</part-num-ref>
|
| 372 |
+
may <boundary-data type="header">
|
| 373 |
+
<confidence value="8">8</confidence>
|
| 374 |
+
</boundary-data>
|
| 375 |
+
<page-break num="9"/>
|
| 376 |
+
<boundary-data type="header">20724</boundary-data>
|
| 377 |
+
gradually decrease an electrical output for a battery charging procedure based on sensed feedback from the battery, thereby maximizing the charge without overcharging the battery. </p>
|
| 378 |
+
<p id="p-26" num="26">
|
| 379 |
+
<confidence value="5">[</confidence>
|
| 380 |
+
0025<confidence value="5">]</confidence>
|
| 381 |
+
As depicted in FIGS. 1-3, the enclosure <part-num-ref name="enclosure">18</part-num-ref>
|
| 382 |
+
includes a common base or frame <part-num-ref name="common base or frame">36</part-num-ref>
|
| 383 |
+
with various access panels to enable servicing, repair, and so forth. For example, a pair of side access panels (removed) is configured to attach to opposite sides of the frame <part-num-ref name="frame">36.</part-num-ref>
|
| 384 |
+
A top <part-num-ref name="top">37</part-num-ref>
|
| 385 |
+
of the enclosure <part-num-ref name="enclosure">18</part-num-ref>
|
| 386 |
+
includes first and second access panels or hatches <part-num-ref name="includes first and second access panels or hatches">38</part-num-ref>
|
| 387 |
+
and <part-num-ref name="and">39,</part-num-ref>
|
| 388 |
+
which are both rotatable between open and closed positions above the components of the system <part-num-ref name="system">10.</part-num-ref>
|
| 389 |
+
As illustrated, the first hatch <part-num-ref name="first hatch">38</part-num-ref>
|
| 390 |
+
can rotate open to enable access to the compressor <part-num-ref name="compressor">16,</part-num-ref>
|
| 391 |
+
the oil fill assembly <part-num-ref name="oil fill assembly">31,</part-num-ref>
|
| 392 |
+
and other features. The second hatch <part-num-ref name="second hatch">39</part-num-ref>
|
| 393 |
+
can rotate open to enable access to the engine <part-num-ref name="engine">12</part-num-ref>
|
| 394 |
+
and other features. </p>
|
| 395 |
+
<p id="p-27" num="27">[0026] As depicted, the control panel <part-num-ref name="control panel">34</part-num-ref>
|
| 396 |
+
is coupled to an end of the enclosure <part-num-ref name="enclosure">18</part-num-ref>
|
| 397 |
+
near the generator <part-num-ref name="generator">14<confidence value="5">.</confidence>
|
| 398 |
+
</part-num-ref>
|
| 399 |
+
The control panel <part-num-ref name="control panel">34</part-num-ref>
|
| 400 |
+
may include various control inputs, indicators, displays, electrical outputs, air outputs, and so forth. In an embodiment, a user input <part-num-ref name="user input">40</part-num-ref>
|
| 401 |
+
may include a knob or button configured for a mode of operation, an output level or type, etc<confidence value="5">.</confidence>
|
| 402 |
+
For instance, the user input <part-num-ref name="user input">40</part-num-ref>
|
| 403 |
+
may include a dial to select a mode of operation, such as a DC weld, an AC weld, a battery charge, or an air tool operation. The control panel <part-num-ref name="control panel">34</part-num-ref>
|
| 404 |
+
may also include various indicators <part-num-ref name="may also include various indicators">42</part-num-ref>
|
| 405 |
+
to provide feedback to the user. For example, the indicator <part-num-ref name="indicator">42</part-num-ref>
|
| 406 |
+
may include an LCD, LED, or Vacuum Florescent display to display voltage, amperage, air pressure, and the like<confidence value="5">,</confidence>
|
| 407 |
+
Embodiments of the control panel <part-num-ref name="control panel">34</part-num-ref>
|
| 408 |
+
include any number inputs and outputs, such as welding methods, air compressor settings, oil pressure, oil temperature, and system power. Further, the user inputs <part-num-ref name="user inputs">40</part-num-ref>
|
| 409 |
+
and indicators <part-num-ref name="and indicators">42</part-num-ref>
|
| 410 |
+
may be electrically coupled to the control circuitry <part-num-ref name="control circuitry">32</part-num-ref>
|
| 411 |
+
and enable a user to set and monitor various parameters within the control circuitry <part-num-ref name="control circuitry">32</part-num-ref>
|
| 412 |
+
and other devices of the system <part-num-ref name="system">10.</part-num-ref>
|
| 413 |
+
</p>
|
| 414 |
+
<p id="p-28" num="28">[0027<confidence value="5">]</confidence>
|
| 415 |
+
The illustrated system <part-num-ref name="illustrated system">10</part-num-ref>
|
| 416 |
+
also includes various external connections <part-num-ref name="also includes various external connections">44.</part-num-ref>
|
| 417 |
+
</p>
|
| 418 |
+
<p id="p-29" num="29">The external connections 44 may include various outlets and couplers configured to provide access to the electrical power and the compressed air generated by the system <part-num-ref name="system">10.</part-num-ref>
|
| 419 |
+
For example, the illustrated external connections <part-num-ref name="illustrated external connections">44</part-num-ref>
|
| 420 |
+
include an AC power output <boundary-data type="header">
|
| 421 |
+
<confidence value="8">9</confidence>
|
| 422 |
+
</boundary-data>
|
| 423 |
+
<page-break num="10"/>
|
| 424 |
+
<boundary-data type="header">20724</boundary-data>
|
| 425 |
+
<part-num-ref name="AC power output">46,</part-num-ref>
|
| 426 |
+
a DC power output <part-num-ref name="DC power output">48,</part-num-ref>
|
| 427 |
+
and a compressed air output <part-num-ref name="compressed air output">50.</part-num-ref>
|
| 428 |
+
<confidence value="4">I</confidence>
|
| 429 |
+
n an embodiment these outputs <part-num-ref name="embodiment these outputs">46,</part-num-ref>
|
| 430 |
+
<part-num-ref name="embodiment these outputs 46,">48</part-num-ref>
|
| 431 |
+
and <part-num-ref name="and">50</part-num-ref>
|
| 432 |
+
are coupled to various devices and tools. For example, the A<confidence value="5">C</confidence>
|
| 433 |
+
power output <part-num-ref name="AC power output">46</part-num-ref>
|
| 434 |
+
or the DC power output <part-num-ref name="DC power output">48</part-num-ref>
|
| 435 |
+
can be coupled to various welding and cutting tools <part-num-ref name="can be coupled to various welding and cutting tools">52.</part-num-ref>
|
| 436 |
+
As depicted, the welding/cutting tools <part-num-ref name="welding/cutting tools">52</part-num-ref>
|
| 437 |
+
included a torch <part-num-ref name="torch">54</part-num-ref>
|
| 438 |
+
coupled to the external connection <part-num-ref name="external connection">44</part-num-ref>
|
| 439 |
+
via a supply conduit <part-num-ref name="supply conduit">56.</part-num-ref>
|
| 440 |
+
For instance, the welding devices may receive current from the generator <part-num-ref name="generator">14</part-num-ref>
|
| 441 |
+
via the external connections <part-num-ref name="external connections">44.</part-num-ref>
|
| 442 |
+
In such an embodiment, the torch <part-num-ref name="torch">54</part-num-ref>
|
| 443 |
+
may be used to weld or cut a work piece <part-num-ref name="work piece">58</part-num-ref>
|
| 444 |
+
coupled to the external connections <part-num-ref name="external connections">44</part-num-ref>
|
| 445 |
+
via a work clamp <part-num-ref name="work clamp">60</part-num-ref>
|
| 446 |
+
and a cable <part-num-ref name="cable">62.</part-num-ref>
|
| 447 |
+
As will be appreciated, the torch <part-num-ref name="torch">54</part-num-ref>
|
| 448 |
+
may include various welding devices, such as a TIG (tungsten inert gas) torch, a M<confidence value="5">T</confidence>
|
| 449 |
+
G (metal inert gas) gun, or a plasma cutting torch. Similarly, the system <part-num-ref name="system">10</part-num-ref>
|
| 450 |
+
may provide compressed air from the air compressor <part-num-ref name="air compressor">16</part-num-ref>
|
| 451 |
+
via the compressed air output <part-num-ref name="compressed air output">50.</part-num-ref>
|
| 452 |
+
For example an air tool <part-num-ref name="air tool">64</part-num-ref>
|
| 453 |
+
may be coupled to the compressed air output <part-num-ref name="compressed air output">50</part-num-ref>
|
| 454 |
+
via an air hose <part-num-ref name="air hose">66.</part-num-ref>
|
| 455 |
+
The air hose <part-num-ref name="air hose">66</part-num-ref>
|
| 456 |
+
may exit the system <part-num-ref name="system">10</part-num-ref>
|
| 457 |
+
at various other locations; including the back of the system <part-num-ref name="system">10</part-num-ref>
|
| 458 |
+
proximate to the air compressor <part-num-ref name="air compressor">16.</part-num-ref>
|
| 459 |
+
The air tool <part-num-ref name="air tool">64</part-num-ref>
|
| 460 |
+
may include various pneumatic tools and the l<confidence value="8">i</confidence>
|
| 461 |
+
ke. In another embodiment, a plasma cutting torch <part-num-ref name="plasma cutting torch">54</part-num-ref>
|
| 462 |
+
may receive power from an external unit (e.g.<confidence value="5">,</confidence>
|
| 463 |
+
wall outlet AC power) while receiving compressed air from the air compressor <part-num-ref name="air compressor">16</part-num-ref>
|
| 464 |
+
of the system <part-num-ref name="system">10.</part-num-ref>
|
| 465 |
+
</p>
|
| 466 |
+
<p id="p-30" num="30">[0028<confidence value="5">]</confidence>
|
| 467 |
+
As discussed previously, the system <part-num-ref name="system">10</part-num-ref>
|
| 468 |
+
may include multiple components working in cooperation to generate power, compressed air, and other outputs. For example, in the illustrated embodiment, a single engine <part-num-ref name="single engine">12</part-num-ref>
|
| 469 |
+
is coupled to the generator <part-num-ref name="generator">14</part-num-ref>
|
| 470 |
+
and the air compressor <part-num-ref name="air compressor">16.</part-num-ref>
|
| 471 |
+
As will be appreciated, mechanical design of such a system <part-num-ref name="system">10</part-num-ref>
|
| 472 |
+
may entail various arrangements of components to provide an efficient and reliable system <part-num-ref name="efficient and reliable system">10.</part-num-ref>
|
| 473 |
+
For example, the operator may turn on the air compressor <part-num-ref name="air compressor">16</part-num-ref>
|
| 474 |
+
which, in turn, engages a clutch to enable the air compressor <part-num-ref name="air compressor">16</part-num-ref>
|
| 475 |
+
to draw power from the engine <part-num-ref name="engine">12.</part-num-ref>
|
| 476 |
+
As will be appreciated, the loading of the devices, such as the air compressor <part-num-ref name="air compressor">16,</part-num-ref>
|
| 477 |
+
may be substantial depending on the specific requirements of each device<confidence value="5">.</confidence>
|
| 478 |
+
For instance, the air compressor <part-num-ref name="air compressor">16</part-num-ref>
|
| 479 |
+
may use a significant amount of power to maintain a minimum oil pressure to circulate cooling oil. <confidence value="6">I</confidence>
|
| 480 |
+
ncreased loads may prove difficult for the engine <part-num-ref name="engine">12</part-num-ref>
|
| 481 |
+
to handle at start-up. Similarly, if the air compressor <part-num-ref name="air compressor">16</part-num-ref>
|
| 482 |
+
is engaged when the engine <part-num-ref name="engine">12</part-num-ref>
|
| 483 |
+
is running at an operating speed, the load of the air <boundary-data type="header">
|
| 484 |
+
<confidence value="88">10</confidence>
|
| 485 |
+
</boundary-data>
|
| 486 |
+
<page-break num="11"/>
|
| 487 |
+
<boundary-data type="header">20724</boundary-data>
|
| 488 |
+
compressor <part-num-ref name="air compressor">16</part-num-ref>
|
| 489 |
+
ramping up to the engine operating speed may create a significant shock to the system <part-num-ref name="system">12.</part-num-ref>
|
| 490 |
+
Accordingly, engaging the air compressor <part-num-ref name="air compressor">16</part-num-ref>
|
| 491 |
+
at a high engine speed may increase wear on the system components, including the engine <part-num-ref name="engine">12,</part-num-ref>
|
| 492 |
+
the drive belt <part-num-ref name="drive belt">30,</part-num-ref>
|
| 493 |
+
the clutch mechanism and the base/frame <part-num-ref name="base/frame">36<confidence value="5">.</confidence>
|
| 494 |
+
</part-num-ref>
|
| 495 |
+
The following d<confidence value="8">i</confidence>
|
| 496 |
+
scussion provides a system <part-num-ref name="system">10</part-num-ref>
|
| 497 |
+
and control method configured to control operations of the engine <part-num-ref name="engine">12,</part-num-ref>
|
| 498 |
+
the electronic governor, the air compressor <part-num-ref name="air compressor">16</part-num-ref>
|
| 499 |
+
and the clutch when engaging an additional device, such as the air compressor <part-num-ref name="air compressor">16.</part-num-ref>
|
| 500 |
+
</p>
|
| 501 |
+
<p id="p-31" num="31">[0029<confidence value="5">1</confidence>
|
| 502 |
+
FIG. 4 illustrates a block diagram of the system <part-num-ref name="system">10,</part-num-ref>
|
| 503 |
+
including the engine <part-num-ref name="engine">12,</part-num-ref>
|
| 504 |
+
the air compressor <part-num-ref name="air compressor">16,</part-num-ref>
|
| 505 |
+
a governor <part-num-ref name="governor">80,</part-num-ref>
|
| 506 |
+
a clutch <part-num-ref name="clutch">82</part-num-ref>
|
| 507 |
+
an electronic control <part-num-ref name="electronic control">84,</part-num-ref>
|
| 508 |
+
and a user interface <part-num-ref name="user interface">86<confidence value="6">.</confidence>
|
| 509 |
+
</part-num-ref>
|
| 510 |
+
<confidence value="6">I</confidence>
|
| 511 |
+
n this configuration, the engine speed may be regulated by the governor <part-num-ref name="governor">80,</part-num-ref>
|
| 512 |
+
and the transfer of the torque from the engine <part-num-ref name="engine">12</part-num-ref>
|
| 513 |
+
to the air compressor <part-num-ref name="air compressor">16</part-num-ref>
|
| 514 |
+
may be regulated by the clutch <part-num-ref name="clutch">82.</part-num-ref>
|
| 515 |
+
As will be discussed in detail below, with reference to FIG. <confidence value="5">5</confidence>
|
| 516 |
+
, the electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 517 |
+
may implement a control algorithm to coordinate the operation of the governor <part-num-ref name="governor">80</part-num-ref>
|
| 518 |
+
and the clutch <part-num-ref name="clutch">82</part-num-ref>
|
| 519 |
+
based on various inputs and parameters. The electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 520 |
+
also may include at least one welding control feature, or the control <part-num-ref name="control">84</part-num-ref>
|
| 521 |
+
may be part of the control circuitry <part-num-ref name="control circuitry">32</part-num-ref>
|
| 522 |
+
or an overall welding control assembly of the system <part-num-ref name="system">10<confidence value="5">.</confidence>
|
| 523 |
+
</part-num-ref>
|
| 524 |
+
</p>
|
| 525 |
+
<p id="p-32" num="32">[0030<confidence value="5">]</confidence>
|
| 526 |
+
The governor <part-num-ref name="governor">80</part-num-ref>
|
| 527 |
+
is generally configured to regulate the speed of the engine <part-num-ref name="engine">12,</part-num-ref>
|
| 528 |
+
e.g., revolutions per minute (<confidence value="66">rp</confidence>
|
| 529 |
+
m), based on a desired level<confidence value="5">.</confidence>
|
| 530 |
+
In an embodiment, the governor <part-num-ref name="governor">80</part-num-ref>
|
| 531 |
+
may include an electronic governor configured to control the engine <part-num-ref name="engine">12</part-num-ref>
|
| 532 |
+
based on the input control signals and monitored engine parameters. For example, the governor <part-num-ref name="governor">80</part-num-ref>
|
| 533 |
+
may receive a control signal commanding a given speed and the governor <part-num-ref name="governor">80</part-num-ref>
|
| 534 |
+
may then generate an output signal to control the throttle of the engine <part-num-ref name="engine">12.</part-num-ref>
|
| 535 |
+
The.output may include an electrical control of the engine <part-num-ref name="engine">12</part-num-ref>
|
| 536 |
+
or may include mechanical actuation of a throttle of the engine <part-num-ref name="engine">12.</part-num-ref>
|
| 537 |
+
</p>
|
| 538 |
+
<p id="p-33" num="33">
|
| 539 |
+
<confidence value="5">[</confidence>
|
| 540 |
+
0031] The control signal may be generated by the electronic control <part-num-ref name="electronic control">84.</part-num-ref>
|
| 541 |
+
In such an embodiment, the control signal may be produced based on a control algorithm embedded within the electronic control <part-num-ref name="electronic control">84.</part-num-ref>
|
| 542 |
+
For example, the electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 543 |
+
may monitor the operating speed and command the governor <part-num-ref name="governor">80</part-num-ref>
|
| 544 |
+
to increase or decrease the speed of the engine <part-num-ref name="engine">12</part-num-ref>
|
| 545 |
+
accordingly. In other embodiments, the governor </p>
|
| 546 |
+
<heading id="h-7">
|
| 547 |
+
<confidence value="66">II</confidence>
|
| 548 |
+
</heading>
|
| 549 |
+
<boundary-data type="header">20724</boundary-data>
|
| 550 |
+
<p id="p-34" num="34">
|
| 551 |
+
<page-break num="12"/>
|
| 552 |
+
80 may include an onboard control loop (such as a proportional-integral-derivative controller (PID controller)) that regulates the output to the engine <part-num-ref name="engine">12.</part-num-ref>
|
| 553 |
+
Thus, the governor <part-num-ref name="governor">80</part-num-ref>
|
| 554 |
+
can independently regulate the engine <part-num-ref name="engine">12</part-num-ref>
|
| 555 |
+
to meet the parameters requested by the control signal output by the electronic control <part-num-ref name="electronic control">84.</part-num-ref>
|
| 556 |
+
<confidence value="5">I</confidence>
|
| 557 |
+
n other words, the governor <part-num-ref name="governor">80</part-num-ref>
|
| 558 |
+
may receive a signal requesting a given speed and implement its own routine to regulate the engine <part-num-ref name="engine">80</part-num-ref>
|
| 559 |
+
to the desired speed<confidence value="5">.</confidence>
|
| 560 |
+
The governor <part-num-ref name="governor">80</part-num-ref>
|
| 561 |
+
may include any mechanism configured to receive a control signal and regulate the engine <part-num-ref name="engine">12</part-num-ref>
|
| 562 |
+
based on the signal. </p>
|
| 563 |
+
<p id="p-35" num="35">[0032] The governor <part-num-ref name="governor">80</part-num-ref>
|
| 564 |
+
may be mounted to the system <part-num-ref name="system">10</part-num-ref>
|
| 565 |
+
in various configurations that enable the governor <part-num-ref name="governor">80</part-num-ref>
|
| 566 |
+
to regulate the engine <part-num-ref name="engine">12.</part-num-ref>
|
| 567 |
+
In an embodiment, the governor <part-num-ref name="governor">80</part-num-ref>
|
| 568 |
+
may be mechanically coupled to the engine <part-num-ref name="engine">12.</part-num-ref>
|
| 569 |
+
</p>
|
| 570 |
+
<p id="p-36" num="36">Mechanically coupling the governor <part-num-ref name="governor">80</part-num-ref>
|
| 571 |
+
to the engine <part-num-ref name="engine">12</part-num-ref>
|
| 572 |
+
enables the governor <part-num-ref name="governor">80</part-num-ref>
|
| 573 |
+
to manipulate components of the engine <part-num-ref name="engine">12,</part-num-ref>
|
| 574 |
+
including a carburetor throttle shaft, and the like. Mechanically coupling the governor <part-num-ref name="governor">80</part-num-ref>
|
| 575 |
+
may include providing an engine <part-num-ref name="engine">12</part-num-ref>
|
| 576 |
+
with the governor <part-num-ref name="governor">80</part-num-ref>
|
| 577 |
+
built into the engine <part-num-ref name="engine">12,</part-num-ref>
|
| 578 |
+
directly attaching the governor <part-num-ref name="governor">80</part-num-ref>
|
| 579 |
+
to the body of the engine <part-num-ref name="engine">12,</part-num-ref>
|
| 580 |
+
or providing the governor <part-num-ref name="governor">80</part-num-ref>
|
| 581 |
+
as a separate component with a linkage to the engine <part-num-ref name="engine">12<confidence value="5">.</confidence>
|
| 582 |
+
</part-num-ref>
|
| 583 |
+
Other embodiments may include electrically coupling the governor <part-num-ref name="governor">80</part-num-ref>
|
| 584 |
+
to a control circuitry located within the engine <part-num-ref name="engine">12.</part-num-ref>
|
| 585 |
+
</p>
|
| 586 |
+
<p id="p-37" num="37">[0033] The clutch <part-num-ref name="clutch">82</part-num-ref>
|
| 587 |
+
is configured to control the transfer of power from the engine <part-num-ref name="engine">12</part-num-ref>
|
| 588 |
+
to the air compressor <part-num-ref name="air compressor">16.</part-num-ref>
|
| 589 |
+
The power transferred may include mechanical power in the form of torque. As depicted in FIGS. 1-4, the engine <part-num-ref name="engine">12</part-num-ref>
|
| 590 |
+
includes the drive shaft <part-num-ref name="drive shaft">20</part-num-ref>
|
| 591 |
+
and the stub shaft <part-num-ref name="stub shaft">22,</part-num-ref>
|
| 592 |
+
which are both rotated by the engine <part-num-ref name="engine">12.</part-num-ref>
|
| 593 |
+
For simplicity, the remainder of the discussion refers to the transfer of power via the shaft <part-num-ref name="shaft">22,</part-num-ref>
|
| 594 |
+
although similar systems may also make use of the shaft <part-num-ref name="shaft">20.</part-num-ref>
|
| 595 |
+
The shaft <part-num-ref name="shaft">22</part-num-ref>
|
| 596 |
+
is coupled to the compressor drive shaft <part-num-ref name="compressor drive shaft">26</part-num-ref>
|
| 597 |
+
via the drive belt <part-num-ref name="drive belt">30,</part-num-ref>
|
| 598 |
+
the pulley <part-num-ref name="pulley">24,</part-num-ref>
|
| 599 |
+
and the compressor pulley <part-num-ref name="compressor pulley">28.</part-num-ref>
|
| 600 |
+
Accordingly, the power from the engine <part-num-ref name="engine">12</part-num-ref>
|
| 601 |
+
is received by the air compressor <part-num-ref name="air compressor">16</part-num-ref>
|
| 602 |
+
as torque. The clutch <part-num-ref name="clutch">82</part-num-ref>
|
| 603 |
+
is positioned between the engine <part-num-ref name="engine">12</part-num-ref>
|
| 604 |
+
and the air compressor <part-num-ref name="air compressor">16,</part-num-ref>
|
| 605 |
+
and is configured to control the transfer of torque between the engine <part-num-ref name="engine">12</part-num-ref>
|
| 606 |
+
and the air compressor <part-num-ref name="air compressor">16.</part-num-ref>
|
| 607 |
+
Configuring the clutch <part-num-ref name="clutch">82</part-num-ref>
|
| 608 |
+
to transfer the torque is generally referred to as engaging the clutch <part-num-ref name="clutch">82.</part-num-ref>
|
| 609 |
+
As mentioned previously, the power required to operate the compressor <part-num-ref name="compressor">16</part-num-ref>
|
| 610 |
+
may increase the demand for power <boundary-data type="header">
|
| 611 |
+
<confidence value="88">12</confidence>
|
| 612 |
+
</boundary-data>
|
| 613 |
+
<page-break num="13"/>
|
| 614 |
+
<boundary-data type="header">20724</boundary-data>
|
| 615 |
+
from the engine <part-num-ref name="engine">12.</part-num-ref>
|
| 616 |
+
Accordingly, engaging the clutch <part-num-ref name="clutch">82</part-num-ref>
|
| 617 |
+
increases the overall load on the engine <part-num-ref name="engine">12,</part-num-ref>
|
| 618 |
+
while disengaging the clutch <part-num-ref name="clutch">82</part-num-ref>
|
| 619 |
+
decreases the load of the air compressor <part-num-ref name="air compressor">16</part-num-ref>
|
| 620 |
+
on the engine <part-num-ref name="engine">12.</part-num-ref>
|
| 621 |
+
</p>
|
| 622 |
+
<p id="p-38" num="38">
|
| 623 |
+
<confidence value="266682">[0034I</confidence>
|
| 624 |
+
The clutch <part-num-ref name="clutch">82</part-num-ref>
|
| 625 |
+
may include any device configured to regulate the amount of torque transferred between the engine <part-num-ref name="engine">12</part-num-ref>
|
| 626 |
+
and the air compressor <part-num-ref name="air compressor">16.</part-num-ref>
|
| 627 |
+
For example, an embodiment includes an electric clutch that has two electromagnetic plates complementary to one another. In such an arrangement, the clutch <part-num-ref name="clutch">82</part-num-ref>
|
| 628 |
+
may enable or disable in response to a control signal. For example, if the clutch <part-num-ref name="clutch">82</part-num-ref>
|
| 629 |
+
receives a signal to engage, the electromagnetic plates may be energized to draw the two plates together and create a friction. Energizing the plates may include a digital input configured to fully engage or disengage the clutch <part-num-ref name="clutch">82</part-num-ref>
|
| 630 |
+
or an analog input configured to provide a proportional friction and, thus a proportional transfer of torque. For example, a digital signal may cause the two plates to energize fully and provide a f<confidence value="8">u</confidence>
|
| 631 |
+
ll friction. An analog signal may enable the plates to partially energize and, thus, vary the amount of friction generated in the clutch<confidence value="5">,</confidence>
|
| 632 |
+
In an embodiment, the signal configured to operate the clutch <part-num-ref name="clutch">82</part-num-ref>
|
| 633 |
+
may be generated by the electronic control <part-num-ref name="electronic control">84<confidence value="5">.</confidence>
|
| 634 |
+
</part-num-ref>
|
| 635 |
+
</p>
|
| 636 |
+
<p id="p-39" num="39">The clutch 82 may also include any other mechanisms configured to vary the amount of torque transferred between the engine <part-num-ref name="engine">12</part-num-ref>
|
| 637 |
+
and the air compressor <part-num-ref name="air compressor">16.</part-num-ref>
|
| 638 |
+
</p>
|
| 639 |
+
<p id="p-40" num="40">
|
| 640 |
+
<confidence value="266662">[0035]</confidence>
|
| 641 |
+
The location of the clutch <part-num-ref name="clutch">82</part-num-ref>
|
| 642 |
+
may be varied to accommodate any number of applications. As depicted the clutch <part-num-ref name="clutch">82</part-num-ref>
|
| 643 |
+
is located in-line with the compressor drive shaft <part-num-ref name="compressor drive shaft">26.</part-num-ref>
|
| 644 |
+
Similarly, the clutch <part-num-ref name="clutch">82</part-num-ref>
|
| 645 |
+
may be located in-line with the shaft <part-num-ref name="shaft">22</part-num-ref>
|
| 646 |
+
and be configured to enable or disable the transfer of torque to the pulley <part-num-ref name="pulley">24</part-num-ref>
|
| 647 |
+
and, thus, the torque provided to the compressor <part-num-ref name="compressor">16.</part-num-ref>
|
| 648 |
+
Further, an embodiment may include the clutch <part-num-ref name="clutch">82</part-num-ref>
|
| 649 |
+
built into a pulley. For example, the pulley <part-num-ref name="pulley">24</part-num-ref>
|
| 650 |
+
or the compressor pulley <part-num-ref name="compressor pulley">28</part-num-ref>
|
| 651 |
+
may include a clutch pulley configured to transfer torque via engagement in response to the control signal. Further, the system <part-num-ref name="system">10</part-num-ref>
|
| 652 |
+
may include a belt tensioning mechanism configured to increase or decrease the tension of the drive belt <part-num-ref name="drive belt">30</part-num-ref>
|
| 653 |
+
based on the control signal. Accordingly, the control signal may be configured to generate a response to tension the drive belt <part-num-ref name="drive belt">30</part-num-ref>
|
| 654 |
+
(i.e., enable the clutch). </p>
|
| 655 |
+
<boundary-data type="header">
|
| 656 |
+
<confidence value="88">13</confidence>
|
| 657 |
+
</boundary-data>
|
| 658 |
+
<boundary-data type="header">20724</boundary-data>
|
| 659 |
+
<p id="p-41" num="41">
|
| 660 |
+
<page-break num="14"/>
|
| 661 |
+
[0036] The electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 662 |
+
is configured to coordinate operation of the system <part-num-ref name="system">10.</part-num-ref>
|
| 663 |
+
<confidence value="5">I</confidence>
|
| 664 |
+
n other words, the electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 665 |
+
monitors any number of inputs, and also outputs various commands to control the operating speed of the engine via the governor <part-num-ref name="governor">80</part-num-ref>
|
| 666 |
+
and the power (i.e., torque) transferred to the air compressor <part-num-ref name="air compressor">16</part-num-ref>
|
| 667 |
+
via the clutch <part-num-ref name="clutch">82.</part-num-ref>
|
| 668 |
+
As depicted in FIG. 4, the electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 669 |
+
is electrically coupled to the governor <part-num-ref name="governor">80</part-num-ref>
|
| 670 |
+
and the clutch <part-num-ref name="clutch">82.</part-num-ref>
|
| 671 |
+
The electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 672 |
+
may be configured to transmit various parameters to the governor <part-num-ref name="governor">80,</part-num-ref>
|
| 673 |
+
including a speed control signal indicative of a desired engine operating speed. For example, the speed control signal may include a set level or value representative of the desired engine speed. In response to the speed control signal, the governor <part-num-ref name="governor">80</part-num-ref>
|
| 674 |
+
may regulate the speed of the engine <part-num-ref name="engine">12,</part-num-ref>
|
| 675 |
+
as described previously. </p>
|
| 676 |
+
<p id="p-42" num="42">[0037<confidence value="4">]</confidence>
|
| 677 |
+
The electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 678 |
+
may also be electrically coupled to the clutch <part-num-ref name="clutch">82</part-num-ref>
|
| 679 |
+
and configured to control engagement of the clutch <part-num-ref name="clutch">82</part-num-ref>
|
| 680 |
+
via a clutch signal. In an embodiment where the clutch <part-num-ref name="clutch">82</part-num-ref>
|
| 681 |
+
is configured to provide a digital clutch signal, the electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 682 |
+
may output a clutch signal above or below a threshold value to enable or disable the clutch <part-num-ref name="clutch">82.</part-num-ref>
|
| 683 |
+
For example, based on the determination to engage or disengage the clutch <part-num-ref name="clutch">82,</part-num-ref>
|
| 684 |
+
the electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 685 |
+
can output a digital high or digital low clutch signal. Similarly, in an embodiment of the clutch <part-num-ref name="clutch">82</part-num-ref>
|
| 686 |
+
that has the ability to incremental<confidence value="8">l</confidence>
|
| 687 |
+
y vary the amount of torque transmitted, the electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 688 |
+
can output an analog signal proportional to the desired torque transfer. In such a configuration, the clutch signal may be configured to ramp up transferred torque to reduce the shock to the system <part-num-ref name="system">10</part-num-ref>
|
| 689 |
+
and the engine <part-num-ref name="engine">12</part-num-ref>
|
| 690 |
+
as the air compressor <part-num-ref name="air compressor">16</part-num-ref>
|
| 691 |
+
begins to draw power from the system <part-num-ref name="system">10.</part-num-ref>
|
| 692 |
+
</p>
|
| 693 |
+
<p id="p-43" num="43">[0038] Further, the electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 694 |
+
may receive and process various inputs<confidence value="5">.</confidence>
|
| 695 |
+
</p>
|
| 696 |
+
<p id="p-44" num="44">In an embodiment, inputs to the electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 697 |
+
may include any number of engine parameters and system parameters. For example, the electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 698 |
+
may receive signals indicative of actual engine speed, a signal relating to engine coolant temperature, engine oil temperature, system temperature, <confidence value="58">or</confidence>
|
| 699 |
+
<confidence value="8">o</confidence>
|
| 700 |
+
ther parameters related to the assessing the performance of the engine <part-num-ref name="engine">12</part-num-ref>
|
| 701 |
+
and the system <part-num-ref name="system">10.</part-num-ref>
|
| 702 |
+
These signals may be provided directly from the engine <part-num-ref name="engine">12,</part-num-ref>
|
| 703 |
+
the governor <part-num-ref name="governor">80,</part-num-ref>
|
| 704 |
+
or other components of the system <part-num-ref name="system">10,</part-num-ref>
|
| 705 |
+
to the control circuitry <part-num-ref name="control circuitry">32.</part-num-ref>
|
| 706 |
+
</p>
|
| 707 |
+
<boundary-data type="header">
|
| 708 |
+
<confidence value="88">14</confidence>
|
| 709 |
+
</boundary-data>
|
| 710 |
+
<boundary-data type="header">20724</boundary-data>
|
| 711 |
+
<p id="p-45" num="45">
|
| 712 |
+
<page-break num="15"/>
|
| 713 |
+
[0039<confidence value="5">]</confidence>
|
| 714 |
+
Similarly, the electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 715 |
+
may receive feedback signals indicative of the current status of the air compressor <part-num-ref name="air compressor">16</part-num-ref>
|
| 716 |
+
and the clutch <part-num-ref name="clutch">82.</part-num-ref>
|
| 717 |
+
For example, the signals may verify that the clutch has engaged, indicate the actual speed of the air compressor <part-num-ref name="air compressor">16,</part-num-ref>
|
| 718 |
+
or the desired rotational speed of the compressor <part-num-ref name="compressor">16.</part-num-ref>
|
| 719 |
+
Accordingly, the electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 720 |
+
may incorporate these signals into a control algorithm<confidence value="5">,</confidence>
|
| 721 |
+
[0040<confidence value="2">]</confidence>
|
| 722 |
+
The system <part-num-ref name="system">10</part-num-ref>
|
| 723 |
+
may also incorporate user input via the user interface <part-num-ref name="user interface">86</part-num-ref>
|
| 724 |
+
in communication with the electronic control <part-num-ref name="electronic control">84.</part-num-ref>
|
| 725 |
+
<confidence value="5">I</confidence>
|
| 726 |
+
n an embodiment, the user interface <part-num-ref name="user interface">86</part-num-ref>
|
| 727 |
+
may include a switch or a plurality of switches configured to turn the air compressor <part-num-ref name="air compressor">16</part-num-ref>
|
| 728 |
+
off and on. <confidence value="5">F</confidence>
|
| 729 |
+
or example, the user interface <part-num-ref name="user interface">86</part-num-ref>
|
| 730 |
+
may include a mechanical or digital switch that the user turns on to start the air compressor <part-num-ref name="air compressor">16<confidence value="5">.</confidence>
|
| 731 |
+
</part-num-ref>
|
| 732 |
+
</p>
|
| 733 |
+
<p id="p-46" num="46">Further, the user interface <part-num-ref name="user interface">86</part-num-ref>
|
| 734 |
+
may also include any number of inputs to increase the flexibility of the system. For example, user interface <part-num-ref name="system. For example, user interface">86</part-num-ref>
|
| 735 |
+
may enable an operator to enter parameters relevant to a control algorithm implemented by the electronic control <part-num-ref name="electronic control">84.</part-num-ref>
|
| 736 |
+
The user interface <part-num-ref name="user interface">86</part-num-ref>
|
| 737 |
+
may be located on the control panel <part-num-ref name="control panel">34</part-num-ref>
|
| 738 |
+
or in other locations within the system <part-num-ref name="system">10.</part-num-ref>
|
| 739 |
+
For instance, the user interface <part-num-ref name="user interface">86</part-num-ref>
|
| 740 |
+
may be located on the air compressor <part-num-ref name="air compressor">16,</part-num-ref>
|
| 741 |
+
proximate to the welding/cutting tools <part-num-ref name="welding/cutting tools">52,</part-num-ref>
|
| 742 |
+
or remote to the system <part-num-ref name="system">10.</part-num-ref>
|
| 743 |
+
</p>
|
| 744 |
+
<p id="p-47" num="47">[0041] The electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 745 |
+
may <confidence value="5">b</confidence>
|
| 746 |
+
e a separate component in the system <part-num-ref name="system">10</part-num-ref>
|
| 747 |
+
or may be integrated with other components and devices within the system <part-num-ref name="system">10<confidence value="5">,</confidence>
|
| 748 |
+
</part-num-ref>
|
| 749 |
+
<confidence value="5">I</confidence>
|
| 750 |
+
n an embodiment, the electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 751 |
+
may include an additional device located within the system <part-num-ref name="system">10.</part-num-ref>
|
| 752 |
+
For example, the electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 753 |
+
may include a processor and/or memory devices<confidence value="5">.</confidence>
|
| 754 |
+
Accordingly, the electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 755 |
+
may be configured to operate with minimal overlap with other control devices within the system <part-num-ref name="system">10.</part-num-ref>
|
| 756 |
+
In another embodiment, at least a portion of the electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 757 |
+
may be located within other control devices contained within the system <part-num-ref name="system">10.</part-num-ref>
|
| 758 |
+
For example, the processing of the electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 759 |
+
may be accomplished within the control circuitry <part-num-ref name="control circuitry">32</part-num-ref>
|
| 760 |
+
using a processor and memory located within the control circuitry <part-num-ref name="control circuitry">32.</part-num-ref>
|
| 761 |
+
</p>
|
| 762 |
+
<p id="p-48" num="48">[0042<confidence value="5">]</confidence>
|
| 763 |
+
FIG. 5 includes a flowchart that illustrates an exemplary computer- implemented method to operate a welding generator/compressor system <part-num-ref name="welding generator/compressor system">10.</part-num-ref>
|
| 764 |
+
The flowchart includes a method to check for a request to turn on the air compressor <part-num-ref name="air compressor">16</part-num-ref>
|
| 765 |
+
followed by a routine to control the speed of the engine <part-num-ref name="engine">12,</part-num-ref>
|
| 766 |
+
and to engage or <boundary-data type="header">
|
| 767 |
+
<confidence value="88">15</confidence>
|
| 768 |
+
</boundary-data>
|
| 769 |
+
<page-break num="16"/>
|
| 770 |
+
<boundary-data type="header">20724</boundary-data>
|
| 771 |
+
disengage the air compressor <part-num-ref name="air compressor">
|
| 772 |
+
<confidence value="66">16</confidence>
|
| 773 |
+
. </part-num-ref>
|
| 774 |
+
For example, block <part-num-ref name="air compressor 16. For example, block">100</part-num-ref>
|
| 775 |
+
includes "start<confidence value="4">,</confidence>
|
| 776 |
+
" Start <part-num-ref name="includes "start," Start">
|
| 777 |
+
<confidence value="688">100</confidence>
|
| 778 |
+
</part-num-ref>
|
| 779 |
+
may include starting the system <part-num-ref name="system">10</part-num-ref>
|
| 780 |
+
which may include an operator turning on power to the system <part-num-ref name="system">10.</part-num-ref>
|
| 781 |
+
For example, the user may flip a switch, such as the user interface <part-num-ref name="user interface">86,</part-num-ref>
|
| 782 |
+
to start the engine <part-num-ref name="engine">12.</part-num-ref>
|
| 783 |
+
<confidence value="5">I</confidence>
|
| 784 |
+
n one embodiment, the clutch <part-num-ref name="clutch">82</part-num-ref>
|
| 785 |
+
may be disengaged at startup to ensure that the engine <part-num-ref name="engine">12</part-num-ref>
|
| 786 |
+
is started without the additional loading of the air compressor <part-num-ref name="air compressor">16.</part-num-ref>
|
| 787 |
+
For instance, the electronic control may maintain the clutch <part-num-ref name="clutch">82</part-num-ref>
|
| 788 |
+
in a disabled state until the electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 789 |
+
determines the system <part-num-ref name="system">10</part-num-ref>
|
| 790 |
+
is properly configured to support the startup load of the compressor <part-num-ref name="compressor">16.</part-num-ref>
|
| 791 |
+
Embodiments may also include starting the system <part-num-ref name="system">10</part-num-ref>
|
| 792 |
+
with the clutch <part-num-ref name="clutch">82</part-num-ref>
|
| 793 |
+
in the same state that it was in when the system <part-num-ref name="system">10</part-num-ref>
|
| 794 |
+
was previously shutdown. </p>
|
| 795 |
+
<p id="p-49" num="49">
|
| 796 |
+
<confidence value="666862">[0043]</confidence>
|
| 797 |
+
The system <part-num-ref name="system">10</part-num-ref>
|
| 798 |
+
may check for a compressor request, as indicated at block <part-num-ref name="compressor request, as indicated at block">102.</part-num-ref>
|
| 799 |
+
For example, after the system <part-num-ref name="system">10</part-num-ref>
|
| 800 |
+
is started, the system <part-num-ref name="system">10</part-num-ref>
|
| 801 |
+
may scan for an input that is indicative of the desire to power the air compressor <part-num-ref name="air compressor">16.</part-num-ref>
|
| 802 |
+
In an embodiment, checking for a compressor request <part-num-ref name="compressor request">102</part-num-ref>
|
| 803 |
+
may include the electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 804 |
+
checking the status of each input, including the user interface <part-num-ref name="user interface">86,</part-num-ref>
|
| 805 |
+
to determine if a request to power the air compressor <part-num-ref name="air compressor">16</part-num-ref>
|
| 806 |
+
has been received. For example, the electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 807 |
+
may query the status of a switch that an operator may turn on or off to start or stop operation of the air compressor <part-num-ref name="air compressor">16,</part-num-ref>
|
| 808 |
+
Further, inputs may include checking a memory within the electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 809 |
+
to determine if there was a compressor request when the system <part-num-ref name="system">10</part-num-ref>
|
| 810 |
+
was previously shutdown. For example, if the compressor <part-num-ref name="compressor">16</part-num-ref>
|
| 811 |
+
was on when the system <part-num-ref name="system">10</part-num-ref>
|
| 812 |
+
was last shutdown, the electronic controller <part-num-ref name="electronic controller">84</part-num-ref>
|
| 813 |
+
may detect a compressor request at startup of the system <part-num-ref name="system">10.</part-num-ref>
|
| 814 |
+
</p>
|
| 815 |
+
<p id="p-50" num="50">
|
| 816 |
+
<confidence value="266662">[0044|</confidence>
|
| 817 |
+
Based on the che<confidence value="8">c</confidence>
|
| 818 |
+
k for a compressor request <part-num-ref name="compressor request">102,</part-num-ref>
|
| 819 |
+
the system <part-num-ref name="system">10</part-num-ref>
|
| 820 |
+
may determine if there is a compressor request, as indicated by block <part-num-ref name="compressor request, as indicated by block">104,</part-num-ref>
|
| 821 |
+
and may configure the electronic clutch <part-num-ref name="electronic clutch">82</part-num-ref>
|
| 822 |
+
and/or the governor <part-num-ref name="governor">80</part-num-ref>
|
| 823 |
+
based on the determination. </p>
|
| 824 |
+
<p id="p-51" num="51">The check for a compressor request <part-num-ref name="compressor request">102</part-num-ref>
|
| 825 |
+
may be implemented after startup <part-num-ref name="may be implemented after startup">100,</part-num-ref>
|
| 826 |
+
as indicated by the arrow connecting block <part-num-ref name="arrow connecting block">100</part-num-ref>
|
| 827 |
+
and block <part-num-ref name="and block">102,</part-num-ref>
|
| 828 |
+
or the check may include a looping continuous check during run-time as indicated by the arrow connecting block <part-num-ref name="arrow connecting block">
|
| 829 |
+
<confidence value="5">1</confidence>
|
| 830 |
+
16 </part-num-ref>
|
| 831 |
+
to block <part-num-ref name="to block">102.</part-num-ref>
|
| 832 |
+
For instance, if there is not a request for the compressor <part-num-ref name="compressor">16,</part-num-ref>
|
| 833 |
+
the system may disengage the compressor, as depicted at block <part-num-ref name="compressor, as depicted at block">106,</part-num-ref>
|
| 834 |
+
and continue to check for a compressor requests at block <part-num-ref name="compressor requests at block">102.</part-num-ref>
|
| 835 |
+
Disengaging the compressor <part-num-ref name="compressor">16</part-num-ref>
|
| 836 |
+
may <boundary-data type="header">
|
| 837 |
+
<confidence value="88">16</confidence>
|
| 838 |
+
</boundary-data>
|
| 839 |
+
<page-break num="17"/>
|
| 840 |
+
<boundary-data type="header">20724</boundary-data>
|
| 841 |
+
include leaving the clutch <part-num-ref name="clutch">82</part-num-ref>
|
| 842 |
+
in a disengaged state to prevent the transfer of power from the engine <part-num-ref name="engine">12</part-num-ref>
|
| 843 |
+
to the air compressor <part-num-ref name="air compressor">16.</part-num-ref>
|
| 844 |
+
For example, if the system <part-num-ref name="system">10</part-num-ref>
|
| 845 |
+
has just been started and the clutch <part-num-ref name="clutch">82</part-num-ref>
|
| 846 |
+
was automatically disengaged at startup, the electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 847 |
+
may continue to output a signal to maintain the clutch <part-num-ref name="clutch">82</part-num-ref>
|
| 848 |
+
in a disengaged state until a compressor request is received. </p>
|
| 849 |
+
<p id="p-52" num="52">
|
| 850 |
+
<confidence value="5">[</confidence>
|
| 851 |
+
0045<confidence value="5">1</confidence>
|
| 852 |
+
When it is determined that there is a compressor request at block <part-num-ref name="compressor request at block">104,</part-num-ref>
|
| 853 |
+
the system <part-num-ref name="system">10</part-num-ref>
|
| 854 |
+
may then take steps to bring the air compressor <part-num-ref name="air compressor">16</part-num-ref>
|
| 855 |
+
on-line. As depicted at block <part-num-ref name="on-line. As depicted at block">108,</part-num-ref>
|
| 856 |
+
in response to the compressor request, the system <part-num-ref name="system">10</part-num-ref>
|
| 857 |
+
may determine the lowest acceptable engine speed<confidence value="5">.</confidence>
|
| 858 |
+
An embodiment may include the electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 859 |
+
monitoring various parameters of the engine <part-num-ref name="engine">12</part-num-ref>
|
| 860 |
+
as well as other parameters with the system <part-num-ref name="system">10</part-num-ref>
|
| 861 |
+
to determine the engine speed that will reduce the shock to the system <part-num-ref name="system">10</part-num-ref>
|
| 862 |
+
when the air compressor <part-num-ref name="air compressor">16</part-num-ref>
|
| 863 |
+
is engaged. For example<confidence value="5">,</confidence>
|
| 864 |
+
the electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 865 |
+
may check various inputs to determine the devices that are currently drawing power from the engine <part-num-ref name="engine">12.</part-num-ref>
|
| 866 |
+
The devices may include the generator <part-num-ref name="generator">14</part-num-ref>
|
| 867 |
+
and/or other components consuming power output by the engine <part-num-ref name="engine">12.</part-num-ref>
|
| 868 |
+
According to the power desired by these devices, as well as the power desired to engage the air compressor <part-num-ref name="air compressor">
|
| 869 |
+
<confidence value="66">16</confidence>
|
| 870 |
+
, </part-num-ref>
|
| 871 |
+
the electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 872 |
+
may determine the lowest speed of the engine <part-num-ref name="engine">12</part-num-ref>
|
| 873 |
+
to operate all of the devices. For example, the electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 874 |
+
may consider setting the engine speed in a range from about <part-num-ref name="range from about">1800</part-num-ref>
|
| 875 |
+
rpm to <part-num-ref name="rpm to">3600</part-num-ref>
|
| 876 |
+
rpm. In an embodiment, the electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 877 |
+
may set the lowest speed at various increments, such as increments of <part-num-ref name="lowest speed at various increments, such as increments of">200</part-num-ref>
|
| 878 |
+
rpm, based on the desired engine speed<confidence value="5">.</confidence>
|
| 879 |
+
An embodiment may also include setting the speed of the engine <part-num-ref name="engine">12</part-num-ref>
|
| 880 |
+
to any speed within a given range, based on the determination of the lowest speed. Providing settings that are incremental or that may be varied infinitely may depend on the ability of the electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 881 |
+
to resolve an accurate speed and the capability of the governor <part-num-ref name="governor">80</part-num-ref>
|
| 882 |
+
to regulate the engine <part-num-ref name="engine">12.</part-num-ref>
|
| 883 |
+
Other parameters may also be considered to determine the lowest engine speed <part-num-ref name="lowest engine speed">108.</part-num-ref>
|
| 884 |
+
For example, embodiments may include monitoring the engine temperature, the oil temperature, the oil pressure, and the like. Other considerations may include determining whether the loads being serviced, such as welding or AC power, may be reduced without <confidence value="8">l</confidence>
|
| 885 |
+
owering their performance below an acceptable level. Based on <boundary-data type="header">
|
| 886 |
+
<confidence value="88">17</confidence>
|
| 887 |
+
</boundary-data>
|
| 888 |
+
<page-break num="18"/>
|
| 889 |
+
<boundary-data type="header">20724</boundary-data>
|
| 890 |
+
such parameters, the electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 891 |
+
may assess the operating conditions and limitations to determine the lowest acceptable engine speed<confidence value="5">.</confidence>
|
| 892 |
+
</p>
|
| 893 |
+
<p id="p-53" num="53">
|
| 894 |
+
<confidence value="5">[</confidence>
|
| 895 |
+
0046<confidence value="4">]</confidence>
|
| 896 |
+
The system <part-num-ref name="system">10</part-num-ref>
|
| 897 |
+
may then check to determine if the engine speed is at or below the lowest acceptable engine speed, as depicted at block <part-num-ref name="lowest acceptable engine speed, as depicted at block">110.</part-num-ref>
|
| 898 |
+
In an embodiment, the electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 899 |
+
may monitor an input signal indicative of engine speed and compare the signal to the lowest acceptable engine speed, determined previously at block <part-num-ref name="lowest acceptable engine speed, determined previously at block">108.</part-num-ref>
|
| 900 |
+
If the system <part-num-ref name="system">10</part-num-ref>
|
| 901 |
+
determines that the current engine speed is not at or below the lowest acceptable level, the system <part-num-ref name="system">10</part-num-ref>
|
| 902 |
+
may lower the engine speed to the lowest acceptable engine speed, as depicted at block <part-num-ref name="lowest acceptable engine speed, as depicted at block">
|
| 903 |
+
<confidence value="5">1</confidence>
|
| 904 |
+
12. </part-num-ref>
|
| 905 |
+
For example, if the electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 906 |
+
determines that the input signal indicates an engine speed that is above the lowest acceptable level, the electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 907 |
+
may output a signal to the governor <part-num-ref name="governor">80</part-num-ref>
|
| 908 |
+
that is configured to lower the engine speed. In response to the signal from the electronic control <part-num-ref name="electronic control">84,</part-num-ref>
|
| 909 |
+
the governor <part-num-ref name="governor">80</part-num-ref>
|
| 910 |
+
may regulate the speed of the engine <part-num-ref name="engine">12,</part-num-ref>
|
| 911 |
+
as desired. For example, the governor <part-num-ref name="governor">80</part-num-ref>
|
| 912 |
+
may implement an <confidence value="885">on-</confidence>
|
| 913 |
+
board routine to reduce the engine speed below the desired level, or the governor <part-num-ref name="governor">80</part-num-ref>
|
| 914 |
+
may incrementally reduce the engine speed and allow the loop illustrated by blocks <part-num-ref name="loop illustrated by blocks">104,</part-num-ref>
|
| 915 |
+
<part-num-ref name="loop illustrated by blocks 104,">108,</part-num-ref>
|
| 916 |
+
<part-num-ref name="loop illustrated by blocks 104, 108,">110</part-num-ref>
|
| 917 |
+
and <part-num-ref name="and">112</part-num-ref>
|
| 918 |
+
to verify that a compressor request is still active and continue to command a reduction in the engine speed until the engine speed is at or below the lowest acceptable level. </p>
|
| 919 |
+
<p id="p-54" num="54">[0047] The system <part-num-ref name="system">10</part-num-ref>
|
| 920 |
+
may engage the compressor, as depicted at block <part-num-ref name="compressor, as depicted at block">114,</part-num-ref>
|
| 921 |
+
when the engine speed is at or below the lowest acceptable level, as determined at block <part-num-ref name="lowest acceptable level, as determined at block">
|
| 922 |
+
<confidence value="5">1</confidence>
|
| 923 |
+
10. </part-num-ref>
|
| 924 |
+
<confidence value="5">I</confidence>
|
| 925 |
+
n an embodiment, engaging the air compressor <part-num-ref name="air compressor">16</part-num-ref>
|
| 926 |
+
may include the electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 927 |
+
outputting a signal configured to engage the clutch <part-num-ref name="clutch">82.</part-num-ref>
|
| 928 |
+
As described previously, the signal may include a digital clutch signal or an analog clutch signal transmitted by the electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 929 |
+
to the clutch <part-num-ref name="clutch">82.</part-num-ref>
|
| 930 |
+
Once the compressor is engaged <part-num-ref name="compressor is engaged">
|
| 931 |
+
<confidence value="5">1</confidence>
|
| 932 |
+
14, </part-num-ref>
|
| 933 |
+
the system <part-num-ref name="system">10</part-num-ref>
|
| 934 |
+
may then bring the engine <part-num-ref name="engine">12</part-num-ref>
|
| 935 |
+
to the desired speed, as indicated by block <part-num-ref name="desired speed, as indicated by block">
|
| 936 |
+
<confidence value="5">1</confidence>
|
| 937 |
+
16. </part-num-ref>
|
| 938 |
+
In an embodiment, bringing the engine to the desired speed <part-num-ref name="desired speed">116</part-num-ref>
|
| 939 |
+
may include transmitting signals to the governor <part-num-ref name="governor">80</part-num-ref>
|
| 940 |
+
to regulate the engine <part-num-ref name="engine">12</part-num-ref>
|
| 941 |
+
to a desired operating speed. For example, the electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 942 |
+
may transmit a signal indicative of the desired speed to the governor <part-num-ref name="governor">80.</part-num-ref>
|
| 943 |
+
In turn, the governor may enable the engine <part-num-ref name="engine">12</part-num-ref>
|
| 944 |
+
to operate at an increased operating speed. The process of bringing the <boundary-data type="header">
|
| 945 |
+
<confidence value="88">18</confidence>
|
| 946 |
+
</boundary-data>
|
| 947 |
+
<page-break num="19"/>
|
| 948 |
+
<boundary-data type="header">20724</boundary-data>
|
| 949 |
+
engine to the desired speed <part-num-ref name="desired speed">116</part-num-ref>
|
| 950 |
+
may include a series of speed increases, such as incremental stepping of engine speed through the various levels, or may include a single command to increase the engine speed to a given level (e.g., gradually ramp up to the desired speed over a time period). Accordingly, block <part-num-ref name="time period). Accordingly, block">116</part-num-ref>
|
| 951 |
+
may include a subroutine or several commands to bring the engine <part-num-ref name="engine">12</part-num-ref>
|
| 952 |
+
up to speed or may include a single command for the engine to operate at a desired speed. </p>
|
| 953 |
+
<p id="p-55" num="55">[0048<confidence value="5">1</confidence>
|
| 954 |
+
To monitor the status of the compressor request, the system <part-num-ref name="system">10</part-num-ref>
|
| 955 |
+
may include a routine that returns to the check for compressor request at block <part-num-ref name="check for compressor request at block">102</part-num-ref>
|
| 956 |
+
and continues to cycle through the routine illustrated by FIG. 5. For example, as depicted, the return from block <part-num-ref name="return from block">116</part-num-ref>
|
| 957 |
+
to block <part-num-ref name="to block">102</part-num-ref>
|
| 958 |
+
enables the system <part-num-ref name="system">10</part-num-ref>
|
| 959 |
+
to continuously scan for a compressor request and to respond accordingly<confidence value="5">.</confidence>
|
| 960 |
+
Thus, the system <part-num-ref name="system">10</part-num-ref>
|
| 961 |
+
may continuously scan for a compressor request <part-num-ref name="compressor request">102,</part-num-ref>
|
| 962 |
+
such as a request from the user interface <part-num-ref name="user interface">86,</part-num-ref>
|
| 963 |
+
and disengage the compressor <part-num-ref name="compressor">106,</part-num-ref>
|
| 964 |
+
regulate the engine speed <part-num-ref name="engine speed">112</part-num-ref>
|
| 965 |
+
and/or engage the compressor <part-num-ref name="compressor">
|
| 966 |
+
<confidence value="5">1</confidence>
|
| 967 |
+
14. </part-num-ref>
|
| 968 |
+
</p>
|
| 969 |
+
<p id="p-56" num="56">[0049<confidence value="5">1</confidence>
|
| 970 |
+
Further, the routine depicted in F<confidence value="5">I</confidence>
|
| 971 |
+
G. 5 may continue to run until the system <part-num-ref name="system">10</part-num-ref>
|
| 972 |
+
is shutdown. For example, the electronic control <part-num-ref name="electronic control">84</part-num-ref>
|
| 973 |
+
may continue to monitor and regulate the engine <part-num-ref name="engine">12,</part-num-ref>
|
| 974 |
+
the governor <part-num-ref name="governor">80,</part-num-ref>
|
| 975 |
+
and the clutch <part-num-ref name="clutch">82</part-num-ref>
|
| 976 |
+
and the routine may terminate upon shutdown of the electronic control <part-num-ref name="electronic control">84.</part-num-ref>
|
| 977 |
+
Accordingly, the method depicted in FIG<confidence value="5">.</confidence>
|
| 978 |
+
5 may include a technique to provide a "soft start" of the compressor <part-num-ref name="compressor">16</part-num-ref>
|
| 979 |
+
when the system <part-num-ref name="system">10</part-num-ref>
|
| 980 |
+
is started or the compressor <part-num-ref name="compressor">16</part-num-ref>
|
| 981 |
+
is started while the system <part-num-ref name="system">10</part-num-ref>
|
| 982 |
+
is already operating. In other words, the system <part-num-ref name="system">10</part-num-ref>
|
| 983 |
+
may implement a method to reduce the shock to the system <part-num-ref name="system">10</part-num-ref>
|
| 984 |
+
when the compressor <part-num-ref name="compressor">16</part-num-ref>
|
| 985 |
+
is started, whether the system <part-num-ref name="system">10</part-num-ref>
|
| 986 |
+
is just s<confidence value="8">t</confidence>
|
| 987 |
+
ar<confidence value="8">t</confidence>
|
| 988 |
+
ing or the system <part-num-ref name="system">10</part-num-ref>
|
| 989 |
+
is running at an operating speed when there is a request to turn on the air compressor <part-num-ref name="air compressor">16,</part-num-ref>
|
| 990 |
+
Again, the soft start may include reducing the engine speed, engaging the clutch, gradually ramping up the engine speed, gradually increasing engagement of the clutch, gradually increasing tension in the belt <part-num-ref name="belt">30</part-num-ref>
|
| 991 |
+
relative to the pulleys <part-num-ref name="pulleys">24</part-num-ref>
|
| 992 |
+
and <part-num-ref name="and">28,</part-num-ref>
|
| 993 |
+
or a combination thereof. </p>
|
| 994 |
+
<p id="p-57" num="57">
|
| 995 |
+
<confidence value="5">1</confidence>
|
| 996 |
+
0050<confidence value="5">1</confidence>
|
| 997 |
+
While only certain features of the invention have been illustrated and described herein, many modifications and changes will occur to those skilled in the <boundary-data type="header">
|
| 998 |
+
<confidence value="88">19</confidence>
|
| 999 |
+
</boundary-data>
|
| 1000 |
+
<page-break num="20"/>
|
| 1001 |
+
<boundary-data type="header">20724</boundary-data>
|
| 1002 |
+
art. <confidence value="5">I</confidence>
|
| 1003 |
+
t is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the invention. </p>
|
| 1004 |
+
<boundary-data type="header">
|
| 1005 |
+
<confidence value="88">20</confidence>
|
| 1006 |
+
</boundary-data>
|
| 1007 |
+
</description>
|
| 1008 |
+
</us-patent-application>
|
| 1009 |
+
|
applicant/11751302.xml
ADDED
|
@@ -0,0 +1,525 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>11751302</doc-number>
|
| 8 |
+
<date>2007-05-21</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<heading id="h-1">METHOD AND APPARATUS FOR PROCESSING PACKETS</heading>
|
| 14 |
+
<heading id="h-2">BACKGROUND OF THE INVENTION</heading>
|
| 15 |
+
<p id="p-1" num="1">1. Field of the Invention:</p>
|
| 16 |
+
<p id="p-2" num="2">[0001<confidence value="4">]</confidence>
|
| 17 |
+
The present invention relates generally to an improved data processing system and in particular to a method and apparatus for processing data. Still more particularly, the present invention relates to a computer implemented method, apparatus, and computer usable program code for processing packets for transmission on a network. </p>
|
| 18 |
+
<p id="p-3" num="3">2. Description of the Related Art:</p>
|
| 19 |
+
<p id="p-4" num="4">[0002] Computers and other devices on a network, such as a local area network (LAN) or the Internet, often exchange data with other computers or devices. For example, a word processing application may retrieve a document from storage device located on another computer or save a document onto a storage device on another computer. A browser application may send information, such as a request for a web page. In response to the request, the browser application may receive a web page from a web site located on a server computer. Further, the browser application may send information, such as data entered into a form on a downloaded web page to a server. All of these different types of data transmissions are accomplished by sending data across a network connection using discrete segments of data. The data sent on to a network is referred to as a packet.</p>
|
| 20 |
+
<p id="p-5" num="5">[0003] Operating systems typically include a network protocol stack that is used to transmit data received by an <boundary-data type="header">
|
| 21 |
+
<confidence value="5">1</confidence>
|
| 22 |
+
</boundary-data>
|
| 23 |
+
<boundary-data type="header">Docket No. AUS920070450US1</boundary-data>
|
| 24 |
+
<page-break num="2"/>
|
| 25 |
+
application for transmission on to a network. This data is typically received in the form of a set of memory locations, such as a set of buffers in the memory of a computer. </p>
|
| 26 |
+
<p id="p-6" num="6">[0004] Normally, data for packets are stored in system buffers. The data in these types of buffers are either copied by the network device driver to pre-registered transmit buffers or the system buffers are registered dynamically or "on-the-fly" to allow the network adapter to access the data in these buffers. In transmitting data in packets, the network adapter requires access to the memory buffer.</p>
|
| 27 |
+
<p id="p-7" num="7">[0005] The process of obtaining the memory address accessible by a network adapter and making the underlying memory visible to the network adapter is referred to as "registration". The processor cycles and/or execution time for registration are significant with respect to performance in transmitting packets. If the buffer in which data for a packet is not registered or cannot be registered, then the data is copied to a buffer or memory location that can be accessed by the adapter. This process also takes time and resources.</p>
|
| 28 |
+
<p id="p-8" num="8">[0006] The networking protocol in the AIX<confidence value="5">®</confidence>
|
| 29 |
+
operating system currently implements interface specific network buffers. AIX<confidence value="5">®</confidence>
|
| 30 |
+
is a registered trademark of International Business Machines Corporation. These types of buffers may be used to improve the performance or speed at which data is transmitted by a networking protocol stack on to the network, due to the fact that these interface specific network buffers are pre-registered with the network adapter. </p>
|
| 31 |
+
<boundary-data type="header">
|
| 32 |
+
<confidence value="8">2</confidence>
|
| 33 |
+
</boundary-data>
|
| 34 |
+
<boundary-data type="header">Docket No. A<confidence value="5">U</confidence>
|
| 35 |
+
S92007<confidence value="5886688">0450US1</confidence>
|
| 36 |
+
</boundary-data>
|
| 37 |
+
<p id="p-9" num="9">
|
| 38 |
+
<page-break num="3"/>
|
| 39 |
+
<confidence value="5">[</confidence>
|
| 40 |
+
0007<confidence value="5">]</confidence>
|
| 41 |
+
Performance gains are obtained with these types of buffers because a network device driver does not have to copy a packet for transmission to pre-registered transmit buffers. As a result, the overhead of a copy operation needed to place data received from an application into pre- registered transmit buffers is avoided. In some cases, the network device driver does not have to perform an on-the- fly or dynamic registration of a transmit buffer containing a packet for transmission. This situation results in avoiding a series of system calls that require time in terms of processor cycles and/or completion time. </p>
|
| 42 |
+
<p id="p-10" num="10">[0008] As a result, interface specific buffers provide a significant performance advantage for transmitting data because the data does not have to be copied or registered dynamically.</p>
|
| 43 |
+
<p id="p-11" num="11">[0009] In some cases, however, the application may pass a list of network buffers in which this list contains both interface specific buffers and regular or non-interface specific buffers. This list may result in data for a packet for transmission to contain both interface specific buffers and non-interface specific buffers. The processing of data found in mixed types of buffers like these result in the network device driver treating the entire packet as being located in a non-interface specific buffer. As a result, both interface specific buffers and non-interface specific buffers are treated the same in which either a registration of the buffers occurs or the data is copied into pre-registered buffers.</p>
|
| 44 |
+
<boundary-data type="header">
|
| 45 |
+
<confidence value="8">3</confidence>
|
| 46 |
+
</boundary-data>
|
| 47 |
+
<boundary-data type="header">Docket No. AUS92007<confidence value="5885588">0450US1</confidence>
|
| 48 |
+
</boundary-data>
|
| 49 |
+
<heading id="h-3">SUMMARY OF THE INVENTION</heading>
|
| 50 |
+
<p id="p-12" num="12">
|
| 51 |
+
<page-break num="4"/>
|
| 52 |
+
[0010] The illustrative embodiments provide a computer implemented method, apparatus, and computer usable program code for processing packets for transmission. A set of interface specific network buffers is identified from a plurality of buffers containing data for a packet received for transmission. A data structure describing the set of interface specific network buffers within the plurality of buffers is created, wherein a section in the data structure for an interface specific network buffer in the set of interface specific network buffers includes information about a piece of data in interface specific network buffer, wherein the data structure is used to process the packet for transmission. </p>
|
| 53 |
+
<boundary-data type="header">
|
| 54 |
+
<confidence value="8">4</confidence>
|
| 55 |
+
</boundary-data>
|
| 56 |
+
<boundary-data type="header">Docket No. AUS920070450<confidence value="488">US1</confidence>
|
| 57 |
+
</boundary-data>
|
| 58 |
+
<heading id="h-4">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
|
| 59 |
+
<p id="p-13" num="13">
|
| 60 |
+
<page-break num="5"/>
|
| 61 |
+
[001<confidence value="55">1.</confidence>
|
| 62 |
+
] The novel features believed characteristic of the invention are set forth in the appended claims. The invention itself, however, as well as a preferred mode of use, further objectives and advantages thereof, will best be understood by reference to the following detailed description of an illustrative embodiment when read in conjunction with the accompanying drawings, wherein: </p>
|
| 63 |
+
<p id="p-14" num="14">[0012] Figure 1 is a block diagram of a data processing system in which illustrative embodiments may be implemented;</p>
|
| 64 |
+
<p id="p-15" num="15">[0013] Figure 2 is a diagram of a transmission control protocol/Internet protocol (T<confidence value="66">CP</confidence>
|
| 65 |
+
/IP) and similar protocols in accordance with an illustrative embodiment; </p>
|
| 66 |
+
<p id="p-16" num="16">[0014] Figure 3 is a diagram illustrating components used in processing data for packets for transmission in accordance with an illustrative embodiment;</p>
|
| 67 |
+
<p id="p-17" num="17">[0015] Figure 4 is a diagram illustrating an entry in a table of buffers in accordance with an illustrative embodiment;</p>
|
| 68 |
+
<p id="p-18" num="18">[0016] Figure 5 is a flowchart of a process for processing data for transmission on a network in accordance with an illustrative embodiment;</p>
|
| 69 |
+
<p id="p-19" num="19">[0017<confidence value="5">]</confidence>
|
| 70 |
+
Figure 6 is a flowchart of a process for processing a packet of data for transmission in accordance with an illustrative embodiment; and [0018<confidence value="5">]</confidence>
|
| 71 |
+
Figure 7 is a flowchart of a process for processing a table of buffers in accordance with an illustrative embodiment. </p>
|
| 72 |
+
<boundary-data type="header">
|
| 73 |
+
<confidence value="8">5</confidence>
|
| 74 |
+
</boundary-data>
|
| 75 |
+
<boundary-data type="header">Docket No. A<confidence value="4">U</confidence>
|
| 76 |
+
S920070450<confidence value="488">US1</confidence>
|
| 77 |
+
</boundary-data>
|
| 78 |
+
<heading id="h-5">DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT</heading>
|
| 79 |
+
<p id="p-20" num="20">
|
| 80 |
+
<page-break num="6"/>
|
| 81 |
+
<confidence value="5">[</confidence>
|
| 82 |
+
0019<confidence value="5">]</confidence>
|
| 83 |
+
With reference now to the figures and in particular with reference to Figure 1, a block diagram of a data processing system is depicted in which illustrative embodiments may be implemented. <confidence value="5">I</confidence>
|
| 84 |
+
n the depicted example, data processing system <part-num-ref name="depicted example, data processing system">100</part-num-ref>
|
| 85 |
+
employs a hub architecture including a north bridge and memory controller hub (NB/MCH) <part-num-ref name="north bridge and memory controller hub (NB/MCH)">102</part-num-ref>
|
| 86 |
+
and a south bridge and input/output <confidence value="6686">(I/0</confidence>
|
| 87 |
+
) controller hub (SB/<confidence value="5">I</confidence>
|
| 88 |
+
CH) <part-num-ref name="south bridge and input/output (I/0) controller hub (SB/ICH)">104.</part-num-ref>
|
| 89 |
+
Processing unit <part-num-ref name="south bridge and input/output (I/0) controller hub (SB/ICH) 104. Processing unit">106,</part-num-ref>
|
| 90 |
+
main memory <part-num-ref name="south bridge and input/output (I/0) controller hub (SB/ICH) 104. Processing unit 106, main memory">108,</part-num-ref>
|
| 91 |
+
and graphics processor <part-num-ref name="south bridge and input/output (I/0) controller hub (SB/ICH) 104. Processing unit 106, main memory 108, and graphics processor">110</part-num-ref>
|
| 92 |
+
are coupled to north bridge and memory controller hub <part-num-ref name="are coupled to north bridge and memory controller hub">102.</part-num-ref>
|
| 93 |
+
Processing unit <part-num-ref name="are coupled to north bridge and memory controller hub 102. Processing unit">106</part-num-ref>
|
| 94 |
+
may contain one or more processors and even may be implemented using one or more heterogeneous processor systems. Graphics processor <part-num-ref name="may contain one or more processors and even may be implemented using one or more heterogeneous processor systems. Graphics processor">110</part-num-ref>
|
| 95 |
+
may be coupled to the NB/MCH through an accelerated graphics port (AGP), for example. </p>
|
| 96 |
+
<p id="p-21" num="21">[0020] <confidence value="5">I</confidence>
|
| 97 |
+
n the depicted example, local area network (LAN) adapter <part-num-ref name="depicted example, local area network (LAN) adapter">112</part-num-ref>
|
| 98 |
+
is coupled to south bridge and I/O controller hub <part-num-ref name="is coupled to south bridge and I/O controller hub">104,</part-num-ref>
|
| 99 |
+
audio adapter <part-num-ref name="is coupled to south bridge and I/O controller hub 104, audio adapter">116,</part-num-ref>
|
| 100 |
+
keyboard and mouse adapter <part-num-ref name="is coupled to south bridge and I/O controller hub 104, audio adapter 116, keyboard and mouse adapter">120,</part-num-ref>
|
| 101 |
+
modem <part-num-ref name="is coupled to south bridge and I/O controller hub 104, audio adapter 116, keyboard and mouse adapter 120, modem">122,</part-num-ref>
|
| 102 |
+
read only memory (ROM) <part-num-ref name="is coupled to south bridge and I/O controller hub 104, audio adapter 116, keyboard and mouse adapter 120, modem 122, read only memory (ROM)">124,</part-num-ref>
|
| 103 |
+
universal serial bus (USB) and other ports <part-num-ref name="is coupled to south bridge and I/O controller hub 104, audio adapter 116, keyboard and mouse adapter 120, modem 122, read only memory (ROM) 124, universal serial bus (USB) and other ports">132,</part-num-ref>
|
| 104 |
+
PC<confidence value="5">I</confidence>
|
| 105 |
+
/PC<confidence value="5">I</confidence>
|
| 106 |
+
e devices <part-num-ref name="is coupled to south bridge and I/O controller hub 104, audio adapter 116, keyboard and mouse adapter 120, modem 122, read only memory (ROM) 124, universal serial bus (USB) and other ports 132, PCI/PCIe devices">134</part-num-ref>
|
| 107 |
+
are coupled to south bridge and I/O controller hub <part-num-ref name="are coupled to south bridge and I/O controller hub">104</part-num-ref>
|
| 108 |
+
through bus <part-num-ref name="through bus">138.</part-num-ref>
|
| 109 |
+
</p>
|
| 110 |
+
<p id="p-22" num="22">Hard disk drive (HDD) 126 and CD-ROM <part-num-ref name="and CD-ROM">130</part-num-ref>
|
| 111 |
+
are coupled to south bridge and I/O controller hub <part-num-ref name="are coupled to south bridge and I/O controller hub">104</part-num-ref>
|
| 112 |
+
through bus <part-num-ref name="through bus">140.</part-num-ref>
|
| 113 |
+
</p>
|
| 114 |
+
<p id="p-23" num="23">
|
| 115 |
+
<confidence value="5">[</confidence>
|
| 116 |
+
0021] PCI/PCIe devices may include, for example, Ethernet adapters, add-in cards, and PC cards for notebook computers. </p>
|
| 117 |
+
<p id="p-24" num="24">PCI uses a card bus controller, while PC<confidence value="5">I</confidence>
|
| 118 |
+
e does not. RO<confidence value="5">M</confidence>
|
| 119 |
+
<part-num-ref name="card bus controller, while PCIe does not. ROM">124</part-num-ref>
|
| 120 |
+
may be, for example, a flash binary input/output system (BIOS). Hard disk drive <part-num-ref name="flash binary input/output system (BIOS). Hard disk drive">126</part-num-ref>
|
| 121 |
+
and CD-ROM <part-num-ref name="and CD-ROM">130</part-num-ref>
|
| 122 |
+
may use, for example, an integrated drive electronics (IDE) or serial <boundary-data type="header">
|
| 123 |
+
<confidence value="8">6</confidence>
|
| 124 |
+
</boundary-data>
|
| 125 |
+
<boundary-data type="header">Docket No. AUS920070450US1</boundary-data>
|
| 126 |
+
<page-break num="7"/>
|
| 127 |
+
advanced technology attachment (SATA) interface. A super I/O <confidence value="8666">(SIO</confidence>
|
| 128 |
+
) device <part-num-ref name="super I/O (SIO) device">136</part-num-ref>
|
| 129 |
+
may be coupled to south bridge and I/O controller hub <part-num-ref name="may be coupled to south bridge and I/O controller hub">104.</part-num-ref>
|
| 130 |
+
</p>
|
| 131 |
+
<p id="p-25" num="25">[0022] An operating system runs on processing unit <part-num-ref name="operating system runs on processing unit">106.</part-num-ref>
|
| 132 |
+
</p>
|
| 133 |
+
<p id="p-26" num="26">This operating system coordinates and controls various components within data processing system 100 in Fig<confidence value="5">u</confidence>
|
| 134 |
+
re 1. </p>
|
| 135 |
+
<p id="p-27" num="27">The operating system may be a commercially available operating system, such as Microsoft<confidence value="2">®</confidence>
|
| 136 |
+
Windows XP<confidence value="4">®</confidence>
|
| 137 |
+
. (Microsoft<confidence value="4">®</confidence>
|
| 138 |
+
<confidence value="86">an</confidence>
|
| 139 |
+
d Windows XP<confidence value="4">®</confidence>
|
| 140 |
+
are trademarks of Microsoft Corporation in the United States, other countries, or both). An object oriented programming system, such as the <confidence value="666652">JavaTM</confidence>
|
| 141 |
+
programming system, may run in conjunction with the operating system and provides calls to the operating system from <confidence value="666652">JavaTM</confidence>
|
| 142 |
+
programs or applications executing on data processing system <part-num-ref name="operating system from JavaTM programs or applications executing on data processing system">100.</part-num-ref>
|
| 143 |
+
</p>
|
| 144 |
+
<p id="p-28" num="28">Java and all Java<confidence value="555">TM-</confidence>
|
| 145 |
+
based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. </p>
|
| 146 |
+
<p id="p-29" num="29">[0023] Instructions for the operating system, the object- oriented programming system, and applications or programs are located on storage devices, such as hard disk drive <part-num-ref name="object- oriented programming system, and applications or programs are located on storage devices, such as hard disk drive">126.</part-num-ref>
|
| 147 |
+
</p>
|
| 148 |
+
<p id="p-30" num="30">These instructions and may be loaded into main memory 108 for execution by processing unit <part-num-ref name="for execution by processing unit">106.</part-num-ref>
|
| 149 |
+
The processes of the illustrative embodiments may be performed by processing unit <part-num-ref name="illustrative embodiments may be performed by processing unit">106</part-num-ref>
|
| 150 |
+
using computer implemented instructions, which may be located in a memory. An example of a memory is main memory <part-num-ref name="memory is main memory">108,</part-num-ref>
|
| 151 |
+
read only memory <part-num-ref name="memory is main memory 108, read only memory">124,</part-num-ref>
|
| 152 |
+
or in one or more peripheral devices. </p>
|
| 153 |
+
<p id="p-31" num="31">[0024] The hardware shown in Figure 1 may vary depending on the implementation of the illustrated embodiments.</p>
|
| 154 |
+
<p id="p-32" num="32">Other internal hardware or peripheral devices, such as flash memory, equivalent non-volatile memory, or optical <boundary-data type="header">
|
| 155 |
+
<confidence value="8">7</confidence>
|
| 156 |
+
</boundary-data>
|
| 157 |
+
<boundary-data type="header">Docket No. AUS920070450US1</boundary-data>
|
| 158 |
+
<page-break num="8"/>
|
| 159 |
+
disk drives and the like, may be used in addition to or in place of the hardware depicted in Figure 1. Additionally, the processes of the illustrative embodiments may be applied to a multiprocessor data processing system. </p>
|
| 160 |
+
<p id="p-33" num="33">[0025] The systems and components shown in Figure 1 can be varied from the illustrative examples shown. In some illustrative examples, data processing system <part-num-ref name="illustrative examples shown. In some illustrative examples, data processing system">100</part-num-ref>
|
| 161 |
+
may be a personal digital assistant (PDA)<confidence value="5">.</confidence>
|
| 162 |
+
A personal digital assistant generally is configured with flash memory to provide a non-volatile memory for storing operating system files and/or user-generated data. Additionally, data processing system <part-num-ref name="non-volatile memory for storing operating system files and/or user-generated data. Additionally, data processing system">100</part-num-ref>
|
| 163 |
+
can be a tablet computer, laptop computer, or telephone device. </p>
|
| 164 |
+
<p id="p-34" num="34">[0026] Other components shown in Figure 1 can be varied from the illustrative examples shown. For example, a bus system may be comprised of one or more buses, such as a system bus, an I/O bus, and a PCI bus. Of course the bus system may be implemented using any suitable type of communications fabric or architecture that provides for a transfer of data between different components or devices attached to the fabric or architecture. Additionally, a communications unit may include one or more devices used to transmit and receive data, such as a modem or a network adapter. Further, a memory may be, for example, main memory <part-num-ref name="memory may be, for example, main memory">108</part-num-ref>
|
| 165 |
+
or a cache such as found in north bridge and memory controller hub <part-num-ref name="cache such as found in north bridge and memory controller hub">102.</part-num-ref>
|
| 166 |
+
Also, a processing unit may include one or more processors or CPUs. </p>
|
| 167 |
+
<p id="p-35" num="35">[0027] The depicted examples in Figure 1 are not meant to imply architectural limitations. In addition, the illustrative embodiments provide for a computer implemented method, apparatus, and computer usable program code for <boundary-data type="header">
|
| 168 |
+
<confidence value="8">8</confidence>
|
| 169 |
+
</boundary-data>
|
| 170 |
+
<boundary-data type="header">Docket No. AUS920070450US1</boundary-data>
|
| 171 |
+
<page-break num="9"/>
|
| 172 |
+
compiling source code and for executing code. The methods described with respect to the depicted embodiments may be performed in a data processing system, such as data processing system <part-num-ref name="data processing system, such as data processing system">100</part-num-ref>
|
| 173 |
+
shown in Figure 1. </p>
|
| 174 |
+
<p id="p-36" num="36">
|
| 175 |
+
<confidence value="5">[</confidence>
|
| 176 |
+
0028] Next, Figure 2 is a diagram of a transmission control protocol/Internet protocol (TCP/IP) and similar protocols is depicted in accordance with an illustrative embodiment. TCP/IP a<confidence value="5">n</confidence>
|
| 177 |
+
d similar protocols are utilized by communications architecture <part-num-ref name="illustrative embodiment. TCP/IP and similar protocols are utilized by communications architecture">200.</part-num-ref>
|
| 178 |
+
In this example, communications architecture <part-num-ref name="illustrative embodiment. TCP/IP and similar protocols are utilized by communications architecture 200. In this example, communications architecture">200</part-num-ref>
|
| 179 |
+
is a 4-layer system. This architecture includes application layer <part-num-ref name="4-layer system. This architecture includes application layer">202,</part-num-ref>
|
| 180 |
+
transport layer <part-num-ref name="4-layer system. This architecture includes application layer 202, transport layer">204,</part-num-ref>
|
| 181 |
+
network layer <part-num-ref name="4-layer system. This architecture includes application layer 202, transport layer 204, network layer">206,</part-num-ref>
|
| 182 |
+
and link layer <part-num-ref name="4-layer system. This architecture includes application layer 202, transport layer 204, network layer 206, and link layer">208.</part-num-ref>
|
| 183 |
+
Each layer is responsible for handling various communications tasks. </p>
|
| 184 |
+
<p id="p-37" num="37">
|
| 185 |
+
<confidence value="5">[</confidence>
|
| 186 |
+
0029] Link layer 208 also is referred to as the data- link layer or the network interface layer and normally includes the device driver in the operating system and the corresponding network interface card in the computer. This layer handles all the hardware details of physically interfacing with the network media being used, such as optical cables or Ethernet cables. </p>
|
| 187 |
+
<p id="p-38" num="38">[0030] Network layer 206 also is referred to as the internet layer and handles the movement of packets of data around the network. For example, network layer <part-num-ref name="network. For example, network layer">206</part-num-ref>
|
| 188 |
+
handles the routing of various packets of data that are transferred over the network. Network layer <part-num-ref name="network. Network layer">206</part-num-ref>
|
| 189 |
+
in the TCP/IP suite is comprised of several protocols, including Internet protocol (IP), Internet control message protocol (<confidence value="2222">ICMP</confidence>
|
| 190 |
+
), and Internet group management protocol (IGMP)<confidence value="5">.</confidence>
|
| 191 |
+
</p>
|
| 192 |
+
<p id="p-39" num="39">[0031] Next, transport layer 204 provides an interface between network layer <part-num-ref name="interface between network layer">206</part-num-ref>
|
| 193 |
+
and application layer <part-num-ref name="and application layer">202</part-num-ref>
|
| 194 |
+
that <boundary-data type="header">
|
| 195 |
+
<confidence value="8">9</confidence>
|
| 196 |
+
</boundary-data>
|
| 197 |
+
<boundary-data type="header">Docket No. A<confidence value="5">U</confidence>
|
| 198 |
+
S92007<confidence value="5884">0450</confidence>
|
| 199 |
+
US1 </boundary-data>
|
| 200 |
+
<page-break num="10"/>
|
| 201 |
+
facilitates the transfer of data between two host computers. Transport layer <part-num-ref name="transfer of data between two host computers. Transport layer">204</part-num-ref>
|
| 202 |
+
is concerned with things such as, for example, dividing the data passed to it from the application into appropriately sized chunks for the network layer below, acknowledging received packets, and setting timeouts to make certain the other end acknowledges packets that are sent. In the TCP/IP protocol suite, two distinctly different transport protocols are present, TCP and User datagram protocol (UDP). TCP provides reliability services to ensure that data is properly transmitted between two hosts, including dropout detection and retransmission services. </p>
|
| 203 |
+
<p id="p-40" num="40">[0032] Conversely, UDP provides a much simpler service to the application layer by merely sending packets of data called datagrams from one host to the other, without providing any mechanism for guaranteeing that the data is properly transferred. When using UDP, the application layer must perform the reliability functionality.</p>
|
| 204 |
+
<p id="p-41" num="41">[0033] Application layer 202 handles the details of the particular application. Many common TCP/IP applications are present for almost every implementation, including a Telnet for remote login; a file transfer protocol (FTP); a simple mail transfer protocol (SMTP) for electronic mail;</p>
|
| 205 |
+
<p id="p-42" num="42">and a simple network management protocol (SNMP)<confidence value="5">.</confidence>
|
| 206 |
+
</p>
|
| 207 |
+
<p id="p-43" num="43">[0034] The different illustrative embodiments may be implemented in link layer <part-num-ref name="different illustrative embodiments may be implemented in link layer">208</part-num-ref>
|
| 208 |
+
in these examples. More specifically, different embodiments for processing data for transmission in packets onto a network may be implemented in a network device driver in link layer <part-num-ref name="network device driver in link layer">208.</part-num-ref>
|
| 209 |
+
</p>
|
| 210 |
+
<p id="p-44" num="44">[0035] The different illustrative embodiments recognize that mixed buffers containing interface specific network <boundary-data type="header">
|
| 211 |
+
<confidence value="88">10</confidence>
|
| 212 |
+
</boundary-data>
|
| 213 |
+
<boundary-data type="header">Docket No. AUS920070450US1</boundary-data>
|
| 214 |
+
<page-break num="11"/>
|
| 215 |
+
buffers and non-interface specific network buffers, may be received for processing. Currently, the processing of these types of buffers is to process the buffers for a packet as all being non-interface specific network buffers. </p>
|
| 216 |
+
<p id="p-45" num="45">This type of processing reduces the performance gain intended by the use of interface specific network buffers.</p>
|
| 217 |
+
<p id="p-46" num="46">As a result, processing buffers in this manner wastes resources because interface specific network buffers are being processed in a slower manner than intended.</p>
|
| 218 |
+
<p id="p-47" num="47">[0036<confidence value="5">]</confidence>
|
| 219 |
+
Thus, the different illustrative embodiments provide a computer implemented method, apparatus, and computer usable program code processing packets for transmission. A set of interface specific network buffers are identified from a plurality of buffers containing data for a packet that is received for transmission. The set of interface network buffers is a set of one or more interface specific network buffers in these examples. A data structure is created in which the data structure describes the set of interface specific network buffers within the plurality of buffers. A section in the data structure for an interface specific network buffer in the set of interface specific network buffers includes information about a piece of data in the interface specific network buffer. </p>
|
| 220 |
+
<p id="p-48" num="48">[0037<confidence value="5">]</confidence>
|
| 221 |
+
The data structure is used to process the packet for transmission. In this manner, buffers that are identified as interface specific network buffers may be processed as intended, while other buffers may be processed by copying data to a pre-registered transmission buffer or dynamically registering the buffer with the adapter. </p>
|
| 222 |
+
<boundary-data type="header">
|
| 223 |
+
<confidence value="88">11</confidence>
|
| 224 |
+
</boundary-data>
|
| 225 |
+
<boundary-data type="header">Docket No. AUS920070450US1</boundary-data>
|
| 226 |
+
<p id="p-49" num="49">
|
| 227 |
+
<page-break num="12"/>
|
| 228 |
+
[0038] Turning now to Figure 3, a diagram illustrating components used in processing data for packets for transmission is depicted in accordance with an illustrative embodiment. In this example, application <part-num-ref name="illustrative embodiment. In this example, application">300</part-num-ref>
|
| 229 |
+
may generate data for transmission onto a network. </p>
|
| 230 |
+
<p id="p-50" num="50">[0039] In this particular example, application 300 stores may store or write data to a location that in accessed across a network. When application <part-num-ref name="network. When application">300</part-num-ref>
|
| 231 |
+
writes the data to transport layer <part-num-ref name="data to transport layer">301,</part-num-ref>
|
| 232 |
+
this layer may write data <part-num-ref name="data to transport layer 301, this layer may write data">302</part-num-ref>
|
| 233 |
+
in interface specific network buffers <part-num-ref name="in interface specific network buffers">304.</part-num-ref>
|
| 234 |
+
Data <part-num-ref name="in interface specific network buffers 304. Data">302</part-num-ref>
|
| 235 |
+
may be stored in one or more buffers in interface specific network buffers <part-num-ref name="may be stored in one or more buffers in interface specific network buffers">304.</part-num-ref>
|
| 236 |
+
Transport layer <part-num-ref name="may be stored in one or more buffers in interface specific network buffers 304. Transport layer">301</part-num-ref>
|
| 237 |
+
also may write data <part-num-ref name="also may write data">306</part-num-ref>
|
| 238 |
+
to system buffers <part-num-ref name="to system buffers">308.</part-num-ref>
|
| 239 |
+
Data <part-num-ref name="to system buffers 308. Data">306</part-num-ref>
|
| 240 |
+
may be stored in one or more buffers in system buffers <part-num-ref name="may be stored in one or more buffers in system buffers">308.</part-num-ref>
|
| 241 |
+
</p>
|
| 242 |
+
<p id="p-51" num="51">
|
| 243 |
+
<confidence value="5">[</confidence>
|
| 244 |
+
0040<confidence value="4">]</confidence>
|
| 245 |
+
In these examples, interface specific network buffers and transmit buffers 309 are buffers assigned to network driver <part-num-ref name="are buffers assigned to network driver">310.</part-num-ref>
|
| 246 |
+
Interface specific network buffers <part-num-ref name="are buffers assigned to network driver 310. Interface specific network buffers">304</part-num-ref>
|
| 247 |
+
may be passed up to application <part-num-ref name="may be passed up to application">300</part-num-ref>
|
| 248 |
+
through the stack for use in placing data <part-num-ref name="stack for use in placing data">302.</part-num-ref>
|
| 249 |
+
In these examples, system buffers <part-num-ref name="stack for use in placing data 302. In these examples, system buffers">308</part-num-ref>
|
| 250 |
+
are buffers that may be accessed by the application, are not mapped to network adapter <part-num-ref name="application, are not mapped to network adapter">311,</part-num-ref>
|
| 251 |
+
and do not belong to network device driver <part-num-ref name="application, are not mapped to network adapter 311, and do not belong to network device driver">310.</part-num-ref>
|
| 252 |
+
</p>
|
| 253 |
+
<p id="p-52" num="52">[0041] Access to interface specific network buffers is obtained by transport layer 301 making a request to network device driver <part-num-ref name="request to network device driver">310</part-num-ref>
|
| 254 |
+
for these types of buffers. System buffers <part-num-ref name="for these types of buffers. System buffers">308</part-num-ref>
|
| 255 |
+
are accessible to transport layer <part-num-ref name="are accessible to transport layer">301</part-num-ref>
|
| 256 |
+
without requiring a request to be made to network device driver <part-num-ref name="request to be made to network device driver">310.</part-num-ref>
|
| 257 |
+
System buffers <part-num-ref name="request to be made to network device driver 310. System buffers">308</part-num-ref>
|
| 258 |
+
are buffers do not belong to network device driver <part-num-ref name="are buffers do not belong to network device driver">310</part-num-ref>
|
| 259 |
+
and are not visible or accessible by network adapter <part-num-ref name="and are not visible or accessible by network adapter">311</part-num-ref>
|
| 260 |
+
for transmission onto a network. </p>
|
| 261 |
+
<p id="p-53" num="53">These types of buffers are used when interface specific <boundary-data type="header">
|
| 262 |
+
<confidence value="88">12</confidence>
|
| 263 |
+
</boundary-data>
|
| 264 |
+
<boundary-data type="header">Docket No. AUS920070450US1</boundary-data>
|
| 265 |
+
<page-break num="13"/>
|
| 266 |
+
network buffers 304 are not provided by network device driver <part-num-ref name="are not provided by network device driver">310.</part-num-ref>
|
| 267 |
+
</p>
|
| 268 |
+
<p id="p-54" num="54">[0042] After transport layer 301 stores data <part-num-ref name="stores data">302</part-num-ref>
|
| 269 |
+
in interface specific network buffers <part-num-ref name="in interface specific network buffers">304</part-num-ref>
|
| 270 |
+
and data <part-num-ref name="and data">306</part-num-ref>
|
| 271 |
+
in system buffers <part-num-ref name="in system buffers">308,</part-num-ref>
|
| 272 |
+
transport layer <part-num-ref name="in system buffers 308, transport layer">301</part-num-ref>
|
| 273 |
+
informs network device driver <part-num-ref name="informs network device driver">310</part-num-ref>
|
| 274 |
+
that data is present for transmission. </p>
|
| 275 |
+
<p id="p-55" num="55">Transport layer 301 passes data <part-num-ref name="passes data">302</part-num-ref>
|
| 276 |
+
and data <part-num-ref name="and data">306</part-num-ref>
|
| 277 |
+
to network device driver <part-num-ref name="to network device driver">310</part-num-ref>
|
| 278 |
+
for processing by sending buffer list <part-num-ref name="for processing by sending buffer list">312</part-num-ref>
|
| 279 |
+
to network device driver <part-num-ref name="to network device driver">310.</part-num-ref>
|
| 280 |
+
Buffer list <part-num-ref name="to network device driver 310. Buffer list">312</part-num-ref>
|
| 281 |
+
identifies buffers containing data <part-num-ref name="identifies buffers containing data">302</part-num-ref>
|
| 282 |
+
and data <part-num-ref name="and data">306.</part-num-ref>
|
| 283 |
+
In these examples, buffer list <part-num-ref name="and data 306. In these examples, buffer list">312</part-num-ref>
|
| 284 |
+
identifies interface specific network buffers <part-num-ref name="identifies interface specific network buffers">304</part-num-ref>
|
| 285 |
+
and system buffers <part-num-ref name="and system buffers">308</part-num-ref>
|
| 286 |
+
as buffers containing data <part-num-ref name="as buffers containing data">302</part-num-ref>
|
| 287 |
+
and data <part-num-ref name="and data">306</part-num-ref>
|
| 288 |
+
as being present for transmission as a packet. </p>
|
| 289 |
+
<p id="p-56" num="56">[0043] In these illustrative examples, network device driver 310 normally would process interface specific network buffers <part-num-ref name="normally would process interface specific network buffers">304</part-num-ref>
|
| 290 |
+
in the same manner as system buffers <part-num-ref name="same manner as system buffers">308</part-num-ref>
|
| 291 |
+
because buffer list <part-num-ref name="because buffer list">312</part-num-ref>
|
| 292 |
+
contains both types of buffers. </p>
|
| 293 |
+
<p id="p-57" num="57">In the illustrative embodiments, however, this type of performance degradation is avoided because network device driver <part-num-ref name="illustrative embodiments, however, this type of performance degradation is avoided because network device driver">310</part-num-ref>
|
| 294 |
+
generates a description of the different types of buffers present in buffer list <part-num-ref name="different types of buffers present in buffer list">312</part-num-ref>
|
| 295 |
+
that contain data for a packet that is to be transmitted by network adapter <part-num-ref name="packet that is to be transmitted by network adapter">311.</part-num-ref>
|
| 296 |
+
</p>
|
| 297 |
+
<p id="p-58" num="58">[0044] Network device driver 310 uses buffer list <part-num-ref name="uses buffer list">312</part-num-ref>
|
| 298 |
+
to examine each of the buffers on buffer list <part-num-ref name="buffers on buffer list">312.</part-num-ref>
|
| 299 |
+
The header of the buffer is parsed to identify interface specific network buffers in these examples. </p>
|
| 300 |
+
<p id="p-59" num="59">[0045] From examining the buffers on buffer list <part-num-ref name="buffers on buffer list">312,</part-num-ref>
|
| 301 |
+
network device driver <part-num-ref name="buffers on buffer list 312, network device driver">310</part-num-ref>
|
| 302 |
+
creates an entry in table <part-num-ref name="entry in table">314</part-num-ref>
|
| 303 |
+
for each buffer in buffer list <part-num-ref name="for each buffer in buffer list">312</part-num-ref>
|
| 304 |
+
that is identified as an interface specific network buffer. As a result, table <part-num-ref name="result, table">314</part-num-ref>
|
| 305 |
+
<boundary-data type="header">
|
| 306 |
+
<confidence value="88">13</confidence>
|
| 307 |
+
</boundary-data>
|
| 308 |
+
<boundary-data type="header">Docket No. AUS920070450US1</boundary-data>
|
| 309 |
+
<page-break num="14"/>
|
| 310 |
+
contains an identification of all of interface specific network buffers <part-num-ref name="identification of all of interface specific network buffers">304</part-num-ref>
|
| 311 |
+
that contain data for a packet. In the depicted examples, network device driver <part-num-ref name="depicted examples, network device driver">310</part-num-ref>
|
| 312 |
+
also may create entries for buffers in buffer list <part-num-ref name="also may create entries for buffers in buffer list">312</part-num-ref>
|
| 313 |
+
that are found in system buffers <part-num-ref name="that are found in system buffers">308.</part-num-ref>
|
| 314 |
+
</p>
|
| 315 |
+
<p id="p-60" num="60">[0046] Although the depicted examples use a data structure in the form of table <part-num-ref name="form of table">314</part-num-ref>
|
| 316 |
+
to describe buffers identified in buffer list <part-num-ref name="to describe buffers identified in buffer list">312,</part-num-ref>
|
| 317 |
+
the data structure may take other forms. One example is a linked list. </p>
|
| 318 |
+
<p id="p-61" num="61">
|
| 319 |
+
<confidence value="5">[</confidence>
|
| 320 |
+
0047] After table 314 is created, network device driver <part-num-ref name="is created, network device driver">310</part-num-ref>
|
| 321 |
+
then processes the data found in buffers identified in buffer list <part-num-ref name="data found in buffers identified in buffer list">312</part-num-ref>
|
| 322 |
+
for processing by network adapter <part-num-ref name="for processing by network adapter">311.</part-num-ref>
|
| 323 |
+
If all of the buffers are located in interface specific network buffers <part-num-ref name="buffers are located in interface specific network buffers">304,</part-num-ref>
|
| 324 |
+
network device driver <part-num-ref name="buffers are located in interface specific network buffers 304, network device driver">310</part-num-ref>
|
| 325 |
+
does not need to perform any further processing of the data. </p>
|
| 326 |
+
<p id="p-62" num="62">[0048] If all of the data is located in system buffers <part-num-ref name="data is located in system buffers">308,</part-num-ref>
|
| 327 |
+
each of the buffers may be copied to transmit buffers <part-num-ref name="buffers may be copied to transmit buffers">309</part-num-ref>
|
| 328 |
+
to pass the network adapter <part-num-ref name="network adapter">311</part-num-ref>
|
| 329 |
+
for transmission onto a network. These buffers are pre-registered buffers that belong to network adapter <part-num-ref name="network. These buffers are pre-registered buffers that belong to network adapter">311.</part-num-ref>
|
| 330 |
+
These are buffers that have not been provided to transport layer <part-num-ref name="network. These buffers are pre-registered buffers that belong to network adapter 311. These are buffers that have not been provided to transport layer">301</part-num-ref>
|
| 331 |
+
in the form of interface specific network buffers. In other words, if network device driver <part-num-ref name="form of interface specific network buffers. In other words, if network device driver">310</part-num-ref>
|
| 332 |
+
does not provide any of these buffers to transport layer <part-num-ref name="does not provide any of these buffers to transport layer">301,</part-num-ref>
|
| 333 |
+
no interface specific network buffers <part-num-ref name="does not provide any of these buffers to transport layer 301, no interface specific network buffers">304</part-num-ref>
|
| 334 |
+
will be present. </p>
|
| 335 |
+
<p id="p-63" num="63">[0049] Alternatively, system buffers 308 may be registered so that network adapter <part-num-ref name="may be registered so that network adapter">311</part-num-ref>
|
| 336 |
+
can access them to send data for the packets in system buffers <part-num-ref name="packets in system buffers">308</part-num-ref>
|
| 337 |
+
onto the network. In any event, these are extra processing steps that are performed for data located in system buffers <part-num-ref name="network. In any event, these are extra processing steps that are performed for data located in system buffers">308.</part-num-ref>
|
| 338 |
+
</p>
|
| 339 |
+
<boundary-data type="header">
|
| 340 |
+
<confidence value="88">14</confidence>
|
| 341 |
+
</boundary-data>
|
| 342 |
+
<boundary-data type="header">Docket No. AUS920070450US1</boundary-data>
|
| 343 |
+
<p id="p-64" num="64">
|
| 344 |
+
<page-break num="15"/>
|
| 345 |
+
<confidence value="5">[</confidence>
|
| 346 |
+
0050<confidence value="5">]</confidence>
|
| 347 |
+
In this example, data is located both in interface specific network buffers 304 and system buffers <part-num-ref name="and system buffers">308.</part-num-ref>
|
| 348 |
+
With the different illustrative embodiments, data <part-num-ref name="different illustrative embodiments, data">302</part-num-ref>
|
| 349 |
+
located in interface specific network buffers <part-num-ref name="located in interface specific network buffers">304</part-num-ref>
|
| 350 |
+
do not require this additional processing even though data <part-num-ref name="do not require this additional processing even though data">302</part-num-ref>
|
| 351 |
+
for the same packet also is located in system buffers <part-num-ref name="same packet also is located in system buffers">308.</part-num-ref>
|
| 352 |
+
</p>
|
| 353 |
+
<p id="p-65" num="65">[0051] Instead, with a mixed list of interface specific network buffers and non-interface specific network buffers in buffer list <part-num-ref name="mixed list of interface specific network buffers and non-interface specific network buffers in buffer list">312,</part-num-ref>
|
| 354 |
+
performance gains still may achieved because the additional processing does not have to be performed for the data found in interface specific network buffers <part-num-ref name="data found in interface specific network buffers">304.</part-num-ref>
|
| 355 |
+
This differentiation of buffers is provided through table <part-num-ref name="data found in interface specific network buffers 304. This differentiation of buffers is provided through table">314</part-num-ref>
|
| 356 |
+
in these examples. In this manner, the buffers identified as interface specific network buffers <part-num-ref name="buffers identified as interface specific network buffers">304</part-num-ref>
|
| 357 |
+
in table <part-num-ref name="in table">314</part-num-ref>
|
| 358 |
+
do not have to be copied or registered as a transmit buffer by network device driver <part-num-ref name="transmit buffer by network device driver">310.</part-num-ref>
|
| 359 |
+
</p>
|
| 360 |
+
<p id="p-66" num="66">
|
| 361 |
+
<confidence value="5">[</confidence>
|
| 362 |
+
0052] Network device driver 310 traverses table <part-num-ref name="traverses table">314</part-num-ref>
|
| 363 |
+
and constructs a transmit descriptor list for use by network adapter <part-num-ref name="transmit descriptor list for use by network adapter">310.</part-num-ref>
|
| 364 |
+
In processing the buffers, network device driver <part-num-ref name="buffers, network device driver">310</part-num-ref>
|
| 365 |
+
may copy the data in that buffer into transmit buffers <part-num-ref name="data in that buffer into transmit buffers">309</part-num-ref>
|
| 366 |
+
or register that buffer as a transmit buffer for each entry that is not an interface specific network buffer associated or assigned to network device driver <part-num-ref name="interface specific network buffer associated or assigned to network device driver">310.</part-num-ref>
|
| 367 |
+
</p>
|
| 368 |
+
<p id="p-67" num="67">Thereafter, the descriptor for that entry is filled out for the data in this buffer.</p>
|
| 369 |
+
<p id="p-68" num="68">
|
| 370 |
+
<confidence value="5">[</confidence>
|
| 371 |
+
0053] If on-the-fly or dynamic registration of non- interface specific network buffers for network device driver 310 is excluded, an entry in table <part-num-ref name="entry in table">314</part-num-ref>
|
| 372 |
+
may describe a linked list of adjacent buffers. In this case, the data in those buffers may be automatically traversed in the linked list. The number of bytes specified in the length <boundary-data type="header">
|
| 373 |
+
<confidence value="88">15</confidence>
|
| 374 |
+
</boundary-data>
|
| 375 |
+
<boundary-data type="header">Docket No. AUS920070450US1</boundary-data>
|
| 376 |
+
<page-break num="16"/>
|
| 377 |
+
field in this entry beginning at the offset value found for the entry. </p>
|
| 378 |
+
<p id="p-69" num="69">[0054] For each entry that contains an interface specific network buffer usable or assigned to network device driver <part-num-ref name="interface specific network buffer usable or assigned to network device driver">310,</part-num-ref>
|
| 379 |
+
network device driver <part-num-ref name="interface specific network buffer usable or assigned to network device driver 310, network device driver">310</part-num-ref>
|
| 380 |
+
bypasses the copy or dynamic registration of the data for the buffer associated with the entry. Network device driver <part-num-ref name="entry. Network device driver">310</part-num-ref>
|
| 381 |
+
only needs to fill out the transmit descriptor for that entry. </p>
|
| 382 |
+
<p id="p-70" num="70">When all of the buffers in table <part-num-ref name="buffers in table">314</part-num-ref>
|
| 383 |
+
are processed by network device driver <part-num-ref name="are processed by network device driver">310,</part-num-ref>
|
| 384 |
+
network adapter <part-num-ref name="are processed by network device driver 310, network adapter">311</part-num-ref>
|
| 385 |
+
sends the packet onto the network. </p>
|
| 386 |
+
<p id="p-71" num="71">[0055] Turning now to Figure 4, a diagram illustrating an entry in a table of buffers is depicted in accordance with an illustrative embodiment. Entry <part-num-ref name="illustrative embodiment. Entry">400</part-num-ref>
|
| 387 |
+
is an example of an entry in table <part-num-ref name="entry in table">314</part-num-ref>
|
| 388 |
+
in Figure 3. </p>
|
| 389 |
+
<p id="p-72" num="72">
|
| 390 |
+
<confidence value="5">[</confidence>
|
| 391 |
+
0056] In this example, entry 400 contains starting address <part-num-ref name="contains starting address">402,</part-num-ref>
|
| 392 |
+
length <part-num-ref name="contains starting address 402, length">404,</part-num-ref>
|
| 393 |
+
offset <part-num-ref name="contains starting address 402, length 404, offset">406,</part-num-ref>
|
| 394 |
+
and registration key <part-num-ref name="contains starting address 402, length 404, offset 406, and registration key">408.</part-num-ref>
|
| 395 |
+
The information in entry <part-num-ref name="information in entry">400</part-num-ref>
|
| 396 |
+
is used to identify a buffer and the information stored by the buffer in these examples. Starting address <part-num-ref name="buffer in these examples. Starting address">402</part-num-ref>
|
| 397 |
+
identifies the starting address of the buffer containing data for transmission in a packet. Length <part-num-ref name="packet. Length">404</part-num-ref>
|
| 398 |
+
identifies the length of the data stored in the buffer from the starting address. </p>
|
| 399 |
+
<p id="p-73" num="73">
|
| 400 |
+
<confidence value="5">[</confidence>
|
| 401 |
+
0057] Offset 406 is a value in bytes that is offset from the beginning of the packet to the beginning of the data for this particular buffer. Registration key <part-num-ref name="data for this particular buffer. Registration key">408</part-num-ref>
|
| 402 |
+
indicates whether the buffer is an interface specific network buffer. For example, a null value may indicate that the buffer is not an interface specific network buffer. Length <part-num-ref name="interface specific network buffer. Length">404</part-num-ref>
|
| 403 |
+
in these examples is a value in bytes. </p>
|
| 404 |
+
<boundary-data type="header">
|
| 405 |
+
<confidence value="88">16</confidence>
|
| 406 |
+
</boundary-data>
|
| 407 |
+
<boundary-data type="header">Docket No. A<confidence value="5">U</confidence>
|
| 408 |
+
S920070450<confidence value="488">US1</confidence>
|
| 409 |
+
</boundary-data>
|
| 410 |
+
<p id="p-74" num="74">
|
| 411 |
+
<page-break num="17"/>
|
| 412 |
+
[0058] Turning now to Figure 5, a flowchart of a process for processing data for transmission on a network is depicted in accordance with an illustrative embodiment. </p>
|
| 413 |
+
<p id="p-75" num="75">The process illustrated in Figure 5 may be implemented in a component, such as network device driver <part-num-ref name="component, such as network device driver">310</part-num-ref>
|
| 414 |
+
in Figure 3. </p>
|
| 415 |
+
<p id="p-76" num="76">[0059] The process begins by receiving request to transmit data in a packet (step 500). In step <part-num-ref name="packet (step 500). In step">500</part-num-ref>
|
| 416 |
+
the request may be a buffer list, such as buffer list <part-num-ref name="buffer list, such as buffer list">312</part-num-ref>
|
| 417 |
+
in Figure 3. Based on the request, interface specific network buffers assigned to or associated with the network device driver are identified in which data is contained for transmission (step 502). Thereafter, a data structure is created describing the interface specific network buffers (step 504). The data is then processed for transmission using the data structure (step <part-num-ref name="data structure (step">506)</part-num-ref>
|
| 418 |
+
with the process terminating thereafter. </p>
|
| 419 |
+
<p id="p-77" num="77">[0060] In these examples, the data structure also may include descriptions of buffers that are interface specific network buffers not associated with the network device driver or buffers that are simply not interface specific network buffers.</p>
|
| 420 |
+
<p id="p-78" num="78">[0061] Turning now to Figure 6, a flowchart of a process for processing a packet of data for transmission is depicted in accordance with an illustrative embodiment.</p>
|
| 421 |
+
<p id="p-79" num="79">The process in Figure 6 may be implemented in a component, such as network device driver <part-num-ref name="component, such as network device driver">310</part-num-ref>
|
| 422 |
+
in Figure 3. The process in Figure 6 is employed to generate a table, such as table <part-num-ref name="table, such as table">314</part-num-ref>
|
| 423 |
+
in Figure 3. </p>
|
| 424 |
+
<p id="p-80" num="80">[0062] In this example, the process begins by determining whether interface specific network buffers are <boundary-data type="header">
|
| 425 |
+
<confidence value="88">17</confidence>
|
| 426 |
+
</boundary-data>
|
| 427 |
+
<boundary-data type="header">Docket No. AUS920070450US1</boundary-data>
|
| 428 |
+
<page-break num="18"/>
|
| 429 |
+
enabled for this interface or on-the-fly registration is supported (step 600)<confidence value="5">.</confidence>
|
| 430 |
+
</p>
|
| 431 |
+
<p id="p-81" num="81">[0063] If the determination to either of these questions is yes, the buffer header for an unprocessed buffer is parsed (step 602)<confidence value="5">.</confidence>
|
| 432 |
+
In these examples, the buffer is parsed to obtain a data address, a data length, and an mpool ID. </p>
|
| 433 |
+
<p id="p-82" num="82">The mpool ID is the identification of which network device driver the network buffer belongs to in this example. Each network device driver has a poo<confidence value="8">l</confidence>
|
| 434 |
+
or group of buffers that are assigned to the network device driver. Thereafter, the current offset in bytes is calculated from the beginning of the packet based on the data length (step 604)<confidence value="5">.</confidence>
|
| 435 |
+
</p>
|
| 436 |
+
<p id="p-83" num="83">[0064<confidence value="5">]</confidence>
|
| 437 |
+
Next, a determination is made as to whether the buffer belongs to this interface (step 606)<confidence value="5">.</confidence>
|
| 438 |
+
The interface is the network device driver in these examples. The determination in step <part-num-ref name="determination in step">606</part-num-ref>
|
| 439 |
+
is made using the mpool ID in these examples. If the buffer belongs to the interface processing the buffer, the buffer header is parsed to obtain a registration key (step 608). This registration key indicates which registered memory region the buffer belongs to in these examples. </p>
|
| 440 |
+
<p id="p-84" num="84">[0065] Afterwards, a new table entry is created for the buffer (step 610)<confidence value="8">.</confidence>
|
| 441 |
+
<confidence value="5">I</confidence>
|
| 442 |
+
n these examples, the table entry includes a table address, data length, offset, and a registration key. The registration key value is null if the buffer is not an interface specific network buffer in these examples. </p>
|
| 443 |
+
<p id="p-85" num="85">[0066] Then, a determination is made as to whether another buffer is present in the linked list for the packet (step 612). If another buffer is not present, the process terminates. Otherwise, the process returns to step <part-num-ref name="process returns to step">602</part-num-ref>
|
| 444 |
+
to <boundary-data type="header">
|
| 445 |
+
<confidence value="88">18</confidence>
|
| 446 |
+
</boundary-data>
|
| 447 |
+
<boundary-data type="header">Docket No. AUS920070450US1</boundary-data>
|
| 448 |
+
<page-break num="19"/>
|
| 449 |
+
parse a buffer header for another unprocessed buffer, as described above. </p>
|
| 450 |
+
<p id="p-86" num="86">[0067] With reference again to step 606, if the buffer does not belong to the interface, a determination is made as to whether the previous table entry in the table is for a non-interface specific network buffer (step 607). If the previous entry is not for a non-interface specific network buffer, the process proceeds to step <part-num-ref name="process proceeds to step">610</part-num-ref>
|
| 451 |
+
as described above. Otherwise, the data length of the current buffer is added to the data length value of the previous entry (step 614). The process then proceeds to step <part-num-ref name="process then proceeds to step">612</part-num-ref>
|
| 452 |
+
as described above. </p>
|
| 453 |
+
<p id="p-87" num="87">[0068] With reference again to step 600, if interface specific network buffers are not enabled or on-the-fly registration is not supported, the process creates a single table entry (step <part-num-ref name="single table entry (step">616)</part-num-ref>
|
| 454 |
+
with the process terminating thereafter. The table entry contains the data address, data length of the packet, an offset value of zero, and a registration key equal to a null value. </p>
|
| 455 |
+
<p id="p-88" num="88">
|
| 456 |
+
<confidence value="5">[</confidence>
|
| 457 |
+
0069] Turning now to Figure 7, a flowchart of a process for processing a table of buffers is depicted in accordance with an illustrative embodiment. The process illustrated in Figure 7 may be implemented by a software component, such as device driver <part-num-ref name="software component, such as device driver">310</part-num-ref>
|
| 458 |
+
in Figure 3. </p>
|
| 459 |
+
<p id="p-89" num="89">[0070] The process begins by selecting an unprocessed entry from the table (step 700). Thereafter, a determination is made as to whether the table entry value for the registration key is a null value (step 702). If the registration key value for the table entry is a null value, a determination is made as to whether on-the-fly registration is supported (step 704). If on-the-fly <boundary-data type="header">
|
| 460 |
+
<confidence value="88">19</confidence>
|
| 461 |
+
</boundary-data>
|
| 462 |
+
<boundary-data type="header">Docket No. AUS920070450US1</boundary-data>
|
| 463 |
+
<page-break num="20"/>
|
| 464 |
+
registration is supported, the buffer for the current entry is registered (step 706). Next, a transmit descriptor is completed using the table entry data (step 708). A determination is then made as to whether another table entry is present that as not yet been processed (step 710)<confidence value="5">.</confidence>
|
| 465 |
+
</p>
|
| 466 |
+
<p id="p-90" num="90">If another table entry has not been present, the process terminates. Otherwise, the process returns to step <part-num-ref name="process returns to step">700</part-num-ref>
|
| 467 |
+
as described above. </p>
|
| 468 |
+
<p id="p-91" num="91">[0071] With reference again to step 704, if on-the-fly registration is not supported, then the process copies the data described by the entry to a pre-registered buffer (step 712). The entry in step <part-num-ref name="entry in step">712</part-num-ref>
|
| 469 |
+
may describe one of more buffers. </p>
|
| 470 |
+
<p id="p-92" num="92">[0072<confidence value="4">]</confidence>
|
| 471 |
+
Thereafter, the process proceeds to step <part-num-ref name="process proceeds to step">708</part-num-ref>
|
| 472 |
+
as described above. With reference again to step <part-num-ref name="as described above. With reference again to step">702,</part-num-ref>
|
| 473 |
+
if the registration key value in the table entry is not a null value, the process proceeds to step <part-num-ref name="process proceeds to step">708</part-num-ref>
|
| 474 |
+
as described above. </p>
|
| 475 |
+
<p id="p-93" num="93">
|
| 476 |
+
<confidence value="5">[</confidence>
|
| 477 |
+
0073<confidence value="5">]</confidence>
|
| 478 |
+
The flowcharts and block diagrams in the different depicted embodiments illustrate the architecture, functionality, and operation of some possible implementations of apparatus, methods and computer program products. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified function or functions. In some alternative implementations, the function or functions noted in the block may occur out of the order noted in the figures. For example, in some cases, two blocks shown in succession may be executed substantially concurrently, or the blocks may sometimes be <boundary-data type="header">
|
| 479 |
+
<confidence value="88">20</confidence>
|
| 480 |
+
</boundary-data>
|
| 481 |
+
<boundary-data type="header">Docket No. AUS920070450US1</boundary-data>
|
| 482 |
+
<page-break num="21"/>
|
| 483 |
+
executed in the reverse order, depending upon the functionality involved. </p>
|
| 484 |
+
<p id="p-94" num="94">[0074] Thus, the different illustrative embodiments provide a computer implemented method, apparatus, and computer usable program code processing packets for transmission. A set of interface specific network buffers are identified from a plurality of buffers containing data for a packet received for transmission. A data structure is created describing the set of interface specific network buffers within the plurality of buffers. A section in the data structure for an interface specific network buffer in the set of the interface specific network buffers includes information about a piece of data in the interface specific network buffer. The data structure is used to process the packet for transmission.</p>
|
| 485 |
+
<p id="p-95" num="95">[0075] The invention can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment containing both hardware and software elements.</p>
|
| 486 |
+
<p id="p-96" num="96">In a preferred embodiment, the invention is implemented in software, which includes but is not limited to firmware, resident software, microcode, etc.</p>
|
| 487 |
+
<p id="p-97" num="97">[0076] Furthermore, the invention can take the form of a computer program product accessible from a computer-usable or computer-readable medium providing program code for use by or in connection with a computer or any instruction execution system. For the purposes of this description, a computer-usable or computer readable medium can be any tangible apparatus that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.</p>
|
| 488 |
+
<boundary-data type="header">
|
| 489 |
+
<confidence value="88">21</confidence>
|
| 490 |
+
</boundary-data>
|
| 491 |
+
<boundary-data type="header">Docket No. A<confidence value="5">U</confidence>
|
| 492 |
+
S92007<confidence value="5886588">0450US1</confidence>
|
| 493 |
+
</boundary-data>
|
| 494 |
+
<p id="p-98" num="98">
|
| 495 |
+
<page-break num="22"/>
|
| 496 |
+
[0077] The medium can be an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system (or apparatus or device) or a propagation medium. Examples of a computer-readable medium include a semiconductor or solid state memory, magnetic tape, a removable computer diskette, a random access memory (RAM), a read-only memory (ROM), a rigid magnetic disk and an optical disk. Current examples of optical disks include compact disk - read only memory (CD-ROM), compact disk - read/write (CD-R/W) and </p>
|
| 497 |
+
<heading id="h-6">DVD.</heading>
|
| 498 |
+
<p id="p-99" num="99">
|
| 499 |
+
<confidence value="5">[</confidence>
|
| 500 |
+
0078] Further, a computer storage medium may contain or store a computer readable program code such that when the computer readable program code is executed on a computer, the execution of this computer readable program code causes the computer to transmit another computer readable program code over a communications link. This communications link may use a medium that is, for example without limitation, physical or wireless. </p>
|
| 501 |
+
<p id="p-100" num="100">[0079] A data processing system suitable for storing and/or executing program code will include at least one processor coupled directly or indirectly to memory elements through a system bus. The memory elements can include local memory employed during actual execution of the program code, bulk storage, and cache memories which provide temporary storage of at least some program code in order to reduce the number of times code must be retrieved from bulk storage during execution.</p>
|
| 502 |
+
<p id="p-101" num="101">
|
| 503 |
+
<confidence value="5">[</confidence>
|
| 504 |
+
0080] Input/output or I/O devices (including but not limited to keyboards, displays, pointing devices, etc.) can be coupled to the system either directly or through intervening I/O controllers. </p>
|
| 505 |
+
<boundary-data type="header">
|
| 506 |
+
<confidence value="88">22</confidence>
|
| 507 |
+
</boundary-data>
|
| 508 |
+
<boundary-data type="header">Docket No. AUS920070450US1</boundary-data>
|
| 509 |
+
<p id="p-102" num="102">
|
| 510 |
+
<page-break num="23"/>
|
| 511 |
+
<confidence value="5">[</confidence>
|
| 512 |
+
0081] Network adapters may also be coupled to the system to enable the data processing system to become coupled to other data processing systems or remote printers or storage devices through intervening private or public networks. Modems, cable modem and Ethernet cards are just a few of the currently available types of network adapters. </p>
|
| 513 |
+
<p id="p-103" num="103">
|
| 514 |
+
<confidence value="5">[</confidence>
|
| 515 |
+
0082<confidence value="4">]</confidence>
|
| 516 |
+
The description of the present invention has been presented for purposes of illustration and description, and is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art. The embodiment was chosen and described in order to best explain the principles of the invention, the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated. </p>
|
| 517 |
+
<boundary-data type="header">
|
| 518 |
+
<confidence value="88">23</confidence>
|
| 519 |
+
</boundary-data>
|
| 520 |
+
<boundary-data type="header">Docket No. A<confidence value="5">U</confidence>
|
| 521 |
+
S920070450<confidence value="588">US1</confidence>
|
| 522 |
+
</boundary-data>
|
| 523 |
+
</description>
|
| 524 |
+
</us-patent-application>
|
| 525 |
+
|
applicant/11756486.xml
ADDED
|
@@ -0,0 +1,332 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>11756486</doc-number>
|
| 8 |
+
<date>2007-05-31</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<heading id="h-1">INVENTORY MANAGEMENT SYSTEM</heading>
|
| 14 |
+
<heading id="h-2">FOR A MEDICAL SERVICE PROVIDER</heading>
|
| 15 |
+
<heading id="h-3">CROSS-REFERENCE TO RELATED APPLICATIONS</heading>
|
| 16 |
+
<p id="p-1" num="1">
|
| 17 |
+
<confidence value="5">[</confidence>
|
| 18 |
+
0001] This application claims priority from U.S. Provisional Application No. 60/914,914, filed April 30, 2007, which is hereby incorporated herein in its entirety by reference. </p>
|
| 19 |
+
<heading id="h-4">FIELD OF THE INVENTION</heading>
|
| 20 |
+
<p id="p-2" num="2">
|
| 21 |
+
<confidence value="5">[</confidence>
|
| 22 |
+
0002<confidence value="5">]</confidence>
|
| 23 |
+
In general, exemplary embodiments of the present invention relate to medication inventory management systems, and in particular to an inventory management system for a medical service provider. </p>
|
| 24 |
+
<heading id="h-5">BACKGROUND OF THE INVENTION</heading>
|
| 25 |
+
<p id="p-3" num="3">
|
| 26 |
+
<confidence value="5">[</confidence>
|
| 27 |
+
0003<confidence value="4">]</confidence>
|
| 28 |
+
Media sources often report on the rising costs of healthcare. With an aging baby- boomer generation, the costs of healthcare are expected to rise even higher. It has been reported that per capita health spending increased <part-num-ref name="costs of healthcare are expected to rise even higher. It has been reported that per capita health spending increased">39</part-num-ref>
|
| 29 |
+
percent between <part-num-ref name="percent between">1999</part-num-ref>
|
| 30 |
+
and <part-num-ref name="and">2003</part-num-ref>
|
| 31 |
+
for privately insured people, while worker's average hourly earnings grew only <part-num-ref name="for privately insured people, while worker's average hourly earnings grew only">14</part-num-ref>
|
| 32 |
+
percent. Some employers have reacted by beginning to eliminate healthcare benefits completely or shift more of the costs to employees. One of the most costly categories of healthcare is oncology healthcare. Some reports estimate that oncology costs exceed $200 billion annually. As a result, oncology service providers are constantly searching for ways to reduce healthcare costs while maintaining their level of patient care. </p>
|
| 33 |
+
<p id="p-4" num="4">
|
| 34 |
+
<confidence value="5">[</confidence>
|
| 35 |
+
0004] In addition to the problem of rising healthcare costs, many healthcare procedures still rely on dated information systems and paper-based records. Paper-based records are often susceptible to being lost, misfiled, damaged, or destroyed, leaving no record of the information contained therein. It has been reported that approximately <part-num-ref name="information contained therein. It has been reported that approximately">20</part-num-ref>
|
| 36 |
+
percent of medical tests require re- ordering simply because previous results were not available. Utilizing the latest and most accurate information is critical in providing optimal healthcare for patients. Yet current procedures and practices do not adequately rely on such information. </p>
|
| 37 |
+
<p id="p-5" num="5">
|
| 38 |
+
<confidence value="5">[</confidence>
|
| 39 |
+
0005] A large part of the daily operation of an oncology service provider involves the management of oncology medications. Using conventional systems, this often includes <boundary-data type="header">- 1 - AttyDktNo: 050704/328952</boundary-data>
|
| 40 |
+
<page-break num="2"/>
|
| 41 |
+
accessing paper patient records, manually tracking the administration of the medications, manually generating the cost of administration, and manually generating a patient bill relating to the administration of the medications. When a particular medication falls below a certain inventory level, additional quantities of the medication may be ordered by manually processing an order. Accurately tracking oncology medications is especially advantageous for an oncology service provider since oncology medications are very expensive relative to other traditional medications. As such, an oncology service provider should generally insure that sufficient medications are on hand to properly service its patients without incurring the cost associated with having an overabundance of costly medications in inventory. </p>
|
| 42 |
+
<p id="p-6" num="6">
|
| 43 |
+
<confidence value="5">[</confidence>
|
| 44 |
+
0006<confidence value="5">]</confidence>
|
| 45 |
+
Recent alternatives to the conventional oncology inventory management solution include cabinet-based inventory management systems, such as the Pyxis<confidence value="2">*</confidence>
|
| 46 |
+
OncologyStation<confidence value="55">TM</confidence>
|
| 47 |
+
system provided by Cardinal Health. However, because medications are contained within a cabinet, these systems require a great deal of physical space within the facility of an oncology service provider. Additionally, these systems do not generally provide interfaced solutions. If electronic medical records are desired, they require a separate and independent electronic medical records database. However, not all oncology service providers have the physical space or funds to dedicate to such systems. Additionally, in order to streamline oncology practice efficiencies and medication inventory management processes, further lowering costs, many oncology service providers desire interfacing with an electronic medical records system. By interfacing an electronic medical record application, database, and/or system with an inventory management application, inventory management processes may be improved by increasing inventory accuracy and decreasing processing times. Additionally, an interfaced system provides a simplified transparent solution as compared to the separate, independent, and non- interfaced systems currently available. </p>
|
| 48 |
+
<p id="p-7" num="7">
|
| 49 |
+
<confidence value="5">[</confidence>
|
| 50 |
+
0007<confidence value="5">]</confidence>
|
| 51 |
+
As a result, there is a need for a system, method, and computer program product that provides an improved oncology inventory management application such as an application that is interfaced with a database or system of electronic medical records. The inventory management system should be configured to process medication data, and to provide integration with the electronic medical records, thus improving the accuracy and decreasing the processing times associated with inventory management processes. The system may also be configured to <boundary-data type="header">
|
| 52 |
+
<confidence value="8">-</confidence>
|
| 53 |
+
<confidence value="8">2</confidence>
|
| 54 |
+
- AttyDktNo: 050704/328952 </boundary-data>
|
| 55 |
+
<page-break num="3"/>
|
| 56 |
+
interface with a transaction services hub, which may process medication charges associated with the administration of medications from the inventory. </p>
|
| 57 |
+
<heading id="h-6">BRIEF SUMMARY OF THE INVENTION</heading>
|
| 58 |
+
<p id="p-8" num="8">
|
| 59 |
+
<confidence value="5">[</confidence>
|
| 60 |
+
0008] Exemplary embodiments of the present invention provide an improvement over the known prior art by, among other things, providing a system for managing an inventory of medications for a medical service provider such as an oncology service provider. According to exemplary embodiments, the system reads data associated with medications, processes the data, and interfaces with an electronic medical records database, system, and/or application (hereinafter referred to collectively as a "database of electronic medical records") to manage the inventory of medications. A method and computer program product for managing an inventory of medications for an oncology service provider are also provided. </p>
|
| 61 |
+
<p id="p-9" num="9">[0009] In one embodiment, the inventory management system comprises a data input device configured to read medication data associated with the medications, a database of electronic medical records, and a processor configured to execute an inventory management application, wherein the inventory management application is configured to process the medication data and to interface with the database of electronic medical records for updating the inventory of medications. The inventory management application may be further configured to maintain a history of medications removed from the inventory for a patient and to provide a list of recent medications removed from the inventory based at least in part on the history of medication removed from the inventory for the patient, for use in selecting a current medication to be removed from the inventory for the patient. The inventory management application may also be configured to interface with the database of electronic medical records to access at least one of a diagnosis, stage, or regimen, and to project patient medication needs based at least in part on the diagnosis, stage, or regimen. The inventory management application may be further configured to automatically order medications based at least in part on the projected patient medication needs.</p>
|
| 62 |
+
<p id="p-10" num="10">
|
| 63 |
+
<confidence value="5">[</confidence>
|
| 64 |
+
0010] The data input device of the system may comprise at least one of a bar code scanner or an RFID reader. The database of electronic medical records may comprise an oncology- specific database or the medical service provider may comprise an oncology medical service provider. The inventory management application may comprise a web-based application and <boundary-data type="header">
|
| 65 |
+
<confidence value="8">-</confidence>
|
| 66 |
+
3 - AttyDktNo: 050704/328952 </boundary-data>
|
| 67 |
+
<page-break num="4"/>
|
| 68 |
+
may be configured to allow automatic or manual ordering of medications. At least a portion of the database of electronic medical records may be hosted externally from the medical service provider. A single graphical user interface may be configured to interface with both the inventory management application and the database of electronic medical records so that from a user's perspective, the inventory management application and the database of electronic medical records appear integrated. At least one medication in the inventory of medications may be received in a predetermined concentration, wherein the database of electronic medical records may include a dosage of the medication to be administered to a patient, and wherein the inventory management application may automatically calculate a draw-up amount of the medication based at least in part on the predetermined medication concentration and the dosage of medication to be administered to the patient. The data input device may be configured to communicate with the inventory management application to verify that medication leaving the inventory of medications for administration to a patient is the proper medication. The system may be configured to interface with an existing transaction services hub for processing medication charges associated with medications leaving the inventory for administration to a patient. At least a portion of the inventory of medications may be received in full medication vials, and the inventory management application may be configured to track inventory levels associated with the medications in partial vial increments. </p>
|
| 69 |
+
<p id="p-11" num="11">
|
| 70 |
+
<confidence value="5">[</confidence>
|
| 71 |
+
0011<confidence value="5">]</confidence>
|
| 72 |
+
As a result, embodiments of the present invention provide a system, method, and computer program product that provide an improved oncology inventory management system. </p>
|
| 73 |
+
<p id="p-12" num="12">The system supports a medical service provider, such as an oncology service provider, by interfacing an inventory management application with a database of electronic medical records.</p>
|
| 74 |
+
<p id="p-13" num="13">By interfacing the inventory management application with the database of electronic medical records, inventory accuracy may be increased and processing times may be decreased.</p>
|
| 75 |
+
<heading id="h-7">BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)</heading>
|
| 76 |
+
<p id="p-14" num="14">[0012] Having thus described the invention in general terms, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:</p>
|
| 77 |
+
<p id="p-15" num="15">
|
| 78 |
+
<confidence value="5">[</confidence>
|
| 79 |
+
0013<confidence value="4">]</confidence>
|
| 80 |
+
Fig. 1 is a diagram illustrating an inventory management system of an exemplary embodiment of the present invention; </p>
|
| 81 |
+
<boundary-data type="header">
|
| 82 |
+
<confidence value="8">-</confidence>
|
| 83 |
+
<confidence value="8">4</confidence>
|
| 84 |
+
- AttyDktNo: 050704/328952 </boundary-data>
|
| 85 |
+
<p id="p-16" num="16">
|
| 86 |
+
<page-break num="5"/>
|
| 87 |
+
<confidence value="5">[</confidence>
|
| 88 |
+
0014] Fig. 2 is a diagram illustrating an inventory management system in accordance with another exemplary embodiment of the present invention; and [0015] Fig. 3 is a block diagram of an exemplary electronic device configured to manage an inventory of medications for an oncology service provider of exemplary embodiments of the present invention. </p>
|
| 89 |
+
<heading id="h-8">DETAILED DESCRIPTION OF THE INVENTION</heading>
|
| 90 |
+
<p id="p-17" num="17">[0016] The present invention now will be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all embodiments of the invention are shown.</p>
|
| 91 |
+
<p id="p-18" num="18">Indeed, this invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Like numbers refer to like elements throughout.</p>
|
| 92 |
+
<p id="p-19" num="19">[0017] An embodiment of the present invention may be better understood with reference to Fig. 1, which is a diagram illustrating an inventory management system <part-num-ref name="inventory management system">100</part-num-ref>
|
| 93 |
+
for managing an inventory of medications for an oncology service provider <part-num-ref name="oncology service provider">101,</part-num-ref>
|
| 94 |
+
and Fig. 2, which is another embodiment of an inventory management system <part-num-ref name="inventory management system">100.</part-num-ref>
|
| 95 |
+
It should be noted that although the depicted embodiments relate to an improved inventory management system for an oncology service provider, embodiments of the present invention may be advantageous for any medical service provider and thus should not be limited to an oncology service provider. The system, method and computer program product of embodiments of the present invention manage the inventory of an oncology service provider <part-num-ref name="oncology service provider">101</part-num-ref>
|
| 96 |
+
by providing an inventory management application <part-num-ref name="inventory management application">102</part-num-ref>
|
| 97 |
+
that processes medication data relating to medications entering and leaving an inventory of medications and interfaces with a database of electronic medical records. The inventory management application <part-num-ref name="inventory management application">102</part-num-ref>
|
| 98 |
+
may interface with the database of electronic medical records <part-num-ref name="database of electronic medical records">106</part-num-ref>
|
| 99 |
+
in a variety of ways as are known in the art. In some embodiments, a single graphical user interface is provided that interfaces the inventory management application <part-num-ref name="inventory management application">102</part-num-ref>
|
| 100 |
+
with the database of electronic medical records <part-num-ref name="database of electronic medical records">106</part-num-ref>
|
| 101 |
+
so that from a user's perspective, the inventory management application <part-num-ref name="inventory management application">102</part-num-ref>
|
| 102 |
+
and the database of electronic medical records appear integrated. It should be noted that in such embodiments, the graphical user interface may be a separate application, or may be associated with either or both the inventory management <boundary-data type="header">
|
| 103 |
+
<confidence value="8">-</confidence>
|
| 104 |
+
<confidence value="8">5</confidence>
|
| 105 |
+
- AttyDktNo: 050704/328952 </boundary-data>
|
| 106 |
+
<page-break num="6"/>
|
| 107 |
+
application <part-num-ref name="inventory management application">102</part-num-ref>
|
| 108 |
+
and the database of electronic medical records <part-num-ref name="database of electronic medical records">106.</part-num-ref>
|
| 109 |
+
Additionally, the graphical user interface may provide single sign-on capability. </p>
|
| 110 |
+
<p id="p-20" num="20">
|
| 111 |
+
<confidence value="5">[</confidence>
|
| 112 |
+
0018<confidence value="5">]</confidence>
|
| 113 |
+
Medications entering the inventory of medications generally relate to medications received from a medication supplier <part-num-ref name="medication supplier">112,</part-num-ref>
|
| 114 |
+
and medications leaving the inventory of medications typically relate to medications that are removed or withdrawn from the inventory prior to being administered to patients. Exemplary embodiments of the present invention manage the inventory of oncology medications by processing medication data relating to medications entering and leaving the inventory, and interfacing with a database of electronic medical records, thus creating an improved inventory management tool. Unlike the cabinet-based inventory management systems described above, where medications must be stored within the system itself (thus occupying a great deal of physical storage space within the facility of the oncology service provider), exemplary embodiments of the present invention do not require medications to be stored within a cabinet of the system. Rather, various embodiments of the present invention allow the oncology service provider <part-num-ref name="oncology service provider">101</part-num-ref>
|
| 115 |
+
to use its current storage system. As a result, various embodiments of the present invention do not present the same physical space and economic constraints presented by current cabinet-based systems. </p>
|
| 116 |
+
<p id="p-21" num="21">[0019<confidence value="5">]</confidence>
|
| 117 |
+
As shown in Fig. 1, the inventory management system <part-num-ref name="inventory management system">100</part-num-ref>
|
| 118 |
+
of an exemplary embodiment includes an inventory management application <part-num-ref name="inventory management application">102</part-num-ref>
|
| 119 |
+
and a data input device <part-num-ref name="data input device">104</part-num-ref>
|
| 120 |
+
in communication with the inventory management application <part-num-ref name="inventory management application">102.</part-num-ref>
|
| 121 |
+
As will be discussed in more detail below, the inventory management application <part-num-ref name="inventory management application">102</part-num-ref>
|
| 122 |
+
interfaces with a database of electronic medical records<confidence value="5">1</confidence>
|
| 123 |
+
06. As shown in the depicted embodiment, the database of electronic medical records <part-num-ref name="database of electronic medical records">106</part-num-ref>
|
| 124 |
+
may communicate with a practice management system <part-num-ref name="practice management system">108</part-num-ref>
|
| 125 |
+
that manages patient check in/out, patient scheduling, and/or patient billing. In various embodiments, the practice management system <part-num-ref name="practice management system">108</part-num-ref>
|
| 126 |
+
may be a separate system, or may be part of the database of electronic medical records <part-num-ref name="database of electronic medical records">106.</part-num-ref>
|
| 127 |
+
The inventory management application <part-num-ref name="inventory management application">102</part-num-ref>
|
| 128 |
+
also communicates with a medication supplier <part-num-ref name="medication supplier">112.</part-num-ref>
|
| 129 |
+
Although the medication supplier <part-num-ref name="medication supplier">112</part-num-ref>
|
| 130 |
+
may be any medication supplier capable of communicating with the inventory management application <part-num-ref name="inventory management application">102,</part-num-ref>
|
| 131 |
+
in the exemplary embodiment, the medication supplier <part-num-ref name="medication supplier">112</part-num-ref>
|
| 132 |
+
is an online medication supply system, such as the McKessso<confidence value="52">n*</confidence>
|
| 133 |
+
SAP<confidence value="2">*</confidence>
|
| 134 |
+
system. The data input device <part-num-ref name="data input device">104</part-num-ref>
|
| 135 |
+
in the exemplary embodiment is a barcode scanner used to scan barcode labels <part-num-ref name="barcode scanner used to scan barcode labels">107</part-num-ref>
|
| 136 |
+
that provide medication data associated with the medications <part-num-ref name="medications">105.</part-num-ref>
|
| 137 |
+
In other embodiments, the data input device <part-num-ref name="data input device">104</part-num-ref>
|
| 138 |
+
may comprise other devices <boundary-data type="header">
|
| 139 |
+
<confidence value="8">-</confidence>
|
| 140 |
+
<confidence value="8">6</confidence>
|
| 141 |
+
- AttyDktNo: 050704/328952 </boundary-data>
|
| 142 |
+
<page-break num="7"/>
|
| 143 |
+
capable of reading information associated with the medications <part-num-ref name="medications">105,</part-num-ref>
|
| 144 |
+
including, but not limited to, Radio Frequency Identification (RFID) readers configured to read RFID transponders associated with the medications. As will be discussed in more detail below, the medication data may be read by the data input device <part-num-ref name="data input device">104</part-num-ref>
|
| 145 |
+
as medications <part-num-ref name="as medications">105</part-num-ref>
|
| 146 |
+
are removed from inventory, such as when medications are administered to patients. Medication data may also be read when new medications <part-num-ref name="are removed from inventory, such as when medications are administered to patients. Medication data may also be read when new medications">105</part-num-ref>
|
| 147 |
+
are added to the inventory. The medication data includes information relating to the medications <part-num-ref name="medications">105,</part-num-ref>
|
| 148 |
+
such as the medication name, dose strength, package size, and an identification number. In various embodiments, this information may also include the medication quantity. In other embodiments this data may comprise additional information including, but is not limited to, the medication manufacturer, the lot number, any expiration date information, and the like. In the exemplary embodiment, the inventory management application <part-num-ref name="inventory management application">102</part-num-ref>
|
| 149 |
+
is configured to not only receive medication data from the data input device, but can also accept manual input of medication data, such as the manual input of the medication quantity, via a computer interface, such as a keyboard, touchscreen or the like. </p>
|
| 150 |
+
<p id="p-22" num="22">
|
| 151 |
+
<confidence value="5">[</confidence>
|
| 152 |
+
0020] The inventory management application <part-num-ref name="inventory management application">102</part-num-ref>
|
| 153 |
+
of the exemplary embodiment is a web- based software application that may be hosted by an external mainframe (not shown) accessible by one or more clients. Although in other embodiments, the inventory management application <part-num-ref name="inventory management application">102</part-num-ref>
|
| 154 |
+
need not be web-based and may a local application located at the medical service provider's <part-num-ref name="medical service provider's">101</part-num-ref>
|
| 155 |
+
site. The exemplary embodiment of the inventory management application is advantageous in that it may not require on-site installation and maintenance, and thus may minimize disruptions to an oncology service provider <part-num-ref name="oncology service provider">101</part-num-ref>
|
| 156 |
+
for product upgrades and other software maintenance issues. </p>
|
| 157 |
+
<p id="p-23" num="23">
|
| 158 |
+
<confidence value="5">[</confidence>
|
| 159 |
+
0021] With regard to medications leaving the inventory of medications for the oncology service provider, the inventory management application <part-num-ref name="inventory management application">102</part-num-ref>
|
| 160 |
+
of embodiments of the present invention provides an electronic list of medications available in the inventory of medications and allows a user to select a particular medication from the inventory for administration to a patient. </p>
|
| 161 |
+
<p id="p-24" num="24">The data input device 104 may be used to scan or read the label <part-num-ref name="label">107</part-num-ref>
|
| 162 |
+
of the medication <part-num-ref name="medication">105</part-num-ref>
|
| 163 |
+
as the medication <part-num-ref name="medication">105</part-num-ref>
|
| 164 |
+
is physically removed from the inventory prior to being administered to the patient. As a result, the inventory management application <part-num-ref name="inventory management application">102</part-num-ref>
|
| 165 |
+
may verify that the medication <part-num-ref name="medication">105</part-num-ref>
|
| 166 |
+
leaving the inventory of medications for administration to the patient is the proper medication. </p>
|
| 167 |
+
<boundary-data type="header">
|
| 168 |
+
<confidence value="8">-</confidence>
|
| 169 |
+
<confidence value="8">7</confidence>
|
| 170 |
+
- AttyDktNo: 050704/328952 </boundary-data>
|
| 171 |
+
<p id="p-25" num="25">
|
| 172 |
+
<page-break num="8"/>
|
| 173 |
+
[0022] As noted above, the inventory management application <part-num-ref name="inventory management application">102</part-num-ref>
|
| 174 |
+
interfaces with a database of electronic medical records <part-num-ref name="database of electronic medical records">106.</part-num-ref>
|
| 175 |
+
In the exemplary embodiment, the database of electronic medical records <part-num-ref name="database of electronic medical records">106</part-num-ref>
|
| 176 |
+
is stored in a memory device and hosted by the oncology service provider <part-num-ref name="oncology service provider">101</part-num-ref>
|
| 177 |
+
and comprises an oncology-specific system of electronic medical records that contains electronic medical records associated with patients of the oncology service provider <part-num-ref name="oncology service provider">101.</part-num-ref>
|
| 178 |
+
It should be noted however, in other embodiments the database of electronic medical records <part-num-ref name="database of electronic medical records">106</part-num-ref>
|
| 179 |
+
may comprise a database that includes patients of various medical service providers. The electronic medical records include clinical data associated with each patient (patient clinical data). In various embodiments the patient clinical data may include, but is not limited to, patient demographics, clinical diagnoses, oncology stages, treatment regimens, and medication usage history. For example, in the exemplary embodiment, the patient clinical data includes patient <confidence value="5">I</confidence>
|
| 180 |
+
CD (International Statistical Classification of Diseases and Related Health Problems) codes including primary, secondary, and/or tertiary data; oncology stages, patient medication regimens and associated CPT (Current Procedural Terminology) codes; medication dose amount specific to the patient; medication dose form and strength; and other pertinent clinical information, such as complete blood count and vital information. Although the database of electronic medical records <part-num-ref name="database of electronic medical records">106</part-num-ref>
|
| 181 |
+
in the exemplary embodiment is associated with the patients of the oncology service provider <part-num-ref name="oncology service provider">101,</part-num-ref>
|
| 182 |
+
in other embodiments, the database of electronic medical records <part-num-ref name="database of electronic medical records">106</part-num-ref>
|
| 183 |
+
may be part of a large aggregate database of electronic medical records. </p>
|
| 184 |
+
<p id="p-26" num="26">[0023] By interfacing with the database of electronic medical records <part-num-ref name="database of electronic medical records">106</part-num-ref>
|
| 185 |
+
associated with patients of the oncology service provider <part-num-ref name="oncology service provider">101,</part-num-ref>
|
| 186 |
+
data relating to the administration of medications may be accessed and monitored as medications <part-num-ref name="administration of medications may be accessed and monitored as medications">105</part-num-ref>
|
| 187 |
+
are administered to patients. Although the database of electronic medical records <part-num-ref name="database of electronic medical records">106</part-num-ref>
|
| 188 |
+
of the exemplary embodiment is hosted by the oncology service provider <part-num-ref name="oncology service provider">101,</part-num-ref>
|
| 189 |
+
in other embodiments, such as the one depicted in Fig. 2, at least a portion of the database of electronic medical records <part-num-ref name="database of electronic medical records">106</part-num-ref>
|
| 190 |
+
may be hosted externally. </p>
|
| 191 |
+
<p id="p-27" num="27">Additionally, although the inventory management application <part-num-ref name="inventory management application">102</part-num-ref>
|
| 192 |
+
may interface with the database of electronic medical records <part-num-ref name="database of electronic medical records">106</part-num-ref>
|
| 193 |
+
in any manner known in the art, in the exemplary embodiment, the inventory management application <part-num-ref name="inventory management application">102</part-num-ref>
|
| 194 |
+
interfaces with the database of electronic medical records <part-num-ref name="database of electronic medical records">106</part-num-ref>
|
| 195 |
+
through a single graphical user interface as described above. As such, in various embodiments a user may sign onto either the inventory management application <part-num-ref name="inventory management application">102</part-num-ref>
|
| 196 |
+
or the database of electronic medical records <part-num-ref name="database of electronic medical records">106</part-num-ref>
|
| 197 |
+
to access the functionality and data of <boundary-data type="header">
|
| 198 |
+
<confidence value="8">-</confidence>
|
| 199 |
+
<confidence value="8">8</confidence>
|
| 200 |
+
- AttyDktNo: 050704/328952 </boundary-data>
|
| 201 |
+
<page-break num="9"/>
|
| 202 |
+
either. In other embodiments, the inventory management application <part-num-ref name="inventory management application">102</part-num-ref>
|
| 203 |
+
may also be configured to import patient data from external sources. The inventory management application may do this in any manner known in the art. </p>
|
| 204 |
+
<p id="p-28" num="28">
|
| 205 |
+
<confidence value="5">[</confidence>
|
| 206 |
+
0024<confidence value="5">]</confidence>
|
| 207 |
+
The inventory management application <part-num-ref name="inventory management application">102</part-num-ref>
|
| 208 |
+
interfaces with the database of electronic medical records <part-num-ref name="database of electronic medical records">106</part-num-ref>
|
| 209 |
+
to improve inventory management processes by increasing inventory accuracy and decreasing processing times. For example, as noted above, prior to physically removing a medication <part-num-ref name="medication">105</part-num-ref>
|
| 210 |
+
from the inventory of medications for administration to a patient, a user may be provided with a list of medications from which the user selects the medication to be removed. In one embodiment of the present invention, a master list of medications is provided to the user. The master list of medications represents most, if not all, of the medications available in the inventory. However, in many instances, the master list of medications includes a vast number of medications, many of which are not relevant to a particular patient's medication regimen. Therefore, in another embodiment of the present invention, the inventory management application <part-num-ref name="inventory management application">102</part-num-ref>
|
| 211 |
+
streamlines this process and is configured to maintain a history of the medications removed from the inventory for a particular patient. As such, when the time comes for a user to select from the inventory management application a current medication to be removed from the inventory for administration to a patient, the inventory management application <part-num-ref name="inventory management application">102</part-num-ref>
|
| 212 |
+
may provide the user with an abbreviated list of medications. The abbreviated list of medications may represent those medications that were most recently removed for that patient. In various embodiments, the inventory management application <part-num-ref name="inventory management application">102</part-num-ref>
|
| 213 |
+
may allow the oncology service provider <part-num-ref name="oncology service provider">101</part-num-ref>
|
| 214 |
+
to specify a period of time for which to maintain the history. This period may be the same for all patients of the oncology service provider, or may be patient- specific. </p>
|
| 215 |
+
<p id="p-29" num="29">
|
| 216 |
+
<confidence value="5">[</confidence>
|
| 217 |
+
0025<confidence value="5">]</confidence>
|
| 218 |
+
Embodiments of the present invention may also improve inventory management processes by interfacing with a database of electronic medical records <part-num-ref name="database of electronic medical records">106</part-num-ref>
|
| 219 |
+
to project patient medication needs. In various embodiments of the present invention, the database of electronic medical records <part-num-ref name="database of electronic medical records">106</part-num-ref>
|
| 220 |
+
may include oncology diagnoses, stages, and/or treatment regimens. The diagnoses, stages, and/or treatment regimens may be patient-specific or may relate to general diagnoses, stages, and/or treatment regimens. In the depicted embodiment, diagnoses may relate, but are not limited to, the identification of one or more cancers. Stages may relate, but are not limited to, an extent of progress of one or more cancers. Treatment regimens may include, but <boundary-data type="header">
|
| 221 |
+
<confidence value="8">-</confidence>
|
| 222 |
+
<confidence value="8">9</confidence>
|
| 223 |
+
- AttyDktNo: 050704/328952 </boundary-data>
|
| 224 |
+
<page-break num="10"/>
|
| 225 |
+
are not limited to, treatment plans, which often include the administration of one or more medications, as well as other courses of treatments, such as diets and/or exercise. By interfacing with the database of electronic medical records <part-num-ref name="database of electronic medical records">106,</part-num-ref>
|
| 226 |
+
the inventory management application <part-num-ref name="inventory management application">102</part-num-ref>
|
| 227 |
+
of one embodiment of the present invention may project patient medication needs based on one or more of a patient's diagnosis, stage, or regimen. Notably, the patient medication needs may, but need not, be determined before medication is removed from the inventory. As a result, the inventory management application <part-num-ref name="inventory management application">102</part-num-ref>
|
| 228 |
+
may project medications and amounts (including dosages, etc.) that will be needed for administration to a patient. The inventory management application <part-num-ref name="inventory management application">102</part-num-ref>
|
| 229 |
+
may also update and/or establish order quantities for the oncology service provider <part-num-ref name="oncology service provider">101</part-num-ref>
|
| 230 |
+
based, at least in part, on this information, and through communication with the medication supplier <part-num-ref name="medication supplier">112,</part-num-ref>
|
| 231 |
+
the inventory management application <part-num-ref name="inventory management application">102</part-num-ref>
|
| 232 |
+
may automatically (i.e., with manual intervention) order one or more of the medications. It should be noted that in various embodiments, the system <part-num-ref name="system">100</part-num-ref>
|
| 233 |
+
is configured to allow other medications to be ordered according to their usage by the oncology service provider, which may be tracked by the inventory management application <part-num-ref name="inventory management application">102.</part-num-ref>
|
| 234 |
+
Additionally, the system <part-num-ref name="system">100</part-num-ref>
|
| 235 |
+
is also configured to permit manual ordering of one or more medications. </p>
|
| 236 |
+
<p id="p-30" num="30">
|
| 237 |
+
<confidence value="5">[</confidence>
|
| 238 |
+
0026<confidence value="5">]</confidence>
|
| 239 |
+
Embodiments of the present invention may also improve inventory management processes and accuracy by performing functions that, under many existing inventory management systems, must be manually performed by a user, such as a person administering medications to a patient. For instance, many medications, such as those that are administered in liquid form, are received by oncology service providers in predetermined concentrations. </p>
|
| 240 |
+
<p id="p-31" num="31">However, dosages to be administered to patients do not always match the concentrations of the medications in the inventory. To accommodate the administration dosage, those who administer the medications typically manually calculate the amount of medication to "draw-up" into a syringe that contains an additional and innocuous substance so that the proper concentration of the medication is contained in the dosage. The inventory management application in accordance with various embodiments of the present invention automatically calculates the draw-up amount (i.e., the amount of medication at the predetermined concentration that should be drawn into in the syringe). As a result, this reduces manual processing time and increases both the accuracy of the administration of the medication, as well as the accuracy of the inventory.</p>
|
| 241 |
+
<boundary-data type="header">
|
| 242 |
+
<confidence value="6">-</confidence>
|
| 243 |
+
<confidence value="88">10</confidence>
|
| 244 |
+
- AttyDktNo: 050704/328952 </boundary-data>
|
| 245 |
+
<p id="p-32" num="32">
|
| 246 |
+
<page-break num="11"/>
|
| 247 |
+
<confidence value="5">[</confidence>
|
| 248 |
+
0027] Embodiments of the present invention may also improve the inventory processes and accuracy by tracking medications in smaller, more accurate increments than current inventory management systems. For instance, many medications are received in full medication containers that contain a predetermined amount of medication. Examples include medications that are administered in liquid form and that are received in vials that contain a predetermined volume of medication. Often, however, the prescribed dosage of the medication may require less than a full vial's worth of the medication. After administering a portion of the vial to the patient, existing inventory management systems would consider the entire vial of medication to have left the inventory. Unfortunately, this leads to an overage of medication as compared to the inventory count. On the other hand, if the partial vial is removed from the inventory and discarded, this amounts to wastage of medication. In either event, the inventory management application <part-num-ref name="inventory management application">102</part-num-ref>
|
| 249 |
+
of one embodiment of the present invention may improve this situation by being configured to track inventory levels for medications in partial increments, the level of which may be determined by the oncology medical service provider <part-num-ref name="oncology medical service provider">101.</part-num-ref>
|
| 250 |
+
For example, a full vial of a medication may comprise <part-num-ref name="medication may comprise">10</part-num-ref>
|
| 251 |
+
milliliters (ml) of medication. If only 7 ml are used for administration to a patient, the inventory management application <part-num-ref name="inventory management application">102</part-num-ref>
|
| 252 |
+
may be configured to track this medication in milliliter increments such that the inventory count for this medication would indicate that <part-num-ref name="inventory count for this medication would indicate that">3</part-num-ref>
|
| 253 |
+
ml's remain in the inventory. This advantage also translates to more accurate patient billing because the patient is more likely to be billed according to the specific amount of medication that was administered, as opposed to the amount of medication that was said to have left the inventory, in this case 7 ml vs. one full vial. </p>
|
| 254 |
+
<p id="p-33" num="33">
|
| 255 |
+
<confidence value="5">[</confidence>
|
| 256 |
+
0028] Under existing systems, medical service providers must have separate practice management system applications that manage patient check in/out, patient scheduling, and patient billing. In some embodiments of the present invention, the inventory management application <part-num-ref name="inventory management application">102</part-num-ref>
|
| 257 |
+
may also interface with an external system that processes patient billing for various medical service providers. Additionally, another system may handle the patient check in/out and scheduling functions, thus alleviating the need for additional practice management system. Fig. 2 represents such an embodiment. In the depicted embodiment, the oncology service provider <part-num-ref name="oncology service provider">101</part-num-ref>
|
| 258 |
+
may communication over a network <part-num-ref name="network">114</part-num-ref>
|
| 259 |
+
with a transaction service hub <part-num-ref name="transaction service hub">116</part-num-ref>
|
| 260 |
+
that handles billing services for the oncology medical service provider <part-num-ref name="oncology medical service provider">101.</part-num-ref>
|
| 261 |
+
It should be noted that although only one medical service provider is shown, there may be many medical service <boundary-data type="header">- 11 - A<confidence value="66">tt</confidence>
|
| 262 |
+
yDktNo: 050704/328952 </boundary-data>
|
| 263 |
+
<page-break num="12"/>
|
| 264 |
+
providers whose billing services are handled by the transaction services hub <part-num-ref name="transaction services hub">116</part-num-ref>
|
| 265 |
+
and who may communicate over the network <part-num-ref name="network">114.</part-num-ref>
|
| 266 |
+
In various embodiments, the network <part-num-ref name="network">114</part-num-ref>
|
| 267 |
+
may be a LAN, a WAN, the Internet, etc. As also shown in depicted embodiment, the inventory management application <part-num-ref name="inventory management application">102</part-num-ref>
|
| 268 |
+
may interface with a database of electronic medical records <part-num-ref name="database of electronic medical records">106</part-num-ref>
|
| 269 |
+
by communicating with the database <part-num-ref name="database">106</part-num-ref>
|
| 270 |
+
over the network <part-num-ref name="network">114.</part-num-ref>
|
| 271 |
+
Additionally, the inventory management application <part-num-ref name="inventory management application">102</part-num-ref>
|
| 272 |
+
may communicate over the network <part-num-ref name="network">114</part-num-ref>
|
| 273 |
+
with a medication supplier <part-num-ref name="medication supplier">112</part-num-ref>
|
| 274 |
+
for ordering medications. In this manner, several medical service providers may share a single database of electronic medical records and may communication with one or more medication suppliers over the network <part-num-ref name="network">114.</part-num-ref>
|
| 275 |
+
</p>
|
| 276 |
+
<p id="p-34" num="34">
|
| 277 |
+
<confidence value="5">[</confidence>
|
| 278 |
+
0029<confidence value="5">]</confidence>
|
| 279 |
+
The inventory management system may also include a printer (not shown) that may be configured to print out certain output. The output may include, for example, labels that are generated upon medication dispensation. The labels may include information relating to the dispensation of the medication including, for example, identifying information such as facility, physician, and patient names, patient identification numbers, and medication dispensation information such as medication name, dose amount, dose strength, and NDC (National Drug Code) numbers. Output may also include certain inventory and cost reports. The reports may include, for example, activity summaries relating to medication dispensation events; medication utilization summaries; inventory count summaries; inventory cost summaries; and medication regimen costs per patient; and other summaries relating to data accessible by the inventory management application. </p>
|
| 280 |
+
<p id="p-35" num="35">
|
| 281 |
+
<confidence value="5">[</confidence>
|
| 282 |
+
0030] The foregoing merely illustrates how exemplary embodiments of the present invention manage an inventory of medications for an oncology service provider. Referring now to Fig. 3, a block diagram of an exemplary electronic device <part-num-ref name="exemplary electronic device">400</part-num-ref>
|
| 283 |
+
(e.g., mainframe, PC, laptop, PDA, etc.) configured to execute the method and computer program product for managing an inventory of medications for an oncology service provider of exemplary embodiments of the present invention is shown. The electronic device may include various means for performing one or more functions in accordance with exemplary embodiments of the present invention, including those more particularly shown and described herein. It should be understood, however, that the electronic device may include alternative means for performing one or more like functions, without departing from the spirit and scope of the present invention. As shown, <boundary-data type="header">
|
| 284 |
+
<confidence value="8">-</confidence>
|
| 285 |
+
<confidence value="88">12</confidence>
|
| 286 |
+
- AttyDktNo: 050704/328952 </boundary-data>
|
| 287 |
+
<page-break num="13"/>
|
| 288 |
+
the electronic device may generally include means, such as a processor, controller, or the like <part-num-ref name="like">402</part-num-ref>
|
| 289 |
+
connected to a memory <part-num-ref name="memory">404,</part-num-ref>
|
| 290 |
+
for performing or controlling the various functions of the entity. </p>
|
| 291 |
+
<p id="p-36" num="36">[0031] The memory can comprise volatile and/or non-volatile memory, and typically stores content, data or the like. For example, the memory typically stores content transmitted from, and/or received by, the electronic device. Also for example, the memory typically stores software applications, instructions or the like for the processor to perform steps associated with operation of the electronic device in accordance with embodiments of the present invention. In particular, the memory <part-num-ref name="memory">404</part-num-ref>
|
| 292 |
+
may store computer program code for an application and other computer programs. For example, in one exemplary embodiment of the present invention, the memory may store computer program code for, among other things reading medication data associated with medications entering or leaving the inventory and interfacing with a database of electronic medical records to processthe medication data, for updating the inventory of medications. In relation to the embodiment depicted in Fig. 1 and described above, the memory may include the inventory management application <part-num-ref name="inventory management application">102</part-num-ref>
|
| 293 |
+
and/or the database of electronic medical records <part-num-ref name="database of electronic medical records">106</part-num-ref>
|
| 294 |
+
with the processor <part-num-ref name="processor">402</part-num-ref>
|
| 295 |
+
configured to execute the inventory management application to perform as described above. </p>
|
| 296 |
+
<p id="p-37" num="37">[0032] In addition to the memory <part-num-ref name="memory">404,</part-num-ref>
|
| 297 |
+
the processor <part-num-ref name="processor">402</part-num-ref>
|
| 298 |
+
can also be connected to at least one interface or other means for displaying, transmitting and/or receiving data, content or the like. In this regard, the interface(s) can include at least one communication interface <part-num-ref name="interface(s) can include at least one communication interface">406</part-num-ref>
|
| 299 |
+
or other means for transmitting and/or receiving data, content or the like. For example, the communication interface may provide for communications with an input device <part-num-ref name="input device">104.</part-num-ref>
|
| 300 |
+
The communication interface may also include at least one user interface that can include a display <part-num-ref name="display">408</part-num-ref>
|
| 301 |
+
and/or a user input interface <part-num-ref name="user input interface">410.</part-num-ref>
|
| 302 |
+
The user input interface, in turn, can comprise any of a number of devices allowing the electronic device to receive data from a user, such as a keypad, a touch display, a joystick or other input device. </p>
|
| 303 |
+
<p id="p-38" num="38">[0033<confidence value="5">]</confidence>
|
| 304 |
+
As described above and as will be appreciated by one skilled in the art, embodiments of the present invention may be configured as a method and apparatus. Accordingly, embodiments of the present invention may be comprised of various means including entirely of hardware, entirely of software, or any combination of software and hardware. Furthermore, embodiments of the present invention may take the form of a computer program product consisting of a computer-readable storage medium (e.g., the memory <part-num-ref name="memory">404</part-num-ref>
|
| 305 |
+
of Fig. 3) and <boundary-data type="header">- 13 - AttyDktNo: 050704/328952</boundary-data>
|
| 306 |
+
<page-break num="14"/>
|
| 307 |
+
computer-readable program instructions (e.g., computer software such as the computer software that comprises the inventory management application <part-num-ref name="inventory management application">102)</part-num-ref>
|
| 308 |
+
stored in the storage medium. Any suitable computer-readable storage medium may be utilized including hard disks, CD-ROMs, optical storage devices, or magnetic storage devices. </p>
|
| 309 |
+
<p id="p-39" num="39">[0034] Exemplary embodiments of the present invention have been described above with reference to block diagrams and flowchart illustrations of methods, apparatuses (i.e., systems) and computer program products. It will be understood that each block of the block diagrams and flowchart illustrations, and combinations of blocks in the block diagrams and flowchart illustrations, respectively, can be implemented by various means including computer program instructions. These computer program instructions may be loaded onto a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions which execute on the computer or other programmable data processing apparatus create a means for implementing the functions specified in the flowchart block or blocks.</p>
|
| 310 |
+
<p id="p-40" num="40">
|
| 311 |
+
<confidence value="5">[</confidence>
|
| 312 |
+
0035<confidence value="5">]</confidence>
|
| 313 |
+
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including computer-readable instructions for implementing the function specified in the flowchart block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions that execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks. </p>
|
| 314 |
+
<p id="p-41" num="41">
|
| 315 |
+
<confidence value="5">[</confidence>
|
| 316 |
+
0036<confidence value="5">]</confidence>
|
| 317 |
+
Accordingly, blocks of the block diagrams and flowchart illustrations support combinations of means for performing the specified functions, combinations of steps for performing the specified functions and program instruction means for performing the specified functions. It will also be understood that each block of the block diagrams and flowchart illustrations, and combinations of blocks in the block diagrams and flowchart illustrations, can be implemented by special purpose hardware-based computer systems that perform the specified functions or steps, or combinations of special purpose hardware and computer instructions. </p>
|
| 318 |
+
<boundary-data type="header">
|
| 319 |
+
<confidence value="8">-</confidence>
|
| 320 |
+
<confidence value="88">14</confidence>
|
| 321 |
+
- AttyDktNo: 050704/328952 </boundary-data>
|
| 322 |
+
<p id="p-42" num="42">
|
| 323 |
+
<page-break num="15"/>
|
| 324 |
+
<confidence value="5">[</confidence>
|
| 325 |
+
0037<confidence value="4">]</confidence>
|
| 326 |
+
As a result, embodiments of the present invention provide a system, method, and computer program product for an improved oncology inventory management system. The system supports a medical service provider, such as an oncology service provider, by interfacing an inventory management application with a database of electronic medical records. By interfacing the inventory management application with the database of electronic medical records, inventory accuracy may be increased and processing times may be decreased. </p>
|
| 327 |
+
<p id="p-43" num="43">[0038<confidence value="4">]</confidence>
|
| 328 |
+
Many modifications and other embodiments of the invention set forth herein will come to mind to one skilled in the art to which this invention pertains having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the invention is not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation. </p>
|
| 329 |
+
<boundary-data type="header">- 15 - AttyDktNo: 050704/328952</boundary-data>
|
| 330 |
+
</description>
|
| 331 |
+
</us-patent-application>
|
| 332 |
+
|
applicant/11767036.xml
ADDED
|
@@ -0,0 +1,26 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>11767036</doc-number>
|
| 8 |
+
<date>2009-04-20</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<p id="p-1" num="1">Application No. 11/767,036 Atty Dkt No. LEAR 04985 PUS <part-num-ref name="PUS">(04985)</part-num-ref>
|
| 14 |
+
Reply to Office Action of March <part-num-ref name="Reply to Office Action of March">19,</part-num-ref>
|
| 15 |
+
<part-num-ref name="Reply to Office Action of March 19,">2009</part-num-ref>
|
| 16 |
+
Amendments to the Specification: </p>
|
| 17 |
+
<p id="p-2" num="2">Please amend the paragraph beginning on page <part-num-ref name="paragraph beginning on page">5,</part-num-ref>
|
| 18 |
+
at line <part-num-ref name="paragraph beginning on page 5, at line">17</part-num-ref>
|
| 19 |
+
as shown below: </p>
|
| 20 |
+
<p id="p-3" num="3">Further, in carrying out the above objects and other objects, the present invention provides a system for communicating diagnostic data of a vehicle from the vehicle to a vehicle service provider. The system includes a plurality of sensors for monitoring the operational status or condition of components of the vehicle. Each sensor generates a sensor signal indicative of the monitored vehicle component. The system further includes a diagnostics module operable for receiving the sensor signals from the sensors. The diagnostics module generates diagnostic data based on the sensor signals. The system further includes a Bluetooth enabled cell phone in the vehicle. The system further includes a hands-free phone system in the vehicle. The hands-free phone system has a communications module operable for wirelessly communicating with the cell phone using Bluetooth communications. The system further includes an Internet server and a computer of a vehicle service provider having access to the Internet server via the Internet. The diagnostics module transfers the diagnostic data to the communications module.</p>
|
| 21 |
+
<p id="p-4" num="4">The communications module wirelessly transmits the diagnostic data to the cell phone using Bluetooth communications. The cell phone communicates the diagnostic data to the Internet server via the Internet. The <confidence value="66">th</confidence>
|
| 22 |
+
e computer of the vehicle service provider accesses the diagnostic data stored on the Internet server for the vehicle service provider to analyze the diagnostic data to determine if any of the vehicle components are in need of repair or maintenance. </p>
|
| 23 |
+
<p id="p-5" num="5">-2- </p>
|
| 24 |
+
</description>
|
| 25 |
+
</us-patent-application>
|
| 26 |
+
|
applicant/11774106.xml
ADDED
|
@@ -0,0 +1,44 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>11774106</doc-number>
|
| 8 |
+
<date>2010-02-09</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<p id="p-1" num="1">Docket No.<confidence value="5">:</confidence>
|
| 14 |
+
449960 </p>
|
| 15 |
+
<heading id="h-1">AMENDMENTS TO THE SPECIFICATION:</heading>
|
| 16 |
+
<p id="p-2" num="2">Please amend the Specification as follows.</p>
|
| 17 |
+
<p id="p-3" num="3">Please replace the paragraph <part-num-ref name="paragraph">0077,</part-num-ref>
|
| 18 |
+
with the following amended paragraph: </p>
|
| 19 |
+
<p id="p-4" num="4">[0077] If this md5 is not matched with the md5 of a previous responder, the md5 is treated as a non-responder, and the process moves to block <part-num-ref name="process moves to block">110.</part-num-ref>
|
| 20 |
+
In the process at block <part-num-ref name="process at block">10,</part-num-ref>
|
| 21 |
+
the non-responder database <confidence value="2525">-3-2</confidence>
|
| 22 |
+
32c is checked for campaigns suitable for this non- responder md5. A campaign is selected for the non-responder md5, typically by selecting the "active" campaign among rotating campaigns (with each campaign of the rotating campaigns being "active" at predetermined intervals). The selected campaign is then subjected to filtration, at block <part-num-ref name="selected campaign is then subjected to filtration, at block">130,</part-num-ref>
|
| 23 |
+
shown in broken lines. </p>
|
| 24 |
+
<p id="p-5" num="5">Please replace the paragraph <part-num-ref name="paragraph">0191,</part-num-ref>
|
| 25 |
+
with the following amended paragraph: </p>
|
| 26 |
+
<p id="p-6" num="6">[0191<confidence value="6">]</confidence>
|
| 27 |
+
The above-described processes including portions thereof can be performed by software in conjunction with hardware, <confidence value="214">b2Y</confidence>
|
| 28 |
+
hardwar<confidence value="6">e</confidence>
|
| 29 |
+
and combinations thereof. These processes and portions thereof can be performed by computers, computer-type devices, workstations, processors, micro-processors, other electronic searching tools and memory and other storage-type devices associated therewith. The processes and portions thereof can also be embodied in programmable storage devices, for example, compact discs (CDs) or other discs including magnetic, optical, etc., readable by a machine or the like, or other computer usable storage media, including magnetic, optical, or semiconductor storage, or <confidence value="2246">oter</confidence>
|
| 30 |
+
<confidence value="2">u</confidence>
|
| 31 |
+
<confidence value="2">o</confidence>
|
| 32 |
+
<confidence value="22">lr</confidence>
|
| 33 |
+
<confidence value="22">in</confidence>
|
| 34 |
+
the like. </p>
|
| 35 |
+
<p id="p-7" num="7">
|
| 36 |
+
<confidence value="8">2</confidence>
|
| 37 |
+
<confidence value="88">of</confidence>
|
| 38 |
+
<confidence value="88">15</confidence>
|
| 39 |
+
Amendment and Response to First Office Action dated August <part-num-ref name="Amendment and Response to First Office Action dated August">11,</part-num-ref>
|
| 40 |
+
<part-num-ref name="Amendment and Response to First Office Action dated August 11,">2009</part-num-ref>
|
| 41 |
+
U.S. Patent Application Serial No.: 11/774,106 1182.019 -ADK1.019 </p>
|
| 42 |
+
</description>
|
| 43 |
+
</us-patent-application>
|
| 44 |
+
|
applicant/11774444.xml
ADDED
|
The diff for this file is too large to render.
See raw diff
|
|
|
applicant/11778521.xml
ADDED
|
The diff for this file is too large to render.
See raw diff
|
|
|
applicant/11782554.xml
ADDED
|
The diff for this file is too large to render.
See raw diff
|
|
|
applicant/11799200.xml
ADDED
|
@@ -0,0 +1,668 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>11799200</doc-number>
|
| 8 |
+
<date>2007-05-01</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<p id="p-1" num="1">Nokia Corporation Docket No.: NC41899 Harrington & Smith, LLP Docket No.: 859.0008.U<confidence value="4">1</confidence>
|
| 14 |
+
(US) Application for United States Letters Patent by: </p>
|
| 15 |
+
<p id="p-2" num="2">Lars Dalsgaard Apparatus, Method And Computer Program Product Providing Uplink Synchronization Through Use Of Dedicated Uplink Resource Assignment <page-break num="2"/>
|
| 16 |
+
</p>
|
| 17 |
+
<heading id="h-1">APPARATUS, METHOD AND COMPUTER PROGRAM PRODUCT PROVIDING</heading>
|
| 18 |
+
<heading id="h-2">UPLINK SYNCHRONIZATION THROUGH USE OF DED<confidence value="8">I</confidence>
|
| 19 |
+
CATED UPLINK </heading>
|
| 20 |
+
<heading id="h-3">RESOURCE ASSIGNMENT</heading>
|
| 21 |
+
<heading id="h-4">CROSS REFERENCE TO RELATED APPL<confidence value="8">I</confidence>
|
| 22 |
+
CATION: </heading>
|
| 23 |
+
<p id="p-3" num="3">
|
| 24 |
+
<confidence value="1">1</confidence>
|
| 25 |
+
0001<confidence value="2">1</confidence>
|
| 26 |
+
This patent application claims priority under 35 U.S.C. <confidence value="5">§</confidence>
|
| 27 |
+
119(e) from U.S. </p>
|
| 28 |
+
<p id="p-4" num="4">Provisional Patent Application No. 60/796, 767, filed on May 1, 2006, and hereby incorporated by reference in its entirety.</p>
|
| 29 |
+
<heading id="h-5">TECHNICAL FIELD:</heading>
|
| 30 |
+
<p id="p-5" num="5">
|
| 31 |
+
<confidence value="4">1</confidence>
|
| 32 |
+
0002<confidence value="2">1</confidence>
|
| 33 |
+
The exemplary and non-limiting embodiments of this invention relate generally to wireless communications systems, methods, computer program products and devices and, more specifically, relate to techniques for achieving uplink temporal synchronization of user equipment. </p>
|
| 34 |
+
<heading id="h-6">BACKGROUND:</heading>
|
| 35 |
+
<p id="p-6" num="6">
|
| 36 |
+
<confidence value="4">1</confidence>
|
| 37 |
+
0003<confidence value="4">]</confidence>
|
| 38 |
+
The following abbreviations are herewith defined: </p>
|
| 39 |
+
<p id="p-7" num="7">3GPP third generation partnership project <confidence value="8">A</confidence>
|
| 40 |
+
T allocation table (also called physical downlink shared control channel PDCCH) C-RNTI cell radio network temporary identifier DL downlink (node B to UE) DRX discontinuous reception GPRS general packet radio service GSM global system for mobile communication HO hand over IMS instant messaging service LTE long term evolution MAC medium access control Node B base station PTCCH packet timing advance control channel RACH random access channel <boundary-data type="header">
|
| 41 |
+
<confidence value="7">1</confidence>
|
| 42 |
+
</boundary-data>
|
| 43 |
+
<page-break num="3"/>
|
| 44 |
+
RLID radio link identifier RNC radio network control RRC radio resource control SCH shared channel TA timing advance TBF temporary block flow UE user equipment UL uplink (UE to node B) UMTS universal mobile telecommunications system UTRAN UMTS terrestrial radio access network E-UTRAN evolved UTRAN, also referred to as UTRAN-LTE and as 3.9G <confidence value="884">VoI</confidence>
|
| 45 |
+
P voice over <confidence value="8">i</confidence>
|
| 46 |
+
nternet protocol <confidence value="2">1</confidence>
|
| 47 |
+
0004<confidence value="2">]</confidence>
|
| 48 |
+
UTRAN-LTE is defined as a packet-based transmission system only. This implies that there will not be a so-called dedicated connection mode (or circuit switched mode) as exists in some currently deployed systems. </p>
|
| 49 |
+
<p id="p-8" num="8">[0005 As currently defined the uplink air interface resources are divided between an <confidence value="8">U</confidence>
|
| 50 |
+
L-SCH and a contention based RAC<confidence value="5">H</confidence>
|
| 51 |
+
. A Node-B may provide an allocation on the UL-SCH if the UE can be identified (such as with RLID/C-RNT<confidence value="4">I</confidence>
|
| 52 |
+
) and if the TA of the UE has been so recently controlled by the Node-B such that it can be considered to be valid. If the UE has no valid TA it is not allowed to transmit on the UL-SCH. The random access procedure may be used by the UE for initial network access, for TA adjustment, for transfer from LTE-IDLE to LTE-ACT<confidence value="5">I</confidence>
|
| 53 |
+
VE state, for uplink resource requests and during HO. One of a synchronous or non-synchronous random access procedure is used, depending on the validity of UE's TA. </p>
|
| 54 |
+
<p id="p-9" num="9">
|
| 55 |
+
<confidence value="5">[</confidence>
|
| 56 |
+
0006 Further reference with regard to the RACH channel can be made to, for example, Annex B o<confidence value="5">f</confidence>
|
| 57 |
+
3GPP TR 25.813, V<confidence value="5">0</confidence>
|
| 58 |
+
.8.3, 3rd Generation Partnership Project, Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E- UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and Radio interface protocol aspects (Release 7). </p>
|
| 59 |
+
<p id="p-10" num="10">
|
| 60 |
+
<confidence value="5">[</confidence>
|
| 61 |
+
0007 One proposal for UTRAN-LTE is that the <confidence value="5">U</confidence>
|
| 62 |
+
E will receive the UL-SCH resource <boundary-data type="header">
|
| 63 |
+
<confidence value="8">2</confidence>
|
| 64 |
+
</boundary-data>
|
| 65 |
+
<page-break num="4"/>
|
| 66 |
+
allocations from the network through an AT, where the UE would receive the AT at certain instants in time determined at least in part by the current DRX period of the UE (which may be defined by the network). </p>
|
| 67 |
+
<p id="p-11" num="11">
|
| 68 |
+
<confidence value="2">1</confidence>
|
| 69 |
+
0008 It should be noted that in the general case resource(s) are assigned to the UE by the network through the use of DL control signaling. The exact format and content of this control signaling is not particularly germane to an understanding of the invention, and in fact may be subject to revision. </p>
|
| 70 |
+
<p id="p-12" num="12">
|
| 71 |
+
<confidence value="1">1</confidence>
|
| 72 |
+
0009<confidence value="2">]</confidence>
|
| 73 |
+
However, if the currently used DRX period of the U<confidence value="5">E</confidence>
|
| 74 |
+
is long (e.g., seconds) the TA used by the UE before the DRX period may no longer be valid for use in transmission in the UL-SCH. If the UE no longer has a valid TA it is not allowed to transmit in the UL-SCH before the U<confidence value="5">E</confidence>
|
| 75 |
+
has received a new TA value from the network. </p>
|
| 76 |
+
<p id="p-13" num="13">
|
| 77 |
+
<confidence value="2">[</confidence>
|
| 78 |
+
0010 More generally, if the time from the last update of the TA is long, however the TA may be updated, then the TA may not be valid. The use of DRX periods to ascertain the potential validity or invalidity of the current TA of the UE is but one non-limiting example. </p>
|
| 79 |
+
<p id="p-14" num="14">
|
| 80 |
+
<confidence value="2">[</confidence>
|
| 81 |
+
0011<confidence value="5">]</confidence>
|
| 82 |
+
It has been proposed that the procedure for achieving a valid TA (when no valid TA is available) includes transmission by the UE on the non-synchronized RACH channel. </p>
|
| 83 |
+
<p id="p-15" num="15">However, this approach, which utilizes a contention based resource (where the possibility of collisions, backoffs and re-transmissions may occur), may introduce an undesirable and unpredictable delay.</p>
|
| 84 |
+
<p id="p-16" num="16">0012<confidence value="5">]</confidence>
|
| 85 |
+
Another issue relates to a requirement in 3.9G that the UE in the Active state shall always be UL synchronized. Such a requirement would in practice mean that there would be a need for constant DL/UL transmissions in order to allow the network to maintain the UL synchronization (TA) of the UE up-to-date, and could require scheduled DL/UL transmission for no other reason than keeping the UE TA current. As can be appreciated, this approach is not efficient in terms of UE power consumption and bandwidth utilization. </p>
|
| 86 |
+
<p id="p-17" num="17">0013<confidence value="5">]</confidence>
|
| 87 |
+
Yet another issue relates to whether it is really necessary for all connection types and services to maintain UL synchronization at all times. One justification for maintaining U<confidence value="5">E</confidence>
|
| 88 |
+
<boundary-data type="header">
|
| 89 |
+
<confidence value="8">3</confidence>
|
| 90 |
+
</boundary-data>
|
| 91 |
+
<page-break num="5"/>
|
| 92 |
+
UL synchronization is that there is a need for fast connection setup time (short delay), and another is to maintain a constant regular UL/DL data flow with short intervals (e.g., Vo<confidence value="4">I</confidence>
|
| 93 |
+
P). <confidence value="56">In</confidence>
|
| 94 |
+
other situations, however, such as normal WEB <confidence value="8">b</confidence>
|
| 95 |
+
rowsing or email download, the setup time may not <confidence value="5">b</confidence>
|
| 96 |
+
e as important and the data may <confidence value="5">b</confidence>
|
| 97 |
+
e transmitted in a bursty (aperiodic) manner. </p>
|
| 98 |
+
<p id="p-18" num="18">
|
| 99 |
+
<confidence value="16658">[0014</confidence>
|
| 100 |
+
It is noted that in the currently deployed GSM HO procedure, when the UE receives a HO command to a new cell and does not have a valid TA for the new cell, the UE is not allowed to transmit a normal UL bu<confidence value="8">r</confidence>
|
| 101 |
+
st in the new cell. Instead, the UE must transmit a shorter duration burst that leaves a large part of the time slot as a guard time or guard band around the burst. The network measures the propagation delay from the received short burst and sends an appropriate TA value to the UE. The UE can then start to use the newly assigned TA value when transmitting a nor<confidence value="8">m</confidence>
|
| 102 |
+
al UL burst. </p>
|
| 103 |
+
<p id="p-19" num="19">
|
| 104 |
+
<confidence value="2">1</confidence>
|
| 105 |
+
0015<confidence value="2">]</confidence>
|
| 106 |
+
The u<confidence value="5">s</confidence>
|
| 107 |
+
e of the PTCCH in the GPRS is another already deployed procedure for assuring that the U<confidence value="5">E</confidence>
|
| 108 |
+
has UL synchronization. However, the use of this procedure is only valid when the UE has an active TBF, which means that there is an already established UL/DL connection between the network and the UE. </p>
|
| 109 |
+
<heading id="h-7">SU<confidence value="8">M</confidence>
|
| 110 |
+
MARY </heading>
|
| 111 |
+
<p id="p-20" num="20">
|
| 112 |
+
<confidence value="2">1</confidence>
|
| 113 |
+
0016 In an exemplary embodiment of the invention there is a method which includes transmitting to a user equipment an assignment of an uplink resource on which to send an uplink synchronization signal, receiving from the user equipment on the uplink resource the uplink synchronization signal, and determining from the uplink synchronization signal a timing advance for the user equipment. </p>
|
| 114 |
+
<p id="p-21" num="21">
|
| 115 |
+
<confidence value="2">1</confidence>
|
| 116 |
+
0017 In an exemplary embodiment of the invention there is a method which includes receiving from a network device an assignment of an uplink resource on which to send an uplink synchronization signal, and transmitting on the assigned uplink resource the uplink synchronization signal. </p>
|
| 117 |
+
<p id="p-22" num="22">
|
| 118 |
+
<confidence value="56668">[0018</confidence>
|
| 119 |
+
In yet another exemplary embodiment of the invention there is a computer program product embodied on a memo<confidence value="8">r</confidence>
|
| 120 |
+
y and executable by a processor to perform operations, <boundary-data type="header">
|
| 121 |
+
<confidence value="8">4</confidence>
|
| 122 |
+
</boundary-data>
|
| 123 |
+
<page-break num="6"/>
|
| 124 |
+
including transmitting to a user equipment an assignment of an uplink resource on which to send an uplink synchronization signal, receiving from the user equipment on the assigned uplink resource the uplink synchronization signal, and determining from the uplink synchronization signal a timing advance for the user equipment. </p>
|
| 125 |
+
<p id="p-23" num="23">
|
| 126 |
+
<confidence value="2">1</confidence>
|
| 127 |
+
0019 In yet another exemplary embodiment of the invention there is a network element, which includes a transmitter adapted to transmit to a user equipment an assignment of an <confidence value="7">u</confidence>
|
| 128 |
+
plink resource on which to send an uplink synchronization signal, a receiver adapted to receive from the user equipment on the assigned uplink resource the uplink synchronization signal, and a processor adapted to determine from the uplink synchronization signal a timing advance for the user equipment. </p>
|
| 129 |
+
<p id="p-24" num="24">
|
| 130 |
+
<confidence value="2">1</confidence>
|
| 131 |
+
0020 In still another exemplary embodiment of the invention there is a user equipment, which includes a receiver adapted to receive from a network device an assignment of an uplink resource on which to send an uplink synchronization signal, a processor coupled to a memory and adapted to determine the uplink synchronization signal, and a transmitter adapted to transmit on the uplink resource the uplink synchronization signal. </p>
|
| 132 |
+
<p id="p-25" num="25">
|
| 133 |
+
<confidence value="2">1</confidence>
|
| 134 |
+
0021<confidence value="2">]</confidence>
|
| 135 |
+
In yet another exemplary embodiment of the invention there is an apparatus which includes means for transmitting to a user equipment an assignment of an uplink resource on which to send an uplink synchronization signal, means for receiving from the user equipment on the assigned uplink resource the uplink synchronization signal, and means for determining from the uplink synchronization signal a timing advance for the user equipment. </p>
|
| 136 |
+
<p id="p-26" num="26">
|
| 137 |
+
<confidence value="1">1</confidence>
|
| 138 |
+
0022<confidence value="2">]</confidence>
|
| 139 |
+
Further, in the exemplary embodiment of the invention above the means for transmitting comprises a transmitter, the means for receiving comprises a receiver, and the means for deter<confidence value="8">m</confidence>
|
| 140 |
+
ining comprises a processor. </p>
|
| 141 |
+
<heading id="h-8">BRIEF DESCRIPTION OF THE DRAWINGS:</heading>
|
| 142 |
+
<p id="p-27" num="27">
|
| 143 |
+
<confidence value="1">1</confidence>
|
| 144 |
+
0023<confidence value="2">1</confidence>
|
| 145 |
+
The foregoing and other aspects of embodiments of this invention are made more evident in the following Detailed Description when read in conjunction with the attached Drawing Figures. </p>
|
| 146 |
+
<boundary-data type="header">
|
| 147 |
+
<confidence value="8">5</confidence>
|
| 148 |
+
</boundary-data>
|
| 149 |
+
<p id="p-28" num="28">
|
| 150 |
+
<page-break num="7"/>
|
| 151 |
+
<confidence value="2">1</confidence>
|
| 152 |
+
0024<confidence value="5">]</confidence>
|
| 153 |
+
Figure <confidence value="5">1</confidence>
|
| 154 |
+
shows a simplified block diagram of various electronic devices that are suitable for use in practicing the exemplary embodiments of this invention. </p>
|
| 155 |
+
<p id="p-29" num="29">
|
| 156 |
+
<confidence value="4">1</confidence>
|
| 157 |
+
0025 Figure 2 illustrates the protocol stacks of an UMTS packet data service for control signaling and transmission of user data. </p>
|
| 158 |
+
<p id="p-30" num="30">
|
| 159 |
+
<confidence value="2">1</confidence>
|
| 160 |
+
0026<confidence value="5">]</confidence>
|
| 161 |
+
Figure 3A illustrates operation of a method in accordance with the exemplary embodiments of this invention, while Figure 3B shows a conventional approach. </p>
|
| 162 |
+
<p id="p-31" num="31">
|
| 163 |
+
<confidence value="2">1</confidence>
|
| 164 |
+
0027<confidence value="2">1</confidence>
|
| 165 |
+
Figure 4 illustrates currently known techniques for a network to acquire the TA of a UE, as well as a RACH procedure proposed for use in UTRAN-LTE, in addition to an UL synchronization procedure in accordance with an embodiment of this invention. </p>
|
| 166 |
+
<p id="p-32" num="32">
|
| 167 |
+
<confidence value="2">1</confidence>
|
| 168 |
+
0028<confidence value="2">1</confidence>
|
| 169 |
+
Figure 5 illustrates a logic flow diagram that is descriptive of a method and an operation of a network device for implementing the exemplary embodiments of this invention. </p>
|
| 170 |
+
<p id="p-33" num="33">
|
| 171 |
+
<confidence value="1">X</confidence>
|
| 172 |
+
0029<confidence value="5">]</confidence>
|
| 173 |
+
Figure 6 illustrates a logic flow diagram that is descriptive of a method and an operation of a user equipment for implementing the exemplary embodiments of this invention. </p>
|
| 174 |
+
<heading id="h-9">DETA<confidence value="7">I</confidence>
|
| 175 |
+
LED DESCRIPTION: </heading>
|
| 176 |
+
<p id="p-34" num="34">
|
| 177 |
+
<confidence value="2">1</confidence>
|
| 178 |
+
0030<confidence value="5">]</confidence>
|
| 179 |
+
The exemplary embodiments of this invention relate to and are described below in the context of UTRAN-LTE. More specifically, the exemplary embodiments of this invention address the area of UE UL synchronization, and an ability for the network to estimate the UL synchronization for the UE. However, it should be appreciated that at least some aspects of the exempla<confidence value="8">r</confidence>
|
| 180 |
+
y embodiments are applicable to other types of wireless communication systems such as GSM, HSPDA, or any packet-switched system. </p>
|
| 181 |
+
<p id="p-35" num="35">
|
| 182 |
+
<confidence value="2">1</confidence>
|
| 183 |
+
0031<confidence value="5">]</confidence>
|
| 184 |
+
Reference is made first to Figure 1 for illustrating a simplified block diagram of various electronic devices that are suitable for use in practicing the exemplary embodiments of this invention. In Figure <confidence value="4">1</confidence>
|
| 185 |
+
a wireless network <part-num-ref name="wireless network">
|
| 186 |
+
<confidence value="5">1</confidence>
|
| 187 |
+
</part-num-ref>
|
| 188 |
+
is adapted for communication with a UE <part-num-ref name="UE">10</part-num-ref>
|
| 189 |
+
via a <boundary-data type="header">
|
| 190 |
+
<confidence value="8">6</confidence>
|
| 191 |
+
</boundary-data>
|
| 192 |
+
<page-break num="8"/>
|
| 193 |
+
Node B (<confidence value="8">b</confidence>
|
| 194 |
+
ase station) <part-num-ref name="Node B (base station)">12,</part-num-ref>
|
| 195 |
+
also referred to herein as an eNodeB. The network <part-num-ref name="network">
|
| 196 |
+
<confidence value="2">1</confidence>
|
| 197 |
+
</part-num-ref>
|
| 198 |
+
may include a RNC <part-num-ref name="RNC">14,</part-num-ref>
|
| 199 |
+
or other radio controller function, which may be referred to as a mobility management entity <confidence value="88">MM</confidence>
|
| 200 |
+
E or gateway (see 3GPP TS 36.300 V<confidence value="5">1</confidence>
|
| 201 |
+
.0.0). The UE <part-num-ref name="UE">10</part-num-ref>
|
| 202 |
+
includes a data processor (DP) <confidence value="86">10</confidence>
|
| 203 |
+
A, a memory (MEM) <part-num-ref name="memory (MEM)">
|
| 204 |
+
<confidence value="5">1</confidence>
|
| 205 |
+
</part-num-ref>
|
| 206 |
+
<confidence value="5">O</confidence>
|
| 207 |
+
B that stores a program (<confidence value="5">P</confidence>
|
| 208 |
+
ROG) <confidence value="5">O</confidence>
|
| 209 |
+
C, and a suitable radio frequency <confidence value="885">(RF</confidence>
|
| 210 |
+
) transceiver <part-num-ref name="suitable radio frequency (RF) transceiver">
|
| 211 |
+
<confidence value="2">1</confidence>
|
| 212 |
+
</part-num-ref>
|
| 213 |
+
<confidence value="6">O</confidence>
|
| 214 |
+
D for bidirectional wireless communications with the Node B <part-num-ref name="Node B">12,</part-num-ref>
|
| 215 |
+
which also includes a DP 12A, a MEM <confidence value="5">1</confidence>
|
| 216 |
+
2B that stores a <confidence value="5">P</confidence>
|
| 217 |
+
ROG <confidence value="5">l</confidence>
|
| 218 |
+
2C, and a suitable R<confidence value="5">F</confidence>
|
| 219 |
+
transceiver <confidence value="5">1</confidence>
|
| 220 |
+
2D. The Node B <part-num-ref name="Node B">12</part-num-ref>
|
| 221 |
+
is coupled via a data path <part-num-ref name="data path">
|
| 222 |
+
<confidence value="5">1</confidence>
|
| 223 |
+
3 </part-num-ref>
|
| 224 |
+
to the RNC <part-num-ref name="RNC">14</part-num-ref>
|
| 225 |
+
that also includes a DP <confidence value="5">1</confidence>
|
| 226 |
+
4A and a MEM 14B storing an associated <confidence value="5">P</confidence>
|
| 227 |
+
ROG 14C. </p>
|
| 228 |
+
<p id="p-36" num="36">
|
| 229 |
+
<confidence value="4">1</confidence>
|
| 230 |
+
0032 As will <confidence value="5">b</confidence>
|
| 231 |
+
e described <confidence value="8">b</confidence>
|
| 232 |
+
elow, at least the PROGs <confidence value="24">1O</confidence>
|
| 233 |
+
C and <confidence value="5">1</confidence>
|
| 234 |
+
2C include program instructions that, when executed by the associated DP, enable the electronic device to operate in accordance with the exemplary embodiments of this invention. For example, the <confidence value="5">P</confidence>
|
| 235 |
+
ROG <confidence value="588">12C</confidence>
|
| 236 |
+
includes program instructions that direct the Node B <part-num-ref name="Node B">
|
| 237 |
+
<confidence value="5">1</confidence>
|
| 238 |
+
2 </part-num-ref>
|
| 239 |
+
to signal the UE <part-num-ref name="UE">10,</part-num-ref>
|
| 240 |
+
such as in a data structure sent as an AT, for assigning to the UE <part-num-ref name="UE">10</part-num-ref>
|
| 241 |
+
a dedicated uplink resource (e.g., an UL-SCH sub-frame) in which to transmit a special synchronization <confidence value="8">b</confidence>
|
| 242 |
+
urst to be used by the Node B <part-num-ref name="Node B">12</part-num-ref>
|
| 243 |
+
for calculating a TA value, as well as to receive the special <confidence value="8">b</confidence>
|
| 244 |
+
urst from the assigned UL resource for use in calculating the TA value. The <confidence value="5">P</confidence>
|
| 245 |
+
ROG <part-num-ref name="PROG">
|
| 246 |
+
<confidence value="5">1</confidence>
|
| 247 |
+
</part-num-ref>
|
| 248 |
+
<confidence value="5">O</confidence>
|
| 249 |
+
C includes program instructions that direct the UE <part-num-ref name="UE">10</part-num-ref>
|
| 250 |
+
to transmit the special burst in the assigned UL resource. </p>
|
| 251 |
+
<p id="p-37" num="37">
|
| 252 |
+
<confidence value="2">1</confidence>
|
| 253 |
+
0033 Reference is now made to Figure 2, where Figures 2 shows the protocol stack used for control signaling between the mobile station MS and the core network CN. Mobility management MM, call control CC and session management SM of the mobile station MS are signaled on the highest protocol layers <confidence value="8">b</confidence>
|
| 254 |
+
etween the mobile station MS and the core network CN in such a manner that the <confidence value="8">b</confidence>
|
| 255 |
+
ase stations BS and the radio network controller RNC located in <confidence value="8">b</confidence>
|
| 256 |
+
etween are transparent to this signaling. The radio resources management of radio links between mobile stations MS and base stations BS is carried out by a radio resource management system RRM which transmits control data from the radio network controller RNC to the base stations BS. These functions associated with the general management of a mobile system form a group called core network protocols (CN protocols), also known as Non-Access Stratum. </p>
|
| 257 |
+
<p id="p-38" num="38">Correspondingly, the signaling related to the radio network control <confidence value="8">b</confidence>
|
| 258 |
+
etween the mobile station MS, the <confidence value="8">b</confidence>
|
| 259 |
+
ase station BS and the radio network controller RNC is carried out on protocol layers called radio access network protocols (RAN protocols), i.e. Access Stratum. <confidence value="8">T</confidence>
|
| 260 |
+
hese include transfer protocols of the lowest level, whose control signaling is transferred to the higher levels <boundary-data type="header">
|
| 261 |
+
<confidence value="8">7</confidence>
|
| 262 |
+
</boundary-data>
|
| 263 |
+
<page-break num="9"/>
|
| 264 |
+
for further processing. The most essential one of the higher Access Stratum layers is the radio resource control protocol RRC which is responsible for example for esta<confidence value="8">b</confidence>
|
| 265 |
+
lishing, configuring, maintaining and releasing logical connections <confidence value="8">b</confidence>
|
| 266 |
+
etween the mobile station MS and the radio network UTRAN and for transmitting control information from the core network CN and the radio network RAN to the mobile stations MS. In addition, the radio resource control protocol RRC is responsible for allocating sufficient capacity according to the instructions of the radio resource management system RRM to a user terminal connectio<confidence value="8">n</confidence>
|
| 267 |
+
in an application-based capacity allocation, for example. </p>
|
| 268 |
+
<p id="p-39" num="39">
|
| 269 |
+
<confidence value="2">1</confidence>
|
| 270 |
+
0034 The exemplary embodiments of this invention may <confidence value="5">b</confidence>
|
| 271 |
+
e implemented <confidence value="5">b</confidence>
|
| 272 |
+
y computer software executa<confidence value="7">b</confidence>
|
| 273 |
+
le by the DP <confidence value="6">O</confidence>
|
| 274 |
+
A of the UE <part-num-ref name="UE">10</part-num-ref>
|
| 275 |
+
and the other DPs, such as in cooperation with a DP in the network, or <confidence value="5">b</confidence>
|
| 276 |
+
y hardware, or by a combination of software and/or firmware and hardware. </p>
|
| 277 |
+
<p id="p-40" num="40">
|
| 278 |
+
<confidence value="2">1</confidence>
|
| 279 |
+
0035 In general, the various embodiments of the UE <part-num-ref name="UE">10</part-num-ref>
|
| 280 |
+
can include, but are not limited to, cellular telephones, personal digital assistants (PDAs) having wireless communication capabilities, portable computers having wireless communication capabilities, image capture devices such as digital cameras having wireless communication capabilities, gaming devices having wireless communication capabilities, music storage and playback appliances having wireless communication capabilities, Internet appliances permitting wireless Internet access and browsing, as well as porta<confidence value="8">b</confidence>
|
| 281 |
+
le units or terminals that incorporate combinations of such functions. </p>
|
| 282 |
+
<p id="p-41" num="41">
|
| 283 |
+
<confidence value="2">1</confidence>
|
| 284 |
+
0036 The <confidence value="5">M</confidence>
|
| 285 |
+
EMs <confidence value="54">lO</confidence>
|
| 286 |
+
B, 12B and 14B may <confidence value="5">b</confidence>
|
| 287 |
+
e of any type suitable to the local technical environment and may <confidence value="5">b</confidence>
|
| 288 |
+
e implemented using any suitable data storage technology, such as semiconductor-<confidence value="5">b</confidence>
|
| 289 |
+
ased memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and remova<confidence value="8">b</confidence>
|
| 290 |
+
le memory. The DPs <confidence value="66">10</confidence>
|
| 291 |
+
A, <confidence value="5">1</confidence>
|
| 292 |
+
2A and 14A may <confidence value="68">be</confidence>
|
| 293 |
+
of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors <confidence value="8">b</confidence>
|
| 294 |
+
ased on a multi-core processor architecture, as non-limiting examples. </p>
|
| 295 |
+
<p id="p-42" num="42">
|
| 296 |
+
<confidence value="2">1</confidence>
|
| 297 |
+
0037<confidence value="4">1</confidence>
|
| 298 |
+
Having thus introduced one suitable <confidence value="5">b</confidence>
|
| 299 |
+
ut non-limiting technical context for the practice of the exemplary embodiments of this invention, the exemplary embodiments will now be descri<confidence value="8">b</confidence>
|
| 300 |
+
ed with greater specificity. </p>
|
| 301 |
+
<boundary-data type="header">
|
| 302 |
+
<confidence value="8">8</confidence>
|
| 303 |
+
</boundary-data>
|
| 304 |
+
<p id="p-43" num="43">
|
| 305 |
+
<page-break num="10"/>
|
| 306 |
+
<confidence value="5">[</confidence>
|
| 307 |
+
0038<confidence value="2">]</confidence>
|
| 308 |
+
The exemplary embodiments of this invention provide a method and apparatus for the network <part-num-ref name="network">
|
| 309 |
+
<confidence value="2">1</confidence>
|
| 310 |
+
</part-num-ref>
|
| 311 |
+
to measure the UL TA for a certain UE <part-num-ref name="certain UE">10</part-num-ref>
|
| 312 |
+
when UL data transfer is required. The method and apparatus may <confidence value="5">b</confidence>
|
| 313 |
+
e applied to (but are not restricted to) a situation where the network <part-num-ref name="network">
|
| 314 |
+
<confidence value="2">1</confidence>
|
| 315 |
+
</part-num-ref>
|
| 316 |
+
has knowledge <confidence value="8">b</confidence>
|
| 317 |
+
eforehand that there will be a need for the UE <part-num-ref name="UE">10</part-num-ref>
|
| 318 |
+
to transmit in the UL-SCH. </p>
|
| 319 |
+
<p id="p-44" num="44">This may be the case when the network <part-num-ref name="network">
|
| 320 |
+
<confidence value="5">1</confidence>
|
| 321 |
+
</part-num-ref>
|
| 322 |
+
desires to request measurements of some sort from the <confidence value="86">UE</confidence>
|
| 323 |
+
<part-num-ref name="UE">10,</part-num-ref>
|
| 324 |
+
as well as when the network <confidence value="4">I</confidence>
|
| 325 |
+
expects that the UE has a need for sending positive or negative acknowledgments (ACK/NACK) in the UL in response to DL traffic<confidence value="8">.</confidence>
|
| 326 |
+
</p>
|
| 327 |
+
<p id="p-45" num="45">
|
| 328 |
+
<confidence value="5">[</confidence>
|
| 329 |
+
0039 <confidence value="6">I</confidence>
|
| 330 |
+
n accordance with the exemplary embodiments of this invention a network- assigned UE <part-num-ref name="network- assigned UE">10</part-num-ref>
|
| 331 |
+
dedicated UL resource is provided for use <confidence value="5">b</confidence>
|
| 332 |
+
y the UE <part-num-ref name="UE">10</part-num-ref>
|
| 333 |
+
for sending a special <confidence value="8">b</confidence>
|
| 334 |
+
urst. This burst is then used <confidence value="5">b</confidence>
|
| 335 |
+
y the network 1(for example, is used by the Node B <part-num-ref name="Node B">12)</part-num-ref>
|
| 336 |
+
for measuring the TA of the UE <part-num-ref name="UE">10.</part-num-ref>
|
| 337 |
+
The burst is specifically designed to accommodate a large timing uncertainty, e.g., the burst type may resemble the <confidence value="8">b</confidence>
|
| 338 |
+
urst used on the non-synchronous RACH in E-UTRAN, or may resemble the access burst type known from GSM that is used in, for example, handover and RAC<confidence value="68">H.</confidence>
|
| 339 |
+
</p>
|
| 340 |
+
<p id="p-46" num="46">
|
| 341 |
+
<confidence value="5">[</confidence>
|
| 342 |
+
0040 The network <part-num-ref name="network">
|
| 343 |
+
<confidence value="2">1</confidence>
|
| 344 |
+
</part-num-ref>
|
| 345 |
+
calculates the TA of the UE <part-num-ref name="UE">
|
| 346 |
+
<confidence value="58">10</confidence>
|
| 347 |
+
</part-num-ref>
|
| 348 |
+
<confidence value="8">b</confidence>
|
| 349 |
+
ased on the received special burst and thereafter info<confidence value="88">rm</confidence>
|
| 350 |
+
s the UE <part-num-ref name="UE">10</part-num-ref>
|
| 351 |
+
of the new TA value in a following resource assignment message, or through other suitable control signaling means. </p>
|
| 352 |
+
<p id="p-47" num="47">
|
| 353 |
+
<confidence value="5">[</confidence>
|
| 354 |
+
0041<confidence value="5">]</confidence>
|
| 355 |
+
The ensuing description is made using the non-limiting example of the UE <part-num-ref name="UE">
|
| 356 |
+
<confidence value="5">1</confidence>
|
| 357 |
+
0 </part-num-ref>
|
| 358 |
+
in an E-UTRAN LTE-ACTIVE state, <confidence value="5">b</confidence>
|
| 359 |
+
ut not UL synchronized. It can <confidence value="5">b</confidence>
|
| 360 |
+
e noted that the exemplary embodiments of this invention may be employed as well to the UE <part-num-ref name="UE">
|
| 361 |
+
<confidence value="5">1</confidence>
|
| 362 |
+
0 </part-num-ref>
|
| 363 |
+
in, for example, the <confidence value="885">E-U</confidence>
|
| 364 |
+
TRAN LTE-IDLE mode, and in other situations as well including <confidence value="5">b</confidence>
|
| 365 |
+
ut not limited to similar modes of other wireless systems noted by example a<confidence value="8">b</confidence>
|
| 366 |
+
ove. </p>
|
| 367 |
+
<p id="p-48" num="48">
|
| 368 |
+
<confidence value="5">[</confidence>
|
| 369 |
+
0042<confidence value="5">]</confidence>
|
| 370 |
+
<confidence value="85">Wh</confidence>
|
| 371 |
+
en the UE <part-num-ref name="UE">10</part-num-ref>
|
| 372 |
+
is in the ACTIVE state it has already been assigned a unique ID <confidence value="5">b</confidence>
|
| 373 |
+
y the network <confidence value="2">l</confidence>
|
| 374 |
+
. In fact, all UE that are in the ACTIVE state in a given cell have been assigned a unique identifier. This means that the network <part-num-ref name="network">
|
| 375 |
+
<confidence value="2">1</confidence>
|
| 376 |
+
</part-num-ref>
|
| 377 |
+
can uniquely address the UE <part-num-ref name="UE">
|
| 378 |
+
<confidence value="5">1</confidence>
|
| 379 |
+
0. </part-num-ref>
|
| 380 |
+
This may be done, for example, through the use of an AT sent o<confidence value="5">n</confidence>
|
| 381 |
+
the DL. The unique address assigned to the UE <part-num-ref name="UE">10</part-num-ref>
|
| 382 |
+
<confidence value="86">ma</confidence>
|
| 383 |
+
y be referred to as the RLID or as the C-RNT<confidence value="4">I</confidence>
|
| 384 |
+
, as two non-limiting examples. </p>
|
| 385 |
+
<boundary-data type="header">
|
| 386 |
+
<confidence value="8">9</confidence>
|
| 387 |
+
</boundary-data>
|
| 388 |
+
<p id="p-49" num="49">
|
| 389 |
+
<page-break num="11"/>
|
| 390 |
+
<confidence value="1">1</confidence>
|
| 391 |
+
0043<confidence value="4">1</confidence>
|
| 392 |
+
When the UE <part-num-ref name="UE">10</part-num-ref>
|
| 393 |
+
is in the LTE-ACT<confidence value="5">I</confidence>
|
| 394 |
+
VE state it may lose synchronization if it has not transmitted on the UL for some period of time, and further the network <part-num-ref name="network">
|
| 395 |
+
<confidence value="2">1</confidence>
|
| 396 |
+
</part-num-ref>
|
| 397 |
+
has not had the opportunity to calculate and assign a new TA value. In this case the UE <part-num-ref name="UE">10</part-num-ref>
|
| 398 |
+
should not be allowed to transmit a normal burst in the UL-SCH before a new and valid TA value has been received from the network <part-num-ref name="network">1.</part-num-ref>
|
| 399 |
+
The network <confidence value="4">I</confidence>
|
| 400 |
+
calculates the TA based on a special synchronization burst that the UE <part-num-ref name="UE">10</part-num-ref>
|
| 401 |
+
sends in the UL. </p>
|
| 402 |
+
<p id="p-50" num="50">
|
| 403 |
+
<confidence value="2">1</confidence>
|
| 404 |
+
0044<confidence value="2">]</confidence>
|
| 405 |
+
As was noted above, it has been proposed that the synchronization is performed using the non-synchronized RAC<confidence value="5">H</confidence>
|
| 406 |
+
channel procedure (see Figure 3B transmission labeled 330)). </p>
|
| 407 |
+
<p id="p-51" num="51">
|
| 408 |
+
<confidence value="2">[</confidence>
|
| 409 |
+
0045<confidence value="5">]</confidence>
|
| 410 |
+
More specifically, in Figure 3B the Node B, which may be referred to as an eNodeB, sends in an AT an order for the UE <part-num-ref name="UE">
|
| 411 |
+
<confidence value="5">1</confidence>
|
| 412 |
+
0 </part-num-ref>
|
| 413 |
+
to transmit on the RACH <part-num-ref name="RACH">310.</part-num-ref>
|
| 414 |
+
The UE <part-num-ref name="UE">10</part-num-ref>
|
| 415 |
+
responds at <part-num-ref name="responds at">320</part-num-ref>
|
| 416 |
+
by transmitting a preamble (the special synchronization burst) on the non- synchronized RAC<confidence value="5">H</confidence>
|
| 417 |
+
. In response, the eNodeB computes the TA for the UE <part-num-ref name="UE">10</part-num-ref>
|
| 418 |
+
and sends in an AT <part-num-ref name="AT">330</part-num-ref>
|
| 419 |
+
the calculated TA and the UL-SCH allocation. At <part-num-ref name="UL-SCH allocation. At">340</part-num-ref>
|
| 420 |
+
the UE <part-num-ref name="UE">10</part-num-ref>
|
| 421 |
+
sends a unique ID on the UL-SCH, and at <part-num-ref name="UL-SCH, and at">350</part-num-ref>
|
| 422 |
+
the eNodeB sends a normal UL-SCH allocation in an AT. </p>
|
| 423 |
+
<p id="p-52" num="52">
|
| 424 |
+
<confidence value="2">1</confidence>
|
| 425 |
+
0046<confidence value="5">]</confidence>
|
| 426 |
+
The exemplary embodiments of this invention instead provide for the special synchronization burst to be transmitted on an UL-SCH allocation assigned to the UE <part-num-ref name="UE">10</part-num-ref>
|
| 427 |
+
by the network <part-num-ref name="network">1</part-num-ref>
|
| 428 |
+
(see Figure 3A <part-num-ref name="(see Figure 3A">315,</part-num-ref>
|
| 429 |
+
and Figure 4 440), and not on the RACH. That is, and referring to Figure <confidence value="5">1</confidence>
|
| 430 |
+
, the special synchronization burst is sent within an UL-SCH sub-frame that is assigned to the UE <part-num-ref name="UE">10</part-num-ref>
|
| 431 |
+
by the Node-B in, for example, an AT. Note that a single AT/PDCCH may allocate more than one UE <part-num-ref name="single AT/PDCCH may allocate more than one UE">10</part-num-ref>
|
| 432 |
+
to the same UL-SCH, which may be dedicated for the special synchronization bursts detailed herein. It is within the scope if this invention that two UEs <part-num-ref name="scope if this invention that two UEs">10</part-num-ref>
|
| 433 |
+
may be assigned in the same AT/PDCCH the same UL (shared) resource on which to transmit their individual uplink synchronization signals. In such a case of simultaneous UL synchronization bursts on the same shared channel, the eNode B <part-num-ref name="eNode B">12</part-num-ref>
|
| 434 |
+
can distinguish the UEs from one another by use of a separate and unique preamble used by each of the UEs <part-num-ref name="UEs">10</part-num-ref>
|
| 435 |
+
on their uplink transmission of the special synchronization burst. In one embodiment such a unique preamble is signalled to each UE upon cell entry (or other control signalling) so that each UE is pre-allocated a unique preamble for use with the UL-SCH synchronization burst. In another embodiment the AT/PDCCH itself may include an additional field so as to make an association between a preamble and an U<confidence value="5">E</confidence>
|
| 436 |
+
's RLID or other UE identifier used in the AT/PDCCH. In this embodiment, when the <confidence value="5">U</confidence>
|
| 437 |
+
E recognizes that a preamble in that new field is associated with its identifier, it uses <boundary-data type="header">
|
| 438 |
+
<confidence value="66">10</confidence>
|
| 439 |
+
</boundary-data>
|
| 440 |
+
<page-break num="12"/>
|
| 441 |
+
that preamble on the UL-SCH synchronization burst. In either manner, the preamble enables the eNode B to distinguish multiple UE's sending their own synchronization bursts at the same time on the same shared channel. </p>
|
| 442 |
+
<p id="p-53" num="53">
|
| 443 |
+
<confidence value="2">[</confidence>
|
| 444 |
+
0047<confidence value="2">(</confidence>
|
| 445 |
+
The special synchronization burst differs from the nor<confidence value="8">m</confidence>
|
| 446 |
+
al UL-SCH burst in the sense that a larger guard time (GT) is included to accommodate the unknown TA (and thus to avoid interfering with UL transmissions sent by other UEs <confidence value="5">1</confidence>
|
| 447 |
+
0). The guard time may be made equal to that used in the non-synchronous RACH transmission (Figure 3B, 320). When the eNodeB <part-num-ref name="eNodeB">
|
| 448 |
+
<confidence value="5">1</confidence>
|
| 449 |
+
2 </part-num-ref>
|
| 450 |
+
receives the special burst it calculates the TA of the UE <part-num-ref name="UE">
|
| 451 |
+
<confidence value="2">1</confidence>
|
| 452 |
+
</part-num-ref>
|
| 453 |
+
<part-num-ref name="">0</part-num-ref>
|
| 454 |
+
in a conventional manner, and assigns the TA to the UE <part-num-ref name="UE">
|
| 455 |
+
<confidence value="5">1</confidence>
|
| 456 |
+
0 </part-num-ref>
|
| 457 |
+
in the DL either through (as non-limiting examples): normal control signaling, as part of a header in a nor<confidence value="8">m</confidence>
|
| 458 |
+
al data transmission, or in a (next) AT. </p>
|
| 459 |
+
<p id="p-54" num="54">
|
| 460 |
+
<confidence value="5">[</confidence>
|
| 461 |
+
0048<confidence value="2">(</confidence>
|
| 462 |
+
In accordance with the exemplary aspects of this invention, and because the synchronization burst is sent on an UL resource dedicated to a specific UE <part-num-ref name="specific UE">10,</part-num-ref>
|
| 463 |
+
there can be no collisions with bursts sent by other UEs, as may occur when using the RACH. </p>
|
| 464 |
+
<p id="p-55" num="55">
|
| 465 |
+
<confidence value="4">1</confidence>
|
| 466 |
+
0049<confidence value="2">(</confidence>
|
| 467 |
+
As one non-limiting example, the synchronization burst may comprise a cell specific pilot code sequence. </p>
|
| 468 |
+
<p id="p-56" num="56">
|
| 469 |
+
<confidence value="2">[</confidence>
|
| 470 |
+
0050<confidence value="2">1</confidence>
|
| 471 |
+
Several different alternatives exist for the network <confidence value="2">I</confidence>
|
| 472 |
+
to indicate to the U<confidence value="5">E</confidence>
|
| 473 |
+
<part-num-ref name="UE">10</part-num-ref>
|
| 474 |
+
that the purpose of the assigned UL resource is for TA measurement. In a first non-limiting example this may be indicated directly in an AT that no TA value is available (in a TA field), and that the UE <part-num-ref name="UE">10</part-num-ref>
|
| 475 |
+
should therefore use the assigned UL-SC<confidence value="5">H</confidence>
|
| 476 |
+
resource for sending the synchronization burst transmission (see Figure 1). In a second non-limiting example this may be indicated based on a TA value lifetime timer (a software and/or hardware timer) that runs in both the UE <part-num-ref name="UE">10</part-num-ref>
|
| 477 |
+
and in the network <confidence value="2">I</confidence>
|
| 478 |
+
(or through the use of other time measurement alternatives such as, for example, the duration of DRX period(s) or frame numbers). If the TA validity timer is exceeded the UE <part-num-ref name="UE">10</part-num-ref>
|
| 479 |
+
should use the assigned UL-SC<confidence value="5">H</confidence>
|
| 480 |
+
resource for transmission of the synchronization burst. In a third non-limiting example the AT/PDCCH or other resource allocation message can include a preamble associated with a UE's temporary identifier (either associated in the AT itself or signalled to the UE upon the UE's entry into the cell), where the presence of such a preamble in the AT indicates to the UE that it is to send a special synchronization burst on the resources allocated it in that AT/PDCCH. The UE then sends that preamble itself on the uplink allocated <boundary-data type="header">
|
| 481 |
+
<confidence value="22">11</confidence>
|
| 482 |
+
</boundary-data>
|
| 483 |
+
<page-break num="13"/>
|
| 484 |
+
resource as<confidence value="5">.</confidence>
|
| 485 |
+
its synchronization <confidence value="8">b</confidence>
|
| 486 |
+
urst (or in conjunction with some other information that serves as the <confidence value="8">b</confidence>
|
| 487 |
+
urst). As above, the same AT/PDCCH can allocate multiple UEs <part-num-ref name="same AT/PDCCH can allocate multiple UEs">10</part-num-ref>
|
| 488 |
+
for sending a synchronization <confidence value="8">b</confidence>
|
| 489 |
+
urst <confidence value="5">b</confidence>
|
| 490 |
+
y using <confidence value="8">u</confidence>
|
| 491 |
+
nique pream<confidence value="8">b</confidence>
|
| 492 |
+
les sent in the same AT/PDCCH and associated with different UEs. Note that the preamble em<confidence value="8">b</confidence>
|
| 493 |
+
odiment may <confidence value="5">b</confidence>
|
| 494 |
+
e used to enable the e-Node B to distinguish among different UE's synchronization bursts even where the AT indicates that no TA value is availa<confidence value="8">b</confidence>
|
| 495 |
+
le or where the lifetime timer has expired. </p>
|
| 496 |
+
<p id="p-57" num="57">
|
| 497 |
+
<confidence value="266662">[00511</confidence>
|
| 498 |
+
The timing advance is a signal derived from the time synchronization of the UL sequence and sent by the eNB <part-num-ref name="eNB">12</part-num-ref>
|
| 499 |
+
to the UE <part-num-ref name="UE">10,</part-num-ref>
|
| 500 |
+
which the UE <part-num-ref name="UE">10</part-num-ref>
|
| 501 |
+
uses to advance its timings of transmissions to the eNB so as to compensate for propagation delay and thus time align the transmissions from different U<confidence value="5">E</confidence>
|
| 502 |
+
s with the receiver window of a eNB <part-num-ref name="eNB">12.</part-num-ref>
|
| 503 |
+
By avoiding the overlapping of uplink transmissions, timing advance allows time domain multiplexing in the <confidence value="88">up</confidence>
|
| 504 |
+
link. </p>
|
| 505 |
+
<p id="p-58" num="58">
|
| 506 |
+
<confidence value="5">[</confidence>
|
| 507 |
+
0052<confidence value="1">!</confidence>
|
| 508 |
+
The active mode or state noted above is sometimes referred to as an LTE- ACTIVE or RRC_CONNECTED state. In such a state, network controlled UE assisted handovers are performed. <confidence value="66">In</confidence>
|
| 509 |
+
this state, the timing advance may be permanently maintained or only temporarily maintained. If temporary, the MAC knows if layer <part-num-ref name="MAC knows if layer">
|
| 510 |
+
<confidence value="5">1</confidence>
|
| 511 |
+
</part-num-ref>
|
| 512 |
+
is synchronized and which procedure to use to start transmitting in the uplink. Cases where the UL synchronization status may move from "synchronized" to "non-synchronized" include an expiration of a timer; non- synchronized handover; or an explicit request by MAC or RRC in the eNB <part-num-ref name="eNB">
|
| 513 |
+
<confidence value="4">1</confidence>
|
| 514 |
+
</part-num-ref>
|
| 515 |
+
<part-num-ref name="">2.</part-num-ref>
|
| 516 |
+
Any of these may cause the eNB to send a resource allocation to the UE for the synchronization <confidence value="8">b</confidence>
|
| 517 |
+
urst above and cause the UE to send it so as to <confidence value="8">b</confidence>
|
| 518 |
+
ecome synchronized. </p>
|
| 519 |
+
<p id="p-59" num="59">
|
| 520 |
+
<confidence value="5">[</confidence>
|
| 521 |
+
0053<confidence value="2">1</confidence>
|
| 522 |
+
As can <confidence value="5">b</confidence>
|
| 523 |
+
e appreciated, the RACH need not <confidence value="5">b</confidence>
|
| 524 |
+
e utilized for achieving the UL UE synchronization, and thereby the procedure in accordance with the exemplary embodiments of this invention avoids collision risks and the uncertainty in the delay that are inherent in the use of the RACH-<confidence value="5">b</confidence>
|
| 525 |
+
ased synchronization procedure. Assuming that the UE <part-num-ref name="UE">10</part-num-ref>
|
| 526 |
+
receives the ATs when requested it can also <confidence value="2">h</confidence>
|
| 527 |
+
e seen that this procedure is a more efficient use of radio resources. </p>
|
| 528 |
+
<p id="p-60" num="60">
|
| 529 |
+
<confidence value="5">[</confidence>
|
| 530 |
+
0054 Referring to Figure 4, the signaling sequence <part-num-ref name="signaling sequence">4<confidence value="5">1</confidence>
|
| 531 |
+
0 </part-num-ref>
|
| 532 |
+
refers to the conventional A<confidence value="5">c</confidence>
|
| 533 |
+
tive state when UE <part-num-ref name="conventional Active state when UE">
|
| 534 |
+
<confidence value="5">1</confidence>
|
| 535 |
+
0 </part-num-ref>
|
| 536 |
+
is UL synchronized, and the <confidence value="58">UE</confidence>
|
| 537 |
+
<part-num-ref name="UE">
|
| 538 |
+
<confidence value="66">10</confidence>
|
| 539 |
+
</part-num-ref>
|
| 540 |
+
uses the synchronized RAC<confidence value="56">I-</confidence>
|
| 541 |
+
channel for requesting resources from the network <part-num-ref name="network">1.</part-num-ref>
|
| 542 |
+
</p>
|
| 543 |
+
<boundary-data type="header">
|
| 544 |
+
<confidence value="88">12</confidence>
|
| 545 |
+
</boundary-data>
|
| 546 |
+
<p id="p-61" num="61">
|
| 547 |
+
<page-break num="14"/>
|
| 548 |
+
<confidence value="2">]</confidence>
|
| 549 |
+
0055<confidence value="5">]</confidence>
|
| 550 |
+
The signal <part-num-ref name="signal">420</part-num-ref>
|
| 551 |
+
is shown for completeness, but actually may be eliminated as the UE <part-num-ref name="UE">10</part-num-ref>
|
| 552 |
+
already has UL synchronization. As such, the use of the non-synchronized RACH channel at this time would be a waste of resources. </p>
|
| 553 |
+
<p id="p-62" num="62">
|
| 554 |
+
<confidence value="4">1</confidence>
|
| 555 |
+
0056<confidence value="5">]</confidence>
|
| 556 |
+
The signal <part-num-ref name="signal">430</part-num-ref>
|
| 557 |
+
shows the conventional procedure, when the UE <part-num-ref name="UE">
|
| 558 |
+
<confidence value="5">1</confidence>
|
| 559 |
+
0 </part-num-ref>
|
| 560 |
+
is not UL synchronized, that uses the non-synchronized RACH channel to initially access the network. </p>
|
| 561 |
+
<p id="p-63" num="63">
|
| 562 |
+
<confidence value="2">]</confidence>
|
| 563 |
+
0057<confidence value="2">]</confidence>
|
| 564 |
+
The signaling sequence <part-num-ref name="signaling sequence">440</part-num-ref>
|
| 565 |
+
is in accordance with the exemplary embodiments of this invention (see also Figure 3A), where the network <part-num-ref name="network">
|
| 566 |
+
<confidence value="5">1</confidence>
|
| 567 |
+
</part-num-ref>
|
| 568 |
+
assigns via an AT a special UL resource to be used by the UE <part-num-ref name="UE">10</part-num-ref>
|
| 569 |
+
for transmitting the UL access burst to be used by the network for TA estimation/calculation. The calculated TA is delivered to the UE in the DL, in this example, via an AT, although other control signaling procedures could be used as was noted above. </p>
|
| 570 |
+
<p id="p-64" num="64">
|
| 571 |
+
<confidence value="2">]</confidence>
|
| 572 |
+
0058<confidence value="2">]</confidence>
|
| 573 |
+
The signaling sequence <part-num-ref name="signaling sequence">450</part-num-ref>
|
| 574 |
+
illustrates a conventional Idle mode procedure (network <part-num-ref name="conventional Idle mode procedure (network">1</part-num-ref>
|
| 575 |
+
initiated throug<confidence value="8">h</confidence>
|
| 576 |
+
paging and UE <part-num-ref name="initiated through paging and UE">10</part-num-ref>
|
| 577 |
+
initiated through the non-synchronized RACH channel procedure). However, as was noted above the exemplary embodiments of this invention may be applied as well to Idle mode UL synchronization. </p>
|
| 578 |
+
<p id="p-65" num="65">
|
| 579 |
+
<confidence value="2">|</confidence>
|
| 580 |
+
0059<confidence value="2">]</confidence>
|
| 581 |
+
There are a number of advantages that can be realized through the use of the exemplary embodiments of this invention. For example, the use of the exemplary embodiments of this invention reduces the load on the non-synchronized RACH channel and, therefore, saves radio resources as transmission on a scheduled resource is generally more efficient than transmission on a contention-based resource. As another example, setup delays due to possible RACH collisions can be reduced, as the possibility for a RACH collision to occur is eliminated. </p>
|
| 582 |
+
<p id="p-66" num="66">As another example, the use of the exemplary embodiments of this invention ensures an easy and controlled way for the network <part-num-ref name="network">
|
| 583 |
+
<confidence value="2">1</confidence>
|
| 584 |
+
</part-num-ref>
|
| 585 |
+
to be able to acquire the UE TA value when the UL traffic needs are known. </p>
|
| 586 |
+
<p id="p-67" num="67">
|
| 587 |
+
<confidence value="2">]</confidence>
|
| 588 |
+
0060<confidence value="2">]</confidence>
|
| 589 |
+
Further, it can be appreciated that the use of the exemplary embodiments of this invention relaxes any restrictions that may be imposed on the length of DRX periods, as it simplifies and makes more efficient a subsequent UL re-synchronization of the U<confidence value="5">E</confidence>
|
| 590 |
+
<part-num-ref name="UE">10</part-num-ref>
|
| 591 |
+
after a possibly lengthy DRX period. </p>
|
| 592 |
+
<boundary-data type="header">
|
| 593 |
+
<confidence value="88">13</confidence>
|
| 594 |
+
</boundary-data>
|
| 595 |
+
<p id="p-68" num="68">
|
| 596 |
+
<page-break num="15"/>
|
| 597 |
+
<confidence value="2">1</confidence>
|
| 598 |
+
0061<confidence value="2">1</confidence>
|
| 599 |
+
Referring to Fig. 5, there is a method in accordance with an exemplary embodiment of the invention, wherein a network device is transmitting <part-num-ref name="network device is transmitting">501</part-num-ref>
|
| 600 |
+
to a user equipment an assignment of an uplink resource on which to send an uplink synchronization signal. This is followed <confidence value="5">b</confidence>
|
| 601 |
+
y receiving <part-num-ref name="uplink synchronization signal. This is followed by receiving">510</part-num-ref>
|
| 602 |
+
from the user equipment on the assigned uplink resource the uplink synchronization signal, and determining <part-num-ref name="uplink synchronization signal, and determining">520</part-num-ref>
|
| 603 |
+
from the uplink synchronization signal a current timing advance for the user equipment. </p>
|
| 604 |
+
<p id="p-69" num="69">
|
| 605 |
+
<confidence value="5">[</confidence>
|
| 606 |
+
0062<confidence value="2">1</confidence>
|
| 607 |
+
Referring to Fig. 6, there is a method of an exemplary embodiment of the invention, wherein a user equipment is receiving from a network device <part-num-ref name="network device">601</part-num-ref>
|
| 608 |
+
an assignment of an uplink resource on which to send an uplink synchronization signal. Thereafter, the user transmits <part-num-ref name="user transmits">610</part-num-ref>
|
| 609 |
+
the uplink synchronization signal on the assigned uplink resource. </p>
|
| 610 |
+
<p id="p-70" num="70">
|
| 611 |
+
<confidence value="5">[</confidence>
|
| 612 |
+
0063<confidence value="2">1</confidence>
|
| 613 |
+
As can <confidence value="5">b</confidence>
|
| 614 |
+
e realized, the exemplary embodiments of this invention provide methods, apparatus and computer program products for use in performing UL synchronization of the UE <part-num-ref name="UE">10</part-num-ref>
|
| 615 |
+
<confidence value="5">b</confidence>
|
| 616 |
+
y assigning to the UE <part-num-ref name="UE">10</part-num-ref>
|
| 617 |
+
an UL resource in which to transmit an UL synchronization signal, and to receive at the Node B <part-num-ref name="Node B">12</part-num-ref>
|
| 618 |
+
the synchronization signal from the assigned U L resource for use in determining a current TA value for use <confidence value="5">b</confidence>
|
| 619 |
+
y the UE <part-num-ref name="UE">10</part-num-ref>
|
| 620 |
+
in subsequent UL transmissions to the Node B <part-num-ref name="Node B">12.</part-num-ref>
|
| 621 |
+
The UL resource is preferably one dedicated to the U<confidence value="5">E</confidence>
|
| 622 |
+
<part-num-ref name="UE">10</part-num-ref>
|
| 623 |
+
so as to avoid a potential for interference with or from a transmission from another UE, and is preferably a non- contention <confidence value="8">b</confidence>
|
| 624 |
+
ased UL resource. Specific preambles pre-allocated to different UEs <part-num-ref name="non- contention based UL resource. Specific preambles pre-allocated to different UEs">10</part-num-ref>
|
| 625 |
+
can also <confidence value="68">be</confidence>
|
| 626 |
+
used to avoid collision among UEs sharing the same UL-SCH as detailed above, in that the synchronization burst itself includes the pre-amble which the e-NodeB recognizes as unique to a particular U<confidence value="5">E</confidence>
|
| 627 |
+
<part-num-ref name="particular UE">10.</part-num-ref>
|
| 628 |
+
The synchronization signal may <confidence value="5">b</confidence>
|
| 629 |
+
e a synchronization burst comprised of<confidence value="5">,</confidence>
|
| 630 |
+
for example, a cell specific pilot code sequence or a pream<confidence value="8">b</confidence>
|
| 631 |
+
le associated with a specific UE <part-num-ref name="specific UE">10</part-num-ref>
|
| 632 |
+
(e.g., associated upon cell entry or in the AT/PDCCH/resource allocation message itself which allocates the uplink resource to send the synchronization burst). </p>
|
| 633 |
+
<p id="p-71" num="71">0064 In general, the various embodiments may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. For example, some aspects may <confidence value="88">be</confidence>
|
| 634 |
+
implemented in hardware, while other aspects may <confidence value="5">b</confidence>
|
| 635 |
+
e implemented in firmware or software which may <confidence value="5">b</confidence>
|
| 636 |
+
e executed <confidence value="5">b</confidence>
|
| 637 |
+
y a controller, microprocessor or other computing device, although the invention is not limited thereto. While various aspects of the invention may <confidence value="5">b</confidence>
|
| 638 |
+
e illustrated and <boundary-data type="header">
|
| 639 |
+
<confidence value="88">14</confidence>
|
| 640 |
+
</boundary-data>
|
| 641 |
+
<page-break num="16"/>
|
| 642 |
+
described as block diagrams, signal flow diagrams, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof. </p>
|
| 643 |
+
<p id="p-72" num="72">
|
| 644 |
+
<confidence value="4">1</confidence>
|
| 645 |
+
0065<confidence value="5">]</confidence>
|
| 646 |
+
Embodiments of the inventions maybe practiced in various components such as integrated circuit modules. The design of integrated circuits is by and large a highly automated process. Complex and powerful software tools are available for converting a logic level design into a semiconductor circuit design ready to be etched and for<confidence value="8">m</confidence>
|
| 647 |
+
ed on a semiconductor substrate. </p>
|
| 648 |
+
<p id="p-73" num="73">
|
| 649 |
+
<confidence value="2">1</confidence>
|
| 650 |
+
0066<confidence value="5">]</confidence>
|
| 651 |
+
Programs, such as those provided by Synopsys, Inc. of Mountain View, California and Cadence Design, of San Jose, California automatically route conductors and locate components on a semiconductor chip using well established rules of design as well as libraries of pre-stored desi<confidence value="8">g</confidence>
|
| 652 |
+
n modules. Once the design for a semiconductor circuit has been completed, the resultant design, in a standardized electronic format (e.g., Opus, GDS<confidence value="55">II</confidence>
|
| 653 |
+
, or the like) may be transmitted to a semiconductor fabrication facility or "fab<confidence value="5">"</confidence>
|
| 654 |
+
for fabrication. </p>
|
| 655 |
+
<p id="p-74" num="74">
|
| 656 |
+
<confidence value="5">[</confidence>
|
| 657 |
+
0067<confidence value="2">]</confidence>
|
| 658 |
+
Various modifications and adaptations may become apparent to those skilled in the relevant arts in view of the foregoing description, when read in conjunction with the accompanying drawings. For example, while the exemplary embodiments of the invention have been described above in the context of the UTRAN and E-UTRAN systems, it should be appreciated that the exemplary embodiments of this invention can be applied as well to other types of wireless communications systems, methods and schemes. However, any and all modifications of the teachings of this invention will still fall within the scope of the non-limiting embodiments of this invention. </p>
|
| 659 |
+
<p id="p-75" num="75">
|
| 660 |
+
<confidence value="2">1</confidence>
|
| 661 |
+
0068<confidence value="5">]</confidence>
|
| 662 |
+
Furthermore, some of the features of the various non-limiting embodiments of this invention may be used to advantage without the corresponding use of other features. As such, the foregoing description should be considered as merely illustrative of the principles, teachings and exemplary embodiments of this invention, and not in limitation thereof. </p>
|
| 663 |
+
<boundary-data type="header">
|
| 664 |
+
<confidence value="88">15</confidence>
|
| 665 |
+
</boundary-data>
|
| 666 |
+
</description>
|
| 667 |
+
</us-patent-application>
|
| 668 |
+
|
applicant/11843036.xml
ADDED
|
The diff for this file is too large to render.
See raw diff
|
|
|
applicant/11844920.xml
ADDED
|
@@ -0,0 +1,22 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>11844920</doc-number>
|
| 8 |
+
<date>2011-12-02</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<p id="p-1" num="1">Amendments to the Specification Please AMEND paragraph [0059] as follows:</p>
|
| 14 |
+
<p id="p-2" num="2">[0059] The number of different excitation and emission wavelength bands (e.g., filter combinations) and images may vary. In general, as more images are captured, more information is gathered for spectral unmixing. In one embodiment, a sequential scan of filters is launched to cover spectral features of all the fluorophores of interest. Sampled spectral peaks and valleys provide orthogonal spectral characteristics so that an unmixing algorithm can differentiate diffe<confidence value="8">r</confidence>
|
| 15 |
+
en<confidence value="8">t</confidence>
|
| 16 |
+
between different fluorophores. At the least, the number of different combinations is no less than the number of fluorophores. In a specific embodiment, successive and different combinations use a common excitation wavelength band and changing emission wavelength bands. In another specific embodiment, different combinations use a common emission wavelength band and changing excitation wavelength bands. Alternatively, multiple excitation wavelength bands and multiple emission wavelength bands may be used for the successive and different combinations. </p>
|
| 17 |
+
<p id="p-3" num="3">XENOP<confidence value="4">0</confidence>
|
| 18 |
+
19 2 of <part-num-ref name="of">15</part-num-ref>
|
| 19 |
+
11/844,920 </p>
|
| 20 |
+
</description>
|
| 21 |
+
</us-patent-application>
|
| 22 |
+
|
applicant/11850930.xml
ADDED
|
@@ -0,0 +1,28 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>11850930</doc-number>
|
| 8 |
+
<date>2010-08-12</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<p id="p-1" num="1">Application Number 11<confidence value="5">/</confidence>
|
| 14 |
+
850,930 </p>
|
| 15 |
+
<heading id="h-1">AMENDED DETAILED DESCRIPTION OF THE PREFERED EMBODIMENT</heading>
|
| 16 |
+
<p id="p-2" num="2">(Currently Amended) [0030] Fig. 3 Shows a <part-num-ref name="">3</part-num-ref>
|
| 17 |
+
dimensional view of the invention and is an example of how the coiled tubes, bein<confidence value="8">g</confidence>
|
| 18 |
+
selected from a group of metals consistin<confidence value="8">g</confidence>
|
| 19 |
+
of copper<confidence value="5">,</confidence>
|
| 20 |
+
steel or aluminum are utilized, wrapping one consecutively inside the other, as in this case with <part-num-ref name="other, as in this case with">7</part-num-ref>
|
| 21 |
+
& <part-num-ref name="&">8</part-num-ref>
|
| 22 |
+
leaving just enough space between the coiled tubes for the viscous product to flow past them in close enough proximity so as to transfer the heat from the coiled tubes to the viscous product. 6a & 6b shows how the center pipe can be utilized as the viscous product inlet to convey the viscous product into the invention. The center pipe 6b stops short of the end of the end of the invention, this allows the viscous product to reverse its direction of flow and return in the same direction from which it came. Inlet <part-num-ref name="same direction from which it came. Inlet">4</part-num-ref>
|
| 23 |
+
& outlet <part-num-ref name="& outlet">5</part-num-ref>
|
| 24 |
+
are for the coiled heating tubes. The viscous product outlet is <part-num-ref name="viscous product outlet is">2.</part-num-ref>
|
| 25 |
+
</p>
|
| 26 |
+
</description>
|
| 27 |
+
</us-patent-application>
|
| 28 |
+
|
applicant/11854279.xml
ADDED
|
The diff for this file is too large to render.
See raw diff
|
|
|
applicant/11854344.xml
ADDED
|
@@ -0,0 +1,333 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<?xml version="1.0" encoding="utf-8"?>
|
| 2 |
+
<!DOCTYPE us-patent-application SYSTEM "PATI-v1.0.3-2011-06-23.dtd">
|
| 3 |
+
<us-patent-application lang="EN" dtd-version="v1.0.3 2011-06-23" id="us-patent-application" country="US">
|
| 4 |
+
<us-bibliographic-data-application lang="EN" country="US">
|
| 5 |
+
<application-reference appl-type="utility">
|
| 6 |
+
<document-id>
|
| 7 |
+
<doc-number>11854344</doc-number>
|
| 8 |
+
<date>2007-09-12</date>
|
| 9 |
+
</document-id>
|
| 10 |
+
</application-reference>
|
| 11 |
+
</us-bibliographic-data-application>
|
| 12 |
+
<description id="description">
|
| 13 |
+
<boundary-data type="header">
|
| 14 |
+
<confidence value="8">1</confidence>
|
| 15 |
+
</boundary-data>
|
| 16 |
+
<p id="p-1" num="1">P000793-NAPD-TJM (003.0381) </p>
|
| 17 |
+
<heading id="h-1">APPARATUS AND METHODS FOR AUTOMATICALLY ACTIVATING</heading>
|
| 18 |
+
<heading id="h-2">A MOTOR VEHICLE TURN SIGNAL LAMP</heading>
|
| 19 |
+
<heading id="h-3">TECHNICAL FIELD</heading>
|
| 20 |
+
<p id="p-2" num="2">[0001<confidence value="5">]</confidence>
|
| 21 |
+
The present invention generally relates to motor vehicles, and more particularly relates to apparatus and methods for automatically activating a motor vehicle turn signal lamp prior to the motor vehicle reaching a turn. </p>
|
| 22 |
+
<heading id="h-4">BACKGROUND OF THE INVENTION</heading>
|
| 23 |
+
<p id="p-3" num="3">[0002<confidence value="5">]</confidence>
|
| 24 |
+
Many motor vehicles include a turn-by-turn navigation system designed to guide the user to a predetermined destination. The user typically inputs a starting point and a destination or just a destination, and the navigation system calculates a route from the starting point to the destination or from the motor vehicle's current location to the destination. As the user navigates along the calculated route, the navigation system provides visual and/or audible instructions. </p>
|
| 25 |
+
<p id="p-4" num="4">[0003<confidence value="5">]</confidence>
|
| 26 |
+
For example, the vast majority of routes include one or more turns that the user must make. Prior to reaching a turn, contemporary navigation systems typically visually and/or audibly instruct the user to "turn left" or "turn right" as the user approaches a turn. However, if the user has muted the sound of the navigation system or is not paying enough attention to the visual and/or audible instructions, the user may miss a turn. Moreover, if the user is paying too much attention to the instructions and/or surrounding environment (e.g., traffic conditions, obstacles, etc.), the user may fail to properly activate a turn signal lamp of his/her motor vehicle. Specifically, the user may fail to activate the turn signal lamp at a safe distance (or a distance prescribed by law) prior to the turn, or may fail to activate the turn signal lamp altogether. </p>
|
| 27 |
+
<p id="p-5" num="5">[0004<confidence value="5">]</confidence>
|
| 28 |
+
Accordingly, it is desirable to provide apparatus and methods for automatically activating a motor vehicle turn signal lamp prior to the motor vehicle reaching a turn. Furthermore, other desirable features and <page-break num="2"/>
|
| 29 |
+
<boundary-data type="header">
|
| 30 |
+
<confidence value="8">2</confidence>
|
| 31 |
+
</boundary-data>
|
| 32 |
+
characteristics of the present invention will become apparent from the subsequent detailed description and the appended claims, taken in conjunction with the accompanying drawings and the foregoing technical field and background. </p>
|
| 33 |
+
<heading id="h-5">SUMMARY OF THE INVENTION</heading>
|
| 34 |
+
<p id="p-6" num="6">[0005<confidence value="5">]</confidence>
|
| 35 |
+
Various exemplary embodiments of the invention provide a motor vehicle comprising a turn signal lamp and a navigation system coupled to the turn signal lamp. The navigation system is configured to determine a route to a destination, the route having a turn. The navigation system is also configured to monitor the present position of the motor vehicle and automatically activate the turn signal when the motor vehicle approaches the turn. </p>
|
| 36 |
+
<p id="p-7" num="7">[0006<confidence value="5">]</confidence>
|
| 37 |
+
Other exemplary embodiments provide navigation systems configured to be coupled to a motor vehicle turn signal lamp. One navigation system comprises means for receiving a destination from a user and means for generating a route to the destination, the route having a turn. The navigation system also comprises means for activating the turn signal lamp coupled to the generating means, the activating means configured to automatically activate the turn signal lamp when the motor vehicle approaches the turn. </p>
|
| 38 |
+
<p id="p-8" num="8">[0007<confidence value="5">]</confidence>
|
| 39 |
+
Methods for automatically activating a turn signal lamp on a motor vehicle are also provided. One method comprises the step of determining a route to a destination, the route having a turn, and monitoring a present location of the motor vehicle as the motor vehicle navigates the route. The method also comprises the step of automatically activating the turn signal when the motor vehicle approaches the turn. </p>
|
| 40 |
+
<heading id="h-6">DESCRIPTION OF THE DRAWINGS</heading>
|
| 41 |
+
<p id="p-9" num="9">[0008<confidence value="5">]</confidence>
|
| 42 |
+
The present invention will hereinafter be described in conjunction with the following drawing figures, wherein like numerals denote like elements, and <page-break num="3"/>
|
| 43 |
+
<boundary-data type="header">
|
| 44 |
+
<confidence value="8">3</confidence>
|
| 45 |
+
</boundary-data>
|
| 46 |
+
[0009<confidence value="5">]</confidence>
|
| 47 |
+
FIG. 1 is a schematic diagram illustrating a top view of a motor vehicle comprising one exemplary embodiment of a system for automatically activating a turn signal lamp of the motor vehicle; and [0010<confidence value="5">]</confidence>
|
| 48 |
+
FIG. 2 is a flow diagram of one exemplary embodiment of a method for automatically activating a turn signal lamp of the motor vehicle of FIG. 1. </p>
|
| 49 |
+
<heading id="h-7">DESCRIPTION OF AN EXEMPLARY EMBODIMENT</heading>
|
| 50 |
+
<p id="p-10" num="10">[0011<confidence value="5">]</confidence>
|
| 51 |
+
The following detailed description is merely exemplary in nature and is not intended to limit the invention or the application and uses of the invention. Furthermore, there is no intention to be bound by any expressed or implied theory presented in the preceding technical field, background, brief summary or the following detailed description. </p>
|
| 52 |
+
<p id="p-11" num="11">[0012<confidence value="5">]</confidence>
|
| 53 |
+
FIG. 1 is a schematic diagram of a motor vehicle <part-num-ref name="motor vehicle">50</part-num-ref>
|
| 54 |
+
including a system <part-num-ref name="system">100</part-num-ref>
|
| 55 |
+
for automatically activating a turn signal lamp (e.g., turn signal lamps <part-num-ref name="turn signal lamps">102,</part-num-ref>
|
| 56 |
+
<part-num-ref name="turn signal lamps 102,">104,</part-num-ref>
|
| 57 |
+
<part-num-ref name="turn signal lamps 102, 104,">106</part-num-ref>
|
| 58 |
+
and <part-num-ref name="and">108)</part-num-ref>
|
| 59 |
+
of motor vehicle <part-num-ref name="of motor vehicle">50.</part-num-ref>
|
| 60 |
+
System <part-num-ref name="of motor vehicle 50. System">100</part-num-ref>
|
| 61 |
+
comprises a navigation system <part-num-ref name="navigation system">115,</part-num-ref>
|
| 62 |
+
a turn signal indicator <part-num-ref name="turn signal indicator">120,</part-num-ref>
|
| 63 |
+
and a turn signal lamp activator <part-num-ref name="turn signal lamp activator">125</part-num-ref>
|
| 64 |
+
each coupled to one another and to turn signal lamps <part-num-ref name="each coupled to one another and to turn signal lamps">102,</part-num-ref>
|
| 65 |
+
<part-num-ref name="each coupled to one another and to turn signal lamps 102,">104,</part-num-ref>
|
| 66 |
+
<part-num-ref name="each coupled to one another and to turn signal lamps 102, 104,">106</part-num-ref>
|
| 67 |
+
and <part-num-ref name="and">108</part-num-ref>
|
| 68 |
+
via a bus <part-num-ref name="bus">130</part-num-ref>
|
| 69 |
+
(e.g., a wired and/or wireless bus). </p>
|
| 70 |
+
<p id="p-12" num="12">[0013<confidence value="5">]</confidence>
|
| 71 |
+
Navigation system 115 is a turn-by-turn navigation system. That is, navigation system <part-num-ref name="turn-by-turn navigation system. That is, navigation system">115</part-num-ref>
|
| 72 |
+
is configured to receive inputs (e.g., a starting point and a destination, or just a destination) and to determine/calculate a route from the starting point to the destination or from the present location of motor vehicle <part-num-ref name="present location of motor vehicle">50</part-num-ref>
|
| 73 |
+
to the destination. Accordingly, navigation system <part-num-ref name="destination. Accordingly, navigation system">115</part-num-ref>
|
| 74 |
+
may include any firmware, hardware, and/or software capable of generating/calculating a route including one or more turns to a destination by means of, for example, global positioning or other navigation techniques. </p>
|
| 75 |
+
<p id="p-13" num="13">[0014<confidence value="5">]</confidence>
|
| 76 |
+
Navigation system 115 is also configured to track the progress of motor vehicle <part-num-ref name="progress of motor vehicle">50</part-num-ref>
|
| 77 |
+
as it follows a route generated by navigation system <part-num-ref name="route generated by navigation system">115.</part-num-ref>
|
| 78 |
+
In addition, navigation system <part-num-ref name="route generated by navigation system 115. In addition, navigation system">115</part-num-ref>
|
| 79 |
+
is configured to activate (via bus <part-num-ref name="is configured to activate (via bus">130)</part-num-ref>
|
| 80 |
+
turn signal lamps <part-num-ref name="turn signal lamps">102</part-num-ref>
|
| 81 |
+
and <part-num-ref name="and">104</part-num-ref>
|
| 82 |
+
or turn signal lamps <part-num-ref name="or turn signal lamps">106</part-num-ref>
|
| 83 |
+
and <part-num-ref name="and">108</part-num-ref>
|
| 84 |
+
when motor <page-break num="4"/>
|
| 85 |
+
<boundary-data type="header">
|
| 86 |
+
<confidence value="8">4</confidence>
|
| 87 |
+
</boundary-data>
|
| 88 |
+
vehicle <part-num-ref name="when motor vehicle">50</part-num-ref>
|
| 89 |
+
approaches a turn. Specifically, navigation system <part-num-ref name="turn. Specifically, navigation system">115</part-num-ref>
|
| 90 |
+
is configured to activate turn signal lamps <part-num-ref name="is configured to activate turn signal lamps">102</part-num-ref>
|
| 91 |
+
and <part-num-ref name="and">104</part-num-ref>
|
| 92 |
+
each time motor vehicle <part-num-ref name="each time motor vehicle">50</part-num-ref>
|
| 93 |
+
approaches a left turn, and activate turn signal lamps <part-num-ref name="left turn, and activate turn signal lamps">106</part-num-ref>
|
| 94 |
+
and <part-num-ref name="and">108</part-num-ref>
|
| 95 |
+
each time motor vehicle <part-num-ref name="each time motor vehicle">50</part-num-ref>
|
| 96 |
+
approaches a right turn. That is, turn signal lamps <part-num-ref name="right turn. That is, turn signal lamps">102</part-num-ref>
|
| 97 |
+
and <part-num-ref name="and">104</part-num-ref>
|
| 98 |
+
or turn signal lamps <part-num-ref name="or turn signal lamps">106</part-num-ref>
|
| 99 |
+
and <part-num-ref name="and">108</part-num-ref>
|
| 100 |
+
are automatically activated prior to motor vehicle <part-num-ref name="are automatically activated prior to motor vehicle">50</part-num-ref>
|
| 101 |
+
reaching each turn without driver involvement (i.e., turn signal lamps <part-num-ref name="turn signal lamps">102,</part-num-ref>
|
| 102 |
+
<part-num-ref name="turn signal lamps 102,">104,</part-num-ref>
|
| 103 |
+
<part-num-ref name="turn signal lamps 102, 104,">106</part-num-ref>
|
| 104 |
+
and <part-num-ref name="and">108</part-num-ref>
|
| 105 |
+
are automatically activated by navigation system 115). </p>
|
| 106 |
+
<p id="p-14" num="14">[0015<confidence value="5">]</confidence>
|
| 107 |
+
In one exemplary embodiment, navigation system 115 activates turn signal lamps <part-num-ref name="activates turn signal lamps">102</part-num-ref>
|
| 108 |
+
and <part-num-ref name="and">104</part-num-ref>
|
| 109 |
+
or turn signal lamps <part-num-ref name="or turn signal lamps">106</part-num-ref>
|
| 110 |
+
and <part-num-ref name="and">108</part-num-ref>
|
| 111 |
+
when motor vehicle is a predetermined distance from a left or right turn, respectively. The predetermined distance may be any distance that provides adequate notification to other drivers or pedestrians; however, the predetermined distance should not be less than and/or greater than any minimum and/or maximum distances prescribed by the law of the jurisdiction where motor vehicle <part-num-ref name="jurisdiction where motor vehicle">50</part-num-ref>
|
| 112 |
+
is operating. </p>
|
| 113 |
+
<p id="p-15" num="15">[0016<confidence value="5">]</confidence>
|
| 114 |
+
In another exemplary embodiment, navigation system 115 activates turn signal lamps <part-num-ref name="activates turn signal lamps">102</part-num-ref>
|
| 115 |
+
and <part-num-ref name="and">104</part-num-ref>
|
| 116 |
+
or turn signal lamps <part-num-ref name="or turn signal lamps">106</part-num-ref>
|
| 117 |
+
and <part-num-ref name="and">108</part-num-ref>
|
| 118 |
+
when motor vehicle is an estimated predetermined time from a turn. Specifically, navigation system <part-num-ref name="turn. Specifically, navigation system">115</part-num-ref>
|
| 119 |
+
is configured to calculate the distance between the present location of motor vehicle <part-num-ref name="present location of motor vehicle">50</part-num-ref>
|
| 120 |
+
and a turn then divide this distance by the present rate of speed of motor vehicle <part-num-ref name="present rate of speed of motor vehicle">50</part-num-ref>
|
| 121 |
+
to calculate an estimate of the time it will take motor vehicle <part-num-ref name="time it will take motor vehicle">50</part-num-ref>
|
| 122 |
+
to reach the turn. The estimated time may include an additional amount of time to account for vehicle braking time prior to reaching the turn. The additional time may be variable depending on the present speed of motor vehicle <part-num-ref name="present speed of motor vehicle">50</part-num-ref>
|
| 123 |
+
at the time of calculation or may be a predetermined amount of time (e.g., in the range of about <part-num-ref name="range of about">10</part-num-ref>
|
| 124 |
+
seconds to about <part-num-ref name="seconds to about">30</part-num-ref>
|
| 125 |
+
seconds). The estimated predetermined time is sufficient to provide adequate notification to other drivers or pedestrians. In either situation the predetermined distance and/or time should comply with the law of the jurisdiction where motor vehicle <part-num-ref name="jurisdiction where motor vehicle">50</part-num-ref>
|
| 126 |
+
is operating. </p>
|
| 127 |
+
<boundary-data type="header">
|
| 128 |
+
<confidence value="8">5</confidence>
|
| 129 |
+
</boundary-data>
|
| 130 |
+
<p id="p-16" num="16">
|
| 131 |
+
<page-break num="5"/>
|
| 132 |
+
[0017<confidence value="5">]</confidence>
|
| 133 |
+
In one embodiment, navigation system is configured to de-activate turn signal lamps 102 and <part-num-ref name="and">104</part-num-ref>
|
| 134 |
+
or turn signal lamps <part-num-ref name="or turn signal lamps">106</part-num-ref>
|
| 135 |
+
and <part-num-ref name="and">108</part-num-ref>
|
| 136 |
+
if motor vehicle <part-num-ref name="if motor vehicle">50</part-num-ref>
|
| 137 |
+
fails to engage a turn on the route. That is, if the driver misses a turn, navigation system <part-num-ref name="turn, navigation system">115</part-num-ref>
|
| 138 |
+
automatically turns OFF turn signal lamps <part-num-ref name="automatically turns OFF turn signal lamps">102</part-num-ref>
|
| 139 |
+
and <part-num-ref name="and">104</part-num-ref>
|
| 140 |
+
or turn signal lamps <part-num-ref name="or turn signal lamps">106</part-num-ref>
|
| 141 |
+
and <part-num-ref name="and">108,</part-num-ref>
|
| 142 |
+
as the case may be, at a predetermined distance (or time) after it is determined that motor vehicle <part-num-ref name="predetermined distance (or time) after it is determined that motor vehicle">50</part-num-ref>
|
| 143 |
+
has failed to engage the turn. Moreover, navigation system <part-num-ref name="turn. Moreover, navigation system">115</part-num-ref>
|
| 144 |
+
is configured to continue to activate turn signal lamps <part-num-ref name="is configured to continue to activate turn signal lamps">102</part-num-ref>
|
| 145 |
+
and <part-num-ref name="and">104</part-num-ref>
|
| 146 |
+
or turn signal lamps <part-num-ref name="or turn signal lamps">106</part-num-ref>
|
| 147 |
+
and <part-num-ref name="and">108</part-num-ref>
|
| 148 |
+
when motor vehicle returns to the calculated route after one or more turns have been missed. </p>
|
| 149 |
+
<p id="p-17" num="17">[0018<confidence value="5">]</confidence>
|
| 150 |
+
Navigation system 115 is also configured to activate turn signal indicator <part-num-ref name="is also configured to activate turn signal indicator">120</part-num-ref>
|
| 151 |
+
each time navigation system <part-num-ref name="each time navigation system">115</part-num-ref>
|
| 152 |
+
activates turn signal lamps <part-num-ref name="activates turn signal lamps">102</part-num-ref>
|
| 153 |
+
and <part-num-ref name="and">104</part-num-ref>
|
| 154 |
+
or turn signal lamps <part-num-ref name="or turn signal lamps">106</part-num-ref>
|
| 155 |
+
and <part-num-ref name="and">108.</part-num-ref>
|
| 156 |
+
Turn signal indicator <part-num-ref name="and 108. Turn signal indicator">120</part-num-ref>
|
| 157 |
+
may be any device, hardware, and/or software capable or providing visual and/or audible cues indicating a left turn or a right turn to a driver of motor vehicle <part-num-ref name="driver of motor vehicle">50.</part-num-ref>
|
| 158 |
+
</p>
|
| 159 |
+
<p id="p-18" num="18">[0019<confidence value="5">]</confidence>
|
| 160 |
+
Turn signal indicator 120 may be integrated on the instrument panel of motor vehicle 50; however, turn signal indicator <part-num-ref name="instrument panel of motor vehicle 50; however, turn signal indicator">120</part-num-ref>
|
| 161 |
+
may be located at other locations <confidence value="22222">on/in</confidence>
|
| 162 |
+
motor vehicle <part-num-ref name="may be located at other locations on/in motor vehicle">50</part-num-ref>
|
| 163 |
+
detectable by the driver to alert the driver that a turn is coming in the near future. Furthermore, in conventional motor vehicles, turn signal indicator <part-num-ref name="near future. Furthermore, in conventional motor vehicles, turn signal indicator">120</part-num-ref>
|
| 164 |
+
typically provides a flashing green arrow pointing to the left indicating activation of turn signal lamps <part-num-ref name="left indicating activation of turn signal lamps">102</part-num-ref>
|
| 165 |
+
and <part-num-ref name="and">104</part-num-ref>
|
| 166 |
+
and a flashing green arrow pointing to the right indicating activation of turn signal lamps <part-num-ref name="right indicating activation of turn signal lamps">106</part-num-ref>
|
| 167 |
+
and <part-num-ref name="and">108.</part-num-ref>
|
| 168 |
+
Moreover, turn signal indicator <part-num-ref name="and 108. Moreover, turn signal indicator">120</part-num-ref>
|
| 169 |
+
also provides an intermittent "clicking" sound coordinated with each flash of the respective arrows. Various embodiments of the present invention contemplate the use of turn signal indicator <part-num-ref name="use of turn signal indicator">120</part-num-ref>
|
| 170 |
+
discussed above when navigation system <part-num-ref name="discussed above when navigation system">115</part-num-ref>
|
| 171 |
+
activates turn signal lamps <part-num-ref name="activates turn signal lamps">102</part-num-ref>
|
| 172 |
+
and <part-num-ref name="and">104</part-num-ref>
|
| 173 |
+
or turn signal lamps <part-num-ref name="or turn signal lamps">106</part-num-ref>
|
| 174 |
+
and <part-num-ref name="and">108.</part-num-ref>
|
| 175 |
+
</p>
|
| 176 |
+
<p id="p-19" num="19">[0020<confidence value="5">]</confidence>
|
| 177 |
+
In accordance with one exemplary embodiment, turn signal indicator 120 is configured to provide a first type of indication when navigation system <part-num-ref name="first type of indication when navigation system">115</part-num-ref>
|
| 178 |
+
activates turn signal lamps <part-num-ref name="activates turn signal lamps">102</part-num-ref>
|
| 179 |
+
and <part-num-ref name="and">104</part-num-ref>
|
| 180 |
+
or turn signal <page-break num="6"/>
|
| 181 |
+
<boundary-data type="header">
|
| 182 |
+
<confidence value="8">6</confidence>
|
| 183 |
+
</boundary-data>
|
| 184 |
+
lamps <part-num-ref name="or turn signal lamps">106</part-num-ref>
|
| 185 |
+
and <part-num-ref name="and">108,</part-num-ref>
|
| 186 |
+
and a second type of indication when the driver activates turn signal lamps <part-num-ref name="driver activates turn signal lamps">102</part-num-ref>
|
| 187 |
+
and <part-num-ref name="and">104</part-num-ref>
|
| 188 |
+
or turn signal lamps <part-num-ref name="or turn signal lamps">106</part-num-ref>
|
| 189 |
+
and <part-num-ref name="and">108.</part-num-ref>
|
| 190 |
+
That is, turn signal indicator <part-num-ref name="and 108. That is, turn signal indicator">120</part-num-ref>
|
| 191 |
+
is configured to provide different visual cues and/or different audible cues when turn signal lamps <part-num-ref name="is configured to provide different visual cues and/or different audible cues when turn signal lamps">102</part-num-ref>
|
| 192 |
+
and <part-num-ref name="and">104</part-num-ref>
|
| 193 |
+
or turn signal lamps <part-num-ref name="or turn signal lamps">106</part-num-ref>
|
| 194 |
+
and <part-num-ref name="and">108</part-num-ref>
|
| 195 |
+
have been automatically or manually activated; i.e., turn signal indicators may include different colors, flash rates, sizes, brightness, and the like for the arrows or may comprises indicators of different shapes when turn signal lamps <part-num-ref name="arrows or may comprises indicators of different shapes when turn signal lamps">102</part-num-ref>
|
| 196 |
+
and <part-num-ref name="and">104</part-num-ref>
|
| 197 |
+
or turn signal lamps <part-num-ref name="or turn signal lamps">106</part-num-ref>
|
| 198 |
+
and <part-num-ref name="and">108</part-num-ref>
|
| 199 |
+
are activated by navigation system <part-num-ref name="are activated by navigation system">115</part-num-ref>
|
| 200 |
+
as opposed to being the result of manual activation. Likewise, turn signal indicators may include different sounds, sound rates, magnitudes, and the like when turn signal lamps <part-num-ref name="like when turn signal lamps">102</part-num-ref>
|
| 201 |
+
and <part-num-ref name="and">104</part-num-ref>
|
| 202 |
+
or turn signal lamps <part-num-ref name="or turn signal lamps">106</part-num-ref>
|
| 203 |
+
and <part-num-ref name="and">108</part-num-ref>
|
| 204 |
+
are activated by navigation system <part-num-ref name="are activated by navigation system">115</part-num-ref>
|
| 205 |
+
as opposed to manually activated. </p>
|
| 206 |
+
<p id="p-20" num="20">[0021<confidence value="5">]</confidence>
|
| 207 |
+
For example, turn signal indicator 120 may provide the known visual and audible cues associated with the arrows in contemporary motor vehicles when turn signal lamps <part-num-ref name="arrows in contemporary motor vehicles when turn signal lamps">102</part-num-ref>
|
| 208 |
+
and <part-num-ref name="and">104</part-num-ref>
|
| 209 |
+
or turn signal lamps <part-num-ref name="or turn signal lamps">106</part-num-ref>
|
| 210 |
+
and <part-num-ref name="and">108</part-num-ref>
|
| 211 |
+
are manually activated, but may provide red arrows with a faster or slower flash rate and a louder or quieter "clicking" sound when turn signal lamps <part-num-ref name="louder or quieter "clicking" sound when turn signal lamps">102</part-num-ref>
|
| 212 |
+
and <part-num-ref name="and">104</part-num-ref>
|
| 213 |
+
or turn signal lamps <part-num-ref name="or turn signal lamps">106</part-num-ref>
|
| 214 |
+
and <part-num-ref name="and">108</part-num-ref>
|
| 215 |
+
are activated by navigation system <part-num-ref name="are activated by navigation system">115.</part-num-ref>
|
| 216 |
+
Various embodiments contemplate the numerous combinations of different visual and/or audible cues even though each is not specifically mentioned. </p>
|
| 217 |
+
<p id="p-21" num="21">[0022<confidence value="5">]</confidence>
|
| 218 |
+
Turn signal lamp activator 125 may be any device, hardware, and/or software capable of activating turn signal lamps <part-num-ref name="may be any device, hardware, and/or software capable of activating turn signal lamps">102</part-num-ref>
|
| 219 |
+
and <part-num-ref name="and">104</part-num-ref>
|
| 220 |
+
or turn signal lamps <part-num-ref name="or turn signal lamps">106</part-num-ref>
|
| 221 |
+
and <part-num-ref name="and">108.</part-num-ref>
|
| 222 |
+
Typically, turn signal lamp activator <part-num-ref name="and 108. Typically, turn signal lamp activator">125</part-num-ref>
|
| 223 |
+
is a lever protruding laterally from the steering column that activates turn signal lamps <part-num-ref name="steering column that activates turn signal lamps">102</part-num-ref>
|
| 224 |
+
and <part-num-ref name="and">104</part-num-ref>
|
| 225 |
+
when pushed down and activates turn signal lamps <part-num-ref name="when pushed down and activates turn signal lamps">106</part-num-ref>
|
| 226 |
+
and <part-num-ref name="and">108</part-num-ref>
|
| 227 |
+
when pushed up. </p>
|
| 228 |
+
<p id="p-22" num="22">[0023<confidence value="5">]</confidence>
|
| 229 |
+
In one embodiment, turn signal lamp activator 125 is not activated (i.e., not pushed up or down) when navigation system <part-num-ref name="not pushed up or down) when navigation system">115</part-num-ref>
|
| 230 |
+
has activated turn signal lamps <part-num-ref name="has activated turn signal lamps">102</part-num-ref>
|
| 231 |
+
and <part-num-ref name="and">104</part-num-ref>
|
| 232 |
+
or turn signal lamps <part-num-ref name="or turn signal lamps">106</part-num-ref>
|
| 233 |
+
and <part-num-ref name="and">108.</part-num-ref>
|
| 234 |
+
In this <page-break num="7"/>
|
| 235 |
+
<boundary-data type="header">
|
| 236 |
+
<confidence value="8">7</confidence>
|
| 237 |
+
</boundary-data>
|
| 238 |
+
embodiment, turn signal lamp activator comprises a button, switch, knob, or the like for manually de-activating turn signal lamps <part-num-ref name="like for manually de-activating turn signal lamps">102</part-num-ref>
|
| 239 |
+
and <part-num-ref name="and">104</part-num-ref>
|
| 240 |
+
or turn signal lamps <part-num-ref name="or turn signal lamps">106</part-num-ref>
|
| 241 |
+
and <part-num-ref name="and">108</part-num-ref>
|
| 242 |
+
when they have been activated by navigation system <part-num-ref name="when they have been activated by navigation system">115.</part-num-ref>
|
| 243 |
+
In another embodiment, turn signal lamp activator <part-num-ref name="when they have been activated by navigation system 115. In another embodiment, turn signal lamp activator">125</part-num-ref>
|
| 244 |
+
is activated (i.e., pushed up or down) by navigation system <part-num-ref name="pushed up or down) by navigation system">115</part-num-ref>
|
| 245 |
+
when navigation system <part-num-ref name="when navigation system">115</part-num-ref>
|
| 246 |
+
activates turn signal lamps <part-num-ref name="activates turn signal lamps">102</part-num-ref>
|
| 247 |
+
and <part-num-ref name="and">104</part-num-ref>
|
| 248 |
+
or turn signal lamps <part-num-ref name="or turn signal lamps">106</part-num-ref>
|
| 249 |
+
and <part-num-ref name="and">108.</part-num-ref>
|
| 250 |
+
In this embodiment, the driver may manually turn OFF turn signal lamps <part-num-ref name="driver may manually turn OFF turn signal lamps">102</part-num-ref>
|
| 251 |
+
and <part-num-ref name="and">104</part-num-ref>
|
| 252 |
+
or turn signal lamps <part-num-ref name="or turn signal lamps">106</part-num-ref>
|
| 253 |
+
and <part-num-ref name="and">108</part-num-ref>
|
| 254 |
+
by returning turn signal lamp activator <part-num-ref name="by returning turn signal lamp activator">125</part-num-ref>
|
| 255 |
+
to the neutral or OFF position. </p>
|
| 256 |
+
<p id="p-23" num="23">[0024<confidence value="5">]</confidence>
|
| 257 |
+
Furthermore, if the driver manually activates turn signal lamps <part-num-ref name="driver manually activates turn signal lamps">102</part-num-ref>
|
| 258 |
+
and <part-num-ref name="and">104</part-num-ref>
|
| 259 |
+
or turn signal lamps <part-num-ref name="or turn signal lamps">106</part-num-ref>
|
| 260 |
+
and <part-num-ref name="and">108</part-num-ref>
|
| 261 |
+
(e.g., via turn signal lamp activator <part-num-ref name="via turn signal lamp activator">125)</part-num-ref>
|
| 262 |
+
prior to navigation system <part-num-ref name="prior to navigation system">115</part-num-ref>
|
| 263 |
+
activating turn signal lamps <part-num-ref name="activating turn signal lamps">102</part-num-ref>
|
| 264 |
+
and <part-num-ref name="and">104</part-num-ref>
|
| 265 |
+
or turn signal lamps <part-num-ref name="or turn signal lamps">106</part-num-ref>
|
| 266 |
+
and <part-num-ref name="and">108,</part-num-ref>
|
| 267 |
+
the automatic activation of turn signal lamps <part-num-ref name="automatic activation of turn signal lamps">102,</part-num-ref>
|
| 268 |
+
<part-num-ref name="automatic activation of turn signal lamps 102,">104,</part-num-ref>
|
| 269 |
+
<part-num-ref name="automatic activation of turn signal lamps 102, 104,">106,</part-num-ref>
|
| 270 |
+
and <part-num-ref name="automatic activation of turn signal lamps 102, 104, 106, and">108</part-num-ref>
|
| 271 |
+
is bypassed. That is, manual activation of turn signal lamps <part-num-ref name="is bypassed. That is, manual activation of turn signal lamps">102</part-num-ref>
|
| 272 |
+
and <part-num-ref name="and">104</part-num-ref>
|
| 273 |
+
or turn signal lamps <part-num-ref name="or turn signal lamps">106</part-num-ref>
|
| 274 |
+
and <part-num-ref name="and">108</part-num-ref>
|
| 275 |
+
overrides automatic activation of turn signal lamps <part-num-ref name="overrides automatic activation of turn signal lamps">102</part-num-ref>
|
| 276 |
+
and <part-num-ref name="and">104</part-num-ref>
|
| 277 |
+
or turn signal lamps <part-num-ref name="or turn signal lamps">106</part-num-ref>
|
| 278 |
+
and <part-num-ref name="and">108</part-num-ref>
|
| 279 |
+
by navigation system <part-num-ref name="by navigation system">115.</part-num-ref>
|
| 280 |
+
</p>
|
| 281 |
+
<p id="p-24" num="24">[0025<confidence value="5">]</confidence>
|
| 282 |
+
FIG. 2 is a flow diagram of one exemplary embodiment of a method <part-num-ref name="method">200</part-num-ref>
|
| 283 |
+
for automatically activating a turn signal lamp (e.g., turn signal lamps <part-num-ref name="turn signal lamps">102</part-num-ref>
|
| 284 |
+
and <part-num-ref name="and">104</part-num-ref>
|
| 285 |
+
or turn signal lamps <part-num-ref name="or turn signal lamps">106</part-num-ref>
|
| 286 |
+
and <part-num-ref name="and">108</part-num-ref>
|
| 287 |
+
of FIG.<confidence value="5">1</confidence>
|
| 288 |
+
) on a motor vehicle (e.g., motor vehicle <part-num-ref name="motor vehicle">50</part-num-ref>
|
| 289 |
+
of FIG. 1). Method <part-num-ref name="of FIG. 1). Method">200</part-num-ref>
|
| 290 |
+
begins when a navigation system (e.g., navigation system <part-num-ref name="navigation system">115</part-num-ref>
|
| 291 |
+
of FIG. 1) receives an input from a user (step 210). Appropriate inputs include a starting point and a destination or just a destination. </p>
|
| 292 |
+
<p id="p-25" num="25">[0026<confidence value="5">]</confidence>
|
| 293 |
+
After the input has been received, a route (including at least one turn) from the starting point to the destination or from the present location of motor vehicle <part-num-ref name="present location of motor vehicle">50</part-num-ref>
|
| 294 |
+
to the destination is determined/calculated (step 220). The route is then visually and/or audibly transmitted to the user (step 230). The progress of motor vehicle <part-num-ref name="progress of motor vehicle">50</part-num-ref>
|
| 295 |
+
is monitored as the driver follows the route (step 240). </p>
|
| 296 |
+
<boundary-data type="header">
|
| 297 |
+
<confidence value="8">8</confidence>
|
| 298 |
+
</boundary-data>
|
| 299 |
+
<p id="p-26" num="26">
|
| 300 |
+
<page-break num="8"/>
|
| 301 |
+
[0027<confidence value="5">]</confidence>
|
| 302 |
+
When motor vehicle 50 approaches a turn along the route, turn signal lamps <part-num-ref name="route, turn signal lamps">102</part-num-ref>
|
| 303 |
+
and <part-num-ref name="and">104</part-num-ref>
|
| 304 |
+
or turn signal lamps <part-num-ref name="or turn signal lamps">106</part-num-ref>
|
| 305 |
+
and <part-num-ref name="and">108</part-num-ref>
|
| 306 |
+
are automatically activated prior to motor vehicle <part-num-ref name="are automatically activated prior to motor vehicle">50</part-num-ref>
|
| 307 |
+
reaching the actual turn (step 250). Turn signal lamps <part-num-ref name="actual turn (step 250). Turn signal lamps">102</part-num-ref>
|
| 308 |
+
and <part-num-ref name="and">104</part-num-ref>
|
| 309 |
+
or turn signal lamps <part-num-ref name="or turn signal lamps">106</part-num-ref>
|
| 310 |
+
and <part-num-ref name="and">108</part-num-ref>
|
| 311 |
+
may be activated a predetermined distance and/or an estimated predetermined amount of time prior to motor vehicle <part-num-ref name="estimated predetermined amount of time prior to motor vehicle">50</part-num-ref>
|
| 312 |
+
actually reaching the turn, as explained above with reference to FIG. 1. </p>
|
| 313 |
+
<p id="p-27" num="27">[0028<confidence value="5">]</confidence>
|
| 314 |
+
After motor vehicle 50 navigates the turn, turn signal lamps <part-num-ref name="turn, turn signal lamps">102</part-num-ref>
|
| 315 |
+
and <part-num-ref name="and">104</part-num-ref>
|
| 316 |
+
or turn signal lamps <part-num-ref name="or turn signal lamps">106</part-num-ref>
|
| 317 |
+
and <part-num-ref name="and">108</part-num-ref>
|
| 318 |
+
are de-activated (step 260). In one embodiment, de-activation occurs automatically by navigation system <part-num-ref name="are de-activated (step 260). In one embodiment, de-activation occurs automatically by navigation system">115</part-num-ref>
|
| 319 |
+
or the motion of the steering wheel of motor vehicle <part-num-ref name="steering wheel of motor vehicle">50</part-num-ref>
|
| 320 |
+
returning to the neutral position, or manually by the driver when the turn is completed. In another embodiment, de-activation occurs automatically when the driver misses a turn. </p>
|
| 321 |
+
<p id="p-28" num="28">In this embodiment, turn signal lamps 102 and <part-num-ref name="and">104</part-num-ref>
|
| 322 |
+
or turn signal lamps <part-num-ref name="or turn signal lamps">106</part-num-ref>
|
| 323 |
+
and <part-num-ref name="and">108</part-num-ref>
|
| 324 |
+
are de-activated a predetermined distance and/or time after the driver has missed the turn. </p>
|
| 325 |
+
<p id="p-29" num="29">[0029<confidence value="5">]</confidence>
|
| 326 |
+
Method 200 then returns to step <part-num-ref name="then returns to step">240</part-num-ref>
|
| 327 |
+
to continue to monitor the progress of motor vehicle <part-num-ref name="progress of motor vehicle">50</part-num-ref>
|
| 328 |
+
(step 270). Steps 240-270 are then repeated as needed until the destination is reached. </p>
|
| 329 |
+
<p id="p-30" num="30">[0030<confidence value="5">]</confidence>
|
| 330 |
+
While at least one exemplary embodiment has been presented in the foregoing detailed description, it should be appreciated that a vast number of variations exist. It should also be appreciated that the exemplary embodiment or exemplary embodiments are only examples, and are not intended to limit the scope, applicability, or configuration of the invention in any way. Rather, the foregoing detailed description will provide those skilled in the art with a convenient road map for implementing the exemplary embodiment or exemplary embodiments. It should be understood that various changes can be made in the function and arrangement of elements without departing from the scope of the invention as set forth in the appended claims and the legal equivalents thereof. </p>
|
| 331 |
+
</description>
|
| 332 |
+
</us-patent-application>
|
| 333 |
+
|