WO2002005569A1 - A method and a system for accessing services - Google Patents

A method and a system for accessing services Download PDF

Info

Publication number
WO2002005569A1
WO2002005569A1 PCT/SE2001/001336 SE0101336W WO0205569A1 WO 2002005569 A1 WO2002005569 A1 WO 2002005569A1 SE 0101336 W SE0101336 W SE 0101336W WO 0205569 A1 WO0205569 A1 WO 0205569A1
Authority
WO
WIPO (PCT)
Prior art keywords
client
node
locally distributed
local gateway
distributed node
Prior art date
Application number
PCT/SE2001/001336
Other languages
French (fr)
Inventor
Dan Jonsson
Original Assignee
Vattenfall Ab
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Vattenfall Ab filed Critical Vattenfall Ab
Priority to AU2001266459A priority Critical patent/AU2001266459A1/en
Publication of WO2002005569A1 publication Critical patent/WO2002005569A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/12Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/2866Architectures; Arrangements
    • H04L67/30Profiles
    • H04L67/306User profiles
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04QSELECTING
    • H04Q3/00Selecting arrangements
    • H04Q3/0016Arrangements providing connection between exchanges
    • H04Q3/0029Provisions for intelligent networking
    • H04Q3/0045Provisions for intelligent networking involving hybrid, i.e. a mixture of public and private, or multi-vendor systems
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]

Definitions

  • the present invention relates to a method and a system for providing intelligent services, in particular for providing access to such services.
  • a system for an intelligent home may include an external network, such as an IP network, and a local network. Between these two networks there is some sort of local gateway. Locally distributed nodes may be connected to the local gateway for - controlling different home appliances. A client can thus from his computer over the internet and via the local gateway communicate with a specific node that controls a specific appliance.
  • this type of technique is not limited, to just intelligent homes but can be implemented in other cases as well .
  • An object of the present invention is to achieve a method and a system which are more flexible then the previously described prior art .
  • Another object of the invention is to make services provided by service providers more easily accessible.
  • Yet another object is to increase the liability of a client for used services.
  • a method in which services provided via an access provider are to be accessed.
  • a respective client structure is registered for a number of clients with the access provider.
  • Each client structure includes a corresponding set of services which are made available by the access provider.
  • a local gateway node which is in communication with the access provider, is provided, wherein a number of said services includes transferring information from and/or to a number of locally distributed nodes via said local gateway node.
  • a client specific locally distributed node is associated with a first client structure and is. connected to said local gateway node for transferring information related to a service included in said first client structure via said local gateway node .
  • a system for accessing services includes: a server including a database with different client structures, each client structure being associated with a client; a service control module for enabling different service providers to interact with the system, said service control module being operatively connected to said server; a local gateway node in communication with said server, wherein said local gateway node being further adapted for communication with locally distributed nodes; and a client specific locally distributed node which is associated with a first client structure, wherein said client specific locally distributed node is operatively connected to said local gateway node for transferring information related to a service included in said first client structure via said local gateway node.
  • the present invention provides, for a service platform which e.g.
  • the service platform is created and operated by an access provider.
  • the access provider provides a commercial infrastructure for intelligent services.
  • the a.ccess provider can give service providers, such as companies, the possibility to interact with the service platform and to offer services to clients registered with the access provider.
  • the services are, in accordance with the invention, node related services, but there may of- course be of other types as ell, such as Internet services, as for instance weather forecasts. Of course some services may even be provided by the access provider .
  • a client which is registered with the access provider can be a large .company, but it- can also be a single person.
  • the access provider defines a respective client structure .
  • each client structure has at least one assigned user. The user is thus the one who actually uses the provided services, while the client in the client structure is liable for the used services.
  • a client and a user may be one and the same person.
  • a locally distributed node is preferably used for controlling, monitoring or in some other way communicating or transferring information to/from a certain appliance, e.g. an electrical appliance.
  • the locally distributed node must be connected to a local gateway node in order to establish communication with the service platform.
  • a user can in one embodiment access a client structure by a simple login on a web page of the access provider. After the' login procedure he will see what services he may use. Naturally, it is not necessary to have a graphical user interface. The user may proceed in a corresponding way over a telephone, using e.g. DTMF tones .
  • the invention is based on the insight that it is possible to achieve a flexible service platform by defining a respective client structure for each client.
  • the client structures, or the contents thereof, may be different from one client to another. However, each client structure may be given the possibility to use some kind of associated service (s) , such as node or web services.
  • a client specific locally distributed node is thus geographically independent, in the sense that it can be located anywhere as long as it is in communication with a local gateway node.
  • a client specific locally distributed node is a movable object, which can be relocated, installed or operatively connected to different appliances.
  • An example of a favourable application of the invention is a client specific locally distributed node being connected to the engine pre-heater of a car.
  • the pre-heater cable plug can be plugged .into a socket which is in communication with any local gateway node.
  • the client specific locally distributed node is associated to a specific client, the client can be identified and charged for the consumed power.
  • the service provider in this case is a power supplier, company.
  • the client can, e.g. from his mobile phone, program the time he desires that the heating of the engine should start, wherein the mobile phone is in communication with a server of the access provider, which server in turn transmits a signal to the locally distributed node- via the local gateway node.
  • Another somewhat different example is a company selling food or beverages from vending machines.
  • Such a company has many machines distributed at different locations, such as factories, tennis halls, train stations etc..
  • the company either regularly sends an operator and maintenance person- to check up on or re-fill the machines, or is informed by somebody at the location that a re-fill is needed or that the machine is out of order.
  • client specific locally distributed nodes applied in the machines the machines can be connected to an existing local gateway node, and thereby the company will continuously have information regarding the state of the machines.
  • the company itself besides being a client to the access provider, may be the service provider that generates information . updates regarding the vending machines, or there may be an external service provider.
  • the first example relates to an appliance (a car, or actually the pre-heater in the car) which is often moved from one geographic location to another, and thus will be connected to many different local gateway nodes on different occasions.
  • the second example relates to a more or less stationary appliance (a vending machine) which will be connected to the same local gateway node for a longer period of time.
  • the relevant client specific locally distributed node and thus the liable client, should be identified.
  • the identification of the locally distributed node may, but is not required to, be performed in somewhat different ways for the two examples above, as will be explained in the following.
  • an identification procedure may be as follows.
  • the client specific locally distributed node When the client specific locally distributed node is operatively connected by means of e.g. the power mains, radio communication or in some other way to a local gateway node, information thereof will be transmitted from the local gateway node to the server of the access provider.
  • the server now knows the location, or the latest location of the client specific locally distributed node.
  • the information received by the server includes a unique identity for the client specific locally distributed node and the server will by means of an associated database verify if the node has been associated to a client and in that case retrieve relevant client information, such as name, billing address or account etc.
  • a service associated with that client structure can be used and service related information be transferred to the client specific locally distributed node via the local gateway node. Since the client specific locally distributed node is connected to a frequently relocated appliance, it is suitably polled by the server via the local gateway node at short intervals, in order to check if the client specific locally distributed node is still under that local gateway node . For a client specific locally distributed node which will be used in conjunction with a more or less stationary appliance, the transfer of information does not need to go all the way to the server. Once the server has been informed of the local gateway node to which the locally distributed node is operatively connected, the identification information is stored in the local gateway node.
  • the downloaded programs in the local gateway node may run independently of the server and information and data may be stored in the local gateway node.
  • the local gateway node may suitably poll the client specific locally distributed node at regular intervals for updating certain data or other type of information.
  • this information must be communicated to the server.
  • this approach is mainly suitable in conjunction with a relatively stationary appliance.
  • the client will reactivate the client specific locally distributed node.
  • client related information that was stored in the first local gateway node will not automatically be transferred to the second local gateway node, unless the client reactivates the client specific locally distributed node.
  • This can e.g. be done by operatively connecting the client specific locally distributed node to the second local gateway node, wherein the server of the access provider will be informed thereof and client related information will consequently be stored at that local gateway node.
  • the client may have to enter his client structure and reregister the client specific locally distributed node. Note that this procedure mainly applies for nodes connected to relatively stationary appliances.
  • a client specific locally distributed node can not only be associated to a client structure, but can also be disconnected therefrom.
  • An advantage of this fact is e.g. if the client specific locally distributed node is stolen. The owner of the node enters his client structure and simply disconnects or inactivates the node, i.e. making it at least temporarily out of order, whereby he is spared from being charged for services attempted to be used by the thief. It may even be possible to trace the thief when he tries to use said node. Alternatively, instead of, or as a complement to, disconnecting said node, one could simply enter the client structure and block said node so that no one can use it. Another possibility is to disconnect the client specific locally distributed node in one client structure and associate it to another. This can occur if someone e.g. gives his node to a friend or the like.
  • a power supplier company may connect a client specific locally distributed node in the form of an electricity meter to a private person's local gateway node.
  • the power supplier company (the client) will have the sole access right to read or manipulate that electricity meter.
  • Another example is a copying machine leasing company which provides offices with copying machines. Each machine may have a client specific locally distributed node connected thereto, so that information regarding number of copies, consumed power, etc. is recorded by the leasing company.
  • the company knows which locally distributed node is operatively connected to which local gateway node, and has thus full control for e.g. invoicing or repairing purposes .
  • An example of the client specific locally distributed node being connected to a frequently relocated appliance may be a node for the electrical charging of an electric car, said car being the frequently relocated appliance.
  • Such a client specific locally distributed node is connected to a set of ' accumulator batteries, and operatively connected to a local gateway node via the power mains, so that the consumed power is registered.
  • Another example is a boat coming to a port and a client specific locally distributed node on the boat is operatively connected to a local gateway for paying harbour dues or for .using certain services in the port.
  • Yet another example is when transporting goods to a certain location or large establishment, the driver of a lorry carrying the goods may e.g. need to be quickly informed of where to unload the goods.
  • the lorry may be provided with a client specific locally distributed node which, when passing a gate of the establishment, communicates by means of e.g. radio communication with a local gateway node and subsequently with the server of the access provider.
  • the server identifies the client and will transfer information to the client specific locally distributed node. Said transferred information includes an indication of which platform that particular lorry should proceed to for unloading the goods .
  • the present invention has many different possible applications, of which only a few have been mentioned herein above. However, the same inventive concept applies for all applications, namely a locally distributed node being directly associated to a client structure, which is registered with an access provider.
  • a local gateway node could communicate with locally distributed nodes in many different ways. Some examples of means of communications are the power mains, telecommunication, radio or data communication, etc.
  • a local gateway node may be associated to a client structure.
  • a private person may have a local gateway node at home, which is in communication over the power mains with normal stationary locally distributed nodes that are connected to different appliances, such as the fridge, the iron, the burglar alarm system, etc.
  • a friend comes for a visit by car he may, as in the previous example, pre-heat the car by plugging the cable into a socket which via the mains communicate with the local gateway node in the house. Since this friend has a client specific locally distributed node installed in connection to the pre- heater, his client structure will be identified and charged for the used service, i.e. the consumed power.
  • a client specific locally distributed node which is associated to a first client structure can be connected to a local gateway node which is associated to a second client structure, thereby transferring information related to a service included in said first client structure via said local gateway node. It goes without saying that a client specific locally distributed node can also be operatively connected to a local gateway node, when both of them are associated to one and the same client structure.
  • the present invention does not exclude the use of locally distributed nodes which are directly associated with a local gateway node. Such nodes can be used as a complement to the more flexible client specific locally distributed node.
  • a client may be a private person who has come to an agreement with the access provider. This private person will then have a client structure registered with the access provider.
  • a client structure includes at least one user.
  • the person himself would suitably be a user in that client structure.
  • a large company is the client, then some of the employees may be users.
  • Such a superuser could decide to associate new users to his client structure. This could apply for a private person as well, as he could associate e.g. family members to his client structure. In such a case, it is preferably the superuser who has the authority to associate new locally distributed nodes and related services to that specific client structure.
  • the person will be able to see what services are available and the nodes associated to his client structure. He may even be able. to see client specific locally distributed nodes from another client structure that have been operatively connected to a local gateway node in his client structure. However, these nodes are merely shown for information and are not controllable by said person.
  • On the private home page he may in one embodiment also have icons or references to all the client structures in which he is a user (a user can be associated to several client structures as will later be described) . Thus, by clicking on one of these references he enters a specific client structure, and will there be able to access a number of services.
  • the client specific locally distributed node according to the present invention can advantageously be utilised in connection with a method and a system as disclosed in the Swedish patent application SE 0001139-5, which is hereby incorporated as a reference.
  • each client structure has at least one user, and a characteristic feature of the invention is that a first user in a first client structure can give authority to a second user in a second client structure to access said first client structure and its corresponding associated services.
  • Such an associated service could relate to a client specific locally distributed node according to the present invention.
  • a client specific locally distributed node is associated to the client structure of Company A, in which Mr. Smith is a user. He decides to give Mr. Burns, who is a user in Company B, access to the client structure in Company A and the associated node ' service . Mr. Burns may then use that node service, but since the client specific locally distributed node is associated to the client structure of Company A, it will be Company A that will be liable for the used services.
  • the client specific locally distributed node may be used by several users in a client structure (e.g. a client specific locally distributed node belonging to a company may be used by many employees) .
  • a client specific locally distributed node belonging to a company may be used by many employees.
  • One user may use it in connection with a specific appliance, while another user can later connect it to another appliance, wherein both users have access to said client structure.
  • client specific node can be associated to one and the same client structure, just as several client specific nodes can be operatively connected to one and the same local gateway node.
  • a server of the access provider preferably performs the functions of a centre or interception point for communication.
  • the server comprises software for administration of the network that interconnects the services and client structures, and also software for the different ' services offered by the service providers.
  • the server when a user in a client structure wishes to use or order a certain service and therefore sends a signal from his homepage to the access provider server, it will be forwarded from said server to the specific service provider, so that said specific service provider for example will know which client to invoice for the provided services.
  • the software for the different services provided by the service providers may be of many different types. There may e.g. be software for programming the time of activation of a service.
  • a person could program a schedule according to which the client specific locally distributed node will "use” the service. He could even program that the services will be used as soon as the client specific locally distributed node will be operatively connected to a local gateway node. There may also be software for continuously controlling, monitoring or transferring information from/to different client specific locally distributed nodes, and of course many other applications.
  • Fig. la illustrates schematically a client structure of the present invention
  • Fig. lb illustrates schematically another client structure of the present invention
  • Fig. lc defines the relationship between "one" and “many” in Fig. la and lb.
  • Fig. 2 illustrates schematically a number of client structures, wherein the inventive concept of the invention is presented
  • Fig. 3 illustrates schematically an infrastructure for the present invention
  • Fig. 4 illustrates schematically the procedure of associating a client specific locally distributed node to 'a client structure.
  • Fig. la illustrates schematically a client structure 2 of the present invention.
  • This client structure 2 is a very simple one.
  • a client structure 2 is registered with said access provider.
  • the client structure 2 also includes an associated client specific locally distributed node 6.
  • Fig. lc a definition of the relationship between "one", and "many” is illustrated, wherein a single connection represents “one” and a branch-off with three connections represents “many” .
  • Fig. la show that in the client structure 2 a single client 4 . can have several associated client specific locally distributed nodes 6.
  • the client may have only one such node 6. Every client structure will have some kind of corresponding service or services made available by the access provider.
  • Fig. la it is obviously a node related service, e.g. power consumption for recharging the batteries of an electric car, wherein a power supplier company is the service provider.
  • Fig. lb illustrates schematically another client structure 12 of the present invention.
  • This client structure 12 is more comprehensive than the one shown in Fig. la.
  • a client 14 of an access provider has a client structure 12 registered with said access provider.
  • the client structure 12 includes, besides the client 14, users 16, local gateway nodes 18, client specific locally distributed nodes 20 and services 22.
  • the term "services" is hereby meant to include such services 22 that are not node related, such as for instance web related services over the Internet (e.g. sports results information) .
  • a client may have several associated users, which is the case in Fig. lb.
  • the local gateway nodes 18 are also to be regarded as associated with some kind of node service, since locally distributed • nodes can be operatively connected thereto for actuating, controlling or monitoring different appliances.
  • the client specific locally distributed node 20, the local gateway node 18 and the services 22 are directly associated with the client 14 and not with the users 16.
  • a user 16 being able to use a service 18,20,22 (node or web related) he must be an associated user 16 in the client structure to which the service is associated.
  • he must also have a certain level of authority to make use of the service.
  • Fig. 2 illustrates schematically a number of client structures 30,40,50, wherein the inventive concept of the invention is presented.
  • Three clients 32,42,52 are represented, each having a respective client structure.
  • the client structures are only shown to include local gateway nodes and client specific locally distributed nodes. However, as has been illustrated previously, other things may be associated as well, such as users or web services.
  • the first client 32 has in his client structure 30 an associated client specific locally distributed node- 34 (or several) .
  • the second client 42 is also illustrated to have at least one client specific locally distributed node 44, and additionally at least one local gateway node 46.
  • the third client 52 is also illustrated to have at least one client specific locally distributed node 54 and at least one local gateway node 56.
  • the client structures 30,40,50 are uniquely defined and completely independent of each other. This is illustrated by the dividing dotted lines.
  • the nodes which are directly associated with a specific respective client, are depicted with continues or unbroken lines to the client. Dashed or broken lines depict that client specific locally distributed nodes are operatively connected to local gateway nodes.
  • a client specific locally distributed node 34 of the first client 32 has been connected to a local gateway node 46 of the second client 42.
  • the first client 32 can make use of his corresponding node related service and be liable thereof, while taking advantage of the second client structure 40.
  • the second client 42 has in turn connected .a client specific locally distributed node 44 being included in his client structure 40 to a local gateway node 56 being included in the third client's 52 client structure 50.
  • a client specific locally distributed node that is associate to a client structure can be operatively connected to any local gateway node, including a local gateway node in the same client structure.
  • a client specific locally distributed node 54 in the third client structure 50 is operatively connected to a local gateway node 56 in the third client structure 50.
  • the inventive idea also works if the local gateway node is not associated to a client structure, but is merely provided by the access provider for enabling said operative connection with client specific locally distributed nodes.
  • Fig. 3 illustrates schematically an infrastructure for the present invention.
  • the figure shows a server 60 of the access provider, a personal computer 62 and a house 64 in which a local gateway node 66 is located.
  • the local gateway node 66 is illustrated with three extension cords having a respective socket outlet 68a, 68b, 68c, to which client specific locally distributed nodes 70a, 70b, 70c with plugs may be connected for communication over the power mains.
  • client specific locally distributed nodes 70a, 70b, 70c are fitted or arranged to appliances (not shown) .
  • the server 60 of the access provider has an integrated or otherwise operatively connected service control module 72, which is illustrated in the form of a comb, -and said server 60 also includes a database 74 with different client structures.
  • the service control module 72 enables different service providers to interact with the system of the access provider.
  • the service providers provide the access provider with software modules which are connected to the service control module. This is . ⁇ . illustrated by the squares 76a, 76b and 76c inserted in the comb .
  • a client, or a user, in a client structure may be able to access services - associated therewith by means of the personal computer 62.
  • the user in order to access the client structure or the access provider system, the user must follow a certain login procedure, in which he must identify himself, e.g. with a password, PIN-code, or any other suitable way.
  • the computer 62 suitably communicates over a data communications network, such as the Internet, with the server 60 of the access provider.
  • the database 74 associated with the server 60- includes information of which services in said client structures are available for said user, and with what level of authority.
  • the database 74 may also point out how different users are connected to the same or different client structures.
  • the services are, as mentioned, provided by means of software modules 76a, 76b, 76c, and can include web services, such as weather information, or node related services, such as guiding a lorry carrying goods to the correct unloading spot, as previously described.
  • the access provider checks the programs provided as software modules, before connecting them to the system.
  • the server 60 of the access provider will, preferably, by means of the corresponding software module 76a, 76b or 76c forward the request and obtain the relevant service.
  • the software modules 76a, 76b, 76c are suitably developed by a respective service provider or another party engaged by the service provider. If e.g.
  • a user being on a winter holiday at a ski resort wishes to preheat his car on a cold morning he may proceed as follows. Having previously operatively connected his client specific locally distributed node • 70a of the pre-heater to a local gateway node 66 (e.g. provided by a hotel) , he may from any computer 62 or telephone send the request to the server 60 of the access provider.
  • the server 60 will retrieve the relevant program and in accordance therewith send command signals to the relevant local gateway node 66.
  • the local gateway node 66 will, in turn, communicate with the client specific locally distributed node 70a connected to the pre-heater of the car and the preheating will start according to the users request .
  • a client specific locally distributed node 70b When a client specific locally distributed node 70b is operatively connected to a local gateway node 66 , information thereof will be transmitted from the local gateway node 66 to the server 60 of the access provider, by means of a suitable communications means, such as e.g. data communication.
  • the server 60 now knows the location of the client specific locally distributed node 70b.
  • the server 60 having received the unique identity for that client specific locally distributed node 70b will by means of the associated database 74 verify if the node 70b has been associated to a client and in that case retrieve relevant client information.
  • a requested service may be executed.
  • the server 60 of the access provider knowing to which local gateway node 66 the client specific locally distributed node 70b has been connected to, will transfer the service related information to said locally distributed node 70b, via the local gateway node 66. If the node 70b has not been associated to a client, the service will not be executed, however, one may be given the possibility to register the node 70b so that the service can be used afterwards . For a client specific locally distributed node 70c which will be used in conjunction with a more or less stationary appliance, the transfer of information does not need to go all the way to the server 60.
  • Fig. 4 illustrates schematically the procedure of associating a client specific locally distributed node 80 to a client structure.
  • a person has acquired or bought a client specific locally distributed node 80, which is not yet associated with a client structure, he must register it with the access provider. In order to do this, he -accesses his client structure by visiting a certain web site of the access provider, by means of a computer 82, wherein a login procedure is performed.

