TWI860175B - A rent application and rent withdrawal system, method and non-volatile computer-readable storage medium thereof for cross-industry service - Google Patents

Abstract

The present invention provides a rent application and rent withdrawal system, method and non-volatile computer-readable storage medium thereof for cross-industry service, including a cross-industry cooperation system and a partner adjustment system, wherein the cross-industry cooperation system generates a user token and a user token status, and the partner adjustment system adjusts the installation instructions between the telecommunications operators and the partner service providers by the user token status. In this way, users can smoothly use the services provided by the cooperative service provider through the telecom operator.

Description

A rental application and cancellation system, method and non-volatile computer-readable storage medium for cross-industry services

The present invention relates to a rental application and cancellation technology, and more particularly to a rental application and cancellation system, method and non-volatile computer-readable storage medium for cross-industry services.

In the existing technology, service providers (such as video streaming service providers) often cooperate with telecommunications operators to increase the competitiveness of their products, thereby increasing the service customer base of their products through cross-industry cooperation. However, cross-industry sales services often encounter problems such as differences in contracts between the two parties, how users bind cross-industry subscriptions, and cross-industry business installation.

Specifically, the problems encountered by cross-industry services are as follows:

Problem 1: The customer applied for the streaming service provided by the video streaming service provider at the telecom operator’s service counter, but the customer’s phone number is not within the service coverage of the video streaming service provider, resulting in the video streaming service provider being unable to provide the streaming service to the customer, and the billing details between the telecom operator and the video streaming service provider cannot be matched.

Question 2: After the customer obtains the streaming service provided by the video streaming service provider through the telecom operator's service desk, he downloads the video streaming service provider's application (Application, APP) and uses the streaming service. However, this method causes the customer to have many steps in the activation process, and only uses the mobile phone number for communication and connection, resulting in low information security.

Question 3: As shown in the table below, the installation instructions provided by telecom operators and the installation API (Application Programming Interface) provided by video streaming service operators do not match, resulting in a gap in communication and connection.

Therefore, how to overcome the above problems, provide a connection for user data, and resolve the differences in the definitions of user behavior between the two operators has become an important topic for technical personnel in this field.

To solve the above problem, the present invention provides a system for applying for or canceling a lease for cross-industry services, which includes: a cross-industry cooperation system, which is connected to a telecommunications system. When the telecommunications system provides a user with a service for applying for or canceling a lease of a system of an operator to be adjusted, the telecommunications system generates a device number and a service order data to be transmitted to the cross-industry cooperation system, and the cross-industry cooperation system generates a corresponding user token according to the device number, sets a user token status, and then transmits a message including the user token, the user token status, and the device token. Instructions and contract data notification messages; and a partner adjustment system, which is connected to the cross-industry cooperation system and the operator system to be adjusted to receive notification messages from the cross-industry cooperation system, and the partner adjustment system sends an agent application or termination call to the operator system to be adjusted to enable the operator system to be adjusted to perform the application or termination service, and after the operator system to be adjusted completes the application or termination service, it notifies the partner adjustment system, and the partner adjustment system replies a response code to the cross-industry cooperation system.

The present invention further provides a method for applying for or canceling a lease of an inter-industry service, comprising: when a telecommunications system provides a user with a service for applying for or canceling a lease of an operator system to be adjusted, a cross-industry cooperation system receives a device number and a service order data generated from the telecommunications system; the cross-industry cooperation system generates a corresponding user token according to the device number, sets a user token status, and then transmits a message including the user token, the user token status, and the user token status. Status, installation instructions and contract data notification messages; a partner adjustment system receives the notification message from the cross-industry cooperation system and sends an agent application or termination call to the operator system to be adjusted, so that the operator system to be adjusted can perform the application or termination service; and after the operator system to be adjusted completes the application or termination service, it notifies the partner adjustment system, and the partner adjustment system replies a response code to the cross-industry cooperation system.

In the above-mentioned embodiment, when the telecommunications system provides the user with a subscription service for the operator system to be adjusted, the cooperative adaptation system receives a first notification message from the cross-industry cooperation system, and the first notification message includes the user token status being set to a new status or an updated status, and the cooperative adaptation system sets the user token status recorded by it to a new status or an updated status according to the user token status in the first notification message.

In the above-mentioned embodiment, when the telecommunications system provides the user with the service of canceling the lease of the operator system to be adjusted, the cooperative adaptation system receives the second notification message from the cross-industry cooperation system, and the second notification message includes the user's token status set to the cancellation status, and the cooperative adaptation system determines the user's token status in the second notification message, and sets the user's token status recorded in it to the conversion waiting status.

In the above-mentioned embodiment, after the time of the switching waiting state has expired, the partner adjustment system makes a call to the operator system to be adjusted to terminate the lease, so that the operator system to be adjusted can perform the termination service, and then the partner adjustment system sets the user token status recorded in its record to the cancellation status.

In the above-mentioned embodiment, when the telecommunications system provides the user with the service of upgrading or downgrading the system of the operator to be adjusted, the partner adjustment system receives the third notification message from the cross-industry cooperation system, and the third notification message includes the user's token status set to the cancellation status, and the partner adjustment system determines the user's token status in the third notification message to set the user's token status recorded in it to the conversion waiting status.

In the above-mentioned embodiment, before the time of the conversion waiting state expires, if the partner adaptation system receives the fourth notification message from the cross-industry cooperation system, and the fourth notification message includes that the user token status is set to the update status, the partner adaptation system will convert the user token status recorded by it from the conversion waiting state to the upgrade or downgrade state, so as to make an agent upgrade or downgrade call to the operator system to be adjusted, so that the operator system to be adjusted can upgrade or downgrade the service.

In the above-mentioned embodiment, the cross-industry cooperation system is further connected to another operator system. When the telecommunications system provides another user with one of the application or termination services of the other operator system, the telecommunications system generates another device number and another service order data to transmit to the cross-industry cooperation system, and the cross-industry cooperation system generates another corresponding user token according to the other device number, sets the status of the other user token, and then transmits another notification message including the other user token, the status of the other user token, another installation instruction and another contract data to the other operator system, so that the other operator system provides the application or termination service to the user.

In the aforementioned embodiment, the cross-industry cooperation system, the partner adaptation system, the telecommunications system, the operator system to be adapted and the other operator system are based on the user token or the other user token to authenticate and transmit information.

In the above-mentioned embodiment, the cross-industry cooperation system includes a contract synchronization module and a partner notification module, and when the cross-industry cooperation system triggers a schedule check, if the contract synchronization module compares the service order data with the contract data, it sends a supply message to the partner notification module, so that the partner notification module sends another notification message to the partner adaptation system, and then the partner adaptation system sends a call to the system of the operator to be adapted, thereby achieving data synchronization.

As in the aforementioned embodiment, when the cross-industry cooperation system triggers a schedule check, if the contract synchronization module compares the other service order data with the other contract data, it sends a supply message to the partner notification module, so that the partner notification module sends another notification message to the other operator system, thereby achieving data synchronization.

The present invention also provides a non-volatile computer-readable storage medium, which is applied to a computing device or a computer and stores instructions for executing the rental application and cancellation method for cross-industry services as described in the above-mentioned embodiment.

From the above, it can be seen that the system, method and non-volatile computer-readable storage medium for applying for and canceling leases for cross-industry services of the present invention mainly generates user tokens and user token status by the cross-industry cooperation system, and the cooperation business adaptation system communicates with the system of the operator to be adjusted, so that the cooperation business adaptation system uses the user token status to adjust the installation instructions between the telecommunications operator and the cooperation service provider, so as to avoid the user being unable to smoothly use the services provided by the cooperation service provider through the telecommunications operator.

1: A rental application and cancellation system for cross-industry services

11: Cross-industry cooperation system

111: Contract synchronization module

112:Partner notification module

113: User notification module

114: Telecommunications authentication serial module

115:Partner query module

116: Service listing module

12:Partners adjust the system

121: User activated the tuning module

122: State Adaptation Module

81: The first operator system

82: Second operator system

90:Telecommunications system

A:User

P: Physical counter

W:Partner’s portal website

S21 to S28, S31A to S36A, S31B to S34B: Steps

S41 to S48, S51 to S55, S61 to S66: Steps

S71A to S74A, S71B to S73B: Steps

Figure 1 is a schematic diagram of the architecture of the rental application and cancellation system used for cross-industry services of the present invention.

Figure 2 is a schematic diagram of the generation and conversion of user tokens and their service notification status.

Figure 3A is a flowchart of the service contract application and termination notification process method.

Figure 3B is a flowchart of the contract synchronization method.

Figure 4 is a flowchart of the method for user service notification, account activation and telecommunications equipment binding.

Figure 5 is a diagram showing the adjustment of user tokens and their service notification status.

Figure 6 is a schematic diagram of the process of users obtaining installation and service binding through telecommunications operators.

Figure 7A is a schematic diagram of the process of the partner's adaptation system to undertake the agent application/refund service operation of general supply and installation instructions.

Figure 7B is a schematic diagram of the process of the partner's adaptation system to undertake the agent upgrade/downgrade operation of general supply and installation instructions.

Figures 8A and 8B are schematic diagrams of the process of the application/refund service operation of the application/refund system for cross-industry services of the present invention.

Figures 9A and 9B are schematic diagrams of the process of the upgrade/downgrade operation of the rental application and cancellation system for cross-industry services of the present invention.

Figure 10 is a schematic diagram of the contract synchronization process of the cross-industry service application and cancellation system of the present invention.

The following is a specific and concrete example to illustrate the implementation of the present invention. People familiar with this technology can easily understand other advantages and effects of the present invention from the content disclosed in this manual.

It should be noted that the structures, proportions, sizes, etc. depicted in the drawings attached to this specification are only used to match the contents disclosed in the specification for understanding and reading by people familiar with this technology, and are not used to limit the restrictive conditions for the implementation of the present invention. Therefore, they have no substantial technical significance. Any modification of the structure, change of the proportion relationship or adjustment of the size should still fall within the scope of the technical content disclosed by the present invention without affecting the effects and purposes that can be achieved by the present invention. At the same time, the terms such as "one", "first", "second", "upper" and "lower" used in this specification are only used to facilitate the clarity of the description, and are not used to limit the scope of implementation of the present invention. The changes or adjustments in their relative relationships shall be regarded as the scope of implementation of the present invention without substantially changing the technical content.

FIG1 is a schematic diagram of the structure of the cross-industry service application and cancellation system 1 of the present invention. As shown in FIG1, the cross-industry service application and cancellation system 1 includes: a cross-industry cooperation system 11 and a partner adaptation system 12. In addition, the cross-industry cooperation system 11 is directly connected to a first operator system 81 of a partner (i.e., a cooperative service provider), and the cross-industry cooperation system 11 is connected to a second operator system 82 of another partner through the partner adaptation system 12, wherein the second operator system 82 of the other partner is the operator system to be adapted.

