US20120173739A1 - Format negotiation for media remoting scenarios - Google Patents
Format negotiation for media remoting scenarios Download PDFInfo
- Publication number
- US20120173739A1 US20120173739A1 US13/421,643 US201213421643A US2012173739A1 US 20120173739 A1 US20120173739 A1 US 20120173739A1 US 201213421643 A US201213421643 A US 201213421643A US 2012173739 A1 US2012173739 A1 US 2012173739A1
- Authority
- US
- United States
- Prior art keywords
- oplock
- media
- state
- 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.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/60—Network streaming of media packets
- H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
- H04L65/612—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/60—Network streaming of media packets
- H04L65/75—Media network packet handling
- H04L65/762—Media network packet handling at the source
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/24—Negotiation of communication capabilities
Abstract
Format negotiation for media remoting involves at least one media data format. In an example embodiment, a media format negotiation for playing media data is begun between a server and a client. The media data format is transferred from the server to the client. A notification that indicates if an attempt at the client to construct a media topology responsive to the media data format was a success or a failure is transferred from the client to the server. Whether and/or how the media data is to be transferred from the server to the client may be impacted by the notification.
Description
- Media data may be played locally on a processing device with a local media player. Typically, a processing device retrieves media data for a local media player. The local media player performs a series of operations on the media data to transform it. The transformed media data is then presented by the processing device via a display screen and/or speaker.
- The transformed media data is usually much larger in size than the media data when it is initially retrieved. In other words, the transformed media data usually occupies relatively more memory for storage and consumes a relatively greater bandwidth during transmission. This larger size can therefore cause difficulties when media data is played in a remoting scenario in which less than all of the playing activities are conducted at a single location.
- Format negotiation for media remoting involves at least one media data format. In an example embodiment, a media format negotiation for playing media data is begun between a server and a client. The media data format is transferred from the server to the client. A notification that indicates if an attempt at the client to construct a media topology responsive to the media data format was a success or a failure is transferred from the client to the server. Whether and/or how the media data is to be transferred from the server to the client may be impacted by the notification.
- This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter. Moreover, other method, system, scheme, apparatus, device, media, procedure, API, arrangement, etc. implementations are described herein.
- The same numbers are used throughout the drawings to reference like and/or corresponding aspects, features, and components.
-
FIG. 1 is a block diagram illustrating an example of media playback in a local scenario. -
FIG. 2 is a block diagram illustrating an example environment for media playback in a remoting scenario that includes a server and a client and in which media communications may be exchanged. -
FIG. 3 is a block diagram illustrating a remoting media playback scenario that includes an example media format negotiation. -
FIG. 4 is a block diagram of an example server side of a remoting media playback scenario. -
FIG. 5 is a block diagram of an example client side of a remoting media playback scenario. -
FIG. 6 is a flow diagram that illustrates an example of a method that involves a media format negotiation for media playback in a remoting scenario. -
FIGS. 7A and 7B areparts -
FIG. 8 is an example sequence diagram between different server and client components for a successful result for a response phase of a media format negotiation. -
FIG. 9 is an example sequence diagram between different server and client components for a failure result for a response phase of a media format negotiation. -
FIG. 10 is a block diagram of an example device that may be used to implement format negotiation for media remoting scenarios. - Media playback in a local scenario usually involves a media player creating a media topology. The topology includes source nodes that provide media data, intermediate nodes that transform the data and/or apply various effects, and sink nodes that render the data. These different nodes in a media topology are typically driven by a clock that controls the timing of data flow. A high level overview of an example approach to media playback in a local scenario is described below with particular reference to
FIG. 1 . -
FIG. 1 is a block diagram 101 illustrating an example of media playback in a local scenario. As illustrated, localmedia playback scenario 101 includes amedia player 103 that creates amedia playback topology 105.Media playback topology 105 includes aclock 107, asource node 109, one or moreintermediate nodes 111, and asink node 113.Clock 107 controls the timing of data flow throughnodes -
Source node 109 reads media data (e.g., from a file, a network, etc.) and forwards the media data to intermediate node(s) 111 of the media topology chain ofmedia playback topology 105. Intermediate node(s) 111 perform various operations on the media data to transform it. These operations may include decoding, re-sampling, and so forth. A finalintermediate node 111 forwards the transformed media data to sinknode 113.Sink node 113 renders the media data on anappropriate device 115. Anappropriate device 115 includes a window for video or a speaker for audio, or both for multimedia media data. - The media playback approach described above with reference to
FIG. 1 is adequate for media playback in local scenarios. However, from time to time, media playback in a remoting scenario is requested. Terminal-server-based remoting scenarios, by way of example only, provide for a desktop remoting experience in which a thin-client can connect remotely over a network to another computer (e.g., the terminal server) to attain a remote desktop experience. In such a terminal server scenario, the applications run on the server, and they provide the desktop experience by remoting their “output” (e.g., graphics with respect to their visual output) to the client device over a network. - If media data is played on the server in a session with a terminal-server-based remoting scenario, various performance problems typically result. Such performance problems usually result from sending fast-changing bitmaps over network links (e.g., using a remote desktop protocol (RDP), etc.) and from the loss of synchronization between the video and the audio for multimedia media data. More specifically, the fast moving video frames result in an extraordinary amount of bitmap data that has to be transferred to the client. This results in a very high bandwidth and server CPU usage. Additionally, the audio and video tend to become unsynchronized because the timing information is often lost when sending video frames through rendered bitmaps (e.g., using a graphics device interface (GDI), etc.).
- One approach to addressing these problems is to send encoded audio/video data directly to the client and to decode/render the data on the client. As a result, timing information, and thus audio and video synchronization, can be maintained. Such an audio/video remoting approach is affected, however, by the ability of the client to decode the provided audio/video data. Also, with certain server configurations, the server session operates more smoothly when the server learns beforehand if the client has available to it decoders that can support the requested audio/video data. For instance, some terminal server configurations involve separate topology creation phases and media playback phases that inhibit backtracking.
- A procedure for determining if the client has available decoders that can support the requested audio/video data is often termed format negotiation. Learning if a client can handle the audio/video data beforehand can enable a server in certain configurations to fallback on bitmap-based remoting or to disable the playback at the client device in a remoting scenario by constructing an appropriate media playback topology at the server at an appropriate time.
- Example embodiments address one or more issues of media format negotiation between a server and a client. In a described implementation, a server performs a media format negotiation with a client during (or at least prior to the completion of) the server media topology construction phase (e.g., before playback actually starts). The result of the media format negotiation is a relatively definitive response from the client that indicates if the client is able to decode media data received from the server in an identified media data format (e.g., a particular video and/or audio format). Also, the negotiation need not depend on any direct enumeration to the server of the formats supported by the client; hence, reliability may be increased. If the identified media data formats are not supported by the client, then the server may fallback on the bitmap-based remote playback or may disable remote playback for the client in a remoting scenario.
-
FIG. 2 is a block diagram illustrating anexample environment 200 for media playback in a remoting scenario that includes a server and a client and in which media communications may be exchanged. As illustrated,environment 200 includes aserver 202, aclient 204, and one ormore networks 212.Media communications 206 may be exchanged by way of transfers betweenserver 202 andclient 204 overnetwork 212.Environment 200 also includes media data in storage 208(S) and at least one mediadata presentation device 210. - In an example embodiment,
server 202 includes or otherwise has access tomedia data 208, such as media data that is being stored 208(S).Media data 208 may be multimedia media data. In operation,server 202 engages in media-relatedcommunications 206 withclient 204. Examples ofmedia communications 206 include, but are not limited to, media data format negotiations, media data transfers, and so forth. Upon receiving media data,client 204 presents (e.g., plays, displays, etc.) the received media data on mediadata presentation device 210. Mediadata presentation device 210 may be coupled to or integrated withclient 204. Mediadata presentation device 210 may be a display screen, a speaker, a window on a display screen, multiple such devices, some combination thereof, and so forth. -
Server 202 may be any device that is capable of providing a media playing remoting scenario for aclient 204.Server 202 may be a web server; a local area network (LAN), wide area network (WAN), etc. server; a cable network head-end; a home media server; a desktop computer; some combination thereof; and so forth.Client 204 may be any device that is capable of receptively participating in a media playing remoting scenario.Client 204 may be a notebook or desktop computer; a mobile telephone; a personal media player; a set-top box; a television or other entertainment device; a personal digital assistant (PDA) or highly-portable computer; a home media server; some combination thereof, and so forth. - Network(s) 212 may be comprised of one or more similar or different network types. By way of example only,
network 212 may be a wired network or a wireless network; an internet; a LAN, WAN, etc.; a cellular network; a cable, telephone, or digital subscriber line (DSL) network; an Ethernet network; a mesh network; a Wi-Fi® network; a WiMAX® network; some combination thereof; and so forth. Although only oneclient 204 is explicitly shown, asingle server 202 may be simultaneously providing a remoting media playback experience to multiplesuch clients 204 over network(s) 212. -
Example environment 200 illustrates a server side on the left and a client side on the right. An example implementation of the server side with a constructed media topology is described herein below with particular reference toFIG. 4 . An example implementation of the client side with a constructed media topology is described herein below with particular reference toFIG. 5 . -
FIG. 3 is a block diagram illustrating a remotingmedia playback scenario 300 that includes an examplemedia format negotiation 306. As illustrated, remotingmedia playback scenario 300 includesserver 202 andclient 204.Server 202 includes one or moreserver media modules 302.Client 204 includes one or moreclient media modules 304. -
Server media module 302 includes a mediadata format administrator 308.Client media module 304 includes amedia topology constructor 310.Server media module 302 andclient media module 304 may be comprised of multiple other modules. Mediadata format negotiation 306 may include multiple negotiation-related communications, such as communications 306(A) and 306(B). Remotingmedia playback scenario 300 also includes media data that is in transit 208(T). - Server and
client media modules Server 202 andclient 204 may be realized as devices. Example devices are described further herein below with particular reference toFIG. 10 . - In an example embodiment, media
data format negotiation 306 includes at least two media-related communications 306(A) and 306(B). Mediadata format administrator 308 ascertains at least one media data format of identified and/or requested media data. The identified media data is usually requested byclient 204. Mediadata format administrator 308 sends at least one media data format 306(A) tomedia topology constructor 310. It should be understood that other media modules at the server and/or the client may facilitate the transfer of communications between mediadata format administrator 308 andmedia topology constructor 310. - Media topology constructor 310 attempts to construct at client 204 a media topology responsive to media data format 306(A). If
media topology constructor 310 is capable of constructing a media topology to play media data in the at least one media data format, then the attempt is successful. Ifmedia topology 310 is unable to construct the media topology, the attempt is failed.Media topology constructor 310 sends a topology construction notification 306(B) indicating the result of the topology construction attempt to mediadata format administrator 308. By way of example only, the indicated result of topology construction notification 306(B) may be success or failure. - If the indicated result is success,
server media module 302 learns that a media topology has been successfully constructed byclient media module 304. Consequently,server media module 302 may send media data in transit 208(T) in an unrendered form of media data format 306(A) towardclient media module 304. If, on the other hand, the indicated result is failure,server media module 302 learns that a media topology was not successfully constructed byclient media module 304. Consequently,server media module 302 may send media data in transit 208(T) in a rendered form (e.g., as bitmapped images) towardclient media module 304. Alternatively, a failure result may prompt mediadata format administrator 308 to send another media data format 306(A) towardmedia topology constructor 310 when the requested media data is available in another format. Furthermore, a failure notification may alternatively precipitate a disallowance of remoting media playback withclient 204 for the requested media data. -
FIG. 4 is a block diagram of anexample server side 400 of a remoting media playback scenario. As illustrated,server side 400 of a remoting media playback scenario includes amedia player 402 that constructs amedia playback topology 404 on server 202 (ofFIGS. 2 and 3 ).Media playback topology 404 includes aclock 406, at least onesource node 408, one or moreintermediate nodes 410, and at least one servertransmission sink node 412.Clock 406 controls the timing of data flow throughnodes FIG. 3 ) ofserver 202 constructsmedia playback topology 404, which may then function as a module thereof. In operation,source node 408 retrieves the identified media data (e.g., from media data in storage 208(S)). The media data may be retrieved from, for example, a file, a network, and so forth.Source node 408 forwards the retrieved media data to intermediate node(s) 410 of a media topology nodal chain ofmedia playback topology 404. Intermediate node(s) 410 may perform various operations on the media data. Because the rendering is being performed at the client, these operations may include any of those that do not transform the data. Intermediate node(s) 410 (e.g., a finalintermediate node 410 if multiple ones are present) forwards the media data to servertransmission sink node 412. - Server
transmission sink node 412 sends unrendered media data towards the client. It also sends events that are relevant to playing the media data, such as clock state transitions, towards the client. Thus, servertransmission sink node 412 sends media data in transit 208(T) toward the client. Media playback topology on the client side is described below with particular reference toFIG. 5 . -
FIG. 5 is a block diagram of anexample client side 500 of a remoting media playback scenario. As illustrated,client side 500 of a remoting media playback scenario includes a duplicatedmedia player 502 that constructs amedia playback topology 504 on client 204 (ofFIGS. 2 and 3 ).Media playback topology 504 includes aclock 506, at least one clientreception source node 508, one or moreintermediate nodes 510, and at least onesink node 512.Clock 506 controls the timing of data flow throughnodes - In an example embodiment, client media module 304 (of
FIG. 3 ) ofclient 204 constructsmedia playback topology 504, which may then function as a module thereof. In operation, clientreception source node 508 receives media data in transit 208(T) from the server (e.g., directly or indirectly from server transmission sink node 412). Clientreception source node 508forwards media data 208 tointermediate nodes 510 of a media topology nodal chain ofmedia playback topology 504. - Intermediate node(s) 510 perform various operations on the media data to transform the media data into renderable media data. By way of example only, such operations may include decoding, re-sampling, and so forth. Intermediate node(s) 510 (e.g., a final
intermediate node 510 if multiple ones are present) forwards the renderable media data to sinknode 512.Sink node 512 renders the media data on an appropriate device (e.g., media data presentation device 210 (ofFIG. 2 )) atclient 204. An appropriate device includes, by way of example but not limitation, a display screen or window thereof for video or a speaker for audio, or both for multimedia types of media data. -
FIG. 6 is a flow diagram 600 that illustrates an example of a method that involves a media format negotiation for media playback in a remoting scenario. Flow diagram 600 includes ten (10) blocks 602-620. Although the actions of flow diagram 600 may be performed in other environments and with a variety of hardware, firmware, software, fixed logic circuitry, etc. combinations, the illustrated aspects ofFIGS. 2-5 may be used, by way of example only, to implement the method of flow diagram 600. - In an example embodiment, starting at
block 602, a format negotiation begins between a server and a client for a media remoting scenario. For example, a mediadata format negotiation 306 may be initiated between aserver media module 302 of aserver 202 and aclient media module 304 of aclient 204. - At
block 604, the server sends at least one media data format to the client. For example, a mediadata format administrator 308 ofserver media module 302 may send at least one media data format 306(A) toclient media module 304 overnetworks 212. For instance, one video format and one audio format may be sent. Alternatively, one video or one audio format (but not both) may be sent. Furthermore, multiple media data formats may be sent toclient media module 304 so that a media topology for each of them may attempt to be constructed, either sequentially or in parallel. - At
block 606, the client receives the at least one media data format from the server. For example,media topology constructor 310 ofclient media module 304 may receive media data format 306(A) from mediadata format administrator 308. - At
block 608, the client attempts to construct a media topology at the client, with a success or failure resulting. For example,media topology constructor 310 may attempt to construct amedia topology 504 atclient 204. This attempt may be a success or a failure. - At
block 610, the client sends a notification to the server indicating the result of the media topology construction attempt. For example,media topology constructor 310 may send a topology construction notification 306(B) indicating a success or a failure result to mediadata format administrator 308. If multiple media data formats are sent tomedia topology constructor 310, multiple media topology constructions may be attempted until a successful result is achieved or until all received media data formats are exhausted. In this embodiment, notification 306(B) may explicitly indicate the media data format for which a media topology was successfully constructed. - At
block 612, the server receives from the client the notification indicating the result of the media topology construction attempt. For example, mediadata format administrator 308 may receive topology construction notification 306(B) frommedia topology constructor 310. - At
block 614, the server determines if the media topology construction attempt at the client resulted in a success or a failure. For example, mediadata format administrator 308 may determine if topology construction notification 306(B) indicates a successful result or a failure result. If the indicated result was a success, flow diagram 600 continues at block diagram 616. If the indicated result was a failure, flow diagram 600 continues atblock 620. - At
block 616, the server constructs a media topology at the server using a server transmission sink node that does not render the media data. For example,server media module 302 add a servertransmission sink node 412 to amedia topology 404 atserver 202. In such an example embodiment,media topology 404 is not completely constructed until a successful result is indicated in a notification received from the client. One or more other nodes (e.g.,source node 408,intermediate nodes 410, etc.) may be constructed prior to receiving the notification. - At
block 618, the server sends unrendered media data to the client. For example,server media module 302 may sendunrendered media data 208 from servertransmission sink node 412 overnetwork 212 to a clientreception source node 508 ofclient media module 304. Theunrendered media data 208 may then be transformed atintermediate nodes 510 and rendered atsink node 512 onclient 204. - At
block 620, the server repeats the method of flow diagram 600 (e.g., from block 604), or the server implements a fallback option. For example, if fewer than all available media data formats have been sent toclient 204 for a media topology construction attempt, then at block 604 a different media data format may be sent to the client. Alternatively or after the available media data formats are exhausted, a fallback option may be implemented. Example fallback options include, but are not limited to, the server sending bitmap images to the client, the server disallowing remoting media playback on the client, and so forth. -
FIGS. 7A , 7B, 8, and 9 illustrate an example sequence diagram for different server and client components during a media communications exchange that includes a media format negotiation.FIGS. 7A and 7B are directed toparts FIGS. 8 and 9 are directed to a response phase—withFIG. 8 reflecting a successful topology resolution at the client andFIG. 9 reflecting a failed topology resolution at the client. The sequence diagram illustrates a relatively specific example implementation for format negotiation in a media remoting scenario. For example, the illustrated implementation involves a terminal server type of media remoting scenario. - As illustrated, there are three
server components client components server media player 702, a terminalserver remoting plugin 704, aformat handler 706, aterminal server client 708, andmedia playback infrastructure 710.Server media player 702 is a specific example ofmedia player 402. Terminalserver remoting plugin 704 is a plugin forserver media player 702 to facilitate providing media playback in terminal server type remoting scenarios.Format handler 706 is a specific example of mediadata format administrator 308. -
Terminal server client 708 is realized as a custom media player that is a specific example of duplicatedmedia player 502 that is capable of interacting withformat handler 706.Media playback infrastructure 710 is a specific example ofmedia playback topology 504 at the client.Terminal server client 708 andmedia playback infrastructure 710 jointly perform at least some of the functionality ofmedia topology constructor 310, as is described further herein below. By way of example only, one or more of these components may be implemented using Media Foundation™ technology. -
FIGS. 7A and 7B areparts Sequence diagram portion 700A ispart 1 of the example interrogation phase, andsequence diagram portion 700B ispart 2 of the example interrogation phase. - At
action 712, it is checked ifserver media player 702 is running in a remote session. Ataction 714,server media player 702 instructs terminalserver remoting plugin 704 to update the partial media topology. Ataction 716, terminalserver remoting plugin 704 finds source node(s) for the media topology. Ataction 718, terminalserver remoting plugin 704 ascertains the media format(s) of the source of the identified audio and video media data. Ataction 720, terminalserver remoting plugin 704 asksformat handler 706 to determine if the ascertained audio and video formats are supported by the requesting client. - At
action 722 ofsequence diagram portion 700B (ofFIG. 7B ),format handler 706 checks a format cache to determine if the requesting client has an entry therein. If so, then it may be determinable from the format cache that the requesting client does support the ascertained media formats. If not, then the sequence continues ataction 724. Ataction 724,format handler 706 asksterminal server client 708 if the client supports the indicated audio and video formats. - At
action 726,terminal server client 708 instructsmedia playback infrastructure 710 to create a media session. Ataction 728,terminal server client 708 creates a custom media source (e.g., client reception source node 508) for a media topology. Ataction 730,terminal server client 708 constructs additional nodes to form a partial media topology. Ataction 732,terminal server client 708 instructsmedia playback infrastructure 710 to resolve the media topology responsive to the indicated audio and video formats. -
FIG. 8 is an example sequence diagram 800 between different server and client components for a successful result for a response phase of a media format negotiation. At action 802,media playback infrastructure 710 provides terminal server client 708 a topology resolved notification indicating that the attempt to resolve the topology at the client was successful. Ataction 804,terminal server client 708 informsformat handler 706 that the formats are supported. Ataction 806,format handler 706 updates the format cache by including an entry positively associating the requesting client with the ascertained audio and video formats. - At
action 808,format handler 706 informs terminalserver remoting plugin 704 that media remoting is enabled. Ataction 810, terminalserver remoting plugin 704 constructs the server media topology with terminal server sink(s) (e.g., with a server transmission sink node 412). Ataction 812, terminalserver remoting plugin 704 returns control toserver media player 702 with terminal server media remoting enabled. -
FIG. 9 is an example sequence diagram 900 between different server and client components for a failure result for a response phase of a media format negotiation. Ataction 902,media playback infrastructure 710 provides terminal server client 708 a failed to resolve topology notification indicating that the attempt to resolve the topology at the client has failed. Ataction 904,terminal server client 708 informsformat handler 706 that the formats are not supported. This informing may be explicit. Alternatively, the informing may be by indicating a failure to fully construct a media topology responsive to the formats. With some media technologies, a specific error code (e.g., indicating that topology construction failed because of incompatible formats) may be produced at the client and forwarded to the server. However, for certain implementations, failure to construct the topology for any reason may be sufficient motivation to avoid sending to the client unrendered media data. Ataction 906,format handler 706 updates the format cache by ensuring that no entry positively associates the requesting client with the ascertained audio and video formats. Any existing associations may be removed and/or a negative association indicating that formats are not supported may be included. - At
action 908,format handler 706 informs terminalserver remoting plugin 704 that media remoting is not enabled. Twoexample fallback options action 910A, terminalserver remoting plugin 704 returns control toserver media player 702 with bitmap-based media remoting enabled. As a second fallback option, ataction 910B-1, terminalserver remoting plugin 704 constructs the server media topology with a null sink. Then, ataction 910B-2, terminalserver remoting plugin 704 returns control toserver media player 702 with no media playback remoting enabled for the requesting client for the requested media data in this session. -
FIG. 10 is a block diagram of anexample device 1002 that may be used to implement format negotiation for media remoting scenarios.Multiple devices 1002 are capable of communicating over one or more networks 212 (also ofFIG. 2 ). Hence,servers 202 and/orclients 204 may be realized asdevices 1002. Network(s) 212 may be, by way of example but not limitation, an internet, an intranet, an Ethernet, a public network, a private network, a cable network, a digital subscriber line (DSL) network, a telephone network, a Fibre network, a Grid computer network, an avenue to connect to such a network, a wireless network, a mesh network, some combination thereof, and so forth. - As illustrated, two devices 1002(1) and 1002(n) are capable of engaging in communications via
network 212. Communications include, by way of example but not limitation, media-relatedcommunications 206. Although twodevices 1002 are specifically shown, one or more than twodevices 1002 may be employed, depending on implementation. - Generally, a
device 1002 may represent any computer or processing-capable device, such as a server device; a workstation or other general computer device; a data storage repository apparatus; a personal digital assistant (PDA); a mobile phone; a gaming platform; an entertainment device; a router computing node; a mesh or other network node; a wireless access point; some combination thereof; and so forth. As illustrated,device 1002 includes one or more input/output (I/O) interfaces 1004, at least oneprocessor 1006, and one ormore media 1008.Media 1008 include processor-executable instructions 1010. - In a described implementation of
device 1002, I/O interfaces 1004 may include (i) a network interface for communicating across network(s) 212, (ii) a display device interface for displaying information on a display screen, (iii) one or more man-machine interfaces, and so forth. Examples of (i) network interfaces include a network card, a modem, one or more ports, a network communications stack, a radio, and so forth. Examples of (ii) display device interfaces include a graphics driver, a graphics card, a hardware or software driver for a screen or monitor, and so forth. Examples of (iii) man-machine interfaces include those that communicate by wire or wirelessly to man-machine interface devices 1012 (e.g., a keyboard, a remote, a mouse or other graphical pointing device, etc.). - Generally,
processor 1006 is capable of effectuating, performing, and/or otherwise executing processor-executable instructions, such as processor-executable instructions 1010.Media 1008 is comprised of one or more processor-accessible media. In other words,media 1008 may include processor-executable instructions 1010 that are executable byprocessor 1006 to effectuate the performance of functions bydevice 1002. Processor-executable instructions may be embodied as software, firmware, hardware, fixed logic circuitry, some combination thereof, and so forth. - Thus, realizations for format negotiation for media remoting scenarios may be described in the general context of processor-executable instructions. Generally, processor-executable instructions include routines, programs, applications, coding, modules, protocols, objects, components, metadata and definitions thereof, data structures, application programming interfaces (APIs), etc. that perform and/or enable particular tasks and/or implement particular abstract data types. Processor-executable instructions may be located in separate storage media, executed by different processors, and/or propagated over or extant on various transmission media.
- Processor(s) 1006 may be implemented using any applicable processing-capable technology.
Media 1008 may be any available media that is included as part of and/or accessible bydevice 1002. It includes volatile and non-volatile media, removable and non-removable media, storage and transmission media (e.g., wireless or wired communication channels), hard-coded logic media, combinations thereof, and so forth.Media 1008 is tangible media when it is embodied as a manufacture and/or composition of matter. For example,media 1008 may include an array of disks or flash memory for longer-term mass storage of processor-executable instructions 1010, random access memory (RAM) for shorter-term storing of instructions that are currently being processed and/or otherwise executed, link(s) onnetwork 212 for transmitting communications, and so forth. - As specifically illustrated,
media 1008 comprises at least processor-executable instructions 1010. Generally, processor-executable instructions 1010, when executed byprocessor 1006, enabledevice 1002 to perform the various functions described herein. Such functions include, but are not limited to: (i) those functions ofserver media module 302 orclient media module 304; (ii) those actions that are illustrated in flow diagram 600 (ofFIG. 6 ) and/or the sequence diagrams ofFIGS. 7A-9 ; (iii) the functions of components 702-710 (ofFIGS. 7A et seq.); (iv) the nodes ofmedia playback topologies 404 and 504 (ofFIGS. 4 and 5 ); and so forth. - The devices, actions, aspects, features, functions, procedures, modules, data structures, protocols, components, communications, etc. of
FIGS. 1-10 are illustrated in diagrams that are divided into multiple blocks and other elements. However, the order, interconnections, interrelationships, layout, etc. in whichFIGS. 1-10 are described and/or shown are not intended to be construed as a limitation, and any number of the blocks and/or other elements can be modified, combined, rearranged, augmented, omitted, etc. in any manner to implement one or more systems, methods, devices, procedures, media, apparatuses, arrangements, etc. for format negotiation for media remoting scenarios. - Although systems, media, devices, methods, procedures, apparatuses, mechanisms, schemes, approaches, processes, arrangements, and other implementations have been described in language specific to structural, logical, algorithmic, and functional features and/or diagrams, it is to be understood that the invention defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
Claims (21)
1.-20. (canceled)
21. A method for maintaining distributed cache coherency across multiple clients accessing a file or a shared resource, the method comprising:
associating an oplock key with a first client, wherein the oplock key includes a file handle;
transmitting an oplock state request from the first client, the request indicating that the first client is locally caching one or more of: (i) write data, (ii) read data, and (iii) the file handle;
receiving the requested oplock state;
in response to determining that the first oplock state is broken, requesting a second oplock state; and
transitioning from the first oplock state to the second oplock state.
22. The method of claim 21 , wherein the oplock key is associated with a plurality of files.
23. The method of claim 21 , wherein the oplock key is generated by a protocol server.
24. The method of claim 21 , wherein determining that the first oplock state is broken comprises determining whether an open request associated with a file has the same oplock key as the first oplock state.
25. The method of claim 21 , wherein determining that the first oplock state is broken comprises determining whether a transition was made from the first oplock state to a state of lesser caching.
26. The method of claim 21 , further comprising sending an acknowledgement that the first oplock state is broken.
27. The method of claim 26 , further comprising sending an indication of a level at which the first oplock state is broken.
28. A computer-readable storage medium encoding computer executable instructions that, when executed by at least one processor, performs a method for maintaining distributed cache coherency across multiple clients accessing a file or a shared resource, the method comprising:
associating an oplock key with a first client, wherein the oplock key includes a file handle;
transmitting an oplock state request from the first client, the request indicating that the first client is locally caching one or more of: (i) write data, (ii) read data, and (iii) the file handle;
receiving the requested oplock state;
in response to determining that the first oplock state is broken, requesting a second oplock state; and
transitioning from the first oplock state to the second oplock state.
29. The computer-readable storage medium of claim 28 , wherein the oplock key is associated with a plurality of files.
30. The computer-readable storage medium of claim 28 , wherein the oplock key is generated by a protocol server.
31. The computer-readable storage medium of claim 28 , wherein determining that the first oplock state is broken comprises determining whether an open request associated with a file has the same oplock key as the first oplock state.
32. The computer-readable storage medium of claim 28 , wherein determining that the first oplock state is broken comprises determining whether a transition was made from the first oplock state to a state of lesser caching.
33. The computer-readable storage medium of claim 28 , further comprising sending an acknowledgement that the first oplock state is broken.
34. The computer-readable storage medium of claim 32 , further comprising sending an indication of a level at which the first oplock state is broken.
35. A computer system comprising:
one or more processors; and
a memory coupled to the one or more processors, the memory for storing instructions which, when executed by the one or more processors, cause the one or more processors to perform a method for maintaining distributed cache coherency across multiple clients accessing a file or a shared resource, the method comprising:
associating an oplock key with a first client, wherein the oplock key includes a file handle;
transmitting an oplock state request from the first client, the request indicating that the first client is locally caching one or more of: (i) write data, (ii) read data, and (iii) the file handle;
receiving the requested oplock state;
in response to determining that the first oplock state is broken, requesting a second oplock state; and
transitioning from the first oplock state to the second oplock state.
36. The system of claim 35 , wherein the oplock key is associated with a plurality of files.
37. The system of claim 35 , wherein determining that the first oplock state is broken comprises determining whether an open request associated with a file has the same oplock key as the first oplock state.
38. The system of claim 35 , wherein determining that the first oplock state is broken comprises determining whether a transition was made from the first oplock state to a state of lesser caching.
39. The system of claim 35 , further comprising instructions for sending an acknowledgement that the first oplock state is broken.
40. The system of claim 35 , further comprising instructions for sending an indication of a level at which the first oplock state is broken.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/421,643 US20120173739A1 (en) | 2007-05-16 | 2012-03-15 | Format negotiation for media remoting scenarios |
US14/084,447 US10015233B2 (en) | 2007-05-16 | 2013-11-19 | Format negotiation for media remoting scenarios |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/749,637 US8234385B2 (en) | 2007-05-16 | 2007-05-16 | Format negotiation for media remoting scenarios |
US13/421,643 US20120173739A1 (en) | 2007-05-16 | 2012-03-15 | Format negotiation for media remoting scenarios |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/749,637 Continuation US8234385B2 (en) | 2007-05-16 | 2007-05-16 | Format negotiation for media remoting scenarios |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/084,447 Continuation US10015233B2 (en) | 2007-05-16 | 2013-11-19 | Format negotiation for media remoting scenarios |
Publications (1)
Publication Number | Publication Date |
---|---|
US20120173739A1 true US20120173739A1 (en) | 2012-07-05 |
Family
ID=40028599
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/749,637 Active 2028-11-18 US8234385B2 (en) | 2007-05-16 | 2007-05-16 | Format negotiation for media remoting scenarios |
US13/421,643 Abandoned US20120173739A1 (en) | 2007-05-16 | 2012-03-15 | Format negotiation for media remoting scenarios |
US14/084,447 Active US10015233B2 (en) | 2007-05-16 | 2013-11-19 | Format negotiation for media remoting scenarios |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/749,637 Active 2028-11-18 US8234385B2 (en) | 2007-05-16 | 2007-05-16 | Format negotiation for media remoting scenarios |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/084,447 Active US10015233B2 (en) | 2007-05-16 | 2013-11-19 | Format negotiation for media remoting scenarios |
Country Status (1)
Country | Link |
---|---|
US (3) | US8234385B2 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110047214A1 (en) * | 2009-08-24 | 2011-02-24 | Samsung Electronics Co., Ltd. | Method and apparatus for sharing functions between devices via a network |
US20120102272A1 (en) * | 2008-06-26 | 2012-04-26 | Microsoft Corporation | Efficient file management through granular opportunistic locking |
US10015233B2 (en) | 2007-05-16 | 2018-07-03 | Microsoft Technology Licensing, Llc | Format negotiation for media remoting scenarios |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP4513029B2 (en) * | 2007-03-09 | 2010-07-28 | 株式会社東芝 | Information processing device |
US20100306406A1 (en) * | 2009-05-29 | 2010-12-02 | Alok Mathur | System and method for accessing a remote desktop via a document processing device interface |
US9235452B2 (en) * | 2010-02-05 | 2016-01-12 | Microsoft Technology Licensing, Llc | Graphics remoting using augmentation data |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070288743A1 (en) * | 2004-01-12 | 2007-12-13 | Cisco Technology, Inc. | Enabling stateless server-based pre-shared secrets |
US20080046718A1 (en) * | 2006-03-14 | 2008-02-21 | Grab Eric W | Federated digital rights management scheme including trusted systems |
Family Cites Families (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6006241A (en) * | 1997-03-14 | 1999-12-21 | Microsoft Corporation | Production of a video stream with synchronized annotations over a computer network |
US6449653B2 (en) * | 1997-03-25 | 2002-09-10 | Microsoft Corporation | Interleaved multiple multimedia stream for synchronized transmission over a computer network |
US6732162B1 (en) * | 1999-11-15 | 2004-05-04 | Internet Pictures Corporation | Method of providing preprocessed images for a plurality of internet web sites |
US7356245B2 (en) * | 2001-06-29 | 2008-04-08 | International Business Machines Corporation | Methods to facilitate efficient transmission and playback of digital information |
US7724281B2 (en) * | 2002-02-04 | 2010-05-25 | Syniverse Icx Corporation | Device facilitating efficient transfer of digital content from media capture device |
US20030177255A1 (en) * | 2002-03-13 | 2003-09-18 | Yun David C. | Encoding and decoding system for transmitting streaming video data to wireless computing devices |
US7376695B2 (en) * | 2002-03-14 | 2008-05-20 | Citrix Systems, Inc. | Method and system for generating a graphical display for a remote terminal session |
EP1627281A4 (en) * | 2003-05-12 | 2010-05-05 | Tekelec Us | Methods and systems for generating, distributing, and screening commercial content |
US7774375B2 (en) * | 2003-06-27 | 2010-08-10 | Microsoft Corporation | Media foundation topology |
KR101095769B1 (en) * | 2004-02-09 | 2011-12-21 | 액세스 시스템즈 어메리카즈 인코포레이티드 | A method and system for a security model for a computing device |
US7590750B2 (en) * | 2004-09-10 | 2009-09-15 | Microsoft Corporation | Systems and methods for multimedia remoting over terminal server connections |
US7966382B2 (en) * | 2004-12-29 | 2011-06-21 | Intel Corporation | Enabling access to media content in media servers in remote networks |
US7730157B2 (en) * | 2005-02-03 | 2010-06-01 | The Trustees Of Columbia University In The City Of New York | Methods, media, and systems for displaying information on a thin-client in communication with a network |
JP5301425B2 (en) * | 2006-03-17 | 2013-09-25 | ソニー株式会社 | Group content presentation and system and method for organizing group communications during group content presentation |
US8234385B2 (en) | 2007-05-16 | 2012-07-31 | Microsoft Corporation | Format negotiation for media remoting scenarios |
-
2007
- 2007-05-16 US US11/749,637 patent/US8234385B2/en active Active
-
2012
- 2012-03-15 US US13/421,643 patent/US20120173739A1/en not_active Abandoned
-
2013
- 2013-11-19 US US14/084,447 patent/US10015233B2/en active Active
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070288743A1 (en) * | 2004-01-12 | 2007-12-13 | Cisco Technology, Inc. | Enabling stateless server-based pre-shared secrets |
US20080046718A1 (en) * | 2006-03-14 | 2008-02-21 | Grab Eric W | Federated digital rights management scheme including trusted systems |
Cited By (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10015233B2 (en) | 2007-05-16 | 2018-07-03 | Microsoft Technology Licensing, Llc | Format negotiation for media remoting scenarios |
US20120102272A1 (en) * | 2008-06-26 | 2012-04-26 | Microsoft Corporation | Efficient file management through granular opportunistic locking |
US9047281B2 (en) * | 2008-06-26 | 2015-06-02 | Microsoft Technology Licensing, Llc | Efficient file management through granular opportunistic locking |
US9654585B2 (en) | 2008-06-26 | 2017-05-16 | Microsoft Technology Licensing, Llc | Efficient file management through granular opportunistic locking |
US20110047214A1 (en) * | 2009-08-24 | 2011-02-24 | Samsung Electronics Co., Ltd. | Method and apparatus for sharing functions between devices via a network |
US9634854B2 (en) * | 2009-08-24 | 2017-04-25 | Samsung Electronics Co., Ltd | Method and apparatus for sharing functions between devices via a network |
US10484195B2 (en) * | 2009-08-24 | 2019-11-19 | Samsung Electronics Co., Ltd | Method and apparatus for sharing functions between devices via a network |
Also Published As
Publication number | Publication date |
---|---|
US20140082061A1 (en) | 2014-03-20 |
US20080288519A1 (en) | 2008-11-20 |
US10015233B2 (en) | 2018-07-03 |
US8234385B2 (en) | 2012-07-31 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10015233B2 (en) | Format negotiation for media remoting scenarios | |
EP3750291B1 (en) | Collaborative editing of media in a mixed computing environment | |
US8655945B2 (en) | Centralized rendering of collaborative content | |
AU2019216773B2 (en) | Live-rendered and forkable graphic edit trails | |
JP2016539394A (en) | Method and apparatus for real-time sharing of multimedia content between wireless devices | |
CN102624695A (en) | Third party initiation of communications between remote parties | |
BR112021009629A2 (en) | method of processing user interface content, system, and non-transient computer readable media | |
US10659556B2 (en) | Progressive hybrid web application | |
US8706803B1 (en) | Client-side generation of preliminary version of network page | |
WO2015198124A1 (en) | System and method for transferring and synchronizing content between electronic devices | |
US11736240B2 (en) | Optimized kernel for concurrent streaming sessions | |
CN116193481A (en) | 5G core network processing method, device, equipment and medium | |
US10514850B2 (en) | Information processing system, server device, Information processing method, and computer program product | |
CN112350921A (en) | Message processing method, terminal and storage medium | |
US8037201B2 (en) | Content holder unit, information processing method, and program | |
KR20160140047A (en) | Method for caching of application for cloud streaming service and apparatus using the same | |
US10880583B2 (en) | Method, apparatus, terminal, and readable storage medium for offline caching | |
WO2023230797A1 (en) | Cross-system test method and apparatus | |
US11910044B1 (en) | Systems and methods for switching the processing of a live content stream to another datacenter | |
CN112243135B (en) | Multimedia playing method and device | |
CN113347234B (en) | Network information acquisition method, device, system, computer equipment and storage medium | |
CN117082124B (en) | Data transmission method, device, equipment, medium and product | |
WO2023131110A1 (en) | Inter-process communication method and device | |
US10416990B2 (en) | System and method for seamlessly patching shared libraries in server environment | |
CN115904543A (en) | Service implementation method, device, equipment and medium based on heterogeneous service framework |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034544/0541 Effective date: 20141014 |