WO2011032494A1 - 精确时间协议报文处理方法和时钟设备 - Google Patents
精确时间协议报文处理方法和时钟设备 Download PDFInfo
- Publication number
- WO2011032494A1 WO2011032494A1 PCT/CN2010/076939 CN2010076939W WO2011032494A1 WO 2011032494 A1 WO2011032494 A1 WO 2011032494A1 CN 2010076939 W CN2010076939 W CN 2010076939W WO 2011032494 A1 WO2011032494 A1 WO 2011032494A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- ptp
- clock
- packet
- message
- determining unit
- 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.)
- Ceased
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04J—MULTIPLEX COMMUNICATION
- H04J3/00—Time-division multiplex systems
- H04J3/02—Details
- H04J3/14—Monitoring arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04J—MULTIPLEX COMMUNICATION
- H04J3/00—Time-division multiplex systems
- H04J3/02—Details
- H04J3/06—Synchronising arrangements
- H04J3/0635—Clock or time synchronisation in a network
- H04J3/0638—Clock or time synchronisation among nodes; Internode synchronisation
- H04J3/0658—Clock or time synchronisation among packet nodes
- H04J3/0661—Clock or time synchronisation among packet nodes using timestamps
- H04J3/0664—Clock or time synchronisation among packet nodes using timestamps unidirectional timestamps
Definitions
- the present invention relates to mobile communication technologies, and in particular, to a precise time protocol message processing method and a clock device.
- the mobile network is evolving to the Internet Protocol (IP).
- IP Internet Protocol
- the all-IP of the mobile network is an all-network end-to-end IP process, including terminal applications, access networks, bearer networks, core networks, maintenance management, etc. aspect.
- Access Network IP is intended to meet the bandwidth needs and quality needs of diverse users, providing higher bandwidth for multiple services and reducing overall costs.
- the IP of the radio access network becomes the key to the evolution of the entire mobile network to full IP.
- Clock synchronization is one of the key issues in the process of IP-based wireless access networks. Effects of the switching clock synchronization performance and coverage performance is very large, both the second-generation mobile communication system (2 nd Generation, 2G), third generation mobile communication system (3 rd generation, 3G) or Super 3G base station clock frequency The accuracy requirements are very strict. In addition, due to the characteristics of the same frequency on the uplink and downlink of the Time Division Duplexing (TDD) base station, the accuracy of the clock phase is also very strict in order to avoid interference.
- the basic function of the Precision Time Protocol (PTP) defined by IEEE 1588 is to keep the most accurate clocks in the distributed network synchronized with other clocks for standard Ethernet or other distributed bus systems using multicast technology.
- PTP Precision Time Protocol
- PTP requires that each network node must have a network interface card containing a real-time clock, which can implement related services based on the PTP protocol stack.
- PTP technology defined by the IEEE 1588 it is assumed that the PTP packet received by the node device is a process that requires the node device to perform processing. The technology only provides a solution for the node device to process PTP packets of the device. Summary of the invention
- the embodiment of the invention provides a method for processing a precise time protocol message and a clock device, and solves the problem of the prior art lacking a solution for determining and processing a non-device PTP message.
- the embodiment of the present invention provides a method for processing a precise time protocol text, including: a clock device receiving a precise time protocol PTP message, where the precise time protocol message carries end-to-end parameter information;
- the clock device determines, according to the end-to-end parameter information, whether the received PTP packet is a non-device PTP packet;
- the clock device forwards the non-device PTP packet.
- the embodiment of the invention provides a clock device, including:
- a receiving module configured to receive a PTP packet, where the PTP packet carries end-to-end parameter information
- a determining module configured to determine, according to the end-to-end parameter information, whether the received PTP packet is a non-native device PTP packet;
- the forwarding module is configured to forward the non-native device PTP text when the received PTP message is a non-native device PTP message.
- the embodiment of the present invention can determine whether the device is a PTP packet that is not a device according to the end-to-end parameter information, and then forwards the PTP packet to the non-device device. The determination and processing of the text.
- FIG. 1 is a schematic flow chart of a method according to a first embodiment of the present invention
- FIG. 2 is a schematic flow chart of a method according to a second embodiment of the present invention.
- FIG. 3 is a schematic flow chart of a method according to a third embodiment of the present invention.
- FIG. 4 is a schematic flow chart of a method according to a fourth embodiment of the present invention.
- FIG. 5 is a schematic structural diagram of a system corresponding to a fourth embodiment of the present invention.
- FIG. 6 is a schematic flow chart of a method according to a fifth embodiment of the present invention.
- FIG. 7 is a schematic structural diagram of a system corresponding to a fifth embodiment of the present invention.
- FIG. 8 is a schematic flow chart of a method according to a sixth embodiment of the present invention.
- FIG. 9 is a schematic structural diagram of a clock device according to a seventh embodiment of the present invention.
- FIG. 10 is a schematic structural diagram of a clock device according to an eighth embodiment of the present invention.
- FIG. 11 is a schematic structural diagram of a clock device according to a ninth embodiment of the present invention.
- FIG. 12 is a schematic structural diagram of a clock device according to a tenth embodiment of the present invention. detailed description
- FIG. 1 is a schematic flowchart of a method according to a first embodiment of the present invention, including:
- Step 11 The clock device receives the PTP packet, and the PTP packet carries the end-to-end parameter information.
- the end-to-end parameter information may be at least one of the following: destination address, domain number
- the destination address is the address information of the receiving end when the end-to-end communication is performed, and the domain number is the domain information of the transmitting end when the end-to-end communication is performed.
- the domain can be divided as follows:
- the two node devices (primary clock device and slave clock device) at the endpoint are grouped into the same domain (for example, Domain 1), and the intermediate nodes involved in end-to-end frequency synchronization are involved.
- the device is zoned as another domain (for example, Domain 2 ).
- the node devices used by different operators are divided into different domains.
- the division is performed according to the level of the mobile communication network. For example, when the 2G network and the 3G network coexist, the node device of the 2G network and the node device of the 3G network are divided into different domains.
- node devices of different domains will have different domain numbers.
- the node device at the transmitting end can carry the domain number of the PTP packet in the generated PTP packet, and then send the PTP packet carrying the domain number to the subsequent node device until the domain to which the sender belongs is carried.
- the PTP packet of the domain number is sent to the node device at the receiving end.
- the node devices defined by IEEE 1588 can be divided into Ordinary Clock (OC) devices, Boundary Clock (BC) devices, and Transparent Clock (TC) devices.
- OC Ordinary Clock
- BC Boundary Clock
- TC Transparent Clock
- Different clock devices perform different processing on the device's PTP packets.
- the OC device or the BC device performs the PTP packet processing on the device.
- the TC device performs normal PTP layer processing on the device and forwards the packet to the subsequent PTP packets. Node device.
- the PTP packet of the device can be a PTP packet to be processed by the clock device.
- the termination process can be understood as not forwarding the received PTP packet at the device node, but ending the PTP at the device node.
- the processing of the packet; the normal PTP layer processing can be performed by adding delay information, adding delay jitter information, and modifying the packet camp time.
- the embodiment of the present invention is related to how the clock device determines whether the received PTP packet is a PTP packet of the device or a PTP packet of the device. How to process non-device PTP packets, where A non-local device PTP packet is a PTP packet that does not require a clock device to perform PTP layer processing. Step 12: The clock device determines, according to the end-to-end parameter information, whether the received PTP packet is a non-native device PTP packet.
- the corresponding clock device can determine whether the received PTP packet is a non-native device PTP packet according to the domain number, or whether the received PTP packet is a non-native device PTP packet according to the destination address, or Determine whether the received PTP packet is a non-native device PTP packet based on the destination address and the domain ID.
- Step 13 When the received PTP packet is a non-local PTP packet, the clock device forwards the non-device PTP text.
- the non-device PTP packet can be forwarded to the node device outside the clock device.
- the clock device may directly discard the non-device PTP packet, and if the end node is synchronized, if the intermediate node generates the PTP packet at the endpoint. If the file is discarded, the end-to-end synchronization will not be implemented, which will affect the network evolution and upgrade.
- the PTP packet of the device is determined and the PTP packet of the device is not forwarded, so that the PTP packet of the device is determined and processed. You can avoid the problem of discarding PTP packets from the device and ensure end-to-end synchronization.
- the OC device, the BC device, and the TC device have different functions, and the processing of the MSC is different. Therefore, the following embodiments will respectively describe the corresponding flows.
- FIG. 2 is a schematic flowchart of a method according to a second embodiment of the present invention, including:
- Step 21 The BC device receives the ⁇ message, which carries the domain number and the destination address.
- the node device at the sending end carries the domain number in the generated packet, and the domain number is the domain number of the sub-domain to which the node device of the transmitting end belongs. After that, when the packet is transmitted on each node device, the domain number remains unchanged, which is the domain of the node device to which the sender is located. Domain number.
- the BC device or the OC device terminates the PTP file of the device and does not forward the PTP packet of the device, the destination address in the PTP packet of the device should be the address of the BC device. Therefore, in the process of determining whether the device is a PTP message, the BC device needs to compare the destination address in addition to the domain number.
- Step 22 The BC device determines whether the PTP packet is a non-native device PTP packet according to the domain number and the destination address carried in the PTP file. If yes, go to step 23. Otherwise, go to step 24.
- the BC device determines whether the domain number carried in the PTP packet is the same as the domain number configured by the BC device. If the judgment result is different, the received PTP packet is not the local device PTP. If the result is the same, and the multicast mode is used, the destination address of the PTP packet is determined to be the multicast address of the BC device. If the result is the destination of the received PTP packet. If the address is the multicast address of the BC device, the received PTP packet is the device's PTP packet. If the result is that the received destination PTP packet is not the multicast address of the BC. If the result is the same, and the unicast mode is used, the destination address of the PTP packet is determined by itself (ie, the BC device).
- the PTP packet is the PTP packet of the device. If the result is the PTP packet. If the destination address carried in the packet is not the port address of the BC device, the PTP packet is a non-local PTP packet.
- Step 23 The BC device forwards the PTP packet.
- the PTP packet is a non-local PTP packet, and the PTP packet is only processed by the BC device. Therefore, the BC device does not need to perform PTP processing on the PTP packet. That is, the BC device ignores the PTP layer processing of the non-native device PTP packet, and forwards the non-local device PTP packet to the node device outside the clock device.
- the node device that is forwarded to the clock device refers to the routing relationship. The next hop node device of the clock device is determined. Step 24: The BC device terminates the PTP packet.
- the BC device Because in ⁇ communication, the BC device will terminate the message of the device. Therefore, this step is compatible with the existing technology, and performs normal processing on the ⁇ 3 ⁇ 4 text.
- the non-device ⁇ message is determined according to the domain number and the destination address, and the BC device or the OC device processes the received ⁇ message to ensure end-to-end synchronization.
- FIG. 3 is a schematic flowchart of a method according to a third embodiment of the present invention, including:
- Step 31 The TC device receives the ⁇ message, where the ⁇ message carries the domain number.
- the TC device forwards and processes the packet of the device, and receives the received message.
- the destination address in the message is irrelevant. Therefore, it is also independent of the destination address when determining whether the device is a message.
- Step 32 The TC device determines, according to the domain number carried in the packet, whether the packet is a non-device packet, and if yes, go to step 33. Otherwise, go to step 34.
- the TC device determines whether the domain number carried in the received packet is the same as the domain number configured by the TC device. If the judgment result is the same, the received packet is the device packet. If the judgment result is different, the received ⁇ message is not the device.
- Step 33 The TC device forwards the packet.
- the TC device can forward the packet directly, or forward the related information after the packet is processed.
- the related information processing refers to adding delay information, adding delay jitter information, and modifying the packet resident. Time and so on. Specifically, whether the direct forwarding or the related information processing and forwarding can be determined according to the network configuration.
- Step 34 After the TC device performs normal layer processing on the file, the processed message is sent.
- the normal layer processing may refer to adding delay information and delay jitter information. Add interest, modify the message dwell time, and so on.
- the TC device performs related information processing on the PTP file of the device. Therefore, this step is compatible with the prior art, and performs normal PTP layer processing on the ⁇ 3 ⁇ 4 text.
- the non-device ⁇ message is determined according to the domain number, and the TC device processes the received ⁇ message to ensure end-to-end synchronization.
- the processing flow of the BC device or the OC device and the TC device is described above. According to the above principle, the packet processing can be correctly processed on the hybrid network system.
- end-to-end frequency synchronization is further implemented in a network system that has been configured for time synchronization.
- the time synchronization means that the phase of the clock signal used by the network element device to be synchronized is adjusted to be consistent.
- the frequency synchronization refers to adjusting the frequency of the clock signal used by the network element device to be synchronized to be consistent. This is called frequency synchronization ⁇ message.
- FIG. 4 is a schematic flowchart of a method according to a fourth embodiment of the present invention
- FIG. 5 is a schematic structural diagram of a system corresponding to a fourth embodiment of the present invention.
- the Global System for Mobile Communication (GSM) system implements frequency synchronization by using a three-layer unicast mode, and the path of the path is the first clock server (IPclk Server 1) 51 ⁇ the first BC device 52. ⁇ Second BC device 53 ⁇ Third BC device 54 - GSM base station 55.
- Time Division Synchronous Code Division Multiple Access (TD-SCDMA) system uses two-layer or three-layer multicast to implement time synchronization.
- the path of the path is the second clock server (IPclk Server 2) 56—first The BC device 52, after that, is split into two paths from the first BC device 52, one for the first BC device 52 ⁇ the second BC device 53 ⁇ the third: 8 (device 54 ⁇ first 3G base station (NodeB) 57, another way It is a first BC device 52 ⁇ a fourth BC device 58 ⁇ a third BC device 54 ⁇ a second 3G base station 59.
- IPclk Server 2 first The BC device 52, after that, is split into two paths from the first BC device 52, one for the first BC device 52 ⁇ the second BC device 53 ⁇ the third: 8 (device 54 ⁇ first 3G base station (NodeB) 57, another way It is a first BC device 52 ⁇ a fourth BC device 58 ⁇ a third BC device 54 ⁇ a second 3G base station 59.
- the first clock server 51 and the GSM base station 55 are configured to have the same domain number, for example, DN 1; and the second clock server 56, the first BC device 52, the second The BC device 53, the third BC device 54, the fourth BC device 58, the first 3G base station 57, and the second 3G base station 59 are configured to have the same other domain number, for example, DN 2.
- the first BC device 52, the second BC device 53, the third BC device 54, and the fourth BC device 58 are configured in a multicast mode.
- the destination address of the transmitted packet is the address that satisfies the multicast protocol, that is, the class D IP address.
- the starting range is 224.0.0.0 to 239.255.255.255.
- the destination address of the transmitted packet Is the IP address of the GSM base station.
- the BC device involved in this embodiment may be a network element such as a router or a switch.
- this embodiment includes:
- Step 401 The first clock server generates a time synchronization PTP packet, and the time synchronization PTP packet carries the domain number (DN 1 ) and the destination address (the IP address of the GSM base station) of the first clock server.
- Step 402 The first clock server sends the time synchronization PTP packet to the first BC device.
- Step 403 The domain number (DN1) carried in the time synchronization PTP file is different from the domain number (DN2) configured by the first BC device. Therefore, the first BC determines that the time synchronization PTP is not the local device PTP. Yan Wen.
- Step 404 The first BC device sends the time synchronization PTP packet to the second BC device.
- Step 405 Similar to the first BC device, the second BC device and the third BC device perform the same process until the time synchronization PTP message is sent to the GSM base station.
- the third BC device and the fourth BC device are not shown in FIG. 4, however, it will be appreciated that the deployment and functionality of these devices can still be determined from the text portion and thus still be covered by embodiments of the present invention. Within the scope.
- Step 406 The GSM base station, as the OC device, receives the time synchronization PTP packet, and determines the time synchronization PTP packet as the device PTP packet according to the domain number and the destination address carried in the time synchronization PTP packet. deal with.
- the domain number carried in the text is DN 1 and the domain configured by the GSM base station.
- the DN 1 is the same, and the destination address carried in the time synchronization PTP is the TP address of the GSM base station, and the GSM base station is configured in the unicast mode. Therefore, the time synchronization PTP message is the local device PTP message of the GMS base station.
- Step 407 The second clock server generates a frequency synchronization PTP packet, and the frequency synchronization PTP packet carries the domain number (DN 2 ) and the destination address (multicast address) of the second clock server.
- Step 408 The second clock server sends the frequency synchronization PTP packet to the first BC device.
- Step 409 The first BC device determines that the frequency synchronization PTP packet is the device PTP packet according to the domain number and the destination address carried in the frequency synchronization PTP file.
- the domain number carried in the frequency synchronization PTP packet is the same as the domain number configured by the first BC device, and the destination address carried in the frequency synchronization PTP text is its own multicast address and the first BC device is configured in the multicast mode.
- the frequency synchronization PTP packet is the local PTP of the first BC device.
- Step 410 The first BC device terminates the frequency synchronization PTP packet.
- Step 411 The first BC device regenerates the frequency synchronization PTP message with its own time information, and the regenerated frequency synchronization PTP file carries the domain number of the DN 2 and the multicast address as the destination address, and synchronizes the regenerated frequency with the PTP report.
- the text is sent to the second BC device and the fourth BC device, respectively.
- Step 412 The second BC device and the third BC device, and the fourth BC device and the third BC device also perform processing of the first BC device until the frequency is synchronized with the PTP message (the synchronized frequency is synchronized). Send to the first 3G base station and the second 3G base station.
- Step 413 The first 3G base station and the second 3G base station are OC devices. After receiving the frequency synchronization packet, the frequency synchronization packet is determined according to the domain number and the destination address carried in the frequency synchronization packet. ⁇ message, so do the final processing.
- the domain address carried in the frequency synchronization packet is the same as the domain number DN 2 configured by the first 3G base station and the second 3G base station, and the destination address carried in the frequency synchronization packet is the first 3G base station and the second 3G respectively.
- the multicast address of the base station, and the first 3G base station and the second 3G The base station is configured in a multicast mode. Therefore, the frequency synchronization PTP is the local device PTP message of the first 3G base station and the second 3G base station.
- whether the device is a non-native device PTP packet is determined by the domain number and the destination address, and the smooth implementation of the end-to-end frequency synchronization when the intermediate node is the BC device can be further implemented in the time synchronization system.
- FIG. 6 is a schematic flowchart of a method according to a fifth embodiment of the present invention
- FIG. 7 is a schematic structural diagram of a system corresponding to a fifth embodiment of the present invention.
- the GSM system implements frequency synchronization by using a three-layer unicast mode, and the path of the path is the first clock server (IPclk Server 1) 71 ⁇ the first TC device 72 ⁇ the second TC device 73 ⁇ the third TC device 74 — GSM Base station 75.
- IPclk Server 1 IPclk Server 1
- the TD-SCDMA system implements time synchronization by using a Layer 2 or Layer 3 unicast mode, and the path of the path includes a second clock server (IPclk Server 2) 76 ⁇ a first TC device 72 ⁇ a second TC device 73 ⁇ a third TC device 74 ⁇ The first 3G base station (NodeB) 77, and the second clock server 76 ⁇ the first TC device 72 ⁇ the fourth TC device 78 ⁇ the third TC device 74 ⁇ the second 3G base station 79.
- IPclk Server 2 IPclk Server 2
- the first clock server 71 and the GSM base station 75 are configured to have the same domain number, for example, DN 1; and the second clock server 76, the first TC device 72, the second TC device 73, the third TC The device 74, the fourth TC device 78, the first 3G base station 77, and the second 3G base station 79 are configured to have the same other domain number, for example, DN 2.
- the first TC device 72, the second TC device 73, the third TC device 74, the fourth TC device 78, the GSM base station 75, the first 3G base station, and the second 3G base station are configured in a unicast mode.
- the destination addresses of the transmitted packets are the IP address of the GSM base station, the IP address of the first 3G base station, and the IP address of the second 3G base station.
- the TC device involved in this embodiment may be a network element such as a router or a switch.
- this embodiment includes:
- Step 601 The first clock server generates a time synchronization PTP packet, and the time synchronization PTP packet
- the text carries the domain number (DN 1 ) of the first clock server and the destination address (the TP address of the GSM base station).
- Step 602 The first clock server sends the time synchronization PTP packet to the first TC device.
- Step 603 The domain number (DN1) carried in the time synchronization PTP text is different from the domain number (DN2) configured by the first TC device. Therefore, the first TC determines that the time synchronization PTP is not the local device PTP. Yan Wen.
- Step 604 The first TC device sends the time synchronization PTP packet to the second TC device.
- Step 605 Similar to the first TC device, the second TC device and the third TC device perform the same processing until the time synchronization PTP message is sent to the GSM base station.
- the TC device can directly transmit transparently to the non-device PTP packet, and can also perform related information processing before transmitting.
- Step 606 The GSM base station, as the OC device, receives the time synchronization PTP packet, and determines the time synchronization PTP packet as the device PTP packet according to the domain number and the destination address carried in the time synchronization PTP packet. deal with.
- the time synchronization PTP message is the local device PTP message of the GMS base station.
- Step 607 The second clock server generates a first frequency synchronization PTP message and a second frequency synchronization PTP message, where the first frequency synchronization PTP message and the second frequency synchronization PTP message respectively carry a domain number and a destination address, where The domain number carried in the first frequency synchronization PTP packet and the second frequency synchronization PTP packet is the domain number (DN 2 ) of the second clock server, and the destination address is the IP address of the first 3G base station and the second 3G base station respectively. IP address.
- Step 608 The second clock server sends the first frequency synchronization PTP message and the second frequency synchronization PTP message to the first TC device.
- Step 609 The first TC device synchronizes the PTP text and the second frequency according to the first frequency.
- the domain number carried in the PTP packet determines the first frequency synchronization PTP packet and the second frequency synchronization.
- a PTP packet is a PTP packet of the device.
- the first frequency synchronization PTP text and the second frequency synchronization PTP message are the same as the domain number carried in the first frequency synchronization PTP text and the second frequency synchronization PTP >3 ⁇ 4 text.
- the local device PTP packet of the first TC device is the same as the domain number carried in the first frequency synchronization PTP text and the second frequency synchronization PTP >3 ⁇ 4 text.
- Step 610 After the first TC device performs the normal PTP layer on the first frequency synchronization PTP packet and the second frequency synchronization PTP packet, the processed first frequency synchronization PTP packet and the second frequency synchronization PTP packet are respectively Send to the second TC device and the fourth TC device.
- Step 611 The second TC device and the third TC device, and the fourth TC device and the third TC device also perform processing of the first TC device, until the first frequency synchronization PTP message and the second frequency synchronization PTP message are respectively sent to The first 3G base station and the second 3G base station.
- the third TC device and the fourth TC device are not shown in FIG. 6, but it can be understood that the deployment and functions of these devices can still be determined from the text portion, and thus still cover the embodiment of the present invention. Within the scope.
- Step 612 The first 3G base station and the second 3G base station are OC devices, respectively, after receiving the first frequency synchronization PTP message or the second frequency synchronization PTP message, respectively, according to the first frequency synchronization PTP text or the second frequency synchronization PTP.
- the domain number and the destination address carried in the text determine that the first frequency synchronization PTP packet or the second frequency synchronization PTP packet is the device PTP packet, and therefore the termination process is performed.
- the first frequency synchronization PTP message and the second frequency synchronization PTP message and the second frequency synchronization PTP>3 ⁇ 4 text carrying the domain number DN 2 are the same as the domain number DN 2 configured by the first 3G base station and the second 3G base station, and the first frequency synchronization PTP message and the first
- the destination addresses carried in the second frequency synchronization PTP packet are respectively the IP address of the first 3G base station and the IP address of the second 3G base station, and the first 3G base station and the second 3G base station are configured in a unicast mode, therefore, the first A frequency synchronization frame and a second frequency synchronization PTP message are respectively the device contents of the first 3G base station and the second 3G base station.
- the OC device in this embodiment determines whether the device is non-device by the domain number and the destination address.
- the TC device determines whether it is a non-device packet through the domain number.
- the TC device can further implement the end-to-end frequency synchronization of the intermediate node as the BC device.
- the fourth embodiment and the fifth embodiment respectively take the BC device and the TC device as intermediate nodes as examples, and further implement end-to-end frequency synchronization in a system that has been configured to perform time synchronization. It can be understood that, by applying the principles of the embodiments of the present invention, it is still possible to further implement the end-J-side time synchronization in a system that has been configured for frequency synchronization.
- the module for performing the above processing in the clock device may be specifically a packet processing device.
- a packet processing device is also present in the clock device.
- the packet processing device in the prior art only reports the device to the PTP.
- the processing of the text can not determine and process the non-device PTP message, and the above embodiment improves the packet processing device to realize the determination and processing of the non-device PTP, ensuring the end-to-end synchronization smoothly. .
- the embodiment of the present invention can also provide a PTP file processing method, which can be used by the address matching device provided by the embodiment of the present invention by adding or expanding an existing address matching device in the clock device. Determination and processing of non-device PTP texts.
- FIG. 8 is a schematic flowchart of a method according to a sixth embodiment of the present invention, including:
- Step 81 The address matching device in the clock device receives the PTP packet, and the PTP packet carries the destination address.
- Step 82 The address matching device determines whether the destination address in the received PTP packet is its own port address. If yes, go to step 83. Otherwise, go to step 84.
- Step 83 The address matching device determines that the received PTP packet is a PTP packet of the device. After that, go to step 85.
- Step 84 The address matching device determines that the received PTP packet is a non-native device PTP packet. After that, go to step 86.
- Step 85 The address matching device forwards the PTP packet of the device to the packet processing device in the clock device, so that the processing device performs normal PTP processing on the PTP file of the device. After that, the process ends.
- Step 86 The address matching device forwards the non-device PTP packet to the node device outside the clock device.
- the node device outside the clock device is the next hop node of the clock device determined according to routing information or the like.
- the clock device may be a BC device, an OC device, or a TC device.
- the address matching method is used to determine whether the PTP text of the device is not the same, and the PTP packet of the device can be determined and processed to ensure end-to-end synchronization.
- This embodiment can be performed relatively easily without comparing the domain numbers.
- FIG. 9 is a schematic structural diagram of a clock device according to a seventh embodiment of the present invention, including a receiving module 91, a determining module 92, and a forwarding module 93.
- the receiving module 91 is configured to receive a precise time protocol PTP packet, where the precise time protocol packet carries end-to-end parameter information.
- the determining module 92 is configured to determine, according to the end-to-end parameter information, whether the received precise time protocol packet is The non-device precision time protocol message is forwarded by the forwarding module 93.
- the forwarding module 93 is configured to forward the non-local device precise time protocol text when the received precision time protocol message is the non-local device precise time protocol message.
- the PTP packet of the device is determined according to the end-to-end parameter information, and the PTP packet of the device is not processed, and the PTP packet of the device is determined and processed. You can avoid the problem of discarding PTP packets from the device and ensure end-to-end synchronization.
- different deployments may be performed according to different clock devices.
- FIG. 10 is a schematic structural diagram of a clock device according to an eighth embodiment of the present invention.
- the clock device may be a BC device or an OC device.
- the end-to-end parameter information includes a domain number and a destination address.
- the determining module 92 includes a first determining unit 101 and a first determining unit 102, where the first determining unit 101 is configured to determine whether the domain number is the same as the domain number configured by itself; the first determining unit 102 is configured to be in the first When the determining unit 101 obtains that the judgment result is different, it is determined that the received PTP packet is a non-native device PTP packet; Alternatively, the determining module 92 includes the first determining unit 101, the second determining unit 103, and the second determining unit 104.
- the second determining unit 103 is configured to obtain the same determination result in the first determining unit 101, and the clock
- the device determines, in the multicast mode, whether the destination address is a multicast address of the clock device itself.
- the second determining unit 104 is configured to obtain, by the second determining unit 103, that the destination address is not the clock device itself.
- the PTP packet received by the device is a non-local PTP packet;
- the determining unit includes the first determining unit 101, the third determining unit 105, and the third determining unit 106; the third determining unit 105 is configured to obtain the same determination result in the first determining unit 101, and the clock device In the unicast mode, it is further determined whether the destination address is the port address of the clock device itself.
- the third determining unit 106 is configured to obtain, at the third determining unit 105, that the destination address is not the port of the clock device itself.
- the received PTP packet is a non-local PTP packet.
- the forwarding module 93 includes a first forwarding unit 107, and the first forwarding unit 107 is configured to forward the PTP packet of the non-native device to the node outside the clock device. device.
- the non-device PTP packet is determined according to the domain number and the destination address, and the BC device or the OC device processes the received ,3 ⁇ 4 text to ensure end-to-end frequency synchronization.
- FIG. 11 is a schematic structural diagram of a clock device according to a ninth embodiment of the present invention.
- the clock device is a TC device.
- the end-to-end parameter information includes a domain number.
- the determining module 92 includes a fourth determining unit 111, a fourth determining unit 112, and a fifth determining unit 113.
- the fourth determining unit 111 is configured to determine whether the domain number is the same as the domain number configured by the TC device itself.
- the fourth determining unit 112 is configured to determine, when the fourth determining unit 111 is different, that the received ⁇ message is a non-device ⁇ message; the fifth determining unit 113 is configured to use the fourth determining When the unit 111 obtains the same result, it determines that the received ⁇ message is the device ⁇ message.
- the forwarding module 93 includes a second forwarding unit 114 or a third forwarding unit 115; the second The forwarding unit 114 is configured to forward the non-native device PTP packet to the node device outside the TC device, and the third forwarding unit 115 is configured to The device PTP packet is processed by the normal PTP layer, and the non-local device PTP packet is forwarded to the node device outside the TC device.
- the PTP packet of the device is determined according to the domain number, and the TC device processes the received PTP packet to ensure end-to-end synchronization.
- Each of the modules involved in the embodiment of Fig. 10 or Fig. 11 may be specifically located in a message processing device in the clock device.
- FIG. 12 is a schematic structural diagram of a clock device according to a tenth embodiment of the present invention.
- the clock device is a BC device, an OC device, or a TC device.
- the end-to-end parameter information includes a destination address.
- the determining module 92 includes a fifth determining unit 121 and a sixth determining module 122.
- the fifth determining unit 121 is configured to determine whether the destination address is its own port address.
- the sixth determining unit 122 is configured to use the When the determining unit 121 obtains the result that the destination address is not its own port address, the clock device determines that the received PTP message is a non-native device PTP message.
- the module (including the receiving module 91, the determining module 92, and the forwarding module 93) in the embodiment may be specifically located in the address matching device 1 in the clock device, and the clock device further includes a processing device 2, the address
- the matching device 1 may further include: a seventh determining unit 123, configured to: when the fifth determining unit 121 obtains the result that the destination address is its own port address, determine that the received PTP packet is a device PTP packet, and The PTP packet of the device is forwarded to the packet processing device 2 in the clock device, so that the packet processing device 2 performs normal PTP layer processing on the PTP packet of the device.
- the address matching method is used to determine whether the PTP text of the device is not the same, and the PTP text of the device can be determined and processed to ensure end-to-end synchronization.
- This embodiment does not need to compare the domain numbers, and can be executed relatively simply.
- the embodiment of the present invention further provides another implementation scheme (which may be referred to as a "context implementation scheme").
- the clock device may be a normal clock OC device or a boundary clock BC device or a transparent clock TC device, and a PTP packet.
- the PTP message sent by the master clock or the slave clock, the end-to-end parameter information includes the context information in the PTP message.
- the clock device can determine whether the received PTP packet is a non-native device PTP packet according to the end-to-end parameter information.
- the context information may be a type length value TLV field including a context ID.
- the clock device may determine whether the PTP message is related to the device according to the context information in the PTP message (or “whether or not The device PTP packet "), for example, if the context ID contained in the TLV field matches the context ID configured by the device, the PTP message is determined to be related to the device; if not, the PTP message is determined to be unrelated to the device. .
- the step of forwarding the non-local device PTP packet may include: the TC device forwards the non-local device PTP packet to the node outside the TC device by directly ignoring the PTP layer of the device.
- the device or the TC device performs the normal PTP layer processing on the non-device PTP packet, and forwards the processed non-device PTP packet to the node device outside the TC device.
- the network device When the network device is in the BC mode (that is, the network device is a BC device) or the OC mode (that is, the network device is an OC device), if the profile ID in the text matches the network device configuration profile ID, the network device may The network device can perform the termination processing (or "transmission"). In this case, the processing at the 1588V2 protocol level is not performed.
- the network device When the network device is in TC mode (that is, the network device is a TC device), if the profile ID in the packet matches the network device configuration profile ID, the network device can be modified. The port time of the message is processed according to the normal 1588V2 protocol. On the contrary, the network device can forward (or "transfer") the text, or it can be processed according to the normal 1588V2 protocol. The specific behavior can be specified through network configuration.
- the GSM system implements frequency synchronization by using a three-layer unicast mode, and the path of the path is the first clock server 51 ⁇ the first BC device 52 ⁇ the second BC device53 ⁇ the third BC.
- Device 54 ⁇ GSM base station 55.
- the TD-SCDMA system implements time synchronization by using Layer 2 or Layer 3 multicast mode.
- the path of the path is the second clock server 56 ⁇ the first BC device 52.
- the first BC device 52 is divided into two paths, and the first path is the first.
- the principle of the TP device and the BC device for the termination of the PTP packet is similar.
- the embodiment of the present invention is mainly described by using the BC device as an example, but is not limited thereto.
- the first clock server 51 and the GSM base station 55 are configured to have the same domain number, for example, DN 1; and the second clock server 56, the first BC device 52, the second BC device 53, the third BC The device 54, the fourth BC device 58, the first 3G base station 57 and the second 3G base station 59 are configured to have the same other domain number, for example, DN 2.
- the first BC device 52, the second BC device 53, the third BC device 54, and the fourth BC device 58 are configured in a multicast mode.
- the destination address of the transmitted packet is the address that satisfies the multicast protocol, that is, the class D IP address.
- the starting range is 224.0.0.0 to 239.255.255.255.
- the destination address of the transmitted packet Is the IP address of the GSM base station.
- the first clock server 51 involved in the unicast, the GSM base station, and the network element involved in the multicast belong to different telecom context telecom profiles, different profile IDs can be configured.
- the first clock server may be A TLV field containing the profile TD is added to the 1588 packet sent by the 51.
- the BC device in the middle can determine whether the profile ID in the packet matches the profile ID of the BC device.
- the intermediate BC node since the profile ID of the BC device matches only the profile ID of the multicast message, the intermediate BC node only terminates the multicast message after comparing the profile ID, and the leaflet broadcasts the message.
- the GSM system implements frequency synchronization by using a three-layer unicast mode, and the path of the path is the first clock server (IPclk Server 1) 71—the first TC device 72 ⁇ the second TC device. 73 ⁇ third TC device 74 ⁇ GSM base station 75.
- the TD-SCDMA system implements time synchronization by using a Layer 2 or Layer 3 unicast mode, and the path of the path includes a second clock server (IPclk Server 2) 76 ⁇ a first TC device 72 ⁇ a second TC device 73 ⁇ a third TC device 74 ⁇ The first 3G base station (NodeB) 77, and the second clock server 76 ⁇ the first TC device 72 ⁇ the fourth TC device 78 ⁇ the third TC device 74 ⁇ the second 3G base station 79.
- IPclk Server 2 IPclk Server 2
- the first clock server 71 and the GSM base station 75 are configured to have the same domain number, for example, DN 1; and the second clock server 76, the first TC device 72, the second TC device 73, the third TC The device 74, the fourth TC device 78, the first 3G base station 77, and the second 3G base station 79 are configured to have the same other domain number, for example, DN 2.
- the first TC device 72, the second TC device 73, the third TC device 74, the fourth TC device 78, the GSM base station 75, the first 3G base station, and the second 3G base station are configured in a unicast mode.
- the destination addresses of the transmitted packets are the IP address of the GSM base station, the IP address of the first 3G base station, and the IP address of the second 3G base station.
- the first clock server 71 involved in the unicast, the GSM base station, and the network element involved in the multicast belong to different telecom context telecom profiles, different profile IDs can be configured.
- a TLV field including a profile ID may be added to the 1588 packet sent by the first clock server 71, and the intermediate TC node may be It is determined whether the profile TD in the message matches the profile TD of the TC device.
- the intermediate TC node processes the multicast time of the multicast message after comparing the profile ID, and directly broadcasts the leaflet broadcast. ⁇ .
- the TC packet of the device is not required to be processed in the configuration of the intermediate TC node, in this embodiment, even if the intermediate TC node compares the profile ID, it finds that the message is a mismatched unicast report.
- the message will also be processed according to the protocol.
- a context determination unit and a context determination module can be configured in the determination module to implement the "context implementation.”
- the determination module includes a context determination unit and a context determination module.
- the context determining unit is configured to determine, according to the context information in the PTP message, whether the PTP message is related to the local device, and the context determining unit is configured to: when the context determining unit obtains the determination result, the determining that the received PTP message is a non-device PTP packet.
- the forwarding module may include a second forwarding unit or a third forwarding unit, where the standby PTP packet is forwarded to the node device outside the TC device; and the third forwarding unit is configured to perform normal PTP layer processing on the non-local device PTP text.
- the processed non-device PTP ⁇ file is forwarded to the node device outside the TC device.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Mobile Radio Communication Systems (AREA)
- Synchronisation In Digital Transmission Systems (AREA)
Description
精确时间协议 文处理方法和时钟设备
本申请要求于 2009 年 9 月 17 日提交中国专利局、 申请号为 200910093302.7、发明名称为"精确时间协议报文处理方法和时钟设备"的中 国专利申请的优先权, 以及于 2010年 1月 25 日提交中国专利局、 申请号 为 201010107643.8、 发明名称为 "精确时间协议报文处理方法和时钟设备" 的中国专利申请的优先权, 其全部内容通过引用结合在本申请中。 技术领域
本发明涉及移动通信技术, 特别涉及一种精确时间协议报文处理方法 和时钟设备。
背景技术
移动网络正在向全互联网协议(Internet Protocol, IP )化演进, 移动网 络的全 IP化是一个全网络端到端的 IP化过程, 包括终端应用、 接入网络、 承载网络、 核心网络、 维护管理等方面。 接入网络 IP化意在承接多样化的 用户的带宽需求和质量需求, 为多种业务提供更高的带宽, 并全面降低成 本。 当前, 随着核心网 IP化改造的逐步完成, 无线接入网的 IP化成为整个 移动网络向全 IP化演进的关键。
在实现无线接入网 IP化的过程中, 时钟同步是关键问题之一。 时钟同 步对切换性能和覆盖性能的影响非常大, 无论是第二代移动通信系统(2nd Generation, 2G )、 第三代移动通信系统( 3rd generation, 3G )还是超 3G的 基站对时钟频率的精度要求都十分严格。此外,由于时分双工( Time Division Duplexing, TDD )基站上下行釆用同一频率的特点, 为了避免千扰, 对时 钟相位的精度要求也十分严格。 IEEE 1588定义的精确时间协议(Precision Time Protocol, PTP )的基本功能是使分布式网络内的最精确时钟与其他时 钟保持同步, 用于对标准以太网或其他采用多播技术的分布式总线系统中
高同步精度, PTP在硬件上要求每个网络节点必须有一个包含实时时钟的 网络接口卡, 可以实现基于 PTP协议栈的相关服务。 现有 IEEE 1588定义 的 PTP技术中 , 假定节点设备接收的 PTP报文是需要节点设备进行处理的 处理。 技术只提供了节点设备对本设备 PTP报文处理的方案。 发明内容
本发明实施例提供了一种精确时间协议报文处理方法和时钟设备, 解 决现有技术中存在的缺乏确定及处理非本设备 PTP报文的方案的问题。
本发明实施例提供了一种精确时间协议 文处理方法, 包括: 时钟设备接收精确时间协议 PTP报文 , 所述精确时间协议报文中携带 端到端的参数信息;
时钟设备根据所述端到端的参数信息, 确定接收的 PTP报文是否为非 本设备 PTP才艮文;
时钟设备在接收的 PTP报文为非本设备 PTP报文时 , 将所述非本设备 PTP 艮文进行转发。
本发明实施例提供了一种时钟设备, 包括:
接收模块, 用于接收精确时间协议 PTP报文, 所述 PTP报文中携带端 到端的参数信息;
确定模块, 用于根据所述端到端的参数信息, 确定接收的 PTP报文是 否为非本设备 PTP报文;
转发模块, 用于在接收的 PTP报文为非本设备 PTP报文时, 将所述非 本设备 PTP 文进行转发。
由上述技术方案可知, 本发明实施例通过根据端到端参数信息确定是 否为非本设备 PTP报文, 之后, 对非本设备 PTP报文进行转发处理, 可以 实现时钟设备对非本设备 PTP报文的确定及处理。 附图说明
图 1为本发明第一实施例的方法流程示意图;
图 2为本发明第二实施例的方法流程示意图;
图 3为本发明第三实施例的方法流程示意图;
图 4为本发明第四实施例的方法流程示意图;
图 5为本发明第四实施例对应的系统的结构示意图;
图 6为本发明第五实施例的方法流程示意图;
图 7为本发明第五实施例对应的系统的结构示意图;
图 8为本发明第六实施例的方法流程示意图;
图 9为本发明第七实施例的时钟设备的结构示意图;
图 10为本发明第八实施例的时钟设备的结构示意图;
图 11为本发明第九实施例的时钟设备的结构示意图;
图 12为本发明第十实施例的时钟设备的结构示意图。 具体实施方式
图 1为本发明第一实施例的方法流程示意图, 包括:
步骤 11: 时钟设备接收 PTP报文, 该 PTP报文中携带端到端的参数信 息。
该端到端的参数信息可以为如下项中的至少一项: 目的地址、 域编号
( Domain Number, DN )。 其中, 目的地址是端到端通信时接收端的地址信 息, 域编号为端到端通信时发送端的域信息。
网络部署时, 可以根据实际需要将网络中涉及的节点设备划分为不同
的域, 不同的域具有不同的域编号。
可以采用如下方式进行域的划分:
例如, 当进行端到端的频率同步时, 将端点处的两个节点设备(主时 钟设备和从时钟设备)划为同一个域(例如, Domain 1 ), 而端到端频率同 步涉及的中间节点设备划为另一个域(例如 , Domain 2 )。
再例如, 按照运营商的不同进行划分, 不同运营商采用的节点设备被 划分到不同的域。
又例如, 按照移动通信网络的级别进行划分, 如, 2G网络和 3G网络 共存时, 将 2G网络的节点设备和 3G网络的节点设备划分为不同的域。
进行域划分后, 不同域的节点设备将具有不同的域编号。 在进行端到 端通信时, 发送端的节点设备可以将自身的域编号携带在产生的 PTP报文 中, 之后, 将携带域编号的 PTP报文向后续节点设备发送, 直至将携带发 送端所属域的域编号的 PTP报文发送给接收端的节点设备。
在采用 PTP 通信时, IEEE 1588 定义的节点设备可以分为普通时钟 ( Ordinary Clock, OC )设备、 边界时钟( Boundary Clock, BC )设备和透 明时钟( Transparent Clock, TC )设备。 不同的时钟设备对本设备 PTP报文 进行不同的处理, 例如, OC设备或者 BC设备会对本设备 PTP才艮文进行 终结处理, TC设备会对本设备 PTP报文进行正常的 PTP层处理后转发给 后续节点设备。
其中, 本设备 PTP报文可以是指时钟设备需要处理的 PTP报文; 终结 处理可以理解为在该设备节点处对接收的 PTP报文不进行转发, 而是在该 设备节点处结束对该 PTP报文的处理流程; 正常的 PTP层处理可以是指进 行时延信息的添加、 时延抖动信息的添加、 修改报文驻留时间等。
上述各时钟设备针对本设备 PTP报文的具体处理流程可以参见现有技 术, 本发明实施例关注于时钟设备如何确定接收的 PTP报文是本设备 PTP 报文还是非本设备 PTP报文,及如何对非本设备 PTP报文进行处理,其中,
非本设备 PTP报文是指不需要时钟设备进行 PTP层面处理的 PTP报文。 步骤 12: 时钟设备根据该端到端的参数信息, 确定接收的 PTP报文是 否为非本设备 PTP报文。
根据时钟设备的不同,对应的时钟设备可以根据域编号确定接收的 PTP 报文是否为非本设备 PTP报文, 或者, 根据目的地址确定接收的 PTP报文 是否为非本设备 PTP报文, 或者, 根据目的地址及域编号确定接收的 PTP 报文是否为非本设备 PTP报文。
步驟 13: 时钟设备在接收的 PTP报文为非本设备 PTP报文时, 将该非 本设备 PTP 文进行转发。
本步驟中, 可以将该非本设备 PTP报文转发给该时钟设备外的节点设 备。
现有技术中由于没有非本设备 PTP报文的处理方案, 因此, 时钟设备 很可能直接丢弃非本设备 PTP报文, 而要实现端到端同步时, 如果中间节 点将端点处产生的 PTP报文丢弃, 则会造成端到端同步的不可实施, 影响 网络演进升级。
本实施例通过确定非本设备 PTP报文, 并对非本设备 PTP报文进行转 发处理, 实现对非本设备 PTP报文的确定及处理。 可以避免丢弃非本设备 PTP报文的问题 , 保证端到端同步的实施。
由上述描述可知, OC设备、 BC设备和 TC设备具有不同的功能, 对 ΡΤΡ ·¾文的处理有所不同, 因此下面的实施例将分别描述对应的流程。
图 2为本发明第二实施例的方法流程示意图, 包括:
步骤 21 : BC设备接收 ΡΤΡ报文, 该 ΡΤΡ报文中携带域编号和目的地 址。
在端到端同步时, 发送端的节点设备会在产生的 ΡΤΡ报文中携带域编 号, 该域编号为发送端的节点设备所属分域的域编号。 之后, ΡΤΡ报文在 各节点设备上传输时该域编号保持不变, 为发送端的节点设备所属分域的
域编号。
可以理解的是: 由于 BC设备或者 OC设备是对本设备 PTP 文进行 终结处理, 不会转发该本设备 PTP报文, 因此本设备 PTP报文中的目的地 址应该为 BC设备的地址。 故而, BC设备在判断是否为本设备 PTP报文的 过程中, 除了域编号之外, 还需要比对目的地址。
步骤 22: BC设备根据该 PTP 文中携带的域编号和目的地址, 判断 该 PTP报文是否为非本设备 PTP报文, 若是, 执行步驟 23, 否则, 执行步 驟 24。
具体地, BC设备判断该 PTP报文中携带的域编号是否与自身 (即 BC 设备)配置的域编号相同, 若判断结果为不同, 则接收的 PTP报文为非本 设备 PTP才艮文; 若判断结果为相同, 且当组播模式时, 进一步判断该 PTP 报文中携带的目的地址是否为自身(即 BC设备)的组播地址, 若判断结果 是接收的 PTP报文中携带的目的地址是自身 (即 BC设备)的组播地址, 则该接收的 PTP报文为本设备 PTP报文,若判断结果是接收的 PTP报文中 携带的目的地址不是自身(即 BC )的组播地址, 则该接收的 PTP报文为非 本设备 PTP报文;若判断结果为相同,且当单播模式时,进一步判断该 PTP 报文中携带的目的地址是否为自身(即 BC设备)的端口地址, 若判断结果 是该 PTP报文中携带的目的地址为该 BC设备的端口地址时, 则该 PTP报 文为本设备 PTP报文, 若判断结果是该 PTP报文中携带的目的地址不是该 BC设备的端口地址时 , 则该 PTP报文为非本设备 PTP报文。
步驟 23: BC设备转发该 PTP报文。
由于该 PTP报文为非本设备 PTP报文, 该 PTP报文只是途径该 BC设 备, 因此, 该 BC设备无需对该 PTP报文进行 PTP层面的处理。 即 BC设 备忽略对非本设备 PTP报文进行 PTP层处理,直接转发该非本设备 PTP报 文给该时钟设备外的节点设备, 该转发给的时钟设备外的节点设备是指按 照路由关系等确定的该时钟设备的下一跳节点设备。
步驟 24: BC设备终结该 PTP报文。
由于在 ΡΤΡ通信中, BC设备会对本设备 ΡΤΡ报文进行终结处理, 因 此, 本步驟是兼容现有技术, 对 ΡΤΡ ·¾文进行正常的 ΡΤΡ层面的处理。
本实施例以 BC设备为例进行了说明,但是,本实施例的方案同样可以 适用于 OC设备, 不再赘述。
本实施例根据域编号和目的地址确定非本设备 ΡΤΡ报文, 实现 BC设 备或者 OC设备对接收的 ΡΤΡ报文的处理, 保证端到端同步的实施。
图 3为本发明第三实施例的方法流程示意图, 包括:
步驟 31 : TC设备接收 ΡΤΡ报文, 该 ΡΤΡ报文中携带域编号。
可以理解的是: TC设备是对本设备 ΡΤΡ报文进行转发处理, 与接收的
ΡΤΡ报文中的目的地址无关, 因此, 在确定是否为本设备 ΡΤΡ报文时也与 目的地址无关。
步骤 32: TC设备根据该 ΡΤΡ报文中携带的域编号, 判断该 ΡΤΡ报文 是否为非本设备 ΡΤΡ报文, 若是, 执行步驟 33 , 否则, 执行步驟 34。
具体地, 该 TC设备判断接收的 ΡΤΡ报文中携带的域编号是否与自身 (即 TC设备)配置的域编号相同, 若判断结果是相同, 则该接收的 ΡΤΡ 报文为本设备 ΡΤΡ报文, 若判断结果是不同, 则该接收的 ΡΤΡ报文为非本 设备 ΡΤΡ才艮文。
步驟 33: TC设备转发该 ΡΤΡ报文。
其中, TC设备可以直接转发该 ΡΤΡ报文, 或者, 对该 ΡΤΡ报文进行 相关信息处理后转发, 相关信息处理是指进行时延信息的添加、 时延抖动 信息的添加、 修改报文驻留时间等。 具体地是直接转发还是进行相关信息 处理后转发可以根据网络配置来确定。
步骤 34: TC设备对该 ΡΤΡ 文进行正常的 ΡΤΡ层处理后, 发送处理 后的 ΡΤΡ才艮文。
其中, 正常的 ΡΤΡ层处理可以是指进行时延信息的添加、 时延抖动信
息的添加、 修改报文驻留时间等。
由于在 PTP通信中, TC设备会对本设备的 PTP 文进行相关信息处 理, 因此, 本步驟是兼容现有技术, 对 ΡΤΡ ·¾文进行正常的 PTP层面的处 理。
本实施例根据域编号确定非本设备 ΡΤΡ报文, 实现 TC设备对接收的 ΡΤΡ报文的处理, 保证端到端同步的实施。
上面对 BC设备或者 OC设备, 及 TC设备的处理流程进行了描述, 依 据上述的原理可以对混合组网的系统进行 ΡΤΡ报文的正确处理。 例如, 在 已经配置成进行时间同步的网络系统中进一步的实现端到端的频率同步。 其中, 时间同步是指将待同步的网元设备釆用的时钟信号的相位调整成一 致, 频率同步是指将待同步的网元设备采用的时钟信号的频率调整为一致。 文称为频率同步 ΡΤΡ报文。
图 4为本发明第四实施例的方法流程示意图, 图 5为本发明第四实施 例对应的系统的结构示意图。
参见图 5, 全球移动通信 ( Global System for Mobile Communication, GSM ) 系统采用三层单播方式实现频率同步, 途径的路径为第一时钟月良务 器( IPclk Server 1 ) 51→第一 BC设备 52→第二 BC设备 53→第三 BC设备 54— GSM基站 55。 时分同步码分多址(Time Division Synchronous Code Division Multiple Access, TD-SCDMA ) 系统采用二层或者三层组播方式实 现时间同步, 途径的路径为第二时钟服务器( IPclk Server 2 ) 56—第一 BC 设备 52, 之后, 从第一 BC设备 52分为两路, 一路为第一 BC设备 52→第 二 BC设备 53→第三:8( 设备 54→第一 3G基站(NodeB ) 57, 另一路为第 一 BC设备 52→第四 BC设备 58→第三 BC设备 54→第二 3G基站 59。
在系统部署时,第一时钟服务器 51和 GSM基站 55被配置成具有相同 的域编号, 例如, DN 1; 而第二时钟服务器 56、 第一 BC设备 52、 第二
BC设备 53、 第三 BC设备 54、 第四 BC设备 58、 第一 3G基站 57和第二 3G基站 59被配置成具有相同的另一域编号, 例如, DN 2。 第一 BC设备 52、 第二 BC设备 53、第三 BC设备 54和第四 BC设备 58被配置成组播模 式。
在组播时, 传输的报文的目的地址为满足组播协议的地址, 即 D类 IP 地址, 起始范围为 224.0.0.0到 239.255.255.255; 在单播时, 传输的报文的 目的地址为 GSM基站的 IP地址。
本实施例中涉及的 BC设备可以为路由器、 交换机等网元。
参加图 4, 本实施例包括:
步驟 401: 第一时钟服务器产生时间同步 PTP报文, 时间同步 PTP报 文中携带第一时钟服务器的域编号 (DN 1 )和目的地址(GSM基站的 IP 地址)。
步骤 402: 第一时钟服务器将时间同步 PTP报文发送给第一 BC设备。 步骤 403: 由于该时间同步 PTP 文中携带的域编号 (DN1 )和第一 BC设备自身配置的域编号 (DN2 ) 不同, 因此, 第一 BC确定该时间同步 PTP才艮文为非本设备 PTP才艮文。
步骤 404: 第一 BC设备将该时间同步 PTP报文发送给第二 BC设备。 步驟 405: 类似于第一 BC设备, 第二 BC设备和第三 BC设备做同样 的处理, 直至将该时间同步 PTP ^艮文发送给 GSM基站。
为了简化起见, 图 4中并未画出第三 BC设备和第四 BC设备, 但是, 可以理解的是, 这些设备的部署及功能仍然可以从文字部分确定, 因此仍 在本发明实施例的覆盖范围内。
步驟 406: GSM基站作为 OC设备, 接收到时间同步 PTP报文后, 根 据时间同步 PTP报文中携带的域编号和目的地址 , 确定该时间同步 PTP报 文为本设备 PTP报文, 因此做终结处理。
由于时间同步 ΡΤΡ ·¾文中携带的域编号为 DN 1与 GSM基站配置的域
编号 DN 1相同, 时间同步 PTP才艮文中携带的目的地址为 GSM基站的 TP 地址,且 GSM基站被配置成单播模式,因此,该时间同步 PTP报文为 GMS 基站的本设备 PTP报文。
步骤 407: 第二时钟服务器产生频率同步 PTP报文, 频率同步 PTP报 文中携带第二时钟服务器的域编号 (DN 2 )和目的地址(组播地址)
步骤 408: 第二时钟服务器将频率同步 PTP报文发送给第一 BC设备。 步驟 409:第一 BC设备根据频率同步 PTP 文中携带的域编号和目的 地址, 确定该频率同步 PTP报文为本设备 PTP报文。
由于频率同步 PTP报文中携带的域编号和第一 BC设备配置的域编号 相同,且频率同步 PTP 文中携带的目的地址为自身的组播地址且第一 BC 设备被配置成组播模式, 因此, 频率同步 PTP报文为第一 BC设备的本设 备 PTP才艮文。
步骤 410: 第一 BC设备终结该频率同步 PTP报文。
步驟 411: 第一 BC设备用自身的时间信息再生频率同步 PTP报文,再 生的频率同步 PTP 文中携带为 DN 2的域编号和作为目的地址的组播地 址, 并将再生后的频率同步 PTP报文分别发送给第二 BC设备和第四 BC 设备。
步驟 412: 第二 BC设备和第三 BC设备, 及第四 BC设备和第三 BC 设备同样做第一 BC设备的处理, 直至将频率同步 PTP报文 (再生后的频 率同步 ΡΤΡ ·¾文)发送给第一 3G基站和第二 3G基站。
步骤 413: 第一 3G基站和第二 3G基站为 OC设备, 接收到频率同步 ΡΤΡ报文后 , 根据频率同步 ΡΤΡ报文中携带的域编号和目的地址, 确定该 频率同步 ΡΤΡ报文为本设备 ΡΤΡ报文, 因此做终结处理。
由于频率同步 ΡΤΡ报文中携带的域编号为 DN 2与第一 3G基站和第二 3G基站配置的域编号 DN 2相同, 频率同步 ΡΤΡ 文中携带的目的地址分 别为第一 3G基站和第二 3G基站的组播地址, 且第一 3G基站和第二 3G
基站被配置成组播模式 , 因此, 该频率同步 PTP才艮文为第一 3G基站和第 二 3G基站的本设备 PTP报文。
步驟 401-406与步驟 406-413之间无时序限制关系。
本实施例通过域编号和目的地址确定是否为非本设备 PTP报文, 可以 在时间同步系统中,进一步实现中间节点为 BC设备时端到端频率同步的顺 利实施。
图 6为本发明第五实施例的方法流程示意图, 图 7为本发明第五实施 例对应的系统的结构示意图。
参见图 7, GSM系统采用三层单播方式实现频率同步, 途径的路径为 第一时钟服务器(IPclk Server 1 ) 71→第一 TC设备 72→第二 TC设备 73 →第三 TC设备 74— GSM基站 75。 TD-SCDMA系统采用二层或者三层单 播方式实现时间同步, 途径的路径包括第二时钟服务器(IPclk Server 2 ) 76 →第一 TC设备 72→第二 TC设备 73→第三 TC设备 74→第一 3G基站 ( NodeB ) 77, 及第二时钟服务器 76→第一 TC设备 72→第四 TC设备 78 →第三 TC设备 74→第二 3G基站 79。
在系统部署时,第一时钟服务器 71和 GSM基站 75被配置成具有相同 的域编号, 例如, DN 1; 而第二时钟服务器 76、 第一 TC设备 72、 第二 TC 设备 73、 第三 TC设备 74、 第四 TC设备 78、 第一 3G基站 77和第二 3G 基站 79被配置成具有相同的另一域编号, 例如, DN 2。 第一 TC设备 72、 第二 TC设备 73、 第三 TC设备 74、 第四 TC设备 78、 GSM基站 75、 第一 3G基站和第二 3G基站被配置成单播模式。
在单播时, 传输的报文的目的地址分别为 GSM基站的 IP地址、 第一 3G基站的 IP地址和第二 3G基站的 IP地址。
本实施例中涉及的 TC设备可以为路由器、 交换机等网元。
参加图 6, 本实施例包括:
步骤 601: 第一时钟服务器产生时间同步 PTP报文, 时间同步 PTP报
文中携带第一时钟服务器的域编号 (DN 1 )和目的地址(GSM基站的 TP 地址)。
步驟 602: 第一时钟服务器将时间同步 PTP报文发送给第一 TC设备。 步骤 603: 由于该时间同步 PTP 文中携带的域编号 (DN1 )和第一 TC设备自身配置的域编号 (DN2 ) 不同, 因此, 第一 TC确定该时间同步 PTP才艮文为非本设备 PTP才艮文。
步驟 604: 第一 TC设备将该时间同步 PTP报文发送给第二 TC设备。 步驟 605: 类似于第一 TC设备, 第二 TC设备和第三 TC设备做同样 的处理, 直至将该时间同步 PTP ^艮文发送给 GSM基站。
其中, 对于非本设备 PTP报文, TC设备可以直接进行透传, 也可以进 行相关信息处理后再传输。
步驟 606: GSM基站作为 OC设备, 接收到时间同步 PTP报文后, 根 据时间同步 PTP报文中携带的域编号和目的地址 , 确定该时间同步 PTP报 文为本设备 PTP报文, 因此做终结处理。
由于时间同步 ΡΤΡ ·¾文中携带的域编号为 DN 1与 GSM基站配置的域 编号 DN 1相同, 时间同步 ΡΤΡ才艮文中携带的目的地址为 GSM基站的 IP 地址,且 GSM基站被配置成单播模式,因此,该时间同步 PTP报文为 GMS 基站的本设备 PTP报文。
步驟 607: 第二时钟服务器产生第一频率同步 PTP报文和第二频率同 步 PTP报文 ,第一频率同步 PTP报文和第二频率同步 PTP报文中分别携带 域编号和目的地址, 其中, 第一频率同步 PTP报文和第二频率同步 PTP报 文中携带的域编号均为第二时钟服务器的域编号(DN 2 ), 目的地址分别为 第一 3G基站的 IP地址和第二 3G基站的 IP地址。
步骤 608: 第二时钟服务器将第一频率同步 PTP报文和第二频率同步 PTP报文均发送给第一 TC设备。
步骤 609: 第一 TC设备根据第一频率同步 PTP 文和第二频率同步
PTP报文中携带的域编号, 确定该第一频率同步 PTP报文和第二频率同步
PTP报文为本设备 PTP报文。
由于第一频率同步 PTP 文和第二频率同步 PTP >¾文中携带的域编号 和第一 TC设备配置的域编号相同, 因此, 第一频率同步 PTP才艮文和第二 频率同步 PTP报文为第一 TC设备的本设备 PTP报文。
步骤 610:第一 TC设备对第一频率同步 PTP才艮文和第二频率同步 PTP 报文进行正常 PTP层后 , 将处理后的第一频率同步 PTP报文和第二频率同 步 PTP报文分别发送给第二 TC设备和第四 TC设备。
步骤 611: 第二 TC设备和第三 TC设备, 及第四 TC设备和第三 TC 设备同样做第一 TC设备的处理, 直至第一频率同步 PTP报文和第二频率 同步 PTP 文分别发送给第一 3G基站和第二 3G基站。
为了简化起见, 图 6中并未画出第三 TC设备和第四 TC设备, 但是, 可以理解的是, 这些设备的部署及功能仍然可以从文字部分确定, 因此仍 在本发明实施例的覆盖范围内。
步骤 612: 第一 3G基站和第二 3G基站为 OC设备, 分别对应接收到 第一频率同步 PTP报文或第二频率同步 PTP报文后 ,根据第一频率同步 PTP 文或第二频率同步 PTP 文中携带的域编号和目的地址, 确定该第一频 率同步 PTP报文或第二频率同步 PTP报文为本设备 PTP报文 , 因此做终结 处理。
由于第一频率同步 PTP 文和第二频率同步 PTP >¾文中携带的域编号 为 DN 2与第一 3G基站和第二 3G基站配置的域编号 DN 2相同,第一频率 同步 PTP报文和第二频率同步 PTP报文中携带的目的地址分别为第一 3G 基站的 IP地址和第二 3G基站的 IP地址, 且第一 3G基站和第二 3G基站 被配置成单播模式, 因此, 该第一频率同步 ΡΤΡ ·¾文和第二频率同步 PTP 才艮文分别为第一 3G基站和第二 3G基站的本设备 ΡΤΡ 文。
本实施例中的 OC设备通过域编号和目的地址确定是否为非本设备
PTP报文, TC设备通过域编号确定是否为非本设备 ΡΤΡ报文, 可以在时间 同步系统中, 进一步实现中间节点为 BC设备时端到端频率同步的顺利实 施。
第四实施例和第五实施例分别以 BC设备和 TC设备作为中间节点为 例, 在已经配置成进行时间同步的系统中进一步实现端到端频率同步。 可 以理解的是, 应用本发明实施例的原理, 仍旧可以实现在已经配置成频率 同步的系统中进一步实现端 'J端时间同步。
在时钟设备中进行上述处理的模块可以具体为报文处理装置, 现有技 术中, 在时钟设备中同样会存在一个报文处理装置, 但是现有技术中的报 文处理装置只是对本设备 PTP报文进行处理,无法确定及处理非本设备 PTP 报文, 而上述实施例通过对报文处理装置进行改进, 实现对非本设备 PTP 才艮文的确定及处理, 保证端到端同步地顺利进行。
与上述实施例不同,本发明实施例还可以提供一种 PTP 文处理方法, 该方法是通过在时钟设备中新增或者扩展现有地址匹配装置, 使本发明实 施例提供的地址匹配装置可以用于非本设备 PTP 文的确定及处理。
图 8为本发明第六实施例的方法流程示意图, 包括:
步骤 81 : 时钟设备中的地址匹配装置接收 PTP报文, 该 PTP报文中携 带目的地址。
步驟 82: 该地址匹配装置判断接收的 PTP报文中的目的地址是否自身 的端口地址, 若是, 执行步驟 83 , 否则, 执行步驟 84。
步驟 83: 该地址匹配装置确定接收的 PTP报文为本设备 PTP报文。 之 后, 执行步骤 85。
步驟 84: 该地址匹配装置确定接收的 PTP报文为非本设备 PTP报文。 之后, 执行步骤 86。
步驟 85: 该地址匹配装置将本设备 PTP报文转发给该时钟设备内的报 文处理装置,以便该 文处理装置对本设备 PTP 文进行正常的 PTP处理。
之后, 结束流程。
步骤 86: 该地址匹配装置将非本设备 PTP报文转发给该时钟设备外的 节点设备。
该时钟设备外的节点设备为根据路由信息等确定的该时钟设备的下一 跳节点。
本实施例中 , 时钟设备可以为 BC设备、 OC设备或者 TC设备。
本实施例采用地址匹配的方式进行是否非本设备 PTP 文的判断, 同 样可以实现非本设备 PTP报文的确定及处理, 保证端到端同步的实施。 本 实施例不用比较域编号, 可以较为简便的执行。
图 9为本发明第七实施例的时钟设备的结构示意图,包括接收模块 91、 确定模块 92和转发模块 93。接收模块 91用于接收精确时间协议 PTP报文, 该精确时间协议报文中携带端到端的参数信息; 确定模块 92用于根据该端 到端的参数信息, 确定接收的精确时间协议报文是否为非本设备精确时间 协议报文; 转发模块 93用于在接收的精确时间协议报文为非本设备精确时 间协议 文时, 将该非本设备精确时间协议 文进行转发。
本实施例根据端到端参数信息确定非本设备 PTP报文, 并对非本设备 PTP报文进行转发处理, 实现对非本设备 PTP报文的确定及处理。 可以避 免丢弃非本设备 PTP报文的问题, 保证端到端同步的实施。
在具体实施时, 可以根据时钟设备的不同进行分别部署。
图 10为本发明第八实施例的时钟设备的结构示意图, 该时钟设备可以 为 BC设备或者 OC设备, 此时, 该端到端的参数信息包括域编号和目的地 址。
此时, 确定模块 92包括第一判断单元 101和第一确定单元 102, 第一 判断单元 101 用于判断该域编号与自身配置的域编号是否相同; 该第一确 定单元 102用于在该第一判断单元 101得到判断结果为不同时, 确定该接 收的 PTP报文为非本设备 PTP报文;
或者, 该确定模块 92包括该第一判断单元 101、 第二判断单元 103和 第二确定单元 104;该第二判断单元 103用于在该第一判断单元 101得到判 断结果为相同, 且该时钟设备在组播模式下, 进一步判断该目的地址是否 为该时钟设备自身的组播地址; 该第二确定单元 104用于在该第二判断单 元 103得到判断结果为该目的地址不是该时钟设备自身的组播地址时, 确 定该接收的 PTP报文为非本设备 PTP报文;
或者, 该确定单元包括该第一判断单元 101、 第三判断单元 105和第三 确定单元 106;该第三判断单元 105用于在该第一判断单元 101得到判断结 果为相同, 且该时钟设备在单播模式下, 进一步判断该目的地址是否为该 时钟设备自身的端口地址;该第三确定单元 106用于在该第三判断单元 105 得到判断结果为该目的地址不是该时钟设备自身的端口地址时, 确定该接 收的 PTP报文为非本设备 PTP报文。
该转发模块 93包括第一转发单元 107, 该第一转发单元 107用于对该 非本设备 PTP报文忽略 PTP层的处理,直接将该非本设备 PTP报文转发给 该时钟设备外的节点设备。
本实施例根据域编号和目的地址确定非本设备 PTP报文, 实现 BC设 备或者 OC设备对接收的 ΡΤΡ ·¾文的处理, 保证端到端频率同步的实施。
图 11为本发明第九实施例的时钟设备的结构示意图,该时钟设备为 TC 设备, 此时, 该端到端的参数信息包括域编号。
此时, 该确定模块 92包括第四判断单元 111、 第四确定单元 112和第 五确定单元 113; 该第四判断单元 111用于判断该域编号与该 TC设备自身 配置的域编号是否相同; 该第四确定单元 112 用于在该第四判断单元 111 得到判断结果为不同时, 确定该接收的 ΡΤΡ报文为非本设备 ΡΤΡ报文; 该 第五确定单元 113用于在该第四判断单元 111得到判断结果为相同时,确定 该接收的 ΡΤΡ报文为本设备 ΡΤΡ报文。
该转发模块 93包括第二转发单元 114或者第三转发单元 115; 该第二
转发单元 114用于对该非本设备 PTP 艮文忽略 PTP层的处理, 直接将该非 本设备 PTP报文转发给该 TC设备外的节点设备; 该第三转发单元 115用 于对该非本设备 PTP报文进行正常的 PTP层处理, 将处理后的该非本设备 PTP报文转发给该 TC设备外的节点设备。
本实施例根据域编号确定非本设备 PTP报文, 实现 TC设备对接收的 PTP报文的处理, 保证端到端同步的实施。
在图 10或图 11的实施例中涉及的各模块可以均具体位于时钟设备中 的报文处理装置中。
图 12 为本发明第十实施例的时钟设备的结构示意图, 该时钟设备为 BC设备、 OC设备或者 TC设备, 此时, 该端到端的参数信息包括目的地 址。
此时, 该确定模块 92包括第五判断单元 121和第六确定模块 122; 该 第五判断单元 121 用于判断该目的地址是否为自身的端口地址; 该第六确 定单元 122用于在该第五判断单元 121得到判断结果为该目的地址不是自 身的端口地址时, 该时钟设备确定接收的 PTP报文为非本设备 PTP报文。
其中 , 本实施例中涉及的模块 (包括接收模块 91、 确定模块 92和转发 模块 93 )可以具体位于时钟设备中的地址匹配装置 1中, 该时钟设备还包 括才艮文处理装置 2, 该地址匹配装置 1还可以包括: 第七确定单元 123 , 用 于在该第五判断单元 121得到判断结果为该目的地址是自身的端口地址时, 确定接收的 PTP报文为本设备 PTP报文,并将该本设备 PTP报文转发给该 时钟设备内的报文处理装置 2, 以便该报文处理装置 2对该本设备 PTP报 文进行正常的 PTP层处理。
该本实施例采用地址匹配的方式进行是否非本设备 PTP 文的判断, 同样可以实现非本设备 PTP才艮文的确定及处理, 保证端到端同步的实施。 本实施例不用比较域编号, 可以较为简便的执行。
本发明实施例还提供了另一种实现方案(可称为 "上下文实现方案"): 该实现方案中,时钟设备可以为普通时钟 OC设备或边界时钟 BC设备 或透明时钟 TC设备, PTP报文为主时钟或从时钟发送的 PTP消息, 端到 端的参数信息包括 PTP消息中的上下文信息。 时钟设备可以根据端到端的 参数信息, 确定接收到的 PTP报文是否为非本设备 PTP报文。
具体的, 上下文信息可以为包含上下文 ID 的类型长度值 TLV字段, 相应的, 时钟设备可以才艮据该 PTP消息中的上下文信息, 判断该 PTP消息 是否与本设备相关(或者说"是否为非本设备 PTP报文"), 比如,如果 TLV 字段中包含的上下文 ID与本设备配置的上下文 ID相匹配, 则判断 PTP消 息与本设备相关; 如果不匹配, 则判断 PTP消息与本设备不相关。
另外, 对于 TC设备, 将非本设备 PTP报文进行转发的步驟可以包括: TC设备对非本设备 PTP报文忽略 PTP层的处理, 直接将非本设备 PTP报 文转发给 TC设备外的节点设备; 或者, TC设备, 对非本设备 PTP报文进 行正常的 PTP层处理, 将处理后的非本设备 PTP 艮文转发给 TC设备外的 节点设备。
以在 1588报文中增加 TLV为例:
1、 在 1588报文中增加新的 TLV ( Type-Length- Value, 类型长度值), 其中携带了该报文所对应的 1588 上下文 profile ID ,网络设备可以对 profile ID进行检查。
2、 当网络设备处于 BC模式(即该网络设备是 BC设备 )或者 OC模 式(即该网络设备是 OC设备 ),如果该 文中的 profile ID与网络设备配置 profile ID匹配, 则该网络设备可以对才艮文进行终结处理; 反之, 则该网络 设备可以对该报文进行转发(或者说 "透传")处理, 此种情况下, 不进行 1588V2协议层面的处理。
3、 当网络设备是 TC模式(即该网络设备是 TC设备) 时, 如果该报 文中的 profile ID与网络设备配置 profile ID匹配, 则该网络设备可以修改
才艮文驻留时间, 按照正常的 1588V2协议进行处理。 反之, 则该网络设备可 以对该 文进行转发(或者说 "透传")处理,或者,也可以按照正常的 1588V2 协议进行处理, 具体的行为可以通过网络配置来规范。
以下是该方案在具体场景中的应用:
在图 4、 图 5所对应的技术方案中, GSM系统采用三层单播方式实现 频率同步, 途径的路径为第一时钟服务器 51→第一 BC设备 52→第二 BC 设备 53→第三 BC设备 54→ GSM基站 55。 TD-SCDMA系统采用二层或者 三层组播方式实现时间同步, 途径的路径为第二时钟服务器 56→第一 BC 设备 52, 之后, 从第一 BC设备 52分为两路, 一路为第一 BC设备 52→第 二 BC设备 53→第三:6( 设备 54→第一 3G基站(NodeB ) 57, 另一路为第 一 BC设备 52→第四 BC设备 58→第三 BC设备 54→第二 3G基站 59。
可以理解的是, OC设备和 BC设备对 PTP报文进行终结处理的原理类 似, 本发明实施例主要以 BC设备为例进行描述, 但不限于此。
在系统部署时,第一时钟服务器 51和 GSM基站 55被配置成具有相同 的域编号, 例如, DN 1; 而第二时钟服务器 56、 第一 BC设备 52、 第二 BC设备 53、 第三 BC设备 54、 第四 BC设备 58、 第一 3G基站 57和第二 3G基站 59被配置成具有相同的另一域编号, 例如, DN 2。 第一 BC设备 52、 第二 BC设备 53、第三 BC设备 54和第四 BC设备 58被配置成组播模 式。
在组播时, 传输的报文的目的地址为满足组播协议的地址, 即 D类 IP 地址, 起始范围为 224.0.0.0到 239.255.255.255; 在单播时, 传输的报文的 目的地址为 GSM基站的 IP地址。
此种情况下, 由于单播涉及的第一时钟服务器 51、 GSM基站与组播涉 及的网元(比如 BC设备)分属不同的电信上下文 telecom profile, 因此可 以配置不同的 profile ID。
根据本发明实施例提供的 "上下文实现方案", 可以在第一时钟服务器
51发出的 1588报文中增加包含 profile TD的 TLV字段 , 中间的 BC设备可 以判断该^艮文中的 profile ID与该 BC设备的 profile ID是否匹配。
在本实施例中,由于 BC设备的 profile ID只与组播^艮文的 profile ID匹 配, 因此中间 BC节点在对比 profile ID后只终结组播 ^艮文 , 而透传单播才艮 文。 在图 6、 图 7所对应的技术方案中, GSM系统采用三层单播方式实现 频率同步, 途径的路径为第一时钟服务器( IPclk Server 1 ) 71—第一 TC设 备 72→第二 TC设备 73→第三 TC设备 74→ GSM基站 75。 TD-SCDMA系 统采用二层或者三层单播方式实现时间同步, 途径的路径包括第二时钟服 务器( IPclk Server 2 ) 76→第一 TC设备 72→第二 TC设备 73→第三 TC设 备 74→第一 3G基站(NodeB ) 77, 及第二时钟服务器 76→第一 TC设备 72→第四 TC设备 78→第三 TC设备 74→第二 3G基站 79。
在系统部署时,第一时钟服务器 71和 GSM基站 75被配置成具有相同 的域编号, 例如, DN 1; 而第二时钟服务器 76、 第一 TC设备 72、 第二 TC 设备 73、 第三 TC设备 74、 第四 TC设备 78、 第一 3G基站 77和第二 3G 基站 79被配置成具有相同的另一域编号, 例如, DN 2。 第一 TC设备 72、 第二 TC设备 73、 第三 TC设备 74、 第四 TC设备 78、 GSM基站 75、 第一 3G基站和第二 3G基站被配置成单播模式。
在单播时, 传输的报文的目的地址分别为 GSM基站的 IP地址、 第一 3G基站的 IP地址和第二 3G基站的 IP地址。
此种情况下, 由于单播涉及的第一时钟服务器 71、 GSM基站与组播涉 及的网元(比如 TC设备 )分属不同的电信上下文 telecom profile, 因此, 可以配置有不同的 profile ID。
根据本发明实施例提供的 "上下文实现方案", 可以在第一时钟服务器 71发出的 1588报文中增加包含 profile ID的 TLV字段, 中间的 TC节点可
以判断该 4艮文中的 profile TD与该 TC设备的 profile TD是否匹配。
在本实施例中,由于 TC设备的 profile ID只与组播^艮文的 profile ID匹 配, 因此中间 TC节点在对比 profile ID后会对组播 文的驻留时间进行处 理, 而直接透传单播^艮文。 当然, 如果在中间 TC节点的配置中明确要求对 非本设备的 TC报文进行处理, 那么在本实施例中 , 即使中间 TC节点在对 比 profile ID后发现该^艮文为不匹配的单播报文, 也会根据协议对报文的驻 留时间进行处理。 另外, 针对设备实施例而言, 可以在确定模块中配置上下文判断单元 和上下文确定模块, 以实现该 "上下文实现方案"。
确定模块包括上下文判断单元和上下文确定模块。 其中, 上下文判断 单元用于根据 PTP消息中的上下文信息,判断 PTP消息是否与本设备相关; 上下文确定单元用于在上下文判断单元得到判断结果为否时, 确定接收的 PTP报文为非本设备 PTP报文。
相应的, 转发模块可以包括第二转发单元或者第三转发单元, 其中, 备 PTP报文转发给 TC设备外的节点设备; 第三转发单元用于对非本设备 PTP 文进行正常的 PTP层处理,将处理后的非本设备 PTP ^艮文转发给 TC 设备外的节点设备。
可以理解的是, 上述实施例可以应用于不同的系统中, 例如 , GSM系 统中、 WCDMA系统中或长期演进 ( Long Term Evolution, LTE ) 系统中 , 或者, 应用于上述系统的混合组网系统中。
本领域普通技术人员可以理解: 实现上述方法实施例的全部或部分步 驟可以通过程序指令相关的硬件来完成, 前述的程序可以存储于一计算机 可读取存储介质中, 该程序在执行时, 执行包括上述方法实施例的步驟; 而前述的存储介质包括: ROM、 RAM, 磁碟或者光盘等各种可以存储程序
代码的介质。 最后应说明的是: 以上实施例仅用以说明本发明的技术方案 而非对其进行限制, 尽管参照较佳实施例对本发明进行了详细的说明, 本 领域的普通技术人员应当理解: 其依然可以对本发明的技术方案进行修改 或者等同替换, 而这些修改或者等同替换亦不能使修改后的技术方案脱离 本发明技术方案的精神和范围
Claims
1、 一种精确时间协议 文处理方法, 其特征在于, 包括:
时钟设备接收精确时间协议 PTP报文, 所述精确时间协议报文中携带 端到端的参数信息;
时钟设备根据所述端到端的参数信息, 确定接收的 PTP报文是否为非 本设备 PTP才艮文;
时钟设备在接收的 PTP报文为非本设备 PTP报文时, 将所述非本设备 PTP 艮文进行转发。
2、 根据权利要求 1所述的方法, 其特征在于, 所述时钟设备为普通时 钟 OC设备或边界时钟 BC设备,所述端到端的参数信息包括域编号和目的 地址;
所述时钟设备根据所述端到端的参数信息, 确定接收的 PTP报文是否 为非本设备 PTP ^艮文包括:
所述时钟设备判断所述域编号与自身配置的域编号是否相同; 若判断结果为不同, 确定所述接收的 PTP报文为非本设备 PTP报文; 或者,
所述时钟设备判断所述域编号与自身配置的域编号是否相同; 若判断结果为相同, 且所述时钟设备在组播模式下, 进一步判断所述 目的地址是否为所述时钟设备自身的组播地址;
若判断结果为所述目的地址不是所述时钟设备自身的组播地址时, 确 定所述接收的 PTP报文为非本设备 PTP报文;
或者,
所述时钟设备判断所述域编号与自身配置的域编号是否相同; 若判断结果为相同, 且所述时钟设备在单播模式下, 进一步判断所述 目的地址是否为所述时钟设备自身的端口地址;
若判断结果为所述目的地址不是所述时钟设备自身的端口地址时, 确 定所述接收的 PTP报文为非本设备 PTP报文。
3、根据权利要求 2所述的方法,其特征在于,所述将所述非本设备 PTP 报文进行转发包括:
4、 根据权利要求 1所述的方法, 其特征在于, 所述时钟设备为透明时 钟 TC设备, 所述端到端的参数信息包括域编号;
所述时钟设备根据所述端到端的参数信息, 确定接收的 PTP报文是否 为非本设备 PTP报文包括:
所述 TC设备判断所述域编号与所述 TC设备自身配置的域编号是否相 同;
若判断结果为不同, 确定所述接收的 PTP报文为非本设备 PTP报文; 若判断结果为相同, 确定所述接收的 ΡΤΡ ·¾文为本设备 ΡΤΡ ·¾文。
5、根据权利要求 4所述的方法,其特征在于,所述将所述非本设备 ΡΤΡ 报文进行转发包括:
所述 TC设备, 对所述非本设备 ΡΤΡ报文忽略 ΡΤΡ层的处理, 直接将 所述非本设备 ΡΤΡ 文转发给所述 TC设备外的节点设备;
或者,
所述 TC设备, 对所述非本设备 ΡΤΡ报文进行正常的 ΡΤΡ层处理, 将 处理后的所述非本设备 ΡΤΡ报文转发给所述 TC设备外的节点设备。
6、 根据权利要求 1所述的方法, 其特征在于, 所述时钟设备为 OC设 备或者 BC设备或者 TC设备, 所述端到端的参数信息包括目的地址;
所述时钟设备根据所述端到端的参数信息, 确定接收的 ΡΤΡ报文是否 为非本设备 ΡΤΡ ^艮文包括:
所述时钟设备判断所述目的地址是否为自身的端口地址;
若判断结果为所述目的地址不是自身的端口地址时, 所述时钟设备确 定接收的 PTP报文为非本设备 PTP报文。
7、 根据权利要求 6所述的方法, 其特征在于, 所述时钟设备判断所述 目的地址是否为自身的端口地址包括: 由所述时钟设备中的地址匹配装置 判断所述目的地址是否为自身的端口地址,
所述方法还包括:
若判断结果为所述目的地址是自身的端口地址时, 所述地址匹配装置 确定接收的 PTP报文为本设备 PTP报文,并将所述本设备 PTP报文转发给 所述时钟设备内的报文处理装置,以便所述报文处理装置对所述本设备 PTP 才艮文进行正常的 PTP层处理。
8、 根据权利要求 1所述的方法, 其特征在于, 所述时钟设备为普通时 钟 OC设备或边界时钟 BC设备或透明时钟 TC设备,所述 PTP ^艮文为主时 钟或从时钟发送的 PTP消息, 所述端到端的参数信息包括所述 PTP消息中 的上下文信息;
所述时钟设备根据所述端到端的参数信息, 确定接收到的 PTP报文是 否为非本设备 PTP报文, 包括:
所述时钟设备根据所述 PTP消息中的上下文信息 , 判断所述 PTP消息 是否与本设备相关。
9、 根据权利要求 8所述的方法, 其特征在于, 所述上下文信息为包含 上下文 ID 的类型长度值 TLV字段;
所述时钟设备根据所述 PTP消息中的上下文信息 , 判断所述 PTP消息 是否与本设备相关, 包括:
所述时钟设备判断所述 TLV字段中包含的上下文 ID是否与本设备配 置的上下文 ID相匹配, 如果是, 则判断所述 PTP消息与本设备相关。
10、 根据权利要求 8或 9所述的方法, 其特征在于, 对于 TC设备, 所 述将所述非本设备 PTP报文进行转发, 包括:
所述 TC设备, 对所述非本设备 PTP报文忽略 PTP层的处理, 直接将 所述非本设备 PTP 艮文转发给所述 TC设备外的节点设备; 或者,
所述 TC设备, 对所述非本设备 ΡΤΡ报文进行正常的 ΡΤΡ层处理, 将
11、 一种时钟设备, 其特征在于, 包括:
接收模块, 用于接收精确时间协议 ΡΤΡ报文, 所述 ΡΤΡ报文中携带端 到端的参数信息;
确定模块, 用于根据所述端到端的参数信息, 确定接收的 ΡΤΡ报文是 否为非本设备 ΡΤΡ报文;
转发模块, 用于在接收的 ΡΤΡ报文为非本设备 ΡΤΡ报文时, 将所述非 本设备 ΡΤΡ 文进行转发。
12、 根据权利要求 11所述的设备, 其特征在于, 所述时钟设备为普通 时钟 OC设备或边界时钟 BC设备,所述端到端的参数信息包括域编号和目 的地址;
所述确定模块包括第一判断单元和第一确定单元;
所述第一判断单元用于判断所述域编号与自身配置的域编号是否相 同; 所述第一确定单元用于在所述第一判断单元得到判断结果为不同时, 确定所述接收的 ΡΤΡ报文为非本设备 ΡΤΡ报文;
或者,
所述确定模块包括所述第一判断单元、 第二判断单元和第二确定单元; 所述第二判断单元用于在所述第一判断单元得到判断结果为相同, 且所述 时钟设备在组播模式下 , 进一步判断所述目的地址是否为所述时钟设备自 身的组播地址; 所述第二确定单元用于在所述第二判断单元得到判断结果 为所述目的地址不是所述时钟设备自身的组播地址时,确定所述接收的 ΡΤΡ 报文为非本设备 ΡΤΡ报文;
或者, 所述确定单元包括所述第一判断单元、 第三判断单元和第三确定单元; 所述第三判断单元用于在所述第一判断单元得到判断结果为相同, 且所述 时钟设备在单播模式下 , 进一步判断所述目的地址是否为所述时钟设备自 身的端口地址; 所述第三确定单元用于在所述第三判断单元得到判断结果 为所述目的地址不是所述时钟设备自身的端口地址时,确定所述接收的 PTP 报文为非本设备 PTP报文。
13、 根据权利要求 12所述的设备, 其特征在于,
所述转发模块包括第一转发单元, 所述第一转发单元用于对所述非本 设备 PTP报文忽略 PTP层的处理,直接将所述非本设备 PTP报文转发给所 述时钟设备外的节点设备。
14、 根据权利要求 11所述的设备, 其特征在于, 所述时钟设备为透明 时钟 TC设备, 所述端到端的参数信息包括域编号;
所述确定模块包括第四判断单元、 第四确定单元和第五确定单元; 所 述第四判断单元用于判断所述域编号与所述 TC设备自身配置的域编号是 否相同; 所述第四确定单元用于在所述第四判断单元得到判断结果为不同 时, 确定所述接收的 PTP报文为非本设备 PTP报文; 所述第五确定单元用 于在所述第四判断单元得到判断结果为相同时, 确定所述接收的 PTP >¾ 为本设备 PTP报文, 或者
所述时钟设备为 OC设备或者 BC设备或者 TC设备,所述 PTP报文为 主时钟或从时钟发送的 PTP消息, 所述端到端的参数信息包括所述 PTP消 息中的上下文信息;
所述确定模块包括上下文判断单元和上下文确定模块;
所述上下文判断单元用于 ^据所述 PTP消息中的上下文信息, 判断所 述 PTP消息是否与本设备相关; 时, 确定接收的 PTP报文为非本设备 PTP报文。
1 5、 根据权利要求 14所述的设备, 其特征在于,
所述转发模块包括第二转发单元或者第三转发单元;
直接将所述非本设备 PTP报文转发给所述 TC设备外的节点设备;
理, 将处理后的所述非本设备 PTP报文转发给所述 TC设备外的节点设备。
16、 根据权利要求 11所述的设备, 其特征在于, 所述时钟设备为 OC 设备或者 BC设备或者 TC设备, 所述端到端的参数信息包括目的地址; 所述确定模块包括第五判断单元和第六确定模块;
所述第五判断单元用于判断所述目的地址是否为自身的端口地址; 所述第六确定单元用于在所述第五判断单元得到判断结果为所述目的 地址不是自身的端口地址时 , 确定接收的 PTP报文为非本设备 PTP报文。
17、 根据权利要求 16所述的设备, 其特征在于, 所述接收模块、 确定 模块和转发模块位于所述时钟设备中的地址匹配装置中; 所述设备还包括 才艮文处理装置; 所述地址匹配装置还包括:
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| JP2012529112A JP5455138B2 (ja) | 2009-09-17 | 2010-09-15 | 高精度時間プロトコルメッセージを処理するための方法およびクロックデバイス |
| EP10816698.4A EP2472916B1 (en) | 2009-09-17 | 2010-09-15 | Method and clock device for processing precision time protocol message |
Applications Claiming Priority (4)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910093302 | 2009-09-17 | ||
| CN200910093302.7 | 2009-09-17 | ||
| CN201010107643.8 | 2010-01-25 | ||
| CN201010107643.8A CN102026364B (zh) | 2009-09-17 | 2010-01-25 | 精确时间协议报文处理方法和时钟设备 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2011032494A1 true WO2011032494A1 (zh) | 2011-03-24 |
Family
ID=43758111
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2010/076939 Ceased WO2011032494A1 (zh) | 2009-09-17 | 2010-09-15 | 精确时间协议报文处理方法和时钟设备 |
Country Status (4)
| Country | Link |
|---|---|
| EP (1) | EP2472916B1 (zh) |
| JP (1) | JP5455138B2 (zh) |
| CN (1) | CN102026364B (zh) |
| WO (1) | WO2011032494A1 (zh) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2013143112A1 (en) * | 2012-03-30 | 2013-10-03 | Telefonaktiebolaget L M Ericsson(Publ) | Method and system for robust precision time protocol synchronization |
| CN116076040A (zh) * | 2020-08-05 | 2023-05-05 | 诺基亚技术有限公司 | 用于移动用户设备的工作时钟确定 |
Families Citing this family (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP2487819B1 (en) * | 2011-02-10 | 2015-08-05 | Alcatel Lucent | Network element for a packet-switched network |
| CN102185686B (zh) * | 2011-05-16 | 2016-09-21 | 南京中兴软件有限责任公司 | 基于ieee 1588协议调整频率的方法及网络装置 |
| CN103428081A (zh) * | 2012-05-14 | 2013-12-04 | 中兴通讯股份有限公司 | 一种分组网络同步方法、装置及系统 |
| CN103428086B (zh) * | 2012-05-25 | 2016-08-03 | 北京东土科技股份有限公司 | 基于ptp协议的透明时钟被动端口选举方法及装置 |
| CN103078699B (zh) * | 2012-12-28 | 2015-08-05 | 华为技术有限公司 | 基于精密时间协议进行时间同步的方法和网络设备 |
| EP2976922B1 (en) * | 2013-03-19 | 2020-06-17 | Telefonaktiebolaget LM Ericsson (publ) | Providing packet synchronization in a virtual private network |
| CN103532970B (zh) * | 2013-10-23 | 2016-12-07 | 杭州华三通信技术有限公司 | 一种时间同步报文的传输方法和设备 |
| CN105103632B (zh) * | 2014-01-28 | 2019-02-12 | 华为技术有限公司 | 同步信号转发方法和用户设备 |
| US11228994B2 (en) | 2019-02-18 | 2022-01-18 | Qualcomm Incorporated | Wireless communication enhancements for transparent and boundary clocks |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080075217A1 (en) * | 2006-09-22 | 2008-03-27 | Ilnicki Slawomir K | Mechanism For Making Delay From Network Elements Transparent To IEEE 1588 Protocols |
| CN101217498A (zh) * | 2008-01-18 | 2008-07-09 | 北京科技大学 | 基于数据报文点点决策的自组织网络寻路方法 |
| CN101242230A (zh) * | 2007-02-05 | 2008-08-13 | 汤姆森许可贸易公司 | 时钟同步辅助设备以及关联的时钟同步设备 |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5469432A (en) * | 1993-08-26 | 1995-11-21 | Gat; Erann | High-speed digital communications network |
| US6982976B2 (en) * | 2000-08-11 | 2006-01-03 | Texas Instruments Incorporated | Datapipe routing bridge |
| JP2003143178A (ja) * | 2001-10-31 | 2003-05-16 | Fujitsu Ltd | デジタル伝送装置 |
| US7633870B2 (en) * | 2005-04-18 | 2009-12-15 | Symmetricom, Inc. | Network forwarding device and method that forward timing packets through the device with a constant delay |
| JP2009065579A (ja) * | 2007-09-10 | 2009-03-26 | Nec Corp | 時刻同期システム、時刻同期方法、ノード及びプログラム |
-
2010
- 2010-01-25 CN CN201010107643.8A patent/CN102026364B/zh not_active Expired - Fee Related
- 2010-09-15 EP EP10816698.4A patent/EP2472916B1/en active Active
- 2010-09-15 JP JP2012529112A patent/JP5455138B2/ja active Active
- 2010-09-15 WO PCT/CN2010/076939 patent/WO2011032494A1/zh not_active Ceased
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080075217A1 (en) * | 2006-09-22 | 2008-03-27 | Ilnicki Slawomir K | Mechanism For Making Delay From Network Elements Transparent To IEEE 1588 Protocols |
| CN101242230A (zh) * | 2007-02-05 | 2008-08-13 | 汤姆森许可贸易公司 | 时钟同步辅助设备以及关联的时钟同步设备 |
| CN101217498A (zh) * | 2008-01-18 | 2008-07-09 | 北京科技大学 | 基于数据报文点点决策的自组织网络寻路方法 |
Non-Patent Citations (1)
| Title |
|---|
| "IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems", IEEE, 24 July 2008 (2008-07-24), pages 6, XP008154794 * |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2013143112A1 (en) * | 2012-03-30 | 2013-10-03 | Telefonaktiebolaget L M Ericsson(Publ) | Method and system for robust precision time protocol synchronization |
| US9690674B2 (en) | 2012-03-30 | 2017-06-27 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and system for robust precision time protocol synchronization |
| CN116076040A (zh) * | 2020-08-05 | 2023-05-05 | 诺基亚技术有限公司 | 用于移动用户设备的工作时钟确定 |
| US12431998B2 (en) | 2020-08-05 | 2025-09-30 | Nokia Technologies Oy | Working clock determination for a mobile user equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| EP2472916A1 (en) | 2012-07-04 |
| CN102026364A (zh) | 2011-04-20 |
| CN102026364B (zh) | 2014-07-09 |
| JP5455138B2 (ja) | 2014-03-26 |
| EP2472916A4 (en) | 2012-11-14 |
| EP2472916B1 (en) | 2016-02-17 |
| JP2013509744A (ja) | 2013-03-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2011032494A1 (zh) | 精确时间协议报文处理方法和时钟设备 | |
| US11695491B2 (en) | 5G system support for conveying TSN time synchronization | |
| US12445897B2 (en) | Communication method, apparatus, and computer-readable storage medium | |
| CN111436113B (zh) | 支持时钟同步的方法及通信设备 | |
| CN102013931B (zh) | 时间同步方法及系统、从属定时设备及主定时设备 | |
| WO2019223466A1 (zh) | 通信的方法和设备 | |
| WO2014117489A1 (zh) | 时钟同步方法及设备 | |
| WO2022021243A1 (zh) | 一种应对链路异常的授时方法和装置 | |
| CN103404226A (zh) | 一种传输数据的方法及设备 | |
| WO2012068844A1 (zh) | 一种主从时钟设备的时钟同步方法及系统 | |
| US11877251B2 (en) | Time synchronization method, electronic device and storage medium | |
| CN102006660B (zh) | 一种时间同步的方法和系统 | |
| CN102036361A (zh) | 时钟源选择的处理方法、装置和系统 | |
| US20220217505A1 (en) | Message transmission method and apparatus | |
| WO2015131350A1 (zh) | 时钟同步方法、设备及通信系统 | |
| WO2014082414A1 (zh) | 业务转发的方法及设备 | |
| WO2020103540A1 (zh) | 同步的方法和装置 | |
| WO2022027666A1 (zh) | 一种时间同步方法及装置 | |
| CN114827056B (zh) | 基于5g移动通信中时间敏感网络传输的系统及方法 | |
| WO2024027633A1 (zh) | 一种业务流属性配置方法、装置和系统 | |
| WO2013097754A1 (zh) | 一种空口数据同步处理的方法和装置 | |
| WO2010102565A1 (zh) | 时间同步的方法、装置和系统 | |
| WO2016138747A1 (zh) | 一种信息同步的方法及装置 | |
| EP2707976B1 (en) | Time synchronisation in a communication network | |
| CN117675066A (zh) | 一种时间同步方法及装置、通信设备 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 10816698 Country of ref document: EP Kind code of ref document: A1 |
|
| WWE | Wipo information: entry into national phase |
Ref document number: 2012529112 Country of ref document: JP |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| WWE | Wipo information: entry into national phase |
Ref document number: 2010816698 Country of ref document: EP |