WO2009006770A1

WO2009006770A1 - Method of p2p node management

Info

Publication number: WO2009006770A1
Application number: PCT/CN2007/003539
Authority: WO
Inventors: Sui Xiao; Xin Zhang; Hongliang Tian; Zheng Huang; Ling Hong
Original assignee: Zte Corporation
Priority date: 2007-07-12
Filing date: 2007-12-11
Publication date: 2009-01-15
Also published as: CN101345684A; CN101345684B

Abstract

A method of P2P node management is disclosed. It includes a user management entity and a node management entity in administrable P2P operation network are divided into an application layer corresponding to operation and a P2P layer not corresponding to operation. The application layer and the P2P layer interact by an interface. When a user registering and logging on, the application layer and the P2P layer are bound completely. The solution adapts to different P2P operation modes. At the same time, it can well match operation policy via adjusting choice policy of P2P management server and auxiliary server, and reduce the affect for existed or new application system in the upper layer.

Description

The present invention relates to the field of communications, and in particular, to a P2P node management method. BACKGROUND The so-called P2P (Peer to Peer) technology is a peer-to-peer network technology. In a P2P network, the status of each node is equal. It is both a server and a client, and each node enjoys While the services provided by other nodes are also serving other nodes. Because P2P technology makes full use of the computing power of each node, it has great advantages in terms of scalability and construction cost. In recent years, various Internet applications based on P2P technology such as file sharing and streaming media have developed rapidly. P2P download traffic has accounted for more than 70% of the total Internet data traffic in the world. P2P technology has become an important media delivery technology for broadband Internet. In contrast, the traditional telecom service architecture (C/S architecture) faces the challenges of high construction costs and poor scalability when providing large-scale services. How to introduce P2P technology in the field of telecommunications, while taking advantage of its self-adaptable growth and low construction cost, it solves its serious lack of functions in user management and access security, and provides carrier-class operational and manageable. P2P applications have become a hot topic in the industry. SUMMARY OF THE INVENTION In view of one or more of the above problems, the present invention provides a P2P node management method, which can be applied to different P2P operation modes, and can also adjust the selection strategy of the P2P management server and the auxiliary server. Match the operational strategy and have less impact on the original or newly created upper application system. The P2P node management method of the present invention includes: dividing a user management entity and a node management entity in a manageable P2P operation network into an application-related application layer and an operation-independent P2P layer, and an application layer and a P2P layer interacting through the interface. Binding at the application level and P2P level when the user registers and logs in. Among them, the P2P central management subsystem in the P2P operation network and the P2P section of the user terminal The points are divided into functional entities at the P2P level, and other parts of the P2P operating network are divided into functional entities at the application level. The node identity and the P2P management server address are assigned to the P2P node by the node management entity in the P2P node registration or login process. The node management entity specifies the secondary server required for system operation in the P2P node registration or login process. The P2P management server or the secondary server may be selected by at least one of the following: a proximity service, a home service, and a load balancing service.

The P2P node management method includes: Step 1: The user terminal obtains the address of the registration server from the system configuration data. Step 2: The user initiates the login request, where the login request carries the location information of the user and the P2P node identifier, and the P2P node identifier Empty; Step 3: The registration server assigns a P2P node identifier to the user terminal according to the preset policy and specifies the login server address, and feeds the P2P node identifier and the login server address to the user terminal in the response message; Step 4: User terminal Recording the P2P node identifier and the login server address fed back, and initiating a login request to the login server; and step 5, the login server initializes the P2P initialization information for the user terminal according to the preset policy. When logging in at the user terminal, you can see the terminal interface, but you do not need to enter a username and password. When the user terminal logs in, the terminal interface cannot be seen. When the user terminal logs in, the encrypted user name and password pair or the node identifier and access password pair assigned by the system are carried. The node management can be centralized or centralized in the whole network. For the domain management, the login server and the registration server can be located in the same management domain or different management domains. The P2P node management method of the present invention can be applied to different P2P operation modes. At the same time, it can also closely match the operation strategy by adjusting the selection strategy of the P2P management server and the auxiliary server, and has less influence on the original or newly built upper application system. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are set to illustrate,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, In the drawing: 1 is a schematic structural diagram of a specific implementation system for implementing the present invention; FIG. 2 is an example of realizing the binding of the user management of the operating layer and the node management process of the P2P layer; and FIG. 3 is a schematic diagram of the implementation process of the domain management of the node . DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, specific embodiments of the present invention will be described in detail with reference to the accompanying drawings. No matter whether it is on the Internet or on the telecommunications network, there is no universal node management method that can adapt to different operating modes. The present invention proposes a P2P node management method that is independent of a specific operation mode: it divides user management in a manageable P2P operation network into an operation-related application layer and an operation-independent P2P layer at two levels, in the user Two levels of binding are completed when registering and logging in. In this way, the flexible combination of P2P node management and any operation mode can be conveniently implemented, and can also be used in different applications. Such evolution of the operating model and application updates will not affect the operation of the underlying P2P approach. The implementation of this management method is shown in Figure 1. The operationally manageable P2P system comprises five subsystems: a user terminal, a service subsystem, an operation management subsystem, a P2P central management subsystem, and a carrier back-end subsystem, wherein the P2P central management subsystem and the P2P node part of the user terminal belong to the present The P2P level functional entities of the system are identified by shading in Figure 1. The rest is part of the operational level functional entity of the system. The two levels of processing are independent of each other and interact only through interfaces. The service subsystems identified by the dashed lines, the operator back-end subsystems, and the application clients in the terminals are not directly related to the present invention, and their existence is only to ensure the integrity of the system structure. In FIG. 1, functional entities closely related to the present invention include: a P2P node of a user terminal, a node management of a P2P central management subsystem, and a user management of an operation management subsystem. The node management is responsible for providing registration and login verification functions of the P2P node; the user management is responsible for providing the user's registration, login, and insurance functions. In a practical implementation, the user management and the node management have different deployment scenarios, which may be a function module of a certain physical function device, such as a user management device in the integrated service management platform, or may be one or more A discrete physical device, such as a node management function entity, may include two physical entities, a node registration server, a node login server, or a physical entity. In the solution of the present invention, each user has a user identifier that can uniquely identify his or her identity, and the identifier may be an existing telephone number (including a mobile phone, PHS number), a broadband Internet account, or an operation in the telecommunication network. The user ID defined for the P2P application can be obtained through WEB registration, business hall application, or terminal registration and identity confirmation. This identifier is an application-level user identifier that can be used for billing, user management, user behavior analysis and statistics, etc. It is related to the operating mode and application. Each P2P software installed on the user terminal has an identity similar to the IMSI of the handset, which uniquely identifies the soft terminal (P2P node). The P2P node identifier may be a fixed identifier or a dynamic identifier. When the fixed identifier is used, when the user installs and runs the P2P terminal software for the first time, the P2P node identifier specified by the system is obtained. When the dynamic P2P node identifier is used, when the user logs in to the P2P network, the P2P node identifier that is valid for the current login specified by the system is obtained. The P2P node identifier is a user identifier of the P2P layer and can be used for node management, resource management, and P2P node behavior analysis and statistics. It is independent of the operation mode and application. However, the association between the P2P node identifier and the user identifier can be used in the operation and application process. It is reflected in it. In actual operation, operators can associate two levels of processing according to their needs. Figure 2 illustrates, in one embodiment, the association between the operational level and the P2P level process, where the user registration is independent of the registration of the P2P node. In the P2P level node registration/login process shown in Figure 2, the system not only assigns the node identifier to the P2P node, but also specifies the default or current login required for the P2P method to run according to the predetermined policy. A valid P2P management server address. In general, the default settings can be done in the node registration process, and if necessary, in the login process. The server that is valid for the current session can be specified through the login process.

Ρ2Ρ The management server includes servers that provide resource query (group member query), resource management, and resource scheduling functions. They may be single-function independent functional entities or combined functional entities with multiple functions. The resource refers to a media file slice that exists in the form of a segment. In addition to the 良2Ρ management server, in the solution of the present invention, the 注册2Ρ node management entity and the Ρ2Ρ node registration/login process can also be utilized to specify other necessary auxiliary servers required for system operation, such as providing terminal version automatic update. A functional (terminal) version server, a content directory server for displaying, querying content, and the like. These secondary servers can be specified as default home servers when registering, and can be modified during the login process if necessary. In the above manner, users do not need to understand complex network deployment, and all the server information required for the normal operation of the system can be obtained through a simple user login process. It is called initial fc information.

The selection strategies of the P2P management server and the auxiliary server include a plurality of nearby services, home services, load balancing, and the like. The so-called near-month service refers to selecting the geographically adjacent server according to the current address of the node; the home service is to specify the server according to the address when the node is registered; the load balancing is based on the load of the relevant server in the network. Status, the average distribution of business. The above strategies can be used singly or in combination.

The selection policy of the P2P management server and the secondary server can be defined and configured through the operations management subsystem. How to define and configure the P2P management server and the secondary server selection strategy can be found in the patent "A P2P Network Application System and Network Side System"> and "A P2P Network Application Method". Through the adjustment of the strategy, operators can easily adjust the operation of the P2P network to better meet the operational needs, but it will not affect the operation process of the P2P network. In the solution of the present invention, the node management solution for unified management or sub-i or management of the entire network can be flexibly selected, and the selection and change of the deployment plan of the P2P layer will not affect the deployment and process of the upper-layer operation layer, nor will it affect. A large number of terminals. In addition, in the present invention, different node management deployment schemes may also be adopted, such as a unified registration server throughout the network, but multiple login servers; the registration server and the login server may also have the same or different administrative domains. (For example, the management domain of the registered server is larger than the management domain of the login server). Figure 2 has only one unified node management point, which can be regarded as an embodiment of unified network node management. Including the following step S202, the user performs user registration with the user management/authentication server, and if necessary, inputs the user password. Step S204: The user management/authentication server allocates a user identifier and records the password of the user, and feeds back a response message carrying the user identifier to the user. In step S206, the user logs in by using the username and password. Step S208: The user management/authentication server performs the user login process processing at the operation level, and feeds back a response message carrying the user identifier to the user. Step S210, the user uses the service, if the terminal is not installed, the system prompts to install the terminal first. End. In step S212, the user installs the terminal, the terminal runs, and performs user login. Step S214, the P2P2 node registers/logs in, and the message sent to the node management entity carries the user login information. Step S216, performing processing of the node registration/login process, and feeding back the user registration/login processing response message to the user management/authentication server, where the initialization information is carried. Step S218: The operation and the management layer are managed, and the correspondence between the user identifier and the identifier of the node is recorded. In step S220, the user management/authentication server feeds back the login success response to the user, and sends back the node registration processing result, such as the node identifier, the initialization information, and the like. Step S222, the user terminal records the 标识2Ρ node identifier and the Ρ2Ρ initialization information, and the user terminal runs successfully. FIG. 3 illustrates an implementation method of a node domain management scheme in an embodiment. In this embodiment, there is only one registration server, but there are multiple login servers, that is, the registration server and the login server have different management i or. The specific implementation steps are as follows: Steps S302-S304, the user installs the terminal, selects or inputs his own location information, and after the terminal runs, obtains the address of the registration server from the system configuration data. Step S306, the user inputs a user name and a password to initiate a login request, and carries the location information of the user and the P2P node identifier in the request, and the node identifier is empty. Steps S308-S314, the registration server allocates a node identifier to the terminal according to the preset policy, and specifies a login server address, and returns a node identifier and a login server address in the response. Steps S316-S318, the terminal records the login server address and the node identifier returned in the response, and initiates a login request to the login server in the background (in a manner that the user cannot perceive). Step S320, the login server configures P2P initialization information for the node according to the preset policy, and feeds back initialization information to the user management entity and the user terminal. Step S322, the user terminal records initialization information, and the user management entity records the user identifier. Correspondence with the node ID. In step S324, the user successfully logs in and the terminal runs successfully. In actual deployment, it is also possible to adopt a scheme in which the registration server and the login server are deployed in different domains. Regardless of the solution, for the terminal, it is only necessary to know the registration server in advance, and the registration server is relatively stable throughout the P2P network. Even if there is a change, it can be conveniently updated by updating the terminal software installation package. Make changes. In the actual deployment, the user login process described above can be completed in an implicit login manner. It can be in the following two forms: The terminal software runs in the foreground, that is, the user can see the terminal interface, but the user does not need to manually input the user name. , the password is completed to log in. The terminal runs in the background mode and completes the login. The user cannot see the terminal interface (but the related process can be seen through the system management tool). The terminal may carry the encrypted username and password pair when logging in, or the system may register with it. The assigned node ID and access password pair. If the operator selects the method of dynamic P2P node identifier allocation, the processing flow is the same as the process described in FIG. 2 and FIG. 3, but the registration server can be omitted, that is, the registration and login are the same process. The P2P node management method according to the present invention can be applied to different P2P operation modes. At the same time, it can also closely match the operation strategy by adjusting the selection strategy of the P2P management server and the auxiliary server, and has less influence on the original or newly built upper application system. The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Claims

Claim

A P2P node management method, comprising: dividing a user management entity and a node management entity in a manageable P2P operation network into an application-related application layer and an operation-independent P2P layer, where the application layer And interacting with the P2P layer through an interface, and completing binding of the application layer and the P2P layer when the user registers and logs in.

The P2P node management method according to claim 1, wherein the P2P central management subsystem and the P2P node of the user terminal in the P2P operation network are divided into functional entities at the P2P level, and the P2P operation is performed. The rest of the network is divided into functional entities at the application level.

The P2P node management method according to claim 2, wherein the node management entity allocates a node identifier and a P2P management server address to the P2P node in the P2P node registration or login process.

The P2P node management method according to claim 2, wherein the node management entity specifies a secondary server required for system operation in the P2P node registration or login process.

The P2P node management method according to claim 3 or 4, wherein centralized management or domain-based management is adopted throughout the network.

The P2P node management method according to claim 5, wherein the P2P management server or the secondary server is selected by at least one of the following: a proximity service, a home service, and a load balancing service.

The P2P node management method according to claim 6, wherein the P2P node management method comprises:

Step 1: The user terminal obtains the address of the registration server from the system configuration data. Step 2: The user initiates a login request, where the login request carries the location information of the user and the P2P node identifier, and the P2P node identifier is empty. ;

Step 3: The registration server resides in a preset policy, allocates a P2P node identifier to the user terminal, and specifies a server address, and feeds the P2P node identifier and the server address to the user in a response message. terminal: Step four, the user terminal records the feedback of the P2P node identifier and the login server address, and initiates a login request to the login server;

Step 5: The login server initializes the P2P initialization information for the user terminal according to a preset policy.

8. The P2P node management method according to claim 7, wherein when the user terminal logs in, the terminal interface can be seen, but the user name and password are not required to be input.

The P2P node management method according to claim 7, wherein when the user terminal logs in, the terminal interface cannot be seen, and the user terminal carries the encrypted user name and password pair or system allocation when logging in. Node ID and access password pair.

The P2P node management method according to claim 7, wherein when the node management of the domain management is adopted, the login server and the registration server are located in the same or different management domains.