Information interaction method and device

Abstract

The invention discloses an information interaction method and device. An order interaction request sent by a user terminal is received, a target journey identifier is determined according to the order interaction request, the journey identifier is used for identifying a unique order, the journey identifier in the same order is kept unchanged, and a response parameter corresponding to the order interaction request is generated according to the target journey identifier and sent. Therefore, by introducing the unique journey identifier, the integrity and accuracy of journey tracking of the user can be improved, the troubleshooting difficulty of problems is reduced, and the root cause positioning efficiency is improved.

Description

Technical Field

[0001] This invention relates to the field of Internet technology, and in particular to an information interaction method and apparatus. Background Technology

[0002] With the development of internet technology, information exchange is needed in various fields, such as shared devices and e-commerce. In these contexts, end-to-end tracking and anomaly detection of the user journey have become particularly important. Taking shared bicycles and similar smart device rental services as an example, from the moment a user scans a code to initiate a rental request until the vehicle is successfully unlocked and returned, every step of the process directly affects the smoothness of the service and user satisfaction.

[0003] However, current technologies for tracking and monitoring the user journey often rely on fragmented or imprecise identification mechanisms, making it difficult to achieve seamless integration and in-depth analysis of the entire user behavior chain, from front-end applications and server-side processing to execution on smart devices. Especially when dealing with critical issues such as failed QR code scanning or lock malfunctions, the lack of a unique identifier throughout the entire user journey leads to difficulties in troubleshooting and inefficient root cause identification. Summary of the Invention

[0004] In view of this, the purpose of this invention is to provide an information interaction method and apparatus that, by introducing a unique journey identifier, can improve the integrity and accuracy of user journey tracking, reduce the difficulty of troubleshooting problems, and improve the efficiency of root cause localization.

[0005] In a first aspect, embodiments of the present invention provide an information interaction method, the method comprising:

[0006] Receive order interaction requests sent by user terminals;

[0007] The target journey identifier is determined based on the order interaction request, wherein the journey identifier is used to identify a unique journey and remains unchanged within the same journey;

[0008] Generate response parameters corresponding to the order interaction request based on the target journey identifier;

[0009] The response parameters are sent to the user terminal.

[0010] In some embodiments, the journey identifier includes a user's unique identifier and a timestamp, and the journey identifier is stored in a database.

[0011] In some embodiments, the order interaction request includes a unique identifier for the target user.

[0012] In some embodiments, the order interaction request is an order creation request, and determining the target journey identifier based on the order interaction request includes:

[0013] A first detection result is determined based on the unique identifier of the target user, and the first detection result is used to characterize whether the target user has any incomplete orders;

[0014] In response to the first detection result indicating the existence of an incomplete order, the journey identifier corresponding to the incomplete order is determined as the target journey identifier;

[0015] In response to the first detection result indicating that there are no incomplete orders, the target journey identifier is determined based on the second detection result, which is used to characterize whether the target user has a journey identifier for creating a failed order.

[0016] In some embodiments, determining the target journey identifier based on the second detection result includes:

[0017] The second detection result is determined based on the database;

[0018] In response to the second detection result indicating that there is no journey identifier for a failed order creation, the target journey identifier is generated and stored in the database;

[0019] In response to the second detection result indicating the existence of a journey identifier for a failed order creation, the journey identifier for the failed order creation is determined as the target journey identifier.

[0020] In some embodiments, the method further includes:

[0021] Create an order for the target user;

[0022] In response to successful order creation, the validity period of the target journey identifier in the database is updated to the first duration;

[0023] In response to order creation failure, the validity period of the target journey identifier is updated in the database to a second duration, where the first duration is longer than the second duration.

[0024] In some embodiments, the method further includes:

[0025] The travel identifiers that have exceeded their expiration date will be deleted or invalidated in the database.

[0026] In some embodiments, the method further includes:

[0027] In response to order completion, the corresponding journey identifier is deleted or invalidated in the database.

[0028] In some embodiments, the order interaction request is an order management request, and determining the target journey identifier based on the order interaction request includes:

[0029] The target journey identifier is retrieved from the database based on the unique identifier.

[0030] In some embodiments, the method includes:

[0031] Generate and store the first log file.

[0032] In some embodiments, generating the response parameters corresponding to the order interaction request based on the target journey identifier includes:

[0033] Determine the execution result corresponding to the order interaction request;

[0034] Response parameters are generated based on the execution result and the target journey identifier. The response parameters include the target journey identifier and the execution result, so that the user terminal generates and stores a second log file based on the response parameters.

[0035] In some embodiments, the method further includes:

[0036] Generate control instructions based on the order interaction request;

[0037] Send the control command to the target control device.

[0038] In some embodiments, the method further includes:

[0039] Generate context information, which includes the target journey identifier;

[0040] The context information is sent to the target control device so that the target control device generates and stores a third log file based on the context information.

[0041] In some embodiments, the same journey includes successful scanning, order creation, order completion, and order settlement; or, the same journey includes scanning failure to successful scanning, and the time interval between scanning failure and successful scanning is less than a predetermined threshold.

[0042] Secondly, embodiments of the present invention provide an information interaction device, the device comprising:

[0043] The order interaction request receiving unit is used to receive order interaction requests sent by the user terminal.

[0044] The target journey identifier determination unit is used to determine the target journey identifier based on the order interaction request, wherein the journey identifier is used to identify a unique journey and remains unchanged within the same journey;

[0045] A response parameter generation unit is used to generate response parameters corresponding to the order interaction request based on the target journey identifier;

[0046] A response parameter sending unit is used to send the response parameters to the user terminal.

[0047] Thirdly, embodiments of the present invention provide an electronic device, including a memory and a processor, wherein the memory is used to store one or more computer program instructions, wherein the one or more computer program instructions are executed by the processor to implement the method as described in the first aspect.

