Terminal device, page access method and storage medium

Abstract

The present application relates to the field of network communication technology, and discloses a terminal device, a page access method and a storage medium. The terminal device includes a Linux system and an RTOS system, an internal thread channel is established between the Linux system and the RTOS system, the Linux system is allocated a first IP address for communication in the internal thread channel, the RTOS system is allocated a second IP address for communication in the internal thread channel, the Linux system is used to access the RTOS system through the second IP address, and the RTOS system is used to access the Linux system through the first IP address, so as to solve the interaction problem between the dual system and the access device.

Description

Technical Field

[0001] The present application relates to the field of network communication technology, and in particular to a terminal device, a page access method and a storage medium. Background Art

[0002] At present, with the popularization of broadband access, more and more network terminal devices are introduced into home and enterprise networks, and dual systems are also applied to such network terminal devices (such as routers). On the contrary, the inventors have found that the dual-system network terminal device products in the traditional solution usually run their own http services (httpserver) in the two systems of the device respectively. The two http services provide corresponding IP addresses for their respective access, which makes data interaction more troublesome, undoubtedly increases the interaction burden of the terminal device, and easily leads to unsmooth data interaction. Summary of the invention

[0003] The embodiments of the present application provide a terminal device, a page access method and a storage medium to solve the technical problem that in the traditional dual-system solution, the interaction burden of the terminal device is increased, which easily leads to unsmooth data interaction.

[0004] A terminal device includes a Linux system and an RTOS system. An internal thread channel is established between the Linux system and the RTOS system, wherein the Linux system is allocated a first IP address for communication in the internal thread channel, the RTOS system is allocated a second IP address for communication in the internal thread channel, the Linux system is used to access the RTOS system through the second IP address, and the RTOS system is used to access the Linux system through the first IP address.

[0005] In one embodiment, the Linux system is the master system and the RTOS system is the slave system.

[0006] In one embodiment, the non-volatile memory of the terminal device is shared between the Linux system and the RTOS system.

[0007] In one embodiment, the RTOS system is used to send a write command corresponding to the write operation to the Linux system when performing a write operation on the non-volatile memory of the terminal device;

[0008] The Linux system is used to respond to the write command and perform the write operation.

[0009] In one embodiment, the RTOS system is further used to send a write command corresponding to the write operation to the Linux system when performing a write operation on the non-volatile memory of the terminal device;

[0010] The Linux system is also used to respond to write commands and perform write operations.

[0011] A page access method based on a terminal device, wherein a Linux system runs a Linux service and a Linux agent, and an RTOS system runs an RTOS service, the method comprising:

[0012] The access device sends a first page request to the Linux service, where the first page request is used to request a page of the RTOS system;

[0013] The Linux service responds to the first page request and sends a first redirection feedback to the access device;

[0014] The access device responds to the first redirection feedback and sends a second page request to the Linux agent, where the second page request is used to request a page of the RTOS system;

[0015] The Linux agent forwards the second page request to the RTOS service via the second IP address;

[0016] The RTOS service responds to the second page request and obtains the corresponding first page data result;

[0017] The RTOS service feeds the first page data result back to the Linux agent through the first IP address;

[0018] The Linux agent feeds the first page data result back to the access device.

[0019] In one embodiment, the page access method further includes:

[0020] The access device sends a third page request to the Linux service, where the third page request is used to request a page of the Linux system;

[0021] The Linux service responds to the third page request and obtains the corresponding second page data result;

[0022] The Linux service feeds the second page data result back to the access device.

[0023] A page access method based on a terminal device, wherein a Linux system runs a Linux service, and an RTOS system runs an RTOS service and an RTOS agent, the method comprising:

[0024] The access device sends a fourth page request to the RTOS service, where the fourth page request is used to request a page of the Linux system;

[0025] When the RTOS service responds to the fourth page request, it sends a second redirection feedback to the access device;

[0026] The access device responds to the second redirection feedback and sends a fifth page request to the RTOS agent, where the fifth page request is used to request a page of the Linux system;

[0027] The RTOS agent forwards the fifth page request to the Linux service via the first IP address;

[0028] The Linux service responds to the fifth page request and obtains the corresponding third page data result;

[0029] The Linux service feeds the third page data result back to the RTOS agent through the second IP address;

[0030] The RTOS agent feeds the third page data result back to the access device.

[0031] In one embodiment, the method further comprises:

[0032] The access device sends a sixth page request to the RTOS service, where the sixth page request is used to request a page of the RTOS system;

