Access control enhancements, network access unit and service provider server for delivery of video and other services

<u style="single">FIELD OF THE INVENTION</u>

0001The present invention relates to a method and apparatus for secure delivery of services over local access networks, and in particular shared medium access networks, and a system incorporating the same.

<u style="single">BACKGROUND TO THE INVENTION</u>

0002This invention relates to shared medium access networks, such as satellite, LMDS, UMTS, cable modem or fibre in the loop access networks, in particular to fibre to the home (FTTH). The following description relates to FTTH, but it will easily be seen how it applies to other scenarios with similar characteristics. FTTH networks can be made more economic by sharing fibre facilities and head end equipment across a number of customers. Passive Optical Networks (PONs) fall into this category. In such a network, a single head end node, normally physically located on the network provider's premises, connects to a number of customer located outstations via a passive optical splitter (POS) which provides a fanout to (typically) 16 outstations.

0003Traffic transmitted in the downstream direction (from the head end to the outstations) appears at all outstations and is selected by a given outstation based on an address included in a header associated with each data packet. In the upstream direction a multiple access protocol is used to ensure that only one outstation transmits information at a time.

0004Such networks can be used to transmit multiple services to a customer, including video services and data services. On the customer premises an Optical Network Unit (ONU) connects to the fibre network and provides one or more interfaces to which the customer can attach end user equipment. This equipment might include one or more Set Top Boxes (STBs) for interfacing video services to a television set and one or more personal computers. Each of these devices could connect via, for example, an Ethernet interface.

0005The ONU will normally be supplied by the network operator who can control the software .included within the ONU itself. Devices attached to the Ethernet interfaces, however, are often outside the control of the network operator and the end user may therefore be able to load software which is outside the control of the network operator.

0006Video services consist of television channels which can be selected for viewing by individual end users and can be classified into two categories: multicast and Video on Demand (VOD). Multicast video channels are viewed simultaneously by a number of users. Such channels may include, for example, standard broadcast channels, subscription channels (where the user pays a monthly fee for the right to view the channel whenever he wants) and pay per view channels (where the user pays to view a particular programme). VOD channels are programmes requested by a particular user and supplied only to that user. Each VOD channel requires a dedicated data path from a video server within the network. Multicast channels avoid dedicated paths from the server to each user by including multicasting features in the data path, typically using a router situated at the head end of the access network. When the first user requests a multicast channel, that channel is delivered to the head end router from the server and a connection is made through the router to the access network. If another user subsequently requests to view the same channel, a second connection is made within the router to cause the channel to be sent out on the interface to which the second user is connected. Since the second user is joining an existing channel, no additional data capacity is required on the link between the server and the router. Protocols exist for signalling from an end user device to a router to join and leave a multicast group. When the data transmission is based on Internet Protocol (IP), a multicast signalling protocol known as Internet Group Management Protocol (IGMP) may be used. Conventionally in IP networks, a multicast stream is given a destination IP address drawn from a group of addresses reserved for multicast IP packets. Similarly, when using Ethernet as the medium access control (MAC) layer, the destination MAC address is drawn from a group of addresses reserved for multicast Ethernet frames. Thus at both the IP layer and the MAC layer, the address used represents the content of the multicast data stream rather than identifying a specific destination.

0007An algorithm for mapping IP layer multicast addresses to MAC layer multicast addresses is given in the Internet Engineering Task Force (IETF) Request for Comment (RFC) 1112. This is a many to one mapping where a single MAC address could represent many different schemes. In systems using this mapping, the multicast channel cannot be identified uniquely at the MAC layer and the IP layer destination address must be checked to guarantee uniqueness. In a variation of the multicast protocol, known as source specific multicast (SSM), both the source IP address and the destination IP address are required to Identify uniquely a specific multicast stream. In a system using SSM the destination multicast MAC address is not guaranteed to be unique. Since current protocols do not reflect the source IP address in the source MAC address, SSM channels cannot be uniquely identified at the MAC layer and the source address at the IP layer must be checked.

0008A problem arises when the end user connection is a shared medium network (such as a PON): a multicast stream will be delivered to the ONUs situated on the premises of all end users on the PON whenever one of the users requests that stream and, by listening to traffic, on that address, a second user would be able to view the service even though he may not have paid to receive it. This could lead to loss of revenues to the content provider which is highly undesirable.

0009European patent application <patcit id="pcit0001" dnum="EP0994800A"><text>0994800</text></patcit> Is concerned with multicast transmission and shows that it is known for a sender to determine if a requesting receiver is authorized to receive the secure multicast transmission, and, if so, separately deliver the multicast transmission security information to each receiver. The receivers can then use the multicast transmission security information to, for example, decode a secure multicast transmission from the sender. To reduce the amount of traffic to the sender, this document proposes a multicast session security server capable of communicating with a plurality of senders and a plurality of requesting receivers. This server receives security information from the sender, including a list of authorised receivers, It then handles requests from receivers and determines if a requesting receiver Is authorized to receive the secure multicast transmission, if so, the multicast transmission security information, such as a security key needed to receive the secure multicast transmission, is sent to the requesting receiver. The approved receiver may then use this key to receive the secure multicast transmission from the sender.

0010<patcit id="pcit0002" dnum="WO004836A"><text>WO004836</text></patcit> shows an arrangement for multicasting of digital TV services, and of data from the internet. A receiver sends an order to an order server, using an ID and password. The order server prepares a list of the ordered services in a form the digital TV set can read, which is transmitted to the set. The set chooses which of the broadcast channels it can display. If a user wants to leave a multicast group, the order server is notified and awaits until it is polled by the multicast server according to the IGMP protocol. Only if there are no users does the multicast server act to cease sending packets to the program broadcaster's network.

0011<patcit id="pcit0003" dnum="EP088029A"><text>EP088029</text></patcit> shows using a directory server DS which has a list of authorised users for a conference. The user sends an ID and password to the DS. These are checked by the DS before the DS sends a multicast IP address and port number to the user, and an ATM address of a MARS server. The user can then connect to the MARS (multicast address resolution server) and a multicast server to undertake the conference.

0012<patcit id="pcit0004" dnum="EP0902569A"><text>EP0902569</text></patcit> shows how Unicast endpoint clients on an IP Unicast network are provided access to Multicast sessions on an IP Multicast network. When a request is received from a client for a copy of the page containing the Multicast sessions, an HTTP server sends a message back to the client requesting the user enter a login id and a password for authentication purposes. If the user is successfully authenticated the server returns a page to the client containing a list of sessions. When the client starts a selected session, the server then launches a control script which sends information about which multimedia tool to launch, and what UDP sockets (the Unicast IP address on the MUS and associated ports) to listen to and to send information to corresponding to the requested group.

<u style="single">OBJECT OF THE INVENTION</u>

0013The invention seeks to provide an improved method and apparatus for overcoming one or more problems associated with the prior art.

<u style="single">SUMMARY OF THE INVENTION</u>

0014According to one aspect of the present invention there is provided a network access unit as set out in claim 1. Additional features are set out In dependent claims.

0015The invention is also directed to a method according to Claim 10 by which the described apparatus operates and including method steps for carrying out every function of the apparatus.

0016The invention is also directed to a program for a computer according to Claim 18, comprising components arranged to perform each of the method functions.

0017Advantageously, the aspects of the present Invention provide improved security for multicast services (for example multicast video) with minimum increase In ONU complexity.

0018The preferred features may be combined as appropriate, as would be apparent to a skilled person, and may be combined with any of the aspects of the invention.

<u style="single">BRIEF DESCRIPTION OF THE DRAWINGS</u>

0019In order to show how the invention may be carried into effect, embodiments of the invention are now described below by way of example only and with reference to the accompanying figures in which: <ul id="ul0001" list-style="none"><li><figref idref="f0001">Figure 1</figref> shows a schematic diagram of a telecommunications network in accordance with the present invention;</li><li><figref idref="f0002">Figure 2</figref> shows a schematic diagram of an Optical Network Unit (ONU) in accordance with the present invention;</li><li><figref idref="f0003">Figure 3</figref> shows an example of multi-cast broadcast channel packages arrangement in accordance with the present invention; and</li><li><figref idref="f0004">Figure 4</figref> shows a further schematic diagram of a telecommunications network in accordance with the present invention.</li></ul>

<u style="single">DETAILED DESCRIPTION OF INVENTION</u>

0020Referring to <figref idref="f0001">Figure 1</figref>, there is shown a system overview of one possible embodiment of an end-to-end network for delivery of multicast video services incorporating a Passive Optical Network (PON) based access network. Only those elements relevant to the present invention are shown.

0021The headend 10 comprises a Router 110 and one or more Optical Line Termination units (OLTs) 120-121. The Router comprises a Packet Forwarder 111 and a signal processor 112 In the downstream direction, each OLT receives packets from the router, adds any protocol and control information needed to implement the PON protocol and converts the data stream to an optical signal for transmission onto the shared optical medium 20 to one or more end users. In the upstream direction, the OLT 120 receives an optical signal which has been multiplexed onto the medium by one or more ONUs 30, and extracts the data stream to be sent to the Router for onward transmission. Optionally, the OLTs 120-121 may be physically integrated into the head end router 110.

0022A Video Server 40 acts as the source of multiple multicast video programmes, each of which is transmitted as a separate packet stream identified by an address in the packet header. Typically, the data link 60 to the server will be a packet switched path across an IP network. In a practical system, multiple additional servers would be used to deliver many services to the end user.

0023A Billing and Administration function, or unit, 50 holds information identifying which multicast streams each end user is entitled to receive.

0024In the example network shown, each OLT connects to an optical network incorporating a signal splitter 210 such that a single OLT is able to exchange information with multiple ONUs 30 situated on end user premises. In a preferred embodiment the signal splitter 210 is a passive optical splitter.

0025Each ONU may connect to one or more end user information devices such as television Set Top Boxes (STBs) 70-71 and Personal Computers (PCs) 80 for video and data applications respectively.

0026<figref idref="f0002">Figure 2</figref> shows an example of ONU 30 in more detail. A Network Receive function 31 converts downstream optical signals from the network connection 211 into electrical signals and passes on to the Packet Filter 32 only those information packets intended for the attached user. Other packets directed to other PON users are blocked. The addresses of packets to be passed through are contained in the Address List 33. In this arrangement, the Address List may be modified dynamically according to the video channel requested by the end user.

0027The Packet Filter 32 extracts from the packet stream those packets which are directed to the Management Processor function 34 within the ONU. Other packets are passed on to the Ethernet Switch 35 to which multiple end user information devices 70-71, 80 are connected.

0028Information packets received by the ONU from end user devices 70-71, 80 pass via the Ethernet Switch 35 to the Control Packet Filter 36. Channel change requests from the end user are encapsulated into control packets by the Set Top Box 70-71, and PC 80 and sent to the ONU. Packets recognised as multicast video control packets are extracted and passed to the IGMP Vetting function 37. Other packets are forwarded to the Network Transmit function 38 which implements the PON upstream transmission protocol and sends packets 212 via the local PON to the head end 10 at the appropriate time.

0029Multicast control packets sent to the IGMP Vetting function 37 are checked against the Permitted Channels list 39. If the requesting user is eligible to receive the requested channel, the IGMP Vetting function forwards the request to the head end via Network Transmit function 38.

0030Optionally, instead of blocking a request for a prohibited channel, the IGMP Vetting function 37 may modify the content of the request packet and forward to the network a modified request to connect the end user device to a video stream inviting the user to subscribe to the service he has requested but is not yet eligible to receive.

0031Forwarding the IGMP request to the headend 10 when it is not present in the permitted channel list would cause the head end router to add the stream to the composite data stream transmitted on the shared downstream medium. A malicious user could initiate many (multi-cast) channel joins, thus increasing the amount of capacity occupied on the downstream link and potentially denying service to others. Consequently, requests for channels not on the permitted channel list are preferably not forwarded.

0032It would be technically possible to reduce the susceptibility to denial of service attacks by intercepting IGMP messages in the head end router, but this would require non-standard features in the router and may not scale well when large numbers of customers are connected.

0033Unless additional capabilities are added in the ONU, as described above, theft of service can only be addressed in the router by including encryption of the multicast streams within the head end equipment using additional hardware processing data streams at the line rate of the access network. Decryption in the ONU would increase complexity in a cost-sensitive area of the system.

0034It is desirable that the end user should be made aware when he requests channels he is not authorised to receive.

0035If the user makes repeated such attempts it may also be desirable to inform the management system, either as part of a policing function or a marketing opportunity.

0036Optionally, if the Vetting function detects (multiple) attempts to connect to unauthorised channels, the ONU 30 may send a message to the Billing and Administration system 50.

0037Once it is determined that the user is eligible to receive a requested channel, the Management Processor 34 is notified and it adds to the Address List 33 the multicast address which will be used in information packets carrying data for the selected channel. Such packets are then allowed through the Network Receive function 31 and forwarded to the Ethernet Switch 34 and thence to the end user information device 70-71, 80.

0038In the head end router 110, IGMP messages are forwarded to a Signalling Processor 112 which instructs the Packet Forwarder 111 to add the new connection to the selected multicast stream so as to cause the stream to be forwarded to the end user via the OLT, Because the vetting function in the ONU ensures that no requests for unauthorised channels are passed to the network, no additional vetting is needed in the router.

