Data processing method, client and server system

Abstract

Embodiments of the present specification provide a data processing method, a client and a server, wherein the data processing method according to an embodiment of the present application comprises: receiving page data; obtaining one or more page elements of a specified type according to the page data; reading attribute values of the one or more page elements of the specified type on a specified attribute; receiving specified operation information of a user on the page; sending the attribute values of the one or more page elements of the specified type on the specified attribute and the specified operation information of the user on the page to the server, updating, by the server, the attribute values of the one or more page elements of the specified type on the specified attribute according to the attribute values and the specified operation information; receiving the updated attribute values of the one or more page elements of the specified type on the specified attribute sent by the server; and displaying the attribute values of the one or more page elements of the specified type on the specified attribute on the page.

Description

[0001] This patent application is a divisional application of Chinese patent application No. 201610391243.1, filed on June 3, 2016, entitled "Data Processing Method, Client and Server". Technical Field

[0002] This document relates to the field of computer technology, and in particular to a data processing method, client, and server. Background Technology

[0003] When a user places an order to purchase goods through a mobile app, an order confirmation process is required. On the order confirmation page, the user needs to confirm and enter information such as the shipping address, delivery method, and points redemption. The order confirmation page displays order-related information, with price being a crucial element. Multiple prices are displayed: the discounted price, the main order price, and the total order price. If the user selects different order-related options, such as delivery method, whether to use points, or whether to use related services (shipping insurance), the price on the order confirmation page will change accordingly.

[0004] For example, if a user changes their shipping method from EMS (originally 20 yuan) to SF Express (free shipping), the price of the main order corresponding to that shipping method will change, and the previously calculated 20 yuan should be deducted. Simultaneously, the total order price should also be reduced by 20 yuan. As another example, if a user chooses to use store points for discounts, the total order price should be reduced by the corresponding amount deducted for points.

[0005] Because the user adjusted the order, the overall order price changed. Additionally, the order confirmation page requires the entry of different order information: quantity, discounts, shipping address, delivery method, service, invoice, delivery time, etc. Different order options selected by the user will result in different order prices; these changes are all determined by the business logic. Under different business rules, different selection methods result in different prices.

[0006] Currently, existing mobile shopping client applications can embed the logic for processing order price information into the client application's local business logic. However, this approach makes it difficult to dynamically update and adjust the price information processing logic, resulting in inaccurate price calculations on the client side. Summary of the Invention

[0007] This specification provides one or more embodiments of a page data processing method. The method includes displaying page data for an order page. Based on user actions on order page elements, a second attribute value of the order page element is obtained from a server. A first attribute value of the order page element is then displayed as the second attribute value.

[0008] This specification provides one or more embodiments of a page data processing method. The method includes a server receiving order operation information from a client on an order page; determining a second attribute value for an order page element based on the order operation information; and sending the second attribute value to the client.

[0009] This specification provides one or more embodiments of a page data processing method. The method includes displaying page data of a target page. Based on a user's specified operation on a page element of the target page, a second attribute value of the page element on a specified attribute is obtained from a server. A first attribute value of the page element on the specified attribute is displayed as the second attribute value.

[0010] This specification provides one or more embodiments of a page data processing method. The method includes a server receiving specified operation information from a client on a target page; determining a second attribute value for a page element on the target page based on the specified operation information; and sending the second attribute value to the client.

[0011] This specification provides a client through one or more embodiments. The client includes a display module for displaying page data of an order page. The client also includes a first sending module for obtaining a second attribute value of the order page element from a server based on user actions on the order page element. The display module displays the first attribute value of the order page element as the second attribute value.

[0012] This specification provides a server through one or more embodiments. The server includes a fourth receiving module for receiving order operation information from a user on an order page sent by a client. The server also includes a second updating module for determining a second attribute value for an order page element based on the order operation information. Finally, the server includes a second sending module for sending the second attribute value to the client. Attached Figure Description

[0013] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0014] Figure 1 This is a flowchart of a client-side data processing method according to an embodiment of this application;

[0015] Figure 2 This is a flowchart of a server-side data processing method according to an embodiment of this application;

[0016] Figure 3This is a flowchart of a client-server data processing method according to an embodiment of this application;

[0017] Figure 4A and 4B This is a schematic diagram of an order confirmation page according to an embodiment of this application;

[0018] Figure 5 This is a structural block diagram of the server and client according to an embodiment of this application. Detailed Implementation

[0019] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0020] Figure 1 This is a flowchart of a client data processing method according to an embodiment of this application, such as... Figure 1 As shown, it includes:

[0021] Step S101: Receive page data.

[0022] The page data may include page structure data. In one embodiment of this application, the page structure data is the organizational structure of various information items on the page. Specifically, the server generates page structure data corresponding to a specific page on the client and sends the page structure data to the client. For example, after the client generates an order confirmation page, it sends the order confirmation page to the server. The server generates page structure data corresponding to the order confirmation page, which may be the organizational structure of information such as products, logistics, and services on the order confirmation page. Then, the server sends the page structure data corresponding to the order confirmation page to the client.

[0023] Step S102: Obtain one or more page elements of a specified type based on the page data.

[0024] After the client splits the page into one or more page elements of a specified type based on the page data sent by the server, it obtains one or more page elements of the specified type. Specifically, the client divides the order confirmation page into page elements based on the page structure data from the server, and determines the page elements of a specified type in the order confirmation page according to the association between pre-set attribute information and page elements. For example, the types of page elements include, but are not limited to: shipping address, first main order, second main order, ..., points deduction A, points deduction B, anonymous purchase switch, total order price, submit order (confirm) button, etc.; furthermore, each main order may also include: unit price of goods, quantity of goods, store discounts, delivery method, shipping insurance, buyer's message, main order price, etc. Corresponding to step S102, the page elements of a specified type refer to page elements with relatively fixed attribute values, such as: unit price of goods, store discount information, etc.

[0025] Step S103: Read the attribute values ​​of one or more page elements of the specified type on the specified attribute.

[0026] After retrieving one or more page elements of a specified type from the page data, read the attribute values ​​of the one or more page elements of the specified type on a specified attribute. For example, read the attribute value "239 yuan" for the page element "product unit price".

[0027] Step S104: Receive the user's specified operation information on the page.

[0028] In this embodiment, the page includes page elements with relatively fixed attribute values ​​as well as page elements with adjustable attribute values. When a user interacts with a page element on the page that has adjustable attribute values, operation information is generated, and the client receives the specified operation information. For example, if a user selects "Free Shipping" and "Points Deduction" as the "Delivery Method," these are page elements with adjustable attribute values. When the user interacts with these page elements, operation information is generated, and the client receives the user's operation information.

[0029] Step S105: Send the attribute values ​​of the one or more page elements on the specified attribute and the user's specified operation information on the page to the server, and the server updates the attribute values ​​of the page elements on the specified attribute according to the attribute values ​​and the specified operation information.

[0030] Specifically, the attribute values ​​of page elements on specified attributes and the user's specified operation information are sent to the server. Since the server can maintain and update a large number of calculation rules in a timely manner, it can recalculate the attribute values ​​of page elements on specified attributes based on the attribute values ​​and the specified operation information. The recalculated attribute values ​​of the page elements are then sent to the client. In this embodiment, the calculation of page element attribute values ​​is handled by the server, and the client is unaware of the calculation logic.

[0031] Step S106: Receive the updated attribute value of the page element on the specified attribute sent by the server.

[0032] Step S107: Display the attribute value of the page element on the specified attribute on the page.

[0033] According to an embodiment of this application, the client splits page data into one or more page elements of a specified type, uploads the attribute values ​​of the page elements and user operation information to the server, and the server is responsible for updating the attribute values ​​of the page elements. The client displays the attribute values ​​and is unaware of the price calculation logic.

[0034] Figure 2 This is a flowchart of a server-side data processing method according to an embodiment of this application, such as... Figure 2 As shown, it includes:

[0035] Step S201: Receive attribute values ​​of one or more page elements on specified attributes and specified operation information of the user on the page sent by the client.

[0036] In this embodiment, the server generates page data corresponding to a specific page on the client and sends the page data to the client. The page data may include page structure data. The client splits the page into one or more page elements of a specified type based on the page data and reads the attribute values ​​of the one or more page elements of the specified type on a specified attribute. Then, it receives specified operation information from the user on the page and sends the attribute values ​​and the specified operation information to the server.

[0037] For example, the page structure data can be the organizational structure of information such as products, logistics, and services in an order confirmation page. The types of page elements include, but are not limited to: shipping address, first main order, second main order, ..., points deduction A, points deduction B, anonymous purchase switch, total order price, and submit order (confirm) button. Furthermore, each main order can also include: unit price, quantity, store discounts, delivery method, shipping insurance, buyer comments, and main order price. The attribute value of a page element on a specified attribute refers to a page element with a relatively fixed attribute value, such as the unit price of a product. The specified operation information on the page can be operation information on the "quantity of products".

[0038] Step S202: Update the attribute value of the page element on the specified attribute according to the attribute value and the specified operation information.

[0039] Specifically, after receiving the attribute value and specified operation information sent by the client, the server determines the calculation rule corresponding to the attribute value and specified operation information in its maintained calculation rule base. Then, based on the calculation rule, the attribute value of the page element in the first attribute, and the specified operation information, the server calculates the attribute value of the page element in the second attribute. For example, when the server receives the first attribute value of the page element "Delivery Method" as "Free Shipping", it calculates its second attribute value (price data) as "0"; when the server receives the first attribute value of the page element "Delivery Method" as "EMS", it calculates its second attribute value (price data) as "-20". Following the above logic, the server calculates new attribute values ​​for each page element, including the total order price on the order confirmation page.

[0040] Step S203: Send the updated attribute value of the page element on the specified attribute to the client.

[0041] According to the embodiments of this application, after receiving the attribute values ​​of page elements and user operation information, the server updates the attribute values ​​of the page elements and sends the updated attribute values ​​to the client. The client displays the attribute values ​​without being aware of the price calculation logic.

[0042] The following is combined Figure 3 This application describes in detail the processing details of the client and server sides in embodiments of this application. (See references...) Figure 3 The method includes:

[0043] In step S301, the server generates order structure data corresponding to the order confirmation page on the client and sends the order structure data to the client. In one embodiment of this application, the server also generates a first calculation rule corresponding to the order structure data and sends it to the client. If the client performs price calculation locally, it uses the first calculation rule to calculate the price data on the order confirmation page.

[0044] In step S302, after receiving the order structure data, the client splits the order confirmation page into one or more page elements based on the order structure data. Each page element has corresponding data information (e.g., numbers) or selection information. The data information can be directly used in calculations; while the selection information provides the user with multiple options or on / off states, which are generated based on the user's actions and cannot be directly used in calculations.

[0045] In one embodiment of this application, the page element types of an order confirmation page include, but are not limited to: shipping address, first main order, second main order, ..., points deduction A, points deduction B, anonymous purchase switch, submit order button, total order price, etc. Furthermore, each main order element information may also include: unit price, quantity, store discounts, shipping method, shipping insurance, buyer comments, etc. Among these, the unit price is relatively fixed data; while the quantity, shipping method, and shipping insurance are optional information, and their prices change depending on different options or switch states.

[0046] refer to Figure 4A If a user selects three items from two different stores and places an order, two main orders will be generated. The main orders are divided according to the store dimension within the order; all items from a single store belong to the same main order. Figure 4A The page shown includes two main orders: main order 41 and main order 42. Main order 41 contains only one item, therefore it contains only one sub-order. See further details. Figure 4B Sub-orders are created based on the products within a main order. Different products in a store represent different sub-orders. Figure 4B The page shown includes two sub-orders, namely the first sub-order 43 and the second sub-order 44.

[0047] Step S303: Read the attribute values ​​of one or more page elements of a specified type on a specified attribute, and receive the specified operation information from the user on the page. The attribute values ​​of the page elements of the specified type on the specified attribute include fixed data information, and the specified operation information from the user on the page includes selection information. (Continue to refer to...) Figure 4BIn the first sub-order (item 43), the product price is fixed data. However, elements affecting the price, such as store discounts, shipping methods, and shipping insurance, are optional. These elements change their prices depending on the selected option or their on / off state. It's important to note that the fixed data refers to relatively constant price data; for example, the seller might adjust the unit price. The optional information, on the other hand, is pre-set on the order confirmation page. This means that the optional information is not static and can be adjusted to fixed data.

[0048] Step S304: Determine whether the update operation is performed remotely by the server or locally by the client. If the update operation is performed remotely by the server, proceed to step S305; otherwise, proceed to step S316.