In one embodiment, the cross-industry cooperation system 11 and the partner adaptation system 12 are established in a server (such as a general server, a file server, a storage unit server, etc.) or other electronic equipment with a suitable computing mechanism, wherein each module in the cross-industry cooperation system 11 and the partner adaptation system 12 can be software, hardware or firmware; if it is hardware, it can be a processing unit, a processor, a computer or a server with data processing and computing capabilities; if it is software or firmware, it can include instructions that can be executed by a processing unit, a processor, a computer or a server, and can be installed on the same hardware device or distributed on different multiple hardware devices.

In this embodiment, the cross-industry cooperation system 11 includes a contract synchronization module 111, a partner notification module 112, a user notification module 113, a telecommunications authentication serial connection module 114, a partner query module 115 and a service listing module 116.

The contract synchronization module 111 is connected to the account system in the telecommunications system 90 of a telecommunications operator to receive contract data from a user A when applying for/terminating a lease, and the contract synchronization module 111 periodically checks the lease status of the user A with the account system in the telecommunications system 90 to prevent inconsistencies.

The partner notification module 112 is communicatively connected to the contract synchronization module 111 to periodically notify the contract synchronization module 111 of the device number to enter the scheduled check, so that the contract synchronization module 111 can check the contract data of the user A; and the partner notification module 112 generates the user token (Token) of the user A and its service notification status to notify the first operator system 81 of a partner's background service application/termination status at least according to the service notification status of the user token (hereinafter referred to as: user token status), and receives a notification message returned by the first operator system 81, thereby obtaining a response code in the notification message to confirm that the partner has received the user token status completely and correctly. When the partner notification module 112 receives the response code, it serves as confirmation that the partner has completely and correctly received the user token status.

In one embodiment, FIG. 2 is a schematic diagram of the generation and conversion of a user token and its service notification status. The partner notification module 112 generates a user token and its service notification status according to the device number of the user device (i.e., telecommunication equipment, such as a smart phone, etc.) of the user A, so as to match the change of the service notification status (i.e., the user token status) of the user token, and notify a partner's first operator system 81. It should be noted that the partner's first operator system 81 matches the installation instruction of the cross-industry cooperation system 11, so there is no need to adjust the installation instruction. The embodiment of adjusting the installation instruction is described in the following FIG. 5. In addition, the similarities between this embodiment and the above embodiment are not repeated. As shown in Figure 2, the generation and conversion operation of the user token status includes the following steps S21 to S28:

In step S21, when the device number of the user device of user A applies for/rents service for the first time, the partner notification module 112 sets the service notification status of the user token (i.e., the user token status) to "New Status" and transmits it to the first operator system 81 of a partner through a notification message to notify the user of the token status.

In step S22, when the user token status is "new status" and the device number of the user device of user A cancels the service provided by the partner, the partner notification module 112 sets the user token status to "cancel status" and transmits the notification message to the first operator system 81 to notify the user token status.

In step S23, when the user token status is "new status" and the user device of user A has a number expiration, number transfer or number vacancy, the partner notification module 112 sets the user token status to "delete status" and transmits the notification message to the first operator system 81, and the user token will no longer be used.

In step S24, when the user token status is "new status" and the device number of the user device of user A further applies for other services of the partner, the partner notification module 112 sets the user token status to "renew status" and transmits the notification message to the first operator system 81 to notify the user token status.

In step S25, when the user token status is "updated status" and the device number of the user device of user A cancels the service provided by the partner, the partner notification module 112 sets the user token status to "cancel status" and transmits the notification message to the first operator system 81 of the partner to notify the user of the user token status.

In step S26, when the user token status is "cancelled status", and the device number of the user device of user A further applies for other services of the partner, the partner notification module 112 sets the user token status to "updated status" and transmits the notification message to the first operator system 81 to notify the user token status.

In step S27, when the user token status is "updated status" and the user device of user A has a number expiration, number transfer or number vacancy, the partner notification module 112 sets the user token status to "deleted status" and transmits the notification message to the first operator system 81, and the user token will no longer be used.

In step S28, when the user token status is "cancelled", and the user device of user A has a number expiration, number transfer, or number vacancy, the partner notification module 112 sets the user token status to "deleted" and transmits the notification message to the first operator system 81, and the user token will no longer be used.

In one embodiment, FIG. 3A is a flow chart of a service contract application and termination notification process method, and the similarities between this embodiment and the above embodiment are not repeated. As shown in FIG. 3A, this method process includes the following steps S31A to S36A:

In step S31A, a user A applies for/cancels the service at a physical counter of a telecom operator or a portal website of a partner (or another partner), so that the telecom operator's telecom system 90 receives the device number and service order data of the user A, and then the telecom system 90 is connected to a cross-industry cooperation system 11 to provide the installation information of the telecom operator's user A to a contract synchronization module 111, and the installation information includes but is not limited to the device number and installation instructions.

In step S32A, the contract synchronization module 111 filters out the required installation instructions such as application service, termination service, termination number or change number from the installation information, and transmits them to the partner notification module 112.

In step S33A, the partner notification module 112 generates a user token and sets the user token status according to the device number in the installation message, so as to notify the user token, the user token status, the installation instruction and a contract data to a first operator system 81 of a partner or a second operator system 82 of another partner through a notification message.

In step S34A, after receiving the notification message, the first operator system 81 of the partner or the second operator system 82 of the other partner replies with a specific response code to confirm that the notification message has been successfully received, and the first operator system 81 of the partner or the second operator system 82 of the other partner provides the upgrade/termination service for the user A. The response code is "200 OK", which means that the notification message of the cross-industry cooperation system 11 has been received. On the contrary, if other codes are responded, it means that an abnormal problem has occurred. In addition, the cross-industry cooperation system 11 and the second operator system 82 of the other partner are connected through a partner adaptation system 12 for communication (as described in the subsequent embodiments).

In step S35A, after notification, the partner notification module 112 records the user token status and reports the device number of the user device of user A to the contract synchronization module 111.

In step S36A, the contract synchronization module 111 schedules a check on the device number of the user device of user A to execute a contract synchronization method and compare the differences between the service order data and the contract data. When there is contract data that does not conform to the agreement, it returns to step S32A to regenerate the installation message.

In one embodiment, FIG. 3B is a flow chart of the contract synchronization method, and this embodiment is a continuation of the above embodiment. In addition, the similarities between this embodiment and the above embodiment are not repeated. As shown in FIG. 3B, this method flow includes the following steps S31B to S34B:

In step S31B, the partner notification module 112 transmits the device number of the user device of user A to the contract synchronization module 111 for scheduling check.

In step S32B, the contract synchronization module 111 waits for the scheduled check trigger of the device number of the user device of user A.

In step S33B, when the schedule check is triggered, the contract synchronization module 111 obtains the service order data of the user A through the accounting system in the telecommunications system 90 to compare with the contract data of the first operator system 81 of the partner or the second operator system 82 of another partner with a correct response (i.e., the response code is "200 OK").

In step S34B, when there is a difference between the service order data and the contract data, the contract synchronization module 111 generates a supply and installation instruction for applying for/removing the lease to notify the partner notification module 112 to execute the subsequent notification process shown in FIG. 3A, thereby achieving the function of synchronizing the contracts of the two parties or resending the notification if it fails.

The user notification module 113 is connected to the user device of user A. When the contract information of user A changes, the user notification module 113 notifies user A of the change of contract information through SMS, Email or other instant messaging (IM) software; and when user A completes the application for service, the user notification module 113 generates a dynamic binding cooperation service URL to be sent to the user device of user A for user device binding and account activation. The dynamic binding cooperation service URL is directed to the user device of user A through the redirection process after telecommunication authentication, so that the service account of user A is bound to the user device and the service account is activated.

The telecommunication authentication serial connection module 114 is a communication connection between the user device of the user A and the authentication system in a telecommunication system 90. After the user A clicks the dynamic binding cooperative service website on his user device and logs in, the telecommunication authentication serial connection module 114 performs telecommunication authentication through the authentication system in the telecommunication system 90. After completing the line authentication of the user device of the user A and the telecommunication member account password authentication of the user A, the telecommunication authentication serial connection module 114 transfers the user token status and contract information of the user A to the first operator system 81 of the cooperative or the second operator system 82 of another cooperative, so as to activate the service of the user A on the first/second operator system 81, 82. In detail, through the telecommunications authentication serial module 114, the partner no longer needs to develop and design the relevant telecommunications equipment authentication interface process.

In one embodiment, the telecommunications authentication serial module 114 transfers the user token status and contract information of the user A to the service user activation website agreed upon by the partner through http, thereby activating the service of the user A on the first/second operator system 81, 82.

In one embodiment, FIG. 4 is a flowchart of a method for user service notification, account activation, and telecommunication equipment binding, and the similarities between this embodiment and the above embodiment are not repeated. As shown in FIG. 4, this method flow includes the following steps S41 to S48:

In step S41, when a partner notification module 112 sends a notification message (including user token, user token status) to a partner's first operator system 81 or another partner's second operator system 82 for installing a rental service, the first/second operator system 81, 82 replies a response code (such as 200 OK) to the partner notification module 112, and the user service notification is triggered.

In step S42, the partner notification module 112 sends an event to a user notification module 113, so that the user notification module 113 dynamically generates a user-specific telecommunications authentication and service activation URL (Uniform Resource Locator, URL).

In step S43, the user notification module 113 adds the telecom operator user authentication and service activation URL into a message, and sends an activation email or activation SMS to user A who has subscribed to the service via the communication protocol (Simple Mail Transfer Protocol, SMTP) or Short Message Service Center (SMSC) provided by the email server.

In step S44, the opening communication email or the opening SMS is sent to the user device of user A.

In step S45, the user device provides the user A with a service activation URL in the activation email or activation SMS to automatically redirect to a telecommunications authentication serial module 114.

In step S46, the telecommunications authentication serial module 114 performs line authentication or telecommunications member account and password input of the user device of user A. After the authentication is successful, the telecommunications authentication serial module 114 carries the user token and contract information of user A through redirection to redirect the request page of user A to the service activation entry interface of the first operator system 81 of the partner or the second operator system 82 of the other partner.

In step S47, when redirected to the service activation entry interface, the service activation entry interface accepts the user token and contract information of user A to perform subsequent service account activation and user token binding.

In step S48, after completing the service account activation and user token binding, the user A can directly connect to the service interface of the first operator system 81 of the partner or the second operator system 82 of the other partner to use the service.

The partner query module 115 is connected to the first operator system 81 of the partner or the second operator system 82 of the other partner. When the first/second operator system 81, 82 encounters issues of contract binding and obstacle query, the partner can perform functions such as user contract query and notification history query through the user token of user A.

The service listing module 116 is connected to the first operator system 81 of the partner or the second operator system 82 of the other partner to provide the file format of the service listing information to the partner or the other partner, so as to agree on multiple service listing information and regularly upload it to the cross-industry cooperation system 11 through file transmission. The service listing information includes the partner service provider code, contract plan data, partner service provider background notification receiving URL, partner service user service activation, and binding URL and other related information. In one embodiment, the service listing module 116 pre-lists and sets a notification URL of a cloud service.

In another embodiment, the partner adaptation system 12 includes a user-activated adaptation module 121 and a state adaptation module 122.

The user-activated adaptation module 121 is used to activate the serial connection to communicate with the telecommunications authentication serial connection module 114, thereby performing authentication binding with the second operator system 82 of another partner.