Abstract

The present invention relates to a method and a system for accessing services provided via an access provider. A number of client structures are registered with the access provider, each client structure including a corresponding set of services made available by the access provider. A local gateway node is provided for communication with the access provider, wherein a number of said services includes transferring information from and/or to a number of locally distributed nodes via said local gateway node. A client specific locally distributed node is associated with a first client structure and said client specific locally distributed node is connected to said local gateway node for transferring information related to a service included in said first client structure via said local gateway node.

Description

A METHOD AND A SYSTEM FOR ACCESSING SERVICES
Technical field o£ the invention
The present invention relates to a method and a system for providing intelligent services, in particular for providing access to such services.
Background art
In today's society there is a great choice of available intelligent services. As people tend to have less time for acquiring desired services, the demand increases for making them easily and quickly accessible. New technologies make intelligent services accessible over different kinds of media. An example where a large quantity of intelligent services are provided is the Internet.
The concept of intelligent homes has received growing attention. A system for an intelligent home may include an external network, such as an IP network, and a local network. Between these two networks there is some sort of local gateway. Locally distributed nodes may be connected to the local gateway for - controlling different home appliances. A client can thus from his computer over the internet and via the local gateway communicate with a specific node that controls a specific appliance. Naturally, this type of technique is not limited, to just intelligent homes but can be implemented in other cases as well .
The problem with such systems is that a client can only use locally distributed nodes when they are connected to his specific local gateway, since the communication goes via this local gateway. On one hand it is a great advantage that the client may be located anywhere when communicating with the locally distributed nodes, on the other hand it is a drawback that the nodes may not correspondingly be located anywhere. Thus, there still remains to find a way to make the locally distributed nodes geographically independent and the client less dependent of his local gateway, since the current systems do not have such flexibility.
If a client would try to use one of his locally distributed nodes by operatively connecting it to a local gateway owned or controlled by someone else, it would not work or the other person would be liable for the used service, which would be morally incorrect.
Summary of the invention
An object of the present invention is to achieve a method and a system which are more flexible then the previously described prior art .
Another object of the invention is to make services provided by service providers more easily accessible.
Yet another object is to increase the liability of a client for used services.
These and other objects which will become apparent in the following are achieved by a method and a system as defined in the accompanied claims.
According to one aspect of the invention a method is provided, in which services provided via an access provider are to be accessed. A respective client structure is registered for a number of clients with the access provider. Each client structure includes a corresponding set of services which are made available by the access provider. A local gateway node, which is in communication with the access provider, is provided, wherein a number of said services includes transferring information from and/or to a number of locally distributed nodes via said local gateway node. A client specific locally distributed node is associated with a first client structure and is. connected to said local gateway node for transferring information related to a service included in said first client structure via said local gateway node .
According to. another aspect of the invention a system for accessing services is provided. The system includes: a server including a database with different client structures, each client structure being associated with a client; a service control module for enabling different service providers to interact with the system, said service control module being operatively connected to said server; a local gateway node in communication with said server, wherein said local gateway node being further adapted for communication with locally distributed nodes; and a client specific locally distributed node which is associated with a first client structure, wherein said client specific locally distributed node is operatively connected to said local gateway node for transferring information related to a service included in said first client structure via said local gateway node. Thus, the present invention provides, for a service platform which e.g. can be accessed via the Internet. The service platform is created and operated by an access provider. In other words, the access provider provides a commercial infrastructure for intelligent services. The a.ccess provider can give service providers, such as companies, the possibility to interact with the service platform and to offer services to clients registered with the access provider. The services are, in accordance with the invention, node related services, but there may of- course be of other types as ell, such as Internet services, as for instance weather forecasts. Of course some services may even be provided by the access provider .
A client which is registered with the access provider can be a large .company, but it- can also be a single person. For every client, the access provider defines a respective client structure . In one embodiment of the invention, each client structure has at least one assigned user. The user is thus the one who actually uses the provided services, while the client in the client structure is liable for the used services. Naturally, a client and a user may be one and the same person.
In a node related service a locally distributed node is preferably used for controlling, monitoring or in some other way communicating or transferring information to/from a certain appliance, e.g. an electrical appliance. The locally distributed node must be connected to a local gateway node in order to establish communication with the service platform.
A user can in one embodiment access a client structure by a simple login on a web page of the access provider. After the' login procedure he will see what services he may use. Naturally, it is not necessary to have a graphical user interface. The user may proceed in a corresponding way over a telephone, using e.g. DTMF tones . The invention is based on the insight that it is possible to achieve a flexible service platform by defining a respective client structure for each client. The client structures, or the contents thereof, may be different from one client to another. However, each client structure may be given the possibility to use some kind of associated service (s) , such as node or web services. In contrary to prior art systems, wherein locally distributed nodes are directly associated to a specific gateway to which they are connected, the present invention breaks up this strict connection, and instead client specific locally distributed nodes are achieved. As the expression states,- these nodes are directly associated to a client. This is obviously an approach which goes completely against the traditional technique in the prior art.
By making a direct logical association between a locally distributed node and a client, this allows of operatively connecting the locally distributed node to . any local' gateway node, while the locally distributed node is still accessible in the client's client structure. This is particularly favourable when a locally distributed node is connected to a mobile or movable appliance .
A client specific locally distributed node is thus geographically independent, in the sense that it can be located anywhere as long as it is in communication with a local gateway node. Preferably, a client specific locally distributed node is a movable object, which can be relocated, installed or operatively connected to different appliances.
An example of a favourable application of the invention is a client specific locally distributed node being connected to the engine pre-heater of a car. The pre-heater cable plug can be plugged .into a socket which is in communication with any local gateway node. Since the client specific locally distributed node is associated to a specific client, the client can be identified and charged for the consumed power. The service provider in this case is a power supplier, company. Suitably, the client can, e.g. from his mobile phone, program the time he desires that the heating of the engine should start, wherein the mobile phone is in communication with a server of the access provider, which server in turn transmits a signal to the locally distributed node- via the local gateway node.
Another somewhat different example is a company selling food or beverages from vending machines. Such a company has many machines distributed at different locations, such as factories, tennis halls, train stations etc.. Usually, the company either regularly sends an operator and maintenance person- to check up on or re-fill the machines, or is informed by somebody at the location that a re-fill is needed or that the machine is out of order. With client specific locally distributed nodes applied in the machines, the machines can be connected to an existing local gateway node, and thereby the company will continuously have information regarding the state of the machines. In this case the company itself, besides being a client to the access provider, may be the service provider that generates information . updates regarding the vending machines, or there may be an external service provider.
In the above described examples, there is a difference to be noted. The first example relates to an appliance (a car, or actually the pre-heater in the car) which is often moved from one geographic location to another, and thus will be connected to many different local gateway nodes on different occasions. The second example relates to a more or less stationary appliance (a vending machine) which will be connected to the same local gateway node for a longer period of time. When the services provided via the access provider are used, the relevant client specific locally distributed node, and thus the liable client, should be identified. The identification of the locally distributed node may, but is not required to, be performed in somewhat different ways for the two examples above, as will be explained in the following. For a client specific locally distributed node which will be used in conjunction with a mobile appliance that is frequently relocated and found connected to different local gateway nodes, an identification procedure may be as follows. When the client specific locally distributed node is operatively connected by means of e.g. the power mains, radio communication or in some other way to a local gateway node, information thereof will be transmitted from the local gateway node to the server of the access provider. The server now knows the location, or the latest location of the client specific locally distributed node. The information received by the server includes a unique identity for the client specific locally distributed node and the server will by means of an associated database verify if the node has been associated to a client and in that case retrieve relevant client information, such as name, billing address or account etc. After a positive identification a service associated with that client structure can be used and service related information be transferred to the client specific locally distributed node via the local gateway node. Since the client specific locally distributed node is connected to a frequently relocated appliance, it is suitably polled by the server via the local gateway node at short intervals, in order to check if the client specific locally distributed node is still under that local gateway node . For a client specific locally distributed node which will be used in conjunction with a more or less stationary appliance, the transfer of information does not need to go all the way to the server. Once the server has been informed of the local gateway node to which the locally distributed node is operatively connected, the identification information is stored in the local gateway node. Suitably, software which is related to the available services is downloaded from the server to the local gateway node. This way, unnecessary data traffic to the server is avoided, the downloaded programs in the local gateway node may run independently of the server and information and data may be stored in the local gateway node. The local gateway node may suitably poll the client specific locally distributed node at regular intervals for updating certain data or other type of information. Of course the first time a client specific locally distributed node is operatively connected to a specific local gateway node, this information must be communicated to the server. However, for subsequent use that will not be necessary. Note that this approach, is mainly suitable in conjunction with a relatively stationary appliance. Suitably, if one wishes to move a client specific locally distributed node which is connected to a relatively stationary appliance as described above from a first local gateway node to a second local gateway node, the client will reactivate the client specific locally distributed node. This is for practical reasons, since client related information that was stored in the first local gateway node will not automatically be transferred to the second local gateway node, unless the client reactivates the client specific locally distributed node. This can e.g. be done by operatively connecting the client specific locally distributed node to the second local gateway node, wherein the server of the access provider will be informed thereof and client related information will consequently be stored at that local gateway node. Alternatively, for security reasons, the client may have to enter his client structure and reregister the client specific locally distributed node. Note that this procedure mainly applies for nodes connected to relatively stationary appliances.
Naturally, a client specific locally distributed node can not only be associated to a client structure, but can also be disconnected therefrom. An advantage of this fact is e.g. if the client specific locally distributed node is stolen. The owner of the node enters his client structure and simply disconnects or inactivates the node, i.e. making it at least temporarily out of order, whereby he is spared from being charged for services attempted to be used by the thief. It may even be possible to trace the thief when he tries to use said node. Alternatively, instead of, or as a complement to, disconnecting said node, one could simply enter the client structure and block said node so that no one can use it. Another possibility is to disconnect the client specific locally distributed node in one client structure and associate it to another. This can occur if someone e.g. gives his node to a friend or the like.
There are of. course many other possible applications of the invention. For instance, a power supplier company may connect a client specific locally distributed node in the form of an electricity meter to a private person's local gateway node. The power supplier company (the client) will have the sole access right to read or manipulate that electricity meter. Another example is a copying machine leasing company which provides offices with copying machines. Each machine may have a client specific locally distributed node connected thereto, so that information regarding number of copies, consumed power, etc. is recorded by the leasing company. The company knows which locally distributed node is operatively connected to which local gateway node, and has thus full control for e.g. invoicing or repairing purposes .
An example of the client specific locally distributed node being connected to a frequently relocated appliance may be a node for the electrical charging of an electric car, said car being the frequently relocated appliance. Such a client specific locally distributed node is connected to a set of ' accumulator batteries, and operatively connected to a local gateway node via the power mains, so that the consumed power is registered. Another example is a boat coming to a port and a client specific locally distributed node on the boat is operatively connected to a local gateway for paying harbour dues or for .using certain services in the port. Yet another example is when transporting goods to a certain location or large establishment, the driver of a lorry carrying the goods may e.g. need to be quickly informed of where to unload the goods. The lorry may be provided with a client specific locally distributed node which, when passing a gate of the establishment, communicates by means of e.g. radio communication with a local gateway node and subsequently with the server of the access provider. The server identifies the client and will transfer information to the client specific locally distributed node. Said transferred information includes an indication of which platform that particular lorry should proceed to for unloading the goods .
The present invention has many different possible applications, of which only a few have been mentioned herein above. However, the same inventive concept applies for all applications, namely a locally distributed node being directly associated to a client structure, which is registered with an access provider.
As has been described above a local gateway node could communicate with locally distributed nodes in many different ways. Some examples of means of communications are the power mains, telecommunication, radio or data communication, etc.
In some cases a local gateway node may be associated to a client structure. For example, a private person may have a local gateway node at home, which is in communication over the power mains with normal stationary locally distributed nodes that are connected to different appliances, such as the fridge, the iron, the burglar alarm system, etc. When a friend comes for a visit by car he may, as in the previous example, pre-heat the car by plugging the cable into a socket which via the mains communicate with the local gateway node in the house. Since this friend has a client specific locally distributed node installed in connection to the pre- heater, his client structure will be identified and charged for the used service, i.e. the consumed power. Thus, a client specific locally distributed node which is associated to a first client structure can be connected to a local gateway node which is associated to a second client structure, thereby transferring information related to a service included in said first client structure via said local gateway node. It goes without saying that a client specific locally distributed node can also be operatively connected to a local gateway node, when both of them are associated to one and the same client structure.
Clearly the present invention does not exclude the use of locally distributed nodes which are directly associated with a local gateway node. Such nodes can be used as a complement to the more flexible client specific locally distributed node.
As mentioned previously a client may be a private person who has come to an agreement with the access provider. This private person will then have a client structure registered with the access provider. In one embodiment of the invention a client structure includes at least one user. In the case of a private person being the client, the person himself would suitably be a user in that client structure. If a large company is the client, then some of the employees may be users. Suitably, there is a superuser who has superior authority to the other users . Such a superuser could decide to associate new users to his client structure. This could apply for a private person as well, as he could associate e.g. family members to his client structure. In such a case, it is preferably the superuser who has the authority to associate new locally distributed nodes and related services to that specific client structure.
When someone, a -user in the above embodiment, wishes to associate a newly acquired client specific locally distributed node, he will do it by accessing his corresponding client structure. This can preferably be done by means of a computer or a telephone. In case of a computer, he can visit on the Internet a web site of the access provider. After a login procedure, including stating some sort of personal identification code, he • will come to a private home page. There he will have an option of adding new client specific locally distributed nodes to his client structure. This is preferably performed by entering a- unique identity number, which is found on the node . or accompanied therewith at the time of acquisition, wherein the node has become associated with the client structure. Suitably, it should be possible to buy client specific locally distributed nodes which are not yet associated to any client structure in any shop or store. Since they are not yet associated or "taken" by anyone, the above mentioned associating procedure may be performed by. the buyer.
Preferably, on a persons private homepage, the person will be able to see what services are available and the nodes associated to his client structure. He may even be able. to see client specific locally distributed nodes from another client structure that have been operatively connected to a local gateway node in his client structure. However, these nodes are merely shown for information and are not controllable by said person. On the private home page, he may in one embodiment also have icons or references to all the client structures in which he is a user (a user can be associated to several client structures as will later be described) . Thus, by clicking on one of these references he enters a specific client structure, and will there be able to access a number of services.
The client specific locally distributed node according to the present invention can advantageously be utilised in connection with a method and a system as disclosed in the Swedish patent application SE 0001139-5, which is hereby incorporated as a reference. In
SE 0001139-5 each client structure has at least one user, and a characteristic feature of the invention is that a first user in a first client structure can give authority to a second user in a second client structure to access said first client structure and its corresponding associated services. Such an associated service could relate to a client specific locally distributed node according to the present invention. For instance, a client specific locally distributed node is associated to the client structure of Company A, in which Mr. Smith is a user. He decides to give Mr. Burns, who is a user in Company B, access to the client structure in Company A and the associated node ' service . Mr. Burns may then use that node service, but since the client specific locally distributed node is associated to the client structure of Company A, it will be Company A that will be liable for the used services.
Thus, the client specific locally distributed node may be used by several users in a client structure (e.g. a client specific locally distributed node belonging to a company may be used by many employees) . One user may use it in connection with a specific appliance, while another user can later connect it to another appliance, wherein both users have access to said client structure.
Naturally, more than one client specific node can be associated to one and the same client structure, just as several client specific nodes can be operatively connected to one and the same local gateway node.
A server of the access provider preferably performs the functions of a centre or interception point for communication. Suitably, the server comprises software for administration of the network that interconnects the services and client structures, and also software for the different ' services offered by the service providers. Thus, when a user in a client structure wishes to use or order a certain service and therefore sends a signal from his homepage to the access provider server, it will be forwarded from said server to the specific service provider, so that said specific service provider for example will know which client to invoice for the provided services. The software for the different services provided by the service providers may be of many different types. There may e.g. be software for programming the time of activation of a service. A person could program a schedule according to which the client specific locally distributed node will "use" the service. He could even program that the services will be used as soon as the client specific locally distributed node will be operatively connected to a local gateway node. There may also be software for continuously controlling, monitoring or transferring information from/to different client specific locally distributed nodes, and of course many other applications.
Brief description of the drawings
Fig. la illustrates schematically a client structure of the present invention; Fig. lb illustrates schematically another client structure of the present invention;
Fig. lc defines the relationship between "one" and "many" in Fig. la and lb.
Fig. 2 illustrates schematically a number of client structures, wherein the inventive concept of the invention is presented;
Fig. 3 illustrates schematically an infrastructure for the present invention;
Fig. 4 illustrates schematically the procedure of associating a client specific locally distributed node to 'a client structure.
Detailed description of the drawings
Fig. la illustrates schematically a client structure 2 of the present invention. This client structure 2 is a very simple one. Thus, for a client 4 of an access provider a client structure 2 is registered with said access provider. Apart from the client 4, the client structure 2 also includes an associated client specific locally distributed node 6. In Fig. lc a definition of the relationship between "one", and "many" is illustrated, wherein a single connection represents "one" and a branch-off with three connections represents "many" . Accordingly, Fig. la show that in the client structure 2 a single client 4. can have several associated client specific locally distributed nodes 6. Naturally, the client may have only one such node 6. Every client structure will have some kind of corresponding service or services made available by the access provider. In Fig. la it is obviously a node related service, e.g. power consumption for recharging the batteries of an electric car, wherein a power supplier company is the service provider.
Fig. lb illustrates schematically another client structure 12 of the present invention. This client structure 12 is more comprehensive than the one shown in Fig. la. Thus, in Fig. lb a client 14 of an access provider has a client structure 12 registered with said access provider. The client structure 12 includes, besides the client 14, users 16, local gateway nodes 18, client specific locally distributed nodes 20 and services 22. The term "services" is hereby meant to include such services 22 that are not node related, such as for instance web related services over the Internet (e.g. sports results information) .
As previously explained a client may have several associated users, which is the case in Fig. lb. The users
16, possibly depending on their level of authority, have access to the different types of services 18,20,22, both node related and web related. It is not only the client specific locally distributed nodes 20 that are associated with some type of node service. Essentially, the local gateway nodes 18 are also to be regarded as associated with some kind of node service, since locally distributed nodes can be operatively connected thereto for actuating, controlling or monitoring different appliances. There may e.g. be a standard locally distributed node (not a client specific node) operatively connected to a local gateway node 18, wherein a .user 16 e.g. can control the temperature of his house from a distant computer which communicates with said standard node via the local gateway node 18.
It should also be appreciated that the client specific locally distributed node 20, the local gateway node 18 and the services 22 are directly associated with the client 14 and not with the users 16. Thus, for a user 16 being able to use a service 18,20,22 (node or web related) he must be an associated user 16 in the client structure to which the service is associated. Suitably, he must also have a certain level of authority to make use of the service.
It should further be pointed out that while standard locally distributed nodes of the prior art would be directly associated to a local gateway node, the client specific locally distributed node of this invention is logically directly associated to the client and is independent of local gateway nodes in that sense.
Fig. 2 illustrates schematically a number of client structures 30,40,50, wherein the inventive concept of the invention is presented. Three clients 32,42,52 are represented, each having a respective client structure. For reasons of clarity, the client structures are only shown to include local gateway nodes and client specific locally distributed nodes. However, as has been illustrated previously, other things may be associated as well, such as users or web services.
The first client 32 has in his client structure 30 an associated client specific locally distributed node- 34 (or several) . The second client 42 is also illustrated to have at least one client specific locally distributed node 44, and additionally at least one local gateway node 46. Likewise, the third client 52 is also illustrated to have at least one client specific locally distributed node 54 and at least one local gateway node 56. The client structures 30,40,50 are uniquely defined and completely independent of each other. This is illustrated by the dividing dotted lines.
The nodes, which are directly associated with a specific respective client, are depicted with continues or unbroken lines to the client. Dashed or broken lines depict that client specific locally distributed nodes are operatively connected to local gateway nodes. Thus, in Fig. 2 a client specific locally distributed node 34 of the first client 32 has been connected to a local gateway node 46 of the second client 42. The first client 32 can make use of his corresponding node related service and be liable thereof, while taking advantage of the second client structure 40. The second client 42 has in turn connected .a client specific locally distributed node 44 being included in his client structure 40 to a local gateway node 56 being included in the third client's 52 client structure 50.
According to the invention a client specific locally distributed node that is associate to a client structure can be operatively connected to any local gateway node, including a local gateway node in the same client structure. This is illustrated in Fig. 2, wherein a client specific locally distributed node 54 in the third client structure 50 is operatively connected to a local gateway node 56 in the third client structure 50. Of course, the inventive idea also works if the local gateway node is not associated to a client structure, but is merely provided by the access provider for enabling said operative connection with client specific locally distributed nodes.
Fig. 3 illustrates schematically an infrastructure for the present invention. The figure shows a server 60 of the access provider, a personal computer 62 and a house 64 in which a local gateway node 66 is located. The local gateway node 66 is illustrated with three extension cords having a respective socket outlet 68a, 68b, 68c, to which client specific locally distributed nodes 70a, 70b, 70c with plugs may be connected for communication over the power mains. This is just an example, and other communication means may be just as adequate, such as radio, data or Bluetooth communication. The client specific locally distributed nodes 70a, 70b, 70c are fitted or arranged to appliances (not shown) .
The server 60 of the access provider has an integrated or otherwise operatively connected service control module 72, which is illustrated in the form of a comb, -and said server 60 also includes a database 74 with different client structures. The service control module 72 enables different service providers to interact with the system of the access provider. The service providers provide the access provider with software modules which are connected to the service control module. This is . \. illustrated by the squares 76a, 76b and 76c inserted in the comb .
A client, or a user, in a client structure may be able to access services - associated therewith by means of the personal computer 62. Preferably, in order to access the client structure or the access provider system, the user must follow a certain login procedure, in which he must identify himself, e.g. with a password, PIN-code, or any other suitable way. The computer 62 suitably communicates over a data communications network, such as the Internet, with the server 60 of the access provider. The database 74 associated with the server 60- includes information of which services in said client structures are available for said user, and with what level of authority. The database 74 may also point out how different users are connected to the same or different client structures.
The services are, as mentioned, provided by means of software modules 76a, 76b, 76c, and can include web services, such as weather information, or node related services, such as guiding a lorry carrying goods to the correct unloading spot, as previously described. Suitably, the access provider checks the programs provided as software modules, before connecting them to the system. At a received request form a user to access a certain service, the server 60 of the access provider will, preferably, by means of the corresponding software module 76a, 76b or 76c forward the request and obtain the relevant service. The software modules 76a, 76b, 76c are suitably developed by a respective service provider or another party engaged by the service provider. If e.g. a user being on a winter holiday at a ski resort wishes to preheat his car on a cold morning he may proceed as follows. Having previously operatively connected his client specific locally distributed node • 70a of the pre-heater to a local gateway node 66 (e.g. provided by a hotel) , he may from any computer 62 or telephone send the request to the server 60 of the access provider. The server 60 will retrieve the relevant program and in accordance therewith send command signals to the relevant local gateway node 66. The local gateway node 66 will, in turn, communicate with the client specific locally distributed node 70a connected to the pre-heater of the car and the preheating will start according to the users request .
When a client specific locally distributed node 70b is operatively connected to a local gateway node 66 , information thereof will be transmitted from the local gateway node 66 to the server 60 of the access provider, by means of a suitable communications means, such as e.g. data communication. The server 60 now knows the location of the client specific locally distributed node 70b. The server 60 having received the unique identity for that client specific locally distributed node 70b will by means of the associated database 74 verify if the node 70b has been associated to a client and in that case retrieve relevant client information. Hereafter, a requested service may be executed. Thus, after a user has sent his service request from his computer 62 or telephone, the server 60 of the access provider, knowing to which local gateway node 66 the client specific locally distributed node 70b has been connected to, will transfer the service related information to said locally distributed node 70b, via the local gateway node 66. If the node 70b has not been associated to a client, the service will not be executed, however, one may be given the possibility to register the node 70b so that the service can be used afterwards . For a client specific locally distributed node 70c which will be used in conjunction with a more or less stationary appliance, the transfer of information does not need to go all the way to the server 60. Once the server 60 has been informed of the location of the locally distributed node 70c, the identification information may be transmitted from the database 74 and stored in the local gateway node 66. Likewise, software related to services will be downloaded from the server 60 to the local gateway node. Fig. 4 illustrates schematically the procedure of associating a client specific locally distributed node 80 to a client structure. When a person has acquired or bought a client specific locally distributed node 80, which is not yet associated with a client structure, he must register it with the access provider. In order to do this, he -accesses his client structure by visiting a certain web site of the access provider, by means of a computer 82, wherein a login procedure is performed. Arriving at his private page, he will be have the possibility to associate a new client specific locally distributed node to his client structure. If he wishes to chose that option, he will be requested to enter a unique identity number or code of the node 80. Thus, the person proceeds by finding out the necessary unique identity. This is illustrated with an eye 84. Aptly, the unique identity is distinctly printed on the node 80. Having found the unique identity, the person will feed these in
Figure imgf000023_0001
PJ - tr rr μ- ) O O Φ 02 Ω o < 02 CQ SD Hi ^ ι-3 SD P μ- SD
Ω μ- •<! Φ P Ω S" tr h-1 TJ j Hi SD rt » ii ii μ- " Ω P rt
Ω Hi 03 Ω H. < d Φ D ϋ H φ 0 LQ Φ Ω H
0 l-h 3 Φ rr Φ rr μ- Ω Ω H- rt μ- d Ω 0 3 Φ CT" d rt
H Φ φ •d »> CQ o μ- μ- 3 t SD Ω μ- « CQ CQ φ 02 "
P- i PJ t P 02 tr d α Hι 1-3 02 φ rt M rt Hi rt L Φ 02 H > rt Φ
P) Φ P 0 Ω S CD SD μ- i-r • μ- rt d μ- U2 t — ' ii Hi li
P P m P Φ T5 02 02 H" rr Ω d T3 o ii Ω ιt» Φ . < T3 O rt SD Ω
Ω rt Φ μ 0 ^ μ- 02 ii P 02 Φ . Φ ii H Φ rt O
Φ 0 0 φ - <! CQ φ 02 tr (i ii O ii Φ H.
SD Hi P> <! 3 Φ φ 02 0 SD 0 ι-3 SD P < Ω 02 ϋ
3 H t μ- hzi Φ 3 ϋ μ- φ Ω d P Ω PJ rt Hi CD μ- O rt Φ μ- rr SD μ- π α P' SD Φ <! rr P SD j Si SD Φ SD 0 CO ϋ &. tr r 02 rt Φ Ω Φ Φ SD Φ P X μ- ct P & tr H Φ Φ Φ PJ Ό
PJ ϋ Ω tr n ϋ 02 P ^ SD Ω μ- 02 02 SD 3 tr ii - μ- o
P Φ CQ - μ- 3 φ 02 μ- tr tr rt ^ Φ 02 SD SD h 02 P rr PJ μ- 0 Q μ- 0 T3 02 P Φ Φ O ii φ rt 02 μ- Φ . fi
PJ rr 02 P o φ Hi rt H" rr <J ti P <! μ- H3 ct ii μ-
Φ μ- P rr u tr Φ PJ 0 φ 3 P Φ μ- Φ > > 0 SD tr CQ P
<! Ω Ω tr rt φ 02 SD P SD 0 02 t t P P μ- μ- 0 CQ ts φ f» » φ Ω ∑r H. <! tr rt P- rt rt rt . 02 02 P d CQ ϋ •d P ii O φ m Hi φ φ H- φ Φ PJ t CD Ω SD φ
H SD 3 0 0 Si μ- μ- oo H] SD CQ μ- rt P* P
TJ 0) * tr Ω 3 h _i SD ϋ tr d P Ξ CQ tr " P 02 02 ϋ SD rt
0 f PJ 0 Φ d ϋ H Φ P μ- rt P ^ μ- O SD 02 ii
CQ Φ 0 Φ 3 SD rt Φ Φ rr Φ P-. rt tr μ- rt μ- 02 tr Ω μ- P •< φ P 3 P Φ <! t-r" P Φ Φ PJ SD P Φ Φ μ- y-> CQ φ
T, φ o P CQ t μ- Ω φ ti Hi O rt Hi ϋ μ- SD t-1 3 P o
0 0 Hi P 0 0 h Q μ- d 0 02 rt d μ- rt P M l-h 02 =3 μ- &) tr d P Φ 0 rr 3 rt P H P SD Φ Φ CQ rt Φ H
CQ rt Ω H SD ra Ω S" μ- O φ C 3 0 02 μ- CQ fi rt rt t rt rt μ- h_> 4 ø) Φ ra Φ CQ P 0 3 SD CQ I-1 μ- H Φ Φ tr t t 1 0) rr Φ p. μ- ro rt P_ Φ rt Φ 0 m 0- SB Cb (D
Φ μ- P φ Φ U φ <5 Φ μ- Ό ii μ- Ω d rr SD rr
Φ 3 m Λ 02 D o i rt P SD O o CO μ- 02 Φ rt rt rt ≤ μ- rr 3 ff d Ω Ω tr Hi tr d 3 O SD ( ϋ W 0 tr (D
3 Hi φ H-- •< SD 0 i 0 SD rr rt CQ rr ii Φ tr φ σ
<i 0 H rr 3 μ- Φ P d rt 4 μ- μ- -3 φ Si SD =5 SD
Φ H Hi rr 3 3 h . P rr Φ P 3 P μ- rt CQ μ- d 02
P 0) μ- φ ^ 'd rr & - Φ IQ 0 rt rt Φ μ- φ rr CQ P H- rr μ- Ω P SD P μ- Φ < SD Si r PJ p- ϋ P - Φ μ- rt μ- 3 φ ua P 13 μ- o ii rr Φ Ω Hi μ- PJ Φ o 4 Λ Φ
0 • - CQ O Ω P CQ PJ P Ω ii Hi Φ rt ^ SD t S < d •
P α CQ SD rr Φ 0 0 μ- PJ Ω μ- 3 P Φ φ
• Φ φ H 0 CQ rr Hi SD * rt 3 3 Ω Φ rt ϋ ^-, ti
3 rr 3 Hi μ- μ- O P tr V SD SD μ- PJ Ω SD μ- P φ Ω ^ tr o H Q, SD o SD rt rt rt Ω φ fi O ti CO Ωi
P • 1 PJ P μ- ti d P PJ μ- SD j P SD Φ 3 ii co φ SD rr • rr Φ rr p φ to. μ- Φ 0 σ μ- rr rt . O P ii J 0 • rr J CQ PJ φ P SD φ Si ϋ SD 3 O rt ii rt ι-3 P O Φ . 0 P* 02 02 02 P O μ- i Hi μ- O μ- P* Φ 1_ P CQ Ω φ rr d Φ φ o rr
0 d CQ 0 rr 3 o 0 SD tr J o rt •<;
P tn ii tr O » 3 P SD Φ 3 • tr co
0 Φ ω φ Φ a, t Φ Si μ- Φ μ- ii rr 1 rt
P t

Claims

Claims
1. A method for accessing services provided via an access provider, including the steps of: registering, for a number of clients, a respective client structure with the access provider, each client . structure including a corresponding set of services made available by the access provider; providing -a local gateway node for communication with the access provider, wherein- a number of said services includes transferring information from and/or to a number of locally distributed nodes via said local gateway node; associating a client specific locally distributed node with a first client structure; ' nd connecting said client specific locally distributed node to said local gateway node for transferring information related to a service included in said first client structure via said local gateway node.
2. The method as claimed in claim 1, wherein said associating step is performed independently of or separately from the local gateway node, for providing a direct logical association between the client . specific locally distributed node and the first client structure.
3. The method as claimed in any one of claims 1 - 2 , wherein said client specific locally distributed node is connectable to any one of a plurality of local gateway nodes which are distributed at different geographical locations.
4. The method as claimed in any one of claims 1 -3, wherein said local gateway node is associated with a second client structure.
5. The method as claimed in any one of claims 1 - 4, wherein said client specific locally distributed node is a movable object ,. herein said movable object is associated with a specific client structure which is registered with the access provider.
6. The method as claimed in any one of claims 1 - 5, further including the step of transmitting a signal from the client specific locally distributed node, via said local gateway node, to the access provider in order to identify said first client structure to which the client specific locally distributed node is associated.
7. The method as claimed in claim 6, wherein said signal transmitting step is only performed the first time that the first client structure is to be identified, whereupon client related information is stored at the local gateway node, and wherein subsequent identification is performed by transmitting a signal from the client specific locally distributed node to said local gateway node.
8. The method as claimed in any one of claims 1 - 6, wherein said client specific locally distributed node is operatively connected to a readily movable appliance or an appliance in motion, and is adapted to control, monitor, collect data from or transfer other type of information to/from said appliance.
9. The method as claimed in claim 8, wherein said movable appliance is a means of conveyance, such as a vehicle, e.g. car, boat, caravan, aeroplane or the like.
10. The method as claimed in any one of claims 1 - 7, wherein said client specific locally distributed node is operatively connected to a relocateable appliance, such as an electricity meter, an office machine, a vending machine or the like, which in use is essentially stationary, said client specific locally distributed node being adapted to control, monitor, collect data from or transfer other type of information to/from said appliance.
11. The method as claimed in any one of claims 1 - 10, wherein said step of associating a client specific locally distributed node includes accessing said first client structure and registering, to said first client structure, a unique identity of said client specific locally distributed node with the access provider.
12. The method as claimed in any one of claims 1 - 11, wherein at least one user is assigned to each client structure .
13. The method as claimed- in claim 12, including the step of associating each assigned user with a user interface with which a corresponding client structure is accessible .
14. The method as claimed in claim 13, wherein said user interface is a graphical user interface, such as a web page.
15. The method as claimed in claim 14, wherein said client specific locally distributed node is adapted to be accessed, operated, controlled or monitored from a computer having said graphical user interface with a reference to the client specific locally distributed node .
16. The method as claimed in any one of claims 1 - 13, wherein said client specific locally distributed node is adapted to be accessed, operated, controlled or monitored from a telephone which is capable of transmitting DTMF (Dual Tone Multi Frequency) tones.
17. The method as claimed in any one of claims 1 - 16, wherein a client is a physical person.
18. The method as claimed in any one of claims 1 - 16, wherein a client is a juridical person.
19. The method as claimed in any one of claims 1 -
18, wherein at least some of said services provided via said access provider are defined by at least one external service provider.
20. The method as claimed in any one of claims 1 -
19, wherein at least some of said services provided via said access provider are defined by said access provider.
21. The method as claimed in any one of claims 1 - 20, wherein the client specific locally distributed node communicates with the local gateway node by means of the power mains, telecommunication, radio or data communication, or the like.
22. A system for accessing services, including: a server including a database with different client structures, each client structure being associated with a client; a service control module for enabling different service providers to interact with the system, said service control module being operatively connected to said server; a local gateway node adapted to communicate with said server, wherein said local gateway node is further adapted to communicate with locally distributed nodes; and a client specific locally distributed node which is associated with a first client structure, wherein said client specific locally distributed node is operatively connected to said local gateway node for transferring information related to a service included in said first client structure via said local gateway node.
23. The system as claimed in claim 22, wherein the client specific locally distributed node is logically directly associated with said first client structure, independently of the local gateway node.
24. The system as claimed in any one of claims 22 -
23, wherein said system includes a plurality of local gateway nodes which are distributed at different geographical locations, wherein the client specific locally distributed node is operatively connectable to any one of said plurality of local gateway nodes.
25. The system as claimed in any one of claims 22 -
24, in which said local gateway node is associated with a second client structure.
26. The system as claimed in any one of claims 22 - 25, wherein said client specific locally distributed node is operatively connected to a readily movable appliance or an appliance in motion, and is adapted to control, monitor, collect data from or transfer other type of information to/from said appliance.
27. The system as claimed in any one of claims 22 -
25, wherein said client specific locally distributed node is operatively connected to a relocateable appliance, such as an electricity meter, an office machine, a vending machine or the like, which in use is essentially stationary, said client specific locally distributed node being adapted to control, monitor, collect data from or transfer other type of information to/from said appliance .
28. The system as claimed in any one of claims 22 - 27, wherein said server provides an interface for enabling different clients to interact with the system.
29. The system as claimed in claim 28, wherein said interface is a graphical user interface, such as a web page.
30. The system as claimed in claim 29, wherein said client specific locally distributed node is adapted to be accessed, operated, controlled or monitored from a computer having said graphical user interface with a reference to the client specific locally distributed node .
31. The system as claimed in any one of claims 22 - 30, wherein said client specific locally distributed node is adapted to be accessed, operated, controlled or monitored from a telephone which is capable of transmitting DTMF (Dual Tone Multi Frequency) tones.
32. The system as claimed in any one of claims 22 - 31, wherein the client specific locally distributed node communicates with the local gateway node by means of the power mains, telecommunication, radio or data communication, or the like.
PCT/SE2001/001336 2000-07-11 2001-06-13 A method and a system for accessing services WO2002005569A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2001266459A AU2001266459A1 (en) 2000-07-11 2001-06-13 A method and a system for accessing services

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
SE0002620A SE516672C2 (en) 2000-07-11 2000-07-11 Procedures and systems for accessing services.
SE0002620-3 2000-07-11

Publications (1)

Publication Number Publication Date
WO2002005569A1 true WO2002005569A1 (en) 2002-01-17

Family

ID=20280456

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2001/001336 WO2002005569A1 (en) 2000-07-11 2001-06-13 A method and a system for accessing services

Country Status (3)

Country Link
AU (1) AU2001266459A1 (en)
SE (1) SE516672C2 (en)
WO (1) WO2002005569A1 (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5828887A (en) * 1996-05-23 1998-10-27 Electronic Data Systems Corporation Network based program loader system and method of operation
US5881134A (en) * 1994-12-02 1999-03-09 Voice Control Systems, Inc. Intelligent call processing platform for home telephone system
US6044403A (en) * 1997-12-31 2000-03-28 At&T Corp Network server platform for internet, JAVA server and video application server

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5881134A (en) * 1994-12-02 1999-03-09 Voice Control Systems, Inc. Intelligent call processing platform for home telephone system
US5828887A (en) * 1996-05-23 1998-10-27 Electronic Data Systems Corporation Network based program loader system and method of operation
US6044403A (en) * 1997-12-31 2000-03-28 At&T Corp Network server platform for internet, JAVA server and video application server

Also Published As

Publication number Publication date
SE0002620D0 (en) 2000-07-11
AU2001266459A1 (en) 2002-01-21
SE516672C2 (en) 2002-02-12
SE0002620L (en) 2002-01-12

Similar Documents

Publication Publication Date Title
CN101971184B (en) Client/server system for communicating according to the standard protocol OPC UA and having single sign-on mechanisms for authenticating, and method for performing single sign-on in such a system
US8396220B2 (en) System and method of mobile content sharing and delivery in an integrated network environment
CN102771102B (en) The network of distribute digital content and management method
CN101350710B (en) Network system, authority issuing server, authority issuing and executing method
CN100583874C (en) Method for creating a peer-to-peer home network using common group label
US20020180582A1 (en) Electronic key device a system and a method of managing electronic key information
JP2004072766A (en) System for providing access control platform service to private network
CA2419793A1 (en) System, device, and method for managing communication services in an optical communication system
CA2576803A1 (en) System and method for managing end user approval for charging in a network environment
KR100953160B1 (en) A method for providing a content compatibility of mutual network devices having respectively different digital right management
CN102113405A (en) Method for personal network service configuration and system for personal network service configuration
CN101212343A (en) System and method for monitoring access terminals remotely
CN102177526A (en) Service providing system and service providing method
CN101939965A (en) Method and apparatuses for authorising provision of indirected content associated with a presentity of a presence service
CN102142067A (en) Digital family network-based digital rights management system
CN101443777A (en) Network system
CN114374740B (en) Industry service platform of interconnection of intelligence household electrical appliances
WO2002005569A1 (en) A method and a system for accessing services
CA2481428A1 (en) Method and system for distributing data
CN101998398A (en) System and method for accessing service provider in accessing place
JP3693922B2 (en) Internet load balancing relay connection method
KR101373234B1 (en) System and method for providing internet services using connecting device information
KR100372789B1 (en) A system offering a suitable Homepage utilizing an internet remotely
JP2004509492A (en) Method and apparatus for coordinating telecommunications services
TW573421B (en) Transmission protocol method of wireless equipment in area controlled by open remote network

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ CZ DE DE DK DK DM DZ EC EE EE ES FI FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP