CN107124477A

CN107124477A - Processing method, terminal and the server of web site contents

Info

Publication number: CN107124477A
Application number: CN201710203087.6A
Authority: CN
Inventors: 梁洁辉
Original assignee: Nubia Technology Co Ltd
Current assignee: Nubia Technology Co Ltd
Priority date: 2017-03-30
Filing date: 2017-03-30
Publication date: 2017-09-01

Abstract

The invention discloses the processing method of web site contents, terminal and server, by sending the content requests message comprising device type mark to server；Allow server to identify the device type for determining terminal according to the device type, and the web site contents being adapted with the device type are returned to terminal.It can so be identified because terminal is added in the content requests message of transmission with the device type of the notification server terminal equipment type, this allows for server after content requests message is received, it can be identified according to the device type in content requests message, directly return to the web site contents being adapted with the terminal, avoid needs to carry out secondary information interaction between server and terminal for same web site contents, Internet resources are saved, accelerate the loading of browsing device net page, the appearance of the situation of page bounce is it also avoid simultaneously, improve browser access effect, greatly improve Consumer's Experience.

Description

Website content processing method, terminal and server

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a method, a terminal, and a server for processing website content.

Background

With the continuous popularization of various intelligent terminals, the browsing demands of people on various websites are also continuously improved. For example, when a website page adapted to a computer is placed in a mobile phone for display, when a user sees the whole webpage, the webpage content is very small, and the user is difficult to see; if the user enlarges the page of the part, the content of the webpage is not completely displayed. Therefore, in current various mainstream websites, designed webpages can be adapted on various terminals only (such as desktop computers, various standard mobile phones, tablet devices, television devices, and the like) so as to meet the requirements of different screen sizes.

However, in the existing adaptation process, the server sends the website content adapted to different types of terminals according to the website domain name, but the website domain name input by the user is often the domain name of the desktop computer at the beginning of "www.

For example, when the user enters www.jd.com into a mobile browser, the browser performs DNS (Domain name system) resolution and sends a request for obtaining web content to the target server. After the target server receives the request, because the domain name is the domain name of the desktop computer, the web page content (such as HTML (HyperText Markup Language), CSS (Cascading Style Sheets), JavaScript, pictures, and the like) adapted to the desktop computer is sent to the mobile phone browser in a HTTP (HyperText Transfer Protocol) response manner, and after the mobile phone browser parses the JavaScript, it finds that the User-Agent (User Agent) of the current device is the mobile phone browser, then discards the currently received web page content, and redirects to the website content request of the mobile terminal through the DOM (Document Object Model) of the HTML, at this time, the access domain name becomes m.jd..

As can be seen from the above process, in the existing adaptation process, since the domain name information input by the user is often the domain name of the desktop computer, the problem of the device type of the terminal cannot be considered, once the terminal used by the user is not the desktop computer, secondary information interaction between the server and the terminal is required, and network resources are greatly wasted; meanwhile, the time for loading the web page by the browser is prolonged, and the user experience is reduced. Under the condition of poor network environment, the browser can even display the page of the desktop computer at first, and then can jump to the page suitable for the terminal used by the user at present, so that the user can obviously feel the page jump, the access effect of the browser is poor, and the user experience is greatly influenced.

Disclosure of Invention

The technical problem to be solved by the invention is as follows: in the existing website content adaptation process, once the domain name input by the user is not matched with the device type of the terminal used by the user, the terminal and the server need to request and return the website content once again, so that network resources are greatly wasted, the access effect of the mobile phone browser is poor, and the user experience is greatly influenced.

In order to solve the above technical problem, the present invention provides a method for processing website content, where the method includes:

the terminal analyzes the website domain name information input by the user to obtain the destination IP address information;

the terminal generates a content request message containing a device type identifier and the website domain name information according to the set device type of the terminal corresponding to the browser;

and the terminal sends the content request message according to the destination IP address information.

Optionally, the device type identifier is set in a header field of the content request packet.

Optionally, before the analyzing the website domain name information input by the user to obtain the destination IP address information, the method for processing the website content further includes:

the terminal detects an operating system adaptive to the browser and sets the equipment type of the terminal corresponding to the browser according to the operating system;

and/or the presence of a gas in the gas,

the browser detects an adaptive operating system of the browser, and sets the device type of a terminal corresponding to the browser according to the adaptive operating system of the browser.

Optionally, the present invention provides a method for processing website content, where the method includes:

the server analyzes the received content request message and extracts the equipment type identification and website domain name information in the content request message;

the server determines the equipment type of the target terminal according to the equipment type identification;

the server determines website content matched with the equipment type according to the equipment type and the website domain name information;

and sending the website content to the target terminal.

Optionally, the processing method of the website content further includes:

when the extracted equipment type identifier in the content request message is empty, the server determines an operating system of a target terminal according to the equipment operating system information in the content request message;

and determining the equipment type of the target terminal based on the operating system, and sending the website content matched with the equipment type to the target terminal.

Optionally, the determining the device type of the target terminal based on the operating system includes:

the server judges whether the operating system only corresponds to one equipment type; if yes, determining the equipment type of the target terminal according to the operating system;

otherwise, determining the equipment type of the target terminal according to the website domain name information in the content request message.

Optionally, the present invention provides a terminal, including:

the domain name resolution module is used for resolving website domain name information input by a user to obtain destination IP address information;

the message generating module is used for generating a content request message containing equipment type identification and website domain name information according to the set equipment type of the terminal corresponding to the browser;

and the message sending module is used for sending the content request message according to the destination IP address information.

Optionally, the present invention provides a server, comprising:

