The network element device domain name method of automatic configuration of IP Multimedia System
Technical field
The invention belongs to multi-media network configuring technical field, particularly relate to a kind of network element device domain name method of automatic configuration of IP Multimedia System.
Background technology
IMS (IP Multimedia System) is the 3G network core technology standard that 3GPP organizes to set up at first, and is considered to the important technical basis realizing following FMC (fixing/mobile network is merged).IMS network comprises three kinds of dissimilar sip proxy servers: proxy CSCF (P-CSCF), inquiry CSCF (I-CSCF) and serving CSCF (S-CSCF), also comprise following or CSCF (CSCF): Breakout Gateway Control Function (BGCF), MGCF (MGCF), media resource controlling functions (MRFC), media resource processing capacity (MRFP) and media gateway (MGW).IMS core framework also comprises signing locator function (SLF) and the application server of ownership place client server (HSS) and the storage HSS address storing user data, and its structure chart as shown in Figure 1.Application server comprises three classes: sip application server, OSA application server and CAMEL IM-SSF.Sip application server is for realizing the valued added applications based on SIP, OSA application server is for realizing the application based on OSA, OSA application server need be undertaken alternately by OSA service capability server (SCS) and IMS core net, and CAMEL IM-SSF is for supporting that IMS business uses CAMEL professional ability.
In Fig. 1, core network is responsible for the basic capacity providing IMS, as Call-Control1 etc.And service enabler application server provides various enhancing professional ability, as POC, Presence, instant message etc.Service enabler can be the SIP service enabler based on 3GPP or OMA, also comprises the IN service engine (IM SSF) for supporting to use CAMEL.OSA service capability server is used for supporting to meet the application of OSA framework, and it carries out abstract to miscellaneous service ability, and provides it to application and conduct interviews.
Call routing due to IMS network is in fact determine down hop according to the address of called subscriber or be directly targeted to terminal called, the address of called subscriber can be E.164 number, URL (uniformResource Locator, uniform resource locator) form or IP address, therefore DNS (Domain NameSystem, domain name resolution server) be part indispensable in the middle of IMS network, it provides the translation function between domain name and IP address for user.IMS network service all depends on domain name resolution service.
When constructing IP IP multimedia subsystem, IMS (IMS) network, network element is as I-CSCF, S-CSCF, the network element device such as P-CSCF, HSS and application server, its IP address and domain name need manually to be configured at dns resolution server, after having configured, if network element device IP address changes, also needing at dns resolution server again to the configuration of domain name and IP address, just there is the problem of dynamic binding between the domain name of network element and the IP address of network element in this.
Summary of the invention
The object of the invention is to, provide a kind of network element device domain name method of automatic configuration of IP Multimedia System, there is the problem needing manually to reconfigure network element domain name and network element IP address when changing in the network element device domain name in order to solve IP Multimedia System.
For achieving the above object, technical scheme provided by the invention is, a kind of network element device domain name method of automatic configuration of IP Multimedia System, realizing by being arranged on registration customer side on each network element device of IP Multimedia System, registrar and domain name resolution server, it is characterized in that described method comprises:
Step 1: set up domain name registration grant table and domain name registration database;
Step 2: registered client sends connection request to registrar, after registrar receives connection request, sets up and is connected with the network of registered client;
Step 3: registrar judges the message whether receiving registered client transmission in setting-up time, if receive the message of registered client transmission in registrar setting-up time, then performs step 4; Otherwise, perform step 6;
Step 4: registrar judges that the message that registered client sends is heartbeat message or request message, if the message that registered client sends is heartbeat message, then returns step 3; Otherwise, perform step 5;
Step 5: the request message type sent according to registered client, configuration domain name resolution server, returns step 3;
Step 6: the domain name of the network element device that de-registration client is corresponding, returns step 2.
Described request type of message comprises binding domain name request, nullifies domain name request and change domain name request.
When described request type of message is binding domain name request, described step 5 specifically comprises:
Step 101: according to binding domain name request, registrar judges whether registered client is legal registered client, if registered client is legal registered client, then performs step 102; Otherwise, perform step 105;
Step 102: registrar checks domain name registration grant table, judges whether the domain name of registered client meets the requirements, if the domain name of registered client meets the requirements, then performs step 103; Otherwise, perform step 105;
Step 103: registrar checks the connectedness of IP address to be bound, if IP address to be bound can be communicated with, then performs step 104; Otherwise, perform step 105;
Step 104: set up the domain name of registered client and the mapping of IP address to be bound in domain name resolution server, joins in domain name registration database by the domain name of registered client and IP address to be bound simultaneously, performs step 106;
Step 105: return binding domain name request failure message;
Step 106: complete domain name resolution server configuration.
When described request type of message is for nullifying domain name request, described step 5 specifically comprises:
Step 201: the domain name of searching registered client in domain name registration database, deletes the record that the domain name of registered client is corresponding;
Step 202: the domain name of searching registered client in domain name resolution server, deletes the mapping of the domain name of registered client and the IP address of its binding.
When described request type of message is for change domain name request, described step 5 specifically comprises:
Step 301: registrar checks domain name registration grant table, judges whether the domain name to be changed of registered client meets the requirements, if the domain name to be changed of registered client meets the requirements, then performs step 302; Otherwise, perform step 304;
Step 302: the domain name of searching registered client in domain name registration database, changes to the domain name to be changed of registered client by the domain name of registered client;
Step 303: the mapping of searching the domain name of registered client and the IP address of its binding in domain name resolution server, changes to the domain name to be changed of registered client by the domain name of registered client, perform step 305;
Step 304: return change domain name request failed message;
Step 305: complete domain name resolution server configuration.
The message that described registered client sends is sent to registrar by TCP or UDP.
Described registered client is encrypted message before sending message; Described registrar is decrypted message after receiving the message of registered client transmission.
The present invention is by the problem dynamically updated between the domain name introducing automatic registered client and registrar and solve network element device to IP address.
Accompanying drawing explanation
Fig. 1 is IP Multimedia System service architecture figure;
Fig. 2 is the automatic configuration structure schematic diagram of network element device domain name of IP Multimedia System;
Fig. 3 is the network element device domain name method of automatic configuration flow chart of IP Multimedia System;
Fig. 4 is the automatic configuration effort process schematic of network element device domain name of IP Multimedia System;
Fig. 5 is the processing procedure schematic diagram of binding domain name request;
Fig. 6 is the processing procedure schematic diagram of change domain name request.
Embodiment
Below in conjunction with accompanying drawing, preferred embodiment is elaborated.It is emphasized that following explanation is only exemplary, instead of in order to limit the scope of the invention and apply.
The automatic configuration of network element device IP address and domain name is the binding issue in order to solve between domain name and IP address.When network element device starts or when network element device IP address changes, the change tread of network element IP address is mapped in corresponding dns resolution server by network element automatic configuration system, automatically upgrade timely, and without the need to human configuration, thus ensure network element can in time with addressed location accurately.
As shown in Figure 2, automatic registered client program operates on the machine at network element place.Another part is automatic registrar end program, is positioned on the main frame of server end.Server end is divided into registrar and domain name resolution server, and wherein registrar is responsible for the domain name update request responding user.DNS name resolution server realizes domain name resolution service and provides domain name IP to dynamically update service.The domain name that system is administered according to dns resolution server sets up corresponding positive resolving inversely district data file, and in respective district, setting allows the IP address of the main frame sending the order dynamically updated.
System realizes the communication between registered client and registrar by TCP and UDP two kinds of modes, in order to prevent stealing transferring content, adopts the encryption technology of triple DEA (3DES) to be encrypted.The all direct same registrar contact of all requests of automatic registered client, dns resolution server only accepts the request from registrar.By isolating contacting directly of automatic registered client and dns resolution server, ensure the safety of system.
Consider Network Abnormal phenomenon, such as the situation such as power-off, suspension, cause registered client abnormal wire-breakage, the domain name of this client application, by heartbeat message, after obtaining client broken string, is nullified by registrar.After network recovery is normal, client is connected with registrar again, resubmits domain name, and registrar is by the data of the registered client that upgrades in time.System increases heartbeat message in service end, whether can find out the existence of client in official hour, and notifies that dns resolution server continues or stops the parsing of this domain name, thus ensures that visitor can obtain correct information.
Fig. 3 is the network element device domain name method of automatic configuration flow chart of IP Multimedia System.In Fig. 3, Fig. 3 is that the network element device domain name method of automatic configuration stream of IP Multimedia System comprises:
Step 1: set up domain name registration grant table and domain name registration database.
Wherein, domain name registration grant table is the table set in advance according to domain name, for judging the legitimacy of domain name.
Step 2: registered client sends connection request to registrar, after registrar receives connection request, sets up and is connected with the network of registered client.
Step 3: registrar judges the message whether receiving registered client transmission in setting-up time, if receive the message of registered client transmission in registrar setting-up time, then performs step 4; Otherwise, perform step 6.
Step 4: registrar judges that the message that registered client sends is heartbeat message or request message, if the message that registered client sends is heartbeat message, then returns step 3; Otherwise, perform step 5.
Step 5: the request message type sent according to registered client, configuration domain name resolution server, returns step 3.
According to the request message type that registered client sends, the process of configuration domain name resolution server as shown in Figure 4.Wherein, request message type comprises binding domain name request, nullifies domain name request and change domain name request.Binding domain name request comprises registered client ID, registered client title, domain name and IP address.Nullify domain name request and comprise registered client ID, registered client title, domain name and IP address.Change domain name request comprises registered client ID, registered client title, domain name, domain name to be changed and IP address.
When type of message is binding domain name request, the processing procedure of binding domain name request as shown in Figure 5, comprising:
Step 101: according to binding domain name request, registrar judges whether registered client is legal registered client, if registered client is legal registered client, then performs step 102; Otherwise, perform step 105.Judge whether registered client is legal registered client, can judge according to the registered client ID in binding domain name request.
Step 102: registrar checks domain name registration grant table, judges whether the domain name of registered client meets the requirements, if the domain name of registered client meets the requirements, then performs step 103; Otherwise, perform step 105.The domain name of registered client refers to the domain name in binding domain name request, if this domain name is in domain name registration grant table, then thinks that the domain name of registered client meets the requirements.
Step 103: registrar checks the connectedness of IP address to be bound, if IP address to be bound can be communicated with, then performs step 104; Otherwise, perform step 105.IP address to be bound refers to the IP address in binding domain name request.
Step 104: set up the domain name of registered client and the mapping of IP address to be bound in domain name resolution server, joins in domain name registration database by the domain name of registered client and IP address to be bound simultaneously, performs step 106;
Step 105: return binding domain name request failure message;
Step 106: complete domain name resolution server configuration.
When type of message is for nullifying domain name request, nullifies domain name request processing procedure and comprising:
Step 201: the domain name of searching registered client in domain name registration database, deletes the record that the domain name of registered client is corresponding.The domain name of registered client refers to the domain name of nullifying in domain name request.
Step 202: the domain name of searching registered client in domain name resolution server, deletes the mapping of the domain name of registered client and the IP address of its binding.
When type of message is for change domain name request, change domain name request processing procedure as shown in Figure 6, comprising:
Step 301: registrar checks domain name registration grant table, judges whether the domain name to be changed of registered client meets the requirements, if the domain name to be changed of registered client meets the requirements, then performs step 302; Otherwise, perform step 304.The domain name to be changed of registered client refers to the domain name to be changed in change domain name request, if this domain name to be changed is in domain name registration grant table, then the domain name to be changed of registered client meets the requirements.
Step 302: the domain name of searching registered client in domain name registration database, changes to the domain name to be changed of registered client by the domain name of registered client.The domain name of registered client refers to the domain name in change domain name request.
Step 303: the mapping of searching the domain name of registered client and the IP address of its binding in domain name resolution server, changes to the domain name to be changed of registered client by the domain name of registered client, perform step 305.
Step 304: return change domain name request failed message.
Step 305: complete domain name resolution server configuration.
Step 6: the domain name of the network element device that de-registration client is corresponding, returns step 2.The process of the domain name of the network element device that de-registration client is corresponding is as step 201-202.Registered client can re-establish the connection with registrar by step 2.
The above; be only the present invention's preferably embodiment, but protection scope of the present invention is not limited thereto, is anyly familiar with those skilled in the art in the technical scope that the present invention discloses; the change that can expect easily or replacement, all should be encompassed within protection scope of the present invention.Therefore, protection scope of the present invention should be as the criterion with the protection range of claim.