EP2792119B1 - Fonctionnement de serveur proxy - Google Patents
Fonctionnement de serveur proxy Download PDFInfo
- Publication number
- EP2792119B1 EP2792119B1 EP12799244.4A EP12799244A EP2792119B1 EP 2792119 B1 EP2792119 B1 EP 2792119B1 EP 12799244 A EP12799244 A EP 12799244A EP 2792119 B1 EP2792119 B1 EP 2792119B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- secure
- server
- content
- user terminal
- data
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 claims description 27
- 238000004891 communication Methods 0.000 claims description 4
- 238000009434 installation Methods 0.000 claims description 3
- 238000011022 operating instruction Methods 0.000 claims description 2
- 230000008569 process Effects 0.000 description 19
- 230000004044 response Effects 0.000 description 13
- 238000010586 diagram Methods 0.000 description 7
- 238000013519 translation Methods 0.000 description 6
- 238000009826 distribution Methods 0.000 description 5
- 230000004048 modification Effects 0.000 description 5
- 238000012986 modification Methods 0.000 description 5
- 238000012545 processing Methods 0.000 description 5
- 238000004519 manufacturing process Methods 0.000 description 4
- 238000012913 prioritisation Methods 0.000 description 3
- 238000003860 storage Methods 0.000 description 3
- 238000010200 validation analysis Methods 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000006399 behavior Effects 0.000 description 1
- 230000003139 buffering effect Effects 0.000 description 1
- 230000000295 complement effect Effects 0.000 description 1
- 230000001010 compromised effect Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 230000010485 coping Effects 0.000 description 1
- 230000006837 decompression Effects 0.000 description 1
- 230000003111 delayed effect Effects 0.000 description 1
- 238000011900 installation process Methods 0.000 description 1
- 230000001404 mediated effect Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 230000000717 retained effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/16—Implementing security features at a particular protocol layer
- H04L63/168—Implementing security features at a particular protocol layer above the transport layer
-
- 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/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/563—Data redirection of data network streams
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
- H04L63/0281—Proxies
Definitions
- This invention relates to data retrieval processes, and in particular a process for retrieving data files from a content delivery database and delivering them to end users over a data network such as the "internet".
- data files carry various forms of content, such as video or sound files, software upgrades, etc.
- the present invention involves the selection and use of a content delivery network other than a default network selected by a content service provider, without modification to the content service provider's own service platform.
- Authenticated Channel a secure channel arranged to transfer data from a server to a client if and only if the server has been authenticated by the client e.g. one-way https.
- a Mutually Authenticated Channel is an Authenticated Channel where data can only be transferred if the Client and the Server have both authenticated each other, typically using X.509 certificates (e.g. https mutual).
- Client Player (14, Figure 1 ) An application, typically on a user terminal , for processing media files received from a data source and processing them for delivery to a user interface
- Client Proxy Configuration - a configuration in the User terminal to force it to send requests using specific Asset Locators via a Proxy Server such as a Redirection Server.
- CDN Content Delivery Network
- Content Distribution Provider - provider of a Content Delivery Network. Not necessarily associated with, or controlled by the Network Service Provider or Content Service Provider.
- Content Service Provider - a provider of data for an original content server.
- Device Identity - unique device identifier, often taking the form of a certificate (and associated private key ) that can be used by a server to authenticate the device. This may be burned into the device as part of the manufacturing process.
- Digital signature a mathematical scheme for demonstrating the authenticity of a digital message or document.
- a valid digital signature gives a recipient reason to believe that the message was created by a known sender, and that it was not altered in transit.
- Digital signatures are commonly used for software distribution, financial transactions, and in other cases where it is important to detect forgery or tampering.
- Public key certificate also known as a digital certificate or identity certificate
- URI Uniform Resource Identifier
- the format of the URI does not necessarily indicate the nature of the content, and so there is no reliable way for the network, or the user terminal, to identify the type of content from the URI alone.
- the URI may be accompanied by a digital signature in order to confirm that the client making the request is authorised to access the content delivery network. Examples are described in United States Patent Application US2009/031368 and European Patent Application EP1278112 .
- a Content Service Provider often has relationships with one or more Content delivery networks, and uses a media selector to identify the best CDN and associated Media Asset Locator to serve a given user terminal.
- the use of a media selector enables a Content Service Provider to use a CDN without losing sight of the requests for its content, and to enforce timing constraints without having to rely on precise synchronisation with the CDN.
- television "catch-up" content is often made available for a limited period only, but this limitation is difficult to police if the content is also duplicated in caches operated by CDNs.
- Content may also need to be withdrawn at short notice, for example if the information in the content becomes out of date, or subject to a legal injunction.
- the original content provider can replace the content with some other response, but the CDN might continue to make available its cached copies.
- a Network Service Provider may have a preferred Content delivery network which can be used to deliver a range of benefits including: lower network cost, use of prioritised delivery over the network, exemption from any broadband usage limits, and transcoding of assets for delivery to different user terminal types.
- CDN may locate streaming servers close to the edge of the network, so as to minimise the distance over which media needs to travel in order to reach the user terminal.
- the Network Service Provider CDN may also enable video content to be identifiable so that it can be prioritised over other data in order to avoid, or minimise the possibility of, exhaustion of buffered content at the user end, resulting in interruption of the content being viewed.
- Some media assets can require a relatively high bit rate over a relatively long period and so can make up a significant proportion of any usage limit applicable to an Internet user's account.
- Some service providers allow content from an authorised source, such as the website of a television broadcaster, to be exempt from such usage limits, for example because such content is paid for in some other way, such as a subscription or advertising revenue. It is therefore desirable that such content be identifiable, and this can be facilitated though use of the Network Service provider's choice of CDN.
- URI Universal Resource Indicator
- the same URI Universal Resource Indicator
- the service provider may wish to transcode media assets into appropriate formats before delivering them to the user terminal. This might be achievable via use of an appropriate CDN with transcoding capability.
- the Network Service Provider may also wish to monitor and control access, so that it can provide services tailored to its own customers. For example it may charge for certain material, or restrict access, for example to prevent content unsuitable for children from being downloaded during times when they are likely to be using the service. It may also substitute some content, for example to provide advertising or news more relevant to the user's location than that provided in the original content. These capabilities can all be facilitated through use of the Network Service Provider's choice of CDN.
- One way to achieve this would be for providers of such content to respond to data requests from subscribers of an approved network service provider by routing the requested data through a dedicated service platform (170, Figure 1 ) hosted by the network service provider, instead of the content distribution provider's own network 160 to which the user would otherwise be directed by the media selector 15.
- this requires modification to the content provider's media selector platform 15 to identify and authenticate users permitted to access the dedicated platform 170. This can be difficult to achieve, especially if more than one network service provider and/or more than one content provider are involved.
- Some network providers have accommodated the current shortage of IPv4 addresses by consolidating several user addresses under the same public network address, allocating separate private addresses to the individual users - known as Carrier Grade Network Address Translation (CG-NAT). It is thus not always possible for a content delivery provider external to the network to distinguish and authenticate requests from individual users, as they may share the same public address. The external content delivery service can only determine whether it should deliver data to the public address, and cannot distinguish between users sharing that address. This makes it impossible for the content service provider's CDN to employ signed media asset locators based on network addresses, and means that URI's could be passed on to enable access by users not entitled to such access.
- CG-NAT Carrier Grade Network Address Translation
- the present invention provides features of an alternative system which overcomes some of these difficulties whilst requiring no modification to the content provider's operating system.
- the inventions of the applicant's copending applications entitled “Data Retrieval Redirection” ( WO2013/088102 ) and “Network Terminal Validation” ( WO2013/088103 ) filed contemporaneously with the present application, provide further features which may also be used in co-operation with the present invention as defined by the appended independent claims.
- Many Content Service Providers operate media selectors which return a URI based on a secure scheme, such as https.
- Conventional user terminal software handles secure data that is to be transmitted to a proxy server by attempting to set up a secure tunnel to the specified location via the proxy, so that only the user and the specified location have access to the secure data, and it is not visible to the proxy server itself (See Figure 10 , tunnel 181).
- the proxy is required to process media asset location requests and issue re-direct responses, as the secure connection would prevent the proxy redirect server from reading the media asset request, or doing anything with it other than forward it to the specified URI. media asset request, or doing anything with it other than forward it to the specified URI.
- This problem may be avoided by providing a user terminal according to independent claim 1 and by configuring the user terminal software according to independent claim 5.
- the invention provides a method for routing data messages according to independent claim 3.
- the connection between the user terminal and the redirection server may be provided by a mutually authenticated connection.
- the user terminal may be configured by transmitting a downloadable data file to the device for installation on the device, the downloadable data file including operating instructions to configure the device to operate according to the invention.
- the connection between the user terminal and the redirection server may itself be a mutually authenticated connection,
- Figure 1 and Figure 2 both depict a user terminal 11 connectable to an access service network 12 such as the "Internet".
- the user terminal 11 can be a general purpose computer or a dedicated media terminal, and may be embodied in two or more intercommunicating devices. Among its functions, typically embodied in software, are a browser 13 for accessing data, a media player 14 for downloading video or audio streamed data, and an output 19 for displaying the data. In most practical applications all these devices would share the same connection to the internet 12.
- FIGS 1 and 2 also depict several functions operated by service providers and accessible from the user equipment 11 over the data network 12.
- a media selector platform 15 and a content delivery network 160 comprising a number of content delivery servers 160, which store content for download to users on request. These platforms derive this content from an Original Content Server 16, which they access as required if the content is not already stored on the individual server 160.
- the media selector platform 15 provides a listing, indexing or cataloguing function, and identifies the internet address (URI) of content stored in the Original Content Server 16 for access by the user. These functions are typically under the control of the content service provider.
- URI internet address
- FIG. 1 The process followed by this equipment is illustrated in Figure 1 .
- a user uses the browser 13 to access a content catalogue of available material, searchable for example by genre, title, date made available, etc, from which the user may select a item.
- the media selector 15 is invoked by the browser 13 to obtain a media asset location URI for that item.
- the platform 15 returns a message to the browser 13 identifying the media asset location for the selected content, in the form of a URI (step 22).
- the browser 13 forwards the media asset location to the media player 14 (step 23).
- the client player then transmits a request 260 to the first delivery platform 16 hosted by the original content provider, using the URI in the media asset location message.
- the delivery platform 16 uses the media asset location to determine the content to be delivered, which it then returns to the media player 14 (step 280) for display 19 (step 29). If the media asset location data is not valid the delivery platform returns an error message. Reasons for such invalidity may include time expiry - the content is no longer available for access. This prevents users from storing media asset location codes, or sharing them with other users, for later access.
- FIG. 2 depicts an arrangement using such a secondary content delivery server 17 which, like the content delivery servers forming the primary content delivery network 160, can also download content to users on request, either by retrieving such content from the Original Content Server 16, or from a cache 176 of data that has previously been so retrieved.
- Figure 3 is sequence diagram illustrating the processes operated by this system.
- Data is downloaded from the originator's delivery platform 16 once (step 27), (e.g. in response to the first customer request for it) and subsequently re-used for any subsequent requests.
- the platform 17 is typically much nearer the customer terminal 11, the network capacity required for delivery is reduced.
- this second content delivery server 17 It is desirable to limit access to this second content delivery server 17 to a specified category of users, so that other users are directed to the default network 160 provided by the content service provider. It is also desired to achieve this without modification to the content service provider's own service platform 15, 16. This is achieved this by using a redirection process mediated by a redirection server 18. The process is made subject to a validation process, typically under the control of a service provider, with whom the user 11 has a trusted (validated) relationship.
- the media player 14 of an authorised terminal 11 is configured to convert any media asset location code it receives so that the request is handled by the platform 17 instead of the originator's platform 16. In practice this is done using a redirection server 18, which provides a concordance between the address of the original content platform 16 and the address of the content platform 17. (For load balancing purposes and other reasons this concordance may vary over time, so the user terminal 14 cannot do the translation itself).
- the functional elements of the redirection server 18 are illustrated in more detail in Figure 4 . It should be understood that these elements may be embodied in software running on a general purpose computer.
- the redirection server 18 has an input 30 for receiving redirection requests 24 from user terminal 14 which has been configured (through an installed application 140) to identify requests addressed to the primary content delivery network 160 and to transmit them instead to the redirection server 18.
- the redirection server comprises a reader 31 for identifying the requested domain name, a retrieval system 32 for retrieving a corresponding proxy domain name from a concordance store 33, a message generator 34 for embodying the retrieved domain name in a new message for return to the client 14 through an output 38. Further features 35, 36, 37 of Figure 4 will be described later.
- a user could pass a URI received from the redirection server 18 to other, unauthorised users (not subscribers to the service provider hosting the delivery platform 17), allowing them to also access content from the delivery platform 17.
- a user could store the uri to allow multiple accessions of the same stream from the delivery platform 17.
- the platform 17 does not have visibility of the time stamp data controlling access to the primary content platform 16, so out-of-date content may remain on the platform 17 after it has ceased to be available from the originator's own service, or has been modified, which would allow a user who has stored the uri to continue to retrieve it.
- Unauthorised access by users not subscribing to the service provided by the delivery platform server 17 would also result in a loss of revenue to the service provider.
- the interaction 24, 25 between the user media player 14 and the redirection server 18 is subject to an authentication process 35, 36.
- This will be referred to as mutual authentication because the client and server are both required to prove their authenticity to each other.
- the client (user terminal 11) is required to prove to the redirection server 18 that it is authorised to have access to the secondary content delivery platform 17.
- the necessary configuration software to access the redirection server 18 includes a public key certificate and a "private" key, wherein the public key certificate can be checked for authenticity by a "public" certification authority key stored in the redirection server 18 for use by the validity checker 35.
- a proxy configuration 140 is installed in the client player device 14.
- This configuration can be installed by any suitable secure means, typically by being “burnt in” to the device on manufacture. However, a download from the service provider may be possible if a secure means of doing so is available as will be discussed with reference to Figure 5 . Provided that the service provider has control of the installation of this configuration 140, its presence on the device 14 is confirmation that the device is authorised to access the redirection processor 18.
- the functional elements of the client player 14, as configured by the proxy configurator 140, are illustrated in Figures 5 to 8 , which together illustrate the various information flows that take place.
- the various components are an input 40, an output 45, a processor 41 for handling incoming messages, a redirection store 42 for maintaining a concordance of redirection addresses, a certification store 43 for maintaining an authenticity certificate, message compiler 44 for assembling outgoing messages, a streaming compiler 46 for processing streamed content, including decompression, buffering and other functions, and a central processor 47 for co-ordinating the operation of the other functions 40-46.
- the configuration process itself may be performed by software installed in the client player 14 on manufacture or, as illustrated in Figure 5 , by download from a storage medium such as a magnetic disc, or from a technician's computer during a site visit, or by download over the internet from a site managed by the service provider.
- the download 20 is delivered through an appropriate input device 40 and installed on the CPU 47, which stores the appropriate redirection instructions and certificate in the respective stores 42, 43. Downloading may also be used to update subscriber details, for example to renew a certificate to confirm payment of a subscription for the service.
- the certificate 43 can be used for other purposes in addition to the redirection process 42, and the two elements do not necessarily have to both be loaded as part of the same process. So for example the certificate 43 might be burned in on manufacture, whilst the proxy configuration 42 might be downloaded as part of a user terminal software upgrade at a later stage, using the process illustrated in Figure 6 .
- the media selector when a user makes an input 21 through the browser 13 to the media selector 15 to request an item of media content, the media selector returns a media asset location 22 to the browser which forwards it to the media player 14 (step 23).
- the incoming message processor 41 reads the media asset location and, under the control of the redirection address function 42 (which has been programmed by the configuration 140) determines if the media asset location address 23 meets predetermined criteria identifying it as suitable for redirection. If the media access location is so identified, the compiler 44 incorporates it in a message 24, to be forwarded via the output 45 to the proxy redirection server 18.
- the redirection server 18 has a validity checking system 35 operating in parallel with the redirection processor 31 - 33.
- the mutual authentication process 24 involves the transmission by each party of a "public key certificate": a data string including identification details, including the public key, together with a copy of the same data, or a string derived from it, which has been encrypted by a trusted third party certification authority's private key. Each party can thus use the public key in the certificate itself to verify that the certificate originates from the owner of the respective private key.
- an authentication processor 36 permits redirection data requests to be processed (31-33) and applies a signature to the redirection messages compiled in the message generator 34, together with a time stamp 37, and transmits it back to the requesting device through the output 38.
- Alternative messages may be generated if the validity check fails.
- Public key certificates are used for the purpose of verifying the identity of the client (by the redirection server) and the redirection server (by the client). This is done at the connection-establishment stage, which creates a secure mutually-authenticated channel for subsequent communication of a media request.
- Digital signatures are used to protect the media asset locators 22, 26, that are returned by both the primary CDN 21 and the proxy server 18.
- the media asset locators contain information such as a time expiry and/or IP address restriction which cannot be tampered with.
- the signature ensures that any attempt to tamper with the media asset locator will be detected, enabling rejection of that media asset locator as invalid.
- the user terminal may be accessed by Carrier Grade Network Address Translation (CGNAT).
- CGNAT Carrier Grade Network Address Translation
- IPv4 32-bit
- IPv6 128-bit addresses
- Figure 9 is a schematic depiction of an interface between a service provider's own network 12 and the public network 120.
- the translation between public and private URIs takes place at the interface 121 between the service provider's own network 12 and the rest of the network 120. Only the public IP address is visible to external parties, and the private IP address is only visible to the local network. Thus, the external media selector 15 would authenticate the user's public URI, which is shared with many other users, but the URI subsequently presented to the secondary media server 17, provisioned by the service provider, would use the private IP.
- the proxy redirection solution with re-signing avoids this difficulty, because the redirection server 18 generates a new signature (authentication) of the request using the private IP address which is subsequently presented to the media server 17.
- This facility also allows the invention be used to enable a small internet service provider, or a small private network such as a hotel or small business, to provide access to content specific to its users using an externally hosted content provider.
- Access to the redirection server 18 is only possible from user terminals having the corresponding proxy configuration 140 installed, and only requests authenticated by the redirection server 18 are accepted by the media platform 17.
- a service provider may host multiple content delivery platforms 17, each only accessible by user terminals 11 having the appropriate respective configuration 141 allowing authentication using a respective redirection and authentication server 18.
- a difficulty can arise if the Content Provider operates a media selector 15 which returns a Media Access Locator 22 that specifies a secure scheme e.g. the URI is in "https" format. Content providers do this to ensure that the connection between the user 11 and content delivery server 16; 170 is secure.
- conventional user terminal software handles secure (https) data that is to be transmitted via a proxy server (18) by attempting to set up a secure "tunnel" 181 between the user terminal 11 and the specified location via the proxy 18, so that the only the user and the specified location have access to the secure data.
- the message compiler 44 would generally set up a secure link 181 between the user terminal and the address specified, (tunnel generation function 441) to be routed by way of the specified proxy.
- the media access locator 251 would therefore not be visible to the proxy server 18 itself.
- Such an arrangement would not be suitable if the proxy is required to redirect the media asset location request 251, as the secure connection 181 would prevent the proxy redirect server from reading the media asset request, or doing anything with it other than forward it to the specified URI 16.
- the proxy must be able to read the media asset location 251 in order to generate the redirected media asset location 26.
- the incoming message processor 41 includes a discrimination function 411 which identifies incoming asset location addresses 23 arriving from a specified source (media asset location server 15), or of a specified type (e.g locations for media assets) and directs the message compiler 44 to handle such requests by setting up a secure connection only between the user terminal 14 and the redirect server 18, so that the redirect server 18 can process the request 251 passed over the connection. For such media access location requests, the tunnel starting at the user terminal 11 therefore terminates at the proxy server 18.
- a discrimination function 411 which identifies incoming asset location addresses 23 arriving from a specified source (media asset location server 15), or of a specified type (e.g locations for media assets) and directs the message compiler 44 to handle such requests by setting up a secure connection only between the user terminal 14 and the redirect server 18, so that the redirect server 18 can process the request 251 passed over the connection.
- the tunnel starting at the user terminal 11 therefore terminates at the proxy server 18.
- the user terminal is arranged so that secure media access locators 251 are passed on to the proxy redirection 18 via a mutually authenticated channel that is based on the identity of the proxy redirection itself, as opposed to the identity of the CDN server 18 identified by the Media Access Locator 251.
- This differs from typical client device behaviour when proxying https requests, which usually entails setting up a secure tunnel 181 to the destination server via the proxy 18, such that the proxy 18 is unable to decrypt the contents.
- the user terminal 11 handles secure data location addresses that are to be handled by a proxy server, other than media access locators, by setting up a secure tunnel 181 to a server specified by the media access locator, by way of the proxy 18, in the usual way.
- the secure redirection server 18 assesses the incoming media asset location address (URL) 251, constructs a new URI and signature that is appropriate for the content delivery network 17, and sends this back to the client 14 using a redirection response 26.
- the secure redirection server 18 only accepts requests from trusted authenticated clients which have satisfied the authentication process 24, so it is not possible for a rogue client to use the proxy to bypass the original media server's URI signature.
- the redirection server 18 checks the authentication certificate, (e.g. by applying a public key to decrypt the certificate sent by the client player). Authentication messages that will be recognised by the validity checker 35 in the redirection server 18 can only be generated by a client player 14 having a valid certificate 43 installed so, provided the network operator maintains control of the installation process for the configuration application 140, the operator can be sure that any client player 14 generating authentication messages 24 is doing so under the operator's authority.
- the proxy name retrieval system 32 creates a new address URI by substituting the domain name of the original media source 15 by that of the delivery platform 17, also providing signature and time stamp or other authentication data which is verifiable by the media player 17.
- the new details are returned to the client player 14 (step 25).
- a secure connection is set up between the redirect server 18 and the secondary content server 17, and the redirect request 26, 252 tunnelled directly to the secondary content server 17, including an instruction to return the requested content 28 to the client player 14 from which the original request 251 was received.
- the client player 20 receives the new media asset request data 25 (which, as indicated above, carries a signature that can only be validated by the secondary content server, so the user of the terminal 11 cannot read it directly, or tamper with it) and compiles it into a new message 26 to be sent to the platform 17, carrying the details in the data 25 received from the redirection server 18. This ensures that the secondary content delivery server 17 only receives media requests 252 that have been recently generated by the redirect server 18.
- the platform 17 checks the time stamp and other authentication data in the media request 26 it receives from the client player 14.
- the authentication data provides proof that the client player making the request has had the proxy configuration 140 installed. Since download of this configuration is under the control of the service provider, the necessary authentication 24 will only be present if the service provider has authorised the client player to use the service.
- the media location request 24 also includes a time stamp. This is checked by the platform 17 to ensure that the request 26 was generated in response to a very recent response from the media selector 12, and thus that the data requested has not been withdrawn by the original data provider 16. This ensures that each accession through the platform 17 is made in response to an original request made to the host media selector 15, allowing the original provider to retain an overview of all such requests, and to control access to the data.
- time-expired media assets cannot be accessed: if a user 14 attempts to use a stored copy of the new media asset locator held in the redirected request 26 the asset locator 24, the redirection server 17 will reject it as time expired. If the user attempts to generate a new redirection message, by using the browser to connect with the media selector platform 15 associated with the media asset's originator, the request will be rejected because the service provider has disabled access to that content.
- the requests 24, 26 cannot be copied and used by unauthorised client players because they are unable to be authenticated for connection to the proxy redirection server 17 and content delivery platform 18, as they do not have the private key held in the proxy configuration 140. If the authentication details are verified, the delivery platform 17 first checks the data cache 176 to determine if the requested media data file is present in the cache (step 270), and retrieves it from the cache if it is present (step 271). However, if this is the first request for that resource material, and it is therefore not already present in the cache, the platform 17 sources the asset from the original source 16 (step 27). As well as delivering the data to the user terminal 14 (step 271), the platform also stores a copy in its data cache 176 for easier retrieval in response to subsequent requests.
- the media data file identified by the delivery platform player 17 as corresponding to the request 26 is then returned (step 28) to the client player 14.
- the content is passed to the streaming processor 46, which processes the streamed content for output (step 29) on a device 19 such as a television set.
- the processing performed by the processor 46 will depend on the nature of the output display 19.
- the proxy configuration 140 may be arranged to cause the requests 26 it generates to be configured to request content in a form suitable for the particular output device 19. For example, if the user device 11 is a general purpose computer, the internet connection 12 has a high bandwidth, and the output is a high definition television 19, a high definition, high bandwidth data stream can be requested.
- the user device 11 is a small portable device, with a low definition monochrome output 19, and connected to the internet 12 over a low bandwidth wireless connection, a lower bandwidth data stream with less definition would be appropriate.
- the ordering processor 17 would be arranged to configure the data stream 28 in accordance with the details of the request 26.
- platforms 16, 17 may both retain media data for a period after requests 21 for that data cease to be valid. This allows users currently viewing content at the time of expiry of availability of that to complete their downloading and viewing of that content. Furthermore, the second platform 17 would not generally be informed by the owner of the primary content delivery platform 16 of the expiry or modification of the data in its cache 176. (The secondary platform "pulls" data from the primary platform - there is no "push” of data by the primary platform). In practice the data is retained in the cache until a specified time has elapsed with no accessions having been made, or until it needs to be overwritten to accommodate a more recent download.
- the present invention prevents out-of-date data being accessible from the cache 176, because no accessions can be made to such data from the cache 176, except in response to a request using a valid timestamp.
- the proxy configuration 140 in the client player 14 will only issue such a timestamp in response to a successful response 22, 23 being received from the media selector 15.
- the invention may be implemented in computer program software, any or all of which may be contained on various storage media so that the program can be loaded onto one or more general purpose computers or downloaded over a computer network using a suitable transmission medium.
- the computer program product used to implement the invention may be embodied on any suitable carrier, readable by a suitable computer input device, such as optically readable media and magnetic media.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Information Transfer Between Computers (AREA)
Claims (5)
- Terminal utilisateur pour un système de communication, pourvu d'un compilateur de messages (441) permettant de transmettre des messages de données à des adresses prédéterminées ;
pourvu d'un moyen de connexion sécurisée (45) permettant de transmettre des messages de données ayant une adresse d'emplacement de données sécurisée afin d'établir un tunnel sécurisé (181) jusqu'au serveur spécifié par l'adresse d'emplacement de données sécurisée,
pourvu d'un discriminateur (411) permettant d'identifier une adresse d'emplacement de données sécurisée, qui est un localisateur d'accès sécurisé aux médias identifiant un serveur parmi un ensemble prédéfini de serveurs médias connus,
pourvu d'un second moyen de connexion permettant de transmettre ledit localisateur d'accès sécurisé aux médias à un serveur de redirection de proxy (18), en suspendant l'établissement du tunnel sécurisé (181) jusqu'au serveur spécifié par le localisateur d'accès sécurisé aux médias (16) et en établissant à la place une connexion par tunnel (251) au serveur de redirection de proxy (18), ledit localisateur d'accès sécurisé aux médias étant transmis au serveur de redirection de proxy via la connexion par tunnel entre le terminal utilisateur et le serveur de redirection de proxy (18), et
pourvu de moyens permettant de recevoir un localisateur d'accès aux médias redirigé depuis le serveur de redirection de proxy. - Terminal utilisateur selon la revendication 1, pourvu en outre d'autres moyens de connexion sécurisée (43, 44) permettant d'établir une connexion mutuellement authentifiée (251) avec le serveur de redirection de proxy (18).
- Procédé de routage de messages de données ayant des adresses d'emplacement de données sécurisées, dans lequel les messages de données ayant une adresse d'emplacement de données sécurisée, autre qu'un localisateur d'accès sécurisé aux médias identifiant un serveur parmi un ensemble prédéfini de serveurs médias connus (16), sont transmises depuis un terminal utilisateur (11) en établissant un tunnel sécurisé (181) jusqu'à un serveur spécifié par l'adresse d'emplacement de données sécurisée, dans lequel un localisateur d'accès sécurisé aux médias identifiant un serveur parmi l'ensemble prédéfini de serveurs médias connus (16) est transmis à un serveur de redirection de proxy (18) via une connexion par tunnel entre le terminal utilisateur (11) et le serveur de redirection de proxy (18), en suspendant l'établissement du tunnel (181) jusqu'au serveur spécifié par le localisateur d'accès sécurisé aux médias (16) et en établissant à la place une connexion par tunnel au serveur de redirection de proxy (18), de façon à ce qu'un localisateur d'accès aux médias redirigé depuis le serveur de redirection de proxy soit reçu (26) par le terminal utilisateur.
- Procédé selon la revendication 3, dans lequel la connexion (251, 26) entre le terminal utilisateur et le serveur de redirection est une connexion mutuellement authentifiée.
- Procédé de configuration d'un terminal utilisateur (11) pour un système de communication consistant à transmettre au terminal un fichier de données téléchargeable (20) en vue de son installation sur le dispositif, le fichier de données téléchargeable comportant des instructions d'utilisation pour configurer le dispositif de façon à ce qu'il fonctionne selon la revendication 3 ou 4.
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
GB201150930 | 2011-12-16 | ||
GB201150929 | 2011-12-16 | ||
GB201150928 | 2011-12-16 | ||
PCT/GB2012/000871 WO2013088101A1 (fr) | 2011-12-16 | 2012-11-29 | Fonctionnement de serveur mandataire |
Publications (2)
Publication Number | Publication Date |
---|---|
EP2792119A1 EP2792119A1 (fr) | 2014-10-22 |
EP2792119B1 true EP2792119B1 (fr) | 2018-05-02 |
Family
ID=51538760
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP12799244.4A Active EP2792119B1 (fr) | 2011-12-16 | 2012-11-29 | Fonctionnement de serveur proxy |
Country Status (1)
Country | Link |
---|---|
EP (1) | EP2792119B1 (fr) |
-
2012
- 2012-11-29 EP EP12799244.4A patent/EP2792119B1/fr active Active
Non-Patent Citations (1)
Title |
---|
None * |
Also Published As
Publication number | Publication date |
---|---|
EP2792119A1 (fr) | 2014-10-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9380028B2 (en) | Proxy server operation | |
US8555367B2 (en) | Method and system for securely streaming content | |
US10140432B2 (en) | Method for scalable access control decisions | |
US7328344B2 (en) | Authority-neutral certification for multiple-authority PKI environments | |
US7783767B2 (en) | System and method for distributed media streaming and sharing | |
US8844001B2 (en) | IP-based mobile device authentication for content delivery | |
MXPA04007546A (es) | Metodo y sistema para proporcionar una tercera autenticacion de autorizacion. | |
US20100104105A1 (en) | Digital cinema asset management system | |
WO2005112334A2 (fr) | Procede et systeme pour la distribution fiable de contenu sur un reseau de communications | |
US20070168293A1 (en) | Method and apparatus for authorizing rights issuers in a content distribution system | |
MX2011003223A (es) | Acceso al proveedor de servicio. | |
CA2717222A1 (fr) | Systeme, dispositif et methode de transfert securitaire de donnees dans un reseau | |
CN101341691A (zh) | 授权与验证 | |
US9875371B2 (en) | System and method related to DRM | |
US20060112271A1 (en) | Cipher mail server device | |
EP2605477A1 (fr) | Fonctionnement de serveur proxy | |
EP2792119B1 (fr) | Fonctionnement de serveur proxy | |
EP2605479A1 (fr) | Validation de terminal de réseau | |
EP2605478A1 (fr) | Redirection de récupération des données | |
WO2012152813A1 (fr) | Procédé d'authentification entre un fournisseur de service de réseau de distribution de contenu et un propriétaire de contenu | |
US20020023222A1 (en) | Method and arrangement for managing data transmission in a data network | |
KR100932612B1 (ko) | 시디엔 서비스 망 시스템 및 시디엔 서비스 망에서의 컨텐트 전송방법 | |
KR20050099108A (ko) | Drm 서비스 정책 제어 방법 | |
Dannewitz et al. | Internet Engineering Task Force S. Farrell Internet-Draft Trinity College Dublin Intended status: Standards Track D. Kutscher Expires: April 26, 2012 NEC |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 20140523 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
DAX | Request for extension of the european patent (deleted) | ||
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: BRITISH TELECOMMUNICATIONS PUBLIC LIMITED COMPANY |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: GRANT OF PATENT IS INTENDED |
|
INTG | Intention to grant announced |
Effective date: 20180131 |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE PATENT HAS BEEN GRANTED |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP Ref country code: AT Ref legal event code: REF Ref document number: 996418 Country of ref document: AT Kind code of ref document: T Effective date: 20180515 |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 602012045998 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: MP Effective date: 20180502 |
|
REG | Reference to a national code |
Ref country code: LT Ref legal event code: MG4D |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180502 Ref country code: ES Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180502 Ref country code: BG Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180802 Ref country code: NO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180802 Ref country code: FI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180502 Ref country code: LT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180502 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180803 Ref country code: HR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180502 Ref country code: LV Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180502 Ref country code: NL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180502 Ref country code: RS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180502 |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MK05 Ref document number: 996418 Country of ref document: AT Kind code of ref document: T Effective date: 20180502 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: CZ Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180502 Ref country code: RO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180502 Ref country code: PL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180502 Ref country code: EE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180502 Ref country code: SK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180502 Ref country code: AT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180502 Ref country code: DK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180502 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 602012045998 Country of ref document: DE |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180502 Ref country code: SM Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180502 |
|
PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |
|
26N | No opposition filed |
Effective date: 20190205 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180502 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MC Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180502 Ref country code: LU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20181129 |
|
REG | Reference to a national code |
Ref country code: BE Ref legal event code: MM Effective date: 20181130 |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: MM4A |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20181130 Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20181130 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20181129 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: BE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20181130 Ref country code: AL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180502 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MT Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20181129 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: TR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180502 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: PT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180502 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MK Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20180502 Ref country code: CY Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180502 Ref country code: HU Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO Effective date: 20121129 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180902 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R079 Ref document number: 602012045998 Country of ref document: DE Free format text: PREVIOUS MAIN CLASS: H04L0029060000 Ipc: H04L0065000000 |
|
P01 | Opt-out of the competence of the unified patent court (upc) registered |
Effective date: 20230623 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20231019 Year of fee payment: 12 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: FR Payment date: 20231020 Year of fee payment: 12 Ref country code: DE Payment date: 20231019 Year of fee payment: 12 |