Information interaction method and apparatus and readable storage medium

Abstract

The present application relates to the field of wireless communications, is applied to a NR or 6G protocol framework, can also be applied to a sidelink communication scenario, and in particular relates to an information interaction method and apparatus and a readable storage medium. The method comprises: a first device determines a first PDC type on the basis of its own requirement or state, and sends first information to a second device, the first information being used for indicating the first PDC type; the first device receives second information used for executing PDC and reference time information, the second information corresponding to the first PDC type; the first device performs time synchronization with the second device on the basis of the reference time information and the second information. By means of the embodiments of the present application, a PDC type can be determined in a more real-time and reasonable manner, thereby improving the reliability of the device supporting TSN / TSC.

Description

Information interaction method, device and readable storage medium

[0001] This application claims priority to the Chinese patent application with application number 202311135686.0 filed with the State Intellectual Property Office of China on August 31, 2023, and priority to the Chinese patent application with the invention name “Information Interaction Method, Device and Readable Storage Medium”, all contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of wireless communication technologies, and in particular to an information interaction method, device, and readable storage medium. Background Art

[0003] The fifth generation (5G) system supports time-sensitive networking (TSN) or time-sensitive communications (TSC). TSN / TSC requires precise time synchronization between the base station and user equipment (UE). The base station can provide time synchronization to the UE to ensure time synchronization between the two. For example, the base station sends reference time information corresponding to a reference time point to the UE based on the 5GS clock (5G internal system clock). Because wireless signal transmission will bring a certain propagation delay, the propagation delay increases with the distance of wireless signal transmission. Therefore, when performing time synchronization, it is necessary to consider the propagation delay caused by wireless signal propagation and compensate for it to achieve more accurate time synchronization.

[0004] Currently, two types of propagation delay compensation (PDC) (or PDC schemes) are supported: round trip time (RTT)-based PDC and timing advance (TA)-based PDC. The base station can enable RTT-based PDC or TA-based PDC based on information provided by the core network. Generally speaking, different types of PDC can achieve different time synchronization accuracies. For example, RTT-based PDC has higher time synchronization accuracy than TA-based PDC.

[0005] Currently, the PDC type is not determined in real time, resulting in low reliability of device support for TSN / TSC.

[0006] Summary of the Invention

[0007] The embodiments of the present application provide an information interaction method, apparatus, and readable storage medium, which can determine the PDC type in real time, thereby improving the reliability of the device supporting TSN / TSC.

[0008] The present application is introduced below from different aspects. It should be understood that the implementation methods and beneficial effects of the following different aspects can be referenced to each other.

[0009] In a first aspect, the present application provides an information interaction method, which is applied to a wireless communication system, such as wireless communication between a base station and a UE, or wireless communication between UEs, or wireless communication between base stations. The method includes: a first device determines a first PDC type and sends first information to a second device, where the first information is used to indicate the first PDC type; the first device receives second information and reference time information for executing PDC, where the second information corresponds to the first PDC type; the first device performs time synchronization with the second device based on the reference time information and the second information. The reference time information may be time information corresponding to a reference time point. For an explanation of the reference time point, please refer to the description below and will not be described in detail here.

[0010] The first device may be a UE, and the second device may be a base station or a UE. It can be understood that when the first device and the second device are both UEs, the first device and the second device are different UEs.

[0011] The first device of the present application determines the PDC type by itself and requests or indicates the PDC type to the second device, so that the PDC type can match the status or needs of the first device more in real time and more reasonably. Then, the first device synchronizes time with the second device based on the received second information and reference time information, which can improve the reliability of TSN / TSC support between the first device and the second device.

[0012] In conjunction with the first aspect, in one possible implementation, the first device determining the first PDC type includes: the first device determining the first PDC type based on preset rules and its own needs. The preset rules may include, but are not limited to, one or more of the following: a correspondence between service information and PDC type, a correspondence between location information and PDC type, or a correspondence between available resources and PDC type.

[0013] Exemplarily, the first device determines the first PDC type based on a correspondence between service information and the PDC type, as well as service information of the first device. For example, the service information may include, but is not limited to, one or more of the following: a service type, or a quality of service (QoS) flow. The correspondence between the QoS flow and the PDC type may be a correspondence between a QoS parameter associated with the QoS flow and the PDC type.

[0014] In some scenarios, when there are multiple service information, the service information of the first device may include one or more of the following: service information with the highest priority, service information with the smallest packet delay budget (PDB), or service information with the highest time synchronization accuracy requirement.

[0015] In some scenarios, when there are multiple business information, the first device can determine multiple PDC types based on the correspondence between the business information and the PDC type, as well as the multiple business information, and determine the first PDC type from these multiple PDC types. The first PDC type is the PDC type with the highest time synchronization accuracy requirement among these multiple PDC types.

[0016] Exemplarily, the first device determines the first PDC type based on the correspondence between the location information and the PDC type and the location information of the first device. The location information may be one or more of the following: longitude and latitude information, cell information (one or more cells), zone information, etc., which is not limited in this application.

[0017] Exemplarily, the first device determines the first PDC type based on a correspondence between available resources and PDC types, as well as the available resources of the first device. The available resources may include, but are not limited to, available communication resources and / or available computing resources. For example, available communication resources may refer to resources available for transmission, such as frequency domain resources, time domain resources, or time-frequency domain resources. For example, available computing resources may refer to one or more of storage resources, hardware resources, and software resources available for computing.

[0018] In conjunction with the first aspect, in one possible implementation, when the first PDC type is (or belongs to) an RTT-based PDC type, the second information is used to indicate a receive-transmit time difference of the second device. When the first PDC type is a TA-based PDC type, the second information is used to indicate a TA value.

[0019] In conjunction with the first aspect, in one possible implementation, the second information is used to indicate the receive-transmit time difference of the second device, or the first PDC type is (belongs to) an RTT-based PDC type. The first device performs time synchronization with the second device based on the reference time information and the second information, including: the first device performs time synchronization with the second device based on the reference time information, the second information, and the receive-transmit time difference of the first device. The second information (or the receive-transmit time difference of the second device) and the receive-transmit time difference of the first device can be used to perform PDC or calculate propagation delay.

[0020] In combination with the first aspect, in a possible implementation, the above-mentioned first PDC type is different from the second PDC type. The second PDC type may be the PDC type corresponding to the current first device or second device executing PDC. In other words, the second PDC type may be the PDC type corresponding to the current second device performing time synchronization with the first device, and the first PDC type may be the PDC type corresponding to the second device performing time synchronization with the first device after the update. In some scenarios, when the location of the first device changes or the business needs of the first device change, the first device may determine to update from the original second PDC type to the first PDC type based on the changed location or business needs. Exemplarily, the second PDC type may be obtained before the location or business needs of the first device change, and the first PDC type may be determined after the location or business needs of the first device change.

[0021] This application can switch the PDC type more timely when the location or business demand of the first device changes, thereby improving the reliability of TSN / TSC.

[0022] In combination with the first aspect, in one possible implementation, after the first device sends the first information, the method also includes: the first device receives third information from the second device, the third information is used to indicate a reference signal, the reference signal corresponds to the above-mentioned first PDC type, and the reference signal is used to measure the reception-transmission time difference of the first device, or to determine TA.

[0023] Exemplarily, when the first PDC type is (belongs to) an RTT-based PDC type, the reference signal may be any one of the following: a synchronization signal and a physical broadcast channel block (SSB), a positioning reference signal (PRS), a tracking reference signal (TRS), a channel state information reference signal (CSI-RS), etc.

[0024] Exemplarily, when the first PDC type is a TA-based PDC type, the reference signal may be a sounding reference signal (SRS) or a random access preamble signal.

[0025] For example, different PDC types may correspond to different reference signals, and one PDC type may correspond to one or more reference signals. The time synchronization accuracy measured by different reference signals may also be different.

[0026] In combination with the first aspect, in a possible implementation, after the first device sends the first information, the method further includes: the first device receives response information from the second device, and the response information can be a response to the above-mentioned first information, used to confirm the use of the above-mentioned first PDC type for PDC.

[0027] In the second aspect, the present application provides an information interaction method, which is applied to a wireless communication system, such as wireless communication between a base station and a UE, or wireless communication between UEs, or wireless communication between base stations. The method includes: a second device receives first information from a first device, where the first information is used to indicate a first PDC type; the second device determines second information for executing PDC based on the first PDC type, and sends the second information to the first device; the second device sends reference time information to the first device, where the reference time information and the second information can be used for time synchronization between the first device and the second device. The reference time information can be time information corresponding to a reference time point. For an explanation of the reference time point, please refer to the description below and will not be described in detail here.

[0028] The first device may be a UE, and the second device may be a base station or a UE. It can be understood that when the first device and the second device are both UEs, the first device and the second device are different UEs.

[0029] In conjunction with the second aspect, in one possible implementation, when the first PDC type is (or belongs to) an RTT-based PDC type, the second information is used to indicate a receive-transmit time difference of the second device. When the first PDC type is a TA-based PDC type, the second information is used to indicate a TA value.

[0030] In conjunction with the second aspect, in a possible implementation, the above-mentioned first PDC type is different from the second PDC type. The second PDC type may be the PDC type corresponding to the current first device or second device executing PDC. In other words, the second PDC type may be the PDC type corresponding to the current second device performing time synchronization with the first device, and the first PDC type may be the PDC type corresponding to the second device performing time synchronization with the first device after the update. In some scenarios, when the location of the first device changes or the business needs of the first device change, the first device may determine to update from the original second PDC type to the first PDC type based on the changed location or business needs. Exemplarily, the second PDC type may be obtained before the location or business needs of the first device change, and the first PDC type may be determined after the location or business needs of the first device change.

[0031] In combination with the second aspect, in one possible implementation, after the second device receives the first information, the method further includes: the second device sends third information to the first device, the third information is used to indicate a reference signal, the reference signal is determined based on the first PDC type, and the reference signal is used to measure the receive-transmit time difference of the first device, or is used for the second device to determine TA.

[0032] Exemplarily, when the first PDC type is (belongs to) an RTT-based PDC type, the reference signal may be any one of the following: SSB, PRS, TRS, CSI-RS, etc.

[0033] Exemplarily, when the first PDC type is a TA-based PDC type, the reference signal may be an SRS, or a random access preamble signal.

[0034] For example, different PDC types may correspond to different reference signals, and one PDC type may correspond to one or more reference signals. The time synchronization accuracy measured by different reference signals may also be different.

[0035] In combination with the second aspect, in a possible implementation, after the second device receives the first information, the method further includes: the second device sends response information to the first device, and the response information can be a response to the above-mentioned first information, used to confirm the use of the above-mentioned first PDC type for PDC.

[0036] In a third aspect, the present application provides a communication device, which may be a first device or a chip / circuit therein. The communication device is configured to perform the method of the first aspect or any possible implementation of the first aspect. The communication device includes a unit capable of performing the method of the first aspect or any possible implementation of the first aspect.

[0037] In a fourth aspect, the present application provides a communication device, which may be a second device or a chip / circuit therein. The communication device is configured to perform the method of the second aspect or any possible implementation of the second aspect. The communication device includes a unit configured to perform the method of the second aspect or any possible implementation of the second aspect.

[0038] In the third or fourth aspect, the communication device may include a transceiver unit and a processing unit. For a detailed description of the transceiver unit and the processing unit, reference may be made to the device embodiments shown below. The beneficial effects of the third to fourth aspects may be referenced to the relevant descriptions of the first and second aspects, and are not further elaborated here.

[0039] In a fifth aspect, the present application provides an information interaction method, which is applied to a wireless communication system, such as wireless communication between a base station and a UE, or wireless communication between UEs, or wireless communication between base stations. The method includes: a first device determines a first PDC type and sends first information to a second device, where the first information is used to indicate the first PDC type; the first device receives reference time information; and the first device synchronizes time with the second device based on the reference time information. The reference time information may be time information corresponding to a reference time point. For an explanation of the reference time point, please refer to the description below and will not be described in detail here.

[0040] The first device may be a UE, and the second device may be a base station or a UE. It can be understood that when the first device and the second device are both UEs, the first device and the second device are different UEs.

[0041] The first device of the present application determines the PDC type by itself and requests or indicates the PDC type to the second device, so that the PDC type can match the status or needs of the first device more in real time and more reasonably. Then, the first device synchronizes time with the second device based on the received reference time information, which can improve the reliability of TSN / TSC support between the first device and the second device.

[0042] In conjunction with the fifth aspect, in one possible implementation, the first device determining the first PDC type includes: the first device determining the first PDC type based on preset rules and its own needs. The preset rules may include, but are not limited to, one or more of the following: a correspondence between service information and PDC type, a correspondence between location information and PDC type, or a correspondence between available resources and PDC type.

[0043] Exemplarily, the first device determines the first PDC type based on a correspondence between service information and the PDC type, as well as service information of the first device. For example, the service information may include, but is not limited to, one or more of the following: service type, or QoS flow. The correspondence between the QoS flow and the PDC type may be a correspondence between QoS parameters associated with the QoS flow and the PDC type.

[0044] In some scenarios, when there are multiple service information, the service information of the first device may include one or more of the following: service information with the highest priority, service information with the smallest PDB, or service information with the highest time synchronization accuracy requirement.

[0045] In some scenarios, when there are multiple business information, the first device can determine multiple PDC types based on the correspondence between the business information and the PDC type, as well as the multiple business information, and determine the first PDC type from these multiple PDC types. The first PDC type is the PDC type with the highest time synchronization accuracy requirement among these multiple PDC types.

[0046] Exemplarily, the first device determines the first PDC type based on the correspondence between the location information and the PDC type and the location information of the first device. The location information may be one or more of the following: longitude and latitude information, cell information (one or more cells), zone information, etc., which is not limited in this application.

[0047] Exemplarily, the first device determines the first PDC type based on a correspondence between available resources and PDC types, as well as the available resources of the first device. The available resources may include, but are not limited to, available communication resources and / or available computing resources. For example, available communication resources may refer to resources available for transmission, such as frequency domain resources, time domain resources, or time-frequency domain resources. For example, available computing resources may refer to one or more of storage resources, hardware resources, and software resources available for computing.

[0048] In combination with the fifth aspect, in a possible implementation manner, the first PDC type is an RTT-based PDC type, or the first PDC type is a TA-based PDC type.

[0049] In conjunction with the fifth aspect, in one possible implementation, the first PDC type is an RTT-based PDC type. After the first device sends the first information, the method further includes: the first device receiving fourth information from the second device, the fourth information being used to request a receive-transmit time difference for the first device; and the first device sending fifth information to the second device, the fifth information being used to indicate the receive-transmit time difference for the first device.

[0050] In combination with the fifth aspect, in a possible implementation, after the first device sends the first information, the method also includes: the first device receives third information from the second device, the third information is used to indicate a reference signal, the reference signal corresponds to the above-mentioned first PDC type, and the reference signal is used to measure the reception-transmission time difference of the first device, or to determine TA.

[0051] Exemplarily, when the first PDC type is (belongs to) an RTT-based PDC type, the reference signal may be any one of the following: SSB, PRS, TRS, CSI-RS, etc.

[0052] Exemplarily, when the first PDC type is a TA-based PDC type, the reference signal may be an SRS, or a random access preamble signal.

[0053] For example, different PDC types may correspond to different reference signals, and one PDC type may correspond to one or more reference signals. The time synchronization accuracy measured by different reference signals may also be different.

[0054] In conjunction with the fifth aspect, in a possible implementation, the above-mentioned first PDC type is different from the second PDC type. The second PDC type may be the PDC type corresponding to the current first device or second device executing PDC. In other words, the second PDC type may be the PDC type corresponding to the current second device performing time synchronization with the first device, and the first PDC type may be the PDC type corresponding to the second device performing time synchronization with the first device after the update. In some scenarios, when the location of the first device changes or the business needs of the first device change, the first device may determine to update from the original second PDC type to the first PDC type based on the changed location or business needs. Exemplarily, the second PDC type may be obtained before the location or business needs of the first device change, and the first PDC type may be determined after the location or business needs of the first device change.

[0055] In combination with the fifth aspect, in a possible implementation, after the first device sends the first information, the method further includes: the first device receives response information from the second device, and the response information can be a response to the above-mentioned first information, used to confirm the use of the above-mentioned first PDC type for PDC.

[0056] In a sixth aspect, the present application provides an information interaction method, which is applied to a wireless communication system, such as wireless communication between a base station and a UE, or wireless communication between UEs, or wireless communication between base stations. The method includes: a second device receives first information from a first device, where the first information is used to indicate a first PDC type; the second device performs PDC based on the first PDC type, and sends reference time information passing through the PDC to the first device, where the reference time information is used for time synchronization between the first device and the second device. The reference time information may be time information corresponding to a reference time point. For an explanation of the reference time point, please refer to the description below and will not be described in detail here.

[0057] In conjunction with the sixth aspect, in one possible implementation, the first PDC type is a TA-based PDC type. The second device performs PDC based on the first PDC type, including: the second device performs PDC based on a timing advance TA. For example, the second device uses half of the TA (i.e., TA / 2) as the propagation delay.

[0058] In conjunction with the sixth aspect, in one possible implementation, the first PDC type is (or belongs to) an RTT-based PDC type. The second device performs PDC based on the first PDC type, including: the second device performs PDC based on a receive-transmit time difference between the first device and the second device. For example, the second device uses half the difference between the receive-transmit time difference between the first device and the second device as the propagation delay.

[0059] Exemplarily, before the second device performs PDC based on the first PDC type, the method also includes: the second device sends fourth information to the first device, the fourth information is used to request the receive-send time difference of the first device; the second device receives fifth information from the first device, the fifth information is used to indicate the receive-send time difference of the first device.

[0060] In combination with the sixth aspect, in a possible implementation, after the second device receives the first information, the method also includes: the second device sends third information to the first device, the third information is used to indicate a reference signal, the reference signal is determined based on the first PDC type, and the reference signal is used to measure the receive-transmit time difference of the first device, or used for the second device to determine TA.

[0061] Exemplarily, when the first PDC type is (belongs to) an RTT-based PDC type, the reference signal may be any one of the following: SSB, PRS, TRS, CSI-RS, etc.

[0062] Exemplarily, when the first PDC type is a TA-based PDC type, the reference signal may be an SRS, or a random access preamble signal.

[0063] For example, different PDC types may correspond to different reference signals, and one PDC type may correspond to one or more reference signals. The time synchronization accuracy measured by different reference signals may also be different.

[0064] In conjunction with the sixth aspect, in a possible implementation, the above-mentioned first PDC type is different from the second PDC type. The second PDC type may be the PDC type corresponding to the current first device or second device executing PDC. In other words, the second PDC type may be the PDC type corresponding to the current second device performing time synchronization with the first device, and the first PDC type may be the PDC type corresponding to the second device performing time synchronization with the first device after the update. In some scenarios, when the location of the first device changes or the business needs of the first device change, the first device may determine to update from the original second PDC type to the first PDC type based on the changed location or business needs. Exemplarily, the second PDC type may be obtained before the location or business needs of the first device change, and the first PDC type may be determined after the location or business needs of the first device change.

[0065] In combination with the sixth aspect, in a possible implementation, after the second device receives the first information, the method further includes: the second device sends response information to the first device, and the response information can be a response to the above-mentioned first information, used to confirm the use of the above-mentioned first PDC type for PDC.

[0066] In a seventh aspect, the present application provides a communication device, which may be a first device or a chip / circuit therein. The communication device is configured to perform the method of the fifth aspect or any possible implementation of the fifth aspect. The communication device includes a unit configured to perform the method of the fifth aspect or any possible implementation of the fifth aspect.

[0067] In an eighth aspect, the present application provides a communication device, which may be a second device or a chip / circuit therein. The communication device is configured to perform the method of the sixth aspect or any possible implementation of the sixth aspect. The communication device includes a unit configured to perform the method of the sixth aspect or any possible implementation of the sixth aspect.

[0068] In the seventh or eighth aspects, the communication device may include a transceiver unit and a processing unit. For a detailed description of the transceiver unit and the processing unit, reference may be made to the device embodiments shown below. The beneficial effects of the seventh to eighth aspects may be referenced to the relevant descriptions of the fifth and sixth aspects, and are not further elaborated here.

[0069] In a ninth aspect, the present application provides an information interaction method, which is applied to a wireless communication system, such as wireless communication between a base station and a UE, wireless communication between UEs, or wireless communication between base stations. The method includes: a first device receiving first information from a second device, where the first information is used to indicate a first PDC type; and the first device parsing the first information to obtain the first PDC type.

[0070] The first device may be a UE, and the second device may be a base station or a UE. It can be understood that when the first device and the second device are both UEs, the first device and the second device are different UEs.

[0071] In combination with the ninth aspect, in a possible implementation, after the first device receives the first information, the method also includes: the first device receives second information for executing PDC from the second device, and the second information corresponds to the first PDC type; the first device receives reference time information from the second device; and the first device performs time synchronization with the second device based on the reference time information and the second information.

[0072] Exemplarily, when the first PDC type is (or belongs to) an RTT-based PDC type, the second information is used to indicate a receive-send time difference of the second device. When the first PDC type is a TA-based PDC type, the second information is used to indicate a TA value.

[0073] Exemplarily, the second information is used to indicate a receive-transmit time difference of the second device. The first device performs time synchronization with the second device based on the reference time information and the second information, including: the first device performs time synchronization with the second device based on the reference time information, the second information, and the receive-transmit time difference of the first device. The second information (or the receive-transmit time difference of the second device) and the receive-transmit time difference of the first device can be used to perform PDC or calculate propagation delay.

[0074] The first device of the present application determines a propagation delay based on a PDC type, and uses the propagation delay to perform time synchronization with a second device; thus, the reliability of TSN / TSC support between the first device and the second device can be improved.

[0075] In conjunction with the ninth aspect, in one possible implementation, the first PDC type is (or belongs to) an RTT-based PDC type. After the first device receives the first information, the method further includes: the first device receiving fourth information from the second device, the fourth information being used to request a receive-transmit time difference of the first device; the first device sending fifth information to the second device, the fifth information being used to indicate a receive-transmit time difference of the first device; the first device receiving reference time information from the second device; and the first device performing time synchronization with the second device based on the reference time information.

[0076] In conjunction with the ninth aspect, in a possible implementation, the above-mentioned first PDC type is different from the second PDC type. The second PDC type may be the PDC type corresponding to the current first device or second device executing PDC. In other words, the second PDC type may be the PDC type corresponding to the current second device performing time synchronization with the first device, and the first PDC type may be the PDC type corresponding to the time synchronization between the second device and the first device after the update. Exemplarily, the second PDC type may be obtained before the location or service requirements of the first device change, and the first PDC type may be determined after the location or service requirements of the first device change.

[0077] In combination with the ninth aspect, in a possible implementation, after the first device receives the first information, the method also includes: the first device receives third information from the second device, the third information is used to indicate a reference signal, the reference signal corresponds to the first PDC type, and the reference signal is used to measure the receive-transmit time difference of the first device, or to determine TA.

[0078] In a tenth aspect, the present application provides an information interaction method, which is applied to a wireless communication system, such as wireless communication between a base station and a UE, or wireless communication between UEs, or wireless communication between base stations. The method includes: a second device determines a first PDC type based on a preset rule, and sends first information to the first device, where the first information is used to indicate the first PDC type. The preset rule includes one or more of the following: a correspondence between service information and PDC type, a correspondence between location information and PDC type, or a correspondence between available resources and PDC type.

[0079] The second device of the present application determines the PDC type based on preset rules, and clarifies the method for determining the PDC type.

[0080] In combination with the tenth aspect, in a possible implementation method, the second device determines the first PDC type based on a preset rule, including: the second device determines the first PDC type based on the correspondence between business information and PDC type, and the business information of the first device; or, the second device determines the first PDC type based on the correspondence between location information and PDC type, and the location information of the first device; or, the second device determines the first PDC type based on the correspondence between available resources and PDC type, and the available resources of the first device.

[0081] Among them, the service information may include but is not limited to one or more of the following: service type, or quality of service (QoS) flow. The correspondence between the QoS flow and the PDC type may be the correspondence between the QoS parameters associated with the QoS flow and the PDC type. The location information may be one or more of the following: longitude and latitude information, cell information (one or more cells), zone information, etc., which is not limited in this application. Available resources may include but are not limited to: available communication resources and / or available computing resources. For example: available communication resources may refer to resources that can be used for transmission, such as frequency domain resources, or time domain resources, or time-frequency domain resources. For example: available computing resources may refer to one or more of storage resources, hardware resources, and software resources that can be used for computing.

[0082] In some scenarios, when there are multiple service information, the service information of the first device may include one or more of the following: service information with the highest priority, service information with the smallest PDB, or service information with the highest time synchronization accuracy requirement.

[0083] In some scenarios, when there are multiple business information, the first device can determine multiple PDC types based on the correspondence between the business information and the PDC type, as well as the multiple business information, and determine the first PDC type from these multiple PDC types. The first PDC type is the PDC type with the highest time synchronization accuracy requirement among these multiple PDC types.

[0084] The second device of the present application determines the PDC type based on preset rules and the status or requirements of the first device, so that the PDC type can match the status or requirements of the first device more real-time and reasonably, thereby improving the reliability of TSN / TSC support between the first device and the second device.

[0085] In combination with the tenth aspect, in a possible implementation, after the second device sends the first information, the method also includes: the second device sends second information for executing PDC to the first device, and the second information is determined based on the first PDC type; the second device sends reference time information to the first device, and the reference time information and the second information are used for time synchronization between the first device and the second device.

[0086] Exemplarily, when the first PDC type is (or belongs to) an RTT-based PDC type, the second information is used to indicate a receive-send time difference of the second device. When the first PDC type is a TA-based PDC type, the second information is used to indicate a TA value.

[0087] In conjunction with the tenth aspect, in one possible implementation, the first PDC type is (belongs to) an RTT-based PDC class. After the second device sends the first information, the method further includes: the second device sends fourth information to the first device, the fourth information being used to request a receive-send time difference of the first device; the second device receives fifth information from the first device, the fifth information being used to indicate a receive-send time difference of the first device; the second device sends reference time information to the first device, the reference time information being determined based on a receive-send time difference of the first device and a receive-send time difference of the second device, the reference time information being used for time synchronization between the first device and the second device.

[0088] The second device of the present application determines the reference time information based on the receive-send time difference of the first device and the receive-send time difference of the second device, so that after the first device receives the reference time information, it synchronizes time with the second device, which can improve the reliability of TSN / TSC support between the first device and the second device.

[0089] In conjunction with the tenth aspect, in a possible implementation, the above-mentioned first PDC type is different from the second PDC type. The second PDC type may be the PDC type corresponding to the current execution of PDC by the first device or the second device. In other words, the second PDC type may be the PDC type corresponding to the time synchronization performed by the current second device to the first device, and the first PDC type may be the PDC type corresponding to the time synchronization performed by the second device to the first device after the update. Exemplarily, the second PDC type may be obtained before the location or service requirements of the first device change, and the first PDC type may be determined after the location or service requirements of the first device change.

[0090] In combination with the tenth aspect, in a possible implementation, after the second device sends the first information, the method also includes: the second device sends third information to the first device, the third information is used to indicate a reference signal, the reference signal is determined based on the first PDC type, and the reference signal is used to measure the receive-transmit time difference of the first device, or used for the second device to determine TA.

[0091] In an eleventh aspect, the present application provides a communication device, which may be a first device or a chip / circuit therein. The communication device is configured to perform the method of the ninth aspect or any possible implementation of the ninth aspect. The communication device includes a unit configured to perform the method of the ninth aspect or any possible implementation of the ninth aspect.

[0092] In a twelfth aspect, the present application provides a communication device, which may be a second device or a chip / circuit therein. The communication device is configured to perform the method of the tenth aspect or any possible implementation of the tenth aspect. The communication device includes a unit configured to perform the method of the tenth aspect or any possible implementation of the tenth aspect.

[0093] In the eleventh or twelfth aspect, the communication device may include a transceiver unit and a processing unit. For a detailed description of the transceiver unit and the processing unit, reference may be made to the device embodiments described below. The beneficial effects of the eleventh to twelfth aspects may be described with reference to the relevant descriptions of the ninth and tenth aspects, and are not further elaborated here.

[0094] In a thirteenth aspect, the present application provides a communication device, which may include a processor and an interface circuit, and the processor is connected to the interface circuit. Wherein, the interface circuit is used to interact (or receive and send or input and output) information or data, and the processor is used to run program instructions so that the communication device executes the method described in any possible implementation of the first aspect, or the second aspect, or the fifth aspect, or the sixth aspect, or the ninth aspect, or the tenth aspect, or any of the aspects thereof. Wherein, the interface circuit may be a communication interface, or a transceiver. The transceiver may be a radio frequency module in a communication device, or a combination of a radio frequency module and an antenna, or an input and output interface of a chip or circuit.

[0095] In the fourteenth aspect, the present application provides a readable storage medium having program instructions stored thereon, which, when executed on a computer, enables the computer to execute the method described in the first aspect, or the second aspect, or the fifth aspect, or the sixth aspect, or the ninth aspect, or the tenth aspect, or any possible implementation of any one of the aspects therein.

[0096] In the fifteenth aspect, the present application provides a program product comprising program instructions, which, when executed, enables the method described in the first aspect, or the second aspect, or the fifth aspect, or the sixth aspect, or the ninth aspect, or the tenth aspect, or any possible implementation of any one of the aspects therein to be executed.

[0097] In a sixteenth aspect, the present application provides a device, which can be implemented in the form of a chip or in the form of a device, and the device includes a processor. The processor is used to read and execute a program stored in a memory to execute one or more of the above-mentioned first aspect, second aspect, fifth aspect, sixth aspect, ninth aspect, and tenth aspect, or one or more of any possible implementation methods of any aspect thereof. Optionally, the device also includes a memory, which is connected to the processor via a circuit. Further optionally, the device also includes a communication interface, and the processor is connected to the communication interface. The communication interface is used to receive information to be processed, and the processor obtains the information from the communication interface, processes the information, and outputs the processing results through the communication interface. The communication interface can be an input and output interface.

[0098] In a possible implementation, the processor and memory may be physically independent units, or the memory may be integrated with the processor.

[0099] In the seventeenth aspect, the present application provides a communication system, which includes a first device and a second device; the first device is used to execute the method described in the first aspect, the fifth aspect, the ninth aspect, or any possible implementation of any one of the aspects above, and the second device is used to execute the method described in the second aspect, the sixth aspect, the tenth aspect, or any possible implementation of any one of the aspects above.

[0100] The technical effects achieved in the above-mentioned aspects can be referred to each other or to the beneficial effects in the method embodiments shown below, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0101] FIG1 is a simplified schematic diagram of a communication system provided in an embodiment of the present application;

[0102] FIG2 is a schematic diagram of a sidelink communication scenario provided by an embodiment of the present application;

[0103] FIG3 is a schematic diagram of a Sidelink UE-to-Network Relay scenario provided in an embodiment of the present application;

[0104] FIG4 is a schematic diagram of a Sidelink UE-to-UE Relay scenario provided in an embodiment of the present application;

[0105] FIG5 is a schematic diagram of accurate reference time transfer via SIB9 provided in an embodiment of the present application;

[0106] FIG6 is a schematic diagram of delivering precise reference time via downlink information transmission messages according to an embodiment of the present application;

[0107] FIG7 is a schematic diagram of RTT-based propagation delay provided in an embodiment of the present application;

[0108] FIG8a is an RTT-based PDC process on the UE side provided in an embodiment of the present application;

[0109] FIG8 b is a PDC process based on RTT on the base station side provided in an embodiment of the present application;

[0110] FIG9 is a flow chart of an information interaction method according to an embodiment of the present application;

[0111] FIG10 is another flow chart of the information interaction method provided in an embodiment of the present application;

[0112] FIG11 is another flow chart of the information interaction method provided in an embodiment of the present application;

[0113] FIG12 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0114] FIG13 is another schematic structural diagram of a communication device provided in an embodiment of the present application;

[0115] FIG14 is another structural diagram of the communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0116] The technical solutions in the embodiments of the present application will be described clearly and completely below in conjunction with the drawings in the embodiments of the present application.

[0117] In the description of this application, words such as "first" and "second" are only used to distinguish different objects, and do not limit the quantity and execution order, and words such as "first" and "second" do not necessarily limit them to be different. For example, the first information and the second information, the first PDC type and the second PDC type, etc. are only used to distinguish different information, and do not limit their order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally also includes steps or units that are not listed, or optionally also includes other steps or units inherent to these processes, methods, products or devices.

[0118] In the description of this application, unless otherwise specified, " / " means "or", for example, A / B can mean A or B. "And / or" in this article is merely a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, "at least one (item)", "the following one (item) or more (items)" or similar expressions refer to any combination of these items, including any combination of single or plural items (items). For example, at least one item (item) of a, b, or c can mean: a, b, c; a and b; a and c; b and c; or a, b, and c. Among them, a, b, and c can be single or multiple.

[0119] In the description of this application, words such as "exemplary" or "for example" are used to indicate an example, illustration, or description. Any embodiment or design described in this application as "exemplary," "for example," or "for example" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary," "for example," or "for example" is intended to present the relevant concepts in a concrete way.

[0120] It should be understood that in the description of this application, the terms "when," "if," and "if" all refer to the device performing a corresponding action under certain objective circumstances. They do not limit the time, do not require the device to perform a judgment action during implementation, and do not imply any other limitations. Specifically, "the device performing a corresponding action under certain objective circumstances" includes: the device performing the corresponding action under certain objective circumstances can perform the corresponding action only if the objective circumstances are met; or the device performing the corresponding action can perform the corresponding action only if the objective circumstances and other circumstances are met.

[0121] The term "simultaneously" in this application may be understood as at the same time point, within a period of time, or within the same cycle, and may be understood in conjunction with the context.

[0122] Elements used in the singular herein are intended to mean "one or more" rather than "one and only one" unless specifically stated otherwise.

[0123] Additionally, the terms "system" and "network" are often used interchangeably herein.

[0124] It should be understood that in the various embodiments of the present application, "A corresponds to B," "A corresponds to B," "A corresponds to B," or similar expressions indicate that B is associated with A and B can be determined based on A. Determining B based on A does not mean determining B based solely on A; B can also be determined based on A and / or other information.

[0125] The technical solutions of the embodiments of the present application can be applied to various wireless communication systems, such as: long term evolution (LTE) systems, worldwide interoperability for microwave access (WiMAX) communication systems, fifth generation (5G) systems, such as new radio access technology (NR), next generation wireless local area network systems, networks that integrate multiple systems, Internet of Things systems, Internet of Vehicles systems, open radio access networks (O-RAN) systems, and future communication systems such as sixth generation (6G) systems.

[0126] In one possible implementation, a communication system includes communication devices, and the communication devices can wirelessly communicate using air interface resources. The communication devices may include network devices and terminal devices. Network devices may also be referred to as base station devices or access network devices. Air interface resources may include at least one of time domain resources, frequency domain resources, code resources, and space resources. In this application, "at least one" may also be described as "one or more," and "many" may be two, three, four, or more, without limitation in this application.

[0127] It should be understood that the system architecture and application scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field can know that with the evolution of the system architecture or application scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0128] Referring to Figure 1, Figure 1 is a simplified schematic diagram of a communication system provided in an embodiment of the present application. As shown in Figure 1, the communication system includes a radio access network 100. The radio access network 100 can be a next-generation (e.g., 6G or higher) radio access network, or a traditional (e.g., 5G, 4G, 3G, or 2G) radio access network. Among them, one or more terminal devices (120a-120j, collectively referred to as 120) can be connected to each other or to one or more network devices (110a, 110b, collectively referred to as 110) in the radio access network 100. The terminal device can be connected to the network device in a wireless manner, and the terminal devices and the network devices can be connected to each other in a wired or wireless manner. It can be understood that Figure 1 is only a schematic diagram, and the communication system can also include other devices, such as core network devices, wireless relay devices, and / or wireless backhaul devices, which are not drawn in Figure 1.

[0129] In practical applications, the communication system may include multiple network devices (also called access network devices) and multiple terminal devices at the same time. A network device may serve one or more terminal devices at the same time. A terminal device may also access one or more network devices at the same time. The embodiments of the present application do not limit the number of terminal devices and network devices included in the communication system.

[0130] A network device may be an entity on the network side for transmitting or receiving signals, such as a base station (BS). A BS may be a device deployed in a wireless access network that can communicate wirelessly with a terminal. Base stations may have various forms, such as macro base stations, micro base stations, relay stations, and access points. For example, the base stations involved in the embodiments of the present application may be base stations in 5G, base stations in sixth-generation (6G) mobile communication systems, access network devices or modules of access network devices in open radio access networks (O-RAN) systems, base stations in future mobile communication systems, or access nodes in WiFi systems, or evolved base stations (evolved node B, eNB) in LTE, etc. Among them, the base station in 5G can also be called a transmission reception point (TRP) or a 5G base station (next-generation node B, gNB). Base station can also be replaced with the following names, such as: wireless access point, node B (nodeB), transmitting point (TP), master station MeNB, secondary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), centralized unit (CU), distributed unit (DU), positioning node, IAB donor, etc.

[0131] The network device in the embodiments of the present application may be an integrated base station, or may be a base station including a centralized unit (CU) and / or a distributed unit (DU). A base station including a CU and a DU may also be referred to as a base station with separate CU and DU, such as a base station including a gNB-CU and a gNB-DU. The CU may also be separated into a CU control plane (CU-CP) and a CU user plane (CU-UP), such as a base station including a gNB-CU-CP, a gNB-CU-UP, and a gNB-DU. Alternatively, the network device in the embodiments of the present application may also be an antenna unit (RU). Alternatively, the network device in the embodiments of the present application may also be an open radio access network (O-RAN) architecture, etc. The embodiments of the present application do not limit the specific deployment method of the network device. For example, when the network device is an O-RAN architecture, the network device shown in the embodiments of the present application may be an access network device in the O-RAN, such as a combination of one or more of a CU, DU, or RU, or a module in the access network device. In the ORAN system, CU may also be referred to as open (O)-CU, CU-CP may also be referred to as O-CU-CP, CU-UP may also be referred to as O-CU-UP, DU may also be referred to as O-DU, and RU may also be referred to as O-RU.

[0132] In the embodiments of the present application, the device for realizing the function of the network device may be a network device; or it may be a device capable of supporting the network device to realize the function, such as a chip system, a communication module, or a modem, etc., which may be installed in the network device. In the technical solutions provided in the embodiments of the present application, the device for realizing the function of the network device is a network device, and the network device is a base station as an example to describe the technical solutions provided in the embodiments of the present application. The base station may support networks with the same or different access technologies. The embodiments of the present application do not limit the specific technology and specific device form adopted by the network device.

[0133] Terminal devices can be called terminals, user equipment (UE), mobile stations (MS), or mobile terminals (MT). They are devices with wireless transceiver capabilities. They can be deployed on land, indoors or outdoors, handheld or vehicle-mounted; on water (such as ships); or in the air (such as airplanes, balloons, and satellites). Terminal devices can be used to connect people, objects, and machines. The terminal device 120 can be widely used in various scenarios, such as cellular communication, device-to-device (D2D), vehicle-to-everything (V2X), peer to peer (P2P), machine to machine (M2M), machine type communication (MTC), Internet of Things (IoT), virtual reality (VR), augmented reality (AR), industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearable, smart transportation, smart city, smart home, drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery and mobility, etc. The terminal device 120 may be a user equipment (UE) conforming to the 3rd Generation Partnership Project (3GPP) standard, a fixed device, a mobile device, a handheld device, a wearable device, a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a personal computer, a smart book, a vehicle, a satellite, a Global Positioning System (GPS) device, a target tracking device, a drone, a helicopter, an aircraft, a ship, a remote control device, a smart home device, or an industrial device. The terminal device may also be a communication device in a future wireless communication system.

[0134] In the embodiment of the present application, the device for realizing the function of the terminal may be a terminal; or it may be a device that can support the terminal to realize the function, such as a chip system, or a communication module, or a modem, etc., which may be installed in the terminal. In the embodiment of the present application, the chip system may be composed of chips, or may include chips and other discrete devices. In the technical solution provided in the embodiment of the present application, the device for realizing the function of the terminal is a terminal, and the terminal is a UE as an example to describe the technical solution provided in the embodiment of the present application. The embodiment of the present application does not limit the specific technology and specific device form adopted by the terminal device.

[0135] Base stations and terminals can be fixed or mobile. They can be deployed on land, indoors or outdoors, handheld or vehicle-mounted; on water; or on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of base stations and terminals.

[0136] The roles of base stations and terminals can be relative. For example, the helicopter or drone 120i in Figure 1 can be configured as a mobile base station. For terminals 120j accessing the wireless access network 100 via 120i, terminal 120i is a base station. However, for base station 110a, 120i is a terminal, meaning that communication between 110a and 120i occurs via a wireless air interface protocol. Of course, communication between 110a and 120i can also occur via a base station-to-base station interface protocol. In this case, 120i is also a base station relative to 110a. Therefore, base stations and terminals can be collectively referred to as communication devices. 110a and 110b in Figure 1 can be referred to as communication devices with base station functionality, while 120a-120j in Figure 1 can be referred to as communication devices with terminal functionality.

[0137] The technical solutions of the embodiments of the present application can be applied to scenarios where a base station and a UE perform wireless communication, scenarios where a UE performs wireless communication, and scenarios where a base station performs wireless communication. In a wireless communication system, data communication can be performed between UEs through a network device (such as a base station), or data communication can be performed directly between UEs without the help of a network device. The interface between UEs is called a PC5 interface, and the interface between UEs and a base station is called a Uu interface. The link between UEs is called a sidelink (SL). A typical application scenario of sidelink communication is vehicle to everything (V2X), such as the communication scenario between 120a and 120b in FIG1 . In the vehicle network, each vehicle is a UE, and data can be directly transmitted between UEs through the sidelink without the help of a network device, which can effectively reduce communication delays. The communication between UEs can be unicast communication, multicast communication, or broadcast communication, where UE1 can be the sender of data or signaling, and UE2 can be the receiver of data or signaling. In sidelink communication, the UE may be configured with one or more antennas for transmitting and receiving messages / information / data, etc. It will be appreciated that the UE may also include multiple components related to the transmission and reception of messages / information / data (e.g., a processor, a modulator, a multiplexer, a demodulator, or a demultiplexer, etc.).

[0138] Refer to Figure 2, which is a schematic diagram of the sidelink communication scenario provided by an embodiment of the present application. As shown in Figure 2, UE1 and UE2 perform sidelink communication, at which time UE1 acts as a transmitting UE (transmission UE, TX UE) and UE2 acts as a receiving UE (reception UE, RX UE). Among them, UE1 can be within the coverage range of the base station (in coverage, IC) or outside the coverage range of the base station (out of coverage, OOC). When UE1 is in a radio resource control (radio resource control, RRC) connection state, UE1 can obtain SL resources (used for SL transmission) from the base station, which is called the resource allocation mode of mode1, that is, the base station scheduling mode. For example, the base station can schedule SL resources for the UE through downlink control information (downlink control information, DCI), or configure a SL configuration authorization (configured grant) for the UE through an RRC message. When UE1 is operating in mode 2 (which can be in RRC connected state, RRC inactive state, RRC idle state, or OOC state), the UE can receive the SL resource pool configuration from the base station or obtain the SL resource pool configuration from the pre-configuration, and then select SL resources in the SL resource pool for transmission. Exemplarily, the selection can be random or based on the results of sensing or partial sensing.

[0139] In one possible implementation, a UE may be configured to act as a base station. For example, a UE may act as a scheduling entity that provides sidelink signals between UEs in V2X, D2D, or P2P, etc.

[0140] In one possible implementation, the UE may also be used to act as a relay node. For example, the UE may act as a relay device or an integrated access and backhaul (IAB) node to provide wireless backhaul services for terminal devices.

[0141] In sidelink communication, the method provided in the present application can be applied not only to V2X scenarios, but also to sidelink UE to network relay (Sidelink UE-to-Network Relay) scenarios and sidelink UE to UE relay (Sidelink UE-to-UE Relay) scenarios. See Figure 3, which is a schematic diagram of the Sidelink UE-to-Network Relay scenario provided by an embodiment of the present application. As shown in Figure 3, the Sidelink UE-to-Network Relay scenario includes a Remote UE (remote UE) and a Relay UE (relay UE), and also includes a base station; the method provided in the present application can be applied to the communication between the Remote UE and the Relay UE. See Figure 4, which is a schematic diagram of the Sidelink UE-to-UE Relay scenario provided by an embodiment of the present application. As shown in Figure 4, the Sidelink UE-to-UE Relay scenario includes a Source UE, a Relay UE, and a target UE; the method provided in this application can be applied to communication between the Source UE and the Relay UE, and / or, communication between the Relay UE and the target UE.

[0142] In various embodiments of the present application, the term "wireless communication" may also be referred to as "communication", and the term "communication" may also be described as "data transmission", "information transmission" or "transmission".

[0143] The following is a brief introduction to several terms related to this application.

[0144] 1. Time Synchronization

[0145] One device can send precise reference time information to another device. This reference time information can be used to indicate the time corresponding to a reference time point (such as a frame boundary) to achieve time synchronization between the two devices. This process can be called accurate reference timing.

[0146] The 5G system supports Time-Sensitive Networking (TSN) / Delay-Sensitive Communication (TSC), and TSN / TSC requires precise time synchronization between the base station and the UE. The base station can provide time synchronization to the UE to ensure the time synchronization between the two. For example, the base station sends the reference time information corresponding to the reference time point to the UE based on the 5GS clock (5G internal system clock). Among them, the "timing" involved in this application can be understood as "transmitting time information", or transmitting a certain standard time information (or reference time signal) to the user who needs time information, so that the time of the entire system is synchronized.

[0147] The base station can perform accurate reference timing delivery (accurate reference timing deliver) in two ways: broadcast and unicast. In the broadcast mode, the base station can perform accurate reference timing delivery through system information block 9 (SIB9). See Figure 5, which is a schematic diagram of accurate reference timing delivery through SIB9 provided in an embodiment of the present application. As shown in Figure 5, the reference time point can be located at the end boundary of the system information (SI) window transmitted by SIB9, or the reference time point can be located at the system frame number (SFN) boundary after the end boundary of the system information window transmitted by SIB9. In the unicast mode, the base station can perform accurate reference timing delivery through a downlink information transmission message (DLInformationTransfer message). See Figure 6, which is a schematic diagram of accurate reference timing delivery through a downlink information transmission message provided in an embodiment of the present application. As shown in Figure 6, the reference time point can be located at the end moment of the reference SFN of the primary cell (PCell), and the reference SFN is indicated in the DLInformationTransfer message. The reference SFN shown in Figure 6 is SFN x.

[0148] The SIB9 and DLInformationTransfer messages both include a reference time information (ReferenceTimeInfo) information element, which is used to indicate the reference time information corresponding to the reference time point.

[0149] 2. RTT-based PDC and TA-based PDC

[0150] Wireless signal transmission introduces a certain propagation delay, which increases with the distance the wireless signal travels. Therefore, when performing time synchronization, it is necessary to account for this propagation delay and compensate for it to achieve more accurate time synchronization.

[0151] Currently, two types of propagation delay compensation (PDC) (or PDC schemes) are supported, including round trip time (RTT)-based PDC and timing advance (TA)-based PDC.

[0152] In RTT-based PDC, both the UE and the base station (such as the gNB) need to measure the receive-transmit (Rx-Tx) time difference, and the Rx-Tx time difference can be determined based on the reference signal. See Figure 7, which is a schematic diagram of the RTT-based propagation delay provided in an embodiment of the present application. As shown in Figure 7, the UE sends an uplink reference signal, such as a sounding reference signal (SRS), the sending time of the uplink reference signal is T1, and the time when the base station receives the uplink reference signal is T2, where the difference between T2 and T1 represents the uplink propagation delay (UL propagation delay); the base station sends a downlink reference signal, such as a tracking reference signal (TRS) or a positioning reference signal (PRS), the sending time of the downlink reference signal is T3, and the time when the UE receives the downlink reference signal is T4, where the difference between T4 and T3 represents the downlink propagation delay (DL propagation delay). Among them, the Rx-Tx time difference measured by the UE is (T4-T1), and the Rx-Tx time difference measured by the base station is (T3-T2). The propagation delay between the base station and the UE can be [(T4-T1)-(T3-T2)] / 2, which is half of the difference between the Rx-Tx time difference of the UE and the Rx-Tx time difference of the base station.

[0153] Refer to Figure 8a, which is a UE-side RTT-based PDC process provided by an embodiment of the present application. As shown in Figure 8a, the UE-side RTT-based PDC process includes but is not limited to: Step 1, the base station provides the UE with a measurement configuration; Step 2a and Step 2b, the base station transmits TRS or PRS to the UE for measurement, and the UE transmits SRS to the base station for measurement; Step 3a and Step 3b, the UE and the base station perform Rx-Tx time difference measurement respectively; Step 4, the base station provides its own Rx-Tx time difference measurement to the UE; Step 5, the UE performs PDC based on its own Rx-Tx time difference measurement and the base station's Rx-Tx time difference measurement. Among them, the propagation delay between the base station and the UE can be equal to [(T4-T1)-(T3-T2)] / 2.

[0154] Refer to Figure 8b, which is a base station-side RTT-based PDC process provided in an embodiment of the present application. As shown in Figure 8b, the base station-side RTT-based PDC process includes but is not limited to: step 1, the base station provides measurement configuration to the UE; step 2a and step 2b, the base station transmits TRS or PRS to the UE for measurement, and the UE transmits SRS to the base station for measurement; step 3a and step 3b, the UE and the base station perform Rx-Tx time difference measurement respectively; step 4, the UE provides its own Rx-Tx time difference measurement to the base station; step 5, the base station performs PDC based on its own Rx-Tx time difference measurement and the UE's Rx-Tx time difference measurement. Among them, the propagation delay between the base station and the UE can be equal to [(T4-T1)-(T3-T2)] / 2.

[0155] In TA-based PDC, the UE uses (TA / 2) as the propagation delay to perform PDC, where the value of TA may be indicated to the UE by the base station.

[0156] Generally speaking, different types of PDCs can achieve different time synchronization accuracies. For example, RTT-based PDCs have higher time synchronization accuracy than TA-based PDCs.

[0157] Currently, base stations can be configured to enable either RTT-based or TA-based PDC. For example, if the rxTxTimeDiff-gNB (receive and transmit time difference gNB) information element is configured in the downlink information transfer message (DLInformationTransfermessage), it indicates that the UE requires RTT-based PDC. If the ta-PDC information element is configured in the DLInformationTransfer field, it indicates that the UE requires TA-based PDC. The configuration method for the base station depends on information provided by the core network.

[0158] It is understandable that after device 1 (such as a base station or UE) grants time to device 2 (such as a UE) and indicates the corresponding PDC type, due to the movement of device 2 or changes in the service requirements of device 2, device 2 may require different types of PDCs to achieve different time synchronization accuracy. Therefore, it is necessary to more reasonably or more real-timely determine the PDC type that matches device 2 to improve the reliability of TSN / TSC support. In other words, the existing technology does not determine the PDC type in real time.

[0159] In addition, in the sidelink (SL) communication scenario, as shown in Figure 2 above, UE1 may not be able to obtain auxiliary information for determining the PDC type from the core network (this is because UE1 may be outside the coverage of the base station). Therefore, in the SL communication scenario, how to determine the PDC type to achieve time synchronization remains to be explored.

[0160] In view of this, the embodiments of the present application provide an information interaction method, apparatus, and readable storage medium, which can determine the PDC type in real time, thereby improving the reliability of communication equipment supporting TSN / TSC.

[0161] The technical solution provided by this application will be described in detail below with reference to more drawings.

[0162] The technical solutions provided in this application can be described in detail through multiple embodiments, with specific reference to the description of each embodiment below. It should be understood that the technical solutions described in the various embodiments below in this application can be combined in any way to form new embodiments, and that the same or similar parts of the concepts or solutions involved can be referenced or combined with each other. Each embodiment is described in detail below.

[0163] In this application, unless otherwise specified, the same or similar parts between the various embodiments or implementation methods can refer to each other. In the various embodiments in this application, and the various implementation methods / implementation methods / implementation methods in each embodiment, if there is no special explanation and logical conflict, the terms and / or descriptions between different embodiments and the various implementation methods / implementation methods / implementation methods in each embodiment are consistent and can be referenced to each other. The technical features in different embodiments and the various implementation methods / implementation methods / implementation methods in each embodiment can be combined to form new embodiments, implementation methods, implementation methods, or implementation methods according to their inherent logical relationships. The implementation methods of this application described below do not constitute a limitation on the scope of protection of this application.

[0164] It should be understood that, in this application, indication includes direct indication (also known as explicit indication) and implicit indication. Direct indication of information A refers to including information A; implicit indication of information A refers to indicating information A through the correspondence between information A and information B and the direct indication of information B. The correspondence between information A and information B can be predefined, pre-stored, pre-burned, or pre-configured.

[0165] It should be understood that, in this application, information D is determined based on information C, which includes information D being determined solely based on information C, as well as information D being determined based on information C and other information. Furthermore, information C being used to determine information D may also include indirect determination, such as information D being determined based on information E, which in turn is determined based on information C.

[0166] In addition, in each embodiment of the present application, "network element A sends information A to network element B" can be understood as the destination end of the information A or the intermediate network element in the transmission path between the destination end and the network element B, which may include directly or indirectly sending information to network element B. "Network element B receives information A from network element A" can be understood as the source end of the information A or the intermediate network element in the transmission path between the source end and the network element A, which may include directly or indirectly receiving information from network element A. The information may be processed as necessary between the source end and the destination end of the information transmission, such as format changes, but the destination end can understand the valid information from the source end. Similar expressions in this application can be understood similarly and will not be elaborated here.

[0167] The present application can be applied to scenarios where a base station provides time to a UE (i.e., the base station transmits reference time information to the UE), or where a UE provides time to a UE (i.e., the UE transmits reference time information to the UE), or where a base station provides time to a base station (i.e., the base station transmits reference time information to the base station). It can be understood that in the scenario where a base station provides time to a UE, the base station, as the party that transmits the reference time information, can be called a time-providing device, and the UE, as the party that receives the reference time information, can be called a time-provided device. Similarly, in the scenario where UE1 provides time to UE2, UE1, as the party that transmits the reference time information, can be called a time-providing device, and UE2, as the party that receives the reference time information, can be called a time-provided device. Similarly, in the scenario where base station 1 provides time to base station 2, base station 1, as the party that transmits the reference time information, can be called a time-providing device, and base station 2, as the party that receives the reference time information, can be called a time-provided device.

[0168] The first device of the present application may be a terminal device or a module applied to the terminal device, such as any terminal in the aforementioned Figure 1; the second device may be a network device or a module applied to the network device, such as any base station in the aforementioned Figure 1. Alternatively, the first device and the second device of the present application are different terminal devices or modules applied to different terminal devices, for example, the first device is UE2 in the aforementioned Figure 2, and the corresponding second device is UE1 in the aforementioned Figure 2; for another example, the first device is the RemoteUE in the aforementioned Figure 3, and the corresponding second device is the Relay UE in the aforementioned Figure 2; for another example, the first device is the Source UE in the aforementioned Figure 4, and the corresponding second device is the Relay UE in the aforementioned Figure 4; or, the first device is the target UE in the aforementioned Figure 4, and the corresponding second device is the Relay UE in the aforementioned Figure 4.

[0169] In this application, the term "PDC type" can also be replaced by terms such as "PDC scheme" or "PDC mechanism". The term "corresponding" in this application can be replaced by "associated", etc., and the term "update" can be replaced by "switching", "replacing", or "using".

[0170] See Figure 9, which is a flow chart of an information exchange method provided in an embodiment of the present application. This method primarily describes how a time-served device (i.e., the first device in this embodiment) determines its own PDC type and requests or instructs a timing device (i.e., the second device in this embodiment) to update its PDC type. The time-served device then determines a propagation delay based on the PDC type to achieve time synchronization with the timing device.

[0171] As shown in FIG9 , the information interaction method includes but is not limited to the following steps:

[0172] S101: A first device (such as a UE) determines a first PDC type.

[0173] The PDC types in the various embodiments of the present application may include: a TA-based PDC type, an RTT-based PDC type, or other PDC types. The other PDC types may be newly defined PDC types as technology or standards evolve. Exemplarily, the RTT-based PDC type may be further divided into a variety of different PDC types, for example, by using different reference signals (such as: synchronization signal and physical broadcast channel block (synchronization signal and PBCH block, SSB), PRS, TRS, or channel state information reference signal (channel state information reference signal, CSI-RS), etc.) to divide the RTT-based PDC into a variety of different PDC types.

[0174] In a possible implementation, the first PDC type may be an RTT-based PDC type, or a TA-based PDC type, or other PDC types, which is not limited in the embodiment of the present application.

[0175] In one possible implementation, the first device may determine (change to / use) the first PDC type based on a preset rule. For example, the upper layer of the first device may determine the first PDC type based on the preset rule and indicate it to the access stratum (AS) layer, where the upper layer may be an application layer, a vehicle-to-everything (V2X) layer, a PC5-S (ProSe communication 5, signaling) layer, or a proximity-based services (ProSe) layer, etc. Alternatively, the preset rule is told by the upper layer of the first device to the AS layer, and the AS layer of the first device further determines the first PDC type based on the preset rule. This is not limited to the embodiments of the present application.

[0176] In one possible implementation, the above-mentioned preset rules may be configured or pre-configured, and the configuration here may be a dynamic configuration. For example, the preset rules may be configured by the base station, and the pre-configuration here may be understood as being pre-stored locally or pre-configured by the core network. Among them, the preset rules may include but are not limited to one or more of the following: the correspondence between service information and PDC type, the correspondence between location information and PDC type, or the correspondence between available resources and PDC type. Exemplarily, the service information may include but is not limited to one or more of the following: service type, or quality of service (QoS) flow. It can be understood that the correspondence between QoS flow and PDC type may be the correspondence between QoS parameters associated with QoS flow and PDC type.

