Methods, systems, and products for subcontracting segments in communications services
Summary by NHIP
Subcontracted Data Segmentation
The method receives a subscriber data stream at a server and recursively segments it based on observed packet structure similarities. It groups segments requiring external processing from other subscribers, then transmits these grouped segments to a different service provider for subcontracted handling before aggregating the results back into the stream.
Claim Score by NHIP
Abstract
Methods, systems, and products are disclosed for providing communications services. One method receives a first data stream at a computer, with the first data stream comprising packets of data packetized according to a packet protocol. The first data stream is recursively segmented into segments, and at least one of the segments is dispersed via a network for a subsequent processing service. A result of the processing service is received, and the result is aggregated into a second data stream. The second data stream is then communicated via the network.

Term
Term ended
Expired 9 June 2024, 2.3 years ago.
- Priority
- Filed
- Granted
- Expired
- Today
18 claims: 3 independent, 15 dependent
- 1Broadest claimClaim Score 47, average(NHIP)A method, comprising:receiving, from a communications network, a data stream at a server of a network service provider, the data stream associated with a subscriber;observing a current sequence of data packets in the data stream has a similar structure to a previous sequence of data packets;recursively segmenting the data stream into segments, such that a characteristic of the previous sequence of data packets in the data stream determines how the current sequence of data packets is segmented;determining one of the segments requires a subcontracted processing service provided by a different service provider;grouping together the one of the segments with other segments from other subscribers that also require the subcontracted processing service provided by the different service provider;subcontracting grouped together segments from the server over the communications network to the different service provider to receive the subcontracted processing service;receiving, at the server, a result of the subcontracted processing service;and aggregating the result of the subcontracted processing service into the data stream.
- 15A system, comprising:a processor;and memory storing code that when executed causes the processor to perform operations, the operations comprising: receiving, from a communications network, data streams from multiple subscribers requesting services from a service provider;observing a current sequence of data packets in one of the data streams has a similar structure to a previous sequence of data packets in another one of the data streams;recursively segmenting each of the data streams into segments, such that a characteristic of the previous sequence of data packets in the another one of the data streams determines how the current sequence of data packets is segmented;determining some of the segments require a subcontracted processing service provided by a different service provider;grouping together the some of the segments from the multiple subscribers that require the subcontracted processing service;subcontracting grouped-together segments over the communications network to the different service provider of another communications network to receive the subcontracted processing service;receiving a result of the subcontracted processing service;and aggregating the result of the subcontracted processing service into a subscriber data stream for each subscriber of the multiple subscribers.
- 17A computer readable memory storing computer-readable instructions that when executed by a processor cause the processor to perform operations, the operations comprising:receiving data streams from multiple subscribers requesting services from a service provider of a communications network;observing a current sequence of data packets in one of the data streams has a similar structure to a previous sequence of data packets in another one of the data streams;recursively segmenting each of the data streams into segments, such that a characteristic of the previous sequence of data packets in the another one of the data streams determines how the current sequence of data packets is segmented;determining some of the segments require a subcontracted processing service provided by a different service provider;grouping together the some of the segments as a new segment that requires the subcontracted processing service;subcontracting the new segment over a communications network to the different service provider of another communications network to receive the subcontracted processing service;receiving a result of the subcontracted processing service;and aggregating the result of the subcontracted processing service into a subscriber data stream for each subscriber of the multiple subscribers.
Independent claims3
47 paragraphs in 6 sections, as filed
CROSS-REFERENCE TO RELATED APPLICATIONS
0001This application is a continuation of U.S. application Ser. No. 10/720,949, filed Nov. 24, 2003, now issued as U.S. Pat. No. 7,467,219, and incorporated herein by reference in its entirety.
NOTICE OF COPYRIGHT PROTECTION
0002A portion of the disclosure of this patent document and its figures contain material subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, but otherwise reserves all copyrights whatsoever.
BACKGROUND OF THE INVENTION
00031. Field of the Invention
0004This invention generally relates to computers and to communications and, more particularly, to processing data in a communications network.
00052. Description of the Related Art
0006Manipulation of electronic data is important in computer networking and in communications. Often times electronic data must be manipulated for presentation at a client communications device. That is, the electronic data must be changed, formatted, or altered to suit the display characteristics, processing abilities, and/or storage capabilities of the client communications device. A handheld personal data assistant, for example, often requires that bandwidth-intensive electronic data, such as on-demand video, be scaled, color corrected, and/or otherwise manipulated for optimum presentation on the small display of the handheld personal data assistant. Heretofore, however, manipulation of electronic data was usually the responsibility of the client communications device—that is, the client communications device stores and utilizes one or more computer programs to manipulate incoming electronic data for presentation on the client communications device.
0007Locally manipulating electronic data, however, poses problems. As the electronic data is received, the client communications device must store the electronic data, process/manipulate the electronic data, and present the manipulated electronic data to the user. This process of storing, manipulating, and/or presenting the electronic data, however, often taxes the limited processing and storage capabilities of the client communications device. As both those skilled and unskilled recognize, when the processing and/or storage capabilities of the client communications device are overwhelmed, the audio/video presentation may “stumble” and degrade the user experience. Sometimes the client communications device even experiences a fault or failure when the processing and/or storage capabilities are overwhelmed. There is, accordingly, a need in the art for methods and systems of manipulating electronic data that reduce the need for locally-stored computer programs and that reduce the need for local processing requirements.
BRIEF SUMMARY OF THE INVENTION
0008The aforementioned problems, and other problems, are reduced by a Analysis Module. This Analysis Module comprises methods, computer systems, computer programs, and computer program products that provide communications services to subscribers. The Analysis Module recursively segments a stream of electronic data. The term “recursively segments” means the Analysis Module uses a characteristic of one segment to determine the segmentation of another segment. That is, when the Analysis Module segments the stream of electronic data, the segmentation of at least one segment is at least in part based upon a characteristic of a preceding segment. As this patent will further describe, these characteristics may include mathematical characteristics, content characteristics, timing characteristics, structural characteristics, processing characteristics, and routing characteristics.
0009Once a segment is created, that segment may be processed. Each individual segment, if required, is routed to one or more devices and/or other software transformation modules, within and without the communications network, for subsequent processing. When the subsequent processing is complete, the Analysis Module aggregates the result of the subsequent processing. The Analysis Module may then assemble that result into another data structure, and/or the Analysis Module may communicate the aggregated result along the communications network. The Analysis Module, for example, may assemble segments and results into a new, formatted data stream, and then communicate that formatted data stream to a client communications device. The client communications device may then view/execute/present the formatted data stream with little or no regard for the original format of the electronic data. That is, the aggregated results have already been substantially formatted, transformed, processed, and/or manipulated to suit the processing, storage, and/or audio/display requirements of the client communications device.
0010Because this invention utilizes recursive segmentation, this invention is particularly useful for structured streams of data. The technique of recursive segmentation, as described herein, lends itself to fast and efficient data compression, data description, and data prediction. As data content formats become more structured, this invention allows automated segmentation, automated processing, and automated assembly of streams of data. The Analysis Module of this invention creates and assembles formatted data streams for a client communications device. The client communications device may then view/execute/present the formatted data stream with little or no regard for the original format of the requested electronic data. The formatted, data stream has already been substantially formatted, transformed, processed, and/or manipulated to suit the processing, storage, and/or audio/display requirements of the client communications device.
0011This invention discloses methods, systems, and products for providing communications services. One of the embodiments describes a method for providing communications services. A first data stream is received at a computer, with the first data stream comprising packets of data packetized according to a packet protocol. The first data stream is recursively segmented into segments, and at least one of the segments is dispersed via a network for a subsequent processing service. A result of the processing service is received, and the result is aggregated into a second data stream. The second data stream is then communicated via the network.
0012Another of the embodiments describes another method for providing communications services. Here data is received at a computer, and the data is received as packets of data packetized according to a packet protocol. The packets of data are recursively segmenting into segments according to a segmentation profile stored in memory. At least one of the segments is dispersing via a network for a subsequent processing service. Results of the subsequent processing service are received and assembled into a data stream. The data stream includes at least one of i) the results of the subsequent processing service and ii) a recursively segmented segment. The assembled data stream may then be communicated via the network to another computer device and/or to a client communications device.
0013Other embodiments of this invention describe a system for providing communications services. An Analysis Module is stored in a memory device, and a processor communicates with the memory device. The Analysis Module receives data at a computer, with the data received as packets of data packetized according to a packet protocol. The Analysis Module recursively segments the packets of data into segments according to a segmentation profile stored in memory. The Analysis Module disperses at least one of the segments via a network for a subsequent processing service. The Analysis Module receives results of the subsequent processing service and assembles a data stream, with the data stream comprising at least one of i) the results of the subsequent processing service and ii) a recursively segmented segment.
0014Other embodiments of this invention describe a computer program product. A computer-readable medium stores an Analysis Module. The Analysis Module receives data at a computer, and the data is received as packets of data packetized according to a packet protocol. The Analysis Module recursively segments the packets of data into segments according to a segmentation profile stored in memory. The Analysis Module disperses at least one of the segments via a network for a subsequent processing service. The Analysis Module receives results of the subsequent processing service and assembles a data stream, with the data stream comprising at least one of i) the results of the subsequent processing service and ii) a recursively segmented segment.
0015Other systems, methods, and/or computer program products according to embodiments will be or become apparent to one with skill in the art upon review of the following drawings and detailed description. It is intended that all such additional systems, methods, and/or computer program products be included within this description, be within the scope of the present invention, and be protected by the accompanying claims.
BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS
These and other features, aspects, and advantages of the embodiments of the present invention are better understood when the following Detailed Description of the Invention is read with reference to the accompanying drawings, wherein:
<figref idref="DRAWINGS">FIGS. 1 and 2</figref> are simplified schematics illustrating one or more embodiments of this invention;
<figref idref="DRAWINGS">FIG. 3</figref> is a schematic illustrating a segmentation profile according to another of the embodiments of this invention;
<figref idref="DRAWINGS">FIG. 4</figref> is a schematic illustrating the assemblage of segments and/or processing results according to more embodiments of this invention;
<figref idref="DRAWINGS">FIGS. 5 and 6</figref> are schematics illustrating a segment containing historical routing information and historical processing information according to still more embodiments of this invention;
<figref idref="DRAWINGS">FIG. 7</figref> is a flowchart illustrating a method of providing communications services according to the embodiments of this invention; and
<figref idref="DRAWINGS">FIGS. 8 and 9</figref> are flowcharts illustrating another method of providing communications services according to the embodiments of this invention.
DETAILED DESCRIPTION OF THE INVENTION
0023This invention now will be described more fully hereinafter with reference to the accompanying drawings, in which exemplary embodiments are shown. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. These embodiments are provided so that this disclosure will be thorough and complete and will fully convey the scope of the invention to those of ordinary skill in the art. Moreover, all statements herein reciting embodiments of the invention, as well as specific examples thereof, are intended to encompass both structural and functional equivalents thereof. Additionally, it is intended that such equivalents include both currently known equivalents as well as equivalents developed in the future (i.e., any elements developed that perform the same function, regardless of structure).
0024Thus, for example, it will be appreciated by those of ordinary skill in the art that the diagrams, schematics, illustrations, and the like represent conceptual views or processes illustrating systems and methods embodying this invention. The functions of the various elements shown in the figures may be provided through the use of dedicated hardware as well as hardware capable of executing associated software. Similarly, any switches shown in the figures are conceptual only. Their function may be carried out through the operation of program logic, through dedicated logic, through the interaction of program control and dedicated logic, or even manually, the particular technique being selectable by the entity implementing this invention. Those of ordinary skill in the art further understand that the exemplary hardware, software, processes, methods, and/or operating systems described herein are for illustrative purposes and, thus, are not intended to be limited to any particular named manufacturer.
0025<figref idref="DRAWINGS">FIGS. 1 and 2</figref> are simplified schematics illustrating this invention. The embodiments of this invention include an Analysis Module <b>20</b>. The Analysis Module <b>20</b> comprises methods, systems, computer programs, and/or computer program products that help provide communications services. The Analysis Module <b>20</b> operates within a computer <b>10</b>. The computer <b>10</b> receives a first stream <b>12</b> of data via a network <b>14</b>. The first stream <b>12</b> of data typically includes individual packets <b>16</b> of information. The first stream <b>12</b> of data may have an XML (eXtensible Mark-up Language) format or a non-XML format. As <figref idref="DRAWINGS">FIG. 1</figref> shows, the Analysis Module <b>20</b> acts upon the first stream <b>12</b> of data by segmenting the individual packets <b>16</b> into segments <b>18</b>. The individual packets <b>16</b> may be segmented according to a similar characteristic and/or according to similar processing services. Some examples of these similar characteristics and/or similar processing services could include scaling requirements, color requirements, and network routing requirements. Some individual packets, for example, might require a scaling correction factor to achieve a “quality of presentation” objective at a smaller/larger display size. Those packets <b>16</b> that require this scaling correction factor are grouped into a segment. Some individual packets might require color correction to achieve that “quality of presentation” objective at a smaller/larger display size. These individual packets requiring color correction are, similarly, grouped into a segment. Some individual packets <b>18</b> may be recursively segmented into segments <b>18</b>. The terms “recursively segments,” “recursive segmentation,” “recursively segmenting,” and similar wording mean the Analysis Module <b>20</b> uses a characteristic of one segment to determine the segmentation of another segment. That is, when the Analysis Module <b>20</b> segments the first stream <b>12</b> of data, the segmentation of at least one segment <b>18</b> is at least in part based upon a characteristic of a preceding segment <b>22</b>, as the following paragraphs will explain in greater detail. Some examples of these similar characteristics include recursively segmenting according to some mathematical characteristic of a preceding segment, recursively segmenting according to a characteristic of the content/structure of a preceding segment, and/or recursively segmenting according to a characteristic of the timing/sequence of a preceding segment. Once a segment is created, if the segment requires subsequent processing, the Analysis Module <b>20</b> then disperses that segment <b>18</b> and/or <b>22</b> via the network <b>14</b> for the subsequent processing service. The Analysis Module <b>20</b> routes the segments <b>18</b>, <b>22</b> to other devices and/or locations via the network <b>14</b>, and the subsequent processing service is performed.
0026The Analysis Module <b>20</b> may subcontract services to different service providers. If a different service provider can provide some requested communications service for a cheaper price, a higher performance, or some other criteria, then the Analysis Module <b>20</b> may determine that it's more profitable and/or more advantageous to “subcontract” some or all of the requested communications service. So, when a client communications device request some communications service for the first stream <b>12</b> of data, the Analysis Module <b>20</b> may interrogate other service providers. The Analysis Module <b>20</b> may dynamically, and in real-time, assess an availability of other communications networks operated by other service providers. The Analysis Module <b>20</b> may send an interrogation to the other service providers of the other communications networks. The interrogation describes what data is requested, and the interrogation includes any parameters for fulfilling a request for communications. The interrogation also solicits the other service provider's available network routing, available bandwidth, and pricing.
0027As <figref idref="DRAWINGS">FIG. 2</figref> shows, the Analysis Module <b>20</b> receives the results <b>24</b> of the subsequent processing services. When the subsequent processing service is complete, the Analysis Module <b>20</b> aggregates the result(s) <b>24</b> of the subsequent processing service(s). The Analysis Module <b>20</b> may then assemble that result <b>24</b> into another data structure, and/or the Analysis Module <b>20</b> may communicate the result(s) <b>24</b> along the communications network <b>14</b>. The Analysis Module <b>20</b>, for example, may assemble unprocessed segments and the results <b>24</b> into a new, formatted, second data stream <b>26</b>. As <figref idref="DRAWINGS">FIG. 2</figref> shows, the second data stream <b>26</b> is typically communicated via the network <b>14</b> to another destination. That is, the second data stream <b>26</b> may be communicated to another computer device, and/or the second data stream <b>26</b> may be communicated to a client communications device. The client communications device may then view/execute/present the second data stream <b>26</b> with little or no regard for the original format of the electronic data. The second data stream <b>22</b>, in other words, has already been substantially formatted, transformed, processed, and/or manipulated to suit the processing, storage, and/or audio/display requirements of the client communications device. The second data stream <b>26</b> may, instead, be communicated to a resident application/processor operating in the computer system <b>10</b>.
0028Many characteristics may influence the recursive segmentation of a segment <b>18</b>. The terms “recursively segments,” “recursive segmentation,” “recursively segmenting,” and other similar wording mean that the Analysis Module <b>20</b> uses a characteristic of one segment to determine the segmentation of another segment. When the Analysis Module segments the first stream <b>12</b> of data, the segmentation of at least one segment <b>18</b> is at least in part based upon a characteristic of one or more preceding segments <b>22</b>. One segment, for example, may be mathematically described from knowing the structure, content, or internal packet sequence of a preceding segment. If, for example, a sequence of packets has a similar structure to a previous sequence, then the corresponding segments may also have a similar structure. If the content of one or more segments resembles some previous segment(s), then the corresponding segments could have similar content. A known chronological characteristic of one segment may be used when segmenting other packets with the same chronological characteristic. As the following paragraphs suggest, any similarities between segments may be exploited for compression, description, and prediction algorithms.
0029The Analysis Module <b>20</b> may be used for data compression. When a segment shares a similar characteristic with a previous segment, the Analysis Module <b>20</b> may autonomously decide that the similar segments may be similarly compressed. As those of ordinary skill in the art understand, data compression is commonly used to reduce the size of data files. The Analysis Module <b>20</b> may similarly utilize data compression techniques to reduce the size, or length, of segments. The Analysis Module <b>20</b>, in addition, may identify similar segments and “insert” similar compression results without actually compressing each similar segment. Static “background” scenes in a video, for example, may not change for several seconds or even several minutes. Once the Analysis Module <b>20</b> recognizes a repetitive segment, the Analysis Module <b>20</b> may substitute the data compression results of a similar, preceding segment. This ability to substitute, or “insert,” compression results from a preceding segment allows the Analysis Module <b>20</b> to reduce, or even eliminate, processing of redundant segments. The Analysis Module <b>20</b> quickly substitutes compression results for similar segments, thus improving system and processor performance.
0030The Analysis Module <b>20</b> may be used for data description. If a segment shares a similar characteristic with a previous segment, then the Analysis Module <b>20</b> may autonomously decide that the similar segments may be similarly described. That is, once a segment is identified, other segments, having the same characteristic, may be similarly identified. Similar segments, in fact, may be abbreviated or referenced using a common descriptor, designation, and/or formula. This similar characteristic would permit similar segments to be replaced with a simpler, and/or shorter, notation. Long segments, and/or complex segments, for example, could be replaced with a short notation or with a shorter segment. If the actual segment is later required, the shorter notation (or shorter segment) may be replaced with the actual segment. The common descriptor, designation, formula, notation, and/or segment, representing similar segments, allows the Analysis Module <b>20</b> to reduce long and/or complicated data segments with shorter and simpler representations.
0031The Analysis Module <b>20</b> may also be used for data prediction. If a segment shares a similar characteristic with a previous segment, then the Analysis Module <b>20</b> may autonomously predict that the similar segment should have similar processing. The Analysis Module <b>20</b>, for example, could discard, or “skip,” any processing requirement for a segment having one or more the similar characteristics to a preceding segment. The Analysis Module <b>20</b>, instead, could simply duplicate the processing results of the preceding segment. These duplicate processing results could then be assembled, or “inserted,” at the appropriate moment or at the appropriate location. This similar characteristic between the segments allows the Analysis Module <b>20</b> to conserve, and perhaps eliminate, redundant processing requirements for similar segments.
0032The Analysis Module <b>20</b> may also be used for encryption of segments. Once a segment is encrypted, other segments with a similar characteristic may be similarly encrypted. That is, if a segment shares a similar characteristic with a previous segment, then the Analysis Module <b>20</b> may autonomously encrypt the similar segment as the preceding segment. Once the Analysis Module <b>20</b> recognizes a repetitive segment, the Analysis Module <b>20</b> may substitute the encryption results of a preceding segment. The Analysis Module <b>20</b> allows the same, or similar, encryption results from a preceding segment to be substituted for a current segment. The Analysis Module <b>20</b> again reduces, or even eliminates, processing of redundant segments. The Analysis Module <b>20</b> quickly substitutes encryption results for similar segments, thus improving system and processor performance.
0033Because there may be many similarities between segments, <figref idref="DRAWINGS">FIG. 3</figref> shows a segmentation profile <b>28</b>. The Analysis Module <b>20</b> may consult the segmentation profile <b>28</b> when processing segments with similar characteristics. The segmentation profile <b>28</b> stores rules that define various actions when a similar characteristic is encountered. The segmentation profile <b>28</b> is stored/maintained in a database <b>30</b> of segmentation profiles. The database <b>30</b> of segmentation profiles may be stored/maintained at any location, and/or on any device, within a communications/communications/computer network <b>32</b>. The segmentation profile <b>28</b> could also be stored on the client communications device. <figref idref="DRAWINGS">FIG. 3</figref>, however, shows the database <b>30</b> of segmentation profiles operating within, or locally to, an application server <b>34</b>. The database <b>30</b> of segmentation profiles is stored within a system memory device of the application server <b>34</b>.
0034The Analysis Module <b>20</b> consults the segmentation profile <b>28</b>. The segmentation profile <b>28</b> specifies how certain types of data and/or segments should be processed. The segmentation profile <b>28</b> may also specify how that data should be segmented. As the Analysis Module <b>20</b> segments data, the Analysis Module <b>20</b> consults the segmentation profile <b>28</b> for identified characteristics. If a segment contains a recognized characteristic, the Analysis Module <b>20</b> applies the rules stored within the segmentation profile <b>28</b>. As <figref idref="DRAWINGS">FIG. 9</figref> shows, the segmentation profile <b>28</b> stores various characteristics and associated factors, rules, requirements, and/or objectives that determine how similar segments should be processed. These characteristics may include timing characteristics, structural characteristics, content characteristics, processing characteristics, routing characteristics, and any other characteristics desired. The segmentation profile <b>28</b>, for example, may specify that the processing of repetitive MPEG segments be suspended and, instead, processing results from an earlier segment be used (those of ordinary skill in the art of programming and communications are assumed familiar with the “Moving Picture Experts Group” family of International Standards for coding audio-visual information in a digital compressed format, e.g., MPEG-1, MPEG-2 and MPEG-4). The segmentation profile <b>28</b> might specify that any XML segment having five percent (5%) or less pixel data change within two seconds be discarded to reduce processing times. The segmentation profile <b>28</b> might specify that 128-bit audio segments be “chopped” to suit the limited, reduced fidelity abilities of a client communications device. Video segments, too, might be chopped/compressed/resized to suit the display characteristics of a client communications device. The segmentation profile <b>28</b> would generally list each characteristic and provide a rule, requirement, or objective for each characteristic. As the Analysis Module <b>20</b> encounters each characteristic, the Analysis Module <b>20</b> abides by the rule, requirement, or objective. If any segments then require subsequent processing service(s), the Analysis Module <b>20</b> disperses the segments <b>18</b> via a data network <b>36</b> and/or a communications network <b>38</b>.
0035<figref idref="DRAWINGS">FIG. 4</figref> is a schematic illustrating another of the embodiments of this invention. <figref idref="DRAWINGS">FIG. 4</figref> shows that the segmentation profile <b>28</b> may specify how various segments and/or results are assembled. As this patent earlier mentioned, the Analysis Module <b>20</b> receives the results <b>24</b> of the subsequent processing services. The Analysis Module <b>20</b> may then aggregate/assemble the second data stream <b>26</b>. The second data stream <b>26</b> includes at least one of i) the results <b>24</b> of the subsequent processing service and ii) an unprocessed, recursively segmented segment <b>40</b>. The Analysis Module <b>20</b> may then communicate the second data stream <b>26</b> along the data network <b>36</b> and/or the communications network <b>38</b> to another computer device and/or a client communications device. The second data stream <b>26</b> is preferably formatted such that the client communications device may view/execute/present the second data stream <b>26</b> with little or no regard for the original format of the first stream of data (shown as reference numeral <b>12</b> in <figref idref="DRAWINGS">FIG. 1</figref>). The second data stream <b>26</b>, in other words, has already been substantially formatted, transformed, processed, and/or manipulated to suit the processing, storage, and/or audio/display requirements of the computer device and/or the client communications device.
0036<figref idref="DRAWINGS">FIG. 5</figref> is a schematic illustrating another of the embodiments of this invention. <figref idref="DRAWINGS">FIG. 5</figref> shows an individual segment <b>18</b> containing historical routing information <b>42</b> and historical processing information <b>44</b>. As each segment <b>18</b> travels, each segment <b>18</b> may accrue the historical routing information <b>42</b> and/or the historical processing information <b>44</b>. The historical routing information <b>42</b> describes past destinations of the segment <b>18</b> as the segment travels via the network (such as the data network <b>36</b> and/or the communications network <b>38</b> shown in <figref idref="DRAWINGS">FIGS. 3 and 4</figref>). This historical routing information <b>42</b> could resemble a “travel log” for the segment <b>18</b>. As the segment <b>18</b> is dispersed for any subsequent processing service, the historical routing information <b>42</b> would be updated with the destination address (such as an Internet Protocol address) of the subsequent processing service. The historical routing information <b>42</b> could also contain the routing/network path for that subsequent processing service. Even if no subsequent processing service is required, the historical routing information <b>42</b> could still be updated with any destination address and any routing/network path as the segment travels. The historical routing information <b>42</b>, therefore, could contain any information that describes the routing of the segment <b>18</b> or the routing of the processing results for the segment <b>18</b>.
0037<figref idref="DRAWINGS">FIG. 5</figref> also shows the historical processing information <b>44</b>. The historical processing information <b>44</b> resembles a “processing log” for the segment <b>18</b>. As the segment <b>18</b> travels via the network from destination to destination, the historical processing information <b>44</b> describes any processing that is performed upon the segment <b>18</b>. The historical processing information <b>44</b> could also describe each result obtained for each process; in other words, the historical processing information <b>44</b> could separately explain any processing performed on the segment and any processing performed on the results of that processing (the results are shown as reference numeral <b>24</b> in <figref idref="DRAWINGS">FIGS. 2 and 4</figref>). No matter how the segment <b>18</b> is processed (e.g., formatted, transformed, encrypted, scaled, compressed, or manipulated), the historical processing information <b>44</b> provides a log of that processing. As the segment <b>18</b> travels, and as the segment <b>18</b> is processed, the Analysis Module <b>20</b> annotates the segment <b>18</b> with a history of its travels and processing. The historical routing information <b>42</b> and the historical processing information <b>44</b> thus allows the Analysis Module <b>20</b> to inherently “mark-up” the segment <b>18</b> without assistance and with little or no oversight.
0038<figref idref="DRAWINGS">FIG. 5</figref> shows the historical routing information <b>42</b> and the historical processing information <b>44</b> contained within a header <b>46</b>. This header <b>46</b> is preferably separately identifiable from the packets <b>16</b> of data contained within the segment <b>18</b>. The header <b>46</b> may be a separate packet, or the header <b>46</b> may be a data field within the segment <b>18</b>. The header <b>46</b> serves as an annotation area for the entire segment <b>18</b>. As the segment travels, and as the segment <b>18</b> is processed, the historical routing information <b>42</b> and the historical processing information <b>44</b> contained within the header <b>46</b> are updated. Although the segment <b>18</b> is shown with the header <b>46</b> leading the packets <b>16</b> of data, the header <b>46</b> may be situated at any location within the segment <b>18</b>. The historical routing information <b>42</b> and the historical processing information <b>44</b>, too, need not be contained within the header <b>46</b>. The historical routing information <b>42</b> and the historical processing information <b>44</b> may be maintained within any portion, or at any location, of the segment <b>18</b>.
0039<figref idref="DRAWINGS">FIG. 6</figref> is a schematic illustrating another of the embodiments of this invention. <figref idref="DRAWINGS">FIG. 6</figref> is similar to <figref idref="DRAWINGS">FIG. 4</figref> and again shows the Analysis Module <b>20</b> assembling the second data stream <b>26</b>. Here, however, the Analysis Module <b>20</b> assembles the second data stream <b>26</b> using the historical routing information <b>42</b> and the historical processing information <b>44</b>. The Analysis Module <b>20</b>, as earlier mentioned, receives the results <b>24</b> of the subsequent processing services. The Analysis Module <b>20</b> may then aggregate/assemble the second data stream <b>26</b>. The second data stream <b>26</b> includes at least one of i) the results <b>24</b> of the subsequent processing service and ii) the unprocessed, recursively segmented segment <b>40</b>. The second data stream <b>26</b>, however, may also include the historical routing information <b>42</b> and the historical processing information <b>44</b>. The Analysis Module <b>20</b> may then communicate the second data stream <b>26</b> along the data network <b>36</b> and/or the communications network <b>38</b> to another computer device and/or a client communications device.
0040The Analysis Module <b>20</b> may employ a “self-assembly” strategy when assembling the second data stream <b>26</b>. Because the Analysis Module <b>20</b> may identify recognizable characteristics of data, the Analysis Module <b>20</b> may use the same characteristics to autonomously assemble a requested stream of data. When, for example, a client communications device requests electronic data, the Analysis Module <b>20</b> can retrieve the requested electronic data and autonomously format that data to suit the client communications device. The Analysis Module <b>20</b> may also use any recognized characteristic to correctly assemble the requested data into the proper/required sequence. Because the Analysis Module <b>20</b> disperses the segments <b>18</b> for subsequent processing services (as <figref idref="DRAWINGS">FIGS. 1 and 3</figref> show), the results (shown as reference numeral <b>24</b> in <figref idref="DRAWINGS">FIGS. 2 and 4</figref>) commonly randomly arrive in no particular order. The Analysis Module <b>20</b>, then, must correctly assemble the second data stream <b>26</b> with the results <b>24</b>, and with any unprocessed recursive segments <b>40</b>, in a correct sequence or order. The Analysis Module <b>20</b>, for example, could use chronological characteristics to determine the correct sequence or order of the second data stream <b>26</b>. If the requested first data stream (shown as reference numeral <b>12</b> in <figref idref="DRAWINGS">FIG. 1</figref>) has a “first in, first out” arrangement, the Analysis Module <b>20</b> could arrange the second data stream <b>26</b> to chronologically correspond with the requested first data stream. The Analysis Module <b>20</b> could also use the historical routing information <b>42</b> and/or the historical processing information <b>44</b> to self-assemble the second data stream <b>26</b>. The Analysis Module <b>20</b> could use the historical routing information <b>42</b> and the historical processing information <b>44</b> to inherently “mark-up” the segment <b>18</b> with assembly instructions.
0041Because this invention utilizes recursive segmentation, this invention is particularly useful for structured streams of data. The technique of recursive segmentation, as described herein, lends itself to fast and efficient data compression, data description, and data prediction. As data content formats become more structured, this invention allows automated segmentation, automated processing, and automated assembly of streams of data. The Analysis Module <b>20</b> of this invention creates and assembles formatted data streams for a client communications device. The client communications device may then view/execute/present the formatted data stream (such as the second data stream shown in FIGS. <b>2</b> and <b>4</b>-<b>6</b>) with little or no regard for the original format of the requested electronic data. The formatted, second data stream <b>26</b> has already been substantially formatted, transformed, processed, and/or manipulated to suit the processing, storage, and/or audio/display requirements of the client communications device.
0042<figref idref="DRAWINGS">FIG. 7</figref> is a flowchart illustrating a method of providing communications services. A request for data is received (Block <b>46</b>). A query is communicated via a network for the requested data (Block <b>48</b>). The requested data is received at a computer as a first data stream, and the first data stream is received as packets of data packetized according to a packet protocol (Block <b>50</b>). The first data stream is recursively segmented into segments (Block <b>52</b>), and at least one segment is dispersed via a network for a subsequent processing service (Block <b>54</b>). A result of the processing service is received (Block <b>56</b>) and aggregated into a second data stream (Block <b>58</b>). The second data stream is then communicated via the network as the requested data (Block <b>60</b>).
0043<figref idref="DRAWINGS">FIGS. 8 and 9</figref> are flowcharts illustrating one or more methods for providing communications services according to the embodiments of this invention. A request for an assembled data stream is received (Block <b>62</b>), and a query is communicated via a network for packets of data fulfilling the request (Block <b>64</b>). The packets of data are received at a computer operating in a network (Block <b>66</b>). The packets of data are packetized according to a packet protocol. If a segmentation profile is stored in memory (Block <b>68</b>), then the packets of data are recursively segmented according to the segmentation profile (Block <b>70</b>). The packets of data may be recursively segmented using a characteristic of one segment to describe another segment (Block <b>72</b>). The packets of data may also be recursively segmented using a characteristic of a preceding segment to describe a current segment (Block <b>74</b>). The packets of data may also be recursively segmented by mathematically describing a segment based upon a preceding segment (Block <b>76</b>).
0044The flowchart continues with <figref idref="DRAWINGS">FIG. 9</figref>. At least one of the segments is dispersed via the network for a subsequent processing service (Block <b>78</b>). As the segment travels via the network, the segment may accrue historical routing information describing at least one destination of the segment (Block <b>80</b>). As the segment is processed, the segment may accrue historical processing information describing at least one process performed on the segment (Block <b>82</b>). A result of the subsequent processing service is received (Block <b>84</b>). A data stream is then assembled (Block <b>86</b>), and the data stream includes at least one of i) the results of the subsequent processing service, ii) a recursively segmented segment, iii) the historical routing information, and iv) the historical processing information. The assembled data stream may be communicated to a client communications device (Block <b>88</b>).
0045The Analysis Module (shown as reference numeral <b>20</b> in <figref idref="DRAWINGS">FIGS. 1-6</figref>) may be physically embodied on or in a computer-readable medium. This computer-readable medium may include CD-ROM, DVD, tape, cassette, floppy disk, memory card, and large-capacity disk (such as IOMEGA®, ZIP®, JAZZ®, and other large-capacity memory products (IOMEGA®, ZIP®, and JAZZ® are registered trademarks of Iomega Corporation, 1821 W. Iomega Way, Roy, Utah 84067, 801.332.1000, www.iomega.com). This computer-readable medium, or media, could be distributed to end-users, licensees, and assignees. These types of computer-readable media, and other types not mention here but considered within the scope of the present invention, allow the Analysis Module to be easily disseminated. A computer program product for providing communications services includes the Analysis Module stored on the computer-readable medium. The Analysis Module receives data at a computer with the data received as packets of data packetized according to a packet protocol. The Analysis Module recursively segments the packets of data into segments according to a segmentation profile stored in memory. The Analysis Module disperses at least one of the segments via a network for a subsequent processing service. The Analysis Module receives results of the subsequent processing service and assembles a data stream, with the data stream including at least one of i) the results of the subsequent processing service and ii) a recursively segmented segment.
0046The Analysis Module may also be physically embodied on or in any addressable (e.g., HTTP, I.E.E.E. 802.11, Wireless Application Protocol (WAP)) wireless device capable of presenting an IP address. Examples could include a computer, a wireless personal digital assistant (PDA), an Internet Protocol mobile phone, or a wireless pager.
0047While the present invention has been described with respect to various features, aspects, and embodiments, those skilled and unskilled in the art will recognize the invention is not so limited. Other variations, modifications, and alternative embodiments may be made without departing from the spirit and scope of the present invention.
Contents6
11 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US10476738B1 | Cited by | United States of America | Applicant |
| US10230658B2 | Cited by | United States of America | Applicant |
| US10346190B1 | Cited by | United States of America | Search report |
| US2011125907A1 | Cited by | United States of America | Pre-grant |
| US9240901B2 | Cited by | United States of America | Search report |
| US2001005358A1 | Cites | United States of America | Applicant |
| US2001014210A1 | Cites | United States of America | Search report |
| US2001029544A1 | Cites | United States of America | Applicant |
| US2001056504A1 | Cites | United States of America | Search report |
| US2002021669A1 | Cites | United States of America | Applicant |
| US2002058532A1 | Cites | United States of America | Applicant |
| US2002073182A1 | Cites | United States of America | Applicant |
| US2002087674A1 | Cites | United States of America | Applicant |
| US2002106019A1 | Cites | United States of America | Search report |
| US2002112060A1 | Cites | United States of America | Applicant |
| US2002120744A1 | Cites | United States of America | Applicant |
| US2002128948A1 | Cites | United States of America | Applicant |
| US2002138398A1 | Cites | United States of America | Applicant |
| US2002138418A1 | Cites | United States of America | Applicant |
| US2002146102A1 | Cites | United States of America | Applicant |
| US2002161908A1 | Cites | United States of America | Search report |
| US2002164018A1 | Cites | United States of America | Search report |
| US2002176378A1 | Cites | United States of America | Applicant |
| US2003004855A1 | Cites | United States of America | Applicant |
| US2003005103A1 | Cites | United States of America | Search report |
| US2003005154A1 | Cites | United States of America | Applicant |
| US2003005155A1 | Cites | United States of America | Applicant |
| US2003012136A1 | Cites | United States of America | Search report |
| US2003012376A1 | Cites | United States of America | Search report |
| US2003033238A1 | Cites | United States of America | Applicant |
| US2003043815A1 | Cites | United States of America | Applicant |
| US2003051054A1 | Cites | United States of America | Applicant |
| US2003055723A1 | Cites | United States of America | Applicant |
| US2003088778A1 | Cites | United States of America | Applicant |
| US2003093550A1 | Cites | United States of America | Search report |
| US2003093790A1 | Cites | United States of America | Applicant |
| US2003097462A1 | Cites | United States of America | Search report |
| US2003100315A1 | Cites | United States of America | Applicant |
| US2003105726A1 | Cites | United States of America | Applicant |
| US2003126610A1 | Cites | United States of America | Applicant |
| US2003143978A1 | Cites | United States of America | Applicant |
| US2003156543A1 | Cites | United States of America | Search report |
| US2003200336A1 | Cites | United States of America | Search report |
| US2003211856A1 | Cites | United States of America | Applicant |
| US2003225677A1 | Cites | United States of America | Applicant |
| US2003233332A1 | Cites | United States of America | Applicant |
| US2004008778A1 | Cites | United States of America | Search report |
| US2004019900A1 | Cites | United States of America | Applicant |
| US2004028049A1 | Cites | United States of America | Search report |
| US2004030681A1 | Cites | United States of America | Search report |
| US2004073701A1 | Cites | United States of America | Search report |
| US2004132449A1 | Cites | United States of America | Applicant |
| US2004139208A1 | Cites | United States of America | Applicant |
| US2004151382A1 | Cites | United States of America | Search report |
| US2004160932A1 | Cites | United States of America | Applicant |
| US2004205013A1 | Cites | United States of America | Applicant |
| US2004218895A1 | Cites | United States of America | Search report |
| US2004220965A1 | Cites | United States of America | Search report |
| US2004221053A1 | Cites | United States of America | Applicant |
| US2004249927A1 | Cites | United States of America | Applicant |
| US2004252681A1 | Cites | United States of America | Search report |
| US2004267686A1 | Cites | United States of America | Applicant |
| US2005025124A1 | Cites | United States of America | Applicant |
| US2005038637A1 | Cites | United States of America | Applicant |
| US2005060420A1 | Cites | United States of America | Applicant |
| US2005102135A1 | Cites | United States of America | Search report |
| US2005183127A1 | Cites | United States of America | Search report |
| US2007192862A1 | Cites | United States of America | Search report |
| US4788721A | Cites | United States of America | Applicant |
| US4873517A | Cites | United States of America | Applicant |
| US5513306A | Cites | United States of America | Search report |
| US5752186A | Cites | United States of America | Applicant |
| US5761429A | Cites | United States of America | Applicant |
| US5771282A | Cites | United States of America | Applicant |
| US5786770A | Cites | United States of America | Applicant |
| US5790176A | Cites | United States of America | Applicant |
| US5838913A | Cites | United States of America | Applicant |
| US5862325A | Cites | United States of America | Applicant |
| US5862471A | Cites | United States of America | Applicant |
| US5941988A | Cites | United States of America | Search report |
| US5970121A | Cites | United States of America | Applicant |
| US5978780A | Cites | United States of America | Applicant |
| US6002689A | Cites | United States of America | Applicant |
| US6012098A | Cites | United States of America | Applicant |
| US6016307A | Cites | United States of America | Applicant |
| US6018359A | Cites | United States of America | Search report |
| US6032190A | Cites | United States of America | Search report |
| US6058301A | Cites | United States of America | Applicant |
| US6088717A | Cites | United States of America | Applicant |
| US6104718A | Cites | United States of America | Applicant |
| US6148290A | Cites | United States of America | Applicant |
| US6178170B1 | Cites | United States of America | Applicant |
| US6226291B1 | Cites | United States of America | Search report |
| US6236642B1 | Cites | United States of America | Applicant |
| US6263358B1 | Cites | United States of America | Applicant |
| US6272343B1 | Cites | United States of America | Applicant |
| US6278446B1 | Cites | United States of America | Search report |
| US6285871B1 | Cites | United States of America | Applicant |
| US6363434B1 | Cites | United States of America | Applicant |
| US6385198B1 | Cites | United States of America | Applicant |
4 members in 1 office
Priority claims6
| Document | Office | Kind | Date |
|---|---|---|---|
| 72094903 | United States of America | A | |
| 72094903 | United States of America | A | |
| 33457808 | United States of America | A | |
| 10720949 | – | – | – |
| US20030720949 | – | – | – |
| US20080334578 | – | – | – |
Members4
| Document | Office | Kind | |
|---|---|---|---|
| US2005144304A1 | United States of America | A1 | |
| US7467219B2 | United States of America | B2 | |
| US2009100191A1 | United States of America | A1 | |
| US8606929B2This record | United States of America | B2 |
83 transactions on the USPTO file
Allowed after 4 non-final rejections, 4 final rejections and 4 RCEs.
- Non-final rejections
- 4
- Final rejections
- 4
- RCEs
- 4
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Expire PatentEXP. | EXP. | |
| Maintenance Fee Reminder MailedREM. | REM. | |
| Payment of Maintenance Fee, 8th Year, Large EntityM1552 | M1552 | |
| Correspondence Address ChangeC.AD | C.AD | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Filing Receipt - CorrectedFLRCPT.C | FLRCPT.C | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Reasons for AllowanceEX.R | EX.R | |
| Interview Summary - Examiner InitiatedEXIE | EXIE | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Correspondence Address ChangeC.AD | C.AD | |
| IFW TSS Processing by Tech Center CompleteTSSCOMP | TSSCOMP | |
| Preliminary AmendmentA.PE | A.PE | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Sent to Classification ContractorPGPC | PGPC | |
| Application Is Now CompleteCOMP | COMP | |
| Filing ReceiptFLRCPT.O | FLRCPT.O | |
| Cleared by OIPE CSRL194 | L194 | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Initial Exam Team nnIEXX | IEXX |
10 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Lapsed due to failure to pay maintenance feeLapsedFP | FP | |
| Lapse for failure to pay maintenance feesLapsedPATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYLAPS | LAPS | |
| Information on status: patent discontinuationPATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362STCH | STCH | |
| Fee payment procedureMAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| Maintenance fee paymentMAFP | MAFP | |
| Fee paymentFPAY | FPAY | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| Fee payment procedurePAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| AssignmentAS | AS | |
| AssignmentAS | AS |
Numbers
- Publication
- 08606929
- Publication, DOCDB
- 8606929
- Publication, EPODOC
- US8606929
- Application
- 12334578
- Application, DOCDB
- 33457808
- Application, EPODOC
- US20080334578
Titles
- English
- Methods, systems, and products for subcontracting segments in communications services
Patent term adjustment
- A delay
- +198 daysthe office missed an examination deadline
- Net adjustment
- 198 days
Classification
- CPC, 4
- H04N21/2343
- H04N21/2662
- H04L69/324
- H04L9/40
- IPC, 4
- H04L29 06
- G06F15 16
- H04L29 08
- H04N7 24
- USPC, 3
- 709227000
- 709231000
- 709234000