[0033] The RTOS service responds to the sixth page request and obtains the corresponding fourth page data result;

[0034] The RTOS service feeds the fourth page data result back to the access device.

[0035] A computer-readable storage medium stores a computer program, wherein the computer program implements functions or steps on a terminal device side when executed by a processor.

[0036] Compared with the traditional solution, in this application, an internal thread communication channel will be established between the Linux system and the RTOS system, and IP addresses will be allocated between the channels of the two systems, rather than using the existing technology to allocate IP addresses for external communication to the http server in the system to provide services. The interaction between the two systems is simpler, the interaction complexity is reduced, and the smoothness of data interaction is improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the description of the embodiments of the present application will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0038] Figure 1 It is a structural diagram of an ITC channel established based on RPC in an embodiment of the present application;

[0039] Figure 2This is a schematic diagram of an interaction process in which a LAN side device requests an RTOS service in an embodiment of the present application;

[0040] Figure 3 This is a schematic diagram of an interactive process in which a WAN side device requests a Linux service in one embodiment of the present application;

[0041] Figure 4 It is a structural diagram of a terminal device in an embodiment of the present application. DETAILED DESCRIPTION

[0042] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0043] Considering that in the traditional solution mentioned in the background technology, each of the two systems of the device runs its own http service (http server), and the two http services provide corresponding IP addresses for each to access, which will make data interaction more troublesome, undoubtedly increase the interaction burden of the terminal device, and easily lead to technical problems such as unsmooth data interaction, the embodiment of the present application proposes a new solution. It mainly includes the following aspects, which are described below.

[0044] In one embodiment, please refer to Figure 1 As shown, a terminal device is provided, which can be a network communication device, such as a router, etc., which is not specifically limited. The terminal device includes a Linux system and an RTOS system, and an internal thread channel (Internal Thread Communication, ITC) is established between the Linux system and the RTOS system. Exemplarily, the internal thread channel can be an ITC channel based on RPC. Among them, the Linux system is allocated a first IP address for communication in the internal thread channel, and the RTOS system is allocated a second IP address for communication in the internal thread channel. That is to say, fixed private IP addresses are allocated between the RTOS system and the Linux system, respectively, for communication between the RTOS system and the Linux system.

[0045] An exemplary example is as follows:

[0046] (1) The Linux system is assigned the first IP address for the ITC channel, which can be: 172.**.255.**;

[0047] (2) The second IP address used for the ITC channel on the RTOS system side can be: 172.**.255.**.

[0048] Based on the communication relationship between the above Linux system and the RTOS system, the Linux system is used to access the RTOS system through the ITC channel using the second IP address of the RTOS system, and the RTOS system is used to access the Linux system through the ITC channel using the first IP address of the Linux system.

[0049] Compared with the traditional solution, in the embodiment of the present application, an internal thread communication channel is established between the Linux system and the RTOS system, and IP addresses are allocated between the channels of the two systems, rather than using the existing technology to allocate IP addresses for external communication to the httpserver within the system to provide services. The interaction between the two systems is simpler, the complexity of interaction is reduced, and the smoothness of data interaction is improved.

[0050] In one embodiment, please continue to refer to Figure 1 As shown, the Linux system and the RTOS system share the non-volatile storage (non-vol) of the terminal device, that is, the flash memory on the terminal device. In this embodiment, the Linux system and the RTOS system share the non-vol, and can share the memory parameter configuration area, which facilitates data synchronization between the two systems. There is no need to open a separate storage area for each system, which is beneficial to the additional synchronization resource overhead between the two systems.

[0051] In one embodiment, the Linux system is the master system and the RTOS system is the slave system, that is, the Linux system is set to the master mode and the RTOS system is set to the slave mode. In this embodiment, the Linux system and the RTOS system are respectively set to the master-slave mode, which is conducive to managing the operation of the two systems.

[0052] In one embodiment, the RTOS system is used to send a write command corresponding to the write operation to the Linux system when performing a write operation on the non-volatile memory of the terminal device; the Linux system is used to respond to the write command and execute the write operation.

[0053] In one embodiment, the RTOS system is further used to send a write command corresponding to the write operation to the Linux system when performing a write operation on the non-volatile memory of the terminal device; the Linux system is further used to respond to the write command and execute the write operation;

[0054] That is to say, if the RTOS system wants to write or read the flash memory of the terminal device, it needs to send the corresponding instructions to the Linux system, and then the Linux system will execute the write or read flash memory operation.

[0055] In one embodiment, continue as Figure 1 As shown, the Linux system runs Linux services and Linux agents, and the RTOS system runs RTOS services and RTOS agents. Linux services and Linux agents can be understood as program modules running on the Linux system, and RTOS services and RTOS agents are program modules running on the RTOS system. Among them, Linux services and Linux agents specifically refer to a web service (linux web server) and a web agent (linux web proxy), and RTOS services and RTOS agents specifically refer to a web service (RTOS web server) and a web agent (RTOS linux webproxy), that is:

[0056] (1) Set up RTOS service and RTOS agent on the RTOS system. The service port can be 8083.

[0057] (2) The Linux system sets up Linux services and Linux agents, and the service port can also be 8083.

[0058] It should be noted that users can access the pages corresponding to the Linux system or RTOS system through an access device, wherein the above-mentioned access device can be a WAN (Wide Area Network) side device or a LAN (Local Area Network) side device. Based on the above-mentioned terminal device, the present application provides a new way for an access device to access the Linux system or RTOS system of the above-mentioned terminal device, which are described below respectively.

[0059] In one embodiment, if Figure 2 As shown, based on the terminal device of the above embodiment, the embodiment of the present application provides a page access method, taking the access device as a LAN side device and the terminal device as a router as an example, the method includes the following steps:

[0060] S101: The LAN side device sends a first page request to the Linux service, where the first page request is used to request a page of the RTOS system.

[0061] In this embodiment, when the LAN side device needs to access the page of the RTOS system, the LAN side device sends a first page request to the Linux service of the router, and the first page request is used to request access to the page of the RTOS system. For example, the LAN side device sends the following first page request to the Linux service: 192.***.0.1 / StatusConnection.html, and the page resource requested by the request is StatusConnection.html.

[0062] S102: The Linux service responds to the first page request and sends a first redirection feedback to the LAN side device;

[0063] After receiving the first page request, the Linux service will send a first redirection feedback (Redirect to 192.***.0.1:8083) to the LAN side device. The first redirection feedback will carry the service port 8083 of the Linux service to allow the LAN side device to resend the request to the Linux proxy.

[0064] S103: The LAN side device responds to the first redirection feedback and sends a second page request to the Linux agent, where the second page request is used to request a page of the RTOS system;

[0065] After the LAN side device receives the first redirection feedback (Redirect to 192.***.0.1:8083), the LAN side device will respond to the first redirection feedback and send a second page request (192.***.0.1:8083 / StatusConnection.html) to the Linux agent, wherein the second page request carries the service port 8083 of the Linux agent, and the second page request is used to request the StatusConnection.html page of the RTOS system.

[0066] S104: The Linux agent forwards the second page request to the RTOS service via the second IP address;

[0067] After receiving the second page request, the Linux agent forwards the second page request to the RTOS service through the second IP address (172.**.255.**), which is used to request the StatusConnection.html page from the RTOS service.

[0068] S105: The RTOS service responds to the second page request, obtains the corresponding first page data result, and feeds the first page data result back to the Linux agent through the first IP address;

[0069] After receiving the second page request, the RTOS service will obtain the first page data result corresponding to the second page request, that is, it will obtain the page data result corresponding to the StatusConnection.html page, and then feed back the first page data result to the Linux agent through the first IP address of the Linux agent (172.**.255.**), that is, feed back the page data result corresponding to the StatusConnection.html page to the Linux agent.

[0070] S106: The Linux agent feeds back the first page data result to the LAN side device.

[0071] After the Linux agent obtains the first page data result, it feeds the first page data result back to the LAN side device through the service port 8083, that is, the page data result corresponding to the StatusConnection.html page. At this point, the LAN side device requests the page data to complete the dual-system interactive communication, and the user obtains the page of the RTOS system to be accessed through the LAN side device.

[0072] It should be noted that the embodiment of the present application provides a new page access method based on the above-mentioned terminal device. It does not require the two http services of the two systems to provide corresponding IP addresses for the access devices to access respectively. Instead, it converts the interaction of the two systems to realize the access of the access device. It can effectively solve the problem of dual-system web data interaction on the terminal device, make the dual-system data interaction smoother, and enhance the user experience.

[0073] In combination with the above embodiment, in one embodiment, the method further includes the following steps:

[0074] S107: The LAN side device sends a third page request to the Linux service, where the third page request is used to request a page of the Linux system;

[0075] S108: The Linux service responds to the third page request and obtains the corresponding second page data result;

[0076] S109: The Linux service feeds back the second page data result to the LAN side device.

