US6011969A
Expired / Lapsed
US
⏱️ 0.0 years remaining
TCAP package type specification for ANSI-41 MAP messages in order to support MAP operation closure
Assignee: Telefonaktiebolaget LM Ericsson AB
•
Filing: 1998-06-02
•
Granted: 2000-01-04
•
Expires: 2018-06-02
Abstract
Abstract The package type identifier of "conversation with permission" is utilized in certain ANSI-41 Mobile Application Part (MAP) messages to allow a node receiving the message to generate an appropriate response message necessary for MAP operation closure within a Transaction Capability Application Part (TCAP) transaction. In one implementation, an ANSI-41 MAP error or reject message includes a package type identifier of "conversation with permission" instead of "response" thus allowing the node receiving the error or reject message to appropriately respond in connection with the closure of an open MAP operation. In another implementation, the "conversation with permission" package type identifier is specified for an ANSI-41 MAP instruction request message to support MAP operation closure in the event of an error or rejection in that operation.
Inventors
- 👤 Marco Antonio Hurtado Vargas
- 👤 Margaret Britt
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-10-28 02:45
CPC Classifications
H; H04; H04W; H04W76/00; H04W76/20; H04W8/00; H04W8/18; H04W92/00; H04W92/16; H04W92/24
Claims Analysis
Total Claims: 15
Claim 1
Independent Claim
169 words
A method for supporting the closure of (MAP) Mobile Application Part operations within a shared Transaction Capability Application Part (TCAP) transaction in the event of an error or reject, comprising the steps of: sending a first MAP message from a first node to a second node, the first message initiating the TCAP transaction; sending a second MAP message from the second node to the first node within the same TCAP transaction, the second message sent in response to the first message; experiencing at the first node a problem preventing processing of the second MAP message; sending a second MAP message answer from the first node to the second node, the second MAP message answer sent in response to the experienced problem and including a package type of "conversation with permission"; and sending a first MAP message answer from the second node to the first node, the first MAP message answer sent in response to the second MAP message answer and closing each MAP operation and the open TCAP transaction.
Claim 2
Independent Claim
169 words
A method for supporting the closure of (MAP) Mobile Application Part operations within a shared Transaction Capability Application Part (TCAP) transaction in the event of an error or reject, comprising the steps of: sending a first MAP message from a first node to a second node, the first message initiating the TCAP transaction; sending a second MAP message from the second node to the first node within the same TCAP transaction, the second message sent in response to the first message; experiencing at the first node a problem preventing processing of the second MAP message; sending a second MAP message answer from the first node to the second node, the second MAP message answer sent in response to the experienced problem and including a package type of "conversation with permission"; and sending a first MAP message answer from the second node to the first node, the first MAP message answer sent in response to the second MAP message answer and closing each MAP operation and the open TCAP transaction.
Claim 3
Dependent Claim
32 words
The method as in claim 1 wherein: the first node comprises a mobile switching center of a telecommunications network; and the second node comprises a home location register of that telecommunications network.
Claim 4
Dependent Claim
46 words
The method as in claim 2 wherein: the second MAP message comprises a remote user interaction directive (RUIDIR) message; and the second MAP message answer comprises a remote user interaction directive (ruidir) reject or error return result message including the package type of "conversation with permission".
Claim 5
Dependent Claim
30 words
The method as in claim 3 wherein: the first MAP message comprises a location request (LOCREQ) message; and the first MAP message answer a location request (locreq) return result message.
Claim 6
Dependent Claim
31 words
The method as in claim 3 wherein: the first MAP message comprises an origination request (ORREQ) message; and the first MAP message answer comprises an origination request (orreq) return result message.
Claim 7
Dependent Claim
31 words
The method as in claim 3 wherein: the first MAP message comprises a feature request (FEATREQ) message; and the first MAP message answer comprises a feature request (featreq) return result message.
Claim 8
Independent Claim
110 words
A method for supporting the closure of Mobile Application Part (MAP) operations within a shared Transaction Capability Application Part (TCAP) transaction in the event of an error or reject, comprising the steps of: sending a MAP message from a first node to a second node, the MAP message sent within an existing open TCAP transaction and including a package type of "conversation with permission"; experiencing at the second node a problem preventing processing of the MAP message; sending a MAP message answer from the first node to the second node, the MAP message answer sent in response to the experienced problem and closing the open TCAP transaction and MAP operation.
Claim 9
Independent Claim
110 words
A method for supporting the closure of Mobile Application Part (MAP) operations within a shared Transaction Capability Application Part (TCAP) transaction in the event of an error or reject, comprising the steps of: sending a MAP message from a first node to a second node, the MAP message sent within an existing open TCAP transaction and including a package type of "conversation with permission"; experiencing at the second node a problem preventing processing of the MAP message; sending a MAP message answer from the first node to the second node, the MAP message answer sent in response to the experienced problem and closing the open TCAP transaction and MAP operation.
Claim 10
Dependent Claim
31 words
The method as in claim 7 wherein: the first node comprises an intelligent peripheral within a telecommunications network; and the second node comprises a service control function within that telecommunications network.
Claim 11
Dependent Claim
40 words
The method as in claim 8 wherein: the MAP message comprises an instruction request (INSTREQ) message including the package type of "conversation with permission"; and the MAP message answer comprises an instruction request (instreq) reject or error return result message.
Claim 12
Dependent Claim
88 words
In connection with the handling of nested Mobile Application Part (MAP) operations within a Transaction Capability Application Part (TCAP) transaction including an outer MAP operation and an inner MAP operation, a method comprising the steps of: specifying in a first MAP message relating a reject or error return result and comprising part of the inner MAP operation a package type of "conversation with permission"; responding to the permission granted by the first MAP message with a second MAP message effectuating a graceful closure of the outer MAP operation.
Claim 13
Dependent Claim
88 words
In connection with the handling of nested Mobile Application Part (MAP) operations within a Transaction Capability Application Part (TCAP) transaction including an outer MAP operation and an inner MAP operation, a method comprising the steps of: specifying in a first MAP message relating a reject or error return result and comprising part of the inner MAP operation a package type of "conversation with permission"; responding to the permission granted by the first MAP message with a second MAP message effectuating a graceful closure of the outer MAP operation.
Claim 14
Dependent Claim
15 words
The method of claim 10 wherein the first MAP message comprises a service invoking message.
Claim 15
Dependent Claim
15 words
The method of claim 10 wherein the first MAP message comprises a service instruction message.
References Cited (Backward Citations)
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2003-01-03 | 2003-07-05 | 2004-01-04 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2007-01-03 | 2007-07-05 | 2008-01-04 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2011-01-03 | 2011-07-05 | 2012-01-04 | $7700.00 | Window Closed / Lapsed |