US20170127067A1 - Run-length encoded image decompressor for a remote desktop protocol client in a standards-based web browser - Google Patents
Run-length encoded image decompressor for a remote desktop protocol client in a standards-based web browser Download PDFInfo
- Publication number
- US20170127067A1 US20170127067A1 US14/930,323 US201514930323A US2017127067A1 US 20170127067 A1 US20170127067 A1 US 20170127067A1 US 201514930323 A US201514930323 A US 201514930323A US 2017127067 A1 US2017127067 A1 US 2017127067A1
- Authority
- US
- United States
- Prior art keywords
- color space
- packet
- rdp
- client
- server
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N19/00—Methods or arrangements for coding, decoding, compressing or decompressing digital video signals
- H04N19/10—Methods or arrangements for coding, decoding, compressing or decompressing digital video signals using adaptive coding
- H04N19/169—Methods or arrangements for coding, decoding, compressing or decompressing digital video signals using adaptive coding characterised by the coding unit, i.e. the structural portion or semantic portion of the video signal being the object or the subject of the adaptive coding
- H04N19/186—Methods or arrangements for coding, decoding, compressing or decompressing digital video signals using adaptive coding characterised by the coding unit, i.e. the structural portion or semantic portion of the video signal being the object or the subject of the adaptive coding the unit being a colour or a chrominance component
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N19/00—Methods or arrangements for coding, decoding, compressing or decompressing digital video signals
- H04N19/90—Methods or arrangements for coding, decoding, compressing or decompressing digital video signals using coding techniques not provided for in groups H04N19/10-H04N19/85, e.g. fractals
- H04N19/93—Run-length coding
Abstract
Description
- This disclosure relates generally to a decompressor for a remote desktop protocol client (RDP) and, more particularly, to run-length encoded image decompressor for an RDP client in a web browser, such as a standards-based web browser.
- As the value and use of information continues to increase, individuals and businesses seek additional ways to process and store information. One option available to users is information handling systems. An information handling system generally processes, compiles, stores, and/or communicates information or data for business, personal, or other purposes thereby allowing users to take advantage of the value of the information. Because technology and information handling needs and requirements vary between different users or applications, information handling systems may also vary regarding what information is handled, how the information is handled, how much information is processed, stored, or communicated, and how quickly and efficiently the information may be processed, stored, or communicated. The variations in information handling systems allow for information handling systems to be general or configured for a specific user or specific use such as financial transaction processing, airline reservations, enterprise data storage, or global communications. In addition, information handling systems may include a variety of hardware and software components that may be configured to process, store, and communicate information and may include one or more information handling systems, data storage systems, and networking systems.
- In desktop virtualization or remote working environments, a remote server provides desktop and application resources to a user. The desktop or application resources are published to the user's computing device by way of a protocol, such as the remote desktop protocol (RDP). The remote desktop or application may be displayed on a user's computing device using a web browser, such as a standards-based web browser. However, standards-based web browsers have limited support for graphics formats, and are not capable of natively rendering the graphics information contained in an RDP data packet. To provide access to a remote desktop or application resource using a standards-based web browser, an implementation of RDP graphics in a standards-based web browser is used. Because RDP graphics are compressed using run-length encoding, a decompressor is needed to display the graphics in a web browser. The present invention provides an efficient decompressor for displaying graphics in a web browser.
- Traditionally, RDP clients are written in a native, full-featured programming language such as C or C++. In such an environment, the native RDP client may utilize an operating system's graphics library to display graphics information. Many operating systems support 8, 16, 24 and 32-bit color spaces. For such operating systems, it is unnecessary to convert between color spaces when RDP graphics data in 8, 16, 24, or 32-bit color space is received from the remote server. However, web browsers compatible with hypertext markup language (HTML) 5 (HTML5) and CANVAS only support a 32-bit color space. Thus, it is necessary to convert graphics received in an 8, 16, or 24-bit color space to a 32-bit color space for rendering by a web browser. But, it may be difficult to accomplish color space conversion in a scripting language such as JAVASCRIPT as the environment runs within a limited host environment provided by the web browser where the operating systems graphics library is not accessible and does not permit pointer operations and manipulations. The present invention provides for drawing or rendering images, such as graphical data comprising, for example, audio or video, or content within such an environment.
- In one embodiment, a packet is received at a web client, where the packet comprises graphics data. The graphics data may be any type of graphics data including, but not limited to, audio data, video data, and teleconferencing data. The packet may be a Protocol Data Unit (PDU). The packet is encoded using run-length encoding. The web client may receive the packet from a remote desktop protocol (RDP) server via a web-socket server. A run-length encoding algorithm for the received packet is determined based, at least in part, on a first color space associated with the packet. It is determined if the first color space is supported and the decompressed packet is converted from the first color space to the supported color space if the first color space is not supported. The first color space may be an 8-bit, 16-bit, 24-bit or 32-bit color space. The second color space may be a 32-bit color space; the color space supported by hypertext markup language 5 (HTML5) and CANVAS. The packet is decompressed based, at least in part, on the determined run-length encoding algorithm. Decompressing the packet includes determining a plurality of commands to be performed on a canvas associated with the web client. The decompressed packet is converted by using a selected color space algorithm, wherein the selected color space algorithm is based, at least in part, on the first color space and the supported color space. The packet is decompressed by determining a selected color space algorithm, where the selected color space algorithm is based, at least in part, on the first color space and the supported color space. The packet may be decompressed using a scripting language, such as HTML5. The graphics data of the decompressed packet is rendered on the canvas using the plurality of commands. The graphics data is associated with a graphical interface for viewing and interacting with a remote desktop.
- In one embodiment an information handling system comprises one or more processors and a memory coupled to the processors comprising instructions executable by the processors, the processors operable when executing the instruction to perform or implement one or more embodiments. In one embodiment, one or more computer-readable non-transitory storage media embodying software that is operable when executed performs or implements one or more embodiments.
- For a more complete understanding of the present invention and its features and advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:
-
FIG. 1 is a block diagram of selected elements of an information handling system. -
FIG. 2 is an example of a network environment. -
FIG. 3A is an example of a network environment utilizing Remote Desktop Protocol. -
FIG. 3B is an example of a network environment utilizing Remote Desktop Protocol. -
FIG. 4 is an example web-socket server environment. -
FIG. 5 is an example method according to one or more embodiments of the present disclosure. -
FIG. 6 is an example method according to one or more embodiments of the present disclosure. -
FIG. 7 is an example method according to one or more embodiments of the present disclosure. - The detailed description set forth below is intended as a description of various configurations of the subject technology and is not intended to represent the only configurations in which the subject technology may be practiced. The appended drawings are incorporated herein and constitute a part of the detailed description. The detailed description includes specific details for the purpose of providing a thorough understanding of the subject technology. However, it will be apparent to those skilled in the art that the subject technology may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring the concepts of the subject technology.
- In the following description, details are set forth by way of example to facilitate discussion of the disclosed subject matter. It should be apparent to a person of ordinary skill in the field, however, that the disclosed embodiments are exemplary and not exhaustive of all possible embodiments.
- For the purposes of this disclosure, an information handling system may include an instrumentality or aggregate of instrumentalities operable to compute, classify, process, transmit, receive, retrieve, originate, switch, store, display, manifest, detect, record, reproduce, handle, or utilize various forms of information, intelligence, or data for business, scientific, control, entertainment, or other purposes. For example, an information handling system may be a personal computer, a PDA, a consumer electronic device, a network storage device, or another suitable device and may vary in size, shape, performance, functionality, and price. The information handling system may include memory, one or more processing resources such as a central processing unit (CPU) or hardware or software control logic. Additional components or the information handling system may include one or more storage devices, one or more communications ports for communicating with external devices as well as various input and output (I/O) devices, such as a keyboard, a mouse, and a video display. The information handling system may also include one or more buses operable to transmit communication between the various hardware components.
- Herein, a computer-readable non-transitory storage medium or media may include one or more semiconductor-based or other integrated circuits (ICs) (such, as for example, field-programmable gate arrays (FPGAs) or application-specific ICs (ASICs)), hard disk drives (HDDs), hybrid hard drives (HHDs), optical discs, optical disc drives (ODDs), magneto-optical discs, magneto-optical drives, floppy diskettes, floppy disk drives (FDDs), magnetic tapes, solid-state drives (SSDs), RAM-drives, SECURE DIGITAL cards or drives, any other suitable computer-readable non-transitory storage media, or any suitable combination of two or more of these, where appropriate. A computer-readable non-transitory storage medium may be volatile, non-volatile, or a combination of volatile and non-volatile, where appropriate.
- In many instances, a remote desktop or application is displayed on an I/O device of a client associated with a user using a web browser, such as a standards-based web browser. A remote server provides desktop and applications resources to the client. The desktop or application resources are published to the user's computing device by way of a protocol, such as the remote desktop protocol (RDP). Many web browsers, such as standards-based web browsers, have limited support for graphics formats and may not be capable of natively rendering the graphics information contained in a RDP data packet. To provide access to a remote desktop or application resource using a standards-based web browser, an implementation of RDP graphics in a standards-based web browser is used. Because RDP graphics are compressed using run-length encoding, a decompressor is needed to display the graphics in a web browser. It may be advantageous to determine the color space and run-length encoding algorithm of a received packet. The packet may then be decompressed at the client using this information and the graphics data or content rendered at the I/O device at the client. The standards-based web-browser may also have limited support for graphics formats and may not be capable of natively rendering graphics information contained in an RDP data packet. For example, native RDP graphics support various size color spaces (8, 16, 24, and 32-bit) while an HTML5 CANVAS compatible web browser only supports a 32-bit color space. To provide access to a remote desktop or application resource using a standards-based web browser, real-time color space conversion to convert graphics to a 32-bit color space is required. Thus, it is necessary to convert graphics received in any color space other than a 32-bit color space for rendering by the web browser. Array indexes may be calculated instead of using pointer operations to perform such conversion as a scripting language, such as JAVASCRIPT, does not permit pointer operation.
- Further, scripting languages run in a limited environment provided by the web browser which does not generally permit access to all of an operating system's libraries, such as the graphics library. Thus, the scripting language must transform the graphics described by the RDP data packet into constructs that are understandable by a web browser. The web browser then can utilize the operating system's graphics library to present the graphics to the user. The RDP packet is decompressed, a color space conversion is applied and the resulting graphics content is drawn on CANVAS for access by a user at a client.
- Particular embodiments are best understood by reference to
FIGS. 1-7 , wherein like numbers are used to indicate like and corresponding parts. -
FIG. 1 illustrates an exampleinformation handling system 100. In particular embodiments, one or moreinformation handling systems 100 perform one or more steps of one or more methods described or illustrated herein. In particular embodiments, one or moreinformation handling systems 100 provide functionality described or illustrated herein. In particular embodiments, software running on one or moreinformation handling systems 100 performs one or more steps of one or more methods described or illustrated herein or provides functionality described or illustrated herein. Particular embodiments include one or more portions of one or moreinformation handling systems 100. Herein, reference to an information handling system may encompass a computing device, and vice versa, where appropriate. Moreover, reference to an information handling system may encompass one or more information handling systems, where appropriate. - This disclosure contemplates any suitable number of
information handling systems 100. This disclosure contemplatesinformation handling system 100 taking any suitable physical form. As example and not by way of limitation,information handling system 100 may be an embedded information handling system, a system-on-chip (SOC), a single-board information handling system (SBC) (such as, for example, a computer-on-module (COM) or system-on-module (SOM)), a desktop information handling system, a laptop or notebook information handling system, an interactive kiosk, a mainframe, a mesh of information handling systems, a mobile telephone, a personal digital assistant (PDA), a server, a tablet information handling system, or a combination of two or more of these. Where appropriate,information handling system 100 may include one or moreinformation handling systems 100; be unitary or distributed; span multiple locations; span multiple machines; span multiple data centers; or reside in a cloud, which may include one or more cloud components in one or more networks. Where appropriate, one or moreinformation handling systems 100 may perform without substantial spatial or temporal limitation one or more steps of one or more methods described or illustrated herein. As an example and not by way of limitation, one or moreinformation handling systems 100 may perform in real time or in batch mode one or more steps of one or more methods described or illustrated herein. One or moreinformation handling systems 100 may perform at different times or at different locations one or more steps of one or more methods described or illustrated herein, where appropriate. - In particular embodiments,
information handling system 100 includes aprocessor 102,memory 104,storage 106, an input/output (I/O)interface 108, acommunication interface 110, and abus 112. Although this disclosure describes and illustrates a particular information handling system having a particular number of particular components in a particular arrangement, this disclosure contemplates any suitable information handling system having any suitable number of any suitable components in any suitable arrangement. - In particular embodiments,
processor 102 includes hardware for executing instructions, such as those making up a computer program. As an example and not by way of limitation, to execute instructions,processor 102 may retrieve (or fetch) the instructions from an internal register, an internal cache,memory 104, orstorage 106; decode and execute them; and then write one or more results to an internal register, an internal cache,memory 104, orstorage 106. In particular embodiments,processor 102 may include one or more internal caches for data, instructions, or addresses. This disclosure contemplatesprocessor 102 including any suitable number of any suitable internal caches, where appropriate. As an example and not by way of limitation,processor 102 may include one or more instruction caches, one or more data caches, and one or more translation lookaside buffers (TLBs). Instructions in the instruction caches may be copies of instructions inmemory 104 orstorage 106, and the instruction caches may speed up retrieval of those instructions byprocessor 102. Data in the data caches may be copies of data inmemory 104 orstorage 106 for instructions executing atprocessor 102 to operate on; the results of previous instructions executed atprocessor 102 for access by subsequent instructions executing atprocessor 102 or for writing tomemory 104 orstorage 106; or other suitable data. The data caches may speed up read or write operations byprocessor 102. The TLBs may speed up virtual-address translation forprocessor 102. In particular embodiments,processor 102 may include one or more internal registers for data, instructions, or addresses. This disclosure contemplatesprocessor 102 including any suitable number of any suitable internal registers, where appropriate. Where appropriate,processor 102 may include one or more arithmetic logic units (ALUs); be a multi-core processor; or include one ormore processors 102. Although this disclosure describes and illustrates a particular processor, this disclosure contemplates any suitable processor. - In particular embodiments,
memory 104 includes main memory for storing instructions forprocessor 102 to execute or data forprocessor 102 to operate on. As an example and not by way of limitation,information handling system 100 may load instructions fromstorage 106 or another source (such as, for example, another information handling system 100) tomemory 104.Processor 102 may then load the instructions frommemory 104 to an internal register or internal cache. To execute the instructions,processor 102 may retrieve the instructions from the internal register or internal cache and decode them. During or after execution of the instructions,processor 102 may write one or more results (which may be intermediate or final results) to the internal register or internal cache.Processor 102 may then write one or more of those results tomemory 104. In particular embodiments,processor 102 executes only instructions in one or more internal registers or internal caches or in memory 104 (as opposed tostorage 106 or elsewhere) and operates only on data in one or more internal registers or internal caches or in memory 104 (as opposed tostorage 106 or elsewhere). One or more memory buses (which may each include an address bus and a data bus) may coupleprocessor 102 tomemory 104.Bus 112 may include one or more memory buses, as described below. In particular embodiments, one or more memory management units (MMUs) reside betweenprocessor 102 andmemory 104 and facilitate accesses tomemory 104 requested byprocessor 102. In particular embodiments,memory 104 includes random access memory (RAM). This RAM may be volatile memory, where appropriate. Where appropriate, this RAM may be dynamic RAM (DRAM) or static RAM (SRAM). Moreover, where appropriate, this RAM may be single-ported or multi-ported RAM. This disclosure contemplates any suitable RAM.Memory 104 may include one ormore memories 104, where appropriate. Although this disclosure describes and illustrates particular memory, this disclosure contemplates any suitable memory. - In particular embodiments,
storage 106 includes mass storage for data or instructions. As an example and not by way of limitation,storage 106 may include a hard disk drive (HDD), a floppy disk drive, flash memory, an optical disc, a magneto-optical disc, magnetic tape, or a Universal Serial Bus (USB) drive or a combination of two or more of these.Storage 106 may include removable or non-removable (or fixed) media, where appropriate.Storage 106 may be internal or external toinformation handling system 100, where appropriate. In particular embodiments,storage 106 is non-volatile, solid-state memory. In particular embodiments,storage 106 includes read-only memory (ROM). Where appropriate, this ROM may be mask-programmed ROM, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), electrically alterable ROM (EAROM), or flash memory or a combination of two or more of these. This disclosure contemplatesmass storage 106 taking any suitable physical form.Storage 106 may include one or more storage control units facilitating communication betweenprocessor 102 andstorage 106, where appropriate. Where appropriate,storage 106 may include one ormore storages 106. Although this disclosure describes and illustrates particular storage, this disclosure contemplates any suitable storage. - In particular embodiments, I/
O interface 108 includes hardware, software, or both, providing one or more interfaces for communication betweeninformation handling system 100 and one or more I/O devices.Information handling system 100 may include one or more of these I/O devices, where appropriate. One or more of these I/O devices may enable communication between a person andinformation handling system 100. As an example and not by way of limitation, an I/O device may include a keyboard, keypad, microphone, monitor, mouse, printer, scanner, speaker, still camera, stylus, tablet, touch screen, trackball, video camera, another suitable I/O device or a combination of two or more of these. An I/O device may include one or more sensors. This disclosure contemplates any suitable I/O devices and any suitable I/O interfaces 108 for them. Where appropriate, I/O interface 108 may include one or more device or softwaredrivers enabling processor 102 to drive one or more of these I/O devices. I/O interface 108 may include one or more I/O interfaces 108, where appropriate. Although this disclosure describes and illustrates a particular I/O interface, this disclosure contemplates any suitable I/O interface. - In particular embodiments,
communication interface 110 includes hardware, software, or both providing one or more interfaces for communication (such as, for example, packet-based communication) betweeninformation handling system 100 and one or more otherinformation handling systems 100 or one or more networks. As an example and not by way of limitation,communication interface 110 may include a network interface controller (NIC) or network adapter for communicating with an Ethernet or other wire-based network or a wireless NIC (WNIC) or wireless adapter for communicating with a wireless network, such as a WI-FI network. This disclosure contemplates any suitable network and anysuitable communication interface 110 for it. As an example and not by way of limitation,information handling system 100 may communicate with an ad hoc network, a personal area network (PAN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), or one or more portions of the Internet or a combination of two or more of these. One or more portions of one or more of these networks may be wired or wireless. As an example,information handling system 100 may communicate with a wireless PAN (WPAN) (such as, for example, a BLUETOOTH WPAN), a WI-FI network, a WI-MAX network, a cellular telephone network (such as, for example, a Global System for Mobile Communications (GSM) network), or other suitable wireless network or a combination of two or more of these.Information handling system 100 may include anysuitable communication interface 110 for any of these networks, where appropriate.Communication interface 110 may include one ormore communication interfaces 110, where appropriate. Although this disclosure describes and illustrates a particular communication interface, this disclosure contemplates any suitable communication interface. - In particular embodiments,
bus 112 includes hardware, software, or both coupling components ofinformation handling system 100 to each other. As an example and not by way of limitation,bus 112 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a front-side bus (FSB), a HYPERTRANSPORT (HT) interconnect, an Industry Standard Architecture (ISA) bus, an INFINIBAND interconnect, a low-pin-count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCIe) bus, a serial advanced technology attachment (SATA) bus, a Video Electronics Standards Association local (VLB) bus, or another suitable bus or a combination of two or more of these.Bus 112 may include one ormore buses 112, where appropriate. Although this disclosure describes and illustrates a particular bus, this disclosure contemplates any suitable bus or interconnect. -
FIG. 2 illustrates an example configuration of networked information handling systems (e.g., client devices and servers). In particular embodiments, one ormore client devices 220 and one ormore servers 240 are connected vianetwork 210.Network 210 may be a public network or a private (e.g., corporate) network. Additionally,network 210 may, for example, be a Local Area Network (LAN), a Wide Area Network (WAN), a wireless network, the Internet, an intranet or any other suitable type of network. In particular embodiments,network 210 may include one or more routers for routing data betweenclient devices 220 and/orservers 240. A device (e.g., aclient device 220 or a server 240) onnetwork 210 may be addressed by a corresponding network address including, for example, an Internet protocol (IP) address, an Internet name, a Windows Internet name service (WINS) name, a domain name or other system name. In particular embodiments,network 210 may include one or more logical groupings of network devices such as, for example, one or more sites (e.g., customer sites) or subnets. As an example, a corporate network may include potentially thousands of offices or branches, each with its own subnet (or multiple subnets) having many devices. One ormore client devices 220 may communicate with one ormore servers 240 via any suitable connection including, for example, a modem connection, a LAN connection including the Ethernet or a broadband WAN connection including DSL, Cable, Ti, T3, Fiber Optics, Wi-Fi, or a mobile network connection including GSM, GPRS, 3G, or WiMax. -
Client device 220 may be a desktop computer, a laptop computer, a tablet computer, a handheld device, a mobile phone, a kiosk, a vending machine, a billboard, or any suitable information handling system. In particular embodiments, aclient device 220 is an embedded computer and may have flash memory (e.g., a solid state drive) instead of a hard disk drive. In particular embodiments, aclient device 220 is a thin client having limited processing capabilities and limited storage, and such a thin client may require minimal management and updates. Aclient device 220 may communicate with aserver 240 via one or more protocols such as Hypertext Transfer Protocol (HTTP), Hypertext Transfer Protocol Secure (HTTPS), File Transfer Protocol (FTP), Common Internet File System (CIFS), Independent Computing Architecture (ICA) protocol (developed by Citrix Systems, Inc.), Remote Desktop Protocol (RDP) (developed by Microsoft Corporation), or any suitable protocol or combination of protocols. - A
server 240 may include one or more of: a computing device, a desktop computer, a laptop computer, a database, a corporate server, a repository server, a configuration application server, a domain name system (DNS) server, a dynamic host configuration protocol (DHCP) server, a virtual machine (e.g., VMware® Virtual Machine), a desktop session (e.g., Microsoft Terminal Server), a published application (e.g., Microsoft Terminal Server), or any suitable information handling system. As an example, a private (e.g., corporate) network may include a device manager server and a repository server each configured to communicate withmultiple client devices 220 across one or more domains, sites, or subnets ofnetwork 210. In particular embodiments, aserver 240 may include one or more servers, or functions of one or more servers. Aclient device 220 may access software resources provided by aserver 240 such as, for example, operating systems, add-ons, content, or any other suitable data, applications, or images. In particular embodiments, aclient 220 may access resources provided by aserver 240 only after providing suitable authentication information. Alternatively, aserver 240 may provide software or other resources automatically to one ormore client devices 220. - It may be desirable, in the case of a private (e.g., corporate) network including multiple sites or subnets to deploy software (including, e.g., all or part of one or more operating systems, applications, add-ons, or data) to one or
more client devices 220 across one or more sites or subnets. Theclient devices 220 may, for example, be located remotely from one or more servers 240 (including, e.g., device managers or resource repositories), and as such, there may be challenges in deploying software or other resources to the client devices. As an example, limited connectivity or limited speed due to bandwidth constraints or network latencies may create delays in deploying software. As another example, remote sites or subnets may not include managed components or may not have any personnel with information technology expertise necessary to implement software deployment to client devices at the sites or subnets. Additionally, as the size of operating system images or other content (e.g., videos) increases, deploying software or other data to remote sites or subnets may be further delayed. These issues may be further exacerbated in the case of embedded computers such as thin clients, which may have limited processing capability and limited storage space. Traditional approaches involving using a static remote software repository for each subnet or site may not be feasible due to cost or management and monitoring requirements. - In particular embodiments, one or
more servers 240 of anetwork 210 may include a device manager that may manage one or more client devices 220 (e.g., thin clients) of one or more sites or subnets of the network. The device manager may, for example, be a software-based management tool that allows for software imaging, software updates, and software configurations to be deployed to the clients from one or more servers. The device manager may also perform any other suitable management function to manage client devices including, for example, enabling or performing (e.g., automatically) device discovery, tracking of assets (e.g., hardware or software inventory) at client devices, monitoring the status or health of client devices, applying one or more policies to client devices (including, e.g., network settings of the client devices), or remote administration and shadowing of client devices. The device manager may deliver any suitable resources including, for example, operating systems, add-ons, content, or any other suitable data, applications, or images to one or morethin client devices 220 ofnetwork 210. - In particular embodiments, a client device such as client device 220 (e.g., a thin client) may be designed with minimal or limited storage capacity (e.g., in a hard disk). The client device may be required, however, to run an operating system such as WINDOWS EMBEDDED or WINDOWS SERVER, but the footprint of such an operating system may grow over time with newer releases or updates. Hence, client devices may, over time, begin to run low on free storage space (e.g., in the hard disk). Unwanted files may be deleted or full volume compression of the storage medium (e.g., the hard disk) may be implemented to increase available storage space. However, full volume compression may introduce performance shortcomings (e.g., increased number of instruction cycles required to compress/uncompress data in the volume) from the point of view of an end user of the client device. In particular embodiments, optimized volume compression may be implemented to reduce effective disk usage on a client device while minimizing impact on system performance.
-
FIG. 3A illustrates a network environment utilizing an application that has virtual channels, which provides a data pathway using a provision of an existing protocol. As an example and not by way of limitation, such an application may be aclient device 220 whereclient device 220 may be anRDP client 220. In particular embodiments,RDP client 220 may be a personal computer, a laptop computer, a thin client, a mobile device, or any other information handling system with an RDP client protocol implementation. In particular embodiments,RDP client 220 may be associated with one or more sites (e.g., subnets) ofnetwork 210. In particular embodiments, communication toservers 240, for example,server 240A,RDP server 240B andserver 240C, may occur through one or more trusted and secure private networks. As an example and not by way of limitation, the trusted and secure private networks may be associated with one or more enterprise networks. In particular embodiments,RDP client 220 ofnetwork 210 may not be secure or trusted. For example,RDP client 220 may be a customer's device, a website visitor's device, or an employee's device (such as in a “bring your own device” environment). As an example and not by way of limitation,network 210 may comprise a public network, such as the Internet, or a third-party network.Network 210 may be untrusted, for example the network may have substantially low security. In order to protectservers 240 against potential security threats fromnetwork 210 andRDP client 220, afirewall 308 may establish one or more barriers that screen incoming and outgoing data traffic betweenservers 240 andRDP client 220. In particular embodiments,firewall 308 may comprise one or more of a software-based network security system or a hardware-based network security system that screen the data traffic according to one or more pre-determined routing rule-sets. In particular embodiments,firewall 308 may comprise one or more network security systems developed by Microsoft Corporation. Furthermore,servers 240 may be deployed using Microsoft Enterprise servers. Herein, reference to the network security systems developed by Microsoft Corporation includes, but is not limited to, Microsoft Enterprise-based firewalls. - Web
socket proxy server 302 may facilitate communications betweenRDP client 220 vianetwork 210 toRDP server 240B. In particular embodiments,RDP server 240B may be a Microsoft Windows server providing Remote Desktop Services. In particular embodiments,RDP server 240B may comprise a device manager that managesRDP client 220, as described above. In particular embodiments,servers 240C may include one or more services that a client-side operation may desire to connect to, or other servers that provide services to be accessed by a client, such asRDP client 220, applications co-located withRDP client 220, a port-forward withinRDP client 220, or virtual network throughRDP client 220. For example,servers 240C may comprise Microsoft Windows servers, Microsoft Enterprise servers, UNIX/LINUX servers, etc. Examples of services provided byservers 240C include, but are not limited to, file sharing, video streaming, audio streaming, database access, instant messaging, telephony, or video conferencing. -
RDP client 220 may create one or more RDPvirtual channels 304 betweenRDP server 240 andRDP client 220 over an established RDP connection. An application at theserver 240 may then communicate withRDP client 220 through thevirtual channel 304.Virtual channel 304 may be utilized to stream video data that includes both audio and video. For example, a user may desire to play an audio stream provided by aserver 240 using an audio player application concurrently running onRDP client 220. To provide access to the remote audio stream, a gateway client located withinRDP client 220 may establish a tunnel and channel using a specialized gateway service attachment through RDPvirtual channel 304 toRDP server 240. TheRDP server 240 may utilize a plug-in that converts all video files to be sent toRDP client 220 as a video streaming data with virtual channel tags. In one embodiment, more than one virtual channel is established. For example, audio may be communicated over onevirtual channel 306 while video is communicated over anothervirtual channel 306. One or morevirtual channels 306 may be a subset ofvirtual channel 304 such that only one virtual channel is established betweenRDP client 220 andRDP server 240. In one embodiment, the audio data or the video data may have higher priority. For example, video data may have a higher priority than the audio data. When theRDP client 220 receives the video data it runs the video data through a queue and determines that the video data has a high priority soRDP client 220 adds the video data to a video worker thread and then adds the audio data to an audio worker thread. - In the example network environment of
FIG. 3B , one or more RDP virtual channels is used to create a virtual private network betweenRDP client 220 and one ormore servers 240C, by attaching gateway functions (gateway client (GWc)//gateway server (GWs)) to each end of the RDP virtual channels. In a particular embodiment,firewall 308 is configured to permit an inbound RDP connection fromRDP client 220 toRDP server 240B. After establishing the RDP connection (RDP client 220//RDP server 240B) 312,RDP client 220 may create one or more RDPvirtual channels 304 over the established RDP connection. For example, a user may desire to play an audio stream provided by aserver 240C using an audio player application concurrently running onRDP client 220. To provide access to the remote audio stream,GWc 410 located withinRDP client 220 may establish a tunnel and channel using specializedGWs 415 attachment through RDPvirtual channel connection 304 toRDP server 240B and again through specializedGWs 415 terminating the RDP server virtual channel.RDP server 240B may be configured to permit such a request to specializedGWs 415 functionality on theRDP server 240B.GWs 415 attached to RDPvirtual channel 304 may provide access to the stream hosted byserver 240C using any acceptable means. The stream may be tagged as a virtual channel so that it may be appropriately processed atRDP client 220. For example, in response to a request fromGWc 410 connected to a virtual channel withinRDP client 220,RDP server 240B may usevirtual channel 304 to stream encoded packets in such a manner that theRDP server 240B throughGWs 415 routes appropriately to aserver 240C the machine that hosts the audio stream.Specialized GWs 415 connected to a virtual channel linked toRDP server 240B′s virtual channel toGWc 410 may also streak packets received fromserver 240C over the RDPvirtual channel 304 and routed to player application onRDP client 220. For example, a local port may be configured to stream packets received from the audio player toserver 240C over the RDPvirtual channel 304, with all sourcing, sinking and routing determined byGWc 410 andGWs 415 attachments at alternate ends of the RDPvirtual channel 304. In this fashion, theRDP client 220 may also stream packets received fromserver 240C over the RDPvirtual channel 304 back to the local port to the audio player (again throughGWc 410//GWs 415 tunnel protocol). - In another particular embodiment, a transport gateway may be used to provide access to a remote service. For example, an application running on
RDP client 220 may require access to a service provided byserver 240C. A gateway client (gwc 310) may be provided onRDP client 220. A corresponding gateway server (gws 300) may be provided network access ofRDP server 240B, theserver 240C providing the target service, or on adifferent server 240C.RDP client 220 may request an RDPvirtual channel 304 on the establishedRDP connection 312 toRDP server 240B. On theRDP client 220, theGWc 410 andGWs 415 are bound to the RDPvirtual channel 304. OnRDP server 240B, the RDPvirtual channel 304 is bound to theGWs 415. The application is then able to communicate with the remote service through the connection pathway. The connection pathway utilizing virtual channel throughRDP connection 312 may be denoted asGWc 410/RDP client 220//RDP server 240B/GWs 415 when a transport gateway is also utilized, the connection pathway may be described asGWc 410/RDP client 220/gwc 310//gws 300/RDP server 240B/GWs 415 when the transport gateway is utilized. “I” is used to denote a local binding, and “II” is used to denote a remote binding. - In other particular embodiments, only a
GWc 410 or aGWs 415 may be provided. For example, an application onRDP client 220 may not require a separate transport gateway client to access a transport gateway server. In such an embodiment, the application connects directly to the transport gateway server. Other particular embodiments are described with reference toFIG. 3B .RDP client 220 may connect toRDP server 240B viafirewall 308 and gws 300. In particular embodiments, gws 300 may comprise one or more of a proxy server (e.g., web proxy) or a connection manager. The proxy server or connection manager may be operated by one ormore servers 240A. The proxy server may act as an intermediary for data transfer betweenRDP client 220 andRDP server 240B. - In particular embodiments, gws 300 may utilize Microsoft's Tunneling Service to allow
RDP client 220 to establish a tunnel toservers gwc 310 may encode the RDP data packets, serialized for transmission over HTTPS, received fromRDP client 220 and translate the data packets into native RDP data packets (also known as RDP protocol data units) for use byRDP server 240B. In the example network environment ofFIG. 3 , gws 300 may consist of one ormore servers 240A. In particular embodiments,RDP server 240B may be an RDP session host such thatRDP client 220 may connect to theRDP server 240B. After establishing theRDP connection 312,RDP client 220 may create one or more RDPvirtual channels 304 over the established RDP connection and attach specialized gateway protocol to each end of the virtual channels (GWc 410//GWs 415) andopen connection gateway 306 to specified server. For example,gateway 306 is a subset of RDPvirtual channel gateway 304 in that packets transmitted overgateway 306 are tagged as virtual channel packets and are communicated over the establishedconnection 304. For example, a user may desire to play an audio stream provided by aserver 240C using server message blocks (SMBs) on a server and using an audio player application concurrently running onRDP client 220. To provide access to the remote audio stream,RDP client 220 may request a RDPvirtual channel 304 on the establishedconnection 312 toRDP server 240B.RDP server 240B may be configured to permit such a request throughGWc 410 andGWs 415 at each end of virtual channel.RDP server 240B may provide access to the stream hosted byserver 240C throughGWc 410 andGWs 415 using any acceptable means, such as port forwarding. For example, in response to a request fromRDP client 220,RDP server 240B may configure a port forward from anRDP client 220 that is a host toRDP server 240B such that packets received from the RDP virtual channel'sgateway 306 are forwarded fromRDP client 220 to theserver 240C that hosts the audio stream.RDP server 240B may also configure a port forward such that packets received fromserver 240C are forwarded over the RDPvirtual channel 304 through theGWc 410//GWs 415 definitions to enable complete communication. Similarly,RDP client 220 may use port forwarding to give an audio player running concurrently with theRDP client 220 onRDP client 220 access to the audio stream. For example, a local port may be configured to forward packets received from the audio player toserver 240C over the RDP virtual channel'sGWc 410//GWs 415 attachments. TheRDP client 220 may also forward packets received fromserver 240C over the RDPvirtual channel gateway 304 to the local port to the audio player. The connection pathway may be denoted AudioPlayer(smbClient):GWc 410/RDP client 220//RDP server 240B/GWs 415:smbHost or AudioPlayer(smbClient):GWc 410/RDP client 220/gwc 310/gws 300/RDP server 240B/GWs 415:smbHost where gwc 310 has corresponding connection to transport gws 300. In particular embodiments, theGWc 410 is integrated with the RDP client software. - [1] In another particular embodiment, a gateway may be used to provide access to a remote service. For example, an application running on
RDP client 220 may require access to a service provided byserver 240C. Agwc 310 may be provided onRDP client 220. A corresponding gateway server may be provided onRDP server 240B (gws 300), theserver 240C providing the target service, or on adifferent server 240C. AfterRDP client 220 andRDP server 240B are connected,RDP client 220 may request an RDPvirtual channel 304 on the establishedRDP connection 312 toRDP server 240B with corresponding tunnel channel throughGWc 410//GWs 415 pair at each end ofvirtual channel 304. On theRDP client 220, the gateway client is bound to the RDPvirtual channel 304. OnRDP server 240B, the RDPvirtual channel 304 is transparently attached through gws 300. The application is then able to communicate with the remote service through the connection pathway. The connection pathway may be denoted asGWc 410/RDP client 220/gwc 310//gws 300/RDP server 240B when the gateway server is provided beyondfirewall 308 within scope ofRDP server 240B. The connection pathway may be denoted asGWc 410/RDP client 220/gwc 310//gws 300/RDP server 240B/GWs 415 whereGWc 410 andGWs 415 are virtual channel attachments and gws 300 may reside on a server other thanRDP server 240B. In other particular embodiments, only a gateway client or a gateway server may be provided. For example, an application onRDP client 220 may not require aseparate gwc 310 to access a gws 300. In such an embodiment, the application connects directly fromRDP client 220 toRDP server 240B to establish a connection gateway through a virtualchannel using GWc 410 andGWs 415. - In other particular embodiments, an Independent Computing Architecture (ICA) protocol supporting virtual channels may be used in place of the Remote Desktop Protocol. In such an embodiment, an ICA Client may be used in place of
RDP client 220, and an ICA Server may be used in place ofRDP server 240B. In other particular embodiments, HTTP may be used with a CONNECT method in similar fashion to virtual channels in RDP. - In particular embodiments, as described in connection with
FIG. 4 , anRDP client 220 may be implemented in a web browser, such as a standards-based web browser. A web-socket server may be used to connect theRDP client 220 implemented in a web browser to theRDP server 240B. -
FIG. 4 is an example websocket server environment 400. In particular embodiments, websocket server environment 400 may include aweb client 460,web socket 420, web-socket server 430,socket 440, andRDP server 450. In particular embodiments,web client 410 may correspond toRDP client 220 andRDP server 450 may correspond to any one or more of or any combination ofRDP servers FIGS. 3A-3B .Web client 410 may be a standards-based web browser. Web-socket server 430 may be a proxy server, and web-socket server 430 may be implemented in C or C++ code. - Web-
socket server 430 may facilitate connections betweenRDP server 450 andweb client 410.Web client 460 may send one or more packets, for example, JAVASCRIPT packets, Protocol Data Units (PDUs), or any other suitable packets, overweb socket 420. Web-socket server 430 may intercept the packets sent fromweb client 460 overweb socket 420 and convert each packet into a socket format, whichRDP server 450 may understand. Web-socket server 430 may open asocket 440 that connects withRDP server 450 and send the converted packets (e.g., in socket format) toRDP server 450 oversocket 440. In particular embodiments, web-socket server 430 may intercept packets sent fromRDP server 450 oversocket 440, which may be in socket format. Web-socket server 430 may convert the packets into a web-socket format and send the converted packets overweb socket 420 toweb client 460. In this manner, web-socket server 430 may facilitate data transmissions and any other suitable communications betweenweb client 460 andRDP server 450. The packets communicated toweb client 410 may include instructions that causeweb client 460 to act as an RDP client or to provide an RDP client, which may mean that theweb client 460 may provide a graphical interface for presenting and interacting with a remote desktop.RDP server 450 may provide the remote desktop, which may be published to theweb client 460 using an RDP via the connection facilitated by web-socket server 430. -
Web client 460,web socket 420, web-socket server 430,socket 440, andRDP server 450 may perform any of the functions and have any of the attributes described in U.S. patent application Ser. No. 14/925582 titled “Remote Desktop Protocol Client for a Standards-Based Web Browser,” filed Oct. 28, 2015, which is incorporated by reference herein. - In particular embodiments,
web client 460 may provide a run-length encoded image decompressor in order to render graphics information contained in packets received fromRDP server 450 by way of web-socket server 430. In particular embodiments, the run-length encoded image decompressor may be provided in JAVASCRIPT. In particular embodiments, the run-length encoded image decompressor may be implemented in hypertext markup language 5 (HTML5) and CANVAS. -
FIG. 5 illustrates anexample method 500 for providing a run-length encoding decompressor for a standards-basedweb client 460 according to one or more embodiments of the present invention. Atstep 502,web client 460 may receive a packet fromRDP server 450 via web-socket server 430. The received packet may be a run-length encoded (RLE) packet—in PDU format and transmitted as a JAVASCRIPT packet. The received packet may contain RLE graphics data. The graphics data may comprise any one or more of audio data, video data, teleconferencing data, and any other type of graphics data known to one of ordinary skill in the art. - At
step 504, theweb client 460 determines the color space of the received packet. The color space may be sent fromRDP server 450 as part of the header of the received packet. Atstep 506, theweb client 460 determines the RLE algorithm for the received packet. The RLE algorithm may be based, at least in part, on the determined color space of the received packet. One or more RLE algorithms may be associated with a given color space. Each packet received has the identified color space and any associated information necessary for the run-length encoder to select the RLE algorithm. - At
step 508,web client 460 may decompress the received packet based, at least in part, on the determined RLE algorithm. Theweb client 460 decompresses the received packet into one or more rows of a plurality of values, where each value corresponds to a color for a particular pixel. During decompression,web client 460 may use an indicator, such as a flag, to mark repetitive pixels in a row. Any such indicator known to one of ordinary skill in the art may be used to mark repetitive pixels in a row. In one embodiment, a received packet comprises four black pixels in a row. Run-length encoding may flag the four black pixels as “B4” as opposed to “BBBB.” A run-length encoded packet, such as a PDU, may be, for example, decompressed using a determined RLE algorithm as shown in Appendix A. - At
step 510, theweb client 460 determines a plurality of commands corresponding to the graphics to be drawn on the canvas, where the canvas is a hypertext markup language (HTML) <canvas> element which can be used to draw graphics using a scripting language, such as JAVASCRIPT. Determining the plurality of commands may, in one or more embodiments, be part ofstep 508. For example, Appendix B illustrates drawing graphics to a canvas. - At
step 512, the graphics associated with the received packet are rendered. The graphics are rendered on the canvas based, at least in part, on the plurality of commands. The graphics associated with the received packet are now ready for display to a user interface associated with theweb client 460 on a graphical interface, such as a monitor or any other graphical interface known to one of ordinary skill in the art, for viewing and interacting with the remote desktop. -
FIG. 6 illustrates anexample method 600 according to one or more embodiments of the present invention. After theweb client 460 decompresses the run-length encoded received packet,web client 460 may determine atstep 602 if the color space of the received packet is supported by theweb client 460. If atstep 602, it is determined that the color space of the received packet is not supported, then atstep 604 theweb client 460 may convert the received packet into a different color space that is supported by theweb client 460. RDP supports various color spaces, for example, 8, 16, 24, and 32-bit color spaces.Web client 460 may support only one, a subset of the possible color spaces, or all of the possible color spaces. In one embodiment,web client 460 may support only one color space, for example, a 32-bit color space. Accordingly,web client 460 may convert the received packet that is encoded using a run-length encoding algorithm for a first color space (for example, 8-bit color space) to a packet that is encoded using a run-length encoding algorithm for a supported or second color space (for example, a 32-bit color space). The RLE algorithm uncompresses, for example, an 8-bit packet to an 8-bit uncompressed packet or a 16-bit packet to a 16-bit uncompressed packet, or a 24-bit packet to a 24-bit uncompressed packet. Then the uncompressed packet is converted to a 32-bit color space using a color space conversion. - The RLE algorithm may be based, at least in part, on either of the first color space or the second color space, whichever corresponds to a 32-bit color space. If a packet is already encoded for a 32-bit color space, then
web client 460 may not need to perform any color space conversion. In one embodiment, theRDP server 450 sends packets with graphics data encoded for a smaller color space (for example, 8-bit color space) than for a larger color space (for example, 32-bit color space) even though theweb client 460 only supports the larger color space as sending for a smaller color space may be faster. - As an example,
web client 460 may receive a packet from web-socket browser 430. Atstep 602,web client 460 may identify the first color space of the packet (for example, read it from the header) and query the canvas associated withweb client 460 to determine the second color space of the packet. If the first color space and the second color space are the same, no conversion needs to be performed. If the first color space and the second color space differ, for example, the first color space might be an 8-bit color space, and the second color space might be a 32-bit color space, then atstep 604web client 460 selects a color space conversion algorithm based, at least in part, on the first color space and the second color space (the color space to convert from and the color space to convert to) and may run the selected color space conversion algorithm to convert the packet to the second color space, the 32-bit color space. The color space conversion algorithm may be any suitable color space conversion algorithm. The selected color space conversion algorithm that is employed may depend on the conversion to be made. For example, the color space conversion algorithm for converting a 16-bit color space to a 24-bit color space differs from that for converting a 24-bit color space to a 32-bit color space. After the run-length encoded received packet has been converted into a supported color space,web client 460 may render the graphics information (e.g., an image) from the received packet as discussed withstep 512 ofFIG. 5 . For example, the standards-based web browser at theweb client 460 may now utilize the operating system's graphics library to present any graphics information to a display or I/O device at theweb client 460. -
FIG. 7 illustrates anexample method 700 according to one or more embodiments of the present invention. In particular embodiments, it may be more efficient to perform pre-processing of a packet before the packet is sent to theweb client 460. Atstep 702, web-socket server 430 may intercept and inspect a packet before sending the packet toweb client 460. Atstep 704, web-socket server 430 determines the processing power of a packet received from theRDP server 450. The web-socket server 430 may inspect the packet and detect that the packet contains RLE encoded data and determine that the decompression may be performed at the web-socket server 430 which increases the performance atweb client 460. - At
step 706, the web-socket server 430 determines if the packet should be pre-processed at the web-socket server 430 before sending to theweb client 460. That is, a packet may require too much processing power forweb client 460 to handle (for example., it would be much slower forweb client 460 to do a particular processing task). If it is determined that the packet should be pre-processed at web-socket server 430, then atstep 708 the web-socket server 430 pre-processes the packet before sending it toweb client 460. For example, web-socket server 430 may perform the run-length encoding expansion and convert the packet to a suitable format, such as a joint photographic experts group (JPEG) format or any other suitable format known to one of ordinary skill in the art, before sending the packet toweb client 460.Web client 460 may then render the pre-processed received packet without having to perform any conversion to a different color space. - Although this disclosure describes and illustrates particular embodiments as being implemented by
web client 460, this disclosure contemplates any suitable embodiments occurring on any suitable interface and as being implemented by any suitable platform or system. As an example, and not by way of limitation, particular embodiments may be implemented by web-socket server 430. Furthermore, although this disclosure describes and illustrates particular components, devices, or systems carrying out particular steps, this disclosure contemplates any suitable combination of any suitable components, devices, or systems carrying out any suitable steps of the method ofFIG. 4 . - Particular embodiments may repeat one or more steps of any method where appropriate. Although this disclosure describes and illustrates particular steps of as occurring in a particular order, this disclosure contemplates any suitable steps occurring in any suitable order. Moreover, although this disclosure describes and illustrates an example method for providing a run-length encoding decompressor for a standards-based
web client 410, this disclosure contemplates any suitable method for providing a run-length encoding decompressor for a standards-basedweb client 410, including any suitable steps, which may include all, some, or none of the steps of the methods ofFIG. 5 ,FIG. 6 , andFIG. 7 where appropriate. Furthermore, although this disclosure describes and illustrates particular components, devices, or systems carrying out particular steps, this disclosure contemplates any suitable combination of any suitable components, devices, or systems carrying out any suitable steps. - Herein, “or” is inclusive and not exclusive, unless expressly indicated otherwise or indicated otherwise by context. Therefore, herein, “A or B” means “A, B, or both,” unless expressly indicated otherwise or indicated otherwise by context. Moreover, “and” is both joint and several, unless expressly indicated otherwise or indicated otherwise by context. Therefore, herein, “A and B” means “A and B, jointly or severally,” unless expressly indicated otherwise or indicated otherwise by context.
- Those of skill in the art would appreciate that items such as the various illustrative blocks, modules, elements, components, methods, operations, steps, and algorithms described herein may be implemented as hardware, computer software, or a combination of both.
- To illustrate the interchangeability of hardware and software, items such as the various illustrative blocks, modules, elements, components, methods, operations, steps, and algorithms have been described generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application.
- In one aspect, “means,” a block, a module, an element, a component or a processor may be an item (for example, one or more of blocks, modules, elements, components or processors) for performing one or more functions or operations. In one aspect, such an item may be an apparatus, hardware, or a portion thereof. In one example, an item may have a structure in the form of, for example, an instruction(s) encoded or stored on a machine-readable medium, on another device, or on a portion thereof. An instruction(s) may be software, an application(s), a subroutine(s), or a portion thereof. The instructions(s) may be for performing the function(s) or operation(s). The instruction(s) may be executable by one or more processors to perform the function(s) or operation(s). One or more processors may execute the instruction(s) by, for example, transferring or copying and instructions into an executable memory space and executing the instructions. In one example, an item may be implemented as one or more circuits configured to perform the function(s) or operation(s). A circuit may include one or more circuits and/or logic. A circuit may be analog and/or digital. A circuit may be electrical and/or optical. A circuit may include transistors. In an example, one or more items may be implemented as a processing system (for example, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), etc.), as a portion(s) of any of the foregoing, or as a combination(s) of any of the foregoing. Those skilled in the art will recognize how to implement the instructions, circuits, and processing systems.
- In one aspect of the disclosure, when actions or functions (for example, hooking, modifying, intercepting, redirecting, determining, traversing, obtaining, creating, operating, deleting, removing, receiving, providing, generating, converting, displaying, notifying, accepting, selecting, controlling, transmitting, reporting, sending, or any other action or function) are described as being performed by an item (for example, one or more of blocks, modules, elements, components or processors), it is understood that such actions or functions may be performed, for example, by the item directly. In another example, when an item is described as performing an action, the item may be understood to perform the action indirectly, for example, by facilitating such an action (for example, assisting, allowing, enabling, causing, or providing for, such action to occur; or performing a portion of such an action). For example, determining can refer to facilitating determination, attaching can refer to facilitating attaching, and receiving can refer to facilitating receiving. In one aspect, performing an action may refer to performing a portion of the action (for example, performing a beginning part of the action, performing an end part of the action, or performing a middle portion of the action).
- A reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more.” For example, a client may refer to one or more clients, a server may refer to one or more servers, an operation may refer to one or more operations, and a signal, message, or communication may refer to one or more signals, messages, or communications.
- Unless specifically stated otherwise, the term “some” refers to one or more. Pronouns in the masculine (for example, his) include the feminine and neuter gender (for example, her and its) and vice versa. Headings and subheadings, if any, are used for convenience only and do not limit the invention.
- A phrase such as an “embodiment” does not imply that such embodiment is essential to the subject technology or that such embodiment applies to all configurations of the subject technology. A disclosure relating to an embodiment may apply to all embodiments, or one or more embodiments. An embodiment may provide one or more examples. A phrase such an embodiment may refer to one or more embodiments and vice versa. A phrase such as a “configuration” does not imply that such configuration is essential to the subject technology or that such configuration applies to all configurations of the subject technology. A disclosure relating to a configuration may apply to all configurations, or one or more configurations. A configuration may provide one or more examples. A phrase such a configuration may refer to one or more configurations and vice versa.
- In one aspect, the term “coupled” or the like may refer to being directly coupled. In another aspect, the term “coupled” or the like may refer to being indirectly coupled or communicatively coupled.
- Various items may be arranged differently (for example, arranged in a different order, or partitioned in a different way) all without departing from the scope of the subject technology. In one aspect of the disclosure, the elements recited in the accompanying claims may be performed by one or more modules or sub-modules.
- It is understood that the specific order or hierarchy of steps, operations or processes disclosed is an illustration of exemplary approaches. Based upon design preferences, it is understood that the specific order or hierarchy of steps, operations or processes may be rearranged. Some of the steps, operations or processes may be performed simultaneously. Some or all of the steps, operations, or processes may be performed automatically, without the intervention of a user. The accompanying method claims, if any, present elements of the various steps, operations or processes in a sample order, and are not meant to be limited to the specific order or hierarchy presented.
- The disclosure is provided to enable any person skilled in the art to practice the various aspects described herein. The disclosure provides various examples of the subject technology, and the subject technology is not limited to these examples. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects.
- All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. No claim element is to be construed under the provisions of 35 U.S.C. §112, sixth paragraph, unless the element is expressly recited using the phrase “means for” or, in the case of a method claim, the element is recited using the phrase “step for.” Furthermore, to the extent that the term “include,” “have,” or the like is used, such term is intended to be inclusive in a manner similar to the term “comprise” as “comprise” is interpreted when employed as a transitional word in a claim.
- The Title, Background, Summary, Brief Description of the Drawings and Abstract of the disclosure are hereby incorporated into the disclosure and are provided as illustrative examples of the disclosure, not as restrictive descriptions. It is submitted with the understanding that they will not be used to limit the scope or meaning of the claims. In addition, in the Detailed Description, it can be seen that the description provides illustrative examples and the various features are grouped together in various embodiments for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed subject matter requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed configuration or operation. The following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separately claimed subject matter.
- The claims are not intended to be limited to the aspects described herein, but are to be accorded the full scope consistent with the language claims and to encompass all legal equivalents. Notwithstanding, none of the claims are intended to embrace subject matter that fails to satisfy the requirement of 35 U.S.C. §101, 102, or 103, nor should they be interpreted in such a way. Any unintended embracement of such subject matter is hereby disclaimed.
- The scope of this disclosure encompasses all changes, substitutions, variations, alterations, and modifications to the example embodiments described or illustrated herein that a person having ordinary skill in the art would comprehend. The scope of this disclosure is not limited to the example embodiments described or illustrated herein. Moreover, although this disclosure describes and illustrates respective embodiments herein as including particular components, elements, feature, functions, operations, or steps, any of these embodiments may include any combination or permutation of any of the components, elements, features, functions, operations, or steps described or illustrated anywhere herein that a person having ordinary skill in the art would comprehend. Furthermore, reference in the appended claims to an apparatus or system or a component of an apparatus or system being adapted to, arranged to, capable of, configured to, enabled to, operable to, or operative to perform a particular function encompasses that apparatus, system, component, whether or not it or that particular function is activated, turned on, or unlocked, as long as that apparatus, system, or component is so adapted, arranged, capable, configured, enabled, operable, or operative.
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/930,323 US9628810B1 (en) | 2015-11-02 | 2015-11-02 | Run-length encoded image decompressor for a remote desktop protocol client in a standards-based web browser |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/930,323 US9628810B1 (en) | 2015-11-02 | 2015-11-02 | Run-length encoded image decompressor for a remote desktop protocol client in a standards-based web browser |
Publications (2)
Publication Number | Publication Date |
---|---|
US9628810B1 US9628810B1 (en) | 2017-04-18 |
US20170127067A1 true US20170127067A1 (en) | 2017-05-04 |
Family
ID=58635764
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/930,323 Active US9628810B1 (en) | 2015-11-02 | 2015-11-02 | Run-length encoded image decompressor for a remote desktop protocol client in a standards-based web browser |
Country Status (1)
Country | Link |
---|---|
US (1) | US9628810B1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109101314A (en) * | 2017-06-20 | 2018-12-28 | 西门子股份公司 | Make the method and apparatus of the virtual machine of the first computer access second computer |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10015228B2 (en) | 2015-10-28 | 2018-07-03 | Dell Products L.P. | Remote desktop protocol client for a standards-based web browser |
US10057376B2 (en) | 2015-10-30 | 2018-08-21 | Dell Products L.P. | Remote desktop protocol client with virtual channel support implemented in a standards-based web browser |
US10051033B2 (en) | 2015-10-30 | 2018-08-14 | Dell Products L.P. | Providing audio data for a remote desktop protocol in a standards-based web browser |
EP3247084B1 (en) | 2016-05-17 | 2019-02-27 | Nolve Developments S.L. | Server and method for providing secure access to web-based services |
FR3059505B1 (en) * | 2016-11-28 | 2019-04-19 | Wallix | INTEGRATION OF A STANDARD NETWORK PROTOCOL LAYER IN A WEB BROWSER BY COMPILATION TO WEBASSEMBLY AND USE OF WEBSOCKET. |
US11528314B2 (en) * | 2020-03-26 | 2022-12-13 | Honeywell International Inc. | WebAssembly module with multiple decoders |
Family Cites Families (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7839860B2 (en) * | 2003-05-01 | 2010-11-23 | Genesis Microchip Inc. | Packet based video display interface |
WO2005073862A1 (en) * | 2004-01-30 | 2005-08-11 | Matsushita Electric Industrial Co., Ltd. | Recording medium, reproduction device, program, and reproduction method |
US8509555B2 (en) * | 2008-03-12 | 2013-08-13 | The Boeing Company | Error-resilient entropy coding for partial embedding and fine grain scalability |
WO2014005053A1 (en) * | 2012-06-29 | 2014-01-03 | Avocent Huntsville Corp. | System and method for single kvm client accommodating multiple different video compression technologies |
US20140040767A1 (en) * | 2012-08-03 | 2014-02-06 | Oracle International Corporation | Shared digital whiteboard |
US20140185950A1 (en) * | 2012-12-28 | 2014-07-03 | Microsoft Corporation | Progressive entropy encoding |
EP2972936B1 (en) * | 2013-03-15 | 2018-12-26 | American Megatrends, Inc. | System and method of web-based keyboard, video and mouse (kvm) redirection and application of the same |
-
2015
- 2015-11-02 US US14/930,323 patent/US9628810B1/en active Active
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109101314A (en) * | 2017-06-20 | 2018-12-28 | 西门子股份公司 | Make the method and apparatus of the virtual machine of the first computer access second computer |
US11188356B2 (en) * | 2017-06-20 | 2021-11-30 | Siemens Aktiengesellschaft | Method and arrangement to access a first computer on a virtual machine of a second computer |
Also Published As
Publication number | Publication date |
---|---|
US9628810B1 (en) | 2017-04-18 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9935790B2 (en) | Virtual channel virtual private network | |
US9628810B1 (en) | Run-length encoded image decompressor for a remote desktop protocol client in a standards-based web browser | |
US10015228B2 (en) | Remote desktop protocol client for a standards-based web browser | |
US11675930B2 (en) | Remoting application across a network using draw commands with an isolator application | |
US9246819B1 (en) | System and method for performing message-based load balancing | |
US10552639B1 (en) | Local isolator application with cohesive application-isolation interface | |
US8112491B1 (en) | Methods and systems for providing direct DMA | |
US10057376B2 (en) | Remote desktop protocol client with virtual channel support implemented in a standards-based web browser | |
US20200349682A1 (en) | Video enhancement using a generator with filters of generative adversarial network | |
US9392053B2 (en) | Generic transcoding service with library attachment | |
US11741582B1 (en) | Video enhancement using a neural network | |
US20200349686A1 (en) | Video enhancement using a recurrent image date of a neural network | |
US9936049B2 (en) | Protocol independent way for dynamically selecting data compression methods for redirected USB devices | |
US10476927B2 (en) | System and method for display stream compression for remote desktop protocols | |
US9553925B2 (en) | Front-end high availability proxy | |
US10791135B2 (en) | Inspection of network traffic in a security device at object level | |
US10623377B1 (en) | On-premises data access and firewall tunneling | |
US10021217B2 (en) | Protocol independent way to selectively restrict write-access for redirected USB mass storage devices | |
US10051033B2 (en) | Providing audio data for a remote desktop protocol in a standards-based web browser | |
CN110545230B (en) | Method and device for forwarding VXLAN message | |
US10482887B1 (en) | Machine learning model assisted enhancement of audio and/or visual communications | |
US9838507B2 (en) | System and method for providing redirection of Bluetooth devices | |
US10146499B2 (en) | System and method to redirect display-port audio playback devices in a remote desktop protocol session | |
US9904475B2 (en) | Systems and methods for setting the operating system properties for a storage device | |
US9817779B2 (en) | System and methods to support vendor defined USB requests for application managed USB devices in VDI environments |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT, NO Free format text: SUPPLEMENT TO PATENT SECURITY AGREEMENT (ABL);ASSIGNORS:DELL SOFTWARE INC.;DELL PRODUCTS L.P.;WYSE TECHNOLOGY L.L.C.;REEL/FRAME:037847/0843 Effective date: 20160212 Owner name: BANK OF AMERICA, N.A., AS COLLATERAL AGENT, NORTH Free format text: SUPPLEMENT TO PATENT SECURITY AGREEMENT (TERM LOAN);ASSIGNORS:DELL SOFTWARE INC.;DELL PRODUCTS L.P.;WYSE TECHNOLOGY L.L.C.;REEL/FRAME:037848/0001 Effective date: 20160212 Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., A Free format text: SUPPLEMENT TO PATENT SECURITY AGREEMENT (NOTES);ASSIGNORS:DELL SOFTWARE INC.;DELL PRODUCTS L.P.;WYSE TECHNOLOGY L.L.C.;REEL/FRAME:037848/0210 Effective date: 20160212 Owner name: BANK OF AMERICA, N.A., AS COLLATERAL AGENT, NORTH CAROLINA Free format text: SUPPLEMENT TO PATENT SECURITY AGREEMENT (TERM LOAN);ASSIGNORS:DELL SOFTWARE INC.;DELL PRODUCTS L.P.;WYSE TECHNOLOGY L.L.C.;REEL/FRAME:037848/0001 Effective date: 20160212 Owner name: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT, NORTH CAROLINA Free format text: SUPPLEMENT TO PATENT SECURITY AGREEMENT (ABL);ASSIGNORS:DELL SOFTWARE INC.;DELL PRODUCTS L.P.;WYSE TECHNOLOGY L.L.C.;REEL/FRAME:037847/0843 Effective date: 20160212 Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT, TEXAS Free format text: SUPPLEMENT TO PATENT SECURITY AGREEMENT (NOTES);ASSIGNORS:DELL SOFTWARE INC.;DELL PRODUCTS L.P.;WYSE TECHNOLOGY L.L.C.;REEL/FRAME:037848/0210 Effective date: 20160212 |
|
AS | Assignment |
Owner name: DELL SOFTWARE INC., CALIFORNIA Free format text: RELEASE OF REEL 037847 FRAME 0843 (ABL);ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:040017/0366 Effective date: 20160907 Owner name: DELL PRODUCTS L.P., TEXAS Free format text: RELEASE OF REEL 037847 FRAME 0843 (ABL);ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:040017/0366 Effective date: 20160907 Owner name: WYSE TECHNOLOGY L.L.C., CALIFORNIA Free format text: RELEASE OF REEL 037847 FRAME 0843 (ABL);ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:040017/0366 Effective date: 20160907 |
|
AS | Assignment |
Owner name: DELL SOFTWARE INC., CALIFORNIA Free format text: RELEASE OF REEL 037848 FRAME 0001 (TL);ASSIGNOR:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;REEL/FRAME:040028/0152 Effective date: 20160907 Owner name: DELL PRODUCTS L.P., TEXAS Free format text: RELEASE OF REEL 037848 FRAME 0210 (NOTE);ASSIGNOR:BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT;REEL/FRAME:040031/0725 Effective date: 20160907 Owner name: DELL PRODUCTS L.P., TEXAS Free format text: RELEASE OF REEL 037848 FRAME 0001 (TL);ASSIGNOR:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;REEL/FRAME:040028/0152 Effective date: 20160907 Owner name: DELL SOFTWARE INC., CALIFORNIA Free format text: RELEASE OF REEL 037848 FRAME 0210 (NOTE);ASSIGNOR:BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT;REEL/FRAME:040031/0725 Effective date: 20160907 Owner name: WYSE TECHNOLOGY L.L.C., CALIFORNIA Free format text: RELEASE OF REEL 037848 FRAME 0001 (TL);ASSIGNOR:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;REEL/FRAME:040028/0152 Effective date: 20160907 Owner name: WYSE TECHNOLOGY L.L.C., CALIFORNIA Free format text: RELEASE OF REEL 037848 FRAME 0210 (NOTE);ASSIGNOR:BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT;REEL/FRAME:040031/0725 Effective date: 20160907 |
|
AS | Assignment |
Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., A Free format text: SECURITY AGREEMENT;ASSIGNORS:ASAP SOFTWARE EXPRESS, INC.;AVENTAIL LLC;CREDANT TECHNOLOGIES, INC.;AND OTHERS;REEL/FRAME:040136/0001 Effective date: 20160907 Owner name: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLAT Free format text: SECURITY AGREEMENT;ASSIGNORS:ASAP SOFTWARE EXPRESS, INC.;AVENTAIL LLC;CREDANT TECHNOLOGIES, INC.;AND OTHERS;REEL/FRAME:040134/0001 Effective date: 20160907 Owner name: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT, NORTH CAROLINA Free format text: SECURITY AGREEMENT;ASSIGNORS:ASAP SOFTWARE EXPRESS, INC.;AVENTAIL LLC;CREDANT TECHNOLOGIES, INC.;AND OTHERS;REEL/FRAME:040134/0001 Effective date: 20160907 Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT, TEXAS Free format text: SECURITY AGREEMENT;ASSIGNORS:ASAP SOFTWARE EXPRESS, INC.;AVENTAIL LLC;CREDANT TECHNOLOGIES, INC.;AND OTHERS;REEL/FRAME:040136/0001 Effective date: 20160907 |
|
AS | Assignment |
Owner name: DELL PRODUCTS L.P., TEXAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BINGOL, EVREN;SCHWEBKE, CURTIS;SIGNING DATES FROM 20151031 TO 20160630;REEL/FRAME:040363/0001 |
|
FEPP | Fee payment procedure |
Free format text: PAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., T Free format text: SECURITY AGREEMENT;ASSIGNORS:CREDANT TECHNOLOGIES, INC.;DELL INTERNATIONAL L.L.C.;DELL MARKETING L.P.;AND OTHERS;REEL/FRAME:049452/0223 Effective date: 20190320 Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., TEXAS Free format text: SECURITY AGREEMENT;ASSIGNORS:CREDANT TECHNOLOGIES, INC.;DELL INTERNATIONAL L.L.C.;DELL MARKETING L.P.;AND OTHERS;REEL/FRAME:049452/0223 Effective date: 20190320 |
|
AS | Assignment |
Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., TEXAS Free format text: SECURITY AGREEMENT;ASSIGNORS:CREDANT TECHNOLOGIES INC.;DELL INTERNATIONAL L.L.C.;DELL MARKETING L.P.;AND OTHERS;REEL/FRAME:053546/0001 Effective date: 20200409 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |
|
AS | Assignment |
Owner name: WYSE TECHNOLOGY L.L.C., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: SCALEIO LLC, MASSACHUSETTS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: MOZY, INC., WASHINGTON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: MAGINATICS LLC, CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: FORCE10 NETWORKS, INC., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: EMC IP HOLDING COMPANY LLC, TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: EMC CORPORATION, MASSACHUSETTS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: DELL SYSTEMS CORPORATION, TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: DELL SOFTWARE INC., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: DELL PRODUCTS L.P., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: DELL MARKETING L.P., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: DELL INTERNATIONAL, L.L.C., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: DELL USA L.P., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: CREDANT TECHNOLOGIES, INC., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: AVENTAIL LLC, CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: ASAP SOFTWARE EXPRESS, INC., ILLINOIS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 |
|
AS | Assignment |
Owner name: SCALEIO LLC, MASSACHUSETTS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: EMC IP HOLDING COMPANY LLC (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MOZY, INC.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: EMC CORPORATION (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MAGINATICS LLC), MASSACHUSETTS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: DELL PRODUCTS L.P., TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: DELL INTERNATIONAL L.L.C., TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: DELL USA L.P., TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO ASAP SOFTWARE EXPRESS, INC.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 |
|
AS | Assignment |
Owner name: SCALEIO LLC, MASSACHUSETTS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: EMC IP HOLDING COMPANY LLC (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MOZY, INC.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: EMC CORPORATION (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MAGINATICS LLC), MASSACHUSETTS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: DELL PRODUCTS L.P., TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: DELL INTERNATIONAL L.L.C., TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: DELL USA L.P., TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO ASAP SOFTWARE EXPRESS, INC.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 |