(12) INTERNATIONALAPPLICATION PUBLISHED UNDER THE PATENTCOOPERATION TREATY (PCT)
`
`(19) World Intellectual Property Organization
`International Bureau
`
`(43) International Publication Date
`14 June 2007 (14.06.2007)
`
`PCT
`
`(51) International Patent Classification:
`H04L 29/08 (2006.01)
`H04L 12/28 (2006.01)
`H04L 29/06 (2006.01)
`
`(21) International Application Number:
`PCT/IL2006/00131 1
`
`(22) International Filing Date:
`14 November 2006 (14.1 1.2006)
`
`(25) Filing Language:
`
`(26) Publication Language:
`
`English
`
`English
`
`(30) Priority Data:
`172454
`
`8 December 2005 (08. 12.2005)
`
`IL
`
`(71) Applicant (for all designated States except US): ECI
`TELECOM LTD. [IL/IL]; 30 Hasivim Street, 49517
`Petach Tikva (IL).
`
`(72) Inventors; and
`(75) Inventors/Applicants (for US only): SCHLISERMAN,
`Alberto [IL/IL]; 4 Nahal Shikma Street, 71700 Modiin
`
`(10) International Publication Number
`WO 2007/066318 Al
`(IL). STEIN, Shai [IL/IL]; 4/17 Shy-Agnon Street, 43380
`Raanana (IL).
`(74) Agents: INGEL, GU et al; ECI TELECOM LTD., Patent
`and Trademark Dept., 30 Hasivim Street, 49517 Petach
`Tikva (IL).
`(81) Designated States (unless otherwise indicated, for every
`kind of national protection available): AE, AG, AL, AM,
`AT, AU, AZ, BA, BB, BG, BR, BW, BY, BZ, CA, CH, CN,
`CO, CR, CU, CZ, DE, DK, DM, DZ, EC, EE, EG, ES, FI,
`GB, GD, GE, GH, GM, GT, HN, HR, HU, ID, IL, IN, IS,
`JP, KE, KG, KM, KN, KP, KR, KZ, LA, LC, LK, LR, LS,
`LT, LU, LV,LY,MA, MD, MG, MK, MN, MW, MX, MY,
`MZ, NA, NG, NI, NO, NZ, OM, PG, PH, PL, PT, RO, RS,
`RU, SC, SD, SE, SG, SK, SL, SM, SV, SY, TJ, TM, TN,
`TR, TT, TZ, UA, UG, US, UZ, VC, VN, ZA, ZM, ZW
`(84) Designated States (unless otherwise indicated, for every
`kind of regional protection available): ARIPO (BW, GH,
`GM, KE, LS, MW, MZ, NA, SD, SL, SZ, TZ, UG, ZM,
`ZW), Eurasian (AM, AZ, BY, KG, KZ, MD, RU, TJ, TM),
`European (AT,BE, BG, CH, CY, CZ, DE, DK, EE, ES, FI,
`FR, GB, GR, HU, IE, IS, IT, LT, LU, LV,MC, NL, PL, PT,
`
`[Continued on next page]
`
`(54) Title: ARCHITECTURE OF GATEWAYBETWEEN A HOME NETWORK AND AN EXTERNAL NETWORK
`
`

