CN104735106A - Node transmission method and device - Google Patents
Node transmission method and device Download PDFInfo
- Publication number
- CN104735106A CN104735106A CN201310714273.8A CN201310714273A CN104735106A CN 104735106 A CN104735106 A CN 104735106A CN 201310714273 A CN201310714273 A CN 201310714273A CN 104735106 A CN104735106 A CN 104735106A
- Authority
- CN
- China
- Prior art keywords
- node
- device type
- nat device
- identification
- node identification
- 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
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/10—Protocols in which an application is distributed across nodes in the network
- H04L67/104—Peer-to-peer [P2P] networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/25—Mapping addresses of the same type
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a node transmission method and device. The method comprises the steps that a server acquires identifiers of request data carried by a node list acquisition request message requesting for node transmission and acquires all node identifiers containing the request data from all nodes administrated locally to generate a first node set; the server acquires NAT device types corresponding to all the node identifiers in the first node set, screens out the node identifiers matched with the NAT device types corresponding to request nodes from the first node set and generates a node list based on all the node identifiers obtained based on screening; the server transmits the node list to the request nodes. By means of the technical scheme, the server screens out the node identifiers containing the request data of the request nodes and acquires the node list which is best matched with the request nodes accordingly, and consumption of system resources is effectively lowered.
Description
Technical field
The present invention relates to communication technical field, particularly relate to a kind of node sending method and device.
Background technology
Along with the develop rapidly of multimedia technology, various ways can be adopted to carry out transmission and the broadcasting of Streaming Media, wherein, P2P(Peer to Peer; Point-to-point) stream media system is a kind of conventional streaming media and Play System.
In existing point-to-point stream media system, streaming medium content is cut into multiple data block (chunk), using each data block as the base unit of transmission of flow media data, thus complete continuous print data flow and transmit between node (Peer), wherein, each data block is identified by unique chunk id.Sharing and exchanging the buffered message (being called for short BM) all depending on the description node buffer status exchanged between node of programme content, namely completes sharing of programme content by buffered message and exchanges.
In above-mentioned point-to-point stream media system, when there is any requesting node for obtaining data to other nodes, namely request message can be obtained to the list of server sending node, server obtains request message according to this node listing and determines local all nodes having above-mentioned data of administering, and be sent to above-mentioned any requesting node based on the nodal information generation node listing determined, then this requesting node can according to this node listing, to the node requests data having above-mentioned data; Wherein, if data are made up of data slot, then " have the node of data ", refer to the node having the some or all of data slot that data comprise.
In point-to-point stream media system, server can directly and each node carry out information interaction, also can by NAT(Network Address Translation; The network address exchanges) network address of each node of equipment control, realize the information interaction between server and each node by this NAT device.NAT device is divided into following several different type, i.e. full cone (Full Cone), restriction taper (RestrictedCone), Port Restricted Cone (Port Restricted Cone), and symmetric form (Symmetric).In addition, in above-mentioned point-to-point stream media system, also there is NAT device type corresponding to node for without NAT device, this node can directly and server carry out information interaction, and need not NAT device be passed through.
At present, when the node listing of requesting node acquisition request institute request msg, due to server None-identified NAT device type, the node listing of the multiple node compositions under therefore different NAT device types being administered all is sent to requesting node.The characteristic corresponding due to different N AT device type is all not identical, causes, between the node under the administration of different N AT device type, may there is the problem cannot carrying out information interaction.Therefore, if do not screen the node in node listing and directly this node listing be sent to requesting node, the request msg that in above-mentioned node listing, part of nodes has cannot be obtained by causing requesting node, wherein, the NAT device type that this part of nodes the is corresponding NAT device type corresponding with requesting node is not mated.Now, ability obtaining request data after requesting node may need to send data request information to all nodes in above-mentioned node listing, namely need more signaling consumption could obtain request msg, thus considerably increase system resources consumption.
As can be seen here, in point-to-point stream media system, presence server cannot obtain the node listing mated most with requesting node, causes the problem that system resources consumption is large.
Summary of the invention
The embodiment of the present invention provides a kind of node sending method and device, in order to solve in prior art in point-to-point stream media system, exists because server cannot obtain the node listing mated most with requesting node, causes the problem that system resources consumption is large.
The concrete technical scheme that the embodiment of the present invention provides is as follows:
A kind of node sending method, is applied in point-to-point stream media system, comprises:
Server receives the node listing acquisition request message that requesting node sends, and the request msg mark of carrying in request message is obtained according to described node listing, in all nodes of this locality administration, determine the node identification of all nodes having request msg corresponding to described request Data Identification, generate first node set;
Described server determines the network address translation device type that in described first node set, each node identification is corresponding, and from described first node set, screen the node identification of the corresponding NAT device type NAT device type matching corresponding with the described request node that described server this locality is preserved, based on the information generation node listing of all node identifications that screening obtains;
Described node listing is sent to described request node by described server.
Optionally, described server receives first of the node transmission that in described first node set, each node identification is corresponding and detects packet; The local ip address that the node carried in the first detection packet that the node that described server is corresponding according to each node identification in described first node set respectively sends is corresponding and local IP port, generate each first response data packet, and send corresponding first response data packet to the node that each node identification in described first node set is corresponding; Described server is determined to meet NAT device type corresponding to first pre-conditioned each node identification for without NAT device type in described first node set; Wherein, to meet the described first pre-conditioned local local internet protocol IP address of preserving of node referring to that the local ip address that carries in described first response data packet that node corresponding to node identification receives is corresponding with local IP port and node identification identical with local IP port for node identification.
Optionally, when there is any node identification in described first node set, the local ip address that node this locality that described any node identification is corresponding is preserved and local IP port, with the local ip address carried in described first response data packet and local IP port incomplete same time, described server receives second of the node transmission that in described first node set, any node identification is corresponding and detects packet, and generate the second response data packet according to described second detection packet, and send described second response data packet to the node that described any node identification is corresponding, wherein, the public network address of the described server carried in described second detection packet is different from the public network address of the described server carried in described second response data packet, and the port address of the described server carried in described second detection packet is different from the port address of the described server carried in described second response data packet, when described server judges that the node that described any node identification is corresponding receives described second response data packet, determine that the NAT device type that described any node identification is corresponding is full cone NAT device type.
Optionally, when there is any node identification in described first node set, the local ip address that node this locality that described any node identification is corresponding is preserved and local IP port, with the local ip address carried in described first response data packet and local IP port incomplete same time, if described server determines that the node that described any node identification is corresponding does not receive described second response data packet, then described server receives the 3rd detection packet that node corresponding to described any node identification sends, detect packet according to the described 3rd and generate the 3rd response data packet, and send described 3rd response data packet to the node that described any node identification is corresponding, and described server receives the 4th detection packet of node transmission corresponding to described any node identification, and detect packet generation the 4th response data packet according to the described 4th, and send described 4th response data packet to the node that described any node identification is corresponding, wherein, the public network address of the described server carried in described 3rd detection packet and port address, different all different with port address from the public network address of the described server carried in described 4th response data packet, it is different that described server judges that node that described any node identification is corresponding meets the public network address of the public network address of node corresponding to described any node identification of carrying in the described 3rd response data packet node corresponding from any node identification carried in described 4th response data packet, or when the port address of the node that the port address of the node that the described any node identification carried in described 3rd response data packet is corresponding is corresponding from any node identification carried in described 4th response data packet is different, determine that the NAT device type that described any node is corresponding is symmetric NAT equipment class.
Optionally, when there is any node identification in described first node set, the local ip address that node this locality that described any node identification is corresponding is preserved and local IP port, with the local ip address carried in described first response data packet and local IP port incomplete same time, described server receives the 5th detection packet that node corresponding to described any node identification sends, and detect packet generation the 5th response data packet according to the described 5th, and send described 5th response data packet to the node that described any node identification is corresponding; Wherein, the public network address of the described server carried in described 5th detection packet is identical with the public network address of the described server carried in described 5th response data packet, and the port address of the described server carried in described 5th detection packet is different from the port address of the described server carried in described 5th response data packet; When described server judges that the node that described any node identification is corresponding receives described second response data packet, determine that the NAT device type that described any node is corresponding is restriction taper NAT device type.
Optionally, when there is any node identification in described first node set, the local ip address that node this locality that described any node identification is corresponding is preserved and local IP port, with the local ip address carried in described first response data packet and local IP port incomplete same time, if described server judges that the node that described any node identification is corresponding does not receive described 5th response data packet in preset duration, then determine that the NAT device type that described any node identification is corresponding is Port Restricted Cone NAT device type.
Optionally, when described request node is without NAT device type node, from described first node set, screening is without node identification, the node identification of full cone NAT device type node, the node identification of restriction taper NAT device type node, the node identification of Port Restricted Cone NAT device type node of NAT device type node, and the node identification of symmetric NAT device type node, as the node identification of the NAT device type matching corresponding with described request node; When described request node is full cone NAT device type node, from described first node set, screening is without node identification, the node identification of full cone NAT device type node, the node identification of restriction taper NAT device type node, the node identification of Port Restricted Cone NAT device type node of NAT device type node, and the node identification of symmetric NAT device type node, as the node identification of the NAT device type matching corresponding with described request node; When described request node is for restriction taper NAT device type node, from described first node set screening without the node identification of NAT device type node, full cone NAT device type node node identification, limit the node identification of taper NAT device type node and the node identification of Port Restricted Cone NAT device type node, as the node identification of the NAT device type matching corresponding with described request node; When described request node is Port Restricted Cone NAT device type node, from described first node set, screening is without node identification, the node identification of full cone NAT device type node, the node identification of restriction taper NAT device type node of NAT device type node, and the node identification of Port Restricted Cone NAT device type node, as the node identification of the NAT device type matching corresponding with described request node; When described request node is symmetric NAT device type node, from described first node set, screening is without the node identification of NAT device type node, and the node identification of full cone NAT device type node, as the node identification of the NAT device type matching corresponding with described request node.
A kind of node dispensing device, is applied in point-to-point stream media system, comprises:
First generation unit, the node listing sent for receiving requesting node obtains request message, and the request msg mark of carrying in request message is obtained according to described node listing, in all nodes of this locality administration, determine the node identification of all nodes having request msg corresponding to described request Data Identification, generate first node set;
Second generation unit, for the network address translation device type determining that in described first node set, each node identification is corresponding, and from described first node set, screen the node identification of the corresponding NAT device type NAT device type matching corresponding with the described request node that this locality is preserved, based on the information generation node listing of all node identifications that screening obtains;
Transmitting element, for being sent to described request node by described node listing.
Optionally, described second generation unit, specifically for: receive the node transmission that in described first node set, each node identification is corresponding first detects packet; What send according to each node in described first node set respectively first detects in packet local ip address corresponding to the node that carries and local IP port, generate each first response data packet, and send corresponding first response data packet to the node that each node identification in described first node set is corresponding; Determine to meet NAT device type corresponding to first pre-conditioned each node identification for without NAT device type in described first node set; Wherein, to meet the described first pre-conditioned local local internet protocol IP address of preserving of node referring to that the local ip address that carries in described first response data packet that node corresponding to node identification receives is corresponding with local IP port and node identification identical with local IP port for node identification.
Optionally, described second generation unit, also for: when there is any node identification in described first node set, the local ip address that node this locality that described any node identification is corresponding is preserved and local IP port, with the local ip address carried in described first response data packet and local IP port incomplete same time, receive the second detection packet that any node in described first node set sends, and generate the second response data packet according to described second detection packet, and send described second response data packet to the node that described any node identification is corresponding, wherein, the local public network address carried in described second detection packet is different from the local public network address carried in described second response data packet, and the local port address of carrying in described second detection packet is different from the local port address of carrying in described second response data packet, when judging that the node that described any node identification is corresponding receives described second response data packet, determine that the NAT device type that described any node identification is corresponding is full cone NAT device type.
Optionally, described second generation unit, also for: when there is any node identification in described first node set, the local ip address that node this locality that described any node identification is corresponding is preserved and local IP port, with the local ip address carried in described first response data packet and local IP port incomplete same time, if determine, the node that described any node identification is corresponding does not receive described second response data packet, then receive the 3rd detection packet that node corresponding to described any node identification sends, detect packet according to the described 3rd and generate the 3rd response data packet, and send described 3rd response data packet to the node that described any node identification is corresponding, and receive the 4th detection packet of node transmission corresponding to described any node identification, and detect packet generation the 4th response data packet according to the described 4th, and send described 4th response data packet to the node that described any node identification is corresponding, wherein, the described 3rd detects the local public network address and port address that carry in packet, different all different with port address from the local public network address carried in described 4th response data packet, judge that described any node identification meets the public network address of the public network address of node corresponding to described any node identification of carrying in the described 3rd response data packet node corresponding from any node identification carried in described 4th response data packet different, or when the port address of the node that the port address of the node that the described any node identification carried in described 3rd response data packet is corresponding is corresponding from any node identification carried in described 4th response data packet is different, determine that the NAT device type that described any node identification is corresponding is symmetric NAT device type.
Optionally, described second generation unit, also for: when there is any node identification in described first node set, the local ip address that node this locality that described any node identification is corresponding is preserved and local IP port, with the local ip address carried in described first response data packet and local IP port incomplete same time, receive the 5th detection packet that node corresponding to described any node identification sends, and detect packet generation the 5th response data packet according to the described 5th, and send described 5th response data packet to the node that described any node identification is corresponding, wherein, the public network address of this locality of carrying in described 5th detection packet is identical with the public network address of this locality of carrying in described 5th response data packet, and the local port address of carrying in described 5th detection packet is different from the local port address of carrying in described 5th response data packet, when judging that the node that described any node identification is corresponding receives described second response data packet, determine that the NAT device type that described any node identification is corresponding is restriction taper NAT device type.
Optionally, described second generation unit, also for: when there is any node identification in described first node set, the local ip address that node this locality that described any node identification is corresponding is preserved and local IP port, with the local ip address carried in described first response data packet and local IP port incomplete same time, the node that described any node identification is corresponding if judge does not receive described 5th response data packet in preset duration, then determine that the NAT device type that described any node identification is corresponding is Port Restricted Cone NAT device type.
Optionally, described second generation unit, specifically for: when described request node is without NAT device type node, from described first node set, screening is without node identification, the node identification of full cone NAT device type node, the node identification of restriction taper NAT device type node, the node identification of Port Restricted Cone NAT device type node of NAT device type node, and the node identification of symmetric NAT device type node, as the node identification of the NAT device type matching corresponding with described request node; When described request node is full cone NAT device type node, from described first node set, screening is without node identification, the node identification of full cone NAT device type node, the node identification of restriction taper NAT device type node, the node identification of Port Restricted Cone NAT device type node of NAT device type node, and the node identification of symmetric NAT device type node, as the node identification of the NAT device type matching corresponding with described request node; When described request node is for restriction taper NAT device type node, from described first node set screening without the node identification of NAT device type node, full cone NAT device type node node identification, limit the node identification of taper NAT device type node and the node identification of Port Restricted Cone NAT device type node, as the node identification of the NAT device type matching corresponding with described request node; When described request node is Port Restricted Cone NAT device type node, from described first node set, screening is without node identification, the node identification of full cone NAT device type node, the node identification of restriction taper NAT device type node of NAT device type node, and the node identification of Port Restricted Cone NAT device type node, as the node identification of the NAT device type matching corresponding with described request node; When described request node is symmetric NAT device type node, from described first node set, screening is without the node identification of NAT device type node, and the node identification of full cone NAT device type node, as the node identification of the NAT device type matching corresponding with described request node.
In the embodiment of the present invention, the node listing that server sends according to requesting node obtains request message, obtain requesting node institute request msg mark, in all nodes of this locality administration, obtain all node identifications having above-mentioned request msg, generate first node set; Server obtains the NAT device type that in above-mentioned first node set, each node identification is corresponding, and from this first node set, screening the node identification of the NAT device type matching corresponding with requesting node, all node identifications obtained based on screening generate node listings; Above-mentioned node listing is sent to requesting node by server.Adopt technical solution of the present invention, the NAT device type that server is corresponding according to requesting node, and the NAT device type that each node identification having requesting node institute request msg is corresponding, the all node identifications having requesting node institute request msg are screened, thus obtain the node listing mated most with requesting node, ensure that the reliability that nodal information that requesting node is corresponding with each node identification in node listing is mutual, effectively save system resources consumption.
Accompanying drawing explanation
Fig. 1 is point-to-point Frame of Streaming Media System figure in the embodiment of the present invention;
Fig. 2 is embodiment of the present invention interior joint transmission flow schematic diagram;
Fig. 3 is embodiment of the present invention interior joint dispensing device structural representation.
Embodiment
In order to solve in prior art in point-to-point stream media system, exist because server cannot obtain the node mated most with requesting node, causing the problem that system resources consumption is large.In the embodiment of the present invention, the node listing that server sends according to requesting node obtains request message, obtain requesting node institute request msg mark, in all nodes of this locality administration, obtain all node identifications having above-mentioned request msg, generate first node set; Server obtains the NAT device type that in above-mentioned first node set, each node identification is corresponding, and from this first node set, screening the node identification of the NAT device type matching corresponding with requesting node, all node identifications obtained based on screening generate node listings; Above-mentioned node listing is sent to requesting node by server.Adopt technical solution of the present invention, the NAT device type that server is corresponding according to requesting node, and the NAT device type that each node identification having requesting node institute request msg is corresponding, the all node identifications having requesting node institute request msg are screened, thus obtain the node listing mated most with requesting node, ensure that the reliability that nodal information that requesting node is corresponding with each node identification in node listing is mutual, effectively save system resources consumption.
The embodiment of the present invention is applied in point-to-point stream media system, consult and Figure 1 shows that point-to-point stream media system structural representation in the embodiment of the present invention, wherein, server is comprised in this point-to-point stream media system, multiple requesting node and the multiple nodes that have requesting node institute request msg corresponding with each requesting node, the plurality of node can directly and server carry out information interaction, also can carry out information interaction by NAT device and server.Below only to comprise a requesting node in point-to-point stream media system, by reference to the accompanying drawings the preferred embodiment of the present invention is described in detail.
Consult shown in Fig. 2, in the embodiment of the present invention, the detailed process of server sending node list is:
Step 200: server receives the node listing acquisition request message that requesting node sends, and the request msg mark of carrying in request message is obtained according to above-mentioned node listing, in all nodes of this locality administration, obtain the node identification of all nodes having request msg corresponding to above-mentioned request msg mark, generate first node set.
In the embodiment of the present invention, node listing obtains the request msg mark of carrying in request message, and the NAT device type that requesting node is corresponding, wherein, the NAT device type that this requesting node is corresponding is without NAT device type (consulting Fig. 1 node A), or full cone NAT device type, or symmetric NAT device type, or restriction taper NAT device type, or Port Restricted Cone NAT device type.
Step 210: the NAT device type that in the set of server determination first node, each node identification is corresponding, and from first node set, screen the node identification of the corresponding NAT device type NAT device type matching corresponding with the requesting node that server this locality is preserved, based on the information generation node listing of all node identifications that screening obtains.
In the embodiment of the present invention, because the NAT device type that node is corresponding comprises five kinds of situations, therefore, the decision process of server to above-mentioned five kinds of NAT device types is respectively:
The first situation: server receives first of the transmission that in first node set, each node identification is corresponding and detects packet; The first detection packet that the node that server is corresponding according to each node identification in first node set respectively sends generates the first response data packet, and sends corresponding first response data packet to the node that each node identification in first node set is corresponding; The NAT device type meeting first pre-conditioned each node identification corresponding in the set of server determination first node is without NAT device type; Wherein, to meet the local ip address preserved the local ip address that carries in the first response data packet that the first pre-conditioned node referring to that node identification is corresponding receives node this locality corresponding with local IP port and node identification identical with local IP port for node identification; To be server generate based on local ip address corresponding to first each node identification detected in the first node set of carrying in packet and local IP port its first response data packet.When any node is without NAT device type node, this any node can not pass through NAT device, and directly and server carry out information interaction.
Such as, there is node identification a in first node set, the local ip address that this node identification a corresponds to node A, this node A is localIP1, and local IP port is localPort1, should (localIP1, localPort1) be distributed by the operating system of node A.Server binds two public networks, public network address and the public network port of two bound public networks are respectively (IP-1, and (IP-2 Port-1), Port-2), what node A sent to server first detects in packet (the localIP1 carrying above-mentioned node A, localPort1), server is based on this first detection packet, the local ip address and local IP port (localIP2 that carry node A is returned to node A, localPort2) the first response data packet, when above-mentioned localIP1 and localIP2 is identical, and localPort1 with localPort2 identical time, server determines that the NAT device type that this node A is corresponding is without NAT device type.
Special, when there is any node identification in first node set, when the node that this any node identification is corresponding does not receive the first response data packet that server returns in multiple preset duration, server determines that the node that this any node identification is corresponding cannot carry out point-to-point service.Wherein, this preset duration is the value pre-set as the case may be, and optionally, this preset duration is 300 milliseconds.
Further, the local ip address carried in first response data packet and the local IP port node this locality local ip address preserved corresponding with this any node identification and local IP port incomplete same time, server determines that node that this any node identification is corresponding is the one in other four kinds of NAT device types, be specially any NAT device type, need to judge further.
The second situation: when there is any node identification in first node set, the local ip address carried in the local ip address that node this locality that this any node identification is corresponding is preserved and local IP port and the first response data packet and local IP port incomplete same time, server receives the second detection packet that node corresponding to this any node identification sends, and generate the second response data packet according to this second detection packet, and send the second response data packet to the node that above-mentioned any node identification is corresponding; Wherein, the public network address of the server carried in the second detection packet is different from the public network address of the server carried in the second response data packet, and the port address of the server carried in the second detection packet is different from the port address of the described server carried in the second response data packet; When server judges that the node that above-mentioned any node identification is corresponding receives the second response data packet, determine that the NAT device type that this any node identification is corresponding is full cone NAT device type.
Such as, any node identification a is there is in first node set, this any node identification a corresponds to node A, the local ip address of this node A is localIP1, local IP port is localPort1, should (localIP1, localPort1) be distributed by the operating system of node A, this node A can carry out point-to-point service, and this node A is not without NAT device node.Server binds two public networks, public network address and the public network port of two bound public networks are respectively (IP-1, and (IP-2 Port-1), Port-2), what node A sent to server second detects in packet the public network address that carries above-mentioned server and public network port is (IP-1, Port-1), server is based on this second detection packet, the public network address and public network port (IP-2 that carry server is returned to node A, Port-2) the second response data packet, when in preset duration, when node A can receive above-mentioned second response data packet, server determines that the NAT device type that this node A is corresponding is full cone NAT device type.
Further, when the node that above-mentioned any node identification is corresponding does not receive the second response data packet that server returns in multiple preset duration, server determines that NAT device type that this any node identification is corresponding is wherein a kind of in residue three kinds of NAT device types, be specially any NAT device type, need to judge further.Wherein, this preset duration is the value pre-set as the case may be, and optionally, this preset duration is 300 milliseconds.
The third situation: when there is any node identification in first node set, the local ip address carried in the local ip address that node this locality that this any node identification is corresponding is preserved and local IP port and the first response data packet and local IP port incomplete same time, if server determines that the node that this any node identification is corresponding does not receive the second response data packet, then server receives the 3rd detection packet that node corresponding to this any node identification sends, detect packet according to the 3rd and generate the 3rd response data packet, and send the 3rd response data packet to the node that above-mentioned any node identification is corresponding, and server receives the 4th detection packet of node transmission corresponding to above-mentioned any node identification, and detect packet generation the 4th response data packet according to the 4th, and send the 4th response data packet to the node that above-mentioned any node identification is corresponding, wherein, the public network address of the server carried in the 3rd detection packet and port address, different from the public network address of the server carried in the 4th response data packet all different with port address, server determines that the public network address of the node that the public network address of the node that above-mentioned any node identification of carrying in above-mentioned 3rd response data packet is corresponding is corresponding from any node identification carried in above-mentioned 4th response data packet is different, or when the port address of the node that the port address of the node that the above-mentioned any node identification carried in the 3rd response data packet is corresponding is corresponding from the above-mentioned any node identification carried in the 4th response data packet is different, determine that the NAT device type that this any node identification is corresponding is symmetric NAT device type.
Such as, any node identification a is there is in first node set, this any node identification a corresponds to node A, the local ip address of this node A is localIP1, and local IP port is localPort1, is somebody's turn to do (localIP1, localPort1) distributed by the operating system of node A, this node A can carry out point-to-point service, and this node A is not without NAT device node, and NAT type corresponding to this node A is not full cone NAT device type.Server binds two public networks, and public network address and the public network port of two bound public networks are respectively (IP-1, Port-1) and (IP-2, Port-2).Node A is to the public network address of server and public network port (IP-1, Port-1) send the 3rd and detect packet, server detects packet based on the 3rd, the 3rd response data packet of local ip address and the local IP port (localIP2, localPort2) of carrying node is returned to node A, meanwhile, node A is to the public network address of server and public network port (IP-2, Port-2) send the 4th and detect packet, server detects packet based on the 4th, the local ip address and local IP port (localIP3 that carry node is returned to node A, localPort3) the 4th response data packet, when node A can receive above-mentioned 3rd response data packet and the 4th response data packet, and this localIP2 and localIP3 is different, or when localPort2 with localPort3 is different, server determines that the NAT device type that this node A is corresponding is symmetric NAT device type.
Further, when the public network address of the public network address of node corresponding to the above-mentioned any node identification carried in the above-mentioned 3rd response data packet node corresponding with any node identification carried in above-mentioned 4th response data packet is identical, and the port address of the port address of node corresponding to the above-mentioned any node identification carried in the 3rd response data packet node corresponding with the above-mentioned any node identification carried in the 4th response data packet also identical time, server determines that NAT device type that this any node identification is corresponding is wherein a kind of in residue two NAT device type, be specially any NAT device type, need to judge further.
4th kind of situation: when there is any node identification in first node set, the local ip address carried in the local ip address that node this locality that this any node identification is corresponding is preserved and local IP port and the first response data packet and local IP port incomplete same, server receives the 5th detection packet that node corresponding to above-mentioned any node identification sends, and detect packet generation the 5th response data packet according to the 5th, and send the 5th response data packet to the node that above-mentioned any node identification is corresponding; Wherein, the public network address of the server carried in the 5th detection packet is identical with the public network address of the server carried in the 5th response data packet, and the port address of the server carried in the 5th detection packet is different from the port address of the server carried in the 5th response data packet; When server judges that the node that any node identification is corresponding receives the second response data packet, determine that the NAT device type that above-mentioned any node identification is corresponding is restriction taper NAT device type.
Such as, any node identification a is there is in first node set, this any node identification a corresponds to node A, the local ip address of this node A is localIP1, and local IP port is localPort1, is somebody's turn to do (localIP1, localPort1) distributed by the operating system of node A, this node A can carry out point-to-point service, and this node A is not without NAT device node, and NAT type corresponding to this node A is not full cone NAT device type and symmetric NAT device type.Server binds two public networks, and public network address and the public network port of two bound public networks are respectively (IP-1, Port-1) and (IP-2, Port-2).Node A sends the 5th to the public network address of server and public network port (IP-1, Port-1) and detects packet, and wherein, the 5th detects the public network address and the public network port (IP-1, Port-1) that carry server in packet; Server detects packet based on the 5th, returns the 5th response data packet of public network address and the public network port (IP-1, Port-2) carrying server to node A; When node A is in multiple preset duration, can receive above-mentioned 5th response data packet, server determines that the NAT device type that this node A is corresponding is restriction taper NAT device type.
5th kind of situation: when there is any node identification in first node set, the local ip address carried in the local ip address that node this locality that this any node identification is corresponding is preserved and local IP port and the first response data packet and local IP port incomplete same time, if server judges that the node that above-mentioned any node identification is corresponding does not receive the 5th response data packet in multiple preset duration, then determine that the NAT device type that above-mentioned any node identification is corresponding is Port Restricted Cone NAT device type.
Adopt technique scheme, server is by detecting the mutual of packet and response data packet between node corresponding to each node identification in gathering with first, obtain the NAT device type that in the first set, each node identification is corresponding, thus the NAT device type enabling above-mentioned server corresponding according to each node identification in above-mentioned first set, obtain the node identification of NAT device type matching corresponding with requesting node in the first set quickly and easily.
Further, the NAT device type acquisition process that requesting node is corresponding gather with above-mentioned first in NAT device type acquisition methods corresponding to node identification identical, repeat no more herein.
Based on technique scheme, different according to the NAT device type that requesting node is corresponding, to the process that the node identification in the first set screens be:
When requesting node is without NAT device type node, server screens the node identification without NAT device type node from first node set, the node identification of full cone NAT device type node, the node identification of restriction taper NAT device type node, the node identification of Port Restricted Cone NAT device type node, and the node identification of symmetric NAT device type node, as the node identification of the NAT device type matching corresponding with requesting node.
When requesting node is full cone NAT device type node, from first node set, screening is without the node identification of NAT device type node, the node identification of full cone NAT device type node, the node identification of restriction taper NAT device type node, the node identification of Port Restricted Cone NAT device type node, and the node identification of symmetric NAT device type node, as the node identification of the NAT device type matching corresponding with requesting node.
When requesting node is for restriction taper NAT device type node, from first node set, screening is without the node identification of NAT device type node, the node identification of full cone NAT device type node, the node identification of restriction taper NAT device type node, and the node identification of Port Restricted Cone NAT device type node, as the node identification of the NAT device type matching corresponding with requesting node.
When requesting node is Port Restricted Cone NAT device type node, from first node set, screening is without the node identification of NAT device type node, the node identification of full cone NAT device type node, the node identification of restriction taper NAT device type node, and the node identification of Port Restricted Cone NAT device type node, as the node identification of the NAT device type matching corresponding with requesting node.
When requesting node is symmetric NAT device type node, from first node set, screening is without the node identification of NAT device type node, and the node identification of full cone NAT device type node, as the node identification of the NAT device type matching corresponding with requesting node.
Optionally, will without NAT device type, full cone NAT device type, restriction taper NAT device type, Port Restricted Cone NAT device type, and symmetric NAT device type identifies with label 0,1,2,3,4 respectively, then correspond to the requesting node of different N AT device type, the NAT device type node mark of screening server is consulted shown in table 1.
Table 1
| The NAT device type that requesting node is corresponding | The NAT type that the node identification that screening obtains is corresponding |
| 0 | 0、1、2、3、4 |
| 1 | 0、1、2、3、4 |
| 2 | 0、1、2、3 |
| 3 | 0、1、2、3 |
| 4 | 0、1 |
Step 220: above-mentioned node listing is sent to requesting node by server.
In the embodiment of the present invention, the node listing that above-mentioned screening obtains is sent to requesting node by server, make the node identification in requesting node and this node listing carry out point-to-point information interaction, thus improve the efficiency of point-to-point information interaction, effectively save system resources consumption.
Based on technique scheme, consult shown in Fig. 3, the invention provides a kind of node dispensing device, comprise the first generation unit 30, second generation unit 31, and transmitting element 32, wherein:
First generation unit 30, the node listing sent for receiving requesting node obtains request message, and the request msg mark of carrying in request message is obtained according to described node listing, in all nodes of this locality administration, determine the node identification of all nodes having request msg corresponding to described request Data Identification, generate first node set;
Second generation unit 31, for the network address translation device type determining that in described first node set, each node identification is corresponding, and from described first node set, screen the node identification of the corresponding NAT device type NAT device type matching corresponding with the described request node that this locality is preserved, based on the information generation node listing of all node identifications that screening obtains;
Transmitting element 32, for being sent to described request node by described node listing.
In the embodiment of the present invention, server receives the node listing acquisition request message that requesting node sends; Server obtains the request msg mark of carrying in request message according to above-mentioned node listing, obtain all node identifications having above-mentioned request msg, generate first node set in all nodes of this locality administration; Server obtains the NAT device type that in above-mentioned first node set, each node identification is corresponding, and from above-mentioned first node set, screening the node identification of the NAT device type matching corresponding with requesting node, all node identifications obtained based on screening generate node listings; Node listing is sent to described request node.Adopt technical solution of the present invention, the NAT device type that server is corresponding according to requesting node, and the NAT device type that each node identification having requesting node institute request msg is corresponding, the all node identifications having requesting node institute request msg are screened, thus obtain the node listing mated most with requesting node, ensure that the reliability that nodal information that requesting node is corresponding with each node identification in node listing is mutual, effectively save system resources consumption.
Those skilled in the art should understand, embodiments of the invention can be provided as method, system or computer program.Therefore, the present invention can adopt the form of complete hardware embodiment, completely software implementation or the embodiment in conjunction with software and hardware aspect.And the present invention can adopt in one or more form wherein including the upper computer program implemented of computer-usable storage medium (including but not limited to magnetic disc store, CD-ROM, optical memory etc.) of computer usable program code.
The present invention describes with reference to according to the flow chart of the method for the embodiment of the present invention, equipment (system) and computer program and/or block diagram.Should understand can by the combination of the flow process in each flow process in computer program instructions realization flow figure and/or block diagram and/or square frame and flow chart and/or block diagram and/or square frame.These computer program instructions can being provided to the processor of all-purpose computer, special-purpose computer, Embedded Processor or other programmable data processing device to produce a machine, making the instruction performed by the processor of computer or other programmable data processing device produce device for realizing the function of specifying in flow chart flow process or multiple flow process and/or block diagram square frame or multiple square frame.
These computer program instructions also can be stored in can in the computer-readable memory that works in a specific way of vectoring computer or other programmable data processing device, the instruction making to be stored in this computer-readable memory produces the manufacture comprising command device, and this command device realizes the function of specifying in flow chart flow process or multiple flow process and/or block diagram square frame or multiple square frame.
These computer program instructions also can be loaded in computer or other programmable data processing device, make on computer or other programmable devices, to perform sequence of operations step to produce computer implemented process, thus the instruction performed on computer or other programmable devices is provided for the step realizing the function of specifying in flow chart flow process or multiple flow process and/or block diagram square frame or multiple square frame.
Although describe the preferred embodiments of the present invention, those skilled in the art once obtain the basic creative concept of cicada, then can make other change and amendment to these embodiments.So claims are intended to be interpreted as comprising preferred embodiment and falling into all changes and the amendment of the scope of the invention.
Obviously, those skilled in the art can carry out various change and modification to the embodiment of the present invention and not depart from the spirit and scope of the embodiment of the present invention.Like this, if these amendments of the embodiment of the present invention and modification belong within the scope of the claims in the present invention and equivalent technologies thereof, then the present invention is also intended to comprise these change and modification.
Claims (14)
1. a node sending method, is applied in point-to-point stream media system, it is characterized in that, comprising:
Server receives the node listing acquisition request message that requesting node sends, and the request msg mark of carrying in request message is obtained according to described node listing, in all nodes of this locality administration, determine the node identification of all nodes having request msg corresponding to described request Data Identification, generate first node set;
Described server determines the network address translation device type that in described first node set, each node identification is corresponding, and from described first node set, screen the node identification of the corresponding NAT device type NAT device type matching corresponding with the described request node that described server this locality is preserved, based on the information generation node listing of all node identifications that screening obtains;
Described node listing is sent to described request node by described server.
2. the method for claim 1, is characterized in that, described server determines the NAT device type that in described first node set, each node identification is corresponding, specifically comprises:
Described server receives first of the node transmission that in described first node set, each node identification is corresponding and detects packet;
The local ip address that the node carried in the first detection packet that the node that described server is corresponding according to each node identification in described first node set respectively sends is corresponding and local IP port, generate each first response data packet, and send corresponding first response data packet to the node that each node identification in described first node set is corresponding;
Described server is determined to meet NAT device type corresponding to first pre-conditioned each node identification for without NAT device type in described first node set; Wherein, to meet the described first pre-conditioned local local internet protocol IP address of preserving of node referring to that the local ip address that carries in described first response data packet that node corresponding to node identification receives is corresponding with local IP port and node identification identical with local IP port for node identification.
3. method as claimed in claim 2, it is characterized in that, described server obtains the NAT device type that in described first node set, each node identification is corresponding, also comprises:
When there is any node identification in described first node set, the local ip address that node this locality that described any node identification is corresponding is preserved and local IP port, with the local ip address carried in described first response data packet and local IP port incomplete same time, described server receives second of the node transmission that in described first node set, any node identification is corresponding and detects packet, and generate the second response data packet according to described second detection packet, and send described second response data packet to the node that described any node identification is corresponding; Wherein, the public network address of the described server carried in described second detection packet is different from the public network address of the described server carried in described second response data packet, and the port address of the described server carried in described second detection packet is different from the port address of the described server carried in described second response data packet;
When described server judges that the node that described any node identification is corresponding receives described second response data packet, determine that the NAT device type that described any node identification is corresponding is full cone NAT device type.
4. method as claimed in claim 3, it is characterized in that, described server obtains the NAT device type that in described first node set, each node identification is corresponding, also comprises:
When there is any node identification in described first node set, the local ip address that node this locality that described any node identification is corresponding is preserved and local IP port, with the local ip address carried in described first response data packet and local IP port incomplete same time, if described server determines that the node that described any node identification is corresponding does not receive described second response data packet, then described server receives the 3rd detection packet that node corresponding to described any node identification sends, detect packet according to the described 3rd and generate the 3rd response data packet, and send described 3rd response data packet to the node that described any node identification is corresponding, and
Described server receives the 4th detection packet that node corresponding to described any node identification sends, and detect packet generation the 4th response data packet according to the described 4th, and send described 4th response data packet to the node that described any node identification is corresponding; Wherein, the public network address of the described server carried in described 3rd detection packet and port address, different all different with port address from the public network address of the described server carried in described 4th response data packet;
It is different that described server judges that node that described any node identification is corresponding meets the public network address of the public network address of node corresponding to described any node identification of carrying in the described 3rd response data packet node corresponding from any node identification carried in described 4th response data packet, or when the port address of the node that the port address of the node that the described any node identification carried in described 3rd response data packet is corresponding is corresponding from any node identification carried in described 4th response data packet is different, determine that the NAT device type that described any node is corresponding is symmetric NAT device type.
5. method as claimed in claim 4, it is characterized in that, described server obtains the NAT device type that in described first node set, each node identification is corresponding, also comprises:
When there is any node identification in described first node set, the local ip address that node this locality that described any node identification is corresponding is preserved and local IP port, with the local ip address carried in described first response data packet and local IP port incomplete same time, described server receives the 5th detection packet that node corresponding to described any node identification sends, and detect packet generation the 5th response data packet according to the described 5th, and send described 5th response data packet to the node that described any node identification is corresponding; Wherein, the public network address of the described server carried in described 5th detection packet is identical with the public network address of the described server carried in described 5th response data packet, and the port address of the described server carried in described 5th detection packet is different from the port address of the described server carried in described 5th response data packet;
When described server judges that the node that described any node identification is corresponding receives described second response data packet, determine that the NAT device type that described any node is corresponding is restriction taper NAT device type.
6. method as claimed in claim 5, it is characterized in that, described server obtains the NAT device type that in described first node set, each node identification is corresponding, also comprises:
When there is any node identification in described first node set, the local ip address that node this locality that described any node identification is corresponding is preserved and local IP port, with the local ip address carried in described first response data packet and local IP port incomplete same time, if described server judges that the node that described any node identification is corresponding does not receive described 5th response data packet in preset duration, then determine that the NAT device type that described any node identification is corresponding is Port Restricted Cone NAT device type.
7. the method as described in any one of claim 1-6, is characterized in that, the node identification of the NAT device type matching that screening is corresponding with described request node identification from described first node set, specifically comprises:
When described request node is without NAT device type node, from described first node set, screening is without node identification, the node identification of full cone NAT device type node, the node identification of restriction taper NAT device type node, the node identification of Port Restricted Cone NAT device type node of NAT device type node, and the node identification of symmetric NAT device type node, as the node identification of the NAT device type matching corresponding with described request node;
When described request node is full cone NAT device type node, from described first node set, screening is without node identification, the node identification of full cone NAT device type node, the node identification of restriction taper NAT device type node, the node identification of Port Restricted Cone NAT device type node of NAT device type node, and the node identification of symmetric NAT device type node, as the node identification of the NAT device type matching corresponding with described request node;
When described request node is for restriction taper NAT device type node, from described first node set screening without the node identification of NAT device type node, full cone NAT device type node node identification, limit the node identification of taper NAT device type node and the node identification of Port Restricted Cone NAT device type node, as the node identification of the NAT device type matching corresponding with described request node;
When described request node is Port Restricted Cone NAT device type node, from described first node set, screening is without node identification, the node identification of full cone NAT device type node, the node identification of restriction taper NAT device type node of NAT device type node, and the node identification of Port Restricted Cone NAT device type node, as the node identification of the NAT device type matching corresponding with described request node;
When described request node is symmetric NAT device type node, from described first node set, screening is without the node identification of NAT device type node, and the node identification of full cone NAT device type node, as the node identification of the NAT device type matching corresponding with described request node.
8. a node dispensing device, is applied in point-to-point stream media system, it is characterized in that, comprising:
First generation unit, the node listing sent for receiving requesting node obtains request message, and the request msg mark of carrying in request message is obtained according to described node listing, in all nodes of this locality administration, determine the node identification of all nodes having request msg corresponding to described request Data Identification, generate first node set;
Second generation unit, for the network address translation device type determining that in described first node set, each node identification is corresponding, and from described first node set, screen the node identification of the corresponding NAT device type NAT device type matching corresponding with the described request node that this locality is preserved, based on the information generation node listing of all node identifications that screening obtains;
Transmitting element, for being sent to described request node by described node listing.
9. device as claimed in claim 8, is characterized in that, described second generation unit, specifically for:
Receive the node transmission that in described first node set, each node identification is corresponding first detects packet; What send according to each node in described first node set respectively first detects in packet local ip address corresponding to the node that carries and local IP port, generate each first response data packet, and send corresponding first response data packet to the node that each node identification in described first node set is corresponding; Determine to meet NAT device type corresponding to first pre-conditioned each node identification for without NAT device type in described first node set; Wherein, to meet the described first pre-conditioned local local internet protocol IP address of preserving of node referring to that the local ip address that carries in described first response data packet that node corresponding to node identification receives is corresponding with local IP port and node identification identical with local IP port for node identification.
10. device as claimed in claim 9, is characterized in that, described second generation unit, also for:
When there is any node identification in described first node set, the local ip address that node this locality that described any node identification is corresponding is preserved and local IP port, with the local ip address carried in described first response data packet and local IP port incomplete same time, receive the second detection packet that any node in described first node set sends, and generate the second response data packet according to described second detection packet, and send described second response data packet to the node that described any node identification is corresponding; Wherein, the local public network address carried in described second detection packet is different from the local public network address carried in described second response data packet, and the local port address of carrying in described second detection packet is different from the local port address of carrying in described second response data packet; When judging that the node that described any node identification is corresponding receives described second response data packet, determine that the NAT device type that described any node identification is corresponding is full cone NAT device type.
11. devices as claimed in claim 10, is characterized in that, described second generation unit, also for:
When there is any node identification in described first node set, the local ip address that node this locality that described any node identification is corresponding is preserved and local IP port, with the local ip address carried in described first response data packet and local IP port incomplete same time, if determine, the node that described any node identification is corresponding does not receive described second response data packet, then receive the 3rd detection packet that node corresponding to described any node identification sends, detect packet according to the described 3rd and generate the 3rd response data packet, and send described 3rd response data packet to the node that described any node identification is corresponding, and receive the 4th detection packet of node transmission corresponding to described any node identification, and detect packet generation the 4th response data packet according to the described 4th, and send described 4th response data packet to the node that described any node identification is corresponding, wherein, the described 3rd detects the local public network address and port address that carry in packet, different all different with port address from the local public network address carried in described 4th response data packet, judge that described any node identification meets the public network address of the public network address of node corresponding to described any node identification of carrying in the described 3rd response data packet node corresponding from any node identification carried in described 4th response data packet different, or when the port address of the node that the port address of the node that the described any node identification carried in described 3rd response data packet is corresponding is corresponding from any node identification carried in described 4th response data packet is different, determine that the NAT device type that described any node identification is corresponding is symmetric NAT device type.
12. devices as claimed in claim 11, is characterized in that, described second generation unit, also for:
When there is any node identification in described first node set, the local ip address that node this locality that described any node identification is corresponding is preserved and local IP port, with the local ip address carried in described first response data packet and local IP port incomplete same time, receive the 5th detection packet that node corresponding to described any node identification sends, and detect packet generation the 5th response data packet according to the described 5th, and send described 5th response data packet to the node that described any node identification is corresponding; Wherein, the public network address of this locality of carrying in described 5th detection packet is identical with the public network address of this locality of carrying in described 5th response data packet, and the local port address of carrying in described 5th detection packet is different from the local port address of carrying in described 5th response data packet; When judging that the node that described any node identification is corresponding receives described second response data packet, determine that the NAT device type that described any node identification is corresponding is restriction taper NAT device type.
13. devices as claimed in claim 12, is characterized in that, described second generation unit, also for:
When there is any node identification in described first node set, the local ip address that node this locality that described any node identification is corresponding is preserved and local IP port, with the local ip address carried in described first response data packet and local IP port incomplete same time, the node that described any node identification is corresponding if judge does not receive described 5th response data packet in preset duration, then determine that the NAT device type that described any node identification is corresponding is Port Restricted Cone NAT device type.
14. devices as described in any one of claim 8-13, is characterized in that, described second generation unit, specifically for:
When described request node is without NAT device type node, from described first node set, screening is without node identification, the node identification of full cone NAT device type node, the node identification of restriction taper NAT device type node, the node identification of Port Restricted Cone NAT device type node of NAT device type node, and the node identification of symmetric NAT device type node, as the node identification of the NAT device type matching corresponding with described request node; When described request node is full cone NAT device type node, from described first node set, screening is without node identification, the node identification of full cone NAT device type node, the node identification of restriction taper NAT device type node, the node identification of Port Restricted Cone NAT device type node of NAT device type node, and the node identification of symmetric NAT device type node, as the node identification of the NAT device type matching corresponding with described request node; When described request node is for restriction taper NAT device type node, from described first node set screening without the node identification of NAT device type node, full cone NAT device type node node identification, limit the node identification of taper NAT device type node and the node identification of Port Restricted Cone NAT device type node, as the node identification of the NAT device type matching corresponding with described request node; When described request node is Port Restricted Cone NAT device type node, from described first node set, screening is without node identification, the node identification of full cone NAT device type node, the node identification of restriction taper NAT device type node of NAT device type node, and the node identification of Port Restricted Cone NAT device type node, as the node identification of the NAT device type matching corresponding with described request node; When described request node is symmetric NAT device type node, from described first node set, screening is without the node identification of NAT device type node, and the node identification of full cone NAT device type node, as the node identification of the NAT device type matching corresponding with described request node.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310714273.8A CN104735106A (en) | 2013-12-20 | 2013-12-20 | Node transmission method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310714273.8A CN104735106A (en) | 2013-12-20 | 2013-12-20 | Node transmission method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN104735106A true CN104735106A (en) | 2015-06-24 |
Family
ID=53458539
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310714273.8A Pending CN104735106A (en) | 2013-12-20 | 2013-12-20 | Node transmission method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104735106A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106713437A (en) * | 2016-12-16 | 2017-05-24 | 江苏神州信源系统工程有限公司 | Method used by server to send message to client in NAT network |
| CN110650358A (en) * | 2019-09-30 | 2020-01-03 | 北京奇艺世纪科技有限公司 | Node distribution method, device, node distribution server and medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101026543A (en) * | 2007-03-28 | 2007-08-29 | 华为技术有限公司 | Point-tor point P2P content sharing method and system |
| CN101083565A (en) * | 2006-05-29 | 2007-12-05 | 腾讯科技（深圳）有限公司 | Method and system for detecting network types |
| CN101098272A (en) * | 2006-06-27 | 2008-01-02 | 腾讯科技（深圳）有限公司 | Seed enquiring method of P2P system and P2P server |
| EP2540059A1 (en) * | 2010-04-07 | 2013-01-02 | Apple Inc. | Apparatus and method for matching users for online sessions |
| CN103312795A (en) * | 2013-05-31 | 2013-09-18 | 合一网络技术(北京)有限公司 | Torrent dispatching method and device for P2P (peer-to-peer) system |
| CN103348633A (en) * | 2011-03-21 | 2013-10-09 | 苹果公司 | Apparatus and method for managing peer-to-peer connections between different service providers |
-
2013
- 2013-12-20 CN CN201310714273.8A patent/CN104735106A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101083565A (en) * | 2006-05-29 | 2007-12-05 | 腾讯科技（深圳）有限公司 | Method and system for detecting network types |
| CN101098272A (en) * | 2006-06-27 | 2008-01-02 | 腾讯科技（深圳）有限公司 | Seed enquiring method of P2P system and P2P server |
| CN101026543A (en) * | 2007-03-28 | 2007-08-29 | 华为技术有限公司 | Point-tor point P2P content sharing method and system |
| EP2540059A1 (en) * | 2010-04-07 | 2013-01-02 | Apple Inc. | Apparatus and method for matching users for online sessions |
| CN103348633A (en) * | 2011-03-21 | 2013-10-09 | 苹果公司 | Apparatus and method for managing peer-to-peer connections between different service providers |
| CN103312795A (en) * | 2013-05-31 | 2013-09-18 | 合一网络技术(北京)有限公司 | Torrent dispatching method and device for P2P (peer-to-peer) system |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106713437A (en) * | 2016-12-16 | 2017-05-24 | 江苏神州信源系统工程有限公司 | Method used by server to send message to client in NAT network |
| CN110650358A (en) * | 2019-09-30 | 2020-01-03 | 北京奇艺世纪科技有限公司 | Node distribution method, device, node distribution server and medium |
| CN110650358B (en) * | 2019-09-30 | 2022-01-28 | 北京奇艺世纪科技有限公司 | Node distribution method, device, node distribution server and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110012437B (en) | Method, device and system for sending multicast message | |
| CN102571587B (en) | Method and equipment for forwarding messages | |
| KR102392120B1 (en) | Processing method, device and system for nf component abnormality | |
| JP6633775B2 (en) | Packet transmission | |
| CN105682182B (en) | A kind of discovery of equipment and equipment connection method, equipment and system | |
| US8774130B2 (en) | Access point, L2 switch and method of supporting multicast handover using the access point and L2 switch | |
| CN101924701B (en) | Building method of multicast forwarding path and route equipment | |
| KR20190002674A (en) | Resource subscription method, resource subscription device, and resource subscription system | |
| TW201543847A (en) | Network topology discovery | |
| CN104468604A (en) | Data access method and device based on peer-to-peer network communication mode in local area network | |
| JP2017503407A (en) | Packet processing method and apparatus | |
| JP2012533959A (en) | Effective host management protocol for multicast routers | |
| CN105656978A (en) | Resource sharing method and device | |
| CN104735106A (en) | Node transmission method and device | |
| CN104184565B (en) | A kind of method and device of processing retransmission information | |
| CN108471558A (en) | A kind of blended data transmission method, data transmission method and relevant device | |
| CN104168302A (en) | Device control realizing method, device control realizing system and proxy gateway | |
| CN104284383A (en) | Method and device for keeping service continuity | |
| CN101309154B (en) | Datagram sending method, sending apparatus and transmission system | |
| US20090157878A1 (en) | Method and system for connecting lower nodes to one another to increase scalability in zigbee network | |
| CN111385324A (en) | Data communication method, device, equipment and storage medium | |
| CN105610619B (en) | A kind of network element managing method and apparatus | |
| CN104780591A (en) | Service interoperation implementation method between terminal equipment, device, system and related equipment | |
| CN103067280A (en) | Method and device of message processing | |
| CN102938793B (en) | Information push device and information push method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20150624 |
|
| WD01 | Invention patent application deemed withdrawn after publication |