A method and apparatus for registering a user as a subscriber in a communication network. The method includes transmitting a registration message which defines an identity of the user to the communication network. The method also includes providing in the registration message a header field for defining at least one other identity of the user as a subscriber. The method also includes performing a one-by-one registration based on an identity information stored at a terminal device, whereby the identity information defines at least one other identity of the user as a subscriber. Thus, the user or subscriber can register some or all of his public identities at once with one registration procedure, allowing the user to utilize his identities by grouping public identities under user profiles or under private identities, while preventing unwanted calls.
|
1. A method, comprising:
generating a session initiation protocol registration message defining a plurality of user identities of a user, the session initiation protocol registration message transmitted to an internet protocol multimedia service network, the session initiation protocol registration message comprising:
a To message header used to define a first user identity,
a From message header used to define a second user identity, and
a third dedicated header field used to define at least a third user identity, wherein the first user identity, the second user identity, and at least the third user identity corresponding correspond to the plurality of user identities; and
transmitting the session initiation protocol registration message.
0. 38. A method, comprising:
receiving a session initiation protocol registration message defining a plurality of user identities of a user, the session initiation protocol registration message transmitted to an internet protocol multimedia service network, the session initiation protocol registration message comprising:
a To message header used to define a first user identity,
a From message header used to define a second user identity, and
a third dedicated header field used to define at least a third user identity, wherein the first user identity, the second user identity, and at least the third user identity correspond to the plurality of user identities; and
transmitting a response to the received session initiation protocol registration message.
29. An apparatus comprising:
a transmitter generator configured to transmit generate a session initiation protocol registration message comprising a plurality of user identities of a user, the session initiation protocol registration message transmitted to an internet protocol multimedia service, the session initiation protocol registration message comprising:
a To message header used to define a first user identity,
a From message header used to define a second user identity, and
a third dedicated header field used to define a third user identity, wherein the first user identity, the second user identity, and at least the third user identity corresponding correspond to the plurality of user identities; and
a detector configured to detect said at least one of the plurality of user identities; and
a registration device configured to register at least the third user identity, wherein at least one of the transmitter, the detector, and the registration service are implemented on a processor of a user equipment a transmitter configured to transmit the session initiation protocol registration message.
0. 39. An apparatus comprising:
a receiver configured to receive a session initiation protocol registration message comprising a plurality of user identities of a user, the session initiation protocol registration message transmitted to an internet protocol multimedia service, the session initiation protocol registration message comprising:
a To message header used to define a first user identity,
a From message header used to define a second user identity, and
a third dedicated header field used to define at least a third user identity, wherein the first user identity, the second user identity, and at least the third user identity correspond to the plurality of user identities; and
a transmitter configured to transmit a response to the received session initiation protocol registration message.
27. A system, comprising:
a terminal device configured to transmit a session initiation protocol registration message comprising a plurality of user identities of a user, the session initiation protocol registration message transmitted to an internet protocol multimedia service, the session initiation protocol registration message comprising:
a To message header used to define a first user identity,
a From message header used to define a second user identity, and
a third dedicated header field used to define at least a third user identity, wherein the first user identity, the second user identity, and at least the third user identity corresponding correspond to the plurality of user identities; and
a network element configured to detect at least the third user identity, and further configured to register at least the third user identity.
23. A method, comprising:
transmitting a session initiation protocol registration message defining a plurality of user identities of a user, the session initiation protocol registration message transmitted to an internet protocol multimedia service, the session initiation protocol registration message comprising:
a To message header used to define a first user identity,
a From message header used to define a second user identity, and
a third dedicated header field used to define at least a third user identity, wherein the first user identity, the second user identity, and at least the third user identity corresponding correspond to the plurality of user identities; and
registering at least one of the first user identity, the second user identity, and at least the third user identity of said user, stored in a subscriber database, by a default setting.
37. An apparatus comprising:
means for transmitting a session initiation protocol registration message comprising a plurality of user identities of a user, the session initiation protocol registration message transmitted to an internet protocol multimedia service, the session initiation protocol registration message comprising:
a To message header used to define a first user identity,
a From message header used to define a second user identity, and
a third dedicated header field used to define a third user identity, wherein the first user identity, the second user identity, and at least the third user identity corresponding correspond to the plurality of user identities;
means for detecting said at least one of the plurality of user identities; and
means for registering said at least one of the plurality of user identities, wherein at least one of the means for transmitting, the means for detecting, and the means for registering are implemented on a processor.
2. The method according to
returning a list of registered identities of said subscriber user from said communication internet protocol multimedia service network in a corresponding header field of a response message.
3. The method according to
4. The method according to
adding a direction information to said session initiation protocol registration message for conveying at least one registration direction for which at least the third user identity is valid.
5. The method according to
6. The method according to
7. The method according to
8. The method according to
9. The method according to
10. The method according to
11. The method according to
dividing said subscriber database into a plurality of subdatabases,
wherein at least one of said plurality of subdatabases can be edited by said subscriber, and at least one of said plurality of subdatabases can be edited by an operator only.
12. The method according to
13. The method according to
editing by said subscriber a temporal copy of a subscriber's entry in said subscriber database;
checking a validity and a correctness of said editing; and replacing said subscriber's entry when no errors are found in said temporal copy of subscriber's entry.
14. The method according to
15. The method according to
defining an identity profile from the first user identity, the second user identity, and at least the third user identity corresponding to the plurality of user identities, the identity profile comprising a predetermined set of identities.
16. The method according to
storing a list of identity profiles in a subscriber identity module.
17. The method according to
attaching attributes for modifying said list of identity profiles to each said identity profile.
18. The method according to
19. The method according to
20. The method according to
registering an unregistered one of the first user identity, the second user identity, and at least the third user identity corresponding to the plurality of user identities by a network element when a call is initiated by said user using said unregistered identity.
21. The method according to
22. The method according to
storing a limiting information in a subscriber database, said limiting information comprising limiting factors for limiting registration choices of said user.
24. The method according to
25. The method according to
26. The method according to
issuing a warning about calls to non-registered public identities to said user.
28. The system according to
30. The apparatus of
31. The apparatus of
32. The apparatus of
33. The apparatus of
34. The apparatus of
35. The apparatus of
36. The apparatus of
|
|||||||||||||||||||||||||||||
This application is a reissue application of U.S. patent application Ser. No. 10/473,795, filed on Oct. 2, 2003, entitled “METHOD AND APPARATUS FOR REGISTRATION OF A USER AS A SUBSCRIBER IN A COMMUNICATION NETWORK,” (issued as U.S. Pat. No. 7,792,974), which is a U.S. National Stage entry claiming benefit under 35 U.S.C. §371 of PCT/EP01/08161, filed Jul. 13, 2001. The contents of the aforementioned applications are hereby incorporated by reference in their entirety.
The present invention relates to a method, terminal device and system for registering a user in a communication network, especially in a 3GPP (third generation partnership project) Internet Protocol (IP) Multimedia subsystem (IMS). In particular, this invention is directed to different ways to deal with the problem of registering multiple identities, which can be seen in the cases “one private identity”, “one private identity but several user profiles”, and “several private identities”.
A user equipment (UE) accessing IM core network (CN) subsystem services requires an IP address that is part of an IP addressing domain of a visited network IM CN subsystem. This is established using an appropriate PDP (Packet Data Protocol) context. For routing efficiency this context should be connected through a GGSN (General Packet Radio Services Gateway Support Node) in the visited network.
Every IM CN subsystem subscriber has a private identity assigned by the home network operator and used e.g. for registration, authorization, administration, and accounting purposes. This private identity is a unique global identity valid for the duration of the user's subscription with the home network and takes the form of a Network Access Identifier (NAI) as defined in the IETF (Internet Engineering Task Force) specification RFC 2486. The NAI for the private identity may contain the IMSI (International Mobile Subscriber Identity). The private identity is securely stored in the USIM (Universal Mobile Telecommunications System Subscriber Identity Module) and cannot be modified by the UE.
Furthermore, every IM CN subsystem subscriber has one or more public identities assigned by the home network operator and used by any user for requesting communications to other users. For example, these public identities may be indicated on a business card. Both telecom numbering and Internet naming schemes can be used to address users depending on the public identities allocated to the users. The public identities may take the form of a SIP URL (Session Initiation Protocol Uniform Resource Locator), as defined in the IETF specifications RFC 2543 and RFC 2396, or an E.164 number. At least one public identity is stored in the USIM.
In SIP as described e.g. in the IETF specification RFC 2543, each public identity is registered separately, as indicated in
The subscriber may have several profiles that he would like to use separately e.g. business profile, private profile, chess club member profile etc. In the case “one private identity but several user profiles”, as shown in
The subscriber registers with one of his public identities and lists all the other public identities that he wants to be registered with at the same time. When a subscriber has registered with one of his identities, he can use his other identities for outgoing calls without any further registration but he doesn't receive any calls with those identities. The subscriber can explicitly change an existing registration or make a new registration with whichever of his identities for incoming calls only, for outgoing calls only, or for both incoming and outgoing calls. He can make one or several registrations at a time.
Furthermore, the subscriber can register with one of his public identities specially indicating that all public identities should be registered, and all his public identities will be registered. As an option the subscriber can register without the mentioned indication, and all his public identities are registered by a default setting.
The subscriber may have several public identities. Normally, he registers with one public identity. If he wants to use another of his public identities e.g. to make a business call in the evening from home, he has to register with that identity before he can use it. It would be desirable to be able to register with all or with some of the public identities all together at the same time. After the registration, that public identity is valid also for incoming calls e.g. people may call home in business matters.
It is an object of the present invention to provide an improved registration mechanism for registering multiple identities of a subscriber in a communication network.
This object is achieved by a method according to any of claims 1, 5, 25 and 27, by a terminal device according to claim 31, and by a system according to claim 32.
Accordingly, three alternative ways how to clarify the administration and registration of public identities are presented by the invention.
Firstly, new optional header field is used in the registration message. As an alternative, the payload of the registration message can be used.
Secondly, the terminal may perform a one-by-one registration to all items stored e.g. in a list on the SIM or the USIM and/or memory of the terminal.
Thirdly, a default registration of at least one other identity of the user, stored in a subscriber database, may be performed based on a default setting. The at least one other identity may be comprised in a default set defined by the user. The default set may be defined via a web page or a terminal menu.
Additionally, a new parameter, header, flag or the like can be added to the registration message to convey the direction (incoming calls/outgoing calls/both) of the registration. To make several registrations at the same time, several fields or a separate header can be used. The registration message might also provide a mechanism to tell that all valid identities should be activated at the same time.
Private identities, user profiles and public identities may all be stored in a subscriber database, e.g. HSS. The client identity may be used as a link that binds together the private identities of one client.
The invention provides the advantage that only one registration is necessary in order to be able to use some or all public identities. This saves resources such as bandwidth and capacity, which is especially important on the air interface. Furthermore, only one registration is necessary in order to be able to use all identities for outgoing calls. The subscriber can explicitly administrate all his identities and decide whether he wants to allow incoming calls, outgoing calls or both. Only those identities are registered that are really needed. Identities may be given by different operators and/or organizations.
As a further advantage, the solution is (IETF) SIP compliant (extension to standard SIP) and backwards compatible.
Moreover, there may be limits in the Home Subscriber Server (HSS) within which the subscriber can allow and deny incoming and outgoing calls of his identities. Thereby, unwanted incoming calls can be prevented. For example the subscriber is allowed to receive incoming business calls always but not make any outgoing business calls in the evening or between certain time period (e.g. vacation).
Additionally, the invention provides a solution, which is easy to use because outgoing calls are allowed with whichever identity as default, if not denied in the master database in the HSS. Moreover, a special usage is possible with parameters.
In the case of “one private identity but several user profiles” a subscriber can administrate a couple of profiles instead of many individual E.164 and SIP URL.
In the case of “several private identities” a subscriber can administrate a couple of private identities instead of many individual E.164 and SIP URLs.
In addition, the subscriber is able to explicitly administrate all his public identities in a one by one registration according to his preferences. Regarding structural implementation thereof, the terminal device or user equipment used for registering the user in the communication network comprises a memory, e.g. the USIM, SIM or any other memory, for storing the identity information of the user, which defines an identity and at least one other identity of the user. Based on this identity information, a signaling function or unit performs or initiates a one-by-one registration according to the user's instructions.
In the following, the present invention will be described in greater detail on the basis of preferred embodiments with reference to the drawing figures, in which:
The preferred embodiments of the invention will now be described on the basis of an SIP registration procedure in a visited network, as indicated in
The architecture is based on the principle that the service control for home subscribed services for a roaming subscriber is in the home network, e.g. the Serving Call State Control Function (S-CSCF) is located in the home network. When the subscriber roams to a visited network, the S-CSCF is located in the home network and the visited network supports a Proxy-CSCF (P-CSCF). The P-CSCF enables the session control to be passed to the home network based S-CSCF which provides the service control. Furthermore, one or more Interrogating-CSCFs (I-CSCFs) may be included in the signalling path to shield the internal structure of the concerned network from other networks.
In a first preferred embodiment, public identities are registered according to a specified user equipment indication. The user equipment, i.e. the user's terminal, sends one of the valid public identities in a “To” header field of the SIP REGISTER message and other identities in a new header field called “Other-Identities”. The S-CSCF registers the public identities, contained in the “To” header field and the “Other-Identities” header field and returns the list of registered public identities in the “Other-Identities” header field. The P-CSCF stores the registered public identities for later use.
In step 1 of
REGISTER
home_a.com SIP/2.0
Via:
SIP/2.0/UDP 12.34.56::EF:5060
From:
Private Identity <sip:245454555@home_a.com>
To:
Mary Blue <sip:Mary.Blue@home_a.com>
Call-Id:
12345@ue_a.home_a.com
Cseq:
1 REGISTER
Contact:
User_A <sip:ue_a@12.34.56::EF:5060>
Other-Identities:
tel: +358-40-7618290, sip:Mary@chessclub-hel.org
In step 2 of
REGISTER
home_a.com SIP/2.0
Via:
SIP/2.0/UDP p_cscf.visited_a.com
Via:
SIP/2.0/UDP 12.34.56::EF:5060
From:
Private Identity <sip:245454555@home_a.com>
To:
Mary Blue <sip:Mary.Blue@home_a.com>
Call-Id:
12345@ue_a.home_a.com
Cseq:
1 REGISTER
Contact:
User_A <sip:ue_a_12.34.56_EF_5060
@p_cscf.visited_a.com >
Other-Identities:
tel: +358-40-7618290, sip:Mary@chessclub-hel.org
In step 3 of
In step 4 of
REGISTER
home_a.com SIP/2.0
Via:
SIP/2.0/UDP i_cscf.home_a.com
Via:
SIP/2.0/UDP p_cscf.visited_a.com
Via:
SIP/2.0/UDP 12.34.56::EF:5060
From:
Private Identity <sip:245454555@home_a.com>
To:
Mary Blue <sip:Mary.Blue@home_a.com>
Call-Id:
12345@ue_a.home_a.com
Cseq:
1 REGISTER
Contact:
User_A <sip:ue_a_12.34.56_EF_5060
@p_cscf.visited_a.com >
Other-Identities:
tel: +358-40-7618290, sip:Mary@chessclub-hel.org
In step 5 of
In step 6 of
SIP/2.0
200 OK
Via:
SIP/2.0/UDP i_cscf.home_a.com
Via:
SIP/2.0/UDP p_cscf.visited_a.com
Via:
SIP/2.0/UDP 12.34.56::EF:5060
From:
Private Identity <sip:245454555@home_a.com>
To:
Mary Blue <sip:Mary.Blue@home_a.com>
Call-Id:
12345@ue_a.home_a.com
Cseq:
1 REGISTER
Contact:
User_A <sip:ue_a_12.34.56_EF_5060
@p_cscf.visited_a.com >
Other-Identities:
tel: +358-40-7618290, sip:Mary@chessclub-hel.org
In step 7 of
SIP/2.0
200 OK
Via:
SIP/2.0/UDP p_cscf.visited_a.com
Via:
SIP/2.0/UDP 12.34.56::EF:5060
From:
Private Identity <sip:245454555@home_a.com>
To:
Mary Blue <sip:Mary.Blue@home_a.com>
Call-Id:
12345@ue_a.home_a.com
Cseq:
1 REGISTER
Contact:
User_A <sip:ue_a_12.34.56_EF_5060
@p_cscf.visited_a.com >
Other-Identities:
tel: +358-40-7618290, sip:Mary@chessclub-hel.org
In step 8 of
Then, in step 9 of
SIP/2.0
200 OK
Via:
SIP/2.0/UDP 12.34.56::EF:5060
From:
Private Identity <sip:245454555@home_a.com>
To:
Mary Blue <sip:Mary.Blue@home_a.com>
Call-Id:
12345@ue_a.home_a.com
Cseq:
1 REGISTER
Contact:
User_A <sip:ue_a@12.34.56::EF:5060>
Other-Identities:
tel: +358-40-7618290, sip:Mary@chessclub-hel.org
Then the registration of the additional other public identities is completed.
In a second preferred embodiment, all public identities stored in subscriber database, e.g. the HSS, are registered if indicated in the user equipment. The user equipment, i.e. the user's terminal sends one of the valid public identities in the “To” header field of the REGISTER message and a flag, a suitable mark, a note or the like, e.g. in the header field “Other-identities” indicating that all public identities should be registered. The S-CSCF registers all public identities listed in the subscriber's profile contained in the subscriber database, i.e. the HSS. The S-CSCF returns the list of registered public identities in the “Other-Identities” header field to the P-CSCF. The P-CSCF stores the registered public identities for later use.
In a third preferred embodiment, all public identities stored in the subscribers database, i.e. the HSS, are registered by a default setting. The REGISTER message is send without the “Other-Identities” header field or any other indication. The S-CSCF registers all available public identities listed in the subscriber's profile stored in the HSS and returns the registered public identities to the P-CSCF in the “Other-Identities” header field, in the payload or in another appropriate way. The P-CSCF then stores the registered public identities for later use. In this “all in one registration by default” case, the subscriber may have defined beforehand, e.g. via a web page, a certain menu displayed on his terminal or the like, the identities and/or profiles included in the “default” set.
It is noted that the “Supported”, “Require”, and “Proxy-Require” header fields are not taken into account for the scope of this embodiment; however, it is quite likely that those may be used as well. Furthermore, considerations about the “Path” header field (as recently decided in 3GPP) are not taken into account for the scope of this embodiment for simplification reasons.
The subscriber might want to administrate his public identities himself to avoid being charged by the operator, to make changes quickly and smoothly and to feel to be his own master. It would be also easy to the operator to allow subscribers e.g. to change the list of public identities that are registered always by default at the registration; or to allow delete, change and create subprofiles and define their content in limits given by the operator.
To achieve this, the HSS database may or may not be divided into several subdatabases. If it is divided into subdatabases, some of the subdatabases can be edited by the subscriber, and others by the operator only. Thereby, the HSS is less vulnerable. If it is not divided into subdatabases, some part(s) of the database can be edited by the subscriber, and others by the operator only. The subscriber edits a temporal copy of his entry in the database. After editing the validity and the correctness of the change or the whole entry is checked. If no errors are found, the temporal copy of the subscribers entry replaces the old entry in the database or subdatabase. According to operator specified rules a new production version may then be generated of the database or the subdatabase(s). Because the HSS is a register of the services the subscriber has ordered, it is the proper place where subscriber can make changes when ordering/cancelling/deleting/changing a service. Furthermore, generating a DNS-ENUM (Domain Name System—E.-Number) database is easier because not the whole HSS database has to be searched. In case the HSS original database is divided into subdatabases, the generation can be done based on possibly only one subdatabase.
The subscriber's private key may be the key that is common in all subdatabases. The database/subdatabase may have three versions: the first is the original database, the second is the production version and the third is the temporal version where the subscriber makes changes to his own entry.
Thus, a new optional header (e.g. “Other-Identities”) is introduced in the REGISTER message to convey the information what other public identities the user wants to register. Any other name can be used for the header field “Other-identities”. The “From” field of the REGISTER message comprises the private identity and the “To” field one of the valid public identities of the subscriber. It doesn't matter which one of the valid public identities is used in the “To” field. In the “Other-identities” header field, there are listed the other public identities that the subscriber wants to register at the same time.
Network elements and terminals that don't understand the new optional header “Other-identities” leave it untouched. This feature cannot be utilized with them. As a further option, one or more of the items in the “Other-identities” optional header can be a profile instead of individual public identity. In that case, all public identities that are included in the listed profiles are registered, according to the concept “one private identity but several user profiles”. Attributes, which modify the registration of individual profile or public identity, may be attached to profiles and even public identities listed in the “Other-identities” header field. If the user wants to attach attributes to the public identity used in the “To” field, the public identity can be repeated in the “Other-identities” header with appropriate attributes. The terminal or user equipment may insert the “Other-identities” header to the REGISTER message. The list of the valid profiles/public identities may be stored in the UMTS subscriber identity module (USIM) and/or in terminal's memory and/or it may be inserted by the user.
Instead of the new optional header “Other-identities” the same information could be conveyed in the payload of the REGISTER message.
It is assumed that the subscriber has registered with one of his identities. As a default setting, that identity can be used for incoming and outgoing calls. When the subscriber wants to use one of his other identities, he simply makes a call with it, i.e. sends an INVITE SIP message with the unregistered identity in the “From” header field. When the network element in charge of keeping track of the subscriber's identities, i.e. S-CSCF and/or P-CSCF, receives the INVITE message from the subscriber's terminal, it stores the INVITE message and sends a REGISTER message with the unregistered identity in order to register it. If the registration succeeds, the identity is registered for outgoing calls as a default setting and the network element proceeds with retrieving the INVITE message and sending it further. If the registration fails the call is released.
The subscriber may register or change his registration explicitly with whichever of his identities for incoming calls only, or for outgoing calls only, or for both by sending a REGISTER message with the identity in question and with an appropriate parameter(s). The subscriber's choice may be limited with master parameters in the HSS. Limiting factors can be e.g. the time, whether the bill is paid, and the direction (incoming/outgoing/both). The subscriber can do several registrations at the same time. With a certain parameter in the INVITE message, the registration may be done also for incoming calls, not only for outgoing calls (that may be a default setting). With another certain parameter in the REGISTER message all valid identities may be registered and received from HSS.
Some resolving functionality (e.g. Domain Name Server (DNS) or similar database or alike) is needed so that the network element in charge of keeping track of the subscriber's identities (i.e. S-CSCF and/or P-CSCF) can find the correct HSS for an identity in order to be able to route the REGISTER message towards the correct HSS.
As regards the “one private identity but several user profiles” case, the present invention can also be used together with user profiles. An operation targeted to a user profile has influence on all public identities which belong to that user profile.
In other words, a user profile is only a bundle of public identities. For example, when a user registers a user profile, all public identities under that profile are registered. A user profile may be addressed e.g. with one of its public identities.
Concerning the “several private identities” case, the present invention can also be used together with several private identities. An operation targeted to a private identity has influence on all public identities that belong to that private identity. In other words, a private identity is a bundle of public identities. The private identities of a subscriber can be bound together with one or more client identities that are used e.g. for charging.
In all cases, the subscriber may get a warning (if desired) about calls to his non-registered public identities.
In summary, the present invention describes a registration method wherein a user is registered in a communication network. According to a first aspect, a registration message is used, which comprises a header field for defining at least one other identity of the subscriber. According to a second aspect, a registration message is used, which comprises an identity information in its payload portion, said identity information defining at least one other identity of the subscriber. According to a third aspect, a one-by-one registration is performed based on an identity information stored at the terminal device, said identity information defining at least one other identity of the subscriber. Thus, the user or subscriber can register some or all of his public identities at once with one registration procedure. Furthermore, the subscriber can utilize his identities smoothly and easily, and at the same time prevent unwanted incoming calls. Additionally, the subscriber can utilize his public identities smoothly and easily by grouping the public identities under user profiles or under private identities.
It is noted that the present invention is not restricted to the above described preferred embodiments but can be applied in any registration procedure of any communication network, where a registration message comprising a user identity is transmitted from a terminal device to the communication network. The invention may thus vary within the scope of the attached claims.
Westman, Ilkka, Honeisen, Bernhard
| Patent | Priority | Assignee | Title |
| Patent | Priority | Assignee | Title |
| 5764730, | Oct 05 1994 | Google Technology Holdings LLC | Radiotelephone having a plurality of subscriber identities and method for operating the same |
| 6108540, | Dec 24 1997 | Microsoft Technology Licensing, LLC | Multi-profile subscriber |
| 6546247, | Sep 08 2000 | Telefonaktiebolaget L M Ericsson (publ) | Home location server and call processing method in a hybrid second/third generation radio telecommunications network |
| 6603969, | Nov 26 1997 | NOKIA SOLUTIONS AND NETWORKS OY | Subscriber service profiles in telecommunication system |
| 6672775, | Aug 01 1997 | International Business Machines Corporation | Cross-machine web page download and storage |
| 7206280, | Sep 12 2000 | Nokia Technologies Oy | Method and apparatus for asynchronous incremental redundancy reception in a communication system |
| 20010024161, | |||
| 20010049790, | |||
| 20020037723, | |||
| 20020141381, | |||
| 20020167946, | |||
| WO79756, | |||
| WO9927722, |
| Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
| Sep 25 2003 | WESTMAN , ILKKA | Nokia Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 027062 | /0305 | |
| Sep 26 2003 | HOENEISEN, BERNARD | Nokia Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 027062 | /0305 | |
| Jun 17 2011 | Nokia Corporation | (assignment on the face of the patent) | / | |||
| Jan 16 2015 | Nokia Corporation | Nokia Technologies Oy | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 035602 | /0299 |
| Date | Maintenance Fee Events |
| Aug 21 2014 | ASPN: Payor Number Assigned. |
| Feb 22 2018 | M1552: Payment of Maintenance Fee, 8th Year, Large Entity. |
| Feb 23 2022 | M1553: Payment of Maintenance Fee, 12th Year, Large Entity. |
| Date | Maintenance Schedule |
| Sep 23 2017 | 4 years fee payment window open |
| Mar 23 2018 | 6 months grace period start (w surcharge) |
| Sep 23 2018 | patent expiry (for year 4) |
| Sep 23 2020 | 2 years to revive unintentionally abandoned end. (for year 4) |
| Sep 23 2021 | 8 years fee payment window open |
| Mar 23 2022 | 6 months grace period start (w surcharge) |
| Sep 23 2022 | patent expiry (for year 8) |
| Sep 23 2024 | 2 years to revive unintentionally abandoned end. (for year 8) |
| Sep 23 2025 | 12 years fee payment window open |
| Mar 23 2026 | 6 months grace period start (w surcharge) |
| Sep 23 2026 | patent expiry (for year 12) |
| Sep 23 2028 | 2 years to revive unintentionally abandoned end. (for year 12) |