the analysis extraction module is used for analyzing the received content request message and extracting the equipment type identifier and the website domain name information in the content request message;

a processing module for determining the device type of the target terminal according to the device type identifier, and determining the website content adapted to the device type according to the device type and the website domain name information,

and the sending module is used for sending the website content to the target terminal.

Optionally, the sending processing module is configured to determine the device type of the target terminal according to the device type identifier, and determine, according to the device type and the website domain name information, the website content adapted to the device type includes:

the operating system is used for determining the operating system of the target terminal according to the equipment operating system information in the content request message when the equipment type identifier in the content request message extracted by the analysis and extraction module is empty;

the device type of the target terminal is determined based on the operating system;

and the equipment is also used for determining the website content matched with the equipment type according to the equipment type and the website domain name information.

Optionally, the determining, by the processing module, the website content adapted to the device type according to the device type and the website domain name information includes:

the device is used for judging whether the operating system only corresponds to one device type;

the terminal is also used for determining the equipment type of the target terminal according to the operating system when the judgment result is yes;

and when the judgment result is negative, determining the equipment type of the target terminal according to the website domain name information in the content request message.

Advantageous effects

According to the processing method of the website content, the terminal and the server, the terminal analyzes the website domain name information input by the user to obtain the destination IP address information, generates the content request message containing the equipment type identifier and the website domain name information according to the equipment type of the terminal corresponding to the set browser, and then sends the content request message according to the destination IP address information; after receiving a content request message sent by a terminal, a server analyzes the content request message, extracts a device type identifier, determines the device type of the terminal according to the device type identifier, and returns website content matched with the device type to the terminal according to the device type and website domain name information. Therefore, the terminal adds the equipment type identifier which can inform the server of the equipment type of the terminal into the content request message sent by the terminal, so that the server can directly return the website content matched with the terminal according to the equipment type identifier in the content request message after receiving the content request message, thereby avoiding the need of secondary information interaction between the server and the terminal for the same website content and saving network resources; the website content matched with the terminal can be obtained through one request, so that the webpage loading time of the browser is shorter, the page jumping situation is avoided, the browser access effect is improved, and the user experience is greatly improved.

Drawings

The invention will be further described with reference to the accompanying drawings and examples, in which:

fig. 1 is a schematic structural diagram of an optional terminal for implementing various embodiments of the present invention;

FIG. 2 is a block diagram of an alternative server for implementing various embodiments of the invention;

FIG. 3 is a schematic diagram of an alternative user, terminal and server interaction architecture for implementing various embodiments of the present invention;

fig. 4 is a flowchart illustrating a method for processing website content according to a first embodiment of the present invention;

fig. 5 is a flowchart illustrating a website content processing method for determining a device type based on an operating system according to a first embodiment of the present invention;

fig. 6 is a schematic flowchart of a more specific operation system-based device type determination of a target terminal according to a first embodiment of the present invention;

fig. 7 is a schematic structural diagram of a terminal according to a third embodiment of the present invention;

fig. 8 is a schematic structural diagram of a more specific terminal according to a third embodiment of the present invention;

fig. 9 is a schematic structural diagram of a server according to a third embodiment of the present invention;

fig. 10 is a schematic structural diagram of a browser according to a fourth embodiment of the present invention.

Detailed Description

It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

A terminal implementing various embodiments of the present invention will now be described with reference to the accompanying drawings. In the following description, suffixes such as "module", "component", or "unit" used to denote elements are used only for facilitating the explanation of the present invention, and have no specific meaning in themselves. Thus, "module" and "component" may be used in a mixture.

The terminal may be implemented in various forms. For example, the terminal described in the present invention may include terminals such as a mobile phone, a smart phone, a notebook computer, a digital broadcast receiver, a PDA (personal digital assistant), a PAD (tablet computer), a PMP (portable multimedia player), a navigation device, and the like, and fixed terminals such as a digital TV, a desktop computer, and the like. In the following, it is assumed that the terminal is a mobile terminal. However, it will be understood by those skilled in the art that the configuration according to the embodiment of the present invention can be applied to a fixed type terminal in addition to elements particularly used for moving purposes.

Fig. 1 is a schematic diagram of a hardware structure of an optional mobile terminal for implementing various embodiments of the present invention.

The mobile terminal 100 may include a wireless communication unit 110, a user input unit 120, an output unit 130, a memory 140, a controller 150, and the like. Fig. 1 illustrates a mobile terminal having various components, but it is to be understood that not all illustrated components are required to be implemented. More or fewer components may alternatively be implemented. Elements of the mobile terminal will be described in detail below.

The wireless communication unit 110 typically includes one or more components that allow radio communication between the mobile terminal 100 and a wireless communication system or network. For example, the wireless communication unit may include a mobile communication module 111, a wireless internet module 112, and the like.

The mobile communication module 111 transmits and/or receives radio signals to and/or from at least one of a base station (e.g., access point, node B, etc.), an external terminal, and a server. Such radio signals may include voice call signals, video call signals, or various types of data transmitted and/or received according to text and/or multimedia messages.

The wireless internet module 112 supports wireless internet access of the mobile terminal. The module may be internally or externally coupled to the terminal. The wireless internet access technology to which the module relates may include WLAN (wireless LAN) (Wi-Fi), Wibro (wireless broadband), Wimax (worldwide interoperability for microwave access), HSDPA (high speed downlink packet access), and the like.

The user input unit 120 may generate key input data to control various operations of the mobile terminal according to a command input by a user. The user input unit 120 allows a user to input various types of information, and may include a keyboard, dome sheet, touch pad (e.g., a touch-sensitive member that detects changes in resistance, pressure, capacitance, and the like due to being touched), scroll wheel, joystick, and the like. In particular, when the touch pad is superimposed on the display module 131 in the form of a layer, a touch screen may be formed.

The output unit 130 is configured to provide output signals (e.g., audio signals, video signals, alarm signals, vibration signals, etc.) in a visual, audio, and/or tactile manner. The output unit 130 may include a display module 131, an audio output module 132, and the like.

The display module 131 may display information processed in the mobile terminal 100. For example, when the mobile terminal 100 is in a phone call mode, the display module 131 may display a User Interface (UI) or a Graphical User Interface (GUI) related to a call or other communication (e.g., text messaging, multimedia file downloading, etc.). When the mobile terminal 100 is in a video call mode or an image capturing mode, the display module 131 may display a captured image and/or a received image, a UI or GUI showing a video or an image and related functions, and the like.

Meanwhile, when the display module 131 and the touch panel are stacked on each other in the form of layers to form a touch screen, the display module 131 may function as an input device and an output device. The display module 131 may include at least one of a Liquid Crystal Display (LCD), a thin film transistor LCD (TFT-LCD), an Organic Light Emitting Diode (OLED) display, a flexible display, a three-dimensional (3D) display, and the like. Some of these displays may be configured to be transparent to allow a user to view from the outside, which may be referred to as transparent displays, and a typical transparent display may be, for example, a TOLED (transparent organic light emitting diode) display or the like. The mobile terminal 100 may include two or more display modules (or other display devices) according to a particular desired implementation, for example, the mobile terminal may include an external display module (not shown) and an internal display module (not shown). The touch screen may be used to detect a touch input pressure as well as a touch input position and a touch input area.

The audio output module 132 may convert audio data received by the wireless communication unit 110 or stored in the memory 140 into an audio signal and output as sound when the mobile terminal is in a call signal reception mode, a call mode, a recording mode, a voice recognition mode, a broadcast reception mode, or the like. Also, the audio output module 132 may provide audio output related to a specific function performed by the mobile terminal 100 (e.g., a call signal reception sound, a message reception sound, etc.). The audio output module 132 may include a speaker, a buzzer, and the like.

The memory 140 may store software programs and the like for processing and controlling operations performed by the controller 150, or may temporarily store data (e.g., a phonebook, messages, still images, videos, and the like) that has been or is to be output.

The memory 140 may include at least one type of storage medium including a flash memory, a hard disk, a multimedia card, a card-type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, and so on. Also, the mobile terminal 100 may cooperate with a network storage device that performs a storage function of the memory 140 through a network connection.

The controller 150 generally controls the overall operation of the mobile terminal. For example, the controller 150 performs control and processing related to voice calls, data communications, video calls, and the like. The controller 150 may perform a pattern recognition process to recognize a handwriting input or a picture drawing input performed on the touch screen as a character or an image.

The various embodiments described herein may be implemented in a computer-readable medium using, for example, computer software, hardware, or any combination thereof. For a hardware implementation, the embodiments described herein may be implemented using at least one of an Application Specific Integrated Circuit (ASIC), a Digital Signal Processor (DSP), a Digital Signal Processing Device (DSPD), a Programmable Logic Device (PLD), a Field Programmable Gate Array (FPGA), a processor, a controller, a microcontroller, a microprocessor, an electronic unit designed to perform the functions described herein, and in some cases, such embodiments may be implemented in the controller 150. For a software implementation, the implementation such as a process or a function may be implemented with a separate software module that allows performing at least one function or operation. The software codes may be implemented by software applications (or programs) written in any suitable programming language, which may be stored in memory 140 and executed by controller 150.

As shown in fig. 2, in order to implement the structural schematic diagram of an optional server according to various embodiments of the present invention, the server 20 at least includes: an Input Output (IO) bus 21, a processor 22, a memory 23, a memory 24, and a communication device 25. Wherein,

the input/output (IO) bus 21 is connected to other components (the processor 22, the storage 23, the memory 24, and the communication device 25) of the server to which it belongs, and provides a transmission line for the other components.

The processor 22 typically controls the overall operation of the server to which it belongs. For example, processor 22 performs computations, validation, etc. The processor 22 may be a Central Processing Unit (CPU), among others.

The communication device 25, typically comprising one or more components, allows radio communication between a server to which it belongs and a wireless communication system or network.

The memory 23 stores processor-readable, processor-executable software code containing instructions for controlling the processor 22 to perform the functions described herein (i.e., software execution functions).

In the server provided by the present invention, software codes for implementing the functions of the parsing extraction module, the processing module, and the sending module may be stored in the memory 23, and executed by the processor 22 or compiled and executed.

The memory 24, which is typically a semiconductor memory unit, includes Random Access Memory (RAM), Read Only Memory (ROM), and CACHE memory (CACHE), of which RAM is the most important memory. The memory 24 is one of the important components in the computer, and is a bridge for communicating with the CPU22, and the operation of all programs in the computer is performed in the memory, and is used for temporarily storing the operation data in the CPU22 and the data exchanged with an external storage such as a hard disk, and as long as the computer is in operation, the CPU22 transfers the data to be operated to the memory for operation, and the CPU22 transmits the result after the operation is completed.

As shown in fig. 3, to implement an alternative interactive structure diagram of a user, a terminal, and a server in various embodiments of the present invention, it should be understood that, in various embodiments, the user, the terminal, and the server implement the solution of the present invention through interaction. The information interaction between the user and the terminal can be directly carried out, and the information interaction between the terminal and the server can be directly carried out.

The following is a detailed description of specific examples.

First embodiment

