Prediction-based telecommunications management subscription system

Through predicting the installation foundation, the problem of basic consistency of future date orders and order stacks in the telecom order management system is solved, ensuring that orders are executed in the predetermined order, reducing inconsistency and invalid orders, and achieving effective placing continuous orders by telecom operators sex.

CN119278462APending Publication Date: 2025-01-07TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280096358.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-07-06
Publication Date
2025-01-07

AI Technical Summary

Technical Problem

The existing telecom order management system is difficult to ensure the consistency and effectiveness of the installation foundation when processing orders and order stacks on future dates, resulting in potential inconsistent service configurations and invalid service charges.

Method used

By predicting the installation foundation, the installation foundation prediction for each order is calculated based on changes in unfinished orders and product/service life cycle changes, ensuring that the order is executed in a predetermined order and relies on the most accurate installation foundation status when executed.

Benefits of technology

The optimal approximate operation of the installation foundation when the telecom operator places continuous orders is achieved, reducing inconsistent and invalid orders, and avoiding undesired service configurations.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119278462A_ABST
    Figure CN119278462A_ABST
Patent Text Reader

Abstract

The invention discloses a management node for managing a plurality of orders. The management node comprises processing circuitry configured to: determine a first prediction of a current installation basis based on an execution date of a first order of the plurality of orders, the first order comprising at least one change to the current installation basis, and the plurality of orders being configured to execute in sequence; determining whether the first order is valid based on the determined first prediction of the current installation basis; and based on the determination of whether the first order is valid, rejecting or queuing the first order to execute at the execution date of the first order.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to a telecommunications managed subscription system, and in particular to a forecast-based telecommunications managed subscription system. Background Art

[0002] In a telecommunications subscription management system, a typical customer order is placed to add a new product / service or to modify an existing product / service. In addition to the customer on-boarding scenario where an order is placed for a new customer who has no previously installed products / services, other customer orders may rely on products / services that are already supplied and installed, which is called the customer's "installed base". A typical installed base may contain (multiple) customer contracts, active and inactive entities such as subscriptions, devices, voice and data services, discounts, etc. When a new order is initiated, the existing installed base is loaded to help ensure that changes to the new order can be applied and are compatible with the customer's most recent installed base. For example, if a customer's installed base does not include any data services, the customer may not be able to place an order to add an additional 5Gb of data usage.

[0003] It may be more optimal to have the most recent customer's installed base at the time of order creation and order fulfillment so order changes are applied to the live installed base. Otherwise, if there is no access to the customer's installed base or the installed base is out of date, a new order may trigger an invalid set of products / services, resulting in potentially inconsistent service configurations and invalid service charges.

[0004] There are scenarios where the installed base may change between the creation of an order and the time the order is fulfilled. It means that the order is executed with an outdated installed base or out of sync with the most recent persistent installed base, thus making the order change inconsistent with the customer's actual installed base.

[0005] The following are two situations where problems may arise in existing systems.

[0006] Future dated order: When an order is executed immediately after it is created, it is relatively safe to assume that the installed base of the order and the actual installed base in the persistence layer are in sync. However, if an order created today is set to execute in the future, there is no guarantee that the customer's installed base will remain the same until the execution date of the order. For example, between order creation and execution, the service expires based on its lifecycle or the installed base is modified externally through other channels (for example, the service is suspended due to collection).

[0007] Stack of orders: When multiple consecutive orders need to be placed, it becomes more challenging to make orders dependent only on the state of the installed base at the time of order creation. As an example, a customer wants to purchase a subscription package today while a promotion is in place, however they will not need it until they go to college in a month, so they request to purchase the subscription package, then immediately suspend it and resume the subscription package a month later. The account representative immediately places an order for the new subscription package, however it may take hours / days for the order to be completed as it requires special approval from the manager. It is not possible to place a second order to suspend the product while the subscription package is not offered to the installed base, and similarly, it is not possible to place a third order to resume it in the future. If the account representative creates the second order immediately, it will be loaded with the installed base of the most recent customer, which does not have a subscription package, and therefore no product to apply the suspension to. The account representative may need to wait until the subscription package is successfully offered and published to the installed base, and then create the suspension order. By the time the suspension order can be created, the subscription package is already active and may incur charges. Moreover, in order to create the "resume" order, the account representative may need to wait several hours / days until the suspension order is completed. Coordinating order placements one by one based on order fulfillment is a complex and expensive process for customer service. The scenario can be even more complex if a scheduled order needs to be created ahead of an existing future-dated order. For example, the same customer calls a few weeks later and requests a change to the data allowance for their subscription plan before resuming it. The new order is executed immediately to provide the new data allowance. However, when the resumed order runs a few weeks later, it overwrites the new allowance configuration with the old value, resulting in an undesired subscription plan configuration.

[0008] Therefore, existing order management systems are not without problems. Summary of the invention

[0009] Some embodiments preferably provide methods, systems and apparatus for telecommunications order management.

[0010] When an order is set to be executed in the future, a forecast is created that assumes not the most recent installed base but the expected installed base at the time the order is executed. The forecast is calculated taking into account changes in one or more (e.g., all) other orders from the customer's backlog that are expected to execute before the order, and in some embodiments, based on estimated life cycle changes of existing products and services.

[0011] One or more embodiments described herein relate to implementing a customer's future orders as a stack of orders sorted by execution date, where the first order is based on the actual installed base, and the installed base of each successive order is a forecast of the installed base resulting from the previous order in the queue. If each order is executed strictly in the order of its position in the queue, and each order starts when the previous order in the queue is completed, then the forecast of the installed base of the order is a close approximation of the real-time installed base. The scheme supports a further scenario of inserting a new order at any position in an established order queue. In this case, the inserted order is positioned in the queue based on its requested start date, a forecast based on the previous order is created, and a re-forecast of the subsequent order is triggered.

[0012] The order stack ensures that future-dated orders are created based on the best approximation of the expected installed base at the time the order is executed. It also supports the creation of multiple future-dated orders, where each order depends on changes from previously unexecuted orders, and the application of actions that take into account these previously unexecuted changes, even though they are not yet available in real time.

[0013] In one or more embodiments, an order is not based on the state of the installed base at the time the order is created. Instead, it should rely on a forecast of the installed base at the scheduled execution time of the order. This forecast is calculated based on one or more of the following factors:

[0014] 1. A change in an order from one or more (eg, all) customers that is scheduled to be executed before the current order.

[0015] 2. Existing product / service lifecycle transitions, such as scheduled activation or expiration.

[0016] Multiple future-dated orders for a customer can be viewed as an order stack, where each order calculates its installed base from the preceding order.

[0017] When a new order is created and scheduled to run after the outstanding customer's order(s), it should be based on the forecasts from these previous orders.

[0018] When new orders are created and scheduled to run before other future dated orders, changes to current orders are propagated to the installed base of these subsequent orders. In other words, the subsequent orders recalculate the installed base forecast and reapply order changes to take effect or validate one or more orders / changes. Typically, only uncompleted orders are considered, as completed orders already provide changes in the live installed base.

[0019] One or more embodiments described herein are executed with stacked orders running continuously, each order waiting for the previous order to be successfully completed. When these conditions are implemented programmatically or otherwise, it can be said with certainty that the orders are running with the best approximation of the customer's installed base.

[0020] According to one aspect of the present application, a management node for managing a plurality of orders is provided. The management node includes a processing circuit configured to determine a first forecast of a current installed base based on an execution date of a first order in the plurality of orders, the first order including at least one change to the current installed base. The plurality of orders are configured to be executed sequentially. The processing circuit is further configured to determine whether the first order is valid based on the determined first forecast of the current installed base; and then, based on the determination of whether the first order is valid, reject or queue the first order for execution on the execution date of the first order.

[0021] According to some embodiments of this aspect, the processing circuit is further configured to determine a second forecast of the current installed base based on a fulfillment date of a second order in the plurality of orders, the second order comprising at least one change to the current installed base. According to some embodiments of this aspect, the second order is prior to the first order in sequence, and the determination of whether the first order is valid is further based on the determined second forecast of the current installed base. According to some embodiments of this aspect, the second order is subsequent to the first order in sequence, and the determination of whether the second order is valid is further based on the determined first forecast of the current installed base.

[0022] According to some embodiments of this aspect, the order is chronologically arranged based on an execution date of each of the plurality of orders. According to some embodiments of this aspect, the processing circuit is further configured to determine a forecast for each of the plurality of orders, each of the forecasts for each of the plurality of orders including at least one change to the current installed base. According to some embodiments of this aspect, determining whether the first order is valid is also based on the forecast determined for each of the plurality of orders. According to some embodiments of this aspect, determining whether the first order is valid is also based on an evaluation of each of the forecasts determined for each of the plurality of orders, the evaluation being based on the execution order of the plurality of orders.

[0023] According to another aspect of the present application, a method for managing a plurality of orders implemented by a management node is provided. A first forecast of a current installed base is determined based on an execution date of a first order in the plurality of orders, the first order including at least one change to the current installed base, and the plurality of orders are configured to be executed in sequence. A determination is performed as to whether the first order is valid based on the determined first forecast of the current installed base, and based on the determination of whether the first order is valid, the first order is rejected or queued for execution on the execution date of the first order.

[0024] According to some embodiments of this aspect, a second forecast of the current installed base is determined based on a fulfillment date of a second order in the plurality of orders, the second order including at least one change to the current installed base.

[0025] According to some embodiments of this aspect, the second order precedes the first order in sequence, and the determination of whether the first order is valid is also based on the determined second forecast of the current installed base. According to some embodiments of this aspect, the second order follows the first order in sequence, and the determination of whether the second order is valid is also based on the determined first forecast of the current installed base. According to some embodiments of this aspect, the sequence is chronologically arranged based on the execution date of each of the multiple orders. According to some embodiments of this aspect, a forecast for each of the multiple orders is determined, and each of the forecasts for each of the multiple orders includes at least one change to the current installed base.

[0026] According to some embodiments of this aspect, determining whether the first order is valid is further based on a forecast determined for each of the plurality of orders. According to some embodiments of this aspect, determining whether the first order is valid is further based on an evaluation of each of the forecasts determined for each of the plurality of orders, the evaluation being based on an order of execution of the plurality of orders.

[0027] According to another aspect of the present application, a computer-readable medium stores an executable program, the executable program including instructions, the instructions being configured to cause a processing circuit to determine a first forecast of a current installed base based on an execution date of a first order among a plurality of orders, the first order including at least one change to the current installed base, and the plurality of orders being configured to be executed sequentially, determining whether the first order is valid based on the determined first forecast of the current installed base, and rejecting or queuing the first order for execution on the execution date of the first order based on the determination of whether the first order is valid.

[0028] According to some embodiments of this aspect, the instructions are further configured to cause the processing circuit to determine a second forecast of the current installed base based on a fulfillment date of a second order in the plurality of orders, the second order comprising at least one change to the current installed base. According to some embodiments of this aspect, the second order is prior to the first order in sequence, and the determination of whether the first order is valid is further based on the determined second forecast of the current installed base. According to some embodiments of this aspect, the second order is subsequent to the first order in sequence, and the determination of whether the second order is valid is further based on the determined first forecast of the current installed base.

[0029] One or more advantages of one or more embodiments include: enabling future dated orders to be run based on installed base forecasts, enabling telecommunications operators to place a series of consecutive orders and run them based on the best forecast of the installed base, and minimizing inconsistent customers' installed bases, invalid orders, and undesirable service configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] The full meaning of the present embodiment and its attendant advantages and features will be more readily understood by referring to the following detailed description in conjunction with the accompanying drawings, in which:

[0031] Figure 1 is a schematic diagram of an example system according to some embodiments of the present application;

[0032] Figure 2 is a block diagram of several entities according to some embodiments of the present application;

[0033] Figure 3 is a flowchart of an example process in a management node according to some embodiments of the present application;

[0034] Figure 4 is a schematic diagram of an example network architecture according to some embodiments of the present application;

[0035] Figure 5 is a flowchart of an example process according to some embodiments of the present application;

[0036] Figure 6 is a timeline diagram of execution dates of orders according to some embodiments of the present application;

[0037] Figure 7 is a timeline diagram of execution dates of orders according to some embodiments of the present application;

[0038] Figure 8 is a timeline diagram of a customer's installed base according to some embodiments of the present application; and

[0039] Fig. 9is a timeline diagram of a customer's installed base according to some embodiments of the present application. DETAILED DESCRIPTION

[0040] As described above, existing telecom order management systems may not operate properly during various scenarios because orders are typically based on an installed base snapshot at the time the order is created, yet when the order is executed, the installed base has changed due to other orders or by other channels or by natural life cycle transitions within the product / service.

[0041] One or more embodiments of the present application solve at least one problem with existing systems by determining and using, for example, a forecast of the installed base. For example, when an order is set to be executed in the future, it is created not by assuming the most recent installed base but rather a forecast of the installed base expected at the time the order is executed. The forecast is calculated taking into account the change in outstanding orders from all other customers expected to be executed before the order and the estimated life cycle change of existing products and services.

[0042] Before describing the exemplary embodiments in detail, it is noted that the embodiments reside primarily in combinations of device components and process steps related to a telecommunications subscription management system. Therefore, conventional symbols are used in the drawings to represent components as appropriate, and only those specific details relevant to understanding the embodiments are shown to avoid obscuring the present application with those details that would be obvious to those of ordinary skill in the art having the benefit of the description herein.

[0043] As used herein, relational terms, such as "first" and "second", "top" and "bottom", etc., can be used individually to distinguish one entity or element from another entity or element, without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terms used herein are only used for the purpose of describing specific embodiments and are not intended to limit the concepts described herein. As used herein, the singular forms "a, an" and "the" are intended to also include plural forms, unless the context clearly indicates otherwise. It will be further understood that the terms "include", "have" and / or "comprise" when used herein refer to the presence of the features, wholes, steps, operations, elements and / or components mentioned, without excluding the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or combinations thereof.

[0044] In the embodiments described herein, connection terms "in communication with" and the like may be used to indicate electrical or data communication, which may be achieved, for example, by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling, or optical signaling. Those of ordinary skill in the art will appreciate that multiple components may interoperate, and modifications and variations in achieving electrical and data communication are possible.

[0045] In some embodiments described herein, the terms "coupled," "connected," and the like may be used herein to indicate a connection, although not necessarily a direct connection, and may include wired and / or wireless connections.

[0046] In some embodiments, a general description expression of the form "one of A and B" corresponds to A or B. In some embodiments, at least one of A and B corresponds to A, B, or AB, or corresponds to one or more of A and B. In some embodiments, at least one of A, B, and C corresponds to one or more of A, B, and C, and / or A, B, C, or a combination thereof.

[0047] The terms used herein are only used for the purpose of recording specific embodiments and are not intended to limit the concepts described herein. As used herein, the singular forms of "a, an" and "the" are intended to also include plural forms unless the context clearly states otherwise. It will be further understood that the terms "include", "have" and / or "comprise" when used herein refer to the presence of the features, wholes, steps, operations, elements and / or components mentioned, and do not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or combinations thereof.

[0048] Further note that the functions recorded herein as being performed by a device or management node may be distributed across multiple devices and / or management nodes. In other words, it is contemplated that the functions of the management nodes and devices recorded herein are not limited to being performed by a single physical device, and in fact, may be distributed across several physical devices.

[0049] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as those commonly understood by those of ordinary skill in the art to which this application belongs. It will be further understood that the terms used herein should be interpreted as having a meaning consistent with their meaning in the context of this specification and the relevant field, and will not be interpreted in an idealized or overly formal sense unless explicitly defined as such herein.

[0050] Referring to the drawings, wherein like elements are designated by like reference numerals, Figure 1 1 is a schematic diagram of a communication system 10. The system 10 includes a customer service node 12, a management node 14, and a service registration node 16, which can communicate with each other and / or with other nodes in the system 10 via a network 18. The connection to and / or from the network 18 can be a wired or wireless connection.

[0051] In particular, the customer service node 12 is configured to perform one or more functions described herein. For example, the customer service node 12 is configured to interface with a customer service representative to facilitate creating an order based on, for example, a request from a subscriber 20. The management node 14 is configured to perform one or more functions described herein. For example, the management node 14 is configured to manage orders as described herein. The management node 14 is configured to include a prediction and verification unit 22, which is configured to perform one or more management node 14 functions described herein, such as determining a prediction of an order and determining whether the order is valid based on the prediction, as described herein. The service registration node 16 is configured to perform one or more functions as described herein. For example, the service registration node 16 can store an installed base of users / subscribers.

[0052] Now refer to Figure 2 An example implementation of the management node 14 and the customer service node 12 discussed in the preceding paragraphs is described according to an embodiment.

[0053] System 10 includes a management node 14 provided in system 10 and includes hardware 28 that enables it to perform one or more functions described herein. Hardware 28 may include a communication interface 30 for communicating with one or more nodes / devices in system 10 (eg, with customer service node 12).

[0054] In the illustrated embodiment, the hardware 28 of the management node 14 further includes a processing circuit 32. The processing circuit 32 may include a processor 36 and a memory 34 (e.g., a computer-readable medium, a non-transitory computer-readable medium, etc.). In particular, in addition to or alternatively to a processor such as a central processing unit and a memory, the processing circuit 32 may include an integrated circuit for processing and / or control, for example, one or more processors and / or processor cores and / or an FPGA (field programmable gate array) and / or an ASIC (application-specific integrated circuit) adapted to execute instructions. The processor 36 may be configured to access (e.g., write and / or read) the memory 34, which may include any kind of volatile and / or non-volatile memory, for example, a cache and / or buffer memory and / or a RAM (random access memory) and / or a ROM (read-only memory) and / or an optical memory and / or an EPROM (erasable programmable read-only memory).

[0055] Thus, the management node 14 further has software 24, which is stored internally, for example, in a memory 34, or stored in an external memory (e.g., a database, a storage array, a network storage device, etc.) that the management node 14 can access via an external connection. The software 24 may include a management application 26 and may be executed by a processing circuit 32. The processing circuit 32 may be configured to control any method and / or process described herein, and / or to cause such a method and / or process to be executed, for example, by the management node 14. The processor 36 corresponds to one or more processors 36 for performing the functions of the management node 14 described herein. The memory 34 is configured to store data, programming software code, and / or other information described herein. In some embodiments, the software 24 may include instructions that, when executed by the processor 36 and / or the processing circuit 32, cause the processor 36 and / or the processing circuit 32 to perform the processes described herein related to the management node 14. For example, the processing circuit 32 of the management node 14 may include a prediction and verification unit 22 that is configured to perform one or more functions described herein, such as regarding, for example, prediction and verification of orders.

[0056] With respect to the customer service node 12, in the illustrated embodiment, the hardware 42 of the customer service node 12 further includes a processing circuit 46. The processing circuit 46 may include a processor 50 and a memory 48 (e.g., a computer-readable medium, a non-transitory computer-readable medium, etc.). In particular, in addition to or in lieu of a processor such as a central processing unit and a memory, the processing circuit 46 may include an integrated circuit for processing and / or control, for example, one or more processors and / or processor cores and / or an FPGA (field programmable gate array) and / or an ASIC (application-specific integrated circuit) adapted to execute instructions. The processor 50 may be configured to access (e.g., write and / or read) the memory 48, which may include any kind of volatile and / or non-volatile memory, for example, a cache and / or buffer memory and / or a RAM (random access memory) and / or a ROM (read-only memory) and / or an optical memory and / or an EPROM (erasable programmable read-only memory).

[0057] The customer service node 12 further has software 38, which is stored internally, for example, in a memory 48, or stored in an external memory (e.g., a database, a storage array, a network storage device, etc.) that the customer service node 12 can access via an external connection. The software 38 may include a customer service application 40 and may be executed by a processing circuit 46. The processing circuit 46 may be configured to control any method and / or process described herein, and / or cause such a method and / or process to be performed, for example, by the customer service node 12. The processor 50 corresponds to one or more processors 50 for performing the functions of the customer service node 12 described herein. The memory 48 is configured to store data, programming software code, and / or other information described herein. In some embodiments, the software 38 may include instructions that, when executed by the processor 50 and / or the processing circuit 46, cause the processor 50 and / or the processing circuit 46 to perform the processes described herein related to the management node 14. The customer service node 12 is configured to perform one or more functions described herein, such as regarding, for example, providing customer service functions. In some embodiments, the internal workings of the management node 14 and the customer service node 12 may be as described herein. Figure 2 shown, and independently, the surrounding network topology can be Figure 1 network topology.

[0058] although Figure 1 and Figure 2 The prediction and verification unit 22 is shown as being within a corresponding processor, but it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuit. In other words, the unit may be implemented in hardware or a combination of hardware and software within the processing circuit.

[0059] Figure 3 1 is a flow chart of an example process in a management node 14 according to one or more embodiments of the present application. One or more blocks described herein may be executed by one or more elements of the management node 14, such as by one or more of the processing circuit 32 (including the prediction and verification unit 22), the processor 36, and / or the communication interface 30. The management node 14 is configured to determine (block S100) a first forecast of a current installed base based on an execution date of a first order in a plurality of orders, wherein the first order includes at least one change to the current installed base, and the plurality of orders are configured to be executed sequentially. The management node 14 is also configured to determine (block S102) whether the first order is valid based on the determined first forecast of the current installed base. The management node 14 is also configured to reject or queue (block S104) the first order for execution on the execution date of the first order based on the determination of whether the first order is valid.

[0060] In at least one embodiment, the processing circuitry 32 is further configured to determine a second forecast of the current installed base based on a fulfillment date of a second order in the plurality of orders, wherein the second order includes at least one change to the current installed base. In at least one embodiment, the second order precedes the first order in sequence, and the determination of whether the first order is valid is further based on the determined second forecast of the current installed base. In at least one embodiment, the second order follows the first order in sequence, and the determination of whether the second order is valid is further based on the determined first forecast of the current installed base. In at least one embodiment, the order is chronologically ordered based on the fulfillment date of each of the plurality of orders.

[0061] In at least one embodiment, the processing circuitry 32 is further configured to determine a forecast for each of the plurality of orders, each of the forecasts for each of the plurality of orders including at least one change to the current installed base. In at least one embodiment, determining whether the first order is valid is further based on the forecast determined for each of the plurality of orders. In at least one embodiment, determining whether the first order is valid is further based on an evaluation of each of the forecasts determined for each of the plurality of orders, the evaluation being based on an order of execution of the plurality of orders.

[0062] Having described the general flow of arrangements of the present application and provided examples of hardware and software arrangements for implementing the processes and functions of the present application, the following section provides details and examples of arrangements for a telecommunications subscription management system.

[0063] Some embodiments provide a telecommunications subscription management system. One or more management node 14 functions described herein may be performed by one or more of processing circuitry 32, processor 36, prediction and verification unit 22, etc. One or more customer service node 12 functions described herein may be performed by one or more of processing circuitry 46, processor 50, etc.

[0064] Figure 4 is a schematic diagram showing another example of a network architecture of a communication system according to the principles disclosed herein. Figure 4 In the embodiment of the present invention, the customer service node 12 is configured to communicate with the management node 14. The customer service node 12 may include a user interface (not shown). The user interface provides one or more functions as described herein, and may expose (e.g., allow access to) a customer's installed base, allow changes to the installed base via new orders, and provide a catalog of available products and services and associated pricing, and allow personalization of data.

[0065] The management node 14 is configured to communicate with the service registration node 16 and the order database 15. The management node 14 acts as a layer between the user interface of the customer service node 12 and the order management engine (i.e., part of the management node 14) for various functions as described herein, including the creation, management, verification, pricing and triggering execution of orders. The order management engine can be responsible for reading / creating / and updating order entities. The order management engine provides one or more functions as described herein and can support the pricing and verification of orders, and trigger order execution based on the respective scheduled times of the orders and other factors.

[0066] The service registry node 16 is configured to communicate with the installed base database 17. The service registry node 16 provides one or more functions as described herein, and can manage the customer's installed base, read existing installed base products and services, publish changes to the installed base, and support queries, and / or perform other functions described herein. The query can have filters that can be used.

[0067] One or more embodiments described herein are implemented on the concept of stacked orders: a series of orders are issued for execution in sequence, where each order is based on a computed forecast of the installed base at its execution time, rather than a recent installed base snapshot from a persistent layer. The series of orders may be referred to as a "stack", and each order has a strict position in the stack based on its scheduled execution time.

[0068] When forming a forecast:

[0069] 1) Calculate a forecast of the installed base for each order based on expected changes from previous orders in the stack; and / or

[0070] 2) Installed base forecasts also take into account scheduled lifecycle changes of installed base products, such as products expected to expire or be activated at a specific point in time.

[0071] Note: The first order in the stack depends on the installed base loaded from the persistence layer. A single order can be considered a stack of orders. If the order is not executed immediately but in the future, (2) (prediction based on lifecycle changes) can still be considered. In one or more embodiments, a stack can be associated with a customer or subscriber.

[0072] Figure 5is an example signaling diagram according to some embodiments of the present application. The customer service node 12 creates an order with a future date (e.g., the current order) and sends the order to the management node 14 (S200). The management node 14 analyzes the customer's stack of unstarted orders and places the current order in a position in the stack based on its requested start date (e.g., execution date) (S202). In one or more embodiments, if the order is the first in the stack, the management node 14 requests the customer's installed base for loading and receives the customer's installed base returned from the service registration node 16 (S204). The management node 14 updates the loaded installed base by, for example, predicting lifecycle changes expected to occur on the order start date (S206).

[0073] In one or more other embodiments, the management node 14 creates the installed base from the forecast at least in part by 1) calculating the expected installed base state after the previous order in the stack is executed, and 2) applying the lifecycle changes expected to occur on the order start date. The customer service node 12 can make new order changes (e.g., add / change items, etc.) and indicate these changes to the management node 14, where the management node 14 returns the order to the customer service node 12 (S212). In one or more embodiments, S212 can be executed in a logical loop. The customer service node 12 submits the order to the management node 14 (S214).

[0074] The management node 14 recalculates and validates the installed base forecast for subsequent orders in the stack as described herein (S216). In one or more embodiments, S216 is executed in a logic loop until the last order in the stack is reached or until the re-forecast results in an invalid order. The customer service node 12 returns an exception to the management node 14 that the order is invalid (S218). The management node 14 submits the order so that the order is ready to be executed when the scheduled time for the order is reached (S220). The management node 14 returns the order to the customer service node 12 (S222).

[0075] Now describe and Figure 5 When a new order is issued (S200), the management node then analyzes the customer's stack of unexecuted orders and places the current order in the stack based on its start date (i.e., execution date). There are then two scenarios to analyze (S202):

[0076] - This is the first outstanding customer order and will be the first order in the stack. The management node 14 loads the customer's installed base by communicating with the service registration node 16. The management node 14 creates a stack with a single order (S204). The order installed base is from the persisted installed base. If the order is scheduled for a future date, the management node 14 predicts the installed base based on possible product / service lifecycle changes (S206).

[0077] - The customer already has an uncompleted order in the stack. The management node inserts a new order in the stack based on the requested start date / execution date of the order and returns the order (S208).

[0078] o If it is not the first order in the stack, the installed base for the new order is derived from a forecast assuming successful execution of the previous order plus an estimated lifecycle variation (S210).

[0079] o If there are other orders after the new order, they are re-predicted based on the new order changes (S216). If the re-prediction detects a conflict, the entire order stack should be invalidated before it provides an invalid service configuration.

[0080] The customer service node 12 communicates with the management node 14 to make new order changes, such as adding or changing items (S212). If necessary, this can be performed multiple times in a loop (i.e., a logical loop) until the changes are made. The customer service node 12 then submits the order to the management node 14 (S214).

[0081] The management node 14 then recalculates the installed base forecast for each successive order in the stack and makes it valid (S216).

[0082] One or more embodiments described herein help ensure that future dated orders and order stacks are run using the best approximation (e.g., the most accurate approximation) of the installed base at their execution time. Also, if there are inconsistencies or conflicts between orders or with the persistent installed base, they are detected early at order creation and can be resolved by returning an exception in the case of an invalid order before inconsistent changes are provided and irreversible behavior occurs (S218). If there are no inconsistencies, the order is submitted and ready for execution when the order scheduled time / execution time arrives (S220), and returns (S222).

[0083] The following example(s) describe how one or more embodiments described herein may be used to: Figures 6 to 8 Used in the specific scenario shown in the figure.

[0084] John Doe (someone) is preparing to temporarily relocate from Toronto, Ontario to Montreal, Quebec to complete graduate studies, and he wants to set up his mobile phone configuration in advance. On December 15, 2021, John Doe calls his mobile carrier and requests to terminate his current Ontario plan and activate a new Quebec voice plan starting January 1, 2022. He also requests that his new Quebec voice plan be suspended on June 1, 2022, because he will be traveling abroad during the upcoming summer.

[0085] The operator accepts the request and creates 2 future dated orders. Order 1 is created to terminate the Ontario Voice plan and activate the new Quebec Voice plan and is scheduled to run on January 1, 2022. Order 2 suspends the Quebec Voice plan and is scheduled to run on June 1, 2022. In the timeline diagram as the execution dates of Order 1 and Order 2 Figure 6 This situation is shown in . Figure 6 Depicted is John Doe's order stack after December 15, 2021, according to the aforementioned example. Order 1 has an ID of 001, a start date of January 1, 2022, a creation date of December 15, 2021, does not refer to a previous order (i.e., the PrevOrder field is empty), and points to Order ID 002 as the next order. It terminates the Ontario Voice Plan and activates the Quebec Voice Plan. Order 2 has an ID of 002, a start date of June 1, 2022, a creation date of December 15, 2021, and points to Order ID 001 as the previous order, but does not refer to a next order (i.e., the NextOrder field is empty). It suspends the Quebec Voice Plan.

[0086] A few days later, on December 20, 2022, John Doe calls the operator again and requests to add the "100 minutes of long distance calls for $10" add-on to his subscription package starting January 3, 2022. The operator creates Order 3 scheduled for January 3, 2022, and adds the add-on to the Quebec Voice Plan, as shown in the following figure: Figure 7 As shown, the Figure 7 is a timeline diagram of the execution dates of the above-mentioned Order 1, Order 2 and Order 3 according to one or more embodiments of the present application. Specifically, Figure 7 The above example describes John Doe's order stack after December 20, 2021. Order 3 is inserted between orders 1 and 2. Order 3 has an ID of 003, a start date of January 3, 2022, a creation date of December 20, 2021, and points to order ID 001 as the previous order and order ID 002 as the next order. Order 1 has been changed to point to 003 as the next order, and order 2 has been changed to point to 003 as the previous order.

[0087] Figure 8 is a timeline diagram of an installed base of customers according to one or more embodiments of the present application. Figure 8 The status of John Doe's services, such as his voice plan and long distance minutes, according to the previous example is depicted.

[0088] Fig. 9 is a diagram that processes the foregoing example scenario without using one or more embodiments described herein. It depicts John Doe's service status, such as his voice plan and long distance minutes. Because the orders are not predicted according to the functionality described herein, they do not have a PrevOrder or NextOrder field.

[0089] First, the mobile operator cannot place two consecutive future-dated orders: Order 1 and Order 2. The customer service representative would place Order 1 but not Order 2 because the new voice plan is not yet in the installed base, so there is nothing to suspend for Order 2. John Doe would need to call again to place the suspension request after January 1, 2022, when the Quebec voice plan is activated and in the installed base. Implementing such a suspension request can become challenging once the customer's request is a series of multiple, complex orders that need to be executed one after the other without delay.

[0090] For the same reason, the "100 Long Distance Minutes" additional order needs to be added after January 1, 2022. Assume that John Doe calls on January 2, 2022 and places a "Pause" order scheduled for June 1, 2022. Later that day, John Doe realizes that he may be able to take advantage of the "100 Long Distance Minutes" and calls again to place Order 3 (Additional) for execution on January 3, 2022, before the "Pause" order. Additional Order 3 runs successfully, adding the required number of long distance minutes to the customer's subscription package on a monthly basis.

[0091] On June 1, 2022, when it is time to run the scheduled "pause" order, problems will arise. Typically, the lifecycle of an "add-on plan" is aligned with the lifecycle of the main plan because the add-on plans use the same services as the main plan. When a plan is paused or deactivated, all connected add-ons are also paused or deactivated. Back Fig. 9In the example of , the pause order is unaware that an "Add-on Plan" was added to the voice plan after the pause order was created. Therefore, when Order 3 runs, it only pauses the voice plan, while keeping the add-on product active. Depending on how the mobile operator handles this, this could cause a variety of scenarios, from subscription issues to unnecessary charges for products that cannot be provided. Therefore, there are several drawbacks to approaches that do not use one or more of the embodiments described herein.

[0092] Although the above examples are of low complexity, it should be understood that in more complex use cases, similar problems arise, resulting in orders not being fulfilled or being fulfilled with unexpected or unintended results, and one or more embodiments of the present application are able to determine these invalid orders before they are implemented.

[0093] As will be appreciated by those skilled in the art, the concepts described herein may be embodied as methods, data processing systems, computer program products, and / or computer storage media storing executable computer programs. Thus, the concepts described herein may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects, all of which are generally referred to herein as "circuits" or "modules". Any process, step, action, and / or function described herein may be performed and / or associated with a corresponding module, which may be implemented in software and / or firmware and / or hardware. In addition, the present application may take the form of a computer program product on a tangible computer-usable storage medium having a computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer-readable medium may be utilized, including a hard disk, a CD-ROM, an electronic storage device, an optical storage device, or a magnetic storage device.

[0094] Some embodiments are described herein with reference to flowcharts and / or block diagrams of methods, systems, and computer program products. It should be understood that each block in the flowcharts and / or block diagrams and combinations of blocks in the flowcharts and / or block diagrams can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer (to thereby create a special-purpose computer), a special-purpose computer, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device create the instructions for implementation in the flowcharts and / or block diagrams. Figure 1 A device that specifies a function / action in one or more boxes.

[0095] These computer program instructions may also be stored in a computer-readable memory or storage medium, which may guide a computer or other programmable data processing device to function in a specific manner, so that the instructions stored in the computer-readable memory generate instructions including implementing the flowchart and / or block diagram. Figure 1An article of manufacture that is an instruction means for performing the functions / actions specified in one or more blocks.

[0096] Computer program instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are performed on the computer or other programmable device to produce a computer-implemented process, such that the instructions executed on the computer or other programmable device provide steps for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram.

[0097] It should be understood that the functions / actions indicated in the blocks may not occur in the order indicated in the operational diagram. For example, two blocks shown in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in the reverse order, depending on the functions / actions involved. Although some figures include arrows on communication paths to illustrate the primary direction of communication, it should be understood that communication may occur in the direction opposite to the arrows depicted.

[0098] Computer program code for carrying out operations of the concepts described herein may be written in languages ​​such as Python, Or C++ object-oriented programming language is written. However, the computer program code for performing the operation of the present application can also be written in a conventional procedural programming language, such as "C" programming language. The program code can be executed completely on the user's computer, partly on the user's computer, as an independent software package, partly on the user's computer and partly on a remote computer or completely on a remote computer. In the latter case, the remote computer can be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (for example, by using the Internet of an Internet service provider).

[0099] Many different embodiments have been disclosed herein in conjunction with the above description and accompanying drawings. It should be understood that literally describing and illustrating every combination and sub-combination of these embodiments would be overly repetitive and confusing. Therefore, all embodiments may be combined in any manner and / or combination, and this specification (including the accompanying drawings) should be interpreted as constituting a complete written description of all combinations and sub-combinations of the embodiments described herein and the manner and process of making and using them, and should support claims for any such combination or sub-combination.

[0100] Those skilled in the art will appreciate that the embodiments described herein are not limited to what has been specifically shown and described above. In addition, unless otherwise mentioned above, it should be noted that all drawings are not to scale. Various modifications and variations according to the above teachings are possible without departing from the scope of the appended claims.

Claims

1. A management node (14) for managing a plurality of orders, the management node (14) comprising: The processing circuit (32) is configured to: determining a first forecast of the current installed base based on an execution date of a first order in the plurality of orders, the first order including at least one change to the current installed base, and the plurality of orders being configured to be executed sequentially; determining whether the first order is valid based on the determined first forecast of the current installed base; as well as Based on the determination of whether the first order is valid, the first order is rejected or queued for execution on an execution date of the first order.

2. The management node (14) according to claim 1, wherein: The processing circuit (32) is further configured to determine a second forecast of the current installed base based on a fulfillment date of a second order in the plurality of orders, the second order including at least one change to the current installed base.

3. The management node (14) according to claim 2, wherein: The second order precedes the first order in sequence, and the determination of whether the first order is valid is further based on the determined second forecast of the current installed base.

4. The management node (14) according to claim 2, wherein: The second order is sequentially subsequent to the first order, and the determination of whether the second order is valid is further based on the determined first forecast of the current installed base.

5. The management node (14) according to any one of claims 1 to 4, wherein: The order is chronologically arranged based on an execution date of each order in the plurality of orders.

6. The management node (14) according to any one of claims 1 to 5, wherein: The processing circuitry (32) is further configured to determine a forecast for each of the plurality of orders, each of the forecasts for each of the plurality of orders including at least one change to the current installed base.

7. The management node (14) according to claim 6, wherein: Determining whether the first order is valid is also based on a forecast determined for each of the plurality of orders.

8. The management node (14) according to claim 7, wherein: Determining whether the first order is valid is also based on evaluating each of the determined predictions for each of the plurality of orders, the evaluation being based on an order of execution of the plurality of orders.

9. A method for managing a plurality of orders implemented by a management node (14), the method comprising: determining ( S100 ) a first forecast of a current installed base based on an execution date of a first order of the plurality of orders, the first order including at least one change to the current installed base, and the plurality of orders being configured to be executed sequentially; Based on the determined first forecast of the current installed base, determining (S102) whether the first order is valid; as well as Based on the determination of whether the first order is valid, the first order is rejected or queued (S104) for execution on the execution date of the first order.

10. The method of claim 1, further comprising determining a second forecast of the current installed base based on a fulfillment date of a second order in the plurality of orders, the second order including at least one change to the current installed base.

11. The method according to claim 2, wherein: The second order precedes the first order in sequence, and the determination of whether the first order is valid is further based on the determined second forecast of the current installed base.

12. The method according to claim 2, wherein: The second order is sequentially subsequent to the first order, and the determination of whether the second order is valid is further based on the determined first forecast of the current installed base.

13. The method according to any one of claims 1 to 4, wherein: The order is chronologically arranged based on an execution date of each order in the plurality of orders.

14. The method of any one of claims 1-5, further comprising determining a forecast for each of the plurality of orders, each of the forecasts for each of the plurality of orders comprising at least one change to the current installed base.

15. The method according to claim 6, wherein: Determining whether the first order is valid is also based on a forecast determined for each of the plurality of orders.

16. The method according to claim 7, wherein: Determining whether the first order is valid is also based on evaluating each of the determined predictions for each of the plurality of orders, the evaluation being based on an order of execution of the plurality of orders.

17. A computer readable medium (34) storing an executable program, the executable program comprising instructions configured to cause a processing circuit (32): determining a first forecast of the current installed base based on an execution date of a first order in the plurality of orders, the first order including at least one change to the current installed base, and the plurality of orders being configured to be executed sequentially; determining whether the first order is valid based on the determined first forecast of the current installed base; as well as Based on the determination of whether the first order is valid, the first order is rejected or queued for execution on an execution date of the first order.

18. The computer readable medium (34) of claim 17, wherein: The instructions are further configured to cause the processing circuit (32) to determine a second forecast of the current installed base based on a fulfillment date of a second order in the plurality of orders, the second order including at least one change to the current installed base.

19. The computer readable medium (34) of claim 18, wherein: The second order precedes the first order in sequence, and the determination of whether the first order is valid is further based on the determined second forecast of the current installed base.

20. The computer readable medium (34) of claim 18, wherein: The second order is sequentially subsequent to the first order, and the determination of whether the second order is valid is further based on the determined first forecast of the current installed base.