[0077] For steps S107-S109, when the LAN side device sends a third page request to the Linux service, and the third page request is used to request a page of the Linux system, the Linux service will directly respond to the third page request, obtain the corresponding second page data result, and feed the second page data result back to the LAN side device. Different from the previous embodiment, in this embodiment, when the LAN side device accesses the Linux system, the Linux service responds directly, which is more efficient.

[0078] It should be noted that the above is an example of an access device being a LAN side device, with the Linux system being the master system and the RTOS system being the slave system. When the access device is a WAN side device, the above implementation logic can also be used, and there is no limitation here.

[0079] In one embodiment, another processing logic is provided, such as Figure 3 As shown, based on the above terminal device, a page access method is also provided, taking the access device as a WAN side device and the terminal device as a router as an example, comprising the following steps:

[0080] S201: The WAN side device sends a fourth page request to the RTOS service, where the fourth page request is used to request a page of the Linux system;

[0081] In this embodiment, when the WAN side device needs to access the Linux system page, the WAN side device will send a fourth page request to the RTOS service of the router, and the fourth page request is used to request access to the Linux system page. For example, the WAN side device sends the following fourth page request to the RTOS service: 192.***.201.60 / WlanBasic.html, that is, the page resource requested by the request is WlanBasic.html.

[0082] S202: When the RTOS service responds to the fourth page request, it sends a second redirection feedback to the WAN side device;

[0083] After receiving the fourth page request, the RTOS service will send a second redirection feedback (Redirect to 192.***.201.60:8083) to the WAN side device. The second redirection feedback will carry the service port 8083 of the RTOS service to allow the WAN side device to resend the request to the RTOS agent.

[0084] S203: The WAN side device responds to the second redirection feedback and sends a fifth page request to the RTOS agent, where the fifth page request is used to request a page of the Linux system;

[0085] After the WAN side device receives the second redirection feedback (Redirect to 192.***.201.60:8083), the WAN side device will respond to the second redirection feedback and send the fifth page request (192.***.201.60 / WlanBasic.html) to the RTOS agent, wherein the fifth page request carries the service port 8083 of the RTOS agent, and the fifth page request is used to request the WlanBasic.html page of the Linux system.

[0086] S204: The RTOS agent forwards the fifth page request to the Linux service via the first IP address;

[0087] After receiving the fifth page request, the RTOS agent forwards the fifth page request to the Linux service via an IP address (172.**.255.**), which is used to request the WlanBasic.html page from the Linux service.

[0088] S205: The Linux service responds to the fifth page request, obtains the corresponding third page data result, and feeds the third page data result back to the RTOS agent through the second IP address;

[0089] After receiving the fifth page request, the Linux service will obtain the third page data result corresponding to the fifth page request, that is, it will obtain the page data result corresponding to the WlanBasic.html page, and then feed back the third page data result to the RTOS agent through the second IP address (172.**.255.**) of the RTOS agent, that is, feed back the page data result corresponding to the WlanBasic.html page to the RTOS agent.

[0090] S206: The RTOS agent feeds back the third page data result to the WAN side device.

[0091] After the RTOS agent obtains the third page data result, it feeds the third page data result back to the WAN side device through the service port 8083, that is, the page data result corresponding to the WlanBasic.html page. At this point, the WAN side device requests the page data to complete the dual-system interactive communication, and the user obtains the page of the RTOS system to be accessed through the WAN side device.

[0092] It should be noted that the embodiment of the present application provides a new page access method based on the above-mentioned terminal device. It does not require the two http services of the two systems to provide corresponding IP addresses for the access devices to access respectively. Instead, it converts the interaction of the two systems to realize the access of the access device. It can effectively solve the problem of dual-system web data interaction on the terminal device, make the dual-system data interaction smoother, and enhance the user experience.

[0093] In combination with the above embodiment, in one embodiment, the method further includes the following steps:

[0094] S207: The WAN side device sends a sixth page request to the RTOS service, where the sixth page request is used to request a page of the RTOS system;

[0095] S208: The RTOS service responds to the sixth page request and obtains the corresponding fourth page data result;

[0096] S209: The RTOS service feeds back the fourth page data result to the WAN side device.

[0097] For steps S207-S209, when the WAN side device sends the sixth page request to the RTOS service, the sixth page request is used to request the page of the RTOS system, then the RTOS service will directly respond to the sixth page request, obtain the corresponding fourth page data result, and feed the fourth page data result back to the WAN side device. Different from the previous embodiment, in this embodiment, when the WAN side device accesses the RTOS system, the RTOS service responds directly, which is more efficient.

[0098] It should be noted that the above is an example of an access device being a WAN side device, with the Linux system being the master system and the RTOS system being the slave system. When the access device is a LAN side device, the above implementation logic can also be used, and there is no limitation here.

[0099] In one embodiment, a computer device is provided. The computer device may be the above-mentioned terminal device. The terminal device may be a network communication device including a router, and its internal structure diagram may be as shown in FIG. Figure 4 As shown. The terminal device includes a processor, a memory, and a network interface connected through a system bus. Among them, the processor of the terminal device is used to provide computing and control capabilities. The memory of the terminal device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores a Linux system, an RTOS system, and a computer program. The internal memory provides an environment for the operation of the Linux system, the RTOS system, and the computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external access device through a network connection. When the computer program is executed by the processor, the functions or steps of the above-mentioned terminal device are realized.

[0100] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the functions or steps on the terminal device side in the above method embodiment or device embodiment are implemented. For details, please refer to the above embodiments, and the description is not repeated here.

[0101] Those of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application may include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0102] Those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example. In actual applications, the above-mentioned functions can be distributed and completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above.

[0103] The embodiments described above are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, a person skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. A page access method based on a terminal device, characterized in that: The terminal device includes a Linux system and an RTOS system, an internal thread channel ITC is established between the Linux system and the RTOS system, wherein the Linux system is allocated a first IP address for communication in the internal thread channel ITC, the RTOS system is allocated a second IP address for communication in the internal thread channel ITC, the Linux system is used to access the RTOS system through the second IP address, the RTOS system is used to access the Linux system through the first IP address, the Linux system runs a Linux service and a Linux agent, and the RTOS system runs an RTOS service, and the method includes: The access device sends a first page request to the Linux service, where the first page request is used to request a page of the RTOS system; The Linux service responds to the first page request and sends a first redirection feedback to the access device; The access device sends a second page request to the Linux agent in response to the first redirection feedback, where the second page request is used to request a page of the RTOS system; The Linux agent forwards the second page request to the RTOS service via the second IP address; The RTOS service responds to the second page request and obtains the corresponding first page data result; The RTOS service feeds the first page data result back to the Linux agent via the first IP address; The Linux agent feeds back the first page data result to the access device.

2. The page access method according to claim 1, characterized in that: The method further comprises: The access device sends a third page request to the Linux service, where the third page request is used to request a page of the Linux system; The Linux service responds to the third page request and obtains the corresponding second page data result; The Linux service feeds the second page data result back to the access device.

3. The page access method according to claim 1, characterized in that: The Linux system is the master system, and the RTOS system is the slave system.

4. The page access method according to claim 1, characterized in that: The non-volatile memory of the terminal device is shared between the Linux system and the RTOS system.

5. The page access method according to claim 1, wherein: The RTOS system is used to send a write command corresponding to the write operation to the Linux system when a write operation is performed on the non-volatile memory of the terminal device; The Linux system is used to respond to the write command and perform the write operation.

6. A page access method based on a terminal device, characterized in that: The terminal device comprises a Linux system and an RTOS system, an internal thread channel ITC is established between the Linux system and the RTOS system, wherein the Linux system is allocated a first IP address for communicating in the internal thread channel ITC, the RTOS system is allocated a second IP address for communicating in the internal thread channel ITC, the Linux system is used to access the RTOS system through the second IP address, the RTOS system is used to access the Linux system through the first IP address, the Linux system runs a Linux service, the RTOS system runs an RTOS service and an RTOS agent, and the method comprises: The access device sends a fourth page request to the RTOS service, where the fourth page request is used to request a page of the Linux system; When the RTOS service responds to the fourth page request, sending a second redirection feedback to the access device; The access device sends a fifth page request to the RTOS agent in response to the second redirection feedback, wherein the fifth page request is used to request a page of the Linux system; The RTOS agent forwards the fifth page request to the Linux service via the first IP address; The Linux service responds to the fifth page request and obtains the corresponding third page data result; The Linux service feeds back the third page data result to the RTOS agent via the second IP address; The RTOS agent feeds back the third page data result to the access device.

7. The page access method according to claim 6, characterized in that: The method further comprises: The access device sends a sixth page request to the RTOS service, wherein the sixth page request is used to request a page of the RTOS system; The RTOS service responds to the sixth page request and obtains the corresponding fourth page data result; The RTOS service feeds the fourth page data result back to the access device.

8. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the page access method according to any one of claims 1 to 5 or any one of claims 6 to 7 are implemented.

Images