0039Optionally, instead of generating IGMP messages in response to user requests to change channels, the STB 70-71, 80 may instead generate control messages in some other format which is interpreted by the ONU and translated to IGMP messages before forwarding to the OLT. The ONU then act on the interpreted messages in a way similar to that described above for incoming IGMP messages.

0040The Permitted List 39 is populated from the head end 10 using management messages sent as part of the downstream traffic and delivered to the Management Processor 34 via the Packet Filter 32. The permitted list may take different forms depending on the implementation, including but not limited to: a list of specific channels which the customer is eligible to receive; a list of channels the customer is to be prevented from viewing; or a set of rules to be applied to a request to determine whether a given channel is to be permitted or not. (An example of a set of rules for this last alternative can be derived from the semantics of the Unix 'hosts.allow / hosts.deny' command.)

0041The system is preferably based on the Internet Protocol suite. In an ONU using bridging (MAC layer forwarding) the IGMP Vetting function 37 is preferably performed using MAC addresses; in an ONU using routing (IP layer forwarding) the IGMP Vetting function 37 is preferably performed using IP addresses. To minimise ONU complexity and improve throughput, blocking of prohibited incoming multicast channels via the Network Receive function may be performed using MAC address matching.

0042Where the mapping from IP layer multicast addresses to MAC layer multicast addresses uses IETF RFC 1112, and the IGMP Vetting function 37 is performed using MAC addresses, the IGMP Vetting function may also optionally check the destination multicast IP address. Where the mapping from IP layer multicast addresses to MAC layer multicast addresses uses IETF RFC 1112 and blocking of prohibited incoming multicast channels via the Network Receive function is performed using MAC address matching, the Network Receive function 311 may optionally also check the IP destination address, but preferably only if the MAC layer address matching function indicates that the user may be eligible to receive the designated stream.

0043Where source specific multicast (SSM) is used in conjunction with IP layer vetting, the vetting function should preferably check both source and destination addresses to determine eligibility to receive a particular stream. Where SSM is used in conjunction with MAC layer vetting, the vetting function should preferably also check the IP addresses. Where SSM is used, the Network Receive function should also preferably check the IP addresses. Where SSM is used, preferably the Network Receive function should check the IP addresses only if an address match is detected at the MAC layer.

0044At the video IP headend, a Protocol Stack such as MPEG-2/RTP/UDP/IP/PON Multi-cast Groups may be employed. Source addresses of IP and MAC are defined and transmitted.

0045All available video channels may be, and ideally are, provided to the OLT. The OLT is arranged to set up and maintain receipt of all IP multi-cast channels. There may, for example be 200 channels provided by a single provider. The OLT also filters out upstream IGMP requests.

0046<figref idref="f0003">Figure 3</figref> shows how a set of channels may be mapped to multi-cast IP addresses. The channels may be provided, on subscription or otherwise, in groups of channels, for example as a basic packages and one or more premium rate packages.

0047At the set top box (STB), conventionally the allowable TV channel list is loaded by a service provider each time the STB boots up. It should be noted that this feature is for the convenience of the viewer, but does not protect the service against unauthorised access from an alternative information device such as a PC. Set top boxes preferably use IGMP version 2, or a protocol having similar functionality.

0048A method for handling a first channel request from a user on, for example set top box #1, comprises the steps of: <ol id="ol0001"><li>1. STB 70 requests a channel (for example channel2) by issuing a join IP multi-cast request for a specific channel IP address (for example) 225.0.1.2</li><li>2. The ONU receives IGMP join request</li><li>3. The ONU checks that the requested channel is on its list of allowable channels and sends an IGMP request for the selected channel (225.0.1.2) up to the headend unit 10 and starts listening for multicast signals on that address (225.0.1.2)</li><li>4. The headend unit 10 receives the IGMP request to join the channel (2). <ul id="ul0002" list-style="bullet"><li>If the requested channel is already being transmitted on that link, the headend unit continues and may optionally log the IP address of the requesting STB.</li><li>If the requested channel is not already being transmitted on that link, the requested channel is streamed on to the requesting link by the headend and optionally the IP address of the requesting STB is logged.</li></ul></li><li>5. The ONU 30 receives the video packets of channel 2 and forwards these streams onto the port of the requesting STB.</li></ol>

0049An example of a method for handling a channel change request from a user on, for example set top box #1, comprises the steps of: <ol id="ol0002"><li>1. A user on STB 70 currently watching a first channel (for example channel 2) presses a channel change to watch a second channel (for example, channel 3).</li><li>2. STB 70 transmits a leave message for channel 2 (leave IP multi-cast 225.0.1.2) and a join request for channel 3 (join IP multi-cast 225.0.1.3)</li><li>3. The ONU 30 receives the IGMP leave request and sends it up to the headend 10.</li><li>4. The ONU 30 checks that channel 3 is on its list of allowable channels for that STB, and sends IGMP request for 225.0.1.3 up to the headend 10 and starts listening for transmission on the requested address (225.0.1.3).</li><li>5. The headend 10 receives the IGMP request to leave channel 2. <ul id="ul0003" list-style="bullet"><li>If STB 70 was the only user requesting that channel on that link, transmission of that channel on that link may be suspended, and optionally the IP address of the requesting STB may be unlogged.</li><li>If STB 70 was not the only user requesting that channel on that link, transmission of that channel on that link may continue, and optionally, the IP address of the requesting STB may be unlogged.</li></ul></li><li>6. The headend 10 receives the IGMP request to join the newly requested channel (channel 3). <ul id="ul0004" list-style="bullet"><li>If that channel was already being transmitted on that link, the headend 10 continues and optionally logs the IP address of the requesting STB 70.</li><li>If that channel was not already being transmitted on that link, the newly requested channel (channel 3) is streamed on to the requesting link by the headend 10 and optionally the IP address of requesting the STB is logged.</li></ul></li><li>7. The ONU 30 receives the video packets of the requested channel. The ONU ceases forwarding the channel 2 stream to the user and instead forwards the newly requested channel stream (channel 3) onto port of the requesting STB.</li></ol>

0050By associating a time or times with a channel in permitted list, a pay-per-view scheme can be supported as well as the pay-per-channel scheme described above. In particular, if the ONU 30 comprises a real-time clock (or has access to a periodic real-time signal from the network or elsewhere) a user may subscribe to a channel for a limited time period, for example: <ul id="ul0005" list-style="bullet"><li>the permitted list may associate a single end-time with each channel after which the channel is deleted form the permitted list, allowing immediate subscription by a user to the current channel; up to, say the end of a currently broadcast film;</li><li>the permitted list may associate both a start and end time with each channel which is then made available only between the start time and the end-time, allowing advance booking of pay-per-view services;</li><li>the permitted list may associate more complex time intervals with any given channel so as to support, for example, subscription to a particular channel only up until 9:00 p.m. where, for example, a channel provider operates a voluntary ban on transmission of "adult" channel content before that time in the evening. Other options include time-of-day, and time-of-week constraints, for which differing subscription rates might apply, etc.</li></ul>

0051Time limits on availability could also be implemented by active control for the head end, by the sending of specific add/remove control messages to the ONU to cause the permitted list to be updated. This would obviate the provision of a real-time clock in each ONU.

0052The permitted list used to vet channel request may be associated either with the ONU as a whole, and therefore apply equally to each STB or PC receiving service through it, or to each individual STB/PC receiving service. In the latter way, distinct STB's may have separate channel access controls applied to support, for example, parental control of children's viewing: STB's in children's rooms receive only channels targeted to children; "adult" material subscribed to is available only to adults in the household.

0053Referring now to <figref idref="f0004">Figure 4</figref>, the invention described above is also not limited to the direct connection of individual STB's or PC's to the ONU. In a further embodiment shown in <figref idref="f0004">Figure 4</figref>, a second ONU 30a is shown connected, via the access network, to OLT 120. The arrangement also has a customer premises network 81 connected to a user port on the ONU. The customer premises network comprises an STB 812 and a PC 811 connected via a switch 813 (for example an Ethernet switch) to the access connection to ONU 30a. In this way a single ONU may support several customer premises (for example in a multiple dwelling unit, or along a street). In such a configuration the ONU may comprise permitted channel lists per ONU customer port, or per STB/PC. Whilst this arrangement increases the complexity of the ONU, it reduces the number of ONU to be deployed thereby potentially reducing operator costs.

0054Furthermore, whilst the above description has been presented in terms of multi-cast signals and IGMP signaling and channels carried over IP, the underlying method of vetting channel requests from users is dearly independent both of the multi-cast nature of the signals requested - access to point-to-point signals in non-multi-cast networks can be controlled in the same way - and of the specific signaling and broadcast protocols used.

0055It will easily be seen that the present invention can be applied to other services delivered using multicast, such as audio, software distribution and general push-oriented content delivery.

0056Any range or device value given herein may be extended or altered without losing the effect sought, as will be apparent to the skilled person for an understanding of the teachings herein.