U.S. patent application number 14/831973 was filed with the patent office on 2015-12-17 for method, system and apparatus for handling terminal capabilities.
The applicant listed for this patent is TELEFONAKTIEBOLAGET L M ERICSSON (PUBL). Invention is credited to Juan Antonio Herrero, David Mariblanca-Nieves, Felix Javier Visiedo.
Application Number | 20150365415 14/831973 |
Document ID | / |
Family ID | 29558392 |
Filed Date | 2015-12-17 |
United States Patent
Application |
20150365415 |
Kind Code |
A1 |
Mariblanca-Nieves; David ;
et al. |
December 17, 2015 |
METHOD, SYSTEM AND APPARATUS FOR HANDLING TERMINAL CAPABILITIES
Abstract
The present invention relates to telecommunication systems
providing multiple services which could require possible
adaptations based on the capabilities of the terminal used to
access those services. Master databases in the telecommunication
system take the responsibility to map between terminal and user
identifiers. Applications and services are thus able to query
terminal related capability information based on a user identity.
In accordance with the invention, a Terminal Capabilities database
(TC-DB) is introduced in order to establish a temporary
relationship between a user and a terminal operated by such user.
When a user attaches to the network, a terminal identifier is sent
to the network that forwards that identity to the TC-DB. For
retrieval of terminal capabilities the application servers send a
request message to the TC-DB by using the user identity as a
correlating key.
Inventors: |
Mariblanca-Nieves; David;
(Madrid, ES) ; Herrero; Juan Antonio; (Madrid,
ES) ; Visiedo; Felix Javier; (Madrid, ES) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
TELEFONAKTIEBOLAGET L M ERICSSON (PUBL) |
Stockholm |
|
SE |
|
|
Family ID: |
29558392 |
Appl. No.: |
14/831973 |
Filed: |
August 21, 2015 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
10453260 |
Jun 2, 2003 |
9154360 |
|
|
14831973 |
|
|
|
|
Current U.S.
Class: |
726/7 |
Current CPC
Class: |
H04L 67/303 20130101;
H04L 67/306 20130101; H04W 8/18 20130101; H04W 12/00512 20190101;
H04M 3/42229 20130101; H04L 63/0892 20130101; H04L 29/06 20130101;
H04L 67/42 20130101; H04W 12/08 20130101 |
International
Class: |
H04L 29/06 20060101
H04L029/06; H04W 12/08 20060101 H04W012/08 |
Foreign Application Data
Date |
Code |
Application Number |
Jun 12, 2002 |
EP |
02077319.8 |
Claims
1. A method for providing capabilities of a terminal equipment
operated by a user, the method carried out at a network entity
holding user profiles for users of a telecommunication network and
comprising: receiving a user identity for a user operating a
terminal equipment and a terminal equipment identifier identifying
the terminal equipment; associating the received user identity with
the received terminal equipment identifier and with a user profile
for the user; receiving a request from an application server for
providing the capabilities of the terminal equipment currently in
use by the user identified by the user identity; obtaining the
terminal equipment identifier associated with the user identity;
fetching from a terminal capabilities database a list of
capabilities stored for the terminal equipment identifier; and
sending the list of capabilities to the application server.
2. The method of claim 1, wherein the network entity holding the
user profiles is a Home Location Register (HLR) or a Home
Subscriber Server (HSS).
3. The method of claim 2, wherein receiving the user identity and
the terminal equipment identifier comprises receiving the user
identity and the terminal equipment identifier at the HSS from a
Serving Call Session Control Function (S-CSCF) of an IP Multimedia
Subsystem (IMS) network.
4. The method of claim 2, wherein receiving the user identity and
the terminal equipment identifier comprises receiving the user
identity and the terminal equipment identifier at the HLR or HSS
from a Serving GPRS Support Node (SGSN) of a GPRS network.
5. The method of claim 2, wherein receiving the user identity and
the terminal equipment identifier comprises receiving the user
identity and the terminal equipment identifier at the HLR from a
Mobile Switching Center (MSC) of a GSM network.
6. The method of claim 2, wherein receiving the user identity and
the terminal equipment identifier comprises receiving the user
identity and the terminal equipment identifier at the HLR or HSS
from a WLAN Support Node (WSN) of a WLAN network.
7. The method of claim 1, wherein the network entity holding the
user profiles is an Authentication Authorization and Accounting
(AAA) server.
8. The method of claim 7, wherein receiving the user identity and
the terminal equipment identifier comprises receiving the user
identity and the terminal equipment identifier at the AAA server
from a Network Access Server (NAS) of a network.
9. A network entity holding user profiles for users of a
telecommunication network, the network entity comprising: a
processor; and a memory containing instructions that, when executed
by the processor, cause the network entity to: receive a user
identity for a user operating a terminal equipment and a terminal
equipment identifier identifying the terminal equipment; store the
received user identity in association with the received terminal
equipment identifier and with a user profile for the user; receive
a request from an application server for providing the capabilities
of the terminal equipment currently in use by the user identified
by the user identity; obtain the terminal equipment identifier
associated with the user identity and fetch from a terminal
capabilities database a list of capabilities stored for the
terminal equipment identifier; and send the list of capabilities to
the application server.
10. The network entity of claim 9, wherein the network entity is a
Home Location Register (HLR) or Home Subscriber Server (HSS).
11. The network entity of claim 10, wherein the network entity is
configured to receive the user identity and the terminal equipment
identifier from a Serving Call Session Control Function (S-CSCF) of
an IP Multimedia Subsystem (IMS) network.
12. The network entity of claim 10, wherein the network entity is
configured to receive the user identity and the terminal equipment
identifier from a Serving GPRS Support Node (SGSN) of a GPRS
network.
13. The network entity of claim 10, wherein the network entity is
configured to receive the user identity and the terminal equipment
identifier from a Mobile Switching Center (MSC) of a GSM
network.
14. The network entity of claim 10, wherein the network entity is
configured to receive the user identity and the terminal equipment
identifier from a WLAN Support Node (WSN) of a WLAN network.
15. The network entity of claim 9, wherein the network entity is an
Authentication Authorization and Accounting (AAA) server.
16. The network entity of claim 15, wherein the network entity is
configured to receive the user identity and the terminal equipment
identifier from a Network Access Server (NAS) of a network.
Description
RELATED APPLICATIONS
[0001] This application is a continuation of U.S. application Ser.
No. 10/453,260, filed Jun. 2, 2003, which claims the benefit of the
filing date as provided in 35 U.S.C. 119 of European patent
application number 02077319.8 filed on Jun. 12, 2002, the
disclosure of which is incorporated herein by reference.
FIELD OF THE INVENTION
[0002] The present invention relates to telecommunication systems
providing multiple services that may require possible adaptations
depending on the capabilities of the terminal that an end-user is
making use of at a certain time.
BACKGROUND OF THE INVENTION
[0003] With the introduction of new network technologies, the
spreading of services and applications grows in number and
complexity. On the other hand, mobile devices supplied by different
manufacturers are expected to be more and more divergent in
performance, input and output capabilities, network connectivity,
processing power, and many other capabilities.
[0004] As a result of this device heterogeneity, client devices may
receive contents from different applications and services, that
they cannot store, that they cannot display, or that it takes too
long to deliver over the supported network technology.
[0005] Some applications and services need to know characteristics
of the terminal used to access the network in order to be able to
adapt contents and services to the capabilities of the user
terminal, thus improving end-user satisfaction and optimizing
network resources.
[0006] The standardization body for Wireless Application Protocol
(WAP), which is generally known as the WAP Forum, specifies a
mechanism incorporated in the WAP2.0 technical specification to
enable an end-to-end flow of a User Agent Profile (hereinafter
UAProf) between a WAP client, intermediate network points, and an
originating server. This User Agent Profile includes a set of
terminal capabilities information. Heretofore, this is a partial
solution to the problem of letting the applications and services
know about terminal capabilities, since it is only valid for WAP
applications and WAP terminals. However, UAProf proposes an
end-to-end negotiation of terminal capabilities between the
application server and the mobile terminal, thus increasing traffic
load and latency time whenever a new service is accessed.
[0007] In addition, the new Mobile Execution Environment
(hereinafter MExE) specification within the 3.sup.rd Generation
Partnership Project (3GPP) describes an application environment for
the latest generations of mobile devices. This MExE comprises a
variety of current technologies and incorporates both WAP and Java,
including also a framework which specifies, among others,
capabilities and contents negotiation.
[0008] Different technologies follow different mechanisms in order
to provide those applications running on top of such technologies
with terminal capabilities information intended for adapting
contents to particular terminals. That is the case of both WAP and
MExE above. The use of UAProf, for instance, is widely spread
around these technologies, and generally accepted as a convenient
solution to the problem of representing and exchanging terminal
capabilities information. Other suitable mechanism under WAP or
MExE is the so-called Composite Capability Preference Profiles
(CC/PP), which is an application of the eXtensible Mark-up Language
(XML) used to describe capabilities and preferences associated with
a user, and the agents used by a user to access the network. These
user agents include the hardware platform, system software and
applications used by the user. User agent capabilities and
references can be thought as meta data or properties, and
descriptions of the user agent hardware and software.
[0009] Despite the current trends of using solutions based on
UAProf or CC/PP, these technologies above implement such solutions
in a proprietary manner, making each solution incompatible with the
others. Moreover, these solutions propose that a dialog for
negotiating terminal capabilities is directly established between
the terminal and each application server, making it necessary to
the terminal the sending of such terminal capabilities to any new
application server that the user wants to make use of. This leads
to an unnecessary increment of traffic from terminal equipment to
application servers and consequently to an increase on the latency
time when accessing a service, what is more significant in a mobile
environment.
[0010] In addition to this, the terminal equipment has to implement
a new protocol for negotiation of terminal capabilities for every
different technology. In other words, a terminal equipment
implementing WAP and MExE has to implement UAProf and/or CC/PP for
WAP and for MExE.
[0011] The international application WO 99/41931 describes a
mechanism for an application server to deal with terminal
capabilities. This application proposes a peer-to-peer mechanism
between the terminal and the server to let the server know the
terminal identifier by using an Unstructured Supplementary Service
Data (USSD) message included in the Mobile Application Part (MAP)
protocol. The server assumes the responsibility to look for
terminal capabilities outside the mobile network and based on said
terminal identifier. Thus, the establishment of a relation between
the user identity and the terminal identifier is not solved.
Terminal capabilities information is related in no way with the
rest of the user profile, forcing the application server to use
different mechanisms to access user profile and terminal
capabilities.
[0012] Moreover, the European application EP 1 051 054 describes a
mechanism for allowing the use of a service, or for adapting the
service behaviour, depending on the terminal capabilities and the
specific location, by accessing to certain databases tracking the
mobile equipment and the geographic location. However, this
mechanism only provides a reference of the equipment model to the
application server, leaving to the application the responsibility
of obtaining the specific terminal capabilities. Moreover, the
invention does not solve the establishment of relations between the
user identity and the terminal equipment identifier.
SUMMARY OF THE INVENTION
[0013] None of the patent applications or standardization bodies
above provides for a telecommunication network based solution where
the terminal capabilities of a terminal equipment, which is
currently in use by a user, can be directly obtained by any
application server from said telecommunication network by simply
making use of the user identity.
[0014] It is therefore an object of the present invention the
provision of a telecommunication network based solution where the
terminal capabilities of a terminal equipment, which is currently
in use by a user, can be directly obtained from the
telecommunication network by any application server running on top
of said telecommunication network by simply making use of the user
identity.
[0015] It is a further object of the present invention to relate
the terminal capabilities of said terminal equipment with the user
profile data for the user currently making use of such terminal
equipment.
[0016] The objects above are accomplished by the present invention
with a method, a system and apparatus for providing capabilities of
a terminal equipment operated by a user in a telecommunication
system to an application server intended for offering services to
said user through such terminal equipment.
[0017] The method comprising the steps of: storing in the
telecommunication system capabilities of at least one of a
plurality of terminal equipment; establishing a temporary
relationship between the user operating a terminal equipment and
the capabilities of said terminal equipment; and providing
capabilities of the terminal equipment currently in use by the
given user, from the telecommunication system to an application
server.
[0018] In accordance with this method, the step of storing terminal
capabilities in the telecommunication system includes a step of
correlating capabilities of each terminal equipment with an
identifier of said terminal equipment.
[0019] Also according to this method, the establishment of a
temporary relationship between user and terminal equipment
comprises the steps of: sending from the terminal equipment toward
the telecommunication system an identifier of said terminal
equipment along with the user identity; receiving the user identity
and the current terminal equipment identifier at an entity holding
user profile data in the telecommunication system; and linking user
profile data, user identity and terminal equipment identifier.
[0020] An advantageous use of this method is the provision of
capabilities of a terminal operated by a given user at request from
an application server. Such mechanism comprises the steps of:
requesting from an application server to a telecommunication
network, by providing the user identity, the capabilities of the
terminal operated by the given user; obtaining at an entity that
holds user profile data in the telecommunication network the
terminal equipment identifier linked to said user identity;
fetching from storage the list of capabilities stored for such
terminal equipment identifier; and responding to the application
server from the telecommunication network with the list of
capabilities requested.
[0021] There is also proposed a telecommunication system in
accordance with the invention for providing capabilities of a
terminal equipment operated by a user to an application server
intended for offering services to said user through such terminal
equipment.
[0022] This telecommunication system comprising: means for storing
capabilities of at least one of a plurality of terminal equipment;
means for establishing a temporary relationship between the user
operating a terminal equipment and the capabilities of said
terminal equipment; and means for providing capabilities of a
terminal equipment currently in use by a given user to the
application server.
[0023] Therefore, the telecommunication system further includes:
means for receiving a user identity and a terminal equipment
identifier of the terminal currently operated by said user; and
means for linking user profile data, user identity and terminal
equipment identifier; both means preferably located at an entity
holding user profile data in the telecommunication system.
[0024] More specifically and directly addressed to objects of the
invention, the telecommunication system also comprises: means for
receiving a request from an application server for providing the
capabilities of a terminal equipment, the request including the
user identity of the user operating said terminal equipment; means
for obtaining the terminal equipment identifier linked to said user
identity; means for fetching from storage the list of capabilities
stored for such terminal equipment identifier; and means for
responding to the application server with the list of capabilities
requested for the indicated user identity.
[0025] The telecommunication network in accordance with the
invention may receive through an entry node the terminal equipment
identifier and the user identity sent from the terminal equipment.
This entry node likely interposed between the terminal and another
entity holding user profile data in the telecommunication network.
In this case, such telecommunication network entry node transfers
the received terminal equipment identifier and user identity to
said entity holding user profile data.
[0026] In particular, the network entity holding user profile data
may be a Home Location Register (HLR), or a Home Subscriber Server
(HSS) whereas the entry node may be a Mobile Switching Center
(MSC), or a Serving GPRS Support Node (SGSN). Under this scenario,
the terminal equipment identifier and the user identity may be both
included in an Update Location message. However, the entry node to
the telecommunication network may be a Call Status Control Function
(CSCF) as well, where the terminal equipment identifier and the
user identity may be both included in an Cx-put message.
[0027] Also in particular, the network entity holding user profile
data, and thus receiving the terminal equipment identifier and the
user identity, may be an Authentication Authorization and
Accounting (AAA) server. Such network entity may be accessed at the
telecommunication network via a Network Access Server (NAS) or a
WLAN Support Node (WSN) acting as network entry node. Under this
scenario, the terminal equipment identifier and the user identity
are both included in a message intended for Access Request from the
entry node to the entity holding user profile data.
[0028] In accordance with the invention, user profile data, user
identity and terminal equipment identifier are linked on a per user
basis in a Home Location Register (HLR), or in a Home Subscriber
Server (HSS), or in an Authentication Authorization and Accounting
(AAA) server.
[0029] In addition, the invention proposes a Terminal Capabilities
Database where user identities and terminal equipment identifiers
are linked on a per user basis. Then, terminal capabilities are
stored in a storage accessible to said Terminal Capabilities
Database and correlated therein with a terminal equipment
identifier.
[0030] Detailed preferred embodiments are further described wherein
an application server requests to a Home Location Register (HLR),
or a Home Subscriber Server (HSS), or an Authentication
Authorization and Accounting (AAA) server the terminal capabilities
of a terminal equipment by providing the user identity of the user
operating said terminal equipment. Then, a list of terminal
capabilities associated to said terminal equipment identifier is
fetched from a storage accessible to the Terminal Capabilities
Database.
BRIEF DESCRIPTION OF DRAWINGS
[0031] The features, objects and advantages of the invention will
become apparent by reading this description in conjunction with the
accompanying drawings, in which:
[0032] FIG. 1 basically represents how an application server can
obtain from a telecommunication network information about the
terminal capabilities of a terminal equipment currently in use by a
user where the telecommunication network is a mobile
network-Circuit, Packet, or IP Multimedia- or a wireless
network.
[0033] FIG. 2 basically represents how an application server can
obtain from a telecommunication network information about the
terminal capabilities of a terminal equipment currently in use by a
user accessing to services through an Internet Service Provider
(ISP).
[0034] FIG. 3 shows a simplified view of the signalling flow for
identifying the terminal capabilities of a terminal equipment
currently in use by a user accessing the telecommunication network
in FIG. 1 and the signalling flow for an application server to
obtain said terminal capabilities, wherein the telecommunication
network is a GSM, or GPRS network.
[0035] FIG. 4 shows a simplified view of the signalling flow for
identifying the terminal capabilities of a terminal equipment
currently in use by a user accessing via an Internet Service
Provider as shown in FIG. 2, and the signalling flow for an
application server to obtain said terminal capabilities.
[0036] FIG. 5 shows a simplified view of the signalling flow for
identifying the terminal capabilities of a terminal equipment
currently in use by a user accessing the telecommunication network
in FIG. 1 and the signalling flow for an application server to
obtain said terminal capabilities, wherein the telecommunication
network is an IP Multimedia network following 3GPP standards.
[0037] FIG. 6 shows a simplified view of the signalling flow for
identifying the terminal capabilities of a terminal equipment
currently in use by a user accessing an Internet Service Provider
through a Wireless Local Area Network (WLAN), and the signalling
flow for an application server to obtain said terminal
capabilities.
DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS
[0038] The following describes currently preferred embodiments of
means, methods and system for providing terminal capabilities of a
terminal equipment, which is currently in use by a user, to any
application server by simply making use of the user identity. In
accordance with an aspect of the present invention, the terminal
capabilities of said terminal equipment are related with the user
profile data for said user currently making use of such terminal
equipment.
[0039] Thus, this invention gives to any application server the
possibility of getting the capabilities of the terminal being used
by a certain user at any time. The application server thus performs
this retrieval of capabilities in order to adapt the contents to be
served to the terminal in the most suitable way. For example, if an
streaming server is about sending an MPEG video to a terminal, it
may be worthwhile to know if the terminal is able to display such
kind of files.
[0040] Therefore, a proposed solution is depicted in FIGS. 1 and 2
for a user accessing an application server (20) through a
telecommunication network (1) via a generic access network (2) or
via an Internet Service Provider (3) respectively. There is
provided in accordance with the invention a Terminal Capabilities
Database (10) (hereinafter referred to as TC-DB) in a
telecommunication network (1) in order to store a temporary
relationship between the user and the terminal equipment (30, 31)
that he or she is making use of.
[0041] Also, this TC-DB is in charge of storing the terminal
capabilities descriptions in a predefined and well known format, by
using CC/PP for example, though this latter functionality can be
achieved with an external storage in addition to the TC-DB. Such
optional storage is shown in FIGS. 1 and 2 as a Capability
Repository (11).
[0042] When a user provided with a terminal equipment (30) attaches
(S-1x) to a telecommunication network (1), as depicted in FIG. 1,
the terminal identifier is sent to the network entry point (12)
which forwards (S-2x) the terminal identifier to a
telecommunication network database (13) where subscriber profiles
reside. In particular, in a traditional 2.sup.nd generation mobile
system, said telecommunication network database is a Home Location
Register (HLR) whereas in 3.sup.rd generation mobile systems with
IP Multimedia the telecommunication network database is a Home
Subscriber Server (HSS). For the purpose of the present invention
they are individually referred to as HLR/HSS irrespective of being
given IP Multimedia or not.
[0043] This forwarding can be performed, for example, just by
upgrading the existing Location Update message, which is addressed
to both HLR and HSS, in order to contain such terminal
identifier.
[0044] In accordance with another aspect of the present invention,
the TC-DB (10) functionality may be collocated or included in a
Home Location Register (HLR) or in Home Subscriber Server (HSS). An
upgraded Location Update message comprising a user identity, as
before, and a new data indicating the terminal identifier, is thus
received at an HLR/HSS. The aforementioned temporary relationship
between the user and the terminal equipment, the latter being
identified by said terminal identifier, may be established at said
HLR/HSS, wherein this relationship includes the whole user profile,
or may be established as well at the TC-DB wherein just the
indicated user identity and terminal identifier are stored.
[0045] In a first embodiment of the present invention, the HLR/HSS
maintains the temporary relationship between the user identity and
the terminal identifier whereas the TC-DB alone or in combination
with the Capability Repository (11) merely comprises lists of
capabilities on a per terminal identifier basis. In a second
embodiment of the present invention, the TC-DB (10) is the one
maintaining such relationship, whereas the Capability Repository
(11) comprises the lists of capabilities on a per terminal
identifier basis. Also under this second embodiment, the HLR/HSS is
the only one maintaining the user profiles so that in case the
TC-DB is directly queried from an application server about
capabilities of the terminal a given user makes use of, such query
done with a user identity other than the one linked to the terminal
identifier under TC-DB premises, the TC-DB can always query the
HLR/HSS about another user identity known to the TC-DB.
[0046] Notwithstanding this, the mechanism explained throughout
this description, in terms of system, means and method, considers
separate entities for the sake of clarity in respect of the
different functions and means residing in said HLR/HSS and
TC-DB.
[0047] The HLR/HSS then, and likely in cooperation with the TC-DB,
links the terminal identifier to the relevant user identity of the
user making use of such terminal equipment at that time. As
referred above such link may as well be performed at the TC-DB
without substantially modifying the scope of the invention.
However, given that a user might make use of different user
identities under different scenarios, the skilled person would find
more advantageous that a relation between the terminal identifier
and the user profile data resides at the HLR/HSS.
[0048] From now on and whilst the user makes use of such terminal
equipment (30), the HLR/HSS (13), in co-operation with the TC-DB
(10), is ready to provide any application server (20) with the
terminal capabilities of a given user. Thus, the application server
does not need to have any knowledge about terminal identities and
their formats.
[0049] Consequently, when an application server (20) needs to
perform a retrieval (S-3x) of terminal capabilities for a given
user, a request message is sent (S-3x, S-4x) to the TC-DB, likely
through the HLR/HSS (13) in charge of said user in the
telecommunication network (1). The TC-DB searches in a list what is
the terminal linked to said user at that time. Once the terminal
identifier is found, it is used to get a list of the capabilities
associated to that terminal. This list of capabilities can be
found, for example, as a file in CC/PP format and stored either
directly in the TC-DB, or alternatively in an external storage as
the Capability Repository (11).
[0050] Generic signalling flows are shown in FIGS. 3, and 5 where
the telecommunication network is a mobile network. The generic flow
in FIG. 3 is applicable to Circuit and Packet domains, whereas FIG.
5 is rather oriented to 3.sup.rd generation (3G) mobile systems
provided with IP Mobility (IP-M). Particular explanations are given
following this on a per domain basis, when relevant for a skilled
person to understand aspects of the invention.
[0051] As shown in FIGS. 3, and 5, the mobile terminal (30), namely
a Mobile Station (MS), provides (S-1x) its terminal identifier to
the mobile network entry point. Said network entry point is a
Mobile Switching Center (MSC) in a Circuit domain, or a Serving
GPRS Support Node (SGSN) in a Packet domain, or a Call Status
Control Function (CSCF) in a 3G mobile system with IP-M.
[0052] In particular and as shown in FIG. 3, the "Identity Request"
operation may be used by an MSC (12) or an SGSN (12) to ask the
terminal (30) for applicable terminal identifiers like, for
example, the International Mobile Equipment Identity (IMEI). The
MSC/SGSN (12) can initiate the identification procedure at any time
by transferring an Identity Request message (S-11) to the mobile
station (30) indicating the requested identifier within the
"identity type" field. The mobile station sends back (S-12) to the
network entry node (12) the terminal identity code, like the IMEI
code for example, encapsulated in an "Identity Response" message.
Such identity code is then stored in the MSC/SGSN (12) which
forwards (S-21) it to the HLR/HSS. In accordance with an aspect of
the present invention, this terminal identifier can be encapsulated
in the Location Update message amended to this end.
[0053] A similar behaviour is proposed for IP Multimedia access in
3GPP as shown in FIG. 5, wherein the mobile station (30) sends
(S-13) the terminal identity code at registration time, namely an
IMEI or similar, by using a Register message towards a Serving CSCF
(S-CSCF) where the received code is stored. The S-CSCF then
forwards (S-21) this terminal identity code to the HLR/HSS through
the 3GPP-standardized Cx Interface. Therefore, either a new
signalling message is provided for, or an upgraded Cx-Put message
is used.
[0054] The complete process has been somewhat simplified in FIG. 5
for the sake of clarity as anyone skilled in the art may
appreciate. In fact, a negotiation and selection of said S-CSCF has
been carried out from an Interrogating CSCF (I-CSCF) that forwards
then the Register message to the selected S-CSCF.
[0055] From now on and as illustrated in FIGS. 3 and 5, an
application server (20) can request (S-31), at any time, the
terminal capabilities of the terminal currently in use by a given
user by sending the user identity to the HLR/HSS. The HLR/HSS,
after looking up the terminal identifier associated to said user,
retrieves (S-41, S-42) the terminal capabilities from the TD-DB
(10) and returns (S-32) the list of capabilities corresponding to
the terminal back to the requester application server (20). The
protocol used between HLR/HSS and the TC-DB could be Diameter,
Lightweight Directory Access Protocol (LDAP), XML including Simple
Object Access Protocol (SOAP), or whatever protocol allowing the
transmission of terminal capabilities descriptions.
[0056] The solution can be applied as well to provide a centralised
terminal capabilities database for those users accessing to
services through an Internet Service Provider (ISP) as FIG. 2
illustrates. An ISP can check, bill and attend the user based on
the username. A mechanism according to the invention, in terms of
system, method and apparatus, thus allows the ISP to receive
information about the capabilities of the terminal equipment used
by a user by including additional information in existing messages
used for Authentication, Authorisation and/or Accounting
(hereinafter AAA) toward a corresponding server.
[0057] When a user provided with a terminal equipment (31) requests
access (S-6x) to an ISP via a telecommunication network (1), as
depicted in FIG. 2, the terminal identifier is sent to the network
entry point (14) which forwards (S-7x) the terminal identifier to a
telecommunication network database (15) where subscriber profiles
reside. In particular, the network entry point (14) is a Network
Access Server (NAS) for generic ISP users and the telecommunication
network database is an Authentication, Authorization and Accounting
(AAA) server, whereas for accessing via WLAN the network entry
point (14) is a WLAN Support Node (WSN) and the telecommunication
network database is a Home Subscriber Server (HSS).
[0058] Thus, as illustrated in FIG. 4, the terminal (31) makes use
of existing access request operations to transmit (S-61, S-62) the
terminal identification and/or model to a Network Access Server
(NAS) (14). Then, the NAS transmits (S-71, S-72) the terminal
identifier to the AAA-server (15), for instance by using extensions
to the RADIUS and Diameter protocols. This new information may be
included in whatever messages transmitted between the NAS (14) and
the AAA-server (15). For example and as shown in FIG. 4, the
terminal identifier has been included in the Access-Request
message.
[0059] The AAA-server (15) under this embodiment behaves in a
similar way as the HLR/HSS does in the preceding embodiments above.
Such AAA-server (15) manages, in accordance with an aspect of the
invention, the temporary relationship between the user profile and
the terminal identifier of the terminal equipment currently in use
by said user, whereas the TC-DB comprises the lists of terminal
capabilities on per terminal identifier basis. Once more, in
accordance with another embodiment of the invention, the TC-DB can
be configured to comprise the relationship between particular user
identity and terminal equipment identifier and thus receiving the
related queries, whereas a co-operating Capability Repository (11)
might be in charge of the lists of terminal capabilities on per
terminal identifier basis.
[0060] In a currently preferred embodiment, an application server
(20) may, at any time, request (S-81) the terminal capabilities of
the terminal currently in use by a given user by sending the user
identity to the AAA-server (15). The AAA-server, after looking up
the terminal identifier associated to said user, retrieves (S-41,
S-42) the terminal capabilities from the TD-DB (10) and returns
(S-82) the list of capabilities corresponding to the terminal back
to the requester application server (20). The protocol used between
AAA-server (15) and the TC-DB (10) could be also Diameter, LDAP,
XML/SOAP or whatever protocol allowing to transmit terminal
capabilities descriptions.
[0061] The solution is directly applicable to provide a centralised
terminal database for the users acceding ISP through WLAN as FIG. 6
illustrates. The signalling flow under this scenario is similar to
the one in FIG. 5 wherein a WLAN Support Node (WSN) is the network
entry point (14), and a Home Subscriber Server (HSS) is the network
database in charge of the temporary relationship between user
profiles and terminal identifier, both WSN and HSS respectively
performing similar procedures as the NAS and AAA in FIG. 5.
[0062] In a further embodiment of the invention not depicted in any
drawing it is noticeable its use for a direct access from the
terminal equipment without intermediate actuation of a network
entry point (12, 14). In other words, an exemplary embodiment may
be offered where a mobile terminal equipment takes the initiative
of sending the terminal identifier to an HLR/HSS for example by
means of an Unstructured Supplementary Service Data (USSD) message.
Afterwards, and at any time, any application server may request the
HLR/HSS about terminal capabilities associated to the given user
identity, said terminal capabilities fetched from the TC-DB as in
any of preceding preferred embodiments.
[0063] The invention is described above in respect of several
embodiments in an illustrative and non-restrictive manner. The
scope of the invention is determined by the claims, and any
modification of the embodiments that fall within the scope of these
claims is intended to be included therein.
* * * * *