WO2002058407A2 - System and method for mapping information from end-user orders to the corresponding inter-provider orders - Google Patents
System and method for mapping information from end-user orders to the corresponding inter-provider orders Download PDFInfo
- Publication number
- WO2002058407A2 WO2002058407A2 PCT/US2002/000162 US0200162W WO02058407A2 WO 2002058407 A2 WO2002058407 A2 WO 2002058407A2 US 0200162 W US0200162 W US 0200162W WO 02058407 A2 WO02058407 A2 WO 02058407A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- user
- order
- value
- provider
- service item
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
- G06Q30/0633—Lists, e.g. purchase orders, compilation or processing
Definitions
- This invention relates in general to provisioning of communications services and more particularly to a system and method for mapping information collected in connection with the creation of end-user orders for communications services to the corresponding inter-provider orders.
- a Local Exchange Carrier must typically manage two types of orders for communications services - service orders for its end-user customers and service orders for other LECs.
- LSP local service provider
- CLEC competitive LEC
- Personnel associated with the LSP must in turn capture sufficient information from the end-user to allow the LSP to provision the requested service items. If the LSP does not own appropriate network, equipment, or other resources necessary to satisfy the end-user request, personnel associated with the LSP must interpret the request to determine appropriate service details and then use the details to create a standardized Local Service Request (LSR).
- LSR Local Service Request
- the LSP communicates the LSR to an incumbent LEC (ILEC) or other network service provider (NSP), which owns the network, equipment, and other resources necessary to satisfy the end-user request.
- LEC incumbent LEC
- NSP network service provider
- the NSP provides requested service items based on the LSR and the LSP completes the provisioning process with respect to the service items.
- the required format for LSRs which is defined in Local Service Ordering Guidelines (LSOG) of the Ordering & Billing Forum (OBF), is frequently revised as competition between LECs evolves, new local services become available, or changes occur in the manner in which local services are requested.
- LSOG Local Service Ordering Guidelines
- OBF Ordering & Billing Forum
- An Operations Support System (OSS) associated with the LSP will typically provide an end-user ordering module that links requested service items to the capabilities of NSPs, but doing so usually requires extensive input of LSP personnel.
- Inter-provider orders such as LSRs between LSPs and NSPs, may often contain much more information than end-user orders or may specify similar information but in a different format.
- a possible solution is to force LSP customer service personnel to interact with end-users, perhaps multiple times, to obtain all information required for corresponding LSRs. This is undesirable, however, in part because it requires such personnel to have familiarity with the complex details of the LSRs and associated inter-provider ordering modules, practices, or both.
- LSPs may not need inter-provider ordering modules or may not have purchased end-user and inter-provider ' ordering modules from the same company, such that the LSPs would not want information for LSRs unduly complicating their end-user ordering processing. Since CLECs may "error out" as many as fifty percent of LSRs due to incorrect or incomplete data entry, streamlining the LSR creation process is often a significant concern.
- LSP personnel may still be required to input information twice - once for the end-user order and again for the LSR.
- the end-user is often inconvenienced as a result of multiple contacts with LSP personnel - once in connection with creation of the end-user order and again in connection with creation of the LSR. This inconvenience may be exacerbated if the second or any subsequent contacts come from LSP provisioning personnel that are skilled in connection with provisioning issues but, unlike customer service personnel, are untrained in interacting with end-users. Alienation of the end-user resulting from a poorly handled interaction with such personnel is highly undesirable.
- a system for mapping values collected in connection with creation of end-user orders for communications services to corresponding inter-provider orders includes an end-user ordering module and an inter- provider ordering module.
- the end-user ordering module determines whether an end-user requested service item contained in a service provider product catalog relates to a service item type having at least one associated developer defined label (DDL).
- the DDL extends the attributes of the associated service item type by specifying an additional attribute for which a value may be collected from the end-user and supplied in connection with creation of an end-user order for the requested service item.
- the value is not needed to complete the end-user order but is collected and supplied to avoid needing to collect the value from the end-user in connection with subsequent creation of an inter-provider order that corresponds to the end-user order.
- the end-user ordering module prompts a user of the end-user ordering module to collect from the end-user and supply a value for the additional DDL-specified attribute in connection with creation of the end-user order for the requested service item.
- the end-user ordering module communicates the end-user order for use in the subsequent creation of the corresponding inter-provider order.
- the inter-provider ordering module receives the end-user order and determines whether the end-user order has a value for the additional DDL-specified attribute. If the end-user order has a value for the additional DDL-specified attribute, the inter-provider ordering module automatically maps the value from the end-user order to an appropriate field of the inter- provider order such that the value need not be collected from the end-user in connection with creation of the inter-provider order.
- end-user ordering module software facilitates the mapping of values collected in connection with the creation of end-user orders for communications services to corresponding inter-provider orders. When executed, the software operates to determine whether an end-user requested service item contained in a service provider product catalog relates to a service item type having at least one associated DDL.
- the DDL extends the attributes of the associated service item type by specifying an additional attribute for which a value may be collected from the end-user and supplied in connection with creation of an end-user order for the requested service item.
- the value is not needed to complete the end-user order but is collected and supplied to avoid needing to collect the value from the end-user in connection with subsequent creation of an inter-provider order corresponding to the end-user order.
- the software prompts a user of the software to collect from the end-user and supply a value for the additional DDL-specified attribute in connection with creation of the end-user order for the requested service item.
- the software provides the end-user order to inter-provider ordering module software for use in subsequently creating the corresponding inter-provider order, such that the inter-provider ordering module software can determine whether the end-user order has a value for the additional DDL-specified attribute and also such that, if the end-user order has a value for the additional DDL-specified attribute, the inter-provider ordering module software can automatically map the value from the end-user order to an appropriate field of the inter- provider order such that the value need not be collected from the end-user in connection with creation of the inter-provider order.
- inter-provider ordering module software facilitates the mapping of values collected in connection with creation of end-user orders for communications services to corresponding inter-provider orders.
- the software When executed, the software operates to access an end-user order for use in subsequently creating a corresponding inter-provider order.
- the software determines whether the end-user order has a value for at least one DDL, the DDL being associated with a service item type related to an end-user requested service item contained in a service provider product catalog.
- the DDL extends the attributes of the associated service item type by specifying an additional attribute for which a value may be collected from the end-user and supplied in connection with creation of the end-user order for the requested service item.
- the value is not needed to complete the end-user order but is collected and supplied to avoid needing to collect the value from the end-user in connection with subsequent creation of the corresponding inter-provider order. If the end-user order has a value for the additional DDL-specified attribute, the software operates to automatically map the value from the end-user order to an appropriate field of the inter-provider order such that the value need not be collected from the end-user in connection with creation of the inter-provider order.
- the present invention provides a number of technical advantages over prior techniques.
- the present invention allows information, such as values for additional DDL- specified attributes, to be collected from an end-user, supplied on an end-user order, and automatically mapped through to an LSR or other inter-provider order. This allows certain fields of the LSR to be automatically populated without further interaction with the end-user. As a result, the provisioning process is more efficient, more reliable, and less burdensome on the end-user.
- one or more DDLs may be readily associated with appropriate item types to accommodate these changes, without requiring new software to be developed.
- the present invention thus provides an integrated, data-driven, and product catalog centric solution that benefits both LSPs and end-users alike. Systems and methods incorporating one or more of these or other technical advantages are well suited for communications service provisioning environments. Other technical advantages are readily apparent to those skilled in the art from the following figures, descriptions, and claims.
- FIGURE 1 illustrates an exemplary business scenario involving switching of residential line service between LSPs
- FIGURE 2 illustrates an exemplary system for mapping information collected in connection with the creation of end-user orders for communications services to corresponding inter-provider orders
- FIGURE 3 illustrates exemplary PSR item type, product specification, and product catalog hierarchies
- FIGURE 4 illustrates exemplary LSR item type, product specification, and product catalog hierarchies
- FIGURE 5 illustrates exemplary mapping between PSR and LSR item type hierarchies.
- FIGURE 1 illustrates an exemplary business scenario 10 involving first LSP 12a, end-user customer 14 of first LSP 12a, and second LSP 12b.
- Business scenario 10 is used to describe the general process of mapping information according to the present invention from a Product Service Request (PSR) or another end-user order to an LSR or another inter-provider order in connection with switching residential line service for the end-user 14 from LSPa to LSP 12b.
- PSR Product Service Request
- end-user 14 has existing residential line service through the first (old) LSP 12a, which might be an ILEC, and is transferring this residential line service to the second (new) LSP 12b, which might be a CLEC.
- Existing residential line service is being provided through first LSP 12a over local loop 16 between end-user 14 and an appropriate port 18 of first LSP 12a.
- end-user 14 communicates with second LSP 12b and arranges for the residential line service to be switched to second LSP 12b from first LSP 12a (as is indicated by arrow 20).
- End-user 14 may request, either explicitly or implicitly, one or more suitable service items from the product catalog of LSP 12b in arranging for this switching of service.
- a customer service representative associated with the second LSP 12b collects appropriate information from the end-user 14, typically including values for attributes of the requested service items, and then supplies this information to a PSR or other end-user order.
- requested service items may include an "Unbundled Port" service item, although any suitable service items may be requested.
- the second LSP 12b is able to create a PSR for an unbundled service item based on an existing arrangement between second LSP 12b and first LSP 12a.
- the second LSP 12b analyzes the service items on the PSR and, according to the present invention, maps the associated values to an LSR or other inter-provider order (as indicated by arrow 22).
- second LSP 12b sends the LSR to first LSP 12a (as indicated by arrow 24), the second LSP 12b provisions the requested service items, the first LSP 12a changes the account information for end-user 14 in its system, and first LSP 12a sends a confirmation to second LSP 12b to complete the transaction (as indicated using arrow 26).
- FIGURE 2 illustrates exemplary system 30 for mapping certain information collected in connection with creation of PSRs or other end-user orders to LSRs or other inter-provider orders.
- PSRs and LSRs are primarily described, the present invention contemplates any appropriate end-user orders and inter-provider orders, respectively.
- System 30 includes a PSR ordering module 32, an associated user 34a, an LSR ordering module 36, and an associated user 34b.
- PSR ordering module 32 and LSR ordering module 36 may be integral to or separate from each other, in whole or in part, and may communicate with each other using any suitable wireline, wireless, or other communications link 38.
- users 34a and 34b may be the same or different users 34.
- PSR ordering module 32 and LSR ordering module 36 may operate on one or more computer systems at one or more locations and may share one or more appropriate resources or constructs.
- the PSR and LSR ordering modules 32 and 34 may share the same database schema.
- the user 34a interacts with the end-user 14 and creates a PSR 40 using the PSR ordering module 32 and communicates information collected on the PSR 40 to LSR ordering module 36.
- User 34b uses LSR ordering module 36 to create a corresponding LSR 42 to effect provisioning of the service items requested by end-user 14.
- FIGURE 3 illustrates exemplary item type hierarchy 50, product specification hierarchy 52, and product catalog hierarchy 54 and relationships that exist between the elements of hierarchies 30, 32, and 34.
- item type hierarchy 50 contains service item types 56 corresponding to line products that an LSP 12 may provide and market to end-users 14.
- the hierarchy 50 contains "Line Product” item type 56 at a first level 58, "Line” item type 56 (a subset of the "Line Product” item type 56) at a second level 60, and "Option” and “MapLSRPort” item types 56 (both subsets of "Line” item type 56) at a third level 62.
- item types 56 within hierarchy 50 form the foundation on which product specification hierarchy 52 and product catalog hierarchy 54 are constructed.
- item types 56 in complete hierarchy 50 may additionally include, without limitation, "Trunk Product,” “Non-Premise Product,” “Line Option,” “Key Option,” “Product Option,” “Business Set,” “Flow through Command,” “Flow through Plan,” and any other appropriate item types 56.
- the item types 56 in hierarchy 50 provide building blocks that a developer of PSR ordering module 32 controls, and may therefore code against, in specifying the logic implemented within PSR ordering module 32 and information that needs to be collected at the PSR creation stage.
- the item types 56 specify developer defined rules (DDRs) for collecting and processing information associated with the creation of PSRs 40.
- DDRs developer defined rules
- a developer may code against item types 56 to specify information that needs to be collected during the PSR creation stage not for use in creating PSRs 40 but for mapping to subsequently created LSRs 42.
- Item type hierarchy 50 and its associated item types 56 are preferably unavailable to and cannot be changed by a customer, such as an LSP 12, that has purchased PSR ordering module 32 from the developer. If any changes to hierarchy 50 are called for, the customer contacts the developer to implement such changes.
- product specification hierarchy 52 contains product specifications 64 corresponding with item types 56 in hierarchy 50.
- This hierarchy 52 contains "Dialtone Product” product specification 64 at first level 58, "Dialtone Line” and “ISDN Line” product specifications 64 (both subsets of "Dialtone Product” product specification 64) at second level 60, and "Call Waiting,” “Call Forwarding,” and “LSR Port” product specifications 64 (all subsets of "Dialtone Line” product specification 64) at third level 62.
- hierarchy 52 corresponding to the exemplary line products is described, the present invention contemplates any hierarchically related product specifications 64.
- product specifications 64 define templates, based on associated item types 56 in hierarchy 50, for line products that LSP 12 is capable of provisioning to end users 14. Therefore, product specifications 64 also provide a boundary for the service items (in this example, service items relating to line products) that the LSP product catalog may contain for actual sale to the end-users 14.
- LSP 12 may create any product specifications 64 that meet its particular needs, limited only by the underlying service item types 56. As indicated by arrow 66 at level 58, LSP 12 is able to provision "Dialtone Product" product specification 64 because the developer has made the corresponding "Line Product" item type 56 available within the hierarchy 50.
- LSP 12 is able to provision "Dialtone Line” and "ISDN Line” product specifications 64 because the developer has made the corresponding "Line” item type 56 available within hierarchy 50.
- LSP 12 is able to provision "Call Waiting,” “Call Forwarding,” and “LSR Port” product specifications 64 because the developer has made the corresponding "Option” and "MapLSRPort” item types 56 available in hierarchy 50.
- an item type 56 might correspond to a shirt and product specifications 64 linked to that item type 56 might specify all the colors and sizes of shirts that can actually be made.
- Product specifications 64 may be differentiated from each other and processed according to their underlying item types 56.
- the product catalog hierarchy 54 contains various product catalog service items 72 corresponding to product specifications 64 in hierarchy 52.
- Hierarchy 54 contains "Residential Service " and "Basic Business” service items 72 at first level 58.
- First and second "Dialtone Line” service items 72 are at second level 60.
- "Call Waiting” and "Unbundled Port” service items 72 are at third level 62.
- service items 72 define, based on associated product specifications 64 in hierarchy 52, the particular line products that LSP 12 actually markets for sale to end-users 14.
- LSP 12 may create any service items 72 that meet its particular needs, limited only by the underlying product specifications 64. As is indicated by arrows 74 at level 58, LSP 12 is able to sell "Residential Service” and "Basic Business” service items 72 because corresponding "Dialtone Product” product specification 64 has already been made available within hierarchy 52. Similarly, as indicated by arrows 76 at level 60, LSP 12 is able to sell first and second "Dialtone Line” service items 72 because corresponding "Dialtone Line” product specification 64 has already been made available within hierarchy 52.
- LSP 12 is able to sell "Call Waiting" and "Unbundled Port” service items 72 for a residential service dialtone line because corresponding "Call Waiting" and "LSR Port” product specifications 64 have already been made available within hierarchy 50.
- LSP 12 is able to sell "Call Waiting” and “Call Forwarding” service items 72 for a basic business dialtone line because the corresponding "Call Waiting" and "Call Forwarding" product specifications 64 have already been made available within hierarchy 50.
- item type 56 corresponds to a shirt and product specifications 64 linked to that item type 56 specify all the colors (red, blue, etc.) and sizes (large, medium, etc.) of shirts that can actually be made
- service items 72 might specify the particular shirts that will actually be sold to customers (large red shirt, medium blue shirt, etc.).
- product specifications 64, and item types 56 marketing personnel associated with LSP 12 are prevented from selling services that LSP 12 is unable to actually provision. Marketing personnel are only presented with an opportunity to sell those service items 72 for which relationships flow back through valid product specifications 64 and item types 56.
- Each item type 56 within hierarchy 50 has a corresponding set of features, characteristics, or other attributes for which values need to be supplied in creating a PSR or other end-user order 40. Certain of these values may in turn be needed for LSR or other inter-provider order 42 being created based upon the PSR 40. For values that have already been collected in connection with PSR 40, and which are needed for LSR 42, it is preferable to map those values through to LSR 42 such that they need not be collected again from the end-user 14. Such mapping reduces the inconvenience to end-user 14 in obtaining requested service items 72 and improves the efficiency and reliability of the transaction for LSP 12. Further, there may be values that, while not needed for PSR 40, are needed in later creating an LSR 42 based on PSR 40.
- DDLs developer defined labels
- MapLSRPort item type 56 may include Line Existing Account Number (LEAN) DDL 80 and Line Existing Account Telephone Number (LEATN) DDL 80. This indicates that LEAN and LEATN are additional attributes of "MapLSRPort” item type 56, the item type 56 for "Unbundled Port” service item 72.
- LSP 12a from which service is being switched
- LEATN Line Existing Account Telephone Number
- LEAN and LEATN fields may be presented to the LSP representative as needing values at the PSR creation stage.
- the representative obtains the information from end-user 14 and supplies the LEAN and LEATN values in the appropriate fields of PSR 40 or otherwise.
- the LEAN and LEATN values may be mapped through for use at the LSR creation stage, along with any other values collected for "Unbundled Port” service item 72 based on inherent attributes of its "MapLSRPort” item type 56.
- LEAN and LEATN DDLs 80 are primarily described, the present invention contemplates any suitable DDLs 80 associated with item types 56 in an appropriate item type hierarchy 50 to extend the attributes of those item types 56.
- Each item type 56 may have zero, one, or multiple associated DDLs 80.
- a DDL 80 will be effective as to all service items 72 associated with the item type 56 of the DDL 80.
- DDLs 80 therefore provide a generic mechanism to add fields associated with values to be collected at the PSR creation stage for mapping through to the LSR creation stage.
- DDLs 80 provides desirable extensibility to the PSR to LSR mapping process. For example, if the industry mandates that LSRs 42 should from some date forward include one or more additional fields requiring values, then the developer of PSR ordering engine 32 can readily associate one or more suitable DDLs 80 with appropriate item types 56 within hierarchy 50 to accommodate these additional fields. The LSP 12 is then able to map these DDL values, once collected during the PSR creation stage, through to the subsequent LSR creation stage. As a result, despite these additional fields, the LSP 12 is still able to reduce or eliminate multiple contacts with end-users 14. Nor will LSP 12 be required to purchase an entirely new PSR ordering engine 32 or LSR ordering engine 34 to obtain these benefits.
- DDLs 80 provide a measure of future- proofing not available using prior techniques.
- item type hierarchy 50, product specification hierarchy 52, and service item hierarchy 54 described above in connection with PSRs 40 there exist hierarchies of items types, product specifications, and service items associated with creating LSRs 42.
- LSR related hierarchies are not in general the same as the corresponding PSR related hierarchies 30, 32, and 34.
- the LSR hierarchies are industry mandated, are not customizable for particular developers or LSPs 12, and specify the exhaustive set of service items that can be ordered through an LSR 42 (and the exhaustive set of corresponding product specifications and item types on which the service items are based).
- an LSR item type hierarchy 90 may include "LSRNum” and “LSReqType” item types 92 at level 94 analogous to "Line Product" item type 56 at level 58 in PSR item type hierarchy 50, may include “Lnum” item type 92 at level 96 analogous to "Line” item type 56 at level 60 in PSR item type hierarchy 50, and may further include “Blocking” and “MapLSRPort” item types 92 at level 98 analogous to "Option" and “MapLSRPort” item types 56 at level 62 in PSR item type hierarchy 50.
- LSR product specification hierarchy 100 and product catalog hierarchy 102 may include product specifications 104 and service items 106, respectively, that are analogous to PSR product specification hierarchy 52 and product catalog hierarchy 54, respectively, described above.
- the PSR and LSR ordering modules 32 and 34, respectively, used to create PSRs 40 and LSRs 42, respectively, have overlapping although not matching hierarchical data structures.
- these differing PSR and LSR data structures must have in common the item type 56 that is associated with DDL 80 - that is, the item type 56 in the PSR item type hierarchy 50 having DDL 80 must have a corresponding item type 92 in LSR item type hierarchy 90.
- FIGURE 5 illustrates exemplary mapping between PSR and LSR item type hierarchies 30 and 70, respectively.
- a customer service representative handling the end-user request for LSP 12 uses a suitable user interface associated with PSR ordering engine 32 to navigate to or otherwise select "Residential Service” service item 72 from the product catalog of the LSP 12.
- PSR ordering engine 32 determines whether "Unbundled Port” service item 72 can be related back through "LSR Port” product specification 64 to "MapLSRPort” item type 56.
- "Unbundled Port” service item 72 does relate back to "MapLSRPort” item type 56.
- PSR ordering engine 32 therefore determines that values associated with DDLs 80 need to be collected and prompts user 34a to supply the DDL values.
- user 34a would be prompted to collect from end-user 14 and supply the LEAN and LEATN values for later mapping through to the LSR creation stage.
- the collection of these DDL values during the PSR creation stage reduces or eliminates the need for LSP personnel to contact the end-user 14 again during the subsequent LSR creation stage to obtain these values, which provides an important technical advantage.
- PSR ordering engine 32 may validate that appropriate DDL values (such as the LEAN and LEATN values) have been properly supplied before accepting PSR 40 as completed, even though these DDL values may not be required until the LSR creation stage.
- PSR ordering engine 32 communicates the completed PSR 40 to the LSR ordering engine 36 for creation of a suitable LSR 42 based on PSR 40. At least some information on PSR 40 is mapped through to the LSR 42.
- DDL values collected during the PSR creation stage (but not needed for PSR 40 itself) are mapped through to the LSR 42.
- the LSRs 42 to which DDL values are mapped may include multiple separate forms, each of which includes one or more fields populated with these DDL values.
- LSR 42 typically includes three forms - a "Port Services" form containing service specific information, a "Local Service Request" form that contains administrative information, and an "End User" form containing end-user related information.
- LSR ordering engine 36 evaluates each service item 72 on the PSR 40 to determine whether the service item 72 can be related back to an item type 56 in PSR item type hierarchy 50 with which DDL 80 is associated. If so, the LSR ordering engine 36 maps the DDL value to a service item 106 contained on the LSR 42 that corresponds to service item 72.
- the mapping between service item 72 and service item 106 may be according to any suitable pre-defined mapping relationship, according to particular needs.
Abstract
Description
Claims
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AU2002246935A AU2002246935A1 (en) | 2001-01-10 | 2002-01-04 | System and method for mapping information from end-user orders to the corresponding inter-provider orders |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/760,096 | 2001-01-10 | ||
US09/760,096 US7567923B2 (en) | 2001-01-10 | 2001-01-10 | System and method for mapping information collected in connection with creation of end-user orders for communications services to the corresponding inter-provider orders |
Publications (3)
Publication Number | Publication Date |
---|---|
WO2002058407A2 true WO2002058407A2 (en) | 2002-07-25 |
WO2002058407A3 WO2002058407A3 (en) | 2002-12-12 |
WO2002058407A8 WO2002058407A8 (en) | 2003-10-16 |
Family
ID=25058081
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2002/000162 WO2002058407A2 (en) | 2001-01-10 | 2002-01-04 | System and method for mapping information from end-user orders to the corresponding inter-provider orders |
Country Status (3)
Country | Link |
---|---|
US (1) | US7567923B2 (en) |
AU (1) | AU2002246935A1 (en) |
WO (1) | WO2002058407A2 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7797425B2 (en) | 2005-12-22 | 2010-09-14 | Amdocs Systems Limited | Method, system and apparatus for communications circuit design |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
TW200411465A (en) * | 2002-11-19 | 2004-07-01 | Xepa Corp | An accounting and management system for self-provisioning digital services |
GB2431067B (en) * | 2005-10-07 | 2008-05-07 | Cramer Systems Ltd | Telecommunications service management |
GB2432992B (en) * | 2005-11-18 | 2008-09-10 | Cramer Systems Ltd | Network planning |
GB2435362B (en) * | 2006-02-20 | 2008-11-26 | Cramer Systems Ltd | Method of configuring devices in a telecommunications network |
US20110150197A1 (en) * | 2009-12-17 | 2011-06-23 | Verizon Patent And Licensing, Inc. | System and method for providing automatic generation of a local service request |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO1998052321A1 (en) * | 1997-05-12 | 1998-11-19 | Evolving Systems, Inc. | Improved telecommunications systems and methods |
WO2000031985A1 (en) * | 1998-11-23 | 2000-06-02 | Koninklijke Kpn N.V. | Mediation of traffic in an intelligent network |
Family Cites Families (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5572653A (en) * | 1989-05-16 | 1996-11-05 | Rest Manufacturing, Inc. | Remote electronic information display system for retail facility |
DE69230905T2 (en) * | 1991-06-28 | 2000-08-17 | Ericsson Telefon Ab L M | USER MODULES IN TELECOMMUNICATION SYSTEMS |
US5610910A (en) * | 1995-08-17 | 1997-03-11 | Northern Telecom Limited | Access to telecommunications networks in multi-service environment |
US6473609B1 (en) * | 1995-12-11 | 2002-10-29 | Openwave Systems Inc. | Method and architecture for interactive two-way communication devices to interact with a network |
US5745681A (en) * | 1996-01-11 | 1998-04-28 | Sun Microsystems, Inc. | Stateless shopping cart for the web |
US5890175A (en) * | 1996-09-25 | 1999-03-30 | Wong; Garland | Dynamic generation and display of catalogs |
US6118777A (en) * | 1997-10-27 | 2000-09-12 | Nortel Networks Corporation | System and method for providing competing local exchange carriers unbundled access to subscriber access lines |
US6249773B1 (en) * | 1998-03-26 | 2001-06-19 | International Business Machines Corp. | Electronic commerce with shopping list builder |
US6249578B1 (en) * | 1998-04-06 | 2001-06-19 | Ameritech Corporation | Interactive electronic ordering for telecommunications products and services |
US6341271B1 (en) * | 1998-11-13 | 2002-01-22 | General Electric Company | Inventory management system and method |
US6718535B1 (en) * | 1999-07-30 | 2004-04-06 | Accenture Llp | System, method and article of manufacture for an activity framework design in an e-commerce based environment |
US6732167B1 (en) * | 1999-11-30 | 2004-05-04 | Accenture L.L.P. | Service request processing in a local service activation management environment |
US7069235B1 (en) * | 2000-03-03 | 2006-06-27 | Pcorder.Com, Inc. | System and method for multi-source transaction processing |
US20010044751A1 (en) * | 2000-04-03 | 2001-11-22 | Pugliese Anthony V. | System and method for displaying and selling goods and services |
US6732175B1 (en) * | 2000-04-13 | 2004-05-04 | Intel Corporation | Network apparatus for switching based on content of application data |
US7158953B1 (en) * | 2000-06-27 | 2007-01-02 | Microsoft Corporation | Method and system for limiting the use of user-specific software features |
US7778889B2 (en) * | 2000-08-31 | 2010-08-17 | The Softad Group, Llc | Modular e-commerce web site development system |
US20040111286A1 (en) * | 2001-12-21 | 2004-06-10 | Koenig Darren Andrew | System for the provision of goods and services over a distributed communication network |
-
2001
- 2001-01-10 US US09/760,096 patent/US7567923B2/en active Active
-
2002
- 2002-01-04 WO PCT/US2002/000162 patent/WO2002058407A2/en not_active Application Discontinuation
- 2002-01-04 AU AU2002246935A patent/AU2002246935A1/en not_active Abandoned
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO1998052321A1 (en) * | 1997-05-12 | 1998-11-19 | Evolving Systems, Inc. | Improved telecommunications systems and methods |
WO2000031985A1 (en) * | 1998-11-23 | 2000-06-02 | Koninklijke Kpn N.V. | Mediation of traffic in an intelligent network |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7797425B2 (en) | 2005-12-22 | 2010-09-14 | Amdocs Systems Limited | Method, system and apparatus for communications circuit design |
Also Published As
Publication number | Publication date |
---|---|
US20020091588A1 (en) | 2002-07-11 |
WO2002058407A3 (en) | 2002-12-12 |
AU2002246935A1 (en) | 2002-07-30 |
WO2002058407A8 (en) | 2003-10-16 |
US7567923B2 (en) | 2009-07-28 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10304098B2 (en) | Generation and execution of custom requests for quote | |
US6002854A (en) | Method and apparatus for configuring systems | |
US7188333B1 (en) | Product incompatibility system | |
JP3090435U (en) | A system for creating, executing, and maintaining business-to-business processes | |
US7440970B1 (en) | System and method for loading commercial web sites | |
US7043407B2 (en) | Method and apparatus for configuring systems | |
US20070124320A1 (en) | Modeling a data element | |
EP1175753B1 (en) | Telecommunications network resource handling arrangement and method | |
US8527369B1 (en) | Metadata-driven processing of supplemental data feeds | |
CN1347531A (en) | Method and system for connecting sevices to automated transaction machine | |
US7272577B1 (en) | System and method of calculating sales tax based upon geographic region | |
CN110222106A (en) | Integrated workflow and db transaction | |
CN107957867B (en) | Electric power retail market model modeling method and system | |
US20030101250A1 (en) | System and method for developing topography based management systems | |
WO2008081336A2 (en) | Technology platform for electronic commerce and a method thereof | |
US7567923B2 (en) | System and method for mapping information collected in connection with creation of end-user orders for communications services to the corresponding inter-provider orders | |
CN102253999A (en) | Verification method for service dependency | |
CN101188617A (en) | A flow service registration and discovery method | |
JP2023550884A (en) | Systems and methods for automatically configuring custom product selections based on user interaction | |
US7146351B2 (en) | System and method for analyzing software components using calibration factors | |
US20030163391A1 (en) | Computerized method, system and computer-readable medium for individualized ordering and billing of packages of goods | |
CN114371874A (en) | Configuration method, system, device and medium of Internet of things equipment | |
TWM591656U (en) | Service Reservation System | |
CN102467504A (en) | Design method of relational database-based workflow engine system | |
WO2006002699A2 (en) | Product modelling |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A2 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ OM PH PL PT RO RU SD SE SG SI SK SL TJ TM TN TR TT TZ UA UG UZ VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A2 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
AK | Designated states |
Kind code of ref document: A3 Designated state(s): AE AG AL AM AT AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ CZ DE DE DK DK DM DZ EC EE EE ES FI FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ OM PH PL PT RO RU SD SE SG SI SK SK SL TJ TM TN TR TT TZ UA UG UZ VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A3 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
CFP | Corrected version of a pamphlet front page | ||
CR1 | Correction of entry in section i |
Free format text: IN PCT GAZETTE 30/2002 DUE TO A TECHNICAL PROBLEM AT THE TIME OF INTERNATIONAL PUBLICATION, SOME INFORMATION WAS MISSING (81). THE MISSING INFORMATION NOW APPEARS IN THE CORRECTED VERSION. Free format text: IN PCT GAZETTE 30/2002 DUE TO A TECHNICAL PROBLEM AT THE TIME OF INTERNATIONAL PUBLICATION, SOME INFORMATION WAS MISSING (81). THE MISSING INFORMATION NOW APPEARS IN THE CORRECTED VERSION. |
|
REG | Reference to national code |
Ref country code: DE Ref legal event code: 8642 |
|
122 | Ep: pct application non-entry in european phase | ||
NENP | Non-entry into the national phase |
Ref country code: JP |
|
WWW | Wipo information: withdrawn in national office |
Country of ref document: JP |