CN106850866B - Method and system for determining DNS data - Google Patents
Method and system for determining DNS data Download PDFInfo
- Publication number
- CN106850866B CN106850866B CN201510886147.XA CN201510886147A CN106850866B CN 106850866 B CN106850866 B CN 106850866B CN 201510886147 A CN201510886147 A CN 201510886147A CN 106850866 B CN106850866 B CN 106850866B
- Authority
- CN
- China
- Prior art keywords
- network element
- dns
- wireless
- configuration file
- location area
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/04—Arrangements for maintaining operational condition
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses a method and a system for determining DNS data, wherein a mapping relation between a wireless entity network element and wireless location area information is obtained from a network element resource database; generating a DNS configuration file according to a preset format according to the mapping relation between the wireless entity network element and the wireless location area information; matching the generated DNS configuration file with the currently used DNS configuration file to obtain a file difference degree; and determining DNS data according to the file difference. The method and the system for determining the DNS data provided by the embodiment of the invention can automatically generate the DNS configuration file, thereby improving the system accuracy and the data making efficiency.
Description
Technical Field
The present invention relates to the field of packet core networks, and in particular, to a method and System for determining DNS (Domain Name System) data.
Background
In a GPRS (General Packet Radio Service) network, RAU (routing Area Update) of 2G and 3G and SRNS (Serving Radio network subsystem) Relocation (redirection) of 3G both need to make data on DNS. For RAU, a corresponding relationship between RAI (Routing Area Identity) and SGSN (Serving GPRS support node ) GTPC (GPRS Tunnel Protocol-control Plane) needs to be created, and for SRNS redirection, a corresponding relationship between rnc (Radio Network control Identity) and SGSN GTPC needs to be created.
In EPC (Evolved Packet Core, 4G Core network), DNS plays a more important role, and all TAC (Trace Area Code) information needs to be associated with MME (Mobile Management Entity) and SGW (Signaling gateway), so as to implement flows such as TAU (Tracking Area update) and handover.
The existing DNS data is created based on manual maintenance and update, and the number of the EPC network elements SGSN, MME, SGW, or the number of the wireless network elements BSC (Base Station Controller), RNC (Radio network Controller), ENB (Evolved Node B) is large. In order to ensure the success rate of each process of RAU, SRNS Relocation, TAU, handover and the like, the corresponding relation of all RAI-SGSN, RNCID-SGSN, TAC-SGW and TAC-MME in province must be made on DNS. Errors are easily generated by manually maintaining huge data, related network flow failures are caused, and the efficiency is low. In addition, data production needs to be performed by local city branch companies before wireless adjustment, data production work orders are distributed to provincial companies, and provincial company maintenance personnel manually produce corresponding relation data on a DNS according to work order information. When emergency adjustment is met, data production cannot be completed quickly.
In summary, the existing DNS data production is based on manual maintenance and update, and has low accuracy and efficiency, and cannot be automatically produced and updated, so that the DNS data production needs to be optimized.
Disclosure of Invention
The invention provides a method and a system for determining DNS data, which are used for solving the problems of low accuracy, low efficiency and poor automation performance of DNS data manufacturing in the prior art.
The embodiment of the invention provides a method for determining DNS data, which comprises the following steps:
acquiring a mapping relation between a wireless entity network element and wireless location area information from a network element resource database;
generating a DNS configuration file according to a preset format according to the mapping relation between the wireless entity network element and the wireless location area information;
matching the generated DNS configuration file with the currently used DNS configuration file to obtain a file difference degree;
and determining DNS data according to the file difference.
Optionally, the radio entity network element is a serving general packet radio service technology GPRS support node SGSN network element, and the radio location area information is one or more of the following:
2G routing area RA, 3G RA and radio network controller RNC mark;
the wireless entity network element is the MME network element, and the wireless location area information is tracking area coded TAC.
Optionally, determining DNS data according to the file difference degree includes:
if the file difference does not exceed a preset threshold value, the generated DNS configuration file is used as a currently used DNS configuration file, and DNS data are determined according to the currently used DNS configuration file;
and if the file difference exceeds a preset threshold value, determining DNS data according to the currently used DNS configuration file.
Optionally, after obtaining the mapping relationship between the wireless entity network element and the wireless location area information, the method further includes:
judging whether the state of the wireless entity network element is normal or not, if so, reserving the mapping relation between the wireless entity network element and the wireless location area information;
and if not, deleting the mapping relation between the wireless entity network element and the wireless location area information.
Optionally, the mapping relationship between the wireless entity network element and the wireless location area information is obtained after one of the following conditions is met:
the acquisition cycle is reached;
and monitoring that the number of the wireless entity network elements changes.
An embodiment of the present invention further provides a system for determining DNS data, including:
the query module: the mapping relation between the wireless entity network element and the wireless location area information is obtained from a network element resource database;
a generation module: the DNS configuration file is generated according to a preset format and according to the mapping relation between the wireless entity network element and the wireless location area information;
a matching module: the DNS configuration file generation module is used for matching the generated DNS configuration file with a currently used DNS configuration file to obtain a file difference degree; and determining DNS data according to the file difference.
Optionally, the radio entity network element is a serving general packet radio service technology GPRS support node SGSN network element, and the radio location area information is one or more of the following:
2G routing area RA, 3G RA and radio network controller RNC mark;
the wireless entity network element is the MME network element, and the wireless location area information is tracking area coded TAC.
Optionally, the matching module is further configured to:
if the file difference does not exceed a preset threshold value, the generated DNS configuration file is used as a currently used DNS configuration file, and DNS data are determined according to the currently used DNS configuration file;
and if the file difference exceeds a preset threshold value, determining DNS data according to the currently used DNS configuration file.
Optionally, the query module is further configured to:
judging whether the state of the wireless entity network element is normal or not, if so, reserving the mapping relation between the wireless entity network element and the wireless location area information;
and if not, deleting the mapping relation between the wireless entity network element and the wireless location area information.
Optionally, the query module is further configured to:
acquiring the mapping relation between the wireless entity network element and the wireless location area information after one of the following conditions is met:
the acquisition cycle is reached;
and monitoring that the number of the wireless entity network elements changes.
The embodiment of the invention provides a method and a system for determining DNS data, which are characterized in that the mapping relation between a wireless entity network element and wireless location area information is obtained from a network element resource database; generating a DNS configuration file according to a preset format according to the mapping relation between the wireless entity network element and the wireless location area information; matching the generated DNS configuration file with the currently used DNS configuration file to obtain a file difference degree; and determining DNS data according to the file difference. The method and the system for determining the DNS data provided by the embodiment of the invention can automatically generate the DNS configuration file, thereby improving the system accuracy and the data making efficiency.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.
Fig. 1 is a schematic flowchart of a method for determining DNS data according to an embodiment of the present invention;
fig. 2 is a flowchart of a method for determining DNS data according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram of a system for determining DNS data according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention clearer, the present invention will be described in further detail with reference to the accompanying drawings, and it is apparent that the described embodiments are only a part of the embodiments of the present invention, not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Fig. 1 illustrates an exemplary method for determining DNS data according to an embodiment of the present invention, including:
step 101: and acquiring the mapping relation between the wireless entity network element and the wireless location area information from the network element resource database.
Specifically, for 2G and 3G networks, the wireless entity network element may be an SGSN network element, and the wireless location area information may be one or more of the following: 2G RA, 3G RA and RNC identity. Namely, the mapping relation between the SGSN network element and the 2G RA, the mapping relation between the SGSN network element and the 3G RA and the mapping relation between the SGSN network element and the RNC can be obtained.
For the 4G network, the wireless entity network element is an MME network element, and the wireless location area information is TAC. Namely, the mapping relationship between the MME network element and the TAC can be obtained.
Further, the mapping relationship between the wireless entity network element and the wireless location area information can be obtained under the condition that the set condition is met. The set condition may be that an acquisition period arrives, the number of the wireless entity network elements is monitored to be changed, and the like.
Specifically, after the acquisition period is reached, the mapping relationship between the wireless entity network element and the wireless location area information may be acquired. For example: 1 part of each day: 00. 2: 00 and 4: 00 obtaining the mapping relation between the wireless entity network element and the wireless location area information at regular time. Or a new wireless entity network element is added, for example, when a new base station is added, the mapping relationship between the wireless entity network element and the wireless location area information is obtained. Or adding a missing radio entity network element, for example, when it is determined that a certain RNC is missing in the network element resource database, adding the RNC in the network element resource database, and obtaining the mapping relationship between the RNC and the radio location area information.
Further, after the mapping relationship between the wireless entity network element and the wireless location area information is obtained, it is necessary to determine whether the state of the wireless entity network element is normal. If the mapping relation between the wireless entity network element and the wireless location area information is normal, the mapping relation between the wireless entity network element and the wireless location area information is reserved; if not, deleting the mapping relation between the wireless entity network element and the wireless location area information.
For example, the state of the wireless entity network element may be determined by querying the number of users under the RNC through a corresponding instruction, and if the number of users under the RNC is 0, it is indicated that there is a failed RNC in the SGSN or the wireless network is cut away, but related data on the SGSN is not deleted, which may cause the obtained mapping relationship to be inaccurate, so that an accurate DNS configuration file cannot be obtained, and thus the obtained corresponding mapping relationship needs to be deleted. In addition, the state of the RNC may also be queried through a response instruction, and if the state of the RNC is out-of-service (fallback), the RNC is a failed RNC, and therefore, the acquired corresponding mapping relationship also needs to be deleted.
Step 102: and generating a DNS configuration file according to a preset format according to the mapping relation between the wireless entity network element and the wireless location area information.
Specifically, the obtained mapping relationship between the SGSN network element and the 2G RA, the obtained mapping relationship between the SGSN network element and the 3G RA, and the obtained mapping relationship between the SGSN network element and the RNC may be written in the rac _ local file; writing the mapping relation between the MME network element and the TAC into a CC _ EPS _ TAI2MME file for a handover process; acquiring the corresponding relation between the TAC and the SGW according to the mapping relation between the MME network element and the TAC and the SGW corresponding to the view file name to which the MME belongs, and writing the corresponding DNS view file into the corresponding DNS view file for establishing a bearer; and analyzing the data in the rac _ loacl file, and constructing a new analysis file CC _ EPS _ RAI for TAU flows from 2G, 3G to 4G.
Step 103: matching the generated DNS configuration file with the currently used DNS configuration file to obtain a file difference degree; and determining DNS data according to the file difference.
Specifically, if the file difference does not exceed a preset threshold, the generated DNS configuration file is used as the DNS configuration file currently in use, and DNS data is determined according to the DNS configuration file currently in use; and if the file difference exceeds a preset threshold value, determining DNS data according to the currently used DNS configuration file, and generating alarm information.
For example, the preset threshold may be 10%, and before making the DNS data, folders are created by date under DNS1, DNS 2/tmp/bak/directory, and the configuration files currently in use are backed up. When the difference between the newly generated DNS file and the currently used DNS file exceeds 10%, the newly generated DNS file does not cover the currently used DNS file, namely, the data production is automatically stopped, comparison log information and alarm information are generated at the same time, relevant personnel are notified in the modes of short messages, mails and the like, and the relevant personnel can perform data analysis according to the backup DNS file and the log information. Therefore, the embodiment of the invention improves the safety performance of the system through the automatic early warning function.
The method for determining DNS data provided by the embodiment of the invention obtains the mapping relation between the wireless entity network element and the wireless location area information from the network element resource database; generating a DNS configuration file according to a preset format according to the mapping relation between the wireless entity network element and the wireless location area information; matching the generated DNS configuration file with the currently used DNS configuration file to obtain a file difference degree; and determining DNS data according to the file difference. The method for determining the DNS data provided by the embodiment of the invention can automatically generate the DNS configuration file, and improves the system accuracy and the data making efficiency.
The following describes in detail the mapping relationship between the wireless entity network element and the wireless location area information obtained in step 101 for the existing three vendor platforms.
First, ATCA (Advanced Telecom Computing Architecture) SGSN/MME
The first step is as follows: all available 2G RAs under the current SGSN are queried.
％％LST GBPAGING:；％％
RETCODE ═ 0 operation was successful
The operation results are as follows:
--------------
the second step is that: all 3G RAs under the current SGSN are queried.
％％LST IUPAGING:；％％
RETCODE ═ 0 operation was successful
The operation results are as follows:
3G paging configuration table
------------
The third step: and inquiring all RNCs under the current SGSN.
％％LST RNC:；％％
RETCODE ═ 0 operation was successful
The operation results are as follows:
RNC information table
---------
The fourth step: the first IP address is taken as the SGSN GTPC address.
％％LST BINDGTPCIP:；％％
RETCODE ═ 0 operation was successful
The operation results are as follows
--------------
The fifth step: and inquiring the MME host name and the SGS Number.
％％LST MMEID:；％％
RETCODE ═ 0 operation was successful
The operation results are as follows:
--------------
460 mobile country code
Mobile net number 00
MME group identifier 0280
MME coding (start value) ═ CA
MME number of codes 2
(number of results 1)
---END
％％LST SCCPOPC:；％％
RETCODE ═ 0 operation was successful
SCCP local signaling point table
----------------
Construct MME host name, mmecca
SGS Number takes the local office SGSN Number of the intranet, namely 8613747158
And a sixth step: query all available TACs under current MME
％％LST S1PAGING:；％％
RETCODE ═ 0 operation was successful
The output results are as follows:
--------------
(the number of results is 12)
---END
In this step, the values of all Tracking Area IDs are taken and the last four bits are truncated, such as 5209 (hexadecimal).
It should be noted that the 3G paging data and RNC identification data in the SGSN are manually made data, and do not depend on the report from the wireless side. If the related data which is invalid exists in the SGSN or the radio is cut away, but the related data on the SGSN is not deleted, the query result is inaccurate, and a correct mapping relationship between the SGSN network element and the 2G RA, a mapping relationship between the SGSN network element and the 3G RA, and a mapping relationship between the SGSN network element and the RNC cannot be constructed. Therefore, some correction is needed to the query results of the second and third steps.
The specific correction method can be as follows: judging whether the number of users under RNC is 0, the operation is as follows:
DSP RNCUSRNUM:
％％DSP RNCUSRNUM: RNCMCC＝"460", RNCMNC＝"00",RNCID＝3484；％％
RETCODE ═ 0 operation was successful
RNC user number information
-------------
460 mobile country code
Mobile net number 00
RNC identity 3484
Number of attached users 312
(number of results 1)
And if the number of the attached users under the RNC is 0, judging that the RNC is invalid, and adding the RA and the RNC identification obtained in the query result into the DNS file.
II, Ericsson SGSN 13A
The first step is as follows: query all 2G RA's under current SGSN
＝＝＝om_conf@eqm01s14p2 ANCB～#gsh list_gras
RAI[MCC-MNC-LAC-RAC]BSC NSE(s)
460-00-20496-0-28304
460-00-20496-1-26335
460-00-20497-0-28304
460-00-20503-1-26342
460-00-20504-0-28305
460-00-20505-0-28305
460-00-20511-0-28304
460-00-20511-1-26350
460-00-20608-0-28304
460-00-20608-1-26351
460-00-20609-1-26352
460-00-20610-0-28305
According to the output result, taking 460-00-20496-0 as an example, MCC-MNC-LAC-RAC respectively, then 20496-0 needs to be extracted and translated into corresponding 16-system data, namely rac0000. lac5010.
The second step is that: query all 3G RA's under the current SGSN
Where wcdma is taken to represent RA for 3G.
The third step: query all RNCs under current SGSN
＝＝＝SUZMME24Ber XunJian@eqm01s0fp2 ANCB～#gsh list_rnc-ri'*'-grc'*'-grn'*'
The fourth step: querying the GTPC address of the SGSN
The fifth step: query MME host name, SGS Number
＝＝＝SUZMME25Ber om_conf@eqm01s0fp2 ANCB～#gsh get_ne
Parameter Active Data Planned Data
---------------------------------------------------------------------
timestamp 20140717000952_
planState__
type(NodeType)sgsnlwg_
hw(Hardware)mkviii_
ss7type(Ss7StackStandard)chinaitu_
lms(LicenseManagerState)normal_
swlt(SoftwareLicenseTargetId)SZSN25SW_
fingerprint(Fingerprint)NW310RBPQ61ACCD2WKDY_
swl(SoftwareLevel)CXS101289_12_R6C01(14A-00-05)_
cnid(CNId)306_
isdn(IsdnNumber)8613747518_
saug(NbrActAttachedSubG)245310_
sauw(NbrActAttachedSubW)102552_
pdpg(NbrActPdpContextG)129379_
pdpw(NbrActPdpContextW)40611_
ni(NodeId)SUZMME25Ber_
nl(NriLength)7_
rbnri(NbrOfReservedBitForNri)8_
mgi(MmeGroupId)653_
mc(MmeCode)60_
rmc(RelativeMmeCapacity)64_
daf(DualAddressBearerFlag)0_
tlo(TaiListOption)currentTai_
ssm(S4SelectionMode)allUe_
ivh(IgnoreVpaaForHomeSub)false_
saul(NbrActAttachedSubL)48335_
tbl(NbrActBearerL)48960_
dbl(NbrActDefaultBearerL)48960_
dan(DefaultApnName)cmwap_
hcmv(HopCounterMaxValue)2_
cpsm(ConvertPdpToBearerSingleMode)false_
dpmm(DeactivatePdpMixedMode)false_
qna(S4QoSNegotiationInActivationAllowed)false_
aifav(AllowIPv6ForAllVisitors)true_
gtdm(S4GgsnTypeDetectionMode)false_
lrc(LteRejectCause)14_
re(RoutingEngine)distributed_
prt(NbrPdpRestorationThrottle)20_
hhfdut(HlrHssFailureDetachUeTimer)60_
In the steps: mgi (MmeGroupID)653_ mc (MmeCode)60_ is converted into hexadecimal respectively, and an MME host name, mmec3C.mmegi028D, is constructed, and is obtained by SGS Number as isdn (Isdn Number), namely 8613747518.
And a sixth step: query all available TACs under current MME
＝＝＝om_conf@eqm01s0fp2 ANCB～#gsh show_mme_ta
ps Class Identifiers|
----------------------------------------------
A ta-mcc 460-mnc 00-tac 20496
A ta-mcc 460-mnc 00-tac 20497
A ta-mcc 460-mnc 00-tac 20498
A ta-mcc 460-mnc 00-tac 20499
A ta-mcc 460-mnc 00-tac 20500
A ta-mcc 460-mnc 00-tac 20501
A ta-mcc 460-mnc 00-tac 20502
A ta-mcc 460-mnc 00-tac 20506
A ta-mcc 460-mnc 00-tac 20507
In this step, the value after tac needs to be converted into hexadecimal, such as 20496 to 5010.
It should be noted that if two BSCs have the same LAC + RAC and are above one SGSN, an empty row may occur. For example, the RAI of the two BSCs with NSE 28304 and 26335 are the same, and are both 460-00-20496-0, then the data for the RAI preceding the 2 nd NSE is null. Therefore, when the empty row is judged to be read, the reading is required to continue to be performed next, and the reading cannot be finished. For example:
RAI[MCC-MNC-LAC-RAC]BSC NSE(s)
460-00-20496-0-28304
-26335
460-00-20497-0-28304
460-00-20503-1-26342
460-00-20504-0-28305
460-00-20505-0-28305
460-00-20511-0-28304
460-00-20511-1-26350
460-00-20608-0-28304
460-00-20608-1-26351
460-00-20609-1-26352
460-00-20610-0-28305
it should be noted that, for an RNC in the SGSN that has failed, the ericsson SGSN may determine the states of all RNCs through an RNC _ status instruction, where the state is in-service if the RNC is a serving RNC, and out-of-service if the RNC is a serving RNC.
＝＝＝om_conf@eqm01s14p2 ANCB～#rnc_status
Initial CPU Load Check...CPU load check passed:load＝10％
RNC Status
------------------------------------------------------------
rn ri spc grc grnlac-rac rs
------------------------------------------------------------
TESTRNC 3427 11083 460 00 21007-0 in-service
TESTRNC02 3428 11084 460 00 9997-0 out-of-service
ZHJHRNC001 1330 10890 460 00 53557-0 in-service
ZHJHRNC002 1331 10891 460 00 53558-0 in-service
For failed RNC data, ri corresponds to 3G RNC id: 3428 (decimal), lac-rac corresponds to 3G RA:9997-0 (decimal), and needs to be eliminated from the results obtained by the previous 3G RA, 3G RNCID queries.
III, Zhongxing SGSN/MME V4
The first step is as follows: all available 2, 3G RAs under the current SGSN are queried.
zte:>SHOW LAI
The command execution is successful.
zte:>SHOW RAI
Routing area name | location area name | routing area code (HEX) | whether supports Flex function | whether has NonBroadcast attribute | Home MSC/VLR POOL | whether it is visually
The command execution is successful.
In this step, the location area code and the location area name are queried through the SHOW LAI, and the corresponding routing area code is found through the SHOW RAI according to the location area name. And according to the routing area code and the position area code, complementing 4 bits to form a complete routing area, namely rac0001. lac5036.
The second step is that: and inquiring all RNCs under the current SGSN.
zte:>SHOW RNC
RNC local direction number | Mobile Country number | Mobile network number | RNC identification
-------------------------------------
20 |460 |00 |3504
The third step: the SGSN GTPC address is queried.
zte:>SHOW SIGIP GTPC
GTPC IPv4 signaling address | GTPC IPv6 signaling address-
------------------------------------
117.142.15.3 | |
------------------------------------
The command execution is successful.
Therefore, the GTPC address obtained is 117.142.15.3.
The fourth step: inquiry of MME host name
zte:>show combocfg
MME group ID | MME node name | Country number | Country destination code | SGSN Mobile Country number | MME Mobile network number | SGSN number | MME number
---------------------------------------------------------------------
645|XZHMME03BZX|86|139|460|00|460|00|8613747141|38
In this step, the MME group ID 645 and the MME number 38 are converted into hexadecimal respectively, and an MME host name, i.e., mmec26.mmegi0285, is constructed; the SGS Number takes the SGSN Number, 8613747141.
The fifth step: and inquiring all available TACs under the current MME.
zte:>SHOW TA
Tracking area identification | group number | mobile country code | mobile network number | tracking area code (HEX) | location area name | tracking area name
---------------------------------------------------------------------
3|1|460|00|523C|xzh-zte-bsc-523c|XZH-ZTE-TAC-523C
In this step, the TAC takes the value of all tracking area codes, e.g. 523C.
The following describes in detail the configuration of the DNS file for different mapping relationships in step 102 according to the mapping relationship between the wireless entity network element and the wireless location area information.
For all the searched available 2G RA under the current SGSN, all the searched 3G RA under the current SGSN and all the RNC under the current SGSN, the 2G RA corresponding to the SGSN and the GTPC corresponding to the SGSN are required to be extracted, and a rac _ local file is written according to a set format, wherein the specific file format is as follows:
and secondly, for all the inquired usable TACs under the current MME, extracting the TACs inquired by the MME and host names corresponding to the MME, and writing the TACs and the host names into a CC _ EPS _ TAI2MME file according to a set format for an S1-handover process.
Specifically, for TACs queried by different MMEs, different MME host names need to be corresponded. For example, TAC corresponding to the NJMME07BHW is TAC-lb09.TAC-hb52.TAC, and host name corresponding to the NJMME07BHW is mmec18.mmegi0280, and the arrangement format is as follows:
tac-lb09.tac-hb52.tac IN NAPTR 10 1 "a" "x-3gpp-mme:x-s10" ""topoff.mme-s10.mmec18.mmegi0280.mme
and thirdly, acquiring the corresponding relation between the TAC and the SGW according to all the inquired usable TACs under the current MME and the SGW corresponding to the view file name to which the MME belongs, and writing the corresponding DNS view file according to a set format for establishing the load.
Specifically, when an MME network element is queried, an input option is added, a name of a view file to which the MME belongs is set, and if the view file corresponding to the NJMME07BHW is CC _ NJ01_ EPS _ TAI2SGw, TAC information corresponding to the NJMME07BHW is written into the view file. The CC _ NJ01_ EPS _ TAI2SGw format is as follows:
tac-lb09.tac-hb52.tac IN NAPTR 10 10 "s""x-3gpp-sgw:x-s5-gtp:x-s8-gtp:x-s11" "" NJ01-sgw-pool-list.node
the queried TAC number 5209 is split into a high-order format and a low-order format to obtain TAC-lb09. In addition, the name of the node is fixed, and the header part needs to be modified according to the name of the View file, for example, the header part is NJ 01-SGw-node-list under the name of the View file CC _ NJ01_ EPS _ TAI2SGw, and the header part is YAC 01-SGw-node-list under the name of the View file CC _ YAC01_ EPS _ TAI2 SGw.
And fourthly, multiplexing the RNC under the current SGSN into an MME analysis file for TAU flows from 2G, 3G to 4G.
Specifically, a new parsing file CC _ EPS _ RAI may be constructed by taking data in RAC files RAC _ loacl of 2G and 3G, and the specific format is as follows.
rac0001.lac5021.rac IN NAPTR 10 1 "a" "x-3gpp-sgsn:x-gn" ""topoff.sgsn-gn.8613745144.sgsn
rac0001.lac5029.rac IN NAPTR 10 1 "a" "x-3gpp-sgsn:x-gn" ""topoff.sgsn-gn.8613745144.sgsn
Further, it is also necessary to specify an a record address of the SGSN, that is, an address of the SGSN GTPC, and the specific format is as follows:
topoff.sgsn-gn.8613745144.sgsn IN A 221.177.137.94
after the DNS configuration file is generated, the generated DNS configuration file is matched with the DNS configuration file which is currently used to obtain the file difference degree, if the file difference degree is smaller than a threshold value, the relevant configuration files under DNS1 and DNS2 are respectively covered, and the configuration files are reloaded through an RNDC platform.
A detailed description is given below of a method for determining DNS data according to an embodiment of the present invention with reference to a specific flow, and fig. 2 is a flowchart of the method for determining DNS data according to the embodiment of the present invention. The method comprises the following steps:
step 201: and determining that the set condition is reached. Specifically, the set condition may be that an acquisition period arrives, the number of the wireless entity network elements is monitored to be changed, and the like.
Further, by setting an acquisition period, for example: 1 part of each day: 00. 2: 00 and 4: 00, when the acquisition period is up, the set condition is met; or a new wireless entity network element is added, for example, a newly added base station meets the set condition; or adding a missing radio entity network element, for example, when it is determined that a certain RNC is missing in the network element resource database, the RNC is added in the network element resource database, that is, the set condition is satisfied.
Step 202: and acquiring the mapping relation between the wireless entity network element and the wireless location area information.
Specifically, for 2G and 3G networks, the wireless entity network element may be an SGSN network element, and the wireless location area information may be one or more of the following: 2G RA, 3G RA and RNC identity. Namely, the mapping relation between the SGSN network element and the 2G RA, the mapping relation between the SGSN network element and the 3G RA and the mapping relation between the SGSN network element and the RNC can be obtained.
For the 4G network, the wireless entity network element is an MME network element, and the wireless location area information is TAC. Namely, the mapping relationship between the MME network element and the TAC can be obtained.
Step 203: judging whether the entity network element state is normal, if so, executing step 204, otherwise, executing step 205
Specifically, the state of the wireless entity network element may be determined by querying the number of users under the RNC through a corresponding instruction, and if the number of users under the RNC is 0, it is indicated that there is a failed RNC in the SGSN or the wireless network is cut away, but relevant data on the SGSN is not deleted, which may cause an inaccurate acquired mapping relationship, and thus an accurate DNS configuration file cannot be obtained. In addition, the state of the RNC can be queried through a response command, and if the state of the RNC is out-of-service, the RNC is an RNC which has failed.
Step 204: and generating a DNS configuration file according to the mapping relationship between the wireless entity network element and the wireless location area information, and continuing to execute step 206.
Specifically, when the status of the entity network element is normal, the mapping relationship between the wireless entity network element and the wireless location area information is reserved, and the DNS configuration file is generated according to the mapping relationship between the wireless entity network element and the wireless location area information.
Further, the obtained mapping relationship between the SGSN network element and the 2G RA, the mapping relationship between the SGSN network element and the 3G RA, and the mapping relationship between the SGSN network element and the RNC can be written into the rac _ local file; writing the mapping relation between the MME network element and the TAC into a CC _ EPS _ TAI2MME file for a handover process; acquiring the corresponding relation between the TAC and the SGW according to the mapping relation between the MME network element and the TAC and the SGW corresponding to the view file name to which the MME belongs, and writing the corresponding DNS view file into the corresponding DNS view file for establishing a bearer; and analyzing the data in the rac _ loacl file, and constructing a new analysis file CC _ EPS _ RAI for TAU flows from 2G, 3G to 4G.
Step 205: and deleting abnormal data, namely deleting the mapping relation between the abnormal wireless entity network element and the wireless location area information.
Step 206: the current DNS profile is backed up.
Specifically, according to the DNS profile currently in use, backup is performed.
Step 207: comparing the configuration files, determining whether the difference is greater than a threshold, if so, executing step 208, otherwise, executing step 209.
Specifically, matching the generated DNS configuration file with the currently used DNS configuration file to obtain a file difference degree; and determining DNS data according to the file difference.
Step 208: and taking the generated DNS configuration file as a current DNS configuration file.
Specifically, if the file difference does not exceed a preset threshold, the generated DNS configuration file is used as the DNS configuration file currently in use, DNS data is determined according to the DNS configuration file currently in use, and the configuration file is reloaded through the RNDC platform.
Step 209: and generating alarm information.
Specifically, if the file difference exceeds a preset threshold, determining DNS data according to the currently used DNS configuration file, and generating alarm information.
For example, the preset threshold may be 10%, and before making the DNS data, folders are created by date under DNS1, DNS 2/tmp/bak/directory, and the configuration files currently in use are backed up. When the difference between the newly generated DNS file and the currently used DNS file exceeds 10%, the newly generated DNS file does not cover the currently used DNS file, namely, the data production is automatically stopped, comparison log information and alarm information are generated at the same time, relevant personnel are notified in the modes of short messages, mails and the like, and the relevant personnel can perform data analysis according to the backup DNS file and the log information. Therefore, the embodiment of the invention improves the safety performance of the system through the automatic early warning function.
The method for determining DNS data provided by the embodiment of the invention obtains the mapping relation between the wireless entity network element and the wireless location area information from the network element resource database; generating a DNS configuration file according to a preset format according to the mapping relation between the wireless entity network element and the wireless location area information; matching the generated DNS configuration file with the currently used DNS configuration file to obtain a file difference degree; and determining DNS data according to the file difference. The method for determining the DNS data provided by the embodiment of the invention can automatically generate the DNS configuration file, and improves the system accuracy and the data making efficiency.
Based on the same inventive concept, an embodiment of the present invention further provides a system for determining DNS data, as shown in fig. 3, which is a schematic structural diagram of the system for determining DNS data provided in the embodiment of the present invention, and includes:
the query module 301: the mapping relation between the wireless entity network element and the wireless location area information is obtained from a network element resource database;
the generation module 302: the DNS configuration file is generated according to a preset format and according to the mapping relation between the wireless entity network element and the wireless location area information;
the matching module 303: the DNS configuration file generation module is used for matching the generated DNS configuration file with a currently used DNS configuration file to obtain a file difference degree; and determining DNS data according to the file difference.
Optionally, the radio entity network element is a serving general packet radio service technology GPRS support node SGSN network element, and the radio location area information is one or more of the following: 2G routing area RA, 3G RA and radio network controller RNC mark; the wireless entity network element is the MME network element, and the wireless location area information is tracking area coded TAC.
Optionally, the matching module 303 is further configured to:
if the file difference does not exceed a preset threshold value, the generated DNS configuration file is used as a currently used DNS configuration file, and DNS data are determined according to the currently used DNS configuration file; and if the file difference exceeds a preset threshold value, determining DNS data according to the currently used DNS configuration file.
Optionally, the query module 301 is further configured to:
judging whether the state of the wireless entity network element is normal or not, if so, reserving the mapping relation between the wireless entity network element and the wireless location area information; and if not, deleting the mapping relation between the wireless entity network element and the wireless location area information.
Optionally, the query module 301 is further configured to:
acquiring the mapping relation between the wireless entity network element and the wireless location area information after one of the following conditions is met:
the acquisition cycle is reached; adding a new wireless entity network element; and adding the missing wireless entity network elements.
In the system for determining DNS data provided in the embodiment of the present invention, a mapping relationship between a wireless entity network element and wireless location area information is obtained from a network element resource database; generating a DNS configuration file according to a preset format according to the mapping relation between the wireless entity network element and the wireless location area information; matching the generated DNS configuration file with the currently used DNS configuration file to obtain a file difference degree; and determining DNS data according to the file difference. The system for determining the DNS data provided by the embodiment of the invention can automatically generate the DNS configuration file, thereby improving the system accuracy and the data making efficiency.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create a system for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including an instruction system which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the invention.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.
Claims (8)
1. A method of determining domain name system, DNS, data, comprising:
acquiring a mapping relation between a wireless entity network element and wireless location area information from a network element resource database;
generating a DNS configuration file according to a preset format according to the mapping relation between the wireless entity network element and the wireless location area information;
matching the generated DNS configuration file with the currently used DNS configuration file to obtain a file difference degree;
if the file difference does not exceed a preset threshold value, the generated DNS configuration file is used as a currently used DNS configuration file, and DNS data are determined according to the currently used DNS configuration file;
and if the file difference exceeds a preset threshold value, determining DNS data according to the currently used DNS configuration file.
2. The method of claim 1, wherein the radio entity network element is a serving general packet radio service technology, GPRS, support node, SGSN, network element, and the radio location area information is one or more of the following:
2G routing area RA, 3G RA and radio network controller RNC mark;
the wireless entity network element is an MME network element, and the wireless location area information is tracking area code TAC.
3. The method of claim 1, wherein after obtaining the mapping relationship between the radio entity network element and the radio location area information, the method further comprises:
judging whether the state of the wireless entity network element is normal or not, if so, reserving the mapping relation between the wireless entity network element and the wireless location area information;
and if not, deleting the mapping relation between the wireless entity network element and the wireless location area information.
4. The method of claim 1, wherein the mapping relationship between the radio entity network element and the radio location area information is obtained after one of the following conditions is satisfied:
the acquisition cycle is reached;
and monitoring that the number of the wireless entity network elements changes.
5. A system for determining DNS data, comprising:
the query module: the mapping relation between the wireless entity network element and the wireless location area information is obtained from a network element resource database;
a generation module: the DNS configuration file is generated according to a preset format and according to the mapping relation between the wireless entity network element and the wireless location area information;
a matching module: the DNS configuration file generation module is used for matching the generated DNS configuration file with a currently used DNS configuration file to obtain a file difference degree; if the file difference does not exceed a preset threshold value, the generated DNS configuration file is used as a currently used DNS configuration file, and DNS data are determined according to the currently used DNS configuration file; and if the file difference exceeds a preset threshold value, determining DNS data according to the currently used DNS configuration file.
6. The system according to claim 5, wherein said radio entity network element is a serving general packet radio service technology, GPRS, support node, SGSN, network element, and said radio location area information is one or more of the following:
2G routing area RA, 3G RA and radio network controller RNC mark;
the wireless entity network element is an MME network element, and the wireless location area information is tracking area code TAC.
7. The system of claim 5, wherein the query module is further configured to:
judging whether the state of the wireless entity network element is normal or not, if so, reserving the mapping relation between the wireless entity network element and the wireless location area information;
and if not, deleting the mapping relation between the wireless entity network element and the wireless location area information.
8. The system of claim 5, wherein the query module is further configured to:
acquiring the mapping relation between the wireless entity network element and the wireless location area information after one of the following conditions is met:
the acquisition cycle is reached;
and monitoring that the number of the wireless entity network elements changes.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510886147.XA CN106850866B (en) | 2015-12-04 | 2015-12-04 | Method and system for determining DNS data |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510886147.XA CN106850866B (en) | 2015-12-04 | 2015-12-04 | Method and system for determining DNS data |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106850866A CN106850866A (en) | 2017-06-13 |
| CN106850866B true CN106850866B (en) | 2020-03-31 |
Family
ID=59152118
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510886147.XA Active CN106850866B (en) | 2015-12-04 | 2015-12-04 | Method and system for determining DNS data |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106850866B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108156262B (en) * | 2018-02-13 | 2019-06-25 | 中国联合网络通信集团有限公司 | A kind of method and device for the validity checking DNS configuration file |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102045215A (en) * | 2009-10-21 | 2011-05-04 | 成都市华为赛门铁克科技有限公司 | Botnet detection method and device |
| CN103220372A (en) * | 2012-01-19 | 2013-07-24 | 中国移动通信集团公司 | Data service access method and system |
| CN103974237A (en) * | 2013-02-06 | 2014-08-06 | 中国移动通信集团公司 | Mobile management method and entity |
| CN104540185A (en) * | 2014-12-15 | 2015-04-22 | 上海华为技术有限公司 | Network access method, access gateway and access control device |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8630247B2 (en) * | 2011-02-15 | 2014-01-14 | Cisco Technology, Inc. | System and method for managing tracking area identity lists in a mobile network environment |
| US20130064108A1 (en) * | 2011-09-12 | 2013-03-14 | Jacques Combet | System and Method for Relating Internet Usage with Mobile Equipment |
| US9811622B2 (en) * | 2011-10-19 | 2017-11-07 | Verizon Patent And Licensing Inc. | Optimized network node selection |
| CN102761965B (en) * | 2012-04-25 | 2016-03-30 | 中兴通讯股份有限公司 | The successional method of user apparatus service and device is kept after tracking area update |
-
2015
- 2015-12-04 CN CN201510886147.XA patent/CN106850866B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102045215A (en) * | 2009-10-21 | 2011-05-04 | 成都市华为赛门铁克科技有限公司 | Botnet detection method and device |
| CN103220372A (en) * | 2012-01-19 | 2013-07-24 | 中国移动通信集团公司 | Data service access method and system |
| CN103974237A (en) * | 2013-02-06 | 2014-08-06 | 中国移动通信集团公司 | Mobile management method and entity |
| CN104540185A (en) * | 2014-12-15 | 2015-04-22 | 上海华为技术有限公司 | Network access method, access gateway and access control device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106850866A (en) | 2017-06-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109684847B (en) | Automatic repairing method, device, equipment and storage medium for script loopholes | |
| US20180359331A1 (en) | Data Cloud Storage System, Client Terminal, Storage Server and Application Method | |
| US8356094B2 (en) | Method, system, client and server for locating operation nodes in communication system | |
| CN112631913A (en) | Method, device, equipment and storage medium for monitoring operation fault of application program | |
| CN110275992B (en) | Emergency processing method, device, server and computer readable storage medium | |
| CN111930842B (en) | Data checking method and device | |
| CN109120432B (en) | Fault server positioning method and device | |
| CN106850866B (en) | Method and system for determining DNS data | |
| CN100440910C (en) | Method for obtaining mobile terminal business ability and using information via operation analytic system | |
| CN112565327B (en) | Access flow forwarding method, cluster management method and related device | |
| US20130086133A1 (en) | Method and apparatus for file revision tracking | |
| CN103812688A (en) | Alarm determining method and device | |
| CN110784358A (en) | Method and device for constructing network call relation topological graph | |
| CN114422602A (en) | Method and device for calling micro-service based on K8S cluster, electronic equipment and storage medium | |
| CN114035539A (en) | Instantiated vehicle type communication matrix generation method, device, equipment and storage medium | |
| CN102238593A (en) | Data cut-over method and device | |
| CN109587013B (en) | APP network compatibility testing method and device, computer equipment and storage medium | |
| CN115578111B (en) | Data tracing method and device, electronic equipment and readable storage medium | |
| CN100389565C (en) | Analytic method of expression type | |
| CN113535730A (en) | Index updating method and system for search engine, electronic equipment and storage medium | |
| CN113761005A (en) | Metadata configuration method and device, electronic equipment and storage medium | |
| CN113556407A (en) | Interface calling method and device for identification analysis node and electronic equipment | |
| CN112445800A (en) | Method and system for generating data serial number and electronic equipment | |
| CN106789315B (en) | System configuration method and device | |
| CN115225609B (en) | User data processing method and device and server |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |