WO2009114997A1

WO2009114997A1 - Application-oriented name registration system for used in multi-layer network address translator environment and the method thereof

Info

Publication number: WO2009114997A1
Application number: PCT/CN2009/000305
Authority: WO
Inventors: 傅川; 张国清; 王迪; 杨清峰
Original assignee: 中国科学院计算技术研究所
Priority date: 2008-03-20
Filing date: 2009-03-20
Publication date: 2009-09-24
Also published as: CN101247408A; CN101247408B

Abstract

An application-oriented name registration system for used in multi-layer network address translator environment, a logon method and a query method are provided, said multi-layer network address translator environment includes a public network and at least a private network, and said private network accesses the public network and other private networks via the network address translation unit, said name registration system includes a system terminal device, a calling agent server and a registration service device which accesses the public network and at least a private network; application of the present invention enables the application, service, user to be located by the ID in the multi-layer NAT network environment.

Description

Application-oriented name registration system and method in multi-layer N A T network

The present invention relates to the field of computer network communication technologies, and more particularly, to an application-oriented name registration system and method in a multi-layer NAT network. Background technique

It is well known that due to the limited IP address space and the uneven distribution of the network, the network address is seriously lacking. From the perspective of practical application and deployment, NAT (Network Addres s Trans lator) technology is to solve the problem of Internet users accessing the Internet when the IP address is insufficient. Important method. With the increase of personal information devices, the popularity of network access devices, and the development of network technologies, more and more companies, groups, and families hope to organize these devices in a networked manner and access the Internet. Security considerations, how to hide high-security nodes on the network is a problem faced by more than 4 companies. In the case of such a serious lack of IP addresses, urgent need for network interconnection, and a large number of security risks, NAT technology is formed. The single-layer or multi-layer private network structure accessing the Internet has become more and more popular and popular in actual deployment.

The NAT device provides the address translation function for the private network address under the NAT, so that the host in the private network can transparently access the external network address. The private network address of the host under the NAT is not routable in the external network. The external network host cannot directly Access the host located in the private network under NAT. Therefore, a large number of services deployed in the private network, such as Web services, instant messages, and FTP services nodes, cannot be directly accessed by the external network corresponding to the private network.

Currently, services on the Internet generally have a globally uniform IP address. In a NAT, services on a private network IP address (such as a Web service node or an FTP service node) are generally only visible inside the private network, and other hosts outside the private network. The domain cannot know and access the services within the private network. Peer-to-peer communication services (such as instant messaging, file sharing, and media transmission) deployed on the private IP of the NAT can generally use the protocols of the RFC standard such as STUN [2], TURN [3], and ICE [4]. Provide services to hosts on the Internet through technologies such as public network service node relay, NAT tunneling, and reverse connection. It is not difficult to find that these implementations are closely related to the specific application, and are embedded in the application as a function module, and for the host node under the same-layer multi-layer NAT with the service, also through the public network service. Node relay provides services, which is obviously unreasonable. How to provide a unified solution, making the services in the private network visible to its external network, independent of the specific application, and providing a more reasonable access path for the external network node is an important issue. Summary of the invention

In order to overcome the defect that the services in the private network are invisible to the external network in the existing multi-layer NAT network environment, the present invention proposes an application-oriented name registration system and method in a multi-layer NAT network.

According to a first aspect of the present invention, the present invention provides a name registration system for an application under a multi-layer NAT environment, the multi-layer NAT environment comprising a public network and at least one private network, the private network being connected by an address translation unit Entering a public network or other private network; the name registration system includes a system terminal device, a call proxy server, and a registration service device that accesses the public network and at least one private network;

The registration service device is composed of a registration service unit that accesses the public network and each private network; the registration service unit is configured to accept a registration and login request of the system terminal device, and record a user registration of the system terminal device, Login information, the user login information includes a user identifier, a user login point used by the system terminal device used by the user in the network accessed by the registration service unit, and a network accessed by the system terminal device used by the user in the registration service unit System terminal access point in the system;

The system terminal device is configured to exchange information with the registration service device and the call proxy server, and send the user login information to the registration service device by using the call proxy server; the system terminal device can identify the SIP protocol, and use the message and the entity defined in the SIP protocol. Pass the user login message;

The call proxy server includes a top-level call proxy server connected to the public network and a call proxy server connected to each private network, and is used to forward the message specified in the SIP protocol, according to an indication of the registration service entity or other functional entity. Forwarding the message, the call proxy server may obtain a service portal from the registration service device, send the user login information to the registration service device, and query the registration service device for the user login point.

The registration service unit is further configured to perform an inquiry according to the recorded user login information.

The user login point is a network address and port of the registration service unit or the system terminal device, or may be converted into an identifier of the network address and port of the registered monthly service unit or the system terminal device; the system terminal device access point The network address and port of the NAT device, or the identifier of the network address and port that can be translated to the NAT device.

The query is to find the user login point with the shortest distance from the called party to the calling party NAT in all the user login points of the called party according to the user login information. The registration service unit includes a top-level registration service unit that accesses the public network and a basic registration service unit that accesses the private network.

The top-level registration service unit accesses the public network through the top-level service bus, and the basic registration service unit accesses the private network through the service bus, and the top-level registration service unit accessing the public network through the top-level service bus uses the public network. The network address is addressed, and the basic registration service unit accessing the private network through the service bus is addressed using the network address of the connected private network.

The registration service unit includes: a registration service logic control unit, a basic configuration information record table, a hierarchical information record table, a target registration server record table, a sub-registration service unit record table, a user registration information record table, and a user login information record table. , message buffer and communication unit.

The registration service logic control unit is configured to control execution of the registration service; the basic configuration information record table is used to record the identity of the unit, the host address of the unit, and the service port of the unit; the hierarchical information record table is used for recording Level information; the target registration server record table is used to record a network address and port of the ancestor registration server; the sub-registration server record table is used to record a network address, a port, an identifier, and a network of the corresponding NAT device of the sub-registration service unit An address and a port; the user registration information record table is used to record a user identifier, a user registry, and a system terminal device access point; the user login information record table is used to record a user identifier, a user login table, and a system terminal device access point; The message buffer area is configured to temporarily save information in the received data packet, and forward the relationship record table; the communication unit is connected to the top service bus device or the service bus device, and is responsible for transmitting and receiving data;

The registration service logic control unit may implement the basic configuration information record table, the hierarchical information record table, the target registration server record table, the sub-registration server record table, and the user registration information record table. And the user login information record table, the message buffer area, and the data of the communication unit are bidirectionally exchanged.

The registration service unit includes a service unit agent for expanding coverage of the registered registration service unit or for providing a unified service entry to the system terminal device; the service unit agent may be The agent is deployed on the network controlled by the same NAT device or the public network, and can also be deployed in the direct lower layer network of the network to which the agent belongs.

The service unit agent may broadcast the service entry of the agent or forward the message between the requestor of the registration service device and the proxy registration service device.

The system terminal device includes a terminal device control unit and basic configuration information. a record table, a target registration server record table, a target call proxy server record table, a message buffer area, and a communication unit, wherein the basic configuration information record table is used to record information such as a user identifier, a network address of the terminal device, a port, and the like; The server record table is used to record the network address and port of the call proxy server, the target registration server record table records the global service entry of the top-level registration server; the message buffer is used to temporarily store the received or sent message; the communication unit is used for public a network or private network connection, the terminal device control unit reads and writes information from a basic configuration information record table, a target registration server record table, a target call proxy server record table, a message buffer area, and the terminal device control unit accesses the network through the communication unit Send and receive data.

The system terminal device includes a SIP protocol processing unit, and interacts with the terminal device control unit to identify a SIP message.

The call proxy server may acquire the network address and port of the registration service device by referring to the manner in which the system terminal device acquires the network address and port of the registration service device.

The call proxy server needs to ensure that the registration service unit corresponding to the service portal of the call proxy server and the registration service device is deployed on the network controlled by the same NAT device, or the registration service device, when acquiring the service portal of the registration service device. The service entry corresponding to the service entry is located directly above the call proxy server.

The call proxy server in the upper layer network serves as a default destination for forwarding the SIP message by the local call proxy server, and needs to save the network address and port of the call proxy server in the upper layer network in the local call proxy server target call proxy record; The Call Proxy Server in the network saves the identity of the Call Proxy Server, the network address, the port, and the network address and port of the corresponding NAT device in the sub-call proxy record.

According to a second aspect of the present invention, there is provided a method for name registration using the name registration system, comprising:

Step 10), the call proxy server acquires the user login point and the system terminal device access point, and generates a "call proxy user login message", where the "call proxy user login message" includes the user identifier, the user login point, and the system terminal device access point. The call proxy server establishes a correspondence between a message sender and a message;

Step 20), according to a service portal of the locally stored registration service device, the call proxy server sends a "call proxy user login message" to the registration service device, and forwards a REGISTER message to the upper call proxy server, where the REGISTER message includes User ID; the service portal is a network address and port or can be converted to a network address and The label of the port;

Step 30) After the "registration agent user login message" is received by the registration service device, a new record is created in the local user information storage table, and the user identifier and user login in the "call agent user login message" are recorded. Points and system terminal access points, returning a successful registration message;

Step 40) The call proxy server receives a response message of the registration service device, and sends a success or failure response message to the message sender according to the correspondence between the message sender and the message;

Step 50) After receiving the REGISTER message, the upper-level call proxy server returns a success or failure response message of the message to the message sender according to the correspondence between the message sender and the message, and deletes the message sending. Correspondence between the person and the message.

The user login point is a network address and a port, or may be converted into an identifier of a network address and a port; the system terminal device access point is a network address and a port, or may be converted into an identifier of the network to the address and the port. .

The top-level registration service unit accessing the public network is started before the step 10) is executed, and then the basic registration service unit accessing the private network is started layer by layer, and registered with the name registration system to join the name registration system.

Wherein, step 10) further comprises:

Step 110), in the SIP protocol, when the Contac t item in the REGISTER message is a call proxy server, the local call proxy server uses the network address and port of the local call proxy server as a user login point according to the user identifier in the REGISTER message. And using a source address and a source port of the data packet carrying the REGISTER message as a system terminal device access point;

Step 120), when the Contact item in the REGISTER message is used to identify the system terminal device and the REGISTER message passes through the NAT device, the network address and port of the call proxy server are used as a user login point, and the REGISTER message is carried. The source address and source port of the data packet are used as system terminal device access points;

Step 130), when the Contact item in the REGISTER message is used to identify the system terminal device, and the REGI STER message passes through the NAT device, the Contact content is used as the user login point;

Step 140): When the Contact item in the REGISTER message is not a call proxy server, nor is it used to identify the system terminal device, the Contact content is used as a user login point.

Wherein, step 20) further comprises: if the Contact in the REGISTER message The item is a call proxy server or an identification system terminal device, and the network address and port in the Contac t item are proxied by the network address and port of the call proxy server.

The step 30) further includes: when the "call agent user login message" passes through the NAT device, setting the relative login location in the local user information storage table to cross-layer login, and carrying the "call proxy user login message" The source address and port are the mapped addresses of the new record.

Wherein, step 40) further comprises:

Step 410) If the call proxy server is a top-level call proxy server, according to the random sequence number in the response message, send the message to the sender of the REGI STER message according to the correspondence between the sender and the message of the REG STER message. a success, failure response message, deleting the correspondence between the message sender and the message;

Step 420), if the call proxy server is not a top-level call proxy server and the response message sent by the registration service device is a login success message, corresponding to the message sender and the message according to the random sequence number in the response message The relationship is set to the logged in status.

Wherein, step 50) further comprises:

Step 510), when the correspondence between the sender of the message and the message is the logged in state, returning a response message of the message to the sender of the REGI STER message, and deleting the correspondence between the sender of the message and the message;

Step 520): When the correspondence between the sender of the message and the message is an unregistered state, return a failure response message of the message to the sender of the REGI STER message, and delete the correspondence between the sender of the message and the message.

According to a third aspect of the present invention, the present invention provides a method for querying a user login point by using the name registration system, including:

Step 10), the call proxy server sends a "Call Agent User Login Point Lookup Request message" to the service portal of the name registration system, the message includes a target user identifier; Step 20), the registration service unit receives the "Call Agent" After the user login point finds the request message, the target user identifier in the message is extracted;

Step 30), when the target user identifier does not exist, if the registration service unit is a top-level registration server, return a failure message to the request message sender, if the registration service unit is not a top-level registration server, to the request message sender Return to the target user does not exist message;

Step 40), when the target user identifier exists, determine whether the network address corresponding to the user login point of the target user and the "call agent user login point lookup request message" are sent. The network address of the sender belongs to the network controlled by the same NAT device or the public network. If not, the target message does not exist to the sender of the request message;

Step 50), when the network address corresponding to the user login point of the target user and the network address of the sender of the "Call Agent User Login Point Lookup Request message" belong to the network controlled by the same NAT device or the public network, if the user login point of the target user If the corresponding network address belongs to the sender of the request message, the system terminal device access point of the target user is returned to the sender of the request message; if the network address corresponding to the user login point of the target user does not belong to the sender of the request message, the sender of the request message is returned. User login point of the target user;

The method further includes: Step 60) After the call proxy server receives the response message of the "Call Agent User Login Point Lookup Request Message", if it is a failure, the call proxy server reverses the call message delivery path to the system. The terminal device returns a failure message; if there is no message for the target user, the call message is forwarded according to the target call agent record; if the response message includes information that can be converted into a network address and port, the converted network address and The port forwards the SIP call request.

In step 40), according to the relative login location and the mapped address, it is determined whether the network address corresponding to the user login point of the target user and the network address of the sender of the call proxy user login point lookup request message belong to the same NAT device controlled network or public The internet.

The user's login information saved in the system is used to guide the delivery of the call message in the network controlled by the NAT device. Thereby achieving the purpose of transmitting a connection request between terminal devices of the system. By applying the present invention, in a multi-layer NAT network environment, applications, services, and users can be located by identification. DRAWINGS

Figure 1 is a structural diagram of the same-root multi-layer NAT network;

Figure 2 is a structural diagram of an application-oriented name registration system;

Figure 3 shows the connection mode of the NAT device connection matrix 1 001;

4 is a schematic structural diagram of a registration service device;

FIG. 5 is a schematic diagram of a process of establishing a registration service device;

Figure 6 is a schematic diagram of a process of establishing a registration service device;

Figure 7 is a schematic diagram of a process of establishing a registration service device;

8 is a flow chart of a system terminal device obtaining a registration service device service entry; 9 is a flowchart of a system terminal device obtaining a registration service device service portal; FIG. 10 is a system terminal device obtaining a registration service device service portal flow chart; FIG. 11 is a system terminal device used by a user to send a user registration information to a registration service device (user account opening information) ) the process of;

Figure 12 is a process in which a system terminal device used by a user sends user login information to a registration service device;

Figure 13 is a schematic diagram of a user login request point for actively requesting a user to obtain a requested user through a registration service system;

Figure 14 is a process flow diagram after the registration service unit receives the "service unit registration message";

Figure 15 is a flow chart of registration of a registration service unit to a registration service device;

Figure 16 is a process flow diagram after the registration service unit receives the "service entry query message";

Figure 17 Flow chart of the system terminal device obtaining the network address and port of the registration service device;

18 is a flowchart of processing after the registration service unit receives the "user login message"; FIG. 19 is a flow chart of the user login information sent by the user to the registration service device through the system terminal device;

20 is a flowchart of processing after the registration service unit receives the "user login point lookup request message";

Figure 21: The user queries the registration service device for the user login point flow chart through the system terminal device;

Figure 22 is a data storage table in the registration service unit;

Figure 23 is a correspondence table of user login information forwarding in the Proxy;

24 is a flow chart of the proxy agent login message sent by the Proxy to the registration service device; FIG. 25 is a structural diagram of the user information storage table in the registration service unit;

26 is a flow chart of the "call agent user login message" processed by the registration service device; FIG. 27 is a flowchart of the response message of the proxy processing the registration service device and the REG STER message;

Figure 28 is a registration service unit processing "call agent user login point lookup request message" flow chart.

detailed description

The application-oriented name registration system and method in a multi-layer NAT network provided by the present invention will be further described below with reference to the accompanying drawings and specific embodiments.

1, the same multi-layer NAT network

FIG. 1 is a schematic diagram showing the structure of a multi-layer multi-layer NAT network. A private network 4-1 accesses the public network 3 through the NAT device 1 001, and a private network 4-2 accesses the private network through another NAT device 1 002 4-1. . The private network connected to the public network 3 through the NAT device 1 001 is the network controlled by the NAT device, and the private network 4-2 accessing the private network 4-1 through the NAT device 1 002 is the network controlled by the NAT device. The NAT device directly connected to the public network 3 is the root NAT device. The network controlled by each NAT device to the public network 3 The number of minimum NAT devices passed is the number of layers controlled by the NAT device, and the path is the shortest path from the network controlled by the NAT device to the public network 3. The fewer the number of layers of the network controlled by the NAT device to the public network 3, the higher the level. If the networks controlled by the two NAT devices are each identical to at least one of the shortest NAT paths of the public network, the networks controlled by the two NAT devices have a common root NAT device. A multi-layer NAT network can be thought of as a combination of multiple multi-rooted NAT networks.

Multi-layer NAT networks increase the number of users' accesses and make the relative positions of the two parties more complicated. The multi-layer NAT network turns the public network flat communication mode into a hierarchical communication mode. In a multi-layer NAT network environment, the typical relationship between the two parties is: (1) the two communicating parties are in the public network; (2) the communicating party is in the network controlled by the NAT device, and the other party is in the public network; (3) the communicating parties are in the same NAT. In the network controlled by the device; (4) the two communicating parties are in the network controlled by different NAT devices, and the two NAT devices are connected to the public network through different root NATs; (5) the two communicating parties are in the network controlled by different NAT devices. And the two NAT devices are connected to the public network through the same root NAT.

The network address of the NAT device refers to the network address bound to the external network interface of the NAT device. For a large private network, the NAT device external network interface can be bound to multiple network addresses. In network management, multiple network addresses can be mapped to one NAT device by enumerating addresses or enumerating network segments. Ordinary users can access the network through the low-end (with basic functions) NAT device. The NAT device external network interface is generally bound to a network address. In the following description of the NAT device, a NAT device external network interface is only associated with one network. Network address binding. Because a NAT device can be represented by a network address bound to the external network interface of the NAT device. Development designers can easily find that the method described below is also applicable to NAT routers with external network interfaces bound to multiple network addresses.

To facilitate the description of a multi-layer NAT network, the following nouns are defined:

The network address of the NAT device refers to the network address bound to the NAT device's external network interface, or the NAT router address. The address can be either a public address or a private address.

The network range controlled by the NAT device: The NAT device is connected to the internal network interface, the network connected along the interface is extended, and the other NAT external network interface is terminated. There is no other NAT device between the two NAT devices. . The network cartridge is called a NAT-controlled network, or a network controlled by a NAT router. The NAT is the controlling NAT device of the network.

Direct upper layer network: If the external network interface of NAT device A is directly connected to the network controlled by NAT device B, the network controlled by NAT device B is the direct upper layer network of the network controlled by NAT device A; the public network is the network controlled by the root NAT device. Direct upper network.

Direct lower layer network: If the external network interface of NAT device A is directly connected to the network controlled by NAT device B, the network controlled by NAT device A is the direct lower layer network of the network controlled by NAT device B; the network controlled by the root NAT device is the public network. Directly underlying network.

NAT path length: The number of NAT devices passing through the reachable path from host A to B is the length of the NAT path.

The shortest NAT path: In the NAT environment, among the NAT paths of hosts A to B, the shortest NAT path with the smallest length of the NAT path is called the shortest NAT path from A to B. The number of NATs passing through is the shortest NAT path length.

Upper-layer network: The network from the direct upper-layer network of the network controlled by the current NAT device to the network controlled by each NAT device and the public network, which is the upper-layer network of the network controlled by the current NAT device.

Lower layer network: The network controlled by each NAT device from the direct network of the public network or the network directly controlled by the current NAT device is the lower network of the public network or the network controlled by the current NAT device.

Network to which the device is deployed: The network to which the device is deployed on the public network is the public network. The network to which the device is deployed on the network controlled by the NAT device is the network controlled by the NAT device.

After NAT: The network to which the device belongs is the public network or the lower layer network of the network controlled by the current NAT device, then the device is behind the NAT. Parent Server: The server in the direct upper-layer network of the current NAT-controlled network is the parent server of the server in the network controlled by the current NAT device.

Subserver: A server in a direct lower layer network of a public network or a network controlled by the current NAT is a subserver of a server in a public network or a network controlled by the current NAT.

Ancestor server: The current server and the parent server of the current server are the ancestor servers of the child servers of the current server.

2 Multi-layer NAT network below to register the name of the application

Under the multi-layer NAT network, the application-oriented name registration system 10 is a new registration system, as shown in Figure 2. The system includes a registration service device 2001, a Call Agent (PROXY) server, and a server system terminal device 6001. The registration service device 2001 is configured to record user registration (opening account) information, user login information, provide user registration information and user login information query; the user uses the system terminal device 6001 to register user information with the registration service device 2001, log in to the system, and query user registration information. Query user login information. The invention can be used not only in the network environment in which the NAT device is built, but also in the network changing environment formed by other devices having the address translation function.

The system terminal device includes at least the following: a terminal device control unit, a basic configuration information record table, a target registration service device record table, a message buffer area, a communication unit, and the like. The terminal device control unit is configured to control the execution of the terminal device; the basic configuration information record table is used to record the user identifier, the network address of the terminal device, the port, and the like; the target registration service device record table is used to record the network address of the registration service device and Port; the message buffer is used to temporarily store received or sent messages; the communication unit is used for public or private network connections.

