Detailed Description
The technical solutions of the embodiments of the present application will be clearly described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which are derived by a person skilled in the art based on the embodiments of the application, fall within the scope of protection of the application.
The terms first, second and the like in the description and in the claims, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate, such that embodiments of the application may be practiced otherwise than as specifically illustrated and described herein, and that the "first" and "second" distinguishing between objects generally being of the same type, and not necessarily limited to the number of objects, such as the first object may be one or more. Furthermore, in the description and claims, "and/or" means at least one of the connected objects, and the character "/" generally means a relationship in which the associated object is an "or" before and after.
It should be noted that the techniques described in the embodiments of the present application are not limited to long term evolution (Long Term Evolution, LTE)/LTE evolution (LTE-Advanced, LTE-a) systems, but may also be used in other wireless communication systems, such as code division multiple access (Code Division Multiple Access, CDMA), time division multiple access (Time Division Multiple Access, TDMA), frequency division multiple access (Frequency Division Multiple Access, FDMA), orthogonal frequency division multiple access (Orthogonal Frequency Division Multiple Access, OFDMA), single-carrier frequency division multiple access (Single-carrier Frequency-Division Multiple Access, SC-FDMA), and other systems. The terms "system" and "network" in embodiments of the application are often used interchangeably, and the techniques described may be used for both the above-mentioned systems and radio technologies, as well as other systems and radio technologies. The following description describes a New Radio (NR) system for exemplary purposes and NR terminology is used in much of the following description, but these techniques may also be applied to applications other than NR system applications, such as 6 th Generation (6G) communication systems.
Fig. 1 shows a block diagram of a wireless communication system to which an embodiment of the present application is applicable. The wireless communication system includes a terminal 11 and a network device 12. The terminal 11 may also be referred to as a terminal device or a User Equipment (UE), and the terminal 11 may be a terminal-side device such as a Mobile phone, a tablet Computer (Tablet Personal Computer), a Laptop (Laptop Computer) or a Personal digital assistant (Personal DIGITAL ASSISTANT, PDA), a palm Computer, a netbook, an ultra-Mobile Personal Computer (ultra-Mobile Personal Computer, UMPC), a Mobile internet device (Mobile INTERNET DEVICE, MID), a wearable device (Wearable Device) or a vehicle-mounted device (VUE), a pedestrian terminal (PUE), and the wearable device includes: a bracelet, earphone, glasses, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may be a base station or a core network, where the base station may be called a node B, an evolved node B, an access Point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a Basic service set (Basic SERVICE SET, BSS), an Extended service set (Extended SERVICE SET, ESS), a node B, an evolved node B (eNB), a next generation node B (gNB), a home node B, a home evolved node B, a WLAN access Point, a WiFi node, a transmission and reception Point (TRANSMITTING RECEIVING Point, TRP), or some other suitable terminology in the field, and the base station is not limited to a specific technical vocabulary so long as the same technical effect is achieved, and it should be noted that, in the embodiment of the present application, only a base station in an NR system is taken as an example, but a specific type of the base station is not limited.
The following describes in detail, with reference to the attached drawings, a specific embodiment and an application scenario thereof, a scheduling method, a terminal and a network side device for discontinuous reception (Discontinuous Reception, DRX) of a sidelink provided in the embodiment of the present application.
As shown in fig. 2, one embodiment of the present application provides a scheduling method 200 of sidelink DRX, which may be performed by a terminal, in other words, by software or hardware installed at the terminal, the method comprising the following steps.
S202: a terminal receives downlink control information (Downlink Control Information, DCI), which configures or activates DRX.
This embodiment can be applied to a base station scheduling Mode (Mode 1), where the network side device (base station) controls and allocates a sidelink resource to each terminal. The DCI in this embodiment may be used to schedule sidelink resources for a terminal.
The terminal mentioned in the various embodiments of the present specification configures or activates DRX, which may include one of the following three cases: the terminal only configures or activates the sidelink DRX; the terminal only configures or activates Uu DRX; the terminal configures or activates the sidelink DRX and Uu DRX.
S204: the terminal obtains a time interval between a receiving time of the DCI and a time of a first block of sidelink resources scheduled by the DCI according to at least one of: the method comprises the steps of a first scheduling time interval parameter, a second scheduling time interval parameter, a configuration offset, a DCI indication and a second scheduling time interval parameter.
In this embodiment, the first scheduling time interval parameter is a parameter used when the terminal configures or activates DRX, and the time of the first block of secondary link resources obtained by the terminal through the first scheduling time interval parameter is typically located in an activation period of the sidelink DRX and/or an activation period of Uu DRX; meanwhile, the receiving time of the DCI may be an active period located in Uu DRX, or may also be an active period located in sidelink DRX and an active period located in Uu DRX.
In this embodiment, the second scheduling time interval parameter is a parameter used in case the terminal is not configured or de-configured or does not activate DRX. In some cases, the terminal may still use the time instant of the first block of sidelink resources obtained by the second scheduling time interval parameter in case of configuring or activating DRX. The embodiment can be realized by the network equipment, so that the moment of the first block of secondary link resources, which is obtained by the terminal through the second scheduling time interval parameter, is usually in the active time period of the sidelink DRX and/or the active time period of the Uu DRX; meanwhile, the receiving time of the DCI may be an active period located in Uu DRX, or may also be an active period located in sidelink DRX and an active period located in Uu DRX.
In an example, the terminal may obtain the time of the first block of sidelink resource according to the second scheduling time interval parameter and the configuration offset, and in this embodiment, the time of the first block of sidelink resource obtained by the terminal is usually located in an active period of the sidelink DRX and/or an active period of Uu DRX through the setting of the configuration offset; meanwhile, the receiving time of the DCI may be an active period located in Uu DRX, or may also be an active period located in sidelink DRX and an active period located in Uu DRX.
The configuration offset mentioned in this example may be a specified duration, e.g. 4ms/slot, but also a multiple value, e.g. 2 times, 2.5 times, etc. the second scheduling time interval parameter used.
In another example, the time interval of the reception time of the DCI and the time of the first block of sidelink resources scheduled by the DCI may be directly indicated by the DCI; or the DCI may be used in combination with the foregoing examples, for example, to indicate a first scheduling interval parameter used by the terminal, or to indicate a second scheduling interval parameter and a configuration offset, or to indicate only a second scheduling interval parameter, etc. through the DCI.
In the embodiment, the DCI indicates that the time of the first block of sidelink resource obtained by the terminal is usually in the active period of the sidelink DRX and/or the active period of Uu DRX; meanwhile, the receiving time of the DCI may be an active period located in Uu DRX, or may also be an active period located in sidelink DRX and an active period located in Uu DRX.
According to the scheduling method of the sub-link DRX, when the DRX is configured or activated, the terminal obtains the time interval between the receiving time of the DCI and the time of the first sub-link resource scheduled by the DCI according to at least one of the following conditions: the method comprises the steps of a first scheduling time interval parameter, a second scheduling time interval parameter, a configuration offset, a DCI indication and a second scheduling time interval parameter.
When the embodiment of the application is applied to a base station scheduling Mode (Mode 1), the condition that the terminal is configured or DRX is activated is considered, so that the network resource efficiency is guaranteed, and the power saving performance of the terminal is greatly improved on the basis of ensuring the system efficiency.
Optionally, in one example, the terminal obtains, according to the first scheduling time interval parameter, a time interval between a time of receiving the DCI and a time of a first block of sidelink resources scheduled by the DCI; the DCI further includes indication information, where the indication information is used to indicate the first scheduling time interval parameter used by the terminal from a set of first scheduling time interval parameters.
In this embodiment, the network side device may configure a set of first scheduling time interval parameters for the terminal in advance, where the set of first scheduling time interval parameters includes a plurality of first scheduling time interval parameters, and when resources are scheduled each time, the network side device indicates, to the terminal device, one first scheduling time interval parameter to be used through DCI, so that a first block of sidelink resources calculated by the terminal is located in an active period of the sidelink DRX as much as possible, and on the basis of ensuring system efficiency, power saving performance of the terminal is greatly improved.
Optionally, each of the foregoing embodiments further includes the steps of: the terminal receives configuration information, wherein the configuration information is used for configuring one or more groups of first scheduling time interval parameters and/or one or more groups of second scheduling time interval parameters for the terminal.
In the above embodiment, the terminal may determine the packet using the first scheduling interval parameter or the packet using the second scheduling interval parameter according to a predefined manner.
For example, the configuration information configures a set of first scheduling time interval parameters and a set of second scheduling time interval parameters for the terminal. A protocol convention uses packets of a first scheduling time interval parameter when a Uu interface and/or a Sidelink (SL) interface configures or activates DRX; when neither the Uu interface nor the SL interface is configured or DRX is activated, packets of the second scheduling time interval parameter are used. This embodiment may also indicate in the DCI which parameter in the packet is specifically used, e.g. the first second scheduling time interval parameter in the packet indicating to the terminal to use the second scheduling time interval parameter, by means of a DCI indication.
In the above embodiment, the terminal may further determine a packet using the first scheduling interval parameter or a packet using the second scheduling interval parameter according to a medium access control (Medium Access Control, MAC) layer signaling or a physical layer signaling indication.
For example, the configuration information configures a set of first scheduling time interval parameters and a set of second scheduling time interval parameters for the terminal. When the Uu interface and/or the Sidelink (SL) interface configures or activates DRX, the network side equipment informs the terminal of using the packet of the first scheduling time interval parameter through MAC layer signaling or physical layer signaling; when neither Uu interface nor SL interface configures or activates DRX, the network side device informs the terminal of the packet using the second scheduling time interval parameter through MAC layer signaling or physical layer signaling.
The physical layer signaling in this embodiment may be DCI scheduling sidelink resources, for example, by means of DCI indication, in which of the specifically used packets and which parameter of the packets is indicated, for example, DCI indicates the first scheduling time interval parameter of the packets using the first scheduling time interval parameter.
In the foregoing embodiments, in the case where DRX is configured or activated, the terminal obtains, according to the first scheduling time interval parameter, a time interval between a reception time of DCI and a time of a first block of sidelink resources scheduled by the DCI, where the method further includes the following steps: and under the condition that the terminal is not configured or does not activate DRX, the terminal obtains the time interval between the receiving time of the DCI and the time of the first block of secondary link resource scheduled by the DCI according to the second scheduling time interval parameter.
Optionally, in embodiment 200, the terminal obtains, according to the second scheduling time interval parameter and the configuration offset, a time interval between a receiving time of the DCI and a time of a first block of sidelink resource scheduled by the DCI; wherein the configuration offset is predefined; or, the configuration offset is configured by radio resource control (Radio Resource Control, RRC) signaling.
In one example, the configuration offset is one, and the method further includes: the terminal determines whether to use the configuration offset according to at least one of the following;
1) RRC signaling.
2) MAC layer signaling.
3) Physical layer signaling.
4) DRX state. For example, the configuration offset is used after Uu DRX configuration or activation; using the configuration offset after SL DRX configuration or activation; using the configuration offset after both SL and Uu DRX are configured or activated; the configuration offset is not used when both SL and Uu DRX are not configured or activated.
In another example, the configuration offset is a plurality, and the method further includes: determining the configuration offset to use or determining the configuration offset to not use according to at least one of;
1) RRC signaling.
2) MAC layer signaling.
3) Physical layer signaling.
4) DRX state. For example, offset 1 is used after Uu DRX configuration or activation (where 1 is an identification or index, the following analogy); offset 2 is used after SL DRX configuration or activation; offset 3 is used after both SL and Uu DRX are configured or activated; when both SL and Uu DRX are not configured or activated, no offset is used.
Optionally, in an embodiment, the terminal obtains, according to the DCI indication, a time interval between a time of receiving the DCI and a time of a first block of sidelink resources scheduled by the DCI; wherein, the DCI carries the first scheduling time interval parameter or the second scheduling time interval parameter by one of the following methods:
1) Predefined coding scheme. For example, the corresponding field value 000 in DCI represents that the minimum value of the scheduling time interval is X ms/slot (where X is a specified value in the standard, for example, 1 or 3), and other values are incremented by an arithmetic progression or an arithmetic progression, for example, the corresponding field value 001 in DCI represents that the second value is x+d ms/slot, or n X ms/slot (where d is a specified value in the standard, for example, 2 or 3, and n is a specified value in the standard, for example, 2).
2) Coding scheme of RRC configuration. For example, the corresponding field value 000 in DCI represents that the minimum value of the scheduling time interval is X ms/slot (where X is an RRC configuration value, for example, 3), and other values are incremented by an arithmetic progression or an arithmetic progression, for example, the corresponding field value 001 in DCI represents that the second value is x+d ms/slot, or n is X ms/slot (where d is an RRC configuration value, for example, may be configured as 3 or 4, etc., and n is also an RRC configuration value, for example, configured as 2).
3) The DCI carries a group identifier and a label of the first scheduling time interval parameter in the group, and the terminal configures a plurality of first scheduling time interval parameter groups. For example, the DCI carries the 3 rd parameter of the second set of first scheduling interval parameters.
4) The DCI carries a configuration offset number and the second scheduling time interval parameter number in the group, and the terminal configures the configuration offset. For example, the DCI carries the 5 th parameter of the first set of second scheduling time interval parameters.
Optionally, each of the foregoing embodiments may further include one of:
1) And if the first block of sidelink resources is positioned in the sidelink DRX inactive time interval, the terminal gives up the sidelink resources scheduled by using the DCI.
2) And if the first block of sidelink resources is positioned in the sidelink DRX activation time interval, the terminal uses the sidelink resources scheduled by the DCI.
3) For the first block of sidelink resources and associated sidelink resources, the terminal relinquishes use of sidelink resources located within a sidelink DRX inactivity time interval.
4) For the first block of sidelink resources and associated sidelink resources, the terminal uses only sidelink resources located within a sidelink DRX activation time interval.
5) For the first block of sidelink resources and associated sidelink resources, the terminal uses only the sidelink resources of the first block located within the sidelink DRX activation time interval and the sidelink resources thereafter.
6) The terminal gives up using the sidelink resources which do not meet the use requirement.
In order to describe the scheduling method of the sidelink DRX provided in the embodiments of the present application in detail, the following description will be made with reference to several specific embodiments.
Embodiment one: independent parameter configuration
In this embodiment, the terminal is configured to determine a first scheduling time interval parameter according to the first scheduling time interval parameter; or a terminal (hereinafter, described as an example of UE) obtains a time interval between a reception time of the DCI and a time of a first block of sidelink resources scheduled by the DCI according to a DCI indication and a first scheduling time interval parameter
In this embodiment, when DRX is not configured/activated by both Uu interface and SL interface of a UE for a UE in a connected state, the UE may obtain a set of Mode 1 scheduling time interval parameters (corresponding to the second scheduling time interval parameter in the foregoing embodiment) from the network side terminal, for example, SL-DCI-ToSL-Trans, which is used to configure a time interval for the UE at the time of receiving DCI and the time of SL first block sidelink resource scheduled by the DCI.
For example, the network side device configures a set of second scheduling time interval parameters for the terminal in advance, wherein the second scheduling time interval parameters are respectively 1ms/slot,2ms/slot,4ms/slot and 8ms/slot.
When in real scheduling, network side equipment carries bit (bit) 00 in DCI to represent that the time interval between the current DCI receiving time and the first block SL resource scheduled by the DCI is 1ms/slot, namely, the 1ms/slot position after the UE receives the DCI uses the SL resource scheduled by the DCI to carry out SL transmission; or the network side equipment carries bit 01 in DCI to represent that the time interval between the current DCI receiving time and the first block SL resource scheduled by the DCI is 2ms/slot; or the network side equipment carries bit 10 in the DCI to represent that the time interval between the current DCI receiving time and the first block SL resource scheduled by the DCI is 4ms/slot, and so on.
In this embodiment, when a UE in a connected state is configured or has Uu interface DRX and/or SL interface DRX activated, the UE may obtain another set of Mode 1 scheduling time interval parameters (corresponding to the first scheduling time interval parameters in the previous embodiment) from the network side device, for example SL-DCI-ToSL-Trans, where the parameters are used to configure a time interval between the time when the UE receives DCI and the SL first block resource scheduled by the DCI.
For example, the network side device configures a set of first scheduling time interval parameters for the terminal in advance, wherein the first scheduling time interval parameters are respectively 2ms/slot,4ms/slot,8ms/slot and 16ms/slot.
When in real scheduling, network side equipment carries bit 00 in DCI to represent that the time interval between the current DCI receiving time and the first block SL resource scheduled by the DCI is 2ms/slot, namely, the UE uses the SL resource scheduled by the DCI to carry out SL transmission at the position of 2ms/slot after receiving the DCI; or the network side equipment carries bit 01 in DCI to represent that the time interval between the current DCI receiving time and the first block SL resource scheduled by the DCI is 4ms/slot; or the network side equipment carries bit 10 in the DCI to represent that the time interval between the current DCI receiving time and the first block SL resource scheduled by the DCI is 8ms/slot, and so on.
It can be seen that when the UE does not configure or activate DRX of any interface, the second scheduling interval parameter used by the UE is smaller, and when the UE is configured or activates DRX of any interface, the scheduling first interval parameter needs to be larger due to the limitation of DRX activation time, so that the UE can obtain different scheduling interval parameter configuration values under different conditions.
In this embodiment, the UE may also obtain multiple sets of scheduling time interval parameters simultaneously, where the multiple sets of scheduling time interval parameters may include at least two sets of second scheduling time interval parameters; or at least two sets of first scheduling time interval parameters; or at least one set of first scheduling time interval parameters and at least one set of second scheduling time interval parameters.
In this case, an example of the manner of use of the scheduling time interval parameter is as follows:
In one case, the UE obtains a plurality of sets of parameter values of the scheduling time interval from the network side device, and the network side device and the UE side determine when to use which set of parameter values in a pre-agreed manner:
for example, when the Uu interface configures or activates DRX, the scheduling time interval parameter value set 2 is used;
For example, when the SL interface configures or activates DRX, the scheduling time interval parameter value set 2 is used;
For example, when both Uu interface and SL interface configure or activate DRX, the scheduling time interval parameter value set 2 is used;
For example, when neither the Uu interface nor the SL interface is configured or DRX is not activated, the scheduling time interval parameter value set 1 is used;
for example, when the Uu interface configures or activates DRX parameter set 1, the scheduling time interval parameter set 2 is used, when the Uu interface configures or activates DRX parameter set 2, the scheduling time interval parameter set 3 is used, and when the Uu interface does not configure or activate DRX, the scheduling time interval parameter set 1 is used;
For example, when the SL interface configures or activates DRX parameter set 1, scheduling time interval parameter set 2 is used, when the SL interface configures or activates DRX parameter set 2, scheduling time interval parameter set 3 is used, and when the SL interface does not configure or activate DRX, scheduling time interval parameter set 1 is used;
For example, when the Uu interface configures or activates DRX parameter set 1 and the SL interface configures or activates DRX parameter set 1, the scheduling time interval parameter set 2 is used, when the Uu interface configures or activates DRX parameter set 2 and the SL interface configures or activates DRX parameter set 2, the scheduling time interval parameter set 3 is used, and otherwise the scheduling time interval parameter set 1 is used.
Set 1 in various embodiments of the present description may correspond to the packet of the second schedule interval parameter, set 2 may correspond to the packet of the first schedule interval parameter, and set 3 may correspond to the packet of the first schedule interval parameter.
In another case, the network side device dynamically notifies the terminal which set of scheduling time interval parameters is used, and the notification mode may be at least one of the following:
1) The MAC CE, for example, the MAC CE indicates the UE to start/stop using a special scheduling interval parameter value dedicated to DRX, or the MAC CE explicitly indicates the UE to start using a scheduling interval parameter value index, where there may be a default scheduling interval parameter, for example, a first group carried in RRC signaling is default, or explicitly specifies default, the index may also be in the order in which the parameters appear in the RRC signaling, the first group parameter value index is 0, the second group index is1, and so on.
2) The physical layer signaling, for example, DCI carries a reference number corresponding to a parameter value, where a default scheduling time interval parameter may also be specified, for example, a first group carried in RRC signaling is default, or default is explicitly specified, the reference number may also be in an order in which parameters appear in RRC signaling, where the first group parameter value is labeled 0, the second group parameter is labeled 1, and so on.
The DCI in this embodiment may be DCI for scheduling the sidelink resource, but may be other DCI.
The embodiment of the application provides a mode of using different scheduling time interval parameters in different DRX states. Under different states and configurations, the scheduling time intervals required by the network side equipment are different, and by the modes, the network side equipment can flexibly send the scheduling signaling under different states, so that electricity consumption caused by delaying and staying the UE at ACTIVE TIME for sending the scheduling signaling is avoided, and resource waste caused by improper scheduling resources is also avoided.
Embodiment two: configuration offset
In this embodiment, the UE configures an offset (abbreviated as offset) according to the second scheduling interval parameter; or according to DCI indication, second scheduling time interval parameter and configuration offset, obtaining the time interval between the receiving time of the DCI and the time of the first block of secondary link resource scheduled by the DCI
In this embodiment, the network side device may configure only one set of scheduling time interval parameters to the UE, and the set of scheduling time interval parameters may include one or more sets of second scheduling time interval parameters. Meanwhile, the network side device may additionally provide one or more offsets, where the offsets may be a specified duration, for example, 4ms/slot, or a multiple value, for example, the offsets are 2 times, 2.5 times, or the like, of the second scheduling time interval parameter used. The offset/multiple is obtained as follows:
1) The standard specifies that this way is a fixed offset, e.g. 4ms/slot, and when Uu/SL DRX is configured/activated, adding an offset to each parameter value on the basis of a normal time interval (i.e. the second scheduling time interval parameter), so as to obtain a new offset applicable to the DRX state; or a fixed multiple, for example 2 times, when Uu/SL DRX is configured/activated, each parameter value is multiplied by 2 on the basis of a common time interval to obtain a new offset suitable for the DRX state.
2) The network side equipment RRC is configured in such a way that different offsets/multiples can be configured, wherein the configuration value of the offsets/multiples can be determined according to different values of the Uu DRX pattern and the SL DRX pattern.
After the offset and the normal scheduling interval configuration are obtained, the UE may be used in the following manner:
1. If there is only one offset/multiple, the UE decides whether to use the offset as follows:
1) RRC signaling whether to superimpose offset/multiple;
2) MAC signaling whether to superimpose offset/multiple;
3) PHY signaling whether to superimpose offset/multiple;
4) Depending on the state decision, whether to superimpose the offset/multiple:
For example, when Uu DRX is configured or activated, an offset/multiple is superimposed; when SL DRX configuration or activation, the offset/multiple is superimposed; when SL and Uu DRX are both configured or activated, the offset/multiple is superimposed; when both SL and Uu DRX are not configured or activated, no offset/multiple is superimposed.
2. If there are multiple offsets/multiples, the UE decides which offset/multiple to use or not to use in the following way:
1) RRC signaling which offset/multiple or not to superimpose currently;
2) The MAC signaling informs which offset/multiple or not to superimpose currently;
3) PHY signaling which offset/multiple or not to superimpose currently may be combined with the scheduling DCI;
4) Depending on the state decision, whether or which offset/multiple to superimpose is or is superimposed:
for example, when Uu DRX configuration or activation, an offset/multiple 1 is superimposed; when SL DRX configuration or activation, the offset/multiple 2 is superimposed; when SL and Uu DRX are both configured or activated, the offset/multiple 3 is superimposed; when both SL and Uu DRX are not configured or activated, no offset/multiple is superimposed.
In the above way, by the method of flexibly specifying the offset/multiple, different scheduling time interval parameters can be used in different DRX states, so as to achieve the adaptation of the scheduling signaling and the DRX cycle.
Embodiment III: DCI carries
In this embodiment, each DCI dynamically carries the current scheduling time interval parameter value in the most flexible manner, but given that the size of the DCI is limited, a certain coding needs to be performed on the carried parameter value, so as to achieve the purpose of obtaining the maximum flexible scheduling manner with the minimum overhead, and the manner in which the DCI carries the scheduling time interval value is as follows:
1) The method adopts a coding mode specified by a standard, for example, a corresponding field value 000 in DCI, the minimum value representing the scheduling time interval is X ms/slot (wherein, X is a specified value in the standard, such as 1 or 3), other values are increased by adopting an arithmetic progression or an arithmetic progression, for example, a corresponding field value 001 in DCI, the second value is X+d ms/slot, or n is X ms/slot (wherein, d is a specified value in the standard, such as 2 or 3, etc., and n is a specified value in the standard, such as 2).
2) The coding mode of RRC configuration is adopted, for example, the corresponding field value 000 in the DCI represents that the minimum value of the scheduling time interval is X ms/slot (where X is an RRC configuration value, for example, 3), and other values are incremented by an arithmetic progression or an arithmetic progression, for example, the corresponding field value 001 in the DCI represents that the second value is x+d ms/slot, or n X ms/slot (where d is an RRC configuration value, for example, may be configured as 3 or 4, etc., and n is also an RRC configuration value, for example, configured as 2).
3) In the first embodiment, a plurality of first scheduling time interval parameter sets are configured, and a set identifier, a parameter number in a set, for example, a first 3 rd interval value, a second 5 th interval value, or the like, are carried in DCI;
4) In the above embodiment, in the case of configuring an offset or multiple, an offset value index or multiple index, and a parameter index in a group, for example, an offset value of 10+4th interval value, or multiple of 4×5th interval value, etc., are carried in DCI.
Through the above method, the DCI can flexibly specify the scheduling time interval used each time, and different scheduling time interval parameters are used in different DRX states or even each scheduling time so as to achieve good adaptation of the scheduling signaling and the DRX current ACTIVE TIME state, which belongs to the mode with the highest flexibility, and has the defect of large scheduling overhead.
Embodiment four: network side equipment implementation, UE behavior
In this embodiment, the network side device may be configured only for a set of scheduling time interval parameter values for the UE, and the UE takes the parameter values and performs execution according to the parameter values. For example, the network side RRC signaling configures 8 time intervals, numbered 0-7, and the UE uses a first time interval to interpret the DCI reception time and the interval of the first scheduled SL resource when 000 is indicated in the DCI, or uses a second time interval to interpret the DCI reception time and the interval of the first scheduled SL resource when 001 is indicated in the DCI, and so on.
The network side ensures the indicated scheduling time interval value and can be matched with the current Uu interface DRX state and SL interface DRX state of the UE. For example, when SL DRX is currently in long DRX off/inactive time (INACTIVE TIME), the network needs to schedule the Uu interface continuously so that the UE is always in active time (ACTIVE TIME) at the Uu interface, and thus can send DCI scheduling at an interval time position when it is enough from the next ACTIVE TIME of the SL DRX so that the time of DCI received by the UE and the SL resource position calculated by the scheduling interval time are located exactly within the interval of SL DRX ACTIVE TIME.
In particular, when the network side does not ensure the time of DCI received by the UE and the SL resource position calculated by the scheduling interval time parameter are located exactly in the interval of the SL DRX ACTIVE TIME, that is, the SL resource position scheduled by the network side is located in the interval of the SL DRX INACTIVE TIME, the terminal acts as follows:
1) And if the first block SL resource position of the scheduling is located in the SL DRX INACTIVE TIME section, the UE gives up the scheduling resource using the DCI.
2) The UE uses the scheduling resource of the DCI if the first block SL resource position of the present scheduling calculated by the time of the DCI received by the UE and the scheduling interval is located in the SL DRX ACTIVE TIME interval.
3) For the time of DCI received by the UE, and the first block SL resource location and other relevant SL resource locations of this schedule calculated by the scheduling interval time, the UE relinquishes use of SL resources located in the SL DRX INACTIVE TIME interval.
4) For the time of DCI received by the UE, and the first block SL resource location and other relevant SL resource locations of this schedule calculated by the scheduling interval time, the UE uses SL resources located in the SL DRX ACTIVE TIME interval.
5) For the time of DCI received by the UE, and the first block SL resource location and other relevant SL resource locations for this scheduling calculated by the scheduling interval time, the UE uses the SL resources that are located in the SL DRX ACTIVE TIME interval and thereafter.
6) The UE gives up using SL scheduling resources that do not meet the usage requirement.
The scheduling method of the sidelink DRX according to the embodiment of the present application is described in detail above with reference to fig. 2. A scheduling method of sidelink DRX according to another embodiment of the present application will be described in detail with reference to fig. 3. It will be appreciated that the interaction of the network side device with the terminal described from the network side device is the same as the description of the terminal side in the method shown in fig. 2, and the related description is omitted appropriately to avoid repetition.
Fig. 3 is a schematic flow chart of an implementation of a scheduling method of sidelink DRX according to an embodiment of the present application, which may be applied to a network device. As shown in fig. 3, the method 300 includes:
S302: the network side equipment transmits DCI, wherein the DCI is used for obtaining a time interval between the receiving time of the DCI and the time of the first block of secondary link resources scheduled by the DCI according to at least one of the following steps: the method comprises the steps of a first scheduling time interval parameter, a second scheduling time interval parameter, a configuration offset, a DCI indication and a second scheduling time interval parameter.
Wherein the terminal configures or activates DRX, the first scheduling time interval parameter is a parameter used in a case where the terminal configures or activates DRX, and the second scheduling time interval parameter is a parameter used in a case where the terminal does not configure or de-configure or does not activate DRX.
In the embodiment of the application, the network side equipment sends DCI, and the terminal obtains the time interval between the receiving time of the DCI and the time of the first block of secondary link resource scheduled by the DCI according to at least one of the following conditions that DRX is configured or activated: the method comprises the steps of a first scheduling time interval parameter, a second scheduling time interval parameter, a configuration offset, a DCI indication and a second scheduling time interval parameter. When the embodiment of the application is applied to a base station scheduling Mode (Mode 1), the condition that the terminal is configured or DRX is activated is considered, so that the network resource efficiency is guaranteed, and the power saving performance of the terminal is greatly improved on the basis of ensuring the system efficiency.
Optionally, as an embodiment, the DCI further includes indication information, where the indication information is used to indicate the first scheduling time interval parameter used by the terminal from a set of the first scheduling time interval parameters.
Optionally, as an embodiment, the method further includes:
And sending configuration information, wherein the configuration information is used for configuring one or more groups of first scheduling time interval parameters and/or one or more groups of second scheduling time interval parameters for the terminal.
Optionally, as an embodiment, the method further includes:
and sending MAC layer signaling or physical layer signaling, wherein the MAC layer signaling or the physical layer signaling is used for indicating the terminal to use the packet of the first scheduling time interval parameter or the packet of the second scheduling time interval parameter.
Optionally, as an embodiment, the method further includes:
And sending RRC signaling, wherein the RRC signaling is used for configuring the configuration offset for the terminal.
Optionally, as an embodiment, the DCI carries the first scheduling time interval parameter or the second scheduling time interval parameter by one of the following:
a predefined coding scheme;
coding mode of RRC configuration;
The DCI carries a group identifier and a label of the first scheduling time interval parameter in the group, and the terminal configures a plurality of first scheduling time interval parameter groups;
The DCI carries a configuration offset number and the second scheduling time interval parameter number in the group, and the terminal configures the configuration offset.
Optionally, as an embodiment, the network side device is further configured to determine that the second number of scheduling time intervals matches the DRX state of the terminal.
It should be noted that, in the scheduling method of the sidelink DRX provided in the embodiment of the present application, the execution body may be a terminal, or a control module in the terminal for executing the scheduling method of the sidelink DRX. In the embodiment of the application, a scheduling method for a terminal to execute a sidelink DRX is taken as an example, and the terminal provided by the embodiment of the application is described.
Fig. 4 is a schematic structural diagram of a terminal according to an embodiment of the present application, and as shown in fig. 4, a terminal 400 includes:
a receiving module 402, configured to receive DCI, where the terminal configures or activates DRX;
A determining module 404, configured to obtain a time interval between a time of receiving the DCI and a time of a first block of sidelink resources scheduled by the DCI according to at least one of: the DCI comprises a first scheduling time interval parameter, a second scheduling time interval parameter and a configuration offset, wherein the DCI indicates the second scheduling time interval parameter;
Wherein the first scheduling time interval parameter is a parameter used in a case where the terminal configures or activates DRX, and the second scheduling time interval parameter is a parameter used in a case where the terminal does not configure or de-configure or does not activate DRX.
In the embodiment of the present application, when DRX is configured or activated, the terminal obtains a time interval between a reception time of DCI and a time of a first block of sidelink resources scheduled by the DCI according to at least one of: the method comprises the steps of a first scheduling time interval parameter, a second scheduling time interval parameter, a configuration offset, a DCI indication and a second scheduling time interval parameter. When the embodiment of the application is applied to a base station scheduling Mode (Mode 1), the condition that the terminal is configured or DRX is activated is considered, so that the network resource efficiency is guaranteed, and the power saving performance of the terminal is greatly improved on the basis of ensuring the system efficiency.
Optionally, as an embodiment, the determining module 404 is configured to obtain, according to the first scheduling time interval parameter, a time interval between a time of receiving the DCI and a time of a first block of sidelink resources scheduled by the DCI;
the DCI further includes indication information, where the indication information is used to indicate the first scheduling time interval parameter used by the terminal from a set of first scheduling time interval parameters.
Optionally, as an embodiment, the receiving module 402 is further configured to receive configuration information, where the configuration information is used to configure one or more sets of the first scheduling time interval parameters and/or one or more sets of the second scheduling time interval parameters for the terminal.
Optionally, as an embodiment, the determining module 404 is further configured to determine, according to a predefined manner, a packet using the first scheduling time interval parameter or a packet using the second scheduling time interval parameter; or alternatively, the first and second heat exchangers may be,
The determining module is further configured to determine, according to a MAC layer signaling or a physical layer signaling indication, a packet using the first scheduling time interval parameter or a packet using the second scheduling time interval parameter.
Optionally, as an embodiment, the determining module 404 is further configured to obtain, according to the second scheduling time interval parameter, a time interval between a time of receiving the DCI and a time of the first block of sidelink resources scheduled by the DCI when the terminal is not configured or does not activate DRX.
Optionally, as an embodiment, the determining module 404 is configured to obtain, according to the second scheduling time interval parameter and the configuration offset, a time interval between a time of receiving the DCI and a time of a first block of sidelink resources scheduled by the DCI;
wherein the configuration offset is predefined; or (b)
The configuration offset is configured for radio resource control, RRC, signaling.
Optionally, as an embodiment, the configuration offset is one, and the determining module 404 is further configured to determine whether to use the configuration offset according to at least one of the following;
RRC signaling;
MAC layer signaling;
physical layer signaling;
DRX state.
Optionally, as an embodiment, the configuration offset is multiple, and the determining module 404 is further configured to determine the configuration offset to be used or determine the configuration offset to be not used according to at least one of the following;
RRC signaling;
MAC layer signaling;
physical layer signaling;
DRX state.
Optionally, as an embodiment, the determining module 404 is configured to obtain, according to the DCI indication, a time interval between a time of receiving the DCI and a time of a first block of sidelink resources scheduled by the DCI; wherein, the DCI carries the first scheduling time interval parameter or the second scheduling time interval parameter by one of the following methods:
a predefined coding scheme;
coding mode of RRC configuration;
The DCI carries a group identifier and a label of the first scheduling time interval parameter in the group, and the terminal configures a plurality of first scheduling time interval parameter groups;
The DCI carries a configuration offset number and the second scheduling time interval parameter number in the group, and the terminal configures the configuration offset.
Optionally, as an embodiment, the method further includes a resource usage module for one of:
If the first block of sidelink resources is located in the sidelink DRX inactive time interval, the terminal gives up using the sidelink resources scheduled by the DCI;
If the first block of sidelink resources is located in the sidelink DRX activation time interval, the terminal uses the sidelink resources scheduled by the DCI;
For the first block of sidelink resources and related sidelink resources, the terminal gives up using sidelink resources located in a sidelink DRX inactive time interval;
For the first block of sidelink resources and related sidelink resources, the terminal only uses sidelink resources located in a sidelink DRX activation time interval;
For the first block of sidelink resources and related sidelink resources, the terminal only uses the sidelink resources of the first block in the sidelink DRX activation time interval and the sidelink resources after the first block;
the terminal gives up using the sidelink resources which do not meet the use requirement.
The terminal 400 according to the embodiment of the present application may refer to the flow of the method 200 corresponding to the embodiment of the present application, and each unit/module in the terminal 400 and the other operations and/or functions described above are respectively for implementing the corresponding flow in the method 200, and can achieve the same or equivalent technical effects, which are not repeated herein for brevity.
The terminal in the embodiment of the application can be a device, a component in the terminal, an integrated circuit or a chip. The device may be a mobile terminal or a non-mobile terminal. By way of example, mobile terminals may include, but are not limited to, the types of terminals 11 listed above, and non-mobile terminals may be servers, network attached storage (Network Attached Storage, NAS), personal computers (personal computer, PCs), televisions (TVs), teller machines, self-service machines, etc., and embodiments of the present application are not limited in particular.
The terminal in the embodiment of the application can be a device with an operating system. The operating system may be an Android operating system, an ios operating system, or other possible operating systems, and the embodiment of the present application is not limited specifically.
The terminal provided by the embodiment of the present application can implement each process implemented by the embodiment of the method of fig. 2, and achieve the same technical effects, and in order to avoid repetition, a detailed description is omitted here.
Fig. 5 is a schematic structural diagram of a network side device according to an embodiment of the present application, as shown in fig. 5, a network side device 500 includes:
a transmitting module 502, configured to transmit DCI;
The DCI is used for obtaining a time interval between the receiving time of the DCI and the time of the first block of secondary link resources scheduled by the DCI by the terminal according to at least one of the following steps: the DCI comprises a first scheduling time interval parameter, a second scheduling time interval parameter and a configuration offset, wherein the DCI indicates the second scheduling time interval parameter;
Wherein the terminal configures or activates DRX, the first scheduling time interval parameter is a parameter used in a case where the terminal configures or activates DRX, and the second scheduling time interval parameter is a parameter used in a case where the terminal does not configure or de-configure or does not activate DRX.
In the embodiment of the application, the network side equipment sends DCI, and the terminal obtains the time interval between the receiving time of the DCI and the time of the first block of secondary link resource scheduled by the DCI according to at least one of the following conditions that DRX is configured or activated: the method comprises the steps of a first scheduling time interval parameter, a second scheduling time interval parameter, a configuration offset, a DCI indication and a second scheduling time interval parameter. When the embodiment of the application is applied to a base station scheduling Mode (Mode 1), the condition that the terminal is configured or DRX is activated is considered, so that the network resource efficiency is guaranteed, and the power saving performance of the terminal is greatly improved on the basis of ensuring the system efficiency.
Optionally, as an embodiment, the DCI further includes indication information, where the indication information is used to indicate the first scheduling time interval parameter used by the terminal from a set of the first scheduling time interval parameters.
Optionally, as an embodiment, the sending module 502 may be configured to send configuration information, where the configuration information is used to configure one or more sets of the first scheduling time interval parameters and/or one or more sets of the second scheduling time interval parameters for the terminal.
Optionally, as an embodiment, the sending module 502 is further configured to send MAC layer signaling or physical layer signaling, where the MAC layer signaling or the physical layer signaling is configured to instruct the terminal to use the packet of the first scheduling time interval parameter or the packet of the second scheduling time interval parameter.
Optionally, as an embodiment, the sending module 502 is further configured to send RRC signaling, where the RRC signaling is used to configure the configuration offset for the terminal.
Optionally, as an embodiment, the DCI carries the first scheduling time interval parameter or the second scheduling time interval parameter by one of the following:
a predefined coding scheme;
coding mode of RRC configuration;
The DCI carries a group identifier and a label of the first scheduling time interval parameter in the group, and the terminal configures a plurality of first scheduling time interval parameter groups;
The DCI carries a configuration offset number and the second scheduling time interval parameter number in the group, and the terminal configures the configuration offset.
Optionally, as an embodiment, the network side device is further configured to determine that the second number of scheduling time intervals matches the DRX state of the terminal.
The network side device 500 according to the embodiment of the present application may refer to the flow of the method 300 corresponding to the embodiment of the present application, and each unit/module in the network side device 500 and the other operations and/or functions described above are respectively for implementing the corresponding flow in the method 300, and may achieve the same or equivalent technical effects, which are not described herein for brevity.
Optionally, as shown in fig. 6, the embodiment of the present application further provides a communication device 600, including a processor 601, a memory 602, and a program or an instruction stored in the memory 602 and capable of running on the processor 601, where, for example, the communication device 600 is a terminal, the program or the instruction is executed by the processor 601 to implement each process of the above-mentioned embodiment of the scheduling method of the sidelink DRX, and the same technical effects can be achieved. When the communication device 600 is a network side device, the program or the instruction implements each process of the above-mentioned scheduling method embodiment of the sidelink DRX when executed by the processor 601, and the same technical effects can be achieved, so that repetition is avoided, and no further description is given here.
Fig. 7 is a schematic diagram of a hardware structure of a terminal for implementing an embodiment of the present application.
The terminal 700 includes, but is not limited to: radio frequency unit 701, network module 702, audio output unit 703, input unit 704, sensor 705, display unit 706, user input unit 707, interface unit 708, memory 709, and processor 710.
Those skilled in the art will appreciate that the terminal 700 may further include a power source (e.g., a battery) for powering the various components, and that the power source may be logically coupled to the processor 710 via a power management system so as to perform functions such as managing charging, discharging, and power consumption via the power management system. The terminal structure shown in fig. 7 does not constitute a limitation of the terminal, and the terminal may include more or less components than shown, or may combine certain components, or may be arranged in different components, which will not be described in detail herein.
It should be appreciated that in embodiments of the present application, the input unit 704 may include a graphics processor (Graphics Processing Unit, GPU) 7041 and a microphone 7042, with the graphics processor 7041 processing image data of still pictures or video obtained by an image capturing device (e.g., a camera) in a video capturing mode or an image capturing mode. The display unit 706 may include a display panel 7061, and the display panel 7061 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 707 includes a touch panel 7071 and other input devices 7072. The touch panel 7071 is also referred to as a touch screen. The touch panel 7071 may include two parts, a touch detection device and a touch controller. Other input devices 7072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and so forth, which are not described in detail herein.
In the embodiment of the present application, after receiving downlink data from a network side device, the radio frequency unit 701 processes the downlink data with the processor 710; in addition, the uplink data is sent to the network side equipment. Typically, the radio unit 701 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.
The memory 709 may be used to store software programs or instructions and various data. The memory 709 may mainly include a storage program or instruction area and a storage data area, wherein the storage program or instruction area may store an operating system, application programs or instructions (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like. In addition, the Memory 709 may include a high-speed random access Memory, and may also include a nonvolatile Memory, wherein the nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable Programmable ROM (EPROM), an Electrically Erasable Programmable EPROM (EEPROM), or a flash Memory. Such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid-state storage device.
Processor 710 may include one or more processing units; alternatively, processor 710 may integrate an application processor that primarily processes operating systems, user interfaces, and applications or instructions, etc., with a modem processor that primarily processes wireless communications, such as a baseband processor. It will be appreciated that the modem processor described above may not be integrated into the processor 710.
The radio frequency unit 701 is configured to receive DCI, where the terminal 700 configures or activates DRX; a processor 710, configured to obtain a time interval between a time of receiving the DCI and a time of a first block of sidelink resources scheduled by the DCI according to at least one of: the DCI comprises a first scheduling time interval parameter, a second scheduling time interval parameter and a configuration offset, wherein the DCI indicates the second scheduling time interval parameter; wherein the first scheduling time interval parameter is a parameter used in a case where the terminal configures or activates DRX, and the second scheduling time interval parameter is a parameter used in a case where the terminal does not configure or de-configure or does not activate DRX.
In the embodiment of the present application, when DRX is configured or activated, the terminal obtains a time interval between a reception time of DCI and a time of a first block of sidelink resources scheduled by the DCI according to at least one of: the method comprises the steps of a first scheduling time interval parameter, a second scheduling time interval parameter, a configuration offset, a DCI indication and a second scheduling time interval parameter. When the embodiment of the application is applied to a base station scheduling Mode (Mode 1), the condition that the terminal is configured or DRX is activated is considered, so that the network resource efficiency is guaranteed, and the power saving performance of the terminal is greatly improved on the basis of ensuring the system efficiency.
The terminal 700 provided in the embodiment of the present application may further implement each process of the above embodiment of the scheduling method for the sidelink DRX, and may achieve the same technical effects, so that repetition is avoided, and no description is repeated here.
Specifically, the embodiment of the application also provides network side equipment. As shown in fig. 8, the network device 800 includes: an antenna 81, a radio frequency device 82, a baseband device 83. The antenna 81 is connected to a radio frequency device 82. In the uplink direction, the radio frequency device 82 receives information via the antenna 81, and transmits the received information to the baseband device 83 for processing. In the downlink direction, the baseband device 83 processes information to be transmitted, and transmits the processed information to the radio frequency device 82, and the radio frequency device 82 processes the received information and transmits the processed information through the antenna 81.
The above-described band processing means may be located in the baseband means 83, and the method performed by the network-side device in the above embodiment may be implemented in the baseband means 83, and the baseband means 83 includes the processor 84 and the memory 85.
The baseband device 83 may, for example, comprise at least one baseband board, on which a plurality of chips are disposed, as shown in fig. 8, where one chip, for example, a processor 84, is connected to the memory 85, so as to invoke a program in the memory 85 to perform the network device operation shown in the above method embodiment.
The baseband device 83 may further include a network interface 86 for interacting with the radio frequency device 82, such as a common public radio interface (common public radio interface, CPRI for short).
Specifically, the network side device of the embodiment of the present invention further includes: instructions or programs stored in the memory 85 and executable on the processor 84, the processor 84 invokes the instructions or programs in the memory 85 to perform the method performed by the modules shown in fig. 5, and achieve the same technical effects, and are not repeated here.
The embodiment of the application also provides a readable storage medium, and the readable storage medium stores a program or an instruction, which when executed by a processor, implements each process of the above-mentioned scheduling method embodiment of the sidelink DRX, and can achieve the same technical effect, so that repetition is avoided, and no further description is given here.
The processor may be a processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium such as a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.
The embodiment of the application further provides a chip, the chip comprises a processor and a communication interface, the communication interface is coupled with the processor, the processor is used for running a program or instructions, the processes of the scheduling method embodiment of the sidelink DRX can be realized, the same technical effect can be achieved, and the repetition is avoided, and the description is omitted here.
It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Furthermore, it should be noted that the scope of the methods and apparatus in the embodiments of the present application is not limited to performing the functions in the order shown or discussed, but may also include performing the functions in a substantially simultaneous manner or in an opposite order depending on the functions involved, e.g., the described methods may be performed in an order different from that described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method according to the embodiments of the present application.
The embodiments of the present application have been described above with reference to the accompanying drawings, but the present application is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those having ordinary skill in the art without departing from the spirit of the present application and the scope of the claims, which are to be protected by the present application.