[0177] In one possible implementation, the first device may determine the first PDC type based on the correspondence between ((pre)configured) service information and the PDC type, and the service information of the first device (for example, information about the current service of the first device). The service information of the first device may be the service type / QoS flow of communication between the first device and the second device, or may be the service type / QoS flow of communication between the first device and the third device. Of course, the service information of the first device may include the service type / QoS flow of communication between the first device and the second device, and the service type / QoS flow of communication between the first device and the third device. Here, the third device may be any device in the network that can communicate with the first device except the second device. Exemplarily, in some scenarios, the second device is a base station, the first device is UE1, and the third device is UE2. It can be understood that the communication between the first device and the second device includes the first device sending to the second device, and / or the second device sending to the first device.

[0178] In some scenarios, when there are multiple service types / QoS flows, the service information of the first device may refer to the service type / QoS flow with the highest priority, or the service type / QoS flow with the smallest packet delay budget (PDB), or the service type / QoS flow with the highest time synchronization accuracy requirement.

[0179] In some scenarios, when there are multiple service types / QoS flows, the first device can determine multiple PDC types based on the correspondence between ((pre)configured) service information (such as service type / QoS flow) and PDC type, as well as these multiple service types / QoS flows, and determine a first PDC type from these multiple PDC types. The first PDC type is the PDC type with the highest time synchronization accuracy requirement among these multiple PDC types.

[0180] In another possible implementation, the first device may determine the first PDC type based on the correspondence between the (pre-configured) location information and the PDC type, and the location information of the first device itself (for example, information about the current location of the first device). The location information may be one or more of the following: longitude and latitude information, cell information (one or more cells), zone information, etc., which is not limited in the embodiments of the present application. It can be understood that the location information of the first device may refer to the longitude and latitude information of the first device, or the cell information to which the first device is connected, or the zone information of the first device, etc.

[0181] In another possible implementation, the first device may determine the first PDC type based on the correspondence between ((pre)configured) available resources and PDC types, and the available resources of the first device and / or the second device (for example, the resources currently available to the first device and / or the second device). Exemplarily, before the first device determines the first PDC type, the second device may also send its own available resources to the first device. The available resources may refer to available communication resources and / or available computing resources. Exemplarily, available communication resources may refer to resources that can be used for transmission, such as frequency domain resources, or time domain resources, or time-frequency domain resources. Exemplarily, available computing resources may refer to one or more of storage resources, hardware resources, and software resources that can be used for computing.

[0182] In yet another possible implementation, when the first device determines the first PDC type based on multiple types of information in a preset rule, the first device can determine the corresponding PDC type for each type of information, and then select the PDC type with the highest synchronization accuracy as the first PDC type. For example, the first device determines a PDC type based on the correspondence between service information and PDC type, and service information of the first device (for example, information about the current service of the first device); and determines another PDC type based on the correspondence between location information and PDC type, and the location information of the first device itself (for example, information about the current location of the first device). The first device can use the PDC type with the highest synchronization accuracy of the two PDC types as the first PDC type.

[0183] In one possible implementation, the first PDC type may be determined when the first device first needs to synchronize time with the second device. It is understood that the first PDC type is the initial PDC type. In another possible implementation, the first device has already obtained the second PDC type before determining the first PDC type. The manner in which the first device obtains the second PDC type may be determined by the first device or the second device based on the aforementioned preset rules, may be configured by the network device of the first device, or may be a predefined initial PDC type, which is not limited in the embodiments of the present application. The second PDC type is the PDC type corresponding to the current PDC execution by the first device or the second device, and the second PDC type is different from the first PDC type. In other words, the second PDC type may be the PDC type corresponding to the current time synchronization performed by the second device with the first device, and the first PDC type may be the PDC type corresponding to the time synchronization performed by the second device with the first device after the update. In some scenarios, when the location of the first device changes or the service needs of the first device change, the first device may determine to update from the original second PDC type to the first PDC type based on the changed location or service needs. Illustratively, the second PDC type may be obtained before the location or service demand of the first device changes, and the first PDC type may be determined after the location or service demand of the first device changes.

[0184] In an optional embodiment, the first PDC type may also be determined by the network device of the first device, and then the network device of the first device sends the first PDC type to the first device, so that the first device obtains the first PDC type.

[0185] S102: A first device (such as a UE) sends first information to a second device (such as a base station or a UE), where the first information is used to indicate the first PDC type.

[0186] Correspondingly, the second device (such as a base station or a UE) receives the first information.

[0187] In one possible implementation, after determining the first PDC type, the first device may send first information to the second device. The first information may be used to indicate the first PDC type (which the first device desires to use). Alternatively, the first information may be used to request second information for executing the PDC.

[0188] S103: The second device (such as a base station or a UE) sends second information for executing PDC to the first device (such as a UE), where the second information is determined based on the first PDC type.

[0189] Correspondingly, the first device (such as UE) receives the second information.

[0190] In one possible implementation, after the second device receives the above-mentioned first information, it can determine the second information for performing PDC based on the first PDC type indicated by the first information. For example, when the first PDC type is (or belongs to) an RTT-based PDC type, the second information can be used to indicate the receive-transmit (Rx-Tx) time difference of the second device, such as (T3-T2) in Figure 7 above. It can be understood that when the first PDC type is (or belongs to) an RTT-based PDC type, the first device and the second device need to send reference signals respectively to measure the receive-transmit (Rx-Tx) time difference respectively, as shown in Figure 7 above, which is not repeated here. For another example, when the first PDC type is a TA-based PDC type, the second information can be used to indicate the value of TA. It can be understood that if the second device has informed the first device of the value of TA before receiving the above-mentioned first information, the second information can be used to respond to the above-mentioned first information, indicating confirmation of using the above-mentioned first PDC type for PDC. In some scenarios, when the first PDC type is a TA-based PDC type and the first device has learned the TA, the second device may not send the second information and jump to execute step S104; of course, the second device may also send the second information to indicate the latest TA value, which can improve the accuracy of time synchronization.

[0191] In one possible implementation, after the second device receives the first information, the second device may determine a reference signal A based on the first PDC type. The second device may then send third information to the first device, where the third information is used to indicate the reference signal A. In other words, the third information is used to instruct the first device to perform PDC based on the reference signal A. The reference signal A may be used to measure the receive-transmit (Rx-Tx) time difference of the first device, or the reference signal A may be used by the second device to determine the TA. Exemplarily, the reference signal A may be any of the following: SSB, PRS, TRS, CSI-RS, SRS, random access preamble signal, etc. The second device may determine the reference signal A corresponding to the first PDC type based on a predefined correspondence between the PDC type and the reference signal. Exemplarily, the resource bandwidth required for the reference signals corresponding to different PDC types is different. Exemplarily, the reference signals corresponding to different PDC types may be different, and one PDC type may correspond to one or more reference signals. The time synchronization accuracy measured by different reference signals may be different. For example, if the above-mentioned first PDC type is a TA-based PDC type, the reference signal A can be an SRS or a random access preamble signal; if the above-mentioned first PDC type is (belongs to) an RTT-based PDC type, the reference signal A can be any one of the following: SSB, PRS, TRS, or CSI-RS.

[0192] In one possible implementation, the first PDC type is (or belongs to) an RTT-based PDC type. After the second device sends the third information to the first device, it may send a reference signal A to the first device. After the first device receives the reference signal A, it may calculate the receive-transmit (Rx-Tx) time difference of the first device based on the reference signal A. Furthermore, the first device may perform PDC using the receive-transmit (Rx-Tx) time difference of the first device and the receive-transmit (Rx-Tx) time difference of the second device indicated by the second information.

[0193] In another possible implementation, the first PDC type is a TA-based PDC type. After receiving the third information, the first device may send a reference signal A (such as an SRS or a random access preamble) to the second device. After receiving the reference signal A, the second device may determine the TA based on the reference signal A. Furthermore, the first device may perform PDC based on the TA value indicated by the second information.

[0194] In one possible implementation, after receiving the first information, the second device may send a response message to the first device. The response message may be a response to the first information and used to confirm the use of the first PDC type for PDC. It is understood that the response message may be sent before step S103.

[0195] S104: The second device (eg, a base station or a UE) sends reference time information to the first device (eg, a UE).

[0196] Correspondingly, the first device (such as UE) receives the reference time information.

[0197] S105: The first device (such as UE) performs time synchronization with the second device based on the reference time information and the second information.

[0198] In one possible implementation, after the second device sends the second information to the first device, the second device may then send reference time information to the first device. The reference time information includes time information corresponding to the reference time point, such as the time information corresponding to the reference time point in the second device. It can be understood that the reference time point may be determined according to a predefined rule, or the reference time point is indicated by the reference time information. Exemplarily, as shown in FIG5 above, the reference time point may be located at the end boundary of the SI window or the SFN or DFN (direct frame number) boundary after the end boundary of the SI window, which will not be repeated here; or, as shown in FIG6 above, the reference time point is located at the end moment of the reference SFN or DFN of the PCell, which will not be repeated here. After the first device receives the reference time information, it may perform time synchronization with the second device based on the reference time information and the above-mentioned second information received.

[0199] For example, when the above-mentioned second information is used to indicate the value of TA (or when the first PDC type is a PDC type based on TA), the first device can use half of the value of TA (i.e., TA / 2) as the propagation delay. In other words, the value of TA can be used for PDC. Then, the first device synchronizes time with the second device based on the propagation delay (i.e., TA / 2) and the received reference time information. For example, the first device adjusts the time corresponding to the above-mentioned reference time point in the first device based on the propagation delay, such as the first device adjusts the clock time corresponding to the above-mentioned reference time point in the first device to the reference time information delayed (TA / 2), or the reference time information advanced (TA / 2). In some scenarios, the clock time corresponding to the reference time point in the first device may be the moment when the first device receives the reference time point.

[0200] For example, when the second information is used to indicate the receive-transmit (Rx-Tx) time difference of the second device (or when the first PDC type is (or belongs to) an RTT-based PDC type), the first device calculates the propagation delay based on the receive-transmit (Rx-Tx) time difference of the second device (such as (T3-T2) in Figure 7 above) and its own receive-transmit time difference (such as (T4-T1) in Figure 7 above). In other words, the Rx-Tx time difference of the second device and the Rx-Tx time difference of the first device can be used for PDC. The propagation delay is equal to half of the difference between the Rx-Tx time difference of the first device and the Rx-Tx time difference of the second device, that is, [(T4-T1)-(T3-T2)] / 2. It can be understood that the propagation delay here can also be [(T3-T2)-(T4-T1)] / 2, that is, the propagation delay here can be half of the difference between the Rx-Tx time difference of the first device and the Rx-Tx time difference of the second device, or half of the difference between the Rx-Tx time difference of the second device and the Rx-Tx time difference of the first device. Then, the first device can synchronize time with the second device based on the propagation delay (such as [(T4-T1)-(T3-T2)] / 2) and the received reference time information. For example, the first device adjusts the time corresponding to the above-mentioned reference time point in the first device based on the propagation delay, such as the first device adjusts the clock time corresponding to the above-mentioned reference time point in the first device to be delayed by [(T4-T1)-(T3-T2)] / 2 by the above-mentioned reference time information, or to advance the reference time information by [(T4-T1)-(T3-T2)] / 2. In some scenarios, the clock time corresponding to the reference time point in the first device can be the moment when the first device receives the reference time point.

[0201] It is understood that the specific implementation of time synchronization can also refer to the existing technology, which is not described in detail here.

[0202] In the embodiment of the present application, the time-serving device (i.e., the first device) requests / instructs the timing device (i.e., the second device) to update the PDC type based on its own needs, so that the PDC type can match the status or needs of the time-serving device more real-time and more reasonably. The time-serving device then determines the propagation delay based on the PDC type and uses the propagation delay to synchronize time with the timing device, which can improve the reliability of TSN / TSC support between the timing device and the time-serving device. In addition, the embodiment of the present application can also support UE-to-UE timing in the sidelink scenario, improving the reliability of TSN / TSC support in the sidelink.

[0203] See Figure 10, which is another flow diagram of the information interaction method provided in an embodiment of the present application. This method primarily describes how the timed device (i.e., the first device in this embodiment) determines its own PDC type and requests or instructs the timing device (i.e., the second device in this embodiment) to update the PDC type. The timing device then determines the propagation delay based on the PDC type requested or indicated by the timed device to achieve time synchronization with the timed device.

[0204] As shown in FIG10 , the information interaction method includes but is not limited to the following steps:

[0205] S201: A first device (such as a UE) determines a first PDC type.

[0206] S202: A first device (such as a UE) sends first information to a second device (such as a base station or a UE), where the first information is used to indicate the first PDC type.

[0207] Correspondingly, the second device (such as a base station or a UE) receives the first information.

[0208] In one possible implementation, the implementation of step S201 and step S202 in the embodiment of the present application can refer to the implementation of step S101 and step S102 in the embodiment shown in Figure 9 above, and will not be repeated here.

[0209] S203: The second device (such as a base station or a UE) performs PDC based on the first PDC type.

[0210] S204: The second device (eg, a base station or a UE) sends the reference time information passing through the PDC to the first device (eg, a UE).

[0211] Correspondingly, the first device (such as UE) receives the reference time information.

[0212] In one possible implementation, the first PDC type is a TA-based PDC type. The second device can then perform PDC based on the TA and send reference time information passing through the PDC to the first device. Exemplarily, the second device can use half of the TA (i.e., TA / 2) as a propagation delay, and can determine reference time information based on the propagation delay, and then send the reference time information to the first device. The reference time information includes time information corresponding to a reference time point. The reference time information can be the original time information of the reference time point advanced (TA / 2), or can be the original time information of the reference time point delayed (TA / 2). It is understood that the original time information of the reference time point can be the clock time corresponding to the reference time point in the second device before performing the PDC. Exemplarily, as shown in FIG5 above, the reference time point can be located at the end boundary of the SI window or at the SFN or DFN boundary after the end boundary of the SI window, which is not described in detail here; or, as shown in FIG6 above, the reference time point can be located at the end moment of the reference SFN or DFN of the PCell, which is not described in detail here.

[0213] In another possible implementation, the first PDC type is (or belongs to) an RTT-based PDC type. Then the second device can perform PDC based on the receive-send time difference of the first device and the receive-send time difference of the second device, and send reference time information passing through the PDC to the first device. Exemplarily, the second device can calculate the propagation delay based on the receive-send time difference of the first device and the receive-send time difference of the second device, such as taking the receive-send time difference of the first device minus half of the difference of the receive-send time difference of the second device as the propagation delay, or taking the receive-send time difference of the second device minus half of the difference of the receive-send time difference of the first device as the propagation delay. The second device can then determine the reference time information based on the propagation delay and send the reference time information to the first device. The reference time information includes the time information corresponding to the reference time point. The reference time information can be the original time information of the reference time point advanced by the propagation delay, or can be the original time information of the reference time point delayed by the propagation delay. For the description of the reference time point and the original time information of the reference time point, please refer to the previous description and will not be repeated here.

[0214] For example, in the case where the above-mentioned first PDC type is (or belongs to) an RTT-based PDC type, after the second device receives the above-mentioned first information, it can send fourth information to the first device. The fourth information can be used to request the receive-send time difference of the first device. After the first device (such as UE) receives the fourth information, it can send fifth information to the second device. The fifth information can be used to indicate the receive-send time difference of the first device. After the second device receives the fifth information, it can determine the propagation delay based on the receive-send time difference of the first device and its own receive-send time difference, and then determine the reference time information based on the propagation delay, and send the reference time information to the first device.

[0215] In some scenarios, after receiving the first information, the second device may determine reference signal A based on the first PDC type indicated by the first information, and then send third information to the first device. The third information may be used to indicate reference signal A. In other words, the third information is used to instruct the first device to perform PDC based on reference signal A. Reference signal A may be used to measure the receive-transmit time difference of the first device, or the second device may determine TA. Exemplarily, reference signal A may be any of the following: SSB, PRS, TRS, CSI-RS, SRS, random access preamble, etc. The second device may determine reference signal A corresponding to the first PDC type based on a predefined correspondence between PDC types and reference signals. Exemplarily, reference signals corresponding to different PDC types require different resource bandwidths. Furthermore, different PDC types may correspond to different reference signals, and one PDC type may correspond to one or more reference signals. The time synchronization accuracy measured by different reference signals may vary. For example, if the above-mentioned first PDC type is a TA-based PDC type, the reference signal A can be an SRS or a random access preamble signal; if the above-mentioned first PDC type is (belongs to) an RTT-based PDC type, the reference signal A can be any one of the following: SSB, PRS, TRS, or CSI-RS.

[0216] In some scenarios, the first PDC type is (or belongs to) an RTT-based PDC type. After the second device sends the third information to the first device, it may send a reference signal A to the first device. After the first device receives the reference signal A, it may calculate the receive-transmit (Rx-Tx) time difference of the first device based on the reference signal A. Furthermore, the second device may perform PDC using the receive-transmit (Rx-Tx) time difference of the first device indicated by the fifth information and the receive-transmit (Rx-Tx) time difference of the second device.

[0217] In another possible implementation, the above-mentioned first PDC type is a PDC type based on TA. After the first device receives the above-mentioned third information, it can send a reference signal A (such as SRS or random access preamble signal) to the second device; after the second device receives the reference signal A, it can determine the TA based on the reference signal A, and then perform PDC based on the value of the TA.

[0218] S205: The first device (eg, UE) performs time synchronization with the second device based on the reference time information.

[0219] In one possible implementation, the above-mentioned reference time information includes time information corresponding to the reference time point. For the explanation of the reference time point, please refer to the previous description and will not be repeated here. Exemplarily, after the first device receives the reference time information, it can use the reference time information as the clock time corresponding to the reference time point in the first device. For example, the original time information of the reference time point is 7:59am, and the original time information of the reference time point (7:59am) is obtained after PDC, and the reference time information is 8:00am; assuming that the propagation delay from the second device to the first device is 1 minute, the moment when the first device actually receives the reference time point is 8:00am, at this time the first device will use the reference time information 8:00am as the clock time corresponding to the reference time point in the first device.

[0220] In the embodiment of the present application, the time-serving device (i.e., the first device) requests / instructs the timing device (i.e., the second device) to update the PDC type based on its own needs, so that the PDC type can match the status or needs of the time-serving device more in real time and more reasonably. The timing device then determines the propagation delay based on the PDC type and determines the reference time information based on the propagation delay, so that the time-serving device can synchronize time with the timing device based on the received reference time information; this can improve the reliability of TSN / TSC support between the timing device and the time-serving device. In addition, the embodiment of the present application can also support UE-to-UE timing in the sidelink scenario, thereby improving the reliability of TSN / TSC support in the sidelink.

[0221] See Figure 11, which is another flow chart of the information interaction method provided in an embodiment of the present application. The method mainly introduces that the timing device (i.e., the second device in the embodiment of the present application) determines the PDC type based on preset rules and the status / requirements of the time-served device (i.e., the first device in the embodiment of the present application). The timing device or the time-served device then determines the propagation delay based on the PDC type to achieve time synchronization between the two.

[0222] As shown in FIG11 , the information interaction method includes but is not limited to the following steps:

[0223] S301, the second device (such as a base station or UE) determines the first PDC type based on preset rules, which preset rules include one or more of the following: the correspondence between service information and PDC type, the correspondence between location information and PDC type, or the correspondence between available resources and PDC type.

[0224] In one possible implementation, the second device may determine (replace with / use) the first PDC type based on a preset rule. For example, the upper layer of the second device may determine the first PDC type based on the preset rule and indicate it to the AS layer. The upper layer here may be an application layer, a vehicle-to-everything (V2X) layer, a PC5-S layer, or a ProSe layer, etc. Alternatively, the preset rule is told by the upper layer of the second device to the AS layer, and the AS layer of the second device further determines the first PDC type based on the preset rule. This is not limited to the embodiments of the present application.

[0225] In one possible implementation, the preset rules may be configured or pre-configured, and the preset rules may include, but are not limited to, one or more of the following: a correspondence between service information and PDC type, a correspondence between location information and PDC type, or a correspondence between available resources and PDC type. Exemplarily, the service information may include, but is not limited to, one or more of the following: service type, or QoS flow. It is understood that the correspondence between QoS flow and PDC type may be a correspondence between QoS parameters associated with the QoS flow and the PDC type.

[0226] In one possible implementation, the second device can determine the first PDC type based on the correspondence between (pre-configured) service information and PDC types, as well as the service information of the first device (e.g., information about the current service of the first device). It is understood that before the second device determines the first PDC type, the first device sends its own service information to the second device. For the specific implementation of the service information of the first device, please refer to the relevant description in the embodiment shown in Figure 9 above and will not be repeated here.

[0227] In another possible implementation, the second device can determine the first PDC type based on the correspondence between (pre-configured) location information and PDC types, as well as the location information of the first device (e.g., information about the current location of the first device). It is understood that before the second device determines the first PDC type, the first device sends its own location information to the second device. For a detailed description of the location information, please refer to the relevant description in the embodiment shown in FIG. 9 above, which will not be repeated here.

[0228] In another possible implementation, the second device may determine the first PDC type based on the correspondence between (pre-configured) available resources and PDC types, as well as the available resources of the first device and / or the second device (e.g., the resources currently available to the first device and / or the second device). Exemplarily, before the second device determines the first PDC type, the first device may also send its own available resources to the second device. For a detailed description of the available resources, please refer to the relevant description in the embodiment shown in FIG. 9 , which will not be repeated here.

[0229] In one possible implementation, the above-mentioned first PDC type may be an RTT-based PDC type, or a TA-based PDC type, or other PDC types, which is not limited in the embodiment of the present application. In one possible implementation, the first PDC type may be determined by the second device when the first device needs to synchronize time with the second device for the first time. It can be understood that the first PDC type may be the initial PDC type. In another possible implementation, the second device has obtained the second PDC type before determining the first PDC type. The way in which the second device obtains the second PDC type may be determined by the second device or the first device based on the above-mentioned preset rules, or it may be configured by the network device of the second device, or it may be a predefined initial PDC type, which is not limited in the embodiment of the present application. The second PDC type is the PDC type corresponding to the current PDC executed by the first device or the second device, and the second PDC type is different from the first PDC type. Regarding the relationship between the second PDC type and the first PDC type, please refer to the relevant description in the embodiment shown in Figure 9 above, which will not be repeated here.

[0230] In an optional embodiment, the first PDC type may also be determined by the network device of the second device, and then the network device of the second device sends the first PDC type to the second device, so that the second device obtains the first PDC type.

[0231] S302: The second device (such as a base station or a UE) sends first information to the first device (such as a UE), where the first information is used to indicate the first PDC type.

[0232] Correspondingly, the first device (such as UE) receives the first information.

[0233] S303: The first device (such as UE) parses the first information to obtain the first PDC type.

[0234] In one possible implementation, after determining the first PDC type, the second device may send first information to the first device. The first information may be used to indicate (whether the first device uses / updates / switches from the second PDC type to) the first PDC type. After receiving the first information, the first device may obtain the first PDC type.

[0235] The timing device (i.e., the second device) of the embodiment of the present application determines the PDC type based on the status or requirements of the device being timed (i.e., the first device) (e.g., factors such as service type / QoS flow / location information / available resources), which can make the PDC type more real-time and more reasonable to match the status or requirements of the device being timed, thereby improving the reliability of TSN / TSC support between the timing device and the device being timed. In addition, the embodiment of the present application can also support UE-to-UE timing in the sidelink scenario, improving the reliability of TSN / TSC support in the sidelink.

[0236] In a possible implementation, after step S302, the information interaction method shown in FIG11 further includes steps S304 to S306:

[0237] S304: The second device (eg, a base station or a UE) sends second information for executing PDC to the first device (eg, a UE), where the second information is determined based on the first PDC type.

[0238] Correspondingly, the first device (such as UE) receives the second information.

[0239] S305: The second device (eg, a base station or a UE) sends reference time information to the first device (eg, a UE).

[0240] Correspondingly, the first device (such as UE) receives the reference time information.

[0241] S306: The first device (such as UE) performs time synchronization with the second device (such as base station or UE) based on the reference time information and the second information.

[0242] In one possible implementation, the implementation of steps S304 to S306 in the embodiment of the present application can refer to the implementation of steps S103 to S105 in the embodiment shown in Figure 9 above, and will not be repeated here.

[0243] In another possible implementation, after step S301 or step S302, the information interaction method shown in FIG11 further includes steps S307 to S309:

[0244] S307: The second device (such as a base station or a UE) performs PDC based on the first PDC type.

[0245] S308: The second device (eg, a base station or a UE) sends the reference time information passing through the PDC to the first device (eg, a UE).

[0246] Correspondingly, the first device (such as UE) receives the reference time information.

[0247] S309: The first device (eg, UE) performs time synchronization with the second device based on the reference time information.

[0248] In one possible implementation, the implementation of steps S307 to S309 in the embodiment of the present application can refer to the implementation of steps S203 to S205 in the embodiment shown in Figure 10 above, and will not be repeated here.

[0249] In one possible implementation, when the first PDC type is (or belongs to) an RTT-based PDC type, steps S302 and S303 may not be performed, and steps S307 to S309 may be performed after step S301. This is because when the second device executes an RTT-based PDC, the first device may not be aware of the PDC type being used, but may provide corresponding information based on an instruction from the second device (such as the fourth information, used to request the Rx-Tx time difference of the first device).

[0250] The timing device (i.e., the second device) of the embodiment of the present application determines the PDC type based on the status or needs of the device being timed (i.e., the first device) (e.g., factors such as service type / QoS flow / location information / available resources), which can make the PDC type more real-time and more reasonable to match the status or needs of the device being timed. The timing device then determines the propagation delay based on the PDC type, and determines the reference time information based on the propagation delay, so that the device being timed performs time synchronization with the timing device based on the received reference time information; or, the device being timed determines the propagation delay based on the PDC type, and uses the propagation delay to perform time synchronization with the timing device; the reliability of TSN / TSC support between the timing device and the device being timed can be improved. In addition, the embodiment of the present application can also support UE-to-UE timing in the sidelink scenario, thereby improving the reliability of TSN / TSC support in the sidelink.

[0251] The above content elaborates on the method provided by the present application. In order to facilitate the implementation of the above scheme of the embodiment of the present application, the embodiment of the present application also provides corresponding devices or equipment.

[0252] The present application divides the functional modules of the first device and the second device according to the above-mentioned method embodiment. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. The above-mentioned integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in this application is schematic and is only a logical functional division. There may be other division methods in actual implementation. The communication device of the embodiment of the present application will be described in detail below with reference to Figures 12 to 14.

[0253] 12 is a schematic diagram of a communication device according to an embodiment of the present invention. As shown in FIG12 , the communication device may include a transceiver unit 10 and a processing unit 20 .

[0254] In some embodiments of the present application, the communication device may be a chip or circuit disposed in the first device shown above or disposed in the first device, that is, the communication device may be used to execute the steps or functions performed by the first device in the above method embodiments.

[0255] In one design, the processing unit 20 is used to determine a first PDC type; the transceiver unit 10 is used to send first information to a second device, where the first information is used to indicate the first PDC type; the transceiver unit 10 is also used to receive second information from the second device for executing PDC, where the second information corresponds to the first PDC type; the transceiver unit 10 is also used to receive reference time information from the second device; and the processing unit 20 is also used to perform time synchronization with the second device based on the reference time information and the second information.

[0256] Exemplarily, the processing unit 20 is specifically used to: determine the first PDC type based on the correspondence between the business information and the PDC type, and the business information of the first device; or, determine the first PDC type based on the correspondence between the location information and the PDC type, and the location information of the first device; or, determine the first PDC type based on the correspondence between the available resources and the PDC type, and the available resources of the first device.

[0257] Exemplarily, the first PDC type is an RTT-based PDC type, and the second information is used to indicate a receive-transmit time difference of the second device. Alternatively, the first PDC type is a TA-based PDC type, and the second information is used to indicate a TA value.

[0258] Exemplarily, the second information is used to indicate a receive-send time difference of the second device. The processing unit 20 is further configured to perform time synchronization with the second device based on the reference time information, the second information, and the receive-send time difference of the first device.

[0259] Illustratively, the first PDC type is different from the second PDC type, and the second PDC type is a PDC type corresponding to the PDC currently executed by the first device or the second device.

[0260] Exemplarily, the transceiver unit 10 is further used to receive third information from the second device, where the third information is used to indicate a reference signal, where the reference signal corresponds to the first PDC type, and where the reference signal is used to measure a receive-send time difference of the first device or to determine a TA.

[0261] In the embodiment of the present application, the description of the first information, the second information, the third information, the reference time information, the first PDC type, etc. can be referred to the introduction in the method embodiment shown in Figure 9 above, and will not be described in detail here.

[0262] It is understood that the specific descriptions of the transceiver unit and the processing unit shown in the embodiment of the present application are merely examples. For the specific functions or execution steps of the transceiver unit and the processing unit, reference can be made to the method embodiment shown in FIG9 above, which will not be described in detail here. In addition, the technical effects of the embodiment of the present application refer to the technical effects of the method embodiment shown in FIG9 above, which will not be repeated here for the sake of brevity.

[0263] In another design, the processing unit 20 is used to determine the first PDC type; the transceiver unit 10 is used to send first information to the second device, where the first information is used to indicate the first PDC type; the transceiver unit 10 is also used to receive reference time information, where the reference time information corresponds to the first PDC type; the processing unit 20 is also used to perform time synchronization with the second device based on the reference time information.

[0264] Exemplarily, the processing unit 20 is specifically used to: determine the first PDC type based on the correspondence between the business information and the PDC type, and the business information of the first device; or, determine the first PDC type based on the correspondence between the location information and the PDC type, and the location information of the first device; or, determine the first PDC type based on the correspondence between the available resources and the PDC type, and the available resources of the first device.

[0265] Exemplarily, the first PDC type is an RTT-based PDC type, or the first PDC type is a TA-based PDC type.

[0266] Illustratively, the first PDC type is different from the second PDC type, and the second PDC type is a PDC type corresponding to the PDC currently executed by the first device or the second device.

[0267] Exemplarily, the first PDC type is an RTT-based PDC type. The transceiver unit 10 is further configured to receive fourth information for requesting a receive-transmit time difference of the first device; and to send fifth information for indicating a receive-transmit time difference of the first device.

[0268] Exemplarily, the first PDC type is an RTT-based PDC type. The transceiver unit 10 is further configured to receive third information indicating a reference signal corresponding to the first PDC type, the reference signal being used to measure a receive-transmit time difference of the first device or to determine a TA.

[0269] In the embodiment of the present application, the description of the first information, the third information, the fourth information, the fifth information, the reference time information, the first PDC type, etc. can be referred to the introduction in the method embodiment shown in Figure 10 above, and will not be described in detail here.

[0270] It is understood that the specific descriptions of the transceiver unit and the processing unit shown in the embodiment of the present application are merely examples. For the specific functions or execution steps of the transceiver unit and the processing unit, reference can be made to the method embodiment shown in FIG10 above, which will not be described in detail here. In addition, the technical effects of the embodiment of the present application refer to the technical effects of the method embodiment shown in FIG10 above, which will not be repeated here for the sake of brevity.

[0271] In another design, the transceiver unit 10 is used to receive first information from the second device, where the first information is used to indicate the first PDC type; and the processing unit 20 is used to parse the first information to obtain the first PDC type.

[0272] Exemplarily, the transceiver unit 10 is further used to receive second information for executing PDC, where the second information corresponds to the first PDC type determination; the transceiver unit 10 is further used to receive reference time information; and the processing unit 20 is further used to perform time synchronization with the second device based on the reference time information and the second information.

[0273] Exemplarily, the first PDC type is an RTT-based PDC type, and the second information is used to indicate a receive-send time difference of the second device; or, the first PDC type is a TA-based PDC type, and the second information is used to indicate a TA value.

[0274] Exemplarily, the second information is used to indicate a receive-send time difference of the second device. The processing unit 20 is further configured to perform time synchronization with the second device based on the reference time information, the second information, and the receive-send time difference of the first device.

[0275] Exemplarily, the first PDC type is an RTT-based PDC type. The transceiver unit 10 is further configured to receive fourth information from the second device, the fourth information being used to request a receive-transmit time difference of the first device; the transceiver unit 10 is further configured to send fifth information, the fifth information being used to indicate a receive-transmit time difference of the first device; the transceiver unit 10 is further configured to receive reference time information from the second device; and the processing unit 20 is further configured to perform time synchronization with the second device based on the reference time information.

[0276] Exemplarily, the transceiver unit 10 is further used to receive third information from the second device, where the third information is used to indicate a reference signal, where the reference signal corresponds to the first PDC type, and where the reference signal is used to measure a receive-send time difference of the first device or to determine a TA.

[0277] Exemplarily, the first PDC type is different from the second PDC type, and the second PDC type is a PDC type corresponding to the PDC currently executed by the first device or the second device.

[0278] In the embodiment of the present application, the description of the first information, the second information, the third information, the fourth information, the fifth information, the reference time information, the first PDC type, etc. can be referred to the introduction in the method embodiment shown in Figure 11 above, and will not be described in detail here.

[0279] It is understood that the specific descriptions of the transceiver unit and the processing unit shown in the embodiment of the present application are merely examples. For the specific functions or execution steps of the transceiver unit and the processing unit, reference can be made to the method embodiment shown in FIG11 above, which will not be described in detail here. In addition, the technical effects of the embodiment of the present application refer to the technical effects of the method embodiment shown in FIG11 above, which will not be repeated here for the sake of brevity.

[0280] Reusing Figure 12, in some other embodiments of the present application, the communication device may be the second device shown above or a chip or circuit provided in the second device. That is, the communication device may be used to execute the steps or functions performed by the second device in the above method embodiment.

[0281] In one design, the transceiver unit 10 is used to receive first information from a first device, where the first information is used to indicate a first PDC type; the transceiver unit 10 is also used to send second information for executing PDC to the first device, where the second information is determined based on the first PDC type; the transceiver unit 10 is also used to send reference time information to the first device, where the reference time information and the second information are used for time synchronization between the first device and the second device.

[0282] Exemplarily, the processing unit 20 is configured to generate the second information and the reference time information.

[0283] Exemplarily, the first PDC type is an RTT-based PDC type, and the second information is used to indicate a receive-send time difference of the second device; or, the first PDC type is a TA-based PDC type, and the second information is used to indicate a TA value.

[0284] Exemplarily, the first PDC type is different from the second PDC type, and the second PDC type is a PDC type corresponding to the PDC currently executed by the first device or the second device.

[0285] Exemplarily, the transceiver unit 10 is further used to send third information to the first device, where the third information is used to indicate a reference signal, which is determined based on the first PDC type and is used to measure the receive-transmit time difference of the first device or to determine the TA of the second device.

[0286] Exemplarily, the processing unit 20 is further configured to generate third information.

[0287] In the embodiment of the present application, the description of the first information, the second information, the third information, the reference time information, the first PDC type, etc. can be referred to the introduction in the method embodiment shown in Figure 9 above, and will not be described in detail here.

[0288] It is understood that the specific descriptions of the transceiver unit and the processing unit shown in the embodiment of the present application are merely examples. For the specific functions or execution steps of the transceiver unit and the processing unit, reference can be made to the method embodiment shown in FIG9 above, which will not be described in detail here. In addition, the technical effects of the embodiment of the present application refer to the technical effects of the method embodiment shown in FIG9 above, which will not be repeated here for the sake of brevity.

[0289] In another design, the transceiver unit 10 is used to receive first information from the first device, where the first information is used to indicate a first PDC type; the processing unit 20 is used to perform PDC based on the first PDC type; the transceiver unit 10 is also used to send reference time information passing through the PDC to the first device, where the reference time information is used for time synchronization between the second device and the first device.

[0290] Exemplarily, the first PDC type is a TA-based PDC type. The processing unit 20 is specifically configured to perform PDC based on the TA.

[0291] Exemplarily, the first PDC type is an RTT-based PDC type. The processing unit 20 is specifically configured to perform PDC based on a receive-send time difference of the first device and a receive-send time difference of the second device.

[0292] Exemplarily, the processing unit 20 is specifically used to control the transceiver unit 10 to send fourth information to the first device and receive fifth information from the first device, the fourth information is used to request the receive-send time difference of the first device, and the fifth information is used to indicate the receive-send time difference of the first device.

[0293] Exemplarily, the transceiver unit 10 is further used to send third information to the first device, where the third information is used to indicate a reference signal, which is determined based on the first PDC type and is used to measure the receive-transmit time difference of the first device or to determine the TA of the second device.

[0294] Exemplarily, the first PDC type is different from the second PDC type, and the second PDC type is a PDC type corresponding to the PDC executed by the second device before receiving the first information.

[0295] In the embodiment of the present application, the description of the first information, the third information, the fourth information, the fifth information, the reference time information, the first PDC type, etc. can be referred to the introduction in the method embodiment shown in Figure 10 above, and will not be described in detail here.

[0296] It is understood that the specific descriptions of the transceiver unit and the processing unit shown in the embodiment of the present application are merely examples. For the specific functions or execution steps of the transceiver unit and the processing unit, reference can be made to the method embodiment shown in FIG10 above, which will not be described in detail here. In addition, the technical effects of the embodiment of the present application refer to the technical effects of the method embodiment shown in FIG10 above, which will not be repeated here for the sake of brevity.

[0297] In another design, the processing unit 20 is used to determine the first PDC type based on preset rules, which preset rules include one or more of the following: a correspondence between service information and PDC type, a correspondence between location information and PDC type, or a correspondence between available resources and PDC type; the transceiver unit 10 is used to send first information to the first device, where the first information is used to indicate the first PDC type.

[0298] Exemplarily, the transceiver unit 10 is also used to send second information for executing PDC to the first device, and the second information is determined based on the first PDC type; the transceiver unit 10 is also used to send reference time information to the first device, and the reference time information and the second information are used for time synchronization between the first device and the second device.

[0299] Exemplarily, the first PDC type is an RTT-based PDC type, and the second information is used to indicate a receive-send time difference of the second device; or, the first PDC type is a TA-based PDC type, and the second information is used to indicate a TA value.

[0300] Exemplarily, the first PDC type is an RTT-based PDC type. The transceiver unit 10 is further configured to send fourth information to the first device, the fourth information being used to request a receive-transmit time difference of the first device; the transceiver unit 10 is further configured to receive fifth information from the first device, the fifth information being used to indicate a receive-transmit time difference of the first device; and the transceiver unit 10 is further configured to send reference time information to the first device, the reference time information being determined based on the receive-transmit time difference of the first device and the receive-transmit time difference of the second device, the reference time information being used for time synchronization between the second device and the first device.

[0301] Exemplarily, the processing unit 20 is specifically used to: determine the first PDC type based on the correspondence between the business information and the PDC type, and the business information of the first device; or, determine the first PDC type based on the correspondence between the location information and the PDC type, and the location information of the first device; or, determine the first PDC type based on the correspondence between the available resources and the PDC type, and the available resources of the first device.

[0302] Illustratively, the first PDC type is different from the second PDC type, and the second PDC type is a PDC type corresponding to the PDC currently executed by the first device or the second device.

[0303] In the embodiment of the present application, the description of the first information, the second information, the third information, the fourth information, the fifth information, the reference time information, the first PDC type, etc. can be referred to the introduction in the method embodiment shown in Figure 11 above, and will not be described in detail here.

[0304] It is understood that the specific descriptions of the transceiver unit and the processing unit shown in the embodiment of the present application are merely examples. For the specific functions or execution steps of the transceiver unit and the processing unit, reference can be made to the method embodiment shown in FIG11 above, which will not be described in detail here. In addition, the technical effects of the embodiment of the present application refer to the technical effects of the method embodiment shown in FIG11 above, which will not be repeated here for the sake of brevity.

[0305] The first and second devices of the embodiments of the present application have been described above. The following describes possible product forms of the first and second devices. It should be understood that any product having the functions of the first or second device described in FIG. 12 falls within the scope of protection of the embodiments of the present application. It should also be understood that the following description is merely illustrative and does not limit the product forms of the communication devices of the embodiments of the present application to these examples.

[0306] In one possible implementation, in the communication device shown in FIG12 , the processing unit 20 may be one or more processors, and the transceiver unit 10 may be a transceiver. Alternatively, the transceiver unit 10 may be a transmitting unit and a receiving unit, wherein the transmitting unit may be a transmitter and the receiving unit may be a receiver, and the transmitting unit and receiving unit are integrated into a single device, such as a transceiver. In embodiments of the present application, the processor and transceiver may be coupled, and the connection method between the processor and transceiver is not limited in embodiments of the present application. During the execution of the above-described method, the process of sending information in the above-described method can be understood as the process of the processor outputting the above-described information. When outputting the above-described information, the processor outputs the above-described information to the transceiver for transmission by the transceiver. After being output by the processor, the above-described information may require further processing before reaching the transceiver. Similarly, the process of receiving information in the above-described method can be understood as the process of the processor receiving the above-described information. When the processor receives the input information, the transceiver receives the above-described information and inputs it into the processor. Furthermore, after the transceiver receives the above-described information, the above-described information may require further processing before being input into the processor.

[0307] Referring to Figure 13, Figure 13 is another structural diagram of a communication device provided in an embodiment of the present application. As shown in Figure 13, the communication device provided in an embodiment of the present application can be used to implement the method described in the above method embodiment, and reference can be made to the description in the above method embodiment. The communication device can be a first device, or a second device, or a chip therein. Exemplarily, the communication device includes one or more processors 1001 and a transceiver 1002. The communication device may further include a memory 1003. In one implementation, the communication device also includes an input and output device (not shown in the figure).

[0308] Processor 1001 is primarily used to process communication protocols and communication data, control the entire communication device, execute software programs, and process software program data. Memory 1003 is primarily used to store software programs and data. Transceiver 1002 may include control circuitry and an antenna. The control circuitry is primarily used to convert baseband signals into radio frequency signals and process radio frequency signals. The antenna is primarily used to transmit and receive radio frequency signals in the form of electromagnetic waves. Input / output devices, such as a touch screen, display, and keyboard, are primarily used to receive user input and output data to the user.

[0309] When the communication device is powered on, the processor 1001 can read the software program in the memory 1003, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be sent wirelessly, the processor 1001 performs baseband processing on the data to be sent and outputs the baseband signal to the radio frequency circuit. The radio frequency circuit performs radio frequency processing on the baseband signal and then transmits the radio frequency signal to the outside in the form of electromagnetic waves through the antenna. When data is sent to the communication device, the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor 1001. The processor 1001 converts the baseband signal into data and processes the data.

[0310] In another implementation, the RF circuit and antenna may be provided independently of the processor performing baseband processing. For example, in a distributed scenario, the RF circuit and antenna may be remotely arranged independent of the communication device.

[0311] The processor 1001 , the transceiver 1002 , and the memory 1003 may be connected via a communication bus.

[0312] Exemplarily, when the communication device is used to execute the steps, methods, or functions performed by the first device in the embodiment shown in FIG. 9 above, the processor 1001 can be used to execute steps S101 and S105 in FIG. 9 , and / or to execute other processes of the technology described herein; the transceiver 1002 can be used to execute step S102 in FIG. 9 , and / or to execute other processes of the technology described herein.

[0313] Exemplarily, when the communication device is used to execute the steps, methods, or functions performed by the second device in the embodiment shown in FIG. 9 above, the processor 1001 can be used to generate the second information sent in step S103 in FIG. 9 and the reference time information sent in step S104, and / or for executing other processes of the technology described herein; the transceiver 1002 can be used to execute steps S103 and S104 in FIG. 9, and / or for other processes of the technology described herein.

[0314] Exemplarily, when the communication device is used to execute the steps, methods, or functions performed by the first device in the embodiment shown in FIG. 10 above, the processor 1001 can be used to execute steps S201 and S205 in FIG. 10 , and / or to execute other processes of the technology described herein; the transceiver 1002 can be used to execute step S202 in FIG. 10 , and / or to execute other processes of the technology described herein.

[0315] Exemplarily, when the communication device is used to execute the steps, methods, or functions performed by the second device in the embodiment shown in FIG. 10 above, the processor 1001 can be used to execute step S203 in FIG. 10 , and / or to execute other processes of the technology described herein; the transceiver 1002 can be used to execute step S204 in FIG. 10 , and / or to execute other processes of the technology described herein.

[0316] Exemplarily, when the communication device is used to execute the steps, methods, or functions performed by the first device in the embodiment shown in FIG. 11 above, the processor 1001 can be used to execute steps S303, S306, and S309 in FIG. 11, and / or for executing other processes of the technology described herein; the transceiver 1002 can be used to receive various information, and / or for other processes of the technology described herein.

[0317] Exemplarily, when the communication device is used to execute the steps, methods, or functions performed by the second device in the embodiment shown in FIG. 11 above, the processor 1001 can be used to execute steps S301 and S307 in FIG. 11 , and / or other processes for executing the technology described herein; the transceiver 1002 can be used to execute steps S302, S304, S305, and S308 in FIG. 11 , and / or other processes for the technology described herein.

[0318] In any of the above implementations, the processor 1001 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing the receiving and transmitting functions may be separate or integrated. The transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or the transceiver circuit, interface, or interface circuit may be used for transmitting or delivering signals.

[0319] In any of the above implementations, processor 1001 may store instructions, which may be computer programs. The computer programs, when executed on processor 1001, may cause the communication device to perform the methods described in the above method embodiments. The computer programs may be embedded in processor 1001, in which case processor 1001 may be implemented by hardware.

[0320] In one implementation, the communication device may include a circuit that can implement the functions of sending, receiving, or communicating in the aforementioned method embodiment. The processor and transceiver described in this application can be implemented in an integrated circuit (IC), an analog IC, a radio frequency integrated circuit (RFIC), a mixed signal IC, an application specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (nMetal-oxide-semiconductor, NMOS), P-channel metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (bipolar junction transistor, BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0321] It is understood that the communication device shown in the embodiment of the present application may also have more components than those in Figure 13, and the embodiment of the present application is not limited to this. The method performed by the processor and transceiver shown above is only an example. For the specific steps performed by the processor and transceiver, please refer to the introduction of the method embodiment above.

[0322] In another possible implementation, in the communication device shown in Figure 12, the processing unit 20 can be one or more logic circuits, and the transceiver unit 10 can be an input / output interface, or a communication interface, or an interface circuit, or an interface, etc. Or the transceiver unit 10 can also be a sending unit and a receiving unit, the sending unit can be an output interface, the receiving unit can be an input interface, and the sending unit and the receiving unit are integrated into one unit, such as an input / output interface. Referring to Figure 14, Figure 14 is another structural diagram of a communication device provided in an embodiment of the present application. As shown in Figure 14, the communication device shown in Figure 14 includes a logic circuit 901 and an interface 902. That is, the above-mentioned processing unit 20 can be implemented with a logic circuit 901, and the transceiver unit 10 can be implemented with an interface 902. Among them, the logic circuit 901 can be a chip, a processing circuit, an integrated circuit or a system on chip (SoC) chip, etc., and the interface 902 can be a communication interface, an input / output interface, a pin, etc. Exemplarily, Figure 14 is shown as an example of the above-mentioned communication device being a chip, and the chip includes a logic circuit 901 and an interface 902.

[0323] In the embodiment of the present application, the logic circuit and the interface may also be coupled to each other. The embodiment of the present application does not limit the specific connection method between the logic circuit and the interface.

[0324] Exemplarily, when the communication device is used to execute the steps, methods or functions performed by the first device in the method embodiment shown in Figure 9 above, the logic circuit 901 is used to determine the first PDC type; the interface 902 is used to send first information, which is used to indicate the first PDC type; the interface 902 is used to receive second information for executing PDC, which corresponds to the first PDC type; the interface 902 is used to receive reference time information; and the logic circuit 901 is used to perform time synchronization with the second device based on the reference time information and the second information.

[0325] Exemplarily, when the communication device is used to execute the steps, methods or functions performed by the second device in the method embodiment shown in Figure 9 above, the interface 902 is used to receive first information, and the first information is used to indicate a first PDC type; the logic circuit 901 is used to determine the second information based on the first PDC type; the interface 902 is also used to send second information for executing PDC; the interface 902 is also used to send reference time information, and the reference time information and the second information are used for time synchronization between the first device and the second device.

[0326] In the embodiment of the present application, the description of the first information, the second information, the reference time information, the first PDC type, etc. can be referred to the description of the method embodiment shown in FIG9 above, and will not be described in detail here. It is understood that the specific description of the logic circuit 901 and the interface 902 can also be referred to the description of the processing unit and the transceiver unit shown in FIG12, and will not be repeated here.

[0327] Exemplarily, when the communication device is used to execute the steps, methods or functions performed by the first device in the method embodiment shown in Figure 10 above, the logic circuit 901 is used to determine the first PDC type; the interface 902 is used to send first information, which is used to indicate the first PDC type; the interface 902 is also used to receive reference time information, which corresponds to the first PDC type; the logic circuit 901 is also used to perform time synchronization with the second device based on the reference time information.

[0328] Exemplarily, when the communication device is used to execute the steps, methods or functions performed by the second device in the method embodiment shown in Figure 10 above, the interface 902 is used to receive first information, and the first information is used to indicate a first PDC type; the logic circuit 901 is used to perform PDC based on the first PDC type; the interface 902 is also used to send reference time information passing through the PDC, and the reference time information is used for time synchronization between the second device and the first device.

[0329] In the embodiment of the present application, the description of the first information, reference time information, first PDC type, etc. can be referred to the description of the method embodiment shown in FIG10 above, and will not be described in detail here. It is understood that the specific description of the logic circuit 901 and the interface 902 can also be referred to the description of the processing unit and the transceiver unit shown in FIG12, and will not be repeated here.

[0330] Exemplarily, when the communication device is used to execute the steps, methods or functions performed by the first device in the method embodiment shown in Figure 11 above, the interface 902 is used to receive first information from the second device, and the first information is used to indicate the first PDC type; the logic circuit 901 is used to parse the first information and obtain the first PDC type.

[0331] Exemplarily, when the communication device is used to execute the steps, methods or functions performed by the second device in the method embodiment shown in Figure 11 above, the logic circuit 901 is used to determine the first PDC type based on preset rules, and the preset rules include one or more of the following: the correspondence between service information and PDC type, the correspondence between location information and PDC type, or the correspondence between available resources and PDC type; the interface 902 is used to send first information to the first device, and the first information is used to indicate the first PDC type.

[0332] In the embodiment of the present application, the description of the first information, the first PDC type, etc. can be referred to the description of the method embodiment shown in FIG11 above, and will not be described in detail here. It is understood that the specific description of the logic circuit 901 and the interface 902 can also be referred to the description of the processing unit and the transceiver unit shown in FIG12, and will not be repeated here.

[0333] It can be understood that the communication device shown in the embodiment of the present application can implement the method provided in the embodiment of the present application in the form of hardware, or can implement the method provided in the embodiment of the present application in the form of software, etc., and the embodiment of the present application is not limited to this.

[0334] For the specific implementation methods of the various embodiments shown in Figure 14, you can also refer to the above embodiments, which will not be described in detail here.

[0335] An embodiment of the present application also provides a communication system, which includes a first device and a second device. The first device and the second device can be used to execute the method in any of the aforementioned method embodiments (Figure 9, or Figure 10, or Figure 11).

[0336] In addition, the present application also provides a computer program, which is used to implement the operations and / or processing performed by the first device in the method provided by the present application.

[0337] The present application also provides a computer program, which is used to implement the operations and / or processing performed by the second device in the method provided by the present application.

[0338] The present application also provides a computer-readable storage medium, which stores computer code. When the computer code runs on a computer, the computer executes the operations and / or processing performed by the first device in the method provided by the present application.

[0339] The present application also provides a computer-readable storage medium, which stores computer code. When the computer code runs on a computer, the computer executes the operations and / or processing performed by the second device in the method provided by the present application.

[0340] The present application also provides a computer program product, which includes computer code or computer program. When the computer code or computer program runs on a computer, the operations and / or processing performed by the first device in the method provided by the present application are executed.

[0341] The present application also provides a computer program product, which includes computer code or computer program. When the computer code or computer program runs on a computer, the operations and / or processing performed by the second device in the method provided by the present application are executed.

[0342] 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 schematic. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, or can be electrical, mechanical or other forms of connection.

[0343] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units may be selected according to actual needs to achieve the technical effects of the solutions provided in the embodiments of the present application.

[0344] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0345] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it 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 prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a readable storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned readable storage medium includes: 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.

[0346] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. An information interaction method, characterized in that: include: The first device determines a first propagation delay compensation PDC type; The first device sends first information to the second device, where the first information is used to indicate the first PDC type; The first device receives second information for performing PDC from the second device, the second information corresponding to the first PDC type; The first device receives reference time information from the second device; The first device performs time synchronization with the second device based on the reference time information and the second information.

2. The method according to claim 1, characterized in that: The first device determines a first propagation delay compensation (PDC) type, including: The first device determines a first PDC type based on a correspondence between service information and a propagation delay compensation PDC type and service information of the first device; Or, the first device determines the first PDC type based on the correspondence between the location information and the propagation delay compensation PDC type, and the location information of the first device; Alternatively, the first device determines the first PDC type based on a correspondence between available resources and propagation delay compensation PDC types and available resources of the first device.

3. The method according to claim 1 or 2, characterized in that: The first device is a terminal device, and the second device is a network device; Alternatively, the first device is a first terminal device, and the second device is a second terminal device.

4. The method according to any one of claims 1 to 3, characterized in that The first PDC type is a PDC type based on a round trip time RTT, and the second information is used to indicate a reception-transmission time difference of the second device; Alternatively, the first PDC type is a PDC type based on a timing advance TA, and the second information is used to indicate a value of TA.

5. The method according to any one of claims 1 to 4, characterized in that The second information is used to indicate a reception-transmission time difference of the second device; The first device performs time synchronization with the second device based on the reference time information and the second information, including: The first device performs time synchronization with the second device based on the reference time information, the second information, and a reception-transmission time difference of the first device.

6. The method according to any one of claims 1 to 5, characterized in that The first PDC type is different from the second PDC type, and the second PDC type is a PDC type corresponding to the PDC currently executed by the first device or the second device.

7. The method according to any one of claims 1 to 6, characterized in that The method further comprises: The first device receives third information from the second device, where the third information is used to indicate a reference signal, where the reference signal corresponds to the first PDC type, and where the reference signal is used to measure a reception-transmission time difference of the first device or to determine a TA.

8. An information interaction method, characterized in that: include: The second device receives first information from the first device, where the first information is used to indicate a first propagation delay compensation PDC type; The second device sends second information for performing PDC to the first device, where the second information is determined based on the first PDC type; The second device sends reference time information to the first device, and the reference time information and the second information are used for time synchronization between the first device and the second device.

9. The method according to claim 8, characterized in that The first device is a terminal device, and the second device is a network device; Alternatively, the first device is a first terminal device, and the second device is a second terminal device.

10. The method according to claim 8 or 9, characterized in that: The first PDC type is a PDC type based on a round trip time RTT, and the second information is used to indicate a reception-transmission time difference of the second device; Alternatively, the first PDC type is a PDC type based on a timing advance TA, and the second information is used to indicate a value of TA.

11. The method according to any one of claims 8 to 10, characterized in that The first PDC type is different from the second PDC type, and the second PDC type is a PDC type corresponding to the PDC currently executed by the first device or the second device.

12. The method according to any one of claims 8 to 11, characterized in that The method further comprises: The second device sends third information to the first device, where the third information is used to indicate a reference signal, where the reference signal is determined based on the first PDC type, and where the reference signal is used to measure a reception-transmission time difference of the first device or is used by the second device to determine a TA.

13. An information interaction method, characterized in that: include: The second device determines the first propagation delay compensation PDC type based on a preset rule, wherein the preset rule includes one or more of the following: a correspondence between service information and PDC type, a correspondence between location information and PDC type, or a correspondence between available resources and PDC type; The second device sends first information to the first device, where the first information is used to indicate the first PDC type.

14. The method according to claim 13, characterized in that The method further comprises: The second device sends second information for performing PDC to the first device, where the second information is determined based on the first PDC type; The second device sends reference time information to the first device, and the reference time information and the second information are used for time synchronization between the first device and the second device.

15. The method according to claim 14, characterized in that The first PDC type is a PDC type based on a round trip time RTT, and the second information is used to indicate a reception-transmission time difference of the second device; Alternatively, the first PDC type is a PDC type based on a timing advance TA, and the second information is used to indicate a value of TA.

16. The method according to claim 13, characterized in that The first PDC type is a PDC type based on a round trip time RTT; The method further comprises: The second device sends fourth information to the first device, where the fourth information is used to request a reception-transmission time difference of the first device; The second device receives fifth information from the first device, where the fifth information is used to indicate a reception-transmission time difference of the first device; The second device sends reference time information to the first device, where the reference time information is determined based on a receive-send time difference of the first device and a receive-send time difference of the second device, and the reference time information is used for time synchronization between the first device and the second device.

17. The method according to any one of claims 13 to 16, characterized in that The second device determines the first propagation delay compensation PDC type based on a preset rule, including: The second device determines the first PDC type based on the correspondence between the service information and the propagation delay compensation PDC type and the service information of the first device; Or, the second device determines the first PDC type based on the correspondence between the location information and the PDC type and the location information of the first device; Alternatively, the second device determines the first PDC type based on a correspondence between available resources and PDC types and available resources of the first device.

18. The method according to any one of claims 13 to 17, characterized in that The first device is a terminal device, and the second device is a network device; Alternatively, the first device is a first terminal device, and the second device is a second terminal device.

19. The method according to any one of claims 13 to 18, characterized in that The first PDC type is different from the second PDC type, and the second PDC type is a PDC type corresponding to the PDC currently executed by the first device or the second device.

20. The method according to any one of claims 13 to 19, characterized in that The method further comprises: The second device sends third information to the first device, where the third information is used to indicate a reference signal, where the reference signal is determined based on the first PDC type, and where the reference signal is used to measure a reception-transmission time difference of the first device or is used by the second device to determine a TA.

21. A communication device, characterized in that: The method comprises a module or a unit for executing the method according to any one of claims 1 to 20.

22. A communication device, characterized in that: It includes a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices and transmit them to the processor or send signals from the processor to other communication devices, and the processor is used to implement the method as described in any one of claims 1 to 20 through a logic circuit or executing code instructions.

23. A readable storage medium, characterized in that: Used to store a program, the program being executed by one or more processors so that a device including the one or more processors performs the method according to any one of claims 1 to 20.

24. A communication system, characterized in that: include: A first device for performing the method of any one of claims 1 to 7, and a second device for performing the method of any one of claims 8 to 12; Alternatively, a second device for executing the method according to any one of claims 13 to 20, and a corresponding first device.

Images