Multiple resolution capture in real time communications
Summary by NHIP
Dynamic Resolution Web Camera
The web camera system switches capture resolution between a first and second level during live conferencing. A marking component adds markers to the bitstream after the first resolution portion to signify the start of the second resolution data.
Claim Score by NHIP
Abstract
During remote communication session, there can be situations where information needs to be sent at a high resolution. Sending information at a high resolution allows for the capture of detail that can be lost without the use of a high resolution. A web camera can obtain information in both a higher resolution and standard resolution. A sending component can send this information encoded with markers that allow a receiving component to process and display the information.

Term
2 yearsleft in the term
Expires 24 September 2028, including 518 days of term adjustment.
- Priority and filed
- Granted
- Today
- Expires
12 claims: 2 independent, 10 dependent
- 1A web camera system, comprising:a web camera;a resolution mode component that can change level of resolution capture of the web camera during a communication session for live conferencing, wherein the resolution mode component can enable the web camera to capture information initially in a first level of resolution, change to capture a document in a second level of resolution, and then return to capture information in the first level of resolution;a marking component that adds marks after a portion of an emitted bitstream containing information that is captured in a first resolution quality to signify at least a beginning of information that is captured in a second resolution quality;and a processor component that creates an intelligent record of information captured by the web camera.
- 9Broadest claimClaim Score 63, broad(NHIP)A method, comprising:transmitting information captured during a communication session at a first resolution level;changing, by a processor, level of resolution capture during the communication session for live conferencing;transmitting additional captured information at a second resolution during the communication session, the additional captured information comprising a high-resolution capture of a document;applying markers to a video bitstream made of captured information, wherein the markers signify a change in level of resolution of at least one portion of information;and creating an intelligent copy of captured information at the second resolution.
Independent claims2
119 paragraphs in 5 sections, as filed
TECHNICAL FIELD
The subject specification relates generally to information capture and in particular to video and photograph capturing in real time communications.
BACKGROUND
Developments in communication technology have changed common protocol for business. There is less in-person communication as people communicate through alternative mediums. For example, electronic mail (e-mail) allows individuals to communicate virtually instantaneously. Real time communications allow individuals to communicate as if they were together even if they are not physically in the same location. For example, employees can communicate though an instant messenger service without ever leaving their desk or personal computer.
One area that has changed due to real time communication developments is business meetings. There are many instances where individuals no longer need to travel all over the world to collaborate on an idea. Software and hardware allow individuals to communicate with one another in real time from remote locations. For example, engineers in Canada, England, India, and Hong Kong can communicate with each other without having to leave their respective nations. A number of benefits occur from this type of communication. Costs can be vastly reduced since there is not physical travel and no incurring of expenses like flights or hotels. In addition, participants can have direct access to local resources (e.g., an employee's personal files) that allow them to begin work immediately at a high efficiency level. Furthermore, problems originating from international travel (e.g., passports, security clearance) are reduced.
SUMMARY
The following presents a simplified summary of the specification in order to provide a basic understanding of some aspects of the specification. This summary is not an extensive overview of the specification. It is intended to neither identify key or critical elements of the specification nor delineate the scope of the specification. Its sole purpose is to present some concepts of the specification in a simplified form as a prelude to the more detailed description that is presented later.
Digital communication technology does not allow for capture of high-resolution images during a real time correspondence. The subject specification discloses information for capture of high-resolution images during real time communication. An encoder has several modes in which to capture images for different purposes and formats. Information can be transmitted at different resolution levels during the same communication session. A specially captured image travels to a receiver with specific information to identify that a communicated image is a specially captured image.
In particular, claimed aspects described herein provide for conducting a webcam session and allow the webcam session to be conducted at a relatively low resolution in order to optimize an amount of date conveyed during the session. However, oftentimes individuals in the session want to capture and send an image to the other end in high-resolution. The session can be mitigated to capture an image at high-resolution. Devoting a higher amount of resources during a brief period of time allows for a high-resolution capture without extensive problems in the session. Typically, webcam sessions have a low bandwidth meaning there is only a limited amount of information that can pass at a single time. If there is an attempt to pass more information then bandwidth allows, then there can be partial breakdown of the session (e.g., choppiness of a transferred sound). Therefore, the subject specification disclosed information for allocating resource for a high-resolution capture for only a limited period of time. Once the high-resolution capture completes, there can be a return to a lower level of resolution.
The following description and the annexed drawings set forth certain illustrative aspects of the specification. These aspects are indicative, however, of but a few of the various ways in which the principles of the specification may be employed. Other advantages and novel features of the specification will become apparent from the following detailed description of the specification when considered in conjunction with the drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
<figref idrefs="DRAWINGS">FIG. 1</figref> illustrates a representative communication system in accordance with an aspect of the subject specification.
<figref idrefs="DRAWINGS">FIG. 2</figref> illustrates a representative sending component in accordance with an aspect of the subject specification.
<figref idrefs="DRAWINGS">FIG. 3</figref> illustrates a representative bitstream in accordance with an aspect of the subject specification.
<figref idrefs="DRAWINGS">FIG. 4</figref> illustrates a representative receiving component in accordance with an aspect of the subject specification.
<figref idrefs="DRAWINGS">FIG. 5</figref><i>a </i>illustrates a representative pixel capture in accordance with an aspect of the subject specification.
<figref idrefs="DRAWINGS">FIG. 5</figref><i>b </i>illustrates a representative pixel capture in accordance with an aspect of the subject specification.
<figref idrefs="DRAWINGS">FIG. 5</figref><i>c </i>illustrates a representative pixel capture in accordance with an aspect of the subject specification.
<figref idrefs="DRAWINGS">FIG. 6</figref> illustrates a representative presentation in accordance with an aspect of the subject specification.
<figref idrefs="DRAWINGS">FIG. 7</figref><i>a </i>illustrates a first part of a representative pixel capture in accordance with an aspect of the subject specification.
<figref idrefs="DRAWINGS">FIG. 7</figref><i>b </i>illustrates a second part of a representative methodology in accordance with an aspect of the subject specification.
<figref idrefs="DRAWINGS">FIG. 7</figref><i>c </i>illustrates a third part of a representative pixel capture in accordance with an aspect of the subject specification.
<figref idrefs="DRAWINGS">FIG. 8</figref> illustrates a representative methodology of a sending component in accordance with an aspect of the subject specification.
<figref idrefs="DRAWINGS">FIG. 9</figref> illustrates a representative methodology of a receiving component in accordance with an aspect of the subject specification.
<figref idrefs="DRAWINGS">FIG. 10</figref> illustrates a representative methodology of a multi-resolution capture session in accordance with an aspect of the subject specification.
<figref idrefs="DRAWINGS">FIG. 11</figref> illustrates a representative schematic block diagram of a computing environment in accordance with an aspect of the subject specification.
<figref idrefs="DRAWINGS">FIG. 12</figref> illustrates a representative block diagram of a computer operable to execute in accordance with an aspect of the subject specification.
DETAILED DESCRIPTION
The claimed subject matter is now described with reference to the drawings, wherein like reference numerals are used to refer to like elements throughout. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the claimed subject matter. It may be evident, however, that the claimed subject matter may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to facilitate describing the claimed subject matter.
As used in this application, the terms “component,” “module,” “system”, “interface”, or the like are generally intended to refer to a computer-related entity, either hardware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a controller and the controller can be a component. One or more components may reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers. As another example, an interface can include I/O components as well as associated processor, application, and/or API components.
Furthermore, the claimed subject matter may be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques to produce software, firmware, hardware, or any combination thereof to control a computer to implement the disclosed subject matter. The term “article of manufacture” as used herein is intended to encompass a computer program accessible from any computer-readable device, carrier, or media. For example, computer readable media can include but are not limited to magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips . . . ), optical disks (e.g., compact disk (CD), digital versatile disk (DVD) . . . ), smart cards, and flash memory devices (e.g., card, stick, key drive . . . ). Additionally it should be appreciated that a carrier wave can be employed to carry computer-readable electronic data such as those used in transmitting and receiving electronic mail or in accessing a network such as the Internet or a local area network (LAN). Of course, those skilled in the art will recognize many modifications may be made to this configuration without departing from the scope or spirit of the claimed subject matter.
Moreover, the word “exemplary” is used herein to mean serving as an example, instance, or illustration. Any aspect or design described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects or designs. Rather, use of the word exemplary is intended to present concepts in a concrete fashion. As used in this application, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or”. That is, unless specified otherwise, or clear from context, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then “X employs A or B” is satisfied under any of the foregoing instances. In addition, the articles “a” and “an” as used in this application and the appended claims should generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form.
During a common communication session, resolution is kept at a relatively low level to minimize communication breakdown (e.g., noticeable break-ups in communication flow) or simply to accommodate other types of traffic (e.g., downloads, uploads, etc.) that can occur on a common transmission network. However, there are situations where individuals participating in the session desire to communicate information at a higher resolution. Specific details can be missed at lower resolutions, which can be undesirable in particular situations (e.g., background noises can be missed with communicating at lower resolutions). Allowing for a resolution change during a communication session can protect both interests of limiting communicating breakdown and capturing necessary details.
For example, a communication session can take place at a relatively lower resolution level. The resolution can be changed to a higher level in order to capture more detail when necessary. The change in resolution dedicates more system resources (e.g., CPU cycles to encode the higher resolution video, higher bitrate to transmit the higher resolution video, etc.) to capturing details. Once necessary information is captured at a high-resolution, the communication session can resume the lower resolution level. This allows for an optimization of the communication session.
<figref idrefs="DRAWINGS">FIG. 1</figref> discloses an example communication system <b>100</b>. A web camera <b>102</b> perceives information and sends the information to a sending component <b>104</b>. The information can be anything perceived, including visual information and/or audio information. The subject specification relates to perception of information. In many parts of the specification, there is reference to visual capture (e.g., image capture). It is to be appreciated that references to visual capture in the subject specification are for example purposes and disclosed information can relate to other perceptions (e.g., perceiving audio sounds).
The web camera <b>102</b> can have multiple settings including a standard resolution mode and a high-resolution mode. It is to be appreciated that the web camera can capture any information capable of perception (e.g., infrared information). This includes perception of visual information as well as audio information. A configuration of the web camera <b>102</b> can have multiple resolution settings, including multiple high-resolution settings. These high-resolution settings can be multi-dimensional (e.g., can capture greater visual resolution and greater audio resolution at the same time). A web camera <b>102</b> can be a webcam; however, there are other possible embodiments. For example, the web camera <b>102</b> can be a computer display touchpad a user is writing onto by hand with a stylus that can be transmitted at different resolutions. Furthermore, the web camera can be a microphone with no optical capabilities. According to one embodiment, the web camera can take a single high-resolution frame shot (e.g., still picture) or a small sequence of contiguous high resolution frames, and automatically returns to a standard resolution mode.
A sending component <b>104</b> prepares images for transmission to a router component <b>106</b> and ultimately to a receiving component <b>108</b>. A common sending component <b>104</b> is a personal computer used by an individual user; a common router component <b>106</b> is an Audio/Video Multi-point Control Unit or AVMCU. A user can engage a sending component <b>104</b> to enable the web camera <b>102</b> to capture different images at different resolutions. A common component of a sending component <b>104</b> is an encoder component <b>110</b>. The encoder component <b>110</b> allows for compression of information (e.g., a standard resolution image or a high-resolution image) as well as creation of transferable information. According to one embodiment, the sending component <b>104</b> sends a continuous stream of information (e.g., a bitstream) to a router component <b>106</b> or a receiving component <b>108</b>. An encoder component <b>110</b> compresses information to allow for improved performance in real time communications. Information commonly travels in an encoded (e.g., compressed) format that can include specific security features (e.g., compressed encryption).
The information can travel to a router component <b>106</b> that couples to a storage component <b>112</b>. The router component <b>106</b> allows for transferring information to at least one receiving component <b>108</b> (e.g., another participant in a video conference). It is possible for the communication system <b>100</b> to function without a router component <b>106</b> and communicate directly with at least one receiving component <b>108</b>. An example of a communication system <b>100</b> that would not use a router component <b>106</b> is a peer-to-peer environment. The router component <b>106</b>, and thus the communication system <b>100</b>, can function in a closed environment (e.g., an internal business infrastructure) or an open environment (e.g., Internet communication system).
Coupled to the router component <b>106</b> is commonly a storage component <b>112</b>. The router component <b>106</b> can configure to be able to determine when it is processing a high-resolution image. There are instances where it can be beneficial for a router component <b>106</b> to store the high-resolution image. For example, there may be a slight interrupt in communications between the router component <b>106</b> and a receiving component <b>108</b>. If a successful communication cannot take place, the router component <b>106</b> can place the high-resolution image in the storage component <b>112</b>. In another embodiment, the router component <b>106</b> can back up all high-resolution images it receives by placing the high-resolution images in the storage component <b>112</b>.
Disclosed are three receiving components <b>108</b> with corresponding storage components <b>114</b>. However, any number of receiving component(s) <b>108</b> and storage component(s) <b>114</b> can be practiced, including uneven amounts (e.g., four receiving components <b>108</b> and one storage component <b>114</b>). In addition, storage components <b>114</b> can integrate with the receiving components <b>108</b> or integrate into the storage component <b>112</b>. Each receiving component <b>108</b> can receive information from the router component <b>106</b> and/or the sending component <b>104</b> and decode (e.g., decompress) the information thought a decoder component <b>116</b>. An example of a receiving component <b>108</b> is a laptop computer.
In one embodiment, the receiving component <b>108</b> decodes the transmitted information in real time during normal operation. Incoming high-resolution information is received and stored automatically. This can be done in a pre-designated folder and then a notice can be sent to the receiving component <b>108</b> that there is a save of a high-resolution capture. In another embodiment, a receiving user has an option to turn an auto-save feature ‘on’ or ‘off’.
While <figref idrefs="DRAWINGS">FIG. 1</figref> shows the router component <b>106</b> communicating with the storage component <b>114</b>, it is possible that the receiving component <b>108</b> communicate with the storage component <b>114</b> and not the router component <b>106</b>. In addition, the receiving component <b>108</b> can communicate with the storage component <b>114</b> through the decoder component <b>116</b>. This allows the storage component <b>114</b> to hold decoded information.
It is to be appreciated that while the disclosed system is configured for a live conferencing environment, there can be other configurations using disclosed information. For example, there could be no live conferencing and the sending component sends an electronic mail message. The receiving component could receive that message without use of live conferencing. Furthermore, there can be instances where a user cannot participate in real time video communication. A user can use the web camera to capture an image of a logo in high definition and that can be displayed to a receiving component as opposed to the live video feed. For example, a user can hold up a logo and capture the logo in high resolution.
The following is an example of an implementation of the communication system <b>100</b>. Any identification is used for example purposed and not intended to limit the scope of any component or feature of the subject specification. For example, a reference to ‘laptop computer <b>108</b>’ should not be limited the receiving component <b>108</b> to a laptop computer. A user sends information in real time using a webcam <b>102</b> integrated with a personal computer <b>104</b>. In common operation, the webcam <b>102</b> functions at a normal resolution (e.g., VGA—640 pixels by 480 pixels). However, the user wants to send an image to another user on a laptop computer <b>108</b> of a document. In order for the user on the laptop computer <b>108</b> to appreciate details of the document it should be transmitted at a higher resolution.
The user instructs the webcam <b>102</b> to capture images at a higher resolution (e.g., HUXGA—6400 pixels by 4800 pixels). The webcam then captures images at the higher resolution. Typically, the user holds up the document for capturing. An encoder <b>110</b> of the personal computer <b>104</b> prepares captured images for transportation. The captured image travels to a video router <b>106</b> that saves a copy of the captured image in storage <b>112</b>. The video router <b>106</b> sends the captured image to the laptop computer <b>108</b> that decodes the captured image with a decoder <b>116</b>. Commonly, the captured image is saved in storage <b>114</b>. It is to be appreciated that while the subject specification discusses selecting a higher resolution, information can configure to display information at a lower resolution.
<figref idrefs="DRAWINGS">FIG. 2</figref> discloses an example web camera <b>102</b> and sending component <b>104</b>. A resolution mode component <b>202</b> allows for specific settings in capture applicable to a web camera <b>102</b> (e.g., a webcam). There is commonly an initial option to select a capture session (e.g., video, fax, photograph, etc.) to take place. There can be a variety of capture modes available with the sending component <b>104</b>. The resolution mode component <b>202</b> can change level of resolution capture of the web camera during a communication session. The level or resolution capture can change for audio capture (e.g., increase perception of sounds), the level or resolution capture can change for visual capture (e.g., increase the amount of optical detail captured), as well as others (e.g., detection of atmospheric pressure). Furthermore, there can be multiple resolution changes at one time (e.g., increase in audio resolution as well as increase in visual resolution at the same time).
In one embodiment, a web camera <b>102</b> can use multiple resolution formats, including formats with a high spatial resolution mode (e.g., a resolution mode with a slower frame rate). These formats allow for capturing high video quality of still images (e.g., documents) and/or animations. While much of the subject specification relates to capturing an image at a resolution that is higher then a standard resolution, it is to appreciated that information disclosed can relate to a lower then standard resolution.
The resolution mode component <b>202</b> can operate manually (e.g., through user manipulation) or automatically. In automated image capture, a system (e.g., web camera <b>102</b> and a sending component <b>104</b>) or component (e.g., web camera <b>102</b>) can recognize when a web camera <b>102</b> perceives an image that can benefit from a display in a high-resolution. For example, a user holds a document up to a web camera <b>102</b>. The web camera <b>102</b> recognizes that it is capturing a document and that a capture of the document can benefit from a higher resolution capture.
Therefore, the web camera <b>102</b> can automatically capture the document at a higher resolution. Once complete, the web camera <b>102</b> can re-enter a normal resolution mode. For example, the resolution mode component can enable the web camera to capture information initially in a first resolution quality, change to capture information in a second resolution quality, and then return to capture information in the first resolution quality. This can be automatic or manual and it does not have to be dependent on the selection for entering a high-resolution mode. For example, if a high-resolution mode is entered automatically, it can be exited manually. In another embodiment, there can be an automatic determination for a time when a standard resolution mode can resume (e.g., after a five-second high-resolution capture, there is a return to standard resolution). The resolution mode component can automatically switch resolution quality for the web camera to obtain information.
In another embodiment, the resolution mode component <b>202</b> can configure with an option for a partial high-resolution capability. This allows a single capture to have different resolution properties. For example, a web camera <b>102</b> can have a document presented in 60% of a capture area and background in 40% of the capture area. The document portion can be captured in high-resolution while the background can be captured in standard resolution.
Once captured, information is passed to an encoder mode component <b>204</b>. The encoder mode component <b>204</b> compresses information for transport to a receiving component <b>108</b> of <figref idrefs="DRAWINGS">FIG. 1</figref>. Compression allows for communication that is more efficient. The encoder mode component <b>204</b> can configure to attempt to compress all captured information to the same size or have different sizes dependent on the resolution. The encoder component <b>110</b> of <figref idrefs="DRAWINGS">FIG. 1</figref> can be the same as the encoder mode component <b>204</b>, a combination of the encoder mode component <b>204</b> and a marking component <b>206</b>, as well as other configurations. In another embodiment, the web camera <b>102</b> communicates captured information directly to the encoder mode component <b>204</b> as opposed to through the resolution mode component <b>202</b>.
Furthermore, the encoder mode component <b>204</b> can be set to produce a high quality production of captured information. For example, the encoder mode component <b>204</b> can attempt to ensure a high quality image production for high-resolution visual capture. There can be a check performed be the encoder mode component <b>204</b> to make sure there are no errors in capturing (e.g., ensure there is production quality of information that is corresponding to that of what was intended to be captured and/or what the web camera can capture). The encoder mode component <b>204</b> can convert captured information into digital information that can be transmitted in order to ensure there is an appropriate quality level of production.
A marking component <b>206</b> adds markers to a bitstream of capture information to notify the receiving component <b>108</b> of <figref idrefs="DRAWINGS">FIG. 1</figref> as to the resolution of received information. The marking component adds marks after a portion of a bitstream with information that is captured in a first resolution quality to signify at least a beginning of information that is captured in a second resolution quality. Information travels from the sending component <b>104</b> as a bitstream that provides the receiving component <b>108</b> of <figref idrefs="DRAWINGS">FIG. 1</figref> with near continuous or continuous information in which to update a visual display. Added marks are commonly at each end of high-resolution information in a compressed bitstream. There is a beginning mark and an end mark so it can be determined where there is a start and a finish of a high-resolution capture.
In addition, the sending component <b>104</b> can increase security in regards to communication. This can be done in various manners. In one embodiment, the encoder mode component <b>204</b> encrypts compressed information. Once encrypted, the marking component <b>206</b> inserts security information (e.g., information on how to decrypt) into the bitstream. In another embodiment, the encoder mode component <b>204</b> encrypts information and a receiving component <b>108</b> of <figref idrefs="DRAWINGS">FIG. 1</figref> possesses information on how to decrypt information.
A photograph component <b>208</b> can specifically integrate with taking a photograph of an individual sending information. In one embodiment of the subject specification, a sender can take a high-resolution photograph of himself or herself. The photograph component <b>208</b> adds information to the bitstream that the high-resolution image is designed to be an identification photograph. The photograph component <b>208</b> associates information captured by the web camera with an identifier. When the information reaches a receiving component <b>108</b> of <figref idrefs="DRAWINGS">FIG. 1</figref>, the high-resolution photograph can be used for identification purposes. Furthermore, the information can be used for identification purposes prior to a transfer (e.g., used on a display component of the sending component). For example, the high-resolution photograph can be placed next to an individuals name on a teleconferencing prompt. In another embodiment, the photograph is not of a person, but of a symbol on a document.
Furthermore, the sending component <b>104</b> can have a processor component <b>210</b> that performs other processing on the information. The processor component <b>210</b> can add other information to the bitstream prior to transfer from the sending component <b>104</b>. Furthermore, the processor component <b>210</b> can display captured images to a display component integrated with the sending component. The processor component <b>210</b> performs analysis to determine characteristics of captured information.
An identifier component <b>212</b> can launch a mode at the start of a communication session to obtain associated information. For example, the identifier component <b>212</b> can instruct the resolution mode component <b>202</b> to begin a session in a higher resolution for utilizing the photograph component <b>208</b>. An image is captured and the photograph component <b>208</b> associates information captured by the web camera with an identifier (e.g., a person's name).
There can be a storage component <b>214</b> within the sending component <b>104</b> and information sent can be backed up locally. In addition, other information concerning the sending component <b>104</b> can be saved in the storage component <b>214</b>. The sending component <b>104</b> can access other storage components for saving captured information as well as the internal storage component <b>214</b>. The other storage components can be dedicated to the sending component <b>104</b> or shared with other components. For example, the sending component <b>104</b> could engage with the storage component <b>112</b> of <figref idrefs="DRAWINGS">FIG. 1</figref>. When engaging the storage component <b>112</b> of <figref idrefs="DRAWINGS">FIG. 1</figref>, there can be a creation of an intelligent record of information captured by the web camera <b>102</b>. This can be done by the processor component <b>210</b>. For example, the web camera <b>102</b> can take a five second video image of a document held up to its field of vision. The processor component <b>210</b> can identify that this is a high-resolution image of a document. A single file can be created and saved not as a video, but as a document file (e.g., a ‘.doc’ file).
A multi-image component <b>216</b> can combine image information to present a more accurate and/or higher resolution image. This creates super-resolution images from information captured by the web camera <b>102</b>. For example, there can be slight movements from the web camera <b>102</b>. These movements allow for a more detailed capture of a general area, specifically of the area at the edge of what is perceived by the web camera <b>102</b>.
The multi-image component <b>216</b> can process different frames of an image capture and integrate captured information into other displays. This allows for data to be received by the receiving component <b>108</b> in a super-resolution format. The multi-image component processes information captured by the web camera to allow for super-resolution. A transfer component <b>218</b> emits information captured by the web camera <b>102</b>. The transfer component <b>218</b> emits information captured by the web camera as a bitstream from the sending component <b>104</b> for further processing. Furthermore, the transfer component <b>218</b> can transmit information capture during a communication session at a first resolution level and transmit additional captured information at a second resolution level during the communication session.
<figref idrefs="DRAWINGS">FIG. 3</figref> discloses an example bitstream that travels from the sending component <b>104</b> of <figref idrefs="DRAWINGS">FIG. 1</figref> ultimately to a receiving component <b>108</b> of <figref idrefs="DRAWINGS">FIG. 1</figref>. A regular information piece <b>302</b> represents information in the bitstream <b>300</b> that has a standard resolution. A photo indication marker <b>304</b> indicates that the next segment of the bitstream represents a photograph that is to be used in a teleconferencing prompt. If a photograph is at a different resolution then the regular information piece <b>302</b>, then there is a change resolution start marker <b>306</b>. Commonly, the change resolution start marker <b>306</b> indicates that the resolution will be at a higher quality then the resolution of a regular information piece. However, it is possible that the resolution quality will be lower for an identification photograph or any other resolution change.
A change resolution information piece <b>308</b> is information that is at a different resolution then the regular information piece <b>302</b>. At an end of the change resolution information piece there is a change resolution end marker <b>310</b>. This signifies that the specific resolution information is ended. Commonly, after a change resolution end marker <b>310</b> there is a regular information piece <b>312</b> that is of the same resolution as the regular information piece <b>302</b>.
Different configurations of the bitstream <b>300</b> are possible. For example, the photograph indication maker <b>304</b> and the change resolution start marker <b>306</b> can be a single block publishing the new horizontal and vertical dimensions of a higher resolution video frame. In another possible configuration, the change resolution information piece <b>308</b> and the change resolution end marker <b>310</b> can be a single block where a new horizontal and vertical dimension of the standard definition video are published.
There are other embodiments available for a bitstream <b>300</b>. In one embodiment, the bitstream <b>300</b> can have check markers to enable a receiving component to confirm that information is processes at a correct resolution. In another embodiment, the bitstream <b>300</b> includes encryption information. Encryption information can arise in many different forms. In one example, the bitstream <b>300</b> can have encrypted information that a receiving component deciphers to read and display information. In another example, the bitstream <b>300</b> can have encrypted information as well as information on how to decrypt the information. A receiving component can process the decryption information in order to process the bitstream <b>300</b>.
While the bitstream <b>300</b> is shown as continuous, it is possible for there to be natural interrupts in the bitstream <b>300</b>. While this can be considered at technically multiple bitstreams, for the purposes of the subject specification, a bitstream <b>300</b> can refer to both a continuous bitstream and multiple bitstreams during the same communication session that have natural spaces and interrupts.
<figref idrefs="DRAWINGS">FIG. 4</figref> discloses an example receiving component <b>108</b>. A detection component <b>402</b> can identify resolution level of received information. For example, the detection component <b>402</b> can read information from a bitstream <b>300</b> of <figref idrefs="DRAWINGS">FIG. 1</figref>. The resolution of a regular information piece <b>302</b> of <figref idrefs="DRAWINGS">FIG. 3</figref> and a change resolution start marker <b>306</b> of <figref idrefs="DRAWINGS">FIG. 3</figref>, as well as other information can be identified by the detection component <b>402</b>.
A record component <b>404</b> stores received information when the received information is at a specified resolution level. For example, information can enter the receiving component <b>104</b> at 320×240. However, a copy of received information is not stored unless the information is above a level of 640×480 or higher. In this example, the specified resolution is a resolution above the level of 640×480. If received information changes to 800×600, then a copy of received information is stored, since it is above a threshold level of 640×480. Therefore the specified resolution level is any resolution within an open-ended resolution level range (e.g., resolution levels above level ‘X’, resolution levels below level ‘Y’).
Creating a copy of received information and storing a copy of the received information is the same as storing received information. However, storing received information can also be storing a non-copy of the received information. Other components in the receiving component <b>108</b> can operate off stored information.
A record component <b>404</b> can make a replica of information contained in a bitstream <b>300</b> of <figref idrefs="DRAWINGS">FIG. 3</figref> that enters the receiving component. The replica can be stored in a storage component <b>114</b> of <figref idrefs="DRAWINGS">FIG. 1</figref>. While the record component <b>404</b> is shown as functioning after the detection component, the record component <b>404</b> could follow other components of the receiver component <b>108</b>. For example, the record component <b>404</b> can operate after a decoder mode component <b>406</b>. Therefore, a decoded copy of information can be made and stored in the storage component <b>114</b> of <figref idrefs="DRAWINGS">FIG. 1</figref>.
A decoder mode component <b>406</b> decompresses received information. This performs the opposite action performed by the encoder more component <b>204</b> of <figref idrefs="DRAWINGS">FIG. 2</figref>. The decoder mode component <b>406</b> can have the capability of checking accuracy of performed decoding. For example, a received bitstream can have information relating to the size a decompressed high-resolution file.
The record component <b>404</b> and decoder mode component <b>406</b> can operate together in multiple manners. According to one embodiment, the record component creates a separate file for received bitstreams in the storage component <b>114</b> of <figref idrefs="DRAWINGS">FIG. 1</figref> automatically. The record component <b>404</b> then transfers the bitstream to the decoder mode component <b>406</b>. As the decoder mode component <b>406</b> decompresses information, the record component <b>404</b> makes a copy of the file and saves it the storage component <b>114</b> of <figref idrefs="DRAWINGS">FIG. 1</figref>.
For example, a bitstream enters the receiving component <b>108</b> and a bitstream begins with standard resolution information. The record component <b>404</b> creates a file folder for the bitstream and sends information to the decoder mode component <b>406</b>. The decoder mode component <b>406</b> decompresses the information. The record component creates a file for the standard resolution in compressed or decompressed format. The record component <b>404</b> can identify a high-resolution marker in the bitstream and create a separate file for high-resolution information. If there is a marker signifying an end to high-resolution information and a return to standard resolution information, then the record component <b>404</b> can create a new file for the standard resolution information or link the information with an original file of the standard resolution.
A processor component <b>408</b> performs actions upon decompressed information. For example, the processor component <b>408</b> can hold the information to assure that it is supplied to a display component <b>410</b> as an equal stream (e.g., supplied so there are few or no gaps or lags in displayed video). The processor component <b>408</b> performs analysis to determine characteristics of captured information. For example, the processor component <b>408</b> can determine if there is a specific format in which information should be displayed (e.g., black and white). Furthermore, the processor component <b>408</b> can determine if information has special characteristics through analysis. For example, high-resolution information can be sent to be added as part of a signature portion of a display. The processor component <b>408</b> can identify this intention and take actions to ensure its completion.
In another embodiment, the processor component <b>408</b> performs intelligent maintenance upon information saved in the storage component <b>114</b> of <figref idrefs="DRAWINGS">FIG. 1</figref>. For example, the record component <b>404</b> can create a file copy of high-resolution information originating from when a user held a document up to a web camera <b>102</b> of <figref idrefs="DRAWINGS">FIG. 1</figref>. Information commonly enters the receiving component as video. However, high-resolution information can be used to show a document. The processor component <b>408</b> can change the file from a video of a displayed document to a document format (e.g., portable document format) through intelligent analysis of information stored in the storage component <b>114</b> of <figref idrefs="DRAWINGS">FIG. 1</figref>.
A verification component <b>412</b> can check information for accuracy and/or validity. For example, information can enter the receiving component <b>108</b> that should be displayed in high-resolution. However, the information is processed to display in standard resolution. The verification component <b>412</b> can determine this error and attempt to correct the error. In another embodiment, the verification component <b>412</b> can check properties of the display component <b>410</b>. For example, high-resolution information is intended to be displayed at ‘X’ resolution. However, the display component <b>410</b> can only display information at ‘Y’ resolution, where ‘Y’ resolution is an inferior resolution to ‘X’ resolution. The verification component <b>412</b> can adjust information to allow it to display at the highest resolution possible within capabilities of the display component <b>410</b>. For example, the verification component <b>412</b> can attempt to display information in an optimal resolution. For example, if information cannot be displayed at the highest resolution, the verification component <b>412</b> can allow for displaying information at a highest resolution possible.
Ultimately, information is presented on a display component <b>410</b>. According to one embodiment, displaying the higher resolution frame is done after a receiving user has been notified that there is such high-resolution information available for perception and he/she has accepted. Likewise, a receiving user can see the higher resolution when he/she has configured his/her system to execute the presentment of such higher resolution information. For example, the display component <b>410</b> can be a monitor with a visual display. However, there can be other embodiments for the display component <b>410</b>. For example, the display component <b>410</b> can be a printer that creates images based on a video feed. The printer can produce images that are both standard resolution and high-resolution. In a further embodiment, the display component <b>410</b> can integrate into the receiving component <b>108</b>.
This display component <b>410</b> can also function outside of visual presentment. For example, the display component can be a set of speakers. Furthermore, the display component <b>410</b> can convert display types. For example, information perceived as sound can be presented as text (e.g., text can be transcribed in the processor component <b>408</b>). The display component <b>410</b> can display information in two different resolution levels (e.g., a lower resolution level and a higher resolution level). In another embodiment, the display component <b>410</b> presents information in two different resolution levels of two different types (e.g., one audio resolution and one visual resolution).
There can be a contact component <b>414</b> that stores received information associated with an identifier. For example, the processor component <b>408</b> identifies that a high-resolution image was received that is to be used for identification purposes (e.g., for display next a name of a participant). The contact component <b>414</b> can create a record of the image as well as identification information (e.g., what person the image associates). In a later communication session, the same identifier can be used for a person without a need to recapture a high-resolution image. While shown as part of the processor component <b>408</b>, the contact component <b>414</b> can operate alone or in conjunction with other components.
<figref idrefs="DRAWINGS">FIG. 5</figref><i>a </i>to <figref idrefs="DRAWINGS">FIG. 5</figref><i>c </i>discloses example multi-image captures. These multi-image captures can be processed by the multi-image component <b>216</b> of <figref idrefs="DRAWINGS">FIG. 2</figref>. The figures display eight points: four white points <b>502</b><i>a</i>-<i>d </i>and four black points <b>504</b><i>a</i>-<i>d</i>. A pixel <b>506</b> of a web camera <b>102</b> of <figref idrefs="DRAWINGS">FIG. 1</figref> can contain four points at one time. <figref idrefs="DRAWINGS">FIG. 5</figref><i>a </i>discloses a first frame where the web camera <b>102</b> of <figref idrefs="DRAWINGS">FIG. 1</figref> captures the four white points <b>502</b><i>a</i>-<i>d</i>. The receiving component would not know information concerning what is to the right of the area capture, so white would be displayed to a user.
After a slight movement for the web camera <b>102</b> of <figref idrefs="DRAWINGS">FIG. 1</figref>, <figref idrefs="DRAWINGS">FIG. 5</figref><i>b </i>discloses that the web camera <b>102</b> of <figref idrefs="DRAWINGS">FIG. 1</figref> now captures two white points <b>502</b><i>b </i>and <b>502</b><i>d </i>as well as two black points <b>504</b><i>a </i>and <b>504</b><i>c </i>with the pixel <b>506</b>. Now it is known that the white points border black points. Therefore, the multi-image component <b>216</b> of <figref idrefs="DRAWINGS">FIG. 2</figref> can create a more accurate image. For example, since it is known that two white points and two black points border each other, a gray may be a proper color for representation.
If the movement continues, the web camera <b>102</b> of <figref idrefs="DRAWINGS">FIG. 1</figref> can capture further right, which is shown by <figref idrefs="DRAWINGS">FIG. 5</figref><i>c</i>. The pixel <b>506</b> captures that there is a pixel of information that is black since the pixel captures four black points <b>504</b><i>a</i>-<i>d</i>. Therefore, the multi-mage component <b>216</b> of <figref idrefs="DRAWINGS">FIG. 2</figref> can produce information that white is next to black. This can allow for a more detailed image, producing a type of super-resolution. Super-resolution is a resolution that includes details that is greater then can be taken in a single frame (e.g., there should be at least two frames that do not capture the same information).
<figref idrefs="DRAWINGS">FIG. 6</figref> discloses an example presentation <b>600</b> disclosed on a display component <b>410</b> of <figref idrefs="DRAWINGS">FIG. 4</figref>. This could be a display component found if the display component had a monitor with a user interface. A header <b>602</b> provides information for a communication session. For example, there can be a meeting among a board of trustees for a private school. The header can display the text ‘School Name—Trustees Meeting—Date”. This can allow participants to have quick access to general information about the communication session. In another embodiment, the header can provide information as to a file folder of the storage component <b>114</b> of <figref idrefs="DRAWINGS">FIG. 1</figref> where information about the communication session is stored. In a further embodiment, the header <b>602</b> is left blank.
Command targets allow a participant to control an experience of a communication session. A minimization command target <b>604</b> allows the participant to have near-full access or full access to the display component <b>410</b> of <figref idrefs="DRAWINGS">FIG. 4</figref>. A restore down command target <b>606</b> allows the participant to have limited access to the display component <b>410</b> of <figref idrefs="DRAWINGS">FIG. 4</figref>. An exit command target <b>608</b> allows the participant to exit out of the communication session.
Identifiers of the participants can be listed on the display <b>610</b>. Shown in the drawings are the names of two participants <b>610</b><i>a </i>and <b>610</b><i>b</i>. In addition to names <b>610</b><i>a </i>and <b>610</b><i>b</i>, other information can be displayed, such as status or who is the leader of the communication session. However, it is to be appreciated that a number other then two participants can be in a communication session and their names can be listed.
It is possible that at least one participant associate a high-resolution picture <b>612</b><i>a </i>and <b>612</b><i>b </i>associated with his/her name (e.g., located next to their name). A participant can engage the web camera <b>102</b> and the sending component <b>104</b>, both of <figref idrefs="DRAWINGS">FIG. 1</figref>, to capture a high-resolution picture. This commonly is a personal photograph; however, this can be other personal representations, such as a company or personal logo. The high-resolution picture can be sent to a receiving component and displayed in conjunction with a participant's name (e.g., next to the participant's name). Information that the high-resolution picture is to be placed next to the participant's name can be added to the bitstream. In addition, a participant's picture can be saved in the storage component <b>114</b> of <figref idrefs="DRAWINGS">FIG. 1</figref>. For later communication sessions with the same participant, the receiving component <b>108</b> of <figref idrefs="DRAWINGS">FIG. 1</figref> can retrieve the high-resolution picture and display it for any user interface <b>600</b> in the communication session.
For later reference in the communication session, there can be a log of pervious text <b>614</b>. This can be of all text that took place during the communication session or only a partial text listing. According to one embodiment, participants can communicate using microphones. Sounds perceived by the microphone can be processed as text. In another embodiment, a participant communicates through sign language (e.g., American Sign Language) through the web camera <b>102</b> of <figref idrefs="DRAWINGS">FIG. 1</figref>. The processor component <b>210</b> of <figref idrefs="DRAWINGS">FIG. 2</figref> can identify the signs and translate them into text. In a further embodiment, the participant can enter test through a text entry button <b>616</b>. This text can also be transported in the bitstream.
Video feed <b>618</b> allows for display of images capture by the web camera <b>102</b> of <figref idrefs="DRAWINGS">FIG. 1</figref>. If the receiving component <b>108</b> of <figref idrefs="DRAWINGS">FIG. 4</figref> that displays the presentation <b>600</b> has a web camera, then there can be multiple feeds into the video feed <b>618</b>, including the feed the participant is sending. For example, if there are four participants each with web cameras, then there can be four feeds integrated into the video feed <b>618</b>. The video feed can also display images that were not captured with a web camera. Furthermore, the video feed can display a single image, such as a business card that was taken in high resolution as opposed to a live video feed.
<figref idrefs="DRAWINGS">FIG. 7</figref><i>a </i>through <figref idrefs="DRAWINGS">FIG. 7</figref><i>c </i>discloses an example methodology implementing some aspects of the subject specification. While many disclosed details discuss a high-resolution change, it is to be appreciated that details can also be practiced for a lower resolution change. Furthermore, while there are some references to visual capture, there can be other forms of capture (e.g., electromagnetic, audio, etc.). A user at a sending component can select a capture mode <b>702</b>. For example, a user can select between a video capture mode and/or a frame capture mode (e.g., capturing a single frame image). In another embodiment, the user can select between capture types (e.g., visual, audio, heat perception, etc.). A video encoder can be set to produce a changed quality image production <b>704</b>. This prepares an encoder to possibly compress information in a different manner since the resolution has changed and thus captured information will be different (e.g., more detailed). Furthermore, this allows the captured information to be prepared for digital transport.
A switch can take place to set a web camera with a change in quality <b>706</b> (e.g., changing resolution). There is selecting a resolution quality in which to capture information. For example, there can be a setting to capture information at a high spatial resolution then in a standard capture. The setting can take place in a plurality of embodiments. For example, a system can recognize there is a document within a capture area and automatically capture at a higher resolution. In another embodiment, a user can switch a resolution mode manually, including between more then two resolution modes. While high spatial resolution is disclosed, it is to be appreciated that other resolutions can be used.
Once there is proper setting for a high-resolution change, there is engagement of the capture (e.g., the web camera captures desired information) <b>708</b>. This is a high-resolution capture, so more system resources are typically used during the high-resolution capture. As the capture takes place, it is added to a bitstream of information with markers <b>710</b>. Markers are applied to a bitstream made of captured information; markers signify a change in resolution quality of at least one portion of information. Commonly, markers are added to the start of the capture and to the end of the capture. This allows a receiving component to understand that there is a high-resolution image as well as its parameters.
Captured information is processed to determine characteristics and if any actions should take place <b>712</b>. For example, it can be determined if the captured information should be stored. Processing can also include handling information that relates to super-resolution, where information from web camera movement processes to create images that are of a greater resolution (e.g., practices disclose in <figref idrefs="DRAWINGS">FIG. 5</figref><i>a </i>to <figref idrefs="DRAWINGS">FIG. 5</figref><i>c</i>). For example, processing can include processing captured information to create information that is of a super-resolution quality, such as actions performed by the multi-image component <b>216</b> of <figref idrefs="DRAWINGS">FIG. 2</figref> (e.g., more then mere handling and identifying, but creating an image). Furthermore, processing can include associating captured information with an identifier during a communication session, similar to operation of the photograph component <b>208</b> of <figref idrefs="DRAWINGS">FIG. 2</figref>. Yet further, processing can include analyzing captured information to determine characteristics of captured information (e.g., determining at what resolution level information was captured).
Once a high-resolution capture is complete, a standard capture mode can be re-entered <b>714</b>. However, it is possible that a third capture mode be entered. In addition, it is possible that after capturing high-resolution information a capture session end, so no mode is re-entered. A check is performed if captured high-resolution information should be saved <b>716</b>. It is possible that this check take place prior to capture taking place or during a capture session. This can be an automated check or a participant can be asked if they would like to save the capture. If the high-resolution capture is to be saved, then a storage action takes place <b>718</b>.
If no storage takes place, then the methodology <b>700</b> continues to event <b>720</b>. Storage can take place on a sending side, a receiving side, and/or a neutral site (e.g., in a database server). Information that is of standard resolution can also be stored. In addition, there can be intelligent storage of information, where a video image can be saved as a document. For example, there can be a document captured in a video format. Storing captured information <b>718</b> can take the video image, recognize that it is a document, and store the document as a document file. In another embodiment, information is intended to be stored on the receiving side. Therefore, information is added to the bitstream signifying that there should be a storage if the information reaches a receiving component.
There can be specific implementation of features of captured information <b>720</b>. For example, at action <b>712</b>, there can be an association of a high-resolution image to an identifier. The association can take place and the identifier with high-resolution image can be displayed on a sending component or a separate display component <b>720</b> (e.g., the actual placement of the identifier associated with the high-resolution image upon a display component).
Captured high-resolution information is communicated to an auxiliary unit <b>722</b>. Commonly, information communicates to either a router component or a receiving component. Communicating can also include compressing the information and/or encoding the information. Furthermore, this is can be transmitting captured information of both a first resolution and a second resolution during a communication session. The information is also displayed <b>724</b>. Displayed information can take place in a plurality of manners, such as presenting on a monitor or printing on paper.
<figref idrefs="DRAWINGS">FIG. 8</figref> discloses an example methodology <b>800</b> of capturing information. While the actions disclosed are directed to capturing information of a non-standard resolution, actions could apply to standard resolution information. Initially a capture mode is determined <b>802</b>. This is commonly a standard resolution mode or a high-resolution mode, thought the methodology <b>800</b> can take place at a lesser-resolution mode. Once complete, there is a selecting of an quality capture <b>804</b> (e.g., a user selects that there should be a special resolution mode). A specific resolution mode can be set <b>806</b> (e.g., the user selects which mode to use).
Once the mode is set, high-resolution begins. This is shown as automatically starting when a mode is set <b>806</b>, but there can be a separate action that verifies the start. A bitstream is marked so a receiving component can determine that there is a high-resolution image <b>808</b>. Common markers are a beginning marker and an ending marker.
Once a high-resolution capture is complete, a standard capture mode can be re-entered <b>810</b> (e.g., a mode that a web camera starts with when powered on). Captured high-resolution information can be transferred to an auxiliary component <b>812</b>. For example, the bitstream can travel to a receiving component or a router component. Commonly information transfers to a storage component where a record of the high-resolution capture can be stored. It is to be appreciated that information can be sent to multiple locations of different types (e.g., information can both be stored and sent to a router component).
<figref idrefs="DRAWINGS">FIG. 9</figref> discloses an example methodology <b>900</b> of receiving captured information. While the actions disclosed are directed to capturing information of a non-standard resolution, actions could apply to standard resolution information. Action <b>902</b> allows for reception of information. This can take place through a number of different embodiments. In one embodiment, a system simply needs to be turned on in order to receive information from a dedicated Internet Protocol (IP) network. In another embodiment, a receiving component can connect to the Internet. In a further embodiment, there needs to be a direct peer-to-peer initialization with a sending component.
Information that was captured can be received as a bitstream <b>904</b>. High-resolution information can be inserted into a standard bitstream. Therefore, a typical bitstream has markers in it to signify when there is high-resolution information. Therefore, there is usually a reading of markers to identify where a specific capture beings and ends <b>906</b>.
There can be storage of high-resolution capture information <b>908</b>. While this is shown as an action <b>908</b>, it can be practiced as a check similar to check <b>716</b> of <figref idrefs="DRAWINGS">FIG. 7</figref><i>b</i>. Information that is of standard resolution can also be stored. In addition, there can be intelligent storage of information, where a video image can be saved as a document. For example, there can be a document captured in a video format. Storing captured information <b>908</b> can take the video image, recognize that it is a document, and store the document as a document file. Ultimately, information received though the bitstream can be displayed <b>910</b>. In one embodiment, both standard resolution information and high-resolution information is displayed. There can be another check if information can be displayed at an intended resolution. Depending on this, captured information can be modified accordingly.
<figref idrefs="DRAWINGS">FIG. 10</figref> discloses an example methodology <b>1000</b> of sending information at different resolutions. There is a transmission of information captured during a communication session at a first resolution level <b>1002</b>. In common operation, the first resolution level is a relatively low-resolution level. This allows for faster operation and a consumption of less resources.
A change of resolution level takes place during the communication session <b>1004</b>. There can be an automatic change in resolution or a manual change. Typically, the change is to a higher resolution level. There is a transmission of additional captured information at a second resolution during the communication session <b>1006</b>. Typically, this is of a higher resolution level then information transmitted during event <b>1002</b>. Actions disclosed in the methodology <b>1000</b> can integrate with actions disclosed in other methodologies. For example, action <b>1006</b> can integrate with applying markers to a bitstream <b>808</b> of <figref idrefs="DRAWINGS">FIG. 8</figref>. Furthermore, actions <b>702</b>-<b>720</b> of <figref idrefs="DRAWINGS">FIG. 7</figref> can operate in line with the methodology <b>1000</b>.
Referring now to <figref idrefs="DRAWINGS">FIG. 11</figref>, there is illustrated a schematic block diagram of a computing environment <b>1100</b> in accordance with the subject specification. The system <b>1100</b> includes one or more client(s) <b>1102</b>. The client(s) <b>1102</b> can be hardware and/or software (e.g., threads, processes, computing devices). The client(s) <b>1102</b> can house cookie(s) and/or associated contextual information by employing the specification, for example.
The system <b>1100</b> also includes one or more server(s) <b>1104</b>. The server(s) <b>1104</b> can also be hardware and/or software (e.g., threads, processes, computing devices). The servers <b>1104</b> can house threads to perform transformations by employing the specification, for example. One possible communication between a client <b>1102</b> and a server <b>1104</b> can be in the form of a data packet adapted to be transmitted between two or more computer processes. The data packet may include a cookie and/or associated contextual information, for example. The system <b>1100</b> includes a communication framework <b>1106</b> (e.g., a global communication network such as the Internet) that can be employed to facilitate communications between the client(s) <b>1102</b> and the server(s) <b>1104</b>.
Communications can be facilitated via a wired (including optical fiber) and/or wireless technology. The client(s) <b>1102</b> are operatively connected to one or more client data store(s) <b>1108</b> that can be employed to store information local to the client(s) <b>1102</b> (e.g., cookie(s) and/or associated contextual information). Similarly, the server(s) <b>1104</b> are operatively connected to one or more server data store(s) <b>1110</b> that can be employed to store information local to the servers <b>1104</b>.
Referring now to <figref idrefs="DRAWINGS">FIG. 12</figref>, there is illustrated a block diagram of a computer operable to execute the disclosed architecture. In order to provide additional context for various aspects of the subject specification, <figref idrefs="DRAWINGS">FIG. 12</figref> and the following discussion are intended to provide a brief, general description of a suitable computing environment <b>1200</b> in which the various aspects of the specification can be implemented. While the specification has been described above in the general context of computer-executable instructions that may run on one or more computers, those skilled in the art will recognize that the specification also can be implemented in combination with other program modules and/or as a combination of hardware and software.
Generally, program modules include routines, programs, components, data structures, etc., that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the inventive methods can be practiced with other computer system configurations, including single-processor or multiprocessor computer systems, minicomputers, mainframe computers, as well as personal computers, hand-held computing devices, microprocessor-based or programmable consumer electronics, and the like, each of which can be operatively coupled to one or more associated devices.
The illustrated aspects of the specification may also be practiced in distributed computing environments where certain tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules can be located in both local and remote memory storage devices.
A computer typically includes a variety of computer-readable media. Computer-readable media can be any available media that can be accessed by the computer and includes both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer-readable media can comprise computer storage media and communication media. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the computer.
Communication media typically embodies computer-readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism, and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of the any of the above should also be included within the scope of computer-readable media.
With reference again to <figref idrefs="DRAWINGS">FIG. 12</figref>, the example environment <b>1200</b> for implementing various aspects of the specification includes a computer <b>1202</b>, the computer <b>1202</b> including a processing unit <b>1204</b>, a system memory <b>1206</b> and a system bus <b>1208</b>. The system bus <b>1208</b> couples system components including, but not limited to, the system memory <b>1206</b> to the processing unit <b>1204</b>. The processing unit <b>1204</b> can be any of various commercially available processors. Dual microprocessors and other multi-processor architectures may also be employed as the processing unit <b>1204</b>.
The system bus <b>1208</b> can be any of several types of bus structure that may further interconnect to a memory bus (with or without a memory controller), a peripheral bus, and a local bus using any of a variety of commercially available bus architectures. The system memory <b>1206</b> includes read-only memory (ROM) <b>1210</b> and random access memory (RAM) <b>1212</b>. A basic input/output system (BIOS) is stored in a non-volatile memory <b>1210</b> such as ROM, EPROM, EEPROM, which BIOS contains the basic routines that help to transfer information between elements within the computer <b>1202</b>, such as during start-up. The RAM <b>1212</b> can also include a high-speed RAM such as static RAM for caching data.
The computer <b>1202</b> further includes an internal hard disk drive (HDD) <b>1214</b> (e.g., EIDE, SATA), which internal hard disk drive <b>1214</b> may also be configured for external use in a suitable chassis (not shown), a magnetic floppy disk drive (FDD) <b>1216</b>, (e.g., to read from or write to a removable diskette <b>1218</b>) and an optical disk drive <b>1220</b>, (e.g., reading a CD-ROM disk <b>1222</b> or, to read from or write to other high capacity optical media such as the DVD). The hard disk drive <b>1214</b>, magnetic disk drive <b>1216</b> and optical disk drive <b>1220</b> can be connected to the system bus <b>1208</b> by a hard disk drive interface <b>1224</b>, a magnetic disk drive interface <b>1226</b> and an optical drive interface <b>1228</b>, respectively. The interface <b>1224</b> for external drive implementations includes at least one or both of Universal Serial Bus (USB) and IEEE 1394 interface technologies. Other external drive connection technologies are within contemplation of the subject specification.
The drives and their associated computer-readable media provide nonvolatile storage of data, data structures, computer-executable instructions, and so forth. For the computer <b>1202</b>, the drives and media accommodate the storage of any data in a suitable digital format. Although the description of computer-readable media above refers to a HDD, a removable magnetic diskette, and a removable optical media such as a CD or DVD, it should be appreciated by those skilled in the art that other types of media which are readable by a computer, such as zip drives, magnetic cassettes, flash memory cards, cartridges, and the like, may also be used in the example operating environment, and further, that any such media may contain computer-executable instructions for performing the methods of the specification.
A number of program modules can be stored in the drives and RAM <b>1212</b>, including an operating system <b>1230</b>, one or more application programs <b>1232</b>, other program modules <b>1234</b> and program data <b>1236</b>. All or portions of the operating system, applications, modules, and/or data can also be cached in the RAM <b>1212</b>. It is appreciated that the specification can be implemented with various commercially available operating systems or combinations of operating systems.
A user can enter commands and information into the computer <b>1202</b> through one or more wired/wireless input devices, e.g., a keyboard <b>1238</b> and a pointing device, such as a mouse <b>1240</b>. Other input devices (not shown) may include a microphone, an IR remote control, a joystick, a game pad, a stylus pen, touch screen, or the like. These and other input devices are often connected to the processing unit <b>1204</b> through an input device interface <b>1242</b> that is coupled to the system bus <b>1208</b>, but can be connected by other interfaces, such as a parallel port, an IEEE 1394 serial port, a game port, a USB port, an IR interface, etc.
A monitor <b>1244</b> or other type of display device is also connected to the system bus <b>1208</b> via an interface, such as a video adapter <b>1246</b>. In addition to the monitor <b>1244</b>, a computer typically includes other peripheral output devices (not shown), such as speakers, printers, etc.
The computer <b>1202</b> may operate in a networked environment using logical connections via wired and/or wireless communications to one or more remote computers, such as a remote computer(s) <b>1248</b>. The remote computer(s) <b>1248</b> can be a workstation, a server computer, a router, a personal computer, portable computer, microprocessor-based entertainment appliance, a peer device or other common network node, and typically includes many or all of the elements described relative to the computer <b>1202</b>, although, for purposes of brevity, only a memory/storage device <b>1250</b> is illustrated. The logical connections depicted include wired/wireless connectivity to a local area network (LAN) <b>1252</b> and/or larger networks, e.g., a wide area network (WAN) <b>1254</b>. Such LAN and WAN networking environments are commonplace in offices and companies, and facilitate enterprise-wide computer networks, such as intranets, all of which may connect to a global communications network, e.g., the Internet.
When used in a LAN networking environment, the computer <b>1202</b> is connected to the local network <b>1252</b> through a wired and/or wireless communication network interface or adapter <b>1256</b>. The adapter <b>1256</b> may facilitate wired or wireless communication to the LAN <b>1252</b>, which may also include a wireless access point disposed thereon for communicating with the wireless adapter <b>1256</b>.
When used in a WAN networking environment, the computer <b>1202</b> can include a modem <b>1258</b>, or is connected to a communications server on the WAN <b>1254</b>, or has other means for establishing communications over the WAN <b>1254</b>, such as by way of the Internet. The modem <b>1258</b>, which can be internal or external and a wired or wireless device, is connected to the system bus <b>1208</b> via the serial port interface <b>1242</b>. In a networked environment, program modules depicted relative to the computer <b>1202</b>, or portions thereof, can be stored in the remote memory/storage device <b>1250</b>. It will be appreciated that the network connections shown are example and other means of establishing a communications link between the computers can be used.
The computer <b>1202</b> is operable to communicate with any wireless devices or entities operatively disposed in wireless communication, e.g., a printer, scanner, desktop and/or portable computer, portable data assistant, communications satellite, any piece of equipment or location associated with a wirelessly detectable tag (e.g., a kiosk, news stand, restroom), and telephone. This includes at least Wi-Fi and Bluetooth™ wireless technologies. Thus, the communication can be a predefined structure as with a conventional network or simply an ad hoc communication between at least two devices.
Wi-Fi, or Wireless Fidelity, allows connection to the Internet from a couch at home, a bed in a hotel room, or a conference room at work, without wires. Wi-Fi is a wireless technology similar to that used in a cell phone that enables such devices, e.g., computers, to send and receive data indoors and out; anywhere within the range of a base station. Wi-Fi networks use radio technologies called IEEE 802.11 (a, b, g, etc.) to provide secure, reliable, fast wireless connectivity. A Wi-Fi network can be used to connect computers to each other, to the Internet, and to wired networks (which use IEEE 802.3 or Ethernet). Wi-Fi networks operate in the unlicensed 2.4 and 5 GHz radio bands, at an 11 Mbps (802.11a) or 54 Mbps (802.11b) data rate, for example, or with products that contain both bands (dual band), so the networks can provide real-world performance similar to the basic 10BaseT wired Ethernet networks used in many offices.
What has been described above includes examples of the present specification. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing the present specification, but one of ordinary skill in the art may recognize that many further combinations and permutations of the present specification are possible. Accordingly, the present specification is intended to embrace all such alterations, modifications and variations that fall within the spirit and scope of the appended claims. Furthermore, to the extent that the term “includes” is used in either the detailed description or the claims, such term is intended to be inclusive in a manner similar to the term “comprising” as “comprising” is interpreted when employed as a transitional word in a claim.
Contents5
15 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13 Sheet 14 Sheet 15
Every citation, both waysCites: the store holds 19 of 20
| Document | Relation | Office | Cited during |
|---|---|---|---|
| USD1023115S | Cited by | United States of America | Applicant |
| US9596388B2 | Cited by | United States of America | Applicant |
| US12399419B2 | Cited by | United States of America | Applicant |
| USD1090676S | Cited by | United States of America | Applicant |
| USD989165S | Cited by | United States of America | Applicant |
| US9699360B2 | Cited by | United States of America | Applicant |
| US10986253B2 | Cited by | United States of America | Applicant |
| USD1096914S | Cited by | United States of America | Applicant |
| USD1100025S | Cited by | United States of America | Applicant |
| USD991318S | Cited by | United States of America | Applicant |
| USD894256S | Cited by | United States of America | Applicant |
| US12321084B2 | Cited by | United States of America | Applicant |
| USD997232S | Cited by | United States of America | Applicant |
| USD1036536S | Cited by | United States of America | Applicant |
| USD1004676S | Cited by | United States of America | Applicant |
| US11025802B2 | Cited by | United States of America | Applicant |
| US11662651B2 | Cited by | United States of America | Applicant |
| USD905786S | Cited by | United States of America | Applicant |
| US10356291B2 | Cited by | United States of America | Applicant |
| US12041326B2 | Cited by | United States of America | Applicant |
| USD1079788S | Cited by | United States of America | Applicant |
| USD1107775S | Cited by | United States of America | Applicant |
| US12379650B2 | Cited by | United States of America | Applicant |
| US10928711B2 | Cited by | United States of America | Applicant |
| USD1024165S | Cited by | United States of America | Applicant |
| US2003052986A1 | Cites | United States of America | Search report |
| US2003069752A1 | Cites | United States of America | Search report |
| US2004119814A1 | Cites | United States of America | Search report |
| US2004233282A1 | Cites | United States of America | Search report |
| US2004257431A1 | Cites | United States of America | Applicant |
| US2005104864A1 | Cites | United States of America | Applicant |
| US2005213739A1 | Cites | United States of America | Applicant |
| US2006268117A1 | Cites | United States of America | Search report |
| US2007147820A1 | Cites | United States of America | Search report |
| US5801758A | Cites | United States of America | Applicant |
| US6259470B1 | Cites | United States of America | Applicant |
| US6380967B1 | Cites | United States of America | Applicant |
| US6678000B1 | Cites | United States of America | Search report |
| US6686956B1 | Cites | United States of America | Search report |
| US6788347B1 | Cites | United States of America | Search report |
| US7054904B2 | Cites | United States of America | Applicant |
| US7119829B2 | Cites | United States of America | Applicant |
| US7152093B2 | Cites | United States of America | Applicant |
| US7495689B2 | Cites | United States of America | Search report |
| Chiu, et al., NoteLook: taking notes in meetings with digital video and ink, http://delivery.acm.org/10.1145/320000/319483/p149-chiu.pdf?key1=319483&key2=0531412711&coll=GUIDE&dl=GUIDE&CFID=15015622&CFTOKEN=28553473, 1999, ACM Press, New York, NY, USA, 10 pages. | Non-patent | – | Applicant |
| Adam, et al., The Vidboard: a video capture and processing peripheral for a distributed multimedia system, http://portal.acm.org/ft-gateway.cfm?id=166279&type=ps&coll=GUIDE&dI=GUIDE&CFID=15015622&CFTOKEN=28553473, MIT Laboratory for Computer Science, 8 pages,1993. | Non-patent | – | Applicant |
| Zhang, et al., A Mobile Teleconference System for Homecare Services, http://ieeexplore.ieee.org/xpl/freeabs-all.jsp?arnumber=1615322, Sep. 2005, 4 pages The University of Aizu, Aizu-Wakamatsu, Fukushima-ken 965-8580, Japan. | Non-patent | – | Applicant |
| Srinivas, et al., MONET: A Multi-media System for Conferencing and Application Sharing in Distributed Systems, http://www.cerc.wvu.edu/cercdocs/techReports/1991/cerc-tr-rn-91-009.pdf, Feb. 1992, 19 pages, Concurrent Engineering Research Center West Virginia University, Morgantown West Virginia, USA. | Non-patent | – | Applicant |
2 members in 1 office
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 74008107 | United States of America | A | |
| US20070740081 | – | – | – |
Members2
| Document | Office | Kind | |
|---|---|---|---|
| US2008266411A1 | United States of America | A1 | |
| US8031222B2This record | United States of America | B2 |
80 transactions on the USPTO file
Allowed after 2 non-final rejections, 3 final rejections and 1 RCE.
- Non-final rejections
- 2
- Final rejections
- 3
- RCEs
- 1
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Payment of Maintenance Fee, 12th Year, Large EntityM1553 | M1553 | |
| Correspondence Address ChangeC.ADB | C.ADB | |
| Payment of Maintenance Fee, 8th Year, Large EntityM1552 | M1552 | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Email NotificationEML_NTR | EML_NTR | |
| 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 | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail Examiner Interview Summary (PTOL - 413)MEXIN | MEXIN | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Final ActionA.NE | A.NE | |
| Examiner Interview Summary Record (PTOL - 413)EXIN | EXIN | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail Advisory Action (PTOL - 303)MCTAV | MCTAV | |
| Advisory Action (PTOL-303)CTAV | CTAV | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Final ActionA.NE | A.NE | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Final ActionA.NE | A.NE | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Email NotificationEML_NTR | EML_NTR | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Correspondence Address ChangeC.AD | C.AD | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Email NotificationEML_NTR | EML_NTR | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| IFW TSS Processing by Tech Center CompleteTSSCOMP | TSSCOMP | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Sent to Classification ContractorPGPC | PGPC | |
| Receipt of all Acknowledgement LettersL130 | L130 | |
| Receipt of Acknowledgment LetterL197 | L197 | |
| Waiting LR clearancePGPW | PGPW | |
| Application Is Now CompleteCOMP | COMP | |
| Agency Referral Letter MailedML196 | ML196 | |
| Referred by L&R for Third-Level Security Review. Agency Referral Letter GeneratedL196 | L196 | |
| Referred to Level 2 (LARS) by OIPE CSRL198 | L198 | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Initial Exam Team nnIEXX | IEXX |
6 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Maintenance fee paymentMAFP | MAFP | |
| Maintenance fee paymentMAFP | MAFP | |
| Fee paymentFPAY | FPAY | |
| AssignmentAS | AS | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| AssignmentAS | AS |
Numbers
- Publication
- 08031222
- Publication, DOCDB
- 8031222
- Publication, EPODOC
- US8031222
- Application
- 11740081
- Application, DOCDB
- 74008107
- Application, EPODOC
- US20070740081
Titles
- English
- Multiple resolution capture in real time communications
Patent term adjustment
- A delay
- +427 daysthe office missed an examination deadline
- B delay
- +106 dayspendency past three years
- Applicant delay
- −15 days
- Net adjustment
- 518 days
Classification
- CPC, 3
- H04L67/565
- H04N23/667
- H04L67/56
- IPC, 2
- H04N7 14
- H04N23 40
- USPC, 2
- 348014120
- 348222100