[0048] Fourthly, embodiments of the present invention provide a computer program product comprising a computer program, wherein when the computer program is run on a computer, the computer executes the method described in the first aspect above.

[0049] Fifthly, embodiments of the present invention provide a computer-readable storage medium having computer program instructions stored thereon, which, when executed by a processor, implement the method described in the first aspect.

[0050] The technical solution of this invention receives an order interaction request sent by a user terminal, determines a target journey identifier based on the order interaction request, and the journey identifier is used to uniquely identify an order, remaining unchanged within the same order. Response parameters corresponding to the order interaction request are generated based on the target journey identifier and sent. Therefore, by introducing a unique journey identifier, the completeness and accuracy of user journey tracking can be improved, the difficulty of troubleshooting can be reduced, and the efficiency of root cause localization can be increased. Attached Figure Description

[0051] The above and other objects, features and advantages of the present invention will become clearer from the following description of embodiments of the invention with reference to the accompanying drawings, in which:

[0052] Figure 1 This is a schematic diagram of an information interaction system according to an embodiment of the present invention;

[0053] Figure 2 This is a flowchart of an information interaction method according to an embodiment of the present invention;

[0054] Figure 3 This is a flowchart of an information interaction method according to another embodiment of the present invention;

[0055] Figure 4 This is a schematic diagram of information interaction according to an embodiment of the present invention;

[0056] Figure 5This is a flowchart of a server information interaction method according to an embodiment of the present invention;

[0057] Figure 6 This is a schematic diagram of the information interaction device of the server according to an embodiment of the present invention;

[0058] Figure 7 This is a schematic diagram of an electronic device according to an embodiment of the present invention. Detailed Implementation

[0059] The present invention is described below based on embodiments, but the invention is not limited to these embodiments. In the detailed description of the invention below, certain specific details are described in detail. Those skilled in the art will fully understand the invention even without these details. To avoid obscuring the essence of the invention, well-known methods, processes, flows, elements, and circuits are not described in detail.

[0060] Furthermore, those skilled in the art should understand that the accompanying drawings provided herein are for illustrative purposes only and are not necessarily drawn to scale.

[0061] Unless the context explicitly requires it, words such as "including" or "contains" throughout the application documents should be interpreted as including rather than exclusive or exhaustive; that is, meaning "including but not limited to".

[0062] In the description of this invention, it should be understood that the terms "first," "second," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance. Furthermore, in the description of this invention, unless otherwise stated, "a plurality of" means two or more.

[0063] The solutions described in this specification and embodiments, if involving the processing of personal information, will be processed only under the premise of having a legal basis (such as obtaining the consent of the personal information subject, or being necessary for the performance of a contract), and will only be processed within the scope stipulated or agreed upon. A user's refusal to process personal information beyond what is necessary for basic functions will not affect the user's use of basic functions.

[0064] For ease of explanation, the information interaction method of this embodiment is illustrated using shared vehicles as an example. However, this embodiment does not limit its application scenarios. The technical solutions of this embodiment can be applied to any technical field involving information interaction, such as e-commerce, online education, telemedicine services, and Internet of Things applications.

[0065] Figure 1 This is a schematic diagram of an information interaction system according to an embodiment of the present invention. Figure 1As shown, the information interaction system of this embodiment includes a server 1, a user terminal 2, and a control device 3. The user terminal 2 and the control device 3 are communicatively connected to the server 1.

[0066] Server 1 serves as the management platform for the control device 3. User terminal 2 can manage or control the control device 3 through server 1.

[0067] This embodiment of the invention uses a user borrowing a vehicle in a shared vehicle scenario as an example for illustration. User terminal 2 is the terminal device used by the user borrowing the vehicle, which can be implemented through a mobile phone, tablet computer, or other data processing terminal. The control device 3 is the vehicle, and more specifically, the control device 3 is a smart lock installed on the vehicle. Server 1 is the service platform for shared vehicles, which can be a single server or a server cluster composed of multiple servers.

[0068] Specifically, users can access the shared vehicle service interface provided by server 1 through the APP (Application), mini-program or webpage of user terminal 2. Through the shared vehicle service interface, users can unlock, lock or perform other operations on the shared vehicle. For example, when the shared vehicle is a helmet, users can also unlock and lock the helmet.

[0069] In existing technologies, all operation requests sent from user terminal 2 to server 1 are marked with an identifier for each request. For example, if a user performs three operations during a ride—unlocking, locking, and payment—the server will generate three identifiers corresponding to unlocking, locking, and payment, respectively. This method of marking is relatively scattered and imprecise, making it difficult to achieve seamless connection and in-depth analysis of the entire chain of user behavior, from front-end application and server-side processing to execution on the control device. Especially when dealing with critical issues such as failed QR code scanning or lock / unlock malfunctions, the lack of a unified and unique identifier throughout the entire user journey leads to difficulties in troubleshooting and inefficient root cause localization.

[0070] Therefore, by introducing a unique journey identifier, the embodiments of the present invention can improve the completeness and accuracy of user journey tracking, reduce the difficulty of troubleshooting problems, and improve the efficiency of root cause localization.

[0071] Specifically, the information interaction methods differ depending on the information interaction request from the user terminal in this embodiment of the invention. These information interaction requests include order creation requests and order management requests.

[0072] The order creation request can be either a barcode scan request or an unlock request. When a user needs to borrow a vehicle, they scan the barcode (QR code or other barcode) on the vehicle to be redirected to the unlocking interface. Clicking the unlock control sends an unlock request to the server, which is also the order creation request. It should be noted that when the shared vehicle has NFC (Near Field Communication) functionality, the unlocking interface can also be accessed via NFC, and an unlock request can be sent.

