CN112995333B - Remote file activation method, system and related device - Google Patents

Remote file activation method, system and related device Download PDF

Info

Publication number
CN112995333B
CN112995333B CN202110361706.0A CN202110361706A CN112995333B CN 112995333 B CN112995333 B CN 112995333B CN 202110361706 A CN202110361706 A CN 202110361706A CN 112995333 B CN112995333 B CN 112995333B
Authority
CN
China
Prior art keywords
npl
server
file
address
client
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202110361706.0A
Other languages
Chinese (zh)
Other versions
CN112995333A (en
Inventor
李西峙
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shenzhen Tatfook Network Tech Co Ltd
Original Assignee
Shenzhen Tatfook Network Tech Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Shenzhen Tatfook Network Tech Co Ltd filed Critical Shenzhen Tatfook Network Tech Co Ltd
Priority to CN202110361706.0A priority Critical patent/CN112995333B/en
Publication of CN112995333A publication Critical patent/CN112995333A/en
Application granted granted Critical
Publication of CN112995333B publication Critical patent/CN112995333B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/104—Peer-to-peer [P2P] networks
    • H04L67/1074—Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
    • H04L67/1078—Resource delivery mechanisms
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H04L69/163—In-band adaptation of TCP data exchange; In-band control procedures
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/50—Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The application discloses a remote file activation method, a remote file activation system and a related device, which are used for realizing the function of activating files on a remote server under an NPL running environment. The method is applied to an NPL running environment, and comprises the following steps: the NPL server configures a port number and an IP address for the NPL server; the NPL server shares a target file through a TCP protocol according to the port number and the IP address, wherein the target file is a public neuron file; the NPL client acquires a port number and an IP address of the NPL server; the NPL client sends a file activation instruction to the NPL server according to the port number and the IP address of the NPL server; and the NPL server activates the target file according to the file activation instruction.

Description

Remote file activation method, system and related device
Technical Field
The present disclosure relates to the field of data processing, and in particular, to a method, system, and related apparatus for remote file activation.
Background
With the development of internet technology, clients may share local resources through a network for other clients to use. These shared resources can be directly accessed by other clients by means of a network, by means of which the clients can easily obtain shared files issued by other users.
In the prior art, a client can share files with each other after being connected with another client, but the remote file activation method in the NPL running environment is not disclosed in the prior art.
Disclosure of Invention
In order to solve the technical problems, the application provides a remote file activation method, a remote file activation system and a related device, which are used for realizing the function of activating files on a remote server under an NPL running environment.
The first aspect of the present application provides a remote file activation method, where the method is applied to an NPL running environment, and the method includes:
the NPL server configures a port number and an IP address for the NPL server;
the NPL server shares a target file through a TCP protocol according to the port number and the IP address, wherein the target file is a public neuron file;
the NPL server receives a file activation instruction sent by the NPL client, wherein the file activation instruction comprises a port number and an IP address of the NPL server;
and the NPL server activates the target file according to the file activation instruction.
Optionally, the sharing, by the NPL server, the target file through the TCP according to the port number and the IP address includes:
the NPL server side shares a public file list to the NPL client side through a TCP protocol according to the port number and the IP address;
and the NPL server adds the target file to the public file list, so that the NPL client accesses the target file through the public file list.
Optionally, the file activation instruction further includes a file identifier of the target file, and before the NPL server activates the target file according to the file activation instruction, the method further includes:
and the NPL server determines a target file to be activated in the public file list according to the file identification.
The second aspect of the present application provides a remote file activation method, where the method is applied to an NPL running environment, and the method includes:
the NPL client acquires a port number and an IP address of an NPL server;
and the NPL client sends a file activation instruction to the NPL server according to the port number and the IP address of the NPL server, so that the NPL server activates the target file according to the file activation instruction, and the target file is a public neuron file.
Optionally, after the NPL client obtains the port number and the IP address of the NPL server, the method further includes:
the NPL client allocates a service end name for the NPL service end;
the NPL client establishes a mapping relation between the name of the server and the port number and IP address of the NPL server;
the NPL client sending a file activation instruction to the NPL server according to the port number and the IP address of the NPL server includes:
and the NPL client sends a file activation instruction to the NPL server according to the name of the server.
A third aspect of the present application provides a remote file activation system, where the system is applied in an NPL running environment, the system includes: an NPL server and an NPL client;
the NPL server configures a port number and an IP address for the NPL server;
the NPL server shares a target file through a TCP protocol according to the port number and the IP address, wherein the target file is a public neuron file;
the NPL client acquires a port number and an IP address of the NPL server;
the NPL client sends a file activation instruction to the NPL server according to the port number and the IP address of the NPL server;
and the NPL server activates the target file according to the file activation instruction.
A fourth aspect of the present application provides an NPL server, including:
a configuration unit, configured to configure a port number and an IP address for the NPL server;
the sharing unit is used for sharing the target file through a TCP protocol according to the port number and the IP address, wherein the target file is a public neuron file;
the receiving unit is used for receiving a file activation instruction sent by the NPL client, wherein the file activation instruction comprises a port number and an IP address of the NPL server;
and the activating unit is used for activating the target file according to the file activating instruction.
Optionally, the sharing unit includes:
the sharing module is used for sharing a public file list to the NPL client through a TCP protocol according to the port number and the IP address;
and the adding module is used for adding the target file to the public file list so that the NPL client accesses the target file through the public file list.
Optionally, the file activation instruction further includes a file identifier of the target file, and the NPL server further includes:
and the determining unit is used for determining the target file to be activated in the public file list according to the file identification.
A fifth aspect of the present application provides an NPL client, comprising:
an obtaining unit, configured to obtain a port number and an IP address of an NPL server;
and the sending unit is used for sending a file activation instruction to the NPL server according to the port number and the IP address of the NPL server so that the NPL server activates the target file according to the file activation instruction, and the target file is a public neuron file.
Optionally, the NPL client further includes:
the distribution unit is used for distributing service end names to the NPL service ends;
the establishing unit is used for establishing a mapping relation between the name of the service end and the port number and the IP address of the NPL service end;
the sending unit is specifically configured to:
and sending a file activation instruction to the NPL server according to the server name.
A sixth aspect of the present application provides a remote document activation apparatus, the apparatus comprising:
a processor, a memory, an input-output unit, and a bus;
the processor is connected with the memory, the input/output unit and the bus;
the memory holds a program that the processor invokes to perform the first and second aspects, and optionally the remote file activation method of any one of the first and second aspects.
A seventh aspect of the present application provides a computer readable storage medium having stored thereon a program which when executed on a computer performs the first and second aspects, and optionally the remote file activation method of any one of the first and second aspects.
From the above technical scheme, the application has the following advantages:
in an NPL operating environment, when one NPL runtimes share a file, other NPL runtimes may use a file activation instruction to remotely activate the file, where the file sharing party is referred to as an NPL server and the file activating party is referred to as an NPL client.
Specifically, the NPL runtimes start the service-side function by configuring the port number and the IP address for itself, and the NPL service side can share the local file to the NPL client, and the file shared to the NPL client is called a public file. The NPL client can access the public file shared by the NPL server through the port number and the IP address of the NPL server, and when the NPL client sends a file activation instruction to the NPL server, the NPL server activates the public file, thereby realizing the function of activating the file on the remote NPL server in the NPL running environment.
Drawings
In order to more clearly illustrate the technical solutions of the present application, the drawings that are needed in the description of the embodiments will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flowchart illustrating an embodiment of a remote file activation method provided in the present application;
FIG. 2 is a flowchart illustrating another embodiment of a remote file activation method provided in the present application;
FIG. 3 is a schematic diagram illustrating an embodiment of a remote file activation system provided herein;
fig. 4 is a schematic structural diagram of an embodiment of an NPL server provided in the present application;
fig. 5 is a schematic structural diagram of another embodiment of an NPL server provided in the present application;
FIG. 6 is a schematic structural diagram of one embodiment of an NPL client provided in the present application;
FIG. 7 is a schematic structural diagram of another embodiment of an NPL client provided in the present application;
fig. 8 is a schematic structural diagram of an embodiment of a remote file activation device provided in the present application.
Detailed Description
The application provides a remote file activation method, a remote file activation system and a related device, which are used for realizing the function of activating files on a remote server under an NPL running environment.
It should be noted that, the remote file activation method provided in the present application is applied to an NPL operating environment, where NPL is a general open source language, the design of NPL uses a human neural network structure as a reference, in NPL, each file corresponds to a neuron, and information interaction between files corresponds to information transfer between neurons in a neural network. NPL run time is the implementation code of the NPL running environment, written in c++ language, and can be understood by dividing NPL run time into three layers: the bottom layer is the realization of NPL thread, and the compiling and executing of lua, C#, C/C++ language are carried out; the middle layer is an NPL thread and the file is scheduled; the top layer is the API of the NPL, covering network connections, resource management, 2D graphics, 3D engines, etc. The remote file activation method provided in the present application is described below.
Referring to fig. 1, fig. 1 is a schematic diagram illustrating an embodiment of a remote file activation method provided in the present application, where the method includes:
101. the NPL server configures a port number and an IP address for the NPL server;
in an NPL operating environment, when one NPL runtimes share a file, other NPL runtimes may use a file activation instruction to remotely activate the file, where the file sharing party is referred to as an NPL server and the file activating party is referred to as an NPL client.
In this embodiment, the NPL run as the server needs to start the server function first, so that it can be accessed by other clients. Specifically, NPL run may use npl.startnetserver function to turn on the server function, the syntax of which is as follows:
NPL.StartNetServer(ip,port)；
in the above grammar, the parameter ip is the ip address of the NPL run, and the parameter port is the port number. Through the function, an NPL run time can be changed into a server, and the server is responsible for receiving and processing information from a client.
For example: npl.startnetserver ("0.0.0.0", 8080);
where "0.0.0.0" represents all IP addresses, it is also possible to use "127.0.0.1", "localhost" or any other IP address; "8080" is a port number, which may be any integer. It should be noted that when the parameter port is "0", it indicates that the NPL running environment does not monitor the incoming connection, i.e. only operates as a pure client.
102. The NPL server shares a target file through a TCP protocol according to the port number and the IP address, wherein the target file is a public neuron file;
after the NPL run time calls the NPL.StartNetServer function to start the server function, the local files can be shared. In the NPL running environment, files shared by the NPL server to the NPL client are referred to as common neuron files, i.e., target files in the application, and the common neuron files can be remotely activated by other NPL clients.
It should be noted that, the communication between the NPL server and the client all adopts TCP protocol.
103. The NPL client acquires a port number and an IP address of an NPL server;
after the NPL server shares the target file, other NPL clients can access the target file shared by the NPL server according to the port number and the IP address of the NPL server. Therefore, in order for the NPL client to remotely activate a file on the NPL server, the NPL client needs to first acquire the port number and the IP address of the NPL server.
104. The NPL client sends a file activation instruction to the NPL server according to the port number and the IP address of the NPL server;
and the NPL client sends a file activation instruction to the NPL server according to the acquired port number and IP address of the NPL server so as to remotely activate the target file shared by the NPL server.
It should be noted that, when the NPL client remotely activates the target file shared by the NPL server for the first time, a TCP connection is automatically established with the NPL server, so as to ensure that all messages between the NPL server and the NPL client can be delivered.
In particular, the implementation of such a remote activation file function relies on the npl.activate function, the syntax of which is as follows:
NPL.activate(url,msg)；
in the above grammar, the parameter url refers to the url address of an NPL file, and in this embodiment, the parameter url refers to the NPL file address on the NPL server because of remote activation; the parameter msg refers to the data sent to the url address.
The parameter url represents the url address of an NPL file, and the complete format of the parameter url is:
(sRuntimeStateName|gl)sNID:sRelativePath@DNSServerName
where sruntimetateate is the name of the selected thread, if the option is to write not sruntimetateate but only gl, then the local current thread is indicated.
sNID represents the identifier of the NPL operating environment, in this embodiment sNID is the identifier of the NPL server, which is determined by the port number and IP address of the NPL server.
sRelativePath is a relative path of files, typically referenced to main folder directory.
The @ stnservername represents the name of the DNS server.
And after the NPL client calls the NPL.activate function, sending a file activation instruction to the NPL server according to the identifier of the NPL server in the NPL.activate function.
105. And the NPL server activates the target file according to the file activation instruction.
After receiving the file activation instruction sent by the NPL client, the NPL server activates the local target file according to the file activation instruction, so as to realize the remote activation of the target file on the NPL server by the NPL client.
In this embodiment, the NPL runtime starts the server function by configuring a port number and an IP address for itself, and the NPL server may share a local file to the NPL client, and a file shared to the NPL client is referred to as a public file. The NPL client can access the public file shared by the NPL server through the port number and the IP address of the NPL server, and when the NPL client sends a file activation instruction to the NPL server, the NPL server activates the public file, thereby realizing the function of activating the file on the remote NPL server in the NPL running environment.
Referring to fig. 2, fig. 2 is a schematic diagram of an embodiment of a remote file activation method provided in the present application, where the method includes:
201. the NPL server configures a port number and an IP address for the NPL server;
step 201 in this embodiment is similar to step 101 in the previous embodiment, and will not be repeated here.
202. The NPL server side shares a public file list to the NPL client side through a TCP protocol according to the port number and the IP address;
because of the remote scheduling, in order to enable the files of the NPL server to be accessed by other NPL clients, the NPL server may share the files in the common file list with the NPL clients by maintaining the common file list.
203. The NPL server adds the target file to the public file list, so that the NPL client accesses the target file through the public file list;
if the NPL server needs to share the target file to other NPL clients, the target file needs to be added into a public file list maintained currently, and the files in the public file list are public neuron files in the application. This common file list is maintained by the server's scheduler, which has the role of an interface of the thread message queue and the underlying socket, which determines which thread the server receives to send information to for processing.
Specifically, the npl.addpublicfile function may be used to add the target file to the public file list, and the function syntax is as follows:
NPL.AddPublicFile(filename,id)；
in the above grammar, filename is the working directory and filename of the file, and id is the number of the file.
For example: npl.addpublicfile ("script/test/test.lua", 1); the addition of the test.lua file to the common file list is indicated and the number is set to 1. After the NPL server invokes the function, other NPL clients can access and activate the test.lua file.
204. The NPL client acquires a port number and an IP address of an NPL server;
in this embodiment, step 204 is similar to step 103 of the previous embodiment, and will not be described again here.
205. The NPL client allocates a service end name for the NPL service end;
an NPL client may be in communication connection with more than one NPL server, so when the NPL client first establishes a connection with an NPL server, an npl.adnpl run function is typically required to assign a local name (server name in this application) to a remote NPL server, so that the NPL client can directly use the server name to find the corresponding NPL server in a subsequent communication process.
206. The NPL client establishes a mapping relation between a service end name and a port number and an IP address of the NPL service end;
the NPL client may call an npl.adnpl run function to establish a mapping relationship between the service name and the port number and IP address of the NPL service, the function syntax being as follows:
NPL.AddNPLRuntimeAddress({host,port,nid})；
in the above grammar, the parameter host and the parameter port correspond to the IP address and the port number of the NPL server, respectively, and the parameter nid is a local name allocated by the NPL client to the NPL server, and it should be noted that, the specific name specified by nid may be random, for example: server1, server2, etc., and is used only at the NPL client to find the NPL server, i.e., different NPL clients may use different names to name the same NPL server.
For example: npl.adnpplruntimedaddress ({ host= "127.0.0.1", port= "8099", nid= "server1" }; the NPL servers denoted as IP address and port number "127.0.0.1" and "8099" are assigned the name "server1", respectively.
207. The NPL client sends a file activation instruction to the NPL server according to the name of the server;
and the NPL client sends a file activation instruction to the NPL server according to the acquired port number and IP address of the NPL server so as to remotely activate the target file shared by the NPL server.
In particular, the function of such a remote activation file depends on the npl.activate function, the syntax of which is as follows:
NPL.activate(url,msg)；
in the above grammar, the parameter url refers to the url address of an NPL file, and in this embodiment, the parameter url refers to the NPL file address on the NPL server because of remote activation; the parameter msg refers to the data sent to the url address.
The parameter url represents the url address of an NPL file, and the complete format of the parameter url is:
(sRuntimeStateName|gl)sNID:sRelativePath@DNSServerName
where sruntimetateate is the name of the selected thread, if the option is to write not sruntimetateate but only gl, then the local current thread is indicated.
sNID represents an identifier of the NPL running environment, in this embodiment, sNID is a local name allocated to the NPL client by the NPL server, and the client may analyze the port number and the IP address of the NPL server according to the sNID.
sRelativePath is a relative path of files, typically referenced to main folder directory.
The @ stnservername represents the name of the DNS server.
And after the NPL client calls the NPL.activate function, sending a file activation instruction to the NPL server according to the identifier of the NPL server in the NPL.activate function. For example:
npl.activate ("server 1: helloworld.lua", { }); representing the NPL client remotely activating a "helloworld.lua" file on the NPL server named server 1.
208. And the NPL server activates the target file according to the file activation instruction.
The NPL server determines the target file to be activated according to the file identification, such as the file name or the file address, of the target file carried in the file activation instruction, and activates the target file, thereby realizing the remote activation of the target file on the NPL server by the NPL client.
In this embodiment, the NPL runtimes turn on the server function by configuring itself with port numbers and IP addresses, and the NPL server maintains a common file list in which files are to be shared to other NPL clients.
Therefore, if the remote activation of the file is to be realized, the NPL server is required to add the local target file to the public file list, so that the NPL client can access the target file, and when the client sends a file activation instruction to the server, the server activates the target file, thereby realizing the function of activating the file on the remote server in the NPL running environment.
Referring to fig. 3, fig. 3 is an embodiment of a remote file activation system provided in the present application, where the system includes: an NPL server 301 and an NPL client 302;
the NPL server 301 configures a port number and an IP address for itself;
the NPL server 301 shares a target file through a TCP protocol according to the port number and the IP address, where the target file is a public neuron file;
the NPL client 302 acquires the port number and the IP address of the NPL server 301;
the NPL client 302 sends a file activation instruction to the NPL server 301 according to the port number and the IP address of the NPL server 301;
the NPL server 301 activates the target file according to the file activation instruction.
In the system of this embodiment, the functions of the NPL server 301 and the NPL client 302 correspond to the steps in the foregoing method embodiments shown in fig. 1 and fig. 2, and are not described herein again.
Referring to fig. 4, fig. 4 is an embodiment of an NPL server provided in the present application, where the NPL server includes:
a configuration unit 401, configured to configure a port number and an IP address for the NPL server;
a sharing unit 402, configured to share, according to a port number and an IP address, a target file through a TCP protocol, where the target file is a public neuron file;
a receiving unit 403, configured to receive a file activation instruction sent by an NPL client, where the file activation instruction includes a port number and an IP address of an NPL server;
an activating unit 404, configured to activate the target file according to the file activation instruction.
In the NPL server provided in this embodiment, the functions of each unit correspond to the steps in the foregoing method embodiment shown in fig. 1, and are not described herein again.
For a detailed description of the NPL server provided in the present application, please refer to fig. 5, fig. 5 is another embodiment of the NPL server provided in the present application, where the NPL server includes:
a configuration unit 501, configured to configure a port number and an IP address for an NPL server;
a sharing unit 502, configured to share, according to the port number and the IP address, a target file through a TCP protocol, where the target file is a public neuron file;
a receiving unit 503, configured to receive a file activation instruction sent by an NPL client, where the file activation instruction includes a port number and an IP address of an NPL server;
an activating unit 504, configured to activate the target file according to the file activation instruction.
In this embodiment, the sharing unit 502 further includes:
the sharing module 5021 is configured to share a public file list with the NPL client through a TCP protocol according to the port number and the IP address;
and the adding module 5022 is configured to add the target file to the public file list, so that the NPL client accesses the target file through the public file list.
Optionally, the file activation instruction further includes a file identifier of the target file, and in this embodiment, the NPL server further includes:
a determining unit 505, configured to determine, according to the file identifier, a target file to be activated in the public file list.
In the NPL server provided in this embodiment, functions of each unit and module correspond to the steps in the foregoing method embodiment shown in fig. 2, and are not described herein again.
Referring to fig. 6, fig. 6 is an embodiment of an NPL client provided in the present application, where the NPL client includes:
an obtaining unit 601, configured to obtain a port number and an IP address of an NPL server;
and the sending unit 602 is configured to send a file activation instruction to the NPL server according to the port number and the IP address of the NPL server, so that the NPL server activates a target file according to the file activation instruction, where the target file is a public neuron file.
In the NPL client provided in this embodiment, the functions of each unit correspond to the steps in the foregoing method embodiment shown in fig. 1, and are not described herein again.
Referring to fig. 7, fig. 7 is another embodiment of an NPL client provided in the present application, where the NPL client includes:
an obtaining unit 701, configured to obtain a port number and an IP address of an NPL server;
and the sending unit 702 is configured to send a file activation instruction to the NPL server according to the port number and the IP address of the NPL server, so that the NPL server activates a target file according to the file activation instruction, where the target file is a public neuron file.
In this embodiment, the NPL client further includes:
a distribution unit 703, configured to distribute a server name to the NPL server;
a building unit 704, configured to build a mapping relationship between a service end name and a port number and an IP address of the NPL service end;
the transmitting unit 702 is specifically configured to:
and sending a file activation instruction to the NPL server according to the name of the server.
In the NPL client provided in this embodiment, the functions of each unit correspond to the steps in the foregoing method embodiment shown in fig. 2, and are not described herein again.
The present application further provides a remote file activation apparatus, referring to fig. 8, fig. 8 is an embodiment of the remote file activation apparatus provided in the present application, where the apparatus includes:
a processor 801, a memory 802, an input/output unit 803, and a bus 804;
the processor 801 is connected to a memory 802, an input/output unit 803, and a bus 804;
the memory 802 holds a program that the processor 801 invokes to perform any of the remote file activation methods described above.
The present application also relates to a computer readable storage medium having a program stored thereon, characterized in that the program, when run on a computer, causes the computer to perform any of the above remote file activation methods.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, which are not repeated herein.
In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods may be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be embodied in essence or a part contributing to the prior art or all or part of the technical solution in the form of a software product stored in a storage medium, including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a read-only memory (ROM), a random access memory (RAM, random access memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

Claims (9)

1. A method for remote file activation, the method being applied to an NPL operating environment, the method comprising:
the NPL server configures a port number and an IP address for the NPL server;
the NPL server shares a target file through a TCP protocol according to the port number and the IP address, wherein the target file is a public neuron file;
the NPL server receives a file activation instruction sent by an NPL client, wherein the file activation instruction comprises a port number and an IP address of the NPL server;
the NPL server activates the functionality contained in the target file according to the file activation instruction so that the target file is called by the NPL client;
the sharing of the target file by the NPL server through the TCP according to the port number and the IP address comprises the following steps:
the NPL server side shares a public file list to the NPL client side through a TCP protocol according to the port number and the IP address;
and the NPL server adds the target file to the public file list, so that the NPL client accesses the target file through the public file list.
2. The method of claim 1, wherein the file activation instruction further comprises a file identifier of the target file, and wherein before the NPL server activates the target file according to the file activation instruction, the method further comprises:
and the NPL server determines a target file to be activated in the public file list according to the file identification.
3. A method for remote file activation, the method being applied to an NPL operating environment, the method comprising:
the NPL client acquires a port number and an IP address of an NPL server;
the NPL client accesses a shared public file list on the NPL server according to the port number and the IP address of the NPL server, wherein the shared public file list comprises target files added by the NPL server, and the target files are public neuron files;
the NPL client sends a file activation instruction to the NPL server according to the port number and the IP address of the NPL server, so that the NPL server activates the functionality contained in the target file in the shared file list according to the file activation instruction;
and the NPL client calls the activated target file on the NPL server.
4. The method of claim 3, wherein after the NPL client obtains the port number and the IP address of the NPL server, the method further comprises:
the NPL client allocates a service end name for the NPL service end;
the NPL client establishes a mapping relation between the name of the server and the port number and IP address of the NPL server;
the NPL client sending a file activation instruction to the NPL server according to the port number and the IP address of the NPL server includes:
and the NPL client sends a file activation instruction to the NPL server according to the name of the server.
5. A remote file activation system, the system being applied to an NPL operating environment, the system comprising: an NPL server and an NPL client;
the NPL server configures a port number and an IP address for the NPL server;
the NPL server side shares a public file list to the NPL client side through a TCP protocol according to the port number and the IP address;
the NPL server adds a target file to the public file list, so that the NPL client accesses the target file through the public file list;
the NPL client acquires a port number and an IP address of the NPL server;
the NPL client accesses a shared public file list on the NPL server according to the port number and the IP address of the NPL server, wherein the shared public file list comprises target files added by the NPL server, and the target files are public neuron files;
the NPL client sends a file activation instruction to the NPL server according to the port number and the IP address of the NPL server;
the NPL server activates the functionality contained in the target file according to the file activation instruction;
and the NPL client calls the activated target file on the NPL server.
6. An NPL server, wherein the NPL server includes:
a configuration unit, configured to configure a port number and an IP address for the NPL server;
the sharing unit is used for sharing the target file through a TCP protocol according to the port number and the IP address, wherein the target file is a public neuron file;
the device comprises a receiving unit, a processing unit and a processing unit, wherein the receiving unit is used for receiving a file activation instruction sent by an NPL client, and the file activation instruction comprises a port number and an IP address of an NPL server;
the activation unit is used for activating the functionality contained in the target file according to the file activation instruction so that the target file is called by the NPL client;
the sharing unit is specifically configured to:
sharing a public file list to the NPL client through a TCP protocol according to the port number and the IP address;
and adding a target file to the public file list, so that the NPL client accesses the target file through the public file list.
7. An NPL client, comprising:
an obtaining unit, configured to obtain a port number and an IP address of an NPL server;
an access unit, configured to access a shared public file list on the NPL server according to a port number and an IP address of the NPL server, where the shared public file list includes a target file added by the NPL server, and the target file is a public neuron file;
a sending unit, configured to send a file activation instruction to the NPL server according to a port number and an IP address of the NPL server, so that the NPL server activates functionality included in a target file in the shared file list according to the file activation instruction;
and the calling unit is used for calling the activated target file on the NPL server.
8. A remote document activation device, the device comprising:
a processor, a memory, an input-output unit, and a bus;
the processor is connected with the memory, the input/output unit and the bus;
the memory holds a program which the processor invokes to perform the method of any one of claims 1 to 4.
9. A computer readable storage medium having a program stored thereon, which when executed on a computer performs the method of any of claims 1 to 4.
CN202110361706.0A 2021-04-02 2021-04-02 Remote file activation method, system and related device Active CN112995333B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110361706.0A CN112995333B (en) 2021-04-02 2021-04-02 Remote file activation method, system and related device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110361706.0A CN112995333B (en) 2021-04-02 2021-04-02 Remote file activation method, system and related device

Publications (2)

Publication Number Publication Date
CN112995333A CN112995333A (en) 2021-06-18
CN112995333B true CN112995333B (en) 2023-05-23

Family

ID=76338986

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110361706.0A Active CN112995333B (en) 2021-04-02 2021-04-02 Remote file activation method, system and related device

Country Status (1)

Country Link
CN (1) CN112995333B (en)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017216976A1 (en) * 2016-06-17 2017-12-21 Nec Corporation Information processing method and device for neural network
CN108521858A (en) * 2016-12-30 2018-09-11 谷歌有限责任公司 The device identifier relevant operation processing of packet-based data communication

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR2817433A1 (en) * 2000-11-30 2002-05-31 Koninkl Philips Electronics Nv DATA TRANSMISSION SYSTEM INVOLVING A SERVER, STATION SUITABLE FOR SUCH A SYSTEM, AND METHOD FOR DOWNLOADING DATA
CN102984228B (en) * 2012-11-16 2017-04-19 Tcl集团股份有限公司 File sharing method and server and client terminal and file sharing system
CN103647588A (en) * 2013-11-19 2014-03-19 上海斐讯数据通信技术有限公司 Media file sharing method and system based on wireless transmission
CN111953714B (en) * 2019-05-14 2022-07-12 华为技术有限公司 File sharing method, communication device and storage medium

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017216976A1 (en) * 2016-06-17 2017-12-21 Nec Corporation Information processing method and device for neural network
CN108521858A (en) * 2016-12-30 2018-09-11 谷歌有限责任公司 The device identifier relevant operation processing of packet-based data communication

Also Published As

Publication number Publication date
CN112995333A (en) 2021-06-18

Similar Documents

Publication Publication Date Title
WO2020177533A1 (en) Electronic invoice identifier allocation method, and electronic ticket generating method, device and system
CN111934918B (en) Network isolation method and device for container instances in same container cluster
EP3837604B1 (en) In situ triggered function as a service within a service mesh
KR101413295B1 (en) DDS structure and node composing DDS with scalability and adaptability
CN107979520B (en) Message processing method and message processing device
US20020046304A1 (en) Dynamic class loading
CN108093098A (en) A kind of domain name mapping request sending method and device
US11843642B1 (en) Serverless signaling in peer-to-peer session initialization
CN111124589A (en) Service discovery system, method, device and equipment
CN111200606A (en) Deep learning model task processing method, system, server and storage medium
CN108664274A (en) Implementation method, system and the device of operating system initialization configuration
CN112104679B (en) Method, apparatus, device and medium for processing hypertext transfer protocol request
CN106357654B (en) Remote procedure calling method, device and communication system
CN109088918B (en) Interaction method, client device and server device
CN113220432B (en) Multi-cloud interconnection method, device, equipment, storage medium and product
CN114244654A (en) URL forwarding method, device, equipment and computer storage medium
CN108429665A (en) A kind of method of concurrent communication transmission data
CN112995333B (en) Remote file activation method, system and related device
CN115333933B (en) Automatic management method, medium and equipment for servers on machine room
CN115437810A (en) Rendering task processing method, device, equipment and medium
CN113452948B (en) Conference terminal control method, device, equipment and storage medium
US20140047014A1 (en) Network access system
CN111861432B (en) Virtual resource information updating method and device, server and storage medium
CN108289056A (en) Share the method, apparatus and computing device of dynamic chart
CN110300131B (en) Routing method, device, equipment and system for multiple services of wind power plant

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant