Arrangement and a method relating to session management in a portal structure

• US 6,941,307 B2
• Filed: 01/24/2002
• Issued: 09/06/2005
• Est. Priority Date: 01/24/2001
• Status: Expired due to Fees

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Akerfeldt, Jan, Papanikolaou, Thomas
• Primary Examiner(s): MOFIZ, APU M
• Application Number:
  US10/466,664
• Publication Number:
  US 20040049589A1
• Time in Patent Office: 1,321 Days
• Field of Search: 707/9, 707/10, 707/104.1, 370/384, 370/404, 455/414.1, 455/418, 455/466, 705/1, 705/14, 705/39, 705/80, 709/203, 709/219, 709/229, 709/246, 713/201, 717/103
• US Class Current: 715/742
• CPC Class Codes: G06F 16/954 Navigation, e.g. using categorised browsing
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/2871 Implementation details of single intermediate entities
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 67/567 Integrating service provisioning from a plurality of service providers
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

The present invention relates to a portal structure providing end user stations (5) with access to services/applications (26), comprising a portal core (1) and a number of services/applications (26). The portal core comprises a presentation arrangement, portal session managing means (13) generating session related information, e.g. session identifications and portal storing means (51) for storing session related information. At least some of the services/applications (26) are external with external session identifications. Session unifying means (50) are provided for mapping between portal session identifications and external session identifications. For communication between the portal core (1) and external services/applications (26), the external identification is used, whereas, in communication between an end user station (5) and the portal core (1), only the portal session identification is used.

Claims

1. A portal node within a computer-implemented communication network providing an end user station with access to services and applications wherein said, services and applications include internal services and applications and a plurality of external services and applications, comprising:

a presentation arrangement for communicating data with said end user station;

a portal session managing means for generating session related information, including portal session identification, the portal session managing means operating according to the servlet session API or the session EJB;

s specifications defining basic session management operations;

a portal storing means for storing session related information;

an external session managing means for generating external session identification; and

a session unifying means for mapping between said portal session identifications and said external session identifications wherein said external session identification is used for communicating between said portal node and said external services and applications and only said portal session identification is used for communicating between said portal node and said end user station.

2. A portal node according to claim 1, wherein the services and applications utilizing a generic markup language.

3. A portal node according to claim 2, wherein the generic markup language is XML.

4. A portal node according to claim 2, wherein the presentation arrangement comprises rendering means for translating service and application data in the generic markup language into a different markup language used by an end user station.

5. A portal node according to claim 2, wherein said data representing services and applications in the generic markup language are defined in a Document Type Definition (DTD) language with an URL-attribute.

6. A portal node according to claim 1, wherein said portal storing means stores all proprietary information associated with an external service and application and identified with a particular external session identification for a defined time period.

7. A portal structure according to claim 1, wherein said external session managing means comprises another portal.

8. A portal structure according to claim 1, wherein the portal session managing means stores information relating to end user initiated actions, including end user entering the portal, end user authentication, and end user access of a service/application into the portal storing means.

9. A portal node according to claim 1, wherein said portal session managing means assigning a portal session identification in response to receiving an end user request for service;

and

in response to determination that the requested service is internal to said portal node, using said assigned portal session identification;

otherwise, said external session managing means assigning an external session identification for said external services and applications.

10. A portal node according to claim 9, wherein said session unifying means correlates said portal session identification with said external session identification allowing data provided by said external services and applications to be forwarded to said end user station.

11. A portal core within a computer-implemented communicating system for communicating data between an end user terminal and service providers wherein said service providers include internal service providers associated with said communication system and external service providers communicably coupled to said communicating system, comprising:

a presentation arrangement;

a portal session managing means generating portal session related information, including portal session identification, the portal session managing means operating according to the servlet session API or the session EJB;

s specifications defining basic session management operations;

a portal storing means for storing portal session related information;

an external session managing means for generating external session identification for communicating with said external service providers;

a session unifying means for unifying management of portal sessions and external sessions by allowing said end user terminal to communicate with said internal service providers using said portal session identification and allowing said portal core to communicate with said external service providers using said external session identification.

12. A portal core of claim 11, wherein said portal storing means stores data mapping a particular portal session identification with a particular external session identification for a particular communication session between said end user terminal and a particular service provider.

13. An arrangement according to claim 11, wherein that the presentation arrangement comprises rendering means for translating service data in a generic markup language into other markup languages depending on the type of a requesting end user terminal for rendering service data output to end user terminals having requested access to a service into a markup language understandable by the end user station.

14. An arrangement according to claim 13, wherein the generic markup language is XML.

15. An arrangement according to claim 11, wherein that external session identification is provided in a meta-information tag introduced into the external service data and in that the meta-information data is stored in the corresponding portal session in the portal storing means storing portal session-information, and in that the portal session identification is added to the external application data as a parameter in communication with the end user terminal, replacing the external session identification.

16. An arrangement according to claim 15, wherein that for a subsequent request to the portal for the same external service by an end user terminal during a session, the metainformation is included into the request when forwarded from the portal core to the external service provider.

17. A computer-implemented method of session management in a portal structure including a portal core further including a presentation arrangement, portal session managing means handling session related information and portal storing means for storing session related information, comprising the steps of:

creating a portal session with a portal session identification when an end user requests access to a service/application, unless a portal session already exists, the portal session managing means operating according to the servlet session API or the session EJB;

s specifications defining basic session management operations;

forwarding the request to the requested external service/application if the requested service/application is externally session managed;

creating in the external session managing means an external service/application proprietary session identification for the requesting end user unless a session already exists;

generating service/application data in the service/application;

introducing information about the external session identification into the service/application data;

returning service/application data including external session identification to the portal;

mapping the external session identification to the portal session identification;

storing the external session identification in the corresponding portal session means;

sending the service/application data to the requesting end user using only the portal session identification.

18. A method according to claim 17, wherein the method comprises the steps of:

in the portal;

looking up the portal session in the storing means at a subsequent request by an end user for an external service/application during the session;

establishing if the portal session related information contains an external session identification, if yes;

forwarding the request including the external session identification to the requested external service/application;

in the external session managing means or in the external service/application;

looking up the external service/application session;

generating service/application data;

adding the external session identification to the service/application data;

returning the service/application data with the external session identification to the portal session managing means;

in the portal;

replacing the external session identification by the corresponding portal session identification;

sending the service/application data to the end user station using the portal session identification only.

19. A method according to claim 17, wherein the external service/application utilizing a generic markup language, e. g. XML.

20. A method according to claim 19, wherein the step of adding external session identification comprises generation of and introduction of a metainformation tag containing at least external session identification to the service/application data.