The state adaptation module 122 is connected to the partner notification module 112 and the second operator system of the other partner (i.e. the operator system to be adapted) 82 to provide a cooperative business installation agent mechanism, and by expanding the user token state, the user token state of the partner notification module 112 is converted to complete the installation agent mechanism, such as upgrading/downgrading the service.

Specifically, for the operator system to be adjusted that has a complete installation instruction interface but cannot be connected to the installation instruction of the cross-industry cooperation system 11 (that is, the installation instruction of the cross-industry cooperation system 11 does not match the installation instruction of the operator system to be adjusted), the partner adjustment system 12 can be used to perform agent partner service background operations to adjust and match the installation instruction defined by the telecommunications operator with the service installation instruction defined by the operator system to be adjusted. Among them, if there are matching installation instructions between the two, the partner adaptation system 12 does not need to be converted, but directly installs the installation instructions of the industry system to be adapted; on the contrary, if there are unmatched installation instructions between the two (such as upgrade instructions or downgrade instructions), the state adaptation module 122 of the partner adaptation system 12 will expand the user token state, thereby performing subsequent installation instruction matching of the cross-industry cooperation system 11. Therefore, the partner adaptation system 12 plays the role of a partner service provider backstage for the cross-industry cooperation system 11. With the partner adaptation system 12, the notification logic of the cross-industry cooperation system 11 will not be changed because the partner cannot match the installation instructions of the cross-industry cooperation system 11. It can also serve as a design guide for subsequent partner service providers to design how to connect to the cross-industry cooperation system.

In one embodiment, the partner notification module 112 uses the notification URL of the cloud service to call the state adaptation module 122 to provide service to the business system to be adapted. It should be noted that since the provisioning interface of the business system to be adapted does not support the provisioning of the cross-industry cooperation system 11, it is necessary to call the state adaptation module 122 through the notification URL of the cloud service, so as to enable the business system to be adapted to perform service provisioning through the state adaptation module 122.

In one embodiment, FIG. 5 is a schematic diagram of the adjustment operation of the user token and its service notification status, and this adjustment operation is based on the generation and conversion operation of the user token and its service notification status described in FIG. 2, and further expands two user token service notification statuses (i.e., user token statuses) to provide the operator system to be adjusted for installation instruction adjustment, wherein the expanded user token statuses are "In-grade Period Status" and "Up/Down Grade Status", and "In-grade Period Status" is a preparation status for user account upgrade/downgrade and has time validity. In addition, the similarities between this embodiment and FIG. 2 or other above-mentioned embodiments are not repeated. As shown in FIG5 , the user token status adjustment operation includes the following steps S51 to S55: In step S51, when the device number of the user device of the user A applies for the service for the first time, the partner notification module 112 sets the service notification status of the user token (i.e., the user token status) to "new status", so as to send a notification message to a business system to be adjusted through the status adjustment module 122, thereby notifying another partner to record the user token status.

In step S52, when the user token status is "new status" and the device number of the user device of user A cancels the service provided by another partner, the status adaptation module 122 sets the user token status to "transfer waiting status".

In step S53, if no event of applying for a rental service occurs during the validity period of the user token status, the status adjustment module 122 changes the user token status from "transfer waiting status" to "cancellation status", and then transmits the notification message to the operator system to be adjusted, thereby notifying the user token status.

In step S54, if the user token status has an event of applying for a rental service during the validity period, the status adjustment module 122 changes the user token status from "transfer waiting status" to "upgrade/downgrade status", and the status adjustment module 122 makes a service upgrade/downgrade call to the operator system to be adjusted.

In step S55, after completing the service upgrade/downgrade call, the status adaptation module 122 converts the user token status from "upgrade/downgrade status" to "update status".

FIG6 is a schematic diagram of the process of user installation and service binding through a telecommunications operator. In addition, the similarities between this embodiment and the above embodiment are not repeated. As shown in FIG6, the process of installation and service binding includes the following steps S61 to S66: In steps S61-1 and S62-1, or in steps S61-2 and S62-2, a user A can apply for a telecommunications contract plan through a partner's portal website W or through a telecommunications operator's physical counter P.

In step S63, when the user completes the process of applying for the rental service, an installation message is sent to a cross-industry cooperation system 11 via an accounting system in a telecommunications system 90.

In step S64, the cross-industry cooperation system 11 will notify the user token of user A and its service notification status to a first operator system 81 of a partner, or further notify a second operator system 82 of another partner through a partner adaptation system 12.

In step S65, the cross-industry cooperation system 11 will provide a service activation URL (i.e., activation URL) to the user A.

In step S66, user A can click on the service activation URL and enter the service front desk through the authenticated user token to complete the binding of the user service account and start using the service.

FIG7A is a flowchart of the agent application/termination service operation of the partner adaptation system in response to a general supply and installation instruction. In addition, the similarities between this embodiment and the above-mentioned embodiment are not repeated here. As shown in FIG7A , the agent application/termination service operation includes the following steps S71A to S74A: In step S71A, when a user A applies for a lease service through a telecommunications system 90, a partner adaptation system 12 receives a notification message from a cross-industry cooperation system 11, and the partner adaptation system 12 sets the user token status recorded in its record to "new status" or "updated status" according to the notification message based on the state logic of the adaptation operation shown in FIG5 , and then a state adaptation module 122 uses a cloud service supply and installation API (Application Programming Interface, application programming interface) to another partner's second operator system (i.e., the operator system to be adjusted) 82 to make an agent subscription call, so that the operator system to be adjusted can apply for rental services according to the installation instructions in the notification message, wherein the user token status is set to "new status" means that the user A has newly applied for rental services, and the user token status is set to "updated status" means that the user A has added other services based on the rental service, i.e., the supplementary contract. In one embodiment, the notification message includes but is not limited to the user token, user token status, installation instructions, and contract information.

In step S72A, the business system to be adjusted replies "Success status" to the partner adjustment system 12, and then the partner adjustment system 12 replies a response code (i.e. "200 OK") to the cross-industry cooperation system 11.

In step S73A, when user A applies for lease termination, the partner adaptation system 12 receives the notification message from the cross-industry cooperation system 11, and then the status adaptation module 122 determines the user token status (i.e. "cancellation status") in the notification message to temporarily set the recorded user token status to "transfer waiting status".

In step S74A, after the "transition waiting state" time has expired, the state adaptation module 122 uses the cloud service provisioning API to make an agent unsubscribe call to the operator system to be adapted, so that the operator system to be adapted performs the unsubscribe service according to the notification message, and after the call is successful, the state adaptation module 122 sets the recorded user token state to "cancel state".

FIG7B is a schematic diagram of the process of the partner adaptation system accepting the agent upgrade/downgrade operation of the general supply and installation instruction. In addition, the similarities between this embodiment and the above embodiment are not repeated. As shown in FIG7B, the agent upgrade/downgrade operation includes the following steps S71B to S73B: In step S71B, when a user A upgrades/downgrades the service through a telecommunications system 90, a partner adaptation system 12 receives a notification message from a cross-industry cooperation system 11, and then a state adaptation module 122 determines the user token status (i.e., "cancel status") in the notification message to temporarily set the recorded user token status to "transfer waiting status".

In step S72B, before the "transfer waiting state" time expires, the partner adaptation system 12 receives a notification message from the cross-industry cooperation system 11, and the notification message includes the user token status set to "update status", and then the status adaptation module 122 converts the recorded user token status from "transfer waiting state" to "upgrade/downgrade status", and uses the cloud service provisioning API to make an agent upgrade/downgrade call to the system of the operator to be adapted, so that the system of the operator to be adapted can upgrade/downgrade services according to the provisioning instructions in the notification message.

In step S73B, the business system to be adjusted replies "success status" to the partner adjustment system 12, and then the status adjustment module 122 sets the recorded user token status to "update status" to achieve the adjustment of the application/downgrade operation, and then the partner adjustment system 12 replies a response code (i.e. "200 OK") to the cross-industry cooperation system 11.

In addition, the present invention also discloses a non-volatile computer-readable storage medium, which is applied to a computing device or computer having a processor (e.g., CPU, GPU, etc.) and/or memory, and stores instructions, and can be used by the computing device or computer to execute the non-volatile computer-readable storage medium through the processor and/or memory to execute the above-mentioned method and each step when executing the non-volatile computer-readable storage medium. In one embodiment, the present invention discloses a non-transitory computer-readable storage medium to execute the above-mentioned method and each step.

FIG8A and FIG8B are schematic diagrams of the process of the application/refund service operation of the application/refund system 1 for cross-industry services of the present invention. In addition, the similarities between this embodiment and the above embodiment will not be repeated.

In this embodiment, as shown in FIG8A , when a user A purchases a network cloud service telecommunications contract of 100GB (hereinafter referred to as: cloud service 100G) at a physical counter of a telecommunications operator, a telecommunications system 90 generates a corresponding installation message according to the device number of the user device of the user A, and transmits the installation message (including but not limited to the device number A’, product code, contract code, and installation instructions, etc.) to a contract synchronization module 111 in a cross-industry cooperation system 11, and the contract synchronization module 111 receives the information in the installation message and provides it to a partner notification module 112. At this time, the partner notification module 112 generates a corresponding user token (i.e., "ABC") according to the device number A' of the installation message, and sets a user token status to "new status". Afterwards, the partner notification module 112 transmits the user token and the user token status to a partner adaptation system 12 via a notification message.

Furthermore, as shown in FIG8B , after receiving the notification message, the partner adaptation system 12 records the user token status, and since the user token status is "new status", the status adaptation module 122 in the partner adaptation system 12 directly performs the proxy subscription (Subscribe) of the cloud service provisioning API to call the second operator system (i.e. the operator system to be adapted) 82 of another partner, and after the call is successful, the operator system to be adapted replies "success status" to the partner adaptation system 12, and then the partner adaptation system 12 replies a response code (i.e. "200 OK") to the partner notification module 112, and finally the partner notification module 112 records the reply of the vendor (i.e. the operator system to be adapted), thereby completing the cross-industry service provisioning.

FIG. 9A and FIG. 9B are schematic diagrams of the process of the upgrade/downgrade operation of the rental application and cancellation system 1 for cross-business services of the present invention. Furthermore, this embodiment is a continuation of the embodiment described in FIG. 8A and FIG. 8B. In addition, the similarities between this embodiment and the above embodiment will not be repeated.

In this embodiment, a user A feels that the 100G cloud service is not enough, and upgrades to a 200G cloud service at the telecom counter. However, since the telecom system 90 does not have an upgraded rental option, it can only adopt a one-return-one-rental installation method. In response, the telecom system 90 instructs the contract synchronization module 111 in the cross-industry cooperation system 11 to execute the installation instructions of rent return and rent application in sequence.

Therefore, as shown in FIG9A and FIG9B, the contract synchronization module 111 sequentially transmits the installation message of the lease termination to a partner notification module 112, and then transmits the installation message of the lease application to the partner notification module 112, and the partner notification module 112 also sequentially converts the service notification status of a user token (i.e., the user token status) into "cancellation status" and "update status" according to the logic of the generation and conversion operation of the user token and its service notification status shown in FIG2.

Furthermore, the partner notification module 112 notifies a partner adaptation system 12, and when the partner adaptation system 12 first receives the notification message that the user token status is set to "cancelled status", the status adaptation module 122 in the partner adaptation system 12 will set the recorded user token status to "conversion waiting status" according to the logic of the adaptation operation of the user token and its service notification status shown in Figure 5 and reply with a response code (i.e., 200 OK). Afterwards, when receiving the notification message that the user token status has been changed to "update status", since the user token status recorded by the partner adaptation system 12 is still in "conversion waiting status", the status adaptation module 122 calls the upgrade application programming interface (Upgrade API) of the operator system to be adjusted, so that the operator system to be adjusted will upgrade the cloud service of user A to 200G. Furthermore, after the call is successful, the status adaptation module 122 changes the user token status recorded by it from "conversion waiting status" to "update status" to be consistent with the user token status recorded by the partner notification module 112, and replies with a response code (i.e. 200 OK).

FIG. 10 is a schematic diagram of the process of contract synchronization of the cross-business service application and cancellation system 1 of the present invention. In addition, the similarities between this embodiment and the above embodiment will not be repeated.

In this embodiment, the service leases of three users A, B, and C need to be changed. All of them send a notification message to notify a first operator system 81 of a partner or a second operator system 82 of another partner (i.e., the operator system to be adjusted) through a partner notification module 112 of a cross-industry cooperation system 11. It should be noted that since the notification message should be completely transmitted to the first operator system 81 of the partner or a partner adjustment system 12, many events, such as network connection abnormalities or equipment maintenance problems, will result in the inability to confirm whether the other party has received the complete notification message. Therefore, it is specified that a response code (i.e., "200 OK") must be returned when the notification message is completely received, so as to confirm that the user token status of the partner background and the partner notification module 112 is consistent.

Therefore, in this embodiment, the partner notified by the device number C' of user C does not reply to the response code (i.e. "200 OK"), and when a contract synchronization module 111 executes the scheduled check of the number, the contract synchronization module 111 compares the service order data of user C (the data changed at the telecommunications operator) with the contract data (the data saved at the partner), and because the service order data of user C has been changed, while the contract data is still the information before the change, the contract synchronization module 111 detects that the two are inconsistent, and the device number of users A and B is changed. Numbers A' and B' are consistent, so the contract synchronization module 111 re-sends the installation message of the device number C' to the partner notification module 112, so that the partner notification module 112 sends a notification message to the first operator system 81, or sends the notification message to the partner adaptation system 12, and then the partner adaptation system 12 sends a call to the second operator system 82 according to the notification message, thereby achieving the purpose of data synchronization.

In summary, the system, method and non-volatile computer-readable storage medium for applying for and canceling leases for cross-industry services of the present invention generates a user token and a user token status through a cross-industry cooperation system, and communicates with a system of an operator to be adjusted through a cooperation business adjustment system, so that the cooperation business adjustment system uses the user token status to adjust the installation instructions between the telecommunications operator and the cooperation service provider, thereby transferring the user to the platform of the cooperation service provider to combine the cross-industry accounts, that is, combining the user's account with the telecommunications operator and the cooperation service provider, so as to avoid the user being unable to use the services provided by the cooperation service provider through the telecommunications operator smoothly.

In addition, the rental application and cancellation system, method and non-volatile computer-readable storage medium of the present invention for cross-industry services have the following advantages or technical effects:

1. Since telecom operators and cooperative service providers do not provide one-stop services, after notifying cooperative service users of installation, cooperative service providers still need to interface with various telecom interfaces to implement telecom member authentication, account binding to telecom number, device number change, and user text message service notification operations. In this regard, the present invention provides cooperative service providers with only the need to interface with the cross-industry service system or cooperative service adaptation system to ensure synchronization of user contracts, user account activation, and binding of telecom equipment, thereby improving efficiency and security.

Second, the present invention can solve the problem of telecommunication users needing to notify service providers when changing phone numbers and reduce the risk of personal information disclosure by designing a unique user token corresponding to the user's telecommunication equipment number and defining the life cycle status of the user token (i.e., the service notification status of the user token, or the user token status) according to the application/termination events.

3. The general subscription and cancellation information interface of telecommunications operators usually does not have the function of upgrading/downgrading accounts, so it can no longer meet the cloud service provisioning behavior of large partners. In response to this, the present invention uses the partner's adjustment system to solve the problem of mismatched provisioning instructions.

4. This invention is responsible for handling the problem of inconsistent contracts between telecommunications operators and cooperative service providers through notification processes and contract synchronization processes, that is, the problem of inconsistency in billing details, so as to synchronize the contract data between the two.

The above implementation forms are merely illustrative of the principles and effects of the present invention, and are not intended to limit the present invention. Anyone familiar with this art may modify and change the above implementation forms without violating the spirit and scope of the present invention. Therefore, the scope of protection of the present invention should be as listed in the scope of the patent application.

1: A rental application and cancellation system for cross-industry services

11: Cross-industry cooperation system

111: Contract synchronization module

112:Partner notification module

113: User notification module

114: Telecommunications authentication serial module

115:Partner query module

116: Service listing module

12:Partners adjust the system

121: User activated the tuning module

122: State Adaptation Module

81: The first operator system

82: Second operator system

90:Telecommunications system

A:User

Claims (13)