[0073] Order management requests are other requests made after an order has been successfully created, such as lock requests and payment requests.

[0074] The following embodiments of the present invention describe order creation requests and order management requests respectively.

[0075] in, Figure 2 This is a flowchart of an information interaction method according to an embodiment of the present invention. Figure 2 The information interaction method shown describes the order creation request, specifically including the following steps:

[0076] Step S101: Send an order creation request.

[0077] In this embodiment, when a user needs to borrow a vehicle, they are redirected to the unlocking interface by scanning the barcode (QR code or barcode, etc.) on the vehicle. Clicking the unlocking control sends an unlocking request to the server, which is also an order creation request. In other words, the order creation request in this embodiment includes both a scanning request and an unlocking request.

[0078] The order creation request includes a unique identifier for the target user. The target user is the currently logged-in user of the user terminal, and the unique identifier can be information such as the user's registered account.

[0079] In some embodiments, the order creation request may also include QR code information read by scanning.

[0080] Step S102: Are there any incomplete orders?

[0081] In this embodiment, the server receives an order creation request sent by the user terminal, parses the order creation request to obtain the unique identifier of the target user, and determines a first detection result based on the unique identifier of the target user. The first detection result is used to characterize whether the target user has any incomplete orders.

[0082] Specifically, each time a user rents a bike for a ride, the server creates an order for that user. The order is completed after the user finishes riding, locks the bike, and pays. Therefore, the server can detect whether there are any incomplete orders based on the target user's unique identifier.

[0083] In response to the first detection result indicating the existence of incomplete orders, proceed to step S106.

[0084] In response to the first detection result indicating that there are no incomplete orders, proceed to step S103.

[0085] Step S103: Does a journey identifier exist?

[0086] In this embodiment, in response to the first detection result that there are no incomplete orders, the server determines a second detection result based on the user's unique identifier. The second detection result is used to characterize whether the target user has a journey identifier that indicates a failed order.

[0087] Specifically, when a user scans a QR code to rent a car, the order creation may fail for various reasons, but the server will create a journey identifier for the failed order. Therefore, when a user fails to rent a car the first time by scanning the code, and then tries to rent a car a second time, there will be a situation where there is no incomplete order but a journey identifier exists because the order was not created the first time.

[0088] The journey identifier includes a unique user identifier and a timestamp, and is stored in a database. Specifically, the database stores journey identifiers for incomplete orders and journey identifiers for orders that failed to be created.

[0089] The code for creating a journey identifier is as follows:

[0090] String userIdHexStr=Long.toHexString(userId);

[0091] String timeHexStr=Long.toHexString(System.currentTimeMillis());

[0092] String tripId=userIdHexStr+"gt"+timeHexStr;

[0093] The purpose of the code above is to generate a unique trip identifier (tripId) based on the user's unique identifier (userId) and the current timestamp (System.currentTimeMillis()). Hexadecimal strings are used to represent the unique identifier and timestamp, with a fixed string "gt" inserted as a separator between them.

[0094] The journey identifier is used to uniquely identify a journey, and it remains unchanged within the same journey. The same journey includes successful scan, order creation, order completion, and order settlement; alternatively, the same journey includes a scan failure followed by a successful scan, and the time interval between the scan failure and success is less than a predetermined threshold. The journey identifier has the following characteristics:

[0095] From the moment a user successfully scans the code to the creation of an order, to the completion of the order, and finally to payment, the business considers it to be the same journey.

[0096] If the interval between a user's failed scan and a successful scan is short, the business considers it as the same process.

[0097] The two successful scans created different cycling orders, which are considered different journeys from a business perspective.

[0098] The journey identifiers of user terminals, servers, and control devices must remain consistent throughout the same journey.

[0099] The lifecycle of the journey identifier is managed uniformly by the server.

[0100] Regarding the acquisition of the journey identifier, if the user currently has no incomplete orders and no journey identifier for a failed order, a new, unique, and valid journey identifier should be generated. If the user currently has incomplete orders, the journey identifier corresponding to the current order should be returned directly. If the user currently has no incomplete orders but a journey identifier for a failed order exists, the journey identifier corresponding to the current order should be returned directly.

[0101] Regarding the update of the journey identifier, in response to successful order creation, the validity period of the target journey identifier is updated to a first duration in the database; in response to order creation failure, the validity period of the target journey identifier is updated to a second duration in the database, where the first duration is longer than the second duration. That is, if an order is not successfully created after scanning the code, the validity period of the journey identifier is the second duration (e.g., 600 seconds); if an order is successfully created after scanning the code, the validity period of the journey identifier is the first duration (e.g., 30 days). The first duration is longer than the second duration. Furthermore, when the journey identifier is valid, the same user does not need to create a new journey identifier when scanning the code again; when the journey identifier is invalid, the same user needs to create a new journey identifier when scanning the code again.

[0102] For the deletion of a journey identifier, journey identifiers that have exceeded their expiration date will be deleted or invalidated in the database, and / or, in response to order completion, the corresponding journey identifier will be deleted or invalidated in the database. Specifically, once a user's ride order payment is completed, the journey identifier needs to be automatically invalidated or deleted. If a journey identifier has exceeded its expiration date, it needs to be automatically invalidated or deleted.

[0103] Therefore, the server retrieves the unique identifier corresponding to each journey identifier from the journey identifiers stored in the database as a candidate unique identifier, and checks whether there is a unique identifier that is the same as the unique identifier of the target user. If there is, it means that there is a journey identifier for creating a failed order; otherwise, it means that there is no journey identifier for creating a failed order.

[0104] In response to the second detection result indicating that there is no journey identifier for a failed order creation, proceed to step S104.

[0105] In response to the second detection result indicating the existence of a journey identifier for a failed order creation, the journey identifier for the failed order creation is determined as the target journey identifier, and the process proceeds to step S105.

[0106] Step S104: Generate and store the journey identifier.

[0107] In this embodiment, in response to the second detection result indicating that there is no journey identifier for a failed order creation, a journey identifier is generated and stored in the database. At this time, the generated journey identifier is the journey identifier corresponding to the target user, i.e., the target journey identifier.

[0108] Step S105: Create an order and update the database.

[0109] In this embodiment, after step S104 or 103, an order is created for the target user, and the database is updated based on the order creation result.

[0110] For updating the database, in response to successful order creation, the validity period of the target journey identifier is updated to a first duration in the database. In response to order creation failure, the validity period of the target journey identifier is updated to a second duration in the database, where the first duration is longer than the second duration.

[0111] Step S106: Determine the target journey identifier.

[0112] In this embodiment, the server determines the target journey identifier, which can be divided into three cases:

[0113] In the first scenario, if the server detects a completed order in step S102, the server will determine the journey identifier corresponding to the incomplete order as the target journey identifier.

[0114] In the second scenario, if the server detects in step S103 that there is no completed order and there is a journey identifier for a failed order, the server will determine the journey identifier for the failed order as the target journey identifier.

[0115] In the third scenario, if the server detects in step S103 that there is no completed order and no journey identifier for a failed order, the server will generate a new journey identifier and identify it as the target journey identifier.

[0116] Step S107: Send control command.

[0117] In this embodiment, if the order is successfully created, the server sends a control command to the control device, which is an unlocking command.

[0118] After receiving the control command, the control device executes the unlocking process and returns the unlocking result to the server, such as unlocking successful or unlocking failed.

[0119] Step S108: Send context information.

[0120] In this embodiment, the server generates context information corresponding to the target journey identifier based on the current order interaction request. The content of this context information varies depending on the content of each request. Specifically, the context information includes the target journey identifier and data content, including information such as the order identifier, the user's unique identifier, the vehicle identifier, and the time.

[0121] The transmission of journey identifiers between different programs within the server and between the server and control devices is achieved through context information.

[0122] In the process of transmitting context information, there are two parties: the service provider and the service consumer. The service provider is responsible for implementing and publishing the service; it exposes the service interface and handles invocation requests from the service consumer. The service consumer is the party that invokes the service provider's services. It initiates requests to the service provider when needed and receives the processing results.

[0123] For the service provider, key-value pairs are generated for the service consumer to use. The code for generating the key-value pairs is as follows:

[0124] TraceContext.getContext().getBizBaggageItems().put(SaasStatLogKeyConst.TRIP_ID,"xxxxxx");

[0125] Specifically, an API (Application Programming Interface) of a TraceContext is used to set a BizBaggage item in the current business tracing context. Specifically, it performs the following operations:

[0126] Obtaining the current tracing context: The tracing context instance for the current thread is obtained via TraceContext.getContext(). This tracing context is typically used in distributed systems to pass tracing information between different service calls.

[0127] Accessing BizBaggage Items: Retrieve the collection of BizBaggage items in the current tracking context by calling the `getBizBaggageItems()` method. BizBaggage is a mechanism that allows business-related metadata, such as a user's unique identifier and order identifier, to be passed through the call chain.

[0128] Setting up a business baggage item: The `put(SaasStatLogKeyConst.TRIP_ID,"xxxxxx")` method adds a key-value pair to the business baggage collection. Here, the key is `SaasStatLogKeyConst.TRIP_ID`, representing the name of the journey identifier, and the value "xxxxxx" is the actual value of the journey identifier, i.e., the hexadecimal string obtained above. This operation means that in the current tracing context, the journey identifier is set to "xxxxxx". Thus, in subsequent call chains, as long as the current tracing context is accessible, this journey identifier can be retrieved.

[0129] For service providers, the journey identifier can be obtained using the following code:

[0130] TraceContext.getContext().getBizBaggageItems().get(SaasStatLogKeyConst.TRIP_ID);

[0131] Obtain the current tracing context: Use the `TraceContext.getContext()` method to obtain the tracing context instance for the current thread. This context instance typically contains various information related to the current request or call chain, such as tracing identifiers, timestamps, and BizBaggage.

[0132] Accessing the BizBaggage Items Collection: Retrieve the collection of BizBaggage items in the current tracking context by calling the `getBizBaggageItems()` method. A BizBaggage is a container that stores business-related metadata, allowing this metadata to be transferred between different services in a distributed system.

[0133] Retrieve a specific business baggage item: Use the get(SaasStatLogKeyConst.TRIP_ID) method to retrieve the value associated with the key SaasStatLogKeyConst.TRIP_ID from the collection of business baggage items.

[0134] If a value associated with SaasStatLogKeyConst.TRIP_ID actually exists in the business baggage item collection, then this line of code will return that value. If such a value does not exist, it will return a message indicating that the retrieval failed.

[0135] After receiving a control command, the control device sends an identifier retrieval request to the server. The server retrieves context information based on the identifier retrieval request and sends it to the control device. The context information includes a target journey identifier. In some embodiments, the context information also includes a call chain tracing identifier, a user's unique identifier, session information, request source, authorization token, business data, etc.

[0136] Step S109: Generate the third log file and upload it.

[0137] In this embodiment, the control device generates and uploads a third log file. Specifically, the control device uploads the third log file to a third file system. The third log file includes information such as Vehicle ID, time information, Span ID, journey ID, service name, and log type.

[0138] Step S110: Determine the execution result.

[0139] In this embodiment, the server determines the execution result of the order creation request, which includes incomplete orders, order creation failure, successful unlocking, and unlocking failure.

[0140] Step S111: Generate the first log file and upload it.

[0141] In this embodiment, the server generates a first log file based on the execution result and the target journey identifier. The first log file includes information such as the target journey identifier, execution result, order identifier, user's unique identifier, vehicle identifier, time, and log type.

[0142] Furthermore, the server uploads the first log file to the first file system and stores it.

[0143] Step S112: Send response parameters.

[0144] In this embodiment, the server generates response parameters based on the execution result and the target journey identifier, the response parameters including the target journey identifier and the execution result.

[0145] The response parameters include a header and a data section, wherein the target journey identifier is stored in the header and the execution result is stored in the data section.

[0146] Step S113: Generate the second log file and upload it.

[0147] In this embodiment, the user terminal generates and stores a second log file based on the response parameters.

[0148] The second log file includes a target journey identifier, business parameters, and system parameters. The business parameters include information such as execution result, order identifier, user's unique identifier, vehicle identifier, and time. The system parameters include information such as operating system and program version number.

[0149] Furthermore, the user terminal uploads the second log file to the second file system and stores it.

[0150] The first, second, and third file systems mentioned above are all cloud-based log storage systems. They can be different subsystems within the same system or different systems in themselves.

[0151] This invention receives an order interaction request from a user terminal, determines a target journey identifier based on the request, and ensures that the journey identifier remains unchanged within the same order. Response parameters corresponding to the order interaction request are generated and sent based on the target journey identifier. Therefore, by introducing a unique journey identifier, the completeness and accuracy of user journey tracking can be improved, the difficulty of troubleshooting can be reduced, and the efficiency of root cause localization can be increased.

[0152] in, Figure 3 This is a flowchart of an information interaction method according to another embodiment of the present invention. Figure 3 The information interaction method shown describes an order management request, specifically including the following steps:

[0153] Step S201: Send an order management request.

[0154] In this embodiment, after a user completes a vehicle rental, they need to perform operations on the order, such as locking the vehicle, unlocking and locking the helmet, and making a payment. These operations are all order management requests. The order management request includes the target user's first identifier.

[0155] Step S202: Determine the target journey identifier.

[0156] In this embodiment, the order management request is generated after the order has been successfully created. Therefore, the server parses the order management request, obtains the first identifier of the target user, and determines the target journey identifier based on the unique identifier of the target user.

[0157] The server retrieves the unique identifiers corresponding to each journey identifier from the database as candidate unique identifiers, searches for candidate unique identifiers that are the same as the unique identifier of the target user, and determines the journey identifier corresponding to the found candidate unique identifier as the target journey identifier.

[0158] Step S203: Send control command.

[0159] Step S204: Send context information.

[0160] Step S205: Generate and upload the third log file.

[0161] Step S206: Determine the execution result.

[0162] Step S207: Generate the first log file and upload it.

[0163] Step S208: Send response parameters.

[0164] Step S209: Generate the second log file and upload it.

[0165] For steps S203-S209 above, refer to steps S107-S113, the implementation method is similar, and the embodiments of the present invention will not be described again here.

[0166] This invention receives an order interaction request from a user terminal, determines a target journey identifier based on the request, and ensures that the journey identifier remains unchanged within the same order. Response parameters corresponding to the order interaction request are generated and sent based on the target journey identifier. Therefore, by introducing a unique journey identifier, the completeness and accuracy of user journey tracking can be improved, the difficulty of troubleshooting can be reduced, and the efficiency of root cause localization can be increased.

[0167] It should be noted that the context information varies depending on the order interaction request in this embodiment of the invention, and the specific configuration can be adjusted according to the actual situation. Meanwhile, Figures 2-3 The information interactions shown are all illustrated using scenarios involving sending control commands to the control device. For order interaction requests that do not require sending control commands to the control device (such as payment requests), the command interaction process between the server and the control device can be omitted.

[0168] At the same time, in response to, Figures 2-3The interaction of context information between the server and the control device can be either the control device requesting to obtain context information or the server proactively sending context information to the control device, which can be configured according to the actual needs and scenarios.

[0169] Figure 4 This is a schematic diagram of information interaction according to an embodiment of the present invention. Figure 4 The illustrated embodiment shows the various modules and information interactions between the user terminal 2, server 1, and control device 3. Server 1 includes a database 11 and a service layer 12.

[0170] like Figure 4 As shown, the user terminal sends an order creation request to the server, and the order creation request includes the unique identifier of the target user.

[0171] After receiving an order creation request, the server checks whether the target user has any incomplete orders based on the target user's unique identifier.

[0172] If there are incomplete orders, the service layer 12 processes the order processing request. Specifically, this includes sending an identification request to the database 11 to retrieve the journey identifier of the incomplete order from the database as the target journey identifier, and generating an execution result.

[0173] If there are no incomplete orders, further check if there is a journey identifier corresponding to the unique identifier of the target user.

[0174] If a journey identifier exists, create an order for the target user and check if the order was created successfully. If the order is created successfully, update the validity period of the corresponding journey identifier to the first duration. If the order creation fails, update the validity period of the corresponding journey identifier to the second duration, and update the validity period in database 11.

[0175] If a journey identifier does not exist, a new journey identifier is created for the target user, and the created journey identifier is written to database 11. Simultaneously, an order is created for the target user, and the success of the order creation is checked. If the order is successfully created, the validity period of the corresponding journey identifier is updated to a first duration. If the order creation fails, the validity period of the corresponding journey identifier is updated to a second duration, and the validity period is updated in database 11. The first duration is longer than the second duration. This allows for a shorter validity period for journey identifiers corresponding to failed orders, enabling the deletion or invalidation of these identifiers within a shorter timeframe. Conversely, a longer validity period for journey identifiers corresponding to successfully created orders prevents the deletion or invalidation of journey identifiers before the order is completed.

[0176] Simultaneously, when the server processes an order creation request, if the order is successfully created, the server sends a control command to the control device to unlock it. The control device sends an identification request to the server to obtain the journey identifier and generates a third log file. This third log file includes information such as Vehicle ID, time information, Span ID, journey identifier, service name, and log type. The third log file is then uploaded to a third file system and stored.

[0177] Simultaneously, the server can also receive order management requests sent by user terminals. These requests include a unique identifier for the target user. Service layer 12 obtains the corresponding target journey identifier based on the target user's unique identifier and processes the order management request to obtain the execution result. Meanwhile, server 1 generates a first log file based on the execution result and the target journey identifier. The first log file includes information such as the target journey identifier, execution result, order identifier, user's unique identifier, vehicle identifier, time, and log type. The first log file is then uploaded to and stored in the first file system.

[0178] Furthermore, the server generates response parameters based on the target journey identifier and execution result, and sends them to user terminal 2. These response parameters include a header and a data section; the target journey identifier is stored in the header, and the execution result is stored in the data section. The server sends the response parameters to user terminal 2 via Hypertext Transfer Protocol (HTTP). The user terminal generates and stores a second log file based on the response parameters. The second log file includes the target journey identifier, business parameters, and system parameters. The business parameters include the execution result, order identifier, user's unique identifier, vehicle identifier, and time information. The system parameters include the operating system and program version number information.

[0179] In some embodiments, the information interaction method of this invention further includes: obtaining a log file from a file system based on the journey identifier, and obtaining analysis results based on the log file. The file system includes a first file system, a second file system, and a third file system; correspondingly, the log file includes a first log file, a second log file, and a third log file. The first file system stores the first log file, the second file system stores the second log file, and the third file system stores the third log file. Obtaining the log file from the file system based on the journey identifier specifically involves: obtaining a log file with the same journey identifier from the file system; parsing the log file to obtain journey-related information; and determining analysis results based on the obtained journey-related information. The analysis results include at least one of problem investigation, user behavior analysis, and user experience optimization.

[0180] This invention uses journey identifiers to connect user access behaviors during the user's QR code scanning and vehicle booking process, including failed scanning and the complete journey from scanning the vehicle, unlocking to create an order, locking to close the order, and finally completing payment. By observing and tracking the user access behavior chain, it enables the investigation and root cause localization of abnormal issues such as vehicle and helmet locking / unlocking, digitally measures changes in the funnel transformation at each level during product feature updates and iterations, and analyzes the performance time from the user initiating the locking / unlocking process to the smart device issuing the command, and from the successful locking / unlocking of the vehicle to the user's perception of successful locking / unlocking.

[0181] This invention receives an order interaction request from a user terminal, determines a target journey identifier based on the request, and ensures that the journey identifier remains unchanged within the same order. Response parameters corresponding to the order interaction request are generated and sent based on the target journey identifier. Therefore, by introducing a unique journey identifier, the completeness and accuracy of user journey tracking can be improved, the difficulty of troubleshooting can be reduced, and the efficiency of root cause localization can be increased.

[0182] Figure 5 This is a flowchart of a server information interaction method according to an embodiment of the present invention. Figure 5 As shown, the information interaction method of the server in this embodiment of the invention includes the following steps:

[0183] Step S310: Receive the order interaction request sent by the user terminal.

[0184] Step S320: Determine the target journey identifier based on the order interaction request, wherein the journey identifier is used to identify a unique journey and remains unchanged within the same journey.

[0185] Step S330: Generate response parameters corresponding to the order interaction request based on the target journey identifier.

[0186] Step S340: Send the response parameters to the user terminal.

[0187] In some embodiments, the journey identifier includes a user's unique identifier and a timestamp, and the journey identifier is stored in a database.

[0188] In some embodiments, the order interaction request includes a unique identifier for the target user.

[0189] In some embodiments, the order interaction request is an order creation request, and determining the target journey identifier based on the order interaction request includes:

[0190] A first detection result is determined based on the unique identifier of the target user, and the first detection result is used to characterize whether the target user has any incomplete orders;

[0191] In response to the first detection result indicating the existence of an incomplete order, the journey identifier corresponding to the incomplete order is determined as the target journey identifier;

[0192] In response to the first detection result indicating that there are no incomplete orders, the target journey identifier is determined based on the second detection result, which is used to characterize whether the target user has a journey identifier for creating a failed order.

[0193] In some embodiments, determining the target journey identifier based on the second detection result includes:

[0194] The second detection result is determined based on the database;

[0195] In response to the second detection result indicating that there is no journey identifier for a failed order creation, the target journey identifier is generated and stored in the database;

[0196] In response to the second detection result indicating the existence of a journey identifier for a failed order creation, the journey identifier for the failed order creation is determined as the target journey identifier.

[0197] In some embodiments, the method further includes:

[0198] Create an order for the target user;

[0199] In response to successful order creation, the validity period of the target journey identifier in the database is updated to the first duration;

[0200] In response to order creation failure, the validity period of the target journey identifier is updated in the database to a second duration, where the first duration is longer than the second duration.

[0201] In some embodiments, the method further includes:

[0202] The travel identifiers that have exceeded their expiration date will be deleted or invalidated in the database.

[0203] In some embodiments, the method further includes:

[0204] In response to order completion, the corresponding journey identifier is deleted or invalidated in the database.

[0205] In some embodiments, the order interaction request is an order management request, and determining the target journey identifier based on the order interaction request includes:

[0206] The target journey identifier is retrieved from the database based on the unique identifier.

[0207] In some embodiments, the method includes:

[0208] Generate and store the first log file.

[0209] In some embodiments, generating the response parameters corresponding to the order interaction request based on the target journey identifier includes:

[0210] Determine the execution result corresponding to the order interaction request;

[0211] Response parameters are generated based on the execution result and the target journey identifier. The response parameters include the target journey identifier and the execution result, so that the user terminal generates and stores a second log file based on the response parameters.

[0212] In some embodiments, the method further includes:

[0213] Generate control instructions based on the order interaction request;

[0214] Send the control command to the target control device.

[0215] In some embodiments, the method further includes:

[0216] Generate context information, which includes the target journey identifier;

[0217] The context information is sent to the target control device so that the target control device generates and stores a third log file based on the context information.

[0218] In some embodiments, the same journey includes successful scanning, order creation, order completion, and order settlement; or, the same journey includes scanning failure to successful scanning, and the time interval between scanning failure and successful scanning is less than a predetermined threshold.

[0219] This invention receives an order interaction request from a user terminal, determines a target journey identifier based on the request, and ensures that the journey identifier remains unchanged within the same order. Response parameters corresponding to the order interaction request are generated and sent based on the target journey identifier. Therefore, by introducing a unique journey identifier, the completeness and accuracy of user journey tracking can be improved, the difficulty of troubleshooting can be reduced, and the efficiency of root cause localization can be increased.

[0220] Figure 6 This is a schematic diagram of the information interaction device of the server according to an embodiment of the present invention. Figure 6 As shown, the information interaction device of the server in this embodiment of the invention includes an order interaction request receiving unit 61, a target journey identifier determining unit 62, a response parameter generating unit 63, and a response parameter sending unit 64. The order interaction request receiving unit 61 receives an order interaction request sent by a user terminal. The target journey identifier determining unit 62 determines a target journey identifier based on the order interaction request, wherein the journey identifier is used to uniquely identify a journey and remains unchanged within the same journey. The response parameter generating unit 63 generates response parameters corresponding to the order interaction request based on the target journey identifier. The response parameter sending unit 64 sends the response parameters to the user terminal.

[0221] In some embodiments, the journey identifier includes a user's unique identifier and a timestamp, and the journey identifier is stored in a database.

[0222] In some embodiments, the order interaction request includes a unique identifier for the target user.

[0223] In some embodiments, the order interaction request is an order creation request, and the target journey identifier determination unit includes:

[0224] The first detection result acquisition subunit is used to determine the first detection result based on the unique identifier of the target user. The first detection result is used to characterize whether the target user has any incomplete orders.

[0225] The first determining subunit is configured to, in response to the first detection result indicating the existence of an incomplete order, determine the journey identifier corresponding to the incomplete order as the target journey identifier;

[0226] The second determining subunit is used to determine the target journey identifier based on the second detection result in response to the first detection result indicating that there are no incomplete orders. The second detection result is used to characterize whether the target user has a journey identifier indicating that a failed order was created.

[0227] In some embodiments, the second determining subunit includes:

[0228] The second detection result acquisition module is used to determine the second detection result based on the database;

[0229] The identifier generation module is configured to generate the target journey identifier and store it in the database in response to the second detection result indicating that there is no journey identifier for a failed order creation.

[0230] The identifier determination module is used to determine the journey identifier of the failed order as the target journey identifier in response to the second detection result indicating that there is a journey identifier of a failed order.

[0231] In some embodiments, the apparatus further includes:

[0232] An order creation unit is used to create an order for the target user.

[0233] The first update unit is used to update the validity period of the target journey identifier to a first duration in the database in response to the successful creation of the order;

[0234] The second update unit is used to update the validity period of the target journey identifier in the database to a second duration in response to the order creation failure, wherein the first duration is longer than the second duration.

[0235] In some embodiments, the apparatus further includes:

[0236] The first invalidation unit is used to delete or invalidate journey identifiers that have exceeded their validity period in the database.

[0237] In some embodiments, the apparatus further includes:

[0238] The second invalidation unit is used to delete or invalidate the corresponding journey identifier in the database in response to order completion.

[0239] In some embodiments, the order interaction request is an order management request, and the target journey identifier determination unit is used for:

[0240] The target journey identifier is retrieved from the database based on the unique identifier.

[0241] In some embodiments, the apparatus further includes:

[0242] The first log storage unit is used to generate and store the first log file.

[0243] In some embodiments, the response parameter generation unit includes:

[0244] The execution result acquisition subunit is used to determine the execution result corresponding to the order interaction request;

[0245] The parameter generation subunit is used to generate response parameters based on the execution result and the target journey identifier. The response parameters include the target journey identifier and the execution result, so that the user terminal generates and stores a second log file based on the response parameters.

[0246] In some embodiments, the apparatus further includes:

[0247] A control instruction generation unit is used to generate control instructions based on the order interaction request.

[0248] A control command sending unit is used to send the control command to the target control device.

[0249] In some embodiments, the apparatus further includes:

[0250] A context information generation unit is used to generate context information, the context information including the target journey identifier;

[0251] The context information sending unit is used to send the context information to the target control device, so that the target control device generates and stores a third log file based on the context information.

[0252] In some embodiments, the same journey includes successful scanning, order creation, order completion, and order settlement; or, the same journey includes scanning failure to successful scanning, and the time interval between scanning failure and successful scanning is less than a predetermined threshold.

[0253] This invention receives an order interaction request from a user terminal, determines a target journey identifier based on the request, and ensures that the journey identifier remains unchanged within the same order. Response parameters corresponding to the order interaction request are generated and sent based on the target journey identifier. Therefore, by introducing a unique journey identifier, the completeness and accuracy of user journey tracking can be improved, the difficulty of troubleshooting can be reduced, and the efficiency of root cause localization can be increased.

