Method and terminal device for wireless communication

Abstract

The embodiment of the application provides a wireless communication method and a terminal device. In the case that there are multiple synchronization sources in sidelink communication, when a sending terminal changes a synchronization source, the DRX synchronization of the sending terminal and a receiving terminal is realized, and it is ensured that the receiving terminal can receive information sent by the sending terminal. The wireless communication method is suitable for sidelink transmission between a first terminal and a second terminal, and comprises the following steps: the first terminal receives information on all receiving resource pools configured for the first terminal according to a DRX configuration, or receives information on a resource pool on which information is received or a receiving resource pool having the same type of synchronization source as the resource pool on which information is received.

Description

TECHNICAL FIELD

[0001] Embodiments of the present application relate to the field of communication, and more particularly, to a method of wireless communication and a terminal device. BACKGROUND

[0002] In sidelink, there can be multiple synchronization sources, and different synchronization sources cause the edges of frames or subframes to be misaligned. When the synchronization scenario or configuration of a transmitting terminal changes and needs to change the synchronization source, how the transmitting terminal and the receiving terminal perform Discontinuous Reception (DRX) synchronization is a problem that needs to be solved urgently. SUMMARY

[0003] Embodiments of the present application provide a method of wireless communication and a terminal device. In the case where there are multiple synchronization sources in sidelink, when the synchronization source of the transmitting terminal changes, the DRX synchronization of the transmitting terminal and the receiving terminal is realized, and it is ensured that the receiving terminal can receive the information transmitted by the transmitting terminal.

[0004] In a first aspect, a method of wireless communication is provided, which is suitable for sidelink transmission between a first terminal and a second terminal, and the method comprises:

[0005] The first terminal performs information reception on all reception resource pools configured to the first terminal according to the DRX configuration, or performs information reception on the resource pool on which information is received or the reception resource pool having the same type of synchronization source as the resource pool on which information is received.

[0006] In a second aspect, a method of wireless communication is provided, which is suitable for sidelink transmission between a first terminal and a second terminal, and the method comprises:

[0007] In the process of changing the synchronization source of the second terminal from a first synchronization source to a second synchronization source, the first terminal and the second terminal maintain the DRX related timers, or the first terminal and the second terminal suspend or stop the DRX related timers.

[0008] In a third aspect, a terminal device is provided, which is used to execute the method in the first aspect.

[0009] Specifically, the terminal device comprises a functional module for executing the method in the first aspect.

[0010] In a fourth aspect, a terminal device is provided, which is used to execute the method in the second aspect.

[0011] Specifically, the terminal device comprises a functional module for executing the method in the second aspect.

[0012] In a fifth aspect, a terminal device is provided, comprising a processor and a memory. The memory is configured to store a computer program, and the processor is configured to invoke and run the computer program stored in the memory to execute the method in the first aspect.

[0013] In a sixth aspect, a terminal device is provided, comprising a processor and a memory. The memory is configured to store a computer program, and the processor is configured to invoke and run the computer program stored in the memory to execute the method in the second aspect.

[0014] In a seventh aspect, an apparatus is provided for implementing the method in any one of the first aspect to the second aspect.

[0015] In particular, the apparatus comprises a processor configured to invoke and run a computer program from a memory, so that a device in which the apparatus is installed executes the method in any one of the first aspect to the second aspect.

[0016] In an eighth aspect, a computer-readable storage medium is provided for storing a computer program, which causes a computer to execute the method in any one of the first aspect to the second aspect.

[0017] In a ninth aspect, a computer program product is provided, comprising computer program instructions, which cause a computer to execute the method in any one of the first aspect to the second aspect.

[0018] In a tenth aspect, a computer program is provided, which, when executed on a computer, causes the computer to execute the method in any one of the first aspect to the second aspect.

[0019] According to the technical solution of the first aspect, the first terminal performs information reception on all reception resource pools configured to the first terminal according to the DRX configuration, or performs information reception on the resource pool in which information is received or the reception resource pool having the same type of synchronization source as the resource pool in which information is received. That is, for the receiving terminal, information reception is performed on all reception resource pools according to the DRX configuration, or information reception is performed on the resource pool in which information is received or the reception resource pool having the same type of synchronization source as the resource pool in which information is received, so that when the synchronization source of the sending terminal changes, the receiving terminal can receive the information sent by the sending terminal, and the DRX synchronization of the sending terminal and the receiving terminal can be realized.

[0020] In the process of changing the synchronization source of the second terminal from the first synchronization source to the second synchronization source, the first terminal and the second terminal keep the DRX related timer, or the first terminal and the second terminal suspend or stop the DRX related timer. That is, for the sending and receiving terminals, in the process of changing the synchronization source of the sending terminal, the DRX related timer is kept, or the DRX related timer is suspended or stopped, so that the DRX synchronization of both the sending terminal and the receiving terminal is realized when the synchronization source of the sending terminal changes, and it is guaranteed that the receiving terminal can receive the information sent by the sending terminal. BRIEF DESCRIPTION OF DRAWINGS

[0021] Figure 1 is a schematic diagram of a communication system architecture to which embodiments of the application can be applied.

[0022] Figure 2 is a schematic diagram of another communication system architecture to which embodiments of the application can be applied.

[0023] Figure 3 is a schematic diagram of a frame / subframe edge misalignment caused by different synchronization sources, provided by the application.

[0024] Figure 4 is a schematic flowchart of a method of wireless communication, provided by an embodiment of the application.

[0025] Figure 5 is a schematic flowchart of another method of wireless communication, provided by an embodiment of the application.

[0026] Figure 6 is a schematic flowchart of DRX synchronization in a synchronization source change process, according to an embodiment of the application.

[0027] Figure 7 is a schematic flowchart of DRX synchronization in a synchronization source change process, according to another embodiment of the application.

[0028] Figure 8 is a schematic flowchart of DRX synchronization in a synchronization source change process, according to still another embodiment of the application.

[0029] Figure 9 is a schematic block diagram of a terminal device, provided by an embodiment of the application.

[0030] Figure 10 is a schematic block diagram of another terminal device, provided by an embodiment of the application.

[0031] Figure 11 is a schematic block diagram of a communication device, provided by an embodiment of the application.

[0032] Figure 12is a schematic block diagram of an apparatus provided by an embodiment of the present application.

[0033] Figure 13 is a schematic block diagram of a communication system provided by an embodiment of the present application. DETAILED DESCRIPTION

[0034] The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments of the present application. All other embodiments obtained by those of ordinary skill in the art without creative labor on the basis of the embodiments in the present application shall fall within the scope of the present application.

[0035] The technical solutions in the embodiments of the present application can be applied to various communication systems, such as a Global System of Mobile communication (GSM) system, a Code Division Multiple Access (CDMA) system, a Wideband Code Division Multiple Access (WCDMA) system, a General Packet Radio Service (GPRS), a Long Term Evolution (LTE) system, an Advanced long term evolution (LTE-A) system, a New Radio (NR) system, an evolved system of the NR system, an LTE-based access to unlicensed spectrum (LTE-U) system, an NR-based access to unlicensed spectrum (NR-U) system, a Non-Terrestrial Networks (NTN) system, a Universal Mobile Telecommunication System (UMTS), a Wireless Local Area Networks (WLAN), a Wireless Fidelity (WiFi), a 5th-Generation (5G) system, or other communication systems, etc.

[0036] Generally, a conventional communication system supports a limited number of connections and is easy to implement. However, with the development of communication technology, a mobile communication system will not only support conventional communication, but also support, for example, Device to Device (D2D) communication, Machine to Machine (M2M) communication, Machine Type Communication (MTC), Vehicle to Vehicle (V2V) communication, or Vehicle to everything (V2X) communication, and the like. Embodiments of the present application can also be applied to these communication systems.

[0037] Optionally, the communication system in the embodiments of the present application can be applied to a Carrier Aggregation (CA) scenario, a Dual Connectivity (DC) scenario, or a Standalone (SA) network deployment scenario.

[0038] Optionally, the communication system in the embodiments of the present application can be applied to an unlicensed spectrum, which can also be considered as a shared spectrum. Alternatively, the communication system in the embodiments of the present application can also be applied to a licensed spectrum, which can also be considered as a non-shared spectrum.

[0039] Embodiments of the present application describe various embodiments in combination with network devices and terminal devices, wherein the terminal device can also be referred to as User Equipment (UE), access terminal, subscriber unit, subscriber station, mobile station, mobile, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user equipment, etc.

[0040] The terminal device can be a station (STATION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication function, a computing device, or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next-generation communication system such as an NR network, or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.

[0041] In the embodiments of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; can also be deployed on the water surface (such as ships, etc.); and can also be deployed in the air (such as airplanes, balloons and satellites, etc.).

[0042] In the embodiments of the present application, the terminal device can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self driving, a wireless terminal device in remote medical treatment, a wireless terminal device in smart grid, a wireless terminal device in transportation safety, a wireless terminal device in smart city, or a wireless terminal device in smart home, etc.

[0043] By way of example and not limitation, in the embodiments of the present application, the terminal device can also be a wearable device. The wearable device can also be referred to as a wearable smart device, which is a general term for devices that are designed and developed by applying wearable technology to daily wear, such as glasses, gloves, watches, clothing and shoes, etc. The wearable device is a portable device that is directly worn on the body or integrated into the clothes or accessories of the user. The wearable device is not only a hardware device, but also has powerful functions through software support and data interaction and cloud interaction. The general wearable smart device includes devices with complete functions, large size, and the ability to realize complete or partial functions without relying on a smart phone, such as smart watches or smart glasses, etc., and devices that focus on a certain type of application function and need to be used in cooperation with other devices such as smart phones, such as various smart wristbands and smart jewelry for monitoring vital signs, etc.

[0044] In the embodiments of the present application, the network device can be a device for communicating with the mobile device, and can be an access point (AP) in a WLAN, a base transceiver station (BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved Node B (eNB or eNodeB) in LTE, or a relay station or an access point, or a vehicle-mounted device, a wearable device, a network device in an NR network or a base station (gNB), or a network device in a future evolved PLMN network or a network device in an NTN network, etc.

[0045] By way of example and not limitation, in the embodiments of the present application, the network device can have a mobile characteristic, for example, the network device can be a mobile device. Alternatively, the network device can be a satellite or a balloon station. For example, the satellite can be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Alternatively, the network device can also be a base station arranged at a position on land, water, etc.

[0046] In the embodiments of the present application, the network device can serve a cell, and the terminal device communicates with the network device through a transmission resource (for example, a frequency domain resource, or a spectrum resource) used by the cell. The cell can be a cell corresponding to the network device (for example, a base station), and the cell can belong to a macro base station or a base station corresponding to a small cell. The small cell can include a metro cell, a micro cell, a pico cell, a femto cell, etc., and these small cells have the characteristics of small coverage and low transmit power, and are suitable for providing high-speed data transmission services.

[0047] It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and / or" herein is only used to describe the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B can represent the three cases of A alone, A and B together, and B alone. In addition, the character " / " herein generally represents an "or" relationship between the associated objects.

[0048] The terms used in the embodiments of the present application are only used to explain the specific embodiments of the present application, and are not intended to limit the present application. The terms "first", "second", "third", and "fourth" and the like in the specification and claims of the present application and the drawings are used to distinguish different objects, and are not used to describe a particular order. In addition, the terms "comprise" and "have" and any variations thereof are intended to cover non-exclusive inclusion.

[0049] It should be understood that the "indication" mentioned in the embodiments of the present application can be direct indication, or indirect indication, or can represent an associated relationship. For example, A indicates B, which can mean that B can be obtained through A; or A indirectly indicates B, for example, A indicates C, and B can be obtained through C; or A and B have an associated relationship.

[0050] In the description of the embodiments of the present application, the term "corresponding" can represent a direct or indirect corresponding relationship between the two, or an associated relationship between the two, or an indication and being indicated, configuration and being configured, etc.

[0051] In the embodiments of the present application, "predefined" can be realized by pre-saving corresponding codes, tables or other means for indicating related information in devices (such as terminal devices and network devices), and the specific implementation mode of the present application is not limited. For example, predefinition can refer to definition in a protocol.

[0052] In the embodiments of the present application, the "protocol" can refer to a standard protocol in the communication field, which can include LTE protocol, NR protocol and related protocols applied to future communication systems, and the present application is not limited thereto.

[0053] Device-to-device communication is a kind of sidelink transmission technology (Sidelink, SL) based on D2D. Unlike the way of receiving or sending communication data through a base station in a traditional cellular system, the vehicle networking system adopts a terminal-to-terminal direct communication mode, so it has higher spectrum efficiency and lower transmission delay.

[0054] Figure 1 is a schematic diagram of a communication system to which the embodiments of the present application are applicable. The transmission resources of the vehicle terminal (vehicle terminal 121 and vehicle terminal 122) are allocated by the base station 110, and the vehicle terminal transmits data on the sidelink according to the resources allocated by the base station 110. Specifically, the base station 110 can allocate resources for single transmission to the terminal, or can allocate resources for semi-static transmission to the terminal.

[0055] Figure 2Fig. 2 is a schematic diagram of another communication system to which embodiments of the present application are applicable. The vehicle-mounted terminals (vehicle-mounted terminal 131 and vehicle-mounted terminal 132) autonomously select transmission resources on the resources of the sidelink for data transmission. Optionally, the vehicle-mounted terminals can randomly select transmission resources, or select transmission resources through sensing.

[0056] For better understanding of the embodiments of the present application, the related terms of the present application are explained.

[0057] Proximity-based Services (ProSe): In release 12 (Rel-12) or release 13 (Rel-13), device-to-device communication is studied for the scenario of ProSe, which mainly aims at public safety services.

[0058] In ProSe, by configuring the location of the resource pool in the time domain, for example, the resource pool is non-continuous in the time domain, the UE can non-continuously transmit / receive data on the sidelink, thereby achieving the effect of power saving.

[0059] V2X: In release 14 (Rel-14) or release 15 (Rel-15), the vehicle-to-everything (V2X) system is studied for the scenario of vehicle-to-vehicle communication, which mainly aims at the services of relatively high-speed vehicle-to-vehicle and vehicle-to-person communication. In V2X, since the vehicle-mounted system has continuous power supply, power efficiency is not the main problem, and the delay of data transmission is the main problem, so the terminal device is required to continuously transmit and receive in the system design.

[0060] FeD2D: In Rel-14, this scenario is studied for the scenario of wearable devices accessing the network through mobile phones, which mainly aims at the scenario of low mobile speed and low power access. In FeD2D, in the pre-research stage, 3GPP concludes that the base station can configure the DRX parameters of the remote terminal through a relay terminal.

[0061] For better understanding of the embodiments of the present application, the related NR V2X of the present application is explained.

[0062] NR V2X is not limited to the broadcast scenario on the basis of LTE V2X, but is further expanded to the unicast and groupcast scenarios, and the application of V2X is studied in these scenarios.

[0063] Similar to LTE V2X, NR V2X also defines mode 1 (corresponding to the above Figure 1 communication system) and mode 2 (corresponding to the above Figure 2Two resource grant modes are shown in the communication system) further, the user can be in a mixed mode, that is, both mode 1 and mode 2 can be used for resource acquisition. The resource acquisition is indicated by the way of sidelink grant, that is, the sidelink grant indicates the time-frequency location of the corresponding physical sidelink control channel (PSCCH) and physical sidelink shared channel (PSSCH) resource.

[0064] Unlike LTE V2X, in addition to feedback-free, UE self-initiated hybrid automatic repeat request (HARQ) retransmission, NR V2X introduces feedback-based HARQ retransmission, not limited to unicast communication, also including groupcast communication.

[0065] The same as LTE V2X, in NR V2X, since the vehicle-mounted system has continuous power supply, power efficiency is not the main problem, and the delay of data transmission is the main problem, so the terminal device is required to continuously transmit and receive in the system design.

[0066] For better understanding of the embodiments of the present application, the resource pool selection method based on different synchronization sources related to the present application is described.

[0067] The synchronization source type allowed by the resource pool is included in the resource pool configuration information, that is, only the terminal selecting the synchronization source type can use the resource pool for data transmission. Before performing sidelink transmission, the terminal first selects a synchronization source, and uses the transmission resource pool allowed by the synchronization source type for data transmission according to the synchronization source type. If there are multiple transmission resource pools allowed by the synchronization source type, there is no specific standardized selection criterion, but one of them is selected based on the terminal implementation.

[0068] For better understanding of the embodiments of the present application, the DRX related to the present application is described.

[0069] A UE discontinuously monitors a physical downlink control channel (PDCCH) according to a DRX configuration for power saving purposes. When the PDCCH carries a cell radio network temporary identity (C-RNTI) corresponding to the UE, a cancellation indication RNTI (CI-RNTI), a configured scheduling RNTI (CS-RNTI), an interrupted transmission indication RNTI (INT-RNTI), a slot format indication RNTI (SFI-RNTI), a semi-persistent channel state information radio network temporary identity (SP-CSI-RNTI), a transmit power control physical uplink control channel RNTI (TPC-PUCCH-RNTI), a transmit power control physical uplink shared channel RNTI (TPC-PUSCH-RNTI), a transmit power control sounding reference signal RNTI (TPC-SRS-RNTI), or an artificial intelligence RNTI (AI-RNTI), the UE performs a corresponding DRX operation according to the control information. The network controls the DRX behavior of the UE by configuring a series of parameters, including:

[0070] DRX on duration timer (drx-onDurationTimer), DRX slot offset (drx-SlotOffset), DRX inactivity timer (drx-InactivityTimer), downlink DRX retransmission timer (drx-RetransmissionTimerDL), uplink DRX retransmission timer (drx-RetransmissionTimerUL), DRX long cycle start offset (drx-LongCycleStartOffset), DRX short cycle (drx-ShortCycle) parameters (optionally): the short DRX cycle (theShortDRXcycle), DRX short cycle timer (drx-ShortCycleTimer) (optionally), downlink HARQ round trip time timer (HARQ-RTT-TimerDL), uplink DRX HARQ RTT (drx-HARQ-RTT-TimerUL), power saving wakeup (ps-Wakeup) (optionally), power saving transmit other periodic channel state information (ps-TransmitOtherPeriodicCSI) (optionally), power saving transmit periodic L1 reference signal received power (ps-TransmitPeriodicL1-RSRP) (optionally).

[0071] wherein the UE will be in the DRX active state if:

[0072] during the running of the drx-onDurationTimer or the drx-InactivityTimer;

[0073] during the running of the drx-RetransmissionTimerDL or the drx-RetransmissionTimerUL;

[0074] during the running of the random access contention resolution timer (ra-ContentionResolutionTimer) or the message B response window (msgB-ResponseWindow);

[0075] There is an unprocessed scheduling request (Scheduling Request, SR);

[0076] The PDCCH indicates that there is a new transmission period.

[0077] For better understanding of the embodiments of the present application, the sidelink synchronization technology related to the present application is described.

[0078] The synchronization source types in the NR-V2X system include: eNB, gNB, Global Navigation Satellite System (GNSS), UE, and terminal internal clock. The levels of each synchronization source defined in the NR-V2X system are shown in Table 1, in which the smaller the priority identifier represents the higher the priority, for example, the GNSS is configured as the highest priority, and the priority size can be: P0>P1>P2>P3>P4>P5>P6>P7. For example, the gNB / eNB is configured as the highest priority, and the priority size can be: P0'>P1'>P2'>P3'>P4'>P5'>P6'>P7'.

[0079] Table 1 NR-V2X system synchronization priority

[0080]

[0081] The terminal for sidelink transmission can be located in or out of the cell coverage, and when in the cell coverage, the network can configure the gNB / eNB or GNSS to be a higher priority. The UE will determine the synchronization source according to different scenarios and different configuration conditions.

[0082] In the DRX mechanism based on the Uu interface (i.e., uplink and downlink transmission), all UEs and the network maintain downlink synchronization, so the DRX of the Uu only needs to be designed for the network-based unique synchronization source. In the DRX mechanism based on the PC5 interface (i.e., sidelink transmission), there are multiple synchronization sources, including GNSS-based synchronization, gNB / eNB-based synchronization, and UE-based synchronization, as shown in Figure 3 The frame / subframe edges caused by different synchronization sources can not be aligned.

[0083] In a sidelink system, when the synchronization scenario or configuration of the sending UE changes and needs to change the synchronization source, after the synchronization source of the sending UE changes, it will transmit in the sending resource pool (Tx pool) that supports the new synchronization source according to the new synchronization source, and the receiving UE continues to perform the DRX receiving operation according to the original synchronization source because it does not know the change, thereby causing the DRX mechanisms of the sending UE and the receiving UE to be out of synchronization, and further causing data transmission failure.

[0084] Based on the above problems, the present application provides a DRX synchronization scheme. In the case of multiple synchronization sources in sidelink communication, when the synchronization source of the sending terminal changes, the receiving terminal can receive the information sent by the sending terminal. In addition, the DRX synchronization of the sending and receiving terminals can also be realized.

[0085] The technical scheme of the present application will be described in detail below through specific embodiments.

[0086] Figure 4 is a schematic flowchart of a method 200 of wireless communication according to an embodiment of the present application, which is suitable for sidelink transmission between a first terminal and a second terminal, as shown in Figure 4 The method 200 of wireless communication can be performed by the first terminal, and the method 200 of wireless communication can include at least part of the following contents:

[0087] S210, according to the DRX configuration, the first terminal performs information reception on all receiving resource pools configured for the first terminal, or on the information receiving resource pool or the receiving resource pool with the same type of synchronization source as the information receiving resource pool.

[0088] In the embodiments of the present application, the first terminal performs information reception on all configured receiving resource pools, or the first terminal performs information reception on the information receiving resource pool or the receiving resource pool with the same type of synchronization source as the information receiving resource pool, so that in the case of synchronization source transformation of the second terminal, the DRX synchronization of the sending and receiving terminals is realized, and the first terminal can receive the information sent by the second terminal.

[0089] In the embodiments of the present application, the DRX configuration is for sidelink between the first terminal and the second terminal. For example, the first terminal can perform information reception on the receiving resource pool according to the DRX configuration, and the second terminal can perform information transmission on the sending resource pool according to the DRX configuration.

[0090] In the embodiments of the present application, the information of the sending and receiving can be data, or a signal or other message type, which is not limited by the present application.

[0091] In some embodiments, the DRX configuration is preconfigured or agreed by protocol, or the DRX configuration is configured by a network device, or the DRX configuration is configured by the second terminal.

[0092] For example, the DRX configuration is configured by a network device through a system information block (SIB) or dedicated signaling.

[0093] In some embodiments, the synchronization source before and after the change of the second terminal can be one of the synchronization sources described in Table 1 and another.

[0094] In some embodiments, in the case where the first condition is met, the first terminal maintains the DRX related timer; or the first terminal suspends or stops the DRX related timer.

[0095] In some embodiments, the DRX related timer can include but is not limited to at least one of the following:

[0096] The sidelink DRX on duration timer (sl-drx-onDurationTimer), the sidelink DRX inactivity timer (sl-drx-InactivityTimer), the sidelink DRX retransmission timer (sl-drx-RetransmissionTimer), and the sidelink HARQ RTT timer (sl-HARQ-RTT-Timer).

[0097] In some embodiments, the first condition includes at least one of the following:

[0098] The first terminal receives information according to the DRX configuration on all receiving resource pools configured for the first terminal;

[0099] When the first terminal receives the first information;

[0100] After the first terminal receives the first information;

[0101] After the first terminal receives the first information for a first time duration;

[0102] After the first terminal receives the first information and sends the second information;

[0103] After the first terminal receives the first information and when sending the second information;

[0104] After the first terminal receives the first information and sends the second information for a second time duration;

[0105] The first information is used to indicate that the synchronization source is changed to a target type of synchronization source, and the second information includes positive feedback for the first information.

[0106] For example, when the first terminal is in the DRX active state, the first terminal receives the first information sent by the second terminal, so as to know that the second terminal needs to change the synchronization source, and in order to realize DRX synchronization, the first terminal needs to receive on the receiving resource pool where the information is received or the receiving resource pool of the same type as the resource pool where the information is received (the resource pool supports the target type of synchronization source).

[0107] For example, after the first terminal receives the first information sent by the second terminal, the first terminal can send positive feedback for the first information to the second terminal.

[0108] It should be noted that the first terminal can receive the information sent by the second terminal when the first terminal is in the DRX active state, and the first terminal cannot receive the information sent by the second terminal when the first terminal is in the DRX inactive state or the deactivation state.

[0109] In some embodiments, in the case where the second terminal does not receive the positive feedback for the first information, the second terminal can resend the first information. The specific number of retransmissions can be preconfigured or agreed by the protocol, or agreed by the first terminal and the second terminal, or configured by the network device.

[0110] In some embodiments, the first time length can be preconfigured or agreed by the protocol, or the first time length is agreed by the first terminal and the second terminal, or the first time length is configured by the network device, or the first time length is determined based on the implementation of the first terminal.

[0111] In some embodiments, the second time length can be preconfigured or agreed by the protocol, or the second time length is agreed by the first terminal and the second terminal, or the second time length is configured by the network device, or the second time length is determined based on the implementation of the first terminal.

[0112] In some embodiments, the first information at least includes information of the synchronization source of the target type.

[0113] In some embodiments, the first terminal receives information according to the first information on one or more receiving resource pools supporting the synchronization source of the target type. Thus, in the case where the second terminal occurs synchronization source switching, the first terminal can receive the information sent by the second terminal, and the DRX synchronization of the transmitting and receiving terminals can also be realized.

[0114] In some embodiments, in the case where the second condition is met, the first terminal continues the DRX related timer previously paused or stopped, or the first terminal restarts the DRX related timer, or the first terminal maintains the DRX active state within a target time length.

[0115] In some embodiments, the target time length can be preconfigured or agreed by the protocol, or the target time length is agreed by the first terminal and the second terminal, or the target time length is configured by the network device, or the target time length is determined based on the implementation of the first terminal.

[0116] In some embodiments, the second condition includes at least one of the following:

[0117] The first terminal receives information on a receiving resource pool of a resource pool where the information is received or a receiving resource pool of a same type of synchronization source as the resource pool where the information is received;

[0118] The first terminal receives third information;

[0119] After the first terminal receives the third information;

[0120] After the first terminal receives the third information for a third time length;

[0121] The first terminal receives the third information and sends fourth information;

[0122] The first terminal receives the third information and sends the fourth information;

[0123] After the first terminal receives the third information and sends the fourth information for a fourth time length;

[0124] The third information is synchronization confirmation information, and the fourth information is synchronization confirmation response information.

[0125] For example, when the first terminal is in a DRX active state, the first terminal receives the third information sent by the second terminal, so as to realize confirmation after a synchronization source is changed.

[0126] For example, after the first terminal receives the third information sent by the second terminal, the first terminal can send the fourth information to the second terminal to respond to the synchronization confirmation information. That is, the first terminal and the second terminal exchange the synchronization confirmation information, and thus realize DRX synchronization.

[0127] In some embodiments, the third time length can be pre-configured or agreed by a protocol, or the third time length is agreed by the first terminal and the second terminal, or the third time length is configured by a network device, or the third time length is determined based on implementation of the first terminal.

[0128] In some embodiments, the fourth time length can be pre-configured or agreed by a protocol, or the fourth time length is agreed by the first terminal and the second terminal, or the fourth time length is configured by a network device, or the fourth time length is determined based on implementation of the first terminal.

[0129] In some embodiments, the first terminal receives fifth information sent by the second terminal; and the first terminal receives information on a receiving resource pool of a resource pool where the fifth information is received or a receiving resource pool of a same type of synchronization source as the resource pool where the fifth information is received.

[0130] Specifically, after the second terminal changes the synchronization source, the second terminal sends the fifth information to the first terminal when the first terminal is in the DRX active state. And the first terminal receives information on the receiving resource pool of the fifth information or the receiving resource pool of the same type of synchronization source as the receiving resource pool of the fifth information, so that in the case of synchronization source transformation of the second terminal, the first terminal can receive the information sent by the second terminal, and the DRX synchronization of the two terminals can also be realized.

[0131] In some embodiments, the fifth information includes but is not limited to at least one of the following:

[0132] Data information, synchronization information, discovery information, PC5-S information.

[0133] For example, the data information is PSSCH information.

[0134] For example, the synchronization information is a sidelink synchronization signal (SLSS).

[0135] It should be noted that the PC5-S information can be PC5 safety (PC5-S) information. For example, it can be upper layer information, NAS layer information, connection establishment request, etc.

[0136] In some embodiments, in the case where the first terminal receives information on all receiving resource pools configured to the first terminal according to the DRX configuration, the above S210 can specifically include:

[0137] For each receiving resource pool, the first terminal determines a first DRX timer according to a sidelink DRX cycle (sl-drx-Cycle), a sidelink DRX start offset (sl-drx-StartOffset), and a sidelink DRX time slot offset (sl-drx-slotOffset); and / or,

[0138] For each receiving resource pool, when the first terminal receives new PSCCH or PSSCH information, or after the first terminal receives new PSCCH or PSSCH information for a second time length, or when the first terminal sends HARQ feedback, or after the first terminal sends HARQ feedback, the first terminal starts or restarts a second DRX timer; and / or,

[0139] For each receiving resource pool, the first terminal starts or restarts the third DRX timer after a HARQ RTT timer expires, or after a PSCCH or PSSCH decoding fails, or after receiving a Sidelink Control Information (SCI) or PSSCH information.

[0140] In some embodiments, in a case that the first terminal receives information according to the DRX configuration on a receiving resource pool where the information is received or a receiving resource pool having a same type of synchronization source as the receiving resource pool where the information is received, the S210 can specifically include:

[0141] For the receiving resource pool where the information is received or a receiving resource pool having a same type of synchronization source as the receiving resource pool where the information is received, the first terminal determines the first DRX timer according to a sidelink DRX cycle (sl-drx-Cycle), a sidelink DRX start offset (sl-drx-StartOffset), and a sidelink DRX slot offset (sl-drx-slotOffset); and / or,

[0142] For the receiving resource pool where the information is received or a receiving resource pool having a same type of synchronization source as the receiving resource pool where the information is received, the first terminal starts or restarts the second DRX timer when the first terminal receives a new transmission PSCCH or PSSCH information, or after the first terminal receives the new transmission PSCCH or PSSCH information for a second time duration, or when the first terminal sends a HARQ feedback, or after the first terminal sends the HARQ feedback; and / or,

[0143] For the receiving resource pool where the information is received or a receiving resource pool having a same type of synchronization source as the receiving resource pool where the information is received, the first terminal starts or restarts the third DRX timer after a HARQ RTT timer expires, or after a PSCCH or PSSCH decoding fails, or after receiving a SCI information or PSSCH information.

[0144] In some embodiments, the first DRX timer can be a sidelink DRX on duration timer (sl-drx-onDurationTimer).

[0145] In some embodiments, the second DRX timer can be a sidelink DRX inactivity timer (sl-drx-InactivityTimer).

[0146] In some embodiments, the third DRX timer can be a sidelink DRX retransmission timer (sl-drx-RetransmissionTimer).

[0147] Therefore, in the embodiments of the present application, the first terminal receives information on all receiving resource pools configured to the first terminal according to the DRX configuration, or receives information on the resource pool on which the information is received or the receiving resource pool having the same type of synchronization source as the resource pool on which the information is received. That is, for the receiving terminal, information is received on all receiving resource pools according to the DRX configuration, or information is received on the resource pool on which the information is received or the receiving resource pool having the same type of synchronization source as the resource pool on which the information is received, so that when the synchronization source of the sending terminal changes, the receiving terminal can receive the information sent by the sending terminal, and the DRX synchronization of the sending terminal and the receiving terminal can be realized.

[0148] The first terminal side embodiments of the present application are described in detail above in combination with Figure 4 The second terminal side embodiments of the present application are described in detail below in combination with Figure 5 It should be understood that the second terminal side embodiments correspond to the first terminal side embodiments, and similar descriptions can be referred to the first terminal side embodiments.

[0149] Figure 5 FIG. 3 is a schematic flowchart of a method 300 of wireless communication according to the embodiments of the present application, which is applicable to the sidelink transmission between the first terminal and the second terminal. As shown in FIG. 3, the method 300 of wireless communication can be performed by the second terminal, and the method 300 of wireless communication can include at least part of the following contents: Figure 5

[0150] S310, in the process that the synchronization source of the second terminal changes from the first synchronization source to the second synchronization source, the second terminal maintains the DRX related timer, or the second terminal suspends or stops the DRX related timer.

[0151] In the embodiments of the present application, in the process that the synchronization source of the second terminal changes from the first synchronization source to the second synchronization source, the first terminal and the second terminal maintain the DRX related timer, or the first terminal and the second terminal suspend or stop the DRX related timer. Thus, in the case that the synchronization source of the second terminal changes, the DRX synchronization of the sending terminal and the receiving terminal is realized, and the first terminal can receive the information sent by the second terminal.

[0152] In some embodiments, the first synchronization source can be one of the synchronization sources described in Table 1 above, and the second synchronization source can be another one of the synchronization sources described in Table 1 above.

[0153] In some embodiments, the DRX related timer can include but is not limited to at least one of the following:

[0154] ​a sidelink DRX on duration timer (sl-drx-onDurationTimer), a sidelink DRX inactivity timer (sl-drx-InactivityTimer), a sidelink DRX retransmission timer (sl-drx-RetransmissionTimer), a sidelink HARQ RTT timer (sl-HARQ-RTT-Timer).

[0155] In some embodiments, in a case that the second terminal maintains the DRX related timer during the synchronization source change process, the second terminal determines a DRX active time of the first terminal according to the synchronization compensation value and the DRX configuration between the second synchronization source and the first synchronization source.

[0156] In some embodiments, the unit of the synchronization compensation value includes, but is not limited to, one of the following:

[0157] subframe, slot, symbol, millisecond.

[0158] In some embodiments, in a case that the second terminal maintains the DRX related timer during the synchronization source change process, the second terminal can perform the following operations:

[0159] In a case that the second terminal changes from the first synchronization source to the second synchronization source during running of the first DRX timer, the second terminal determines a running time of the first DRX timer in a transmission resource pool for information transmission after the synchronization source change according to a sidelink DRX cycle (sl-drx-Cycle), a sidelink DRX start offset (sl-drx-StartOffset), a sidelink DRX slot offset (sl-drx-slotOffset); and / or,

[0160] In a case that the second terminal changes from the first synchronization source to the second synchronization source during running of the second DRX timer, the second terminal determines a running time of the second DRX timer in a transmission resource pool for information transmission after the synchronization source change according to a start time and a running time length of the second DRX timer in the transmission resource pool for information transmission before the synchronization source change, and the synchronization compensation value.

[0161] In some embodiments, the first DRX timer can be a sidelink DRX on duration timer (sl-drx-onDurationTimer).

[0162] In some embodiments, the second DRX timer can be a sidelink DRX inactivity timer (sl-drx-InactivityTimer) or a sidelink DRX retransmission timer (sl-drx-RetransmissionTimer).

[0163] In some embodiments, when the first terminal is in the DRX active state, the second terminal transmits information on one or more transmission resource pools supporting the second synchronization source according to the DRX configuration.

[0164] It should be noted that when the first terminal is in the DRX active state, the first terminal can receive the information transmitted by the second terminal, and when the first terminal is in the DRX inactive state or the deactivation state, the first terminal cannot receive the information transmitted by the second terminal.

[0165] In some embodiments, when the third condition is met, the second terminal suspends or stops the DRX related timer.

[0166] In some embodiments, the third condition includes at least one of:

[0167] When the second terminal transmits the first information;

[0168] After the second terminal transmits the first information;

[0169] After the second terminal transmits the first information for a fifth time length;

[0170] After the second terminal transmits the first information and receives the second information;

[0171] When the second terminal transmits the first information and receives the second information;

[0172] After the second terminal transmits the first information and receives the second information for a sixth time length;

[0173] Wherein, the first information is used to indicate that the synchronization source is changed to a target type of synchronization source, and the second information includes positive feedback for the first information.

[0174] For example, when the first terminal is in the DRX active state, the first terminal receives the first information transmitted by the second terminal, so as to know that the second terminal needs to change the synchronization source, and in order to realize the DRX synchronization, the first terminal needs to receive on the reception resource pool on which the information is received or the reception resource pool of the same synchronization type as the resource pool on which the information is received (the resource pool supports the target type of synchronization source).

[0175] For example, after the first terminal receives the first information transmitted by the second terminal, the first terminal can send positive feedback for the first information to the second terminal.

[0176] In some embodiments, the first information at least includes information of the target type of synchronization source.

[0177] In some embodiments, after sending the first information, the second terminal enters a DRX active state, or the second terminal enters a state in which data can be received.

[0178] In some embodiments, in a case where positive feedback for the first information is not received, the second terminal re-sends the first information. The specific number of retransmissions can be pre-configured or agreed by protocol, or agreed by the first terminal and the second terminal, or configured by the network device.

[0179] In some embodiments, the fifth time length can be pre-configured or agreed by protocol, or agreed by the first terminal and the second terminal, or configured by the network device, or determined based on implementation of the second terminal.

[0180] In some embodiments, the sixth time length can be pre-configured or agreed by protocol, or agreed by the first terminal and the second terminal, or configured by the network device, or determined based on implementation of the second terminal.

[0181] In some embodiments, in a case where the fourth condition is met, the second terminal continues a DRX-related timer that was previously suspended or stopped, or the second terminal restarts the DRX-related timer, or the second terminal can send information to the first terminal within a target time length.

[0182] In some embodiments, the target time length can be pre-configured or agreed by protocol, or agreed by the first terminal and the second terminal, or configured by the network device, or determined based on implementation of the second terminal.

[0183] In some embodiments, the fourth condition includes at least one of the following:

[0184] When the second terminal sends third information;

[0185] After the second terminal sends the third information;

[0186] After the second terminal sends the third information for a seventh time length;

[0187] After the second terminal sends the third information and receives fourth information;

[0188] When the second terminal sends the third information and receives the fourth information;

[0189] After the second terminal sends the third information and receives the fourth information for an eighth time length;

[0190] Wherein the third information is synchronization confirmation information, and the fourth information is synchronization confirmation response information.

[0191] For example, the first terminal receives the third information sent by the second terminal when the first terminal is in the DRX active state, so as to realize the confirmation after the change of the synchronization source.

[0192] For example, after the first terminal receives the third information sent by the second terminal, the first terminal can send the fourth information to the second terminal to respond to the synchronization confirmation information. That is, the first terminal and the second terminal exchange the synchronization confirmation information, and then realize the DRX synchronization.

[0193] In some embodiments, the seventh time length can be pre-configured or agreed by protocol, or the seventh time length is agreed by the first terminal and the second terminal, or the seventh time length is configured by the network device, or the seventh time length is determined based on the implementation of the second terminal.

[0194] In some embodiments, the eighth time length can be pre-configured or agreed by protocol, or the eighth time length is agreed by the first terminal and the second terminal, or the eighth time length is configured by the network device, or the eighth time length is determined based on the implementation of the second terminal.

[0195] In some embodiments, in the case that the second terminal suspends or stops the DRX related timer in the synchronization source change process, after the synchronization source of the second terminal changes from the first synchronization source to the second synchronization source, and the first terminal is in the DRX active state, the second terminal sends fifth information to the first terminal according to the DRX configuration on one or more sending resource pools supporting the second synchronization source.

[0196] Specifically, the first terminal receives information on the receiving resource pool of the fifth information or the receiving resource pool of the same type of synchronization source as the receiving resource pool of the fifth information. Thus, in the case that the second terminal changes the synchronization source, the first terminal can receive the information sent by the second terminal, and the DRX synchronization of both the sending terminal and the receiving terminal can be realized.

[0197] In some embodiments, the fifth information includes at least one of the following:

[0198] Data information, synchronization information, discovery information, PC5-S information.

[0199] It should be noted that the PC5-S information can be PC5 safety (PC5-S) information. For example, it can be upper layer information, NAS layer information, connection establishment request, etc.

[0200] In some embodiments, the DRX configuration is for a sidelink between the first terminal and a second terminal. For example, the first terminal can perform information receiving on a receiving resource pool according to the DRX configuration, and the second terminal can perform information transmitting on a transmitting resource pool according to the DRX configuration.

[0201] In the embodiments of the present application, the information being transceived can be data, or a signal or other information type, which is not limited in the present application.

[0202] In some embodiments, the DRX configuration is preconfigured or agreed by a protocol, or the DRX configuration is configured by a network device, or the DRX configuration is configured by the first terminal.

[0203] For example, the DRX configuration is configured by the network device through SIB or dedicated signaling.

[0204] Therefore, in the embodiments of the present application, during the process of changing the synchronization source of the second terminal from the first synchronization source to the second synchronization source, the first terminal and the second terminal maintain the DRX related timers; or the first terminal and the second terminal suspend or stop the DRX related timers. That is, for the transmitting terminal and the receiving terminal, during the process of changing the synchronization source of the transmitting terminal, the DRX related timers are maintained, or the DRX related timers are suspended or stopped, so that the DRX synchronization of the transmitting terminal and the receiving terminal is realized when the synchronization source of the transmitting terminal changes, and it is ensured that the receiving terminal can receive the information transmitted by the transmitting terminal.

[0205] The technical solutions of the present application are described in detail below through Embodiments 1 to 3.

[0206] In Embodiment 1, the receiving UE (i.e. UE2, corresponding to the first terminal) performs information receiving on all receiving resource pools based on the DRX configuration, and the transmitting UE (i.e. UE1, corresponding to the second terminal) does not stop the DRX related timers during the process of switching the synchronization source. As shown in the following figure, Figure 6 In Embodiment 1, UE1 and UE2 perform DRX synchronization by executing the processes described in S11 to S16.

[0207] S11, UE2 acquires the DRX configuration.

[0208] The DRX configuration is for a sidelink between UE1 and UE2.

[0209] The DRX configuration can be obtained in the following ways:

[0210] Preconfiguration or protocol agreement;

[0211] Configuration by the network side through SIB or dedicated signaling;

[0212] UE1 configuration.

[0213] S12, UE2 receives information on all receiving resource pools configured to UE2 according to the DRX configuration.

[0214] For example, for each receiving resource pool, UE2 determines the sidelink DRX on duration timer (sl-drx-onDurationTimer) according to the sidelink DRX cycle (sl-drx-Cycle), the sidelink DRX start offset (sl-drx-StartOffset), and the sidelink DRX slot offset (sl-drx-slotOffset).

[0215] For example, for each receiving resource pool, UE2 starts or restarts the sidelink DRX inactivity timer (sl-drx-InactivityTimer) when or after UE2 receives a new PSCCH or PSSCH information, or when or after UE2 sends a HARQ feedback.

[0216] For example, for each receiving resource pool, UE2 starts or restarts the sidelink DRX retransmission timer (sl-drx-RetransmissionTimer) after a HARQ RTT timer expires, or after a PSCCH or PSSCH decoding fails, or after UE2 receives a SCI information.

[0217] S13, UE1 synchronizes to the new synchronization source and transmits using a transmitting resource pool (Tx pool) that supports the synchronization source.

[0218] S14, UE1 calculates a synchronization compensation value between the new and old synchronization sources.

[0219] The unit of the synchronization compensation value can include one of the following:

[0220] Subframe, slot, symbol, millisecond.

[0221] S15, UE1 determines the DRX activation time of UE2 according to the synchronization compensation value and the DRX configuration.

[0222] For example, if the synchronization source is switched during the running of the sidelink DRX on duration timer (sl-drx-onDurationTimer), the UE 1 determines the running time of the sl-drx-onDurationTimer in the new Tx pool according to the sidelink DRX cycle (sl-drx-Cycle), the sidelink DRX start offset (sl-drx-StartOffset), and the sidelink DRX slot offset (sl-drx-slotOffset).

[0223] For example, if the synchronization source is switched during the running of the sidelink DRX inactivity timer (sl-drx-InactivityTimer), the UE 1 determines the running time of the sl-drx-InactivityTimer in the new Tx pool according to the synchronization compensation value, the starting time of the sl-drx-InactivityTimer on the original Tx pool, and the value of the sl-drx-InactivityTimer.

[0224] For example, if the synchronization source is switched during the running of the sidelink DRX retransmission timer (sl-drx-RetransmissionTimer), the UE 1 determines the running time of the sl-drx-RetransmissionTimer in the new Tx pool according to the synchronization compensation value, the starting time of the sl-drx-RetransmissionTimer on the original Tx pool, and the value of the sl-drx-RetransmissionTimer.

[0225] S16, the UE 1 sends information to the UE 2 within the DRX active time of the UE 2 and continues to transmit information in the new Tx pool based on the DRX configuration.

[0226] In embodiment 2, the receiving UE (i.e., the UE 2, corresponding to the first terminal described above) receives information based on the DRX configuration, and the receiving resource pool or the same synchronization source as the information receiving on the resource pool of the transmitting UE (i.e., the UE 1, corresponding to the second terminal described above) is informed of the change of the synchronization source during the switching of the synchronization source, and the receiving UE synchronizes the receiving resource pool (Rx pool) and the DRX. As shown in Figure 7

[0227] S21, the UE 2 acquires the DRX configuration.

[0228] The DRX configuration is for the sidelink between the UE 1 and the UE 2.

[0229] The DRX configuration can be obtained in the following manner:​

[0230] Pre-configuration or protocol agreement;

[0231] Configured by SIB or dedicated signaling on network side;

[0232] UE1 configuration.

[0233] S22, UE2 performs discontinuous reception operation according to the DRX configuration on the reception resource pool (Rx pool) of the received data or the same Rx pool as the synchronization source of the Rx pool.

[0234] For example, for each reception resource pool, UE2 determines the sidelink DRX duration timer (sl-drx-onDurationTimer) according to the sidelink DRX cycle (sl-drx-Cycle), the sidelink DRX start offset (sl-drx-StartOffset), and the sidelink DRX slot offset (sl-drx-slotOffset).

[0235] For example, for each reception resource pool, UE2 starts or restarts the sidelink DRX inactivity timer (sl-drx-InactivityTimer) when receiving or after receiving the new transmission PSCCH or PSSCH information, or after a period of time of receiving the new transmission PSCCH or PSSCH information, or when sending or after sending the HARQ feedback.

[0236] For example, for each reception resource pool, UE2 starts or restarts the sidelink DRX retransmission timer (sl-drx-RetransmissionTimer) after the HARQ RTT timer expires, or after the PSCCH or PSSCH decoding fails, or after receiving the SCI information.

[0237] S23, UE1 sends synchronization source change notification information to UE2.

[0238] The synchronization source change notification information contains new synchronization source synchronization information.

[0239] It should be noted that the synchronization source change notification information needs to be sent during the DRX activation period of UE2.

[0240] In some real ways, after sending the synchronization source change notification information, UE1 enters the DRX activation state (if DRX is configured) or the receivable data state to wait for the feedback information of UE2.

[0241] S24, UE2 receives the synchronization source change notification information and feeds back to UE1.

[0242] S25, UE1 receives the positive feedback from UE2 and suspends or stops the DRX related timer.

[0243] In some practical ways, UE1 retransmits the synchronization source change notification information in the case where UE1 does not receive the positive feedback.

[0244] In some practical ways, the DRX related timer can include but is not limited to at least one of the following:

[0245] The sidelink DRX on duration timer (sl-drx-onDurationTimer), the sidelink DRX inactivity timer (sl-drx-InactivityTimer), the sidelink DRX retransmission timer (sl-drx-RetransmissionTimer), and the sidelink HARQ RTT timer (sl-HARQ-RTT-Timer).

[0246] S26, UE2 suspends or stops the DRX related timer when or after sending the positive feedback, or a period of time after sending the positive feedback.

[0247] S27, UE1 synchronizes to the new synchronization source.

[0248] S28, UE2 uses the Rx pool supporting the new synchronization source of UE1 for reception according to the indication of UE1 (i.e. the new synchronization source indicated in the synchronization source change notification information).

[0249] S29, UE1 and UE2 exchange synchronization confirmation information.

[0250] S30, UE1 continues the DRX related timer, or restarts the DRX related timer, or remains in the DRX active state for a period of time.

[0251] S31, UE2 continues the DRX related timer, or restarts the DRX related timer, or remains in the DRX active state for a period of time.

[0252] In embodiment 3, the receiving UE (i.e. UE2, corresponding to the first terminal described above) receives information based on the DRX configuration, or receives information on the resource pool synchronized with the synchronization source of the resource pool. The sending UE (i.e. UE1, corresponding to the second terminal described above) stops the DRX related timer during the switching of the synchronization source, and waits for the receiving UE to enter the DRX active state before sending information after the switching is completed. As shown in Figure 8 In embodiment 3, UE1 and UE2 perform the process described in S41 to S46 to synchronize the DRX.

[0253] S41, UE2 acquires the DRX configuration.

[0254] The DRX configuration is for the sidelink between UE1 and UE2.

[0255] The DRX configuration can be acquired in the following ways:

[0256] Pre-configuration or protocol agreement;

[0257] Configured by the network side through SIB or dedicated signaling;

[0258] Configured by UE1.

[0259] S42, UE2 performs the discontinuous reception operation according to the DRX configuration on the Rx pool where the data is received or the Rx pool with the same synchronization source as the Rx pool.

[0260] For example, for each receiving resource pool, UE2 determines the sidelink DRX on duration timer (sl-drx-onDurationTimer) according to the sidelink DRX cycle (sl-drx-Cycle), the sidelink DRX start offset (sl-drx-StartOffset), and the sidelink DRX slot offset (sl-drx-slotOffset).

[0261] For another example, for each receiving resource pool, UE2 starts or restarts the sidelink DRX inactivity timer (sl-drx-InactivityTimer) when receiving the new transmission PSCCH or PSSCH information, or after receiving the new transmission PSCCH or PSSCH information, or after a period of time after receiving the new transmission PSCCH or PSSCH information, or when sending the HARQ feedback, or after sending the HARQ feedback.

[0262] For another example, for each receiving resource pool, UE2 starts or restarts the sidelink DRX retransmission timer (sl-drx-RetransmissionTimer) after the HARQ RTT timer expires, or after the PSCCH or PSSCH decoding fails, or after receiving the SCI information.

[0263] S43, UE1 stops the DRX related timer.

[0264] In some practical ways, the DRX related timer can include but is not limited to at least one of the following:

[0265] Side-by-side DRX continuous timer (sl-drx-onDurationTimer), side-by-side DRX deactivation timer (sl-drx-InactivityTimer), side-by-side DRX retransmission timer (sl-drx-RetransmissionTimer), and side-by-side HARQ RTT timer (sl-HARQ-RTT-Timer).

[0266] S44, UE1 synchronizes to the new synchronization source.

[0267] S45, UE1 waits for UE2 to enter the DRX active state before sending information to UE2. This information may be:

[0268] Data information, such as PSSCH information;

[0269] Synchronization information, such as SLSS information;

[0270] Discovery information;

[0271] PC5-S information.

[0272] S46, UE2 receives information in the Rx pool where the information is received or in the same Rx pool as the synchronization source of the Rx pool, according to the DRX configuration.

[0273] The above text combined Figures 4 to 8 The method embodiments of this application are described in detail below, in conjunction with... Figures 9 to 13 The present application describes the device embodiments in detail. It should be understood that the device embodiments correspond to the method embodiments, and similar descriptions can be referred to the method embodiments.

[0274] Figure 9 A schematic block diagram of a terminal device 400 according to an embodiment of this application is shown. It is suitable for side-by-side transmission between a first terminal and a second terminal, wherein the terminal device 400 is the first terminal, such as... Figure 9 As shown, the terminal device 400 includes:

[0275] The communication unit 410 is configured to receive information on all receiving resource pools configured for the first terminal according to the discontinuous reception DRX configuration, or to receive information on the resource pool where information is received or on the receiving resource pool that has a synchronization source of the same type as the resource pool where information is received.

[0276] In some embodiments, the terminal device 400 further includes a processing unit 420, wherein,

[0277] If the first condition is met, the processing unit 420 is used to maintain the DRX-related timer; or, the processing unit 420 is used to pause or stop the DRX-related timer.

[0278] In some embodiments, the first condition comprises at least one of:

[0279] The first terminal receives information according to the DRX configuration on all receiving resource pools configured to the first terminal;

[0280] When the first terminal receives the first information;

[0281] After the first terminal receives the first information;

[0282] After the first terminal receives the first information for a first time duration;

[0283] After the first terminal receives the first information and sends the second information;

[0284] After the first terminal receives the first information and when sending the second information;

[0285] After the first terminal receives the first information and sends the second information for a second time duration;

[0286] The first information is used to indicate that the synchronization source is changed to a target type of synchronization source, and the second information comprises positive feedback for the first information.

[0287] In some embodiments, the first information at least comprises information of the target type of synchronization source.

[0288] In some embodiments, the processing unit 420 is further configured to receive information on one or more receiving resource pools supporting the target type of synchronization source according to the first information.

[0289] In some embodiments, the terminal device 400 further comprises a processing unit 420, wherein,

[0290] When the second condition is met, the processing unit 420 is configured to continue the DRX related timer previously paused or stopped, or the processing unit 420 is configured to restart the DRX related timer, or the processing unit 420 is configured to maintain the DRX active state within a target time duration.

[0291] In some embodiments, the second condition comprises at least one of:

[0292] The first terminal receives information on a resource pool receiving information or a receiving resource pool having the same type of synchronization source as the resource pool receiving information;

[0293] When the first terminal receives the third information;

[0294] After the first terminal receives the third information;

[0295] the first terminal receives the third information for a third time length;

[0296] the first terminal receives the third information and sends the fourth information;

[0297] the first terminal receives the third information and sends the fourth information;

[0298] the first terminal receives the third information and sends the fourth information for a fourth time length;

[0299] The third information is synchronization confirmation information, and the fourth information is synchronization confirmation response information.

[0300] In some embodiments, the first terminal is in a DRX active state,

[0301] The communication unit 410 is also configured to receive fifth information sent by the second terminal.

[0302] The communication unit 410 is also configured to receive information on a receiving resource pool of the fifth information or a receiving resource pool of a synchronization source of the same type as the receiving resource pool of the fifth information.

[0303] In some embodiments, the fifth information includes at least one of the following:

[0304] Data information, synchronization information, discovery information, PC5-S information.

[0305] In some embodiments, the first terminal receives information on all receiving resource pools configured to the first terminal according to the DRX configuration, and the terminal device 400 further includes a processing unit 420, wherein,

[0306] For each receiving resource pool, the processing unit 420 is configured to determine a first DRX timer according to a sidelink DRX cycle, a sidelink DRX start offset, and a sidelink DRX slot offset; and / or,

[0307] For each receiving resource pool, the processing unit 420 is configured to start or restart a second DRX timer when the first terminal receives new transmission physical sidelink control channel (PSCCH) or physical sidelink shared channel (PSSCH) information, or after the first terminal receives new transmission PSCCH or PSSCH information for a second time length, or when the first terminal sends hybrid automatic repeat request (HARQ) feedback, or after the first terminal sends HARQ feedback; and / or,

[0308] For each receiving resource pool, after a HARQ round trip transmission time RTT timer expires, or after PSCCH or PSSCH decoding fails, or after receiving sidelink control information SCI information or PSSCH information, the processing unit 420 is configured to start or restart a third DRX timer.

[0309] In some embodiments, the first terminal receives information on a resource pool on which information is received or a receiving resource pool having a same type of synchronization source as the resource pool on which information is received according to the DRX configuration, and the terminal device 400 further includes a processing unit 420, configured to:

[0310] For the resource pool on which information is received or the receiving resource pool having the same type of synchronization source as the resource pool on which information is received, the processing unit 420 is configured to determine a first DRX timer according to a sidelink DRX cycle, a sidelink DRX start offset, and a sidelink DRX slot offset; and / or,

[0311] For the resource pool on which information is received or the receiving resource pool having the same type of synchronization source as the resource pool on which information is received, the processing unit 420 is configured to start or restart a second DRX timer when the first terminal receives new transmission PSCCH or PSSCH information, or after the first terminal receives new transmission PSCCH or PSSCH information for a second time length, or when the first terminal sends HARQ feedback, or after the first terminal sends HARQ feedback; and / or,

[0312] For the resource pool on which information is received or the receiving resource pool having the same type of synchronization source as the resource pool on which information is received, the processing unit 420 is configured to start or restart a third DRX timer after a HARQ RTT timer expires, or after PSCCH or PSSCH decoding fails, or after receiving SCI information or PSSCH information.

[0313] In some embodiments, the DRX configuration is for a sidelink between the first terminal and the second terminal.

[0314] In some embodiments, the DRX configuration is preconfigured or agreed by a protocol, or the DRX configuration is configured by a network device, or the DRX configuration is configured by the second terminal.

[0315] In some embodiments, the communication unit can be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip. The processing unit can be one or more processors.

[0316] It should be understood that the terminal device 400 according to the embodiments of the present application can correspond to the first terminal in the method embodiments of the present application, and the above and other operations and / or functions of each unit in the terminal device 400 are respectively used to achieve the corresponding processes of the first terminal in the method 200 shown in FIG. 2. Figure 4 For brevity, the corresponding processes of the first terminal in the method 200 shown in FIG. 2 will not be repeated here.

[0317] Figure 10 A schematic block diagram of a terminal device 500 according to an embodiment of the present application is shown. The terminal device 500 is suitable for sidelink transmission between a first terminal and a second terminal, and the terminal device 500 is the second terminal, as shown in Figure 10 The terminal device 500 includes:

[0318] The processing unit 510 is configured to maintain a discontinuous reception (DRX) related timer, or pause or stop the DRX related timer, during a process in which a synchronization source of the second terminal is changed from a first synchronization source to a second synchronization source.

[0319] In some embodiments, the second terminal maintains the DRX related timer during the synchronization source change process,

[0320] The processing unit 510 is further configured to determine a DRX active time of the first terminal according to a synchronization compensation value between the second synchronization source and the first synchronization source and a DRX configuration.

[0321] In some embodiments, the unit of the synchronization compensation value includes one of the following:

[0322] Subframe, slot, symbol, millisecond.

[0323] In some embodiments, in the case that the second terminal changes from the first synchronization source to the second synchronization source during running of a first DRX timer, the processing unit 510 is further configured to determine a running time of the first DRX timer in a transmission resource pool for information transmission after the synchronization source change according to a sidelink DRX cycle, a sidelink DRX start offset, and a sidelink DRX slot offset; and / or,

[0324] In the case that the second terminal changes from the first synchronization source to the second synchronization source during running of a second DRX timer, the processing unit 510 is further configured to determine a running time of the second DRX timer in a transmission resource pool for information transmission after the synchronization source change according to a starting time and a running time length of the second DRX timer in the transmission resource pool for information transmission before the synchronization source change, and the synchronization compensation value.

[0325] In some embodiments, the first terminal is in a DRX active state, and the terminal device 500 further includes a communication unit 520, wherein,

[0326] The communication unit 520 is configured to transmit information on one or more transmission resource pools supporting the second synchronization source according to the DRX configuration.

[0327] In some embodiments, the processing unit 510 is specifically configured to:

[0328] pause or stop a DRX related timer in case the third condition is met.

[0329] In some embodiments, the third condition comprises at least one of:

[0330] when the second terminal transmits the first information;

[0331] after the second terminal transmits the first information;

[0332] after the second terminal transmits the first information for a fifth time length;

[0333] after the second terminal transmits the first information and receives the second information;

[0334] when the second terminal transmits the first information and receives the second information;

[0335] after the second terminal transmits the first information and receives the second information for a sixth time length;

[0336] wherein the first information is used to indicate that the synchronization source is changed to a target type of synchronization source, and the second information comprises a positive feedback for the first information.

[0337] In some embodiments, the first information at least comprises information of the target type of synchronization source.

[0338] In some embodiments, after transmitting the first information, the second terminal enters a DRX active state, or the second terminal enters a state in which data can be received.

[0339] In some embodiments, in case no positive feedback for the first information is received, the communication unit 520 is further configured to retransmit the first information.

[0340] In some embodiments, in case the fourth condition is met, the processing unit 510 is further configured to continue the previously paused or stopped DRX related timer, or the processing unit 510 is further configured to restart the DRX related timer, or the second terminal can transmit information to the first terminal within a target time length.

[0341] In some embodiments, the fourth condition comprises at least one of:

[0342] when the second terminal transmits the third information;

[0343] after the second terminal sends the third information for a seventh time length;

[0344] after the second terminal sends the third information for a seventh time length;

[0345] after the second terminal sends the third information and receives the fourth information;

[0346] when the second terminal sends the third information and receives the fourth information;

[0347] after the second terminal sends the third information and receives the fourth information for an eighth time length;

[0348] The third information is synchronization confirmation information, and the fourth information is synchronization confirmation response information.

[0349] In some embodiments, the second terminal suspends or stops a DRX related timer during a synchronization source change process, and the terminal device 500 further includes a communication unit 520, wherein,

[0350] After the synchronization source of the second terminal is changed from the first synchronization source to the second synchronization source, and the first terminal is in a DRX active state, the communication unit 520 is configured to send fifth information to the first terminal on one or more transmission resource pools supporting the second synchronization source according to a DRX configuration.

[0351] In some embodiments, the fifth information includes at least one of the following:

[0352] Data information, synchronization information, discovery information, PC5-S information.

[0353] In some embodiments, the DRX configuration is for a sidelink between the first terminal and the second terminal.

[0354] In some embodiments, the DRX configuration is preconfigured or agreed by a protocol, or the DRX configuration is configured by a network device, or the DRX configuration is configured by the first terminal.

[0355] In some embodiments, the above communication unit can be a communication interface or a transceiver, or a communication chip or an input / output interface of a system on chip. The above processing unit can be one or more processors.

[0356] It should be understood that the terminal device 500 according to the embodiments of the present application can correspond to the second terminal in the method embodiments of the present application, and the above and other operations and / or functions of each unit in the terminal device 500 are respectively used to realize the corresponding process of the second terminal in the method 300 shown in the method embodiments of the present application. For brevity, they will not be repeated here. Figure 5 The corresponding process of the second terminal in the method 300 shown is described above, and will not be repeated here.

[0357] Figure 11Fig. 6 is a schematic structural diagram of a communication device 600 according to an embodiment of the present application. Figure 11 The communication device 600 shown in Fig. 6 includes a processor 610, which can invoke and run a computer program from a memory to implement the method in the embodiments of the present application.

[0358] In some embodiments, as shown in Fig. 6, the communication device 600 can further include a memory 620. The processor 610 can invoke and run a computer program from the memory 620 to implement the method in the embodiments of the present application. Figure 11

[0359] The memory 620 can be a separate device independent of the processor 610, or can be integrated in the processor 610.

[0360] In some embodiments, as shown in Fig. 6, the communication device 600 can further include a transceiver 630, which can be controlled by the processor 610 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices. Figure 11

[0361] The transceiver 630 can include a transmitter and a receiver. The transceiver 630 can further include an antenna, and the number of antennas can be one or more.

[0362] In some embodiments, the communication device 600 can be specifically a terminal device of the embodiments of the present application, and the communication device 600 can implement the corresponding processes implemented by the first terminal in the various methods of the embodiments of the present application. For the sake of brevity, details are not repeated here.

[0363] In some embodiments, the communication device 600 can be specifically a terminal device of the embodiments of the present application, and the communication device 600 can implement the corresponding processes implemented by the second terminal in the various methods of the embodiments of the present application. For the sake of brevity, details are not repeated here.

[0364] Figure 12 Fig. 7 is a schematic structural diagram of an apparatus 700 according to an embodiment of the present application. Figure 12 The apparatus 700 shown in Fig. 7 includes a processor 710, which can invoke and run a computer program from a memory to implement the method in the embodiments of the present application.

[0365] In some embodiments, as shown in Fig. 7, the apparatus 700 can further include a memory 720. The processor 710 can invoke and run a computer program from the memory 720 to implement the method in the embodiments of the present application. Figure 12

[0366] ​​​The memory 720 can be a separate device independent of the processor 710, or can be integrated in the processor 710.

[0367] In some embodiments, the apparatus 700 can further include an input interface 730. The processor 710 can control the input interface 730 to communicate with other devices or chips, and specifically, can acquire information or data sent by other devices or chips.

[0368] In some embodiments, the apparatus 700 can further include an output interface 740. The processor 710 can control the output interface 740 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.

[0369] In some embodiments, the apparatus can be applied to the terminal device in the embodiments of the present application, and the apparatus can implement the corresponding procedures realized by the first terminal in the methods of the embodiments of the present application. For brevity, details are not described herein.

[0370] In some embodiments, the apparatus can be applied to the terminal device in the embodiments of the present application, and the apparatus can implement the corresponding procedures realized by the second terminal in the methods of the embodiments of the present application. For brevity, details are not described herein.

[0371] In some embodiments, the apparatus mentioned in the embodiments of the present application can also be a chip. For example, it can be a system chip, a system chip, a chip system, or a system on chip, etc.

[0372] Figure 13 is a schematic block diagram of a communication system 800 provided by the embodiments of the present application. As shown in the figure, the communication system 800 includes a first terminal 810 and a second terminal 820. Figure 13

[0373] The first terminal 810 can be used to implement the corresponding functions realized by the first terminal in the above methods, and the second terminal 820 can be used to implement the corresponding functions realized by the second terminal in the above methods. For brevity, details are not described herein.

[0374] ​It should be understood that the processor of the embodiments of the present application can be an integrated circuit chip with a processing capability of signals. In the implementation process, each step of the method embodiments described above can be completed by the integrated logic circuit of hardware in the processor or the instructions in the form of software. The processor described above can be a general processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The disclosed methods, steps and logic block diagrams in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor or the like. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly embodied as a hardware coding processor for execution, or a combination of hardware and software modules in the coding processor for execution. The software module can be located in a random access memory, a flash memory, a read only memory, a programmable read only memory or an electrically erasable programmable memory, a register or other mature storage medium in the art. The storage medium is located in the storage, and the processor reads the information in the storage, and combines the hardware to complete the steps of the above method.

[0375] It is to be understood that the memory in the embodiments of the present application can be a volatile memory or a nonvolatile memory, or can include both volatile and nonvolatile memory. Among them, the nonvolatile memory can be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically erasable programmable read-only memory (Electrically EPROM, EEPROM) or a flash memory. The volatile memory can be a random access memory (Random Access Memory, RAM) used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (Synchlink DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM). It should be noted that the memory of the system and method described herein is intended to include, but not limited to, these and any other suitable types of memory.

[0376] It should be understood that the above-mentioned memory is exemplary but not limiting, for example, the memory in the embodiments of the present application can also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and the like. That is, the memory in the embodiments of the present application is intended to include, but not limited to, these and any other suitable types of memory.

[0377] The embodiment of the present application further provides a computer readable storage medium for storing the computer program.

[0378] In some embodiments, the computer readable storage medium can be applied to the terminal device in the embodiment of the present application, and the computer program makes the computer execute the corresponding process realized by the first terminal in the various methods of the embodiment of the present application, which will not be repeated here for the sake of brevity.

[0379] In some embodiments, the computer readable storage medium can be applied to the terminal device in the embodiment of the present application, and the computer program makes the computer execute the corresponding process realized by the second terminal in the various methods of the embodiment of the present application, which will not be repeated here for the sake of brevity.

[0380] The embodiment of the present application further provides a computer program product comprising computer program instructions.

[0381] In some embodiments, the computer program product can be applied to the terminal device in the embodiment of the present application, and the computer program instructions make the computer execute the corresponding process realized by the first terminal in the various methods of the embodiment of the present application, which will not be repeated here for the sake of brevity.

[0382] In some embodiments, the computer program product can be applied to the terminal device in the embodiment of the present application, and the computer program instructions make the computer execute the corresponding process realized by the second terminal in the various methods of the embodiment of the present application, which will not be repeated here for the sake of brevity.

[0383] The embodiment of the present application further provides a computer program.

[0384] In some embodiments, the computer program can be applied to the terminal device in the embodiment of the present application, and when the computer program runs on the computer, makes the computer execute the corresponding process realized by the first terminal in the various methods of the embodiment of the present application, which will not be repeated here for the sake of brevity.

[0385] In some embodiments, the computer program can be applied to the terminal device in the embodiment of the present application, and when the computer program runs on the computer, makes the computer execute the corresponding process realized by the second terminal in the various methods of the embodiment of the present application, which will not be repeated here for the sake of brevity.

[0386] Those skilled in the art can clearly understand that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be realized by electronic hardware or a combination of computer software and electronic hardware. Whether the functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0387] Those skilled in the art can clearly understand that, for the convenience and brevity of the description, the specific working processes of the above-described system, device and unit can refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

[0388] In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the above-described device embodiments are only schematic, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interface, device or unit, and can be electrical, mechanical or other forms.

[0389] The units described as separate components can or can not be physically separated, and the components shown as units can or can not be physical units, that is, they can be located in one place, or can be distributed on a plurality of network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment.

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

[0391] If the functions are implemented in the form of software function units and sold or used as independent products, they can be stored in a computer readable storage medium. For such understanding, the technical solutions of the present application or the parts of the technical solutions that essentially contribute to the prior art or the parts of the technical solutions can be embodied in the form of software products. The computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in the embodiments of the present application. The aforementioned storage medium includes a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various media that can store program codes.

[0392] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A method of wireless communication, comprising: The method is suitable for sidelink transmission between a first terminal and a second terminal, and the method comprises the following steps: The first terminal receives information according to a discontinuous reception (DRX) configuration on a resource pool on which the information is received or a receiving resource pool having a same type of synchronization source as the resource pool on which the information is received; In a case where a first condition is met, the first terminal suspends or stops a DRX-related timer, wherein the first condition comprises that, after the first terminal receives first information, the first information is used to indicate that a synchronization source is changed to a target type of synchronization source; In a case where a second condition is met, the first terminal continues the previously suspended or stopped DRX-related timer, or the first terminal restarts the DRX-related timer, or the first terminal maintains a DRX active state for a target time length, wherein the second condition comprises that, after the first terminal receives third information, the third information is synchronization confirmation information; The first terminal receives information on one or more receiving resource pools supporting the target type of synchronization source according to the first information.

2. The method of claim 1, wherein, The first condition further comprises at least one of the following: When the first terminal receives the first information; After the first terminal receives the first information for a first time length; After the first terminal receives the first information and sends second information; When the first terminal receives the first information and sends the second information; After the first terminal receives the first information and sends the second information for a second time length; The second information comprises positive feedback for the first information.

3. The method of claim 1, wherein, The first information at least comprises information of the target type of synchronization source.

4. The method of claim 1, wherein, The second condition further comprises at least one of the following: When the first terminal receives the third information; After the first terminal receives the third information for a third time length; After the first terminal receives the third information and sends fourth information; When the first terminal receives the third information and sends the fourth information; After the first terminal receives the third information and sends the fourth information for a fourth time length; The fourth information is synchronization confirmation response information.

5. The method of claim 1, wherein, The first terminal is in a DRX active state, and the method further comprises the following steps: The first terminal receives fifth information sent by the second terminal; The first terminal receives information on a receiving resource pool on which the fifth information is received or a receiving resource pool having a same type of synchronization source as the receiving resource pool on which the fifth information is received.

6. The method of claim 5, wherein, The fifth information comprises at least one of the following: Data information, synchronization information, discovery information, and PC5-S information.

7. The method of any one of claims 1 to 6, wherein, The method further comprises the following steps: For a resource pool on which information is received or a receiving resource pool having a same type of synchronization source as the resource pool on which information is received, the first terminal determines a first DRX timer according to a sidelink DRX cycle, a sidelink DRX start offset, and a sidelink DRX time slot offset; and / or, For a resource pool receiving the information or a receiving resource pool having a same type of synchronization source as the resource pool receiving the information, the first terminal starts or restarts a second DRX timer when the first terminal receives new transmission PSCCH or PSSCH information, or after the first terminal receives new transmission PSCCH or PSSCH information for a second time length, or when the first terminal transmits HARQ feedback, or after the first terminal transmits HARQ feedback; and / or, For a resource pool receiving the information or a receiving resource pool having a same type of synchronization source as the resource pool receiving the information, the first terminal starts or restarts a third DRX timer after a HARQ RTT timer expires, or after PSCCH or PSSCH decoding fails, or after receiving SCI information or PSSCH information.

8. The method of any one of claims 1 to 6, wherein, The DRX configuration is for sidelink between the first terminal and the second terminal.

9. The method of any one of claims 1 to 6, wherein, The DRX configuration is preconfigured or agreed by a protocol, or the DRX configuration is configured by a network device, or the DRX configuration is configured by the second terminal.

10. A method of wireless communication, comprising: The method is suitable for sidelink transmission between a first terminal and a second terminal, and the method comprises: In a process in which a synchronization source of the second terminal is changed from a first synchronization source to a second synchronization source, the second terminal suspends or stops a DRX related timer in a case where a third condition is met, wherein the third condition comprises that the second terminal transmits first information after the first information is used to indicate that the synchronization source is changed to a target type of synchronization source; In a case where a fourth condition is met, the second terminal continues the previously suspended or stopped DRX related timer, or the second terminal restarts the DRX related timer, or the second terminal can transmit information to the first terminal within a target time length, wherein the fourth condition comprises that the second terminal transmits third information after the third information is synchronization confirmation information.

11. The method of claim 10, wherein, The third condition further comprises at least one of the following: When the second terminal transmits the first information; After the second terminal transmits the first information for a fifth time length; After the second terminal transmits the first information and receives second information; When the second terminal transmits the first information and receives the second information; After the second terminal transmits the first information and receives the second information for a sixth time length; The second information comprises positive feedback for the first information.

12. The method of claim 10, wherein, The first information at least comprises information of the target type of synchronization source.

13. The method according to any one of claims 10 to 12, characterized in that, The method further comprises: After transmitting the first information, the second terminal enters a DRX active state, or the second terminal enters a state in which data can be received.

14. The method of any one of claims 10 to 12, wherein, The method further comprises: In a case where positive feedback for the first information is not received, the second terminal retransmits the first information.

15. The method according to any one of claims 10 to 12, wherein, The fourth condition further comprises at least one of the following: When the second terminal transmits the third information; After the second terminal transmits the third information for a seventh time length; After the second terminal transmits the third information and receives fourth information; The second terminal sends third information and receives fourth information; The second terminal sends third information and receives fourth information after an eighth time length; The fourth information is a synchronization confirmation response information.

16. The method of any one of claims 10 to 12, wherein, The method further comprises: After a synchronization source of the second terminal is changed from the first synchronization source to the second synchronization source, and the first terminal is in a DRX active state, the second terminal sends fifth information to the first terminal according to a DRX configuration on one or more sending resource pools supporting the second synchronization source.

17. The method of claim 16, wherein, The fifth information comprises at least one of: Data information, synchronization information, discovery information, and PC5-S information.

18. The method of claim 16, wherein, The DRX configuration is for a sidelink between the first terminal and the second terminal.

19. The method of claim 16, wherein, The DRX configuration is preconfigured or agreed by a protocol, or the DRX configuration is configured by a network device, or the DRX configuration is configured by the first terminal.

20. A terminal device, comprising: The terminal device is suitable for sidelink transmission between a first terminal and a second terminal, and the terminal device comprises: A communication unit configured to receive information according to a discontinuous reception (DRX) configuration on a resource pool on which the information is received or a receiving resource pool having a same type of synchronization source as the resource pool on which the information is received; A processing unit configured to pause or stop a DRX-related timer if a first condition is met, wherein the first condition comprises that the first terminal receives first information after the first information is received, and the first information is used to indicate that a synchronization source is changed to a target type of synchronization source. The processing unit is further configured to continue the previously paused or stopped DRX-related timer if a second condition is met, or the processing unit is configured to restart the DRX-related timer, or the processing unit is configured to maintain a DRX active state for a target time length, wherein the second condition comprises that the first terminal receives third information after the third information is received, and the third information is synchronization confirmation information. The communication unit is further configured to receive information on one or more receiving resource pools supporting the target type of synchronization source according to the first information.

21. The terminal device according to claim 20, characterized by The first condition further comprises at least one of: The first terminal receives the first information; The first terminal receives the first information after a first time length; The first terminal receives the first information and sends second information after; The first terminal receives the first information and sends the second information; The first terminal receives the first information and sends the second information after a second time length; The second information comprises positive feedback for the first information.

22. The terminal device of claim 20, wherein, The first information at least comprises information of the target type of synchronization source.

23. The terminal device of claim 20, wherein, The second condition further comprises at least one of: The first terminal receives the third information; The first terminal receives the third information after a third time length; The first terminal receives the third information and sends fourth information after; The first terminal receives the third information and sends the fourth information; The first terminal receives the third information and sends the fourth information after a fourth time length; The fourth information is a synchronization confirmation response information.

24. The terminal device of claim 20, wherein, The first terminal is in a DRX active state, The communication unit is further configured to receive fifth information sent by the second terminal. The communication unit is further configured to receive information on a receiving resource pool of the fifth information or a receiving resource pool of a same type of synchronization source as the receiving resource pool of the fifth information.

25. The terminal device according to claim 24, characterized by The fifth information includes at least one of the following: Data information, synchronization information, discovery information, and PC5-S information.

26. The terminal device of any one of claims 20 to 25, wherein, For a resource pool on which information is received or a receiving resource pool of a same type of synchronization source as the resource pool on which information is received, the processing unit is configured to determine a first DRX timer according to a sidelink DRX period, a sidelink DRX start offset, and a sidelink DRX slot offset; and / or, For a resource pool on which information is received or a receiving resource pool of a same type of synchronization source as the resource pool on which information is received, the processing unit is configured to start or restart a second DRX timer when the first terminal receives new transmission PSCCH or PSSCH information, or after the first terminal receives new transmission PSCCH or PSSCH information for a second time length, or when the first terminal sends HARQ feedback, or after the first terminal sends HARQ feedback; and / or, For a resource pool on which information is received or a receiving resource pool of a same type of synchronization source as the resource pool on which information is received, the processing unit is configured to start or restart a third DRX timer after a HARQ RTT timer expires, or after PSCCH or PSSCH decoding fails, or after receiving SCI information or PSSCH information.

27. The terminal device of any one of claims 20 to 25, wherein, The DRX configuration is for a sidelink between the first terminal and the second terminal.

28. The terminal device of any one of claims 20 to 25, wherein, The DRX configuration is preconfigured or agreed upon by a protocol, or the DRX configuration is configured by a network device, or the DRX configuration is configured by the second terminal.

29. A terminal device, comprising: The terminal device is suitable for sidelink transmission between a first terminal and a second terminal, the terminal device is the second terminal, and the terminal device includes: A processing unit configured to, during a process in which a synchronization source of the second terminal is changed from a first synchronization source to a second synchronization source, pause or stop a DRX related timer if a third condition is met. The processing unit is further configured to continue the previously paused or stopped DRX related timer if a fourth condition is met, or the processing unit is further configured to restart the DRX related timer, or the second terminal can send information to the first terminal within a target time length, wherein the fourth condition includes after the second terminal sends third information.

30. The terminal device of claim 29, wherein, The third condition further includes at least one of the following: When the second terminal sends first information; After the second terminal sends first information for a fifth time length; After the second terminal sends first information and receives second information; When the second terminal sends first information and receives second information; the second terminal sends the first information and receives the second information after a sixth time length; wherein the second information comprises positive feedback for the first information.

31. The terminal device of claim 29, wherein, The first information at least comprises information of the target type of synchronization source.

32. The terminal device of any of claims 29 to 31, wherein, after sending the first information, the second terminal enters a DRX active state, or the second terminal enters a state in which data can be received.

33. The terminal device of any one of claims 29 to 31, wherein, The terminal device further comprises a communication unit; in a case where no positive feedback for the first information is received, the communication unit is configured to resend the first information.

34. The terminal device of any one of claims 29 to 31, wherein, The fourth condition further comprises at least one of: when the second terminal sends the third information; after the second terminal sends the third information for a seventh time length; after the second terminal sends the third information and receives the fourth information; when the second terminal sends the third information and receives the fourth information; after the second terminal sends the third information and receives the fourth information for an eighth time length; wherein the fourth information is synchronization confirmation response information.

35. The terminal device of any one of claims 29 to 31, wherein, The terminal device further comprises a communication unit, wherein, after a synchronization source of the second terminal is changed from the first synchronization source to the second synchronization source, and the first terminal is in a DRX active state, the communication unit is configured to send fifth information to the first terminal on one or more transmission resource pools supporting the second synchronization source according to a DRX configuration.

36. The terminal device of claim 35, wherein, The fifth information comprises at least one of: data information, synchronization information, discovery information, PC5-S information.

37. The terminal device according to claim 35 or 36, characterized by The DRX configuration is for a sidelink between the first terminal and the second terminal.

38. The terminal device according to claim 35 or 36, characterized by The DRX configuration is preconfigured or agreed by a protocol, or the DRX configuration is configured by a network device, or the DRX configuration is configured by the first terminal.

39. A terminal device, comprising: comprises: a processor and a memory for storing a computer program, the processor being configured to invoke and run the computer program stored in the memory to perform the method of any of claims 1 to 9, or to perform the method of any of claims 10 to 19.

40. A chip, comprising: comprises: a processor configured to invoke and run a computer program from a memory, so that a device in which the chip is installed performs the method of any of claims 1 to 9, or performs the method of any of claims 10 to 19.

41. A computer-readable storage medium, comprising: a computer program for storing, the computer program causing a computer to perform the method of any of claims 1 to 9, or to perform the method of any of claims 10 to 19.

42. A computer program product, characterised in that, comprises computer program instructions that cause a computer to perform the method of any of claims 1 to 9, or to perform the method of any of claims 10 to 19.

Images