A cross-industry service application and cancellation system includes: a cross-industry cooperation system, which is connected to a telecommunications system. When the telecommunications system provides a user with a service for applying for or canceling a system of an operator to be adjusted, the telecommunications system generates a device number and a service order data to be transmitted to the cross-industry cooperation system, and the cross-industry cooperation system generates a corresponding user token according to the device number, sets a user token status, and then transmits a package containing the user token, the user token status, installation instructions and contract information. and a partner adaptation system, which is connected to the cross-industry cooperation system and the operator system to be adapted, to receive the notification message from the cross-industry cooperation system, and the partner adaptation system sends an agent application or termination call to the operator system to be adapted, so that the operator system to be adapted can perform the application or termination service, and after the operator system to be adapted completes the application or termination service, it notifies the partner adaptation system, and the partner adaptation system replies a response code to the cross-industry cooperation system. As described in claim 1, the lease application and cancellation system for inter-industry services, wherein when the telecommunications system provides the user with a lease application service for the operator system to be adjusted, the partner adjustment system receives a first notification message from the inter-industry cooperation system, and the first notification message includes the user token status set to a new status or an updated status, and the partner adjustment system sets the user token status recorded by it to a new status or an updated status according to the user token status in the first notification message. As described in claim 1, the application and cancellation system for inter-industry services, wherein when the telecommunications system provides the user with the cancellation service of the operator system to be adjusted, the cooperative adaptation system receives a second notification message from the inter-industry cooperation system, and the second notification message includes the user's token status set to a cancellation status, and the cooperative adaptation system determines the user's token status in the second notification message to set the user's token status recorded in it to a conversion waiting status. As described in claim 1, the lease application and cancellation system for inter-industry services, wherein when the telecommunications system provides the user with an upgrade or downgrade service of the operator system to be adjusted, the partner adjustment system receives a third notification message from the inter-industry cooperation system, and the third notification message includes the user's token status set to a canceled status, and the partner adjustment system determines the user's token status in the third notification message to set the user's token status recorded in it to a conversion waiting status. As described in claim 1, the inter-industry cooperation system is further connected to another operator system. When the telecommunications system provides another user with one of the services of applying for or cancelling the lease of the other operator system, the telecommunications system generates another device number and another service order data to transmit to the inter-industry cooperation system. The inter-industry cooperation system generates another corresponding user token according to the other device number, sets the status of the other user token, and then transmits another notification message including the other user token, the status of the other user token, another installation instruction and another contract data to the other operator system, so that the other operator system provides the application or cancellation service to the user. As described in claim 1, the inter-industry service application and return system, wherein the inter-industry cooperation system includes a contract synchronization module and a partner notification module, and when the inter-industry cooperation system triggers a schedule check, if the contract synchronization module compares the service order data with the contract data, it sends a supply message to the partner notification module, so that the partner notification module sends another notification message to the partner adaptation system, and then the partner adaptation system sends a call to the system of the operator to be adapted, thereby achieving data synchronization. A method for applying for or canceling a lease for a cross-industry service includes: when a telecommunications system provides a user with a service for applying for or canceling a lease of a system of an operator to be adjusted, a cross-industry cooperation system receives a device number and service order data generated from the telecommunications system; the cross-industry cooperation system generates a corresponding user token according to the device number, sets a user token status, and then transmits a message including the user token, the user token status, A notification message of installation instructions and contract data; a partner adjustment system receives the notification message from the cross-industry cooperation system and sends a call for agent application or termination to the operator system to be adjusted, so that the operator system to be adjusted can perform application or termination services; and after the operator system to be adjusted completes the application or termination services, the partner adjustment system is notified, and the partner adjustment system replies a response code to the cross-industry cooperation system. The method for applying for and canceling a lease for a cross-industry service as described in claim 7 further includes that when the telecommunications system provides the user with a lease application service for the operator system to be adjusted, the cooperative adaptation system receives a first notification message from the cross-industry cooperation system, and the first notification message includes the user token status being set to a new status or an updated status, and the cooperative adaptation system sets the user token status recorded by it to a new status or an updated status according to the user token status in the first notification message. The method for applying for and cancelling a lease for a cross-industry service as described in claim 7 further includes that when the telecommunications system provides the user with a lease cancellation service for the operator system to be adjusted, the cooperative adjustment system receives a second notification message from the cross-industry cooperation system, and the second notification message includes that the user's token status is set to a cancel status, and the cooperative adjustment system determines the user's token status in the second notification message to set the user's token status recorded in it to a conversion waiting status. The method for applying for and canceling a lease for a cross-industry service as described in claim 7 further includes that when the telecommunications system provides the user with an upgrade or downgrade service for the operator system to be adjusted, the cooperative adjustment system receives a third notification message from the cross-industry cooperation system, and the third notification message includes that the user's token status is set to a cancel status, and the cooperative adjustment system determines the user's token status in the third notification message to set the user's token status recorded therein to a conversion waiting status. The inter-industry service application and termination method as described in claim 7 further includes: when the telecommunications system provides another user with one of the application or termination services of another operator's system, the inter-industry cooperation system receives another device number and another service order data generated from the telecommunications system; and the inter-industry cooperation system generates another corresponding user token according to the other device number, sets another user token status, and then transmits another notification message including the other user token, the other user token status, another installation instruction and another contract data to the other operator system, so that the other operator system provides the application or termination service to the other user. The method for applying for or canceling a lease for a cross-industry service as described in claim 7 further includes that when the cross-industry cooperation system triggers a schedule check, if the contract synchronization module in the cross-industry cooperation system compares the service order data with the contract data, a provision message is sent to the partner notification module in the cross-industry cooperation system, so that the partner notification module sends another notification message to the partner adaptation system, and then the partner adaptation system sends a call to the system of the operator to be adapted, thereby achieving data synchronization. A non-volatile computer-readable storage medium, used in a computing device or a computer, stores instructions for executing a method for applying for and canceling a lease for a cross-business service as described in any one of claim items 7 to 12.

Images