The system terminal device is at least for interacting with the registration service device: obtaining a service entry from the registration service device; and transmitting a user registration message to the registration service device. In the system terminal device, the terminal device control unit reads and writes information from the basic configuration information record table, the target registration service device record, and the message buffer area. The terminal device control unit transmits and receives data from the network through a function module such as a communication unit.

According to the characteristics of the multi-layer NAT network, the registration service device 2001 records the content of the user login information as: the user identifier, the user login point mapped to the public network and the related private network, and the user mapping to the public network and the related private network. System terminal access point. At the same time, the registration service device 2001 can record the user login information according to the system. Information, help to actively request the user to determine the user login point of the user's current communication device with the shortest NAT path among all the user login points of the requested user. User login point: When the user is in the network controlled by the public network or NAT device, the user login point in the network is the network address and port of the system terminal device used by the user; when the user is in the network controlled by the NAT device The user login point in the upper layer network of the network controlled by the NAT device is a network address and port for receiving the user login request message by the service unit of the network controlled by the access public network or the NAT device, or may be converted into a receiving user. The network address of the login request message and the identity of the service unit of the port. System Terminal Access Point: This access point is located on the NAT device and is generated when a user login message passes through the NAT device. The access point can be represented in two ways: 1) the network address and port of the NAT device; 2) the network address and port identifier that can be calculated or converted to the NAT device.

According to the provisions of RFC 3261 and related protocols, the Proxy entity is first used to receive and forward various messages specified in the protocol, such as INVITE, ACK, etc.; secondly, the Proxy needs to be based on the registered service entity or other functional entity in the process of forwarding the message. Guide the forwarding of messages. In practice, in order to provide the efficiency of the Proxy forwarding message, a default forwarding message object can be defined for the Proxy. We can refer to a device that provides Proxy functionality in an actual system as a Proxy server, or a call server. The Proxy server is deployed on a network controlled by a public network and a NAT device as needed.

In order to facilitate the exchange of information between the registration service device and the Proxy server, the Proxy server needs to implement the following functions in addition to the functions defined in RFC3261:

1) The Proxy server can obtain the network address and port of the registration service device by referring to the system terminal device acquiring the network address and port of the registration service device. When obtaining the network address and port of the registration service device, the Proxy needs to ensure that the Proxy and the registration service unit belong to the same NAT device controlled network, or the registration service unit is directly on the Proxy. The service portal of the registration service device is stored in the Proxy server local target registration server record.

2) As the default destination of the Proxy forwarding message, the Proxy needs to know the Proxy in the upper layer network and save it locally as the target Proxy record. The saved content includes: network address and port; at the same time, the upper Proxy needs to know the Proxy in the direct lower layer network. And saved in the child Proxy record, the content is saved as: Proxy ID, network address, port, network address and port of the corresponding NAT device. The Proxy server deployed on the public network is the top-level Proxy server.

3), the following table shows the user login information forwarding correspondence table in the proxy server. Random serial number network address port response status bit

Dhlka ld88899 5000 0

The table includes a random sequence number, a network address, a port, and a response status bit. The random sequence number is used to distinguish the REGI STER message, and the response status bit is used to indicate that the reply of the registration service device is received. When the bit is 0, the response is not received. When the bit is non-zero, it indicates that a reply is received, for example, set to 1, and the response status bit defaults to 0.

In order for the system terminal device to recognize the S IP message, the system terminal device needs to add an S IP protocol processing unit, and the unit can exchange information with the terminal device control unit. The system terminal device needs to add a target Proxy server record for recording the call proxy server. The terminal device control unit can read and write the target Proxy server record.

In order to facilitate the description of the registration and login process, the Proxy server is first ignored, mainly describing the basic composition of the name registration service device, how the name registration service device interacts with the system terminal device, completes basic tasks such as user registration and login, and related methods. Secondly, the Proxy server is added to the name registration service device, so that the system can be used not only for user registration and login, but also for the call system; and the corresponding adjustment of the Proxy server, name registration service device, system terminal device, etc. .

As shown in FIG. 2, the registration service device 2001 is configured to record at least user registration information, user login information, user registration information and user login information query, registration service device service portal query, etc.; top service bus 1 is used to register the service device. Access to the public network 3; the service bus 2 is used to access the registration service device to the private network 4. The registration service device 2001 is connected to the public network 3 via the top service bus 1; it is connected to the private network 4 via the service bus 2.

The public network 3 and the private network 4 are connected together through a NAT device connection matrix 1001. The user terminal device 6001 and the service device 2001 are connected to the public network 3 and the private network 4.

Figure 3 shows the connection mode of the NAT device connection matrix 1 001. The relationship between NAT devices within the NAT device connection matrix 1001 is determined by the private network and the public network coupled to the NAT device connection matrix 1001. The connection rules between the private network and the public network and the NAT device are: The NAT device connection matrix 1001 has at least one line 5 accessing the public network; each private network has at least one line 6 that accesses the NAT device connection matrix 1001; There may be no network, and there may be multiple lines 7 connected to the private network by the NAT device connection matrix 1001. Taking the three-level NAT network structure shown in a of FIG. 3 as an example, b of FIG. 3 shows a connection diagram of the NAT device connection matrix 1001 of a. The public network 3 and the private network 4 are included; the NAT device connection matrix 1001 accesses the line 5 of the public network, the private network accesses the line 6 of the NAT device connection matrix 1001; and the line 7 of the private network is accessed by the NAT device connection matrix 1001. When deploying a multi-layer NAT network, you need to consider the overlap between network segments. The system must have the ability to discriminate and deal with overlapping problems between network segments.

Figure 4 shows the structure of the registration service device. As shown in Fig. 4a, the registration service device 2001 is composed of a top-level registration service unit 2011 and a plurality of basic registration service units 2021. The top-level registration service unit 2011 is connected to the public network 3 through the top-level service bus device 1, and is addressed using the network address of the public network; the basic registration service unit 2021 is connected to the private network 4 through the service bus device 2, and uses the connected private network. The network address is addressed. The registration service unit is the collective name of the top-level registration service unit 2011 and the basic registration service unit 2021. The registration service unit 2801 is the basic functional structure of the top-level registration service unit 2011 and the basic registration service unit 2021. The registration service unit 2801 as shown in FIG. 4b at least includes: a registration service logic control unit 2100, a basic configuration information record table 2101, a hierarchy information record table 2102, a target registration server record table 2103, a child registration service unit record table 2104, and user login information. A function module such as a record table 2105, a user registration information record table 2106, a message buffer area 2109, and a communication unit 2110.

The registration service logic control unit 2100 is configured to control the execution of the registration service; the basic configuration information record table 2101 is used to record the identity of the unit, the host address of the unit, and the service port of the unit; the hierarchical information record 2102 is used to record hierarchical information; the target registration server The record 2103 is used to record the network address and port of the ancestor registration server; the sub-registration server record table 2104 is used to record the network address, port, identifier, and network address and port of the corresponding NAT device of the sub-registration service unit, as shown in FIG. 22, table a The user login information record table 2105 is used to record the user identifier, the user login point, and the system terminal device access point, as shown in FIG. 22, the table b; the user registration information record table 2106 records at least the account identifier of the account user, and the account opening information; the message buffer 2109 For temporarily storing the information in the received data packet and the forwarding relationship record table, as shown in FIG. 22, the communication unit 2110 is connected to the top-level service bus device or the service bus device, and is responsible for transmitting and receiving data.

The registration service logic control unit 2100 reads the unit identifier, the unit unit address, and the unit service port from the basic configuration information record table 2101 according to the execution requirement, reads the record level information from the hierarchical information record 2102, and reads from the target registration server record 2103. Take the network address and port of the registration service device, read from the sub-registration server record table 2104 Take the network address, port, ID, and network address and port of the corresponding NAT device of the record registration service unit, and read the user ID, user login point, system terminal device access point from the user login information record table 21 05, and register from the user. The information record table 21 06 reads the user identifier, reads the information and the forwarding relationship in the temporarily stored received data packet from the message buffer 21 09, and reads the received data from the communication unit 21 1 0; The logic control unit writes the unit identifier, the unit host address, and the unit service port to the target registration server record 21 03 according to the execution requirement, and writes the network address, port, and sub-register of the registration service device to the target registration server. The registration server record table 21 04 writes the network address, port, identifier, and network address and port of the corresponding NAT device of the record sub-registration service unit, and writes the user ID, user login point, system terminal device to the user information record table 21 05 The access point, the user registration information record table 21 06 writes the user ID, to the message Writing information memory area 2109 temporarily stores the received data packet, and forwarding relationship, writes the data to be sent to the communication unit 2110.

Service unit agent, a special service unit. It is mainly used to expand the coverage of the service unit being served, or to provide a unified service portal to the system terminal equipment. The service unit agent can be deployed on the network or public network controlled by the same NAT device as the agent, or in the direct lower layer network of the network controlled by the NAT device to which the agent belongs. The service unit agent may broadcast the service entry of the agent or forward the message between the requester of the service device and the proxy service device. For convenience of description, the network address and port in the service unit that receives various messages are hereinafter referred to as service entries.

In a multi-level NAT network, the data or message transmission relationship is complex, and the most single data or message delivery form is: without the NAT device, the system terminal device and the service unit directly communicate; after the NAT device, the system terminal device and the service unit communicate; The service unit and the service unit communicate directly without going through the NAT device; through the NAT device, the service unit and the service unit communicate. In the above data or message delivery form, from the perspective of the data receiver, if the data is directly transferred between the system terminal device and the service unit, the service unit, and the service unit, the system terminal device and the service unit are data senders or message transmissions. If the data passes through the NAT device, the NAT device is a data sender or a message sender, and the NAT device receives data from the system terminal device and the service unit. Since the NAT device has a data transmission and reception relationship mapping table, the response message can be automatically forwarded.

3 Multi-layer NAT network environment registration service device construction process and method

In a multi-layer NAT network environment, the registration service device stores user registration and login information. At the same time, the user registration and login information is returned for the user information finder. The process of registering the service unit to join the registration service device: Starting by the top-level registration service unit, the registration service device is initially recognized, that is, the user information registration, the user login, the user registration and the login information inquiry service, and the service entry point inquiry service can be provided; The basic registration service unit in the network controlled by the root NAT device registers with the registration service device to join the system; again, the second layer NAT basic registration service unit registers with the registration service device to join the system; again, the third layer NAT basic registration service unit The registration service device is registered to join the system. In the above manner, the basic registration service unit sequentially joins the registration service device to provide services for the name registration service system 10 as needed. There is only one top-level registration service unit in the public network; there is only one basic registration service unit in each private network. In the following description of the registration service unit, each registration service unit runs on a server. When the registration service unit is composed of multiple servers, at least the existing user registration information and the content of the user login information are required, and the characteristics of the distributed system need to be expanded based on the existing information content to maintain the multi-service portal. The mapping relationship with the NAT device and the access relationship between the registered units. When the registration service unit is composed of multiple servers, the developer is not difficult to extend the spirit of the method, and the features of the distributed system are extended in registration, login, query, and the like.

Figure 5 is a registration service device building process, which is an example of a registration service unit joining a registration service device. The registration service device 2001 performs initial recognition by the top-level registration server 201 1 installed in the public network. The top level registration service unit 201 1 is provided with a network address of the public network, which is a well-known service portal within the system, or can be obtained by a system defined method. The NAT device 1 01 0 directly accesses the public network and is the root NAT device. The registration service unit 2021 is deployed in a network controlled by the root NAT device. The NAT device modifies the source or destination address of the traversed data packet. The description of the modification of the data packet by the NAT device is ignored in the figure.

The registration service unit 2021 in the network controlled by the root NAT device sends a "service unit registration message" to the top-level registration service unit 201 1; the message includes the network address, port, identity, and preset hierarchy information of the registration service unit 2021. , indicating that the registration service unit 2021 is the first layer registration service unit, and the shortest distance from the network controlled by the NAT device to the public network is 1.

* The top-level registration service unit 201 1 receives the "service unit registration message, and then determines whether the message is converted by the NAT device according to whether the network address of the data packet carrying the message and the network address of the registration service unit carried in the message are the same. ; If the NAT device converts, extract the hierarchical information in the registration request, if the level is more than the current registration If the service unit is greater than 1, the network address, the port, the identifier, and the network address and port of the corresponding NAT device are recorded in the sub-registration service unit record table, and a registration success message is returned to the service unit that sent the message; If the level difference between the level and the current registered service unit level is greater than 1, and the record of the registered service unit corresponding to the NAT device is not in the child registration service unit record table, a registration failure message is returned; if the NAT device is not converted, the registration failure is returned. Message.

Figure 6 is a registration service device building process, which is an example of a registration service unit joining a registration service device. The top level registration service unit 201 1 is provided with a network address of the public network, the address and the port providing the service being a well-known service portal within the system, or may be obtained by a system defined method. The first NAT device 1 01 0 directly accesses the public network and is the root NAT device. The first registration service unit 2021 is deployed in a network controlled by the root NAT device 1000-1. The second NAT device 1 020 directly accesses the root NAT device 1 01 0 controlled network, and the second registration service unit 2031 is deployed in the network controlled by the second NAT device 1 020. The networked host and the networked device in the network controlled by the second NAT device 1 020 can access the networked host and the networked device in the network controlled by the root NAT device. The NAT device modifies the passed data packet source or destination address. The description of the data packet modification by the NAT device is ignored in the figure.

The second registration service unit 2031 in the network controlled by the second NAT device 1 020 sends a "service unit registration message" to the top-level registration service unit 201 1 , the message including the network address, port, identity of the registration service unit 2031, The preset level information is 2, indicating that the registration service unit 2031 belongs to the shortest distance 2 of the network controlled by the NAT device 1 020 to the public network.

* The top-level registration service unit 201 1 receives the "service unit registration message, and then determines whether the message passes through the NAT device according to whether the network address of the data packet carrying the message and the registration server network address carried in the registration application message are the same. Converting; if the NAT device converts, extracts the hierarchical information in the registration request, if the level difference between the level and the current registered service unit is greater than 1, the sub-registration service unit record table searches for the registration service unit corresponding to the NAT device, If the registration service unit exists, a redirect response message including the network address and port of the registration service unit corresponding to the NAT device 101 is returned to the second registration service unit 2031.

After receiving the redirect response message of the registration service device, the second registration service unit 2031 sends a "service unit registration message" to the registration service device according to the network address and port information of the registration service unit included in the message; The network address, port, and preset level information of the second registration service unit 2031 is 2, indicating that the registration service unit 2031 The shortest distance from the network controlled by the NAT device 1 020 to the public network.

After receiving the "service unit registration message", the first registration service unit 2021 determines whether the message is converted by the NAT device according to whether the network address of the data packet carrying the message and the network address of the registration server carried in the registration application message are the same. If the NAT device converts the hierarchical information in the registration request, if the hierarchy is greater than the current registered service unit, the network address, port, and corresponding NAT of the registration service unit 2031 are recorded in the sub-registration service unit record table. The network address and port of the device 1 020 return a registration success message to the second registration service unit 2031; if the level difference between the level and the current registration service unit is greater than 1, the sub-registration service unit record table does not have the corresponding NAT device. Register the record of the service unit and return the registration failure message; if the NAT device has not been converted, return the registration failure message.

Figure 7 is a registration service device building process, which is an example of a registration service unit joining a registration service device. The top-level registration service unit 201 1 is provided with a network address of the public network, which is a well-known service portal within the system, or can be obtained by a system-defined method. The first NAT device 1 01 0 directly accesses the public network and is the root NAT device. The first registration service unit 2021 is deployed in the network controlled by the root NAT device 101. The second NAT device 1 020 directly accesses the network controlled by the root NAT device 101, the first registration service unit agent 2032 and the second registration service. The unit 2031 is deployed in a network controlled by the second NAT device 1 020. The networked host and the networked device in the network controlled by the second NAT device 1 020 can access the networked host and the networked device in the network controlled by the root NAT device. The NAT device modifies the source or destination address of the data packet that has passed, and the description of the modification of the data packet by the NAT device is ignored.

• The first registration service unit agent 2032 broadcasts a message containing the first registration service device network address and port in the network controlled by the second NAT device 1 020.

• The second registration service unit 2031 listens for a message containing the first registration service device network address and port broadcast in the network controlled by the second NAT device 1 020.

* After receiving the message including the registration service device network address and port, the second registration service unit 2031 sends a "service unit registration message" to the registration service device according to the network address and port of the registration service device provided in the message, and the message includes The network address, port, and preset level information 2 of the second registration service unit 2031 indicate the shortest distance from the network controlled by the NAT device 1 020 to the public network to which the registration service unit 2031 belongs.

* After receiving the "service unit registration message", the first registration service unit 2021, based on the network address of the data packet carrying the message and the registration carried in the registration application message Whether the server network address is the same, determining whether the message passes through the NAT device; if the NAT device extracts the hierarchical information in the registration request, if the level is greater than the current registered service unit, the registration is recorded in the sub-registration service unit record table. The network address of the service unit 2031, the port and the network address and port of the corresponding NAT device 1020, return a registration success message to the second registration service unit 2031; if the level difference between the level and the current registration service unit is greater than 1, the sub-registration The service unit record table does not have a record of the registration service unit corresponding to the NAT device, and returns a registration failure message; if the NAT device is not passed, a registration failure message is returned.

The second registration service unit agent shown in Figure 7 does not provide message forwarding. If necessary, it is not difficult for developers to develop a registration server proxy with message forwarding capabilities.

In addition, the broadcast mode can use wired, wireless or wired and wireless, etc. depending on the network environment in which the various service agents are located.

In addition, it is not difficult for developers to implement the registration service device in a multi-layer NAT network with reference to the examples in Figures 5-7. In addition, registration messages can be fully encrypted or partially encrypted, taking into account security issues.

Figure 14 is a flowchart of the processing method after the registration service unit receives the "service unit registration message" in the registration service device.

S1000: Start;

S1001: waiting to receive a data packet;

S1002: Whether the data packet is received, if no data packet is received, go to S1001, if the data packet is received, go to S1003;

S1003: extract a message in a data packet;

S1004: Determine whether it is "service unit registration message", if not, go to S1200, if yes, go to S1100;

S1100: determining, according to the source address of the data packet carrying the message and the network address of the service unit in the message, whether the message passes through the NAT device, if not, to S1130, if yes, go to S1120;

S1120: Extract hierarchical information in the message;

S 1121: determining whether the difference between the level information of the layer and the current service unit is equal to 1, if not, transferring to S1140, if yes, to S1122;

S1122: The service unit identifier, network address, port, and corresponding NAT in the message Network address and port are recorded in the sub-registration server record table;

S1123: Returning the message of successful registration to the sender of the message, and returning to S1001;

S1130: Returning the message that the registration failed to the message sender, and returning to S1001;

S1140: discriminate whether there is a sub-registration server in the network controlled by the NAT device corresponding to the source address of the data packet in the sub-registration server record, if not, transfer to S1130, if yes, go to S1141;

S1141: Return a redirect message containing the network address and port of the sub-registration server to the sender of the message, and return to S1001;

S1200: discriminate whether it is a system response message, if not, go to S1300, if yes, go to S1201;

S1201: Whether it is a failure message, if not, go to S1210, if yes, go to S1202; S1202: end;

S1210: Determine whether it is a redirect message, if not, go to S1220, if yes, go to S1211;

S1211: trigger a redirect message processing process corresponding to the "service unit registration message", and return to S1001;

S1220: Whether it is a success message, if yes, go to S1221, if not, go to S1001;

S1221: Trigger a successful message processing flow corresponding to the "service unit registration message", and return to S100L

Figure 15 is a method of registering a registration service unit with a registration service device. In order to maintain the data transmission and reception mapping relationship in the NAT device, the registration service unit needs to perform this method periodically.

S1800: Start;

S1801: Initializing the target registration server record as a top-level registration service unit service entry on the public network, and issuing a "service unit registration message" to the top-level registration service unit deployed on the public network;

S1802: Waiting for a trigger reply of the feedback message;

S1803: Determine whether the received information is a failure, if yes, go to S1804, if not, go to S1810;

S1810: Determine whether the received information is successful, if yes, go to S1804, if not, go to S1820; S 1820: Determine whether the received information is a redirect, if not, go to S 1802, and if yes, go to S 1821;

S 1821: extracting the service entry in the redirect message and storing it in the target registration server record;

S 1822: Send a "service unit registration message" to the registration service device according to the network address and port in the redirect message, and return to S 18 02;

S 1804: End.

4, registration service system

4. 1. Workflow and processing method for obtaining the network address and port of the registration service device The network address and port of the registration service device 2001 are used as service entries of the registration service device 2001. In a multi-layer NAT network environment, the name registration service device 2001 has different service entries for the public network and the private network. The service portal of the public network can be accessed by the system terminal device in the network controlled by the public network and each NAT device without special restrictions. This type of port is a global service entry; otherwise, the port can only be accessed by some system terminal devices. For local service entrances. After the terminal system 6001 obtains the service entry, the registration, login, and inquiry request can be submitted to the registration service device 2001.

Figure 8 is a flow diagram of the system terminal device 6001 requesting a local service entry from the registration service device 10 based on the registration service device global service entry in the public network. The flowchart is an example of a system terminal device obtaining a registration service device service entry. The top-level registration service unit 201 1 is provided with a network address of the public network, which is a well-known service portal within the system, or can be obtained by a system-defined method. The first NAT device 1 01 0 directly accesses the public network and is the root NAT device. The second basic registration service unit 2021 is deployed in the network controlled by the root NAT device 101. The second NAT device 1 020 directly accesses the network controlled by the root NAT device 101, and the third basic registration service unit 2022 is deployed in the second. In the network controlled by the NAT device 1 020, the system terminal device 6001 is deployed in the network controlled by the second NAT device 1 020. The networked host and networked device in the network controlled by the second NAT device 1 020 can access the networked host and the networked device in the network controlled by the root NAT device. The NAT device modifies the source or destination address of the data packet that has passed, and the description of the modification of the data packet by the NAT device is ignored in the figure.

• The system terminal device 6001 sends a "service portal query message" to the global service portal of the registration service device; * After receiving the "Service Entry Query Message", the top-level registration service unit 201 1 judges whether it can be executed according to logic (see FIG. 16). If the return success message can be executed, if it cannot be executed, it is determined whether it can be redirected to the sub-registration service unit. If the redirect message can be returned; in this embodiment, a redirect message including the network address and port of the first basic registration service unit 2021 is returned;

After receiving the redirect response message, the system terminal device 6001 sends a "service portal query message" to the registration service device according to the service entry of the registration service device included in the message;

* After receiving the "service entry query message", the first basic registration service unit 2021 determines whether it can be executed according to logic. If the return success message can be executed, if it cannot be executed, it is determined whether it can be redirected to the sub-registration service unit, if possible, Then, a redirect message is returned; in this embodiment, a redirect message containing the network address and port of the second basic registration service unit 2022 is returned.

* After receiving the "service entry query message", the second basic registration service unit 2021 determines whether it can be executed according to logic. If the return success message can be executed, if it cannot be executed, it is determined whether it can be redirected to the sub-registration service unit, if possible, Returning the redirect message, in this embodiment, a success response message is returned.

• After receiving the success response message, the system terminal device 6001 stores the service entry of the registration service device included in the message in the local target registration service device record.

The request message in Figure 8 can be sent or received by wire or / and wireless.

FIG. 9 is a flow chart for obtaining a local service entry by monitoring a service entry including a registration service device and a system terminal device 6001. The flowchart is an example in which the system terminal device obtains a registration service device service entry. The top-level registration service unit 201 1 is provided with a network address of the public network, which is a well-known service portal within the system, or can be obtained by a system-defined method. The first NAT device 101 0 directly accesses the public network and is a root NAT device. The first basic registration service unit 2021 is deployed in the network controlled by the root NAT device 101. The second NAT device 1 020 directly accesses the network controlled by the root NAT device 101, and the second basic registration service unit 2022 is deployed in the second. In the network controlled by the NAT device 1 020, the system terminal device 6001 is deployed in the network controlled by the second NAT device 1 020. The networked host and the networked device in the network controlled by the second NAT device 1 020 can access the networked host and the networked device in the network controlled by the root NAT device. The NAT device modifies the source or destination address of the data packet that has passed, and the description of the modification of the data packet by the NAT device is ignored in the figure. • The second basic registration service unit 2022 broadcasts a message containing the registration service device network address and port in the network to which the NAT is controlled;

• The system terminal device 6001 is listening for a broadcast message containing a message of the registered service device network address and port;

• After receiving the broadcast message, the system terminal device 6001 stores the service entry of the registration service device included in the message in the record of the local target registration service device.

In addition, the manner in which the service portal is published in the form of a broadcast as described in FIG. 9 can be replaced by means of publicity, pre-notification of the user, etc., and the system terminal device 6001 is manually configured by the user.

Figure 10 shows the flow of the system terminal device 6001 to obtain a partial service entry when listening to the service entry including the registration service device. The flow chart is an example of a system terminal device obtaining a registration service device service entry. The top-level registration service unit 201 1 is provided with a network address of the public network, which is a well-known service portal within the system, or can be obtained by a system-defined method. The first NAT device 1 01 0 directly accesses the public network and is the root NAT device. The first basic registration service unit 2021 is deployed in the network controlled by the root NAT device 101. The second NAT device 1 020 directly accesses the network controlled by the root NAT device 101. The first basic registration service unit agent 2023 is deployed in the first In the network controlled by the NAT device 1 020, the system terminal device 6001 is deployed in the network controlled by the second NAT device 1 020. The networked host and the networked device in the network controlled by the second NAT device 1 020 can access the networked host and the networked device in the network controlled by the root NAT device. The NAT device modifies the source or destination address of the data packet that has passed, and the description of the modification of the data packet by the NAT device is ignored in the figure. Service Units There may be a private communication interface between the agent and the agent service unit for information exchange between the service unit agent and the agent service unit.

• The first basic registration service unit agent 2023 broadcasts a message containing the registration service device network address and port in the NAT controlled network;

The first registration service unit agent in Figure 10 does not provide message forwarding. If necessary, it is not difficult for developers to develop a registration server agent with message forwarding.

In addition, in a multi-layer NAT network, it is not difficult for developers to propose other phases according to this process. The process of executing the process can be wired or/and wireless.

In addition, FIG. 10 shows that the manner of publishing the service portal through the broadcast form can be replaced by means of publicity, pre-notifying the user, etc., and the user configures the service client manually.

Figure 16 is a flow chart showing the processing after the registration service unit in the registration service device receives the "service entry inquiry message".

S2000: Start;

S2001: waiting to receive a data packet;

S2002: Whether the data packet is received, if no data packet is received, go to S2001, if the data packet is received, go to S2003;

S2003: extracting a message in a data packet;

S2004: Determine whether it is "service entry query message", if not, go to S2005, if yes, go to S2100;

S2100: determining, according to the source address of the data packet carrying the message and the network address of the user terminal in the message, whether the user terminal is after the NAT, if not, then transferring to S2101, if yes, to S2200;

S2200: In the sub-registration server record table, if there is a sub-registration server in the network controlled by the NAT device corresponding to the source address of the data packet, if not, go to S2101, if yes, go to S2201;

S2201: Return, to the message sender, a redirect message including the network address and port of the sub-registration server, and return to S2001;

S2101: returning a success response message to the sender of the message, including the network address and port of the available registration service unit, and returning to S2001;

S2005: Perform other processing and return to S2001.

Figure 17 is a flow chart showing the system terminal device acquiring the registration service device network address and port. In order to maintain the data transmission and reception mapping relationship in the NAT device, the system terminal device needs to perform the method periodically.

S2800: Start;

S2801: Listening to broadcast messages;

S2802: Whether a broadcast message containing the service entry of the registration service device is received, if yes, go to S2806, if not, go to S2803; S2806: Record a network address and a port in the broadcast message in the local target registration service device record;

S2807: End;

S2803: Send a "Service Portal Inquiry Message" to a top-level registration service unit deployed on the public network, and initialize the local target registration service device record with a service entry of a top-level registration service unit deployed on the public network;

S2804: waiting for a reply;

S2805: Determine whether the received information is a success message. If yes, go to S2807. If not, go to S2810.

S2810: Determine whether the received information is a redirect message, if not, go to S2804, and if yes, go to S2811;

S2811: The network address and port of the registration service device in the redirect message are stored in the local target registration service device record table, and the service entry query message is sent to the registration service device according to the network address and port in the redirect message. S2804.

4. 2. User Information Registration Process and Method FIG. 11 shows the process in which the system terminal device used by the user sends user registration information (user account opening information) to the registration service device. This flowchart is an example in which the system terminal device used by the user transmits user registration information to the registration service device. The top-level registration service unit 2011 is equipped with a public network network address, which is a well-known service portal within the system, or can be obtained by a system-defined method. The first NAT device 1010 directly accesses the public network and is a root NAT device. The first basic registration service unit 2021 is deployed in the network controlled by the root NAT device 1010; the second NAT device 1020 directly accesses the network controlled by the root NAT device 1010, and the second basic registration service unit 2031 is deployed in the second NAT device 1020. In the network, the system terminal device 6001 is deployed in the network controlled by the second NAT device 1020; the system terminal device 6001 has obtained the service portal of the registration service device. The networked host and the networked device in the network controlled by the second NAT device 1020 may Access networked hosts and networked devices in the network controlled by the root NAT device. The NAT device modifies the source or destination address of the passed data packet. The description of the modification of the data packet by the NAT device is ignored in the figure.

• The system terminal device 6001 sends a “user registration message” to the top-level registration service unit 201 1 , where the message includes at least the user identifier and the network address of the user-used terminal; • the top-level registration service unit 201 1 registers with the user after receiving the user registration message. If the same user identifier is not found in the information record table, if the user identifier and related information are not added to the user registration information record table, it is determined whether the "user registration message" passes through the NAT device (for example, according to the user) The source address of the data packet of the registration message and the user in the message use the network address of the terminal to determine whether the message passes through the NAT device. If the NAT device passes, look up the registration service unit related to the NAT device in the sub-registration server record. If the sub-registration service unit exists, returning a redirect response message, where the message includes the service entry of the registration service unit; if the NAT device is not passed, or the NAT device does not have an associated sub-registration service unit, a success message is returned; User ID exists Back failure response message.

• After receiving the response message, the system terminal device ends the registration if it is a failure response message or a success response message. If it is a redirect response message, it sends a "user registration message" according to the registration service unit service entry in the message. The message includes at least User ID, the network address of the user using the terminal;

After the first registration service unit 2021 receives the user registration message, it searches for the same user identifier in the user registration information record table, if there is no same user identifier. Adding the user user identifier and related information to the user registration information record table, and determining whether the "user registration message" passes through the NAT device (for example, according to the source address of the data packet carrying the "user registration message" and the user using the terminal in the message The network address determines whether the message passes through the NAT device. If the NAT device passes, the registration service unit related to the NAT device is searched in the sub-registration server record. If the sub-registration service unit exists, the redirect response message is returned. The service entry of the registration service unit is included; if the NAT device is not passed, or the NAT device does not have an associated sub-registration service unit, a successful registration message is returned; if the user identification exists, a failure response message is returned.

After the second registration service unit 2031 receives the user registration message, it searches for the same user identifier in the user registration information record table. If the user identifier and related information are not added to the user registration information record table, the same is determined. Whether the "user registration message" passes through the NAT device (for example, according to the source address of the data packet carrying the "user registration message" and the network address of the user using the terminal in the message to determine whether the message passes through the NAT device), if it passes through the NAT device, Then, in the sub-registration server record, look up the registration service unit related to the NAT device, and if the sub-registration service unit exists, return a redirect response message, where the message includes the service entry of the registration service unit; if not through the NAT device, Or the NAT device does not have an associated sub-registration service unit, then returns a successful registration message; if the user ID exists, a failure response message is returned. • After receiving the response message, the system terminal device ends the registration if it is a failure response message or a success response message. If it is a redirect response message, it sends a "user registration message" according to the registration service unit service entry in the message. The message includes at least User ID, network address of the user's use terminal; Since the user registration information exists in a hierarchical manner in a multi-level NAT network, when the registration service unit receives the "user registration information query message", it can use multiple policies to query. For example, first search in the local user registration record table, if the user exists, return a success message to the query requester; if the user does not exist, query the top-level registration service unit, if receiving the success message returned by the top-level registration service unit, The query requester returns a success message; if a failure message returned by the top-level registration service unit is received, a failure message is returned to the query requester.

4. 3 User Login Process and Method

FIG. 12 shows a flow of transmitting user login information to a registration service device by a system terminal device used by a user, which is an example in which a system terminal device used by a user transmits user login information to a registration service device. The top-level registration service unit 201 1 is provided with a network address of the public network, which is a well-known service portal within the system, or can be obtained by a system-defined method. The first NAT device 101 0 directly accesses the public network and is a root NAT device. The first basic registration service unit 2021 is deployed in the network controlled by the root NAT device 1010-1; the second NAT device 1 020 directly accesses the network controlled by the root NAT device 101, and the second basic registration service unit 2031 is deployed in the second In the network controlled by the NAT device 1 020, the system terminal device 6001 is deployed in the network controlled by the second NAT device 1 020; the system terminal device 6001 has obtained the service portal of the registration service device. The networked host and the networked device in the network controlled by the second NAT device 1 020 can access the networked host and the networked device in the network controlled by the root NAT device. The NAT device modifies the source or destination address of the traversed data packet, and the description of the modification of the data packet by the NAT device is ignored in the figure. • The system terminal device 6001 sets the user login status to not registered, and sends a “user login message” to the registration service device according to the service entry of the locally stored registration service device, where the message includes at least a user identifier, a user login point, and the user login point. The network address and port of the system terminal device used by the user;

After receiving the user login message, the second registration service unit 2031 determines whether to record the user identification and related information according to logic, and determines whether to return the response message and return the response message; after recording the user login information, if the unit is not a top-level registration service unit that records a user login message forwarded to the registration service device according to the local target registration server;

• After receiving the success response message, the system terminal device sets the user login status to login;

After receiving the user login message, the first registration service unit 2021 determines whether to record the user identification and related information according to logic, and determines whether to return the response message and return the response message; after recording the user login information, if the unit is not a top-level registration service unit that records a user login message forwarded to the registration service device according to the local target registration server;

• After the top-level registration service unit 2011 user registration message, it is logically determined whether to record the user's identification and related information, and decide whether to return the response message and return the response message; after recording the user login information, if the unit is not the top registration service The unit records the user login message forwarded to the registration service device according to the local target registration server.

In addition, the user needs to periodically send a user login message to the registration service device to ensure that the user status in the registration service device is online. If the registration service device does not receive a user login message for a certain user within a certain period of time, the registration service device sets the user's status to offline. If the system terminal device moves, the system terminal device needs to resend the user login message. 18 is a processing method after the registration service unit in the registration service device receives the "user login message". S3000: Start;

S3001: waiting to receive a data packet;

S3002: Whether to receive the data packet, if no data packet is received, go to S3001, such as Receive the data packet, go to S3003;

S3003: extracting a message in a data packet;

S3004: Determine whether it is "user login message", if not, go to S3005, if yes, go to S 3100;

S3100: According to the user login point in the message, it is determined whether the sender of the message is a child registration server, and if so, to S3101, if not, to S3200;

S3101: The user identifier in the message is used as the user identifier, the data packet source address and the source port carrying the message are the system terminal device access point, and the unit identifier is used as the user login point, and is stored in the user login information record table, and the sequence is Execute S 3300;

S3200: Find whether the user is registered in the system. If there is no registration, go to S 3290. If it is already registered, go to S3201.

S 3201: determining, according to the source address of the data packet carrying the message and the network address of the system terminal device used by the user in the message, whether the system terminal device is behind the NAT, if not, going to S3202, if yes, going to S3203;

S 3202: the user identifier in the message is used as the user identifier, and the user login point is used as the user login point, and is stored in the user login information record table;

S 3203: the user identifier in the message is used as the user identifier, the data packet source address and the source port carrying the message are the system terminal device access point, and the unit identifier is used as the user login point, and is stored in the user login information record table; S3204: return a success response message to the message sender;

S3300: Determine whether the unit is a top-level registration server. If yes, go to S 3001. If not, go to S3301;

S 3301: Generate a new user login message by using the identifier of the unit instead of the user login point of the received message;

S3302: Send a new user login message to the registration service device according to the local target registration server record, and return to S3001;

S3290: Returning a failure response message to the sender of the message, and returning to S3001;

S3005: Perform other processing.

In addition, when the user login message is forwarded between the registration service units, the sub-registration service unit record of the registration service unit stores the registration service unit identifier and the NAT device-related information in the subordinate network, and therefore uses the registration service unit identifier as the system terminal device. When accessing a point, it can be mapped to a network address and port on the NAT device. Figure 19 shows the user sending user login information to the registration service device through the system terminal device.

S3800: Start;

S 3802: setting a timeout period, setting the terminal to an unregistered state;

S3803: Send a "user login message" to the registration service device according to the record of the local target registration service device; S3804: Waiting for a reply;

S3805: Determine whether it times out; if yes, go to S3809, if not, go to S 3806; S3806: judge whether it is a success message, if not, go to S3808, if yes, go to S3807;

S3807: Set the terminal status to login; S3809: End;

S3808: Determine whether it is a failure message. If yes, go to S3809, if not, turn S 3804. It is not difficult for developers to improve according to the above-mentioned user login method and the needs of user registration, which is used to complete user registration and account opening tasks.

4. The user login point acquisition process and method of the requested user

FIG. 13 is a flowchart of actively requesting a user to obtain a user login point of a requested user through a registration service system, and the process is an example of a process of acquiring a user login point of the requested user. The top-level registration service unit 201 1 is provided with a network address of the public network, which is a well-known service portal within the system or can be obtained by a system defined method. The first NAT device 1 01 0 directly accesses the public network and is the root NAT device. The first basic registration service unit 2021 is deployed in the network controlled by the root NAT device 101. The second NAT device 1 020 directly accesses the network controlled by the root NAT device 101, and the second basic registration service unit 2031 is deployed in the second. In the network controlled by the NAT device 1 020, the system terminal device 6001 is deployed in the network controlled by the second NAT device 1 020; the system terminal device 6001 has obtained the service portal of the registration service device. The networked host and the networked device in the network controlled by the second NAT device 1 020 can access the networked host and the networked device in the network controlled by the root NAT device. The NAT device modifies the source or destination address of the traversed data packet, and the description of the modification of the data packet by the NAT device is ignored in the figure.

The system terminal device 6001 sends a "user login point lookup request message" to the registration service device according to the locally stored target registration service device record port, and the message includes at least the requested user identifier and the random serial number.

After receiving the "user login point lookup request message", the second registration service unit 2031 extracts the requested user identifier in the message, and searches in the user login information record table, if the requested user identifier exists in the user login information record table. Returning a success message including the current user login point of the requested user to the message sender, where the message includes a random sequence number in the corresponding original request message; if the requested user identifier does not exist in the user login information record table, and the service node It is not a top-level registration service unit. The mapping relationship between the message and the sender of the message is established according to the random sequence number in the message, the mapping relationship is saved in the message buffer area, and the "user login point lookup is forwarded to the registration service device according to the local registration server record. Request message";

After receiving the "user login point lookup request message", the first registration service unit 2021 extracts the requested user identifier in the message, and searches in the user login information record table, if the requested user identifier exists in the user login information record table. Returning a success message containing the current user login point of the requested user to the message sender, where the message includes a random sequence number in the corresponding original request message; if the requested user identifier does not exist in the user login information record table, and the service node Not a top-level registration service unit, according to the random order in the message Establishing a mapping relationship between the message and the sender of the message, saving the mapping relationship in the message buffer, and forwarding the "user login point lookup request message" to the registration service device according to the local registration server record;

• After receiving the "user login point lookup request message", the top-level registration service unit 2011 extracts the requested user identifier in the message, and searches in the user login information record table. If the requested user identifier exists in the user login information record table, Returning a success message containing the current user login point of the requested user to the message sender, where the message includes a random sequence number in the corresponding original request message; if the requested user identifier does not exist in the user login information record table, and the service node is The top-level registration service unit returns a failure message to the message sender, where the message includes a random sequence number in the corresponding original request message;

* After receiving the response message, the first registration service unit 2021 finds the corresponding sender node lookup request message sender according to the random sequence number in the response message, and forwards the response message to the sender.

* After receiving the response message, the second registration service unit 2022 finds the corresponding sender node lookup request message sender according to the random sequence number in the response message, and forwards the response message to the sender.

• After receiving the response message, the system terminal device 6001 records the user login point of the requested user in the message if it is a success response message; if it is a failure response message, it ends.

The above process is the basic process of finding a user login point that satisfies the condition. It is not difficult for developers to extend and change the above processes according to the needs of specific applications, and to change the subsequent execution process after finding the user login point. It does not affect the nature of the process of querying the user's logon point based on the requested user ID.

Figure 20 is a flow chart showing the processing after the registration service unit in the registration service device receives the "user login point lookup request message".

S4000: Start;

S4001: waiting to receive a data packet;

S4002: Whether to receive the data packet, if no data packet is received, go to S4001, if the data packet is received, go to S4003;

S4003: extracting a message in a data packet;

S4004: Determine whether it is "user login point lookup request message", if not, go to S4005, if yes, go to S4100;

S4100: extracting a random sequence in the message; S4101: Find the corresponding sender in the forwarding relationship list, if yes, go to S4106, if not, go to S4102;

S4102: present a user identifier and a requested user identifier in the message;

S4103: Query whether the requested user identifier exists in the user login information record table, if yes, go to S4200, if not, go to S4104;

S4104: Determine whether the unit is a top-level registration server, if yes, go to S4107, if not, go to S4105;

S4105: Establish a correspondence between the sender of the message and the message according to the random sequence in the message, and store the information in the forwarding relationship table.

S4106: forwarding a "user login point lookup request message" to the registration service device according to the local target registration server record, and returning to S4001;

S4107: returning a failure message to the sender of the message, and returning to S4001;

S4200: returning a success message to the sender of the message, where the message includes the user login point of the requested user in the user login information record table, and returns to S4001;

S4005: Determine whether it is a response message of "user login point lookup request message", if not, go to S4006, if yes, go to S4300;

S4300: extracting a random sequence in the message;

S4301: Find the corresponding sender in the forwarding relationship list, if any, go to S4302, if not, go to S4001;

S4302: Forward the response message to the sender corresponding to the random sequence, delete the related item in the forwarding relationship list, and return to S4001.

Figure 21 is a flow diagram of a user querying a registration service device for a user login point through a user terminal.

S4800: Start;

S4801: setting a timeout period;

S4802: generate a random serial number;

S4803: Send a “user login point lookup request message” to the registration service device according to the record of the local target registration server, where the message includes a random serial number;

S4804: Waiting for a reply;

S4805: Determine whether it times out, if yes, go to S4806, if not, go to S4810; S4810: Determine whether the random serial numbers in the message are the same, if different, go to S4804; S4820: whether it is a success message, if not, go to S4830, if yes, go to S4821; S4821: extract the network address and port in the message;

S4822: End;

S4830: Is it a failure, if yes, go to S4822, if not, go to S4804;

S4806: Send a "user login point lookup request message" to the registration service device according to the record of the local target registration server, and the message includes a random serial number, and returns to S4804.

5, the basic message format message name purpose message basic content additional description service unit note marriage h to the registration service - install message type, network

Message registration address, port, standard

Knowledge, prefabricated level letter

Interest

Broadcast message to the registration service - single message type, broadcast

Yuan broadcasts the marriage service of the service device

Service portal

Entrance

Service entry check J query registration Λ message type,

Message device

mouth

User registration acknowledgment - Add user Message type, User Add a logo to the system New user User registration, Find user _ No Message type, User

Query message Open account in the system Identification User login response - User login Message type, user User login point can be identified, user login. Is the network address and endpoint, port, or can be transferred

4匕 is the network address and port of the user only login point: query is requested - with message type, user

Find the user's wall record of the request message, and request it.

Accountant identity, random order number

Success Reply Message To the message sender, the message type identifier, for "user login returns a success message, the response message corresponding to the point lookup request message, request message information" includes user login. Recorded points, random serial numbers.

For "service entry query messages" include network addresses and ports.

For other requests, see related algorithm requirements.

Failure response message to the message sender, the message type identifier,

Return failure information

Request message class

type.

Redirect message To the message sender, the message type is identified, and the redirect message is a type that should return a request A message including the registration corresponding response. The message type of the service device, the message for querying the registration address and port setting service entry, return the corresponding network address and port for the response of other requests, see related algorithm requirements.

6. Improvement of registration service system based on session protocol

In a multi-layer NAT network, because of the existence of a NAT device, the terminals cannot directly access each other. The call system represented by the Session Initiation Protocol (SES) uses signaling. The way to pass communication requests between terminals. The communication mode in which the call and the data transmission are separated can effectively solve the problem of data communication between terminals in the multi-layer NAT network. The following is based on the SIP protocol and describes how the registrar provides services to the calling system.

In order to facilitate the call system to transfer call requests between system terminal devices, the system terminal is set. The user is required to pass user login messages using messages and entities defined in the SIP protocol, such as using REGISTER messages instead of user login messages. According to the user login information and the requirements of the registration service device, the Proxy is responsible for extracting relevant information in the REGISTER message, and transmitting relevant information to the registration service device, and is also responsible for updating the content of the REGISTER message. The registration service device is only responsible for storing the user login information, and no longer directly receives the user login message, the user login point lookup request message sent by the system terminal device, and does not forward the user login message or the user login point lookup request message. The original "user login message": user ID, user login point, etc., corresponding to From, Contact in the REGISTER message. The manner in which the system terminal device obtains the Proxy network address and port is determined by the calling system formed by the Proxy server, and the method for obtaining the registration service device by the system terminal device can be referred to. In a SIP-based system, the service unit associated with the user's logon point is the Proxy server.

The method in which the system terminal device having the SIP module obtains the network address and port of the Proxy server is determined by the calling system composed of the Proxy server. The network address and port of the Proxy server are stored in the target Proxy server record of the system terminal device. The target registration server of the system terminal device records the global service entry for recording the top-level registration service device, and is used to complete the registration according to the above registration process. According to the global service portal system terminal device, registration is completed according to the above registration process. The system terminal periodically sends a REGISTER message to the Proxy.

Figure 23 shows the user login registration information forwarding correspondence table in the Proxy. The table includes random sequence numbers, network addresses, ports, and acknowledgment status bits. Random serial numbers are used to distinguish REGISTER messages. The acknowledge status bit is used to indicate the reply received by the registration service device. When the bit is 0, it indicates that no reply has been received; when the bit is non-zero, it indicates that a reply is received, for example, it is set to 1 and the response status bit defaults to 0.

The Proxy server receiving the REGISTER message generates a "Call Agent User Login Message" according to the flow of Fig. 24, updates the REGISTER message, and submits the login information to the registration service device. The registration service device receives the "Call Agent User Login Message" and stores the contents of the registration message in the user information record table. The "Call Agent User Login Message" includes information such as user identification, user login point, system terminal device access point, and so on.

S6000: Start;

S6001: Waiting for a message;

S6002: Whether it is a REGI STER message, if yes, go to S6100, if not, go to S6003;

S6003: Other processing, and return to S6001; S6100: Determine whether the Contact item in the message is a child Proxy server, if yes, go to S6101, if not, go to S6200;

S6101: using the content of the From in the REGSITER message as the user identifier, and using the network address and port of the Proxy as the user login point; generating the "call" as the system terminal device access point by using the source address and the source port of the data packet carrying the REGISTER message Proxy user login message", sequentially executing S6304;

S 6200: determining whether the Con t a c t item in the message is used to identify the network address and port of the system terminal device, and if so, to the S6300, if not, to S6303;

S6300: Determine whether the REGISTER registration message passes through the NAT device, if it is to S6301, if not, go to S6303;

S6301: Extract a source address and a port of a data packet carrying the message;

S6302: The content of the From in the REGISTER message is used as the user identifier, and the network address and port of the Proxy are used as the user login point; and the obtained source address and source port are used as the system terminal device access point to generate a "Call Agent User Login Message". , executing S6304 in sequence;

S6303: The content of the From in the REGISTER message is used as the user identifier, and the "call agent user login message" is generated by using the Contact content as the user login point, and sequentially executing S6304;

S6304: The correspondence between the sender and the message is established according to the random sequence number in the message, and is stored in the "user login information forwarding correspondence table", and the response status bit is "0", and the REGISTER message is temporarily stored;

S6305: Send a "Call Agent User Registration Message" to the registration service according to the service entry of the locally stored registration service device;

S6400: Determine whether the server is a top-level proxy server. If yes, go to S6001. If not, go to S6306.

S6306: Determine whether the Contact item in the message is used to identify the system terminal device or the child Proxy server. If yes, go to S6307, if not, go to S6308;

S6307: Use the identifier of the Proxy or the network address and port to replace the content in Con tact to generate a new REGISTER;

S6308: Forward the newly generated REGISTER message to the superior Proxy and return to S6001. Since the REGISTER message is forwarded between Proxy, the sub-Proxy record of this Proxy There are information about the Proxy ID and the NAT device in the subordinate network. Therefore, when the Proxy ID is used as the system terminal access point, it can be mapped to the network address and port on the NAT device.

Fig. 25 shows the structure of a user login information storage table in the registration service unit. In order to adapt to the Proxy server, the structure has been extended in the original structure. The structure includes information such as user identification, user login point, system terminal device access point, relative login location, mapped address, and the like. The relative login location indicates whether the network address of the user login point and the registration service unit belong to the network controlled by the same NAT device or the public network. The cross-layer registration can be represented by 1, and the same layer registration can be represented by 0. The default value is 0; : The network address and port of the NAT device when the "Call Agent User Login Message" message traverses the NAT device. The mapping address is empty when the peer is registered. The system terminal access point can also be empty. Figure 26 is a flow chart of the registration service device processing the "Call Agent User Login Message".

S7000: Start;

S7001: Waiting to receive a data packet;

S7002: Whether to receive the data packet, if yes, transfer to S7003, if not, switch to S7001;

S7003: Extracting a message in a data packet;

S7004: Determine whether it is "Call Agent User Login Message". If yes, go to S 7006. If not, go to S7005.

S7006: Create a new record in the user information storage table;

S7010: Determine whether the message passes through the NAT device. (If the network address of the user login point and the source address of the data packet carrying the request message are equal, determine whether the NAT device is passed.) If yes, go to S7011, if not, go to S7013. ;

S7011: Set the relative login location of the record to cross-layer login;

S7012: Fill in the mapping address of the record by using the source address and port of the data packet carrying the message, and sequentially execute S7013;

S7013: Fill in the related items of the record according to the user identifier, the user login point, the system terminal access point, and the like in the message, and return a success message, indicating that the login is successful, and returning to S7001;

S7005: Perform other processing and return to S7001.

Receive a "Call Agent User Login Message" from the logically registered service unit. The information is stored in the user login information record table, and there is no failure problem. However, in practice, there are various causes of failure, such as system problems such as full recording medium and large number of concurrent. Therefore, the party that processes the response message is to process the error response message that the registration service unit may return.

The Proxy server processes the response message returned by the registration service device and the response message of the REGISTER message in accordance with the flow of FIG.

S6500: Start;

S6501: Waiting for the message;

S6600: Is the "Call Agent User Login Message" response message, if yes, go to S6610, if not, go to S6800;

S6610: Determine whether the Proxy server is a top-level proxy server (or whether the response message sender is a top-level registration service unit, for example, can be judged by a public network address), if yes, go to S6620, if not, go to S6611;

S6620: Determine whether it is a success message, if yes, go to S6621, if not, go to S6622;

S6621: According to the random sequence number in the message, find the related item in the "user login message forwarding correspondence table", and generate a success response message of the relevant REGISTER message according to the content of the related REGI STER message, sequentially executing S 6623;

S6622: According to the random sequence number in the message, find the related item in the "user login message forwarding correspondence table", and generate a failure response message of the related REGISTER message according to the content of the related REGI STER message, sequentially executing S 6623;

S 6623; returning a response message of the REG STER message to the sender of the REG STER message;

S6624; Delete the relevant item and the corresponding REGISTER message from the "user login message forwarding correspondence table", and return to S6501;

S6611: Determine whether it is a success response message. If yes, go to S6612, if not, go to S6501;

S6612: According to the random sequence number in the message, find the related item in the "user login message forwarding correspondence table", and set the response status bit to the response message of the registered service device, for example, 1, return to S6501;

S6800: Is the response message of the REGI STER message, if yes, go to S6801, if not, go to S6900; S6801: According to the random serial number in the message, find the related item in the "user login message forwarding correspondence table";

S6802: Determine whether the response status bit of the related item in the "User Login Message Forwarding Correspondence Table" indicates that the registration service device has received a successful response, if not, go to S6803, if yes, go to S6805;

S6803: According to the random sequence number in the message, find a related item in the “user login message forwarding correspondence table”, and generate a failure response message of the related REGI STER message according to the related content;

S 6804: returning the response message of the REG I STER message to the sender of the REG I STER message, and executing S6806 in sequence;

S 6805: returning the response message of the REG I STER message to the sender of the REG STER message, and executing S6806 in sequence;

S6806: Delete the related item from the "User Login Message Forwarding Correspondence Table", and the related temporary REGI STER message, and return to S6501;

S6900: After other processing, return to S6501.

The Proxy requests the registration service device to forward the call message (for example: INVI TE message of the SIP protocol). The Proxy sends a "Call Agent User Login Point Lookup Request Message" to the registration service device. The Proxy forwards the call message according to the reply message received by the registration service device. When forwarding a call message between Proxy, the corresponding feedback message is forced to return according to the original path of the forwarding request message. The "Call Agent User Login Point Lookup Request Message" includes at least the target user ID and the proxy's network address. When the request message is transmitted between the Proxy (for example, the INVITE message of the S IP protocol), the target user identifier is the called party user identifier, and when the feedback message is transmitted between the Proxy (for example: 200 messages of the SIP protocol), the target user Identifies the calling party user ID.

Figure 28 is a flow diagram of the registration service unit processing the "call agent user login point lookup request message".

S8000: Getting started

S8001: waiting to receive a data packet;

S8002: Whether to receive the data packet, if received, transfer to S8 QQ 3, if not received, transfer to S8001;

S8003: extracting a message in a data packet; S8004: Determine whether it is "Call Agent User Login Point Lookup Request Message", if yes, go to S8102, if not, go to S8006;

S8102: the target user identifier in the proposed message;

S8103: Find in the user information table whether the target user identifier exists, if yes, go to S8200, if it does not exist, go to S8104;

S8104: Determine whether the server is a top-level registration server. If yes, go to S8107. If not, go to S8105.

S8105: Return a message that the target user identifier does not exist to the sender of the request message, and return to S8001;

S8107: returning a failure message to the sender of the request message, and returning to S8001;

S8200: determining, according to the relative registration location and the mapping address, whether the network address corresponding to the user login point of the target user and the network address of the sender of the "Call Agent User Login Point Lookup Request message" belong to a network or public network controlled by the same NAT device, if Yes, go to S8201, if not, go to S8202;

S8201: discriminate whether the user login point of the target user belongs to the request message sender, if yes, go to S8203, if not, go to S8204;

S8203: returning the target user's system terminal device access point to the request message sender, and returning to S8001;

S8204: returning the user login point of the target user to the sender of the request message, and returning to S8001;

S8202: Return a message that the target user identifier does not exist to the sender of the request message, and return to S8001;

After the Proxy receives the response message of the "Call Agent User Login Point Lookup Request Message", if it fails, the Proxy returns a failure message to the system terminal device according to the reverse direction of the call message delivery path; if the target user does not exist, the target is The Proxy forwards the call message; if the received response message contains information that can be translated into a network address and port, the call message is forwarded to the network address and port.

It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not limited thereto, and may be extended to other modifications, changes, applications, and embodiments, and all such modifications and changes are considered. The application, the embodiments are all within the spirit and scope of the invention.

Claims

Rights request

1. A multi-layer NAT environment, wherein the multi-layer NAT environment includes a public network and at least one private network, and the private network accesses a public network or other private network through an address translation unit; The name registration system includes a system terminal device, a call proxy server, and a registration service device that accesses the public network and at least one private network;

The system terminal device is configured to exchange information with the registration service device and the call proxy server, and send the user login information to the registration service device by using the call proxy server; the system terminal device is configured to identify the SIP protocol, use the message defined in the SIP protocol, and The entity passes the user login message;

The call proxy server includes a top-level call proxy server connected to the public network and a call proxy server connected to each private network, used to forward the message specified in the SIP protocol, and forwarded according to the indication of the registration service entity or other functional entity. The message, the call proxy server acquires a service portal from the registration service device, transmits user login information to the registration service device, and queries the registration service device for the user login point.

2. The name registration system according to claim 1, wherein the registration service unit is further configured to perform an inquiry according to the recorded user login information.

3. The name registration system according to claim 1, wherein the user login point is a network address and port of a registered monthly service unit or a system terminal device, or is converted into a network address of a registration service unit or a system terminal device. And the identifier of the port; the system terminal access point is the network address and port of the NAT device, or the identifier of the network address and port that is converted into the NAT device.

4. The name registration system according to claim 2, wherein the query is to find a user login point with the shortest distance from the called party to the calling party NAT in all the user login points of the called party according to the user login information.

5. The name registration system according to claim 1, wherein the registration service unit comprises a top-level registration service unit accessing a public network and a basic registration service unit accessing a private network.

6. The name registration system according to claim 5, wherein the top-level registration service unit accesses a public network through a top-level service bus, and the basic registration service unit accesses a private network through a service bus, and the top-level service bus The top-level registration service unit accessing the public network is addressed using the network address of the public network, and the basic registration service unit accessing the private network through the service bus is addressed using the network address of the connected private network.

7. The name registration system according to claim 1, wherein the registration service unit comprises: a registration service logic control unit, a basic configuration information record table, a hierarchical information record table, a target registration server record table, and a sub-registration service unit record. Table, user registration information record table, user login information record table, message buffer, and communication unit.

8. The name registration system according to claim 7, wherein the registration service logic control unit is configured to control execution of a registration service; the basic configuration information record table is used to record the identity of the unit, the host address of the unit, and the present a unit service port; the hierarchical information record table is used to record hierarchical information; the target registration server record table is used to record a network address and a port of an ancestry registration server; and the sub-registration server record table is used to record a sub-registration service unit a network address, a port, an identifier, and a network address and a port of the corresponding NAT device; the user registration information record table is used to record a user identifier, a user registry, and a system terminal device access point; and the user login information record table is used for recording a user identifier, a user login table, and a system terminal device access point; the message buffer area is configured to temporarily save information in the received data packet, and forward a relationship record table; the communication unit is coupled to the top-level service bus device or the service bus device , responsible for sending and receiving data;

The registration service logic control unit is configured to implement the basic configuration information record table, the hierarchical information record table, the target registration server record table, the sub-registration server record table, and the user registration information record. The table, the user login information record table, the message buffer area, and the data of the communication unit are bidirectionally exchanged.

9. The name registration system according to claim 1, wherein said registration service unit comprises a service unit agent for expanding coverage of a registered registration service unit or for providing to a system terminal device A unified service portal; the service unit proxy may be deployed on the network or public network controlled by the same NAT device as the agent, or may be deployed in the direct lower layer network of the network to which the agent belongs.

10. The name registration system according to claim 9, wherein the service unit agent is for broadcasting a service entry of the agent or forwarding the message between the requester of the registration service device and the proxy registration service device.

11. The name registration system according to claim 1, wherein said system terminal The device includes a terminal device control unit, a basic configuration information record table, a target registration server record table, a target call proxy server record table, a message buffer area, and a communication unit, and the basic configuration information record table is used to record the user identifier and the network address of the terminal device. Information such as a port; the target call proxy server record table is used to record a network address and port of the call proxy server, the target registration server record table, a global service entry for recording a top-level registration server; and a message buffer for temporarily storing a message to or from the communication unit; the communication unit is used for a public network or a private network connection, and the terminal device control unit reads and writes information from the basic configuration information record table, the target registration server record table, the target call proxy server record table, the message buffer area, The terminal device control unit transmits and receives data from the network through the communication unit.

The name registration system according to claim 11, wherein the system terminal device comprises a SIP protocol processing unit, and interacts with the terminal device control unit to identify an S IP message.

The name registration system according to claim 1, wherein the call proxy server is configured to acquire a network address and a port of the registration service device by referring to the manner in which the system terminal device acquires the network address and port of the registration service device. .

14. The name registration system according to claim 1, wherein the call proxy server needs to ensure that the registration service unit corresponding to the service portal of the call proxy server and the registration service device is deployed when acquiring the service portal of the registration service device. The registration service unit corresponding to the service controlled by the same NAT device or the service entry of the registration service device is located directly above the call proxy server.

15. The name registration system according to claim 14, wherein the call proxy server in the upper layer network serves as a default destination for forwarding the SIP message by the local call proxy server, and needs to be saved in the upper layer network in the local call proxy server target call proxy record. The network address and port of the call proxy server; at the same time, the call proxy server in the upper network saves the identity of the call proxy server, the network address, the port, and the network address and port of the corresponding NAT device in the sub-call proxy record.

16. A method of using a name registration system according to any one of claims 1 to 15 for name registration, comprising:

Step 20), according to the service entry of the locally stored registration service device, the call The proxy server sends a "Call Agent User Login Message" to the registration service device, and forwards a REGISTER message to the upper call proxy server, the REGISTER message includes a user identifier; the monthly service portal is a network address and port or is used for conversion The label for the network address and port;

The method for registering a name according to claim 16, wherein the user login point is a network address and a port, or is converted into an identifier of a network address and a port; and the system terminal device access point is a network address and a port. , or an identifier that is translated into a network address and port.

The method for registering a name according to claim 16, wherein, before the step 10), the top-level registration service unit of the access public network is started, and then the basic registration service unit of the access private network is started layer by layer, and The name registration system is registered to join the name registration system.

The method for naming a name according to claim 16, wherein the step 10) further comprises:

Step 130), when the Contact item in the REGISTER message is used to identify the system terminal device And the REGI STER message passes the Contac t content as a user login point when there is no NAT device;

Step 140), when the Contac t item in the REGI STER message is not a call proxy server, nor is it used to identify the system terminal device, the Contac t content is used as a user login point.

The method for registering a name according to claim 16, wherein the step 20) further comprises: if the Contac t item in the REGI STER message is a call proxy server or an identification system terminal device, using the call proxy server The network address and port proxy the network address and port in the Contac item.

The method for registering a name according to claim 16, wherein the step 30) further comprises: when the "call agent user login message" passes through the NAT device, setting a relative login location in the local user information storage table to Cross-layer login, will carry the

The source address and port of the "Call Agent User Login Message" are the mapped addresses of the new record.

22. The method of name registration according to claim 16, wherein the step 40) further comprises:

The method for naming a name according to claim 16, wherein the step 50) further comprises:

24. A method of querying a user login point using the name registration system of one of claims 1 to 15, comprising:

Step 10), the call proxy server sends the service portal of the name registration system a "call agent user login point lookup request message", the message includes a target user identifier; step 20), after receiving the "call agent user login point lookup request message", the registration service unit extracts the target user identifier in the message;

Step 40), when the target user identifier exists, determine whether the network address corresponding to the user login point of the target user and the network address of the sender of the "Call Agent User Login Point Lookup Request message" belong to the same NAT device controlled network or public The network, if not, returns a target user non-existent message to the request message sender;

The name registration point query method according to claim 24, wherein the method further comprises:

Step 60) After the call proxy server receives the response message of the "Call Agent User Login Point Lookup Request Message", if it is a failure, the call proxy server returns a failure message to the system terminal device according to the reverse of the call message delivery path; If there is no message for the target user, the call message is forwarded according to the target call agent record; if the received response message contains information that can be converted into a network address and port, the SIP call request is forwarded to the convertible network address and port.

The method for querying a name registration point according to claim 24, wherein, in step 40), determining whether the network address corresponding to the user login point of the target user and the call agent user login point lookup request are based on the relative login location and the mapped address The sender's network address belongs to the network controlled by the same NAT device or the public network.