Patent classifications
H04L61/4553
METHOD FOR PROVIDING AND VALIDATING ALTERNATIVE OBJECT IDENTIFIERS AND FOR DETERMINING REFERENCES OF ALTERNATIVE OBJECT IDENTIFIERS WITHIN AN OPC-UA-BASED COMMUNICATION ENVIRONMENT
A method for providing alternative object identifiers for objects of an address space of a server within an OPC UA based communication environment, wherein each object of the address space of the server is uniquely identified by a conventional object identifier, wherein at least one additional identifier is defined and is stored in a directory of additional identifiers defined for this address space of the server, and wherein an alternative object identifier also uniquely identifying the object is formed for each object of the address space of the server, whereby the additional identifier is combined with the conventional object identifier of the respective object according to a determined pattern. Another method for validating alternative object identifiers and a method for determining references of object identifiers, as well as a server, a system, and a computer program product designed to carry out at least one of the methods.
Distributing and synchronizing objects
The described embodiments distribute and synchronize objects in a network. More specifically, the described embodiments distribute copies of objects locally (i.e., store copies of objects in local address spaces). By storing a copy of a given object in a local address space, the object's methods may be executed locally, which can help to avoid excessive network traffic associated with remotely executing the object's methods. However, executing an object's methods locally can result in the state of the object (i.e., data associated with the object, etc.) becoming out of sync with other copies of the object in the network. To avoid issues associated with unsynchronized copies of the object in the network, the described embodiments use a policy that specifies conditions under which objects are to be synchronized.
Communications using the common object request broker architecture (CORBA)
Communications using the common object request broker architecture (CORBA) is disclosed. The communications are between a first computing device and a second computing device separated by a NAT device. The first computing device issues a request conforming to the CORBA protocol to obtain an IOR for an object from the second computing device. A first request interceptor on the first device adds a public IP address of the second computing device as user-defined data in the request. A second request interceptor on the second computing device extracts the IP address from the request and stores it. The second computing device builds the IOR for the object including embedding the public IP address of the second computing device in the IOR. The second computing device sends the IOR to the first computing device. The first computing device then establishes a successful connection to the public IP address received in the IOR.
Method and apparatus for collecting data in network communication using concealed user address
A method and an apparatus for collecting data in a network communication are provided. The method includes receiving a request from a local application for a connection to a remote application using a first address which is assigned for Inter Process Communication (IPC) process corresponding to the local application, wherein the IPC process is performed on a Distributed IPC Facility (DIF) layer, storing a routing table that maps the first address of the local application in the DIF layer and an address of the remote application in a network layer, generating a connection between the local application and the remote application using the routing table to conceal a network layer address of the local application, and storing a communication data between the local application and the remote application using the first address of the local application.
Aliasing of named data objects and named graphs for named data networks
A method for aliasing of named data objects (in named data networks) and entities for named data networks (e.g., named graphs for named data networks). In various examples, aliasing of named data objects may be implemented in one or more named data networks in the form of systems, methods and/or algorithms. In other examples, named graphs may be implemented in one or more named data networks in the form of systems, methods and/or algorithms.
Objectclass versioning
Techniques for objectclass versioning in directory server schema are provided. The techniques include migrating from one version of a directory server to another version of the directory server, maintaining one or more versions of an objectclass while migrating from one version of a directory server to another version of the directory server, and selecting one of the one or more versions of an objectclass for normal functioning of an application.
Relay device, network system, and network control method
A network system according to the present invention includes: a server that provides a content to a communication terminal; a relay device that establishes a connection with the server; and a DNS server that stores an IP address of the server. When accepting an inquiry of the IP address of the server being a providing source of the content from the communication terminal, the relay device inquires the IP address from the DNS server, and performs in parallel processing of transmitting the IP address received in response to the inquiry to the communication terminal, and processing of establishing a connection with the server assigned the IP address.
Providing selective peer-to-peer monitoring using MBeans
Providing selective peer-to-peer monitoring using MBeans by providing a federation of peer-to-peer network servers based on the MBeans, and enabling each of the peer-to-peer networks servers to selectively monitor data associated with at least a subset of the peer-to-peer network servers using at least one of the MBeans.
SCALABLE AND ROBUST NETWORK MANAGEMENT FOR CLOUD-BASED NAT ENVIRONMENTS
Scalable, robust cloud-based network management systems (NMSs) are described. In one, an NMS includes a set of NMS applications, a pool of device communication managers (DCMs), and a pool of device operations managers (DOMs). Each of the DCMs and DOMs executed by the processors as software containers. The NMS includes an API gateway configured to route remote procedure calls (RPCs) from the DCMs to the DOMs via the APIs exposed by the DOMs and according to device identifiers of the managed elements. The DOMs are configured to establish a set of persistent application-layer communication sessions from the DOMs to the DCMs and to direct communications from the NMS applications to the DCMs over the persistent application-layer communication sessions according to a mapping between device identifiers associated with the managed elements and network addresses associated with the DCMs.
METHOD AND APPARATUS FOR COLLECTING DATA IN NETWORK COMMUNICATION USING CONCEALED USER ADDRESS
A method and an apparatus for collecting data in a network communication are provided. The method includes receiving a request from a local application for a connection to a remote application using a first address which is assigned for Inter Process Communication (IPC) process corresponding to the local application, wherein the IPC process is performed on a Distributed IPC Facility (DIF) layer, storing a routing table that maps the first address of the local application in the DIF layer and an address of the remote application in a network layer, generating a connection between the local application and the remote application using the routing table to conceal a network layer address of the local application, and storing a communication data between the local application and the remote application using the first address of the local application.