`

`RO, SE, SI, SK, TR), OAPI (BF, BJ, CF, CG, CI, CM, GA,
`GN, GQ, GW, ML, MR, NE, SN, TD, TG).
`Published
`
`For two-letter codes and other abbreviations, refer to the "Guid-
`ance Notes on Codes and Abbreviations" appearing at the begin-
`ning of each regular issue of the PCT Gazette.
`
`

`

`Architecture of Gateway between a Home Network and an External
`Network
`
`Field of the invention
`
`The invention relates to the field of services for the home user in the
`
`broadband networks environment. In particular,
`
`the present
`
`invention relates to
`
`architecture of a gateway intended for supporting both communication between a
`
`home network and an external network, and services for users of the home network.
`
`Background of the invention
`
`The design and creation of services in the Home Network Environment has
`
`encountered many hurdles, the biggest is the need for every device on the network to
`
`be able to communicate with the different servers in the Home Network (HN) and in
`
`the outside External (say, Internet) Network. Although many protocols standardized
`
`many various services, the current technology is still oriented to specific services and
`
`does not provide the flexibility to create new services without going through the
`
`whole process of standardization of the new services from end to end with all
`
`participants in the service actualization process.
`
`Presently existing home or residential gateways between a home network and an
`
`external network (such as Internet, Ethernet, etc.) are capable of supporting
`
`communication between the two networks and enable providing some basic services
`
`for users of the home network (for various network devices). However, it should be
`
`noted that the mentioned capability is ensured by using (or providing) quite complex
`
`hardware and software means both at the side of home network devices, and at the
`
`side of servers of the external network (such as IP servers). Any new and/or
`
`technologically advanced service which is desired for the home network devices
`
`becomes problematic (beginning from just
`
`installing and connecting a new home
`
`network device, up to any novel service requiring participation of a group of network
`
`devices of the interconnected networks). The problem stems from the need of
`
`intervention into the existing software architecture of the home network devices, of
`
`the home gateway and/or of the external networks services, and thus from the need of
`
`

`

`seeking and producing new program "patches" for performing each of the newly
`
`required services.
`
`Fig. 1 (prior art) illustrates a well known and widely used architecture of a
`
`Home (or Residential) gateway RG (110), serving a home network 100 where each of
`
`the home network devices HNDl
`
`- HNDN (101 - 104) is intrinsically capable of
`
`communicating with an external network
`
`120 via the Home gateway 110. In this
`
`example, the external 120 network is IP network which may further be referred to as
`
`IN. Network devices of the IP network 120 are represented by a number of servers
`
`ISl -
`
`ISN (121- 124). Figure 1 depicts the standard methodology for creation of
`
`services in the home network 100. Home Network Devices HNDlOl- HND 104 must
`
`all be IP capable (with either integrated IP capabilities or an additional adaptor
`
`device). HNDs may have Ethernet or IP connectivity among them over the Home
`
`Network (100). When a need arises to reach an external server, an HND creates
`
`service related sessions via the Residential Gateway (110). The RG (110) provides
`
`various connectivity services to the Home Network: Bridge Services (111), Router
`
`Services (112) which may include Network Address Translation NAT and Firewall,
`
`Proxy Services ( 113) and Application Level Gateway Services ( ALG 114).
`
`Using any of these connectivity services, the Home Network Device (say, 101) sends
`
`messages over the Internet Network (120) and reaches the necessary servers that take
`
`care of the message.
`A schematic example of a simple service can be seen in Figure 2 (prior art),
`
`illustrating the message interplay related to a Content Retrieval service (the details are
`
`provided to demonstrate the complexity of the service performed by the prior art
`
`gateway). First phase (211) demands
`
`IP initialization of
`
`the Home Network
`
`(Residential) Gateway RG (202) from a Dynamic Host Control Protocol DHCP
`
`Server (203). Then Home Network Devices (generally marked 201) get their Local IP
`
`addresses from the RG (202). Second Phase (212) includes Configuration of the HND
`
`(201) by an Auto-Configuration Server ACS (204). Third Phase (213) is the phase
`
`where the HND 201 can access the content, which is provided by HTTP Server (205).
`
`The service creation and service actualization for other services is even more
`
`complicated then the content retrieval service. In other services different protocols can
`
`

`

`be involved (e.g. SIP or H.232), other servers can be used (Call Server, Video
`
`Servers).
`
`In case the desired service demands a combination of services (e.g., a combination of
`
`voice, data, and video), specific applications - say, similar to "Net-Meeting" must be
`
`built on a PC-like device for that specific service, without having a possibility to use
`
`them for other services.
`
`In parallel to the service actualization, the end-to end network must be configured to
`
`support the service. In the solutions that exist today, these tasks are split between the
`
`service provider (from server to the residential or home Gateway) and the user (from
`
`the Gateway to the HND). Harmonization of these tasks is still under debate; either
`
`RG will take care of assuring end-to-end requirements or external controller will do it
`
`as part of IMS (IP Multimedia Subsystem) concept.
`
`Addresses of Network layer commands arriving to the Gateway either from the side
`
`of Home Network or from the side of External Network have to be translated, in any
`
`direction. The function of coordination the Home Network Devices addresses with
`
`External Network (IP) addresses is usually performed with the aid of modules like
`
`NAT (Network Address Translation ), ALG 114 (Application Level Gateway) or
`
`Proxy. NAT is indicated as 206 in Fig. 2, ALG and Proxy are respectively marked as
`
`114 and 113 in Fig. 1.
`
`In presently known solutions, many of the HN attributes are discovered,
`
`configured and directly controlled by the IN or Service providers (e.g. Technical
`
`Report DSL Forum TR-094,
`
`(August 2004) www.dslforum.org/techwork/tr/TR-
`
`094.pdf.
`
`Having described today's solution for service creation and delivery, it
`
`is
`
`evident that any attempt to introduce new services demands understanding of Home
`
`Network technologies, Provider Network architectures and protocols, as well as the
`
`capability to integrate all technologies into a valid end-to end service delivery
`
`platform.
`
`US patents 6,930,598 B2 "Home Gateway Server Appliance" and
`
`6,317,884 Bl "Video, Data and Telephony Gateway" describe various solutions that
`
`still do not solve the problem of cumbersome and complex coordination of services
`
`and protocols of different inter-communicating networks, as well as the problem of
`
`

`

`intrinsic capabilities of different network devices belonging to these different
`
`networks.
`
`A
`
`relatively
`
`novel
`
`technology
`
`called
`
`PARLAY
`
`(http://www.parlay.org/en/specifications/) has
`
`been
`
`developed
`
`for
`
`supporting
`
`telecommunication services between a number of standard network applications and a
`
`telecommunication network. The Parlay Group aims to link Information Technology
`
`(IT) applications with the capabilities of the telecommunications world by specifying
`
`and promoting application programming interfaces (APIs) that are easy to use, rich in
`
`functionality, and based on open standards. Parlay integrates telecom network
`
`switches with IT applications via a secure, measured, and billable interface. Parlay
`
`presents
`
`the notion of an API
`
`that
`
`allows
`
`applications
`
`to interface the
`
`Telecommunication Network (for example, a central office of a PSTN network) with
`
`the aim to allow multiple network services to be then offered to telephony users.
`
`US patent 6,690,782 B2 describes a way of implementing the Parlay concept
`
`between an application layer, a service layer and a protocol
`
`layer of a
`
`telecommunications network. Neither Parlay, nor the US patent 6,690,782 B2 has
`
`reference to a home network, specific home network devices, nor specific home
`
`network services.
`
`Summary of the invention
`
`The Inventors point out that there has been a long felt need of providing such a
`
`home (residential) gateway for interconnecting a home network with an external
`
`network, which would overcome disadvantages of the presently used home gateways,
`
`i.e. would alleviate communication between the home network and the external
`
`network, and creation of various new services for users of the home network.
`
`Providing such a home gateway is the object of the invention.
`
`To achieve the above object, this invention proposes a new architecture of a home
`
`gateway (HGW)
`
`to be placed and utilized for communication and service
`
`actualization between a home network (HN) and an External Network (EN), the
`
`HGW being adapted to communicate with the HN and EN at a Network layer and
`
`being provided with a Service Application Programming Interface Layer (SAPI
`
`

`

`Layer) capable of performing, at an Application layer, mediator
`
`functions for
`
`supporting communication and services between the HN and the EN.
`
`More particularly, when the HN comprises a number of different home network
`
`devices (HNDs) and an external network (EN) comprises one or more external
`
`network devices (ENDs), said SAPI Layer of the HGW enables any one of the home
`
`network devices (HNDs):
`
`a)
`
`to communicate with one or more of the external network devices ENDs via
`
`the HGW, by utilizing said network and service mediator functions of the
`
`HGW, regardless of the fact whether any of said HNDs has individual
`
`capability of communicating with with any of the external network devices
`
`ENDs);
`
`b)
`
`to order
`
`from the HGW and acquire there-from services
`
`involving
`
`participation of one or more network devices belonging to any of the HN and
`
`EN (i.e., any network devices selected from HNDs and ENDs).
`
`In other words, the preferred embodiment of the HGW, which should probably
`
`become widespread or even standard in the closest future, ensures communication and
`
`services for said different HNDs even in case when no one of the HNDs has
`
`individual capability of communicating with the ENDs. The new architecture of
`
`HGW will therefore result in a possibility for a user to utilize simple and economic
`
`HNDs, and in the long term -
`
`in simplifying all types of home network devices
`
`HNDs.
`
`The proposed invention also allows the communication and actualization of
`
`services in the opposite direction too, by enabling network devices belonging to the
`
`external network (ENDs) to communicate with the network devices of the home
`
`network via the HGW by utilizing the novel mediator
`
`functions of
`
`the
`
`HGW.Preferably, the External Network is an Internet Network.
`
`Actually, the proposed concept aims at creating a so-called service level
`
`partitioning between the Home Network and the External (or Provider) Network. The
`
`architecture presented in the present description resolves the complexities of service
`
`creation and actualization from the "user side" of the network (i.e., from the Home
`
`network) and creates a Service Application Layer between the user side and the
`
`