[0049] In this embodiment, it can be determined whether to perform a remote update on the server or a local update on the client based on the user's specified operation information (i.e., the changed selection information) received on the page. Specifically, remote calculation logic that needs to be calculated remotely by the server is pre-set; that is, if any selection information(s) changes, remote calculation is performed, and if any selection information(s) changes, local calculation is performed. For example, adjusting the delivery method belongs to remote calculation logic, and the server performs the price calculation; the points deduction operation belongs to local calculation logic, and the server performs the price calculation locally. In other words, complex price calculations are performed remotely by the server, while the client only performs some simple price calculations locally.

[0050] Step S305: Perform remote calculation. The client sends the attribute values ​​of one or more page elements of a specified type on a specified attribute, as well as the specified operation information of the user on the page, to the server.

[0051] In steps S306-S307, the server receives the attribute value and the specified operation information, calculates the attribute value of the page element based on the attribute value and the specified operation information, and then sends the new attribute value of the page element to the client.

[0052] Step S308: The client updates the attribute values ​​of the page elements according to the attribute values ​​and the specified operation information.

[0053] Step S309: Display the attribute value of the page element on the specified attribute on the client's page.

[0054] exist Figure 4A and Figure 4BIn the illustrated embodiment, the total order price (totalPrice_1) is the sum of the prices of the two main orders and the prices of the two points deductions (with or without use). The price of the first main order (orderPrice_1_1) is the sum of the prices of the two sub-orders, the price of the delivery method, and the service price. The points deduction operation is a local calculation, while the delivery method adjustment is a remote calculation. Taking enabling points deduction with "Tmall Points" (tmallPoint_1) as an example, the price of tmallPoint_1 changes from 0.0 to -2.0, thus requiring a recalculation of the total order price. According to the above calculation rules, the new total order price is obtained by re-adding all elements under totalPrice_1. For adjusting the delivery method (deliveryMethod_1_1), since the attribute values ​​corresponding to different delivery method options cannot be determined on the client side, after the user selects a delivery method, the client uploads the attribute values ​​of the page elements and the user's operation information to the server. The server recalculates and distributes new attribute values ​​for each page element based on these attribute values ​​and operation information. After receiving the new attribute values, the client refreshes the corresponding attribute values ​​on the page. When the price calculation logic changes, no new client-side logic is needed; only the calculation rules need to be updated or remote calculation can be used.

[0055] The following is combined Figure 5 Describe the structure of the client and server according to embodiments of this application. For example... Figure 5 As shown, the client includes:

[0056] The first receiving module 51 is used to receive page data;

[0057] The acquisition module 52 is configured to acquire one or more page elements of a specified type based on page data. In one embodiment, the acquisition module 52 is further configured to split the page into one or more page elements of a specified type based on the page structure data.

[0058] Reading module 53 is used to read the attribute values ​​of one or more page elements of the specified type on a specified attribute.

[0059] The second receiving module 54 is used to receive the specified operation information of the user on the page.

[0060] The first sending module 55 is used to send the attribute values ​​of the one or more page elements on the specified attribute and the user's specified operation information on the page to the server, and the server updates the attribute values ​​of the page elements on the specified attribute according to the attribute values ​​and the specified operation information.

[0061] The third receiving module 56 is used to receive the updated attribute value of the page element on the specified attribute sent by the server.

[0062] Display module 57 is used to display the attribute value of the page element on the specified attribute on the page.

[0063] Continue to refer to Figure 5 In one embodiment of this application, the client further includes:

[0064] The judgment module 58 is used to determine whether to perform server update processing based on the attribute value and the specified operation information. If so, the first sending module 55 is executed.

[0065] The first update module 59 is used to update the attribute value of the page element on the specified attribute according to the attribute value and the specified operation information if the judgment module 58 determines that client update processing is to be performed.

[0066] Continue to refer to Figure 5 The server includes:

[0067] The fourth receiving module 61 is used to receive attribute values ​​of one or more page elements on specified attributes and specified operation information of the user on the page sent by the client.

[0068] The second update module 62 is used to update the attribute value of the page element on the specified attribute according to the attribute value and the specified operation information.

[0069] The second sending module 63 is used to send the updated attribute value of the page element on the specified attribute to the client.

[0070] In one embodiment, the second update module 62 is further configured to determine a corresponding calculation rule based on the attribute value and the specified operation information; and to calculate the attribute value of the page element on the second attribute based on the calculation rule, the attribute value of the page element on the first attribute, and the specified operation information. Furthermore, the second sending module 63 is further configured to send the calculation rule to the client.

[0071] The operational steps of the method in this application correspond to the structural features of the device, and can be referred to each other, so they will not be described in detail here.

[0072] In summary, according to the technical solution of this application, the client splits page data into one or more page elements of a specified type, uploads the attribute values ​​of the page elements and user operation information to the server, the server is responsible for updating the attribute values ​​of the page elements, and the client displays the attribute values. This application improves the speed and accuracy of the client in handling complex calculations.

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

[0074] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0075] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0076] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0077] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0078] The above description is merely an embodiment of this application and is not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A page data processing method, comprising: Displays the page structure data for the order page; Based on the page structure data, obtain at least one order page element of a specified type; Determine the value of the first attribute on the first attribute of the obtained order page element; Based on the first attribute value and the user's operation on the order page element, the second attribute value of the order page element on the second attribute is obtained from the server; The second attribute is different from the first attribute; Display the first attribute value as the second attribute value; The step of obtaining the second attribute value of the order page element in the second attribute from the server based on the first attribute value and the user's operation on the order page element includes: The first attribute value and the user's order operation information on the order page are sent to the server. The server receives the second attribute value of the order page element on the second attribute sent by the server; wherein the second attribute value is calculated by the server based on the calculation rule, the first attribute value of the order page element on the first attribute, and the order operation information after determining the corresponding calculation rule based on the first attribute value and the order operation information.

2. The method according to claim 1, wherein obtaining the second attribute value of the order page element in the second attribute from the server based on the first attribute value of the order page element in the first attribute and the user's operation on the order page element includes: Based on the user's actions on the order page elements, determine whether to perform server-side update processing; If so, then obtain the value of the second attribute of the order page element in the second attribute from the server.

3. The method according to claim 2, further comprising: If client-side update processing is performed based on the user's operation on the order page element, then the attribute value of the order page element on the specified attribute is updated.

4. A data processing method, comprising: The server receives the first attribute value of the first attribute of the order page element sent by the client, as well as the user's order operation information on the order page; The corresponding calculation rule is determined based on the first attribute value and the order operation information; Calculate the second attribute value of the order page element on the second attribute according to the calculation rule, the first attribute value of the order page element on the first attribute, and the order operation information; The second attribute is different from the first attribute; The second attribute value is sent to the client.

5. A data processing method, comprising: Displays the page structure data of the target page; Based on the page structure data, obtain at least one page element of a specified type; Determine the value of the first attribute on the first attribute of the obtained page element; Send the first attribute value and the user's specified operation information on the target page to the server; The server receives a second attribute value of the target page element on a second attribute sent by the server; wherein the second attribute value is calculated by the server based on the calculation rule, the first attribute value of the target page element on the first attribute, and the specified operation information after determining the corresponding calculation rule based on the first attribute value and the specified operation information; the second attribute is different from the first attribute. Display the first attribute value as the second attribute value.

6. A data processing method, comprising: The server receives the first attribute value of the page element on the target page and the user's specified operation information on the target page from the client. The corresponding calculation rule is determined based on the first attribute value and the specified operation information; Calculate the second attribute value of the page element in the second attribute according to the calculation rule, the first attribute value of the page element in the first attribute, and the specified operation information; The second attribute is different from the first attribute; The second attribute value is sent to the client.

7. A client, comprising: The display module shows the page structure data of the order page; The acquisition module acquires at least one order page element of a specified type based on the page structure data; The reading module determines the value of the first attribute on the first attribute of the obtained order page element; The first sending module, based on the first attribute value and the user's operation on the order page element, obtains the second attribute value of the order page element on the second attribute from the server; the second attribute is different from the first attribute. The display module displays the first attribute value as the second attribute value; The first sending module is specifically used to send the first attribute value and the user's order operation information on the order page to the server. The third receiving module receives the second attribute value of the order page element on the second attribute sent by the server; wherein the second attribute value is calculated by the server based on the calculation rule, the first attribute value of the order page element on the first attribute, and the order operation information after determining the corresponding calculation rule based on the first attribute value and the order operation information.

8. A server, comprising: The fourth receiving module receives the first attribute value of the first attribute of the order page element sent by the client and the order operation information of the user on the order page; The second update module determines the corresponding calculation rule based on the first attribute value and the order operation information; and calculates the second attribute value of the order page element on the second attribute based on the calculation rule, the first attribute value of the order page element on the first attribute, and the order operation information. The second attribute is different from the first attribute; The second sending module sends the second attribute value to the client.

Images