Centralized Market Platform for Telecommunications-Related Services

Abstract

A method, system, apparatus, and computer-readable medium for trading telecommunications-related services on a centralized market network. The method includes presenting a first telecommunications-related service to a first user, the first telecommunications-related service being based on a configuration profile defined by a second user. The method further includes receiving a selection of the first telecommunications-related service by the first user and receiving a purchase order request from the first user regarding the selected first telecommunications-related service. The method may also include receiving input from the first user regarding customizing or configuring the first telecommunications-related service, receiving input from the first user to add the customized or configured first telecommunications-related service to the purchase order request, and applying a price change or discount to the first telecommunications-related service or the purchase order request.

Description

Background Art

[0001] The conventional market for network-related services is highly fragmented. Even in the Internet era, purchasers of network services usually have to contact each vendor individually, especially via email or phone, evaluate their capabilities, and negotiate specifications, products, availability, and prices separately. As a result, comparison shopping, negotiation, and coordination with service providers and vendors have traditionally been time-consuming, inefficient, and costly for purchasers of network services. Specifically, the telecommunications industry has one of the most complex and cumbersome processes in which network operators search for end-to-end solutions, service providers, vendors, or implementers to assist in the resolution and implementation of network operation business plans. Conventionally, telecommunications systems have been mainly hardware-based, and hardware devices were usually proprietary or managed by a specific vendor. Therefore, network operators need to carefully select the appropriate vendor to provide network services to meet the needs of the network operator. Furthermore, different regions and customers have different requirements for network services, and it can be a difficult task for network operators to select the appropriate network service provider or vendor that can meet all the needs of customers. Even after selecting a vendor or service provider, various types of arrangements need to be made by network operators to deploy or install the service (e.g., schedule on-site visits, on-site installations, etc.).

[0002] Furthermore, vendors are usually selected by network operators, and end-users or customers of a particular service cannot choose the service providers or vendors they want to work with. For example, when an end-user / customer selects a network operator, the network services provided by the network operator are bundled with specific service providers or vendors selected by the network operator and not by the customer. Thus, if a customer is not satisfied with a service provider or vendor, the customer may need to lodge a complaint with the network operator or may need to switch to another network operator. Therefore, there is a need to provide a solution to reduce or eliminate the burden on network operators of selecting service providers and onboarding them onto network services, and to further provide end-users and customers with the flexibility to select network services (and their respective providers) according to the customers' needs and requirements. Summary of the Invention

[0003] According to an exemplary embodiment, a centralized online marketplace, trading platform, and network are provided that enable a user to market and sell network and telecommunications related services to customers who are trying to build solutions and operate a business. In particular, telecommunications network services can be defined and provided in a software-based form such as virtualized network functions (VNFs) or software-defined networks (SDNs), or virtual network services. Thus, software-based and virtualized network services are stored via the market platform of one or more embodiments (e.g., within a cloud cluster such as a hybrid cloud, data center). Here, the service provider of the market platform can directly configure how to promote and sell network services to customers. Similarly, end users and customers can customize the requirements of the network services they want to purchase and select the most appropriate service provider or specific vendor as desired. In particular, the market platform of one or more embodiments provides a centralized platform for a market audience (market players) targeted at telecommunications related to seeking solutions for operating a business. By simplifying and automating processes such as the process of capturing product interest for order fulfillment and adjustment, both buyers and sellers of the market platform can save time and resources as opposed to manual intervention, thereby automating the process, minimizing errors, and in particular, improving customer satisfaction. Further, through this automation, the market platform can provide customers with a simple, flexible, cost-effective, efficient, and rapid deployment of network solutions.

[0004] According to an exemplary embodiment, a method for trading telecommunications-related services on a centralized marketplace network includes presenting a first telecommunications-related service to a first user, where the first telecommunications-related service is based on a configuration profile (settings profile) defined by a second user; receiving a selection of the first telecommunications-related service by the first user; and receiving a purchase order request from the first user for the selected first telecommunications-related service.

[0005] The method also includes receiving input from the first user regarding customizing or configuring (setting) the first telecommunications-related service; receiving input from the first user to add the customized or configured (set) first telecommunications-related service to the purchase order request; and applying a price change or discount to the first telecommunications-related service or the purchase order request. Here, the configuration profile may include a price change or discount, and the price change or discount is associated with the first user.

[0006] The method may also include receiving one or more identification information regarding the first user, where the identification information is composed of one or more of a name, location, company, job role, and contact time.

[0007] The method may also include receiving a request from a second user accessing a dashboard portal. The dashboard portal may include at least one of a product or service catalog portal, a customer lead or prospect information portal, a customer purchase history portal, or a product or service order portal.

[0008] The method may also include receiving a request from a second user to create a second telecommunications-related product or service within a catalog portal for products or services. Further, the created second telecommunications-related product or service may be a software-based network service or a virtual network service.

[0009] The method may also include receiving a request from a second user to create one or more customer leads or prospects within a customer lead or prospect information portal. Further, the method may include receiving a request from a second user to create one or more promotion (sales promotion, marketing) campaigns for a second telecommunications-related product or service based on the purchase history of a first user or a third user from a customer purchase history portal or an order portal for products or services. Here, the first user may be an end user, and the second user may be a network service provider.

[0010] According to an exemplary embodiment, an apparatus for trading telecommunications-related services on a centralized market network may include a memory storage storing computer-executable instructions and a processor communicatively coupled to the memory storage. The processor is configured to execute the computer-executable instructions to cause the apparatus to present a first telecommunications-related service to a first user via a central server. The first telecommunications-related service is configured to receive a selection of the first telecommunications-related service via the first user based on a configuration profile defined by a second user, and receive a purchase order request for the selected first telecommunications-related service or the selected first telecommunications-related service via the first user.

[0011] Furthermore, when executed by a processor, the computer-executable instructions can cause the apparatus to receive input from a first user regarding customizing or configuring a first telecommunications-related service, receive input from the first user to add the customized or configured first telecommunications-related service to a purchase order request, and further cause the apparatus to apply a price change or a price reduction to the first telecommunications-related service or the purchase order request. Further, the configuration profile may further include a price change or a price reduction, which is associated with the first user.

[0012] In addition, when executed by a processor, the computer-executable instructions can cause the apparatus to further receive one or more identification information regarding the first user, and the identification information is composed of one or more of a name, a location, a company, a job role, and a contact time.

[0013] Furthermore, when executed by a processor, the computer-executable instructions can cause the apparatus to further receive a request from a second user to access a dashboard portal. Here, the dashboard portal may include at least one of a product or service catalog portal, a customer lead or prospect information portal, a customer purchase history portal, or a product or service order portal.

[0014] Furthermore, when executed by a processor, the computer-executable instructions can cause the apparatus to further receive a request from a second user to create a second telecommunications-related product or service in a product or service catalog portal. Here, the first user may be an end user, and the second user may be a network service provider.

[0015] According to an exemplary embodiment, a non-transitory computer-readable medium includes computer-executable instructions for trading telecommunications-related services on a centralized market by a device. When the computer-executable instructions are executed by at least one processor of the device, the device is caused to present a first telecommunications-related service to a first user, the first telecommunications-related service being based on a configuration profile defined by a second user, receive a selection of the first telecommunications-related service by the first user, and receive a purchase order request from the first user regarding the selected first telecommunications-related service.

Brief Description of the Drawings

[0016] Hereinafter, features, advantages, and importance of exemplary embodiments of the present invention disclosure will be described with reference to the accompanying drawings, in which like reference numerals denote like elements.

[0017]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8A

Figure 8B

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17A

Figure 17B

[0018] The following detailed description of the exemplary embodiments refers to the accompanying drawings. The same reference numerals in different drawings may be treated identically for the same or similar elements.

[0019] The foregoing disclosure of the present invention provides examples and explanations, but is not intended to be exhaustive or to limit the disclosed embodiments to the exact forms. In light of the above disclosure, changes and modifications are possible, or may be obtained from the implementation of the embodiments. Further, one or more features or components of one embodiment may be incorporated into another embodiment (or one or more features of another embodiment), or may be combined with another embodiment (or one or more features of another embodiment). Additionally, in the flowcharts and descriptions of operations provided below, one or more operations may be omitted, one or more operations may be added, one or more operations may be (at least partially) performed simultaneously, and the order of one or more operations may be rearranged.

[0020] It will be apparent that the systems and / or methods described herein may be implemented in various forms of hardware, firmware, or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not limiting of the embodiments. Thus, the operations and behaviors of the systems and / or methods are described herein without reference to specific software code, and it is understood that software and hardware may be designed to implement the systems and / or methods based on the description herein.

[0021] Even if a particular combination of features is recited in the claims and / or disclosed herein, these combinations are not intended to limit the disclosure of possible embodiments. In fact, many of these features may be combined in forms not specifically recited in the claims and / or not disclosed herein. Each of the dependent claims listed below may depend directly on only one claim, but in the disclosure of possible embodiments, each dependent claim includes combinations with all other claims in the set of claims.

[0022] Elements, operations, or instructions used in this specification should not be construed as important or essential unless explicitly described. Also, the articles "a" and "an" used in this specification are intended to include one or more items and may be used synonymously with "one or more." When only one item is intended, the term "one" or similar language is used. Further, terms such as "has," "have," "having," "include," and "including" used in this specification are intended to be non-limiting terms. Additionally, the phrase "based on" is intended to mean "based, at least in part, on" unless otherwise specified. Furthermore, expressions such as "at least one of [A] and [B]" or "at least one of [A] or [B]" should be understood to include only A, only B, or both A and B.

[0023] Throughout this specification, references to "one embodiment," "an embodiment," "a non-limiting, exemplary embodiment," or similar language mean that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the solution of the present invention. Thus, the phrases "in one embodiment," "in an embodiment," "in one non-limiting, exemplary embodiment," and similar language throughout this specification do not necessarily refer to the same embodiment, although they may.

[0024] Furthermore, the described features, advantages, and characteristics of the present disclosure may be combined in any suitable manner in one or more embodiments. Those skilled in the art will recognize, in light of the description herein, that the present disclosure can be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments of the present disclosure.

[0025] In one implementation of the present disclosure described herein, the display page may include information present in the memory of a computing device, which may be transmitted from the computing device to a database center via a network and vice versa. The information may be stored in the memory of each of the computing devices, in a data storage present at the end of the network, or in the servers of the database center. A computing device or a mobile device may receive a non-transitory computer-readable medium, which may include instructions, logic, data, or code stored in the persistent or temporary memory of the mobile device, or may affect or initialize the operation of the mobile device in some form. Similarly, one or more servers may communicate with one or more mobile devices via a network and may transmit computer files present in the memory. The network can include, for example, the Internet, a wireless communication network, or any other network connecting one or more mobile devices to one or more servers.

[0026] Any discussion regarding a computing device or a mobile device may apply to any type of network device, including, but not limited to, mobile devices such as cellular phones (e.g., any "smartphone"), personal computers, server computers, or laptop computers, and roaming devices such as telephones, personal digital assistants (PDAs), network-connected roaming devices, wireless devices such as wireless email devices or other devices capable of wirelessly communicating with a computer network, or any other type of network device that may communicate via a network and operate electronic transactions. Any description regarding any mobile device mentioned may apply, in particular, to other devices including, but not limited to, short-range ultra-high frequency (UHF) devices, near-field communication (NFC), infrared (IR), and devices with Wi-Fi capabilities.

[0027] Phrases and terms similar to "software", "application", "app", and "firmware" may include any non-transitory computer-readable medium that stores therein a program that causes a computer to perform a method, function, or control operation when executed by the computer.

[0028] Terms and phrases similar to "network" may include one or more data links that enable the transfer of electronic data between computer systems and / or between modules. When information is transferred or provided to a computer via a network or another communication connection (either wired, wireless, or a combination of wired and wireless), the computer uses that connection as a computer-readable medium. Thus, by way of example and not limitation, a computer-readable medium can also include a network or data link that can be used to carry or store desired program code means in the form of computer-executable instructions or data structures and that can be accessed by a general-purpose or special-purpose computer.

[0029] Terms and phrases similar to "portal" or "terminal" may include an intranet page, an Internet page, locally existing software or application, a graphical user interface of a mobile device, or a digital presentation for a user. A portal can also be any graphical user interface that accesses the various modules, components, features, options, and / or attributes of the present invention disclosure described herein. For example, a portal can be a web page accessed via a web browser, a mobile device application, or any application or software existing on a computing device.

[0030] FIG. 1 shows a diagram of a general network architecture according to one or more embodiments. Referring to FIG. 1, users 110, 120, and 130 can communicate bidirectionally with a central server or application server 100 via a secure network according to one or more embodiments. Further, users 110, 120, and 130 can also communicate directly with each other bidirectionally via a market platform network system according to one or more embodiments. Here, user 110 can be any type of vendor or service provider, such as vendor A, vendor B, and vendor C, that provides similar, identical, or different services or products to either user 120 or user 130 with respect to a network operator or service operator. In particular, user 110 can provide any type of telecommunications-related service or product, such as the deployment of a cellular service network, the update of network capacity, operation monitoring, data analysis and reporting, and any other suitable service. Each of users 110 can communicate with server 100 via their respective terminals or portals. User 120 can be network operator A and network operator B and service provider C, and can provide similar, identical, or different services or products to user 130 or user 110. Here, user 110 or 120 can be, among others, any type of telecommunications vendor or network service provider, network operator, carrier, broadband provider, Unified Communications as a Service (UCaaS) provider, wired or wireless cellular network service provider, radio access network (RAN), web host, or any network-related or telecommunications-related service provider or network provider. Each of users 120 can communicate with server 100 via their respective terminals or portals.User 130 can be any type of end user, such as end user A or customer B and customer C, or an end user who purchases and / or receives telecommunications network-related services from user 120 or user 110, or a customer of user 120 or user 110. Each of the users 130 can communicate with the server 100 via their respective terminals or portals.

[0031] Referring further to FIG. 1, the central server 100 of the market platform system according to one or more embodiments can further communicate bi-directionally with the management terminal / dashboard 140. Here, the management terminal / dashboard 140 can provide various tools to any of users 110, 120, and 130 or the sales team or the content / product creation team for managing various customers / end users and customer leads. Such management can include, among other things, creating, editing, and promoting sales promotion campaigns for various types of telecommunications network services or products according to one or more embodiments, and advertising, offering, and ordering options for the customers and other users of the market platform. Further, the management terminal / dashboard 140 may also include various types of access rights for various users of the market platform system according to one or more embodiments. Further, the central server 100 according to one or more embodiments can further communicate bi-directionally with the database / third-party server 150. Here, the server 150 can provide various types of data storage (such as cloud-based storage), web services, content creation tools, data streams, data feeds, and / or provide various types of third-party support services to the central server 100 of the market platform. However, within the scope of the present invention disclosure described herein, the network service market platform process and system according to one or more embodiments are considered to be able to include any type of general network architecture.

[0032] Referring further to FIG. 1, one or more of the servers or terminals among elements 100 to 150 may include a personal computer (PC), a printed circuit board equipped with a computing device, a minicomputer, a mainframe computer, a microcomputer, a telephone computing device, a wired / wireless computing device (e.g., a smartphone, a personal digital assistant (PDA)), a laptop, a tablet, a smart device, a wearable device, or any other similar functional device.

[0033] In some embodiments, as shown in FIG. 1, one or more servers, terminals, and users 100 to 150 may include a set of components such as a processor, a memory, a storage component, an input component, an output component, a communication interface, and a JSON UI rendering component. The set of components of the device may be communicatively coupled via a bus.

[0034] The bus may include one or more components that enable communication between the set of components of one or more of the servers or terminals among elements 100 to 150. For example, the bus may be a communication bus, a crossover bar, a network, etc. The bus may be implemented using single or multiple (two or more) connections between the set of components of one or more of the servers or terminals among elements 100 to 150. The present disclosure is not limited thereto.

[0035] One or more of the servers or terminals of elements 100 to 150 may include one or more processors. The one or more processors may be implemented in hardware, firmware, and / or a combination of hardware and software. For example, the one or more processors may be a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), a microprocessor, a microcontroller, a digital signal processor (DSP), a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), a general-purpose single-chip or multi-chip processor, or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, or any conventional processor, controller, microcontroller, or state machine. The one or more processors may also be implemented as a combination of computing devices such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration. In some embodiments, certain processes and methods may be performed by circuitry specific to a given function.

[0036] One or more processors may control the overall operation of one or more of the servers or terminals of elements 100 to 150 and / or an entire set of components (e.g., memory, storage components, input components, output components, communication interfaces, rendering components) of one or more of the servers or terminals of elements 100 to 150.

[0037] One or more of the servers or terminals of elements 100 to 150 may further include a memory. In some embodiments, the memory may include a random access memory (RAM), a read only memory (ROM), an electrically erasable programmable ROM (EEPROM), a flash memory, a magnetic memory, an optical memory, and / or another type of dynamic storage device or static storage device. The memory may store information and / or instructions used (e.g., executed) by the processor.

[0038] The storage component of one or more of the servers or terminals of elements 100 to 150 may store information and / or computer-readable instructions and / or code related to the operation and use of one or more of the servers or terminals of elements 100 to 150. For example, the storage component may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optical disk, and / or a solid state disk), a compact disc (CD), a digital versatile disc (DVD), a universal serial bus (USB) flash drive, a Personal Computer Memory Card International Association (PCMCIA) card, a floppy disk, a cartridge, a magnetic tape, and / or another type of non-transitory computer-readable medium, along with the corresponding drive.

[0039] One or more of the servers or terminals of elements 100 to 150 may further include an input component. The input component may include one or more components that enable one or more of the servers and terminals 110 to 140 to receive information via user input (e.g., touch screen, keyboard, keypad, mouse, stylus, button, switch, microphone, camera, etc.). Alternatively or in addition, the input component may include sensors that sense information (e.g., a Global Positioning System (GPS) component, accelerometer, gyroscope, actuator, etc.).

[0040] One or more output components of any one or more of the servers or terminals of elements 100 to 150 may include one or more components that can provide output information from device 100 (e.g., display, liquid crystal display (LCD), light-emitting diode (LED), organic light emitting diode (OLED), tactile feedback device, speaker, etc.).

[0041] One or more of the servers or terminals of elements 100 to 150 may further include a communication interface. The communication interface may include a receiver component, a transmitter component, and / or a transceiver component. With the communication interface, one or more of the servers or terminals of elements 100 to 150 may be enabled to establish a connection with other devices (e.g., servers, other devices) and / or transfer communications. The communication may be enabled via a wired connection, a wireless connection, or a combination of a wired connection and a wireless connection. With the communication interface, one or more of the servers or terminals of elements 100 to 150 may be permitted to receive information from other devices and / or provide information to other devices. In some embodiments, the communication interface may provide communication with other devices via a network such as a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a private network, an ad hoc network, an intranet, the Internet, an optical fiber-based network, a cellular network (e.g., a fifth-generation (5G) network, a long-term evolution (LTE) network, a third-generation (3G) network, a code division multiple access (CDMA) network, etc.), a public land mobile network (PLMN), a telephone network (e.g., a Public Switched Telephone Network (PSTN)), etc., and / or a combination thereof or a combination of other types of networks. Alternatively or in addition, the communication interface may provide communication with other devices via a device-to-device (D2D) communication link such as FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi, LTE, 5G, etc.In other embodiments, the communication interface may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, and the like.

[0042] Figure 2 shows a telecommunications network service market and a trading platform system according to one or more embodiments. Referring to Figure 2, the market platform module or portal 200 can be a portal for the market platform and can communicate bidirectionally with a Customer Management System (CMS) distribution node module 202 that includes one or more of the modules 212 to 220 shown in Figure 2 of a Business Support Systems (BSS) product stack module or portal 210, and can also include a CMS integration module or portal 206 for content management and integration with various repositories. A user / customer module or portal 224 (e.g., a user terminal or client device) can access the market through communication with the CMS distribution node module or portal 202. In some embodiments, the user / customer module or portal 224 can also communicate with a Content Distribution Network (CDN) module or portal that further communicates with the module or portal 202 and the module or portal 206. In some embodiments, the CMS distribution node module or portal 202 can handle interactions with a first customer when the customer accesses the market platform 200 according to one or more embodiments. For example, the CMS distribution node module or portal 202 can receive requests from the customer's user terminal or portal 224 to browse available products / services, search for product / service data from a product catalog, and generate / present a graphical representation (e.g., columns, lists, etc.) of a user interface showing the available products / services of the market platform or one or more service providers or vendors. Additionally, a product / content team module or portal 222 (e.g., a terminal or client device of a seller, service provider, vendor, etc.) can also communicate with the market platform module or portal through communication with the CMS integration module or portal 206.In this case, the CMS integration module or portal 206 can generate and / or present a graphical user interface related to a seller, service provider, vendor, etc. (e.g., a user interface for listing products for sale, constructing a sales list, generating or editing a customer or product configuration profile, promoting sales activities, etc.).