`

`External Network, so that the Service Application Layer masks the complexities of
`
`the External network beyond the Residential (Home) Gateway.
`
`The main component of the Service Application Programming Interface Layer
`
`in the novel architecture of the HGW is formed by a group of Home network
`
`Application level Programming Interfaces (HAPIs or HAPI modules) that together
`
`compose a Home Network Application Layer (HAPI Layer). Each of said HAPIs
`
`being designed to present a predetermined Application level Programming Interface
`
`(API) to at least one of the home network devices HNDs. The Home Network
`
`Application layer will be further shortly referred to as HAPI layer.
`
`The HAPI layer of the SAPI Layer (Service Application Programming
`
`Interface Layer) can be defined as comprising a functionally complete set of Home
`
`network Application Programming Interface modules (HAPIs). The functionally
`
`complete set of HAPIs can be understood as such a set of interfaces that enables
`
`performing within the HGW at least the functions that otherwise would have to be
`
`performed by said individual capabilities (interfaces) of all the HNDs connected to
`
`said HGW. It should be kept in mind that the mentioned individual capability or
`
`interface of a Home Network Device HND supports communication and services
`
`between the HND and the External Network EN).
`
`The functionally complete set of HAPIs in the HAPI layer therefore makes
`
`unnecessary said individual capabilities of the HNDs, i.e. HNDs could be produced
`
`without their complex individual interfaces .
`
`Owing to the above-described features, the Service Application layer (SAPI)
`
`Layer is adapted to perform services within the Home Network, access the External
`
`Network (usually Internet) for services outside the home network and combine
`
`services from both within the Home and in the External Network.
`
`The SAPI Layer allows home network devices to provide new services for the
`
`home network user (that activates HND) without being aware of the details of the
`
`home network and its devices nor the External Network behind the Home Gateway.
`
`Since the SAPI Layer represents the services capabilities of both Home Network and
`
`its devices and the External Network and its devices, the home network user's access
`
`to services at the external network shall be performed by activating specific HAPI(s)
`
`that own the capability to reach the external network servers. Similarly, access of the
`
`

`

`home user to services within the home network is also performed by activating one or
`
`more specific HAPIs and their interaction with one another and the relevant HNDs.
`
`In view of the above, the new architecture of HGW allows easy development of
`
`services for the home user, based on using the HAPI layer and developing it by
`
`programmers of any qualification.
`
`In other words, the plurality of HAPIs modules of the HAPI Layer shall allow
`
`easy creation and actualization of services by service programmers, even by those
`
`unable to understand the technologies behind the services both within the Home
`
`Network and in the Outside Provider (External) Networks, since the creation of a
`
`modified or new service would require just composing a specific group of HAPI
`
`modules and actualizing thereof in a predetermined order of interaction.
`
`The creation of a unified and, probably - of a standardized SAPI Layer (and a
`
`standardized HAPI Layer), means that Home Network devices will be able to get
`
`services from the External Network and shall facilitate many new services that cannot
`
`be implemented with currently known capabilities of residential (home) gateways.
`
`From the point of protocol
`
`layers,
`
`the invention can be formulated as
`
`proposing a Home Gateway (HGW) architecture for providing communication and/or
`
`service via a Home Gateway (HGW) interconnecting
`
`a Home Network and an
`
`External Network, and capable of terminating any one of incoming Network layer
`
`communication and/or service commands and converting them into Application layer
`
`commands, handling the Application layer commands within the Home Gateway for
`
`ensuring required services and establishing required communication, the HGW further
`
`converting the Application layer commands for issuing outgoing commands as
`
`Network layer commands.
`
`It is the Service Application Programming Layer
`
`(SAPI layer) of the HGW,
`
`who is responsible for translating all Network layer commands, incoming the HGW
`
`from either the Home Network Devices or the External Network Devices,
`
`into
`
`Application layer commands and of handling said Application layer commands at the
`
`SAPI
`
`layer; the SAPI layer is also responsible for outputting said Application layer
`
`commands either towards the Home Network Devices or the External Network
`
`Devices in the form of Network layer commands.
`
`

`

`More specifically, and in a particular case the proposed HGW is intended for
`
`communication and service actualization between an external network (EN) and a
`
`home network (HN) comprising a plurality of home network devices (HNDs), said
`
`HGW is provided with a plurality of Home Application Programming Interface
`
`(HAPI) modules forming a Home Network Application Layer (which can be shortly
`
`called HAPI layer) in the HGW; the Home Gateway HGW being operative:
`
`a)
`
`to translate Network layer ( usually, IP) commands received from said HNDs
`
`and requesting communication and/or services involving participation of the
`
`EN,
`
`into Application layer commands,
`
`to handle said Application layer
`
`commands at the HAPI layer, to re-translate said Application layer commands
`
`back to the IP layer commands and to forward thereof to the external network
`
`(EN).
`
`b)
`
`to translate Network (IP) layer commands received from said EN and intended
`
`for the HN, into Application layer commands to handle the Application layer
`
`commands at the HAPI layer, to re-translate said Application layer commands
`
`back to the IP layer commands and to forward thereof to the home network
`
`(HN).
`
`It should be noted that since the HGW is capable of translating any incoming
`
`Network layer commands into Application layer commands, the commands incoming
`
`the HGW from said HNDs and is not requesting communication and/or services
`
`involving participation of the ENDs (e. g., related just
`
`to internal home network
`
`services and/or communications), will also be translated into the Application layer
`
`commands to be handled at the HAPI layer for further re-translating said Application
`
`layer commands back to the IP layer commands to be issued to the Home Network
`
`Device(s).
`
`It should further be noted that the SAPI layer of the Home Gateway HGW
`
`may also comprise an External (or Provider) Network Interface Layer - ENI layer- for
`
`serving network devices of the EN (ENDs). ENDs, for example, may be IP Servers).
`
`The External Network Interface Layer preferably has functions with respect to
`
`the External Network EN, analog to the functions, which the HAPI layer has with
`
`respect to the Home Network HN.
`
`

`

`When the SAPI layer comprises the HAPI layer and the ENI layer, the internal
`
`communication within the SAPI layer between the HAPI layer and the ENI layer
`
`is
`
`preferably provided at the Application layer commands.
`
`One of the major advantages of this invention is the creation of a unite and
`
`stable demarcation point between HN and EN (say, Internet network IN). This
`
`function is performed by the SAPI Layer within the HGW. The Unite Demarcation
`
`Point solves several problems
`
`that exist in today's networks when HN is a sub¬
`
`network within the IN. The unite demarcation point is efficient both at the network
`
`layer and at the service layer.
`
`Network Layer Demarcation
`
`The IP Layer Addressing of the two realms IN and HN may be completely separate.
`
`The interface between the two networks is at the service (application)
`
`layer over the
`
`SAPI (not at the network layer over IP).
`
`This means that
`
`there is no need to perform at the HGW any Network Address
`
`Translation that causes problems for many applications (e.g. L3 VPN, VOIP) and
`
`demands application specific algorithms to correct the problems caused by network
`
`translation (e.g. Application Level Gateways for many on line gaming services)
`
`Instead of that,
`
`the HGW performs translation of incoming IP commands
`
`into
`
`commands of the Application layer to be handled in the SAPI layer of HGW, and also
`
`performs
`
`translation
`
`of Application
`
`layer commands
`
`into outgoing IP layer
`
`commands.
`
`Service Layer Demarcation
`
`The HGW performs all the tasks needed for services of the two networks. The HGW
`
`will perform the requests of the HN via the HAPI and all the tasks and services
`
`required by the IN (EN) entities over the applicable protocols of the ENI layer.
`
`The HGW may be trusted by both providers (Network and Services) so there is no
`
`need to make other HNDs trusted (although the HGW can serve as a relay if the HND
`
`must be a trusted device).
`
`Creating a clear demarcation between HN and IN is not mandatory but it may appeal
`
`to some of the network providers. The demarcation point does not preclude the
`
`possibility to offer Remote HN Management Services. The remote Management shall
`
`be relayed via the HGW as any other service.
`
`

`

`This demarcation point shall reduce the amount of knowledge the IN provider or
`
`Services provider have about the HN and HNDs on it.
`
`The HGW will transfer only data that is requested by server when requested. This
`
`makes the HN a separate network that does not have to be discovered and directly
`
`controlled by the service provider. Remember, that in the prior art many of the HN
`
`attributes where discovered, configured and directly controlled by the IN or Service
`
`providers.
`
`In order to implement the above-mentioned objectives concerning developing
`
`new services for the Home Network, HAPIs forming the HAPI layer preferably have
`
`specific structure and format.
`
`HAPI shall have the format of a client-server API. Depending on the side that
`
`needs a service done, than some HAPI will behave with HGW as a Server and with
`
`HND as Client. Other HAPIs shall behave with HND as a Server, and with HGW as a
`
`Client.
`
`Each HAPI shall have a Name, HAPI Attributes, HAPI Methods and an HAPI
`
`implementation Sequence.
`
`HAPI Name: identifies the specific HAPI between client and server.
`
`HAPI Attributes define the parameters exchanged between the client and server.
`
`HAPI Method defines the action requested by the client to be performed by the server.
`
`The HAPI implementation sequence shall define the message interplay and activities
`
`performed by the client or server at each step of the process. The implementation
`
`process shall also define irregular behavior and the actions to be taken in case of
`
`irregular conditions: errors in message, communications problems, SW and HW
`
`problems.
`
`Without limiting the technology, the invention presents two preferred HAPI
`
`Classes in the HAPI Layer:
`
`Class 1: HAPI Class for complete services (i.e a HAPI module ensuring a complete
`
`service for performing a specific task)
`
`Class 2 : HAPI Class Building Blocks i.e. HAPI modules that allow the generation of
`
`new services by creating new HAPI combinations.
`
`In addition to the HAPI Layer HAPFs, the HGW preferably comprises a
`
`Home Network Services Framework (HNSF) module capable of providing generic
`
`

`

`services to the HAPI layer ( to any of the HAPIs ) and to the Provider Network
`
`Interface Layer. The HNSF is considered to be part of the HAPI Layer.
`
`For example, HNSF may handle all real time issues for the HAPI layer and the
`
`Provider (external) Network Interface Layer.
`
`Other types and combinations of the HAPI modules will be discussed as the
`
`description proceeds.
`
`According to a second aspect of the invention, there is provided a system
`
`comprising the new Home Gateway (HGW), wherein the system also includes a
`
`Home network with Home Network Devices and an External Network with its entities
`
`(ENDs),
`
`the Home network and the External Network being capable of
`
`communicating with one another via the HGW.
`
`According to yet another aspect of the invention, there is proposed a method
`
`of providing communication and/or
`
`services via a Home Gateway (HGW)
`
`interconnecting a Home Network and an External Network, the method comprising
`
`converting all Network layer communication and/or
`
`service
`
`commands incoming the (HGW) either from the Home Network or
`
`from the External Network,
`
`into Application layer commands,
`
`-
`
`handling the Application layer commands within the HGW for
`
`ensuring
`
`required
`
`services
`
`and/or
`
`establishing
`
`required
`
`communication,
`
`issuing commands outgoing from the HGW either to the Home
`
`Network or to the External Network, as Network layer commands.
`
`More particularly, the method includes preliminarily providing in the HGW a
`
`Service Application Programming Interface Layer
`
`(SAPI Layer) comprising a
`
`functionally complete set of Home network Application Programming Interface
`
`modules. As has been explained above, the functionally complete set can be defined
`
`as such a set of interfaces that enables performing in the HGW, at its SAPI layer, at
`
`least the functions that otherwise would have to be performed by said individual
`
`capabilities (interfaces) of all the HNDs belonging to the HN and connected to said
`
`HGW. We keep in mind that the individual capabilities (or interfaces) of the HNDs
`
`

`

`are to be understood as enabling to the HNDs communicatin with the EN and/or
`
`support services involving the ENDs.
`
`An additional subject of the invention is a software product comprising
`
`software implementable instructions and/or data for carrying out the above-described
`
`method, as well as a carrier medium carrying the software product.
`
`Brief description of the drawings
`
`The invention will be further illustrated with reference to the following non-
`
`limiting graphical examples, in which:
`Fig. 1 (prior art) is a schematic representation of the current model for the Home
`
`Network attachment to the Internet Network via a residential Gateway.
`
`Fig. 2 (prior art) is a schematic representation of the messages involved in the
`
`implementation of a service from the Home network Device, via the Residential
`
`Gateway to the Internet Server via the Internet Network.
`
`Fig. 3 is a schematic representation of the proposed Home Network API Layer in the
`
`Residential Gateway. The HAPI Layer serves to present a number of specified API
`
`modules to the Home Network and its devices masking all the details of the Internet
`
`Network and Internet Servers.
`
`Fig. 4 provides a schematic representation of the message interactions needed to
`
`implement services for the Home Network using the API interface modules provided
`
`by the HAPI Layer.
`
`Fig. 5 schematically illustrates a multi-layer diagram of service traffic via a
`
`conventional Home Gateway HGW.
`
`Fig. 6 schematically illustrates a multi-layer diagram of service traffic via the new
`
`HGW proposed in the present invention.
`
`Detailed description of the preferred embodiments
`
`In view of the principles stated above, and taking into account specific
`
`features, which will be described below in more detail,
`
`the present
`
`invention
`
`proposes:
`
`- An architecture of Home (Residential) Gateway, comprising of a HAPI
`
`Layer that allows Home Network Devices of all types to communicate
`
`

`

`among themselves and with External (Internet) Network servers of all
`
`types;
`
`The new HGW with the HAPI Layer becomes a clear and unite
`
`demarcation between External (Internet) Network and its entities and
`
`Home Network and its devices.
`
`o the demarcation at the network layer means that network addresses
`
`at the two sides of HGW do not have to be translated in any
`
`direction. Network layer commands are completely translated into
`
`Application layer commands.
`
`Both the communication and
`
`services are both handled exclusively at the Application layer via
`
`the HAPI Layer from the HN side and via Internet Services (ENI
`
`layer) at the External Network side. This invention solves the need
`
`for coordination of HN addresses with IN Addresses via processes
`
`like NAT, ALG or Proxy;
`
`o Service Level Demarcation provided by the HAPI Layer means
`the HGW(RG) 5 on both sides
`thereof. The HGW handles the services from side to the other at a
`
`that services are terminated at
`
`service level, and HNDs use the HAPI layer as their interface to
`
`invoke services from HGW, and through HGW indirectly from the
`
`External Network,
`
`- The HAPI Layer can be built by various classes of HAPI and a Framework
`
`HAPI, for example HAPI can be a HAPI module to a complete service, a
`
`building block module for services or a HAPI module to any of the
`
`services provided by the framework in the HAPI Layer, HAPI module
`
`allowing OAM Procedures for HGW and HNDs; HAPI modules allowing
`
`real time streaming services through the HGW at a service level; other
`
`expanded classes of HAPI;
`
`Owing to the new architecture of the HGW, the HNDs do not need to have
`
`individual capabilities (interfaces) for supporting communication/services with one
`
`another and with ENDs across the networks, since all the required interfaces (the so-
`
`called functionally complete set of HAPIs) are provided in the HGW. The new
`architecture of HGW allows easy creation of new and modified services for HNDs5
`
`

`

`since this process does not require knowledge of HNDs, ENDs and high qualification
`
`from users, programmers and providers.
`
`For example, newly created advanced
`
`services for HNDs may be a) providing popping up messages concerning all HNDs in
`
`a display of an HNDs presently active; b) providing home maintenance or household
`
`operations by remotely controlling HNDs by e-mail, etc. Combinations are numerous,
`
`and can be dictated and limited only by the number and nature of HND devices
`
`connected to the HGW and the set of HAPIs currently available in the HGW.
`
`Fig. 3 illustrates a schematic block diagram of the newly proposed architecture of a
`
`Home (or Residential) Gateway HGW 310 serving for interconnecting a Nome
`
`network 300 and an External network 320. The HGW 310 is provided with a Service
`
`Application Program Interface (SAPI) layer 252, the main part of which is a Home
`
`network Application (HAPI) Layer 254. In the example of Fig. 3, the SAPI layer 252
`
`of the Home Gateway 310 comprises also an External Network Interface 316 which
`
`can be considered an ENI layer 316. Alternatively, or in addition the External
`
`Network Interface can be distributed among network elements of the External
`
`Network (in this example, Servers 321-324 of the Internet network 320).
`
`The HAPI Layer shall provide, to the HN devices HNDl-HNDN (301-304), any of
`
`the known interfaces and some additional complementing interfaces in order to
`
`perform for the HN devices both old and new services without a need for the HNDs to
`
`interact "themselves" with network nodes outside the HN.
`
`The side (preferably, only HNDs, but possibly also external network's
`
`IP servers
`
`3421-324) that wishes to activate a service shall be responsible for activating the
`
`applicable HAPI Classes with the correct attributes/features and in the needed
`
`sequence in order to actualize the service. Some of the HAPIs may be "organizers"
`
`for other ones.
`
`Once HAPI classes are defined and the HAPI layer is built in general, every se