Optical fiber networking access method, communication device, storage medium and program product

Abstract

The invention discloses an optical fiber networking access method, communication equipment, a storage medium and a program product. The method comprises the following steps: a cloud platform determines a target access mode corresponding to a network environment in response to the detected network environment of terminal equipment; wherein the target access mode is a near-end access mode, a far-end direct connection access mode or a far-end relay access mode; and sending the target access mode to gateway storage equipment and terminal equipment in the optical fiber network, so that the gateway storage equipment communicates with the terminal equipment in the target access mode. The access reliability of the optical fiber networking can be improved.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to an access method, communication device, storage medium and program product for optical fiber networking. Background Technology

[0002] With the widespread adoption of gigabit broadband, Fiber to the Room (FTTR) networking technology has been widely used due to its advantages of full coverage and high stability, while Network Attached Storage (NAS) devices have become the core devices for centralized data management in home and office scenarios.

[0003] However, in traditional solutions, FTTR networks and NAS devices are usually deployed and operated as two independent systems. This separate architecture is prone to causing intranet communication barriers and transmission bottlenecks, making it difficult to fully utilize the high bandwidth potential of FTTR and the large-capacity storage advantages of NAS, thus restricting the access reliability of fiber optic networks. Summary of the Invention

[0004] This application provides an access method, communication device, storage medium, and program product for fiber optic networks, aiming to improve the access reliability of fiber optic networks.

[0005] In a first aspect, embodiments of this application provide an access method for fiber optic networks, applied to a cloud platform, comprising: in response to detecting the network environment of a terminal device, determining a target access mode corresponding to the network environment; wherein the target access mode is a near-end access mode, a far-end direct connection access mode, or a far-end relay access mode; and sending the target access mode to a gateway storage device and a terminal device in the fiber optic network, so that the gateway storage device communicates with the terminal device using the target access mode.

[0006] Secondly, embodiments of this application provide an access method for fiber optic networks, applied to a gateway storage device in a fiber optic network, comprising: receiving a target access mode sent by a cloud platform, wherein the target access mode is determined by the cloud platform based on the network environment of the detected terminal device, and the target access mode is a near-end access mode, a far-end direct connection access mode, or a far-end relay access mode; and communicating with the terminal device using the target access mode.

[0007] Thirdly, embodiments of this application provide a communication device, including: at least one processor; at least one memory for storing at least one program; and when at least one of the programs is executed by at least one of the processors, implementing the fiber optic network access method as described in the first, second, or third aspects.

[0008] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions for performing the fiber optic network access method as described in the first or second aspect.

[0009] Fifthly, embodiments of this application provide a computer program product, including a computer program or computer instructions, which are stored in a computer-readable storage medium. A processor of a communication device reads the computer program or computer instructions from the computer-readable storage medium and executes the computer program or computer instructions, causing the communication device to perform the fiber optic network access method as described in the first or second aspect.

[0010] In this embodiment, on the one hand, an integrated data storage device—a gateway storage device—deeply integrating FTTR and NAS is constructed to solve the intranet interconnection obstacles and transmission bottlenecks caused by the separation of FTTR and NAS. On the other hand, intelligent collaboration of three access modes—near-end, remote direct connection, and remote relay—is designed. The cloud platform can continuously detect the network environment of the terminal devices to realize intelligent selection and dynamic switching of access modes between the terminal devices and the gateway storage device, ensuring transmission efficiency and success rate. Thus, the access reliability of the fiber optic network can be significantly improved. Attached Figure Description

[0011] The accompanying drawings are used to provide a further understanding of the technical solutions of this application and constitute a part of the specification. They are used together with the embodiments of this application to explain the technical solutions of this application and do not constitute a limitation on the technical solutions of this application.

[0012] Figure 1 This is a schematic diagram illustrating the integration of an FTTR router and a NAS device according to an embodiment of this application;

[0013] Figure 2 This is one of the schematic diagrams of the FTTR+NAS integrated data storage system provided in the embodiments of this application; Figure 3 This is the second schematic diagram of the FTTR+NAS integrated data storage system provided in the embodiments of this application; Figure 4 This is one of the flowcharts illustrating the access method for fiber optic networking provided in the embodiments of this application; Figure 5 This is a second schematic flowchart of the access method for fiber optic networking provided in the embodiments of this application; Figure 6 This is the third schematic diagram of the FTTR+NAS integrated data storage system provided in the embodiments of this application; Figure 7 This is a schematic diagram of the near-end access process provided in an embodiment of this application; Figure 8 This is a schematic diagram of the remote P2P access process provided in the embodiments of this application; Figure 9 This is a schematic diagram of the remote relay access process provided in the embodiments of this application; Figure 10 This is a schematic diagram of the architecture of the intelligent routing strategy provided in the embodiments of this application; Figure 11 This is one of the schematic diagrams of virtual machine deployment provided in the embodiments of this application; Figure 12 This is the second schematic diagram of virtual machine deployment provided in the embodiments of this application; Figure 13 This is the third schematic diagram of virtual machine deployment provided in the embodiments of this application; Figure 14 This is a schematic diagram of the structure of the communication device provided in the embodiments of this application. Detailed Implementation

[0014] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0015] It should be understood that in the description of the embodiments of this application, the use of terms such as "first" and "second" is only for the purpose of distinguishing technical features and should not be construed as indicating or implying relative importance, or implicitly indicating the number of technical features indicated, or implicitly indicating the order of the technical features indicated. "At least one" refers to one or more, and "more" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent the existence of A alone, the simultaneous existence of A and B, or the existence of B alone. A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" and similar expressions refer to any group of these items, including any group of singular or plural items. For example, at least one of a, b, and c can represent: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, and c can be single or multiple.

[0016] To facilitate understanding of the solutions in the embodiments of this application, some contents involved in the embodiments of this application are described below: This application provides an integrated FTTR+NAS data storage solution that deeply integrates FTTR and NAS to create an integrated FTTR+NAS data storage device. In this application, the integrated FTTR+NAS data storage device can be called a gateway storage device or an FTTR-NAS device, but this does not limit its naming. This solution resolves the intranet communication barriers and transmission bottlenecks caused by the separation of FTTR and NAS, thereby improving the access reliability of fiber optic networks.

[0017] In this embodiment, the gateway storage device can be a gateway device with integrated NAS storage functionality.

[0018] This application does not limit the way a gateway device integrates NAS storage functionality. In some embodiments, the gateway device can integrate NAS storage functionality through a built-in hard drive, an external disk array, or a standalone NAS device (also referred to as a NAS storage disk, NAS drive, NAS storage unit, or storage stick). In other words, the gateway storage device can directly integrate a NAS device, or connect to an external NAS device through a dedicated interface to form an integrated FTTR+NAS data storage system.

[0019] This application does not limit the specific form of the gateway device. In some embodiments, the gateway device may be, but is not limited to, any of the following: a router, a central office access device, a transmission network device, or a user-side terminal device. Further, the central office access device may include, but is not limited to, an optical line terminal (OLT), the transmission network device may include, but is not limited to, an optical transport network (OTN), wavelength division multiplexing (WDM), etc., and the user-side terminal device may include, but is not limited to, an optical network unit (ONU), a gateway, etc.

[0020] In some embodiments, the fiber optic network of FTTR can adopt a master-slave optical gateway networking architecture, including an FTTR master gateway device (hereinafter referred to as the FTTR master device) and an FTTR slave gateway device (hereinafter referred to as the FTTR slave device). The FTTR master gateway device, as the core network node, can be equipped with a high-performance processor, large-capacity memory, and built-in hard drive or external storage interface, directly integrating NAS storage functionality or connecting to an external NAS device through a dedicated interface. The FTTR slave gateway devices provide fiber optic interfaces and Ethernet interfaces, distributed in different rooms, and interconnected with the FTTR master gateway device via fiber optic cables to form a fully covered high-speed internal network. Furthermore, the fiber optic network can support gigabit and higher access bandwidths. Internally, Gigabit-Capable Passive Optical Network (GPON) or the more advanced 10-Gigabit-Capable Passive Optical Network (XG-PON) technology can be used to achieve high-speed data transmission between master and slave devices, accessing the FTTR network via Wi-Fi 6 / 7 or wired connections, improving internal network transmission efficiency.

[0021] In some embodiments, FTTR routers can be deeply integrated with NAS technology. For example... Figure 1 As shown, a high-speed data storage system for home and enterprise can be built by plugging NAS devices into an FTTR master-slave router.

[0022] This application provides an FTTR+NAS integrated data storage system. The system adopts a layered architecture design and can be composed of three main layers: the client access layer (also known as the application service layer), the cloud platform layer, and the device access layer.

[0023] The client access layer can be viewed as a client (also known as an APP), including at least one terminal device (also known as a user device). The terminal device can be, but is not limited to, smartphones, tablets, personal computers (PCs), and smart TVs. Furthermore, the terminal device can access the system through any of the following: an APP, or a cloud platform's web management interface; the APP can be, but is not limited to, operator-customized APPs or self-developed APPs. In this embodiment, the terminal device can remotely access the gateway storage device via a mobile network or external Wi-Fi, or access the gateway storage device via a local area network (LAN) through internal Wi-Fi and wired connections within the FTTR network.

[0024] The device access layer can be viewed as the NAS device side, including at least one gateway storage device.

[0025] The cloud platform layer can be viewed as the server side, i.e., the cloud, including the cloud platform (which can also be a NAS management platform or a cloud platform).

[0026] In addition, the FTTR+NAS integrated data storage system may also include a transport layer. This transport layer is not an independent logical layer, but rather a horizontal support layer that runs through all layers of the entire system. As the core of this horizontal support, the transport layer connects to application services above and schedules network and storage resources below. It is not an independent layer, but rather empowers the entire system with capabilities such as intelligent routing, protocol conversion, and load balancing, enabling the perception and linkage of network topology and storage services.

[0027] The FTTR+NAS integrated data storage system of this application embodiment allows the cloud to communicate with both the APP and the NAS device. The cloud can remotely manage the NAS device, store photos, videos, and other files from the client on the NAS device, and enable secure sharing and access between terminal devices.

[0028] In some embodiments, such as Figure 2 As shown, the FTTR+NAS integrated data storage system can consist of an APP, a cloud platform, and FTTR-NAS devices.

[0029] In some embodiments, an integrated FTTR+NAS data storage system for home users can be as follows: Figure 3 As shown, its core is to remotely manage multiple local storage devices in a home through a NAS management platform. It mainly serves home users and can store files such as photos and videos on local storage sticks, enabling secure sharing and remote access among all family members. It also supports dual backups, both local and cloud, to prevent data loss.

[0030] In this application embodiment, the network environment mainly relies on FTTR all-optical indoor network and Internet access and public network capabilities. The former serves as the system's "highway," providing a gigabit or even 10-gigabit intranet environment with seamless coverage throughout the house. The main optical modem (or SDN controller) and the slave optical modem can be networked through fiber optics to ensure that the devices connected to the NAS (such as PCs and mobile phones) and the NAS itself are in the same high-performance local area network, providing a high-speed transmission channel of over 100MB / s for near-end access. The latter serves as the "bridge" for remote access, and the upload bandwidth directly affects the remote access speed.

[0031] The embodiments of this application may be applicable to, but are not limited to, the following application scenarios: First, it serves as a smart home hub, acting as the digital foundation of the family and providing a unified, massive data storage center for all family members. Each member has an independent private space, while also supporting "one-click sharing" of resources such as photos and videos, enabling data flow across devices.

[0032] Secondly, it serves as a lightweight private cloud drive for small and micro enterprises and SOHO offices, enabling team members to remotely and securely access internal company data and ensuring business data security through a local / cloud dual backup mechanism.

[0033] Thirdly, it caters to multimedia creators and enthusiasts, meeting their storage needs for large-capacity materials such as 4K / 8K high-definition videos and large design files, and enabling high-speed editing and rendering via the gigabit intranet provided by FTTR, while also supporting remote direct transmission of materials.

[0034] Fourth, remote work and mobile access: Users can access all files on their home or office NAS at high speed and with security, just like they would locally, from anywhere with internet access, completely breaking geographical limitations.

[0035] The access method for fiber optic networking provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0036] See Figure 4 , Figure 4 This is one of the flowcharts illustrating the access method for fiber optic networking provided in the embodiments of this application. Figure 4 The fiber optic network access method shown can be applied to a cloud platform, for example, such as... Figure 2 In the specific implementation of the cloud platform shown, this method can be executed by the cloud platform itself, or by components of the cloud platform, such as the cloud platform's processor, chip, or chip system, or by logic modules or software that implement all or part of the cloud platform's functions.

[0037] like Figure 4 As shown, the access method for fiber optic networks applied to cloud platforms includes, but is not limited to, the following steps: Step 401: In response to detecting the network environment of the terminal device, determine the target access mode corresponding to the network environment; wherein, the target access mode is a near-end access mode, a remote direct connection access mode, or a remote relay access mode.

[0038] In the embodiments of this application, multiple access modes (also known as access architectures) can be designed for the FTTR+NAS integrated data storage system, including, but not limited to, near-end access mode, remote direct connection access mode, and remote relay access mode. This enriches the access methods of the FTTR+NAS integrated data storage system, thereby improving the access reliability of fiber optic networks.

[0039] The near-end access mode can be implemented through a near-end LAN. Specifically, the terminal device can access the gateway storage device through a fiber optic LAN (also known as an intranet or private network).

[0040] Remote direct access mode and remote relay access mode can be implemented via the remote Internet. Specifically, terminal devices can access the gateway storage device remotely via the Internet (also known as the public network) through either direct or remote relay access. For remote direct access, the terminal device can directly access the gateway storage device; for remote relay access, the terminal device can access the gateway storage device through the relay server on the cloud platform.

[0041] In this embodiment, the access mode between the terminal device and the gateway storage device can be intelligently selected and dynamically switched by the cloud platform. Specifically, the cloud platform can continuously detect the network environment of the terminal device to intelligently select and dynamically switch the access mode between the terminal device and the gateway storage device. In other words, in this embodiment, as the network environment of the terminal device changes, its access mode with the gateway storage device can also change accordingly, thereby achieving a smooth transition between different modes. This ensures transmission efficiency and success rate without the user's awareness, thus improving the access reliability of fiber optic networks.

[0042] The network environment of a terminal device can be either located within a fiber optic local area network (LAN) or located outside of a fiber optic LAN. In the former case, the terminal device is connected to the LAN; in the latter case, the terminal device is connected to the Internet.

[0043] Step 402: Send the target access mode to the gateway storage device and terminal device in the fiber optic network, so that the gateway storage device can communicate with the terminal device using the target access mode.

[0044] After determining the target access mode corresponding to the network environment, the cloud platform can send the target access mode to the terminal device and the gateway storage device, so that the terminal device and the gateway storage device can communicate using the target access mode. In other words, the gateway storage device and the communication device can communicate using the target access mode. This allows the access mode between the terminal device and the gateway storage device to be adapted to the network environment of the terminal device, thereby ensuring transmission efficiency and success rate, and improving the access reliability of fiber optic networking.

[0045] The fiber optic network access method in this application embodiment, on the one hand, constructs an integrated data storage device—a gateway storage device—that deeply integrates FTTR and NAS, thereby solving the intranet interconnection obstacles and transmission bottlenecks caused by the separation of FTTR and NAS; on the other hand, it designs intelligent coordination of three access modes: near-end, far-end direct connection, and far-end relay. The cloud platform can continuously detect the network environment of the terminal devices to realize intelligent selection and dynamic switching of access modes between the terminal devices and the gateway storage device, ensuring transmission efficiency and success rate. Thus, the access reliability of the fiber optic network can be significantly improved.

[0046] The following provides a detailed explanation of how the target access mode is determined.

[0047] In some embodiments, in response to detecting the network environment of the terminal device, determining the target access mode corresponding to the network environment may include any of the following: In response to the network environment where the terminal device is located in a fiber optic local area network, the target access mode is determined to be the near-end access mode. In response to the network environment where the terminal device is located outside the local area network of the fiber optic network, the target access mode is determined to be either remote direct access mode or remote relay access mode.

[0048] In practice, if a terminal device is detected to be connected to the local area network (LAN), it is determined to be the near end, and the near-end access mode is selected as the access mode between the terminal device and the gateway storage device. If a terminal device is detected not to be connected to the LAN, it is determined to be the far end, and either the far-end direct access mode or the far-end relay access mode is selected as the access mode between the terminal device and the gateway storage device. In other words, when the terminal device and the NAS device are on the same LAN, it intelligently switches to the near-end access mode; when the terminal device is on the internet and not on the same LAN as the NAS device, it intelligently switches to the remote access mode.

[0049] This allows the access mode between the terminal device and the gateway storage device to be adapted to the network environment of the terminal device, thereby ensuring transmission efficiency and success rate, and thus improving the access reliability of the fiber optic network.

[0050] In cases where the terminal device is located outside the local area network, in some embodiments, an access mode can be randomly selected from the remote direct access mode and the remote relay access mode as the access mode between the terminal device and the gateway storage device.

[0051] In other embodiments, in response to the network environment being that the terminal device is located outside the local area network of the fiber optic network, determining the target access mode as a remote direct access mode or a remote relay access mode may include: In response to the network environment where the terminal device is located outside the local area network of the fiber optic network, the target access mode is determined to be the remote direct connection access mode. If the establishment of the direct data transmission channel in the remote direct access mode fails or the service quality of the direct data transmission channel is lower than the preset quality threshold, the target access mode is updated to the remote relay access mode.

[0052] In these embodiments, if the terminal device is detected to be outside the local area network, considering that the transmission efficiency of remote direct access is higher than that of remote relay access, the remote direct access mode can be preferentially selected as the access mode between the terminal device and the gateway storage device; when the access using the remote direct access mode fails, the system switches to the remote relay access mode. In this way, transmission efficiency can be maximized.

[0053] In practice, access failure using the remote direct connection mode can manifest in, but is not limited to, the failure to establish the direct data transmission channel or the service quality of the direct data transmission channel falling below a preset quality threshold. In other words, if the direct data transmission channel in the remote direct connection mode fails to establish, or if the service quality of the direct data transmission channel is poor, the cloud platform can seamlessly switch the access mode between the terminal device and the gateway storage device to the remote relay access mode to improve the access reliability of the fiber optic network.

[0054] The following provides a detailed explanation of each access mode.

[0055] In this embodiment, the access service type of the fiber optic network may include at least one of the following: signaling transmission and file transmission. Signaling transmission refers to small data transmission, and may include, but is not limited to, signaling transmission and file access (i.e., browsing). File transmission refers to large data transmission, and may include, but is not limited to, file transmission. The size of the data can be characterized by a preset data threshold. Specifically, if the size of the data is less than or equal to the preset data threshold, it can be considered small data; otherwise, it can be considered large data.

[0056] In practice, to ensure the reliability, efficiency and security of transmission, signaling transmission and file transmission can be implemented through independent transmission channels. Specifically, signaling transmission can be implemented through a signaling transmission channel, and file transmission can be implemented through a data transmission channel.

[0057] In some embodiments, in the near-end access mode, the terminal device can transfer files with the gateway storage device through the near-end data transmission channel and can transmit signaling with the gateway storage device through the near-end signaling transmission channel; Among them, the near-end data transmission channel uses the first communication protocol for file transfer. The first communication protocol is a computer network communication protocol with network data transmission and storage resource sharing functions. The near-end signaling transmission channel uses a second communication protocol for signaling transmission. The second communication protocol is a transport layer communication protocol used for end-to-end data packet transmission in the network.

[0058] In these embodiments, the near-end LAN can perform file transfer via a near-end data transmission channel using a computer network communication protocol (referred to as the first communication protocol) that enables network data transmission and storage resource sharing; and can perform signaling transmission via a near-end signaling transmission channel using a transport layer communication protocol (referred to as the second communication protocol) for end-to-end data packet transmission. This ensures the reliability, efficiency, and security of the near-end LAN's transmission, thereby improving the access reliability of the fiber optic network.

[0059] In some embodiments, in remote direct access mode and remote relay access mode, the terminal device can share the same remote signaling transmission channel to transmit signaling with the gateway storage device; in remote direct access mode, the terminal device can transfer files with the gateway storage device through the direct data transmission channel; in remote relay access mode, the terminal device can transfer files with the gateway storage device through the relay data transmission channel. Among them, the remote signaling transmission channel uses a third communication protocol for signaling transmission, which is the distributed system signaling interaction and message transmission protocol; The direct data transmission channel uses the fourth communication protocol for file transfer. The fourth communication protocol is a secure data interaction and resource sharing protocol based on a distributed node architecture. The relay data transmission channel uses the fifth communication protocol for file transfer. The fifth communication protocol is an application layer bidirectional low-latency communication protocol.

[0060] In these embodiments, the remote Internet supports a dual-mode switching mechanism for remote direct connection transmission and remote relay transmission. Remote direct connection transmission and remote relay transmission can use the same remote signaling transmission channel, employing a distributed system signaling interaction and message transmission protocol (referred to as the third communication protocol) for signaling transmission, simplifying system complexity. For file transfer, it can be implemented through independent data transmission channels. Specifically, remote direct connection transmission can use a direct data transmission channel, employing a secure data interaction and resource sharing protocol based on a distributed node architecture (referred to as the fourth communication protocol) for file transfer; remote relay transmission can use a relay data transmission channel, employing an application-layer bidirectional low-latency communication protocol (referred to as the fifth communication protocol) for file transfer. This ensures the reliability, efficiency, and security of remote Internet transmission, thereby improving the access reliability of fiber optic networks.

[0061] The embodiments of this application do not limit the specific form of the above communication protocol, so as to enrich the communication methods of near-end local area networks and remote Internet.

[0062] In some embodiments, the first communication protocol may be, but is not limited to, any of the following: Server Message Block (SMB), Network File System (NFS), File Transfer Protocol (FTP), Secure File Transfer Protocol (SFTP), Web-based Distributed Authoring and Versioning (WebDAV), Remote Sync Protocol (rsync), and Internet Small Computer System Interface (iSCSI).

[0063] In some embodiments, the second communication protocol may be, but is not limited to, any of the following: Transmission Control Protocol (TCP), User Datagram Protocol (UDP), Quick UDP Internet Connections (QUIC), or Stream Control Transmission Protocol (SCTP).

[0064] In some embodiments, the third communication protocol may be, but is not limited to, any of the following: Message Queuing Telemetry Transport (MQTT), MQTT for Sensor Networks (MQTT-SN), Session Initiation Protocol (SIP), Google Remote Procedure Calls (gRPC, which may be based on HTTP / 2), Data Distribution Service (DDS), Simple Text Oriented Messaging Protocol (STOMP), Web Transport (which may be based on HTTP / 3 / QUIC), HyperText Transfer Protocol (HTTP) / 1.1 / 2 / 3 (which may include RESTful APIs), Advanced Message Queuing Protocol (AMQP), Extensible Messaging and Presence Protocol (XMPP), and Constrained Application Protocol (CoAP).

[0065] In some embodiments, the fourth communication protocol may be, but is not limited to, any of the following: Peer-to-Peer (P2P) network protocol, Web Real-Time Communication Data Channel (WebRTC Data Channel, ICE framework (including STUN / TURN) + SRTP / DTLS encryption + SCTP data channel), SSH / SFTP over SSH Tunnel (SSH protocol establishes an encrypted tunnel, utilizes its TCP forwarding function to achieve NAT traversal and port mapping, and runs SFTP for file transfer within the tunnel), STUN+QUIC / DTLS (STUN server performs address discovery + QUIC or DTLS protocol establishes an encrypted connection and transmits data), Syncthing (BlockExchange Protocol, uses relay servers and global discovery servers to coordinate connections, uses TLS encryption, and uses a dedicated protocol for block synchronization), InterPlanetary File System (IPFS, content-addressed distributed network), Freenet, and RetroShare (Friend-to-Friend network).

[0066] In some embodiments, the fifth communication protocol may be, but is not limited to, any of the following: WebSocket, WebTransport (low latency, bidirectional communication, multiplexed multiple streams on a single connection), or Web Real-Time Communication Data Channel (WebRTCDataChannel, based on UDP, using ICE / STUN / TURN to achieve NAT traversal, and supporting end-to-end encryption).

[0067] In one example, the first communication protocol can be SMB, the second can be TCP, the third can be MQTT, the fourth can be P2P, and the fifth can be WebSocket. In this example, the three access modes can be represented as local SMB, remote P2P direct connection, and remote relay, respectively. The local LAN uses the SMB protocol for file transfer and TCP for file access and related signaling interaction. The remote internet supports a dual-mode switching mechanism between P2P direct connection and relay transmission, both using MQTT messages for file access and related signaling interaction. The P2P direct connection mode uses a P2P connection for point-to-point file transfer. When relay mode is active, the WebSocket protocol ensures the reliability of file data transmission.

[0068] In some embodiments, the signaling structure of each access mode can remain consistent. In these embodiments, the signaling structure of near-end signaling and far-end signaling can be consistent. In one example, whether it's near-end TCP signaling or far-end MQTT signaling, the data structure of the instructions such as "request file list" or "download a file block" carried is completely identical. This eliminates the need for upper-layer applications to write two sets of processing logic for different access modes, simplifying protocol processing complexity.

[0069] In some embodiments, the direct data transmission channel in the remote direct access mode can be: an end-to-end encrypted direct channel established based on the target encryption protocol by the target server of the cloud platform performing Network Address Translation (NAT) traversal based on the sixth communication protocol; wherein, the sixth communication protocol is the Network Address Discovery and NAT Traversal Protocol.

[0070] In these embodiments, the remote direct access mode can achieve NAT traversal through the target server of the cloud platform and establish an end-to-end encrypted channel for peer-to-peer file transfer, thereby improving the reliability of remote direct access.

[0071] In specific implementations, the target server can perform NAT traversal based on a network address discovery and NAT traversal protocol (referred to as the sixth communication protocol). In some embodiments, the sixth communication protocol can be, but is not limited to, any of the following: Session Traversal Utilities for NAT (STUN), Interactive Connectivity Establishment (ICE, which includes STUN), or Traversal Using Relaysaround NAT (TURN, a relay address discovery and traversal protocol). In some embodiments, the NAT traversal type can be full cone NAT traversal. It is understood that the target server's behavior matches the behavior of the sixth communication protocol; for example, if the sixth communication protocol is the STUN protocol, the target server can behave as a STUN server.

[0072] This application does not limit the target encryption protocol used for the encrypted direct connection channel. In some embodiments, the target encryption protocol may be, but is not limited to, the WebSocket Secure (WSS) protocol.

[0073] In one example, full cone NAT traversal can be achieved based on the STUN protocol, establishing an end-to-end encrypted direct connection channel to achieve efficient P2P traversal.

[0074] In one example, remote P2P direct connection can achieve high-performance transmission of 22-34 MB / s by using the STUN protocol for NAT traversal, obtaining the device's public IP address, and then establishing an end-to-end encrypted WSS direct connection channel. If the ISP allocates a public IP address, the success rate and quality of the P2P direct connection will be greatly improved. If no public IP address is available, NAT traversal and relay forwarding can be achieved through the STUN / TURN service.

[0075] In some embodiments, the relay data transmission channel of the remote relay access mode can be established based on the relay server of the cloud platform. The relay server can satisfy any of the following: the relay server provides external services through the floating address of the virtual machine to which the cloud platform belongs; or the relay server provides external services through an independently configured public network address.

[0076] In these embodiments, the relay service of the relay server can be implemented in the following ways: Method 1: Relay services can be proxied through virtual machines belonging to the cloud platform, meaning that the relay server can provide services to the outside world through this virtual machine; Method 2: Relay services can bypass the virtual machine proxy of the cloud platform and can directly access the service through an independently configured public IP address.

[0077] For Method 1, the implementation method of the relay server's relay service can be further determined based on the deployment method of the virtual machines belonging to the cloud platform. Specifically, if the virtual machine belonging to the cloud platform and another virtual machine are deployed in a dual-machine master-slave mode, the relay server can provide services externally through a floating address (floating IP) shared by these two virtual machines. In practice, this floating IP can be mapped to a public IP address (public IP) to provide services externally. If the virtual machine belonging to the cloud platform is deployed as a single machine, the relay server provides services externally through the public IP address opened by this virtual machine.

[0078] This can enrich the ways in which relay servers can implement relay services, thereby expanding the access methods of fiber optic networks and meeting the requirements of different operators.

[0079] In some embodiments of this application, unified storage resource management can be provided for each gateway storage device in the optical fiber network, as detailed below.

[0080] In some embodiments, the method may further include at least one of the following: Create a unified namespace corresponding to the fiber optic network. The unified namespace corresponds to the storage resources of each gateway storage device in the fiber optic network and is used for the unified management of the storage resources of each gateway storage device. A load balancing and failover mechanism is used to manage the storage resources of each gateway storage device. The load balancing and failover mechanism supports allocating data storage locations and data access paths for terminal devices based on the storage capacity, current load, and device status of each gateway storage device.

[0081] In these embodiments, the cloud platform can aggregate the storage resources of each gateway storage device in the fiber optic network into a unified logical storage pool by creating a unified namespace corresponding to the storage resources of each gateway storage device in the fiber optic network, and provide a unified access entry point. In this way, terminal devices can access the storage resources of each gateway storage device in the fiber optic network based on the global data access path of the unified namespace, thereby improving access efficiency.

[0082] The cloud platform can also employ load balancing and failover mechanisms to manage the storage resources of each gateway storage device. Specifically, these mechanisms can intelligently allocate data storage locations and access paths for terminal devices based on their storage capacity, current load, and device status, thereby improving the overall system capacity, performance, and reliability. As the number of users increases, the system can dynamically allocate storage resources, avoiding single-point bottlenecks and achieving linear scalability.

[0083] For example, when a terminal device stores a file based on the global data access path of a unified namespace, it can first find the working gateway storage device based on the device status of each gateway storage device, and then calculate the corresponding remaining space based on the storage capacity and current load of these gateway storage devices, and store the file in the gateway storage device with the largest remaining space to achieve load balancing.

[0084] When a terminal device accesses a file using a global data access path within a unified namespace, a data access path can be assigned based on the device status of each gateway storage device to avoid navigating through a faulty gateway storage device, thereby improving the access success rate. Furthermore, based on the storage capacity and current load of normally functioning gateway storage devices, a gateway storage device with more remaining space can be selected to generate the data access path, reducing the impact of access on the gateway storage device and further improving the access success rate.

[0085] Furthermore, the cloud platform can create independent data spaces for each terminal device within a unified logical storage pool, achieving access control isolation. It can also set up a shared data space for all terminal devices to access. This enables cross-device data isolation and secure sharing, further enhancing the flexibility of storage resource management.

[0086] In this way, by providing unified storage resource management for the storage devices of each gateway in the fiber optic network, the overall capacity, performance and reliability of the system can be improved.

[0087] In some embodiments of this application, cloud-integrated collaboration can be provided to build an integrated data storage ecosystem of "end (NAS device) - pipe (network) - cloud (cloud)". In some embodiments, the cloud platform calls the interface provided by the Software Development Kit (SDK) to establish a data communication connection with the gateway storage device in the cloud platform; wherein, the data communication connection supports at least one of the following: issuing upload tasks from the gateway storage device, monitoring the progress of upload tasks, and pausing upload tasks.

[0088] The SDK interface is used to communicate with gateway storage devices, and therefore can also be called NAS-SDK. The SDK interface service can meet the requirements of different operators to adapt to different application scenarios.

[0089] In these embodiments, the gateway storage device can be deeply integrated with the cloud platform through the NAS-SDK to realize automatic synchronization and backup of data between the local NAS and the cloud, and build a complete "end (NAS)-pipe (network)-cloud (cloud disk)" ecosystem, thereby improving storage reliability.

[0090] In practical implementation, the gateway storage device and the cloud platform can support, but are not limited to, fine-grained control over scheduled upload task distribution, progress monitoring, and task pause. For example, the cloud platform can distribute upload tasks to the gateway storage device through the provided NAS-SDK; during the execution of the upload task, its progress can be fed back to the user in real time, and the user can also pause the upload at any time. This improves the flexibility of task uploads.

[0091] In these embodiments, by combining the high-speed transmission characteristics of fiber optic networks with the centralized management advantages of NAS storage, an end-to-end high-performance data storage solution is built, effectively meeting the diverse data storage, sharing, and backup needs of modern families and enterprises.

[0092] In this application embodiment, the cloud platform can remotely manage the gateway storage device in the fiber optic network. In some embodiments, the cloud platform can, but is not limited to, supporting the provision of at least one of the following services to the gateway storage device: identity authentication, file service, data backup, space management, storage resource aggregation, and artificial intelligence classification, so as to improve the operational reliability of the gateway storage device.

[0093] In some embodiments, the cloud platform can achieve functional decoupling through the Spring Cloud microservice architecture.

[0094] In some embodiments, the cloud platform can provide the gateway storage device with the functional services shown in Table 1.

[0095] Table 1: Functions of Gateway Storage Devices

[0096] See Figure 5 , Figure 5 This is the second flowchart illustrating the access method for fiber optic networking provided in the embodiments of this application. Figure 5 The fiber optic network access method shown can be applied to gateway storage devices, for example, such as... Figure 2 The FTTR-NAS device is shown. In specific implementations, this method can be executed by the gateway storage device, or by components of the gateway storage device, such as the gateway storage device's processor, chip, or chip system, or by logic modules or software that implement all or part of the gateway storage device's functions.

[0097] like Figure 5 As shown, the access method for fiber optic networking applied to gateway storage devices includes, but is not limited to, the following steps: Step 501: Receive the target access mode sent by the cloud platform. The target access mode is determined by the cloud platform based on the network environment of the detected terminal device. The target access mode is a near-end access mode, a remote direct connection access mode, or a remote relay access mode.

[0098] Step 502: Communicate with the terminal device using the target access mode.

[0099] In some embodiments, communicating with the terminal device using a target access mode includes: in response to the cloud platform creating a unified namespace corresponding to the fiber optic network, communicating with the terminal device using a target access mode based on the data global access path of the unified namespace; wherein, the unified namespace corresponds to the storage resources of each gateway storage device in the fiber optic network and is used for unified management of the storage resources of each gateway storage device.

[0100] In some embodiments, communicating with a terminal device using a target access mode includes: in response to receiving a transmission request for a target file from the terminal device, transmitting the target file with the terminal device in a fragmented manner.

[0101] In this embodiment, files between the terminal device and the gateway storage device can be transmitted in fragments to improve file transmission efficiency and reliability.

[0102] In some embodiments, the transmission method of the file to be transmitted can be determined based on the file size. Specifically, if the file size is larger than a preset file size, it can be transmitted in chunks; that is, the file is first divided into chunks, and then the chunks are transmitted sequentially until the transmission is complete. If the file size is smaller than or equal to the preset file size, it can be transmitted directly. This maximizes transmission efficiency.

[0103] In some embodiments, the gateway storage device is a gateway device that integrates network-attached storage (NAS) functionality. The gateway device can be any of the following: a router, a central office access device, a transmission network device, or a user-side terminal device.

[0104] It should be noted that, Figure 5 The method embodiments are examples of gateway storage devices corresponding to the above method embodiments. Therefore, the relevant descriptions in the above method embodiments can be referred to, and the same beneficial effects can be achieved. To avoid repetition, further details will not be provided here.

[0105] It is understood that the various embodiments described in this application can be combined with each other or implemented individually without conflict, and this application does not limit this.

[0106] This application relates to an integrated data storage solution that deeply integrates FTTR and NAS. Its key invention lies in the construction of three intelligent access architectures and a unified management platform, effectively solving the technical bottlenecks of traditional solutions in intranet transmission, remote access, and storage management. In a scenario where a high-speed internal network with full coverage is formed by interconnecting fiber optic cables and a main gateway, users access the FTTR network via Wi-Fi 6 / 7 or wired connections. This application includes the following embodiments: First, it features an intelligent three-access architecture, innovatively achieving intelligent coordination of three access modes: near-end SMB, remote P2P direct connection, and remote relay. Through an intelligent routing policy engine, it automatically detects the network environment, with near-end file transfers using direct SMB connections, remote file transfers prioritizing P2P direct connection transmission, and seamlessly switching to relay mode in case of failure. Near-end signaling uses a TCP signaling channel, while remote signaling uses a unified MQTT signaling channel. The design of the access signaling bodies for both is completely identical, simplifying the complexity of protocol processing.

[0107] Secondly, it features a highly efficient P2P traversal mechanism that achieves full-cone NAT traversal based on the STUN standard protocol, establishing an end-to-end encrypted direct connection channel; it completes P2P signaling transmission through the MQTT channel, and uses the same port to simultaneously handle STUN requests and WSS service listening; achieving high-performance remote file transfer with a transmission rate of 22-34MB / s.

[0108] Third, it provides unified storage resource management, supports the aggregation of storage resources from multiple NAS devices to form a unified logical storage pool; has a built-in load balancing and failover mechanism, and provides unified namespace management; and enables cross-device data isolation and secure sharing, with each family member having an independent data space.

[0109] Fourth, it features integrated cloud-to-cloud collaboration, achieving seamless collaboration between local and cloud storage through deep integration with the operator's cloud disk platform via NAS-SDK; it supports fine-grained control such as scheduled upload task distribution, progress monitoring, and task pause; and it builds a complete end-to-end-to-cloud integrated data storage ecosystem.

[0110] This application embodiment achieves a significant increase in intranet transmission speed and solves the intranet interconnection barrier of traditional FTTR+NAS solutions; it ensures the stability and efficiency of remote access through intelligent routing strategies; and the unified resource management architecture significantly improves storage resource utilization and system reliability, providing users with a high-speed, secure, and convenient integrated data storage experience.

[0111] For ease of understanding, a specific embodiment will be used as an example: In this specific embodiment, the FTTR+NAS integrated data storage system can be as follows: Figure 6 As shown, it is divided into cloud, APP and FTTR-NAS devices.

[0112] based on Figure 6 The architecture can achieve various functions through the configuration of servers in the cloud and communication interactions within the architecture, specifically: An app can have, but is not limited to, a user interface layer (providing a user interface), an app base (core control framework), an SMB Client (high-speed file access client within a local area network), a Relay Client (relay transmission client), and a P2P Client (point-to-point direct connection client).

[0113] FTTR-NAS devices can, but are not limited to, having NAS services (core storage services), P2P Client (peer-to-peer connection client), and Relay Client (relay service client).

[0114] The cloud can include, but is not limited to, SCP platforms (business control platforms and responsible for overall scheduling), user management services (user authentication and permission management), NAS management services (NAS device registration and status management), Relay Servers (unified signaling control and data relay), STUN Servers (NAT traversal services and assisting in establishing P2P connections), and PG databases (storing user information, device information, and configuration data).

[0115] exist Figure 6 In the diagram, the remote access path is represented by a solid blue line, and the near-end access path is represented by a dashed black line. The remote signaling interaction channel uses the MQTT protocol for user authentication and signaling interaction (APP to SCP) and device registration and status reporting (NAS to SCP). The remote file data transmission channel uses relay mode data transmission (APP to Relay Server to NAS), P2P direct connection establishment (APP to STUN Server to NAS), and P2P direct connection data transmission (APP to NAS). The near-end signaling interaction uses the TCP protocol (APP to NAS), and the file data transmission uses the SMB protocol for direct access within the local area network (APP to NAS).

[0116] The core functional modules are as follows: user authentication and remote signaling (responsible for user authentication, managing remote access sessions, and coordinating P2P connection establishment), intelligent routing strategy (automatically selecting the optimal transmission path SMB / P2P / Relay, realizing dynamic path switching during transmission, and ensuring transmission success rate and efficiency), and data service layer (providing a unified data access interface, supporting multiple transmission protocol adaptations, and ensuring secure and reliable data transmission). This layered architecture achieves good scalability and maintainability of the system through standardized hardware design and microservice-based software services. Each component adopts standard communication protocols to ensure compatibility and replaceability, providing a complete high-speed data storage solution for home and enterprise users.

[0117] for Figure 6 The architecture shown allows near-end apps to directly access NAS devices via TCP and SMB protocols for signaling and file transfer. Remote access to NAS devices requires interaction through a cloud platform using P2P direct connection and relay services. Signaling uses MQTT, and file transfer uses STUN (P2P) and WebSocket (relay) protocols. Specifically, when the terminal device and NAS are on the same FTTR LAN, SMB is automatically used for high-speed, low-latency intranet transmission. When remote, it prioritizes NAT traversal via a STUN server to establish an end-to-end encrypted P2P direct connection for optimal speed. If traversal fails (e.g., due to complex NAT), it automatically and seamlessly degrades to WebSocket relay transmission, ensuring connection reliability. All remote signaling is exchanged through a unified MQTT channel, simplifying system complexity. In other words, the near-end SMB enables high-speed file sharing within the intranet via the SMB protocol; the remote P2P direct connection uses the STUN protocol for NAT traversal, establishing an end-to-end encrypted WSS direct connection channel; and the remote relay seamlessly switches to the relay server for data forwarding when P2P fails, ensuring service reliability. Thus, by dynamically detecting the network environment, the system automatically selects the optimal path among these three modes and switches seamlessly for the user.

[0118] It should be noted that, Figure 6 The P2P protocol in the context can also be other protocols, and STUN can also be other protocols. Correspondingly, the names of the client and server will change as the protocol changes. In addition, the cloud can contain more than one RelayServer and STUN Server; the number of these two types of servers is not limited to one.

[0119] The following provides illustrative examples of the four contents included in the embodiments of this application.

[0120] First, there's the intelligent three-layer access architecture: This architecture's intelligent collaboration is manifested in specific scenarios. For example, when a user accesses NAS files via the same Wi-Fi network at home, the device's intelligent routing policy engine automatically determines it as "nearby" based on the IP segment (e.g., 192.168.1.x) and directly establishes an SMBv3 connection for high-speed transmission. When the user accesses the NAS remotely using a mobile app, the engine triggers remote mode: first, it sends commands to the server and the accessed device via an MQTT signaling channel, and both parties attempt to exchange address information through a STUN server to establish a P2P direct connection; if penetration fails due to both parties being behind symmetric NAT, the signaling will notify both parties to seamlessly switch to a WebSocket relay server for transmission. Crucially, whether it's the near-end TCP signaling or the remote MQTT signaling, the data structure of the commands such as "request file list" or "download a file block" is completely consistent, eliminating the need for upper-layer applications to write two sets of processing logic for different network modes.

[0121] Secondly, there is a highly efficient P2P traversal mechanism: its efficiency is achieved through a specific process. Assuming device A and device B need to connect remotely, they first exchange "attempt P2P connection" signaling via a shared MQTT channel. Subsequently, based on this signaling agreement, both parties simultaneously send requests to a public STUN server to obtain their public IP address (IP:Port) behind the NAT. If both parties have full-cone NAT, they will exchange their public IP address information again via the MQTT channel and then directly initiate a connection to the other party's public IP address. To simplify implementation, the device listens for two services simultaneously on the same network port (e.g., port 443) during startup: one is handling UDP requests via the STUN protocol, and the other is providing WSS service. Once the P2P TCP connection is successfully established via WSS, file transfer speeds of 22-34 MB / s will be achieved over this encrypted channel.

[0122] Thirdly, unified storage resource management: This management function is implemented through virtualization technology. For example, a family connects two NAS devices from different brands (with 4TB and 6TB of space respectively) to the system. The system aggregates them into a "unified storage pool" with a total capacity of approximately 10TB and provides an access point such as \\homecloud\family. When a user stores a video file through this access point, the built-in load balancing algorithm may, based on the remaining space and current load of each NAS, actually store it on the 6TB NAS, completely transparent to the user. The system also creates independent data spaces for each family member (such as parents and children) within the storage pool (such as \\homecloud\father, \\homecloud\kid) to achieve permission isolation, and can also set up a \\homecloud\public shared area for the whole family to access.

[0123] Fourth, integrated cloud-based collaboration: Collaboration capabilities are achieved through the SDK and task scheduling. The carrier's cloud storage platform, through its provided NAS-SDK, can send "scheduled backup of phone photos" tasks to NAS devices in the home. Users can set "daily backup at 2 AM" in the cloud storage app, and this command is sent to the NAS via the cloud's MQTT service. Upon receiving the command, the NAS creates the task, and during execution, it encrypts and uploads newly added photos to the cloud, providing real-time progress (e.g., "350 / 500MB transferred") to the cloud storage app for user viewing through the same channel. Users can also pause the process at any time in the app. Simultaneously, the NAS's local "Work Documents" folder can be set to automatically synchronize to the cloud and cache recently accessed files locally, achieving integrated cloud-based access.

[0124] Figure 7 The near-end access process was demonstrated: after the APP starts, it automatically scans for FTTR devices in the local area network. The master and slave FTTR-NAS respond to the scan request and return device information. After the system confirms that the APP and NAS are in the same local area network, it directly exchanges signaling through the TCP protocol and uses the SMB protocol for file transfer.

[0125] Figure 8 The remote P2P priority access process is presented as follows: When it is detected that the APP and NAS are not on the same local area network, the APP initiates a remote access request to the SCP carrying the user identity and device serial number; the SCP returns the Relay Server address, STUN service address, and the access capabilities supported by the system; the APP notifies the NAS device to prepare to establish a P2P connection via MQTT; the NAS device interacts with the STUN server to obtain the public network address and port mapping information; both parties exchange the signaling information required for the P2P connection through the MQTT channel, and finally establish an end-to-end encrypted direct connection channel to achieve efficient file transfer.

[0126] Figure 9The relay access process is described as follows: When the P2P connection fails or is of poor quality, the system switches to relay mode via MQTT notification; the APP initiates the scanning process, and the master FTTR-NAS returns the device scan results; after confirming that the APP and FTTR / NAS are on different local area networks, the APP initiates a remote access MQTT request to the SCP; the SCP returns the URL address of the Relay Server; the APP initiates service access to the NAS via MQTT and obtains service data containing the device IP address; subsequently, the APP notifies the master FTTR-NAS to prepare to establish a relay connection, and after confirmation by the master FTTR-NAS, coordinates with the slave FTTR-NAS to jointly establish a relay connection; the master and slave FTTR-NAS rewrite the URL and connect to the Relay Server respectively; finally, the APP uploads files to the Relay Server in fragments, the master and slave FTTR-NAS receive files in fragments from the Relay Server, and the Relay Server completes data forwarding according to the pairing information.

[0127] The system employs four core technologies: intelligent routing strategy automatically selects the optimal transmission path, achieving P2P priority and automatic degradation relay in case of failure; unified signaling control simplifies protocol complexity through MQTT; end-to-end security ensures that all remote transmissions pass through encrypted channels; and high-performance transmission supports file fragmentation, significantly improving the efficiency and reliability of large file transmissions.

[0128] like Figure 10 As shown, the intelligent routing strategy can be composed of an upper control plane and a lower data plane. The control plane, as the system core, integrates four modules: a task scheduling center, an environment awareness engine, a policy decision engine, and a routing execution engine. These modules respectively handle overall coordination, network status detection, intelligent path selection, and connection management execution. The data plane includes three transmission channels: a near-end SMB channel, a P2P direct connection channel, and a relay backup channel. These provide high-speed intranet transmission, end-to-end encrypted direct connection, and reliable forwarding capabilities, all converging at the data plane layer. This architecture achieves separation of control and data through a hierarchical design. Blue indicates the core control module, green indicates the preferred transmission channel, red indicates the backup guarantee channel, and purple indicates the awareness and decision module. Clear arrow directions illustrate the information flow and control flow. Each functional unit uses abstract naming and clear boundaries to ensure the intuitiveness and maintainability of the system structure. In some embodiments, the two servers in the cloud platform can achieve corresponding communication functions only after the following configuration / deployment.

[0129] Relay and P2P remote access multi-virtual machine deployment method 1: Determine the deployment mode. If high availability is required, adopt a dual-machine master-slave mode, such as... Figure 11As shown, Nginx and Keepalived are deployed on virtual machines A and B, sharing a single floating IP address, and public IP mapping is enabled. If deployed on a single machine, as... Figure 12 As shown, Nginx can be deployed solely on virtual machine A, without requiring Keepalived and a floating IP address; public IP mapping can be directly enabled. Deploying STUN Server and Relay Server services (if needed): Deploy STUN Server and Relay Server services first. They can be deployed on the same virtual machine (or even coexist with Nginx), but each virtual machine can only deploy one Relay Server instance. Each Relay Server virtual machine needs a separate public IP address and port 8114 must be opened (if the site does not require relay functionality, Relay deployment and port opening can be ignored). Deploying Nginx and Keepalived in dual-machine mode: Configure Nginx and Keepalived on virtual machines A and B, set floating IP addresses, and open ports 8115, 8116, and 8117 via public IP addresses; Single-machine mode: Deploy Nginx on virtual machine A, opening the same ports (8115, 8116, 8117) via public IP addresses. The deployment order can be STUN / Relay Server first, then Nginx / Keepalived. If the site does not require P2P remote or relay services, STUN Server and Relay Server do not need to be deployed, simplifying the deployment process.

[0130] Relay and P2P remote access multi-virtual machine deployment method 2: Adopting a dual-machine high-availability mode, such as Figure 13 As shown, Virtual Machine A (primary) and Virtual Machine B (backup) form a primary-backup cluster using Keepalived, sharing a floating IP address, which is then mapped to a public IP address to provide services externally. Deploy STUN Server and Relay Server services (if required for functionality), first deploying the STUN Server service (port 8118). Figure 11 The STUN servers are distributed across virtual machines 1, 2, and 3, and a Relay Server service (port 8114) is deployed there. Figure 11 The Relay Server is deployed on virtual machine 3. If the site does not require P2P remote or relay functionality, this step and subsequent public IP configuration can be skipped. Deploy Nginx and Keepalived on virtual machines A and B, configuring virtual IPs (VIPs) to achieve master-slave failover. For network and port configuration, the Nginx cluster maps a floating IP to a public IP and opens ports (8115, 8116, 8117); if the Relay service is already deployed, it needs to be on the virtual machine where the Relay resides (…). Figure 13Assign a separate public IP address to virtual machine 3) and open its service port 8114. The relay service does not go through the Nginx proxy and can be configured with an independent public IP address to provide services directly to the outside world. The deployment can strictly follow the order of STUN / Relay first, then Nginx / Keepalived.

[0131] exist Figures 11 to 13 In Chinese, STUN corresponds to Figure 6 STUN Server, Relay corresponds to Figure 6 The RelayServer in the middle.

[0132] In traditional solutions, the FTTR network and NAS storage operate independently, resulting in intranet communication barriers and transmission bottlenecks. This application combines the FTTR network and NAS storage, interconnecting them via fiber optic cable to the main gateway to form a fully covered, high-speed internal network. Through a unified MQTT signaling channel and intelligent routing policy engine, near-end SMB, remote P2P, and remote relay modes are organically integrated, dynamically selecting the optimal transmission path based on the network environment. This deep integration solves the problems of unstable device discovery and low cross-network transmission efficiency in traditional solutions, achieving a significant improvement in transmission rates from less than 10MB / s in traditional solutions to 22-34MB / s. Secondly, the coordinated design of unified storage resource management and P2P traversal mechanism breaks through the scalability limitations of traditional storage systems. In existing technologies, multi-device storage aggregation and remote access are two independent technical areas. This application combines unified namespace management with intelligent NAT traversal, enabling multiple NAS devices distributed in different physical locations to form a unified logical storage pool and achieve remote access through efficient P2P direct connection. This collaborative design ensures both flexible expansion of storage resources and high-speed, stable remote access. Furthermore, the deep integration of cloud-based collaboration and intelligent transmission networks creates a superior end-to-end user experience. Traditional solutions often present a disconnect between cloud disk integration and local storage. This application's embodiment, through deep integration of the NAS-SDK and carrier cloud disks, combined with the protection of intelligent transmission networks, achieves seamless data flow between local and cloud environments, while ensuring data transmission security and reliability, and meeting the needs of domestic and international carriers.

[0133] This application also provides a communication device, such as... Figure 14 As shown, the communication device 1400 includes: One or more processors 1410; The memory 1420 stores one or more programs that, when executed by one or more processors 1410, enable the one or more processors 1410 to implement the fiber optic network access method described in any of the above embodiments.

[0134] Memory 1420, as a non-transitory network system, can be used to store non-transitory software programs and non-transitory computer-executable programs. Furthermore, memory 1420 may include high-speed random access memory and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, memory 1420 may optionally include remotely located memories 1420 relative to processor 1410, which can be connected to processor 1410 via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0135] The memory 1420 can be implemented as a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 1420 can store the operating system and other applications. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program code is stored in the memory 1420 and is called and executed by the processor 1410.

[0136] The processor 1410 can be implemented using a general-purpose CPU (Central Processing Unit), microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this application.

[0137] In some embodiments, the communication device further includes: Input / output interfaces are used to implement information input and output; The communication interface is used to enable communication and interaction between this device and other devices. Communication can be achieved through wired means (such as USB, Ethernet cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.). The bus transmits information between various components of the device (e.g., processor 1410, memory 1420, input / output interfaces, and communication interfaces); The processor 1410, memory 1420, input / output interface, and communication interface can communicate with each other within the device via a bus.

[0138] One embodiment of this application also provides a computer-readable storage medium storing computer-executable instructions for performing the fiber optic network access method provided in any embodiment of this application.

[0139] One embodiment of this application also provides a computer program product, including a computer program or computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer program or computer instructions from the computer-readable storage medium and executes the computer program or computer instructions, causing the computer device to perform the fiber optic network access method provided in any embodiment of this application.

[0140] The system architecture and application scenarios described in this application are for the purpose of more clearly illustrating the technical solutions of this application, and do not constitute a limitation on the technical solutions provided in this application. Those skilled in the art will know that as system architectures evolve and new application scenarios emerge, the technical solutions provided in this application are also applicable to similar technical problems.

[0141] Those skilled in the art will understand that all or some of the steps in the methods disclosed above, as well as the functional modules / units in the systems and devices, can be implemented as software, firmware, hardware, or suitable combinations thereof.

[0142] In hardware implementations, the division between functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed collaboratively by several physical components. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include computer storage media (or non-transitory media) and communication media (or transient media). As is known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer. Furthermore, as is known to those skilled in the art, communication media typically contain computer-readable instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.

[0143] As used in this specification, the terms "component," "module," "system," etc., are used to refer to computer-related entities, hardware, firmware, combinations of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, or a computer. As illustrated, applications running on computing devices and computing devices can both be components. One or more components may reside in a process or execution thread, and components may be located on a single computer or distributed among two or more computers. Furthermore, these components can be executed from various computer-readable media on which various data structures are stored. Components can communicate, for example, via local or remote processes based on signals having one or more data packets (e.g., data from two components interacting with another component between a local system, a distributed system, or a network, such as the Internet interacting with other systems via signals).

[0144] The above description, with reference to the accompanying drawings, illustrates some embodiments of this application, but does not limit the scope of this application. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and spirit of this application shall be within the scope of this application.

Claims

1. An access method for fiber optic networking, applied to a cloud platform, comprising: In response to detecting the network environment of the terminal device, a target access mode corresponding to the network environment is determined; wherein, the target access mode is a near-end access mode, a remote direct connection access mode, or a remote relay access mode. The target access mode is sent to the gateway storage device and the terminal device in the optical fiber network, so that the gateway storage device communicates with the terminal device using the target access mode.

2. The method according to claim 1, characterized in that, The step of determining the target access mode corresponding to the network environment in response to detecting the network environment of the terminal device includes any one of the following: In response to the network environment being that the terminal device is located within the local area network of the fiber optic network, the target access mode is determined to be the near-end access mode; In response to the network environment being that the terminal device is located outside the local area network of the optical fiber network, the target access mode is determined to be either the remote direct connection access mode or the remote relay access mode.

3. The method according to claim 2, characterized in that, The step of determining the target access mode as either the remote direct access mode or the remote relay access mode in response to the network environment being that the terminal device is located outside the local area network of the fiber optic network includes: In response to the network environment being that the terminal device is located outside the local area network of the optical fiber network, the target access mode is determined to be the remote direct connection access mode; In response to the failure to establish a direct data transmission channel in the remote direct access mode or the service quality of the direct data transmission channel being lower than a preset quality threshold, the target access mode is updated to the remote relay access mode.

4. The method according to claim 1, characterized in that, In the near-end access mode, the terminal device performs file transfer with the gateway storage device through the near-end data transmission channel and performs signaling transmission with the gateway storage device through the near-end signaling transmission channel; The near-end data transmission channel uses a first communication protocol for file transfer, which is a computer network communication protocol with network data transmission and storage resource sharing functions. The near-end signaling transmission channel uses a second communication protocol for signaling transmission. The second communication protocol is a transport layer communication protocol used for end-to-end data packet transmission in the network.

5. The method according to claim 1, characterized in that, In both the remote direct access mode and the remote relay access mode, the terminal device shares the same remote signaling transmission channel with the gateway storage device for signaling transmission; in the remote direct access mode, the terminal device performs file transfer with the gateway storage device through the direct data transmission channel; in the remote relay access mode, the terminal device performs file transfer with the gateway storage device through the relay data transmission channel. The remote signaling transmission channel uses a third communication protocol for signaling transmission, which is a distributed system signaling interaction and message transmission protocol. The direct data transmission channel uses a fourth communication protocol for file transfer. The fourth communication protocol is a secure data interaction and resource sharing protocol based on a distributed node architecture. The relay data transmission channel uses the fifth communication protocol for file transfer, which is an application-layer bidirectional low-latency communication protocol.

6. The method according to claim 1, characterized in that, The signaling structure for each access mode remains consistent.

7. The method according to claim 1, characterized in that, The direct data transmission channel of the remote direct access mode is: an end-to-end encrypted direct connection channel established by the target server of the cloud platform through network address translation (NAT) traversal based on the sixth communication protocol and the target encryption protocol; wherein, the sixth communication protocol is the network address discovery and NAT traversal protocol.

8. The method according to claim 1, characterized in that, The relay data transmission channel of the remote relay access mode is established based on the relay server of the cloud platform, and the relay server satisfies any one of the following: the relay server provides external services through the virtual machine belonging to the cloud platform; The relay server provides services to the outside world through an independently configured public IP address.

9. The method according to claim 1, characterized in that, The method further includes at least one of the following: Create a unified namespace corresponding to the optical fiber network, wherein the unified namespace corresponds to the storage resources of each gateway storage device in the optical fiber network, and is used for the unified management of the storage resources of each gateway storage device; A load balancing and failover mechanism is used to manage the storage resources of each gateway storage device. The load balancing and failover mechanism supports allocating the data storage location and data access path of the terminal device according to the storage capacity, current load and device status of each gateway storage device.

10. The method according to claim 1, characterized in that, The cloud platform calls the interface provided by the software development kit (SDK) to establish a data communication connection with the gateway storage device in the cloud platform; wherein, the data communication connection supports at least one of the following: issuing upload tasks to the gateway storage device, monitoring the progress of the upload tasks, and pausing the upload tasks.

11. The method according to claim 1, characterized in that, The cloud platform supports providing at least one of the following services to the gateway storage device: identity authentication, file service, data backup, space management, storage resource aggregation, and artificial intelligence classification.

12. An access method for an optical fiber network, applied to a gateway storage device in the optical fiber network, comprising: The system receives a target access mode sent by the cloud platform, wherein the target access mode is determined by the cloud platform based on the network environment of the detected terminal device, and the target access mode is a near-end access mode, a far-end direct connection access mode, or a far-end relay access mode. The target access mode is used to communicate with the terminal device.

13. The method according to claim 12, characterized in that, The step of communicating with the terminal device using the target access mode includes: In response to the cloud platform creating a unified namespace corresponding to the fiber optic network, a target access mode is adopted, and communication with the terminal device is based on the data global access path of the unified namespace; The unified namespace corresponds to the storage resources of each gateway storage device in the optical fiber network and is used for the unified management of the storage resources of each gateway storage device.

14. The method according to claim 12, characterized in that, The step of communicating with the terminal device using the target access mode includes: In response to receiving a transmission request for a target file from the terminal device, the target file is transmitted to the terminal device in a fragmented manner.

15. The method according to claim 12, characterized in that, The gateway storage device is a gateway device that integrates Network Attached Storage (NAS) storage functionality. The gateway device can be any of the following: a router, a central office access device, a transmission network device, or a user-side terminal device.

16. A communication device, comprising: At least one processor; At least one memory for storing at least one program; When at least one of the programs is executed by at least one of the processors, it implements the access method for the optical fiber network according to any one of claims 1 to 11, or implements the access method for the optical fiber network according to any one of claims 12 to 15.

17. A computer-readable storage medium storing computer-executable instructions, the computer-executable instructions being used to execute the access method of the optical fiber network according to any one of claims 1 to 11, or to implement the access method of the optical fiber network according to any one of claims 12 to 15.

18. A computer program product comprising a computer program or computer instructions stored in a computer-readable storage medium, wherein a processor of a communication device reads the computer program or computer instructions from the computer-readable storage medium, and the processor executes the computer program or computer instructions to cause the communication device to perform the fiber optic network access method according to any one of claims 1 to 11, or to implement the fiber optic network access method according to any one of claims 12 to 15.

Images