WO2021032194A1 - Sidelink的drx配置方法和设备 - Google Patents

Sidelink的drx配置方法和设备 Download PDF

Info

Publication number
WO2021032194A1
WO2021032194A1 PCT/CN2020/110529 CN2020110529W WO2021032194A1 WO 2021032194 A1 WO2021032194 A1 WO 2021032194A1 CN 2020110529 W CN2020110529 W CN 2020110529W WO 2021032194 A1 WO2021032194 A1 WO 2021032194A1
Authority
WO
WIPO (PCT)
Prior art keywords
drx
terminal device
configuration
information
configuration information
Prior art date
Application number
PCT/CN2020/110529
Other languages
English (en)
French (fr)
Inventor
杨晓东
郑倩
鲍炜
Original Assignee
维沃移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 维沃移动通信有限公司 filed Critical 维沃移动通信有限公司
Priority to JP2022512296A priority Critical patent/JP7498263B2/ja
Priority to EP20855559.9A priority patent/EP4021140A4/en
Priority to KR1020227007278A priority patent/KR20220045184A/ko
Priority to BR112022003122A priority patent/BR112022003122A2/pt
Publication of WO2021032194A1 publication Critical patent/WO2021032194A1/zh
Priority to US17/676,590 priority patent/US20220174781A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
    • H04W52/0216—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave using a pre-established activity schedule, e.g. traffic indication frame
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
    • H04W52/0219—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave where the power saving management affects multiple terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0229—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0261—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level
    • H04W52/0274—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level by switching on or off the equipment or parts thereof
    • H04W52/028—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level by switching on or off the equipment or parts thereof switching on or off only a part of the equipment circuit blocks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/18—Interfaces between hierarchically similar devices between terminal devices
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the embodiments of the present application relate to the field of communications, and in particular to a discontinuous reception (DRX) configuration method and device for a sidelink (sidelink, or translated as a side link, side link, etc.).
  • DRX discontinuous reception
  • Both the Long Term Evolution (LTE) system and the New Radio (NR) system support sidelink transmission, which means that terminal devices can directly transmit data over the wireless air interface.
  • LTE Long Term Evolution
  • NR New Radio
  • the LTE system and the NR system also introduce the DRX mechanism on the Uu port, and realize the energy saving of terminal equipment through the configured DRX on and off time.
  • the purpose of the embodiments of this application is to provide a sidelink DRX configuration method and device to implement DRX configuration of a terminal device in the sidelink.
  • a DRX configuration method for sidelink including:
  • the terminal device determines the configuration information of DRX
  • a DRX configuration method for sidelink is provided.
  • the method is executed by a network device and includes:
  • a terminal device in a third aspect, includes:
  • the determining module is used to determine the configuration information of DRX
  • the configuration module is used to perform DRX configuration according to the configuration information.
  • a network device in a fourth aspect, includes:
  • the sending module is used to send DRX configuration information to the terminal device; wherein the configuration information is used for the terminal device to perform DRX configuration.
  • a terminal device in a fifth aspect, includes a processor, a memory, and a computer program stored on the memory and running on the processor. When the computer program is executed by the processor, The steps of implementing the DRX configuration method of sidelink as described in the first aspect.
  • a network device in a sixth aspect, includes a processor, a memory, and a computer program stored on the memory and running on the processor. When the computer program is executed by the processor, The steps of implementing the DRX configuration method of sidelink as described in the second aspect.
  • a computer-readable storage medium is provided, and a computer program is stored on the computer-readable storage medium.
  • the computer program is executed by a processor, the DRX of the sidelink described in the first and second aspects is realized. The steps of the configuration method.
  • the terminal device can determine DRX configuration information, and perform DRX configuration according to the determined configuration information, so as to save the power of the terminal device in the sidelink system.
  • Fig. 1 is a schematic flowchart of a sidelink DRX configuration method according to an embodiment of the present application
  • Fig. 2 is a schematic diagram of sidelink transmission according to an embodiment of the present application.
  • FIG. 3 is a schematic diagram of the active period and the dormant period of UE1 and UE2 in the embodiment shown in FIG. 2;
  • 4 to 6 are schematic flowcharts of sidelink DRX configuration methods according to three specific embodiments of the present application.
  • FIG. 7 is a schematic flowchart of a DRX configuration method of sidelink according to another embodiment of the present application.
  • Fig. 8 is a schematic structural diagram of a terminal device according to an embodiment of the present application.
  • Fig. 9 is a schematic structural diagram of a network device according to an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a terminal device according to another embodiment of the present application.
  • Fig. 11 is a schematic structural diagram of a network device according to another embodiment of the present application.
  • terminal equipment may include, but is not limited to, a mobile station (Mobile Station, MS), mobile terminal (Mobile Terminal), mobile phone (Mobile Telephone), User Equipment (UE), and mobile phone (handset) And portable equipment (portable equipment), vehicles (vehicle), etc.
  • the terminal equipment can communicate with one or more core networks via a radio access network (Radio Access Network, RAN), for example, the terminal equipment can be a mobile phone (or It is called a "cellular" phone), a computer with wireless communication function, etc.
  • the terminal device can also be a portable, pocket-sized, handheld, built-in computer or vehicle-mounted mobile device.
  • a network device is a device deployed in a wireless access network to provide wireless communication functions for terminal devices.
  • the network device may be a base station, and the base station may include various forms of macro base stations, micro base stations, relay stations, and access points.
  • the names of devices with base station functions may be different.
  • an LTE network it is called an evolved NodeB (evolved NodeB, eNB, or eNodeB)
  • eNB evolved NodeB
  • 3G Third Generation
  • Node B Node B
  • Network equipment, etc. the wording does not constitute a restriction.
  • an embodiment of the present application provides a sidelink DRX configuration method 100.
  • the method may be executed by a terminal device and includes the following steps:
  • the terminal device provided in each embodiment of this specification can be a sending device that sends sidelink data or a receiving device that receives sidelink data.
  • the two can be a terminal device, because a terminal device can not only send sidelink data
  • the step of receiving sidelink data can also be performed.
  • a terminal device that performs sidelink communication with a terminal device is referred to as a peer device.
  • the terminal device may receive configuration information sent by the peer device.
  • the opposite terminal device can perform DRX configuration for the local terminal device.
  • the terminal device and the peer device may pre-appoint configuration information, for example, pre-appoint DRX transmission related parameters, such as pre-appointed DRX cycle and offset, DRX activation period duration, DRX The duration of the dormant period, etc.
  • pre-appoint DRX transmission related parameters such as pre-appointed DRX cycle and offset, DRX activation period duration, DRX The duration of the dormant period, etc.
  • the terminal device before performing DRX transmission with the opposite terminal device, the terminal device can determine the configuration information to perform DRX configuration according to the pre-agreed configuration information.
  • the network device may perform DRX configuration on the terminal device and the peer device, and in this step, the terminal device may receive configuration information sent by the network device.
  • this step can perform at least one of the following configurations on the terminal device:
  • Hybrid Automatic Repeat request Hybrid Automatic Repeat request, HARQ
  • RTT Red-Trip Time
  • the terminal device can determine DRX configuration information, and perform DRX configuration according to the determined configuration information, so as to save the power of the terminal device in the sidelink system.
  • UE1 can send sidelink data to UE2, UE1 can send sidelink data to UE3, UE1 can send sidelink data to UE4, and UE2 can send sidelink data to UE3.
  • a UE cannot receive and send sidelink data at the same time. Therefore, when UE2 sends sidelink data to UE3, UE2 does not expect to receive sidelink data from UE1.
  • the active period and the dormant period of the UE1 and the UE2 are shown in FIG. 3.
  • the protruding part in the vertical direction in Figure 3 represents the active/monitoring state
  • the low-flat part in the vertical direction represents the dormant state
  • the horizontal direction is the time axis.
  • the activation period of the two can be made the same, which is convenient for sidelink data transmission. transmission.
  • the time domain positions occupied by the active period and the dormant period of UE1 and UE2 may be exactly the same, that is, the time domain positions occupied by the active period of UE1 and UE2 are the same, and UE1 The time domain position occupied by the sleep period of UE2 is also the same.
  • the peer device can perform DRX configuration on the local terminal device.
  • the following step may be included before the implementation of embodiment 100: the terminal device sends DRX auxiliary information or a DRX configuration request to the peer device .
  • the terminal device sends DRX auxiliary information or a DRX configuration request to the network device.
  • S102 in the foregoing embodiment may specifically be that the terminal device receives DRX configuration information.
  • the configuration information can be from the peer device or from the network device.
  • UE2 sends DRX assistance information or DRX configuration request to UE1.
  • the terminal device can send DRX auxiliary information, which can be used by the peer device to perform DRX configuration on the terminal device according to the DRX auxiliary information.
  • the peer device can also ignore the auxiliary information directly to the terminal. The device performs DRX configuration.
  • the terminal device can send DRX auxiliary information, so that the peer device can fully consider the sidelink transmission situation of the terminal device when configuring DRX for the terminal device, and perform DRX configuration for the terminal device in combination with its own sidelink transmission situation , To a certain extent, it is equivalent to the terminal device and the peer device negotiate the optimal DRX configuration, in order to maximize the effect of saving the power of the terminal device and the peer device.
  • the terminal device may send a DRX configuration request, and the DRX configuration request is used to request the peer device to perform DRX configuration on the terminal device.
  • the peer device can directly perform DRX configuration for the terminal device.
  • the terminal device can send the DRX auxiliary information and the DRX configuration request at the same time.
  • the DRX auxiliary information DRX configuration request please refer to the above introduction.
  • the terminal device mentioned in each of the foregoing embodiments is a sidelink data receiving device, and the opposite device is a sidelink data sending device; or, the terminal device mentioned in each of the foregoing embodiments is a sidelink data sending device, and the opposite device is It is the receiving device of sidelink data; of course, the terminal device mentioned in the above embodiments can not only send sidelink data to the opposite device, but also receive sidelink data sent by the opposite device. Accordingly, the opposite device can not only receive the terminal The sidelink data sent by the device can also send sidelink data to the terminal device.
  • the terminal device and the peer device mentioned in each embodiment of this specification are all from the direction of the local terminal device. It can be understood that, as far as the peer device is concerned, it can be called a local terminal device, and the terminal device described above can be called a peer device.
  • the terminal device may also send DRX feedback information to the peer device; wherein the DRX feedback information may be used to indicate the configuration of DRX, for example, indicating that the DRX configuration is successful, or Indicates DRX configuration failure, etc.
  • the DRX auxiliary information mentioned in each of the foregoing embodiments includes at least one of the following:
  • the length of the DRX continuous monitoring timer desired by the terminal device is the length of the DRX continuous monitoring timer desired by the terminal device
  • the length of the DRX inactivation timer desired by the terminal device is the length of the DRX inactivation timer desired by the terminal device
  • the length of the HARQ RTT timer desired by the terminal device is the length of the HARQ RTT timer desired by the terminal device
  • the time domain unit that the terminal device does not want DRX to activate can be a subframe, a time slot, etc.;
  • the time domain unit that the terminal device wants DRX to activate is the time domain unit that the terminal device wants DRX to activate.
  • the network device can perform DRX configuration for the terminal device and the peer device.
  • S102 of this embodiment may specifically be that the terminal device receives the DRX configuration information sent by the network device.
  • the configuration information Is determined by the network device.
  • the peer device can also receive the configuration information sent by the network device and perform DRX configuration.
  • both the terminal device and the peer device maintain an RRC connection with the network device.
  • the terminal device may also receive indication information; where the indication information is used to indicate the opposite device to which the configuration information is directed, for example, indicating the identification information of the opposite device.
  • the terminal device after the terminal device performs DRX configuration according to the configuration information, it can also send DRX feedback information to the network device.
  • the DRX feedback information can be used to indicate the configuration of DRX, for example, indicating that the DRX configuration is successful, or indicating that the DRX configuration has failed, etc. .
  • the network device can configure the sending DRX mode for the terminal device, and notify the terminal device of the peer device for which the DRX mode is sent; and configure the receiving DRX mode for the peer device, and notify the peer device to receive DRX The terminal device targeted by the mode.
  • the above is only the case where the terminal device is the sending device and the opposite device is the receiving device.
  • the network device can also be the terminal device and the opposite device. The device configures the corresponding configuration receiving/sending DRX mode.
  • This embodiment is particularly suitable for scenarios where the resource allocation mode of the terminal device is the network device scheduling mode (Mode 1). Because the network device allocates resources to a pair of terminal devices for sidelink data transmission, it is easier to determine the The time domain position of the sidelink data transmission, so that when the terminal device is configured for DRX, the time period when the terminal device does not transmit sidelink data is configured as a dormant period as much as possible, which can save the power of the terminal device to the greatest extent.
  • the resource allocation mode of the terminal device is the network device scheduling mode (Mode 1). Because the network device allocates resources to a pair of terminal devices for sidelink data transmission, it is easier to determine the The time domain position of the sidelink data transmission, so that when the terminal device is configured for DRX, the time period when the terminal device does not transmit sidelink data is configured as a dormant period as much as possible, which can save the power of the terminal device to the greatest extent.
  • this embodiment can be executed by a sidelink receiving device (hereinafter referred to as receiving device), and includes the following steps:
  • the receiving device can specifically send auxiliary information to the sidelink sending device (hereinafter referred to as the sending device), the sending device performs DRX configuration on the receiving device, and the sending device can combine the auxiliary information to perform DRX configuration on the receiving device, or the auxiliary information can be ignored , DRX configuration on the receiving device.
  • the sending device can specifically send auxiliary information to the sidelink sending device (hereinafter referred to as the sending device), the sending device performs DRX configuration on the receiving device, and the sending device can combine the auxiliary information to perform DRX configuration on the receiving device, or the auxiliary information can be ignored , DRX configuration on the receiving device.
  • the auxiliary information includes at least one of the following:
  • the length of the DRX continuous monitoring timer desired by the receiving device is the length of the DRX continuous monitoring timer desired by the receiving device
  • the length of the DRX inactivation timer desired by the receiving device is the length of the DRX inactivation timer desired by the receiving device.
  • the length of the HARQ RTT timer desired by the receiving device is the length of the HARQ RTT timer desired by the receiving device.
  • the length of the retransmission timer desired by the receiving device is the length of the retransmission timer desired by the receiving device
  • the time domain unit that the receiving device does not want DRX to activate can be a subframe, a time slot, etc.;
  • the time domain unit that the receiving device wants DRX to activate is the time domain unit that the receiving device wants DRX to activate.
  • the receiving device After receiving the configuration information, the receiving device can perform DRX configuration according to the configuration information.
  • the configuration information For the specific configuration process, refer to the introduction of the foregoing embodiment.
  • S406 Send DRX feedback information.
  • the DRX feedback information may be used to indicate the configuration of DRX, for example, indicating that the DRX configuration is successful, or indicating that the DRX configuration fails.
  • step S402 and step S406 may be omitted, that is, the sending device directly performs DRX configuration on the receiving device.
  • this embodiment can be executed by a sidelink sending device (hereinafter referred to as sending device), and includes the following steps:
  • the sending device can specifically send auxiliary information to the sidelink receiving device (hereinafter referred to as the receiving device), the receiving device performs DRX configuration on the sending device, and the receiving device can combine the auxiliary information to perform DRX configuration on the sending device, or the auxiliary information can be ignored , DRX configuration of the sending device.
  • the receiving device can specifically send auxiliary information to the sidelink receiving device (hereinafter referred to as the receiving device), the receiving device performs DRX configuration on the sending device, and the receiving device can combine the auxiliary information to perform DRX configuration on the sending device, or the auxiliary information can be ignored , DRX configuration of the sending device.
  • the auxiliary information includes at least one of the following:
  • the length of the HARQ RTT timer desired by the sending device is the length of the HARQ RTT timer desired by the sending device.
  • the time domain unit that the sending device does not want DRX to activate can be a subframe, a time slot, etc.;
  • the time domain unit that the sending device wants DRX to activate is the time domain unit that the sending device wants DRX to activate.
  • the sending device After receiving the configuration information, the sending device can perform DRX configuration according to the configuration information.
  • the specific configuration process refer to the introduction of the foregoing embodiment.
  • S506 Send DRX feedback information.
  • the DRX feedback information may be used to indicate the configuration of DRX, for example, indicating that the DRX configuration is successful, or indicating that the DRX configuration fails.
  • step S502 and step S506 may be omitted, that is, the receiving device directly performs DRX configuration on the sending device.
  • the network device in this embodiment can perform DRX configuration for the sidelink sending device (hereinafter referred to as the sending device) and the sidelink receiving device (hereinafter referred to as the receiving device), and the sending device and the receiving device can receive the configuration information sent by the network device. .
  • both the sending device and the receiving device maintain an RRC connection with the network device.
  • the sending device may also receive indication information; where the indication information is used to indicate the receiving device, for example, indicating the identification information of the receiving device.
  • the receiving device may also receive indication information; where the indication information is used to indicate the sending device, for example, indicating the identification information of the sending device.
  • the DRX configuration method of the sidelink according to the embodiment of the present application is described in detail above with reference to FIGS. 1 to 6.
  • the DRX configuration method of sidelink according to another embodiment of the present application will be described in detail below with reference to FIG. 7. It can be understood that the interaction between the network device and the terminal device described from the network device side is the same as the description on the terminal device side in the method shown in FIG. 1, and to avoid repetition, the related description is appropriately omitted.
  • FIG. 7 is a schematic diagram of the implementation process of the sidelink DRX configuration method according to an embodiment of the present application, which can be applied to the network device side. As shown in FIG. 7, the method 700 includes:
  • S702 Send DRX configuration information to the terminal device, where the configuration information is used for the terminal device to perform DRX configuration.
  • the terminal device can receive DRX configuration information, and perform DRX configuration according to the configuration information, so as to save the power of the terminal device in the sidelink system.
  • the method further includes:
  • the configuration information is sent to a peer device targeted by the configuration information, and the configuration information is also used for the peer device to perform DRX configuration.
  • the method further includes:
  • the indication information is used to indicate the terminal device.
  • the DRX configuration method of the sidelink according to the embodiment of the present application is described in detail above with reference to FIGS. 1 to 7.
  • the terminal device according to the embodiment of the present application will be described in detail below with reference to FIG. 8.
  • Fig. 8 is a schematic structural diagram of a terminal device according to an embodiment of the present application. As shown in FIG. 8, the terminal device 800 includes:
  • the determining module 802 may be used to determine DRX configuration information; the configuration module 804 may be used to perform DRX configuration according to the configuration information.
  • the terminal device provided in the embodiment of the present application can determine DRX configuration information, and perform DRX configuration according to the determined configuration information, so as to save power of the terminal device in the sidelink system.
  • the determining module 802 may be used to receive DRX configuration information sent by a peer device; wherein the configuration information is determined by the peer device.
  • the terminal device is a sidelink receiving device and the opposite device is a sidelink sending device; or, the terminal device is a sidelink sending device, and the opposite device is a sidelink receiving device.
  • the determining module 802 may be configured to send DRX feedback information to the peer device; wherein, the DRX feedback information indicates that the DRX configuration is successful or indicates that the DRX configuration fails.
  • the determining module 802 may be used to send DRX auxiliary information or a DRX configuration request to a peer device; or, send DRX auxiliary information or a DRX configuration request to a network device.
  • the DRX auxiliary information includes at least one of the following:
  • the time domain unit that the terminal device does not want DRX to activate
  • the time domain unit that the terminal device wants DRX to activate is the time domain unit that the terminal device wants DRX to activate.
  • the configuration information is agreed in advance by the terminal device and the peer device.
  • the determining module 802 may be used to receive configuration information sent by a network device; where the configuration information is determined by the network device.
  • the determining module 802 may be used to receive indication information
  • the indication information is used to indicate the peer device targeted by the configuration information; the network device is also used to perform DRX configuration for the peer device.
  • the determining module 802 may be configured to send DRX feedback information to the network device; wherein, the DRX feedback information indicates that the DRX configuration is successful or indicates that the DRX configuration fails.
  • the terminal device 800 can refer to the process of the method 100 corresponding to the embodiment of the present application, and each unit/module in the terminal device 800 and the other operations and/or functions mentioned above are used to implement the corresponding methods in the method 100.
  • Fig. 9 is a schematic structural diagram of a network device according to an embodiment of the present application. As shown in FIG. 9, the network device 900 includes:
  • the sending module 902 may be used to send DRX configuration information to the terminal device; wherein the configuration information is used for the terminal device to perform DRX configuration.
  • the terminal device can receive DRX configuration information, and perform DRX configuration according to the configuration information, so as to save the power of the terminal device in the sidelink system.
  • the sending module 902 is further configured to send the configuration information to a peer device targeted by the configuration information, where the configuration information is used for the peer device to perform DRX configuration.
  • the sending module 902 is further configured to: send first indication information to the terminal device; wherein the first indication information is used to indicate the opposite terminal device; and/or, Sending second indication information to the opposite terminal device; wherein the second indication information is used to indicate the terminal device.
  • the terminal device 900 can refer to the process of the method 700 corresponding to the embodiment of the present application, and each unit/module in the terminal device 900 and the other operations and/or functions described above are used to implement the corresponding methods in the method 700.
  • Fig. 10 is a block diagram of a terminal device according to another embodiment of the present application.
  • the terminal device 1000 shown in FIG. 10 includes: at least one processor 1001, a memory 1002, at least one network interface 1004, and a user interface 1003.
  • the various components in the terminal device 1000 are coupled together through the bus system 1005.
  • the bus system 1005 is used to implement connection and communication between these components.
  • the bus system 1005 also includes a power bus, a control bus, and a status signal bus.
  • various buses are marked as the bus system 1005 in FIG. 10.
  • the user interface 1003 may include a display, a keyboard, a pointing device (for example, a mouse, a trackball), a touch panel or a touch screen, etc.
  • the memory 1002 in the embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), and electrically available Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be a random access memory (Random Access Memory, RAM), which is used as an external cache.
  • RAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • DDRSDRAM Double Data Rate Synchronous Dynamic Random Access Memory
  • Enhanced SDRAM, ESDRAM Synchronous Link Dynamic Random Access Memory
  • Synchlink DRAM Synchronous Link Dynamic Random Access Memory
  • DRRAM Direct Rambus RAM
  • the memory 1002 stores the following elements, executable modules or data structures, or their subsets, or their extended sets: operating system 10021 and application programs 10022.
  • the operating system 10021 includes various system programs, such as a framework layer, a core library layer, a driver layer, etc., for implementing various basic services and processing hardware-based tasks.
  • the application program 10022 includes various application programs, such as a media player (Media Player), a browser (Browser), etc., which are used to implement various application services.
  • the program for implementing the method of the embodiment of the present application may be included in the application program 10022.
  • the terminal device 1000 further includes: a computer program stored in the memory 1002 and capable of running on the processor 1001.
  • the computer program is executed by the processor 1001 to implement the steps of the method 100 as follows.
  • the methods disclosed in the foregoing embodiments of the present application may be applied to the processor 1001 or implemented by the processor 1001.
  • the processor 1001 may be an integrated circuit chip with signal processing capabilities. In the implementation process, the steps of the foregoing method can be completed by hardware integrated logic circuits in the processor 1001 or instructions in the form of software.
  • the foregoing processor 1001 may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other Programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor.
  • the software module may be located in a mature computer readable storage medium in the field, such as random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers.
  • the computer-readable storage medium is located in the memory 1002, and the processor 1001 reads information in the memory 1002, and completes the steps of the foregoing method in combination with its hardware.
  • a computer program is stored on the computer-readable storage medium, and when the computer program is executed by the processor 1001, each step of the above-mentioned method 100 embodiment is implemented.
  • the embodiments described in the embodiments of the present application may be implemented by hardware, software, firmware, middleware, microcode, or a combination thereof.
  • the processing unit can be implemented in one or more Application Specific Integrated Circuits (ASIC), Digital Signal Processing (DSP), Digital Signal Processing Equipment (DSP Device, DSPD), programmable Logic device (Programmable Logic Device, PLD), Field-Programmable Gate Array (Field-Programmable Gate Array, FPGA), general-purpose processors, controllers, microcontrollers, microprocessors, and others for performing the functions described in this application Electronic unit or its combination.
  • ASIC Application Specific Integrated Circuits
  • DSP Digital Signal Processing
  • DSP Device Digital Signal Processing Equipment
  • PLD programmable Logic Device
  • PLD Field-Programmable Gate Array
  • FPGA Field-Programmable Gate Array
  • the technology described in the embodiments of the present application can be implemented through modules (for example, procedures, functions, etc.) that execute the functions described in the embodiments of the present application.
  • the software codes can be stored in the memory and executed by the processor.
  • the memory can be implemented in the processor or external to the processor.
  • the terminal device 1000 can implement the various processes implemented by the terminal device in the foregoing embodiments, and can achieve the same or equivalent technical effects. To avoid repetition, details are not described herein again.
  • FIG. 11 is a structural diagram of a network device applied in an embodiment of the present application, which can implement the details of the method embodiment 700 and achieve the same effect.
  • the network device 1100 includes: a processor 1101, a transceiver 1102, a memory 1103, and a bus interface, where:
  • the network device 1100 further includes: a computer program that is stored in the memory 1103 and can be run on the processor 1101. The computer program is executed by the processor 1101 to implement the steps of the method 700.
  • the bus architecture may include any number of interconnected buses and bridges. Specifically, one or more processors represented by the processor 1101 and various circuits of the memory represented by the memory 1103 are linked together.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, power management circuits, etc., which are all known in the art, and therefore, no further descriptions are provided herein.
  • the bus interface provides the interface.
  • the transceiver 1102 may be multiple elements, that is, including a transmitter and a receiver, and provide a unit for communicating with various other devices on the transmission medium.
  • the processor 1101 is responsible for managing the bus architecture and general processing, and the memory 1103 can store data used by the processor 1101 when performing operations.
  • the embodiments of the present application also provide a computer-readable storage medium, and a computer program is stored on the computer-readable storage medium.
  • a computer program is stored on the computer-readable storage medium.
  • the computer program is executed by a processor, the various processes of the foregoing method embodiments 100 and 700 are realized, and the same Technical effects, in order to avoid repetition, I will not repeat them here.
  • the computer readable storage medium such as read-only memory (Read-Only Memory, ROM for short), random access memory (Random Access Memory, RAM for short), magnetic disk or optical disk, etc.
  • the method of the above embodiments can be implemented by means of software plus the necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is better. ⁇
  • the technical solution of this application essentially or the part that contributes to the existing technology can be embodied in the form of a software product, and the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk, The optical disc) includes several instructions to make a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) execute the methods described in the various embodiments of the present application.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Power Sources (AREA)

Abstract

本申请实施例公开了一种sidelink的DRX配置方法和设备，所述方法包括：终端设备确定DRX的配置信息；根据所述配置信息进行DRX配置。本申请实施例中，终端设备可以确定DRX的配置信息，并根据确定的配置信息进行DRX配置，以在sidelink中节约终端设备的电能。

Description

sidelink的DRX配置方法和设备
相关申请的交叉引用
本申请主张在2019年08月22日在中国提交的中国专利申请号201910780098.X的优先权，其全部内容通过引用包含于此。
技术领域
本申请实施例涉及通信领域，尤其涉及一种副链路(sidelink，或译为侧链路，边链路等)的非连续接收(Discontinuous Reception，DRX)配置方法和设备。
背景技术
长期演进(Long Term Evolution，LTE)系统和新空口(New Radio，NR)系统均支持sidelink传输，即终端设备之间能够直接在无线空口上进行数据传输。同时，LTE系统和NR系统在Uu口还引入了DRX机制，通过配置的DRX on和off时间来实现终端设备的节能。
然而，目前Uu口的DRX配置方案并没有在sidelink中采用，因此，在sidelink中如何实现终端设备的DRX配置，是相关技术中亟需解决的技术问题。
发明内容
本申请实施例的目的是提供一种sidelink的DRX配置方法和设备，用以在sidelink中实现终端设备的DRX配置。
第一方面，提供了一种sidelink的DRX配置方法，包括：
终端设备确定DRX的配置信息；
根据所述配置信息进行DRX配置。
第二方面，提供了一种sidelink的DRX配置方法，所述方法由网络设备执行，包括：
向终端设备发送DRX的配置信息；其中，所述配置信息用于所述终端设备进行DRX配置。
第三方面，提供了一种终端设备，该终端设备包括：
确定模块，用于确定DRX的配置信息；
配置模块，用于根据所述配置信息进行DRX配置。
第四方面，提供了一种网络设备，该网络设备包括：
发送模块，用于向终端设备发送DRX的配置信息；其中，所述配置信息用于所述终端设备进行DRX配置。
第五方面，提供了一种终端设备，该终端设备包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如第一方面所述的sidelink的DRX配置方法的步骤。
第六方面，提供了一种网络设备，该网络设备包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如第二方面所述的sidelink的DRX配置方法的步骤。
第七方面，提供了一种计算机可读存储介质，所述计算机可读存储介质上存储计算机程序，所述计算机程序被处理器执行时实现如第一方面和第二方面所述的sidelink的DRX配置方法的步骤。
在本申请实施例中，终端设备可以确定DRX的配置信息，并根据确定的配置信息进行DRX配置，以在sidelink系统中节约终端设备的电能。
附图说明
此处所说明的附图用来提供对本申请的进一步理解，构成本申请的一部分，本申请的示意性实施例及其说明用于解释本申请，并不构成对本申请的不当限定。在附图中：
图1是根据本申请的一个实施例的sidelink的DRX配置方法的示意性 流程图；
图2是根据本申请的一个实施例的sidelink传输示意图；
图3是图2所示的实施例中UE1和UE2的激活期和休眠期示意图；
图4至图6是根据本申请的三个具体实施例的sidelink的DRX配置方法的示意性流程图；
图7是根据本申请的另一个实施例的sidelink的DRX配置方法的示意性流程图；
图8是根据本申请的一个实施例的终端设备的结构示意图；
图9是根据本申请的一个实施例的网络设备的结构示意图；
图10是根据本申请的另一个实施例的终端设备的结构示意图；
图11是根据本申请的另一个实施例的网络设备的结构示意图。
具体实施方式
为使本申请的目的、技术方案和优点更加清楚，下面将结合本申请具体实施例及相应的附图对本申请技术方案进行清楚、完整地描述。显然，所描述的实施例仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。本说明书各个实施例中的“和/或”表示前后两者中的至少一个。
应理解，本申请实施例的技术方案可以应用于各种通信系统，例如：LTE sidelink系统或NR sidelink系统，或者为后续演进的sidelink通信系统。
在本申请实施例中，终端设备可以包括但不限于移动台(Mobile Station，MS)、移动终端(Mobile Terminal)、移动电话(Mobile Telephone)、用户设备(User Equipment，UE)、手机(handset)及便携设备(portable equipment)、车辆(vehicle)等，该终端设备可以经无线接入网(Radio Access Network，RAN)与一个或多个核心网进行通信，例如，终端设备可以是 移动电话(或称为“蜂窝”电话)、具有无线通信功能的计算机等，终端设备还可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动装置。
本申请实施例中，网络设备是一种部署在无线接入网中用以为终端设备提供无线通信功能的装置。所述网络设备可以为基站，所述基站可以包括各种形式的宏基站，微基站，中继站，接入点等。在采用不同的无线接入技术的系统中，具有基站功能的设备的名称可能会有所不同。例如在LTE网络中，称为演进的节点B(Evolved NodeB，eNB或eNodeB)，在第三代(3rd Generation，3G)网络中，称为节点B(Node B)，或者后续演进通信系统中的网络设备等等，然用词并不构成限制。
如图1所示，本申请的一个实施例提供一种sidelink的DRX配置方法100，该方法可以由终端设备执行，包括如下步骤：
S102：确定DRX的配置信息。
本说明书各个实施例提供的终端设备，可以是发送sidelink数据的发送设备，也可以是接收sidelink数据的接收设备，当然，这两者可以是一个终端设备，因为一个终端设备不仅可以执行发送sidelink数据的步骤，还可以执行接收sidelink数据的步骤。
本申请实施例将与终端设备进行sidelink通信的终端设备称作是对端设备。
可选地，在一个实施例中，该步骤中终端设备可以接收对端设备发送的配置信息。在该实施例中，对端设备可以为本端终端设备进行DRX配置。
可选地，在另一个实施例中，终端设备可以和对端设备预先约定配置信息，例如，预先约定DRX传输的相关参数，比如，预先约定DRX周期和偏移、DRX激活期的时长、DRX休眠期的时长等。这样，在和对端设备进行DRX传输之前，终端设备可以确定配置信息，以根据预先约定的配置信息进行DRX配置。
可选地，在再一个实施例中，网络设备可以对终端设备和对端设备进行DRX配置，该步骤中，终端设备可以接收网络设备发送的配置信息。
S104：根据配置信息进行DRX配置。
具体例如，该步骤可以对终端设备进行下述至少一种配置：
1)DRX的周期和偏移(offset)。
2)DRX持续监听定时器(drx-onDuration Timer)的长度。
3)DRX非激活定时器(drx-Inactivity Timer)的长度。
4)混合自动重传请求(Hybrid Automatic Repeat request，HARQ)往返时延(Round-Trip Time，RTT)定时器(drx-HARQ-RTT-Timer)的长度。
5)重传定时器(drx-Retransmission Timer)的长度。
上述提到的各个定时器的功能以及使用方法可以具体沿用NR Uu接口，在此不再重复描述。
本申请实施例提供的sidelink的DRX配置方法，终端设备可以确定DRX的配置信息，并根据确定的配置信息进行DRX配置，以在sidelink系统中节约终端设备的电能。
在一个具体的应用场景中，如图2所示，UE1可以给UE2发送sidelink数据，UE1可以给UE3发送sidelink数据，UE1可以给UE4发送sidelink数据，UE2可以给UE3发送sidelink数据。
通常，一个UE不能同时进行sidelink数据的接收和发送，因此，UE2给UE3发送sidelink数据的时刻，UE2并不期望接收UE1的sidelink数据。
通过本申请实施例提供的sidelink的DRX配置方法对UE1或UE2进行DRX配置之后，UE1和UE2的激活期和休眠期如图3所示。图3中的竖直方向突出部分表激活/监听状态，竖直方向低平部分代表休眠状态，水平方向为时间轴。
在图3中，UE1给UE2发送sidelink数据的时刻，UE1和UE2同时处于激活期。可选地，UE1给UE2发送sidelink数据的时刻，UE1和UE2 的激活期所占的时域位置相同。
另外，在图3中，UE1给UE3和UE4发送sidelink数据的时刻，UE1处于激活期，同时，UE2也处于激活期，这样，UE2可以给UE3发送sidelink数据。
图3所示的实施例中，通过对终端设备进行DRX配置，对于进行sidelink数据传输的一对终端设备(例如，UE1和UE2)而言，可以使两者的激活期一致，便于进行sidelink数据传输。
可选地，在图2所示的实施例中，UE1和UE2的激活期和休眠期所占的时域位置可以完全相同，即UE1和UE2的激活期所占的时域位置相同，且UE1和UE2的休眠期所占的时域位置也相同。
在实施例100中提到，对端设备可以对本端终端设备进行DRX配置，可选地，在实施例100执行之前还可以包括如下步骤：终端设备向对端设备发送DRX辅助信息或DRX配置请求。或所述终端设备向网络设备发送DRX辅助信息或DRX配置请求。
这样，前文实施例中的S102具体可以是终端设备接收DRX的配置信息。该配置信息可以是来自于对端设备，也可以是来自于网络设备。
具体例如，在图2和图3所示的实施例中，UE2向UE1发送DRX辅助信息或DRX配置请求。
在一个实施例中，终端设备可以发送DRX辅助信息，该DRX辅助信息可以用于对端设备根据该DRX辅助信息对终端设备进行DRX配置，当然，对端设备也可以忽略该辅助信息直接对终端设备进行DRX配置。
在该实施例中，终端设备可以发送DRX辅助信息，这样，对端设备在为终端设备进行DRX配置时可以充分考虑终端设备的sidelink传输情况，并结合自身的sidelink传输情况为终端设备进行DRX配置，在一定程度上相当于是终端设备和对端设备协商最优的DRX配置，以最大程度地实现节约终端设备和对端设备电能的效果。
在另一个实施例中，终端设备可以发送DRX配置请求，该DRX配置请求用于请求对端设备对终端设备进行DRX配置。在该实施例中，对端设备可以直接为终端设备进行DRX配置。
当然，在又一个实施例中，终端设备可以同时发送DRX辅助信息和DRX配置请求，关于DRX辅助信息DRX配置请求的作用可以参见上述介绍。
在上述各个实施例中提到的终端设备是sidelink数据的接收设备，对端设备是sidelink数据的发送设备；或者，上述各个实施例中提到的终端设备是sidelink数据的发送设备，对端设备是sidelink数据的接收设备；当然，上述各个实施例中提到的终端设备不仅可以向对端设备发送sidelink数据，也可以接收对端设备发送的sidelink数据，相应地，对端设备不仅可以接收终端设备发送的sidelink数据，也可以向终端设备发送sidelink数据。
需要说明是的是，本说明书各个实施例中提到的终端设备和对端设备，均是从本地终端设备的方向而言的。可以理解，对于对端设备而言，其本身可以称作是本地终端设备，而上述介绍的终端设备则可以称作是对端设备。
在上述各个实施例中，根据配置信息进行DRX配置之后，终端设备还可以向对端设备发送DRX反馈信息；其中，DRX反馈信息可以用来指示DRX的配置情况，例如，指示DRX配置成功，或者指示DRX配置失败等。
可选地，上述各个实施例中提到的DRX辅助信息包括下述至少一种：
终端设备希望的DRX的周期和偏移；
终端设备希望的DRX持续监听定时器的长度；
终端设备希望的DRX非激活定时器的长度；
终端设备希望的HARQ RTT定时器的长度；
终端设备希望的重传定时器的长度；
终端设备不希望DRX激活的时域单元，该处提到的时域单元可以是子帧、时隙等；
终端设备希望DRX激活的时域单元。
在上述实施例100中提到，网络设备可以为终端设备和对端设备进行DRX配置，可选地，该实施例的S102具体可以是终端设备接收网络设备发送的DRX的配置信息，该配置信息是由网络设备确定的。当然，对端设备也可以接收网络设备发送的配置信息并进行DRX配置。该实施例中，终端设备和对端设备都和网络设备保持RRC连接。
可选地，在上述实施例中，终端设备还可以接收指示信息；其中，该指示信息用于指示该配置信息针对的对端设备，例如，指示对端设备的标识信息。
可选地，终端设备根据配置信息进行DRX配置之后，还可以向网络设备发送DRX反馈信息，该DRX反馈信息可以用来指示DRX的配置情况，例如，指示DRX配置成功，或者指示DRX配置失败等。
在实际应用中，网络设备可以为终端设备配置发送DRX模式，并通知终端设备该发送DRX模式所针对的对端设备；并且，为对端设备配置接收DRX模式，并通知对端设备该接收DRX模式所针对的终端设备。上述只是以终端设备是发送设备，对端设备是接收设备为例进行介绍，实际上，在终端设备是接收设备，对端设备是发送设备的情况下，网络设备还可以为终端设备和对端设备配置相应的配置接收/发送DRX模式。
该实施例特别适用于终端设备的资源分配模式是网络设备调度模式(Mode 1)的场景中，因为网络设备为进行sidelink数据传输的一对终端设备分配资源，更容易确定这一对终端设备的sidelink数据发送的时域位置，从而对终端设备进行DRX配置时，将终端设备不进行sidelink数据传输的时间段尽可能配置为休眠期，能够最大程度地节约终端设备的电能。
为详细说明本申请各个实施例提供的sidelink的DRX配置方法，以下将结合几个具体的实施例进行介绍。
实施例一
如图4所示，该实施例可以由sidelink接收设备(后续简称接收设备)执行，包括如下步骤：
S402：发送辅助信息。
该实施例中，接收设备具体可以向sidelink发送设备(后续简称发送设备)发送辅助信息，发送设备对接收设备进行DRX配置，发送设备可以结合辅助信息对接收设备进行DRX配置，也可以忽略辅助信息，对接收设备进行DRX配置。
该辅助信息包括下述至少一种：
接收设备希望的DRX的周期和偏移；
接收设备希望的DRX持续监听定时器的长度；
接收设备希望的DRX非激活定时器的长度；
接收设备希望的HARQ RTT定时器的长度；
接收设备希望的重传定时器的长度；
接收设备不希望DRX激活的时域单元，该处提到的时域单元可以是子帧、时隙等；
接收设备希望DRX激活的时域单元。
S404：接收DRX的配置信息。
接收设备在接收到配置信息之后，即可根据配置信息进行DRX配置，具体的配置过程可以参见前文实施例的介绍。
S406：发送DRX反馈信息。
该DRX反馈信息可以用来指示DRX的配置情况，例如，指示DRX配置成功，或者指示DRX配置失败等。
可选地，在其他的实施例中，步骤S402和步骤S406可以省略，即发 送设备直接对接收设备进行DRX配置。
实施例二
如图5所示，该实施例可以由sidelink发送设备(后续简称发送设备)执行，包括如下步骤：
S502：发送辅助信息。
该实施例中，发送设备具体可以向sidelink接收设备(后续简称接收设备)发送辅助信息，接收设备对发送设备进行DRX配置，接收设备可以结合辅助信息对发送设备进行DRX配置，也可以忽略辅助信息，对发送设备进行DRX配置。
该辅助信息包括下述至少一种：
发送设备希望的DRX的周期和偏移；
发送设备希望的DRX持续监听定时器的长度；
发送设备希望的DRX非激活定时器的长度；
发送设备希望的HARQ RTT定时器的长度；
发送设备希望的重传定时器的长度；
发送设备不希望DRX激活的时域单元，该处提到的时域单元可以是子帧、时隙等；
发送设备希望DRX激活的时域单元。
S504：接收DRX的配置信息。
发送设备在接收到配置信息之后，即可根据配置信息进行DRX配置，具体的配置过程可以参见前文实施例的介绍。
S506：发送DRX反馈信息。
该DRX反馈信息可以用来指示DRX的配置情况，例如，指示DRX配置成功，或者指示DRX配置失败等。
可选地，在其他的实施例中，步骤S502和步骤S506可以省略，即接收设备直接对发送设备进行DRX配置。
实施例三
如图6所示，该实施例中网络设备可以为sidelink发送设备(后续简称发送设备)和sidelink接收设备(后续简称接收设备)进行DRX配置，发送设备和接收设备可以接收网络设备发送的配置信息。该实施例中，发送设备和接收设备都和网络设备保持RRC连接。
可选地，在该实施例中，发送设备还可以接收指示信息；其中，该指示信息用于指示接收设备，例如，指示接收设备的标识信息。
可选地，在该实施例中，接收设备还可以接收指示信息；其中，该指示信息用于指示发送设备，例如，指示发送设备的标识信息。
以上结合图1至图6详细描述了根据本申请实施例的sidelink的DRX配置方法。下面将结合图7详细描述根据本申请另一实施例的sidelink的DRX配置方法。可以理解的是，从网络设备侧描述的网络设备与终端设备的交互与图1所示的方法中的终端设备侧的描述相同，为避免重复，适当省略相关描述。
图7是本申请实施例的sidelink的DRX配置方法实现流程示意图，可以应用在网络设备侧，如图7所示，该方法700包括：
S702：向终端设备发送DRX的配置信息，该配置信息用于终端设备进行DRX配置。
在本申请实施例中，终端设备可以接收DRX的配置信息，并根据配置信息进行DRX配置，以在sidelink系统中节约终端设备的电能。
可选地，作为一个实施例，所述发送DRX的配置信息之后，所述方法还包括：
向所述配置信息针对的对端设备发送所述配置信息，所述配置信息还用于所述对端设备进行DRX配置。
可选地，作为一个实施例，所述向所述配置信息针对的对端设备发送所述配置信息之后，所述方法还包括：
向所述终端设备发送第一指示信息；其中，所述第一指示信息用于指示所述对端设备；和/或，向所述对端设备发送第二指示信息；其中，所述第二指示信息用于指示所述终端设备。
以上结合图1至图7详细描述了根据本申请实施例的sidelink的DRX配置方法。下面将结合图8详细描述根据本申请实施例的终端设备。
图8是根据本申请实施例的终端设备的结构示意图。如图8所示，终端设备800包括：
确定模块802，可以用于确定DRX的配置信息；配置模块804，可以用于根据所述配置信息进行DRX配置。
本申请实施例提供的终端设备可以确定DRX的配置信息，并根据确定的配置信息进行DRX配置，以在sidelink系统中，节约终端设备的电能。
可选地，作为一个实施例，所述确定模块802，可以用于接收对端设备发送的DRX的配置信息；其中，所述配置信息是所述对端设备确定的。
可选地，作为一个实施例，所述终端设备是sidelink接收设备，所述对端设备是sidelink发送设备；或，所述终端设备是sidelink发送设备，所述对端设备是sidelink接收设备。
可选地，作为一个实施例，所述确定模块802，可以用于向所述对端设备发送DRX反馈信息；其中，所述DRX反馈信息指示所述DRX配置成功或指示所述DRX配置失败。
可选地，作为一个实施例，所述确定模块802，可以用于向对端设备发送DRX辅助信息或DRX配置请求；或，向网络设备发送DRX辅助信息或DRX配置请求。
可选地，作为一个实施例，所述DRX辅助信息包括下述至少一种：
DRX的周期和偏移；
DRX持续监听定时器的长度；
DRX非激活定时器的长度；
混合自动重传请求HARQ往返时延RTT定时器的长度；
重传定时器的长度；
所述终端设备不希望DRX激活的时域单元；
所述终端设备希望DRX激活的时域单元。
可选地，作为一个实施例，所述配置信息由所述终端设备和对端设备预先约定。
可选地，作为一个实施例，确定模块802，可以用于接收网络设备发送的配置信息；其中，所述配置信息是由网络设备确定的。
可选地，作为一个实施例，确定模块802，可以用于接收指示信息；
其中，所述指示信息用于指示所述配置信息针对的对端设备；所述网络设备还用于为所述对端设备进行DRX配置。
可选地，作为一个实施例，确定模块802，可以用于向所述网络设备发送DRX反馈信息；其中，所述DRX反馈信息指示所述DRX配置成功或指示所述DRX配置失败。
根据本申请实施例的终端设备800可以参照对应本申请实施例的方法100的流程，并且，该终端设备800中的各个单元/模块和上述其他操作和/或功能分别为了实现方法100中的相应流程，并且能够达到相同或等同的技术效果，为了简洁，在此不再赘述。
图9是根据本申请实施例的网络设备的结构示意图。如图9所示，网络设备900包括：
发送模块902，可以用于向终端设备发送DRX的配置信息；其中，所述配置信息用于所述终端设备进行DRX配置。
在本申请实施例中，终端设备可以接收DRX的配置信息，并根据配置信息进行DRX配置，以在sidelink系统中节约终端设备的电能。
可选地，作为一个实施例，所述发送模块902还用于：向所述配置信息针对的对端设备发送所述配置信息，所述配置信息用于所述对端设备进 行DRX配置。
可选地，作为一个实施例，所述发送模块902还用于：向所述终端设备发送第一指示信息；其中，所述第一指示信息用于指示所述对端设备；和/或，向所述对端设备发送第二指示信息；其中，所述第二指示信息用于指示所述终端设备。
根据本申请实施例的终端设备900可以参照对应本申请实施例的方法700的流程，并且，该终端设备900中的各个单元/模块和上述其他操作和/或功能分别为了实现方法700中的相应流程，并且能够达到相同或等同的技术效果，为了简洁，在此不再赘述。
图10是本申请另一个实施例的终端设备的框图。图10所示的终端设备1000包括：至少一个处理器1001、存储器1002、至少一个网络接口1004和用户接口1003。终端设备1000中的各个组件通过总线系统1005耦合在一起。可理解，总线系统1005用于实现这些组件之间的连接通信。总线系统1005除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。但是为了清楚说明起见，在图10中将各种总线都标为总线系统1005。
其中，用户接口1003可以包括显示器、键盘、点击设备(例如，鼠标，轨迹球(trackball))、触感板或者触摸屏等。
可以理解，本申请实施例中的存储器1002可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器 (Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DRRAM)。本申请实施例描述的系统和方法的存储器1002旨在包括但不限于这些和任意其它适合类型的存储器。
在一些实施方式中，存储器1002存储了如下的元素，可执行模块或者数据结构，或者他们的子集，或者他们的扩展集：操作系统10021和应用程序10022。
其中，操作系统10021，包含各种系统程序，例如框架层、核心库层、驱动层等，用于实现各种基础业务以及处理基于硬件的任务。应用程序10022，包含各种应用程序，例如媒体播放器(Media Player)、浏览器(Browser)等，用于实现各种应用业务。实现本申请实施例方法的程序可以包含在应用程序10022中。
在本申请实施例中，终端设备1000还包括：存储在存储器上1002并可在处理器1001上运行的计算机程序，计算机程序被处理器1001执行时实现如下方法100的步骤。
上述本申请实施例揭示的方法可以应用于处理器1001中，或者由处理器1001实现。处理器1001可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器1001中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器1001可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器 也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的计算机可读存储介质中。该计算机可读存储介质位于存储器1002，处理器1001读取存储器1002中的信息，结合其硬件完成上述方法的步骤。具体地，该计算机可读存储介质上存储有计算机程序，计算机程序被处理器1001执行时实现如上述方法100实施例的各步骤。
可以理解的是，本申请实施例描述的这些实施例可以用硬件、软件、固件、中间件、微码或其组合来实现。对于硬件实现，处理单元可以实现在一个或多个专用集成电路(Application Specific Integrated Circuits，ASIC)、数字信号处理器(Digital Signal Processing，DSP)、数字信号处理设备(DSP Device，DSPD)、可编程逻辑设备(Programmable Logic Device，PLD)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)、通用处理器、控制器、微控制器、微处理器、用于执行本申请所述功能的其它电子单元或其组合中。
对于软件实现，可通过执行本申请实施例所述功能的模块(例如过程、函数等)来实现本申请实施例所述的技术。软件代码可存储在存储器中并通过处理器执行。存储器可以在处理器中或在处理器外部实现。
终端设备1000能够实现前述实施例中终端设备实现的各个过程，并且能够达到相同或等同的技术效果，为避免重复，这里不再赘述。
请参阅图11，图11是本申请实施例应用的网络设备的结构图，能够实现方法实施例700的细节，并达到相同的效果。如图11所示，网络设备1100包括：处理器1101、收发机1102、存储器1103和总线接口，其中：
在本申请实施例中，网络设备1100还包括：存储在存储器上1103并可在处理器1101上运行的计算机程序，计算机程序被处理器1101、执行 时实现方法700的步骤。
在图11中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器1101代表的一个或多个处理器和存储器1103代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机1102可以是多个元件，即包括发送机和接收机，提供用于在传输介质上与各种其他装置通信的单元。
处理器1101负责管理总线架构和通常的处理，存储器1103可以存储处理器1101在执行操作时所使用的数据。
本申请实施例还提供一种计算机可读存储介质，计算机可读存储介质上存储有计算机程序，该计算机程序被处理器执行时实现上述方法实施例100和700的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。其中，所述的计算机可读存储介质，如只读存储器(Read-Only Memory，简称ROM)、随机存取存储器(Random Access Memory，简称RAM)、磁碟或者光盘等。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品 的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本申请的保护之内。

Claims (29)

  1. 一种副链路的非连续接收DRX配置方法，所述方法包括：
    终端设备确定DRX的配置信息；
    根据所述配置信息进行DRX配置。
  2. 如权利要求1所述的方法，其中，所述终端设备确定DRX的配置信息包括：
    所述终端设备接收对端设备发送的DRX的配置信息；
    其中，所述配置信息是所述对端设备确定的。
  3. 如权利要求2所述的方法，其中，
    所述终端设备是副链路接收设备，所述对端设备是副链路发送设备；或
    所述终端设备是副链路发送设备，所述对端设备是副链路接收设备。
  4. 如权利要求3所述的方法，其中，所述根据所述配置信息进行DRX配置之后，所述方法还包括：
    向所述对端设备发送DRX反馈信息；
    其中，所述DRX反馈信息指示所述DRX配置成功或指示所述DRX配置失败。
  5. 如权利要求1所述的方法，其中，所述终端设备确定DRX的配置信息之前，所述方法还包括：
    所述终端设备向对端设备发送DRX辅助信息或DRX配置请求；或
    所述终端设备向网络设备发送DRX辅助信息或DRX配置请求。
  6. 如权利要求5所述的方法，其中，所述DRX辅助信息包括下述至少一种：
    DRX的周期和偏移；
    DRX持续监听定时器的长度；
    DRX非激活定时器的长度；
    混合自动重传请求HARQ往返时延RTT定时器的长度；
    重传定时器的长度；
    所述终端设备不希望DRX激活的时域单元；
    所述终端设备希望DRX激活的时域单元。
  7. 如权利要求1所述的方法，其中，所述配置信息由所述终端设备和对端设备预先约定。
  8. 如权利要求1所述的方法，其中，所述终端设备确定DRX的配置信息包括：
    所述终端设备接收网络设备发送的DRX的配置信息；
    其中，所述配置信息是由所述网络设备确定的。
  9. 如权利要求8所述的方法，其中，所述方法还包括：
    接收指示信息；
    其中，所述指示信息用于指示所述配置信息针对的对端设备；所述网络设备还用于为所述对端设备进行DRX配置。
  10. 如权利要求8所述的方法，其中，所述根据所述配置信息进行DRX配置之后，所述方法还包括：
    向所述网络设备发送DRX反馈信息；
    其中，所述DRX反馈信息指示所述DRX配置成功或指示所述DRX配置失败。
  11. 一种副链路的DRX配置方法，所述方法由网络设备执行，包括：
    向终端设备发送DRX的配置信息；其中，所述配置信息用于所述终端设备进行DRX配置。
  12. 如权利要求11所述的方法，其中，所述方法还包括：
    向所述配置信息针对的对端设备发送所述配置信息，所述配置信息还用于所述对端设备进行DRX配置。
  13. 如权利要求12所述的方法，其中，所述方法还包括：
    向所述终端设备发送第一指示信息；其中，所述第一指示信息用于指示所述对端设备；和/或
    向所述对端设备发送第二指示信息；其中，所述第二指示信息用于指示所述终端设备。
  14. 一种终端设备，包括：
    确定模块，用于确定DRX的配置信息；
    配置模块，用于根据所述配置信息进行DRX配置。
  15. 如权利要求14所述的终端设备，其中，所述确定模块，用于接收对端设备发送的DRX的配置信息；
    其中，所述配置信息是所述对端设备确定的。
  16. 如权利要求15所述的终端设备，其中，
    所述终端设备是副链路接收设备，所述对端设备是副链路发送设备；或
    所述终端设备是副链路发送设备，所述对端设备是副链路接收设备。
  17. 如权利要求16所述的终端设备，其中，所述确定模块，还用于向所述对端设备发送DRX反馈信息；
    其中，所述DRX反馈信息指示所述DRX配置成功或指示所述DRX配置失败。
  18. 如权利要求14所述的终端设备，其中，所述确定模块，还用于
    向对端设备发送DRX辅助信息或DRX配置请求；或
    向网络设备发送DRX辅助信息或DRX配置请求。
  19. 如权利要求18所述的终端设备，其中，所述DRX辅助信息包括下述至少一种：
    DRX的周期和偏移；
    DRX持续监听定时器的长度；
    DRX非激活定时器的长度；
    HARQ RTT定时器的长度；
    重传定时器的长度；
    所述终端设备不希望DRX激活的时域单元；
    所述终端设备希望DRX激活的时域单元。
  20. 如权利要求14所述的终端设备，其中，所述配置信息由所述终端设备和对端设备预先约定。
  21. 如权利要求14所述的终端设备，其中，所述确定模块，用于接收网络设备发送的DRX的配置信息；
    其中，所述配置信息是由所述网络设备确定的。
  22. 如权利要求21所述的终端设备，其中，所述确定模块，还用于接收指示信息；
    其中，所述指示信息用于指示所述配置信息针对的对端设备；所述网络设备还用于为所述对端设备进行DRX配置。
  23. 如权利要求21所述的终端设备，其中，所述确定模块，还用于向所述网络设备发送DRX反馈信息；
    其中，所述DRX反馈信息指示所述DRX配置成功或指示所述DRX配置失败。
  24. 一种网络设备，包括：
    发送模块，用于向终端设备发送DRX的配置信息；其中，所述配置信息用于所述终端设备进行DRX配置。
  25. 如权利要求24所述的网络设备，其中，所述发送模块还用于
    向所述配置信息针对的对端设备发送所述配置信息，所述配置信息用于所述对端设备进行DRX配置。
  26. 如权利要求25所述的网络设备，其中，所述发送模块还用于
    向所述终端设备发送第一指示信息；其中，所述第一指示信息用于指示所述对端设备；和/或
    向所述对端设备发送第二指示信息；其中，所述第二指示信息用于指示所述终端设备。
  27. 一种终端设备，包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如权利要求1至10中任一项所述的副链路的DRX配置方法的步骤。
  28. 一种网络设备，包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如权利要求11至13中任一项所述的副链路的DRX配置方法的步骤。
  29. 一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求1至13中任一项所述的副链路的DRX配置方法的步骤。
PCT/CN2020/110529 2019-08-22 2020-08-21 Sidelink的drx配置方法和设备 WO2021032194A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
JP2022512296A JP7498263B2 (ja) 2019-08-22 2020-08-21 ｓｉｄｅｌｉｎｋのＤＲＸ配置方法と機器
EP20855559.9A EP4021140A4 (en) 2019-08-22 2020-08-21 DRX CONFIGURATION METHOD AND DEVICE FOR SIDELINK
KR1020227007278A KR20220045184A (ko) 2019-08-22 2020-08-21 Sidelink의 DRX 배치 방법 및 기기
BR112022003122A BR112022003122A2 (pt) 2019-08-22 2020-08-21 Dispositivo e método de configuração drx para sidelink.
US17/676,590 US20220174781A1 (en) 2019-08-22 2022-02-21 Drx configuration method for sidelink and device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910780098.XA CN111800894A (zh) 2019-08-22 2019-08-22 sidelink的DRX配置方法和设备
CN201910780098.X 2019-08-22

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/676,590 Continuation US20220174781A1 (en) 2019-08-22 2022-02-21 Drx configuration method for sidelink and device

Publications (1)

Publication Number Publication Date
WO2021032194A1 true WO2021032194A1 (zh) 2021-02-25

Family

ID=72804940

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/110529 WO2021032194A1 (zh) 2019-08-22 2020-08-21 Sidelink的drx配置方法和设备

Country Status (7)

Country Link
US (1) US20220174781A1 (zh)
EP (1) EP4021140A4 (zh)
JP (1) JP7498263B2 (zh)
KR (1) KR20220045184A (zh)
CN (1) CN111800894A (zh)
BR (1) BR112022003122A2 (zh)
WO (1) WO2021032194A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022194088A1 (zh) * 2021-03-17 2022-09-22 维沃移动通信有限公司 非连续接收方法、装置及终端
WO2022211584A1 (ko) * 2021-04-02 2022-10-06 주식회사 아이티엘 무선 통신 시스템에서 drx 동작 방법 및 장치

Families Citing this family (30)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113225845B (zh) * 2020-01-21 2024-06-11 华硕电脑股份有限公司 处理关于周期性传送的侧链路不连续接收的方法和设备
US20220022279A1 (en) * 2020-07-15 2022-01-20 Electronics And Telecommunications Research Institute Low power operation method of terminal supporting direct communication, and apparatus for the same
CN114390598B (zh) * 2020-10-22 2024-03-01 维沃移动通信有限公司 Drx确定方法、装置、终端及可读存储介质
WO2022082677A1 (zh) * 2020-10-22 2022-04-28 富士通株式会社 边链路非连续接收方法及装置
US20240049342A1 (en) * 2020-12-14 2024-02-08 Beijing Xiaomi Mobile Software Co., Ltd. Drx configuration method and apparatus, communication device and storage medium
WO2022133937A1 (zh) * 2020-12-24 2022-06-30 华为技术有限公司 侧行链路通信方法、装置和系统
US20240114486A1 (en) * 2020-12-24 2024-04-04 Beijing Xiaomi Mobile Software Co., Ltd. Method for selecting transmission resource, communication device, and storage medium
WO2022147658A1 (zh) * 2021-01-05 2022-07-14 Oppo广东移动通信有限公司 侧行链路中设备状态的指示方法、装置、设备及存储介质
JP2024503674A (ja) * 2021-01-13 2024-01-26 北京小米移動軟件有限公司 サイドリンク通信制御方法、装置、機器及びその記憶媒体
CN114765832B (zh) * 2021-01-13 2024-06-07 维沃移动通信有限公司 省电处理方法、装置及终端
US20220232665A1 (en) * 2021-01-14 2022-07-21 Lg Electronics Inc. Method and apparatus for operating a ue related to sidelink drx in a wireless communication system
CN114765840B (zh) * 2021-01-14 2024-06-14 华为技术有限公司 一种通信方法及装置
CN117376952A (zh) * 2021-01-14 2024-01-09 Oppo广东移动通信有限公司 参数配置方法、用户设备和存储介质
CN116724586A (zh) * 2021-01-14 2023-09-08 中兴通讯股份有限公司 用于执行侧边发送和接收的方法和设备
US20240073907A1 (en) * 2021-01-14 2024-02-29 Lenovo (Beijing) Limited Mechanism for inter-ue coordination for sidelink drx ue
WO2022151277A1 (zh) * 2021-01-14 2022-07-21 华为技术有限公司 应用于非连续接收机制的通信方法及相关装置
CN114845318A (zh) * 2021-02-01 2022-08-02 大唐移动通信设备有限公司 信息指示方法、装置及终端
CN115119182A (zh) * 2021-03-17 2022-09-27 维沃移动通信有限公司 定时器控制方法、装置及终端
EP4316183A1 (en) * 2021-04-01 2024-02-07 Lenovo (Beijing) Limited Method and apparatus for sidelink communication
WO2022217468A1 (zh) * 2021-04-13 2022-10-20 Oppo广东移动通信有限公司 非连续接收方法及相关装置
CA3188394A1 (en) * 2021-05-08 2022-11-17 Wei Luo Methods, devices, and systems for configuring sidelink drx
WO2023274016A1 (zh) * 2021-07-02 2023-01-05 大唐移动通信设备有限公司 信息传输方法、资源调度方法、装置、终端及网络侧设备
CN115580887A (zh) * 2021-07-05 2023-01-06 维沃移动通信有限公司 单播侧链路配置方法、装置及终端
KR20240024310A (ko) * 2021-07-09 2024-02-23 베이징 시아오미 모바일 소프트웨어 컴퍼니 리미티드 사이드링크 통신 방법 및 장치
EP4374616A1 (en) * 2021-07-23 2024-05-29 Lenovo (Beijing) Limited Methods and apparatuses for determining sidelink drx configurations
CN113767651A (zh) * 2021-08-04 2021-12-07 北京小米移动软件有限公司 通信配置方法、装置、通信设备及存储介质
CN117859370A (zh) * 2021-09-30 2024-04-09 Oppo广东移动通信有限公司 资源配置方法、设备及存储介质
CN116017786A (zh) * 2021-10-22 2023-04-25 维沃移动通信有限公司 Sl drx的配置方法、装置及终端
CN117177262A (zh) * 2022-05-28 2023-12-05 华为技术有限公司 一种通信方法及相关装置
GB2623995A (en) * 2022-11-03 2024-05-08 Nokia Technologies Oy Sidelink Positioning

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160044740A1 (en) * 2014-08-11 2016-02-11 Telefonaktiebolaget L M Ericsson (Publ) Method of sharing a ue receiver between d2d and cellular operations based on activity
US20170289940A1 (en) * 2016-03-30 2017-10-05 Lg Electronics Inc. Method of transmitting slss by v2v terminal
CN108307489A (zh) * 2016-08-11 2018-07-20 中兴通讯股份有限公司 信息处理方法、装置、用户设备及基站
CN109155709A (zh) * 2016-05-23 2019-01-04 Lg 电子株式会社 接收下行链路控制信息的方法和用户设备
CN109479189A (zh) * 2016-07-21 2019-03-15 三星电子株式会社 设备到设备(d2d)通信中通过侧链路发现用户设备(ue)的系统和方法

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2013201508A (ja) 2012-03-23 2013-10-03 Sumitomo Electric Ind Ltd 無線端末装置、無線基地局装置および通信制御方法
JP5944592B2 (ja) * 2012-12-10 2016-07-05 テレフオンアクチーボラゲット エルエム エリクソン（パブル） ワイヤレス機器、無線ネットワークノード、および機器間通信での不連続受信のための方法
KR102118402B1 (ko) * 2014-02-25 2020-06-03 삼성전자 주식회사 단말 간 직접 통신을 지원하는 무선 통신 시스템에서 단말의 전력 감소 방법 및 장치
CN105379406B (zh) * 2014-05-21 2019-12-06 华为技术有限公司 一种设备到设备d2d通信中的信号传输方法及装置
EP3413645A1 (en) 2016-02-04 2018-12-12 NTT DoCoMo, Inc. User equipment and receiving method
CN114071678A (zh) * 2016-08-11 2022-02-18 中兴通讯股份有限公司 信息处理方法、装置、用户设备及基站
CN108307486A (zh) * 2016-08-11 2018-07-20 索尼公司 用于网络控制端和网络节点的电子设备和方法
WO2018027821A1 (zh) * 2016-08-11 2018-02-15 华为技术有限公司 一种通信方法、相关设备及系统
WO2018064477A1 (en) * 2016-09-30 2018-04-05 Intel IP Corporation Systems and methods for discontinuous reception in device-to-device communication

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160044740A1 (en) * 2014-08-11 2016-02-11 Telefonaktiebolaget L M Ericsson (Publ) Method of sharing a ue receiver between d2d and cellular operations based on activity
US20170289940A1 (en) * 2016-03-30 2017-10-05 Lg Electronics Inc. Method of transmitting slss by v2v terminal
CN109155709A (zh) * 2016-05-23 2019-01-04 Lg 电子株式会社 接收下行链路控制信息的方法和用户设备
CN109479189A (zh) * 2016-07-21 2019-03-15 三星电子株式会社 设备到设备(d2d)通信中通过侧链路发现用户设备(ue)的系统和方法
CN108307489A (zh) * 2016-08-11 2018-07-20 中兴通讯股份有限公司 信息处理方法、装置、用户设备及基站

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
See also references of EP4021140A4 *
ZTE: "Discussion on the RRC state of remote UE and relay UE", 3GPP DRAFT; R2-168199 DISCUSSION ON THE RRC STATE OF REMOTE UE, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Reno, USA; 20161114 - 20161118, 13 November 2016 (2016-11-13), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051177867 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022194088A1 (zh) * 2021-03-17 2022-09-22 维沃移动通信有限公司 非连续接收方法、装置及终端
WO2022211584A1 (ko) * 2021-04-02 2022-10-06 주식회사 아이티엘 무선 통신 시스템에서 drx 동작 방법 및 장치

Also Published As

Publication number Publication date
EP4021140A1 (en) 2022-06-29
CN111800894A (zh) 2020-10-20
KR20220045184A (ko) 2022-04-12
EP4021140A4 (en) 2022-10-26
BR112022003122A2 (pt) 2022-05-17
US20220174781A1 (en) 2022-06-02
JP2022545493A (ja) 2022-10-27
JP7498263B2 (ja) 2024-06-11

Similar Documents

Publication Publication Date Title
WO2021032194A1 (zh) Sidelink的drx配置方法和设备
US20220174780A1 (en) Method for configuring drx parameter for sidelink, and terminal device
CN111800893B (zh) 边链路非连续发送、接收方法与装置及终端设备
JP7462053B2 (ja) 不連続受信ｄｒｘパラメーター構成方法及び装置
WO2014161472A1 (zh) 一种进行寻呼的方法、装置及系统
CN113382379B (zh) 无线通信方法和通信装置
US20210212053A1 (en) Method for capability and resource allocation, terminal device, and control device
CN111263451B (zh) 副链路传输方法和设备
WO2018170914A1 (zh) 一种系统信息传输方法及装置
WO2013044415A1 (en) Discontinuous reception
EP4102864A1 (en) Communication method and communication apparatus for sidelinks
JP2016532337A (ja) ページング方法、ネットワーク装置及び通信システム
WO2020150903A1 (zh) 省电信号图案的使用方法、装置、设备及系统
US20210345155A1 (en) Wireless communication method and device
JP2022501951A (ja) Ｐｄｃｐ重複の設定方法及び端末機器
US10492176B2 (en) Methods, network node, wireless device, computer programs and computer program products for use with discontinuous reception
WO2021239135A1 (zh) 优先级确定方法和设备
US20240032142A1 (en) Sidelink transmission method and apparatus
WO2021088795A1 (zh) Harq-ack反馈信息的传输方法和设备
CN113708889A (zh) 数据传输方法和设备
CN111436119A (zh) 一种drx传输方法及相关设备
WO2021136516A1 (zh) 触发发现的方法、终端设备及网络设备
JP2024511608A (ja) サイドリンク不連続受信命令のトリガー方法、装置及びシステム
US20170359783A1 (en) Apparatus, Systems and Methods for Enhanced Dormancy Triggers and Dynamic Dormancy Timer Selection
WO2023116740A1 (zh) 通信方法和通信装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20855559

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022512296

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20227007278

Country of ref document: KR

Kind code of ref document: A

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112022003122

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 2020855559

Country of ref document: EP

Effective date: 20220322

ENP Entry into the national phase

Ref document number: 112022003122

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20220218