[0254] Figure 7 This is a schematic diagram of an electronic device according to an embodiment of the present invention. Figure 7The illustrated electronic device is a general-purpose data processing device, comprising a general-purpose computer hardware architecture, including at least a processor 71 and a memory 72. The processor 71 and memory 72 are connected via a bus 73. The memory 72 is adapted to store instructions or programs executable by the processor 71. The processor 71 can be a standalone microprocessor or a collection of one or more microprocessors. Thus, the processor 71 executes the instructions stored in the memory 72, thereby performing the method flow of the embodiments of the present invention as described above to process data and control other devices. The bus 73 connects the aforementioned components together, and also connects these components to a display controller 74, a display device, and an input / output (I / O) device 75. The input / output (I / O) device 75 can be a mouse, keyboard, modem, network interface, touch input device, motion-sensing input device, printer, and other devices known in the art. Typically, the input / output device 75 is connected to the system via an input / output (I / O) controller 76.

[0255] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, apparatus (devices), or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can be implemented as a computer program product on one or more computer-readable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0256] This invention is described with reference to flowchart illustrations of methods, apparatus (devices), and computer program products according to embodiments of this application. It should be understood that each step in the flowchart can be implemented by computer program instructions.

[0257] These computer program instructions may be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including an instruction means, the implementation process of which is described in the instruction means. Figure 1 The function specified in one or more processes.

[0258] These computer program instructions may also be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing device, produce instructions for implementing processes. Figure 1 A device for a function specified in one or more processes.

[0259] The above description is merely a preferred embodiment of the present invention and is not intended to limit the invention. For those skilled in the art, the present invention can be modified and varied in various ways. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principle of the present invention should be included within the scope of protection of the present invention.

Claims

1. An information exchange method, characterized in that, The method includes: Receive order interaction requests sent by user terminals; The target journey identifier is determined based on the order interaction request, wherein the journey identifier is used to identify a unique journey and remains unchanged within the same journey; Generate response parameters corresponding to the order interaction request based on the target journey identifier; The response parameters are sent to the user terminal.

2. The method according to claim 1, characterized in that, The journey identifier includes a unique identifier for the user and a timestamp, and the journey identifier is stored in a database.

3. The method according to claim 2, characterized in that, The order interaction request includes the unique identifier of the target user.

4. The method according to claim 3, characterized in that, The order interaction request is an order creation request, and determining the target journey identifier based on the order interaction request includes: A first detection result is determined based on the unique identifier of the target user, and the first detection result is used to characterize whether the target user has any incomplete orders; In response to the first detection result indicating the existence of an incomplete order, the journey identifier corresponding to the incomplete order is determined as the target journey identifier; In response to the first detection result indicating that there are no incomplete orders, the target journey identifier is determined based on the second detection result, which is used to characterize whether the target user has a journey identifier for creating a failed order.

5. The method according to claim 4, characterized in that, The step of determining the target journey identifier based on the second detection result includes: The second detection result is determined based on the database; In response to the second detection result indicating that there is no journey identifier for a failed order creation, the target journey identifier is generated and stored in the database; In response to the second detection result indicating the existence of a journey identifier for a failed order creation, the journey identifier for the failed order creation is determined as the target journey identifier.

6. The method according to claim 5, characterized in that, The method further includes: Create an order for the target user; In response to successful order creation, the validity period of the target journey identifier in the database is updated to the first duration; In response to order creation failure, the validity period of the target journey identifier is updated in the database to a second duration, where the first duration is longer than the second duration.

7. The method according to claim 6, characterized in that, The method further includes: The travel identifiers that have exceeded their expiration date will be deleted or invalidated in the database.

8. The method according to claim 6, characterized in that, The method further includes: In response to order completion, the corresponding journey identifier is deleted or invalidated in the database.

9. The method according to claim 3, characterized in that, The order interaction request is an order management request, and determining the target journey identifier based on the order interaction request includes: The target journey identifier is retrieved from the database based on the unique identifier.

10. The method according to claim 1, characterized in that, The method includes: Generate and store the first log file.

11. The method according to claim 1, characterized in that, The step of generating the response parameters corresponding to the order interaction request based on the target journey identifier includes: Determine the execution result corresponding to the order interaction request; Response parameters are generated based on the execution result and the target journey identifier. The response parameters include the target journey identifier and the execution result, so that the user terminal generates and stores a second log file based on the response parameters.

12. The method according to claim 1, characterized in that, The method further includes: Generate control instructions based on the order interaction request; Send the control command to the target control device.

13. The method according to claim 1, characterized in that, The method further includes: Generate context information, which includes the target journey identifier; The context information is sent to the target control device so that the target control device generates and stores a third log file based on the context information.

14. The method according to claim 1, characterized in that, The same journey includes successful scanning, order creation, order completion, and order settlement; or, the same journey includes scanning failure to successful scanning, and the time interval between scanning failure and successful scanning is less than a predetermined threshold.

15. An information interaction device, characterized in that, The device includes: The order interaction request receiving unit is used to receive order interaction requests sent by the user terminal. The target journey identifier determination unit is used to determine the target journey identifier based on the order interaction request, wherein the journey identifier is used to identify a unique journey and remains unchanged within the same journey; A response parameter generation unit is used to generate response parameters corresponding to the order interaction request based on the target journey identifier; A response parameter sending unit is used to send the response parameters to the user terminal.

16. An electronic device comprising a memory and a processor, characterized in that, The memory is used to store one or more computer program instructions, wherein the one or more computer program instructions are executed by the processor to implement the method as described in any one of claims 1-14.

17. A computer program product comprising a computer program, characterized in that, When the computer program is run on a computer, the computer performs the method according to any one of claims 1-14.

18. A computer-readable storage medium storing computer program instructions thereon, characterized in that, The computer program instructions, when executed by a processor, implement the method as described in any one of claims 1-14.

Images