CN1988481A - Method for obtaining exact time and network device - Google Patents

Method for obtaining exact time and network device Download PDF

Info

Publication number
CN1988481A
CN1988481A CNA2006101623166A CN200610162316A CN1988481A CN 1988481 A CN1988481 A CN 1988481A CN A2006101623166 A CNA2006101623166 A CN A2006101623166A CN 200610162316 A CN200610162316 A CN 200610162316A CN 1988481 A CN1988481 A CN 1988481A
Authority
CN
China
Prior art keywords
time
information
daylight saving
network entity
local
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.)
Granted
Application number
CNA2006101623166A
Other languages
Chinese (zh)
Other versions
CN100466553C (en
Inventor
黎步松
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CNB2006101623166A priority Critical patent/CN100466553C/en
Publication of CN1988481A publication Critical patent/CN1988481A/en
Application granted granted Critical
Publication of CN100466553C publication Critical patent/CN100466553C/en
Expired - Fee Related legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/102—Gateways
    • H04L65/1043—Gateway controllers, e.g. media gateway control protocol [MGCP] controllers
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/305—Authentication, i.e. establishing the identity or authorisation of security principals by remotely controlling device operation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6209—Protecting access to data via a platform, e.g. using keys or access control rules to a single file or object, e.g. in a secure envelope, encrypted and accessed using a key, or with access control rules appended to the object itself
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/70—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer
    • G06F21/71—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure computing or processing of information
    • G06F21/74—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure computing or processing of information operating in dual or compartmented mode, i.e. at least one secure mode
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/70—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer
    • G06F21/88—Detecting or preventing theft or loss
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
    • G11B20/00—Signal processing not specific to the method of recording or reproducing; Circuits therefor
    • G11B20/10—Digital recording or reproducing
    • G11B20/10009—Improvement or modification of read or write signals
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
    • G11B20/00—Signal processing not specific to the method of recording or reproducing; Circuits therefor
    • G11B20/10—Digital recording or reproducing
    • G11B20/10009—Improvement or modification of read or write signals
    • G11B20/10305—Improvement or modification of read or write signals signal quality assessment
    • G11B20/10398—Improvement or modification of read or write signals signal quality assessment jitter, timing deviations or phase and frequency errors
    • G11B20/10425—Improvement or modification of read or write signals signal quality assessment jitter, timing deviations or phase and frequency errors by counting out-of-lock events of a PLL
    • H—ELECTRICITY
    • H03—ELECTRONIC CIRCUITRY
    • H03L—AUTOMATIC CONTROL, STARTING, SYNCHRONISATION OR STABILISATION OF GENERATORS OF ELECTRONIC OSCILLATIONS OR PULSES
    • H03L7/00—Automatic control of frequency or phase; Synchronisation
    • H03L7/06—Automatic control of frequency or phase; Synchronisation using a reference signal applied to a frequency- or phase-locked loop
    • H03L7/08—Details of the phase-locked loop
    • H03L7/085—Details of the phase-locked loop concerning mainly the frequency- or phase-detection arrangement including the filtering or amplification of its output signal
    • H03L7/091—Details of the phase-locked loop concerning mainly the frequency- or phase-detection arrangement including the filtering or amplification of its output signal the phase or frequency detector using a sampling device
    • H—ELECTRICITY
    • H03—ELECTRONIC CIRCUITRY
    • H03M—CODING; DECODING; CODE CONVERSION IN GENERAL
    • H03M13/00—Coding, decoding or code conversion, for error detection or error correction; Coding theory basic assumptions; Coding bounds; Error probability evaluation methods; Channel models; Simulation or testing of codes
    • H03M13/03—Error detection or forward error correction by redundancy in data representation, i.e. code words containing more digits than the source words
    • H03M13/23—Error detection or forward error correction by redundancy in data representation, i.e. code words containing more digits than the source words using convolutional codes, e.g. unit memory codes
    • H—ELECTRICITY
    • H03—ELECTRONIC CIRCUITRY
    • H03M—CODING; DECODING; CODE CONVERSION IN GENERAL
    • H03M13/00—Coding, decoding or code conversion, for error detection or error correction; Coding theory basic assumptions; Coding bounds; Error probability evaluation methods; Channel models; Simulation or testing of codes
    • H03M13/29—Coding, decoding or code conversion, for error detection or error correction; Coding theory basic assumptions; Coding bounds; Error probability evaluation methods; Channel models; Simulation or testing of codes combining two or more codes or code structures, e.g. product codes, generalised product codes, concatenated codes, inner and outer codes
    • H03M13/2903—Methods and arrangements specifically for encoding, e.g. parallel encoding of a plurality of constituent codes
    • H—ELECTRICITY
    • H03—ELECTRONIC CIRCUITRY
    • H03M—CODING; DECODING; CODE CONVERSION IN GENERAL
    • H03M13/00—Coding, decoding or code conversion, for error detection or error correction; Coding theory basic assumptions; Coding bounds; Error probability evaluation methods; Channel models; Simulation or testing of codes
    • H03M13/29—Coding, decoding or code conversion, for error detection or error correction; Coding theory basic assumptions; Coding bounds; Error probability evaluation methods; Channel models; Simulation or testing of codes combining two or more codes or code structures, e.g. product codes, generalised product codes, concatenated codes, inner and outer codes
    • H03M13/2957—Turbo codes and decoding
    • H03M13/2993—Implementing the return to a predetermined state, i.e. trellis termination
    • H—ELECTRICITY
    • H03—ELECTRONIC CIRCUITRY
    • H03M—CODING; DECODING; CODE CONVERSION IN GENERAL
    • H03M13/00—Coding, decoding or code conversion, for error detection or error correction; Coding theory basic assumptions; Coding bounds; Error probability evaluation methods; Channel models; Simulation or testing of codes
    • H03M13/63—Joint error correction and other techniques
    • H03M13/635—Error control coding in combination with rate matching
    • H03M13/6356—Error control coding in combination with rate matching by repetition or insertion of dummy data, i.e. rate reduction
    • H—ELECTRICITY
    • H03—ELECTRONIC CIRCUITRY
    • H03M—CODING; DECODING; CODE CONVERSION IN GENERAL
    • H03M13/00—Coding, decoding or code conversion, for error detection or error correction; Coding theory basic assumptions; Coding bounds; Error probability evaluation methods; Channel models; Simulation or testing of codes
    • H03M13/63—Joint error correction and other techniques
    • H03M13/635—Error control coding in combination with rate matching
    • H03M13/6362—Error control coding in combination with rate matching by puncturing
    • H—ELECTRICITY
    • H03—ELECTRONIC CIRCUITRY
    • H03M—CODING; DECODING; CODE CONVERSION IN GENERAL
    • H03M7/00—Conversion of a code where information is represented by a given sequence or number of digits to a code where the same, similar or subset of information is represented by a different sequence or number of digits
    • H03M7/30—Compression; Expansion; Suppression of unnecessary data, e.g. redundancy reduction
    • H03M7/40—Conversion to or from variable length codes, e.g. Shannon-Fano code, Huffman code, Morse code
    • H03M7/4006—Conversion to or from arithmetic code
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B10/00—Transmission systems employing electromagnetic waves other than radio-waves, e.g. infrared, visible or ultraviolet light, or employing corpuscular radiation, e.g. quantum communication
    • H04B10/25—Arrangements specific to fibre transmission
    • H04B10/2575—Radio-over-fibre, e.g. radio frequency signal modulated onto an optical carrier
    • H04B10/25752—Optical arrangements for wireless networks
    • H04B10/25753—Distribution optical network, e.g. between a base station and a plurality of remote units
    • H04B10/25754—Star network topology
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/24—Radio transmission systems, i.e. using radiation field for communication between two or more posts
    • H04B7/26—Radio transmission systems, i.e. using radiation field for communication between two or more posts at least one of which is mobile
    • H04B7/2628—Radio transmission systems, i.e. using radiation field for communication between two or more posts at least one of which is mobile using code-division multiple access [CDMA] or spread spectrum multiple access [SSMA]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J13/00—Code division multiplex systems
    • H04J13/0077—Multicode, e.g. multiple codes assigned to one user
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J13/00—Code division multiplex systems
    • H04J13/16—Code allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0056—Systems characterized by the type of code used
    • H04L1/0064—Concatenated codes
    • H04L1/0066—Parallel concatenated codes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0056—Systems characterized by the type of code used
    • H04L1/0067—Rate matching
    • H04L1/0068—Rate matching by puncturing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L25/00—Baseband systems
    • H04L25/02—Details ; arrangements for supplying electrical power along data transmission lines
    • H04L25/03—Shaping networks in transmitter or receiver, e.g. adaptive shaping networks
    • H04L25/03006—Arrangements for removing intersymbol interference
    • H04L25/03012—Arrangements for removing intersymbol interference operating in the time domain
    • H04L25/03019—Arrangements for removing intersymbol interference operating in the time domain adaptive, i.e. capable of adjustment during data reception
    • H04L25/03038—Arrangements for removing intersymbol interference operating in the time domain adaptive, i.e. capable of adjustment during data reception with a non-recursive structure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L25/00—Baseband systems
    • H04L25/38—Synchronous or start-stop systems, e.g. for Baudot code
    • H04L25/40—Transmitting circuits; Receiving circuits
    • H04L25/49—Transmitting circuits; Receiving circuits using code conversion at the transmitter; using predistortion; using insertion of idle bits for obtaining a desired frequency spectrum; using three or more amplitude levels ; Baseband coding techniques specific to data transmission systems
    • H04L25/497—Transmitting circuits; Receiving circuits using code conversion at the transmitter; using predistortion; using insertion of idle bits for obtaining a desired frequency spectrum; using three or more amplitude levels ; Baseband coding techniques specific to data transmission systems by correlative coding, e.g. partial response coding or echo modulation coding transmitters and receivers for partial response systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/48—Message addressing, e.g. address format or anonymous messages, aliases
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/58—Message adaptation for wireless communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/12—Applying verification of the received information
    • H04L63/126—Applying verification of the received information the source of the received data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0816—Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
    • H04L9/085—Secret sharing or secret splitting, e.g. threshold schemes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/30—Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy
    • H04L9/304—Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy based on error correction codes, e.g. McEliece
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/72409—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by interfacing with external accessories
    • H04M1/72415—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by interfacing with external accessories for remote control of appliances
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/12—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
    • H04M7/1205—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal where the types of switching equipement comprises PSTN/ISDN equipment and switching equipment of networks other than PSTN/ISDN, e.g. Internet Protocol networks
    • H04M7/1295—Details of dual tone multiple frequency signalling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N19/00—Methods or arrangements for coding, decoding, compressing or decompressing digital video signals
    • H04N19/10—Methods or arrangements for coding, decoding, compressing or decompressing digital video signals using adaptive coding
    • H04N19/102—Methods or arrangements for coding, decoding, compressing or decompressing digital video signals using adaptive coding characterised by the element, parameter or selection affected or controlled by the adaptive coding
    • H04N19/103—Selection of coding mode or of prediction mode
    • H04N19/109—Selection of coding mode or of prediction mode among a plurality of temporal predictive coding modes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N19/00—Methods or arrangements for coding, decoding, compressing or decompressing digital video signals
    • H04N19/10—Methods or arrangements for coding, decoding, compressing or decompressing digital video signals using adaptive coding
    • H04N19/134—Methods or arrangements for coding, decoding, compressing or decompressing digital video signals using adaptive coding characterised by the element, parameter or criterion affecting or controlling the adaptive coding
    • H04N19/136—Incoming video signal characteristics or properties
    • H04N19/137—Motion inside a coding unit, e.g. average field, frame or block difference
    • H04N19/139—Analysis of motion vectors, e.g. their magnitude, direction, variance or reliability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N19/00—Methods or arrangements for coding, decoding, compressing or decompressing digital video signals
    • H04N19/60—Methods or arrangements for coding, decoding, compressing or decompressing digital video signals using transform coding
    • H04N19/625—Methods or arrangements for coding, decoding, compressing or decompressing digital video signals using transform coding using discrete cosine transform [DCT]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N19/00—Methods or arrangements for coding, decoding, compressing or decompressing digital video signals
    • H04N19/90—Methods or arrangements for coding, decoding, compressing or decompressing digital video signals using coding techniques not provided for in groups H04N19/10-H04N19/85, e.g. fractals
    • H04N19/91—Entropy coding, e.g. variable length coding [VLC] or arithmetic coding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/10—Integrity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—TPC
    • H04W52/30—TPC using constraints in the total amount of available transmission power
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2105—Dual mode as a secondary aspect
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2115—Third party
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
    • G11B20/00—Signal processing not specific to the method of recording or reproducing; Circuits therefor
    • G11B20/22—Signal processing not specific to the method of recording or reproducing; Circuits therefor for reducing distortions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/42221—Conversation recording systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • H04W8/245—Transfer of terminal data from a network towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/085—Access point devices with remote components
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S370/00—Multiplex communications
    • Y10S370/901—Wide area network
    • Y10S370/902—Packet switching
    • Y10S370/903—Osi compliant network
    • Y10S370/906—Fiber data distribution interface, FDDI
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S370/00—Multiplex communications
    • Y10S370/901—Wide area network
    • Y10S370/902—Packet switching
    • Y10S370/903—Osi compliant network
    • Y10S370/907—Synchronous optical network, SONET

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Multimedia (AREA)
  • Probability & Statistics with Applications (AREA)
  • General Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Computing Systems (AREA)
  • Human Computer Interaction (AREA)
  • Mathematical Physics (AREA)
  • Health & Medical Sciences (AREA)
  • Bioethics (AREA)
  • General Health & Medical Sciences (AREA)
  • Spectroscopy & Molecular Physics (AREA)
  • Business, Economics & Management (AREA)
  • Electromagnetism (AREA)
  • Discrete Mathematics (AREA)
  • Power Engineering (AREA)
  • General Business, Economics & Management (AREA)
  • Electric Clocks (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

The invention discloses a method for accessing the exact time information, which includes: it judges whether the time information in the operation information consists of a summer time sign used to differentiate between summer time and standard time or not. If so, it judges the time information is local summer time and gets the exact time. Otherwise, it is the standard time and gets the exact time. The invention also discloses the network equipment of accessing the exact time information. The invention is used to distinguish the time between summer time and standard time, and different time zones, so as to avoid the time information chaos because of summer time jump and difference of time zones.

Description

Method and network equipment for acquiring exact time information
Technical Field
The invention relates to the technical field of network management, in particular to a method for acquiring exact time and network equipment.
Background
In a wireless network, summer time hopping rules corresponding to the location of a network entity located at a network terminal location may be different, and time zones in which the network entities are located are also different, so that when a network node providing access service for the network entity manages the network entity, the network entity generally adopts local time to describe service information, so that time information in the service information is easily confused.
Taking a model structure of a Telecommunications Management Network (TMN) as an example, in the TMN network, a Network Element (NE) is a network entity at a terminal location, daylight saving time hopping rules at the location of the NE may be different, and the NE may also be in different time zones. An Element Management System (EMS) is used as an access node, needs to manage NE administered by itself, and processes service information reported by different NEs and described by using local time, wherein the information reported by the NE is described by the local time of the location of the NE.
If summer time hopping occurs at the NE location, the local time at the NE location is repeated or lost. Assume that the NE reports traffic information up at local time 02:30: 00. If the summer time hopping rule of the NE location is that the next second of the summer time 02:59:59 is hopped to the standard time 02:00:00, the local time appears twice 02:30:00 in the process of hopping from the summer time to the standard time, and the time reported by the NE in the service information also appears twice 02:30:00, so that the EMS cannot distinguish whether the local time 02:30:00 is the time before or after the summer time is hopped in the service information reported by the NE. If the NE reports the alarm information at 02:30:00, the EMS cannot accurately position the alarm of the NE. Similarly, if the daylight saving time hopping rule of the NE location is that the next second of the standard time 01:59:59 hops to the daylight saving time 03:00:00, when the NE location hops from the standard time to the daylight saving time, no 02:30:00 appears in the local time, thereby causing the loss of the service information reported by the NE in the EMS.
If the NE governed by the EMS is in different time zones, confusion also easily occurs when the time for reporting the service information by the NE is displayed on the EMS. For example, the time for reporting the service information by the NE in the east 8 zone is 02:00:00, and the time for reporting the service information by the NE in the east 9 zone at the same time is 03:00:00, so that the time for receiving the service information by the EMS at the same time is different, which makes the user difficult to understand when reading the service information on the EMS, and leads to confusion of the time for reporting the service information by the NE in the EMS.
At present, the daylight saving time rules of the locations of network entities in a wireless network are different or the network entities are in different time zones, and different network entities managed by an access node usually use local time reporting messages, so that the access node cannot judge the exact time of reporting service messages by the network entities under jurisdiction. When the network entity reports the service information when the summer time jumps, the local time in the service information is repeated or lost, and then the access node cannot position the service information and cannot completely collect the performance data of the network entity. The network entities in different time zones report service messages at the same time in different times, which causes operation confusion when the access node performs time-related operations on different network entities.
Disclosure of Invention
In view of the above, an embodiment of the present invention is directed to a method for an access node to manage a network entity, so as to determine the exact time information in service information.
Another objective of the embodiments of the present invention is to provide a network device, configured to determine the exact time information in the service information.
In order to achieve the above purpose, the technical solution of the embodiment of the present invention is realized as follows:
a method of obtaining exact time information, the method comprising:
judging whether the time information in the service information comprises a daylight saving time identifier for distinguishing daylight saving time from standard time, if so, judging that the local time is described by the daylight saving time in the time information, and acquiring exact time information; otherwise, the local time is described by adopting the standard time in the time information, and the exact time information is obtained.
A network equipment for obtaining exact time information comprises a control module and a judgment module;
the control module is used for receiving the service information containing the time information and sending the received service information to the judging module; receiving a judgment result which is from a judgment module and represents a time information description mode, and acquiring exact time information;
the judging module is used for judging whether the received time information comprises a daylight saving time identifier for distinguishing daylight saving time from standard time, if so, judging that the time information is local time described by the daylight saving time, and sending a daylight saving time judging result to the control module; if not, the time information is judged to be the local time described by the standard time, and the standard judgment result is sent to the control module.
It can be seen from the foregoing solutions that, according to the daylight saving time identifier used for distinguishing the daylight saving time from the standard time in the time information, the method and the network device for obtaining the exact time information provided in the embodiments of the present invention distinguish different description modes of the local time, exactly obtain the time information, and avoid repetition or loss of the time information due to the daylight saving time jump.
The access node distinguishes the service information of different local time sent by the network entity at the same time through the time zone information of different network entities.
In addition, the access node and the network entity can convert the local time into universal coordinated time (UTC) time by using the daylight saving time offset and/or the time zone information of the location of the network entity, thereby avoiding time operation confusion caused by different time zones or different daylight saving time rules of the location of the network entity.
Drawings
Fig. 1 is a flowchart of the EMS acquiring and storing daylight saving time offset from the NE in an embodiment of the present invention;
fig. 2 is a flowchart of the NE acquiring and storing daylight savings time offset from the EMS in an embodiment of the present invention;
fig. 3 is a schematic structural diagram of a network device in an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the present invention is further described in detail with reference to the embodiments below.
In the embodiment of the present invention, the obtaining of the exact time information refers to determining a description mode of a local time in the time information. Different description modes are adopted, so that different description results can be obtained at the same time; or describe the same time of the result, corresponding to different UTC times. The embodiment of the invention obtains the exact time information by determining the description mode of the local time.
The method for acquiring the exact time in the embodiment of the invention is suitable for a wireless network comprising a network entity and an access node. Wherein, the summer time hopping rules of the location of the network entity are different, or the network entity is located in different time zones; the access node is used for providing access service for the network entity and carrying out information interaction with the network entity. The network entity can be not only a mobile user crossing time zones, but also a network terminal working in a fixed place or a network management layer entity needing to process services in different time zones or daylight saving time. For example, in a TMN network, when a network entity is a NE, the corresponding EMS is an access node; when EMS is used as a network entity, a corresponding Network Management System (NMS) is an access node; in a Code Division Multiple Access (CDMA) network, when a Base Station Subsystem (BSS) and a Mobile Switching Center (MSC) are network entities, a corresponding Operation and Maintenance Center (OMC) is an access node.
The following describes a method for acquiring an exact time in the embodiment of the present invention, taking EMS as an access node, and managing NEs with different daylight saving time rules or in different time zones as an example.
In this embodiment, the EMS and the NE respectively determine whether the time information in the service information has a daylight saving time identifier, if no daylight saving time identifier exists in the time information, the time information adopts standard time description, and if a daylight saving time identifier exists in the time information, the time information adopts daylight saving time description, so as to determine the exact time corresponding to the time information adopting different description modes, thereby obtaining the determined time information.
And after the exact time information is obtained, operating the service information according to the exact time information.
Taking EMS as an access node and NE as a network entity for detailed description as an example, assume that the daylight saving time hopping rule at the location of the NE is that the next second of daylight saving time 02:59:59 hops to standard time 02:00: 00.
When the NE or the EMS that governs the NE processes the internal service information, it is assumed that the time information in the service information is 02:30:00, if the time information does not include the daylight saving time identifier, the time information is the standard time 02:30:00, and if the time information includes the daylight saving time identifier, the time information is the daylight saving time 02:30:00, that is, the standard time 03:30:00, thereby distinguishing the daylight saving time from the standard time.
The NE or EMS may perform subsequent processing on the service information according to the acquired exact time information. For example, when the time in the service information is displayed to the user, the time described by the daylight saving time is displayed as "02: 30:00 DST", that is, the Daylight Saving Time (DST) character is added after the local time as the daylight saving time identifier. In this way, the user can identify the exact time corresponding to the same time information by looking up the display.
In the process of exchanging service information between the EMS and the NE, the EMS and the NE may operate the service information using the exact time information. Assuming that the EMS needs to query the alarm information sent by the NE between daylight savings time 02:30:00 and standard time 02:30:00, the daylight savings time flag is included only in the starting time in the query command sent by the EMS to the NE. Thus, after receiving the query command, the NE can distinguish the start time from the end time and return corresponding service information.
In this embodiment, the access node and the network entity both determine whether the daylight saving time identifier is included in the time information to describe the exact time point of the time information, which is merely a preferred example of the present invention. Other methods of distinguishing daylight savings time from standard time may be used by the access node and the network entity. For example, the access node and the network entity set a value of the daylight saving time identifier in the time information, and when the value of the daylight saving time identifier is 1, it indicates that the time information is daylight saving time, and when the value of the daylight saving time identifier in the time information is 0, it indicates that the time information is standard time. In practical applications, the method capable of distinguishing the daylight saving time from the standard time is within the protection scope of the present invention, and is not limited to the method in the embodiment.
In the embodiment of the invention, the access node and the network entity can judge whether the local time is the daylight saving time by judging whether the time information comprises the daylight saving time identifier or not, and acquire the exact time information. If necessary, the local time described by the daylight saving time can be converted into the UTC time, so that the time information is uniformly described by the UTC time, and the problem that the time information is disordered due to the fact that the daylight saving time cannot be distinguished from the standard time is avoided.
The conversion formula of the local time and the UTC time described by the daylight saving time is as follows: UTC is local time + daylight savings time offset. The daylight savings offset is determined by the daylight savings rule for the NE location, for example, the daylight savings rule for the NE location is: when the next second of the summer time 02:59:59 jumps to the standard time 02:00:00, the offset of the summer time corresponding to the NE is-60 minutes. Firstly, the steps of obtaining and storing the daylight saving time offset by the access node and the network entity are introduced by taking the EMS as the access node and the NE as the network entity.
Fig. 1 shows a flow of acquiring and storing daylight savings time offset from an NE by an EMS in an embodiment of the present invention. As shown in fig. 1, the step of the EMS acquiring and storing the daylight saving time offset from the NE is:
step 11: the EMS provides UTC consistency for the NEs.
EMS provides a Network Time Protocol (NTP) server for NE, NE is used as a client of the NTP server, and the time is synchronized from the NTP server by using the existing time synchronization method, thereby ensuring the consistency of EMS and NE on UTC time.
When the EMS or the NE needs to convert daylight saving time into UTC time, UTC time synchronization needs to be carried out between the EMS and the NE so as to ensure that time references between the EMS and the NE are consistent when local time is converted into UTC time, and avoid time confusion.
Step 12: the EMS sends a query command to the NE, and the query command is used for acquiring the summer time offset preset by the NE.
The EMS may send the query command to the NE via human machine language (MML).
When the EMS monitors that the NE is accessed, the EMS sends an inquiry command to the newly accessed NE to acquire the daylight saving time offset preset by the NE. The EMS may also periodically send a query command to a different NE, and obtain the offset of the daylight saving time newly set by the NE.
Step 13: the NE sends a query response message to the EMS.
And after receiving the query command sent by the EMS, the NE carries the preset daylight saving time offset of the location of the NE in a query response message and sends the query response message to the EMS. Wherein the daylight saving time offset at the location of the NE may be set when the NE starts to operate for initialization.
The EMS receives the inquiry response message of the NE, and acquires and stores the daylight saving time offset of the location of the NE.
Through the steps, the NE sends the summer time offset of the location to the EMS, so that the EMS stores and records the summer time offset of the location of the NE.
Fig. 2 shows a flow of the NE acquiring and storing the daylight savings time offset from the EMS in an embodiment of the present invention. As shown in fig. 2, the steps of the NE acquiring and storing the daylight saving time offset from the EMS are:
step 21: the EMS provides UTC consistency for the NEs.
EMS provides NTP server for NE, NE is as the customer end of NTP server, utilize the existing method of carrying on time synchronization, from NTP server synchronization time, guarantee EMS and NE in UTC temporal conformance.
Step 22: the EMS sends a modification command to the NE, and the summer time offset preset by the EMS is sent to the NE.
The EMS may send a modification command to the NE through the MML.
When the EMS starts to work and initializes, or when the daylight saving offset of the NE under the jurisdiction of the EMS changes, the EMS uniformly configures the daylight saving offset for the NE under the jurisdiction, and the EMS carries the set daylight saving offset in a modification command and sends the modification command to the NE.
Step 23: the NE sends a modification reply message to the EMS.
And after receiving the modification command sent by the EMS, the NE acquires the summer time offset of the location where the NE is located, which is preset by the EMS, modifies and stores the summer time offset, and carries the modified result in a modification response message to send to the EMS.
And the EMS receives the modification response message of the NE, and after the NE is determined to successfully modify the daylight saving time offset of the location, the EMS establishes and updates the daylight saving time offset of the location of the NE on the EMS local record. If the NE fails to modify the daylight saving time offset at the location, the EMS does not update the daylight saving time offset at the location of the NE on the local record, and continues to send a modification command to the NE.
Through the steps, the EMS sends the summer time offset of the location of the different NE preset by the EMS to the NE, so that the NE acquires and stores the summer time offset of the location of the EMS.
In addition, the process of the EMS and NE to save and store the daylight savings time offset may also be triggered by the NE side.
When the NE starts to work, an operator initializes the daylight saving time offset of the NE according to the daylight saving time rule of the location of the NE, and after the daylight saving time initialization of the NE is completed, the NE informs the EMS to update the daylight saving time offset of the NE in the local record by using the MML.
When the daylight saving time rule of the location of the NE is changed, the NE modifies the daylight saving time offset of the NE according to the change of the daylight saving time rule. When the summer time offset of the NE is updated, the NE uses the MML to notify the EMS to update the summer time offset of the NE in the local record.
The above embodiments are merely preferred examples of the method for the access node or the network entity to obtain and store the daylight saving time offset, and are not intended to limit the present invention. In the invention, in any service information interaction process between the access node and the network entity, the network entity or the access node can send the daylight saving offset of the network entity to the opposite side through MML or other information transmission modes, so that the access node or the network entity can acquire and store the daylight saving offset of the network entity.
After the EMS or the NE receives the service information comprising the time information, the EMS or the NE converts the local time described by the daylight saving time into the UTC time by using the stored daylight saving time offset, and the UTC is used for describing the time information, so that the problem of time information confusion is avoided, and the service information is further operated.
The process of the EMS operating the service information by using the UTC time is similar to the process of the EMS operating the service information by using the daylight saving time identifier, and the process of the NE operating the service information by using the UTC time is similar to the process of the NE operating the service information by using the daylight saving time identifier, which is not described herein again.
When the EMS and the NE carry out service information interaction by utilizing the UTC time, the EMS is supposed to send a query command, alarm information sent by the NE between the daylight saving time 02:30:00 and the standard time 02:30:00 is queried, and in the query command, only the start time information comprises the daylight saving time identifier. After receiving the query command, the NE converts the start time 02:30:00 into the UTC time 01:30:00 according to a conversion formula of the daylight saving time offset and the UTC time, wherein the end time information does not include the daylight saving time identifier, namely standard time description is adopted, the corresponding daylight saving time offset is 0, and the corresponding UTC time corresponding to the end time is 02:30: 00. Therefore, the NE obtains the exact time information of the query command by converting the local time into the UTC time, and sends the alarm information between the UTC time 01:30:00 and the UTC time 02:30:00 to the EMS, so that time information confusion caused by summer season jump is avoided, and the exact time information can be obtained even if the local time appears repeatedly.
In this embodiment, the NE performs UTC time conversion on the time information transmitted by the EMS, which is merely a preferred example of the present invention and is not a limitation. When the invention is applied, EMS can convert the time information in the service information into UTC time after receiving the service information sent by NE. When the EMS and the NE process service information or perform service information interaction, the EMS and the NE may use local daylight saving time or converted UTC time, that is, the EMS and the NE may flexibly convert daylight saving time and UTC time according to actual service requirements.
When the embodiment of the invention is applied, the description modes of the time information in the service information of the EMS and the NE can be agreed in advance, or the description modes are local time or UTC time, so that the service information conversion disorder caused by the difference of the description modes of the time information is avoided. The EMS and the NE can also realize the step of appointing specific time conversion, and can also avoid the confusion of service information conversion caused by different time information description modes.
In order to better distinguish the local time from the UTC time, a time identifier for distinguishing the local time from the UTC time is added to the time information of the service information, and if the time information in the service information is the local time, the time identifier is 0, and if the time information in the service information is the UTC time, the time identifier is 1. Therefore, the EMS and the NE can carry out different processing on the service information according to the time identification, and the service information is prevented from being confused due to different time information description modes.
Still taking the EMS as an example to send the query command to the NE, assuming that the EMS needs to query the alarm information sent by the NE between daylight savings time 02:30:00 and standard time 02:30:00, the EMS converts the start time 02:30:00 into 01:30:00 of the UTC time according to the saved daylight savings time rule and the conversion formula of the UTC time, and the UTC time corresponding to the standard time 02:30:00 is 02:30: 00. The EMS sets a time stamp in the time information in the query command sent to the NE, and the time stamps for the start time and the end time are both set to 1. In this way, after the NE receives the query command of the EMS, the alarm information between the UTC time 01:30:00 and the UTC time 02:30:00 can be directly transmitted to the EMS.
When the network entity governed by the access node does not need to perform daylight saving time hopping, for example, when the location of the network entity governed by the access node does not have or does not enable daylight saving time rules, the access node identifies the service information sent by different network entities according to the time zone information of different network entities governed by the access node. The method for storing time zone information by the access node and the network entity is the same as the method for storing the daylight saving time rule by the access node and the network entity, and is not described herein again. If the access node or the network entity is needed, the local time can be converted into the UTC time, so that the time information is uniformly described by the UTC time, and the confusion of the time information caused by different time zones of different network entities governed by the access node is avoided.
The conversion formula of local time and UTC time with different time zone information is as follows: UTC is local time + time zone information. The time zone information is determined by the time zone in which the NE is located, for example, if the NE is located in the east 8 zone, the time zone information corresponding to the NE is-8.
The following describes a method for acquiring the exact time according to the embodiment of the present invention, taking EMS as an access node and NE as a network entity as an example.
When the NE governed by the EMS does not need to carry out daylight saving time hopping, but different NEs governed by the EMS are in different time zones, the EMS converts the local time of the NE in the different time zones into the UTC time by using a conversion formula of the local time and the UTC time. In this embodiment, it is assumed that the first NE governed by the EMS is located in the east 8 area, the time zone information corresponding to the NE is-8, the second NE governed by the EMS is located in the east 9 area, and the time zone information corresponding to the NE is-9.
When NE in different time zones reports service information to EMS by local time of its location, EMS converts local time into UTC time, thereby obtaining exact time information. For example, at the same UTC time, the time for the first NE to report the service information is 10:00, and the time for the second NE to report the service information is 11: 00. After receiving the service information with different local time, the EMS calculates that the UTC time corresponding to the local time in the service information reported by different NEs is 02:00 according to the conversion formula of the local time and the UTC time, thereby knowing that the service information with different reported time of the first NE and the second NE is reported at the same time, and being convenient for a user to identify the exact time of the NE reported information when reading the information reported by the NE on the EMS.
Similarly, the NEs in different time zones can calculate the UTC time corresponding to the local time, and report the information of the UTC time to the EMS.
The EMS may operate the service information using a conversion formula of local time and UTC time and NE having different time zone information. Taking an example that an EMS sends an operation command with time information to NEs in different time zones, assuming that the EMS needs to query information reported by different NEs between UTC time 01:00 and 02:00, the EMS calculates local time corresponding to the UTC time according to time zone information of a first NE and a second NE, in the query command sent to the first NE, the time information is 09:00 to 10:00, and in the query command sent to the second NE, the time information is: 10:00 to 11: 00.
When the EMS sends an operation command with time information to the NEs in different time zones, the time information in the operation command can also be described directly by using the UTC time. And after receiving the operation command described by the UTC, the NE calculates the local time corresponding to the UTC time and executes the operation command sent by the EMS. The NE may also directly execute the operation command transmitted by the EMS according to the UTC time.
When the network entities governed by the access node have different daylight saving time rules and are located in different time zones, the access node acquires exact time information according to daylight saving time identifications of different NE governed by the access node and time zone information of the location of the NE. The conversion formula adopted at this time is: UTC is local time + daylight savings time offset + time zone information.
The following describes an embodiment of the present invention by taking EMS as an access node and NE as a network entity as an example.
The EMS sends an operation command with time information to the managed NEs in different time zones and with different daylight saving time rules, and the daylight saving time rule of the first NE managed by the EMS is assumed as follows: when the next second of the daylight saving time 02:59:59 jumps to the standard time 02:00:00, the daylight saving time offset corresponding to the NE is-60 minutes, and the daylight saving time rule of the second NE governed by the EMS is as follows: when the next second of the daylight saving time 02:59:59 jumps to the standard time 01:00:00, the daylight saving time offset corresponding to the NE is-120 minutes, the first NE is located in the east 8 area, the time zone information corresponding to the first NE is-8, the second NE is located in the east 9 area, and the time zone information corresponding to the second NE is-9. The EMS needs to inquire the information reported by different NEs between UTC time 01:00 to 02:00, the EMS calculates the local time corresponding to the UTC time according to the time zone information of the first NE and the second NE and the daylight saving time rule, the time information is 10:00 to 11:00 in the inquiry command sent to the first NE, and the time information is 11:00 to 12:00 in the inquiry command sent to the second NE.
When the embodiment of the invention is applied, the access node and the network entity can flexibly use the daylight saving time identifier and the time identifier, and the aim of determining the exact time of the service information is achieved by utilizing the daylight saving time rule and the time zone rule.
The following describes the components and functions of the network device to which the above method is applied in detail.
Fig. 3 shows a composition structure of a network device in an embodiment of the present invention, and as shown in fig. 3, the network device in the embodiment of the present invention includes a control module, a determination module, an application module, a calculation module, and a storage module.
The control module is used for receiving service information containing time information, sending the service information to the judging module, receiving a judging result which is from the judging module and represents a time information description mode, determining the time information description mode and obtaining exact time information.
And the judging module is used for receiving the service information containing the time information sent by the control module, judging whether the time information comprises a daylight saving time identifier for distinguishing daylight saving time from standard time, if no daylight saving time identifier exists in the time information, describing the time information by adopting the standard time, if the daylight saving time identifier exists in the time information, describing the time information by adopting the daylight saving time, and sending a judging result of a time information description mode to the control module after the judgment.
When the service information is further operated, the control module is further used for sending a control command described by the daylight saving time or a control command described by the standard time to the application module according to the description mode of the time information in the judgment result, so that the application module operates the service information by adopting the description mode corresponding to the time information.
And the application module is used for receiving a control command which is described by adopting daylight saving time or a control command which is described by adopting standard time from the control module and operating the service information. For example, the application module is configured to display the time information after receiving a control command from the control module. If the control module sends a control command described by the daylight saving time, the application module adds a daylight saving time identifier for distinguishing the standard time from the daylight saving time after the time information when displaying the time information.
If the local time is preset to be converted into the UTC time, the control module is further used for sending a query command to the storage module, receiving the daylight saving time rule and/or the time zone information fed back by the storage module, sending the daylight saving time rule and/or the time zone information to the calculation module, and receiving the UTC time corresponding to the local time sent by the calculation module.
And the storage module is used for storing the daylight saving time offset and/or the time zone information corresponding to the local time, and sending the daylight saving time offset and/or the time zone information which needs to be inquired by the control module to the control module when receiving the inquiry command sent by the control module.
And the calculation module is used for receiving the daylight saving time rule and/or the time zone information from the control module and calculating the UTC time corresponding to the local time. When the local time is described by adopting daylight saving time, the calculation module adds the local time and the daylight saving time offset from the control module to obtain UTC time corresponding to the local time, and feeds back a calculation result to the control module; when the local time does not include the daylight saving time identification, the calculation module adds the local time and the time zone information from the control module to obtain UTC time corresponding to the local time, and feeds back the calculation result to the control module; when the local time is described by adopting daylight saving time and the time zone information needs to be considered, the calculation module adds the local time, the daylight saving time offset from the control module and the time zone information to obtain UTC time corresponding to the local time, and feeds back the calculation result to the control module.
When the service information is further operated, the control module is further used for sending a control command described by the UTC time to the application module according to the UTC time corresponding to the local time from the computing module, so that the application module operates the service information by the UTC time.
And the application module is used for receiving a control command which is described by UTC time and is sent from the control module and operating the service information. For example, the application module is configured to display the time information after receiving a control command from the control module. And displaying the time information described by the UTC time after the application module receives the control command described by the UTC time sent by the control module.
By utilizing the network equipment in the embodiment of the invention, the exact time information can be obtained. When the method for acquiring the exact information in the embodiment of the present invention is applied, the network device may be an access node, or may be a network entity having different daylight saving time rules or being in different time zones. For example, in a TMN network, the network device may be either an EMS or a NE; in a CDMA network, the network device may be either a BSS or an MSC.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like that fall within the spirit and principle of the present invention are intended to be included therein.

Claims (10)

1. A method of obtaining exact time information, the method comprising:
judging whether the time information in the service information comprises a daylight saving time identifier for distinguishing daylight saving time from standard time, if so, judging that the local time is described by the daylight saving time in the time information, and acquiring exact time information; otherwise, the local time is described by adopting the standard time in the time information, and the exact time information is obtained.
2. The method of claim 1, further comprising:
acquiring daylight saving time offset, and adding the local time and the acquired daylight saving time offset to acquire universal coordinated UTC time corresponding to the local time; or,
acquiring time zone information, adding the local time and the time zone information, and acquiring UTC time corresponding to the local time; or,
and acquiring the daylight saving time offset and the time zone information, and adding the local time, the acquired daylight saving time offset and the acquired time zone information to acquire the UTC time corresponding to the local time.
3. The method according to claim 1 or 2, wherein after obtaining the exact time information, the method further comprises: operating the service information according to the exact time information;
after obtaining the UTC time corresponding to the local time, the method further includes: and operating the service information by adopting the UTC time corresponding to the local time.
4. The method of claim 3, wherein if the service information is operated by using the UTC time corresponding to the local time, the operating the service information further comprises: and adding a time identifier for distinguishing local time and UTC time in the time information of the service information.
5. The method of claim 3, wherein the method is applied between an access node and a network entity, the access node provides access service for the network entity, the network entity has daylight saving time rule, and the method for obtaining daylight saving time offset is:
the network entity sends the summer and the current offset of the location of the network entity to the access node; or,
the access node sends the preset daylight saving time offset to a network entity;
the network entity is in different time zones, and the method for obtaining time zone information comprises the following steps:
the network entity sends the time zone information of the location of the network entity to the access node; or,
the access node sends the preset time zone information to the network entity;
the location of the network entity has a daylight saving time rule and is in different time zones, and the method for acquiring the daylight saving time offset and the time zone information comprises the following steps:
the network entity sends the daylight saving time offset and the time zone information of the location of the network entity to the access node; or,
and the access node sends the preset daylight saving time offset and time zone information to the network entity.
6. The method of claim 5, wherein if the access node obtains the daylight-time offset by sending the daylight-time offset of the location to the network entity, the method further comprises: the access node queries a daylight saving time offset of the network entity;
if the time zone information of the location of the access node is sent to the access node through the network entity to obtain the time zone information, the method further comprises the following steps: the access node querying time zone information of a network entity;
if the daylight saving time offset and the time zone information of the location of the network entity are sent to the access node through the network entity to obtain the daylight saving time offset and the time zone information, the method further comprises the following steps: the access node queries the daylight savings time offset and time zone information of the network entity.
7. The network equipment for acquiring the exact time information is characterized by comprising a control module and a judgment module;
the control module is used for receiving the service information containing the time information and sending the received service information to the judging module; receiving a judgment result which is from a judgment module and represents a time information description mode, and acquiring exact time information;
the judging module is used for judging whether the received time information comprises a summer time identifier for distinguishing summer time and current time from standard time, if so, judging that the time information is local time described by the summer time identifier, and sending a summer time judging result to the control module; if not, the time information is judged to be the local time described by the standard time, and the standard judgment result is sent to the control module.
8. The network device of claim 7, wherein the network device further comprises an application module;
the control module is further used for sending a control command described by summer time and current time or a control command described by standard time to the application module according to the judgment result of the judgment module;
and the application module is used for receiving a control command described by adopting daylight saving time or a control command described by adopting standard time from the control module and operating the service information.
9. The network device of claim 7, wherein the network device further comprises a storage module and a computing module,
the storage module is used for storing the daylight saving time rule and/or the time zone information corresponding to the local time, receiving the query command of the control module and sending the queried daylight saving time rule and/or time zone information to the control module;
the calculation module is used for calculating the UTC time corresponding to the local time, adding the local time and the daylight saving time rule and/or the time zone information from the control module, and feeding back the calculation result to the control module;
the control module is used for sending a query command to the storage module, receiving the daylight saving time rule and/or the time zone information fed back by the storage module, sending the daylight saving time rule and/or the time zone information to the calculation module, and receiving the UTC time corresponding to the local time sent by the calculation module.
10. The network device of claim 9, wherein the device further comprises an application module;
the control module is used for sending a control command described by UTC time to the application module according to the UTC time corresponding to the local time from the calculation module;
and the application module is used for receiving a control command which is described by UTC time and is sent from the control module and operating the service information.
CNB2006101623166A 2006-12-11 2006-12-11 Method for obtaining exact time and network device Expired - Fee Related CN100466553C (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CNB2006101623166A CN100466553C (en) 2006-12-11 2006-12-11 Method for obtaining exact time and network device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CNB2006101623166A CN100466553C (en) 2006-12-11 2006-12-11 Method for obtaining exact time and network device

Publications (2)

Publication Number Publication Date
CN1988481A true CN1988481A (en) 2007-06-27
CN100466553C CN100466553C (en) 2009-03-04

Family

ID=38185124

Family Applications (1)

Application Number Title Priority Date Filing Date
CNB2006101623166A Expired - Fee Related CN100466553C (en) 2006-12-11 2006-12-11 Method for obtaining exact time and network device

Country Status (1)

Country Link
CN (1) CN100466553C (en)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102684808A (en) * 2012-06-06 2012-09-19 哈尔滨工业大学 Self-adaptive clock synchronous system
CN103324078A (en) * 2012-03-22 2013-09-25 华为终端有限公司 Method, device, server and system for collocating daylight saving time
CN105843034A (en) * 2015-01-30 2016-08-10 精工爱普生株式会社 Electronic timepiece, electronic device, update information transmission device, and update information transmission program
WO2019192451A1 (en) * 2018-04-04 2019-10-10 华为技术有限公司 Communication method and communication apparatus
CN111800211A (en) * 2019-04-08 2020-10-20 杭州海康威视系统技术有限公司 Data processing method, device and system
WO2021051242A1 (en) * 2019-09-16 2021-03-25 Oppo广东移动通信有限公司 Time determination method and apparatus, and device

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2001356838A (en) * 2000-06-12 2001-12-26 Toshiba Corp Local time computer, clock device, communication terminal equipment and local time calculating method
WO2002063626A2 (en) * 2001-02-02 2002-08-15 Matsushita Electric Industrial Co., Ltd. Recording apparatus and method, playback apparatus and method, recording medium, program, and computer-readable recording medium
JP4251786B2 (en) * 2001-05-11 2009-04-08 ソニー株式会社 Information processing apparatus and method, and program
KR100639340B1 (en) * 2004-09-08 2006-10-30 엘지전자 주식회사 Method for Displaying World time of Mobile Communication Terminal and Mobile Communication Terminal using the same

Cited By (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103324078B (en) * 2012-03-22 2017-04-05 华为终端有限公司 A kind of daylight-saving time collocation method, equipment, server and system
CN103324078A (en) * 2012-03-22 2013-09-25 华为终端有限公司 Method, device, server and system for collocating daylight saving time
WO2013139180A1 (en) * 2012-03-22 2013-09-26 华为终端有限公司 Daylight saving time configuration method, device, server, and system
US9383728B2 (en) 2012-03-22 2016-07-05 Huawei Device Co., Ltd. Method, device, server, and system for configuring daylight saving time
CN102684808A (en) * 2012-06-06 2012-09-19 哈尔滨工业大学 Self-adaptive clock synchronous system
CN105843034B (en) * 2015-01-30 2020-11-17 精工爱普生株式会社 Electronic timepiece, electronic device, update information transmission device, and update information transmission method
CN105843034A (en) * 2015-01-30 2016-08-10 精工爱普生株式会社 Electronic timepiece, electronic device, update information transmission device, and update information transmission program
WO2019192451A1 (en) * 2018-04-04 2019-10-10 华为技术有限公司 Communication method and communication apparatus
CN110351709A (en) * 2018-04-04 2019-10-18 华为技术有限公司 Communication means and communication device
CN110351709B (en) * 2018-04-04 2020-12-04 华为技术有限公司 Communication method and communication device
CN111800211A (en) * 2019-04-08 2020-10-20 杭州海康威视系统技术有限公司 Data processing method, device and system
CN111800211B (en) * 2019-04-08 2023-07-25 杭州海康威视系统技术有限公司 Data processing method, device and system
WO2021051242A1 (en) * 2019-09-16 2021-03-25 Oppo广东移动通信有限公司 Time determination method and apparatus, and device
CN113647054A (en) * 2019-09-16 2021-11-12 Oppo广东移动通信有限公司 Time determination method, device and equipment
CN113647054B (en) * 2019-09-16 2023-12-05 Oppo广东移动通信有限公司 Time determination method, device and equipment

Also Published As

Publication number Publication date
CN100466553C (en) 2009-03-04

Similar Documents

Publication Publication Date Title
CN100466553C (en) Method for obtaining exact time and network device
CN101340340B (en) Access point configuring management method and access controller
CN103096435B (en) Connect keeping method, device and mobile terminal
CN109155933A (en) Reflective service quality control and management
CN104137578A (en) Method of updating a location information representing a physical location of a communication device, a computer program product for executing the method, and a communication system for updating the location information
KR20110083485A (en) Method for addressing management object in management tree and associated device management system
CN103188616B (en) The management method and system of a kind of set of terminal
GEP20094599B (en) Device for transferring information between network management entities of a wireless communication system
JP5947982B2 (en) Serving gateway, mobility management node, method and system for obtaining data gateway
US10602475B2 (en) Method and system for device location management
CN102711193B (en) Perform the apparatus and method switched fast
CN112654028B (en) Easymesh protocol-based networking management method and system
CN109995579A (en) A kind of positioning system and method for Asset Allocation
CN101247282B (en) Network test method, system and network managing station based on service level protocol
US8688741B2 (en) Device description framework information reporting and updating method, device and system
CN102447542B (en) Difference self-recognizing method and system for configuration data of network equipment
CN100499637C (en) Method for obtaining information in communication system
CN104871567A (en) Extending global operator device ID to aggregated devices
CN105592485B (en) A method of it is acquired in real time based on SNMP network management protocol and handles message
CN100518188C (en) Implementing method of developing service based on storage configuration parameter
US20100153551A1 (en) Method of managing non-ip based sensor network using simple network management protocol
CN101232404A (en) Remote network management method of EPON access system
US20080069320A1 (en) Method and system for managing information collection
EP1161846A1 (en) Relating network events to subscriber and mobile equipment identities
CN111355789A (en) Communication method and device between block chain nodes

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
C14 Grant of patent or utility model
GR01 Patent grant
C17 Cessation of patent right
CF01 Termination of patent right due to non-payment of annual fee

Granted publication date: 20090304

Termination date: 20101211