CN104780203A - Multi-point access method based on elastic cloud - Google Patents
Multi-point access method based on elastic cloud Download PDFInfo
- Publication number
- CN104780203A CN104780203A CN201510128857.6A CN201510128857A CN104780203A CN 104780203 A CN104780203 A CN 104780203A CN 201510128857 A CN201510128857 A CN 201510128857A CN 104780203 A CN104780203 A CN 104780203A
- Authority
- CN
- China
- Prior art keywords
- server
- communication
- client
- data
- service
- 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.)
- Pending
Links
Abstract
The invention relates to a multi-point access method based on an elastic cloud. A plurality of local area networks can be connected to realize data interaction among all nodes inside the elastic cloud. The multi-point access method comprises the following characteristics: a general standard communication protocol and an interface specification are adopted to meet a requirement of data interaction of different business systems, a communication layer is unrelated to an application; the general standard communication protocol and the interface specification are adopted to ensure that different applications are coordinated on a general communication bottom layer. A uniform communication module is provided for call: to unify the communication between a service system server end and a client end, the bottom layer communication module is used for realizing communication and is packaged together with some communication protocols, and a server end program and a client end program uniformly call the bottom layer communication modules and are connected and communicated by adopting a TCP long connection manner. The development of an application program focuses on realization of the function of the application program without considering realization of a communication part.
Description
Technical field
The present invention relates to a kind of multi-point access method based on elastic cloud.
Background technology
Along with the step that the information age constantly advances, IT application in enterprise also deepens continuously, and operation system quantity constantly increases, data interaction between each operation system, data interaction between each subservice system and core business system, the application demand of scene like this constantly occurs.And developing along with enterprise, also more and more higher to the requirement of these system communications, the system originally only applied at oneself internal lan may will expand to the Internet to use, such as original a set of Human Resources Management System just only uses in intra-company, along with the foundation of various places branch company, each branch company also needs to use this cover system and parent company also needs all data centralizations to unified management together, so this cover system just must be deployed to the Internet various places branch company could be allowed to access, and security consideration Network Based, it is inappropriate that inner privately owned Account Dept is deployed to the Internet, simultaneously because the consideration of network security, many enterprises, the isolation of intranet and extranet has all been done by government bodies etc., the access of intranet and extranet is provided in limited mode, also the scheme that this Intranet directly accesses outer net is not suitable for, this operation system just needing a kind of reliable and secure method allow and be in heterogeneous networks can carry out data interaction, namely connect each local area network (LAN) by the Internet, build one " private network ", in this " private network " scope, can not carry out the data interaction outside this network, but but can not by the restriction of intranet and extranet, carry out data interaction between the individual nodes, as long as access this " private network ", just can have access to any one node of this network internal, both fail safe is ensured like this, data interaction can not be carried out again by intranet and extranet restriction.
Numerous technology of current communication Network Based and product, although much all achieving intranet and extranet penetrates with Point-to-Point Data mutual, but substantially just single application, can not form such one " private network " can make the node of access network and other nodes carry out data interaction, and the node of access also can provide access port, form the elastic cloud of energy multiple spot access.
Summary of the invention
The present invention wants technical solution problem to be: the above-mentioned deficiency overcoming prior art, utilizes pure software technological means, provides a kind of multi-point access method based on elastic cloud, can connect the data interaction that multiple local area network (LAN) realizes between the inner each node of elastic cloud.
In order to solve above technical problem, a kind of multi-point access method based on elastic cloud provided by the invention, comprises following characteristics:
Adopt general standard communication protocol and interface specification: for meeting the data interaction of different business systems, Communication Layer must and be applied irrelevant, adopt general standard communication protocol and interface specification, so just can ensure that different being applied on general communication bottom is worked in coordination with.
Unified communication module is provided to supply to call: to be uniform traffic system server terminal, communication between client, bottom communication module encapsulates communication programming and some communications protocol, serve end program, client-side program equal unified call bottom communication module, adopts the long connected mode of TCP to carry out connecting and communication.Develop Application System without the need to considering the realization of communication part, can be absorbed in the realization of function own.
Deployment framework of the present invention comprises following part:
Client: the client of each operation system, must access elastic cloud and just can be connected to concrete business system server.
Communication server: route and the transfer of being responsible for data, ensures that the transfer of data energy arrives target machine, does not need database, can dispose easily and access elastic cloud, while access, also provide interface can accept the access of other communication servers and client.
Application server: service server, processes specific business, disposes the operation system of enterprise, provides various concrete application service.
Index server: connection management, be responsible for the index server of distributing user, client is known, and the business datum of oneself and which application server carry out alternately.Index server is actually application server, provides application and the addressing service of application server in network.Application server access network should provide log-on message to index server, namely oneself ID and provide what service.Such as application server 1 provides the service of making out an invoice on the net, application server 2 provides the interactive service of tax enterprise, concrete application server ID should be inquired about to index server after client's side link communication server, as tax look forward to interactive client just can inquire need with application server 2 carry out data interaction.Index server should be set to a fixing ID, as 127.0.0.1(ID, have nothing to do with real ip address), such client can connect any communication server, ID to 127.0.0.1 sends inquiry request, just can carry out data interaction with concrete application server after knowing the server ID of embody rule.Realize anywhere login and all may have access to respective application.
Because of serve end program equal unified call bottom communication module, Servers-all all has the function of communication server.
Service end must have a unique ID to identify, and this ID provides with IP address format, general consistent with the machine IP, but also can specify arbitrarily.Data retransmission between service end relies on this ID to carry out.Transmit leg client id is comprised in the packet header of the communication data packets of bottom communication module transfer, sender server ID, recipient's server ID, recipient's client id, according to originating server ID and destination server ID, middle data retransmission is completed by communication server.
For ensureing fail safe, the connection between server must have authorization identifying, is arranged by configuration file.Such as, must have ID and the password of logon server B in the configuration file of server A connection server B, A, also need ID and the authentication password of A in the configuration file of B, both mate and just can connect.
Connection between service end is specified by configuration file, and bottom communication module automatically connects other service ends according to the server address of specifying in configuration file and exchanges respective routing iinformation, and the data interaction forming server/customer end arbitrarily in network can reach.
Connection between server end can be configured to following 3 kinds of modes:
1, initiatively connect: service routine initiatively connects other servers after starting, and this is modal mode.
2, connection is accepted: service routine does not initiatively connect other servers after starting, but waits for the connection of other servers, is applicable to the server being positioned at the Internet.Due to the isolation of intranet and extranet, the server of Intranet can not be connected, can only wait for that the server of Intranet connects.
3, be bi-directionally connected: service routine initiatively connects other servers after starting, wait for the connection of this server simultaneously, namely have two SOCKET between server to connect, be applicable to the environment that network communication is ill-conditioned, when wherein a connection disconnects time, bottom communication module can use another to connect transmission data automatically.Due to network condition instability, may there is the situation that connection often disconnects, bottom communication module has disconnection detection and Auto-reconnect mechanism, when a connection disconnection reconnects time, another connection can be used to carry out transfer of data.
Data retransmission addressing mechanism between service end:
Server ID in the addressing forwarding dependence transmission data packet head of data and client id.Bottom communication module can add this data packet head at the packet of transmission automatically.Data packet head has 4 fields, specifies destination server ID, destination client ID, sender's server ID, sender's (client) ID.Given server ID and client id can be distinguished time client call bottom communication module sends data, wherein any one or both also can be specified all not to specify, following several situation can be divided into:
1, given server ID and client id: communication server forwards the data to given server, this server forwards the data to given client end again.The client of specifying must be connected to given server, otherwise data retransmission failure.
2, given client end ID: data are forwarded directly to given client end by communication server, this client must connecting communication server.This situation is the data interaction between the client of same service end.
3, given server ID: this server ID is generally the ID of application server, and communication server forwards the data to the server of specifying.
4, any server ID and client id is not specified: communication server forwards the data to the application server of default configuration.
The addressing of data retransmission is completed by bottom communication module, not dependency database, has come according to structure routing table during configuration file access elastic cloud when program starts.This routing table is made up of 3 fields:
Destination server ID, forwarding server ID, hop count.
In this routing table, destination server ID records the ID list of the destination server that all book servers can be forwarded to.Forwarding server ID must be then the ID of current other servers be connected with oneself.Hop count refers to and could arrive destination server by forwarding several times.
Consider with next scene: Li Si says king five: " I is familiar with Zhang San, and you will look for Zhang San just to look for me.", king five couples of Zhao six say: " I can find Zhang San, and you look for the words of Zhang San to look for me.", Zhao six says: " I has envelope to believe will to Zhang San, and you help me to bring him.", so king five gives Li Si letter, Li Si gives Zhang San letter again.The single-line link of Here it is underground worker.The addressing of data retransmission is similar to this, and every station server does not all know complete data forwarding paths, but knows correct routing direction.When a communication server accesses this network time, between the server that meeting is connected with oneself, carry out the exchange of routing table information.In time finding that routing table has variation, can give all servers be connected with oneself the message notice of variation, notify so layer by layer, the routing table of whole network just obtains renewal.
The structure of routing table:
When a communication server access network, after being connected by certification with other servers, bottom communication module will carry out the exchange of routing table information.The routing table information of oneself can be informed the communication server of connection, message format and routing table format are slightly distinguished, as following table:
| Forwarding server ID | Destination server quantity | Server ID | Server ID | . . . |
Being meant to of this routing table information: " I arrives following server by forwarding.", so only need forwarding server ID record, i.e. a local server ID in information, being then accessibility destination server quantity, is the ID list of destination server with that.The routing table update of oneself is just completed after receiving the communication server resolving information of message, then all servers be connected with oneself can be given the message notice upgraded, each server receiving information can be transmitted to all servers be connected with oneself again information after the routing table upgrading oneself, notify so layer by layer, in network, the routing table of Servers-all is obtained for correct renewal.
Accompanying drawing explanation
Below in conjunction with accompanying drawing, the present invention is further illustrated.
Fig. 1 is the network design example architecture of elastic cloud.
Fig. 2 is the routing table information of each server in Fig. 1.
Embodiment
Describe the present invention in detail with reference to the accompanying drawings below, be clearly and completely described the technical scheme in the embodiment of the present invention, how the detailed realization of data retransmission addressing and the routing table of each server build.Accompanying drawing example just technical scheme of the present invention and constructing for convenience of description, practical application is not necessarily identical with example.
In Fig. 1, each server has a unique ID mark, and this ID provides with IP form, as 0.0.0.1, but has nothing to do with the IP address of reality.ID can specify arbitrarily, but needs to ensure that be unique in the elastic cloud of server formation.Client equally also has unique ID mark, is arranged voluntarily by client-side program.Server in elastic cloud, between client, data interaction carrys out by ID the forwarding that addressing route carries out data, do not rely on actual IP address (physical machine only accessing elastic cloud needs to know that the IP address of access point is to access elastic cloud).
Suppose that in Fig. 2, customer end B has accessed elastic cloud by connecting communication server D, need the data of asking certain operation system, need to arrive first the server ID that index server inquires about this operation system place, communication server D will look into oneself routing table, destination server is index server, forward the data to communication server E, communication server E looks into oneself routing table, forward the data to communication server C, communication server C forwards the data to communication server B, communication server B forwards the data to communication server A, communication server A finally forwards the data to index server.Index server receives data, the operation system of client-requested is obtained at application server 3 by inquiry, after completing process, result data is beamed back client, according to the sender's server ID in data packet head, sender's (client) ID locates, look into the routing table of oneself equally, the data of communication server D are forwarded to communication server A, again by A->B->C->E-Gre atT.GreaT.GTD-> customer end B, complete once complete data interaction.
Customer end B knows that the operation system of oneself is after application server 3, just no longer need to produce data interaction with index server, only concrete service request data need be sent to communication server D, in like manner arrive application server 3 by the path of D->E->C-> application server 3, by the path of C->E->D-> customer end B, result data is beamed back customer end B after application server 3 completes data processing, the data interaction of finishing service system.
Routing table building process the following detailed description of server each in Fig. 2:
Suppose that in Fig. 2, communication server D accesses elastic cloud, connect with communication server E, E will inform D the routing table information of oneself, and message format is as follows:
| Forwarding server ID | Destination server quantity | Server ID | Server ID | . . . |
Because E tells that the information of D is: " I arrives following server by forwarding.", so only need forwarding server ID record, i.e. a server ID of E in information, being then accessibility destination server quantity, is the ID list of destination server with that.The routing table completing oneself is just built: application server 1,2,3, communication server A, B, C, E, the data of index server are all be forwarded to E after D resolving information.
The routing table information of the D that E receives only has one, the data retransmission being exactly D, to D, after being joined the routing table update of oneself, can give all servers be connected with oneself (except D the message notice upgraded, because carry out routing table information exchange), info class is like following table:
| The ID(of communication server E forwards target) | The ID (final goal) of communication server D | 1 (hop count) |
In Fig. 2, communication server C and E connects, and knows that the data of communication server D will be forwarded to E after C resolving information, after upgrading routing table, lastest imformation is sent to application server 3 and communication server B:
| The ID(of communication server C forwards target) | The ID (final goal) of communication server D | 2 (hop counts) |
Each server receiving information can replace with first character section in information (forwarding server ID) oneself ID after upgrading oneself routing table, and then be transmitted to all servers be connected with oneself, notify so layer by layer, in network, the routing table of Servers-all is obtained for correct renewal.
The winding process of routing table:
Server in Fig. 2 is all linearly connected, do not form winding, if communication server D is connected with communication server A again in figure, communication server A, B, C, D, E just constitutes a winding, at this moment communication server A will receive two routing iinformations to server D, article one, be that D sends, D->D, article one, be that B sends, D->B, article one, forward-path is forwarded directly to D, another paths is B->C->E->D, optimum forward-path is obviously D->D.Form winding, each information in routing table all will be upgraded, the routing table of oneself has been upgraded after D connection E, connect A again, the information being not only D of notice A, also has the routing iinformation of " Servers-all is all forwarded by D ", A will receive the routing iinformation of E->D, how to judge which bar circuit is optimum with oneself existing routing table information E->B, because server does not know complete forward-path, the hop count field in routing table information can only be relied on.
In illustrating above seeing, D is connected to the example of E again, E receives the information of D->D, hop count is 1, then by hop count+1, the message notice of D->E is to C, C equally by the message notice of hop count+1, D->C to application server 3 and communication server B, the routing table information of last A will be listed in Table:
| Destination server | Forwarding server | Hop count |
| Application server 1 | Application server 1 | 1 |
| Application server 2 | Communication server B | 2 |
| Application server 3 | Communication server B | 3 |
| Communication server B | Communication server B | 1 |
| Communication server C | Communication server B | 2 |
| Communication server D | Communication server B | 4 |
| Communication server E | Communication server B | 3 |
| Index server | Index server | 1 |
When D connects A again, A receives and the routing iinformation parsed will be following table:
| Destination server | Forwarding server | Hop count |
| Application server 1 | Communication server D | 6 |
| Application server 2 | Communication server D | 5 |
| Application server 3 | Communication server D | 4 |
| Communication server B | Communication server D | 4 |
| Communication server C | Communication server D | 3 |
| Communication server D | Communication server D | 1 |
| Communication server E | Communication server D | 2 |
| Index server | Communication server D | 6 |
In the routing table that D provides, only have the hop count of D and E fewer than the hop count in oneself routing table, therefore the A information that two information updatings of this in routing table will be provided for D, again by the hop count+1 of these two information, the ID that forwarding server ID changes oneself into informs the application server 1 be connected with oneself, communication server B and index server, other servers are action like this also, and the routing table of such Servers-all all upgrades in order to the shortest forward-path.A is when upgrading the Shortest path routing of oneself, routing iinformation is not originally deleted, but as standby message, the afterbody of shortest route is added on chain sheet form, connection like this between D and A disconnects, A deletes the route of D->D, the former routing iinformation of D->B can be replaced, still can carry out information interaction between A and D.
The dissection process process that more than just routing table information is basic, add that the operation of routing table is deleted in server disconnection, in fact routine processes gets up to want complicated many, upgrade routing table and also not only upgrade shortest path, long path is needed also to record as backup path, reinform other servers, also will prevent the detailed problems such as the unlimited winding transmission of routing iinformation from needing process.
The process of data mass-sending:
When needs mass-sending data time, such as similar operation system sends to the notification message of all clients, the group chat information of similar QQ, owing to may need through data retransmission, data Replica n part sent, so transfer process will significant wastage bandwidth, and therefore system is designed to interim data only, after destination server, be distributed to client again, need this to do special processing.First, as information sender, application server needs the client of the information of reception by place classification server, the user of all reception information adheres to (connection) n server separately, needs to be divided into n group, then often will organize user place server ID, user ID list, the information content, size carries out message transmission as parameter call bottom communication module, sends n bar data altogether.
Then bottom communication module is by destination server, and the information such as user list and data package, and data are sent to destination server.
Ideal server receives information, parses user list, by Data dissemination to client.
Such as client 1,2,3 are connected to communication server A, client 4,5,6 are connected to communication server D, application server 1 will generate two packets and be distributed to communication server A and D respectively, be sent to the ID list of the data band client 1,2,3 of A, be sent to the data band client 4 of B, the ID list of 5,6, communication server A with D after receiving bag respectively by Data dissemination to being connected oneself client.Such data between servers transfer time data volume minimum, also improve efficiency of transmission.
In addition to the implementation, the present invention can also have other execution modes.All employings are equal to the technical scheme of replacement or equivalent transformation formation, all drop on the protection range of application claims.
Claims (5)
1., based on a multi-point access method for elastic cloud, it is characterized in that:
Adopt general standard communication protocol and interface specification: for meeting the data interaction of different business systems, Communication Layer must and be applied irrelevant, adopts general standard communication protocol and interface specification, ensures that different being applied on general communication bottom is worked in coordination with;
Unified communication module is provided to supply to call: to be uniform traffic system server terminal, communication between client, bottom communication module encapsulates communication programming and some communications protocol, serve end program, client-side program equal unified call bottom communication module, adopts the long connected mode of TCP to carry out connecting and communication;
Dispose framework and comprise following part:
Client: the client of each operation system, access elastic cloud just can be connected to concrete business system server;
Communication server: route and the transfer of being responsible for data, ensures that the transfer of data energy arrives target machine, does not need database, can dispose easily and access elastic cloud, while access, also provide interface can accept the access of other communication servers and client;
Application server: service server, processes specific business, disposes the operation system of enterprise, provides various concrete application service;
Index server: connection management, be responsible for the index server of distributing user, client is known, and the business datum of oneself and which application server carry out alternately, application and the addressing service of application server in network are provided, application server access network should provide log-on message to index server, namely oneself ID and provide what service;
Service end has a unique ID to identify, and this ID provides with IP address format, and the data retransmission between service end relies on this ID to carry out; Transmit leg client id is comprised in the packet header of the communication data packets of bottom communication module transfer, sender server ID, recipient's server ID, recipient's client id, according to originating server ID and destination server ID, middle data retransmission is completed by communication server;
Connection between service end is specified by configuration file, and bottom communication module automatically connects other service ends according to the server address of specifying in configuration file and exchanges respective routing iinformation, and the data interaction forming server/customer end arbitrarily in network can reach.
2. the multi-point access method based on elastic cloud according to claim 1, is characterized in that: the connection between described server end can be configured to following 3 kinds of modes:
1, initiatively connect: service routine initiatively connects other servers after starting, and this is modal mode;
2, connection is accepted: service routine does not initiatively connect other servers after starting, but wait for the connection of other servers, be applicable to the server being positioned at the Internet, due to the isolation of intranet and extranet, the server of Intranet can not be connected, can only wait for that the server of Intranet connects;
3, be bi-directionally connected: service routine initiatively connects other servers after starting, wait for the connection of this server simultaneously, namely have two SOCKET between server to connect, be applicable to the environment that network communication is ill-conditioned, when wherein a connection disconnects time, bottom communication module can use another to connect transmission data automatically; Due to network condition instability, may there is the situation that connection often disconnects, bottom communication module has disconnection detection and Auto-reconnect mechanism, when a connection disconnection reconnects time, another connection can be used to carry out transfer of data.
3. the multi-point access method based on elastic cloud according to claim 2, is characterized in that: the data retransmission addressing mechanism between described service end is as follows:
Server ID in the addressing forwarding dependence transmission data packet head of data and client id, bottom communication module can add this data packet head at the packet of transmission automatically, data packet head has 4 fields, specify destination server ID, destination client ID, sender's server ID, sender's (client) ID.
4. the multi-point access method based on elastic cloud according to claim 1, is characterized in that: when described client call bottom communication module sends data, be divided into following several situation:
1, given server ID and client id: communication server forwards the data to given server, this server forwards the data to given client end again, and the client of specifying must be connected to given server, otherwise data retransmission failure;
2, given client end ID: data are forwarded directly to given client end by communication server, this client must connecting communication server, and this situation is the data interaction between the client of same service end;
3, given server ID: this server ID is generally the ID of application server, and communication server forwards the data to the server of specifying;
4, any server ID and client id is not specified: communication server forwards the data to the application server of default configuration.
5. the multi-point access method based on elastic cloud according to claim 4, it is characterized in that: the addressing of data retransmission is completed by bottom communication module, not dependency database, come according to structure routing table during configuration file access elastic cloud when program starts, this routing table is made up of 3 fields:
Destination server ID, forwarding server ID, hop count;
In this routing table, destination server ID records the ID list of the destination server that all book servers can be forwarded to; Forwarding server ID must be then the ID of current other servers be connected with oneself; Hop count refers to and could arrive destination server by forwarding several times.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510128857.6A CN104780203A (en) | 2015-03-23 | 2015-03-23 | Multi-point access method based on elastic cloud |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510128857.6A CN104780203A (en) | 2015-03-23 | 2015-03-23 | Multi-point access method based on elastic cloud |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN104780203A true CN104780203A (en) | 2015-07-15 |
Family
ID=53621437
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510128857.6A Pending CN104780203A (en) | 2015-03-23 | 2015-03-23 | Multi-point access method based on elastic cloud |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104780203A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105978974A (en) * | 2016-05-13 | 2016-09-28 | 捷开通讯科技(上海)有限公司 | Electronic device connecting system and method |
| CN107360205A (en) * | 2016-05-09 | 2017-11-17 | 阿里巴巴集团控股有限公司 | The transmission method and device of data message, system |
| CN114301915A (en) * | 2021-12-28 | 2022-04-08 | 武汉杰创达科技有限公司 | Cloud commerce platform commodity information processing method |
-
2015
- 2015-03-23 CN CN201510128857.6A patent/CN104780203A/en active Pending
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107360205A (en) * | 2016-05-09 | 2017-11-17 | 阿里巴巴集团控股有限公司 | The transmission method and device of data message, system |
| CN107360205B (en) * | 2016-05-09 | 2020-12-29 | 阿里巴巴集团控股有限公司 | Data message transmission method, device and system |
| CN105978974A (en) * | 2016-05-13 | 2016-09-28 | 捷开通讯科技(上海)有限公司 | Electronic device connecting system and method |
| CN114301915A (en) * | 2021-12-28 | 2022-04-08 | 武汉杰创达科技有限公司 | Cloud commerce platform commodity information processing method |
| CN114301915B (en) * | 2021-12-28 | 2024-02-20 | 武汉杰创达科技有限公司 | Commodity information processing method of cloud business platform |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102594711B (en) | Message forwarding method and edge device therefor | |
| US20200059976A1 (en) | IoT DEVICE CONNECTIVITY, DISCOVERY, AND NETWORKING | |
| EP2583415B1 (en) | Method, diameter node, and computer readable medium for providing dynamic origination-based routing key registration in a diameter network | |
| CN102754409B (en) | For the method for Diameter protocol harmonization, system and computer-readable medium | |
| CN105634956B (en) | A kind of message forwarding method, device and system | |
| JP4479647B2 (en) | Route generation system, route generation method, route management server, relay device, terminal device, and control program | |
| CN110601906B (en) | Data transmission method and device based on block chain | |
| CN103036784A (en) | Methods and apparatus for a self-organized layer-2 enterprise network architecture | |
| CN103475750A (en) | Address translation method and equipment suitable for multi-export network | |
| CN104980427A (en) | System And Method For Simple Service Discovery In Content-centric Networks | |
| CN102055816A (en) | Communication method, business server, intermediate equipment, terminal and communication system | |
| CN103067416A (en) | Virtual private cloud (VPC) access authentication method and correlation apparatus | |
| CN102739497A (en) | Automatic generation method for routes and device thereof | |
| CN102739541A (en) | Method, device and system for starting routing function and transmitting data | |
| WO2015108106A1 (en) | Packet transfer device, control device, communication system, communication method, and program | |
| CN104094243A (en) | Information processing apparatus, information processing method and program | |
| CN104980484A (en) | System and method for device registration and discovery in content-centric networks | |
| CN109586958A (en) | The configuring management method and dual system device of dual system device | |
| CN103561122B (en) | IPv6 address collocation method, IPv6 client and server | |
| CN109257392A (en) | A kind of command handling method, device, server and storage medium | |
| CN104780203A (en) | Multi-point access method based on elastic cloud | |
| CN108966363A (en) | A kind of connection method for building up and device | |
| CN101766007A (en) | Methods and systems for providing racf configuration information | |
| CN108234165A (en) | A kind of method and apparatus that gateway is configured | |
| WO2022160864A1 (en) | Network access method and apparatus for intelligent device, and intelligent device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20150715 |
|
| WD01 | Invention patent application deemed withdrawn after publication |