WO2023213159A1

WO2023213159A1 - Communication method and apparatus

Info

Publication number: WO2023213159A1
Application number: PCT/CN2023/084904
Authority: WO
Inventors: 王亚鑫; 孙海洋; 余芳
Original assignee: 华为技术有限公司
Priority date: 2022-05-06
Filing date: 2023-03-29
Publication date: 2023-11-09
Also published as: CN117062207A

Abstract

A communication method and apparatus, by means of which a clock domain having an abnormal clock synchronization state can be accurately determined. The method comprises: receiving first clock state information from a first device; receiving second clock state information from a second device; and according to the first clock state information and the second clock state information, determining, from an internal clock domain of a communication system and a precision time protocol clock domain, a clock domain which has an abnormal clock synchronization state, wherein the first clock state information is used for indicating a clock synchronization state of the precision time protocol clock domain, the second clock state information is used for indicating a clock synchronization state of the precision time protocol clock domain, and the first device and the second device both support the acquisition of synchronization information corresponding to the internal clock domain of the communication system, and synchronization information corresponding to the precision time protocol clock domain; and the first device is a network-side adapter, and the second device is a device-side adapter; or the first device is a user plane network element, and the second device is a first terminal device.

Description

Communication methods and devices

This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on May 6, 2022, with application number 202210488539.0 and application title "Communication Method and Device", the entire content of which is incorporated into this application by reference.

Technical field

The present application relates to the field of communication, and in particular, to a communication method and device.

Background technique

The time sensitive network (TSN) system uses the (generalized) precision time protocol (g)PTP clock domain, and the mobile communication system uses the internal clock domain of the communication system.

In the scenario where the time-sensitive network system and the mobile communication system are integrated, the time-sensitive network system can send the synchronization information corresponding to (g)PTP to the end device (the device that needs to connect to the time-sensitive network) through the mobile communication system, so that the end device Perform time synchronization. Since the process of transmitting synchronization information through the mobile communication system will generate dwell time in the nodes of the mobile communication system, the nodes in the mobile communication system can use the clock corresponding to the internal clock domain of the communication system to determine the dwell time and send it to the terminal. equipment, so that the end equipment uses this dwell time for clock correction. In this way, the terminal device can obtain the clock corresponding to the precise time protocol clock domain based on the synchronization information and the dwell time, and perform clock synchronization based on the clock corresponding to the time protocol clock domain.

However, when the terminal device detects that the deviation between the clock corresponding to the obtained precision time protocol clock domain and the clock corresponding to the local precision time protocol clock domain of the terminal device is too large, and determines that the clock synchronization status of the precision time protocol clock domain is abnormal, it cannot be determined. Is the abnormality in the clock synchronization state of the precision time protocol clock domain caused by problems with the synchronization information itself, or is it caused by the abnormality in the synchronization state of the clock domain within the communication system that causes problems with the dwell time.

In other words, how to accurately determine the clock domain in which the clock synchronization status is abnormal has become an urgent problem to be solved.

Contents of the invention

Embodiments of the present application provide a communication method and device that can accurately determine the clock domain in which the clock synchronization state is abnormal.

In order to achieve the above purpose, this application adopts the following technical solutions:

In the first aspect, a communication method is provided, which is applied to the first core network element. The communication method includes: receiving first clock status information from a first device, receiving second clock status information from a second device, and according to the first clock status information and the second clock status information, from the internal clock domain of the communication system and accurately In the time protocol clock domain, determine the clock domain in which the clock synchronization status is abnormal. The first clock status information is used to indicate the clock synchronization status of the precise time protocol clock domain. The second clock status information is used to indicate the clock synchronization status of the precise time protocol clock domain. Both the first device and the second device support obtaining synchronization information corresponding to the internal clock domain of the communication system and synchronization information corresponding to the precise time protocol clock domain. The first device is a network-side adapter, and the second device is a device side adapter. Alternatively, the first device is a user plane network element, and the second device is a first terminal device.

Based on the method provided in the first aspect, both the first device and the second device support obtaining synchronization information corresponding to the internal clock domain of the communication system and synchronization information corresponding to the precise time protocol clock domain. When the first device is a network side adapter, the second device The second device is the device side adapter. Or, when the first device is a user plane network element, the second device is the first terminal device. The first device and the second device respectively send first clock status information and second clock status information to the first core network element. The first clock status information indicates the clock synchronization status of the precise time protocol clock domain, and the second clock status information Indicates the clock synchronization status of the Precision Time Protocol clock domain. According to the different transmission directions of the synchronization information corresponding to the precise time protocol clock domain, there will always be one clock status information in the first clock status information and the second clock status information. The result indicated by the clock status information is affected by the clock synchronization status of the internal clock domain of the communication system. , In this way, the core network element can accurately determine the clock domain in which the clock synchronization status is abnormal from the internal clock domain of the communication system and the precise time protocol clock domain based on the first clock status information and the second clock status information.

In a possible design approach, the clock domain port state of the first device is the slave clock state, and the clock domain port state of the second device is the master clock state. According to the first clock state information and the second clock state information, the slave clock state is Among the internal clock domains of the communication system and the precision time protocol clock domain, determining the clock domain in which the clock synchronization status is abnormal may include: if the first clock status information indicates that the clock synchronization status of the precision time protocol clock domain is not abnormal, and the second clock status If the information indicates that the clock synchronization status of the precise time protocol clock domain is abnormal, it is determined that the clock synchronization status of the internal clock domain of the communication system is abnormal. Alternatively, if the first clock status information indicates that the clock synchronization status of the precision time protocol clock domain is abnormal, it is determined that the clock synchronization status of the precision time protocol clock domain is abnormal.

In this way, in a scenario where the first device receives the synchronization information of the precise time protocol clock domain and sends the synchronization information to the second device through the mobile communication system, the clock domain in which the clock synchronization status is abnormal can be accurately determined.

In a possible design approach, the clock domain port state of the second device is the slave clock state, and the clock domain port state of the first device is the master clock state. According to the first clock state information and the second clock state information, the slave clock state is Among the internal clock domains of the communication system and the precision time protocol clock domain, determining the clock domain in which the clock synchronization status is abnormal may include: if the second clock status information indicates that the clock synchronization status of the precision time protocol clock domain is not abnormal, and the first clock status If the information indicates that the clock synchronization status of the precise time protocol clock domain is abnormal, it is determined that the clock synchronization status of the internal clock domain of the communication system is abnormal. Alternatively, if the second clock status information indicates that the clock synchronization status of the precision time protocol clock domain is abnormal, it is determined that the clock synchronization status of the precision time protocol clock domain is abnormal.

In this way, in a scenario where the second device receives the synchronization information of the precise time protocol clock domain and sends the synchronization information to the first device through the mobile communication system, the clock domain in which the clock synchronization status is abnormal can be accurately determined.

In a possible design approach, the communication method provided in the first aspect may further include: obtaining information about the first access network device when the clock synchronization state of the internal clock domain of the communication system is abnormal. Wherein, the first access network device is an access network device corresponding to the internal clock domain of the communication system. In this way, information about access network equipment with abnormal clock synchronization status can be obtained.

In a possible design manner, the above-mentioned obtaining the information of the first access network device may include: sending a first request message to the mobility management network element, and receiving the first request message from the mobility management network element of the first access network device. information. The first request message may include the identification of the terminal device corresponding to the device-side adapter or the identification of the first terminal device, and the first request message may be used to request access to the terminal device corresponding to the device-side adapter or the first terminal device. access network equipment information. The first access network device is a terminal device corresponding to the device-side adapter or an access network device connected to the first terminal device. In this way, the first core network element can request information about the first access network device from the mobility management network element.

In a possible design approach, the first core network element is a delay clock network element. The above-mentioned obtaining the information of the first access network device may include: sending a second request message to the session management network element, receiving the information from Information about the first access network device of the session management network element. The second request message may include an identifier of the first terminal device or a port identifier of the device-side adapter, and the second request message may be used to request an access network device to which the first terminal device or the terminal device corresponding to the device-side adapter accesses. Information. The first access network device is an access network device connected to the first terminal device or the terminal device corresponding to the device-side adapter. In this way, the first core network element can request the information of the first access network device from the session management network element.

In a possible design approach, the first core network element is a session management network element. The above-mentioned obtaining the information of the first access network device may include: based on the identification of the first terminal device or the port identification of the device-side adapter. , obtain information about the first access network device. The first access network device is an access network device to which the first terminal device or the terminal device corresponding to the device-side adapter is connected. In this way, the session management network element can obtain the information of the first access network device.

In a possible design manner, the communication method provided in the first aspect may further include: receiving a clock status notification request from the application network element. The clock status notification request may include the identification of the second terminal device, and the clock status notification request may be used to request the clock synchronization status of the second terminal device. In this way, the application network element can request to monitor the clock synchronization status of the second terminal device.

Optionally, the number of second terminal devices may be one or more.

In a possible design manner, the communication method provided in the first aspect may further include: sending the first clock abnormality information to the second terminal device according to the identification of the second terminal device. The first clock abnormality information may be used to indicate a clock domain in which the clock synchronization state is abnormal, and the access network device accessed by the second terminal device is the first access network device.

In this way, the first terminal device can obtain that the clock synchronization status of the internal clock domain of the communication system is abnormal, and can stop using the clock of the internal clock domain of the communication system.

In a possible design manner, the communication method provided in the first aspect may further include: sending a first clock status request to the first device. The first clock status request may include an identification of the Precision Time Protocol clock domain, and the first clock status request may be used to request the clock synchronization status of the Precision Time Protocol clock domain.

In a possible design manner, the communication method provided in the first aspect may further include: sending a second clock status request to the second device. The second clock status request may include an identification of the Precision Time Protocol clock domain, and the second clock status request may be used to request the clock synchronization status of the Precision Time Protocol clock domain.

In a possible design manner, the first clock status information may include: whether the clock synchronization status of the Precision Time Protocol clock domain is abnormal and/or the Precision Time Protocol clock domain deviation. The precision time protocol clock domain deviation is the difference between the clock corresponding to the precision time protocol clock domain on the first device side and the first clock. The first clock is the clock indicated by the synchronization information corresponding to the precision time protocol clock domain.

In this way, the clock synchronization status of the precise time protocol clock domain can be indicated explicitly or implicitly through the first clock status information.

In a possible design approach, the first clock status information may also include: communication system internal clock domain Whether the information of the corresponding first access network device and/or the clock synchronization status of the internal clock domain of the communication system is abnormal.

In a possible design manner, the second clock status information may include: whether the clock synchronization status of the Precision Time Protocol clock domain is abnormal and/or the Precision Time Protocol clock domain deviation. The precision time protocol clock domain deviation is the difference between the clock corresponding to the precision time protocol clock domain on the second device side and the first clock. The first clock is the clock indicated by the synchronization information corresponding to the precision time protocol clock domain.

In a possible design manner, the second clock status information also includes: information about the first access network device corresponding to the internal clock domain of the communication system, and/or whether the clock synchronization status of the internal clock domain of the communication system is abnormal.

In the second aspect, a communication method is provided, which is applied to the first core network element. The communication method includes: receiving first clock status information from the first device; when the clock domain port status of the first device is in the main clock status, and the first clock status information indicates that the clock synchronization status of the precision time protocol clock domain is abnormal. In this case, request the first access network device for the clock synchronization status of the internal clock domain of the communication system, receive the clock synchronization status of the internal clock domain of the communication system from the first access network device, and based on the clock synchronization status of the internal clock domain of the communication system , determine the clock domain in which the clock synchronization status is abnormal from the internal clock domain of the communication system and the precise time protocol clock domain. The first clock status information is used to indicate the clock synchronization status of the Precision Time Protocol clock domain, and the first device supports obtaining synchronization information corresponding to the internal clock domain of the communication system and synchronization information corresponding to the Precision Time Protocol clock domain.

Based on the communication method provided in the second aspect, when the clock domain port status of the first device is in the main clock status, and the first clock status information indicates that the clock synchronization status of the precise time protocol clock domain is abnormal, the clock domain port status of the first device can be passed to the first device. The access network device requests the clock synchronization status of the internal clock domain of the communication system, and determines which clock domain among the precise time protocol clock domain and the internal clock domain of the communication system has an abnormal clock synchronization status based on the clock synchronization status of the internal clock domain of the communication system. . In this way, the clock domain in which the clock synchronization status is abnormal can be accurately determined.

In a possible design method, the above-mentioned method determines the clock domain in which the clock synchronization status is abnormal from the internal clock domain of the communication system and the precise time protocol clock domain based on the clock synchronization status of the internal clock domain of the communication system, which may include: If the communication system If there is no abnormality in the clock synchronization status of the internal clock domain of the system, it is determined that the clock synchronization status of the precise time protocol clock domain is abnormal.

In a possible design method, the above-mentioned method determines the clock domain in which the clock synchronization status is abnormal from the internal clock domain of the communication system and the precise time protocol clock domain based on the clock synchronization status of the internal clock domain of the communication system, which may include: If the communication system If the clock synchronization status of the internal clock domain of the system is abnormal, it is determined that the clock synchronization status of the internal clock domain of the communication system is abnormal.

In a possible design approach, the communication method provided in the second aspect may further include: obtaining information about the first access network device when the clock synchronization state of the internal clock domain of the communication system is abnormal. Wherein, the first access network device is an access network device corresponding to the internal clock domain of the communication system.

In a possible design manner, the above-mentioned obtaining the information of the first access network device may include: sending a first request message to the mobility management network element, and receiving the first request message from the mobility management network element of the first access network device. information. The first request message may include the identification of the terminal device corresponding to the device-side adapter or the identification of the first terminal device, and the first request message may be used to request access to the terminal device corresponding to the device-side adapter or the first terminal device. Network device information. The first access network device is a terminal device corresponding to the device-side adapter or an access network device connected to the first terminal device.

In a possible design manner, the above-mentioned obtaining the information of the first access network device may include: sending a second request message to the session management network element, and receiving the information of the first access network device from the session management network element. The second request message may include an identifier of the first terminal device or a port identifier of the device-side adapter, and the second request message may be used to request an access network device to which the first terminal device or the terminal device corresponding to the device-side adapter accesses. Information. The first access network device is an access network device connected to the first terminal device or the terminal device corresponding to the device-side adapter.

In a possible design manner, the communication method provided in the second aspect may further include: receiving a clock status notification request from the application network element. The clock status notification request may include the identification of the second terminal device, and the clock status notification request may be used to request the clock synchronization status of the second terminal device.

In a possible design manner, the communication method provided in the second aspect may further include: sending the first clock abnormality information to the second terminal device according to the identification of the second terminal device. The first clock abnormality information may be used to indicate a clock domain in which the clock synchronization state is abnormal, and the access network device accessed by the second terminal device is the first access network device.

In a possible design manner, the communication method provided in the second aspect may further include: sending a first clock status request to the first device. The first clock status request may include an identification of the Precision Time Protocol clock domain, and the first clock status request may be used to request the clock synchronization status of the Precision Time Protocol clock domain.

In a possible design manner, the communication method provided in the second aspect may further include: sending a second clock status request to the second device. The second clock status request may include an identification of the Precision Time Protocol clock domain, and the second clock status request may be used to request the clock synchronization status of the Precision Time Protocol clock domain.

In a possible design manner, the first clock status information may also include: information about the first access network device corresponding to the internal clock domain of the communication system, and/or whether the clock synchronization status of the internal clock domain of the communication system is abnormal.

In a possible design manner, the second clock status information may also include: information about the first access network device corresponding to the internal clock domain of the communication system, and/or whether the clock synchronization status of the internal clock domain of the communication system is abnormal.

In addition, the technical effects of the communication method described in the second aspect can be referred to the technical effects of the communication method described in any possible implementation manner in the first aspect, which will not be described again here.

In a third aspect, a communication method is provided, which is applied to communication equipment. The communication method includes: receiving a first clock status request from a first core network element, and sending first clock status information to the first core network element. The first clock status request includes an identification of the Precision Time Protocol clock domain, and the first clock status request is used to request the clock synchronization status of the Precision Time Protocol clock domain. The first clock status information includes: whether the clock synchronization status of the precision time protocol clock domain is abnormal and/or the precision time protocol clock domain deviation. The precision time protocol clock domain deviation is the difference between the clock corresponding to the precision time protocol clock domain on the communication device side and the first clock status information. The difference between one clock and the first clock for communication The device receives the clock indicated by the synchronization information corresponding to the Precision Time Protocol clock domain.

In a possible design approach, the first clock status information includes whether the clock synchronization status of the precision time protocol clock domain is abnormal. The communication method provided in the third aspect may further include: determining the first clock status based on the precision time protocol clock domain deviation. Clock status information.

In a possible design approach, determining the first clock status information based on the precision time protocol clock domain deviation may include: the precision time protocol clock domain deviation is greater than the first threshold, then the first clock status information indicates the precision time protocol clock The synchronization status of the domain is abnormal. Alternatively, if the precision time protocol clock domain deviation is less than or equal to the first threshold, then the first clock status information indicates that the synchronization status of the precision time protocol clock domain is normal.

In a possible design approach, the first clock status information also includes whether the clock synchronization status of the internal clock domain of the communication system is abnormal. The communication method provided in the third aspect may also include: determining the first clock status based on the internal clock domain deviation of the communication system. A clock status information. The communication system internal clock domain deviation is the difference between the clock corresponding to the communication system internal clock domain on the communication device side and the second clock. The second clock is indicated by the synchronization information corresponding to the communication system internal clock domain received by the communication device. clock.

In a possible design manner, the first clock status information may also include: information of the first access network device corresponding to the internal clock domain of the communication system.

In a possible design manner, the communication device may be a network side adapter, a device side adapter, a user plane network element, or a first terminal device.

For the technical effects of the communication method described in the third aspect, reference can be made to the technical effects of the communication method described in any possible implementation manner of the first aspect, which will not be described again here.

A fourth aspect provides a communication device. The communication device includes: a transceiver module and a processing module. Wherein, the transceiver module is used to receive the first clock status information from the first device. The first clock status information is used to indicate the clock synchronization status of the precise time protocol clock domain. The transceiver module is also used to receive the second clock status information from the second device. The second clock status information is used to indicate the clock synchronization status of the precise time protocol clock domain. Both the first device and the second device support obtaining synchronization information corresponding to the internal clock domain of the communication system and synchronization information corresponding to the precise time protocol clock domain. The first device is a network-side adapter and the second device is a device-side adapter. Alternatively, the first device is a user plane network element, and the second device is a first terminal device. The processing module is configured to determine, based on the first clock status information and the second clock status information, the clock domain in which the clock synchronization state is abnormal from the internal clock domain of the communication system and the precise time protocol clock domain.

In a possible design method, the clock domain port status of the first device is the slave clock status, and the clock domain port status of the second device is the master clock status. The processing module is also used to determine if the first clock status information indicates the precise time. If there is no abnormality in the clock synchronization status of the protocol clock domain, and the second clock status information indicates that the clock synchronization status of the precise time protocol clock domain is abnormal, it is determined that the clock synchronization status of the internal clock domain of the communication system is abnormal. Alternatively, the processing module is further configured to determine that the clock synchronization status of the precision time protocol clock domain is abnormal if the first clock status information indicates that the clock synchronization status of the precision time protocol clock domain is abnormal.

In a possible design method, the clock domain port status of the second device is the slave clock status, and the clock domain port status of the first device is the master clock status. The processing module is also used to determine if the second clock status information indicates the precise time. If there is no abnormality in the clock synchronization status of the protocol clock domain, and the first clock status information indicates that the clock synchronization status of the precise time protocol clock domain is abnormal, it is determined that the clock synchronization status of the internal clock domain of the communication system is abnormal. Alternatively, the processing module is also configured to: if the second clock status information indicates the clock synchronization status of the precise time protocol clock domain Abnormal, it is determined that the clock synchronization status of the precise time protocol clock domain is abnormal.

In a possible design approach, the processing module is also used to obtain information about the first access network device when the clock synchronization state of the internal clock domain of the communication system is abnormal. Wherein, the first access network device is an access network device corresponding to the internal clock domain of the communication system.

In a possible design manner, the transceiver module is also used to send the first request message to the mobility management network element. The first request message may include the identification of the terminal device corresponding to the device-side adapter or the identification of the first terminal device, and the first request message may be used to request access to the terminal device corresponding to the device-side adapter or the first terminal device. Network device information. The transceiver module is also used to receive information from the first access network device of the mobility management network element. The first access network device is a terminal device corresponding to a device-side adapter or an access network device to which the first terminal device is connected.

In a possible design manner, the communication device is a delay clock network element, a transceiver module, and is also used to send the second request message to the session management network element. The second request message may include an identifier of the first terminal device or a port identifier of the device-side adapter, and the second request message may be used to request an access network device to which the first terminal device or the terminal device corresponding to the device-side adapter accesses. Information. The transceiver module is also configured to receive information from the first access network device of the session management network element. The first access network device is an access network device to which the terminal device corresponding to the first terminal device or the device-side adapter is connected.

In a possible design manner, the communication device is a session management network element, and the processing module is further configured to obtain information about the first access network device according to the identifier of the first terminal device or the port identifier of the device-side adapter. The first access network device is an access network device to which the first terminal device or the terminal device corresponding to the device-side adapter is connected.

In a possible design approach, the transceiver module is also used to receive clock status notification requests from application network elements. The clock status notification request may include the identification of the second terminal device, and the clock status notification request may be used to request the clock synchronization status of the second terminal device.

In a possible design manner, the transceiver module is also configured to send the first clock abnormality information to the second terminal device according to the identifier of the second terminal device. The first clock abnormality information may be used to indicate a clock domain in which the clock synchronization state is abnormal, and the access network device accessed by the second terminal device is the first access network device.

In a possible design manner, the transceiver module is also used to send a first clock status request to the first device. The first clock status request may include an identification of the Precision Time Protocol clock domain, and the first clock status request may be used to request the clock synchronization status of the Precision Time Protocol clock domain.

In a possible design manner, the transceiver module is also used to send a second clock status request to the second device. The second clock status request may include an identification of the Precision Time Protocol clock domain, and the second clock status request may be used to request the clock synchronization status of the Precision Time Protocol clock domain.

In a possible design manner, the second clock status information may include: whether the clock synchronization status of the Precision Time Protocol clock domain is abnormal and/or the Precision Time Protocol clock domain deviation. The precision time protocol clock domain deviation is The difference between the clock corresponding to the precise time protocol clock domain on the second device side and the first clock, where the first clock is the clock indicated by the synchronization information corresponding to the precise time protocol clock domain.

It should be noted that the transceiver module described in the fourth aspect may include a receiving module and a sending module. This application does not specifically limit the specific implementation of the transceiver module.

Optionally, the communication device described in the fourth aspect may further include a storage module that stores programs or instructions. When the processing module executes the program or instruction, the communication device described in the fourth aspect can perform the method described in the first aspect.

It should be noted that the communication device described in the fourth aspect may be a first core network element, such as a delay clock network element or a session management network element, or it may be a chip that can be disposed in the first core network element. (system) or other components or components, this application does not limit this.

The technical effects of the communication device described in the fourth aspect may be referred to the technical effects of the communication method described in any possible implementation manner in the first aspect, and will not be described again here.

In a fifth aspect, a communication device is provided. The communication device includes: a transceiver module and a processing module. Wherein, the transceiver module is used to receive the first clock status information from the first device. The first clock status information is used to indicate the clock synchronization status of the Precision Time Protocol clock domain, and the first device supports obtaining synchronization information corresponding to the internal clock domain of the communication system and synchronization information corresponding to the Precision Time Protocol clock domain.

The transceiver module is also configured to request the first access network device when the clock domain port status of the first device is in the main clock state and the first clock status information indicates that the clock synchronization status of the precise time protocol clock domain is abnormal. Clock synchronization status of the internal clock domain of the communication system.

The transceiver module is also configured to receive the clock synchronization status of the internal clock domain of the communication system from the first access network device.

The processing module is used to determine, based on the clock synchronization status of the internal clock domain of the communication system, the clock domain in which the clock synchronization status is abnormal from the internal clock domain of the communication system and the precise time protocol clock domain.

In a possible design approach, the processing module is also used to determine that the clock synchronization status of the precise time protocol clock domain is abnormal if there is no abnormality in the clock synchronization status of the internal clock domain of the communication system.

In a possible design method, the processing module is also used to determine that the clock synchronization status of the internal clock domain of the communication system is abnormal if the clock synchronization status of the internal clock domain of the communication system is abnormal.

In a possible design manner, the transceiver module is also used to send the first request message to the mobility management network element. The first request message may include the identification of the terminal device corresponding to the device-side adapter or the identification of the first terminal device, and the first request message may be used to request access to the terminal device corresponding to the device-side adapter or the first terminal device. Network device information.

The transceiver module is also used to receive information from the first access network device of the mobility management network element. The first access network device is a terminal device corresponding to a device-side adapter or an access network device to which the first terminal device is connected.

In a possible design manner, the transceiver module is also used to send a second request message to the session management network element. The second request message may include an identifier of the first terminal device or a port identifier of the device-side adapter, and the second request message may be used to request an access network device to which the first terminal device or the terminal device corresponding to the device-side adapter accesses. Information. The transceiver module is also configured to receive information from the first access network device of the session management network element. The first access network device is an access network device to which the terminal device corresponding to the first terminal device or the device-side adapter is connected.

It should be noted that the transceiver module described in the fifth aspect may include a receiving module and a sending module. This application does not specifically limit the specific implementation of the transceiver module.

Optionally, the communication device according to the fifth aspect may further include a storage module that stores programs or instructions. When the processing module executes the program or instruction, the communication device described in the fifth aspect can perform the method described in the second aspect.

It should be noted that the communication device described in the fifth aspect may be a first core network element, such as a delay clock network element, or may be a chip (system) or other that can be disposed in the first core network element. Parts or components are not limited in this application.

The technical effects of the communication device described in the fifth aspect can be referred to the technical effects of the communication method described in any possible implementation manner in the second aspect, and will not be described again here.

A sixth aspect provides a communication device. The communication device includes: a sending module and a receiving module. Wherein, the receiving module is used to receive the first clock status request from the first core network element. The first clock status request includes an identification of the Precision Time Protocol clock domain, and the first clock status request is used to request the clock synchronization status of the Precision Time Protocol clock domain.

The sending module is configured to send the first clock status information to the first core network element. The first clock status information includes: whether the clock synchronization status of the precision time protocol clock domain is abnormal and/or the precision time protocol clock domain deviation, and the precision time protocol clock domain deviation is the clock corresponding to the precision time protocol clock domain on the communication device side The difference between the first clock and the first clock is the clock indicated by the synchronization information corresponding to the precise time protocol clock domain received by the communication device.

In a possible design manner, the first clock status information includes whether the clock synchronization status of the precise time protocol clock domain is abnormal, and the communication device further includes a processing module. The processing module is used to determine the first clock status information according to the precision time protocol clock domain deviation.

In a possible design manner, the processing module is also configured to: if the precision time protocol clock domain deviation is greater than the first threshold, the first clock status information indicates that the synchronization status of the precision time protocol clock domain is abnormal. Alternatively, the processing module is also configured to configure the precision time protocol clock domain deviation to be less than or equal to the first threshold, and then the first clock status information indicates that there is no abnormality in the synchronization status of the precision time protocol clock domain.

In a possible design approach, the first clock status information also includes whether the clock synchronization status of the internal clock domain of the communication system is abnormal, and the processing module is also configured to determine the first clock status information based on the internal clock domain deviation of the communication system. The communication system internal clock domain deviation is the difference between the clock corresponding to the communication system internal clock domain on the communication device side and the second clock. The second clock is indicated by the synchronization information corresponding to the communication system internal clock domain received by the communication device. clock.

It should be noted that the receiving module and the sending module can be set up separately, or they can be integrated into one module, that is, the sending and receiving module. This application does not specifically limit the specific implementation methods of the receiving module and the sending module.

Optionally, the communication device according to the sixth aspect may further include a storage module that stores programs or instructions. When the processing module executes the program or instruction, the communication device described in the sixth aspect can perform the method described in the third aspect.

It should be noted that the communication device described in the sixth aspect may be a network side adapter, a device side adapter, a user plane network element, or a first terminal device, or may be disposed on a network side adapter, a device side adapter, a user plane network element, or a first terminal device. The network element, or the chip (system) or other components or components of the first terminal device is not limited in this application.

The technical effects of the communication device described in the sixth aspect can be referred to the technical effects of the communication method described in any possible implementation manner in the third aspect, and will not be described again here.

In a seventh aspect, a communication device is provided. The communication device includes a processor coupled to a memory for storing a computer program.

The processor is configured to execute a computer program stored in the memory, so that the method described in any possible implementation manner of the first to third aspects is executed.

In a possible design, the communication device described in the seventh aspect may further include a transceiver. The transceiver can be a transceiver circuit or an input/output port. The transceiver may be used for the communication device to communicate with other devices.

It should be noted that the input port can be used to implement the receiving functions involved in the first to third aspects, and the output port can be used to implement the sending functions involved in the first to third aspects.

In this application, the communication device described in the seventh aspect may be the first core network element or communication equipment, or a chip or chip system provided inside the first core network element or communication equipment. The first core network element may be a delay clock network element or a session management network element, and the communication device may be a network side adapter, a device side adapter, a user plane network element, or a first terminal device.

In addition, the technical effects of the communication device described in the seventh aspect can be referred to the technical effects of the method described in any implementation manner of the first aspect, which will not be described again here.

An eighth aspect provides a communication system. The communication system includes a first core network element, a first device and a second device. Wherein, the first core network element is used to implement the method described in the first aspect. The first device is used to implement the method described in the third aspect. The second device is used to implement the method described in the third aspect.

Alternatively, the communication system includes a communication device as described in the fourth aspect for implementing the method as described in the first aspect, a communication device as described in the sixth aspect for implementing the method as described in the third aspect (communication device (being the first device), and the communication device as described in the sixth aspect for implementing the method as described in the third aspect (the communication device is the second device).

The first core network element may be: a delay clock network element, a session management network element, etc. The above-mentioned first device may be a network side adapter or a user plane network element. The second device may be a device-side adapter or the first terminal device.

Exemplarily, the communication system includes a delay clock network element, a network side adapter, and a device side adapter.

As another example, the communication system includes a session management network element, a user plane network element and a first terminal device.

Alternatively, the communication system includes a first core network element, a first device and a first access network device. Wherein, the first core network element is used to implement the method described in the first aspect. The first device is used to implement the method described in the third aspect. The first access network device is configured to receive a clock synchronization status request of the internal clock domain of the communication system from the first core network element, and is also configured to send the clock synchronization status of the internal clock domain of the communication system to the first core network element.

Alternatively, the communication system includes a communication device as described in the fifth aspect for implementing the method as described in the second aspect, a communication device as described in the sixth aspect for implementing the method as described in the third aspect (communication device is the first device), and the first access network device.

Exemplarily, the communication system includes a delay clock network element, a network side adapter, and a first access network device.

In a ninth aspect, a chip system is provided, the chip system including a logic circuit and an input/output port. Wherein, the logic circuit is used to implement the processing functions involved in the first aspect to the third aspect, and the input/output port is used to implement the transceiver functions involved in the first aspect to the third aspect. Specifically, the input port can be used to implement the receiving functions involved in the first to third aspects, and the output port can be used to implement the sending functions involved in the first to third aspects.

In a possible design, the chip system further includes a memory, which is used to store program instructions and data for implementing the functions involved in the first to third aspects.

The chip system may be composed of chips, or may include chips and other discrete devices.

In a tenth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program or instructions; when the computer program or instructions are run on a computer, the steps in the first to third aspects are achieved. The method described in any possible implementation is executed.

In an eleventh aspect, a computer program product is provided, including a computer program or instructions. When the computer program or instructions are run on a computer, the method described in any one of the possible implementations of the first to third aspects is achieved. be executed.

Description of the drawings

Figure 1 is a schematic architectural diagram of a communication system provided by an embodiment of the present application;

Figure 2 is a schematic diagram of a network architecture provided by an embodiment of the present application;

Figure 3 is a topological diagram of a transmission path of a clock synchronization signal provided by an embodiment of the present application;

Figure 4 is a schematic diagram of the integration of a time-sensitive network system and a mobile communication system provided by an embodiment of the present application;

Figure 5 is a schematic diagram of a transmission path provided by an embodiment of the present application;

Figure 6 is a schematic flow chart of a communication method provided by an embodiment of the present application;

Figure 7 is a schematic flow chart of another communication method provided by an embodiment of the present application;

Figure 8 is a schematic flow chart of another communication method provided by an embodiment of the present application;

Figure 9 is a schematic structural diagram of a communication device provided by an embodiment of the present application;

Figure 10 is a schematic structural diagram of another communication device provided by an embodiment of the present application;

Figure 11 is a schematic structural diagram of another communication device provided by an embodiment of the present application.

Detailed ways

The technical solutions in this application will be described below with reference to the accompanying drawings.

The technical solutions of the embodiments of the present application can be applied to various communication systems, such as universal mobile telecommunications system (UMTS), wireless local area network (WLAN), wireless fidelity (wireless fidelity, Wi-Fi) ) system, wired network, vehicle to everything (V2X) communication system, device-to-device (D2D) communication system, Internet of Vehicles communication system, 4th generation (4G) mobile communication Systems, such as long term evolution (LTE) systems, worldwide interoperability for microwave access (WiMAX) communication systems, fifth generation (5th generation, 5G) mobile communication systems, such as new radio , NR) system, as well as future communication systems, such as the sixth generation (6th generation, 6G) mobile communication system.

This application will present various aspects, embodiments, or features in terms of systems, which may include multiple devices, components, modules, etc. It should be understood and appreciated that various systems may include additional devices, components, modules, etc., and/or may not include all devices, components, modules, etc. discussed in connection with the figures. Additionally, a combination of these scenarios can be used.

In addition, in the embodiments of this application, words such as "exemplarily" and "for example" are used to represent examples, illustrations or explanations. Any embodiment or design described herein as "example" is not intended to be construed as preferred or advantageous over other embodiments or designs. Rather, the use of the word example is intended to present a concept in a concrete way.

In the embodiments of this application, "of", "corresponding, relevant" and "corresponding" can sometimes be used interchangeably. It should be noted that when the difference is not emphasized, the intended expression The meaning is consistent.

The network architecture and business scenarios described in the embodiments of this application are for the purpose of explaining the technical solutions of the embodiments of this application more clearly, and do not constitute a limitation on the technical solutions provided by the embodiments of this application. Those of ordinary skill in the art It can be known that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

In order to facilitate understanding of the embodiments of the present application, a communication system applicable to the embodiments of the present application is first described in detail, taking the communication system shown in FIG. 1 as an example. Exemplarily, FIG. 1 is an architectural schematic diagram of a communication system to which the communication method provided by the embodiment of the present application is applicable.

As shown in Figure 1, the communication system includes a first core network element, a first device and a second device. Alternatively, the communication system includes a first core network element, a first device and a first access network device.

Wherein, the above-mentioned first core network element is located on the network side of the above-mentioned communication system and can be used to provide network services for the first access network device, the first device and/or the second device, etc. The first core network element may be: a delay clock network element, a session management network element, etc.

For example, the delay clock network element: can be used to control clock synchronization related functions. In the 5G communication system, the delay clock network element can be a time-sensitive communication and time synchronization function (TSCTSF) network element.

For example, the session management network element is mainly used for session management (such as creation, deletion, etc.), maintenance of session context and user plane forwarding pipeline information, network interconnection protocol (IP) address allocation and management of user equipment, Select endpoints that can manage user plane functions, policy control and charging function interfaces, downlink data notifications, etc.

In the 5G communication system, the session management network element can be a session management function (SMF) network element, which completes terminal IP address allocation, UPF selection, accounting and QoS policy control, etc.

It should be noted that the first core network element can also be other core network elements, as long as it can realize the functions of the first core network element in the embodiment of this application.

Wherein, the above-mentioned first device may be a network side adapter or a user plane network element. The second device may be a device-side adapter or the first terminal device. For example, the first device is a network-side adapter, and the second device is a device-side adapter; or the first device is a user plane network element, and the second device is a first terminal device.

As another example, the communication system includes a delay clock network element, a network side adapter, and a first access network device.

User plane network element: As an interface with the data network, it completes functions such as user plane data forwarding, session/flow-level accounting statistics, and bandwidth limitation. That is, packet routing and forwarding and quality of service (QoS) processing of user plane data, etc. In the 5G communication system, the user plane network element may be a user plane function (UPF) network element.

It should be noted that the specific implementation of the network-side adapter and the device-side adapter is shown in the corresponding description in Figure 2 below.

Wherein, the above-mentioned first access network device may also be called an access device. The first access network device can manage wireless resources, provide access services for user equipment, and complete data forwarding between the user equipment and the core network. An access network device can also be understood as a base station in the network.

Illustratively, the first access network device in the embodiment of the present application may be any communication device with a wireless transceiver function used to communicate with the first terminal device. The first access network equipment includes but is not limited to: evolved Node B (eNB), radio network controller (radio network controller, RNC), Node B (Node B, NB), base station controller (BSC), base transceiver station (BTS), home base station (home evolved NodeB, HeNB, or home Node B, HNB), baseband unit (baseBand unit, BBU), access point (AP), wireless relay node, wireless backhaul node, transmission point (TP) or sending and receiving in a wireless fidelity (WIFI) system Point (transmission and reception point, TRP), etc., can also be 5G, such as gNB in the NR system, or transmission point (TRP or TP), one or a group (including multiple antenna panels) antennas of the base station in the 5G system The panel may also be a network node that constitutes a gNB or a transmission point, such as a baseband unit (BBU) or a distributed unit (DU).

In some deployments, gNB may include centralized units (CUs) and DUs. The gNB may also include an active antenna unit (AAU). CU implements some functions of gNB, and DU implements some functions of gNB. For example, CU is responsible for processing non-real-time protocols and services, implementing radio resource control (RRC), and packet data convergence protocol (PDCP) layer functions. DU is responsible for processing physical layer protocols and real-time services, and implementing the functions of the radio link control (RLC) layer, media access control (MAC) layer and physical (physical, PHY) layer. AAU implements some physical layer processing functions, radio frequency processing and active antenna related functions. The RRC layer information is generated by the CU, and will eventually be encapsulated by the PHY layer of the DU into PHY layer information, or converted from the PHY layer information. Therefore, under this architecture, high-level signaling, such as RRC layer signaling, can also be considered to be sent by DU, or sent by DU+AAU. It can be understood that the first access network device may be a device including one or more of a CU node, a DU node, and an AAU node. In addition, the CU can be divided into access network equipment in the access network (radio access network, RAN), or the CU can be divided into access network equipment in the core network (core network, CN). This application does not Make limitations.

Wherein, the above-mentioned first terminal device is a terminal that is connected to the above-mentioned communication system and has a wireless transceiver function, or a chip or chip system that can be installed in the terminal. The terminal equipment (such as first terminal equipment, etc.) in this application may also be called terminal, user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal , mobile device, user terminal, wireless communication device, user agent or user device. The terminal in the embodiment of the present application may be a mobile phone (mobile phone), a tablet computer (pad), a computer with wireless transceiver functions, a customer premise equipment (customer premise equipment, CPE), or a virtual reality (virtual reality, VR) terminal. , augmented reality (AR) terminals, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical, smart grid ), wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home, cellular phones, cordless phones, session initiation protocols initiation protocol (SIP) telephone, wireless local loop (WLL) station, personal digital assistant (personal digital assistant (PDA)), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem , vehicle equipment, wearable devices, terminals in 5G networks or terminals in future evolution networks, etc.

For another example, the terminal device in this application (such as the first terminal device, etc.) can be an express terminal in smart logistics (such as a device that can monitor the location of cargo vehicles, a device that can monitor the temperature and humidity of cargo, etc.), a wireless terminal in smart agriculture, etc. Terminals (such as wearable devices that can collect data about livestock, etc.), wireless terminals in smart buildings (such as smart elevators, fire monitoring equipment, and smart meters, etc.), wireless terminals in smart medical care (such as Wearable devices that can monitor the physiological status of people or animals), wireless terminals in smart transportation (such as smart buses, smart vehicles, shared bicycles, charging pile monitoring equipment, smart traffic lights, and smart monitoring and smart parking equipment, etc.), Wireless terminals in smart retail (such as vending machines, self-checkout machines, and unmanned convenience stores, etc.). For another example, the terminal device of this application may be a vehicle-mounted module, vehicle-mounted module, vehicle-mounted component, vehicle-mounted chip or vehicle-mounted unit built into the vehicle as one or more components or units. The vehicle uses the built-in vehicle-mounted module, vehicle-mounted module The group, vehicle-mounted component, vehicle-mounted chip or vehicle-mounted unit can implement the method provided by this application.

Optionally, the communication system shown in Figure 1 may be applicable to the communication network currently being discussed, or may be applicable to other networks in the future, etc. This is not specifically limited in the embodiment of the present application.

For example, FIG. 2 is a schematic diagram of a network architecture provided by an embodiment of the present application. The communication system shown in Figure 1 can be applied to the network architecture shown in Figure 2.

As shown in Figure 2, the network architecture may include but is not limited to one or more of the following: terminal equipment 100, device side adapter 110, terminal equipment 120, (wireless) access network equipment 130, user plane network element 140, Network side adapter 150, data network 160, mobility management network element 170, session management network element 180, delay clock network element 190, application network element 191, and policy control network element 192.

Each network element involved in the network architecture is described below.

1. Terminal device 100: It can be a programmable logic controller (PLC) or an input/output (IO) device, or a chip that can be set in the programmable logic control device or the input/output device. or system-on-a-chip. For example, the programmable logic control device can be the main PLC, or the main control robot, etc., and the input and output devices can be various types of IO, such as digital input and output modules, voltage and current input and output modules, or temperature input and output modules.

2. Device-side adapter 110: can be used to support TSN and establish a protocol stack related to time-sensitive communication (TSC), including receiving synchronization information from the precise time protocol clock domain for clock synchronization, and conducting data traffic according to the clock synchronization status. Rectification and gating, etc. The device-side adapter 110 and the terminal device 120 may be separate devices, or the device-side adapter 110 and the terminal device 120 may be integrated into one device, which is not limited in this application.

In the 5G mobile communication system, the device side adapter may be a device side time sensitive network translator (DS-TT).

3. For the implementation of the terminal device 120, reference can be made to the description of the first terminal device in FIG. 1 above, which will not be described again here.

4. The implementation of the (radio) access network device ((radio) access network, (R)AN) 130 can be referred to the description of the first access network device in Figure 1 above, and will not be described again here.

5. For the implementation of the user plane network element 140, reference can be made to the description of the first terminal device in Figure 1 above, which will not be described again here.

6. Network side adapter 150: can be used to support TSN and establish TSC-related protocol stacks, including receiving synchronization information from the precise time protocol clock domain for clock synchronization, and performing data traffic rectification and gating according to the clock synchronization status. The network side adapter 150 and the user plane network element 140 may be separate devices, or the network side adapter 150 and the user plane network element 140 may be integrated into one device, which is not limited in this application.

In the 5G mobile communication system, the network side adapter may be a network side time sensitive network translator (NW-TT).

7. Data network 160: can be used to provide operator services, Internet access or third-party services, including servers, which implement video source encoding and rendering on the server side. In the 5G mobile communication system, the data network may be a data network (DN).

8. Mobility management network element 170: mainly used for mobility management and access management. In the 5G mobile communication system, the access management network element can be an access and mobility management function (AMF) network element, which mainly performs functions such as mobility management and access authentication/authorization. In addition, the mobility management network element can also be responsible for transmitting user policies between the terminal and the policy control function (PCF) network element.

9. The implementation of the session management network element 180 may refer to the description of the session management network element in Figure 1 above, and will not be described again here.

10. The implementation of the delay clock network element 190 may refer to the description of the delay clock network element in Figure 1 above, and will not be described again here.

11. Application network element 191: can be used to provide various business services, can interact with the core network through network exposure function (NEF) network elements, and can interact with the policy management framework for policy management. In the 5G mobile communication system, the application network element can be an application function (AF) network element or a time-sensitive network application function (TSNAF) network element, representing a third-party or operator's application Function is the interface for the 5G network to obtain external application data. It is mainly used to convey the needs of the application side to the network side.

12. Policy control network element 192: includes user subscription data management functions, policy control functions, billing policy control functions, quality of service (QoS) control, etc. It is a unified policy framework used to guide network behavior and serves as the control plane Functional network elements (such as AMF, SMF network elements, etc.) provide policy rule information, etc.

In the 5G mobile communication system, the policy control network element may be the PCF.

It can be understood that the above network elements or functions can be network elements in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (for example, a cloud platform). The above functional network elements can be divided into one or more services. Furthermore, there may also be services that exist independently of network functions. The above network element or function can be implemented by one device, or can be implemented by multiple devices together, or can be a functional module in one device, which is not specifically limited in the embodiments of this application.

It should be noted that the communication method provided by the embodiments of the present application can be applied to the communication system shown in Figure 1. For specific implementation, please refer to the following method embodiments, which will not be described again here.

It should be noted that the solutions in the embodiments of the present application can also be applied to other communication systems, and the corresponding names can also be replaced with the names of corresponding functions in other communication systems.

It should be understood that FIG. 2 is only a simplified schematic diagram for ease of understanding. The network architecture may also include other network devices and/or other terminal devices, which are not shown in FIG. 2 .

In order to make the embodiments of the present application clearer, some contents and concepts related to the embodiments of the present application are introduced in a unified manner below.

First, clock domain port status:

The clock domain port status includes master clock status and slave clock status.

It should be noted that the master clock state can be called the master state (master state or leader state), the clock domain port in the master clock state can be called the egress port, and the slave clock state can be called the slave state. (slave state or follower state), the clock domain port in the slave clock state can be called an ingress port, which is not limited in this application.

In time-sensitive networks, the (generalized) precision time protocol ((g)PTP) clock synchronization mechanism can be used to synchronize clocks between nodes. The main synchronization mechanism is for the master clock to send clock synchronization signals to the slave clock, such as synchronization (sync) signals and follow (follow up) signals. The slave clock calculates the clock deviation between the two and adjusts it. The synchronization signal may include synchronization information (such as configuration information related to the master clock), and the following signal may include the time when the synchronization signal is sent.

Figure 3 is a topological diagram of a transmission path of a clock synchronization signal provided by an embodiment of the present application.

Combined with Figure 3, the clock types in the clock synchronization signal transmission path can include one or more of the following: ordinary clock (ordinary clock, OC), boundary clock (boundary clock, BC) and transparent clock (transparent clock, TC). Ordinary clocks have only one clock domain port, while boundary clocks can provide two or more clock domain ports. Transparent clocks can estimate the transmission time of synchronization signals and send the transmission time to other clocks that receive the message.

Figure 3 shows the clock domain port status of each clock. The master clock status is abbreviated as M, and the slave clock status is abbreviated as S. During the clock synchronization process, the synchronization signal and the follow-up signal can only be sent from the clock domain port in the master clock state to the clock domain port in the slave clock state. Assume that OC1 is the master clock and OC2-OC4 are slave clocks. The master clock OC1 sends the synchronization signal and the follow-up signal to the clock domain port 1 of BC1 through the transparent clock TC (port 1 is the slave clock state S). The transparent clock TC can be regarded as Transparent transmission path, no clock domain port status. Internally, the boundary clock can only receive the synchronization signal and the following signal from the clock domain port in the slave clock state, and send the received signal to the clock domain port in the slave clock state. For example, the clock domain port 1 of BC1 receives the synchronization signal and the following signal. It can be sent to the clock domain port 2 of BC1 and the clock domain port 2 of BC1 (both clock domain port 2 and clock domain port 3 are in the main clock state M).

Second, the scenario of the integration of time-sensitive network systems and mobile communication systems:

Figure 4 is a schematic diagram of the integration of a time-sensitive network system and a mobile communication system according to an embodiment of the present application.

Combined with Figure 4, the time-sensitive network system uses the (generalized) precise time protocol clock domain, and the mobile communication system uses the internal clock domain of the communication system. The time-sensitive network system can send the synchronization information corresponding to (g)PTP to the end device (the device that needs to be connected to the time-sensitive network) through the mobile communication system, so that the end device can perform time synchronization. The mobile communication system can serve as the boundary of the time-sensitive network. clock. The clock represented by the solid line in Figure 4 may be the clock corresponding to the internal clock domain of the communication system, and the clock represented by the dotted line in Figure 4 may be the clock corresponding to the precise time protocol clock domain.

It should be noted that Figure 4 indicates that synchronization information corresponding to the precise time protocol clock domain is transmitted from the network side adapter to the device side adapter as an example. Terminal equipment can be externally connected or integrated with device-side adapters, and user plane network elements can be externally connected with or integrated with network-side adapters. This application takes the Precision Time Protocol clock domain as an example for elaboration. The methods or functions applicable to the Precision Time Protocol clock domain are also applicable to the Generalized Precision Time Protocol clock domain.

For example, the time-sensitive network system can send and broadcast the synchronization information (synchronization information corresponding to the precise time protocol clock domain) to the network bridge and/or the terminal device that can directly receive it through the corresponding management entity, and the network bridge transmits the synchronization information. To the network side adapter, the user plane network element can receive the synchronization information of the time-sensitive network broadcast through the network side adapter and send it to each terminal device (for example, in the form of unicast), and then the terminal device sends the synchronization information to the end device through the device side adapter. .

The mobile communication system can send synchronization information (synchronization information corresponding to the internal clock domain of the communication system) to the access network device through the corresponding management entity, and the access network device can use system information block (SIB) messages or wireless resources. The synchronization information is sent to the terminal device in the form of a radio resource control (RRC) message, and then the terminal device transmits the synchronization information to the device-side adapter. The access network equipment can send the synchronization information to the user plane network element.

Among them, the user plane network element can receive and maintain the clock corresponding to the internal clock domain of the communication system (the clock represented by the solid line in Figure 4) and the clock corresponding to the precise time protocol clock domain (the clock represented by the solid line in Figure 4 ), the network side adapter can receive and maintain the clock corresponding to the internal clock domain of the communication system and the clock corresponding to the precise time protocol clock domain. The access network equipment can receive and maintain the clock corresponding to the internal clock domain of the communication system, and the terminal equipment receives and maintains the clock corresponding to the internal clock domain of the communication system and the clock corresponding to the precision time protocol clock domain. The device-side adapter can receive and maintain the clock corresponding to the internal clock domain of the communication system and the clock corresponding to the precise time protocol clock domain.

Figure 5 is a schematic diagram of a transmission path provided by an embodiment of the present application.

As shown in Figure 5, the network side adapter can receive the synchronization information broadcast by the time-sensitive network (synchronization information corresponding to the clock domain of the precision time protocol), and transmit it through the nodes in the mobile communication system (user plane network elements, access network equipment and terminals). device) to the device-side adapter, or the device-side adapter can also receive the synchronization information broadcast by the time-sensitive network and transmit it to the network side through the nodes in the mobile communication system (terminal equipment, access network equipment and user plane network elements) adapter.

Combined with Figure 4, in the process of the time-sensitive network system transmitting synchronization information corresponding to the precise time protocol clock domain through the mobile communication system, dwell time will be generated in the mobile communication system. Equipment in the mobile communication system can use the internal clock of the communication system The clock update dwell time corresponding to the domain. For example, the data packet header of the synchronization information includes a correction field. The user plane network element receives the data packet and sends it to the terminal device through the access network device. The terminal device receives the data packet and adds the correction field in the data packet header. The residence time of the data packet from the user plane network element to the terminal device and is sent to the terminal device. In this way, the terminal device obtains the residence time of the synchronization information corresponding to the precise time protocol clock domain in the node of the mobile communication system.

The communication method provided by the embodiment of the present application will be described in detail below with reference to Figures 6-7. Among them, the actions, terms, etc. involved in the various embodiments of this application can be referred to each other and are not limited. The object names or parameter names in the embodiments of this application are just examples, and other names can also be used in specific implementations without limitation.

Exemplarily, FIG. 6 is a schematic flowchart of a communication method provided by an embodiment of the present application. In the communication method shown in Figure 6, the first core network element may be a delay clock network element or a session management network element, the first device may be a network side adapter or a user plane network element, and the second device may be a device side adapter or first terminal device.

For example, the first core network element is a delay clock network element, the first device is a network-side adapter, and the second device is a device-side adapter. For another example, the first core network element is a session management network element, the first device is a user plane network element, and the second device is a first terminal device.

As shown in Figure 6, the communication method includes the following steps:

S601. The first device sends the first clock status information to the first core network element. Correspondingly, the first core network element receives the first clock status information from the first device.

For example, the first clock status information may be used to indicate the clock synchronization status of the precision time protocol clock domain.

Optionally, the first clock status information may also be used to indicate the clock synchronization status of the internal clock domain of the communication system.

In some embodiments, the first clock status information may include: whether the clock synchronization status of the Precision Time Protocol clock domain is abnormal and/or the Precision Time Protocol clock domain deviation.

Optionally, the first clock status information may also include: whether the clock synchronization status of the internal clock domain of the communication system is abnormal and/or the internal clock domain deviation of the communication system.

Optionally, the precision time protocol clock domain deviation may be a difference between a clock corresponding to the precision time protocol clock domain on the first device side and the first clock.

For example, the clock corresponding to the precise time protocol clock domain on the first device side may be the clock corresponding to the precise time protocol clock domain stored locally on the first device.

Optionally, the first clock may be a clock indicated by synchronization information corresponding to the precise time protocol clock domain.

For example, the synchronization information corresponding to the precise time protocol clock domain can be used to clock synchronize the clock of the precise time protocol clock domain, and the first clock is the clock indicated by the synchronization information.

Taking the transmission of synchronization information corresponding to the precise time protocol clock domain from the network side adapter to the device side adapter as an example, combined with Figure 4, assume that the first device is a network side adapter, and the network side adapter receives synchronization information corresponding to the precise time protocol clock domain (for example Through synchronization signal reception), the synchronization information indicates the first clock 1, and the network side adapter locally stores the clock 1 corresponding to the precision time protocol clock domain, then the difference between the first clock 1 and clock 1 is the precision time protocol clock domain deviation 1. Optionally, if the precision time protocol clock domain deviation 1 is less than or equal to the set threshold and the synchronization status of the precision time protocol clock domain is normal, the network side adapter can perform clock synchronization and replace the local clock 1 with the first clock 1 .

Optionally, the communication system internal clock domain deviation may be a difference between a clock corresponding to the communication system internal clock domain on the first device side and the second clock.

Optionally, the second clock may be a clock indicated by the synchronization information corresponding to the internal clock domain of the communication system received by the first device.

That is to say, the first device can receive synchronization information corresponding to the internal clock domain of the communication system. The synchronization information corresponding to the internal clock domain of the communication system is used to clock synchronize the clock of the internal clock domain of the communication system. The second clock is the synchronization information. Indicating clock.

For example, the first clock status information may explicitly indicate the clock synchronization status of the precision time protocol clock domain through whether the clock synchronization status of the precision time protocol clock domain is abnormal, or may indicate the precise time implicitly through the deviation of the precision time protocol clock domain. Clock synchronization status of the protocol clock domain.

For example, if the precision time protocol clock domain deviation is greater than the first threshold, it indicates that the synchronization status of the precision time protocol clock domain is abnormal. If the precision time protocol clock domain deviation is less than or equal to the first threshold, it indicates that there is no abnormality in the synchronization state of the precision time protocol clock domain.

For example, the first clock status information can explicitly indicate the clock synchronization status of the internal clock domain of the communication system by whether the clock synchronization status of the internal clock domain of the communication system is abnormal, or it can implicitly indicate the communication system by using the deviation of the internal clock domain of the communication system. Clock synchronization status of the internal clock domain.

For example, if the deviation of the internal clock domain of the communication system is greater than the second threshold, it indicates that the synchronization status of the internal clock domain of the communication system is abnormal. If the deviation of the internal clock domain of the communication system is less than or equal to the second threshold, it indicates that there is no abnormality in the synchronization state of the internal clock domain of the communication system.

In some embodiments, the first clock status information may also indicate whether the clock synchronization status of the precise time protocol clock domain has returned to normal, and/or whether the clock synchronization status of the internal clock domain of the communication system has returned to normal.

For example, the first clock status information may be explicitly indicated by whether the clock synchronization status of the Precision Time Protocol clock domain is restored to normal, or may be implicitly indicated by whether the clock synchronization status of the Precision Time Protocol clock domain is restored to normal by the deviation of the Precision Time Protocol clock domain. Back to normal.

For example, the first clock status information may be explicitly indicated by whether the clock synchronization status of the internal clock domain of the communication system is restored to normal, or it may be implicitly indicated by whether the clock synchronization status of the internal clock domain of the communication system is restored to normal by the deviation of the internal clock domain of the communication system. Back to normal.

Optionally, the method provided by the embodiment of the present application may also include: the first device sending information about the first access network device corresponding to the internal clock domain of the communication system to the first core network element. Correspondingly, the first core network element receives information from the first access network device corresponding to the internal clock domain of the communication system of the first device.

For example, the information about the first access network device may include: an identifier of the first access network device, and/or an address of the first access network device, etc.

In this way, the first core network element can obtain the terminal device that accesses the first access network device based on the information of the first access network device. When the internal clock domain of the communication system is abnormal, it can obtain the terminal device based on the first access network device. Device information is obtained from the affected end device.

It should be noted that the first device sends the information of the first access network device corresponding to the internal clock domain of the communication system to the first core network element, and the first device sends the first clock status information to the first core network element. It can be performed in the same step or in different steps, which is not limited in this application.

Optionally, in the above S601, when the first device is a device-side adapter, the device-side adapter can send the above-mentioned first clock status information to the first core network element through the first terminal device, and send it to the first core network element. Yuan.

Optionally, the first device supports obtaining synchronization information corresponding to the internal clock domain of the communication system and synchronization information corresponding to the precise time protocol clock domain.

Optionally, the synchronization information corresponding to the internal clock domain of the communication system may be received by the first device through the synchronization signal corresponding to the internal clock domain of the communication system.

For example, assume that the first device is a user plane network element, and the user plane network element receives a synchronization signal from a management entity of the mobile communication system. The synchronization signal carries synchronization information corresponding to the internal clock domain of the communication system.

Or, optionally, the synchronization information corresponding to the internal clock domain of the communication system may be the clock information of the internal clock domain of the communication system.

For example, assuming that the first device is a network-side adapter, the synchronization information corresponding to the internal clock domain of the communication system can be the clock information of the internal clock domain of the communication system sent by the user plane network element to the network-side adapter. The clock information of the internal clock domain of the communication system can be It is the clock of the internal clock domain of the communication system obtained after clock synchronization of user plane network elements.

Optionally, the synchronization information corresponding to the precise time protocol clock domain may be received by the first device through the synchronization signal corresponding to the precise time protocol clock domain.

For example, assuming that the first device is a network-side adapter, take the transmission of synchronization information corresponding to the precise time protocol clock domain from the network-side adapter to the device-side adapter as an example. The network side adapter receives a synchronization signal from a management entity of the time-sensitive network system, and the synchronization signal carries synchronization information corresponding to the precise time protocol clock domain.

Or, optionally, the synchronization information corresponding to the precision time protocol clock domain may be the clock information of the precision time protocol clock domain.

For example, assume that the first device is a user plane network element to transmit accurate data from the network side adapter to the device side adapter. Take the synchronization information corresponding to the time protocol clock domain as an example. The synchronization information corresponding to the precise time protocol clock domain can be the clock information of the precise time protocol clock domain sent by the network side adapter to the user plane network element. The clock information of the precise time protocol clock domain can be the precise clock information obtained by the network side adapter after clock synchronization. The clock for the time protocol clock domain.

It should be noted that in this embodiment of the present application, the information, messages, or requests transmitted between the first device and the first core network element may be sent directly or through other devices. For example, assuming that the first device is a user plane network element, the user plane network element can directly send the first clock status information to the session management network element. Assume that the first device is a network side adapter. The network side adapter can send the first clock status information to the delay clock network element through the session management network element and the policy control network element. For example, the network side adapter can use the port management message container (port management information container (PMIC) message or user plane node management information container (UMIC) message to send the first clock status information to the delay clock network element.

Information, messages, or requests transmitted between the second device and the first core network element may be sent through other devices. For example, assuming that the second device is a device-side adapter, the device-side adapter can send the second clock state to the delay clock network element through the terminal device, the first access network device, the mobility management network element, and the session management network element. Information, for example, the device-side adapter can send the second clock status information to the delay clock network element through a PMIC message or a UMIC message. Assuming that the second device is a first terminal device, the first terminal device may send the second clock status information to the session management network element through the first access network device and the mobility management network element.

S602: The second device sends the second clock status information to the first core network element. Correspondingly, the first core network element receives the second clock status information from the second device.

For example, the second clock status information may be used to indicate the clock synchronization status of the precision time protocol clock domain.

Optionally, the second clock status information may also be used to indicate the clock synchronization status of the internal clock domain of the communication system.

In some embodiments, the second clock status information may include: whether the clock synchronization status of the Precision Time Protocol clock domain is abnormal and/or the Precision Time Protocol clock domain deviation.

Optionally, the second clock status information may also include: whether the clock synchronization status of the internal clock domain of the communication system is abnormal and/or the internal clock domain deviation of the communication system.

The implementation of the second clock status information is similar to the first clock status information. The second clock status information can explicitly and/or implicitly indicate the clock synchronization status of the precise time protocol clock domain. The second clock status information can explicitly and/or implicitly indicate the clock synchronization status of the precise time protocol clock domain. Or implicitly indicate the clock synchronization status of the internal clock domain of the communication system.

In some embodiments, the second clock status information may also indicate whether the clock synchronization status of the precise time protocol clock domain has returned to normal, and/or whether the clock synchronization status of the internal clock domain of the communication system has returned to normal. For specific implementation methods, please refer to the description corresponding to the first clock status information in S601 above, which will not be described again here.

Optionally, the method provided by the embodiment of the present application may also include: the second device sending the information of the first access network device corresponding to the internal clock domain of the communication system to the first core network element. Correspondingly, the first core network element receives information from the first access network device corresponding to the internal clock domain of the communication system of the second device.

It should be noted that the second device sends the information of the first access network device corresponding to the internal clock domain of the communication system to the first core network element, and the second device sends the second clock status information to the first core network element. It can be performed in the same step or in different steps, which is not limited in this application.

What needs to be explained is whether the clock synchronization status of the precise time protocol clock domain is abnormal, whether the precise time protocol clock domain deviation is abnormal, whether the clock synchronization status of the internal clock domain of the communication system is abnormal, whether the internal clock domain deviation of the communication system is abnormal, And/or the implementation of the information of the first access network device corresponding to the internal clock domain of the communication system may refer to the description in S601 above, and will not be described again here.

Optionally, the second device supports obtaining synchronization information corresponding to the internal clock domain of the communication system and synchronization information corresponding to the precise time protocol clock domain.

Optionally, the synchronization information corresponding to the internal clock domain of the communication system may be received by the second device through the synchronization signal corresponding to the internal clock domain of the communication system.

For example, assume that the second device is a first terminal device, and the first terminal device receives a synchronization signal from a management entity of the mobile communication system. The synchronization signal carries synchronization information corresponding to the internal clock domain of the communication system.

For example, assuming that the second device is a device-side adapter, the synchronization information corresponding to the internal clock domain of the communication system may be the clock information of the internal clock domain of the communication system sent by the first terminal device to the device-side adapter. The clock information of the internal clock domain of the communication system may be It is the clock of the internal clock domain of the communication system obtained after the first terminal device performs clock synchronization.

Optionally, the synchronization information corresponding to the precise time protocol clock domain may be received by the second device through the synchronization signal corresponding to the precise time protocol clock domain.

For example, assuming that the second device is a device-side adapter, take the transmission of synchronization information corresponding to the precise time protocol clock domain from the network-side adapter to the device-side adapter as an example. The device-side adapter receives a synchronization signal from a management entity of the time-sensitive network system, and the synchronization signal carries synchronization information corresponding to the precise time protocol clock domain.

For example, assuming that the second device is the first terminal device, take the transmission of synchronization information corresponding to the precise time protocol clock domain from the network side adapter to the device side adapter as an example. The synchronization information corresponding to the precise time protocol clock domain may be the clock information of the precise time protocol clock domain sent by the device-side adapter to the first terminal device. The clock information of the precise time protocol clock domain may be the precise clock information obtained by the device-side adapter after clock synchronization. The clock for the time protocol clock domain.

It should be noted that this application does not limit the order between the above-mentioned S601 and S602.

S603. The first core network element determines the clock domain in which the clock synchronization state is abnormal from the internal clock domain of the communication system and the precise time protocol clock domain based on the first clock status information and the second clock status information.

In a possible design method, the clock domain port status of the first device is the slave clock status, and the clock domain port status of the second device is the master clock status. The above S603 may include: if the first clock status information indicates the precise time If there is no abnormality in the clock synchronization status of the protocol clock domain, and the second clock status information indicates that the clock synchronization status of the precise time protocol clock domain is abnormal, then the first core network element determines that the clock synchronization status of the internal clock domain of the communication system is abnormal. Alternatively, if the first clock status information indicates that the clock synchronization status of the Precision Time Protocol clock domain is abnormal, the first core network element determines that the clock synchronization status of the Precision Time Protocol clock domain is abnormal.

For example, with reference to Figure 4, in a scenario where the first device receives the synchronization information of the Precision Time Protocol clock domain and sends the synchronization information to the second device through the mobile communication system, if the first device determines the clock of the Precision Time Protocol clock domain There is no abnormality in the synchronization status. If the second device determines that the clock synchronization status of the precise time protocol clock domain is abnormal, and the result of the second device is affected by the clock synchronization status of the internal clock domain of the communication system, then the first core network element According to the first clock status information fed back by the first device and the second clock status information fed back by the second device, it is determined that the clock synchronization status of the internal clock domain of the communication system is abnormal.

Alternatively, if the first device determines that the clock synchronization status of the Precision Time Protocol clock domain is abnormal, the first core network element determines that the clock synchronization status of the Precision Time Protocol clock domain is abnormal based on the first clock status information fed back by the first device. Optionally, if the first clock status information indicates that the clock synchronization status of the Precision Time Protocol clock domain is abnormal, the first core network element may directly determine that the clock synchronization status of the Precision Time Protocol clock domain is abnormal without considering the second clock status information. . Because the second clock status information is affected by the clock synchronization status of the precise time protocol clock domain, it must indicate that the clock synchronization status of the precise time protocol clock domain is abnormal.

The above design method can be applied to a scenario where the first device receives the synchronization information of the precise time protocol clock domain and sends the synchronization information to the second device through the mobile communication system.

In another possible design method, the clock domain port status of the second device is the slave clock status, and the clock domain port status of the first device is the master clock status. The above S603 may include: If the second clock status information indicates accurate If there is no abnormality in the clock synchronization status of the time protocol clock domain, and the first clock status information indicates that the clock synchronization status of the precise time protocol clock domain is abnormal, then the first core network element determines that the clock synchronization status of the internal clock domain of the communication system is abnormal. Alternatively, if the second clock status information indicates that the clock synchronization status of the Precision Time Protocol clock domain is abnormal, the first core network element determines that the clock synchronization status of the Precision Time Protocol clock domain is abnormal.

For example, in a scenario where the second device receives the synchronization information of the Precision Time Protocol clock domain and sends the synchronization information to the first device through the mobile communication system, if the second device determines that there is no abnormality in the clock synchronization status of the Precision Time Protocol clock domain , the first device determines that the clock synchronization status of the precise time protocol clock domain is abnormal, and the result of the first device is affected by the clock synchronization status of the internal clock domain of the communication system, then the first core network element determines based on the first clock fed back by the first device The status information and the second clock status information fed back by the second device determine that the clock synchronization status of the internal clock domain of the communication system is abnormal.

Alternatively, if the second device determines that the clock synchronization status of the precise time protocol clock domain is abnormal, the first core network element determines that the clock synchronization status of the internal clock domain of the communication system is abnormal based on the second clock status information fed back by the second device. Optionally, if the second clock status information indicates that the clock synchronization status of the Precision Time Protocol clock domain is abnormal, the first core network element may directly determine that the clock synchronization status of the Precision Time Protocol clock domain is abnormal without considering the first clock status information. . Because the first clock status information is affected by the clock synchronization status of the Precision Time Protocol clock domain, it must indicate that the clock synchronization status of the Precision Time Protocol clock domain is abnormal.

The above design method can be applied to a scenario where the second device receives the synchronization information of the precise time protocol clock domain and sends the synchronization information to the first device through the mobile communication system.

For example, in a scenario where the first device receives the synchronization information of the Precision Time Protocol clock domain and sends the synchronization information to the second device through the mobile communication system, or the second device receives the synchronization information of the Precision Time Protocol clock domain and In the scenario where the synchronization information is sent to the first device through the mobile communication system, if the second clock status information indicates that the clock synchronization status of the Precision Time Protocol clock domain is normal, and the first clock status information indicates the clock synchronization of the Precision Time Protocol clock domain If there is no abnormality in the status, the first core network element determines the clock synchronization status of the precise time protocol clock domain and the internal clock domain of the communication system based on the first clock status information fed back by the first device and the second clock status information fed back by the second device. There is no abnormality in the clock synchronization status.

In a possible design method, the above S603 may include: if the first clock status information and the second clock status information both indicate that the clock synchronization status of the precise time protocol clock domain is abnormal, the first core network element determines The clock synchronization status of the precision time protocol clock domain is abnormal.

In a possible design method, the above S603 may include: if the first clock status information indicates that the clock synchronization status of the Precision Time Protocol clock domain is abnormal, and the second clock status information indicates that the clock synchronization status of the Precision Time Protocol clock domain is abnormal, If abnormal, the first core network element determines that the clock synchronization state of the internal clock domain of the communication system is abnormal. Alternatively, if the first clock status information indicates that the clock synchronization status of the Precision Time Protocol clock domain is not abnormal, and the second clock status information indicates that the clock synchronization status of the Precision Time Protocol clock domain is abnormal, then the first core network element determines that the communication system internal The clock synchronization status of the clock domain is abnormal.

That is to say, in the process of determining the clock domain in which the clock synchronization status is abnormal, the clock domain port status of the first device or the second device may be determined directly based on the first clock status information and the second clock status information, without considering the clock domain port status of the first device or the second device.

For example, if both the first clock status information and the second clock status information indicate that the clock synchronization status of the precision time protocol clock domain is abnormal, it is determined that the clock synchronization status of the precision time protocol clock domain is abnormal.

If one and only one of the first clock status information and the second clock status information indicates that the clock synchronization status of the precise time protocol clock domain is abnormal, it is determined that the clock synchronization status of the internal clock domain of the communication system is abnormal.

If both the first clock status information and the second clock status information indicate that the clock synchronization status of the precise time protocol clock domain is normal, it is determined that the clock synchronization status of the precise time protocol clock domain and the clock synchronization status of the internal clock domain of the communication system are normal. .

In some embodiments, the above-mentioned S603 first core network element determines the clock domain in which the clock synchronization status is abnormal from the internal clock domain of the communication system and the precise time protocol clock domain based on the first clock status information and the second clock status information. During the process, the clock synchronization status of the internal clock domain of the communication system indicated by the first clock status information and/or the clock synchronization status of the internal clock domain of the communication system indicated by the second clock status information may also be considered.

In some embodiments, the number of second clock status information in S603 above may be one or more, and the first core network element may obtain the clock status information from the internal clock domain of the communication system based on the first clock status information and at least one second clock status information. In the precise time protocol clock domain, determine the clock domain in which the clock synchronization status is abnormal.

For example, when the number of second clock status information is multiple, the plurality of second clock status information may come from multiple second devices.

For example, the plurality of second clock status information may come from multiple device-side adapters, and the multiple device-side adapters may be device adapters that access the same or different access network devices through terminal devices (the terminal devices may be the same or different).

For example, in the scenario where the first device receives the synchronization information of the precise time protocol clock domain and sends the synchronization information to the second device through the mobile communication system, taking the second device as a device-side adapter as an example, assuming that multiple second devices The device is connected to the same access network device through different terminal devices, the second device 1 and the second device 2 are connected to the terminal device 1, the second device 3 is connected to the terminal device 2, and the second clock status information 1 (corresponding to the second device 1) Indicates that the clock synchronization status of the precise time protocol clock domain is normal. The second clock status information 2 (corresponding to the second device 2) indicates that the clock synchronization status of the precise time protocol clock domain is normal. The second clock status information 3 (corresponds to the second device 3) Indicates that the clock synchronization status of the precise time protocol clock domain is abnormal, the first core network element may use the second clock status information 1 and the second clock status information 2, without considering the second clock status information 3.

For example, it can be considered that the abnormality of the channel between the terminal device 2 and the access network device causes the synchronization information of the clock domain of the precise time protocol to be transmitted to be abnormal, thus causing the second clock status information 3 (corresponding to the second device 3) to indicate the precise time. The clock synchronization status of the protocol clock domain is abnormal.

The first core network element may determine the clock domain in which the clock synchronization state is abnormal based on the first clock status information, the second clock status information 1 and the second clock status information 2. In this way, the first core network element can make a comprehensive judgment based on the first clock status information and at least one second clock status information, thereby improving the accuracy of determining the clock domain in which the clock synchronization status is abnormal.

In some embodiments, in S603 above, according to the first clock status information and the second clock status information, from the internal clock domain of the communication system and the precise time protocol clock domain, the clock domain in which the clock synchronization status is abnormal may be determined by the policy control network. element or other network elements.

Exemplarily, the first core network element receives the first clock status information and sends it to the policy control network element or other network elements. The first core network element receives the second clock status information and sends it to the policy control network element or other network elements. other network elements. In this way, the policy control network element or other network elements obtain the first clock status information and the second clock status information.

Optionally, the policy control network element or other network elements obtain the result of the clock domain in which the clock synchronization status is abnormal and send it to the first core network element, or the second clock abnormality information can be sent to the application network element. For example, execute the following figure S802 to S804 in 8.

In a possible design method, the method provided by this application may also include: S604, the first core network element sends a first clock status request to the first device. Correspondingly, the first device receives the first clock status request from the first core network element.

Optionally, the first clock status request may include an identification of the Precision Time Protocol clock domain.

Optionally, the first clock status request may be used to request the clock synchronization status of the Precision Time Protocol clock domain.

Optionally, the first clock status request may also include an identification of the internal clock domain of the communication system, and the first clock status request may also be used to request the clock synchronization status of the internal clock domain of the communication system.

It should be noted that the above S604 may be executed before the above S601.

In a possible design method, the method provided by this application may also include: S605, the first device determines the first clock status information.

In some embodiments, the first clock status information includes the precision time protocol clock domain deviation. The above S605 may include: the first device may synchronize the clock corresponding to the precision time protocol clock domain on the first device side and the clock corresponding to the precision time protocol clock domain. information to obtain precise time protocol clock domain deviation.

For example, the first device locally stores the clock corresponding to the precise time protocol clock domain, such as clock 1. The first device receives the synchronization information corresponding to the precise time protocol clock domain. The synchronization information indicates clock 2. Then the deviation of the precise time protocol clock domain is The difference between clock 1 and clock 2.

In some embodiments, the first clock status information includes whether the clock synchronization status of the precision time protocol clock domain is abnormal. The above S605 may include: the first device determines the first clock status information based on the precision time protocol clock domain deviation.

That is to say, the first device can determine whether the clock synchronization state of the precision time protocol clock domain is abnormal based on the precision time protocol clock domain deviation.

In some embodiments, the above-mentioned first device determines the first clock status information based on the precision time protocol clock domain deviation, which may include: the precision time protocol clock domain deviation is greater than the first threshold, then the first clock status information indicates the precision time protocol clock domain. The synchronization status is abnormal. Alternatively, if the precision time protocol clock domain deviation is less than or equal to the first threshold, then the first clock status information indicates that the synchronization status of the precision time protocol clock domain is normal.

In other embodiments, the first device determining the first clock status information based on the precision time protocol clock domain deviation may include: the first device determining the first clock status information based on the precision time protocol clock domain deviation and the first deviation.

For example, if the precision time protocol clock domain deviation is greater than the first threshold, and the first deviation is less than or equal to the fifth threshold, then the first clock status information indicates that the synchronization status of the precision time protocol clock domain is abnormal.

Alternatively, if the precision time protocol clock domain deviation is less than or equal to the first threshold, and the first deviation is greater than the fifth threshold, then the first clock status information indicates that the synchronization status of the precision time protocol clock domain is normal. Optionally, there may be a problem with the clock in the internal clock domain of the communication system local to the first device. The clock synchronization may be performed according to the synchronization information of the internal clock domain of the communication system, and the clock in the internal clock domain of the communication system local to the first device may be replaced by Second clock.

Alternatively, if the precision time protocol clock domain deviation is less than or equal to the first threshold, and the first deviation is less than or equal to the fifth threshold, then the first clock status information indicates that the synchronization status of the precision time protocol clock domain is normal.

Or, if the precision time protocol clock domain deviation is greater than the first threshold, and the first deviation is greater than the fifth threshold, then there is a problem with the local clock of the first device's precision time protocol clock domain, and the clock can be performed based on the synchronization information of the precision time protocol clock domain. Synchronizing, replacing the clock of the local precision time protocol clock domain of the first device with the first clock.

Optionally, the first deviation may be a difference between a clock corresponding to the precise time protocol clock domain on the first device side and a clock corresponding to the internal clock domain of the communication system on the first device side.

For example, the clock corresponding to the precise time protocol clock domain stored in the first device is clock a, the clock corresponding to the communication system internal clock domain stored in the first device is clock b, and the first deviation is the difference between clock a and clock b. .

In some embodiments, the first clock status information includes the internal clock domain deviation of the communication system. The above S605 may include: the first device may synchronize according to the clock corresponding to the internal clock domain of the communication system on the first device side and the corresponding clock domain of the internal clock domain of the communication system. information to obtain the internal clock domain deviation of the communication system.

For example, the first device locally stores the clock corresponding to the internal clock domain of the communication system, such as clock 3. The first device receives the synchronization information corresponding to the internal clock domain of the communication system. The synchronization information indicates clock 4. Then the internal clock domain deviation of the communication system is The difference between clock 3 and clock 4.

In some embodiments, the first clock status information includes whether the clock synchronization status of the internal clock domain of the communication system is abnormal. The above S605 may include: the first device determines the first clock status information based on the internal clock domain deviation of the communication system.

That is to say, the first device can determine whether the clock synchronization state of the internal clock domain of the communication system is abnormal based on the internal clock domain deviation of the communication system.

In some embodiments, the above-mentioned first device determines the first clock status information based on the internal clock domain deviation of the communication system. The determination of the first clock status information may include: the internal clock domain deviation of the communication system is greater than the second threshold, then the first clock status information indicates the internal clock domain of the communication system. The synchronization status is abnormal. Alternatively, if the deviation of the internal clock domain of the communication system is less than or equal to the second threshold, the first clock status information indicates that the synchronization status of the internal clock domain of the communication system is normal.

In other embodiments, the above-mentioned first device determining the first clock status information based on the internal clock domain deviation of the communication system may include: the first device determining the first clock status information based on the internal clock domain deviation of the communication system and the first deviation.

Exemplarily, the communication system internal clock deviation is greater than the second threshold, and the first deviation is less than or equal to the sixth threshold. value, the first clock status information indicates that the synchronization status of the internal clock domain of the communication system is abnormal.

Alternatively, if the internal clock deviation of the communication system is less than or equal to the second threshold, and the first deviation is greater than the sixth threshold, then the first clock status information indicates that the synchronization status of the internal clock domain of the communication system is normal. Optionally, there may be a problem with the clock of the first device's local Precision Time Protocol clock domain. The clock may be synchronized according to the synchronization information of the Precision Time Protocol clock domain, and the clock of the first device's local Precision Time Protocol clock domain may be replaced by First clock.

Alternatively, if the internal clock deviation of the communication system is less than or equal to the second threshold, and the first deviation is less than or equal to the sixth threshold, then the first clock status information indicates that the synchronization status of the internal clock domain of the communication system is normal.

Alternatively, if the internal clock deviation of the communication system is greater than the second threshold, and the first deviation is greater than the sixth threshold, then there is a problem with the clock of the internal clock domain of the local communication system of the first device, and clock synchronization can be performed based on the synchronization information of the internal clock domain of the communication system. , replacing the clock of the internal clock domain of the communication system local to the first device with the second clock.

In the embodiment of the present application, the first to sixth thresholds may be preset, the fifth threshold and the sixth threshold may be equal or unequal, and the first to sixth thresholds may be equal or unequal to each other. There are no restrictions on applications.

In a possible design method, the method provided by this application may also include: S606, the first core network element sends a second clock status request to the second device. Correspondingly, the second device receives the second clock status request from the first core network element.

Optionally, the second clock status request may include an identification of the Precision Time Protocol clock domain.

Optionally, the second clock status request may be used to request the clock synchronization status of the Precision Time Protocol clock domain.

Optionally, the second clock status request may also include the identification of the internal clock domain of the communication system, and the second clock status request may also be used to request the clock synchronization status of the internal clock domain of the communication system.

It should be noted that S606 can be executed before the above-mentioned S602, and this application does not limit the order between the above-mentioned S604 and S606.

In a possible design method, the method provided by this application may also include: S607, the second device determines the second clock status information.

In some embodiments, the second clock status information includes the precision time protocol clock domain deviation. The above S607 may include: the second device may synchronize the clock corresponding to the precision time protocol clock domain on the second device side and the clock corresponding to the precision time protocol clock domain. information to obtain precise time protocol clock domain deviation. The specific implementation method may refer to the corresponding description in the above-mentioned S605, the first device determines the first clock status information, and just replace the first device with the second device.

In some embodiments, the second clock status information includes whether the clock synchronization status of the precision time protocol clock domain is abnormal. The above S607 may include: the second device determines the second clock status information based on the precision time protocol clock domain deviation.

In some embodiments, the above-mentioned second device determines the second clock status information based on the precision time protocol clock domain deviation, which may include: the precision time protocol clock domain deviation is greater than a third threshold, then the second clock status information indicates the precision time protocol clock domain. The synchronization status is abnormal. Alternatively, if the precision time protocol clock domain deviation is less than or equal to the third threshold, then the second clock status information indicates that the synchronization status of the precision time protocol clock domain is normal.

Optionally, the third threshold and the first threshold may be equal or unequal.

In other embodiments, the second device determining the second clock status information based on the precise time protocol clock domain deviation may include: the second device determining the second time based on the precise time protocol clock domain deviation and the second deviation. clock status information. The specific implementation method is similar to the first device determining the first clock status information based on the precision time protocol clock domain deviation and the first deviation in S605 above. Reference may be made to the description of S605 above, which will not be described again in this application.

Optionally, the second deviation may be a difference between a clock corresponding to the precision time protocol clock domain on the second device side and a clock corresponding to the internal clock domain of the communication system on the second device side. The second deviation is similar to the first deviation in the above-mentioned S605, and reference may be made to the description of the above-mentioned S605, which will not be described again in this application.

In some embodiments, the second clock status information includes the internal clock domain deviation of the communication system. The above S607 may include: the second device may synchronize according to the clock corresponding to the internal clock domain of the communication system on the second device side and the corresponding clock domain of the internal clock domain of the communication system. information to obtain the internal clock domain deviation of the communication system. The specific implementation method may refer to the corresponding description in the above-mentioned S605, the first device determines the first clock status information, and just replace the first device with the second device.

In some embodiments, the second clock status information includes whether the clock synchronization status of the internal clock domain of the communication system is abnormal. The above S607 may include: the first device determines the second clock status information based on the internal clock domain deviation of the communication system.

In some embodiments, the above-mentioned second device determines the second clock status information based on the internal clock domain deviation of the communication system may include: the internal clock domain deviation of the communication system is greater than the fourth threshold, then the second clock status information indicates the internal clock domain of the communication system The synchronization status is abnormal. Alternatively, if the deviation of the internal clock domain of the communication system is less than or equal to the fourth threshold, then the first clock status information indicates that the synchronization status of the internal clock domain of the communication system is normal.

Optionally, the fourth threshold and the second threshold may be equal or unequal.

In other embodiments, the second device determining the second clock status information based on the internal clock domain deviation of the communication system may include: the second device determining the second clock status information based on the internal clock domain deviation of the communication system and the second deviation. The specific implementation method is similar to the first device determining the first clock status information based on the internal clock domain deviation and the first deviation of the communication system in the above-mentioned S605. Reference may be made to the description of the above-mentioned S605, which will not be described again in this application.

Based on the method shown in Figure 6, both the first device and the second device support obtaining the synchronization information corresponding to the internal clock domain of the communication system and the synchronization information corresponding to the precise time protocol clock domain. When the first device is a network-side adapter, the second device The second device is the device side adapter. Or, when the first device is a user plane network element, the second device is the first terminal device. The first device and the second device respectively send first clock status information and second clock status information to the first core network element. The first clock status information indicates the clock synchronization status of the precise time protocol clock domain, and the second clock status information Indicates the clock synchronization status of the Precision Time Protocol clock domain. According to the different transmission directions of the synchronization information corresponding to the precise time protocol clock domain, there will always be one clock status information in the first clock status information and the second clock status information. The result indicated by the clock status information is affected by the clock synchronization status of the internal clock domain of the communication system. , In this way, the core network element can accurately determine the clock domain in which the clock synchronization status is abnormal from the internal clock domain of the communication system and the precise time protocol clock domain based on the first clock status information and the second clock status information.

Exemplarily, FIG. 7 is a schematic flowchart of another communication method provided by an embodiment of the present application. In the communication method shown in Figure 7, the first core network element may be a delay clock network element, and the first device may be a network side adapter. The communication method shown in Figure 7 is applied in a scenario where the device-side adapter sends synchronization information of the precise time protocol clock domain to the network-side adapter.

As shown in Figure 7, the communication method includes the following steps:

S701. The first device sends the first clock status information to the first core network element. Correspondingly, the first core network element receives the first clock status information from the first device.

Illustratively, the first clock status information is used to indicate the clock synchronization status of the precise time protocol clock domain.

In some embodiments, the first clock status information may include one or more of the following: whether the clock synchronization status of the precision time protocol clock domain is abnormal, whether the clock synchronization status of the precision time protocol clock domain is abnormal, whether the clock synchronization status of the internal clock domain of the communication system is abnormal, The internal clock domain deviation of the communication system and/or the information of the first access network device corresponding to the internal clock domain of the communication system.

It should be noted that the specific implementation method of the first clock status information may refer to the above-mentioned S601, which will not be described again here.

Optionally, when the clock domain port status of the first device is the main clock status, if the first clock status information indicates that there is no abnormality in the clock synchronization status of the precision time protocol clock domain, the precision time protocol clock domain and the internal communication system There is no abnormality in the clock synchronization status of the clock domain.

For example, in a scenario where the device side adapter sends the synchronization information of the precise time protocol clock domain to the network side adapter through the mobile communication system, if the first clock status information indicates that the clock synchronization status of the precise time protocol clock domain is not abnormal, then the precise time There is no abnormality in the clock synchronization status of the protocol clock domain and the internal clock domain of the communication system.

S702: When the clock domain port status of the first device is in the main clock state, and the first clock status information indicates that the clock synchronization status of the precise time protocol clock domain is abnormal, the first core network element reports to the first access network The device requests the clock synchronization status of the internal clock domain of the communication system.

For example, when the clock domain port status of the first device is the main clock status, and the first clock status information indicates that the clock synchronization status of the precise time protocol clock domain is abnormal, the first access network device may be configured by further Request the clock synchronization status of the internal clock domain of the communication system to determine which of the precise time protocol clock domain and the internal clock domain of the communication system has an abnormal clock synchronization status.

Optionally, the first core network element may request the first access network device for information about the first access network device.

It should be noted that the first core network element requests the first access network device for information about the first access network device and requests the first access network device for the clock synchronization status of the internal clock domain of the communication system in the same step. execution, this application is not limited to this.

S703. The first access network device sends the clock synchronization status of the internal clock domain of the communication system to the first core network element. Correspondingly, the first core network element receives the clock synchronization status of the internal clock domain of the communication system of the first access network device.

Optionally, the first access network device sends to the first core network element whether the clock synchronization status of the internal clock domain of the communication system is abnormal and/or the internal clock domain deviation of the communication system.

Optionally, the first access network device may send the information of the first access network device to the first core network element.

It should be noted that the first access network device sending the information of the first access network device to the first core network element and sending the clock synchronization status of the internal clock domain of the communication system to the first core network element can be performed in the same step. execution, this application is not limited to this.

It should be noted that whether the clock synchronization status of the internal clock domain of the communication system is abnormal, the internal clock domain deviation of the communication system, and/or the implementation of the information of the first access network device can refer to the explanation in S601 above, and will not be discussed here. Repeat.

In some embodiments, the first access network device may determine the clock synchronization status of the internal clock domain of the communication system.

Optionally, the first access network device may obtain the communication system internal clock domain deviation based on the clock corresponding to the communication system internal clock domain on the first access network device side and the synchronization information corresponding to the communication system internal clock domain. The specific implementation method is similar to the method in which the first device obtains the internal clock domain deviation of the communication system in S605. Reference may be made to the description of S605, which will not be described again here.

Optionally, the first access network device may determine whether the clock synchronization state of the internal clock domain of the communication system is abnormal based on the internal clock domain deviation of the communication system. The specific implementation manner is similar to the manner in which the first device determines whether the clock synchronization state of the internal clock domain of the communication system is abnormal in the above-mentioned S605. Reference may be made to the description of S605, which will not be described again here.

S704. The first core network element determines the clock domain in which the clock synchronization status is abnormal from the internal clock domain of the communication system and the precise time protocol clock domain based on the clock synchronization status of the internal clock domain of the communication system.

In a possible design method, the above S704 includes: if the clock synchronization status of the internal clock domain of the communication system is not abnormal, the first core network element determines that the clock synchronization status of the precise time protocol clock domain is abnormal.

For example, in a scenario where the device side adapter receives the synchronization information of the precise time protocol clock domain and sends the synchronization information to the network side adapter through the mobile communication system, if the clock synchronization status of the precise time protocol clock domain is abnormal, the internal clock of the communication system If there is no abnormality in the clock synchronization status of the domain, the first core network element determines that the clock synchronization status of the precise time protocol clock domain is abnormal.

In a possible design method, the above S704 includes: if the clock synchronization status of the internal clock domain of the communication system is abnormal, the first core network element determines that the clock synchronization status of the internal clock domain of the communication system is abnormal.

For example, in a scenario where the device side adapter receives the synchronization information of the precise time protocol clock domain and sends the synchronization information to the network side adapter through the mobile communication system, if the clock synchronization status of the precise time protocol clock domain is abnormal, the internal clock of the communication system The clock synchronization status of the domain is abnormal. The abnormal clock synchronization status of the precision time protocol clock domain may be caused by the abnormal clock synchronization status of the internal clock domain of the communication system. Then the first core network element determines the clock synchronization status of the internal clock domain of the communication system. An exception occurs.

In a possible design method, the method provided by this application may also include: S705, the first core network element sends a first clock status request to the first device. Correspondingly, the first device receives the first clock status request from the first core network element.

It should be noted that the specific implementation of S705 may refer to the above-mentioned S604, and will not be described again here. The above S705 may be executed before the above S701.

In a possible design method, the method provided by this application may further include: the first device determines the first clock status information. The specific implementation method may refer to the above-mentioned S605, which will not be described again here.

Based on the communication method shown in Figure 7, when the clock domain port status of the first device is in the main clock state, and the first clock status information indicates that the clock synchronization status of the precise time protocol clock domain is abnormal, the clock domain port status of the first device can be passed to the third device. An access network device requests the clock synchronization status of the internal clock domain of the communication system, and determines the clock synchronization status of which of the precise time protocol clock domain and the internal clock domain of the communication system is based on the clock synchronization status of the internal clock domain of the communication system. abnormal.

Exemplarily, FIG. 8 is a schematic flowchart of yet another communication method provided by an embodiment of the present application. In the communication method shown in Figure 8, the first core network element may be a delay clock network element or a session management network element.

As shown in Figure 8, the communication method includes the following steps:

S801. The application network element sends a clock status notification request to the first core network element. Accordingly, the first core network The network element receives the clock status notification request from the application network element.

Optionally, the clock status notification request may be used to request the clock synchronization status of the second terminal device.

Optionally, the clock status notification request may include the identification of the second terminal device and may also include the clock domain identification.

For example, the clock status notification request may be used to request the clock synchronization status of the clock domain corresponding to the clock domain identification of the second terminal device.

Optionally, the clock status notification request may also include the clock domain type of the clock domain corresponding to the clock domain identifier.

For example, the clock domain type may include a precision time protocol clock domain or a communication system internal clock domain.

Optionally, the number of second terminal devices may be one or more.

Optionally, if the number of second terminal devices can be one, the second terminal device can be the first terminal device. If the number of second terminal devices may be multiple, the plurality of second terminal devices may include the first terminal device.

For example, when there are multiple second terminal devices, the clock status notification request may include identifications corresponding to multiple second terminal devices, or the application network element may send clock status notifications to the first core network element multiple times. request, the clock status notification request includes an identification of the second terminal device.

In this way, the user plane network element can monitor the clock synchronization status of one or more second terminal devices.

For example, the first core network element may be a delay clock network element.

For another example, in the case where the first core network element is a session management network element, the above S801 may include: the application network element sends a clock status notification request to the delay clock network element. That is to say, when the first core network element is the session management network element, the clock status notification request may be sent to the delay clock network element.

Optionally, S801 can be executed before the above-mentioned S604 or S705. The first core network element receives the identification of the second terminal device, can obtain the first device corresponding to the second terminal device according to the identification of the second terminal device, and provides the first device to the second terminal device. The first device sends a first clock status request.

Optionally, the method provided by the embodiment of the present application may also include: S805, the device side adapter, the network side adapter, the user plane network element, the delay clock network element, etc., establish a TSC session.

For example, during the process of establishing a TSC session, the delay clock network element can obtain the clock domain port information of the device-side adapter. For example, the address or identification of the clock domain port of the device-side adapter, the correspondence between the identification of the clock domain port of the device-side adapter and the clock domain identification, the correspondence between the identification of the clock domain port of the device-side adapter and the identification of the terminal device, etc.

For example, when the clock synchronization status of the precise time protocol clock domain is abnormal, the first core network element can use the corresponding relationship between the clock domain port identifier of the device-side adapter and the clock domain identifier, and the identification of the clock domain port of the device-side adapter. The corresponding relationship with the identification of the terminal device is to obtain the affected terminal device.

It should be noted that establishing the TSC session can be performed before the above S801.

In some embodiments, the method provided by the embodiments of this application may also include: S806, the device side adapter and the network side adapter execute the best master clock algorithm (BMCA) process.

Optionally, the above S806 may include the following steps 1 to 3.

Step 1: The device-side adapter sends a notification message to the network-side adapter. Accordingly, the network side adapter receives the notification message from the device side adapter.

Exemplarily, the notification message may include, but is not limited to: the identification of the precise time protocol clock domain, the source port identification, and the clock accuracy.

Optionally, the source port identification may be an identification of a source port that sends the synchronization information of the precision time protocol clock domain.

For example, the source port identification can be used to determine the port status of the clock domain port of each node on the synchronization information transmission path of the precise time protocol clock domain.

Optionally, the clock precision may indicate the clock precision corresponding to the clock of the precise time protocol clock domain.

Step 2: In response to the notification message from the device-side adapter, the network-side adapter obtains clock information.

Optionally, the clock information includes but is not limited to: the identification of the clock domain port of the first device, the identification of the generalized precision time protocol clock domain, the clock domain port status of the device side adapter, and the clock domain port status of the network side adapter.

Step 3: The network side adapter sends clock information to the first core network element. Correspondingly, the first core network element receives the clock information from the network side adapter.

As another example, the first core network element may be a session management network element. The above step three may include: the network side adapter sends clock information to the delay clock network element, and the delay clock network element sends clock information to the session management network element. Clock information.

It should be noted that the BMCA process can be executed after the above S801, which is not limited by this application.

S802: When the clock synchronization state of the internal clock domain of the communication system is abnormal, the first core network element obtains the information of the first access network device.

Optionally, the first access network device is an access network device corresponding to an internal clock domain of the communication system.

It should be noted that the specific implementation method of the information of the first access network device may refer to the corresponding explanation in S601 above, and will not be described again here.

In this way, information about access network equipment with abnormal clock synchronization status can be obtained.

In a possible design method, in the above S802, the first core network element obtains the information of the first access network device, which may include steps four and five.

Step 4: The first core network element sends a first request message to the mobility management network element. Correspondingly, the mobility management network element receives the first request message from the first core network element.

Optionally, the first request message may include the identification of the terminal device corresponding to the device-side adapter or the identification of the first terminal device.

For example, if the second device is a device-side adapter, the first request message may include the identification of the terminal device corresponding to the device-side adapter, such as the identification of the first terminal device. If the second device is the first terminal device, the first request message may include the identification of the first terminal device.

Optionally, the first request message may be used to request information about the access network device that the terminal device corresponding to the device-side adapter accesses or resides on. Alternatively, the first request message may be used to request information about the access network device that the first terminal device accesses or resides on.

Step 5: The mobility management network element sends the information of the first access network device to the first core network element. The first core network element receives information from the first access network device of the mobility management network element.

Optionally, the first access network device may be a terminal device corresponding to the device-side adapter or an access network device where the first terminal device accesses or resides.

For example, in steps four to five, the first core network element may be a delay clock network element or a session management network element.

In this way, the first core network element can request information about the first access network device from the mobility management network element.

In another possible design method, the first core network element is a delay clock network element. In the above S802, the first core network element obtains the information of the first access network device, which may include step 6 and step seven.

Step 6: The first core network element sends a second request message to the session management network element. Correspondingly, the session management network element receives the second request message from the first core network element.

Optionally, the second request message may include the identification of the first terminal device or the port identification of the device-side adapter.

Optionally, the second request message may be used to request information about the access network device that the first terminal device or the terminal device corresponding to the device-side adapter accesses or resides on.

Step 7: The session management network element sends the information of the first access network device to the first core network element. Correspondingly, the first core network element receives information from the first access network device of the session management network element.

Optionally, the first access network device may be an access network device that the terminal device corresponding to the first terminal device or the device-side adapter accesses or resides on.

In this way, the first core network element can request the information of the first access network device from the session management network element.

In another possible design method, the first core network element is a session management network element. In the above S802, the first core network element obtains information about the first access network device, which may include: the first core network element The element obtains the information of the first access network device according to the identifier of the first terminal device or the port identifier of the device-side adapter.

Optionally, the first access network device is an access network device to which the first terminal device or the terminal device corresponding to the device-side adapter accesses or resides.

In this way, the session management network element can obtain the information of the first access network device.

In a possible design method, the above S802 may be an optional step.

For example, the first core network element obtains the information of the first access network device in the above S601 and/or S602. The first clock status information includes the information of the first access network device corresponding to the internal clock domain of the communication system. The second The clock status information includes information about the first access network device corresponding to the internal clock domain of the communication system. In this case, S802 may not be executed and the following S803 may be executed directly.

S803: The first core network element sends the first clock abnormality information to the first terminal device according to the identification of the first terminal device. Correspondingly, the first terminal device receives the first clock abnormality information from the first core network element.

Optionally, the first clock abnormality information may be used to indicate a clock domain in which an abnormal clock synchronization state occurs.

For example, the clock synchronization status of the internal clock domain of the communication system is abnormal, and the first clock abnormality information includes an identification of the internal clock domain of the communication system.

It can be understood that the first terminal device is affected by abnormal clock synchronization status of the internal clock domain of the communication system, but the application network element does not necessarily require monitoring of the clock synchronization status of the first terminal device.

For example, when the application network element requests to monitor the clock synchronization status of the first terminal device, the first core network element may send the first clock abnormality information to the first terminal device. In the case where the application network element requests to monitor the clock synchronization status of the first terminal device, this application does not limit whether the first core network element sends the first clock abnormality information to the first terminal device.

In some embodiments, the method provided by the embodiments of the present application may also include steps eight and nine.

Step 8: The first core network element determines the terminal served by the first access network device based on the information of the first device. The identification of the device.

Step 9: The first core network element determines the identity of the third terminal device based on the identity of the terminal device served by the first access network device and the identities of one or more second terminal devices.

Optionally, the identity of the terminal device served by the first access network device includes the identity of the third terminal device, and the identity of the one or more second terminal devices includes the identity of the third terminal device.

For example, the identity of the third terminal device is the intersection of the identity of the terminal device served by the first access network device and the identity of one or more second terminal devices.

Optionally, the number of third terminal devices may be one or more.

For example, the third terminal device is a terminal device that is affected by abnormal clock synchronization status of the internal clock domain of the communication system and is monitored by the application network element request.

Optionally, the first core network element may send the first clock abnormality information to the third terminal device.

Optionally, the identification of the third terminal device may include the identification of the first terminal device.

It should be noted that the above-mentioned steps eight and nine can be executed before the above-mentioned S803.

In other embodiments, the method provided by the embodiments of the present application may further include: the first core network element sending the first clock abnormality information to the second terminal device according to the identifier of the second terminal device. Correspondingly, the second terminal device receives the first clock abnormality information from the first core network element.

For example, the first core network element may directly notify the application network element of the terminal device for monitoring the clock domain in which the clock synchronization status is abnormal.

For example, if the second terminal device is currently using the clock corresponding to the clock domain in which the clock synchronization state is abnormal, the second terminal device may stop using the clock corresponding to the clock domain in which the clock synchronization state is abnormal. If the second terminal device does not use the clock corresponding to the clock domain in which the clock synchronization state is abnormal, the second terminal device can be prevented from using the clock corresponding to the clock domain in which the clock synchronization state is abnormal.

In some embodiments, the method provided by the embodiments of the present application may further include: the first core network element sending the clock domain in which the clock synchronization status is abnormal to the device-side adapter. Correspondingly, the device-side adapter receives the clock domain in which the clock synchronization status from the first core network element is abnormal.

Optionally, the clock domain in which the clock synchronization status is abnormal can be the clock domain currently being used by the device-side adapter, and can be stopped after receiving the notification.

In some embodiments, the method provided by the embodiments of the present application may also include: the first core network element sends the clock domain in which the clock synchronization status is abnormal to the network side adapter. Correspondingly, the network side adapter receives the clock domain in which the clock synchronization status of the first core network element is abnormal.

Optionally, the clock domain in which the clock synchronization status is abnormal can be the clock domain currently being used by the network-side adapter, and can be stopped after receiving the notification.

In some embodiments, the method provided by the embodiments of the present application may further include: the first core network element sends the clock domain in which the clock synchronization status is abnormal to the user plane network element. Correspondingly, the user plane network element receives the clock domain in which the clock synchronization status of the first core network element is abnormal.

Optionally, the clock domain in which the clock synchronization status is abnormal can be the clock domain currently being used by the user plane network element, and the use can be stopped after receiving the notification.

That is to say, the first core network element can notify the device side adapter, the network side adapter and/or the user plane network element of the abnormal clock domain, such as the abnormality of the precision time protocol clock domain and/or the abnormality of the internal clock domain of the communication system. Abnormality occurs.

In some embodiments, the method provided by the embodiments of the present application may also include: S804, the first core network element sends the second clock abnormality information to the application network element. Correspondingly, the application network element receives the second clock abnormality information from the first core network element.

Optionally, the second clock abnormality information may be used to indicate that the clock synchronization status of one or more second terminal devices is abnormal. The one or more second terminal devices may be part or all of the second terminal devices to which the network element request detection is applied in S801.

Optionally, the second clock abnormality information may include the identification of the second terminal device in which the clock synchronization status is abnormal, and may also include the identification of the clock domain in which the clock synchronization status is abnormal.

For example, the clock status notification request includes the second terminal device 1 and the second terminal device 2. If the clock synchronization status of the second terminal device 1 is normal and the clock synchronization status of the second terminal device 2 is abnormal, the second terminal device 2 uses communication If the clock synchronization status of the internal clock domain 1 of the system and the internal clock domain 1 of the communication system is abnormal, the second clock abnormality information may include the second terminal device 2 and the internal clock domain 1 of the communication system.

In this way, the first core network element can notify the application network element which second terminal device or devices are currently using abnormal clock synchronization status, and can also notify the clock domain in which the clock synchronization status is abnormal.

It should be noted that the method shown in Figure 8 and the method shown in Figure 6 can be used in combination. For example, S801 can be executed before the above-mentioned S604, and S802 can be executed after the above-mentioned S603. The method shown in Figure 8 can be used in combination with the method shown in Figure 7. For example, S801 can be executed before the above-mentioned S705, and S802 can be executed after the above-mentioned S704.

Based on the communication method shown in Figure 8, when the clock synchronization state of the internal clock domain of the communication system is abnormal, the first core network element can obtain the information of the first access network device corresponding to the internal clock domain of the communication system, It can further obtain the affected terminal device and notify the terminal device that an abnormality occurs in the clock domain it is currently using.

In this application, unless otherwise specified, the same or similar parts between various embodiments may be referred to each other. In the various embodiments of this application and the various implementation methods/implementation methods/implementation methods in each embodiment, if there are no special instructions or logical conflicts, the differences between different embodiments and the various implementation methods/implementation methods in each embodiment will be different. The terminology and/or descriptions between implementation methods/implementation methods are consistent and can be referenced to each other. Different embodiments, as well as the technical features in each implementation method/implementation method/implementation method in each embodiment are based on their inherent Logical relationships can be combined to form new embodiments, implementations, implementation methods, or implementation methods. The embodiments of the present application described below do not constitute a limitation on the protection scope of the present application.

The communication method provided by the embodiment of the present application is described in detail above with reference to Figures 1-8. The communication device provided by the embodiment of the present application will be described in detail below with reference to Figures 9-11.

FIG. 9 is a schematic structural diagram of a communication device that can be used to implement an embodiment of the present application.

The communication device 900 may be a first core network element (such as a delay clock network element or a session management network element), a first device (such as a network side adapter or a user plane network element), or a second device (such as a device side adapter). or the first terminal device), or may be a chip or other components with corresponding functions applied in the first core network element, the first device, or the second device. As shown in FIG. 9 , the communication device 900 may include a processor 901 . Optionally, the communication device 900 may also include one or more of a memory 902 and a transceiver 903. The processor 901 may be coupled to one or more of the memory 902 and the transceiver 903, for example, through a communication bus, or the processor 901 may be used alone.

The following is a detailed introduction to each component of the communication device 900 with reference to Figure 9:

The processor 901 is the control center of the communication device 900 and may be one processor or a collective name for multiple processing elements. For example, the processor 901 is one or more central processing units (CPUs), an application specific integrated circuit (ASIC), or one or more processors configured to implement the embodiments of the present application. An integrated circuit, such as one or more microprocessors (digital signal processor, DSP), or one or more field programmable gate arrays (field programmable gate array, FPGA).

The processor 901 can perform various functions of the communication device 900 by running or executing software programs stored in the memory 902 and calling data stored in the memory 902 .

In a specific implementation, as an embodiment, the processor 901 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG. 9 .

In specific implementation, as an embodiment, the communication device 900 may also include multiple processors, such as the processor 901 and the processor 904 shown in FIG. 9 . Each of these processors can be a single-core processor (single-CPU) or a multi-core processor (multi-CPU). A processor here may refer to one or more communications devices, circuits, and/or processing cores for processing data (eg, computer program instructions).

Optionally, the memory 902 may be a read-only memory (ROM) or other type of static storage communication device that can store static information and instructions, a random access memory (random access memory, RAM) or a device that can store information. and other types of dynamic storage communication devices of instructions, which may also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or Other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage communication devices, or can be used to carry or store expectations in the form of instructions or data structures program code and any other medium capable of being accessed by a computer, without limitation. The memory 902 may be integrated with the processor 901 or may exist independently and be coupled to the processor 901 through the input/output port (not shown in Figure 9) of the communication device 900. This is not specifically limited in the embodiment of the present application.

Exemplarily, the input port can be used to implement the receiving function performed by the first core network element, the first device, or the second device in any of the above method embodiments, and the output port can be used to implement the receiving function performed by the first core network element, the first device, or the second device in any of the above method embodiments. The sending function performed by the first core network element, the first device, or the second device.

Among them, the memory 902 can be used to store the software program for executing the solution of the present application, and the processor 901 controls the execution. For the above specific implementation, reference may be made to the following method embodiments, which will not be described again here.

Optionally, the transceiver 903 is used for communication with other communication devices. For example, when the communication device 900 is a first core network element, the transceiver 903 may be used to communicate with the first device, the second device, and/or the first access network device. For another example, when the communication device 900 is a first device, the transceiver 903 may be used to communicate with the first core network element and/or the second device. For another example, when the communication device 900 is a second device, the transceiver 903 may be used to communicate with the first core network element and/or the first device.

In addition, the transceiver 903 may include a receiver and a transmitter (not shown separately in FIG. 9). Among them, the receiver is used to implement the receiving function, and the transmitter is used to implement the sending function. The transceiver 903 may be integrated with the processor 901, or may exist independently and be coupled to the processor 901 through the input/output port (not shown in Figure 9) of the communication device 900. This is not specifically limited in the embodiment of the present application. .

It should be noted that the structure of the communication device 900 shown in Figure 9 does not constitute a limitation on the communication device. The actual communication device may include more or less components than shown in the figure, or some components may be combined, or Different component arrangements.

Among them, the above-mentioned actions of the first core network element (which can be an access network device or a terminal device) in Figures 1 to 8 can be performed by the processor 901 in the communication device 900 shown in Figure 9 to call the application stored in the memory 902 The program code is executed by instructing the first core network element.

The above-mentioned actions of the first device in Figures 1 to 8 can be executed by the processor 901 in the communication device 900 shown in Figure 9 by calling the application code stored in the memory 902 to instruct the first device to execute. This embodiment does not do anything about this. limit.

The above-mentioned actions of the second device in Figures 1 to 8 can be executed by the processor 901 in the communication device 900 shown in Figure 9 by calling the application code stored in the memory 902 to respectively instruct the second device to execute. This embodiment does not do this. Any restrictions.

It should be noted that all relevant content of each step involved in the above method embodiment can be quoted from the functional description of the corresponding functional module, and will not be described again here.

Figure 10 is a schematic structural diagram of another communication device provided by an embodiment of the present application. For ease of explanation, FIG. 10 shows only the main components of the communication device.

The communication device 1000 may include a transceiver module 1001 and a processing module 1002.

The communication device 1000 may be the first core network element in the foregoing method embodiment. The transceiver module 1001, which may also be called a transceiver unit, is used to implement the transceiver function performed by the first core network element in any of the above method embodiments.

It should be noted that the transceiver module 1001 may include a receiving module and a sending module (not shown in Figure 10). This application does not specifically limit the specific implementation of the transceiver module 1001. The transceiver module 1001 may be composed of a transceiver circuit, a transceiver, a transceiver, or a communication interface.

Optionally, the communication device 1000 may also include a storage module (not shown in FIG. 10), which stores programs or instructions. When the processing module 1002 executes the program or instruction, the communication device 1000 can perform the method described in any of the above method embodiments.

The processing module 1002 may be used to implement the processing functions performed by the first core network element in any of the above method embodiments. The processing module 1002 may be a processor.

Figure 11 is a schematic structural diagram of another communication device provided by an embodiment of the present application. For ease of explanation, FIG. 11 shows only the main components of the communication device.

The communication device 1100 may include a sending module 1101 and a receiving module 1102.

The communication device 1100 may be the first device or the second device in the aforementioned method embodiment. The sending module 1101, which may also be called a sending unit, is used to implement the sending function performed by the first device or the second device in any of the above method embodiments. The receiving module 1102, which may also be called a receiving unit, is used to implement the receiving function performed by the first device or the second device in any of the above method embodiments.

It should be noted that the sending module 1101 and the receiving module 1102 can be set up separately, or they can be integrated into one module, that is, the sending and receiving module. This application does not specifically limit the specific implementation methods of the receiving module and the sending module. The transceiver module may be composed of a transceiver circuit, a transceiver, a transceiver, or a communication interface.

Optionally, the communication device 1100 may also include a processing module 1103 and a storage module (not shown in Figure 11), This storage module stores programs or instructions. When the processing module 1103 executes the program or instruction, the communication device 1100 can perform the method described in any of the above method embodiments.

The processing module 1103 may be used to implement the processing function performed by the first device or the second device in any of the above method embodiments. The processing module 1103 may be a processor.

In this embodiment, the communication device 1000 or the communication device 1100 is presented in the form of dividing various functional modules in an integrated manner. A "module" here may refer to a specific ASIC, circuit, processor and memory that executes one or more software or firmware programs, integrated logic circuits, and/or other devices that may provide the above functions. In a simple embodiment, those skilled in the art can imagine that the communication device 1000 or the communication device 1100 may take the form of the communication device 900 shown in FIG. 9 .

For example, the processor 901 in the communication device 900 shown in FIG. 9 can cause the communication method in the above method embodiment to be executed by calling the computer execution instructions stored in the memory 902.

Specifically, the functions/implementation processes of the transceiver module, the sending module and the receiving module in the communication device 1000 or the communication device 1100 can be implemented by the transceiver 903 in the communication device 900 shown in FIG. 9 . The function/implementation process of the processing module in the communication device 1000 or the communication device 1100 can be realized by the processor 901 in the communication device 900 shown in FIG. 9 calling the computer execution instructions stored in the memory 902.

Since the communication device 1000 or the communication device 1100 provided in this embodiment can execute the above communication method, the technical effects that can be obtained can be referred to the above method embodiments, which will not be described again here.

In a possible design solution, the communication device 1000 shown in Figure 10 can be applied to the system shown in Figure 1 to perform the communication method of the first core network element in the above-mentioned communication methods described in Figures 6 and 8. Function.

Among them, the transceiver module 1001 is used to receive the first clock status information from the first device. The first clock status information is used to indicate the clock synchronization status of the precise time protocol clock domain.

The transceiver module 1001 is also used to receive the second clock status information from the second device. The second clock status information is used to indicate the clock synchronization status of the precise time protocol clock domain. Both the first device and the second device support obtaining synchronization information corresponding to the internal clock domain of the communication system and synchronization information corresponding to the precise time protocol clock domain. The first device is a network-side adapter and the second device is a device-side adapter. Alternatively, the first device is a user plane network element, and the second device is a first terminal device.

The processing module 1002 is configured to determine, based on the first clock status information and the second clock status information, the clock domain in which the clock synchronization state is abnormal from the internal clock domain of the communication system and the precision time protocol clock domain.

Optionally, the communication device 1000 may also include a storage module (not shown in Figure 10), which stores programs or instructions. When the processing module 1002 executes the program or instruction, the communication device 1000 can perform the functions of the first core network element in the methods shown in FIG. 6 and FIG. 8 .

It should be noted that the communication device 1000 may be the first core network element, or may be a chip (system) or other components or components that can be disposed on the first core network element, which is not limited in this application.

In addition, the technical effects of the communication device 1000 can be referred to the technical effects of the communication methods shown in FIG. 6 and FIG. 8 , which will not be described again here.

In another possible design solution, the communication device 1000 shown in Figure 10 can be applied to the system shown in Figure 1 to perform the first core network element in the communication method described in Figures 7 and 8. function.

Among them, the transceiver module 1001 is used to receive the first clock status information from the first device. The first clock status information is used to indicate the clock synchronization status of the Precision Time Protocol clock domain, and the first device supports obtaining synchronization information corresponding to the internal clock domain of the communication system and synchronization information corresponding to the Precision Time Protocol clock domain.

The transceiver module 1001 is also configured to notify the first access network device when the clock domain port status of the first device is in the main clock state and the first clock status information indicates that the clock synchronization status of the precise time protocol clock domain is abnormal. Requests the clock synchronization status of the internal clock domain of the communication system.

The transceiver module 1001 is also used to receive the clock synchronization status of the internal clock domain of the communication system from the first access network device.

The processing module 1002 is configured to determine, based on the clock synchronization status of the internal clock domain of the communication system, the clock domain in which the clock synchronization status is abnormal from the internal clock domain of the communication system and the precision time protocol clock domain.

Optionally, the communication device 1000 may also include a storage module (not shown in Figure 10), which stores programs or instructions. When the processing module 1002 executes the program or instruction, the communication device 1000 can perform the functions of the first core network element in the methods shown in FIG. 7 and FIG. 8 .

In addition, the technical effects of the communication device 1000 can be referred to the technical effects of the communication method shown in FIG. 7 and FIG. 8 , which will not be described again here.

In yet another possible design solution, the communication device 1100 shown in FIG. 11 can be applied to the system shown in FIG. 1, and the first device in the communication method described in FIG. 6, FIG. 7 and FIG. 8 is executed. , or the function of the second device.

Among them, the receiving module 1102 is used to receive the first clock status request from the first core network element. The first clock status request includes an identification of the Precision Time Protocol clock domain, and the first clock status request is used to request the clock synchronization status of the Precision Time Protocol clock domain.

The sending module 1101 is configured to send the first clock status information to the first core network element. The first clock status information includes: whether the clock synchronization status of the precision time protocol clock domain is abnormal and/or the precision time protocol clock domain deviation, and the precision time protocol clock domain deviation is the clock corresponding to the precision time protocol clock domain on the communication device side The difference between the first clock and the first clock is the clock indicated by the synchronization information corresponding to the precise time protocol clock domain received by the communication device.

In a possible design manner, the first clock status information includes whether the clock synchronization status of the precise time protocol clock domain is abnormal, and the communication device 1101 also includes a processing module 1103. The processing module 1103 is used to determine the first clock status information according to the precision time protocol clock domain deviation.

Optionally, the communication device 1100 may also include a storage module (not shown in FIG. 11), which stores programs or instructions. When the processing module 1102 executes the program or instruction, the communication device 1100 can perform the functions of the first device or the second device in the communication methods described in FIG. 6, FIG. 7, and FIG. 8.

It should be noted that the communication device 1100 may be the first device or the second device, or may be disposed on the third device. The chip (system) or other components or components of a device or a second device are not limited in this application.

In addition, the technical effects of the communication device 1100 can be referred to the technical effects of the communication methods shown in FIG. 6, FIG. 7, and FIG. 8, which will not be described again here.

An embodiment of the present application provides a communication system. The communication system includes a first core network element, a first device and a second device. Alternatively, the communication system includes a first core network element, a first device and a first access network device.

Among them, the first core network element is used to perform the actions of the first core network element in the above method embodiment, the first device is used to perform the actions of the first device in the above method embodiment, and the second device is used to perform the above method. For the actions of the second device in the embodiment, the first access network device is used to perform the actions of the first access network device in the above method embodiment. The specific execution method and process can be referred to the above method embodiment, and will not be described again here.

Embodiments of the present application provide a chip system, which includes a logic circuit and an input/output port. The logic circuit can be used to implement the processing function involved in the communication method provided by the embodiment of the present application, and the input/output port can be used for the transceiver function involved in the communication method provided by the embodiment of the present application.

For example, the input port can be used to implement the receiving function involved in the communication method provided by the embodiment of the present application, and the output port can be used to implement the sending function involved in the communication method provided by the embodiment of the application.

For example, the processor in the communication device 900 may be used to perform, for example, but not limited to, baseband related processing, and the transceiver in the communication device 900 may be used to perform, for example, but not limited to, radio frequency transceiver. The above-mentioned devices may be arranged on separate chips, or at least part or all of them may be arranged on the same chip. For example, processors can be further divided into analog baseband processors and digital baseband processors. Among them, the analog baseband processor can be integrated with the transceiver on the same chip, and the digital baseband processor can be set on an independent chip. With the continuous development of integrated circuit technology, more and more devices can be integrated on the same chip. For example, a digital baseband processor can be combined with a variety of application processors (such as but not limited to graphics processors, multimedia processors, etc.) Integrated on the same chip. Such a chip can be called a system on chip. Whether each device is independently installed on different chips or integrated on one or more chips often depends on the specific needs of product design. The embodiments of the present invention do not limit the specific implementation forms of the above devices.

In a possible design, the chip system further includes a memory, which is used to store program instructions and data for implementing functions involved in the communication method provided by the embodiments of the present application.

Embodiments of the present application provide a computer-readable storage medium. The computer-readable storage medium stores computer programs or instructions. When the computer program or instructions are run on a computer, the communication method provided by the embodiments of the present application is executed.

An embodiment of the present application provides a computer program product. The computer program product includes: a computer program or instructions. When the computer program or instructions are run on a computer, the communication method provided by the embodiment of the present application is executed.

It should be understood that the processor in the embodiment of the present application can be a central processing unit (CPU), and the processor can also be other general-purpose processors, digital signal processors (DSP), special-purpose integrated processors, etc. Circuit (application specific integrated circuit, ASIC), off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

It should also be understood that the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Among them, non-volatile memory can be read-only memory (ROM), programmable ROM (PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically removable memory. Erase electrically programmable read-only memory (EPROM, EEPROM) or flash memory. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of illustration, but not limitation, many forms of random access memory (RAM) are available, such as static random access memory (static RAM (SRAM)), dynamic random access memory (DRAM), synchronous dynamic random access memory (RAM) Access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory access memory (synchlink DRAM, SLDRAM) and direct memory bus random access memory (direct rambus RAM, DR RAM).

The above embodiments may be implemented in whole or in part by software, hardware (such as circuits), firmware, or any other combination. When implemented using software, the above-described embodiments may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on the computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another, e.g., the computer instructions may be transferred from a website, computer, server, or data center Transmit to another website, computer, server or data center through wired (such as infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that a computer can access, or a data storage device such as a server or a data center that contains one or more sets of available media. The usable media may be magnetic media (eg, floppy disk, hard disk, tape), optical media (eg, DVD), or semiconductor media. The semiconductor medium may be a solid state drive.

It should be understood that the term "and/or" in this article is only an association relationship describing related objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A alone exists, and A and B exist simultaneously. , there are three cases of B alone, where A and B can be singular or plural. In addition, the character "/" in this article generally indicates that the related objects are an "or" relationship, but it may also indicate an "and/or" relationship. For details, please refer to the previous and later contexts for understanding.

In this application, "at least one" refers to one or more, and "plurality" refers to two or more. "At least one of the following" or similar expressions thereof refers to any combination of these items, including any combination of a single item (items) or a plurality of items (items). For example, at least one of a, b, or c can mean: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c can be single or multiple .

It should be understood that in the various embodiments of the present application, the size of the sequence numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its functions and internal logic, and should not be used in the embodiments of the present application. The implementation process constitutes any limitation.

Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented with electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Specialize Skilled artisans may implement the described functionality using different methods for each specific application, but such implementations should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the systems, devices and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be described again here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or they may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit.

If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program code. .

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any person familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application. should be covered by the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

A communication method, characterized in that it is applied to a first core network element and includes:

Receive first clock status information from the first device; wherein the first clock status information is used to indicate the clock synchronization status of the Precision Time Protocol clock domain;

Receive second clock status information from the second device; wherein the second clock status information is used to indicate the clock synchronization status of the precision time protocol clock domain; both the first device and the second device support obtaining Synchronization information corresponding to the internal clock domain of the communication system and synchronization information corresponding to the precise time protocol clock domain; the first device is a network-side adapter, and the second device is a device-side adapter; or, the first device is a user plane network element, and the second device is a first terminal device;

According to the first clock status information and the second clock status information, the clock domain in which the clock synchronization status is abnormal is determined from the internal clock domain of the communication system and the precise time protocol clock domain.
The communication method according to claim 1, characterized in that the clock domain port state of the first device is a slave clock state, the clock domain port state of the second device is a master clock state, and the clock domain port state of the second device is a master clock state. A clock status information and the second clock status information, determining the clock domain in which the clock synchronization status is abnormal from the internal clock domain of the communication system and the precise time protocol clock domain, including:

If the first clock status information indicates that there is no abnormality in the clock synchronization status of the precise time protocol clock domain, and the second clock status information indicates that the clock synchronization status of the precise time protocol clock domain is abnormal, then it is determined that the clock synchronization status of the precise time protocol clock domain is abnormal. The clock synchronization status of the internal clock domain of the communication system is abnormal; or,

If the first clock status information indicates that the clock synchronization status of the precise time protocol clock domain is abnormal, it is determined that the clock synchronization status of the precise time protocol clock domain is abnormal.
The communication method according to claim 1, characterized in that the clock domain port state of the second device is a slave clock state, the clock domain port state of the first device is a master clock state, and the clock domain port state of the second device is a master clock state. A clock status information and the second clock status information, determining the clock domain in which the clock synchronization status is abnormal from the internal clock domain of the communication system and the precise time protocol clock domain, including:

If the second clock status information indicates that there is no abnormality in the clock synchronization status of the precise time protocol clock domain, and the first clock status information indicates that the clock synchronization status of the precise time protocol clock domain is abnormal, then it is determined that the communication system The clock synchronization status of the internal clock domain is abnormal; or,

If the second clock status information indicates that the clock synchronization status of the precise time protocol clock domain is abnormal, it is determined that the clock synchronization status of the precise time protocol clock domain is abnormal.
A communication method, characterized in that it is applied to a first core network element and includes:

Receive first clock status information from the first device; wherein the first clock status information is used to indicate the clock synchronization status of the precision time protocol clock domain, and the first device supports obtaining synchronization information corresponding to the internal clock domain of the communication system Synchronization information corresponding to the precise time protocol clock domain;

When the clock domain port status of the first device is in the main clock state, and the first clock status information indicates that the clock synchronization status of the precision time protocol clock domain is abnormal, request the first access network device The clock synchronization status of the internal clock domain of the communication system;

Receive the clock synchronization status of the internal clock domain of the communication system from the first access network device;

According to the clock synchronization status of the internal clock domain of the communication system, the clock domain in which the clock synchronization status is abnormal is determined from the internal clock domain of the communication system and the precise time protocol clock domain.
The communication method according to claim 4, characterized in that, according to the clock synchronization state of the internal clock domain of the communication system, clock synchronization is determined from the internal clock domain of the communication system and the precision time protocol clock domain. Clock domains with abnormal status include:

If there is no abnormality in the clock synchronization state of the internal clock domain of the communication system, it is determined that the clock synchronization state of the precise time protocol clock domain is abnormal.
The communication method according to claim 4, characterized in that, according to the clock synchronization state of the internal clock domain of the communication system, clock synchronization is determined from the internal clock domain of the communication system and the precision time protocol clock domain. Clock domains with abnormal status include:

If the clock synchronization state of the internal clock domain of the communication system is abnormal, it is determined that the clock synchronization state of the internal clock domain of the communication system is abnormal.
The communication method according to any one of claims 1-6, characterized in that the method further includes:

When the clock synchronization state of the internal clock domain of the communication system is abnormal, obtain information of the first access network device; wherein the first access network device is the access network device corresponding to the internal clock domain of the communication system. network equipment.
The communication method according to claim 7, wherein the obtaining information of the first access network device includes:

Send a first request message to the mobility management network element; wherein the first request message includes the identification of the terminal device corresponding to the device-side adapter or the identification of the first terminal device, and the first request message is used to request the Information about the terminal device corresponding to the device-side adapter or the access network device connected to the first terminal device;

Receive information from the first access network device of the mobility management network element; wherein the first access network device is a terminal device corresponding to the device side adapter or the first terminal device access access network equipment.
The communication method according to claim 7, characterized in that the first core network element is a delay clock network element, and the obtaining the information of the first access network device includes:

Send a second request message to the session management network element; wherein the second request message includes the identification of the first terminal device or the port identification of the device-side adapter, and the second request message is used to request the first terminal device , or information about the access network equipment connected to the terminal equipment corresponding to the device-side adapter;

Receive information from the first access network device of the session management network element; wherein the first access network device is accessed by a terminal device corresponding to the first terminal device or the device-side adapter. Access network equipment.
The communication method according to claim 7, characterized in that the first core network element is a session management network element, and the obtaining the information of the first access network device includes:

Obtain the information of the first access network device according to the identifier of the first terminal device or the port identifier of the device-side adapter; wherein the first access network device is the first terminal device or the port identifier of the device-side adapter. The access network equipment that the terminal equipment corresponding to the device-side adapter is connected to.
The communication method according to any one of claims 1-10, characterized in that the method further includes:

Receive a clock status notification request from an application network element; wherein the clock status notification request includes an identification of the second terminal device, and the clock status notification request is used to request a clock synchronization status of the second terminal device.
The communication method according to claim 11, characterized in that the method further includes:

According to the identification of the second terminal device, first clock abnormality information is sent to the second terminal device; wherein the first clock abnormality information is used to indicate the clock domain in which the clock synchronization state is abnormal, and the third two The access network device to which the terminal device is connected is the first access network device.
The communication method according to any one of claims 1-12, characterized in that the method further includes:

Send a first clock status request to the first device; wherein the first clock status request includes an identification of the Precision Time Protocol clock domain, and the first clock status request is used to request the Precision Time Protocol clock domain clock synchronization status.
The communication method according to any one of claims 1-13, characterized in that the method further includes:

Send a second clock status request to the second device; wherein the second clock status request includes the identification of the precise time protocol clock domain, and the second clock status request is used to request the precise time protocol clock domain clock synchronization status.
The communication method according to any one of claims 1 to 14, characterized in that the first clock status information includes: whether the clock synchronization status of the precision time protocol clock domain is abnormal, and/or the precision time protocol clock Domain deviation; the precision time protocol clock domain deviation is the difference between the clock corresponding to the precision time protocol clock domain on the first device side and the first clock, and the first clock is the precision time protocol clock domain The clock indicated by the corresponding synchronization information.
The communication method according to claim 15, wherein the first clock status information further includes: information about the first access network device corresponding to the internal clock domain of the communication system, and/or information about the internal clock domain of the communication system. Check whether the clock synchronization status of the clock domain is abnormal.
The communication method according to any one of claims 1 to 16, characterized in that the second clock status information includes: whether the clock synchronization status of the precision time protocol clock domain is abnormal, and/or the precision time protocol clock Domain deviation; the precision time protocol clock domain deviation is the difference between the clock corresponding to the precision time protocol clock domain on the second device side and the first clock, and the first clock is the precision time protocol clock domain The clock indicated by the corresponding synchronization information.
The communication method according to claim 17, wherein the second clock status information further includes: information about the first access network device corresponding to the internal clock domain of the communication system, and/or information about the internal clock domain of the communication system. Check whether the clock synchronization status of the clock domain is abnormal.
A communication method, characterized in that it is applied to communication equipment, including:

Receive a first clock status request from a first core network element; wherein the first clock status request includes an identification of a Precision Time Protocol clock domain, and the first clock status request is used to request the Precision Time Protocol clock domain clock synchronization status;

Send the first clock status information to the first core network element; wherein the first clock status information includes: whether the clock synchronization status of the precision time protocol clock domain is abnormal, and/or the precision time protocol clock Domain deviation. The precision time protocol clock domain deviation is the difference between the clock corresponding to the precision time protocol clock domain on the communication device side and the first clock. The first clock is the clock received by the communication device. The clock indicated by the synchronization information corresponding to the precise time protocol clock domain.
The communication method according to claim 19, wherein the first clock status information includes whether the clock synchronization status of the precision time protocol clock domain is abnormal, and the method further includes:

The first clock status information is determined based on the precision time protocol clock domain deviation.
The communication method according to claim 20, wherein determining the first clock status information according to the precision time protocol clock domain deviation includes:

If the precision time protocol clock domain deviation is greater than a first threshold, the first clock status information indicates that the synchronization status of the precision time protocol clock domain is abnormal; or,

If the precision time protocol clock domain deviation is less than or equal to the first threshold, then the first clock status information indicates that the synchronization state of the precision time protocol clock domain is normal.
The communication method according to claim 19 or 20, wherein the first clock status information also includes whether the clock synchronization status of the internal clock domain of the communication system is abnormal, and the method further includes:

The first clock status information is determined according to the internal clock domain deviation of the communication system; wherein the internal clock domain deviation of the communication system is the difference between the clock corresponding to the internal clock domain of the communication system on the communication device side and the second clock The second clock is the clock indicated by the synchronization information corresponding to the internal clock domain of the communication system received by the communication device.
The communication method according to any one of claims 19 to 22, characterized in that the first clock status information further includes: information of the first access network device corresponding to the internal clock domain of the communication system.
The communication method according to any one of claims 19 to 23, characterized in that the communication device is a network side adapter, a device side adapter, a user plane network element, or a first terminal device.
A communication device, characterized in that the communication device includes a unit or module for executing the method according to any one of claims 1-18.
A communication device, characterized in that the communication device includes a unit or module for executing the method according to any one of claims 19-24.
A communication device, characterized in that the communication device includes: a processor; the processor is used to execute the communication method according to any one of claims 1-18.
A communication device, characterized in that the communication device includes: a processor; the processor is configured to execute the communication method according to any one of claims 19-24.
A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program or instructions, and when the computer program or instructions are run on a computer, the computer program or instructions enable any one of claims 1-24 The described communication method is executed.
A computer program product, characterized in that the computer program product includes: a computer program or instructions that, when run on a computer, enable the communication as described in any one of claims 1-24 The method is executed.