In order to ensure that a server can return website content adapted to a device type of a terminal after receiving a content request message sent by the terminal, this embodiment provides a method for processing the website content, and referring to fig. 4, fig. 4 is a flowchart of a method for processing the website content according to a first embodiment of the present invention, where the method includes:

s401, the terminal analyzes the website domain name information input by the user to obtain the destination IP address information;

it should be understood that, in this embodiment, after the user inputs website domain name information (i.e., website information, such as www.jd.com, etc.), the browser will parse the website domain name information to obtain the IP address information of the target server corresponding to the website. Then, the terminal can send the content request message to the target server according to the IP address information so as to request to acquire the website content of the website.

S402, the terminal generates a content request message containing a device type identifier and website domain name information according to the device type of the terminal corresponding to the set browser;

the device types in this embodiment include desktop devices, mobile devices, tablet devices, television devices, and other unusual device types such as smart tape devices.

In this embodiment, the device type identifier may be any character or field that can be recognized by the server and satisfies the rule set in the content request message, such as numbers 1, 2, and 3, or fields DeviceType/A, DeviceType/B, DeviceType/C.

It should be noted that in the present embodiment, one device type identifier necessarily uniquely characterizes one mobile device type. For example, a desktop device is characterized by 0, and other device types cannot be characterized by 0 thereafter.

And S403, the terminal sends a content request message according to the destination IP address information.

In this embodiment, the content request message sent to the server according to the destination IP address information may be an HTTP request message, and the device type identifier may be set in a header field of the content request message.

S404, the server analyzes the received content request message and extracts the equipment type identifier and the website domain name information in the content request message;

it should be understood that the server can extract the device type identifier and the website domain name information only after parsing the received content request message.

S405, the server determines the equipment type of the target terminal according to the equipment type identifier;

it should be understood that, in this embodiment, a correspondence relationship between the device type identifier and the device type is stored in the server, and the server may correspondingly determine what the device type represented by one device type identifier is through the correspondence relationship.

S406, the server determines the website content matched with the equipment type according to the equipment type and the website domain name information;

in this embodiment, the device type may be null, that is, the terminal that sends the content request packet to the server does not add the device type identifier to the content request packet, and at this time, a feasible method is to determine the device type according to the operating system of the target terminal.

S407, the server sends the website content to the target terminal.

In this embodiment, the website content received by the target terminal is the website content adapted to the device type of the terminal, and may be directly displayed to the user.

It should be noted that in the present embodiment, steps S401 to S403 are terminal-operated, and steps S404 to S407 are server-operated.

In this embodiment, when the device type identifier set by the terminal is a character, in order to ensure that the server can know which of the header fields of the content request packet is the device type identifier, negotiation with the server may be performed, and the character appointed to a specific position in the header field is the device type identifier, for example, the last character in the header field.

Taking an HTTP request message of the desktop device as an example, a is set to represent the desktop device. Here, we need to know the header field of the existing HTTP request message, which usually contains information of the application type, the operating system, etc. of the device, but does not contain the device type identifier. For example, "Mozilla/5.0 (X11; Linux X86_64) AppleWebKit/537.36(KHTML, likeGecko) Chrome/51.0.2704.103 Safari/537.36" indicates an HTTP request of a Chrome browser under the Linux system. According to the message generation rule of the present embodiment, the header field of the generated HTTP request message is: "Mozilla/5.0 (X11; Linux X86_64) AppleWebKit/537.36(KHTML, like Gecko) Chrome/51.0.2704.103Safari/537.36, A", which indicates: HTTP request of Chrome browser in desktop device under Linux system. Thus, after the server receives the HTTP request message, the last character a in the header field of the message, i.e., the device type representing the terminal, is understood to be desktop device by the negotiated rule.

It should be understood that when the device type identifier is a field, in order to ensure that the server can know that the field is the device type identifier, a portion of the field can be used to set the identifier name, for example, the DeviceType in the field DeviceType/a is the set identifier name. Thus, after receiving the message, the server can find the whole identification device type identification DeviceType/A according to the identification name DeviceType, and obtain the device type of the terminal.

In this embodiment, before analyzing the website domain name information input by the user to obtain the destination IP address information, or before analyzing the website domain name information input by the user, the device type of the terminal corresponding to the browser needs to be set.

In this embodiment, the setting of the device type of the terminal corresponding to the browser may be an automatic setting, and in this case, one possible manner is:

the browser detects the self-adapted operating system, and then determines the device type of the terminal corresponding to the browser according to the operating system adapted to the browser.

For example, if the browser is a browser suitable for Android (Android) devices, the operating system adapted to the browser is an Android system, and the Android system is an operating system for a mobile phone, so that the terminal sets the device type of the terminal corresponding to the browser as a mobile device.

It should be understood that when the current application provider provides a browser application, different versions of browsers, such as an Android version browser, an IOS version browser, a PC-side browser, etc., may be provided according to different terminal device kernels. Therefore, the browser installed in the terminal initially or downloaded later can only be used in terminal equipment of a specific type, for example, an Android browser cannot run on an apple mobile phone and a computer, and therefore the equipment type of the terminal corresponding to the browser can be automatically determined according to an operating system adapted to the browser.

It should be understood that, in this embodiment, the correspondence between the operating system and the device type of the terminal corresponding to the browser may be stored in the terminal along with the installation of the browser in the form of a graph or the like, and the browser may find the corresponding device type through the stored correspondence after detecting the operating system adapted to the browser itself.

It should be understood that, in the present embodiment, for a browser compatible with multiple operating systems, the device type of the browser can be manually set by a user, and the specific manner of manual setting by the user is described in detail later.

It should be understood that, in the present embodiment, the adapted operating system can be used for browsers of multiple device types, and the device types can also be manually set by the user.

In this embodiment, another possible way to automatically set the device type of the terminal corresponding to the browser is as follows:

and acquiring the size information of the terminal, and then determining the equipment type of the terminal corresponding to the browser according to the acquired size information.

Specifically, the terminal may call an API (Application Programming Interface) Interface to obtain size information in the terminal basic information written in the terminal before.

And judging which size range the size information is in according to the acquired size information, and correspondingly determining the equipment type of the terminal where the current browser is located.

It should be understood that, in this embodiment, the correspondence between the size range and the device type may be stored in the terminal in the form of a graph or the like along with the installation of the browser, and the terminal may find the size range in which the terminal falls after detecting its own size, and then find the corresponding device type through the stored correspondence. For example, when the terminal detects that the size of the terminal is 5 inches, that is, the terminal falls within the size range of the mobile device, the terminal sets the device type of the terminal corresponding to the browser to be the mobile device.

It should be understood that, in the present embodiment, when the terminal size falls within the size range of two or more types of devices, the device type thereof may be manually set by the user.

It should be understood that, in the present embodiment, the device type of the terminal may be manually set by the user when the size of the terminal does not fall within the set size range.

In this embodiment, the setting of the device type of the terminal corresponding to the browser may also be manually set by the user, where the terminal receives device type information input by the user, and sets the device type of the terminal corresponding to the browser according to the device type information input by the user.

For example, a device type input box is set in the browser, the user inputs device type information in the input box, such as a mobile phone, a computer, and the like, and the terminal analyzes the input device type information to obtain a corresponding device type and sets the device type. For example, when the user inputs a mobile phone, the terminal finds the device type corresponding to the mobile phone as the mobile device according to the information correspondence table stored in the terminal, and then sets the device type of the terminal corresponding to the browser as the mobile device.

It should be understood that, in the above example, the user needs to input the device type information by typing, and the information input by the user must be stored in the information correspondence table, which is complex in process and inconvenient in operation, so a better way is to set a device type selection menu in the setting page of the browser, and the user selects a certain device type given in the menu by clicking the selection menu, so as to realize the input of the device type information, and thus, the terminal can directly set the device type of the terminal corresponding to the browser according to the device type selected by the user. It is noted that the process of selecting the device type by the user at the selected menu is actually the process of inputting the device type information by the user.

In this embodiment, before the user manually sets the device type, the browser may be set with a default device type (i.e., a default device type). The default device type can be set automatically by the browser in the automatic setting mode; or may be preset in the browser application by the application provider of the browser.

In this embodiment, the setting function of the browser may be integrated into a plug-in or an application, so that uniform device type setting is performed on all browsers downloaded from a terminal, and when a user downloads a new browser and surfs the internet through the new browser, the user may still obtain adaptive website content through one-time interaction, thereby further improving user experience.

In this embodiment, if the device type identifier in the content request packet extracted by the server is empty, that is, the terminal that sends the content request packet to the server does not add the device type identifier in the content request packet, at this time, in order to improve the accuracy of identifying the terminal type by the server and ensure the probability of successful adaptation between the returned website content and the target terminal as much as possible, the embodiment further provides a method for processing the website content based on the operating system to determine the device type, referring to fig. 5, including:

s501, determining an operating system of the target terminal according to the equipment operating system information in the content request message;

it should be understood that, according to the existing generation rule of the content request message, the header field of the content request message usually contains the operating system information of the device. For example, in the header field of the HTTP request message "Mozilla/5.0 (X11; Linux X86_64) applewkit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36", after the server parses the HTTP request message, the operating system information "Linux X86_ 64" in the request message can be obtained, and thus the server can determine that the operating system of the target terminal is the 64-bit Linux operating system.

S502, determining the device type of the target terminal based on the operating system;

it should be understood that, for some operating systems, they are only applied to a certain type of device, and at this time, the determination of the device type according to the operating system can be implemented; for example, the MacOSX system only runs on an apple Macintosh series computer, so that the server can determine that the device type of the target terminal is desktop equipment according to the MacOSX system, and for the operating systems only corresponding to a certain type of device, the operating systems include Android, iOS, Windows XP, Windows 8, Windows10, Windows phone and the like. Due to the existence of the operating system, the server can determine the device type of the target terminal according to the operating system at some time.

And S503, sending the website content matched with the device type to the target terminal.

It should be understood that the target terminal in this embodiment is a terminal that sends a content request message, that is, a terminal that the server returns the content of the website.

In this embodiment, a specific process of determining the device type of the target terminal based on the operating system is shown in fig. 6, and includes:

s601, judging whether the operating system only corresponds to one equipment type, if so, turning to S602; otherwise, go to S603;

it should be understood that for some operating systems, it may be applied to two or more types of devices, such as a Linux system, for example.

And S602, determining the device type of the target terminal according to the operating system.

It should be understood that, in this embodiment, the server may store the correspondence between the operating system and the device type in the form of a graph or the like, so as to implement an operation of determining the device type of the target terminal according to the operating system.

S603, determining the equipment type of the target terminal according to the website domain name information in the content request message.

It should be understood that, in this embodiment, for an operating system such as a Linux system that can be applied to two or more types of devices, the server cannot determine the device type of the target terminal according to the operating system, and at this time, the device type of the target terminal is still determined according to the website domain name information in the manner of the prior art.

It should be noted that, the steps in this embodiment may be respectively performed by the terminal shown in fig. 1 and the server shown in fig. 2, specifically, the process of parsing the website domain name information input by the user and generating the content request message may be performed by the controller 150 of the terminal shown in fig. 1, the process of setting the device type of the terminal corresponding to the browser may be performed by the user input unit 120, the memory 140 and the controller 150, and the process of sending the content request message may be performed by the wireless communication unit 110. The receiving of the content request message and the sending of the website content are performed by the communication device 25 of the server shown in fig. 2, and the parsing of the content request message and the determining of the device type may be performed by 22, the storage 23 and the memory 24.

In the processing method for website content provided by this embodiment, a content request message including an equipment type identifier is sent to a server; and the server can determine the equipment type of the terminal according to the equipment type identifier and return the website content matched with the equipment type to the terminal. Therefore, the terminal adds the equipment type identifier which can inform the server of the equipment type of the terminal into the content request message sent by the terminal, so that the server can directly return the website content matched with the terminal according to the equipment type identifier in the content request message after receiving the content request message, thereby avoiding the need of secondary information interaction between the server and the terminal for the same website content and saving network resources; the website content matched with the terminal can be obtained through one request, so that the webpage loading time of the browser is shorter, the page jumping situation is avoided, the browser access effect is improved, and the user experience is greatly improved.

Second embodiment

In order to better understand the technical solution of the present invention, this embodiment further exemplifies the case where, on the basis of the first embodiment, the content request message is an HTTP request message, the device type identifier is set at the end of the header field of the HTTP request message, the user can manually set the device type, and the browser sets a default value for the device type.

Setting: the device type identification contains an identification name part "DeviceType"; setting: 0 represents desktop equipment, 1 represents mobile equipment, 2 represents tablet equipment, and 3 represents television equipment; setting: the current terminal used by the user is a mobile phone.

Firstly, a user enters a browser to set the type of browser equipment, and the step can be skipped because the browser is provided with a default value;

then, when the user inputs a website domain name to be accessed in the address bar and starts to browse a webpage, the mobile phone browser resolves the website domain name into an IP address, generates an HTTP request message (in this embodiment, the device type identifier is DeviceType/1) containing a device type identifier in a header field, and sends the HTTP request message to a target website server to request to acquire website content;

the server receives and analyzes the HTTP request message sent by the mobile phone, and extracts the equipment type identifier in the HTTP request message: DeviceType/1;

the server can determine that the device type of the device sending the HTTP request message is the mobile device according to the stored corresponding relationship between the device type identifier and the device type.

Then, the server returns the website content suitable for the mobile phone to browse to the mobile phone according to the determined equipment type;

after the mobile phone receives the website content returned by the server, the browser analyzes the website content and renders the website content so as to enable a user to operate.

In the method for processing website content provided in this embodiment, the server may directly determine the device type of the terminal and return the adapted website content by adding the device type identifier to the HTTP request packet. The method and the system have the advantages that the request and the return of the website contents can be realized at one time between the server and the terminal, network resources are saved, the loading of the browser to the webpage is accelerated, the page jumping condition is avoided, the browser access effect is improved, and the user experience is improved.

Third embodiment

Referring to fig. 7, fig. 7 is a schematic structural diagram of a terminal according to a third embodiment of the present invention, where the terminal includes:

the domain name resolution module 71 is configured to resolve website domain name information input by a user to obtain destination IP address information;

a message generating module 72, configured to generate a content request message including a device type identifier and website domain name information according to a device type of a terminal corresponding to a set browser;

and a message sending module 73, configured to send a content request message according to the destination IP address information.

It should be understood that, in this embodiment, after the user inputs the website domain name information, the browser will parse the website domain name information, so as to obtain the IP address information of the target server corresponding to the website. Then, the terminal can send the content request message to the target server according to the IP address information so as to request to acquire the website content of the website.

It should also be understood that, in this embodiment, the device type of the terminal corresponding to the browser is the device type of the terminal corresponding to the browser. The device types in this embodiment include desktop devices, mobile devices, tablet devices, television devices, and other unusual device types such as smart tape devices.

In this embodiment, the device type identifier may be any character or field that can be recognized by the server and satisfies the setting rule of the content request message, such as a letter A, B, C, or fields of DeviceType/1, DeviceType/2, DeviceType/3, and the like.

It should be noted that in the present embodiment, one device type identifier necessarily uniquely characterizes one mobile device type. For example, if a mobile device is characterized by B, then other device types cannot be characterized by B thereafter.

In this embodiment, the content request message for the server may be an HTTP request message, and the device type identifier may be set in a header field of the content request message.

It should be understood that when the device type identifier is a character, in order to ensure that the server can know which of the header fields of the content request message is the device type identifier, negotiation with the server may be performed, and the character appointed to a specific position in the header field is the device type identifier, such as the last character in the header field.

In this embodiment, referring to fig. 8, the terminal further includes a system setting module 74, configured to set a device type of the terminal corresponding to the browser before the domain name resolution module 71 works or before website domain name information input by the user.

In this embodiment, the setting of the system setting module 74 for the device type of the terminal corresponding to the browser may be automatic setting, and in this case, one possible setting manner is:

the system setting module 74 detects the operating system adapted to the browser, and then determines the device type of the terminal corresponding to the browser according to the operating system adapted to the browser.

It should be understood that when the current application provider provides a browser application, different versions of browsers, such as an Android version browser, an IOS version browser, a PC-side browser, etc., may be provided according to different terminal device kernels. Therefore, since the browser initially installed or downloaded in the terminal can only be used in a specific type of terminal device, for example, an Android browser cannot run on an apple mobile phone or a computer, the system setting module 74 can automatically determine the device type of the terminal corresponding to the browser according to the operating system adapted to the browser.

It should be understood that, in this embodiment, the correspondence between the operating system and the device type of the terminal corresponding to the browser may be stored in the terminal in the form of a graph or the like along with the installation of the browser, and the system setting module 74 may find the corresponding device type according to the stored correspondence after detecting the operating system adapted to the browser itself.

It should be understood that, in the present embodiment, for a browser compatible with a plurality of operating systems, the device type thereof may be manually set by the user.

In this embodiment, another possible way for the system setting module 74 to automatically set the device type of the terminal corresponding to the browser is as follows:

the system setting module 74 obtains the size information of the terminal, and then determines the device type of the terminal corresponding to the browser according to the obtained size information.

Specifically, the system setting module 74 may call an API interface to obtain size information in the terminal basic information written in the terminal before; and judging which size range the size information is in according to the acquired size information, and correspondingly determining the equipment type of the terminal where the current browser is located.

It should be understood that, in this embodiment, the correspondence between the size range and the device type may be stored in the terminal in the form of a graph or the like along with the installation of the browser, and the terminal may find the size range in which the terminal falls after detecting its own size, and then find the corresponding device type through the stored correspondence.

In this embodiment, the setting of the device type of the terminal corresponding to the browser by the system setting module 74 may also be manually set by the user, at this time, the system setting module 74 receives the device type information input by the user, and sets the device type of the terminal corresponding to the browser according to the device type information input by the user.

In this embodiment, before the user manually sets the device type, the browser may be set with a default device type (i.e., a default device type). The default device type setting may be automatically set by the system setting module 74 in the automatic setting manner described above; or may be preset in the browser application by the application provider of the browser.

In this embodiment, the function of setting the device type of the terminal corresponding to the browser by the system setting module 74 may be integrated into one plug-in or one application, so as to implement uniform device type setting for all browsers downloaded from the terminal, so that when a user downloads a new browser and surfs the internet through the new browser, the user may still obtain the adapted website content through one-time interaction, thereby further improving user experience.

The present embodiment further provides a server, referring to fig. 9, where fig. 9 is a schematic structural diagram of a server according to a third embodiment of the present invention, including:

the parsing and extracting module 91 is configured to parse the received content request packet, and extract the device type identifier and the website domain name information in the content request packet;

the processing module 92 is configured to determine the device type of the target terminal according to the device type identifier, and determine, according to the device type and the website domain name information, website content adapted to the device type;

and a sending module 93, configured to send the website content to the target terminal.

In this embodiment, the device type identifier in the content request packet extracted by the parsing and extracting module 91 may be empty, that is, the device type identifier is not added to the content request packet by the terminal that sends the content request packet to the server, at this time, in order to improve the accuracy of identifying the terminal type by the server and ensure the probability of successful adaptation between the returned website content and the target terminal as much as possible, the processing module 92 is further configured to determine the operating system of the target terminal according to the device operating system information in the content request packet when the device type identifier in the content request packet extracted by the parsing and extracting module 91 is empty, determine the device type of the target terminal based on the operating system, and determine the website content adapted to the device type according to the device type and the website domain name information.

Thereafter, the sending module 93 may send the website content adapted to the device type to the target terminal.

It should be understood that, according to the existing generation rule of the content request message, the header field of the content request message usually contains the operating system information of the device.

It should be understood that, for some operating systems, they are only applied to a certain type of device, and at this time, the determination of the device type according to the operating system can be implemented; for example, the MacOSX system only runs on an apple Macintosh series computer, so that the server can determine that the device type of the target terminal is desktop equipment according to the MacOSX system, and for the operating systems only corresponding to a certain type of device, the operating systems include Android, iOS, Windows XP, Windows 8, Windows10, Windows phone and the like. Due to the existence of such an operating system, the processing module 92 may determine the device type of the target terminal according to the operating system at some time.

It should be understood that for some operating systems, it may be applied to two or more types of devices, such as a Linux system, for example. Therefore, the processing module 92 is configured to determine, according to the device type and the website domain name information, website content adapted to the device type, including:

That is, for an operating system that can be applied to two or more types of devices, the processing module 92 cannot determine the device type of the target terminal according to the operating system, and at this time, the device type of the target terminal is still determined according to the website domain name information in the prior art.

It should be noted that, in this embodiment, the specific structures of the terminal and the server may also be as shown in fig. 1 and fig. 2, at this time, the domain name resolution module 71, the message generation module 72, and the system setting module 74 may be disposed in the controller 150 of the terminal as shown in fig. 1, and the functions thereof may be completed by the controller 150, and the message sending module 73 may be disposed in the wireless communication unit 110, and the functions thereof may be completed by the wireless communication unit 110. And software codes implementing the functions of the parsing extraction module 91 and the processing module 92 may be stored in the memory 23 of the server as shown in fig. 2 and executed by the processor 22 or compiled and then executed.

The terminal and the server provided by the embodiment send a content request message containing the device type identifier to the server through the terminal; and the server can determine the equipment type of the terminal according to the equipment type identifier and return the website content matched with the equipment type to the terminal. Therefore, the terminal adds the equipment type identifier which can inform the server of the equipment type of the terminal into the content request message sent by the terminal, so that the server can directly return the website content matched with the terminal according to the equipment type identifier in the content request message after receiving the content request message, thereby avoiding the need of secondary information interaction between the server and the terminal for the same website content and saving network resources; the website content matched with the terminal can be obtained through one request, so that the webpage loading time of the browser is shorter, the page jumping situation is avoided, the browser access effect is improved, and the user experience is greatly improved.

Fourth embodiment

In order to better understand the technical solution of the present invention, in this embodiment, on the basis of the third embodiment, a content request message is an HTTP request message, a device type identifier is set at the end of a header field of the HTTP request message, a user may manually set a device type, and a case where a default value is set for the device type by a browser and a case where the HTTP request message does not include the device type identifier are taken as examples, which further exemplifies the present invention.

Setting: the current using terminal of the user is an android mobile phone.

Example 1:

setting: the device type identification contains an identification name part "DeviceType"; setting: 0 represents desktop equipment, 1 represents mobile equipment, 2 represents tablet equipment, and 3 represents television equipment.

Referring to fig. 10, fig. 10 is a schematic structural diagram of a browser 1000 according to this embodiment, including: address bar unit 10001, system setting unit 10002, content analysis unit 10003, website content rendering unit 10004, HTTP unit 10005, and DNS analysis unit 10006.

It should be understood that the address bar unit 10001 and the system setting unit 10002 may be set in the APP layer 1001 of the browser 1000, where the APP layer 1001 is mainly used for human-computer interaction between the browser and the user; the content parsing unit 10003 and the website content rendering unit 10004 may be disposed in the core layer 1002 of the browser 1000, where the core layer 1002 of the browser is mainly configured to parse the received data and display the parsed data to the user; the HTTP unit 10005 and the DNS resolution unit 10006 may be disposed in a network protocol layer 1003 of the browser 1000, and the network protocol layer 1003 is mainly used for data interaction with a server.

Specifically, the user may set the browser device type through the system setting unit 10002, and the user may also choose not to set the browser device type because the browser itself has a default value, and directly use the default device type;

thereafter, the address bar unit 10001 may receive the website domain name to be accessed, which is input in the address bar by the user, and submit the website domain name to the DNS resolution unit 10006 of the network protocol layer 1003 for resolution, so as to obtain the IP address of the website server, and the HTTP unit 10005 generates an HTTP request message containing the device type identifier "DeviceType/1" in the header field, and sends the HTTP request message to the target website server according to the IP address of the website server.

the analysis and extraction module of the server can determine the equipment type of the equipment sending the HTTP request message as the mobile equipment according to the stored corresponding relationship between the equipment type identification and the equipment type.

Then, the sending processing module of the server can send the website content suitable for the mobile phone to browse to the mobile phone according to the determined equipment type;

after receiving the website content returned by the server, the mobile phone parses the website content through the content parsing unit of the core layer 1002, and renders the website content through the website content rendering unit 10004, so as to enable the user to perform an operation.

Example 2:

at this time, the HTTP request message does not include the device type identifier, so the system setting unit 10002 of the APP layer 1001 of the browser 1000 is no longer used for setting the device type of the browser, and the whole browser operates: first, the address bar unit 10001 receives a website domain name to be accessed, which is input in the address bar by the user, and sends the website domain name to the DNS resolution unit 10006 of the network protocol layer 1003 for resolution, so as to obtain an IP address of the website server, and the HTTP unit 10005 generates an HTTP request message (the request message does not include the device type identifier), and sends the HTTP request message to the target website server according to the IP address of the website server.

After the analysis and extraction module of the server receives and analyzes the HTTP request message sent by the android mobile phone, the operating system determining unit determines that the operating system of the device sending the HTTP request message is an android operating system according to the operating system information in the HTTP request message.

And then the device type determining unit can determine the device type of the device sending the HTTP request message as the mobile device according to the determined android operating system through the corresponding relation between the operating system and the device type.

Then, a content sending unit of the server can send the website content suitable for the mobile phone to browse to the android mobile phone according to the determined equipment type;

after receiving the website content returned by the server, the android phone parses the website content through the content parsing unit 10003 of the core layer 1002, and renders the website content through the website content rendering unit 10004, so as to allow the user to perform an operation.

According to the terminal and the server provided by the embodiment, the device type identifier is added into the HTTP request message, so that the server can directly determine the device type of the terminal and return the adapted website content, the request and the return of the website content can be realized between the server and the terminal at one time, network resources are saved, the loading of a webpage by a browser is accelerated, the page jumping condition is avoided, and the access effect of the browser is improved; meanwhile, when the HTTP request message received by the server does not contain the equipment type identifier, the equipment type is judged according to the operating system information in the HTTP request message, so that the identification accuracy of the server on the terminal type is improved, the probability of successful adaptation between the returned website content and the target terminal is ensured to the greatest extent, and the user experience is further improved.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.

While the present invention has been described with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, which are illustrative and not restrictive, and it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the invention as defined in the appended claims.

Claims

1. A method for processing website content, comprising:

the terminal generates a content request message containing a device type identifier and the website domain name information according to the device type of the terminal corresponding to the browser;

2. The method for processing website content according to claim 1, wherein the device type identifier is set in a header field of the content request message.

3. The method for processing website contents according to claim 1 or 2, wherein before the parsing the website domain name information input by the user to obtain the destination IP address information, the method for processing website contents further comprises:

the terminal receives equipment type information input by a user, and the equipment type of the terminal corresponding to the browser is set according to the equipment type information;

and/or the presence of a gas in the gas,

4. A method for processing website content, comprising:

and sending the website content to the target terminal.

5. The method for processing website contents according to claim 4, wherein the method for processing website contents further comprises:

6. The method for processing website content according to claim 5, wherein the determining the device type of the target terminal based on the operating system comprises:

7. A terminal, comprising:

8. A server, comprising:

the processing module is used for determining the equipment type of the target terminal according to the equipment type identifier and determining the website content matched with the equipment type according to the equipment type and the website domain name information;

9. The server according to claim 8, wherein the processing module is configured to determine a device type of the target terminal according to the device type identifier, and determine the website content adapted to the device type according to the device type and the website domain name information includes:

10. The server of claim 9, wherein the processing module to determine website content adapted to the device type based on the device type and website domain name information comprises: