Itinerary permission application method, device, storage medium and apparatus

Abstract

The present invention relates to the field of Internet technology, and discloses an itinerary permission application method, equipment, storage medium and device, the method comprising: upon receiving a permission application request initiated by a requesting user based on an itinerary, sending a reminder message to a management user corresponding to the itinerary, receiving confirmation information fed back by the management user based on the reminder message, and applying for collaborative editing permissions of the itinerary for the requesting user based on the confirmation information; because the present invention allows the requesting user to initiate an itinerary permission application request, and the management user confirms whether to authorize the requesting user, it is possible to apply for collaborative editing permissions of the itinerary for the requesting user, thereby optimizing the editing method of the itinerary and improving the user experience.

Description

Technical Field

[0001] The present invention relates to the field of Internet technology, and in particular to a method, device, storage medium and apparatus for applying for itinerary permission. Background Art

[0002] Currently, travel itineraries are usually edited by the creator and then shared with fellow travelers. If fellow travelers have more reasonable arrangements for the itinerary, they usually need to express their opinions in writing, and then the creator will modify it.

[0003] However, the above method requires the creator to collect the opinions of fellow travelers one by one, which is time-consuming and labor-intensive, and has a poor user experience.

[0004] The above contents are only used to assist in understanding the technical solution of the present invention and do not constitute an admission that the above contents are prior art. Summary of the invention

[0005] The main purpose of the present invention is to provide a method, device, storage medium and apparatus for applying for itinerary permission, aiming to solve the technical problem in the prior art that the itinerary creator needs to count the opinions of fellow travelers one by one, which is time-consuming and labor-intensive and has a poor user experience.

[0006] To achieve the above object, the present invention provides a method for applying for itinerary order permissions, the method comprising the following steps:

[0007] Upon receiving a permission application request initiated by a requesting user based on an itinerary, a reminder message is sent to the management user corresponding to the itinerary;

[0008] Receiving confirmation information fed back by the management user according to the reminder information;

[0009] Apply for collaborative editing authority of the itinerary for the requesting user according to the confirmation information.

[0010] Optionally, upon receiving a permission application request initiated by a requesting user based on an itinerary, the step of sending a reminder message to a management user corresponding to the itinerary includes:

[0011] Upon receiving a permission application request initiated by a requesting user based on an itinerary, verifying the requesting user;

[0012] When the verification is passed, a reminder message will be sent to the management user corresponding to the itinerary.

[0013] Optionally, upon receiving the permission application request initiated by the requesting user based on the itinerary, the step of verifying the requesting user includes:

[0014] Upon receiving a permission application request initiated by a requesting user based on an itinerary, detecting whether the requesting user is in a logged-in state;

[0015] If yes, then generate application reminder information, and receive application information fed back by the requesting user according to the application reminder information;

[0016] The requesting user is verified according to the application information.

[0017] Optionally, after the step of detecting whether the requesting user is in a logged-in state when receiving the permission application request initiated by the requesting user based on the itinerary, the method further includes:

[0018] If not, generating a login reminder message, and receiving the login information input by the requesting user according to the login reminder message;

[0019] The requesting user is authenticated according to the login information.

[0020] Optionally, the step of verifying the requesting user according to the login information includes:

[0021] Obtaining key information of the requesting user;

[0022] The requesting user is authenticated according to the login information and the key information.

[0023] Optionally, before the step of receiving confirmation information fed back by the management user according to the reminder information, the step further includes:

[0024] Receiving monitoring information uploaded by the terminal device corresponding to the management user;

[0025] monitoring whether the management user views the reminder information according to the monitoring information;

[0026] Correspondingly, the receiving confirmation information fed back by the management user according to the reminder information includes:

[0027] If yes, then receiving confirmation information fed back by the management user according to the reminder information.

[0028] Optionally, the step of monitoring whether the management user views the reminder information according to the monitoring information includes:

[0029] Determining operation information of the management user according to the monitoring information;

[0030] Obtaining the sending time of the reminder information;

[0031] Whether the management user views the reminder information is monitored according to the operation information and the sending time.

[0032] Optionally, after the step of monitoring whether the management user views the reminder information according to the monitoring information, the method further includes:

[0033] If not, obtaining user information of the requesting user;

[0034] Generate SMS reminder information according to the itinerary and the user information;

[0035] The SMS reminder information is sent to the management user.

[0036] Optionally, the step of applying for collaborative editing rights of the itinerary for the requesting user according to the confirmation information includes:

[0037] Parsing the confirmation information to obtain the authorization content;

[0038] Apply for collaborative editing permissions for the itinerary for the requesting user based on the authorization content.

[0039] Optionally, after the step of applying for collaborative editing rights of the itinerary for the requesting user according to the confirmation information, the method further includes:

[0040] Upon receiving a collaborative editing request initiated by a requesting user based on a target itinerary, performing authority verification on the requesting user;

[0041] When the verification is passed, the target itinerary is edited based on the editing operation of the requesting user.

[0042] Optionally, upon receiving a collaborative editing request initiated by a requesting user based on a target itinerary, the step of verifying the authority of the requesting user includes:

[0043] Upon receiving a collaborative editing request initiated by a requesting user based on a target itinerary, obtaining a current state of the target itinerary;

[0044] The requesting user is authenticated according to the current status.

[0045] Optionally, after the step of applying for collaborative editing rights of the itinerary for the requesting user according to the confirmation information, the method further includes:

[0046] Upon receiving a permission modification request initiated by the management user, determining permission modification information according to the permission modification request;

[0047] The collaborative editing permission of the itinerary is modified according to the permission modification information.

[0048] In addition, to achieve the above-mentioned purpose, the present invention also proposes an itinerary permission application device, which includes a memory, a processor, and an itinerary permission application program stored in the memory and executable on the processor, and the itinerary permission application program is configured to implement the itinerary permission application method as described above.

[0049] In addition, to achieve the above-mentioned purpose, the present invention also proposes a storage medium, on which an itinerary permission application program is stored, and when the itinerary permission application program is executed by a processor, the itinerary permission application method described above is implemented.

[0050] In addition, to achieve the above-mentioned purpose, the present invention also proposes a travel order permission application device, the travel order permission application device comprising: an information sending module, an information receiving module and a permission application module;

[0051] The information sending module is used to send a reminder message to the management user corresponding to the itinerary when receiving the permission application request initiated by the requesting user based on the itinerary;

[0052] The information receiving module is used to receive confirmation information fed back by the management user according to the reminder information;

[0053] The permission application module is used to apply for the collaborative editing permission of the itinerary for the requesting user according to the confirmation information.

[0054] Optionally, the information sending module is further used to verify the requesting user when receiving the permission application request initiated by the requesting user based on the itinerary;

[0055] The information sending module is also used to send reminder information to the management user corresponding to the itinerary when the verification is passed.

[0056] Optionally, the information sending module is further used to detect whether the requesting user is in a logged-in state when receiving the permission application request initiated by the requesting user based on the itinerary;

[0057] The information sending module is further configured to generate application reminder information and receive application information fed back by the requesting user according to the application reminder information;

[0058] The information sending module is also used to verify the requesting user according to the application information.

[0059] Optionally, the information sending module is further configured to generate login reminder information if no, and receive login information input by the requesting user according to the login reminder information;

[0060] The information sending module is further used to verify the requesting user according to the login information.

[0061] Optionally, the information sending module is further used to obtain key information of the requesting user;

[0062] The information sending module is further used to verify the requesting user according to the login information and the key information.

[0063] Optionally, the itinerary permission application device further includes: a user monitoring module;

[0064] The user monitoring module is used to receive monitoring information uploaded by the terminal device corresponding to the management user;

[0065] The user monitoring module is further used to monitor whether the management user views the reminder information according to the monitoring information;

[0066] Correspondingly, the information receiving module is further used to receive confirmation information fed back by the management user based on the reminder information.

[0067] The present invention discloses that when a permission application request based on an itinerary is received from a requesting user, a reminder message is sent to a management user corresponding to the itinerary, confirmation information fed back by the management user based on the reminder message is received, and collaborative editing permission of the itinerary is applied for the requesting user based on the confirmation information; since the present invention allows the requesting user to initiate a permission application request for the itinerary, and the management user confirms whether to authorize the requesting user, it is possible to apply for collaborative editing permission of the itinerary for the requesting user, thereby optimizing the editing method of the itinerary and improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0068] Figure 1 It is a structural diagram of an itinerary permission application device in a hardware operating environment involved in an embodiment of the present invention;

[0069] Figure 2 This is a flow chart of a first embodiment of a method for applying for itinerary permission of the present invention;

[0070] Figure 3 A schematic diagram of an application collaborative editing interface of an embodiment of a method for applying for itinerary permission of the present invention;

[0071] Figure 4 A schematic diagram of a push notification interface of an embodiment of a method for applying for itinerary permission of the present invention;

[0072] Figure 5 A schematic diagram of a pop-up message reminder interface of an embodiment of a method for applying for itinerary permission of the present invention;

[0073] Figure 6 This is a schematic diagram of a permission modification interface of an embodiment of a method for applying for permission for an itinerary ticket of the present invention;

[0074] Figure 7 This is a flow chart of a second embodiment of the itinerary ticket permission application method of the present invention;

[0075] Figure 8 This is a flow chart of a third embodiment of the itinerary ticket permission application method of the present invention;

[0076] Fig. 9 This is a schematic diagram showing application reminder information according to an embodiment of a method for applying for itinerary permission of the present invention;

[0077] Fig.10 This is a structural block diagram of the first embodiment of the itinerary permission application device of the present invention.

[0078] The realization of the purpose, functional features and advantages of the present invention will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0079] It should be understood that the specific embodiments described herein are only used to explain the present invention, and are not used to limit the present invention.

[0080] Reference Figure 1 , Figure 1 A schematic diagram of the structure of an itinerary permission application device in the hardware operating environment involved in an embodiment of the present invention.

[0081] like Figure 1 As shown, the itinerary ticket permission application device may include: a processor 1001, such as a central processing unit (CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. Among them, the communication bus 1002 is used to realize the connection and communication between these components. The user interface 1003 may include a display screen (Display), and the user interface 1003 may also include a standard wired interface and a wireless interface. The wired interface of the user interface 1003 may be a USB interface in the present invention. The network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a wireless fidelity (Wireless-Fidelity, Wi-Fi) interface). The memory 1005 may be a high-speed random access memory (Random Access Memory, RAM) memory, or a stable memory (Non-volatile Memory, NVM), such as a disk memory. The memory 1005 may also be a storage device independent of the aforementioned processor 1001.

[0082] Those skilled in the art will understand that Figure 1 The structure shown in does not constitute a limitation on the itinerary receipt authority application device, and may include more or fewer components than shown in the figure, or a combination of certain components, or a different arrangement of components.

[0083] like Figure 1 As shown, the memory 1005 identified as a computer storage medium may include an operating system, a network communication module, a user interface module, and an itinerary permission application program.

[0084] exist Figure 1 In the itinerary permission application device shown, the network interface 1004 is mainly used to connect to the background server and communicate data with the background server; the user interface 1003 is mainly used to connect to the user device; the itinerary permission application device calls the itinerary permission application program stored in the memory 1005 through the processor 1001, and executes the itinerary permission application method provided in the embodiment of the present invention.

[0085] Based on the above hardware structure, an embodiment of the itinerary order permission application method of the present invention is proposed.

[0086] Reference Figure 2 , Figure 2 It is a flow chart of the first embodiment of the method for applying for itinerary receipt authority of the present invention, and proposes the first embodiment of the method for applying for itinerary receipt authority of the present invention.

[0087] In a first embodiment, the itinerary ticket authority application method includes the following steps:

[0088] Step S10: upon receiving a permission application request initiated by a requesting user based on an itinerary, a reminder message is sent to the management user corresponding to the itinerary.

[0089] It should be understood that the executor of the method of this embodiment can be an itinerary permission application device with data processing, network communication and program running functions, such as a server, etc., or other electronic devices that can achieve the same or similar functions, and this embodiment does not limit this.

[0090] It should be noted that the requesting user may be the user who applies for collaborative editing of the itinerary.

[0091] The itinerary can be uploaded to the server in advance by the management user, and the itinerary can include information such as travel time, travel location, and travel route.

[0092] For ease of understanding, refer to Figure 3 This is for illustration only, but does not limit this solution. Figure 3 This is a schematic diagram of the interface for applying for collaborative editing. The requesting user can browse the itinerary in the figure and click the Apply for Collaborative Editing button below the itinerary to initiate a permission request.

[0093] It should be noted that the management user can be the creator of the itinerary or the manager of the itinerary, and this embodiment does not limit this.

[0094] It is understandable that in order to prevent the itinerary from being modified at will, in this embodiment, when a permission application request initiated by the requesting user based on the itinerary is received, a reminder message will be sent to the management user corresponding to the itinerary so that the management user can authorize according to the actual situation.

[0095] Step S20: receiving confirmation information fed back by the management user according to the reminder information.

[0096] It should be understood that after receiving the reminder information, the management terminal that manages the user can first call the push interface to send a push notification.

[0097] For ease of understanding, refer to Figure 4 This is for illustration only, but does not limit this solution. Figure 4 This is a schematic diagram of the push notification interface. In the figure, after receiving the reminder information, the management end that manages the user calls the push interface to send a push notification "XXX wants to edit XXX itinerary with you, respond immediately."

[0098] It is understandable that when the management user opens the client, the client will first authenticate the management user, and after the authentication is passed, a message reminder will pop up actively.

[0099] For ease of understanding, refer to Figure 5 This is for illustration only, but does not limit this solution. Figure 5 This is a schematic diagram of the pop-up message reminder interface. When the management user opens the client, the client will first authenticate the management user. After the authentication is passed, a message will pop up to remind "XXX wants to help you edit XXX itinerary."

[0100] It should be understood that the management user can feedback the confirmation information through the confirmation button on the client. For example, the management user can click the confirmation button and the rejection button on the pop-up message reminder interface to send the confirmation information.

[0101] Step S30: applying for collaborative editing authority of the itinerary for the requesting user according to the confirmation information.

[0102] It can be understood that applying for collaborative editing permissions for the itinerary for the requesting user based on the confirmation information can be that when the confirmation information is approval, collaborative editing permissions for the itinerary are applied for the requesting user; when the confirmation information is rejection, collaborative editing permissions for the itinerary are not applied for the requesting user.

[0103] Furthermore, in order to facilitate the management of the user's collaborative editing authority, after step S30, the following steps are further included:

[0104] When receiving a permission modification request initiated by the management user, determining permission modification information according to the permission modification request;

[0105] The collaborative editing permission of the itinerary is modified according to the permission modification information.

[0106] It should be understood that the management user can also initiate a permission modification request when viewing the itinerary through the client.

[0107] For ease of understanding, refer to Figure 6 This is for illustration only, but does not limit this solution. Figure 6 This is a schematic diagram of the permission modification interface. When viewing the itinerary through the client, the management user can click the Agree button, Reject button, or Delete button to initiate a permission modification request.

[0108] It can be understood that modifying the collaborative editing permissions of the itinerary according to the permission modification information can be to determine the permission modification object and the permission increase and decrease information according to the permission modification information, and modify the collaborative editing permissions of the itinerary according to the permission modification object and the permission increase and decrease information.

[0109] In the first embodiment, it is disclosed that when a permission application request based on an itinerary is received from a requesting user, a reminder message is sent to a management user corresponding to the itinerary, confirmation information fed back by the management user based on the reminder message is received, and the collaborative editing permission of the itinerary is applied for the requesting user based on the confirmation information; since in this embodiment, the permission application request for the itinerary can be initiated by the requesting user, and the management user confirms whether to authorize the requesting user, the collaborative editing permission of the itinerary can be applied for the requesting user, thereby optimizing the editing method of the itinerary and improving the user experience.

[0110] Reference Figure 7 , Figure 7 This is a flow chart of the second embodiment of the itinerary ticket permission application method of the present invention, based on the above Figure 2 The first embodiment shown is a second embodiment of the itinerary receipt authority application method of the present invention.

[0111] In the second embodiment, the step S10 includes:

[0112] Step S101: upon receiving a permission application request from a requesting user based on an itinerary, verifying the requesting user.

[0113] It should be understood that in order to avoid information interference caused by malicious requests, this embodiment will also verify the requesting user when receiving the permission application request initiated by the requesting user based on the itinerary.

[0114] It should be understood that the verification may be at least one of login verification, account verification, and authority authentication, and this embodiment does not limit this.

[0115] Step S102: When the verification is passed, a reminder message is sent to the management user corresponding to the itinerary.

[0116] It should be understood that when the verification is passed, it means that the permission application request initiated by the requesting user is compliant. Therefore, the reminder information can be sent to the management user corresponding to the itinerary.

[0117] In the second embodiment, it is disclosed that when a permission application request is received from a requesting user based on an itinerary, the requesting user is verified, and when the verification is passed, a reminder message is sent to the management user corresponding to the itinerary; because this embodiment verifies the requesting user who initiates the permission application request before sending the reminder message to the management user, thereby avoiding information interference caused by malicious requests and improving user experience.

[0118] In the second embodiment, before step S20, the method further includes:

[0119] Step S110: receiving monitoring information uploaded by the terminal device corresponding to the management user.

[0120] It should be understood that in actual applications, there are also situations where the management user does not read the reminder information. Therefore, in order to avoid the request user waiting time being too long, in this embodiment, it is also monitored whether the management user checks the reminder information.

[0121] It should be noted that the monitoring information may include user operation information, terminal operation information, current time, etc.

[0122] Step S120: monitoring whether the management user views the reminder information according to the monitoring information.

[0123] It can be understood that monitoring whether the management user views the reminder information according to the monitoring information may be determining the behavior information of the management user according to the monitoring information, and monitoring whether the management user views the reminder information according to the behavior information.

[0124] Furthermore, in order to avoid managing the reminder information that the user has not read for a long time, the step S120 includes:

[0125] Determining operation information of the management user according to the monitoring information;

[0126] Obtaining the sending time of the reminder information;

[0127] Whether the management user views the reminder information is monitored according to the operation information and the sending time.

[0128] It should be understood that monitoring whether the management user views the reminder information based on the operation information and the sending time can be to obtain the current time, and determine the user's unread time based on the current time and the sending time, judge whether the operation information is a viewing operation, and judge whether the user's unread time is greater than the preset time. When the operation information is not a viewing operation and the user's unread time is greater than the preset time, it is determined that the management user has not viewed the reminder information.

[0129] Furthermore, in order to further remind the management user when the management user has not read the reminder information, after step S120, it also includes:

[0130] If not, obtaining user information of the requesting user;

[0131] Generate SMS reminder information according to the itinerary and the user information;

[0132] The SMS reminder information is sent to the management user.

[0133] It should be noted that user information may include user name, user phone number, user email address and other information.

[0134] It is understandable that the SMS reminder information generated according to the itinerary and user information can be obtained by writing the itinerary and user information into a preset SMS template. The SMS reminder template can be preset, for example, "[XX client] XXX wants to edit XXX itinerary with you. He has been waiting for X minutes. Brainstorming will lead to better ideas. Go and respond to his request immediately" is used as the SMS reminder template.

[0135] Accordingly, the step S20 includes:

[0136] Step S20': If yes, receiving confirmation information fed back by the management user according to the reminder information.

[0137] It should be understood that after monitoring that the management user views the reminder information, confirmation information fed back by the management user based on the reminder information can be directly received.

[0138] In the second embodiment, it is disclosed to receive monitoring information uploaded by the terminal device corresponding to the management user, monitor whether the management user views the reminder information based on the monitoring information, and if so, receive confirmation information from the management user based on the reminder information; since this embodiment also monitors whether the management user views the reminder information, it avoids the management user not reading the reminder information, thereby avoiding the requesting user from waiting for too long.

[0139] In the second embodiment, the step S30 includes:

[0140] Step S301: parse the confirmation information to obtain the authorized content.

[0141] It should be understood that in actual applications, in order to achieve partial authorization of the requesting user. For example, the management user can only authorize the requesting user to edit the scenic spot information of the itinerary. In this embodiment, the confirmation information can also be parsed to obtain the authorization content, and the collaborative editing permission of the itinerary can be applied for the requesting user according to the authorization content.

[0142] It is understandable that parsing the confirmation information to obtain the authorized content may be parsing the confirmation information according to the information identifier to obtain the authorized content, wherein the information identifier is used to indicate the information content.

[0143] Step S302: applying for collaborative editing rights of the itinerary for the requesting user according to the authorization content.

[0144] It is understandable that applying for collaborative editing rights of the itinerary for the requesting user according to the authorization content can be to search for the authorization rights corresponding to the authorization content in the preset authority table, and apply for collaborative editing rights of the itinerary for the requesting user according to the authorization rights. The preset authority table includes the correspondence between the authorization content and the authorization rights, and the correspondence between the authorization content and the authorization rights can be preset.

[0145] In the second embodiment, it is disclosed that the confirmation information is parsed to obtain the authorization content, and the collaborative editing permission of the itinerary is applied for the requesting user according to the authorization content; because this embodiment also applies for partial collaborative editing permission for the requesting user based on the authorization content of the management user, it ensures the fine management of the itinerary, thereby improving the security of the itinerary.

[0146] In the second embodiment, after step S30, the method further includes:

[0147] Step S40: upon receiving a collaborative editing request initiated by a requesting user based on a target itinerary, performing authority verification on the requesting user.

[0148] It should be understood that in order to achieve collaborative editing of the itinerary, in this embodiment, a collaborative editing request initiated by the requesting user based on the target itinerary is also received, and the target itinerary is edited based on the editing operation of the requesting user.

[0149] Furthermore, in order to avoid confusion in the itinerary due to multiple users editing at the same time, the step S40 includes:

[0150] Upon receiving a collaborative editing request initiated by a requesting user based on a target itinerary, obtaining a current state of the target itinerary;

[0151] The authority of the requesting user is verified according to the current status.

[0152] It should be noted that the current state of the itinerary can be an open state or a closed state. When the itinerary is opened by the user, the itinerary is in the open state; when the itinerary is not opened by the user, the itinerary is in the closed state.

[0153] It should be understood that when the itinerary is in an open state, it means that other users are opening the itinerary for editing. At this time, if the requesting user is allowed to edit the itinerary, it may cause the itinerary to be disordered. Therefore, in this embodiment, judging whether the itinerary is allowed to be edited according to the current state can be that when the itinerary is in an open state, it is determined that the itinerary is not allowed to be edited; when the itinerary is in a closed state, it is determined that the itinerary is allowed to be edited.

[0154] Step S50: When the verification is passed, the target itinerary is edited based on the editing operation of the requesting user.

[0155] It is understandable that, when the verification is passed, the requesting user can edit the target itinerary. Therefore, the target itinerary can be edited based on the editing operation of the requesting user.

[0156] In the second embodiment, it is disclosed that when a collaborative editing request initiated by a requesting user based on a target itinerary is received, the requesting user is authenticated, and when the authentication is passed, the target itinerary is edited based on the editing operation of the requesting user; since this embodiment also receives a collaborative editing request initiated by a requesting user, and edits the target itinerary based on the editing operation of the requesting user, collaborative editing of the itinerary can be achieved.

[0157] Reference Figure 8 , Figure 8 This is a flow chart of the third embodiment of the itinerary permission application method of the present invention, based on the above Figure 7 The second embodiment shown is a third embodiment of the itinerary receipt authority application method of the present invention.

[0158] In the third embodiment, the step S101 includes:

[0159] Step S1011: upon receiving a permission application request from a requesting user based on an itinerary, detecting whether the requesting user is in a logged-in state.

[0160] It should be understood that, since the editing user's information needs to be written during collaborative editing, in this embodiment, when receiving the permission application request initiated by the requesting user based on the itinerary, it will be detected whether the requesting user is in a logged-in state.

[0161] Furthermore, in order to remind the user when the user is not logged in, after step S1011, the following is further included:

[0162] If not, generating a login reminder message, and receiving the login information input by the requesting user according to the login reminder message;

[0163] The requesting user is authenticated according to the login information.

[0164] It should be noted that the login reminder information can be preset. For example, the login reminder information can be preset as: "Since you are not logged in, you cannot apply for collaborative editing."

[0165] It is understandable that after the login reminder information is generated, the login reminder information can be sent to the client of the requesting user, and the login information fed back by the requesting user according to the login reminder information can be received.

[0166] It should be noted that the login information may include login account, login password, verification code and other information.

[0167] It should be understood that verifying the requesting user according to the login information may be to match the login information with the registered user information in the preset information library, and verifying the requesting user according to the matching result. The registered user information in the preset information library may be pre-registered user information.

[0168] Furthermore, in order to improve the security of user login, the verifying the requesting user according to the login information includes:

[0169] Obtaining key information of the requesting user;

[0170] The requesting user is authenticated according to the login information and the key information.

[0171] It is understandable that in order to further improve the security of user login, in this embodiment, the key information of the requesting user can also be obtained, and the requesting user can be verified based on the login information and the key information.

[0172] Step S1012: If yes, then generate application reminder information, and receive application information fed back by the requesting user according to the application reminder information.

[0173] It is understandable that in order to avoid user misoperation resulting in a permission application request, in this embodiment, after receiving a permission application request initiated by the requesting user based on the itinerary and detecting that the requesting user is logged in, an application reminder message will also be generated to remind the requesting user for further confirmation.

[0174] It should be understood that generating the application reminder information may be generating the application reminder information according to the user information of the management user.

[0175] It is understandable that generating application reminder information based on the user information of the management user may be to write the user information of the management user into a preset application reminder template to obtain the application reminder information. The preset application reminder template may be preset, for example, the preset application reminder template may be preset as: "A collaborative editing application will be initiated to the creator XXX, and the creator may edit this itinerary with the creator only after the creator approves it."

[0176] It should be understood that after the application reminder information is generated, the application reminder information can be sent to the client of the requesting user, and application information fed back by the requesting user according to the application reminder information can be received.

[0177] For ease of understanding, refer to Fig. 9 This is for illustration only, but does not limit this solution. Fig. 9 This is a schematic diagram for displaying application reminder information. When the application reminder information is sent to the client of the requesting user, the client of the requesting user can display the information as shown in the figure, and the requesting user can feedback the application information by clicking the Initiate Application button in the figure.

[0178] Step S1013: verify the requesting user according to the application information.

[0179] It is understandable that verifying the requesting user according to the application information may be that when the application information is confirmation of initiating the application, it is determined that the requesting user has passed the verification, and when the application information is other, it is determined that the requesting user has failed the verification.

[0180] In the third embodiment, it is disclosed that when a permission application request based on an itinerary is received from a requesting user, whether the requesting user is in a logged-in state is detected. If so, application reminder information is generated, and application information fed back by the requesting user based on the application reminder information is received, and the requesting user is verified based on the application information; since this embodiment detects whether the requesting user is in a logged-in state when a permission application request based on an itinerary is received from a requesting user, collaborative editing by non-logged-in users can be avoided, thereby improving the user experience.

[0181] In addition, an embodiment of the present invention further proposes a storage medium, on which an itinerary permission application program is stored, and when the itinerary permission application program is executed by a processor, the itinerary permission application method as described above is implemented.

[0182] In addition, refer to Fig.10 , the embodiment of the present invention also provides a device for applying for permission of an itinerary bill, the device for applying for permission of an itinerary bill comprises: an information sending module 10, an information receiving module 20 and a permission application module 30;

[0183] The information sending module 10 is used to send reminder information to the management user corresponding to the itinerary when receiving a permission application request initiated by the requesting user based on the itinerary.

[0184] It should be noted that the requesting user may be the user who applies for collaborative editing of the itinerary.

[0185] The itinerary can be uploaded to the server in advance by the management user, and the itinerary can include information such as travel time, travel location, and travel route.

[0186] For ease of understanding, refer to Figure 3 This is for illustration only, but does not limit this solution. Figure 3 This is a schematic diagram of the interface for applying for collaborative editing. The requesting user can browse the itinerary in the figure and click the Apply for Collaborative Editing button below the itinerary to initiate a permission request.

[0187] It should be noted that the management user can be the creator of the itinerary or the manager of the itinerary, and this embodiment does not limit this.

[0188] It is understandable that in order to prevent the itinerary from being modified at will, in this embodiment, when a permission application request initiated by the requesting user based on the itinerary is received, a reminder message will be sent to the management user corresponding to the itinerary so that the management user can authorize according to the actual situation.

[0189] The information receiving module 20 is used to receive confirmation information fed back by the management user according to the reminder information.

[0190] It should be understood that after receiving the reminder information, the management terminal that manages the user can first call the push interface to send a push notification.

[0191] For ease of understanding, refer to Figure 4 This is for illustration only, but does not limit this solution. Figure 4This is a schematic diagram of the push notification interface. In the figure, after receiving the reminder information, the management end that manages the user calls the push interface to send a push notification "XXX wants to edit XXX itinerary with you, respond immediately."

[0192] It is understandable that when the management user opens the client, the client will first authenticate the management user, and after the authentication is passed, a message reminder will pop up actively.

[0193] For ease of understanding, refer to Figure 5 This is for illustration only, but does not limit this solution. Figure 5 This is a schematic diagram of the pop-up message reminder interface. When the management user opens the client, the client will first authenticate the management user. After the authentication is passed, a message will pop up to remind "XXX wants to help you edit XXX itinerary."

[0194] It should be understood that the management user can feedback the confirmation information through the confirmation button on the client. For example, the management user can click the confirmation button and the rejection button on the pop-up message reminder interface to send the confirmation information.

[0195] The permission application module 30 is used to apply for the collaborative editing permission of the itinerary for the requesting user according to the confirmation information.

[0196] It can be understood that applying for collaborative editing permissions for the itinerary for the requesting user based on the confirmation information can be that when the confirmation information is approval, collaborative editing permissions for the itinerary are applied for the requesting user; when the confirmation information is rejection, collaborative editing permissions for the itinerary are not applied for the requesting user.

[0197] Further, in order to facilitate the management of user management collaborative editing permissions, the itinerary permission application device includes: a permission modification module;

[0198] The permission modification module is used to determine permission modification information according to the permission modification request when receiving the permission modification request initiated by the management user;

[0199] The permission modification module is also used to modify the collaborative editing permission of the itinerary according to the permission modification information.

[0200] It should be understood that the management user can also initiate a permission modification request when viewing the itinerary through the client.

[0201] For ease of understanding, refer to Figure 6 This is for illustration only, but does not limit this solution. Figure 6 This is a schematic diagram of the permission modification interface. When viewing the itinerary through the client, the management user can click the Agree button, Reject button, or Delete button to initiate a permission modification request.

[0202] It can be understood that modifying the collaborative editing permissions of the itinerary according to the permission modification information can be to determine the permission modification object and the permission increase and decrease information according to the permission modification information, and modify the collaborative editing permissions of the itinerary according to the permission modification object and the permission increase and decrease information.

[0203] In the present embodiment, it is disclosed that when a permission application request based on an itinerary is received from a requesting user, a reminder message is sent to a management user corresponding to the itinerary, confirmation information fed back by the management user based on the reminder message is received, and the collaborative editing permission of the itinerary is applied for the requesting user based on the confirmation information; since in the present embodiment, the permission application request for the itinerary can be initiated by the requesting user, and the management user confirms whether to authorize the requesting user, the collaborative editing permission of the itinerary can be applied for the requesting user, thereby optimizing the editing method of the itinerary and improving the user experience.

[0204] Other embodiments or specific implementations of the itinerary ticket permission application device described in the present invention can refer to the above-mentioned method embodiments and will not be repeated here.

[0205] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or system including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or system. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or system including the element.

[0206] The serial numbers of the embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments. In a unit claim that lists several means, several of these means may be embodied by the same hardware item. The use of the words first, second, and third, etc. does not indicate any order and these words may be interpreted as names.

[0207] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as a read-only memory image (ROM) / random access memory (RAM), a magnetic disk, or an optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in each embodiment of the present invention.

[0208] The above are only preferred embodiments of the present invention, and are not intended to limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made using the contents of the present invention specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present invention.

Claims

1. A method for applying for itinerary permission, characterized in that: The itinerary ticket authority application method comprises the following steps: Upon receiving a permission application request initiated by a requesting user based on an itinerary, a reminder message is sent to the management user corresponding to the itinerary; Receiving confirmation information fed back by the management user according to the reminder information; Applying for collaborative editing authority of the itinerary for the requesting user according to the confirmation information; Before the step of receiving the confirmation information fed back by the management user according to the reminder information, the step further includes: Receiving monitoring information uploaded by the terminal device corresponding to the management user; Determining operation information of the management user according to the monitoring information; Obtaining the sending time of the reminder information; monitoring whether the management user views the reminder information according to the operation information and the sending time; If not, obtaining user information of the requesting user; Generate SMS reminder information according to the itinerary and the user information; Sending the SMS reminder information to the management user; Correspondingly, the receiving confirmation information fed back by the management user according to the reminder information includes: If yes, then receiving confirmation information fed back by the management user according to the reminder information.

2. The itinerary permission application method according to claim 1, characterized in that: The step of sending a reminder message to the management user corresponding to the itinerary upon receiving the permission application request initiated by the requesting user based on the itinerary includes: Upon receiving a permission application request initiated by a requesting user based on an itinerary, verifying the requesting user; When the verification is passed, a reminder message will be sent to the management user corresponding to the itinerary.

3. The itinerary order permission application method according to claim 2, characterized in that: The step of verifying the requesting user upon receiving the permission application request initiated by the requesting user based on the itinerary includes: Upon receiving a permission application request initiated by a requesting user based on an itinerary, detecting whether the requesting user is in a logged-in state; If yes, then generate application reminder information, and receive application information fed back by the requesting user according to the application reminder information; The requesting user is verified according to the application information.

4. The itinerary order authorization application method according to claim 3, characterized in that: After the step of detecting whether the requesting user is in a logged-in state upon receiving the permission application request initiated by the requesting user based on the itinerary, the method further includes: If not, generating a login reminder message, and receiving the login information input by the requesting user according to the login reminder message; The requesting user is authenticated according to the login information.

5. The itinerary permission application method according to claim 4, characterized in that: The step of verifying the requesting user according to the login information includes: Obtaining key information of the requesting user; The requesting user is authenticated according to the login information and the key information.

6. The itinerary order authorization application method according to any one of claims 1 to 5, characterized in that: The step of applying for collaborative editing rights of the itinerary for the requesting user according to the confirmation information comprises: Parsing the confirmation information to obtain the authorization content; Apply for collaborative editing permissions for the itinerary for the requesting user based on the authorization content.

7. The itinerary permission application method according to claim 1, characterized in that: After the step of applying for collaborative editing authority of the itinerary for the requesting user according to the confirmation information, the method further includes: Upon receiving a collaborative editing request initiated by a requesting user based on a target itinerary, performing authority verification on the requesting user; When the verification is passed, the target itinerary is edited based on the editing operation of the requesting user.

8. The itinerary permission application method according to claim 7, characterized in that: The step of performing authority verification on the requesting user upon receiving the collaborative editing request initiated by the requesting user based on the target itinerary includes: Upon receiving a collaborative editing request initiated by a requesting user based on a target itinerary, obtaining a current state of the target itinerary; The requesting user is authenticated according to the current status.

9. The itinerary order authorization application method according to any one of claims 1 to 5, characterized in that: After the step of applying for collaborative editing authority of the itinerary for the requesting user according to the confirmation information, the method further includes: Upon receiving a permission modification request initiated by the management user, determining permission modification information according to the permission modification request; The collaborative editing permission of the itinerary is modified according to the permission modification information.

10. A device for applying for itinerary permission, characterized in that: The itinerary permission application device includes: a memory, a processor, and an itinerary permission application program stored in the memory and executable on the processor. When the itinerary permission application program is executed by the processor, the itinerary permission application method as described in any one of claims 1 to 9 is implemented.

11. A storage medium, characterized in that: The storage medium stores an itinerary permission application program, and when the itinerary permission application program is executed by the processor, the itinerary permission application method as described in any one of claims 1 to 9 is implemented.

12. A device for applying for itinerary permission, characterized in that: The itinerary permission application device comprises: an information sending module, an information receiving module and a permission application module; The information sending module is used to send a reminder message to the management user corresponding to the itinerary when receiving the permission application request initiated by the requesting user based on the itinerary; The information receiving module is used to receive confirmation information fed back by the management user according to the reminder information; The permission application module is used to apply for the collaborative editing permission of the itinerary for the requesting user according to the confirmation information; The itinerary permission application device further includes: a user monitoring module; The user monitoring module is used to receive monitoring information uploaded by the terminal device corresponding to the management user; determine the operation information of the management user according to the monitoring information; obtain the sending time of the reminder information; and monitor whether the management user views the reminder information according to the operation information and the sending time; The information receiving module is further used to obtain the user information of the requesting user if no; generate SMS reminder information according to the itinerary and the user information; and send the SMS reminder information to the management user; The information receiving module is further configured to receive confirmation information fed back by the management user based on the reminder information.

13. The itinerary permission application device according to claim 12, characterized in that: The information sending module is further used to verify the requesting user upon receiving the permission application request initiated by the requesting user based on the itinerary; The information sending module is also used to send reminder information to the management user corresponding to the itinerary when the verification is passed.

14. The itinerary permission application device according to claim 13, characterized in that: The information sending module is further configured to detect whether the requesting user is in a logged-in state upon receiving a permission application request initiated by the requesting user based on the itinerary; The information sending module is further configured to generate application reminder information and receive application information fed back by the requesting user according to the application reminder information; The information sending module is also used to verify the requesting user according to the application information.

15. The itinerary permission application device according to claim 13, characterized in that: The information sending module is further configured to generate login reminder information if no, and receive login information input by the requesting user according to the login reminder information; The information sending module is further used to verify the requesting user according to the login information.

16. The itinerary permission application device according to claim 15, characterized in that: The information sending module is further used to obtain the key information of the requesting user; The information sending module is further used to verify the requesting user according to the login information and the key information.

Images