[0043] Within the scope of the present invention disclosure described herein, any user of the market platform can first log in to the user management platform to determine the user's type or role, or the appropriate user of module or portal 222 or module or portal 224, etc., that is, the user's access rights. For example, the login page is generated by the user management platform and then presented to the user via each module or portal 222 or module or portal 224, enabling the user to enter the user's qualification information for logging in to the market platform. The user's qualification information is provided to the user management platform to determine the user's type or role or the user's access rights. When the user management platform determines that the user is a service provider / vendor / seller (accessing the market platform via the product / content team module 222), the user management platform can connect the product / content team module 222 to the CMS integration module 206. Similarly, when the user management platform determines that the user is a customer / purchaser (accessing the market platform via the user / customer module 224), the user management platform can connect the user / customer module 224 to the CMS delivery node module 202.

[0044] Referring further to FIG. 2, a market platform module or portal 200 according to one or more embodiments may also include a BSS product stack module or portal 210. Here, module 210 may further include a product catalog module or portal 212 that can be a repository / data storage for storing product / service data. Further, module 212 may also include and store product / service level promotion offers, or markdown indicators or events associated with one or more stored products / services. Module 210 may also include a customer information management (CIM) module or portal 214 that can be a repository / data storage for storing customer information (e.g., name, contact information, ID, customer interest list, customer level promotion offers or markdown events, etc.). Module 210 may also include a customer interaction management module or portal 216 that can be a repository / data storage for storing information on the interaction between the customer and the market platform (e.g., interaction history between the customer and interaction elements of a graphical user interface (GUI), communication between the customer and a service provider or other customers, etc.) according to one or more embodiments.

[0045] Referring further to FIG. 2, module 210 may also include a billing / invoice module or portal 218 that stores information associated with a customer's billing / invoice for services provided by a market platform (e.g., previously created claims, claim history, etc.). Further, module 210 may also include a customer care / sales module or portal 220 that stores information on sales or customer-related activities (e.g., sales campaign history, sales promotion activities for specific types of customers, sales history analysis, etc.). In some embodiments, module 220 can identify data associated with sales activities and the user's experience, search / collect data from an external data storage or any of modules or portals 212 - 218, store such data in a repository included in module 220, and provide such data to a network service provider / vendor as needed. As shown, module 220 can also communicate with a product / content team module or portal 222. Here, the product / content team module or portal 222 can be a user or portal for users (e.g., vendors / service providers) who want to promote / sell network services. Further, the product / content team module or portal 222 can be a lead conversion system, or a user who wants to convert customer leads, analyze customer activities, and also promote pre-sales activities, post-sales activities, and marketing campaigns.

[0046] Referring further to FIG. 2, the market platform module or portal 200 can also communicate with the orchestrator module 230 (e.g., via an application programming interface (API)). In particular, any one or more of the modules or portals 212 of module 210 to the module or portal 220 can communicate with and / or be supported by any of the modules or portals 238 to 240 of module 230. Specifically, the orchestrator module 230 can include a product / service management module 238 and a cloud orchestration module 240. In particular, any of the modules 238 to 240 can be containerized and stored within a "cloud" or cloud cluster on an external server and database. In some embodiments, the product / service management module 238 comprises a repository / datastorage for storing products and services provided by vendors / service providers. In some embodiments, the products and services are virtualized or software-based. In some embodiments, the cloud orchestration module 240 is configured to schedule products and services and provide them to users of the network service market platform.

[0047] FIG. 3 is a diagram showing a process flow for customers using a network service market platform according to one or more embodiments. Referring to FIG. 3, at step 300, a user (such as a customer, potential customer, or end user) accesses the portal of the market platform (such as accessing the CMS delivery node module 202 via the user / customer module 224), and can present products / services based on a configuration profile predefined by the service provider or vendor for that customer or a specific product. In particular, at step 300, the CMS delivery node module 202 receives a request from a user browsing the available products / services (via the user / customer module 224), searches for product / service data from the product catalog module 212 based on the request, and generates / presents a graphical user interface (GUI) representation (such as columns, lists, etc.) showing the available products / services of the market platform or one or more service providers or vendors. Referring to FIGS. 6 to 8B, for illustrative purposes, "Product / Service 1" can be an available telecommunications network-related service or product presented to the user for purchase.

[0048] In step 302, the user can select a service or product within the list / catalog via the GUI, and the market platform system can receive the selection of the service or product by the user. In particular, the metrics defining the selected product / service are sent from the user / customer module 224 to the CMS distribution node module 202 of the market platform. Then, the CMS distribution node module 202 searches for the configuration profile of the selected product or service from each data storage (such as the product catalog module 212), generates a service detail page based on the configuration profile, and can send the generated service detail page to the user / customer module 224 to further present the page to the user. In the configuration profile, a vendor or service provider can create, define, or pre-define how to specifically promote / present a service / product to customers or end-users (such as specific customers, groups of customers, or customers interested in a specific product / service) on the market platform. For example, the configuration profile can be criteria-based. Thus, the details of the service / product can include any appropriate information.

[0049] Referring further to FIG. 3, at step 304, the market platform or the user can optionally decide whether to apply a price cut to the selected service / product. If so (Yes), the CMS delivery node module 202 searches for price cut information (e.g., from the product catalog module 212 and / or the customer information management module 214, etc.) at step 304A, applies the price cut to the original price of the selected service / product, and then proceeds to step 306. If No, the process proceeds to step 306 without applying any price cut. In particular, the price of a specific service / product may vary according to the user or the type of user (e.g., end user, vendor, etc.). In particular, the network service provider / vendor can provide the user with price cut indicators, options, or codes (e.g., discount coupons, time-based sales indicators, indicators for special offers or sales promotion discounts for special users such as internal users or users who have complained about previous services, etc.), and the price cut indicators can be presented on a per-product / service basis (e.g., receiving a price cut for only a specific product / service) or on a per-user basis (e.g., receiving a price cut for all services the user is viewing). In some embodiments, the price cut indicators per product / service are stored in the product catalog module 212, and the price cut indicators per user are stored in the customer information management module 214. Therefore, when the user logs in to the market platform to select a specific service / product, the CMS delivery node module 202 of the market platform can search for the price cut indicators associated with the user login information from each data storage (e.g., the product catalog module 212, the customer information management module 214, etc.), apply the price cut to the original price of the service (set by the service provider), and present the price reduction on the page.

[0050] Referring further to FIG. 3, at step 306, the market platform can receive a selection by the user to add a particular selected service / product to a "product interest list" or purchase order list, and such information can be stored (or retrieved from) within the customer information management module 214. In particular, if the user is interested in a service / product selected, or wishes to purchase / order / shortlist a service / product, the user can trigger an interaction element (e.g., dedicated buttons such as "add to purchase list", "add to interest list", or any other suitable GUI element) within the portal of the market platform. The market platform can then add the configuration profile of the selected service to the user's interest list, calculate the information of the selected service / product, provide an overview of the price of the selected service / product, and further generate an interest list and present it to the user via the GUI. Referring to FIG. 8A, for illustrative purposes, an exemplary interest list GUI is shown via the portal of the market platform.

[0051] Referring further to FIG. 3, at step 308, the user can determine whether to customize the selected product / service. If so, at step 308A, the CMS delivery node module 202 receives the customization of the product / service from the user / customer module 224, applies the customization of the product / service to the list or order, and the process proceeds to step 310. If not, the process proceeds to step 310 without applying the customization of the product / service. Here, the user can customize the service / product order for each of the user's requirements (such as by triggering an interaction element such as a dedicated button "Change Requirements"), and send an order request to the service provider or seller by triggering an interaction element (such as a dedicated button "Contact" or any GUI element) (for example, when the requested order is not available or the user is a new customer), or (when the service / product is available and the user's customer details / identification / purchase history have been previously registered) select to purchase the service / product by triggering an interaction element (such as a dedicated button "Quick Checkout" or any GUI element). Referring to FIG. 8B, for illustrative purposes, the customization options and processes are shown via the GUI portal of the marketplace platform. Here, such interactions between the user and the marketplace platform can be stored (or retrieved from) within the customer interaction module 216.

[0052] Referring further to FIG. 3, in step 310, the CMS delivery node module 202 of the market platform can receive a selection from a user ordering a selected service / product or a selection from a user sending a request for a customized service / product. In particular, when the user selects to purchase the selected service / product (e.g., by triggering or selecting a "Quick Checkout" button or any GUI element), and the CMS delivery node module 202 determines that the user is logged in to the market platform (user details / identification / purchase history have been previously registered), and the selected service / product is pre-defined and available (e.g., based on data obtained from the product catalog module 212), the CMS delivery node module 202 can generate a purchase page and present it to the user. The price can be calculated based on the price defined by the service provider within the configuration profile, the price reduction indicator(s) retrieved from the product catalog module, the customer information management module, and / or other data storage (if any), and customizations made by the user via the interest list. Further, the user can review and change their personal information (e.g., name, job title, company, contact information, etc.) and payment method (e.g., credit card / debit card, bank transfer, payment by reward points, etc.). If the market platform determines that the user is a guest user, the market platform can direct the user to the user management system, and the user management system can generate and present a login page to request the user to log in before the market platform presents a purchase page or GIU portal to the user. After reviewing the purchase details, the user triggers or selects an interaction element (e.g., a dedicated "Pay" button or any GUI element), and the CMS delivery node module 202 sends a payment request to the billing / invoice module 218, whereupon the billing / invoice module 218 collects the associated billing data and charging data stored within the billing / invoice module 218 and generates payment information based on the billing data, charging data, and the payment request.After that, the Billing / Bill Module 218 then sends the payment information to the billing team or an external payment platform to process the payment. When the payment is successful, the billing team or the external payment platform generates a bill containing the order reference ID and sends it to the Billing / Bill Module 218. The Billing / Bill Module 218 stores a copy of the generated bill in a repository within the Billing / Bill Module 218 and then sends the bill to the CMS Delivery Node Module 202. The CMS Delivery Node Module then presents the bill (or only the order reference ID) to the user via the User / Customer Module 224.

[0053] Referring further to FIG. 3, in step 310, if the user selects to place an order request for the selected service (e.g., by triggering a "touch" button or any GUI element), and the market platform determines that the user is a "guest" user, the CMS delivery node module 202 directs the user to the user management system, and the user management system generates and presents a page that requests the user to log in (for registered customers) or create an order request (for new customers). If the user is a new customer, the user can trigger a dedicated button (e.g., "Create Order Request" or any GUI element). Then, the user management system notifies the CMS delivery node module to generate and present an order request creation page or GUI portal to the user. This page or GUI portal can include multiple input fields that enable the user to specify their personal information (e.g., company, location, name, contact information, job role, contact hours, etc.). In some embodiments, such information can be stored (or retrieved from) within the customer information management module 214. In one embodiment, the input fields can be pre-populated by the market platform (e.g., based on the user's location information, etc.). After the user has confirmed the details of their information, the user can trigger or select an interaction element (e.g., a dedicated "Submit" button or any GUI element), and then the market platform transmits the order information to the sales team for processing the order request, such as via the billing / invoice module 218 as described above. In some embodiments, the CMS delivery node module 202 transmits the entered user information to the user management platform to create a new user account for the new customer. Subsequently, the user management platform provides the user's information (e.g., the user's purchase history, etc.) to the CMS delivery node module 202, and the CMS delivery node module 202 then stores the user information in each module of the BSS product stack module 210.

[0054] Figure 4 shows the process flow of a seller or service provider / vendor using a network service market platform according to one or more embodiments. Referring to Figure 4, at step 400, a user (such as a network service provider or vendor) can present a login GUI portal, and the user can log in to the dashboard portal / administrator portal / back office portal of the market platform according to one or more embodiments via a product / content team module 222 as described above. Specifically, after successful login, the product / content team module 222 is connected to the CMS integration module 206, and the CMS integration module 206 collects information from the BSS product stack module 210 via the CMS distribution node module 202, and then generates and presents the aforementioned information to the user via a dashboard or back office GUI portal. Here, information about the user (such as purchaser, seller, etc.) can be stored and managed in one or more of the modules 212 to 220 within the BSS product stack module 210 and / or in any other appropriate repository. In particular, the back office portal can include pages / portals of the dashboard, pages / portals of the product catalog, pages / portals of customer leads, pages / portals of customer details or identification or purchase history, and pages / portals of orders. The user can choose to navigate between various pages / portals / sub-portals by triggering or selecting each interaction element (such as buttons, shortcut keys, etc., or any GUI element). Furthermore, the dashboard page / portal includes a graphical presentation (such as GUI, graph, chart, etc.) indicating the status of the service(s) associated with the user. For example, the traffic of requests for quotes (RFQs) for a service (such as the aforementioned "Product / Service 1") and the interest in the product can be provided to the user via a dashboard page / portal as illustrated in Figure 9.

[0055] Referring further to FIG. 4, at step 402, the CMS integration module 206 generates various services / products associated with the user, such as pages / portals of a product catalog as illustrated in FIG. 10 (e.g., based on information retrieved from the product catalog module 212), and can present them to the user (e.g., a service provider, vendor, or seller) via the product / content team module 222. In particular, the pages / portals of the product catalog include sub-pages / sub-portals such as catalogs (e.g., groups of products for Company A, including, among others, 4G network services, 5G network services, etc.), categories (e.g., cloud services associated with Company A, operation services associated with 4G services, digital experience services associated with 5G network services, etc.), products (Products A - C associated with cloud services, etc.), details (specifications of Product A, etc.). Here, such products / services can be any type of hardware or software-based or virtualized network-related service products, such as software virtualized network function (VNF) and / or software defined networking (SDN) products or services. Additionally, further categories can include, among others, access services, cloud services, operation services, unified cloud services, network function services, intelligent operation services, digital experience services, and Internet / ecosystem services. Additional products or services can include, among others, large-scale deployment tests and development projects for cloud RAN, virtualized NFC-compatible virtual base station solutions for both in-building wireless networks and macro networks, local network deployment, indoor connectivity, fixed access, backhaul and IoT applications, indoor and outdoor massive MIMO, macro and small cells, interference management and dual connectivity for improving network performance, baseband, wireless processors, and wireless access processing platforms, end-to-end flexible RAN solutions for projects including network design and optimization services.In step 404, the user can also add, modify, and delete various types of product / service offering and sales promotion campaigns via the product catalog pages / portals as illustrated in FIGS. 11 - 14 for illustrative purposes. In some embodiments, the user can also add new catalogs, new categories, new products, and new specifications via respective sub - pages according to one or more embodiments. Additionally, the user can also modify the created catalogs, categories, products, and specifications via the respective sub - pages.

[0056] Referring further to FIG. 4, in step 406, the CMS integration module 206 can retrieve various types of customer leads / prospects, customer information, customer identification, customer interest lists, and customer orders / purchase histories (from the customer information management module 214, the customer interaction module 216, and / or any other suitable repository) and present them to the user (via the product / content team module 222). In particular, the customer lead or prospect page / portal sub - page indicates the person in charge / representative from each business partner / customer (e.g., service provider or vendor) that the user is connected to or communicating with. Here, the user can view the customer lead or prospect information within the lead sub - page or sub - portal, modify the customer lead information included in this sub - page, and further add new leads or additional leads or prospects to this sub - page. In particular, the customer sub - page or sub - portal can indicate the customers (specific customers from associations / companies, individual customers, etc.) associated with the services / products provided / managed / offered by the user (e.g., service provider or vendor). The user can view the customer information within this sub - page, modify the customer information included in this sub - page, and add new customers to this sub - page or sub - portal.

[0057] Referring further to FIG. 4, in step 406, the CMS integration module 206 retrieves orders associated with services / products provided / offered / managed by a user (e.g., a service provider or vendor) from (such as the customer interaction module 216, the billing / invoicing module 218, the customer care / sales module 220, etc.), and presents them on a sub-page / sub-portal of the order. Here, the user can view the order information within this sub-page, change the order information included in this sub-page / sub-portal, and as shown in FIGS. 15 to 17B for illustrative purposes, add a new order to this sub-page / sub-portal. Further, in other embodiments, when the user receives an order request from a customer, the user uses the back office to customize the service / product based on the customer's request, and then can publish the customized service / product to the market platform so that other users can select / purchase it. The custom configuration parameters entered by the user can be saved as a configuration profile in a data storage (e.g., the product catalog module 212, the customer information management module 214, or any other appropriate repository) so that when another customer accesses the market platform, the market platform can retrieve the customer's configuration profile and present the service / product to the customer based on the configuration profile associated with the customer. When the customized service is ready, the user can store / host the service / product via the market platform so that the orchestrator of the market platform (the orchestrator module 230 in FIG. 2) can schedule the provision of the service / product to the customer. Here, the aforementioned customer information can be stored (or retrieved therefrom) in the customer information management module 214, the customer interaction module 216, and any other appropriate repository.

[0058] FIG. 5 shows a process flow of a user (such as a service provider / vendor, etc.) using a network service market platform according to one or more embodiments. Referring to FIG. 5, at step 500, a user (e.g., a seller, vendor, service provider, etc.) can be presented with a login GUI portal of a user management platform that allows the user to log in to a dashboard portal / administrator portal / back-office portal of the market platform according to one or more embodiments, via a product / content team module 222 as described above. After successful login, the product / content team module 222 is connected to the BSS product stack module 210. Further, the product / content team module 222 can retrieve any information (from any of the modules 212 to 220 of the BSS product stack module 210) that may be useful in constructing a sales activity or a sales promotion plan. Thereafter, the user can use the information for constructing a sales activity or a sales promotion plan.

[0059] Next, in step 502, the product / content team module 222 retrieves, among other things, customer information, browsing history, purchase history, and interest lists (from the customer information management module 214, the customer interaction module 216, and / or any other appropriate repository) and presents them to the user. In particular, the browsing history, purchase history, interest lists, etc. of registered customers on the market platform can be transferred by the BSS product stack module 210 of the market platform to the product / content team module 222 (e.g., the terminal of a user of a service provider / vendor / internal content team). Here, sub-pages / sub-portals of registered customers such as browsing history, purchase history, interest lists, etc. can be considered by the user when creating a sales / promotion plan based on the information of the registered customers (e.g., role / company / location, etc.). For example, registered customer A has role A in company A, and the market platform can provide information about another registered customer B with role A in company A, information about another registered customer C with role A in company Z, and information about another registered customer D with role B in company A, etc. to the user (e.g., a network service provider / vendor) for consideration. As a result, the user can more accurately promote services (e.g., propose related products or adjust price ranges, etc.) to any of the registered customers (users) A, B, C, or D.

[0060] Referring further to FIG. 5, at step 504, the product / content team module 222 can receive a selection from the user and create a promotion (sales promotion) campaign plan for products / services available on the market platform (e.g., products / services available in the product catalog module 212). In particular, the user or the market platform can analyze the received customer history information (such as information retrieved from the customer management module 214, customer interaction module 216, etc.) and / or the received sales history information (such as the analysis of the sales history retrieved from the customer care / sales module 220), and then construct a plan to promote / market / sell a service(s) or product(s) to the registered customers based thereon. At step 506, the user can optionally determine (via the product / content team module 222) whether to create a price reduction / change indicator or event for a specific service / product and / or a specific user / user group. If so, at step 506A, the process or the user can create a price reduction event for the product / service and the sales promotion campaign or plan via, for example, the product catalog module 212. If not, at step 506B, the process or the user does not create any price reduction event for the product / service and the promotion (sales promotion) campaign or plan. In particular, the user can create a price reduction event for a specific catalog / category / product / service (e.g., because customers interested in the aforementioned specific catalog / category / product / service will receive the price reduction), and offer a price reduction offer to a specific workgroup / user / customer, or a combination thereof. Referring to FIGS. 16 to 17B, for illustrative purposes, among other things, the dashboard page and the price reduction / change process are shown for various GUI portals (or screens) according to one or more embodiments.

[0061] FIG. 6 shows one non-limiting exemplary embodiment of a GUI portal for a list / catalog of available network products / services of a network service market platform. From here, a user may select a network product / service of interest. The GUI portal shown in FIG. 6 may be generated and / or input by the CMS delivery node 202 based on product / service data retrieved from the product catalog module 212.

[0062] FIG. 7 shows another non-limiting exemplary embodiment of a GUI portal for details of a product / service of a network service market platform. From here, a user may examine details of a selected network product / service (e.g., from the GUI portal of FIG. 6) and may add the network product / service to a purchase list / product interest list.

[0063] FIG. 8A shows another non-limiting exemplary embodiment of a GUI portal for a product / service purchase page of a network service market platform, further showing a product interest list including details of a particular selected product / service such as the number of users, the size of data storage, and the price. From here, a user may check out his order or purchase request and submit it to the network service market platform of the present invention disclosure described herein. Further, the user may also choose to specify his requirements for the selected product / service. Further, the user may also choose to continue browsing other network products / services.

[0064] FIG. 8B shows another non-limiting exemplary embodiment of a GUI portal for a product / service customization page of a network service market platform, further showing an option for a user to optionally configure or customize his product / service selection.

[0065] FIG. 9 shows one non-limiting, exemplary embodiment of a GUI portal for a back office dashboard page of a network service marketplace platform. The GUI portal for the back office dashboard page may include the status of services associated with a user, such as requests for quote (RFQ) traffic for services and interest in products. Here, the back office dashboard may also include a GUI menu element for selecting additional sub-pages or sub-portals having information regarding product catalogs (including additional sub-pages or sub-portals regarding catalogs, categories, products, and specifications), leads, orders, and customers.

[0066] FIG. 10 shows one non-limiting, exemplary embodiment of a GUI portal for a product sub-page of a back office dashboard, including viewing of each network service / product associated with a user (such as a seller, vendor, service provider, etc.). The GUI portal for the product sub-page may include a list of products, which may further include the status of each product, the category of each product, and any other suitable information regarding the product / service. From here, the user may also create a new product / service (such as by triggering a "new product" button or any other suitable option that triggers creation of a new product / service), and, for illustrative purposes, may further add various characteristics, pricing, and options to each product and product specification, as shown in FIGS. 11-12.

[0067] FIG. 11 is a diagram showing a GUI portal for defining the specifications of a new product. As shown in FIG. 11, the user may select an existing (i.e., pre-defined and stored) specification or create a new specification. For example, if the user selects "Use existing specification", a list of existing specifications may subsequently be presented, from which the user may select the specification to use. Otherwise, the user may create a new specification by filling in one or more of the fields shown in the exemplary GUI portal of FIG. 11. For example, the user may provide (manually or by searching and selecting from a predetermined list of product types) the title or name of the specification, a description of the specification, the product number of the corresponding product to which the specification applies, the expiration period of the specification, and the type of product. One or more of the fields shown may be required (i.e., the user must define them), and one or more may be optional (e.g., the user may not need to define or set the expiration period). It is understood that one or more additional fields may also be included. For example, one or more parameters or characteristics of the product may be defined, such as various selectable parameters (e.g., the number of user accounts or licenses, the size of data storage, etc.) that the user (purchaser or customer) may set when purchasing the product, default values for selectable options, etc. In this case, the parameters or characteristics may be set such that the customer (e.g., the customer can manually enter the number of user accounts or the size of data storage) defines them, or the user may define selectable options in the specification. The parameters or characteristics may be defined or created manually by the user, or may be pre-defined or associated with the type of product selected by the user (and subsequently editable by the user on the specification page).

[0068] FIG. 12 shows a GUI portal for defining product details of a new product. For example, when the definition of the specifications of a new product is completed, the product details page may be displayed. Through the product details GUI shown in FIG. 12, as an example, a user may define or set a product title, a product description, a market segment, a sales channel, a product category (e.g., by selecting one from a plurality of predetermined categories or by manually creating a new category), a product expiration period, and attached files (e.g., product images, product manuals, technical specifications, etc.). The user may also set the price of the product (or various prices corresponding to different customizable options) through the product details page, locations where the product / service is provided, etc.

[0069] Within the product subpage shown in FIG. 10, the user may also edit the product / service, edit the specifications of the product / service, view the details of the product / service, assign the product / service to a product / service category, apply a sales or offer schedule to the product / service, create additional price setting options for the product / service (such as monthly recurring fees or one-time fees) including technical information or manuals related to the product, and select the products / services described therein, in particular, for browsing and adding linked or associated products / services as shown in FIGS. 13 - 14 for illustrative purposes.

[0070] FIGS. 13 and 14 are diagrams showing a GUI portal for editing the product details of a previously created product / service. As shown in FIGS. 13 and 14, any of the values or information of the product details that can be defined at the time of creating the product / service may be edited thereafter.

[0071] FIG. 15 shows one non-limiting, exemplary embodiment of a GUI portal for an order sub-page of a back office dashboard that includes, among other things, viewing customer orders and their status. From here, the user may also view a particular order, view and select workflow options for the order (e.g., in process, on hold, completed, canceled, refunded, and payment on hold), edit a particular order (including viewing products / services to add / replace), and further select or define the price of the order.

[0072] FIG. 16 shows another non-limiting, exemplary embodiment of an order sub-page or product sub-page of a back office dashboard. From here, the user can select and customize the price and price setting options for a particular order or a particular product / service.

[0073] FIG. 17A shows another non-limiting, exemplary embodiment of an order sub-page or product sub-page of a back office dashboard. From here, the user can apply a price event (such as a price reduction) to a particular order or product / service, as shown in FIG. 17B. As shown in FIG. 17B, the user may add the name of the price event and include the price, frequency, interval, and duration of the price event.

[0074] It is understood that the specific order or hierarchy of blocks in the processes / flowcharts disclosed herein are illustrative approaches. It is understood that, based on design preferences, the specific order or hierarchy of blocks within a process / flowchart may be rearranged. Also, some blocks may be combined or omitted. The appended method claims present various block elements in a sample order and are not meant to be limited to the specific order or hierarchy presented.

[0075] Some embodiments may relate to systems, methods, and / or computer-readable media at any possible technical detail level of integration. Further, one or more of the above-described components may be implemented as instructions stored on a computer-readable medium and executable by at least one processor (and / or may include at least one processor). The computer-readable medium may include one or more computer-readable non-transitory storage media having computer-readable program instructions for causing a processor to perform operations.

[0076] Alternatively, the computer-readable storage medium can be a tangible device that can hold and store instructions for use by an instruction execution device. The computer-readable storage medium can be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination thereof. A non-exhaustive list of more specific examples of the computer-readable storage medium includes the following. That is, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disc (DVD), a memory stick, a floppy disk, a punched card or a raised structure of grooves having instructions recorded thereon, a mechanically encoded device, and any suitable combination thereof. The computer-readable storage medium used herein should not be construed as being a transient signal itself, such as a radio wave or other freely propagating electromagnetic wave, an electromagnetic wave propagating through a waveguide or other transmission medium (e.g., an optical pulse passing through an optical fiber cable), or an electrical signal transmitted through a wire.

[0077] The computer-readable program instructions described herein can be downloaded from a computer-readable storage medium to respective computing / processing devices or to an external computer or external storage device via a network, such as the Internet, a local area network, a wide area network, and / or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface within each computing / processing device receives the computer-readable program instructions from the network and transfers the computer-readable program instructions for storage in a computer-readable storage medium within each respective computing / processing device.

[0078] The computer-readable program code / instructions for performing the operation may be source code or object code written in any combination of one or more programming languages, including assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state-setting data, configuration data for integrated circuits, or object-oriented programming languages such as Smalltalk and C++, and procedural programming languages such as the "C" programming language or similar programming languages. The computer-readable program instructions may be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., through the Internet using an Internet service provider). In some embodiments, for example, an electronic circuit including a programmable logic circuit, a field programmable gate array (FPGA), or a programmable logic array (PLA) may execute the computer-readable program instructions by utilizing the state information of the computer-readable program instructions for personalizing the electronic circuit to perform the aspect or operation.

[0079] These computer-readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions executed via the processor of the computer or other programmable data processing apparatus create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks. These computer-readable program instructions may also be stored in a computer-readable storage medium that can direct a computer, programmable data processing apparatus, and / or other devices to function in a particular manner, such that the computer-readable storage medium storing the instructions comprises an article of manufacture including instructions for implementing the function / act manner specified in the flowchart and / or block diagram block or blocks.

[0080] The computer-readable program instructions may also be loaded onto a computer, other programmable apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other device to produce a computer-implemented process, such that the instructions executed on the computer, other programmable apparatus, or other device implement the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0081] The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer-readable media according to various embodiments. In this regard, each block in the flowchart or block diagram may represent a module, segment, or portion of one or more executable instructions for implementing the specified logical function. The methods, computer systems, and computer-readable media may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those shown in the figures. In some alternative implementations, the functions described in the blocks may be performed in a different order than that described in the figures. For example, two blocks shown in succession may actually be performed simultaneously, or substantially simultaneously, or the blocks may sometimes be performed in the reverse order depending on the related functions. It should also be noted that each block of the block diagrams and / or flowchart diagrams, and combinations of blocks of the block diagrams and / or flowchart diagrams, can be implemented by a dedicated hardware-based system that performs the specified function or operation, or a combination of dedicated hardware and computer instructions.

