CN116911839A - Charging order processing method, electronic equipment and storage medium - Google Patents

Charging order processing method, electronic equipment and storage medium Download PDF

Info

Publication number
CN116911839A
CN116911839A CN202310711997.0A CN202310711997A CN116911839A CN 116911839 A CN116911839 A CN 116911839A CN 202310711997 A CN202310711997 A CN 202310711997A CN 116911839 A CN116911839 A CN 116911839A
Authority
CN
China
Prior art keywords
charging
operator
feedback information
order
instruction
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202310711997.0A
Other languages
Chinese (zh)
Inventor
郑文杰
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Human Horizons Shanghai Internet Technology Co Ltd
Original Assignee
Human Horizons Shanghai Internet Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Human Horizons Shanghai Internet Technology Co Ltd filed Critical Human Horizons Shanghai Internet Technology Co Ltd
Priority to CN202310711997.0A priority Critical patent/CN116911839A/en
Publication of CN116911839A publication Critical patent/CN116911839A/en
Pending legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/14—Payment architectures specially adapted for billing systems
    • G06Q20/145—Payments according to the detected use or quantity
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/06—Energy or water supply

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Economics (AREA)
  • Theoretical Computer Science (AREA)
  • Health & Medical Sciences (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Finance (AREA)
  • Strategic Management (AREA)
  • Development Economics (AREA)
  • Public Health (AREA)
  • Water Supply & Treatment (AREA)
  • General Health & Medical Sciences (AREA)
  • Human Resources & Organizations (AREA)
  • Marketing (AREA)
  • Primary Health Care (AREA)
  • Tourism & Hospitality (AREA)
  • Charge And Discharge Circuits For Batteries Or The Like (AREA)

Abstract

The application provides a charging order processing method, electronic equipment and a storage medium. The method may include: and responding to the creation instruction of the charging order, and detecting feedback information of the operator aiming at the creation instruction. And under the condition that the feedback information is delayed to push as a result of detection, inquiring whether the operator has charged or not. And sending charging data of the operator to the user side to display the charging data by the user side under the condition that the query result is charged. The application solves the problem of delay of pushing various status messages of the charging operator, ensures the continuity of the charging experience of the user and simultaneously ensures and protects the rights and interests of the charging operator.

Description

Charging order processing method, electronic equipment and storage medium
Technical Field
The present application relates to the field of intelligent transportation technologies, and in particular, to a method for processing a charging order, an electronic device, and a storage medium.
Background
Along with the promotion of new energy automobile popularity, the requirement of the user to the charging service of new energy automobile also increases. Such as convenience of charging, security of payment, etc. For operators of charging piles, the number of charging users is large, so that information pushing delay of the operators is usually caused. The occurrence of the above delay has a certain impact on the charging experience of the user or the normal charging of the operator.
Disclosure of Invention
The embodiment of the application provides a processing method of a charging order, electronic equipment and a storage medium, solves the problem of pushing delay of various status messages of a charging operator, and ensures and protects the rights and interests of the charging operator while ensuring the continuity of charging experience of users.
In a first aspect, an embodiment of the present application provides a method for processing a charging order, where the method may include:
and responding to the creation instruction of the charging order, and detecting feedback information of the operator aiming at the creation instruction.
And under the condition that the feedback information is delayed to push as a result of detection, inquiring whether the operator has charged or not.
And sending charging data of the operator to the user side to display the charging data by the user side under the condition that the query result is charged.
In a second aspect, an embodiment of the present application provides an electronic device, including a memory, a processor, and a computer program stored on the memory, the processor implementing any one of the methods described above when the computer program is executed.
In a third aspect, an embodiment of the present application provides a vehicle having a computer program stored in a readable storage medium of the vehicle, which when executed by a processor implements the method of any one of the above.
Compared with the prior art, the application has the following advantages:
according to the embodiment of the application, under the condition that the delayed pushing of the feedback information is detected, the effectiveness of the charging order is maintained first, so that the continuity of charging experience of a user side is protected. In addition, whether the charging pile on the operator side is charged or not can be detected, and order processing is performed on the detection result. For example, if charging is started, charging can be continued, and charging data is sent to the client side so that the client side can update and display the charging data periodically. Otherwise, order closing processing is carried out, which also ensures the rights and interests of operators.
The foregoing description is only an overview of the present application, and is intended to provide a better understanding of the technical means of the present application, as it is embodied in the present specification, and is intended to provide a better understanding of the above and other objects, features and advantages of the present application, as it is embodied in the following description.
Drawings
In the drawings, the same reference numerals refer to the same or similar parts or elements throughout the several views unless otherwise specified. The figures are not necessarily drawn to scale. It is appreciated that these drawings depict only some embodiments according to the application and are not therefore to be considered limiting of its scope.
FIG. 1 is a flow chart of a method for processing a charging order according to an embodiment of the application;
FIG. 2 is a schematic diagram of a method for processing a charging order according to an embodiment of the application;
FIG. 3 is a second schematic diagram of a method for processing a charging order according to an embodiment of the application; and
fig. 4 is a block diagram of an electronic device used to implement an embodiment of the application.
Detailed Description
Hereinafter, only certain exemplary embodiments are briefly described. As will be recognized by those skilled in the pertinent art, the described embodiments may be modified in numerous different ways without departing from the spirit or scope of the present application. Accordingly, the drawings and description are to be regarded as illustrative in nature, and not as restrictive.
In order to facilitate understanding of the technical solutions of the embodiments of the present application, the following describes related technologies of the embodiments of the present application. The following related technologies may be optionally combined with the technical solutions of the embodiments of the present application, which all belong to the protection scope of the embodiments of the present application.
An embodiment of the present application provides a method for processing a charging order, as shown in fig. 1, which is a flowchart of a method for processing a charging order according to an embodiment of the present application, and may include:
step S101: and responding to the creation instruction of the charging order, and detecting feedback information of the operator aiming at the creation instruction.
Step S102: and under the condition that the feedback information is delayed to push as a result of detection, inquiring whether the operator has charged or not.
Step S103: and sending charging data of the operator to the user side to display the charging data by the user side under the condition that the query result is charged.
The execution main body of the processing method of the charging order can be a service platform or a cloud server of an application program and the like. The service platform or cloud server of the application program may be collectively referred to as a server, and the description below uses an execution body as the server. The application may be a charging type application running on the user side. And the user initiates a charging request through an application program at the user side, so that a charging order creation instruction is generated at the user side.
The service side may issue a charging request to the operator based on the creation instruction of the charging order. The carrier may respond synchronously to the charge request to inform the server that the charge request has been received by the carrier. In addition, the operator generates an instruction for controlling the start of the charging pile, and the instruction for controlling the start of the charging pile is sent to the charging pile in an asynchronous mode, so that the charging pile is started to charge the new energy vehicle.
And under the condition that the charging pile is started normally, sending state change information to an operator. The state change information may be used as feedback information for the creation instruction. The state change information is used for informing an operator that the charging pile has been changed from the unopened state to the opened state. The operator informs the server of the information. The information transmission between the operator and the service end can adopt a message queue mode. And the operator sends the charging pile state change information to the server, and finally the server informs the user that the charging pile is started.
Correspondingly, for the user side, the state of the charging order generally includes an on-line state and an off-state. The online state includes waiting for feedback information, presentation of charging data, and the like. The charge data may include charge amount data, charge duration data, order amount data, and the like. The off state is the closing of the charge order. Typically, an operator may communicate with a plurality of charging piles, and there may be a situation in which information in a message queue is squeezed due to the influence of the number of charging piles or due to the influence of network quality, thereby causing a feedback information push delay. For example, the charging pile is started normally, but the service end cannot learn that the charging pile is started normally in time due to the fact that the feedback information delays pushing. In this way, the server triggers the protection to automatically close or cancel the charging order, and the state of the charging order at the client is changed from the on-line state to the off-state. Thus, bad account may occur for the operator, which may be caused by the charging stake being started but not being charged. For the user, if order cancellation or closing is often encountered, trust in the carrier's product is also reduced.
In the application, in response to the instruction of creating the charging order, the service end sends a charging request to the operator. Meanwhile, the server side also starts the detection of feedback information of the operator aiming at the creation instruction. The detection of feedback information of an operator for a creation instruction may be mainly embodied in detecting whether the feedback information is delayed in pushing. If the detection result is that the pushing is not delayed, the application program of the user terminal can be controlled to display the charging data on the display interface. Otherwise, if the detection result is delayed push, the charging order can be kept valid temporarily. The temporary and effective maintenance of the charging order can be that a trigger instruction of an offline state is sent to the user terminal, and the user terminal can change the charging order into the offline state under the condition that the user terminal receives the trigger instruction of the offline state. The offline state may be used as a third state other than the online state and the off state newly created by the present application. In the offline state, the feedback information does not need to be continuously waited, and the charging order can be kept valid.
Meanwhile, the server side can also perform corresponding processing on the charging order based on the query result of whether the operator starts charging. For example, a query may be made as to whether the operator has already charged. If the query result is that charging fails, the charging order can be closed. Otherwise, if the query result is that charging is started, notification information can be sent to the user side. The notification information may include interpretation information of delayed pushing of the feedback information, notification information that the charging has been started, related information of charging data, etc., so as to continue the charging process.
Through the above process, under the condition that the delayed pushing of the feedback information is detected, the effectiveness of the charging order is maintained first, so that the continuity of the charging experience of the user side is protected. In addition, whether the charging pile on the operator side is charged or not can be detected, and order processing is performed on the detection result. For example, if charging is started, charging can be continued, and charging data is sent to the client side so that the client side can update and display the charging data periodically. Otherwise, order closing processing is carried out, which also ensures the rights and interests of operators.
In one embodiment, the determining the basis for the feedback information delay push in step S102 may include:
step S1021: after sending the charge order creation instruction to the operator, starting timing.
Step S1022: and determining that the feedback information is delayed to be pushed under the condition that the feedback information is not received after the first designated time length.
Responding to the creation instruction of the charging order, and sending the creation instruction of the charging order to an operator on the one hand; on the other hand, the detection of feedback information of the operator for the creation instruction is started. For detection, it may be embodied in detecting whether the feedback information is delayed in pushing. Thus, the timing may be started after the creation instruction of the charge order is sent to the carrier.
Correspondingly, the time when the creation instruction of the charging order is sent to the operator can be taken as the starting time t 0 . From the starting time t 0 Starting the timing. The first specified duration may correspond to t 1 Time, i.e. from the start time t 0 Starting until t 1 And if the feedback information is not received at all times, determining that the feedback information is delayed to be pushed. Illustratively t 1 Time and t 0 Time of dayThe difference may be 60 seconds, 90 seconds, etc.
In one embodiment, the determining manner of the query result in step S103 may include:
step S1031: and starting timing under the condition that the feedback information is delayed to push as a result of detection.
Step S1032: and determining a query result according to the acquired charging data of the operator after the second designated time period.
The time when the charge order creation command is sent to the operator can be used as the starting time t 0 . From the starting time t 0 Starting the timing. If from the starting time t 0 Starting until t 1 And if the feedback information is not received at all times, determining that the feedback information is delayed to be pushed. Thus, in the case that the feedback information is delayed to push as a result of detection, the start timing may correspond to t 1 Timing started by the moment. The second time period may correspond to t 2 Time of day. Correspondingly, t 2 Time and t 1 The difference in time of day may be 3 minutes, 5 minutes, etc. That is, at t 2 The time of day may be communicated to the carrier to obtain charging data for the carrier. By means of communication with operators, specific charge amount distribution can be distinguished by setting active inquiry timing tasks crossing charging time period points based on electric vehicle charging and changing service information exchange (part 3: service information exchange specification) of electric vehicle (T/TEC 102.3-2016) of China electric power enterprises Association standards, and therefore charging cost based on a custom charging policy can be accurately calculated. Correspondingly, the information such as the charge order code, the interface code of the charging equipment, the interface state of the charging equipment, the current and voltage of the phase A, the phase B and the phase C, the charging starting time, the sampling time, the accumulated charge amount and the like can be obtained through the active inquiry timing task, and the accumulated electricity charge can be calculated according to the information. Wherein the interface code of the charging device is typically composed of a string of numbers, which may be used as a unique identifier of the charging device. The interface states of the charging device may include 1-idle, 2-occupied but uncharged, 3-occupied and charging, 4-occupied and reserved lock, 255-fault, etcClass. If the accumulated charge amount is not 0 (positive number), the query result can be determined to be charged. Otherwise, if the accumulated charge quantity is 0, it can be determined that the query result is not charged.
For the situation that the operator starts charging (the charging electric quantity and the charge are actually generated), but the feedback information is delayed to be pushed due to the fact that the operator fails to call back the state information, and finally the server judges that the starting is overtime and automatically cancels the order, through the process, the server autonomously detects whether the operator starts charging or not. For the condition that charging is started, the charging order can be kept valid, so that the rights and interests of operators can be ensured.
In one embodiment, the second specified time period is configured to be any value from 3 minutes to 5 minutes.
Correspondingly, the second specified duration may be any value within 3 minutes to 5 minutes, such as 3 minutes 30 seconds, 4 minutes 05 seconds, 5 minutes, etc. The specific value may be set according to the scene.
In one embodiment, the method may further include:
and canceling the charging order under the condition that the query result is uncharged.
And under the condition that the query result is uncharged, the charging order can be canceled. Thus, since the client is in the offline mode, the client has no anxiety about waiting, and does not have negative emotion to the operator, and the operator cannot charge, so that the cancellation of the charging order does not cause substantial loss to the operator. Further, as the operator fails to charge, the related information of the charging pile which fails to charge can be sent to the operator, so that the operator can conduct fault investigation in time. For canceling a charge order, different treatments may be performed for the payment mode of the user. For example, for pay-per-payment mode, canceling the charge order includes a refund process. For post-paid mode, the charge order may be turned off directly.
In one embodiment, in a case of receiving a settlement instruction for the charging order, the method may further include:
step S104: after the settlement instruction of the charging order is sent to the operator, timing is started.
Step S105: and under the condition that the feedback information of the settlement instruction is not received after the first designated time length, determining that the feedback information of the settlement instruction is delayed to push.
Step S106: and settling the charging order based on the moment of receiving the settlement instruction of the electric order.
The order settlement instruction of the charging order can be issued by the user at the user side, and the order settlement instruction of the charging order can be sent to the operator under the condition that the order settlement instruction of the charging order issued by the user through voice or touch and the like is received. And starting timing after sending.
Correspondingly, the time when the settlement instruction of the charging order is sent to the operator can be taken as the starting time t 3 . From the starting time t 3 Starting the timing. The first specified duration may correspond to t 4 Time, i.e. from the start time t 3 Starting until t 4 And if the feedback information of the settlement instruction cannot be received at any moment, the delayed pushing of the feedback information of the settlement instruction can be determined. Thus t 4 Time and t 3 The difference in time of day may be any value from 30 seconds to 90 seconds, such as 60 seconds, 90 seconds, etc. Typically, the maximum time that the feedback information of the settlement instruction is delayed to push is 7 days.
In this case, the settlement of the charge order may be performed based on the timing at which the settlement instruction of the electric order is received. For example, the time of the settlement instruction of the charging order issued by the user at the user side can be recorded as t 5 Because the communication delay between the user side and the service side is negligible, the time when the service side receives the settlement instruction for the charging order can be recorded as t 5 . It will be appreciated that t 5 Time t is earlier than t 3 Time of day. The time t when the charge order creation instruction is sent to the operator is as described above 0 Time of day. Thus, it can be based on t 5 Time and t 0 The difference in time determines the charge duration Δt. Correspondingly, the corresponding amount of the accumulated charge quantity generated by the charge duration delta tI.e. the charging amount.
Therefore, for the user side, the whole charging process is completed, and in the charging process, even if the feedback information of the creation instruction is delayed to be pushed due to the number of charged people or network delay, or the feedback information of the settlement instruction is delayed to be pushed. As a server, the verification of the validity of the charging order can be completed. And for orders which are charged by the operators, the orders can be reserved, and the occurrence of bad orders of the operators is reduced.
In one embodiment, the first specified duration is configured to be any value from 30 seconds to 90 seconds.
Specifically, the first specified duration may be 30 seconds, 41 seconds, 52 seconds, or the like. Any integer of 30 seconds to 90 seconds is satisfied. The duration may be set by the user at his own initiative or may be set for the operator. For example, 60 seconds may be set for operator a and 70 seconds may be set for operator B.
In one embodiment, the method further comprises:
and sending an offline state triggering instruction to the user terminal under the condition that feedback information is pushed in a delayed mode.
The offline state may be a third state other than the online state and the off state. In the offline state, the feedback information does not need to be continuously waited, and the charging order can be kept valid. Therefore, under the condition that feedback information is delayed to push, the user side can be controlled to be switched into an offline state, and therefore anxiety emotion of the user can be relieved. When the user terminal is in an offline state, the server terminal can rapidly inquire whether the operator starts charging by borrowing the server terminal.
Corresponding to the application scenario and method of the method provided by the embodiment of the present application, fig. 2 is a schematic diagram of a method for processing a charging order according to an embodiment of the present application.
And the user initiates a charging request through an application program (APP/applet) at the user side, and a charging order creation instruction is generated.
And the server responds to the creation instruction of the charging order and sends a charging request to the operator.
And the operator generates an instruction for controlling the start of the charging pile and sends the instruction for controlling the start of the charging pile to the charging pile in an asynchronous mode.
The charging pile is started asynchronously, feedback information (state change information-change from an unopened state to an opened state) of the creation instruction is generated, and the feedback information is sent to an operator.
And the operator sends feedback information of the creation instruction to the server in a message queue mode.
The server detects whether the feedback information of the creation instruction is delayed in pushing (for example, whether the receiving time exceeds 90 seconds), and sends an offline state triggering instruction to the user terminal when the detection result is delayed in pushing. In this process, as shown in connection with fig. 3, the work performed by the server may specifically include:
and detecting whether the feedback information is pushed in a delayed manner.
If the pushing is not delayed (normal pushing), the charging data is sent to the user terminal, and the user terminal displays the charging data on the display interface.
If the pushing is delayed, sending an offline state triggering instruction to the user terminal, and inquiring whether the operator has charged or not during the offline period of the user terminal.
If the query result is that the charging order is charged, the charging order is maintained to be effective until a settlement instruction for the charging order is received.
And if the query result is that the charging order is not charged, canceling the charging order. So far, the work executed by the server corresponding to fig. 3 in the offline process of the client is ended.
And the user side enters an offline charging page based on the received offline state triggering instruction. If the charge cancellation order and refund processing are received in the process, the user can reselect the charging pile if the user wants to continue charging. In addition, if charging data is received in this process, it may indicate that charging is resumed. The server waits for a charging settlement instruction of the user side. For the user side, the charging settlement instruction may be clicked on the selection area corresponding to the end of charging.
And the server side sends a settlement instruction of the charging order to the operator.
The operator controls the charging pile to stop charging.
The charging pile stops charging, generates feedback information (state change information-change from on state to off state) of the settlement instruction, and transmits the feedback information to the operator.
And the operator sends feedback information of the settlement instruction to the server in a message queue mode.
The server detects whether the feedback information of the calculation instruction is delayed in pushing or not, and the order settlement is directly carried out under the condition that the detection result is delayed in pushing. The order settlement can be classified into a pre-paid mode and a post-paid mode, and if the pre-paid mode is used, the order settlement amount can be used for multi-refund processing, and if the post-paid mode is used, the order settlement amount can be directly used for settlement.
Fig. 4 is a block diagram of an electronic device for implementing an embodiment of the application. As shown in fig. 4, the electronic device includes: memory 410 and processor 420, memory 410 stores a computer program executable on processor 420. The processor 420, when executing the computer program, implements the methods of the above-described embodiments. The number of memories 410 and processors 420 may be one or more.
The electronic device further includes:
and the communication interface 430 is used for communicating with external equipment and carrying out data interaction transmission.
If the memory 410, the processor 420, and the communication interface 430 are implemented independently, the memory 410, the processor 420, and the communication interface 430 may be connected to each other and communicate with each other through buses. The bus may be an industry standard architecture (Industry Standard Architecture, ISA) bus, an external device interconnect (Peripheral Component Interconnect, PCI) bus, or an extended industry standard architecture (Extended Industry StandardArchitecture, EISA) bus, among others. The bus may be classified as an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in fig. 4, but not only one bus or one type of bus.
Alternatively, in a specific implementation, if the memory 410, the processor 420, and the communication interface 430 are integrated on a chip, the memory 410, the processor 420, and the communication interface 430 may communicate with each other through internal interfaces.
The embodiment of the application provides a computer readable storage medium storing a computer program which, when executed by a processor, implements the method provided in the embodiment of the application.
The embodiment of the application also provides a chip, which comprises a processor and is used for calling the instructions stored in the memory from the memory and running the instructions stored in the memory, so that the communication equipment provided with the chip executes the method provided by the embodiment of the application.
The embodiment of the application also provides a chip, which comprises: the input interface, the output interface, the processor and the memory are connected through an internal connection path, the processor is used for executing codes in the memory, and when the codes are executed, the processor is used for executing the method provided by the application embodiment.
It should be appreciated that the processor may be a central processing unit (Central Processing Unit, CPU), but may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), field programmable gate arrays (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or any conventional processor or the like. It is noted that the processor may be a processor supporting an advanced reduced instruction set machine (Advanced RISC Machines, ARM) architecture.
Further alternatively, the memory may include a read-only memory and a random access memory. The memory may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), programmable ROM (PROM), erasable Programmable ROM (EPROM), electrically Erasable EPROM (EEPROM), or flash Memory, among others. Volatile memory can include random access memory (RandomAccess Memory, RAM), which acts as external cache memory. By way of example, and not limitation, many forms of RAM are available. For example, static RAM (SRAM), dynamic RAM (Dynamic RandomAccess Memory, DRAM), synchronous DRAM (SDRAM), double Data Rate Synchronous DRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), and Direct RAM (DR RAM).
In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions in accordance with the present application are fully or partially produced. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. Computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another.
In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present application. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, the different embodiments or examples described in this specification and the features of the different embodiments or examples may be combined and combined by those skilled in the art without contradiction.
Furthermore, the terms "first," "second," and the like, are used for descriptive purposes only and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include at least one such feature. In the description of the present application, the meaning of "a plurality" is two or more, unless explicitly defined otherwise.
Any process or method described in flow charts or otherwise herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process. And the scope of the preferred embodiments of the present application includes additional implementations in which functions may be performed in a substantially simultaneous manner or in an opposite order from that shown or discussed, including in accordance with the functions that are involved.
Logic and/or steps described in the flowcharts or otherwise described herein, e.g., may be considered a ordered listing of executable instructions for implementing logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions.
It is to be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above-described embodiments, the various steps or methods may be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. All or part of the steps of the methods of the embodiments described above may be performed by a program that, when executed, comprises one or a combination of the steps of the method embodiments, instructs the associated hardware to perform the method.
In addition, each functional unit in the embodiments of the present application may be integrated in one processing module, or each unit may exist alone physically, or two or more units may be integrated in one module. The integrated modules may be implemented in hardware or in software functional modules. The integrated modules described above, if implemented in the form of software functional modules and sold or used as a stand-alone product, may also be stored in a computer-readable storage medium. The storage medium may be a read-only memory, a magnetic or optical disk, or the like.
The above description is merely an exemplary embodiment of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think of various changes or substitutions within the technical scope of the present application, and these should be covered in the scope of the present application. Therefore, the protection scope of the application is subject to the protection scope of the claims.

Claims (10)

1. A method for processing a charging order, comprising:
responding to a creation instruction of a charging order, and detecting feedback information of an operator aiming at the creation instruction;
inquiring whether the operator has charged or not under the condition that the feedback information is pushed in a delayed mode as a result of the detection;
and sending charging data of the operator to a user side for the user side to display the charging data under the condition that the query result is charged.
2. The method of claim 1, wherein determining the basis for delayed pushing of the feedback information comprises:
after sending the creation instruction of the charging order to an operator, starting timing;
and determining that the feedback information is delayed to be pushed under the condition that the feedback information is not received after the first designated time length.
3. The method according to claim 1, wherein the determining the query result includes:
starting timing under the condition that the feedback information is delayed to be pushed as a result of the detection;
and after a second designated time period, determining the query result according to the acquired charging data of the operator.
4. A method according to claim 3, wherein the second specified duration is configured to be any value from 3 minutes to 5 minutes.
5. A method according to claim 1 or 3, further comprising:
and canceling the charging order under the condition that the query result is uncharged.
6. A method according to claim 1 or 3, further comprising, in case a settlement instruction for the charge order is received:
after sending the settlement instruction of the charging order to an operator, starting timing;
under the condition that feedback information of the settlement instruction is not received after the first designated time length, determining that the feedback information of the settlement instruction is delayed to push;
and settling the charging order based on the moment of receiving the settlement instruction of the electric order.
7. The method of claim 2 or 6, wherein the first specified duration is configured to be any value from 30 seconds to 90 seconds.
8. The method as recited in claim 1, further comprising:
and sending an offline state triggering instruction to the user terminal under the condition that the feedback information is pushed in a delayed mode.
9. An electronic device, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1 to 8.
10. A non-transitory computer readable storage medium storing computer instructions for causing the computer to perform the method of any one of claims 1 to 8.
CN202310711997.0A 2023-06-15 2023-06-15 Charging order processing method, electronic equipment and storage medium Pending CN116911839A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310711997.0A CN116911839A (en) 2023-06-15 2023-06-15 Charging order processing method, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310711997.0A CN116911839A (en) 2023-06-15 2023-06-15 Charging order processing method, electronic equipment and storage medium

Publications (1)

Publication Number Publication Date
CN116911839A true CN116911839A (en) 2023-10-20

Family

ID=88363792

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310711997.0A Pending CN116911839A (en) 2023-06-15 2023-06-15 Charging order processing method, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN116911839A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117391825A (en) * 2023-12-13 2024-01-12 广州骏伯网络科技有限公司 Method, device and system for order distribution and circulation of operators

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117391825A (en) * 2023-12-13 2024-01-12 广州骏伯网络科技有限公司 Method, device and system for order distribution and circulation of operators
CN117391825B (en) * 2023-12-13 2024-04-02 广州骏伯网络科技有限公司 Method, device and system for order distribution and circulation of operators

Similar Documents

Publication Publication Date Title
CN108416855B (en) Parking lot charging method, system and computer readable storage medium
EP2924917B1 (en) Method, system, gateway and server for cancelling redirection
US20210146881A1 (en) Security of User Data Stored in Shared Vehicles
CN116911839A (en) Charging order processing method, electronic equipment and storage medium
WO2015154350A1 (en) Internet access traffic sharing method, device and terminal
CN111209578A (en) Application service access method and device
CN101604371A (en) The control method of authority of plug-in unit and system
CN108306882A (en) A kind of method and the network equipment of terminal access business
CN105450583A (en) Information authentication method and device
CN106201574A (en) A kind of startup method and device of application interface
CN109639692A (en) Offline login method, device, equipment, system and storage medium
CN110704121A (en) Operation retry method, system and computer device
US9710833B2 (en) Method and apparatus for enabling concurrent rating during a re-rating operation
CN101132403A (en) Business authorization method and its server
CN108302771B (en) Shared control method, device and system for gas water heater
CN104935616A (en) Data processing method, device and ESB system
CN103888465A (en) Method and device for detecting webpage hijacking
CN106203067A (en) The method for cleaning of a kind of application program and device
CN215117219U (en) Vehicle maintenance control system and vehicle
CN110880981A (en) Gx session exception handling method and device
CN112153036B (en) Security defense method and system based on proxy server
EP4322033A1 (en) Access method, apparatus and system
CN106792915B (en) Traffic management method, mobile terminal and system
CN111137164B (en) Charging method and device
EP3628117B1 (en) A method of providing management and control of hotspots with reduced messaging

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination