WO2020057410A1

WO2020057410A1 - Synchronization method and communication apparatus

Info

Publication number: WO2020057410A1
Application number: PCT/CN2019/105307
Authority: WO
Inventors: 范强; 王君; 酉春华; 戴明增; 卓义斌
Original assignee: 华为技术有限公司
Priority date: 2018-09-18
Filing date: 2019-09-11
Publication date: 2020-03-26
Also published as: CN110912846A; CN110912846B

Abstract

Provided are a synchronization method and a communication apparatus. A first wireless access network device can receive, from a second wireless access network device, a first DFN offset value of a first carrier, and send a second DFN offset value that corresponds to the first carrier to a first terminal device, so that the first terminal device determines a DFN and a subframe number according to the second DFN offset value and thus shifts a subframe boundary derived by using a GNSS as a synchronization reference source, and that the subframe boundary derived by using the GNSS as the synchronization reference source is aligned with a subframe boundary derived by using a wireless access network device as the synchronization reference source, and thus, mutual interference between NR SL transmission controlled by an LTE Uu interface and NR UL transmission for a neighboring station is prevented or mutual interference between LTE SL transmission controlled by an NR Uu interface and LTE UL transmission for a neighboring station can be prevented.

Description

Method and communication device for synchronization

This application claims priority from a Chinese patent application filed on September 18, 2018 with the Chinese Patent Office, application number 201811087406.2, and application name "Synchronized Method and Communication Device", the entire contents of which are incorporated herein by reference.

Technical field

The present application relates to the field of communication, and more specifically, to a method and a communication device for synchronization in the field of communication.

Background technique

Vehicle to Vehicle (V2X) is considered to be one of the fields with the most industrial potential and the clearest market demand in the Internet of Things system. It has the characteristics of wide application space, large industrial potential, and strong social benefits. It is of great significance to innovate and develop the communications industry, build a new model and new business model of automobiles and transportation services, promote the innovation and application of autonomous driving technology, and improve transportation efficiency and safety. The Internet of Vehicles refers to the provision of vehicle information through sensors mounted on the vehicle, on-board terminals, etc., and the communication between vehicles and vehicles, vehicles and people, vehicles and roadside infrastructure, and vehicles and networks through various communication technologies.

V2X communication involves two communication interfaces, namely the PC5 interface and the Uu interface. Among them, the V2X PC5 interface communication is a direct communication between V2X terminal devices, and its communication link is also defined as a sidelink (SL); V2X Uu interface communication is where the sender V2X terminal device passes V2X data through Uu The communication method that the interface sends to the network device and the network device sends to the V2X application server for processing, and then the V2X application server sends it to the receiver V2X terminal device.

In V2X communication, there may be a Long Term Evolution (LTE) Uu port to control new radio (NR) SL transmission, or an NR Uu port to control LTE SL transmission. At this time, how to avoid the mutual interference between the NR and SL transmissions controlled by the LTE Uu interface and the NR and UL transmissions of neighboring stations, or how to avoid the mutual interference of the LTE SL transmissions controlled by the NR Uu interface and the LTE UL transmissions of neighboring stations are urgently needed problem.

Summary of the Invention

The present application provides a synchronization method and a communication device, which can avoid mutual interference between NR and SL transmissions controlled by LTE Uu interfaces and NR and UL transmissions of neighboring stations, or can avoid LTE SL transmissions controlled by NR Uu interfaces and LTE UL of neighboring stations. Mutual interference in transmission.

In a first aspect, a synchronization method is provided, including:

The first radio access network device configures a first terminal device with a first carrier for side-link transmission;

Receiving, by the first radio access network device, a first direct frame number DFN offset value corresponding to the first carrier from a second radio access network device;

Sending, by the first radio access network device, a second DFN offset value corresponding to the first carrier to the first terminal device;

The first radio access network device operates in a first radio communication system, the second radio access network device and the first carrier operate in a second radio communication system, and the side link is The direct wireless communication link between the first terminal device and the second terminal device is described.

In the embodiment of the present application, the first radio access network device may receive the first DFN offset value of the first carrier from the second radio access network device, and send a second terminal device corresponding to the first carrier to the second DFN offset value. The DFN offset value enables the first terminal device to determine the DFN and the subframe number according to the second DFN offset value, and then offsets the subframe boundary derived using GNSS as the synchronization reference source, so that GNSS is used as the synchronization reference source The derived subframe boundary is aligned with the subframe boundary derived using the radio access network device as a synchronization reference source.

In the embodiment of the present application, the first radio access network device may send a second DFN offset value corresponding to the first carrier to the first terminal device according to the first DFN offset value. Here, the first DFN offset value may be the same as or different from the second DFN offset value, which is not limited in this embodiment of the present application.

In the embodiment of the present application, the first communication system and the second communication system may be the same or different. The first offsetDFN value and the second offsetDFN value may be the same or different.

As an example, in a scenario where an LTE eNB schedules a V2X terminal device for NR and SL transmission, the first communication system is an LTE communication system, the second communication system is an NR communication system, the first radio access network device is an LTE eNB, and the second radio The access network device is NR gNB. At this time, the LTE eNB configures the V2X terminal device as the first carrier for side-link SL transmission. In the scenario where NR gNB dispatches V2X terminal equipment for LTE SL transmission, the first communication system is the NR communication system, the second communication system is the LTE communication system, the first radio access network device is the NR gNB, and the second radio access network The device is an LTE eNB. At this time, the NR gNB configures the V2X terminal device as the first carrier for side-link SL transmission.

With reference to the first aspect, in some implementations of the first aspect, the first radio access network device receives a first direct frame number DFN corresponding to the first carrier from a second radio access network device Before the offset value, it also includes:

The first radio access network device sends first information to the second radio access network device, where the first information is used to request the first DFN offset value corresponding to the first carrier.

Exemplarily, the first information includes information of the SL carrier.

In an implementation manner, after determining the information of the NR and SL carrier, the LTE eNB notifies the neighbor of the corresponding NR and SL carrier through the Xn interface or the X2 interface, and the neighbor NR and the NB of the NR and gNB feedback the corresponding NR and SL carrier through the Xn interface. offsetDFN value.

In another implementation manner, the NR gNB will inform the LTE eNB of the information of the UL scheduled carriers and the corresponding offsetDFN value of each carrier through the Xn interface. If the LTE eNB is used in the carrier provided by the NR and the NB, the offsetDFN of the NR and the carrier is set to the corresponding offsetDFN value provided by the NR. If the LTE eNB is used in the NR and the carrier provided by the NR and the NB , The offsetDFN value of NR, SL, and carrier is set to 0.

Optionally, in the embodiment of the present application, the first radio access network device and the second radio access network device may exchange resource pool information on the first carrier.

With reference to the first aspect, in some implementations of the first aspect, before the first radio access network device sends the first information to the second radio access network device, the method further includes:

Receiving, by the first radio access network device, a measurement result of the first carrier in a neighboring cell reported by the first terminal device, where the neighboring cell is a cell provided by the second radio access network device. The cell measurement result may include cell information, and may also include the measured signal strength (for example, the RSRP or RSRQ or RSSI value of the cell).

After the first radio access network device receives the measurement result reported by the first terminal device, it can determine whether the NR SL transmission and the NR UL transmission of the second radio access network device interfere with each other according to the measurement result.

In the embodiment of the present application, according to the measurement and reporting of the terminal device, it can be ensured that only when there is interference between NR and SL transmission and NR and UL transmission, the LTE eNB and the specific NR gNB need to obtain an appropriate offsetDFN value. When there is no interference between NR SL transmission and NR UL transmission, the first radio access network device and the second radio access network device do not need to exchange offset DFN information through the Xn interface. Therefore, this embodiment can ensure the first radio access network The device and the second radio access network device only exchange the offsetDFN information when necessary, which can save signaling overhead.

With reference to the first aspect, in some implementation manners of the first aspect, the first DFN offset value and the second DFN offset value are the same.

Optionally, the first radio access network device may further indicate the access type of the SL carrier to the first terminal device. Exemplarily, the access type of the SL carrier includes an LTE access type and an NR access type.

Optionally, after the terminal device accesses the network and enters the RRC_CONNECTED state, it can report the SL communication capabilities it supports to the LTE eNB, such as only supporting LTE SL transmission, or only NR SL transmission, or both LTE SL transmission and NR SL transmission. In this way, the LTE eNB can configure the SL carrier that the terminal device can use for V2X communication and the access technology used on each SL carrier according to the SL communication capability reported by the terminal device.

In the embodiment of the present application, the first radio access network device may send the second offsetDFN value of the first carrier to the first terminal device multiple times (at least twice), where each second offsetDFN value configured at different time points may be the same It can also be different.

Optionally, in the embodiment of the present application, whether the first radio access network device reconfigures the offsetDFN value for the first terminal device after receiving the cell measurement result reported by the first terminal device depends on the first access network device. The implementation of this is not limited in the embodiments of the present application.

In this embodiment, the offset DFN value of the NR, SL, and carrier is obtained through the interaction between the first radio access network device and the second radio access network device. This process is transparent to the terminal device. Therefore, this solution is applicable to both connected and idle terminal devices. The terminal equipment can be reused with the existing LTE technology as much as possible to avoid increasing the implementation complexity of the terminal equipment. In addition, this embodiment does not require the terminal device to be equipped with an NR Uu module, and the proposed technical problem can be solved only by software upgrade, which reduces the hardware cost of the terminal device.

In a second aspect, a synchronization method is provided, including:

The second radio access network device sends a first direct frame number DFN offset value corresponding to the first carrier to the first radio access network device;

Wherein, the first carrier is a carrier configured by the first radio access network device for the first terminal device for side-link transmission, and the first radio access network device operates in the first radio communication standard. The second wireless access network device and the first carrier operate in a second wireless communication standard, and the side link is a direct-connected wireless communication link between the first terminal device and the second terminal device road.

With reference to the first aspect, in some implementations of the first aspect, before the second radio access network device sends the first direct frame number DFN offset value corresponding to the first carrier to the first radio access network device ,Also includes:

The second radio access network device sends first information to the first radio access network device, where the first information is used to request the first DFN value corresponding to the first carrier.

In a third aspect, a synchronization method is provided, which includes:

The first terminal device receives a second DFN offset value corresponding to a first carrier sent by a first radio access network device, where the first carrier is the first radio access network device and is the first terminal The carrier configured by the device for side-link transmission, the second DFN offset value is corresponding to the first carrier sent by the second radio access network device to the first radio access network device Determined by the first DFN;

Determining, by the first terminal device, a DFN and a subframe number according to the second DFN offset value;

With reference to the first aspect, in some implementations of the first aspect, before the receiving, by the first terminal device, the second DFN offset value corresponding to the first carrier sent by the first radio access network device, the method further includes:

The first terminal device reports a measurement result of the first carrier in a neighboring cell to the first radio access network device, where the neighboring cell is a cell provided by the second radio access network device.

With reference to the first aspect, in some implementations of the first aspect, the first DFN offset value is the same as the second DFN offset value.

In a fourth aspect, a synchronization method is provided, including:

Receiving, by a first terminal device, a third DFN offset value corresponding to a first carrier and sent by a second radio access network device;

Determining, by the first terminal device, a DFN and a subframe number according to the third DFN offset value;

The first carrier is a carrier configured by the first radio access network device for the first terminal device and used for side-link transmission, and the side-link is the first terminal device and a second carrier. A direct wireless communication link between terminal devices, the first wireless access network device operates in a first wireless communication system, and the second wireless access network device and the first carrier are in a second wireless communication system. run.

Therefore, in the embodiment of the present application, if the first terminal device can directly obtain the third offsetDFN value sent by the second radio access network device, the DFN and the subframe number are determined according to the third offsetDFN value, and then the GNSS is used for synchronization. The subframe boundary derived from the reference source is offset so that the subframe boundary derived from the GNSS as the synchronous reference source is aligned with the subframe boundary derived from the radio access network device as the synchronous reference source, thereby realizing LTEUu Control NR and SL transmission scenarios to avoid mutual interference between NR SL transmission and neighboring station NR and UL transmissions, or be able to avoid mutual interference between LTE SL transmission and neighboring station LTE UL transmissions in the NR Uu port control LTE SL transmission scenario.

In addition, in the embodiment of the present application, the LTE eNB can reuse the existing LTE technology, and has a small impact on the network device side. Because the offsetDFN value for NR and SL carriers set by NR and NB is more accurate, if the terminal device reads and applies the offset DFN value for NR and SL carriers carried by NR base stations, it can more effectively avoid interference between NR UL and NR SL transmissions.

With reference to the first aspect, in some implementation manners of the first aspect, the method further includes:

Determining, by the first terminal device, that a measurement result of the first carrier in a neighboring cell exceeds a first threshold, and the neighboring cell is a cell provided by the second radio access network device;

When the first terminal device determines that the measurement result of the first carrier in the neighboring cell exceeds a first threshold, the first terminal device determines a DFN and a subframe number according to the third DFN offset value.

Receiving, by the first terminal device, a second DFN offset value corresponding to the first carrier and sent by the first radio access network device;

When the first terminal device determines that the measurement result of the first carrier in the neighboring cell is less than or equal to a first threshold, the first terminal device determines a DFN and a subframe number according to the second DFN offset value.

In a fifth aspect, a synchronization method is provided, including:

The second radio access network device sends a third DFN offset value corresponding to the first carrier to the first terminal device;

Therefore, in the embodiment of the present application, if the first terminal device can directly obtain the third offsetDFN value sent by the second radio access network device, the DFN and the subframe number are determined according to the third offsetDFN value, and then the GNSS is used for synchronization. The subframe boundary derived from the reference source is offset so that the subframe boundary derived from the GNSS as the synchronous reference source is aligned with the subframe boundary derived from the radio access network device as the synchronous reference source, thereby realizing the LTE Uu port. Control NR and SL transmission scenarios to avoid mutual interference between NR SL transmission and neighboring station NR and UL transmissions, or be able to avoid mutual interference between LTE SL transmission and neighboring station LTE UL transmissions in the NR Uu port control LTE SL transmission scenario.

According to a sixth aspect, a communication apparatus is provided for performing any one of the foregoing aspects or a method in any possible implementation manner of any aspect. Exemplarily, the communication apparatus includes a unit for performing any one of the foregoing aspects or a method in any possible implementation manner of any aspect.

According to a seventh aspect, a communication device is provided. The device includes a processor and a transceiver. Optionally, the device may further include a memory and a bus system. The transceiver, the memory, and the processor are connected through the bus system. The memory is used to store instructions. The processor is used to execute instructions, such as executing instructions stored in the memory, to control the transceiver to receive and / or send signals. And when the processor executes an instruction, such as an instruction stored in the memory, the execution causes the processor or the communication device to execute a method in any one of the foregoing aspects or any possible implementation manner of any aspect.

According to an eighth aspect, a computer-readable medium is provided for storing a computer program, the computer program including instructions for performing a method in any possible implementation manner of any of the foregoing aspects.

According to a ninth aspect, a computer program product is provided. The computer program product includes computer program code. When the computer program code is used by a communication unit, a processing unit, or a transceiver of a communication device (for example, a terminal device or a network device). When the processor is running, the communication device is caused to execute the method in any possible implementation manner of any of the foregoing aspects.

According to a tenth aspect, a chip is provided. The chip is applicable to a communication device, and the chip includes at least one processor. When the at least one processor executes an instruction, the chip or the communication device executes any of the foregoing aspects. In a possible implementation manner, the chip may further include a memory, and the memory may be used to store related instructions.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a schematic diagram of a communication system to which an embodiment of the present application is applied.

FIG. 2 shows examples of SL subframe boundaries deduced using a radio access network device as a synchronization reference source and SL subframe boundaries deduced using GNSS as a synchronization reference source.

FIG. 3 shows a schematic diagram of offsetting a subframe boundary derived by using GNSS as a synchronization reference source.

FIG. 4 shows a schematic diagram of a communication system to which an embodiment of the present application is applied.

FIG. 5 shows a schematic flowchart of a synchronization method according to an embodiment of the present application.

FIG. 6 is a schematic flowchart of another synchronization method according to an embodiment of the present application.

FIG. 7 shows a schematic flowchart of another synchronization method according to an embodiment of the present application.

FIG. 8 shows a schematic block diagram of a communication device according to an embodiment of the present application.

FIG. 9 shows a schematic block diagram of another communication device according to an embodiment of the present application.

FIG. 10 shows a schematic block diagram of another communication device according to an embodiment of the present application.

FIG. 11 shows a schematic block diagram of a terminal device according to an embodiment of the present application.

detailed description

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

The technical solutions in the embodiments of the present application can be applied to a long term evolution (LTE) system, a WiFi system, a 5th generation (5G) mobile communication system, a new radio (NR), or a future evolved mobile Communication Systems. This application does not limit the mobile communication system applied in the embodiments.

The terminal device in the embodiments of the present application may also be referred to as a terminal, a user equipment (UE), a mobile station (MS), a mobile terminal (MT), and the like. The terminal device may be a sensor mounted on the vehicle in the V2X communication system, a vehicle-mounted terminal, a wireless terminal in self-driving, a wireless terminal in transportation safety, and the like. The embodiment of the present application does not limit the specific technology and specific device form adopted by the terminal device.

The radio access network device in the embodiment of the present application is a device that is deployed in a radio access network to provide a terminal device with a wireless communication function. Radio access network equipment may include various forms of base stations, macro base stations, micro base stations (also called small stations), relay stations, access points, new wireless controllers (new controllers, NR controllers), and centralized network elements ( centralized unit, radio remote module, distributed network unit, transmission point (TRP) or transmission point (TP), or any other wireless access device, but this application implements Examples are not limited to this. Among them, in a system adopting different wireless access technologies, the names of devices having a base station function may be different. For example, the wireless access network device may be an access point (AP) in a wireless local area network (WLAN) or an evolved NodeB (eNB or eNodeB) in an LTE system. It can also be a next generation base station (nNB) in a 5G mobile communication system, an NR communication system, or a base station in a future mobile communication system. The embodiment of the present application does not limit the specific technology and specific device form adopted by the wireless access network device.

FIG. 1 shows a schematic diagram of a communication system to which an embodiment of the present application is applied. As shown in FIG. 1, in the communication system, there may be a lateral link SL transmission between the terminal device V1 and the terminal device V2 and an uplink (uplink, UL) between the radio access network device 101 and the terminal device 102. transmission. The side link SL is a directly connected wireless communication link between the terminal device V1 and the terminal device V2, and the uplink UL is a wireless communication link between the radio access network device 101 and the terminal device 102. In the embodiment of the present application, a terminal device (for example, terminal device V1, terminal device V2) supporting V2X communication may be referred to as a V2X terminal device.

When a V2X terminal device (for example, terminal device V1) resides in a cell, system messages broadcast by the radio access network device through the cell can be read. Exemplarily, if the radio access network device supports V2X communication on the frequency in which the cell is located and / or other frequencies, the radio access network device may broadcast system information block (SIB) 21 information in the cell . Here, the frequency where the cell is located may be referred to as a carrier frequency, and the carrier may be, for example, carrier 1 in FIG. 1.

It should be noted that the radio access network device can configure a cell on multiple carrier frequency bands. For a terminal device, a frequency band in which a cell in which the terminal device resides can be referred to as a primary frequency. The other carrier frequency bands supported by the radio access network equipment are non-primary frequencies to the terminal equipment. For connected terminal equipment, if SCell is configured on a non-primary frequency, this frequency band is also called secondary frequency.

In the SIB21 information, the radio access network device can be configured for resource allocation configuration and synchronization configuration for V2X communication on the current frequency (that is, the frequency that the terminal device receives the SIB21), and / or resource allocation for V2X communication on other frequencies Configuration and synchronization configuration. As an example, the synchronization configuration may include a field "typeTxSync", which is used to indicate a synchronization reference source that is preferentially selected when performing V2X communication on one frequency. Exemplarily, the so-called selection of a synchronization reference source is to determine which synchronization frame of a synchronization reference source is used to determine a subframe boundary for V2X communication. Exemplarily, the synchronization reference source may be configured as a radio access network device (such as an eNB, gNB) or a global satellite navigation system (GNSS).

If the terminal device chooses to perform V2X communication on one frequency, and the corresponding "typeTxSync" in SIB21 is configured as the eNB, the terminal device selects a cell on the frequency as the synchronization reference source. The criteria for selecting which cell to use as the synchronization reference source meets any one or more of the following conditions:

If the frequency is a primary frequency, the terminal device selects a primary cell (PCell) or a serving cell (serving cell) as a synchronization reference source. Exemplarily, if the terminal device is in an RRC connected (RRC_CONNECTED) state, the primary frequency is the frequency at which the PCell is located, and if the terminal device is in the RRC idle (RRC_IDLE) state, the primary frequency is the frequency at which the serving device resides.

If the frequency is a secondary frequency, the corresponding SCell is selected as the synchronization reference source.

If the terminal device is within the frequency coverage range, a downlink frequency paired with the frequency is selected as the synchronization reference source.

If the terminal equipment is out of the frequency coverage range, select PCell or resident serving cell as the synchronization reference source.

Exemplarily, the terminal device selects a cell on the frequency as a synchronization reference source, that is, the downlink subframe boundary of the cell is used as the SL subframe boundary during V2X transmission.

If the terminal device chooses V2X communication on a frequency, and the corresponding "typeTxSync" in SIB21 is configured as GNSS or not configured, and the GNSS signal is reliable, the terminal device uses GNSS as the synchronization reference on this frequency. source. As shown in Figure 1, both terminal equipment V1 and terminal equipment V2 can obtain GNSS signals from SNSS103. The GNSS signals include coordinated universal time (UTC) time and UTC reference time (standard calendar time January 1, 1990 00:00:00 on the day), the terminal device may calculate a direct frame number (DFN) and a subframe number at the current time according to the GNSS signal, and use the inferred subframe boundary as the SL subframe boundary during V2X transmission.

In LTE V2X communication, the SL subframe boundary derived by the terminal device using the radio access network device (such as eNB or gNB) as the synchronization reference source and the SL subframe boundary derived by using GNSS as the synchronization reference source may be misaligned . At this time, the V2X terminal device uses the GNSS as a synchronous reference source for SL transmission on a carrier, and the radio access network device also schedules the uplink (UL) transmission of the terminal device on this carrier. SL transmission and UL will occur. Interference and collision between transmissions. As shown in FIG. 1, the radio access network device 101 broadcasts in SIB21 to notify the V2X terminal device V1 that V2X communication can be performed on the carrier 1, and GNSS 103 is the preferred synchronization reference source. At the same time, the radio access network device 101 also The terminal device 102 is scheduled on the carrier 1 for uplink transmission. FIG. 2 shows examples of SL subframe boundaries deduced using a radio access network device as a synchronization reference source and SL subframe boundaries deduced using GNSS as a synchronization reference source. As shown in FIG. 2, the subframe boundary derived by the terminal device V1 using the GNSS as the synchronization reference source and the subframe boundary derived by using the radio access network device as the synchronization reference source are not aligned. In this way, the radio access network

equipment reserves subframes

1,2 for V2X terminal equipment V1 for V2X transmission, but the resources actually used by V2X terminal equipment V1 are not the same as the reserved resources. For example, V2X terminal equipment V1 performs subframe 1 During SL transmission, interference will occur on uplink transmission on subframe 0 that is not reserved by the radio access network equipment.

To this end, a DFN offset value (offsetDFN) is introduced, which is used to offset the subframe boundary deduced to the right using GNSS as the synchronization reference source. As shown in Figure 3 below, by offsetting the subframe boundary derived using GNSS as a synchronous reference source, the subframe boundary derived using GNSS as a synchronous reference source and the radio access network device as a synchronous reference source can be derived. Out the sub-frame boundaries are aligned. Exemplarily, when the terminal device selects GNSS as the synchronization reference source, the DFN and the subframe number are calculated according to the following formulas (1) and (2):

DFN = Floor (0.1 * (Tcurrent--Tref-offsetDFN)) mod 1024 (1)

subframeNumber = Floor (Tcurrent--Tref-offsetDFN) mod 10 (2)

Among them, subframeNumber is the subframe number, Tcurrent is the current UTC time obtained by the UE from GNSS (the value is expressed in milliseconds), Tref is the UTC reference time, offsetDFN is the offset value to the right of the derived subframe boundary, and the offsetDFN The value is expressed in milliseconds, the value range is 0ms to 1ms, and the value is an integer multiple of 0.001ms. The radio access network device can configure the parameter value appropriately when configuring the synchronization reference source of the frequency, so that the terminal equipment can use the GNSS as the synchronization reference source to offset the subframe boundary, which can avoid the SL transmission and UL transmission. Interference issues. If the radio access network device does not configure an offsetDFN for a certain frequency, the terminal device considers the offsetDFN to be 0.

In NR V2X communication, there may be an LTE Uu port to control NR SL transmission, or an NR Uu port to control LTE SL transmission. As shown in FIG. 4, an eNB scheduling NR and SL on carrier 1 in LTE is taken as an example. At this time, there is an NR gNB near the LTE eNB, and the NR gNB uses carrier 1 to schedule the uplink transmission of the UE. At this time, according to the technical solution described above, the LTE eNB can determine the offsetDFN value to ensure that the SL transmission of the V2X terminal device and its own UL transmission do not interfere. At this time, how does the LTE eNB determine the appropriate offsetDFN value so that the subframe boundary derived when the V2X terminal device uses GNSS as the synchronization reference source is aligned with the subframe boundary of the NR and gNB, thereby avoiding the NR and SL transmission and neighbor control controlled by the LTEUu port? The mutual interference of NR and UL transmissions of stations is an urgent problem.

Similarly, there is an LTE eNB near the NR and NB, and the LTE eNB uses the carrier 1 to schedule the uplink transmission of the UE. At this time, how does the NR gNB determine the appropriate offsetDFN value so that the subframe boundary derived when the V2X terminal device uses GNSS as the synchronization reference source is aligned with the subframe boundary of the LTE eNB, thereby avoiding the LTE SL transmission and neighbor control controlled by the NRUu port? The mutual interference of LTE UL transmissions of stations is an urgent problem to be solved.

FIG. 5 shows a schematic flowchart of a synchronization method according to an embodiment of the present application. In the synchronization method provided in the embodiment of the present application, the first radio access network device may receive the first DFN offset value of the first carrier from the second radio access network device, and send the first DFN offset value to the first carrier according to the first DFN offset value. A terminal device sends a second DFN offset value corresponding to the first carrier, so that the first terminal device determines a DFN and a subframe number according to the second DFN offset value, and further deduces a sub-frame derived from the GNSS as a synchronization reference source. The frame boundary is shifted so that the subframe boundary derived using GNSS as the synchronization reference source and the subframe boundary derived using the radio access network device as the synchronization reference source are aligned.

It should be understood that, in FIG. 5, a first terminal device, a first radio access network device, and a second radio access network device are taken as an execution subject of a method for performing synchronization as an example to describe the method for synchronization. By way of example and not limitation, the execution subject of the synchronization method may also be a chip of a first terminal device, a chip of a first radio access network device, and a chip of a second radio access network device.

It should also be understood that FIG. 5 shows the steps or operations of the synchronized method, but these steps or operations are merely examples, and the embodiments of the present application may also perform other operations or a modification of each operation in FIG. 5. In addition, each step in FIG. 5 may be performed in a different order than that presented in FIG. 5, and it is possible that not all operations in FIG. 5 are to be performed.

501. A first radio access network device configures a first terminal device with a first carrier for side-link SL transmission.

In the embodiment of the present application, the first radio access network device operates in a first radio communication system, the second radio access network device and the first carrier operate in a second radio communication system, and the side line The link is a directly connected wireless communication link between the first terminal device and the second terminal device. It should be noted that, in the embodiments of the present application, the first communication system and the second communication system may be the same or different.

As an example, in a scenario where an LTE eNB schedules a V2X terminal device for NR and SL transmission, the first communication system is an LTE communication system, the second communication system is an NR communication system, the first radio access network device is an LTE eNB, and the second radio The access network device is NR gNB. At this time, the LTE eNB configures the V2X terminal device as the first carrier for side-link SL transmission.

In the scenario where NR gNB dispatches V2X terminal equipment for LTE SL transmission, the first communication system is the NR communication system, the second communication system is the LTE communication system, the first radio access network device is the NR gNB, and the second radio access network The device is an LTE eNB. At this time, the NR gNB configures the V2X terminal device as the first carrier for side-link SL transmission.

In the embodiment of the present application, the first carrier operates in the second wireless communication system, which can be understood as that the second radio access network device running in the second communication system can schedule the first carrier for uplink and downlink transmission in its cell. Here, the uplink and downlink transmissions include at least one of uplink data transmission, uplink signaling transmission, downlink data transmission, and further downlink signaling transmission.

In the embodiment of the present application, the first carrier may be referred to as a carrier. When the first carrier is used for side-link SL transmission, it may be recorded as NR and carrier. When the first carrier is used for uplink UL transmission, it may be recorded as NR and UL carrier.

The synchronization method in the embodiment of the present application is applicable to a scenario in which an LTE eNB schedules a V2X terminal device for NR and SL transmission, and may also be applicable to a scenario in which the NR gNB schedules a V2X terminal device for LTE and SL transmission. Exemplarily, the following describes a scenario where LTE eNB schedules V2X terminal equipment for NR and SL transmission as an example to describe how to avoid mutual interference between NR SL transmission and NR UL transmission, and how NR gNB schedules V2X terminal equipment for LTE SL transmission. To avoid mutual interference between LTE SL transmission and LTE UL transmission, reference may be made to the description of a scenario in which an LTE eNB schedules a V2X terminal device for NR SL transmission. For the sake of brevity, the embodiments of this application will not repeat them.

Exemplarily, for an LTE communication system, there may be multiple cells under each eNB, and the technical solution in the embodiment of the present application may be applicable to the eNB and terminal equipment in each cell. For a 5G or NR system, there may be one or more TRPs under one gNB, and the technical solution in the embodiment of the present application may be applicable to each gNB or TRP. For the CU-DU separation scenario, there may be multiple DUs under one CU, and the technical solution in the embodiment of the present application may be applied to each CU or DU.

502. The first radio access network device receives a first direct frame number DFN offset (offsetDFN) value corresponding to the first carrier from the second radio access network device.

Exemplarily, if the NR gNB will perform UL scheduling on the carrier x, the NR gNB sets the offsetDFN on the carrier x to the gap between the SFN subframe and the DFN subframe. If the NR gNB does not perform the scheduling on the carrier x, For UL scheduling, the NR gNB sets the offsetDFN to 0.

In another implementation manner, the NR gNB will inform the LTE eNB of the information of the UL scheduled carriers and the corresponding offsetDFN value of each carrier through the Xn interface. If the LTE eNB is used in the carrier provided by the NR and the NB, the offsetDFN of the NR and the carrier is set to the corresponding offsetDFN value provided by the NR. If the LTE eNB is used in the NR and SL carrier, the carrier is not provided by the NR and gNB. , The offsetDFN value of NR, SL, and carrier is set to 0.

Optionally, when the LTE eNB is adjacent to multiple NR gNBs, and these NR gNBs use the corresponding NR SL carrier for UL scheduling, the network management function or the LTE eNB itself may decide to use the offsetDFN value set by one of the NR gNBs as The offsetDFN value on the NR SL carrier.

Optionally, in the embodiment of the present application, when both the LTE eNB and the NR gNB are connected to a 5G core network (5G core, 5GC), the LTE eNB may notify the NR gNB of the first carrier information or the offsetDFN value through the Xn interface. When both the LTE eNB and the NR gNB are connected to an evolved packet core network (EPC), the LTE eNB can notify the NR gNB of the first carrier information or the offsetDFN value through the X2 interface, which is not limited in this embodiment of the present application. Alternatively, the offset DFN information of the first carrier may be carried in a related message of the existing Xn interface or X2 interface establishment process, or a related message of the base station configuration update, or other Xn interface message, which is not specifically described in this embodiment of the present application. limited. Among them, before the signaling interaction between the LTE eNB and the NR gNB through the Xn interface or the X2 interface, the connection of the Xn interface or the X2 interface needs to be established. This process is called the Xn interface or X2 interface establishment process. At this time, the Xn interface or X2 The relevant messages of the interface establishment process include Xn or X2 establishment request messages and Xn or X2 establishment response messages.

Exemplarily, the LTE eNB and the NR gNB can exchange resource pool information on the NR SL carrier in addition to the NR SL carrier information and the corresponding offsetDFN information on the Xn interface or the X2 interface. The so-called resource pool information on NR and SL carrier refers to the frequency domain resources and / or time domain resources that will be used for NR SL transmission on this carrier. These resource pool information can be notified to the NR and NB through the Xn interface or X2 interface after being determined by the LTE eNB, and can also be notified to the LTE eNB through the Xn interface or X2 interface after being determined by the LTE eNB, and can also be determined through negotiation between the NR and the LTE eNB.

In the embodiment of the present application, when both the LTE eNB and the NR gNB are connected to the 5GC, the LTE eNB can notify the NR through the Xn interface of the resource pool information on the NR SL carrier and the NB. When both the LTE eNB and the NR gNB are connected to the EPC, The LTE eNB can notify the NR and the NB of the resource pool on the carrier through the X2 interface. When both the LTE eNB and the NR and the NB are connected to the 5GC, the NR and the NB can notify the LTE eNB of the NR and the resource pool on the carrier through the Xn interface. Information, when both the LTE eNB and the NR gNB are connected to the EPC, the NR gNB can notify the LTE eNB of the resource pool information on the NR SL carrier through the X2 interface, which is not limited in this embodiment of the present application. Alternatively, information such as the resource pool may also be carried in related messages of the existing Xn interface or X2 interface establishment process, or related messages of the base station configuration update, or other Xn interface messages, which are not specifically limited in this embodiment of the present application. .

Optionally, in the embodiment of the present application, at least one of resource pool information, SL carrier information, or offsetDFN value may be exchanged between the NR and NB and the LTE eNB, that is, only resources may be exchanged between the NR and the NB and the LTE eNB. The pool information may also only exchange SL carrier information, or only the offsetDFN value, or two of the three pieces of information, or all three pieces of information, which are not limited in the embodiment of the present application.

503. The first radio access network device sends a second offsetDFN value corresponding to the first carrier to the first terminal device.

In the embodiment of the present application, the second offsetDFN value may be the same as or different from the first offsetDFN value.

As an example, the LTE eNB can obtain the offsetDFN value on the NR SLcarrier from the NR and gNB through the Xn interface or the X2 interface, that is, the above step 502, and then sends the offsetDFN value to the first terminal device through the SIB / RRC dedicated signaling, that is, Step 503: At this time, the second offsetDFN value is the same as the first offsetDFN value.

As another example, the offsetDFN value (that is, the second offsetDFN value) of the NR, SL, and carrier in the SIB / RRC signaling sent by the first radio access network device to the first terminal device may be configured as 0, or configured as a pre-configuration The offsetDFN value. Among them, the pre-configuration cell indicates the V2X configuration adopted by the terminal device during out-of-coverage. At this time, the second offsetDFN value may be different from the first offsetDFN value.

Optionally, 504, the first terminal device reports the measurement result of the first carrier in the neighboring cell to the first radio access network device. The cell measurement result may include cell information, and may also include a measured signal strength (for example, the RSRP or RSRQ or RSSI value of the cell). Here, the neighboring cell is a cell provided by the second radio access network device. Optionally, step 504 may be performed before step 502, which is not specifically limited in this embodiment of the present application.

For example, after the V2X terminal device enters the RRC_CONNECTED state, it can report the SL communication capability it supports to the LTE eNB. If the terminal device supports both NR SL and LTE SL transmission, the LTE eNB can perform measurement configuration and measurement reporting configuration for the terminal device through RRC dedicated signaling. In the embodiment of the present application, the measurement configuration may indicate which NR and SL carriers the terminal device performs measurement on, and the measurement report configuration may instruct the terminal device to report the measurement result to the LTE eNB when the measurement result meets a specified condition, or instruct the terminal device to periodically Report the measurement results to the LTE eNB. As an example, the specified condition is, for example, that the RSRP or RSQP or RSSI of the neighboring cell is greater than a certain threshold value, or is greater than a certain threshold value for a certain duration, or is greater than a certain threshold value for N consecutive samples, where N Is an integer greater than 0.

Then, the terminal device can measure the carrier in the neighboring cell according to the measurement configuration, and report the measurement result to the LTE eNB according to the measurement reporting configuration. After the first radio access network device receives the measurement result reported by the first terminal device, it can determine whether the NR SL transmission and the NR UL transmission of the second radio access network device interfere with each other according to the measurement result.

Exemplarily, the terminal device reports the measurement results of all carriers that meet the specified conditions according to the measurement configuration and the measurement reporting configuration. Then, the LTE eNB can identify the terminal device and the neighboring NR gNB in the same frequency cell according to the measurement result. After that, the LTE eNB notifies the corresponding carrier information or cell information of the NR gNB through the Xn interface or the X2 interface. Optionally, the LTE eNB notifies the NR and gNB of the corresponding carrier information or cell information through the Xn interface or the X2 interface. For details, refer to the description in 502. For brevity, details are not described herein again.

Optionally, in the embodiment of the present application, the first radio access network device may further configure, to the first terminal device, synchronization reference source information and / or resource configuration information of the first carrier (ie, NR, SL, and carrier). Optionally, the LTE eNB may configure the synchronization reference source information and / or the resource configuration information of the NR, SL, and RX carrier to the first terminal device through the SIB / RRC dedicated signaling.

In a possible implementation manner, an optional indication field radio access technology (RAT) type may be used in the SIB / RRC dedicated signaling to indicate that the SIB / RRC dedicated signaling is configured. Is the SL carrier used for NR SL transmission or LTE SL transmission? For example, when RAT-type = LTE is configured, it means that the SL carrier is used for LTE SL transmission; when RAT-type = NR is configured, it means that the SL carrier is used for NR SL transmission.

It should be noted that, in the embodiment of the present application, only the indication field for indicating the access type of the SL is RAT-type is used as an example for description. The indication information may also be called other names, which is not described in this embodiment of the present application. Specific limitations.

In another possible implementation manner, when the indication field RAT-type is not configured, it indicates that the protocol predefines the SL for NR SL transmission, or when the indication field RAT-type is not configured, it indicates that the protocol predefines the SL The carrier is used for LTE SL transmission.

Optionally, after the terminal device accesses the network and enters the RRC_CONNECTED state, it can report the SL communication capabilities it supports to the LTE eNB, such as only supporting LTE SL transmission, or only NR SL transmission, or both LTE SL transmission and NR SL transmission. At this time, the LTE eNB can configure the SL carrier that the terminal device can use for V2X communication and the access technology used on each SL carrier according to the SL communication capability reported by the terminal device. If the terminal equipment only supports SL transmission of one access technology, the RAT-type field corresponding to the SL carrier in the RRC dedicated signaling may not be configured. In this case, it means that the SL carrier configured by the LTE eNB can be used for the terminal equipment. SL transmission of supported access technologies. Specific examples are as follows:

Example 1

The LTE eNB configures SL carrier1 and SL carrier2 for V2X communication through the SIB information, and configures RAT-type corresponding to SL carrier1 = LTE, and RAT-type = NR corresponding to SL carrier2. The above configuration indicates that the LTE eNB instructs the V2X terminal device to use SL carrier1 for communication on the LTE SL interface, and SL carrier2 for communication on the NR SL interface.

Example 2

The undefined RAT-type of the protocol indicates that the default RAT-type = LTE. The LTE eNB configures SL carrier1 and SL carrier2 through the SIB information. The RAT-type corresponding to SL carrier1 is not configured, and the RAT-type corresponding to SL carrier2 = NR. The above configuration indicates that the base station instructs the terminal device to use SL1 carrier for communication on the LTE SL interface, and SL2 carrier 2 for communication on the NR SL interface.

Example 3

The connected terminal equipment reports support only NR and SL transmission. LTE eNB can configure SL carrier1 and SLcarrier2 for the terminal equipment through RRC dedicated signaling, and neither of these SL carriers is configured with RAT-type. The above configuration indicates that the LTE eNB indicates that the terminal device can communicate with SL1 and SL2 on the NR SL interface.

It should be noted that, in the embodiment of the present application, only the offsetDFN value, synchronization reference source information, or resource configuration information of the NR, SL, and carrier are configured for the first terminal device through SIB / RRC signaling. The first radio access network device in China may also configure an offsetDFN value, synchronization reference source information, or resource configuration information to the first terminal device through other methods such as high-level signaling or physical layer signaling, which is not limited in this embodiment of the present application.

505. The first terminal device determines the DFN and the subframe number according to the second offsetDFN value.

Exemplarily, when the first terminal device uses GNSS as the synchronization reference source on the carrier x, the DFN and the subframe number are calculated according to the offsetDFN value of the carrier x currently configured. For the calculation of the DFN and the subframe boundary, reference may be made to the description in FIG. 2 and FIG. 3 above. For brevity, details are not described herein again.

It should be noted that, in the embodiment of the present application, the foregoing steps are merely examples. In the embodiment of the present application, the first terminal device, the first radio access network device, and the second radio access network device are not required to strictly follow the above steps. The execution method sequentially executes the synchronization method in the embodiment of the present application.

For example, in the embodiment of the present application, the first radio access network device may send the second offsetDFN value of the first carrier to the first terminal device multiple times (at least twice), where each second offsetDFN value configured at a different time point It can be the same or different.

Exemplarily, the first radio access network device may first execute 503 to configure the second offset value to 0 or the offsetDFN value in the pre-configuration. In a possible implementation manner, if the first terminal device performs 504, that is, reports the measurement result of the first carrier in the neighboring cell to the first radio access network device, the first radio access network device may perform 502 and 503. That is, the first offsetDFN value is received from the second radio access network device, and the second offsetDFN value is configured as the first offsetDFN value, and is sent to the first terminal device. In another possible implementation manner, if the first terminal device does not perform 504, that is, the measurement result of the first carrier in the neighboring cell is not reported to the first radio access network device, the first radio access network device may 502 and 503 are not needed, that is, the second offsetDFN value is not reconfigured.

In another possible implementation manner, after the first access network device executes 503 and configures the second offset value to 0 or the offsetDFN value in the pre-configuration, the first terminal device may execute 505, That is, the DFN and the subframe number are determined according to the second offsetDFN value configured by the first access network device. After that, if the first terminal device performs execution 504, that is, reports the measurement result of the first carrier in the neighboring cell to the first radio access network device, the first radio access network device may perform 502 and 503, that is, from the second radio The access network device receives the first offsetDFN value, configures the second offsetDFN value as the first offsetDFN value, and sends it to the first terminal device, so that the first terminal device can perform 505 again, that is, determine the DFN according to the reconfigured offsetDFN value. And subframe number.

Therefore, in the embodiment of the present application, the first radio access network device may receive the first DFN offset value of the first carrier from the second radio access network device, and send the first DFN offset value to the first terminal according to the first DFN offset value. The device sends a second DFN offset value corresponding to the first carrier, so that the first terminal device determines the DFN and the subframe number according to the second DFN offset value, and then the first terminal device deduces the GNSS as a synchronization reference source. The subframe boundary of the mobile station is offset, so that the subframe boundary derived from the GNSS as the synchronization reference source is aligned with the subframe boundary derived from the radio access network device as the synchronization reference source, so as to control the NR and SL transmission on the LTEUu port. In the scenario, mutual interference between NR SL transmission and neighboring station NR UL transmission can be avoided, or mutual interference between LTE SL transmission and neighboring station LTE UL transmission can be avoided in the NR Uu port control LTE SL transmission scenario.

In addition, in this embodiment, the offset DFN value of the NR, SL, and carrier x is obtained through the interaction between the first radio access network device and the second radio access network device. This process is transparent to the terminal device, so this solution is applicable to both connected and idle terminal devices. It is applicable to allow the terminal equipment to reuse the existing LTE technology as much as possible to avoid increasing the complexity of the implementation of the terminal equipment. In addition, this embodiment does not require the terminal device to be equipped with an NR Uu module, and the proposed technical problem can be solved only by software upgrade, which reduces the hardware cost of the terminal device.

In the embodiment of the present application, the LTE eNB can configure a scheduling-free resource for the terminal device on the LTE carrier, or the NR gNB can configure the scheduling-free resource for the terminal device on the NR carrier. Schedule-free resources can also be called grant free resources, or configured grant 1 type resources.

The scheduling-free resources are configured by RRC signaling. The relevant parameters include the time offset of the first scheduling-free resource relative to the SFN = 0 position, and the time-frequency domain resource position occupied by the first scheduling-free resource. Cycle of resources, etc. The time offset of the first scheduling-free resource with respect to the SFN = 0 position is the offset value of the slot where the first symbol of the resource block is located with respect to the SFN = 0 position.

And because the position of SFN = 0 and the position of DFN = 0 are not aligned, when the terminal device uses GNSS as the synchronization reference source, the terminal device may not maintain the current time offset from SFN = 0, and it is difficult for the terminal device at this time. Determine the specific location of the scheduling-free resource, and if the terminal device estimates the location of the scheduling-free resource with DFN = 0, it will cause the resources used by the terminal device to be inconsistent with the scheduling-free resources actually reserved by the network, and may cause data transmission to other terminal devices Produce interference. Therefore, when the terminal device is configured with SL scheduling-free resources and the radio access network device is used as the synchronization reference source, the corresponding scheduling-free resource configured by the radio access network device can be used. If the terminal device uses GNSS as the synchronization reference source When the corresponding scheduling-free resource is suspended (that is, the use of the scheduling-free resource is stopped), if the synchronization reference source of the terminal device is restored from the GNSS to the radio access network device, the scheduling-free resource is resumed. For a SL carrier, if the terminal device is out-of-coverage, the terminal device can use the pre-configured available scheduling-free resources. At this time, the time domain position of the first resource block of the pre-configured scheduling-free resource is configured as Relative to time offset of DFN = 0.

FIG. 6 is a schematic flowchart of another synchronization method according to an embodiment of the present application. In the synchronization method provided in the embodiment of the present application, if the first terminal device can directly obtain the third offsetDFN value sent by the second radio access network device, the DFN and the subframe number may be determined according to the third offsetDFN value, and The subframe boundary derived using GNSS as the synchronization reference source is shifted, so that the subframe boundary derived using GNSS as the synchronization reference source is aligned with the subframe boundary derived using the radio access network device as the synchronization reference source.

It should be understood that FIG. 6 shows the steps or operations of the synchronization method, but these steps or operations are merely examples, and the embodiment of the present application may also perform other operations or a modification of each operation in FIG. 6. In addition, each step in FIG. 6 may be performed in a different order than that presented in FIG. 6, and it is possible that not all operations in FIG. 6 are to be performed.

In the embodiment of the present application, the first radio access network device, the second radio access network device, and the first terminal device may refer to the description in FIG. 5. To avoid repetition, details are not described herein again.

601. A first radio access network device configures a first terminal device with a first carrier for side-link SL transmission.

For example, 601 may refer to the description of 501 in FIG. 5. To avoid repetition, details are not described herein again.

Optionally, 602, the first radio access network device sends a second offsetDFN value corresponding to the first carrier to the first terminal device. In the embodiment of the present application, the second radio access network device does not need to send the direct frame number DFN offset (offsetDFN) value corresponding to the first carrier to the first radio access network device.

Optionally, the second offsetDFN value here can be configured as 0, or the offsetDFN value in the pre-configuration, or other.

Correspondingly, the first terminal device receives the second offsetDFN value. Optionally, after receiving the second offsetDFN field sent by the second radio access network device, the first terminal device may ignore the value of the field, that is, the default offsetDFN corresponding to the first carrier is 0 or the value in the pre-configuration. .

For example, for the manner in which the first radio access network device configures the SL transmission in 602, refer to the description of 503 in FIG. 5. To avoid repetition, details are not described herein again.

603. The second radio access network device sends a third offsetDFN value corresponding to the first carrier to the first terminal device.

Exemplarily, if the terminal device measures a strong NR cell signal on the NR SL carrier, for example, if the signal strength of the NR cell (such as RSRP or RSRQ value or RSSI) exceeds a certain threshold or meets certain conditions The terminal device reads the SIB message carrying the V2X configuration information broadcast by the NR base station. Here, satisfying a certain condition may include that the RSRP or RSRQ value exceeds a threshold value within a period of time, and the threshold value and the condition may be broadcasted by the SIB or configured by RRC dedicated signaling. In addition, the terminal device can read the SIB message on the NR cell, and can also read the SIB message on the measured other NR cells, and obtain the offsetDFN value configured in the SIB message for the NR SL carrier.

Optionally, after the terminal device receives the offsetDFN value broadcasted by the NR gNB, it may cover the offsetDFN obtained from the SIB information of the LTE eNB. When the terminal device uses GNSS as the synchronization reference source on the NR SL carrier, the DFN subframe boundary is calculated according to the currently configured offset DFN.

In the embodiment of the present application, after the terminal device finds a strong NR cell signal, it reads the SIB message of the NR base station.

An optional method is that, no matter whether the terminal device finds a strong NR cell signal, it will read the SIB message of the NR gNB, and if the terminal device receives the SIB message broadcast by the NR gNB, and can obtain the The offsetDFN value configured by an NR SL carrier x directly covers the offsetDFN value corresponding to the NR SL carrier x obtained from the SIB information of the LTE eNB.

Another alternative is to read the SIB message of the NR gNB regardless of whether the terminal device finds a strong NR cell signal, and if the terminal device receives the SIB message broadcast by the NR gNB, for the NR SL carrier, Two offsetDFN values will be saved, one obtained from the LTE eNB and one obtained from the NR gNB. Only when the terminal equipment uses GNSS as the synchronization reference source on the NR and SL carrier, and the terminal equipment measures a strong NR cell signal on the NR and SL carrier, will the offsetDFN value obtained from NR and gNB be used, otherwise it will use LTE from LTE. The offsetDFN value obtained by the eNB.

Optionally, in this embodiment, the LTE eNB can control whether the terminal device measures and measures the NR cell signal and whether to read the SIB message. For example, after the LTE eNB performs measurement configuration for the terminal device through RRC signaling, the terminal device measures the NR cell signal and reads the SIB message; if the LTE eNB does not perform measurement configuration on the terminal device, the terminal device does not perform measurement on the NR cell signal. Do not read SIB messages. In addition, if the terminal device fails to read the SIB message carrying the offsetDFN from the NR gNB, the terminal device continues to use the offsetDFN value obtained from the LTE eNB.

For example, for the manner in which the second radio access network device configures the SL transmission in 603, refer to the manner in which the second radio access network device configures the SL transmission. For brevity, details are not described herein again.

604. The first terminal device determines a DFN and a subframe boundary.

Exemplarily, when the first terminal device uses GNSS as the synchronization reference source on the carrier x, the DFN and the subframe number are calculated according to the offsetDFN value of the carrier x currently configured. Optionally, for calculating the DFN and the subframe boundary, reference may be made to the description in FIG. 2 and FIG. 3 above. For brevity, details are not described herein again.

It should be noted that, unless otherwise specified, the terminal device described in the embodiment of the present application is the first terminal device described above.

FIG. 7 shows a schematic flowchart of another synchronization method according to an embodiment of the present application. In the synchronization method provided in the embodiment of the present application, the first wireless access network device may send a second DFN offset value corresponding to the first carrier to the first terminal device, and the first terminal device may also measure the first wireless access SFN subframe boundary interval between the network equipment and the second radio access network equipment, and according to the second DFN offset value and the measured subframe boundary interval, determine the DFN and the subframe number, and then use GNSS as the synchronization reference source The deduced subframe boundary is shifted so that the subframe boundary derived using GNSS as a synchronization reference source is aligned with the subframe boundary derived using a radio access network device as a synchronization reference source.

It should be understood that FIG. 7 shows the steps or operations of the synchronization method, but these steps or operations are merely examples, and the embodiments of the present application may also perform other operations or a modification of each operation in FIG. 7. In addition, each step in FIG. 7 may be performed in a different order than that presented in FIG. 7, and it is possible that not all operations in FIG. 7 are to be performed.

701. A first radio access network device configures a first terminal device with a first carrier for side-link SL transmission.

Exemplarily, 701 may refer to the description of 501 in FIG. 5. To avoid repetition, details are not described herein again. 702. The first radio access network device sends a second offsetDFN value corresponding to the first carrier to the first terminal device. In the embodiment of the present application, the second radio access network device does not need to send the direct frame number DFN offset (offsetDFN) value corresponding to the first carrier to the first radio access network device.

In the embodiment of the present application, the second offsetDFN value may be configured as a gap value at the boundary of the SFN subframe and the measured DFN subframe of the first radio access network device itself.

Optionally, for the manner in which the first radio access network device configures the SL transmission in 702, refer to the description of 503 in FIG. 5. To avoid repetition, details are not described herein again.

703. The terminal device measures a subframe boundary gap of the first network device and the second network device.

Exemplarily, if the terminal device measures a strong NR cell signal on the NR SL carrier, for example, if the signal strength of the NR cell (such as RSRP or RSRQ or RSSI value) exceeds a certain threshold or meets a certain condition The terminal device measures the gap at the subframe boundary of the NR cell and the LTE cell, and the subframe boundary gap may be referred to as an SFN offset (offsetSFN) value, where the LTE cell refers to a PCell of the terminal device or a serving cell that currently resides. The above-mentioned subframe boundary gap refers to a time interval between an NR cell subframe boundary and a next LTE cell subframe boundary in the time domain, and ranges from 0 to 1 ms. Here, the threshold value and conditions can refer to the description of 603 in FIG. 6, and for the sake of brevity, they are not repeated here.

704. The first terminal device determines the DFN and the subframe boundary according to the second compensation DFN value and the measured subframe boundary gap (that is, offsetSFN).

Exemplarily, when the terminal device uses GNSS as the synchronization reference source on the NR SL carrier, the DFN subframe boundary is calculated according to the currently configured second offsetDFN value plus the measured offsetSFN value as an offset, that is, the terminal device Calculate the DFN and DFN subframe numbers at the current moment according to the following formulas (3) and (4):

DFN = Floor (0.1 * (Tcurrent--Tref--offsetDFN-offsetSFN)) mod1024 (3)

subframeNumber = Floor (Tcurrent--Tref-offsetDFN-offsetSFN) mod10 (4)

Exemplarily, if the terminal device does not measure a strong NR cell signal on the NR carrier, the offsetSFN = 0 is used when calculating the current DFN and subframe number.

Alternatively, the first radio access network device may control whether the first terminal device measures an offsetSFN value. For example, after the LTE eNB performs measurement configuration for the terminal device through RRC signaling, the terminal device measures the NR cell signal and offsetSFN; if the LTE eNB does not perform measurement configuration for the terminal device, the terminal device does not measure the NR cell signal and offsetSFN. At this time, offsetSFN = 0.

Therefore, in the embodiment of the present application, the first radio access network device may send a second DFN offset value corresponding to the first carrier to the first terminal device, and the first terminal device may also measure the first radio access network device and The SFN subframe boundary interval of the second radio access network device, and according to the second DFN offset value and the measured subframe boundary interval, determine the DFN and the subframe number, and then derive the GNSS as the synchronization reference source. Subframe boundaries are shifted so that the subframe boundaries derived using GNSS as the synchronization reference source are aligned with the subframe boundaries derived using radio access network equipment as the synchronization reference source, so as to control the NR and SL transmission scenarios on the LTE Uu port. To avoid mutual interference between NR SL transmission and neighboring station NR UL transmission, or to avoid mutual interference between LTE SL transmission and neighboring station LTE UL transmission in the NR Uu port control LTE SL transmission scenario.

In the embodiment of the present application, the LTE eNB side can reuse the existing LTE technology, which has little impact on the network equipment side. For the terminal equipment, if it supports the measurement on the NR carrier, it is easy to measure the gap of the SFN subframe between the LTE eNB and the NR gNB, so for the terminal equipment, it will not increase the implementation complexity.

The above mainly introduces the solutions provided by the embodiments of the present application from the perspective of interaction between different devices. It can be understood that, in order to implement the foregoing functions, the first radio access network device, the second radio access network device, and the first terminal device include a hardware structure and / or a software module corresponding to each function. With reference to the units and algorithm steps of each example described in the embodiments disclosed in this application, the embodiments of this application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is performed by hardware or computer software-driven hardware depends on the specific application of the technical solution and design constraints. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the technical solutions of the embodiments of the present application.

In the embodiment of the present application, the functional units of the first radio access network device, the second radio access network device, and the first terminal device may be divided according to the foregoing method example. For example, each functional unit may be divided corresponding to each function, or Integrate two or more functions into one processing unit. The above-mentioned integrated units can be implemented in the form of hardware or software functional units. It should be noted that the division of the units in the embodiments of the present application is schematic, and is only a logical function division. There may be another division manner in actual implementation.

In the case of using an integrated unit, FIG. 8 shows a possible exemplary block diagram of a communication device involved in the embodiment of the present application. The device 800 may exist in the form of software, hardware, or a combination of software and hardware. . FIG. 8 shows a possible schematic block diagram of a device involved in an embodiment of the present application. The apparatus 800 includes a processing unit 802 and a communication unit 803. The processing unit 802 is configured to control and manage the operation of the device. The communication unit 803 is configured to support communication between the device and other devices. The device may further include a storage unit 801 for storing program code and data of the device.

The apparatus 800 shown in FIG. 8 may be a first radio access network device and a second radio access network device involved in the embodiments of the present application.

When the apparatus 800 shown in FIG. 5 is a first radio access network device, the processing unit 802 can support the apparatus 800 to perform the actions performed by the first radio access network device in the foregoing method examples. For example, the processing unit 802 supports the apparatus 800 performs an action of configuring a first carrier for the first terminal device for SL transmission, such as 501 in FIG. 5, 601 in FIG. 6, 701 in FIG. 7, and / or the techniques described herein. Other processes. The communication unit 803 can support communication between the device 800 and the second radio access network device, the first terminal device, and the like. For example, the communication unit 803 supports the device 800 to perform steps 502, 503, and 504 in FIG. 5, and Step 602, 702 in FIG. 7, and / or other related communication processes.

When the apparatus 800 shown in FIG. 8 is a second radio access network device, the processing unit 802 can support the apparatus 800 to perform the actions performed by the second radio access network device in the foregoing method examples. For example, the processing unit 802 supports the apparatus 800 performs an action of generating a third offsetDFN value, and / or other processes for the techniques described herein. The communication unit 803 can support communication between the device 800 and the first radio access network device, the first terminal device, etc. For example, the communication unit 803 supports the device 800 to perform step 502 in FIG. 5, step 603 in FIG. 6, and / Or other related communication processes.

Exemplarily, the processing unit 802 may be a processor or a controller. For example, the processing unit 802 may be a central processing unit (CPU), a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), and an application specific integrated circuit (Application) -Specific Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute various exemplary logical blocks, units, and circuits described in connection with the present disclosure. The processor may also be a combination that implements computing functions, such as a combination including one or more microprocessors, a combination of a DSP and a microprocessor, and so on. The communication unit 803 may be a communication interface. The communication interfaces are collectively referred to. In a specific implementation, the communication interface may include one or more interfaces. The storage unit 801 may be a memory.

When the processing unit 802 is a processor, the communication unit 803 is a communication interface, and the storage unit 801 is a memory, the device 800 involved in the embodiment of the present application may be the communication device 900 shown in FIG. 9.

Referring to FIG. 9, the apparatus 900 includes: a processor 902 and a communication interface 903. Further, the apparatus 900 may further include a memory 901. Optionally, the device 900 may further include a bus 904. The communication interface 903, the processor 902, and the memory 901 may be connected to each other through a bus 904. The bus 904 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA). Bus, etc. The bus 904 may be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only a thick line is used in FIG. 9, but it does not mean that there is only one bus or one type of bus.

The processor 902 may execute various functions of the device 900 by running or executing a program stored in the memory 901.

Exemplarily, the communication device 900 shown in FIG. 9 may be a first access and mobility management network element and a second access and mobility management network element involved in the embodiments of the present application.

When the device 900 is the first access and mobility management network element, the processor 902 may execute or execute a program stored in the memory 901 to execute the foregoing method examples by the first access and mobility management network element. Actions. When the device 900 is the second access and mobility management network element, the processor 902 may execute or execute a program stored in the memory 901 to execute the foregoing method examples by the second access and mobility management network element. Actions.

In the case of using an integrated unit, FIG. 10 shows a possible exemplary block diagram of another device involved in the embodiment of the present application. The device 1000 may exist in the form of software, hardware, or a combination of software and hardware. . FIG. 10 shows a possible schematic block diagram of a device involved in an embodiment of the present application. The device 1000 includes a processing unit 1002 and a communication unit 1003. The processing unit 1002 is configured to control and manage the operation of the device. The communication unit 1003 is configured to support communication between the device and other devices. The device may further include a storage unit 1001 for storing program code and data of the device.

The communication device 1000 shown in FIG. 10 may be a first terminal device or a chip applied to the first terminal device. The processing unit 1002 can support the device 1000 to perform the actions performed by the terminal device in the foregoing method examples. For example, the processing unit 1002 supports the device 1002 to perform the actions of determining the DFN and the subframe number, and / or other processes used in the technology described herein. . The communication unit 1003 can support communication between the device 1000 and the first radio access network device and the second radio access network device. For example, the communication unit 1003 supports the device 1000 to perform steps 503 and 504 in FIG. 5, and in FIG. 6. Steps 602 and 603, step 702 in FIG. 7, and / or other related communication processes.

Exemplarily, the processing unit 1002 may be a processor or a controller, for example, it may be a CPU, a general-purpose processor, a DSP, an ASIC, an FPGA, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute various exemplary logical blocks, units, and circuits described in connection with the present disclosure. The processor may also be a combination that implements computing functions, such as a combination including one or more microprocessors, a combination of a DSP and a microprocessor, and so on. The communication unit 1003 may be a communication interface. The communication interfaces are collectively referred to. In a specific implementation, the communication interface may include one or more interfaces. The storage unit 1001 may be a memory.

When the processing unit 1002 is a processor, the communication unit 1003 is a transceiver, and the storage unit 1001 is a memory, the apparatus 1000 involved in the embodiment of the present application may be a terminal device shown in FIG. 11.

FIG. 11 shows a simplified schematic diagram of a possible design structure of a first terminal device involved in an embodiment of the present application. The first terminal device 1100 includes a transmitter 1101, a receiver 1102, and a processor 1103. The processor 1103 may also be a controller, which is shown as "controller / processor 1103" in FIG. 11. Optionally, the first terminal device 1100 may further include a modem processor 1105. The modem processor 1105 may include an encoder 1106, a modulator 1107, a decoder 1108, and a demodulator 1109.

In one example, the transmitter 1101 conditions (e.g., analog conversion, filtering, amplification, upconversion, etc.) the output samples and generates an uplink signal, which is transmitted to the base station described in the above embodiment via an antenna . On the downlink, the antenna receives the downlink signal transmitted by the base station in the above embodiment. The receiver 1102 conditions (e.g., filters, amplifies, downconverts, and digitizes, etc.) a signal received from an antenna and provides input samples. In the modem processor 805, the encoder 806 receives service data and signaling messages to be transmitted on the uplink, and processes (e.g., formats, encodes, and interleaves) the service data and signaling messages. The modulator 1107 further processes (e.g., symbol maps and modulates) the encoded service data and signaling messages and provides output samples. A demodulator 1109 processes (e.g., demodulates) the input samples and provides symbol estimates. The decoder 1108 processes (eg, deinterleaves and decodes) the symbol estimates and provides decoded data and signaling messages sent to the first terminal device 1100. The encoder 1106, the modulator 1107, the demodulator 1109, and the decoder 1108 may be implemented by a synthetic modem processor 1105. These units process according to the radio access technology (such as LTE, 5G, and other evolved system access technologies) adopted by the radio access network. It should be noted that when the first terminal device 1100 does not include the modem processor 1105, the above functions of the modem processor 1105 may also be performed by the processor 1103.

The processor 1103 controls and manages the actions of the first terminal device 100, and is configured to execute the processing procedure performed by the first terminal device 1100 in the foregoing embodiment of the present application. For example, the processor 1103 is further configured to execute a processing process involving the first terminal device in the methods shown in FIG. 5, FIG. 6, and FIG. 7 and / or other processes of the technical solution described in this application.

Further, the first terminal device 1100 may further include a memory 1104. The memory 1104 is configured to store program codes and data for the first terminal device 1100.

The steps of the method or algorithm described in connection with the disclosure of the embodiments of the present application may be implemented in a hardware manner, or may be implemented in a manner that a processor executes software instructions. Software instructions can be composed of corresponding software modules. Software modules can be stored in Random Access Memory (RAM), flash memory, Read Only Memory (ROM), erasable programmable read-only memory (ROM Erasable (Programmable ROM, EPROM), electrically erasable programmable read-only memory (EPROM), registers, hard disks, removable hard disks, read-only optical disks (CD-ROMs), or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be an integral part of the processor. The processor and the storage medium may reside in an ASIC. In addition, the ASIC may be located in a control plane entity of the centralized unit, a user plane entity of the centralized unit, a terminal device, or a unified data storage network element. Of course, the processor and the storage medium may also exist as discrete components in a control plane entity of the centralized unit, a user plane entity of the centralized unit, a terminal device, or a unified data storage network element.

An embodiment of the present application further provides a computer-readable storage medium including a computer program, and when the computer program is run on a computer, the computer is caused to execute the method provided by the foregoing method embodiment.

An embodiment of the present application further provides a computer program product containing instructions, and when the computer program product runs on a computer, the computer is caused to execute the method provided by the foregoing method embodiment.

An embodiment of the present application further provides a chip applicable to a communication device. The chip includes at least one processor, and when the at least one processor executes an instruction, the chip or the communication device executes the foregoing method embodiment. In the method, the chip may further include a memory, and the memory may be used for storing related instructions.

It should be understood that the processor mentioned in the embodiments of the present application may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), and application-specific integrated circuits (DSPs). Application Specific Integrated Circuit (ASIC), off-the-shelf Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

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

It should also be understood that the first, second, and various numerical numbers referred to herein are only for the convenience of description and are not intended to limit the scope of the application.

Those of ordinary skill in the art may realize that the units and algorithm steps of each example described in connection with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments, and are not repeated here.

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

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

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

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

The above is only a specific implementation of this application, but the scope of protection of this application is not limited to this. Any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in this application. It should be covered by the protection scope of this application. Therefore, the protection scope of this application shall be subject to the protection scope of the claims.

Claims

A synchronization method, comprising:

The first radio access network device configures a first terminal device with a first carrier for side-link transmission;

Receiving, by the first radio access network device, a first direct frame number DFN offset value corresponding to the first carrier from a second radio access network device;

Sending, by the first radio access network device, a second DFN offset value corresponding to the first carrier to the first terminal device;

The first radio access network device operates in a first radio communication system, the second radio access network device and the first carrier operate in a second radio communication system, and the side link is The direct wireless communication link between the first terminal device and the second terminal device is described.
The method according to claim 1, further comprising:

The first radio access network device sends first information to the second radio access network device, and the first information message is used to request the first DFN offset value corresponding to the first carrier.
The method according to claim 1 or 2, further comprising:

Receiving, by the first radio access network device, a measurement result of the first carrier in a neighboring cell reported by the first terminal device, where the neighboring cell is a cell provided by the second radio access network device.
The method according to any one of claims 1-3, wherein the first DFN offset value and the second DFN offset value are the same.
A synchronization method, comprising:

The second radio access network device sends a first direct frame number DFN offset value corresponding to the first carrier to the first radio access network device;

Wherein, the first carrier is a carrier configured by the first radio access network device for the first terminal device for side-link transmission, and the first radio access network device operates in the first radio communication standard. The second wireless access network device and the first carrier operate in a second wireless communication standard, and the side link is a direct-connected wireless communication link between the first terminal device and the second terminal device road.
The method according to claim 5, further comprising:

The second radio access network device sends first information to the first radio access network device, where the first information is used to request the first DFN value corresponding to the first carrier.
A synchronization method, comprising:

Receiving, by a first terminal device, a second direct frame number DFN offset value corresponding to a first carrier sent by a first radio access network device, wherein the first carrier is the first radio access network device and the The carrier configured for side-link transmission by the first terminal device, the second DFN offset value is corresponding to the first DFN offset value sent by the second radio access network device to the first radio access network device. Determined by the first DFN of a carrier;

Determining, by the first terminal device, a DFN and a subframe number according to the second DFN offset value;

The first radio access network device operates in a first radio communication system, the second radio access network device and the first carrier operate in a second radio communication system, and the side link is The direct wireless communication link between the first terminal device and the second terminal device is described.
The method according to claim 7, further comprising:

The first terminal device reports a measurement result of the first carrier in a neighboring cell to the first radio access network device, where the neighboring cell is a cell provided by the second radio access network device.
The method according to claim 7 or 8, wherein the first DFN offset value is the same as the second DFN offset value.
A synchronization method, comprising:

Receiving, by a first terminal device, a third direct frame number DFN offset value corresponding to a first carrier and sent by a second radio access network device;

Determining, by the first terminal device, a DFN and a subframe number according to the third DFN offset value;

The first carrier is a carrier configured by the first radio access network device for the first terminal device and used for side-link transmission, and the side-link is the first terminal device and a second carrier. A direct wireless communication link between terminal devices, the first wireless access network device operates in a first wireless communication system, and the second wireless access network device and the first carrier are in a second wireless communication system. run.
The method according to claim 10, further comprising:

Determining, by the first terminal device, that a measurement result of the first carrier in a neighboring cell exceeds a first threshold, and the neighboring cell is a cell provided by the second radio access network device;

Determining, by the first terminal device, a DFN and a subframe number according to the third DFN offset value.
The method according to claim 10, further comprising:

Receiving, by the first terminal device, a second DFN offset value corresponding to the first carrier and sent by the first radio access network device;

When the first terminal device determines that the measurement result of the first carrier in the neighboring cell is less than or equal to a first threshold, the first terminal device determines a DFN and a subframe number according to the second DFN offset value.
A synchronization method, comprising:

The second radio access network device sends a third direct frame number DFN offset value corresponding to the first carrier to the first terminal device;

The first carrier is a carrier configured by the first radio access network device for the first terminal device and used for side-link transmission, and the side-link is the first terminal device and a second carrier. A direct wireless communication link between terminal devices, the first wireless access network device operates in a first wireless communication system, and the second wireless access network device and the first carrier are in a second wireless communication system. run.
A communication device, comprising:

A processing unit, configured to configure a first carrier for the first terminal device for side-link transmission;

A receiving unit, configured to receive a first direct frame number DFN offset value corresponding to the first carrier from a second radio access network device;

A sending unit, configured to send a second DFN offset value corresponding to the first carrier to the first terminal device;

The synchronization device operates in a first wireless communication system, the second wireless access network device and the first carrier operate in a second wireless communication system, and the side link is the first terminal. A direct wireless communication link between the device and the second terminal device.
The device according to claim 14, wherein:

The sending unit is further configured to send first information to the second radio access network device, where the first information is used to request the first DFN offset value corresponding to the first carrier.
The device according to claim 14 or 15, wherein:

The receiving unit is further configured to receive a measurement result of the first carrier in a neighboring cell reported by the first terminal device, where the neighboring cell is a cell provided by the second radio access network device.
The apparatus according to any one of claims 14 to 16, wherein the first DFN offset value and the second DFN offset value are the same.
A communication device, comprising:

A sending unit, configured to send a first direct frame number DFN offset value corresponding to the first carrier to the first radio access network device;

Wherein, the first carrier is a carrier configured by the first radio access network device for the first terminal device for side-link transmission, and the first radio access network device operates in the first radio communication standard. The device and the first carrier operate in a second wireless communication standard, and the side link is a direct-connected wireless communication link between the first terminal device and the second terminal device.
The device according to claim 18, wherein:

The sending unit is further configured to send first information to the first radio access network device, where the first information is used to request the first DFN value corresponding to the first carrier.
A communication device, comprising:

A receiving unit, configured to receive a second DFN offset value corresponding to a first carrier sent by a first radio access network device, where the first carrier is the first radio access network device configured for the apparatus Carrier for side-link transmission, the second DFN offset value is a first corresponding to the first carrier sent by the second radio access network device to the first radio access network device DFN determined;

A processing unit, configured to determine a DFN and a subframe number according to the second DFN offset value;

The first radio access network device operates in a first radio communication system, the second radio access network device and the first carrier operate in a second radio communication system, and the side link is The direct wireless communication link between the device and the second terminal device.
The apparatus according to claim 20, further comprising:

A sending unit is configured to report a measurement result of the first carrier in a neighboring cell to the first radio access network device, where the neighboring cell is a cell provided by the second radio access network device.
The apparatus according to claim 20 or 21, wherein the first DFN offset value is the same as the second DFN offset value.
A communication device, comprising:

A receiving unit, configured to receive a third direct frame number DFN offset value corresponding to the first carrier sent by the second radio access network device;

A processing unit, configured to determine a DFN and a subframe number according to the third DFN offset value;

The first carrier is a carrier configured by the first radio access network device for the device for side-link transmission, and the side-link is a direct link between the device and a second terminal device. Connected to a wireless communication link, the first wireless access network device operates in a first wireless communication system, and the second wireless access network device and the first carrier operate in a second wireless communication system.
The apparatus according to claim 23, wherein the processing unit is specifically configured to:

Determining that the measurement result of the first carrier in a neighboring cell exceeds a first threshold, and the neighboring cell is a cell provided by the second radio access network device;

Determine the DFN and the subframe number according to the third DFN offset value.
The device according to claim 23, wherein:

The receiving unit is further configured to receive a second DFN offset value corresponding to the first carrier sent by the first radio access network device;

When it is determined that the measurement result of the first carrier in the neighboring cell is less than or equal to a first threshold, the processing unit is configured to determine a DFN and a subframe number according to the second DFN offset value.
A communication device, comprising:

A sending unit, configured to send a third direct frame number DFN offset value corresponding to the first carrier to the first terminal device;

The first carrier is a carrier configured by the first radio access network device for the first terminal device and used for side-link transmission, and the side-link is the first terminal device and a second carrier. A direct wireless communication link between terminal devices, the first radio access network device operates in a first communication system, and the device and the first carrier operate in a second communication system.
A computer storage medium is used for storing a computer program, and the computer program comprises a method for performing any one of claims 1-13.
A chip, wherein the chip is applied to a communication device, and the chip includes at least one processor, and when the at least one processor executes an instruction, causes the communication device to execute any one of claims 1-13. Item.