Patent Application
20240129997
The present disclosure relates to the field of communication technologies, and in particular to a resource allocation method, a device, and a storage medium.
An existing sidelink communication system supports unicast sidelink discontinuous reception (sidelink DRX, also SL DRX) configuration. In the unicast SL DRX configuration, a receiver terminal (i.e., the terminal that receives the SL DRX configuration) receives the SL DRX configuration from a sender terminal (i.e., the terminal that sends the SL DRX configuration), and the receiver terminal can reject the SL DRX configuration. How to improve a success rate of the SL DRX configuration is a problem that needs to be solved.
The present disclosure provides a resource allocation method and a device.
In a first aspect, the present disclosure provides a resource allocation method, performed by a first device and comprising: sending a first information to a second device; wherein the first information comprises an assistance information, the assistance information comprising at least one sidelink discontinuous reception (DRX) parameter indicated by the first device; the first information is configured for the second device or a network device to configure a sidelink DRX parameter for the first device.
In a second aspect, the present disclosure provides a resource allocation method, performed by a second device and comprising: receiving a first information from a first device; wherein the first information comprises an assistance information, the assistance information comprising at least one sidelink discontinuous reception (DRX) parameter indicated by the first device; the first information is configured for the second device or a network device to configure a sidelink DRX parameter for the first device.
In a third aspect, the present disclosure provides a first device, comprising: a transceiver, a processor, and a memory; wherein the memory stores a computer-executable instruction; the processor is configured to execute the computer-executable instruction stored in the memory, to be caused to perform the method in the first aspect.
The technical solutions in the present disclosure will be described below in conjunction with the accompanying drawings.
The information transmission method provided in the present disclosure may be applied to various communication systems, such as: a long term evolution (LTE) system, an LTE frequency division duplex (FDD) system, an LTE time division duplex (TDD), a universal mobile telecommunication system (UMTS), a worldwide interoperability for microwave access (WiMAX) communication system, a fifth generation (5G) mobile communication system or new radio access technology (NR). The 5G mobile communication system may include a non-standalone (NSA) network and/or a standalone (SA) network.
The information transmission method provided in the present disclosure may further be applied to machine type communication (MTC), long term evolution-machine (LTE-M), device to device (D2D) network, machine to machine (M2M) network, internet of things (IoT) network, or other networks. The IoT network may, for example, include Internet of Vehicles (IoV). The communication methods in the IoV system are collectively referred to as vehicle to other devices (vehicle to X, V2X, where X may represent anything). For example, the V2X may include: vehicle to vehicle (V2V) communication, vehicle to infrastructure (V2I) communication, vehicle to pedestrian (V2P) communication, or vehicle to network (V2N) communication, etc.
The information transmission method provided in the present disclosure may further be applied to future communication systems, such as a 6th generation mobile communication system, without limitation herein.
In the embodiments of the present disclosure, the terminal device may also be referred to as a user equipment (UE), an access terminal, a user unit, a user station, a mobile station, a mobile platform, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user device.
The terminal device may be a device that provides voice/data connectivity to a user, e.g., a handheld device, an in-vehicle device, etc. with wireless connectivity. Currently, some examples of the terminal may be: a mobile phone, a tablet computer (pad), a computer (e.g., laptop, PDA, etc.) with wireless transceiver functionality, a mobile internet device (MID), a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, a cellular telephone, a cordless telephone, a session initiation protocol (SIP) telephone, a wireless local loop (WLL) station, a personal digital assistant (PDA), handheld devices, computing devices with wireless communication capabilities, or other processing devices connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a 5G network, or a terminal device in a future evolved public land mobile network (PLMN).
Among them, the wearable device may also be called a wearable smart device, which is a general term for the application of wearable technology to intelligentize daily wear and develop wearable devices, such as glasses, gloves, watches, clothing, and shoes. The wearable device is a portable device that can be worn directly on the body or integrated into the user's clothing or accessories. The wearable device is not only a hardware device, but also can realize powerful functions through software support as well as data interaction and cloud interaction. Broadly speaking, the wearable smart device includes full-featured, large-sized devices that do not rely on smartphones to achieve complete or partial functionality, such as smartwatches or smart glasses, etc., as well as those that focus on a certain type of application functionality and is required to be used in conjunction with other devices such as smartphones, such as various types of smart bracelets and smart jewelry for monitoring physical signs.
In addition, the terminal device may be a terminal device in the Internet of things (IoT) system. IoT is an important part of the future development of information technology, and its main technical characteristic is to connect items with the network through communication technology, so as to realize an intelligent network with human-machine interconnection and thing-thing interconnection. IoT technology may be achieved through, for example, a narrow band (NB) technology, to achieve massive connectivity, deep coverage, and terminal power saving.
In addition, the terminal device may include sensors such as a smart printer, a train detector, a gas station, etc., and the main functions thereof include collecting data (for some terminal devices), receiving control information and downlink data from a network device, and sending electromagnetic waves to transmit uplink data to the network device.
In the embodiments of the present disclosure, the network device may be any kind of device with wireless transceiver function. The network device includes, but is not limited to: evolved Node B (eNB), radio network controller (RNC), Node B (NB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home evolved NodeB, or home Node B, HNB), baseband unit (BBU), access point (AP) in a wireless fidelity (Wi-Fi) system, wireless relay node, wireless backhaul node, transmission point (TP), or transmission and reception point (TRP), etc., gNB or transmission point (TRP or TP) in a 5G, e.g., NR, system, an antenna panel for one or a group (including multiple antenna panels) of a base station in the 5G system, or, network node that constitutes a gNB or a transmission point, e.g., a baseband unit (BBU) or a distributed unit (DU), and the like.
In some deployments, the gNB may include a centralized unit (CU) and a DU. The gNB may further include an active antenna unit (AAU). The CU implements some of the functionality of the gNB, and the DU implements some of the functionality of the gNB. For example, the CU may be responsible for handling non-real-time protocols and services, e.g., realizing the functions of radio resource control (RRC) layer, service data adaptation protocol (SDAP) layer, and/or packet data convergence protocol (PDCP) layer; the DU may be responsible for handling physical layer protocols and real-time services, e.g., realizing the functions of radio link control (RLC) layer, media access control (MAC) layer, and physical (PHY) layer. One DU can be connected to only one CU or to multiple CUs, while one CU can be connected to multiple DUs. The CU may communicate with the DU through the F1 interface. The AAU can realize some of the physical layer processing functions, RF processing, and active antenna related functions. Since the RRC layer information is eventually handed over to the PHY layer and thus becomes PHY layer information, or, is transformed from PHY layer information, in this architecture, high-level signaling, such as RRC layer signaling, can also be considered to be sent by DU, or, by DU and AAU.
It can be understood that the network device may be a device including one or more of a CU node, a DU node, and an AAU node. In addition, the CU may be classified as a network device in a radio access network (RAN), or the CU may be classified as a network device in a core network (CN), which is not limited by the present disclosure.
The network device provides services for the cell, and the terminal device communicates with the cell through transmission resources (e.g., frequency domain resources, or to say, spectrum resources) allocated by the network device. The cell may belong to a macro base station (e.g., a macro eNB or a macro gNB, etc.), or may belong to a base station corresponding to a small cell, where the small cell herein may include: metro cell, micro cell, pico cell, femto cell, etc. These small cells are characterized by a small coverage area, low transmit power, etc., and are suitable for providing a high-speed rate data transmission service.
To facilitate the understanding of the embodiments of the present disclosure, the following points are made.
In the embodiments of the present disclosure, the terms “system” and “network” are often used interchangeably herein. The term “and/or” merely describes an association relationship of associated objects, and indicates that three kinds of relationships may exist, e.g., A and/or B, which may be expressed as A alone, both A and B, and B alone. In addition, the character “/” herein generally indicates that the associated objects are in an “or” relationship.
The terms used in the embodiments of the present disclosure are intended only to explain specific embodiments of the present disclosure and are not intended to limit the present disclosure. The terms “first”, “second”, “third”, “fourth”, etc. in the specification, claims, and described drawings of the present disclosure are intended to distinguish between different objects and not to describe a particular order. In addition, the terms “including” and “having”, and any variations thereof, are intended to cover non-exclusive inclusion.
References to “instruction” in the embodiments of the present disclosure may be direct instruction, indirect instruction, or an indication of an associative relationship. For example, A instructing B may mean that A instructs B directly, such as B can be accessed through A; or that A instructs B indirectly, such as A instructs C and B can be accessed through C; or that there is an associative relationship between A and B.
In the embodiments of the present disclosure, the terms “corresponding” may indicate a direct or indirect corresponding relationship between the two, or an associated relationship between the two, or a relationship between instructing and being instructed, or configuring and being configured.
In the embodiments of the present disclosure, “predefined” or “pre-configured” may be realized by storing a corresponding code, form, or other means that can indicate relevant information in advance in a device (e.g., including a terminal device and a network device), and the present disclosure does not limit the specific ways of realization. For example, “predefined” may mean being defined in a protocol.
In the embodiments of the present disclosure, the “protocol” may refer to standard protocols in the field of communication, for example, LTE protocol, NR protocol, and relevant protocols applied in future communication systems, and the present disclosure does not limit in this regard.
In order to facilitate the understanding of the embodiments of the present disclosure, the application scenarios of the embodiments of the present disclosure are first described.
It is to be noted that the system architecture and the application scenarios described in the embodiments of the present disclosure are for the purpose of more clearly illustrating the technical solutions of the embodiments of the present disclosure, and do not constitute a limitation on the technical solutions provided in the embodiments of the present disclosure. Those skilled in the art may know that, with the evolution of the network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present disclosure are equally applicable to similar scenarios.
Unlike the traditional cellular system in which communication data is received or sent through a base station, D2D communication introduces sidelink transmission technology and adopts terminal-to-terminal direct communication, thereby providing higher frequency efficiency as well as lower transmission latency. The 3rd Generation Partnership Project (3GPP) defines two transmission modes: first transmission mode and second transmission mode.
Exemplarily, the terminal device 12 shown in
Exemplarily, the terminal device 12 shown in
In 3GPP, the research on D2D mainly includes the following stages:
NR-V2X is a communication scenario based on sidelink for communication. In NR-V2X communication, X can refer generically to any device with wireless receiving and transmitting capabilities, including but not limited to slow-moving wireless devices, fast-moving vehicle-mounted devices, and network control nodes with wireless transmitting and receiving capabilities.
NR-V2X communication supports unicast, multicast, and broadcast transmission. For unicast transmission, a sending terminal sends data and there is only one receiving terminal. For multicast transmission, the sending terminal sends data, and the receiving terminals are all the terminals within a communication group or within a certain transmission distance. For broadcast transmission, the sending terminal sends data and the receiving terminal is any terminal around the sending terminal.
Similar to LTE V2X, the NR V2X defines the two transmission modes described above.
Unlike LTE V2X, in addition to the feedback-free, UE-initiated hybrid automatic repeat request (HARQ), NR V2X introduces feedback-based HARQ retransmission, i.e., the sending device can determine whether data retransmission is required based on the feedback information from the receiving device. The feedback-based HARQ retransmission is not limited to unicast communication, but also includes multicast communication.
Same as LTE V2X, in the NR V2X, the power efficiency is not the main problem because the vehicle system can be continuously powered, while the delay of data transmission is the main problem. Therefore, the terminal device is required to send and receive continuously in the system design.
In wireless networks, when there is data to be transmitted, the UE is required to listen to the physical downlink control channel (PDCCH) all the time, and send and receive data according to an instruction message sent by the network side, such that the power consumption of the UE and the delay of the data transmission are relatively large. Therefore, the 3GPP standard protocol introduces a discontinuous reception (DRX) energy saving strategy.
The basic mechanism of DRX is to configure a DRX cycle for the UE in RRC_CONNECTED state. The DRX cycle consists of “On Duration” and “Opportunity for DRX”. The DRX cycle consists of “On Duration” and “Opportunity for DRX”: during the “On Duration” time (also known as active time), the UE listens and receives the PDCCH; during the “Opportunity for DRX” time (also known as inactive time), the UE does not receive the PDCCH to reduce power consumption. The “Opportunity for DRX” time can also be called “DRX off duration” compared to “DRX on duration”.
In DRX operation, the terminal controls the active time and inactive time of the terminal according to some timer parameters configured by the network. For example, when the UE receives a PDCCH from the network scheduling the UE during the On Duration period, the UE activates a timer, such as drx_inactiveTimer, and the terminal is in an active state until the timer expires.
The UE monitors the PDCCH discontinuously according to the DRX configuration for power saving purposes, and when the PDCCH carries C-RNTI, CI-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI, and AI-RNTI, the UE will conduct the corresponding DRX operation according to the control information.
The network controls the DRX behavior of the UE by configuring a series of parameters, which (Uu DRX parameters) include:
Among them, the UE will be in DRX-active state when at least one of the following cases is met:
In the listening process of NR V2X, the terminal is required to continuously listen for resources to determine which resources are available, and the terminal consumes too much energy. In order to achieve power saving, DRX mechanism is introduced in the sidelink system. Similar to the DRX mechanism of the Uu interface described above, the terminal receives data sent by other terminals within the On duration range, and when no data is detected, it enters the inactive state within the DRX off duration range to save power; when the data sent to the terminal by other terminals is detected, the terminal activates a timer, and the terminal is in the active state until the timer expires.
As shown in
The above sidelink DRX configuration has the following problems.
First, the first device does not know the data information (i.e., information such as traffic pattern) sent from the second device, and thus cannot accurately derive the sidelink DRX configuration parameter that match the sent data.
Second, after the first device rejects the sidelink DRX configuration, when the two parties have not been able to agree on the sidelink DRX configuration, the first device has to continuously listen, resulting in excessive energy consumption.
The embodiments of the present disclosure propose a resource allocation method. Considering that the first device is unaware of the data information sent from the second device, when the first device sends assistance information to the second device, a situation of values of at least one sidelink DRX parameter that can be accepted by the first device may be indicated, such as a value set or a value range. The assistance information may indicate a situation of value of each of the at least one sidelink DRX parameter, or may indicate situations of values of multiple sets of sidelink DRX parameters, each set including at least one sidelink DRX parameter. Based on the above setting of the content of the assistance information, the first device may effectively assist the second device in configuring the sidelink DRX parameters for the second device without being aware of the data information sent from the second device, so as to improve the success rate of the sidelink DRX configuration. Further, in order to reduce the power consumption of the first device, a timer or a counter may be set to control the maximum number of times or the maximum duration of the sidelink resource configuration to meet the power saving needs of the first device.
The technical solutions provided by the embodiments of the present disclosure are described in detail below by means of specific embodiments. It is noted that the technical solution provided by the embodiments of the present disclosure may include some or all of the following, and these following several specific embodiments may be combined with each other, and the same or similar concepts or processes may not be repeated in certain embodiments.
It should be noted that in the following embodiments, the first device is a receiver UE (RX UE), i.e., a UE that receives the sidelink DRX configuration, and the second device is a transmitter UE (TX UE), i.e., a UE that sends the sidelink DRX configuration.
In the embodiments, the first information is configured for the second device or a network device to configure a sidelink DRX parameter for the first device, and the network device herein refers to a network device to which the second device belongs. The second information includes the sidelink DRX parameter configured by the second device or the network device for the first device.
Specifically, the step 102 includes the following two implementations.
In one possible implementation, the second device configures the sidelink DRX parameter for the first device according to the first information, and the second device sends the second information to the first device, the second information including the sidelink DRX parameter configured by the second device for the first device.
In another possible implementation, the second device sends the first information to the network device to configure the sidelink DRX parameter for the first device according to the first information, and the second device sends the second information to the first device, the second information including the sidelink DRX parameter configured by the network device for the first device.
In some embodiments, the first information includes assistance information, the assistance information including at least one sidelink discontinuous reception (sidelink DRX) parameter indicated by the first device.
In some embodiments, the assistance information includes the at least one sidelink DRX parameter indicated by the first device, including: the assistance information includes a value range of the at least one sidelink DRX parameter indicated by the first device. In the embodiments, each sidelink DRX parameter is individually configured. For example, Parameter1=valueRange1, Parameter2=valueRange2, and so on.
In some embodiments, the assistance information includes the at least one sidelink DRX parameter indicated by the first device, including: the assistance information includes a value range or a value of each sidelink DRX parameter among each of multiple sets of sidelink DRX parameters indicated by the first device. In the embodiments, the sidelink DRX parameters are configured in combination. Accordingly, the second device or the network device selects one of the sets of sidelink DRX parameters and configures the at least one sidelink DRX parameter for the first device according to the value range of or value of the set of sidelink DRX parameters.
Exemplarily, the assistance information includes DesiredDRXSL1={Parameter1value1, Parameter2value2 . . . }, DesiredDRXSL2={Parameter1value3, Parameter2value4 . . . }, etc. The second device or network device selects DesiredDRXSL2 and configures Parameter1=value3, Parameter2=value4 for the first device.
Exemplarily, DesiredDRXSL1={Parameter1valueRange1, Parameter2valueRange2 . . . }, DesiredDRXSL2={Parameter1valueRange3, Parameter2valueRange4 . . . }, etc. The second device or network device selects DesiredDRXSL1 to configure Parameter1=valueRange1, Parameter2=valueRange2 for the first device.
In some embodiments, the assistance information includes the at least one sidelink DRX parameter indicated by the first device, including: the assistance information includes any one of the following data for each sidelink DRX parameter in the at least one sidelink DRX parameter indicated by the first device:
In some embodiments, the assistance information includes a maximum value of the at least one sidelink DRX parameter. For each sidelink DRX parameter, the second device or network device shall not configure a value that exceeds the maximum value of the sidelink DRX parameter.
In some embodiments, the assistance information includes a minimum value of the at least one sidelink DRX parameter. For each sidelink DRX parameter, the second device or network device shall not configure a value less than the minimum value of the sidelink DRX parameter.
In some embodiments, the assistance information includes maximum and minimum values of the at least one sidelink DRX parameter. For each sidelink DRX parameter, the second device or network device is required to configure a value between the minimum and maximum values of the sidelink DRX parameter.
In some embodiments, the assistance information includes a preset value and a float coefficient of the at least one sidelink DRX parameter. Exemplarily, a sidelink DRX parameter has a preset value of x and a float coefficient of 0.1, and the second device or the network device is required to configure a value of [0.9x, 1.1x] of the sidelink DRX parameter.
In some embodiments, the assistance information includes a value set of the at least one sidelink DRX parameter. Exemplarily, the value set of a sidelink DRX parameter is {x1,x2,x3}, and the second device or the network device is required to configure a value in the value set.
In the embodiments, the sidelink DRX parameter includes at least one of the following parameters: sl-drx-LongCycle, sl-drx-StartOffset, sl-drx-onDurationTimer, sl-drx-SlotOffset, sl-drx-InactivityTimer, sl-drx-RetransmissionTimer, sl-drx-HARQ-RTT-Timer.
In some embodiments, the first information further includes a first parameter of a first counter, the first parameter being configured to indicate a maximum number of times for the first device to reject the sidelink DRX configuration. In the embodiments, the first device sends the first information to the second device, the first information including the assistance information and the first parameter.
In some embodiments, the first device may further send the assistance information and the first parameter to the second device separately.
It should be noted that the first counter may be understood as a sidelink counter, and the first counter may be arranged in both the first device and the second device in sidelink communication. The first counter is configured to record the number of times that the first device rejects the sidelink DRX configuration of the second device or the network device.
In some embodiments, the first device sends the first information to the second device, the first information including the first parameter of the first counter, and the first device may set an initial value of the first counter to be 0.
In some embodiments, the second device sends the second information to the first device, and the second device may set an initial value of the first counter to be 0.
In some embodiments, the first parameter is pre-configured, or configured by network, or instructed by an upper layer, or determined by the first device, for which the embodiments of the present disclosure are not specifically limited.
In the above embodiments, the first device and the second device are each arranged with the first counter, which is configured to record the number of times that the first device rejects the sidelink DRX configuration, and also to control the number of failures of the sidelink DRX configuration, as described in the later embodiments.
In some embodiments, the first information further includes a second parameter of the first timer, the second parameter being configured to indicate a maximum duration for the first device to receive the sidelink DRX configuration. In the embodiments, the first device sends the first information to the second device, the first information including the assistance information and the second parameter.
In some embodiments, the first device may further send the assistance information and the second parameter to the second device separately.
It is to be noted that the first timer may be understood as a sidelink timer, and the first timer may be arranged in both the first device and the second device in sidelink communication, and the first timer is configured to record the duration of the sidelink DRX configuration.
In some embodiments, the first device sends the first information to the second device for the first time, the first information including the second parameter of the first timer, and the first device may turn on the first timer.
In some embodiments, the first device sends a first instruction information to the second device for the first time, and the first device may turn on the first timer. The first instruction information is configured to indicate that the first device rejects the sidelink DRX configuration.
In some embodiments, the second device receives the first information sent by the first device for the first time, the first information including the second parameter of the first timer, and the second device may turn on the first timer.
In some embodiments, the second device receives the first instruction information from the first device for the first time, and the second device may turn on the first timer. The first instruction information is configured to indicate that the first device rejects the sidelink DRX configuration.
In some embodiments, the second parameter is pre-configured, or configured by network, or instructed by an upper layer, or determined by the first device.
In the above embodiments, the first device and the second device turn on the first timer for controlling the duration of the sidelink DRX configuration in addition to recording the duration of the sidelink DRX configuration, as can be seen in later embodiments.
The embodiments of the present disclosure illustrate a resource configuration method, where the first device sends a first information to the second device, the first information being configured for the second device or the network device to configure a sidelink DRX parameter for the first device; the first information includes an assistance information, the assistance information including at least one sidelink DRX parameter indicated by the first device. The above method may assist the second device or the network device in configuring accurate sidelink DRX parameters for the first device, for improving the success rate of sidelink DRX configuration, thereby improving the quality of sidelink communication.
It is to be noted that in the following embodiments, the first network device is a network device to which the first device belongs, the second network device is a network device to which the second device belongs, and the first network device and the second network device may be the same or different network devices.
In some embodiments, the first information includes an assistance information and a first parameter of a first counter.
In some embodiments, the first device may send the assistance information and the first parameter of the first counter to the second device separately. In some embodiments, when the first device is in a connected state, the first device may further send the first parameter of the first counter to a first network device.
The assistance information includes at least one sidelink discontinuous reception (sidelink DRX) parameter indicated by the first device. The first parameter, i.e., a maximum value of the first counter, is configured to indicate a maximum number of times that the first device rejects the sidelink DRX configuration. Specifics regarding the assistance information, the first counter, and the first parameter may be found in the embodiments above and will not be repeated herein.
In some embodiments, when the second device is in a connected state, the second device, after receiving the first information, may report the received first information to a second network device, and the second network device may configure the sidelink DRX parameter for the first device according to the first information.
In some embodiments, when the second device is in a connected state, the second device may receive the second information from the second network device, the second information including the sidelink DRX parameter configured by the second network device for the first device.
In some embodiments, the second device configures the sidelink DRX parameter for the first device according to the first information and sends the second information to the first device, the second information including the sidelink DRX parameter configured by the second device for the first device.
In some embodiments, when the first device is in a connected state, the first device reports the second information to the first network device. The first network device sends the feedback information of the second information to the first device, the feedback information including an instruction of receiving or rejecting the sidelink DRX configuration.
In some embodiments, the first device determines to receive or reject the sidelink DRX configuration according to its own implementation.
In some embodiments, the first device determines to receive or reject the sidelink DRX configuration according to the feedback information of the second information from the first network device.
When the current value of the first counter is less than or equal to the first parameter, step 211 is performed. When the current value of the first counter is greater than the first parameter, the first device may release the sidelink (not shown) with the second device.
In the embodiments, the first instruction information is configured to indicate that the first device rejects the sidelink DRX configuration. The first instruction information may also be referred to as a rejection instruction.
In some embodiments, the first instruction information includes at least one of the following:
In some embodiments, the first instruction information further includes a reason for the first device to reject the sidelink DRX parameter configuration.
In some embodiments, the reason for the first device to reject the sidelink DRX parameter configuration includes that: the first device does not receive the sidelink DRX configuration (i.e., the second information does not include the sidelink DRX configuration), or the sidelink DRX configuration in the second information does not correspond to the desired sidelink DRX configuration indicated by the first information.
In some embodiments, when the first device determines to reject the sidelink DRX configuration, it may directly send the first instruction information to the second device.
In some embodiments, when the second device is in a connected state, the second device sends the first instruction information to the second network device, such that the second network device is informed of that the first device rejects the sidelink DRX parameter configuration.
In some embodiments, when the current value of the first counter is less than the first parameter, the first device sends the first information to the second device again. The fact that the current value of the first counter is less than its maximum value indicates that the number of failures of the sidelink DRX configuration of the first device has not yet reached the maximum number of failures, and thus the first device may resend the first information to assist the second device or the second network device in configuring the sidelink DRX parameter for the first device.
It should be noted that the order of execution of the various steps in the embodiments is only for example and should not constitute any limitation of the present disclosure.
The embodiments of the present disclosure illustrate a resource allocation method, where the first device sends a first information to the second device, and the first device receives a second information from the second device, the second information including a sidelink DRX parameter configured by the second device or the second network device for the first device; and when the first device determines to reject the sidelink DRX configuration and a current value of the first counter is less than or equal to a first parameter, the first device sends a first instruction information to the second device, the first instruction information for instructing that the first device rejects the sidelink DRX configuration. In the embodiments, the first device controls the number of times the sidelink DRX configuration is rejected by the first counter, such that when a resource allocator and a resource allocation receiver (e.g., the second device and the first device or, alternatively, the second network device and the first device) have not been able to reach an agreement on the sidelink DRX configuration, a power saving need of the first device can be met by setting the counter.
In some embodiments, the first information includes an assistance information and a second parameter of a first timer.
In some embodiments, the first device may send the assistance information and the second parameter of the first timer to the second device separately. In some embodiments, when the first device is in a connected state, the first device may further send the second parameter of the first timer to a first network device.
The assistance information includes at least one sidelink discontinuous reception (sidelink DRX) parameter indicated by the first device. The second parameter, i.e., a maximum duration of the first timer, is configured to record a duration of the sidelink DRX configuration. Specifics regarding the assistance information, the first timer, and the second parameter may be found in the embodiments above and will not be repeated herein.
In some embodiments, when the second device is in a connected state, the second device, after receiving the first information, may report the received first information to the second network device, and the second network device may configure the sidelink DRX parameter for the first device according to the first information.
In some embodiments, when the second device is in a connected state, the second device may receive the second information from the second network device, the second information including the sidelink DRX parameter configured by the second network device for the first device.
In some embodiments, the second device configures the sidelink DRX parameter for the first device according to the first information and sends the second information to the first device, the second information including the sidelink DRX parameter configured by the second device for the first device.
In some embodiments, when the first device is in a connected state, the first device reports the second information to the first network device. The first network device sends the feedback information of the second information to the first device, the feedback information including an instruction of receiving or rejecting the sidelink DRX configuration.
In some embodiments, the first device determines to receive or reject the sidelink DRX configuration according to its own implementation.
In some embodiments, the first device determines to receive or reject the sidelink DRX configuration according to the feedback information of the second information from the first network device.
In the embodiments, when the first timer has not timed out, step 310 is performed. When the first timer times out, the first device may release the sidelink (not shown) with the second device.
In the embodiments, the first instruction information is configured to indicate that the first device rejects the sidelink DRX configuration.
In some embodiments, the first instruction information includes at least one of the following:
In some embodiments, the first instruction information further includes a reason for the first device to reject the sidelink DRX parameter configuration.
In some embodiments, when the first device determines to reject the sidelink DRX configuration, it may directly send the first instruction information to the second device.
In some embodiments, when the second device is in a connected state, the second device sends the first instruction information to the second network device, such that the second network device is informed of that the first device rejects the sidelink DRX parameter configuration.
In some embodiments, when the first timer has not timed out, the first device sends the first information to the second device again. The fact that the first timer has not timed out indicates that the duration for the first device to receive the sidelink DRX configuration has not reached the maximum duration, and thus the first device may resend the first information to assist the second device or the second network device in configuring the sidelink DRX parameter for the first device.
It should be noted that the order of execution of the various steps in the embodiments is only for example and should not constitute any limitation of the present disclosure.
The embodiments of the present disclosure illustrate a resource allocation method, where the first device sends a first information to the second device, and the first device receives a second information from the second device, the second information including a sidelink DRX parameter configured by the second device or the second network device for the first device; and when the first device determines to reject the sidelink DRX configuration and a first timer is not timed out, the first device sends a first instruction information to the second device, the first instruction information for instructing that the first device rejects the sidelink DRX configuration. In the embodiments, the first device controls whether or not to send the instruction of rejecting the sidelink DRX configuration through the first timer, such that when a resource allocator and a resource allocation receiver (e.g., the second device and the first device or, alternatively, the second network device and the first device) have not been able to reach an agreement on the sidelink DRX configuration, a power saving need of the first device can be met by setting the timer.
In some embodiments, the first information includes an assistance information and a first parameter of a first counter.
In some embodiments, the first device may send the assistance information and the first parameter of the first counter to the second device separately. In some embodiments, when the first device is in a connected state, the first device may further send the first parameter of the first counter to a first network device.
In some embodiments, the first information includes an assistance information and a second parameter of a first timer.
In some embodiments, the first device may send the assistance information and the second parameter of the first timer to the second device separately. In some embodiments, when the first device is in a connected state, the first device may further send the second parameter of the first timer to a first network device.
The assistance information includes at least one sidelink discontinuous reception (sidelink DRX) parameter indicated by the first device. The first parameter, i.e., a maximum value of the first counter, is configured to indicate a maximum number of times that the first device rejects the sidelink DRX configuration. The second parameter, i.e., a maximum duration of the first timer, is configured to record a duration of the sidelink DRX configuration. Specifics regarding the assistance information, the first counter, the first parameter, the first timer, and the second parameter may be found in the embodiments above and will not be repeated herein.
In some embodiments, when the second device is in a connected state, the second device, after receiving the first information, may report the received first information to the second network device, and the second network device may configure the sidelink DRX parameter for the first device according to the first information.
In some embodiments, when the second device is in a connected state, the second device may receive the second information from the second network device, the second information including the sidelink DRX parameter configured by the second network device for the first device.
In some embodiments, the second device configures the sidelink DRX parameter for the first device according to the first information and sends the second information to the first device, the second information including the sidelink DRX parameter configured by the second device for the first device.
In some embodiments, when the first device is in a connected state, the first device reports the second information to the first network device. The first network device sends the feedback information of the second information to the first device, the feedback information including an instruction of receiving or rejecting the sidelink DRX configuration.
When any one of the first conditions is met, step 408 is performed.
In some embodiments, the first conditions include that: a current value of the first counter is greater than a first parameter of the first counter; or the first timer times out; or the first device determines according to its own implementation.
In the embodiments, the second instruction information is configured to instruct the second device to release the sidelink with the first device. The second instruction information may also be referred to as a release instruction.
In some embodiments, the second instruction information is carried in a PC5 secure (PC5-S) signaling or a PC5 radio resource control (RRC) signaling.
In some embodiments, when the first device determines that the current value of the first counter is greater than the first parameter, the first device sends the second instruction information to the second device, and/or, releases the sidelink with the second device.
In some embodiments, when the first device determines that the first timer has timed out, the first device sends the second instruction information to the second device, and/or, releases the sidelink with the second device.
In some embodiments, when the first device determines to release the sidelink according to its own implementation, the first device sends the second instruction information to the second device, and/or, releases the sidelink with the second device.
In some embodiments, the sidelink release may be a PC5-S link release, or, a PC5 RRC link release.
As can be seen from the above embodiments, the first device may only send the second instruction information to the second device, or, directly release the sidelink with the second device without sending the second instruction information, or, release the sidelink with the second device after sending the second instruction information. Power saving is thus achieved by releasing the sidelink.
In some embodiments, the second device receives the second instruction information from the first device, and/or, releases the sidelink with the first device.
In some embodiments, when the second device determines that the current value of the first counter is greater than the first parameter, and/or, the second device receives the second instruction information from the first device, the second device releases the sidelink with the first device.
In some embodiments, when the second device determines that the first timer times out, and/or, the second device receives the second instruction information from the first device, the second device releases the sidelink with the first device.
In the embodiments, the third information is configured to indicate that the first device has released the sidelink with the second device.
In the embodiments, the fourth information is configured to indicate that the second device has released the sidelink with the first device.
It should be noted that the order of execution of the various steps in the embodiments is only for example and should not constitute any limitation of the present disclosure.
The embodiments of the present disclosure illustrate a resource allocation method, where the first device sends a first information to the second device, and the first device receives a second information from the second device, the second information including a sidelink DRX parameter configured by the second device or the second network device for the first device. When a current value of the first counter is greater than a maximum value, or, the first timer times out, or, the first device determines that the sidelink is required to be released according to its own implementation, the first device sends a second instruction information to the second device, the second instruction information for instructing that the second device releases the sidelink with the first device. The first device may send only the second instruction information, or may directly release the sidelink with the second device without sending the second instruction information, or may release the sidelink with the second device after sending the second instruction information. The above embodiments have the following beneficial effect: when a resource allocator and a resource allocation receiver (e.g., the second device and the first device or, alternatively, the second network device and the first device) have not been able to reach an agreement on the sidelink DRX configuration, a power saving need of the first device can be met by setting the timer.
Based on each of the above embodiments, in some embodiments, when the first device determines to reject the sidelink DRX parameter configuration, the first device may send the first instruction information and the second instruction information separately, or, the first device may send the first instruction information and the second instruction information at the same time.
Steps 501 to step 506 of the present embodiments are similar to steps 401 to step 406 of the above embodiments, which may be seen in the above embodiments, and will not be repeated herein.
When any one of the first conditions is met, step 508 is performed.
In some embodiments, the first conditions include that: a current value of the first counter is greater than a first parameter of the first counter; or the first timer times out; or the first device determines according to its own implementation.
In the embodiments, the third instruction information is configured to indicate that the first device falls back to a default sidelink DRX configuration. The third instruction information may also be referred to as a fallback indication.
In some embodiments, the default sidelink DRX parameter includes any of the following:
In some embodiments, the third instruction information is carried in a medium access control control element (MAC CE), a PC5 RRC signaling, or a physical layer signaling.
In some embodiments, when the first device determines that the current value of the first counter is greater than the first parameter, the first device sends the third instruction information to the second device, and/or, sets the sidelink DRX parameter of the first device to the default sidelink DRX parameter (i.e., the first device adopts the default sidelink DRX parameter for the sidelink communication with the second device).
In some embodiments, when the first device determines that the first timer has timed out, the first device sends the third instruction information to the second device, and/or, sets the sidelink DRX parameter of the first device to the default sidelink DRX parameter.
In some embodiments, when the first device determines to fall back to the default sidelink DRX parameter according to its own implementation, the first device sends the third instruction information to the second device, and/or, sets the sidelink DRX parameter of the first device to the default sidelink DRX parameter.
As can be seen from the above embodiments, instead of releasing the sidelink with the second device, the first device may fall back to the default sidelink DRX parameter configuration, and the first device sends the third instruction information to the second device instructing the second device to communicate with the first device in sidelink using the default sidelink DRX parameter. There is no need for the second device or the second network device to configure the sidelink DRX parameter to the first device again.
In some embodiments, the second device receives the third instruction information from the first device, and/or, performs the sidelink communication with the first device using the default sidelink DRX parameter.
In some embodiments, when the second device determines that the current value of the first counter is greater than the first parameter, and/or, the second device receives the third instruction information from the first device, the second device performs the sidelink communication with the first device using the default sidelink DRX parameter.
In some embodiments, when the second device determines that the first timer times out, and/or, the second device receives the third instruction information from the first device, the second device performs the sidelink communication with the first device using the default sidelink DRX parameter.
It should be noted that the order of execution of the various steps in the embodiments is only for example and should not constitute any limitation of the present disclosure.
The embodiments of the present disclosure illustrate a resource allocation method, where the first device sends a first information to the second device, and the first device receives a second information from the second device, the second information including a sidelink DRX parameter configured by the second device or the second network device for the first device. When a current value of the first counter is greater than a maximum value, or, the first timer times out, or, the first device determines to fall back to the default sidelink DRX parameter according to its own implementation, the first device sends a third instruction information to the second device, the third instruction information for indicating that the first device falls back to the default sidelink DRX configuration, and the first device and the second device perform sidelink communication using the default sidelink DRX configuration. The above embodiments have the following beneficial effect: when a resource allocator and a resource allocation receiver (e.g., the second device and the first device or, alternatively, the second network device and the first device) have not been able to reach an agreement on the sidelink DRX configuration, a power saving need of the first device can be met by setting the timer.
In the embodiments, the first information does not include an assistance information.
In the embodiments, the fifth information is configured to indicate that the second device does not receive the assistance information.
In some embodiments, when the first information does not include the assistance information, the second device sends the fifth information to the second network device.
In some embodiments, when the first information does not include the assistance information, the second device waits for a second duration after receiving the first information to send the fifth information to the second network device. The purpose of the second device waiting for the second duration is to extend a time for receiving the assistance information.
In some embodiments, when the first information does not include the assistance information, the second device directly sends the fifth information to the second network device after receiving the first information.
In some embodiments, the second duration is configured by network, or configured by the first device, or instructed by an upper layer, or a duration until the second device receives the assistance information.
In some embodiments, the second device sends the second duration to the first device, and the first device is required to send the assistance information to the second device within the second duration (when the first device requires the sidelink DRX configuration).
In some embodiments, the second network device sends the second information to the second device after receiving the fifth information, the second information including a sidelink DRX parameter configured by the second network device for the first device, i.e., the second network device may configure the sidelink DRX parameter for the first device when not receiving the assistance information.
In some embodiments, the second network device sends the second information to the second device after receiving the fifth information, the second information not including a sidelink DRX parameter configured by the second network device for the first device.
In some embodiments, the second device receives the second information from the second network device and sends the second information to the first device. The second information includes or does not include the sidelink DRX parameter configured by the second network device for the first device.
In some embodiments, the second information includes or does not include sidelink DRX parameter configured by the second device for the first device.
In some embodiments, when the second information does not include the sidelink DRX parameter configured by the second device or the second network device for the first device, the second device adds one to a current value of a first counter.
In some embodiments, when the first information does not include the assistance information, the second device waits for a second duration after receiving the first information to send the second information to the first device.
In some embodiments, when the first information does not include the assistance information, the second device directly sends the second information to the first device after receiving the first information.
In some embodiments, when the first information does not include the assistance information, the second device sends the fifth information to the second network device, and the second device sends the second information to the first device.
In the embodiments, the fifth instruction information is configured to indicate that the first device has not received the sidelink DRX configuration.
In some embodiments, when the second information does not include the sidelink DRX configuration, the first device sends the fifth instruction information to the first network device.
In some embodiments, when the second information does not include the sidelink DRX configuration, the first device waits for a first duration after receiving the second information to send the fifth instruction information to the first network device. The purpose of the first device waiting for the first duration is to extend a time for receiving the sidelink DRX configuration.
In some embodiments, when the second information does not include the sidelink DRX configuration, the first device sends the fifth instruction information directly to the first network device after receiving the second information.
In some embodiments, the first duration is configured by network, or configured by the second device, or instructed by an upper layer, or a duration until the first device receives the sidelink DRX configuration.
In some embodiments, the first device sends the first duration to the second device. The second device is required to configure the sidelink DRX parameter for the first device within the first duration.
In some embodiments, when the second information does not include the sidelink DRX configuration, the first device sends the first information to the second device again.
In some embodiments, when the second information does not include the sidelink DRX configuration, the first device waits for a first duration after receiving the second information to send the first information to the second device again.
In some embodiments, when the second information does not include the sidelink DRX configuration, the first device sends the first information directly to the second device after receiving the second information.
In some embodiments, when the second information does not include the sidelink DRX configuration, the first device may perform at least one of the following steps.
The feedback information may carry the first instruction information (i.e., a rejection instruction) as described above.
In some embodiments, when the second information does not include the sidelink DRX configuration, the first device waits for a first duration after receiving the second information to send the feedback information of the second information to the second device.
In some embodiments, when the second information does not include the sidelink DRX configuration, the first device sends the feedback information of the second information directly to the second device after receiving the second information.
In some embodiments, when the second information does not include the sidelink DRX configuration, the first device adds one to a current value of the first counter.
In some embodiments, when the second information does not include the sidelink DRX configuration, the first device turns on a first timer.
It should be noted that the order of execution of the various steps in the embodiments is only for example and should not constitute any limitation of the present disclosure.
The embodiments of the present disclosure illustrate a resource allocation method, where the second device may wait for a second duration when the second device does not receive an assistance information from the first device, and when the second device still does not receive the assistance information, the second device sends a second information to the first device, the second information including or not including the sidelink DRX configuration. When the second information includes the sidelink DRX configuration, the configuration is not based on the assistance information. When the second information does not include the sidelink DRX configuration, the first device may wait for a first duration, and when the first device still does not receive the sidelink DRX configuration, the first device sends a first information including the assistance information to the second device again, or, the first device sends a fifth instruction information to the first network device indicating that the first device has not received the sidelink DRX configuration. The above-described scheme may increase the flexibility of the sidelink device to receive information.
Based on each of the above embodiments, in some embodiments, the second device may send a first request to the first device, the first request being configured to trigger the first device to send the first information. That is, the first device may send the first information to the second device based on the triggering request of the second device.
In some embodiments, the first request may be a 1-bit indication, e.g., 1 indicates triggering the first device to send the first information, and 0 indicates not triggering the first device to send the first information.
In some embodiments, the first request carries information about data sent from the second device (i.e., information such as traffic pattern).
The resource allocation methods provided by the embodiments of the present disclosure are described in detail above, and sidelink devices provided by the embodiments of the present disclosure, including the first device and the second device, will be described below.
The sending module 701 is configured to send a first information to a second device; where the first information includes an assistance information, the assistance information including at least one sidelink discontinuous reception (DRX) parameter indicated by the first device; the first information is configured for the second device or a network device to configure a sidelink DRX parameter for the first device.
In some embodiments, the assistance information includes at least one sidelink DRX parameter indicated by the first device, including
In some embodiments, the assistance information includes at least one sidelink DRX parameter indicated by the first device, including
In some embodiments, the assistance information includes at least one sidelink DRX parameter indicated by the first device, including:
In some embodiments, the first information further includes a first parameter of a first counter, the first parameter being configured to indicate a maximum number of times the first device rejects the sidelink DRX configuration.
In some embodiments, the sending module 701 is further configured to:
In some embodiments, the first parameter is pre-configured, or configured by network, or instructed by an upper layer, or determined by the first device.
In some embodiments, the processing module 702 is configured to:
In some embodiments, the first information further includes a second parameter of a first timer, the second parameter being configured to indicate a maximum duration for the first device to receive the sidelink DRX configuration.
In some embodiments, the sending module 701 is further configured to:
In some embodiments, the second parameter is pre-configured, or configured by network, or instructed by an upper layer, or determined by the first device.
In some embodiments, the processing module 702 is further configured to turn on or restart the first timer.
In some embodiments, the receiving module 703 is configured to:
In some embodiments, the sending module 701 is configured to:
In some embodiments, the first instruction information includes at least one of the following.
In some embodiments, the first instruction information includes at least one of the following.
In some embodiments, the first instruction information further includes a reason for the first device to reject the sidelink DRX parameter configuration.
In some embodiments, the first instruction information is carried in a medium access control control element (MAC CE), a PC5 radio resource control (RRC) signaling, or a physical layer signaling.
In some embodiments, the sending module 701 is further configured to:
In some embodiments, the processing module 702 is further configured to add one to the current value of the first counter.
In some embodiments, the sending module 701 is further configured to send the first information to the second device again.
In some embodiments, the sending module 701 is further configured to send a second instruction information to the second device, and/or, the processing module 702 is further configured to release a sidelink with the second device; the second instruction information is configured to instruct the second device to release the sidelink with the first device.
In some embodiments, the sending module 701 is further configured to send the second instruction information to the second device, and/or, the processing module 702 is further configured to release the sidelink with the second device, in response to any one of first conditions being met.
The first conditions include that: a current value of the first counter is greater than a first parameter of the first counter; or the first timer times out; or the first device determines according to its own implementation.
In some embodiments, the second instruction information is carried in a PC5 secure signaling or a PC5 RRC signaling.
In some embodiments, the sending module 701 is further configured to:
In some embodiments, the sending module 701 is further configured to send a third instruction information to the second device, and/or, the processing module 702 is further configured to set the sidelink DRX parameter of the first device to a default sidelink DRX parameter; the third instruction information being configured to indicate that the first device falls back to the default sidelink DRX configuration.
In some embodiments, the sending module 701 is further configured to send the third instruction information to the second device, and/or, the processing module 702 is further configured to set the sidelink DRX parameter of the first device to the default sidelink DRX parameter, in response to any one of first conditions being met.
The first conditions include that: a current value of the first counter is greater than a first parameter of the first counter; or the first timer times out; or the first device determines according to its own implementation.
In some embodiments, the default sidelink DRX parameter includes any one of the following:
In some embodiments, the third instruction information is carried in a MAC CE, a PC5 RRC signaling, or a physical layer signaling.
In some embodiments, in response to the second information not including the sidelink DRX configuration, the sending module 701 is further configured to perform at least one of the following steps:
In some embodiments, the sending module 701 is further configured to:
In some embodiments, the sending module 701 is further configured to:
In some embodiments, the sending module 701 is further configured to:
In some embodiments, the first duration is configured by network, or configured by the second device, or instructed by an upper layer, or a duration until the first device receives the sidelink DRX configuration.
The first device provided in the above embodiments may be configured to perform the method performed by the first device in any of the method embodiments described above, which are similar in principle of realization and technical effect, which will not be repeated herein.
The receiving module 801 is configured to receive a first information from a first device; where the first information includes an assistance information, the assistance information including at least one sidelink discontinuous reception (DRX) parameter indicated by the first device; the first information is configured for the second device or a network device to configure a sidelink DRX parameter for the first device.
In some embodiments, the assistance information includes at least one sidelink DRX parameter indicated by the first device, including:
In some embodiments, the assistance information includes at least one sidelink DRX parameter indicated by the first device, including:
In some embodiments, the assistance information includes at least one sidelink DRX parameter indicated by the first device, including
In some embodiments, the first information further includes a first parameter of a first counter, the first parameter being configured to indicate a maximum number of times the first device rejects the sidelink DRX configuration.
In some embodiments, the receiving module 801 is further configured to:
In some embodiments, the first parameter is pre-configured, or configured by network, or instructed by an upper layer, or determined by the first device.
In some embodiments, the processing module 802 is configured to: set an initial value of the first counter to be 0. The first counter is configured to record the number of times the first device rejects the sidelink DRX configuration.
In some embodiments, the first information further includes a second parameter of a first timer, the second parameter being configured to indicate a maximum duration for the first device to receive the sidelink DRX configuration.
In some embodiments, the receiving module 801 is further configured to:
In some embodiments, the second parameter is pre-configured, or configured by network, or instructed by an upper layer, or determined by the first device.
In some embodiments, the processing module 802 is further configured to turn on or restart the first timer.
In some embodiments, the sending module 803 is configured to send a second information to the first device, the second information including a sidelink DRX parameter configured by the second device or the network device for the first device.
In some embodiments, the receiving module 801 is further configured to receive a first instruction information from the first device, the first instruction information being configured to indicate that the first device rejects the sidelink DRX parameter configuration.
In some embodiments, the first instruction information includes at least one of the following.
In some embodiments, the first instruction information includes at least one of the following.
In some embodiments, the first instruction information further includes a reason for the first device to reject the sidelink DRX configuration.
In some embodiments, the first instruction information is carried in a medium access control control element (MAC CE), a PC5 radio resource control (RRC) signaling, or a physical layer signaling.
In some embodiments, the processing module 802 is further configured to add one to the current value of the first counter.
In some embodiments, the receiving module 801 is further configured to receive the first information from the first device again.
In some embodiments, the receiving module 801 is further configured to receive a second instruction information from the first device, and/or, the processing module 802 is further configured to release a sidelink with the first device; the second instruction information is configured to instruct the second device to release the sidelink with the first device.
In some embodiments, the second instruction information is carried in a PC5 secure signaling or a PC5 RRC signaling.
In some embodiments, the sending module 803 is further configured to send a fourth information to the network device, the fourth information being configured to indicate that the second device has released the sidelink with the first device.
In some embodiments, the receiving module 801 is further configured to receive a third instruction information from the first device, and/or, the processing module 802 is further configured to perform sidelink communication with the first device using a default sidelink DRX parameter; the third instruction information being configured to indicate that the first device falls back to the default sidelink DRX configuration.
In some embodiments, the default sidelink DRX parameter includes any of the following:
In some embodiments, the third instruction information is carried in a MAC CE, a PC5 RRC signaling, or a physical layer signaling.
In some embodiments, the sending module 803 is further configured to:
In some embodiments, the sending module 803 is further configured to:
In some embodiments, the sending module 803 is further configured to:
In some embodiments, the second duration is configured by network, or configured by the first device, or instructed by an upper layer, or a duration until the second device receives the assistance information.
The second device provided in the embodiments may be configured to perform the method performed by the second device in any of the method embodiments described above, which are similar in principle of realization and technical effect, which will not be repeated herein.
The memory 903 stores computer execution instructions.
The processor 902 executes the computer execution instructions stored in the memory 903, causing the processor 902 to execute the technical solution of the first device as in any of the preceding method embodiments.
In some embodiments, the memory 903 may be either stand-alone or integrated with the processor 902. When the memory 903 is a device independent of the processor 902, the electronic device 900 may further include: a bus 904 for connecting the memory 903 to the processor 902.
In some embodiments, the processor 902 may be a chip.
The present disclosure further provides a computer-readable storage medium, the computer-readable storage medium having computer-executable instructions stored therein. When the computer-executable instructions are executed by a processor, the processor is caused to implement the technical solution of the first device in any of the preceding method embodiments.
The embodiments of the present disclosure further provide a program. When the program is executed by a processor, the processor is caused to implement the technical solution of the first device in any of the preceding method embodiments.
The embodiments of the present disclosure further provide a computer program product including program instructions, the program instructions being configured to implement the technical solution of the first device in any of the preceding method embodiments.
The embodiments of the present disclosure further provide a chip including: a processing module and a communication interface, the processing module being capable of implementing the technical solution of the first device in any of the preceding method embodiments. Further, the chip further includes a storage module (e.g., a memory), the storage module for storing instructions, and the processing module for executing the instructions stored in the storage module. The execution of the instructions stored in the storage module causes the processing module to execute the technical solution of the first device.
The memory 1003 stores computer execution instructions.
The processor 1002 executes the computer-executed instructions stored in the memory 1003, causing the processor 1002 to execute the technical solution of the second device as in any of the preceding method embodiments.
In some embodiments, the memory 1003 may be either stand-alone or integrated with the processor 1002. When the memory 1003 is a device independent of the processor 1002, the electronic device 1000 may further include: a bus 1004 for connecting the memory 1003 to the processor 1002.
In some embodiments, the processor 1002 may be a chip.
The present disclosure further provides a computer-readable storage medium, the computer-readable storage medium having computer-executable instructions stored therein. When the computer-executable instructions are executed by a processor, the processor is caused to implement the technical solution of the second device in any of the preceding method embodiments.
The embodiments of the present disclosure further provide a program. When the program is executed by a processor, the processor is caused to implement the technical solution of the second device in any of the preceding method embodiments.
The embodiments of the present disclosure further provide a computer program product including program instructions, the program instructions being configured to implement the technical solution of the second device in any of the preceding method embodiments.
The embodiments of the present disclosure further provide a chip including: a processing module and a communication interface, the processing module being capable of implementing the technical solution of the second device in any of the preceding method embodiments. Further, the chip further includes a storage module (e.g., a memory), the storage module for storing instructions, the processing module for executing the instructions stored in the storage module. The execution of the instructions stored in the storage module causes the processing module to execute the technical solution of the second device.
It is to be noted that the above division of the various modules of the first device or the second device is merely a logical functional division, and that the actual realization may be fully or partially integrated into a physical entity, or may be physically separated. And these modules may all be realized in the form of software invoked through a processing element; be realized in the form of hardware; partially in the form of software invoked through the processing element, and partially realized in the form of hardware. For example, the processing module may be a separately established processing element, or it may be realized by integrating it in a certain chip of the above apparatus, and furthermore, it may be stored in the form of a program code in the memory of the above apparatus, which is invoked by a certain processing element of the above apparatus and carries out the functions of the determining module. Other modules are realized similarly. In addition, all or some of these modules may be integrated together or may be realized independently. The processing element described herein may be an integrated circuit with signal processing capability. In the realization, the steps of the method described above or each of the above modules may be accomplished by integrated logic circuits of hardware in the processor element or by instructions in the form of software.
For example, these modules may be one or more integrated circuits configured to implement the method described above, such as: one or more application specific integrated circuits (ASICs), one or more microprocessors (digital signal processors (DSPs), or one or more field programmable gate arrays (FPGAs), etc. For example, when one of the above modules is implemented in the form of a processing element scheduling a program code, the processing element may be a general purpose processor, such as a central processing unit (CPU) or other processor that can invoke the program code. Further, the modules may be integrated together and implemented as a system-on-a-chip (SOC).
In the above embodiments, the implementation may be in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. Loading and executing the computer program instructions on a computer produces, in whole or in part, a process or function in accordance with the embodiments of the present disclosure. The computer may be a general-purpose computer, a specialized computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, e.g., the computer instructions may be transmitted by wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means from one website site, computer, server, or data center to another website site, computer, server or data center. The computer-readable storage medium may be any usable medium to which a computer has access or a data storage device such as a server, data center, etc. containing one or more usable media integrated. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk solid state disk (SSD)), and the like.
In the present disclosure, “at least two” means two or more, and “more than one” means two or more. The character “and/or” describes an association relationship of associated objects, indicating that three relationships may exist, for example, A and/or B, which may indicate: the existence of A alone, the existence of both A and B, and the existence of B alone, where A and B may be singular or plural. The character “/” generally indicates that the objects associated before and after are in an “or” relationship; in the formula, the character “/”, indicates that the objects associated before and after are in a relationship of “division”. “at least one of the following” or its similar expression, refers to any combination of these items, including a single item or plural items of any combination. For example, at least one of a, b, or c, may be expressed as: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, and c may be single or multiple.
It will be appreciated that the various numerical numbers involved in the embodiments of the present disclosure are only distinctions made for descriptive convenience and are not intended to limit the scope of the present disclosure.
It is to be understood that in the embodiments of the present disclosure, the serial numbers of the above processes do not imply the order of execution, and the order of execution of the processes shall be determined by their functions and inherent logic without constituting any limitation to the implementation process of the embodiments of the present disclosure.
The foregoing is only specific embodiments of the present disclosure, but the scope of the present disclosure is not limited thereto. Any changes or substitutions that can be readily thought of by those skilled in the art within the scope of the technology disclosed in the present disclosure shall be covered by the scope of the present disclosure. Therefore, the scope of the present disclosure shall be subject to the scope of the stated claims.
The present disclosure is a continuation-application of International (PCT) Patent Application No. PCT/CN2021/122416, filed on Sep. 30, 2021, the entire contents of which are hereby incorporated by reference in their entirety.
| Number | Date | Country | |
|---|---|---|---|
| Parent | PCT/CN2021/122416 | Sep 2021 | US |
| Child | 18396457 | US |