[0082] It will be apparent that the systems and / or methods described herein may be implemented in various forms of hardware, firmware, or a combination of hardware and software. The actual specific control hardware or software code used to implement these systems and / or methods is not limiting of the implementations. Thus, the operation and behavior of the systems and / or methods are described herein without reference to specific software code, and it is understood that software and hardware may be designed to implement the systems and / or methods based on the description herein.

Claims

1. A method for trading telecommunications-related services on a centralized market network, comprising: presenting a first telecommunications-related service to a first user, wherein the first telecommunications-related service is based on a configuration profile defined by a second user; receiving a selection of the first telecommunications-related service by the first user; receiving a purchase order request from the first user for the selected first telecommunications-related service.

2. receiving an input from the first user regarding customizing or configuring the first telecommunications-related service; receiving an input from the first user to add the customized or configured first telecommunications-related service to the purchase order request; applying a price change or discount to the first telecommunications-related service or the purchase order request. The method according to claim 1, further comprising:

3. The method according to claim 2, wherein the configuration profile further comprises the price change or discount, and the price change or discount is associated with the first user.

4. The method according to claim 1, further comprising receiving one or more identification information regarding the first user, wherein the identification information is composed of one or more of name, location, company, job role, and contact time. The method according to claim 1.

5. The method according to claim 1, further comprising receiving a request from the second user to access a dashboard portal. The method according to claim 1, further comprising:

6. The method according to claim 5, wherein the dashboard portal comprises at least one of a product or service catalog portal, a customer lead or prospect information portal, a customer purchase history portal, or a product or service order portal.

7. The method according to claim 6, further comprising receiving a request from the second user to create a second telecommunications-related product or service within the product or service catalog portal. The method according to claim 6, further comprising:

8. The method according to claim 7, wherein the created second telecommunications-related product or service is a software-based network service or a virtual network service.

9. Receiving, within the customer lead or prospect information portal, a request from the second user to create one or more customer leads or prospects The method according to claim 6, further comprising

10. Receiving, from the customer purchase history portal or the product or service order portal, a request from the second user to create one or more promotional campaigns for the second telecommunications-related product or service based on the purchase history of the first user or the third user The method according to claim 6, further comprising

11. The method according to claim 1, wherein the first user is composed of end-users and the second user is composed of network service providers

12. An apparatus for trading telecommunications-related services on a centralized market network, comprising A memory storage for storing computer-executable instructions A processor communicatively coupled to the memory storage, the processor being configured to execute the computer-executable instructions, and causing the apparatus to Present a first telecommunications-related service to a first user via a central server, the first telecommunications-related service being based on a configuration profile defined by a second user Receive a selection of the first telecommunications-related service from the first user Receive a purchase order request from the first user regarding the selected first telecommunications-related service An apparatus comprising

13. When the computer-executable instructions are executed by the processor, further causing the apparatus to Receive an input from the first user regarding customizing or configuring the first telecommunications-related service Receive an input from the first user to add the customized or configured first telecommunications-related service to the purchase order request Apply a price change or a price cut to the first telecommunications-related service or the purchase order request, the apparatus according to claim 12

14. The apparatus according to claim 12, wherein the configuration profile further comprises the price change or the price cut, and the price change or the price cut is associated with the first user

15. When the computer-executable instructions are executed by the processor, further causing the apparatus to Causing the apparatus according to claim 12 to receive one or more pieces of identification information regarding the first user, the identification information being composed of one or more of name, location, company, job role, and contact time.

16. When the computer-executable instructions are executed by the processor, further causing the apparatus to Receive a request from the second user to access the dashboard portal, for the apparatus according to claim 12.

17. The dashboard portal comprises at least one of a product or service catalog portal, a customer lead or prospect information portal, a customer purchase history portal, or a product or service order portal, for the apparatus according to claim 16.

18. When the computer-executable instructions are executed by the processor, further causing the apparatus to Receive a request from the second user to create a second telecommunications-related product or service within the product or service catalog portal, for the apparatus according to claim 17.

19. The first user is composed of end-users, and the second user is composed of network service providers, for the apparatus according to claim 12.

20. A non-transitory computer-readable medium comprising computer-executable instructions for trading telecommunications-related services on a centralized market network by an apparatus, the computer-executable instructions, when executed by at least one processor of the apparatus, causing the apparatus to Present a first telecommunications-related service to a first user, the first telecommunications-related service being based on a configuration profile defined by a second user, Receive a selection of the first telecommunications-related service by the first user, Receive a purchase order request from the first user regarding the selected first telecommunications-related service.

Images