Conditionally skipping monitoring of downlink control channels
By receiving a skip command in the terminal device and skipping monitoring of the downlink control channel in the part where the random access process overlaps the time window, the command is ignored or executed after the time window is over according to the successful results of the access process. The problem of high battery consumption in the prior art is achieved, and more effective power management is achieved.
Patent Information
- Application Number
- CN202280095337.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-09-23
- Publication Date
- 2024-12-06
AI Technical Summary
The prior art is difficult to monitor the conditionally skip downlink control channel in terminal devices, especially during and after the process is successfully completed, resulting in an increase in battery consumption.
Provides an apparatus and method to skip monitoring of downlink control channels within a specific time period by receiving commands and performing within a portion where the random access process overlaps with the associated time window, according to competition resolution or success of the access process The result is that the skip command is ignored or executed after the time window is over.
Optimize the power savings of terminal devices to ensure timely monitoring is restored after a successful competition resolution or access process, avoiding unnecessary battery consumption.
Smart Images

Figure CN119096694A_ABST
Abstract
Description
Technical Field
[0001] Embodiments of the present disclosure relate generally to the field of telecommunications, and more particularly to apparatus, methods, and computer-readable storage media for conditionally skipping monitoring of a downlink (DL) control channel. Background Art
[0002] Skipping monitoring of downlink control channels is a method of reducing battery consumption by instructing a terminal device to skip monitoring of DL control channels for a certain period of time. If skipping monitoring of DL control channels is supported, the terminal device may receive a command during or before a random access (RA) procedure instructing the terminal device to skip monitoring the DL control channels. Therefore, it is necessary to clarify how the terminal device should operate with respect to skipping monitoring of DL control channels during an ongoing RA procedure and after a successful contention resolution or successful completion of the RA procedure. Summary of the invention
[0003] Generally speaking, example embodiments of the present disclosure provide a scheme for conditionally skipping monitoring of DL control channels during a RA procedure and after a successful contention resolution or successful completion of the RA procedure.
[0004] In a first aspect, a first device is provided. The first device includes at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, causes the first device to at least: receive a command from a second device, the command instructing the first device to skip monitoring of a downlink control channel between the second device and the first device within a time period; initiate an RA process to the second device, the time period at least partially overlapping with a time window associated with the RA process, and the end of the time period is after the end of the time window; determine whether the RA process is successfully completed or whether contention resolution for the RA process is successful; and based on the determination, ignore or execute the command after the end of the time window.
[0005] In a second aspect, a method implemented at a first device is provided. The method includes: receiving a command from a second device, the command instructing the first device to skip monitoring of a downlink control channel between the second device and the first device for a time period; initiating an RA process to the second device, the time period at least partially overlapping with a time window associated with the RA process, and the end of the time period is after the end of the time window; determining whether the RA process is successfully completed or whether contention resolution for the RA process is successful; and based on the determination, ignoring or executing the command after the end of the time window.
[0006] In a third aspect, a first device is provided. The first device includes: a component for receiving a command from a second device, the command instructing the first device to skip monitoring of a downlink control channel between the second device and the first device within a time period; a component for initiating a random access (RA) procedure to the second device, the time period at least partially overlapping with a time window associated with the RA procedure, and the end of the time period is after the end of the time window; a component for determining whether the RA procedure is successfully completed or whether contention resolution for the RA procedure is successful; and a component for ignoring or executing the command after the end of the time window based on the determination.
[0007] In a fourth aspect, a non-transitory computer-readable medium comprising a computer program is provided, the computer program being configured to cause an apparatus to at least perform the method according to the second aspect above.
[0008] It should be understood that the summary is not intended to identify the key or essential features of the embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS
[0009] Some example embodiments will now be described with reference to the accompanying drawings, in which:
[0010] Figure 1 shows an example communication network in which embodiments of the present disclosure may be implemented;
[0011] Figure 2 Skipping of monitoring of a DL control channel according to some example embodiments of the present disclosure is shown;
[0012] Figure 3 shows a signaling diagram illustrating a process for conditionally skipping monitoring of a DL control channel according to some example embodiments of the present disclosure;
[0013] Figure 4A and Figure 4B shows the relationship between the skip period and the time window associated with the RA according to some example embodiments of the present disclosure;
[0014] Figure 5 shows a signaling diagram illustrating a process for conditionally skipping monitoring of a DL control channel according to some other example embodiments of the present disclosure;
[0015] Figure 6 shows a signaling diagram illustrating a process for conditionally skipping monitoring of a DL control channel according to yet other example embodiments of the present disclosure;
[0016] Figure 7A flowchart showing a method implemented at a first device according to some example embodiments of the present disclosure is shown;
[0017] Figure 8 shows a simplified block diagram of an apparatus suitable for implementing an embodiment of the present disclosure; and
[0018] Fig. 9 A block diagram of an example computer-readable medium is shown according to some example embodiments of the present disclosure.
[0019] Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION
[0020] The principle of the present disclosure will now be described with reference to some example implementations. It should be understood that describing these implementations is only for illustrative purposes, and helps those skilled in the art to understand and implement the present disclosure, without implying any limitation on the scope of the present disclosure. The disclosure described herein can be implemented in various ways different from the ways described below.
[0021] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.
[0022] References in this disclosure to "one embodiment," "an embodiment," "an example embodiment," etc., indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes the particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in conjunction with an embodiment, it is considered to be within the knowledge of those skilled in the art to affect such feature, structure, or characteristic in conjunction with other implementations (whether or not explicitly described).
[0023] It should be understood that although the terms "first" and "second" and the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, without departing from the scope of the example implementation, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.
[0024] The terms used herein are for the purpose of describing particular implementations only and are not intended to limit the example implementations. As used herein, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the terms "includes", "comprising", "having", "including", and / or "comprising" when used herein specify the presence of stated features, elements, and / or components, etc., but do not preclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.
[0025] As used in this application, the term "circuitry" may refer to one, more than one, or all of the following: (a) only hardware circuit implementation (e.g., only implementation in analog and / or digital circuits) and (b) a combination of hardware circuitry and software, such as (where applicable): (i) a combination of analog and / or digital hardware circuitry and software / firmware, and (ii) a hardware processor (including a digital signal processor) with software, software and any portion of memory that work together to enable a device such as a mobile phone or server to perform various functions) and (c) Hardware circuits and / or processors (e.g., a microprocessor or a portion of a microprocessor) that require software (e.g., firmware) to operate, but where software is not required to operate, the software may not be present.
[0026] This definition of circuitry applies to all uses of this term in this application, including in any claims. As another example, as used in this application, the term circuitry also covers an implementation of only a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its (or its) accompanying software and / or firmware. The term circuitry also covers (for example and if applicable to a particular claim element) a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in a server, a cellular network device or other computing or network device.
[0027] As used herein, the term "communication network" refers to a network that follows any suitable communication standard, such as, but not limited to, the fifth generation (5G) system, long term evolution (LTE), advanced LTE (LTE-A), wideband code division multiple access (WCDMA), high speed packet access (HSPA), narrowband Internet of Things (NB-IoT), Wi-Fi, etc. In addition, the communication between the terminal device and the network device in the communication network can be performed according to any suitable generation of communication protocols, including but not limited to the first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G) new radio (NR) communication protocol, and / or any other protocol currently known or to be developed in the future. The embodiments of the present disclosure can be applied to various communication systems. In view of the rapid development of communication, there are of course future types of communication technologies and systems, using which the present disclosure can be implemented. It should not be regarded as limiting the scope of the present invention to the above-mentioned systems.
[0028] As used herein, the term "network device" refers to a node in a communication network via which a terminal device accesses the network and receives services from it. Depending on the terminology and technology applied, a network device may refer to a base station (BS) or an access point (AP), for example, a Node B (Node B or NB), an evolved Node B (eNodeB or eNB), a NRNB (also known as a gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, a low-power node such as a femto base station, a pico base station, etc. The RAN split architecture includes a gNB-CU (centralized unit, mastering RRC, SDAP and PDCP) that controls multiple gNB-DUs (distributed units, mastering RLC, MAC and PHY). A relay node may correspond to the DU portion of an IAB node.
[0029] The term "terminal device" refers to any terminal device capable of wireless communication. By way of example and not limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS) or access terminal (AT). The terminal device may include, but is not limited to, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet computer, a wearable terminal device, a personal digital assistant (PDA), a portable computer, a desktop computer, an image capture terminal device such as a digital camera, a game terminal device, a music storage and playback device, a vehicle-mounted wireless terminal device, a wireless endpoint, a mobile station, a laptop embedded device (LEE), a laptop mounted device (LME), USB dongles, smart devices, wireless client equipment (CPE), an Internet of Things (IoT) device, a watch or other wearable device, a head mounted display (HMD), a vehicle, a target, medical equipment and applications (e.g., remote surgery), industrial equipment and applications (e.g., robots and / or other wireless devices operating in an industrial and / or automated processing chain environment, consumer electronic devices, devices operating on a commercial and / or industrial wireless network, etc. The terminal device may also correspond to the mobile terminal (MT) part of an integrated access and backhaul (IAB) node. Relay node). In the following description, the terms "terminal device", "communication device", "terminal", "user equipment" and "UE" may be used interchangeably.
[0030] Figure 1 An example communication network 100 in which embodiments of the present disclosure may be implemented is shown. The network 100 includes a first device 110 and a second device 120 that may communicate with each other. In this example, the first device 110 is shown as a terminal device, and the second device 120 is shown as a network device serving the terminal device. Therefore, the service area of the second device 120 is referred to as a cell 102. It will be understood that the number of network devices and terminal devices is only for illustrative purposes and does not imply any limitation. The network 100 may include any suitable number of network devices and terminal devices adapted to implement embodiments of the present disclosure. Although not shown, it will be understood that one or more terminal devices may be located in the cell 102 and served by the second device 120.
[0031] The communication in the communication network 100 can be implemented according to any appropriate (multiple) communication protocols, including but not limited to cellular communication protocols of the first generation (1G), second generation (2G), third generation (3G), fourth generation (4G) and fifth generation (5G), such as wireless local area network communication protocols such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, and / or any other protocol currently known or to be developed in the future. In addition, the communication can utilize any appropriate wireless communication technology, including but not limited to: code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), frequency division duplex (FDD), time division duplex (TDD), multiple input multiple output (MIMO), orthogonal frequency division multiplexing (OFDM), discrete Fourier transform spread OFDM (DFT-s-OFDM) and / or any other technology currently known or to be developed in the future.
[0032] In the communication network 100, the first device 110 and the second device 120 can communicate data and control information with each other. In the case where the first device 110 is a terminal device and the second device 120 is a network device, the link from the second device 120 to the first device 110 is called a downlink (DL), and the link from the first device 110 to the second device 120 is called an uplink (UL).
[0033] In order to support power saving, the second device 120 may send a command instructing the first device 110 to skip monitoring the DL control channel for a time period. Skipping the monitoring of the DL control channel may be beneficial in the case of scheduling gaps due to beam scanning or other scheduling decisions on the transmitter side. For example, the second device 120 may have multiple terminal devices to be scheduled, for example in different beams, but the scheduling cannot be completed at the same time. Similarly, skipping the monitoring of the DL control channel may also be a case when no data is available for the terminal device. The second device 120 may indicate to one or more of the terminal devices that they are allowed to skip monitoring the DL control channel for a period of time, i.e., these terminal devices will not be scheduled until a number of time slots, and therefore, they can enter a sleep mode to save battery power.
[0034] Figure 2Skipping monitoring of a DL control channel according to some example embodiments of the present disclosure is shown. As shown, in a scheduling period 210, the second device 120 continuously schedules the first device 110. If the second device 120 will not schedule the first device 110 for a period of time, at the end of the scheduling period 210, the second device 120 can send a skip command to the first device 110, which instructs the first device 110 to skip monitoring the DL control channel during the time period 220. During the time period 220, the first device 110 will execute the command and will not monitor the DL control channel during the time period. In this regard, the terms "skip monitoring", "execute a skip command" and "do not monitor the DL control channel" can be used interchangeably.
[0035] For the purpose of discussion, the time period in which the first device 110 skips monitoring the DL control channel is also referred to as a skip period. The skip period 220 may be explicitly indicated in a skip command from the second device 120, or may be pre-configured by the second device 120, for example, via radio resource control (RRC) signaling. For example, the skip period 220 may include multiple monitoring opportunities or include a duration.
[0036] At the end of the skip period 220 , the first device 110 resumes monitoring the DL control channel in the scheduled period 230 .
[0037] If skipping monitoring of the DL control channel is supported, the second device 120 may send a skip command to the first device 110 during and / or before a random access (RA) procedure.
[0038] If skipping of monitoring of the DL control channel is supported, the first device 110 may indicate to the second device 120 that it supports skipping of the DL control channel, for example, through a UE capability message.
[0039] The second device 120 considers the capability of the first device 110 (eg, considers the skip period) when configuring the skip command to the first device 110 and when scheduling or allocating radio resources to the first device 110 .
[0040] However, the first device 110 may ignore the skip command if the first device 110 is on one of the following: - all serving cells in the corresponding cell group when a scheduling request (SR) is sent and pending; - Special cell (SpCell) when the contention resolution (CR) timer is running; -SpCell during the monitoring period of the RA response (RAR) or message B (MsgB) window.
[0041] Conventionally, if the skip period extends beyond the contention resolution timer, the terminal device will continue to skip after the CR timer stops or after the CR timer expires. This may be counterproductive in the case where a RA procedure is performed, for example, due to the arrival of UL data, because the terminal device will expect to receive an additional UL grant to send UL data.
[0042] According to some example embodiments, a scheme is provided for conditionally skipping monitoring of a DL control channel during an RA procedure and after a successful contention resolution or successful completion of an RA procedure. According to the scheme, the device ignores or executes the skip command based on the result of the contention resolution or completion of the RA procedure. In this way, power savings of the device can be optimized.
[0043] Reference now Figure 3 , which shows a signaling diagram illustrating a process 300 for conditionally skipping monitoring of a DL control channel during a RA procedure according to some example embodiments of the present disclosure. For the purpose of discussion, reference will be made to Figure 1 Describe process 300. Process 300 may involve Figure 1 The first device 110 and the second device 120 are shown. Figure 1 The process 300 is described in the communication network 100 of FIG. 1 , but the process can also be applied to other communication scenarios.
[0044] At 310, the first device 110 receives a skip command from the second device 120. The skip command instructs the first device 110 to skip monitoring a DL control channel between the second device 120 and the first device 110 for a time period (which is also referred to as a skip period).
[0045] In some example embodiments, when the first device 110 is a terminal device and the second device 120 is a network device, the DL control channel to be monitored may be a physical downlink control channel (PDCCH). The PDCCH is referred to as a scheduling channel in the sense that it carries scheduling information. The control information sent via the PDCCH is referred to as downlink control information (DCI). By monitoring the DL control channel, the first device 110 may determine when and / or how it is scheduled to send data to the second device 120. The skip command may be sent to the first device 110 in control information, such as in the PDCCH.
[0046] The first device 110 initiates 320 a RA procedure to the second device 120. For example, the first device 110 may initiate the RA procedure by sending a RA preamble to the second device 120.
[0047] The skip period overlaps at least partially with the time window associated with the RA process. The end of the skip period is after the end of the time window. For the purpose of discussion, the time window associated with the RA process is also referred to as the RA time window.
[0048] In some embodiments, the RA time window may be defined by at least one of: a contention resolution timer, a message B (MsgB) response window, or a RA response window.
[0049] In some embodiments, action 310 may be performed before action 320. In such embodiments, the first device 110 receives a skip command before the RA process. For example, the skip command may be received when the first device 110 is about to enter the RA process.
[0050] In some other embodiments, action 310 may be performed after action 320. In such embodiments, the first device 110 receives the skip command during the RA process. In other words, the skip command may be received when the first device 110 is in the ongoing RA process.
[0051] In yet other embodiments, act 310 and act 320 may be performed in parallel.
[0052] Continue to refer Figure 3 , the first device 110 determines 330 whether the RA process is successfully completed, or whether contention resolution for the RA process is successful.
[0053] Then, based on the determination, the first device 110 ignores or executes 340 the command after the end of the time window.
[0054] Using the process 300, the first device 110 ignores or executes a skip command based on the result of the contention resolution or RA process completion. In this way, power saving of the first device 110 can be optimized.
[0055] In some embodiments, the first device 110 may determine the end of the RA time window based on one of the following: the RA time window is stopped, or the RA time window expires. As an example, the RA time window may be stopped upon a successful RA operation (e.g., successful contention resolution or receipt of an RA response). As another example, the RA time window may expire upon an unsuccessful RA operation (e.g., unsuccessful contention resolution or unsuccessful receipt of an RA response).
[0056] To better understand the actions performed by the first device 110 based on the result of the contention resolution or RA process completion, reference will be made to Figure 4A and Figure 4B Describes the relationship between the skip period and the RA time window.
[0057] like Figure 4A As shown, the skip period 410 partially overlaps with the RA time window 420. The start of the skip period 410 is after the start of the RA time window 420.
[0058] The RA time window 420 expires at time 421. In some embodiments, the first device 110 can determine the end of the RA time window 420 based on the expiration of the RA time window 420 at time 421.
[0059] Alternatively, in other embodiments, the first device 110 may stop the RA time window 420 before the RA time window 420 expires at time 421. For example, the first device 110 may stop the RA time window 420 at time 422 before time 421. In such an embodiment, the first device 110 may determine the end of the RA time window 420 based on the RA time window 420 being stopped at time 422.
[0060] The skip period 410 expires at time 411. In other words, the skip period 410 ends at time 411 after the RA time window 420 is stopped at time 422, or after the RA time window 420 expires at time 421.
[0061] like Figure 4B As shown, the skip period 430 partially overlaps the RA time window 420 . Figure 4B Examples with Figure 4A The example of is different in that the start of the skip period 430 is before the start of the RA time window 420 .
[0062] Similar to Figure 4A For example, the first device 110 can determine the end of the RA time window 420 based on the RA time window 420 expiring at time 421. Alternatively, the first device 110 can determine the end of the RA time window 420 based on the RA time window 420 being stopped at time 422.
[0063] Similar to Figure 4A In the example of , after the RA time window 420 is stopped at time 422 , or after the RA time window 420 expires at time 421 , the skip period 430 ends at time 431 .
[0064] In some embodiments, if the contention resolution is successful or the RA process is successfully completed, the first device 110 may expect to receive a scheduling command from the second device 120 to avoid delays in UL transmission. Therefore, the first device 110 may ignore the skip command after stopping the RA time window. This will refer to Figure 5 Give a description.
[0065] Figure 5A signaling diagram is shown that illustrates a process 500 for conditionally skipping monitoring of a DL control channel during a RA procedure according to some other example embodiments of the present disclosure. For discussion purposes, reference will be made to Figure 1 Describe process 500. Process 500 may involve Figure 1 The first device 110 and the second device 120 are shown. The process 500 may be considered an example implementation of the process 300.
[0066] like Figure 5 As shown, the first device 110 sends 505 an RA preamble to the second device 120 to initiate a RA process. The RA process may be a contention-based RA process.
[0067] Upon receiving the RA preamble, the second device 120 may estimate the transmission timing of the first device 110 to enable uplink synchronization of the first device 110 .
[0068] If the second device 120 will not schedule the first device 110 for a period of time, the second device 120 may send 510 a skip command to the first device 110. The skip command instructs the first device 110 to skip monitoring the DL control channel during the skip period. For example, the skip command may instruct the first device 110 to skip monitoring the DL control channel during the skip period. Figure 4A In the skip period 410 shown or in Figure 4B Monitoring of the DL control channel is shown skipped during skip period 430. It should be noted that the operation in 510 may occur before 505, or after 525, or before the second device has decoded the transmission from the first device at 530.
[0069] Upon receiving the skip command, the first device 110 determines 515 whether the skip period overlaps with the RA time window in order to obtain information required for the RA process from the second device 120. For example, in this example implementation, the first device 110 may determine whether the skip period overlaps with the RA response window.
[0070] If the first device 110 determines that the skip period completely overlaps with the RA response window, the first device 110 may ignore 520 the skip command. Thus, receipt of the RA response is ensured. If the first device 110 ignores the skip command, the first device 110 will monitor the DL control channel. In this regard, the terms "ignore the skip command" and "monitor the DL control channel" may be used interchangeably.
[0071] On the other hand, if the first device 110 determines that the skip period partially overlaps with the RA response window, the first device 110 may execute 520 a skip command until the start of the RA response window. From the start of the RA response window, the first device 110 ignores the skip command to monitor the DL control channel. In this way, scheduling flexibility can be enabled and reception of RA responses can be ensured.
[0072] For example, Figure 4B As shown, the first device 110 may execute the skip command from the start of the skip period 430 to the start of the RA response window 420. From the start of the RA response window 420, the first device 110 ignores the skip command to monitor the DL control channel.
[0073] Alternatively, if the first device 110 determines that the skip period does not overlap with the RA response window, the first device 110 may execute the skip command. In this way, scheduling flexibility may be enabled.
[0074] Based on the estimated transmission timing of the first device 110, the second device 120 may send 525 a RA response to the first device 110. The RA response may include information about the timing advance for the first device 110, and the UL resources to be used by the first device 110 in action 530.
[0075] Upon receiving the RA response, the first device 110 sends 530 a scheduled transmission to the second device 120 using the UL resources indicated in the RA response. The scheduled transmission may include a cell radio network temporary identifier (C-RNTI) of the first device 110 or another ID of the first device 110.
[0076] The first device 110 determines 540 whether the RA process is successfully completed or whether the contention resolution for the RA process is successful. If the contention resolution is successful or the RA process is successfully completed, the first device 110 stops 545 the RA time window. Furthermore, the first device 110 ignores 550 the skip command after stopping the RA time window.
[0077] For example, the first device 110 can stop the RA time window 420 at time 422, such as Figure 4A As shown. The first device 110 can ignore the skip command after stopping the RA time window 420 at time 422 until the skip period 410 ends (at time 411). As another example, the first device 110 can stop the RA time window 420 at time 422, as shown. Figure 4B The first device 110 may ignore the skip command after stopping the RA time window 420 at time 422 until the skip period 410 ends (at time 431 ).
[0078] In this example implementation, from the start of the RA response window 420 to the end of the RA time window 420 at time 422, the first device 110 ignores the skip command, and the first device 110 does not continue to skip monitoring of the DL control channel.
[0079] In this example implementation, if the second device 120 determines that the first device 110 is successful in contention resolution for the RA procedure, the second device 120 may perform 535 a transmission on a DL control channel to the first device 110. The transmission is addressed to a cell radio network temporary identifier (C-RNTI) of the first device 110. For example, the transmission may include a contention resolution message. For example, the contention resolution message may include a PDCCH transmission addressed to the C-RNTI of the first device.
[0080] In other example implementations, the transmission on the DL control channel (at 535) may also include an uplink grant for a new transmission.
[0081] If the second device 120 determines that the first device 110 is unsuccessful in contention resolution for the RA procedure, the second device 120 may perform transmission to other terminal devices on the DL control channel.
[0082] If the first device 110 receives a transmission addressed to the C-RNTI of the first device 110 from the second device 120 on the DL control channel, the first device 110 may determine that the contention resolution is successful. Furthermore, the first device 110 may determine that the RA procedure is successfully completed.
[0083] In some embodiments, if the first device 110 receives a transmission addressed to the C-RNTI of the first device 110 from the second device 120 on the DL control channel, the first device 110 may stop the RA time window and determine that the contention resolution is successful. In other words, the action of stopping the RA time window and the action of determining that the contention resolution is successful may be performed in parallel.
[0084] On the other hand, if the first device 110 does not receive a transmission from the second device 120 on the DL control channel within the RA time window, the first device 110 may determine that the contention resolution is unsuccessful. In this case, the second device 120 is not yet aware that the first device 110 performs the RA process. Therefore, the second device 120 does not expect any interruption of the skip period. Therefore, the first device 110 may execute the skip command after the end of the RA time window. For example, the first device 110 may execute the skip command after the RA time window 420 expires at time 421. In other words, the first device 110 continues to skip monitoring of the DL control channel.
[0085] In some embodiments, if the contention resolution is unsuccessful, the first device 110 may send a new RA preamble to the second device 120 to initiate the RA process again. If the number of RA preambles sent exceeds a preconfigured threshold, the first device 110 may determine that the RA process is not successfully completed. In such an embodiment, the first device 110 may execute a skip command after the end of the RA time window.
[0086] It should be understood that from the start of the RA time window 420 to the end of the RA time window 420 , the first device 110 ignores the skip command to obtain information for the RA process from the second device 120 .
[0087] It will be appreciated that although process 500 is described in conjunction with a RA response window, a similar process may be applied to a time window defined by a RA contention resolution timer or a MsgB response window.
[0088] It will also be appreciated that although process 500 is described using a 4-step RA process as an example, a similar process may be applied to a 2-step RA process.
[0089] It will further be appreciated that although process 500 is described as an example in which act 505 occurs before act 510 , in other example implementations, act 505 may occur after act 510 .
[0090] In some embodiments, if the first device 110 receives a transmission on the downlink control channel that is addressed to the C-RNTI of the first device 110 and contains an uplink grant for a new transmission, the first device 110 may determine that the contention resolution is successful or the RA procedure is successfully completed. Furthermore, in some cases, the first device 110 may execute a skip command. This will refer to Figure 6 Give a description.
[0091] Figure 6 A signaling diagram is shown that illustrates a process 600 for conditionally skipping monitoring of a DL control channel during a RA procedure according to some other example embodiments of the present disclosure. For the purpose of discussion, reference will be made to Figure 1 Process 600 is described. Process 600 may involve Figure 1 The first device 110 and the second device 120 are shown. The process 600 may be considered as another example implementation of the process 300.
[0092] Actions 505, 510, 515, 520, 525, 530, 535, 540, and 545 in process 600 are the same as actions in process 500. Details of these actions are omitted for brevity.
[0093] Process 600 differs from process 500 in actions 610 , 615 , and 620 .
[0094] Specifically, the first device 110 determines 610 whether the uplink grant can accommodate all data to be sent by the first device 110 .
[0095] If the uplink grant can accommodate all the data, the first device 110 sends 615 all the data to the second device 120 based on the uplink grant.
[0096] In this case, because the first device 110 sends all data to the second device 120 based on the uplink grant, the first device 110 does not need further scheduling information in a timely manner. Therefore, the first device 110 can execute 620 the skip command after sending the data. Alternatively, the first device 110 can execute 620 the skip command after the stop time window 420.
[0097] On the other hand, if the uplink grant cannot accommodate all the data, the first device 110 can ignore the skip command after sending the partial data. Alternatively, after determining 610 that the uplink grant can accommodate all the data and before sending the partial data, the first device 110 can ignore the skip command.
[0098] It should be noted that a similar determination of whether to continue the skip command may be similarly applicable to a scheduling request (SR) process. After sending a scheduling request to the second device 120, the first device 110 may ignore the PDCCH skip command when the scheduling request is pending. In an example, after a buffer status report (BSR) is sent by the first device 110 to the second device 120, the first device 110 may ignore the PDCCH skip command after the pending SR is canceled. In an example, when there is still data remaining in the buffer of the first device 110 after UL transmission, the first device 110 may ignore the PDCCH skip command.
[0099] In some embodiments, the first device 110 may initiate a RA procedure in a special cell (SpCell) and ignore the skip command only in the SpCell.
[0100] Alternatively, in some embodiments, the first device 110 may initiate the RA procedure in the SpCell and ignore the skip command in a subset of serving cells in the cell group including the SpCell.
[0101] In some embodiments, the first device 110 may initiate the RA procedure in the SpCell and ignore the skip command in all serving cells in the cell group including the SpCell.
[0102] In some embodiments, the SpCell may include a master cell (PCell) in a master cell group (MCG).
[0103] Alternatively, in some embodiments, the SpCell may include a secondary primary cell (SPCell) in a secondary cell group (SCG).
[0104] Figure 7 FIG. 7 is a flowchart showing an example method 700 implemented at a first device according to some example embodiments of the present disclosure. For the purpose of discussion, reference will be made to Figure 1 The method 700 is described from the perspective of the first device 110 .
[0105] At block 710 , the first device 110 receives a skip command from the second device 120 , the skip command instructing the first device to skip monitoring of a downlink control channel between the second device 120 and the first device 110 for a period of time.
[0106] At block 720, the first device 110 initiates a RA procedure to the second device 120. The time period at least partially overlaps with a time window associated with the RA procedure, and an end of the time period is subsequent to an end of the time window.
[0107] In block 730 , the first device 110 determines whether the RA process is successfully completed or whether contention resolution for the RA process is successful.
[0108] In block 740 , based on the determination, the first device 110 ignores or executes a skip command after the end of the time window.
[0109] In some example embodiments, the method 700 further comprises: determining the end of the time window based on one of: the time window being stopped, or the expiration of the time window.
[0110] In some embodiments, ignoring or executing the command after the end of the time window includes: ignoring the command after stopping the time window based on determining that the contention resolution is successful or the RA process is successfully completed.
[0111] In some example embodiments, the method 700 further includes determining that contention resolution is successful based on determining that a transmission on the downlink control channel is received within the time window, the transmission being addressed to a cell radio network temporary identifier (C-RNTI) of the first apparatus.
[0112] In some embodiments, the transmission includes an uplink grant for a new transmission.
[0113] In some example embodiments, the method 700 further includes stopping the time window in response to determining that a transmission on the downlink control channel is received.
[0114] In some embodiments, initiating the RA procedure includes initiating the RA procedure in a special cell (SpCell), and ignoring the command only in the SpCell after an end of the time window.
[0115] In some embodiments, initiating the RA procedure includes initiating the RA procedure in a special cell (SpCell) and ignoring the command after an end of a time window in a subset of serving cells in a cell group that includes the SpCell.
[0116] In some embodiments, initiating the RA procedure includes initiating the RA procedure in a special cell (SpCell) and ignoring the command after an end of a time window in all serving cells in a cell group including the SpCell.
[0117] In some embodiments, ignoring or executing the command after the end of the time window includes executing the command after the end of the time window based on determining that contention resolution is unsuccessful or the RA process is not successfully completed.
[0118] In some example embodiments, the method 700 further includes performing the following items based on determining that a transmission on a downlink control channel is received, the transmission being addressed to a cell radio network temporary identifier (C-RNTI) of the first device and including an uplink grant for a new transmission: determining that contention resolution is successful or the RA process is successfully completed, stopping the time window, determining whether the uplink grant can accommodate all data to be sent by the first device, based on determining that the uplink grant can accommodate all data, sending data to the second device based on the uplink grant, and executing a command after the stop time window or after sending the data.
[0119] In some embodiments, ignoring or executing the command after the end of the time window includes ignoring the command after stopping the time window or after sending a portion of the data based on determining that the uplink grant cannot accommodate all the data.
[0120] In some embodiments, the time window is defined by at least one of: a contention resolution timer, a message B response window, or a RA response window.
[0121] In some embodiments, ignoring the command includes monitoring a downlink control channel.
[0122] In some example embodiments, a first device (e.g., first device 110) capable of executing any method 700 may include a component for executing the corresponding steps of method 700. The component may be implemented in any suitable form. For example, the component may be implemented in a circuit or a software module.
[0123] In some example embodiments, the first device includes: a component for receiving a command from a second device, the command instructing the first device to skip monitoring of a downlink control channel between the second device and the first device within a time period; a component for initiating a random access (RA) process to the second device, the time period at least partially overlapping with a time window associated with the RA process, and the end of the time period is after the end of the time window; a component for determining whether the RA process is successfully completed or whether contention resolution for the RA process is successful; and a component for ignoring or executing the command after the end of the time window based on the determination.
[0124] In some example embodiments, the first apparatus further comprises: means for determining an end of the time window based on one of: the time window being stopped, or an expiration of the time window.
[0125] In some embodiments, the means for ignoring or executing the command after the end of the time window includes means for ignoring the command after stopping the time window based on determining that the contention resolution is successful or the RA process is successfully completed.
[0126] In some example embodiments, the first apparatus further comprises means for determining that contention resolution is successful based on determining that a transmission on the downlink control channel is received within the time window, the transmission being addressed to a cell radio network temporary identifier (C-RNTI) of the first apparatus.
[0127] In some embodiments, the transmission includes an uplink grant for a new transmission.
[0128] In some example embodiments, the first apparatus further comprises means for stopping the time window based on determining that a transmission on the downlink control channel is received.
[0129] In some embodiments, the means for initiating the RA procedure includes means for initiating the RA procedure in a special cell (SpCell) and ignoring the command only in the SpCell after an end of the time window.
[0130] In some embodiments, means for initiating a RA procedure includes means for initiating a RA procedure in a special cell (SpCell) and ignoring the command after an end of a time window in a subset of serving cells in a cell group that includes the SpCell.
[0131] In some embodiments, the means for initiating the RA procedure includes means for initiating the RA procedure in a special cell (SpCell) and ignoring the command after an end of a time window in all serving cells in a cell group including the SpCell.
[0132] In some embodiments, the means for ignoring or executing the command after the end of the time window includes means for executing the command after the end of the time window based on determining that contention resolution was unsuccessful or the RA process did not complete successfully.
[0133] In some example embodiments, the first device also includes: a component for performing the following items: performing the following items based on determining that a transmission on a downlink control channel is received, the transmission is addressed to the cell radio network temporary identifier (C-RNTI) of the first device and includes an uplink grant for a new transmission: determining that contention resolution is successful or the RA process is successfully completed, stopping the time window, determining whether the uplink grant can accommodate all data to be sent by the first device, based on determining that the uplink grant can accommodate all data, sending data to the second device based on the uplink grant, and the component for ignoring or executing the command after the end of the time window includes: a component for executing the command after stopping the time window or after sending the data.
[0134] In some embodiments, means for ignoring or executing the command after the end of the time window includes means for ignoring the command after stopping the time window or after sending partial data based on determining that the uplink grant cannot accommodate all the data.
[0135] In some embodiments, the time window is defined by at least one of: a contention resolution timer, a message B response window, or a RA response window.
[0136] In some embodiments, means for ignoring the command comprises means for monitoring a downlink control channel.
[0137] Figure 8 800 is a simplified block diagram of a device 800 suitable for implementing embodiments of the present disclosure. The device 800 may be provided to implement a communication device, such as Figure 1 The first device 110 is shown. As shown, the device 800 includes one or more processors 810, one or more memories 820 coupled to the processors 810, and one or more communication modules 840 coupled to the processors 810.
[0138] The communication module 840 is used for two-way communication. The communication module 840 has at least one antenna to facilitate communication. The communication interface may represent any interface required to communicate with other network elements.
[0139] Processor 810 may be of any type suitable for the local technology network and may include one or more of the following: as non-limiting examples, a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Device 800 may have multiple processors, such as application specific integrated circuit chips that are time slaved to a clock that synchronizes a main processor.
[0140] The memory 820 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 824, electrically programmable read-only memory (EPROM), flash memory, hard disks, compact disks (CDs), digital video disks (DVDs), and other magnetic and / or optical memories. Examples of volatile memories include, but are not limited to, random access memory (RAM) 822 and other volatile memories that do not persist over the duration of a power outage.
[0141] The computer program 830 includes computer executable instructions that are executed by the associated processor 810. The program 830 may be stored in the ROM 824. The processor 810 may perform any suitable actions and processes by loading the program 830 into the RAM 822.
[0142] The embodiments of the present disclosure can be implemented by means of program 830, so that the device 800 can execute the following steps: Figures 1 to 7 Any process of the present disclosure discussed. The embodiments of the present disclosure may also be implemented by hardware or a combination of software and hardware.
[0143] In some example embodiments, the program 830 may be tangibly embodied in a computer-readable medium that may be included in the device 800 (e.g., in the memory 820) or in other storage devices accessible by the device 800. The device 800 may load the program 830 from the computer-readable medium to the RAM 822 for execution. The computer-readable medium may include any type of tangible non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. Fig. 9 An example of a computer readable medium 900 in the form of a CD or DVD is shown. The computer readable medium has a program 830 stored thereon.
[0144] In general, various embodiments of the present disclosure may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software, which may be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure are shown and described as block diagrams, flow charts, or using some other graphical representations, it should be understood that the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general hardware or controllers or other computing devices, or some combination thereof, as non-limiting examples.
[0145] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer executable instructions such as those included in a program module that are executed in a device on a target real or virtual processor to perform the above-referenced Figure 7 The method 700 is described. In general, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The functions of program modules can be combined or separated between program modules as needed in various embodiments. The machine executable instructions of program modules can be executed in local or distributed devices. In distributed devices, program modules can be located in local and remote storage media.
[0146] The program code for executing the method of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general-purpose computer, a special-purpose computer or other programmable data processing device so that the program code, when executed by the processor or controller, enables the functions / operations specified in the flow chart and / or block diagram to be implemented. The program code may be executed entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine, partially on a remote machine, or entirely on a remote machine or server.
[0147] In the context of the present disclosure, computer program codes or related data may be carried by any suitable carrier to enable a device, apparatus or processor to perform various processes and operations as described above. Examples of carriers include signals, computer readable media, etc.
[0148] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable medium may include, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared or semiconductor system, apparatus or device, or any suitable combination of the foregoing. More specific examples of computer readable storage media would include an electrical connection having one or more conductors, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0149] In addition, although operations are described in a particular order, this should not be understood as requiring the specific order shown or to perform these operations in sequence, or to perform all the operations shown, to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these details should not be interpreted as limitations on the scope of the present disclosure, but should be interpreted as descriptions of features peculiar to a particular embodiment. Certain features described in the context of a separate embodiment may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable sub-combination.
[0150] Although the disclosure has been described in language specific to structural features and / or methodological actions, it should be understood that the disclosure defined in the appended claims is not necessarily limited to the specific features or actions described above. Instead, the specific features and actions described above are disclosed as example forms of implementing the claims.
Claims
1. A first device, comprising: at least one processor; as well as at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: receiving a command from a second device, the command instructing the first device to skip monitoring a downlink control channel between the second device and the first device for a time period; initiating a random access (RA) procedure to the second apparatus, the time period at least partially overlapping with a time window associated with the RA procedure, and an end of the time period being after an end of the time window; determining whether the RA process is successfully completed or whether contention resolution for the RA process is successful; and Based on the determination, the command is ignored or executed after the end of the time window.
2. The first device of claim 1 , wherein the first device is further caused to determine the end of the time window based on one of: The time window is stopped, or Expiration of the time window.
3. The first device according to claim 2, wherein the first device is configured to: Based on determining that the contention resolution is successful or the RA process is successfully completed, the command is ignored after stopping the time window.
4. The first device according to any one of claims 1 to 3, wherein the first device is further configured to: The contention resolution is determined to be successful based on determining that a transmission on the downlink control channel is received within the time window, the transmission being addressed to a cell radio network temporary identifier (C-RNTI) of the first apparatus.
5. The first device of claim 4, wherein the transmission comprises an uplink grant for a new transmission.
6. The first device according to claim 4 or 5, wherein the first device is further configured to: Based on determining that the transmission on the downlink control channel is received, the time window is stopped.
7. The first device according to any one of claims 1 to 6, wherein the first device is caused to initiate the RA procedure in a special cell (SpCell) and ignore the command only in the SpCell after the end of the time window.
8. A first device according to any one of claims 1 to 6, wherein the first device is configured to initiate the RA process in a special cell (SpCell) and ignore the command after the end of the time window in a subset of serving cells in a cell group including the SpCell.
9. A first device according to any one of claims 1 to 6, wherein the first device is caused to initiate the RA process in a special cell (SpCell) and ignore the command after the end of the time window in all serving cells in a cell group including the SpCell.
10. The first device according to claim 1, wherein the first device is caused to: Based on determining that the contention resolution was unsuccessful or the RA process was not successfully completed, executing the command after the end of the time window.
11. The first device according to claim 2, wherein the first device is caused to: performing the following in accordance with determining that a transmission on the downlink control channel is received, the transmission being addressed to a cell radio network temporary identifier (C-RNTI) of the first apparatus and including an uplink grant for a new transmission: Determining that the contention resolution is successful or the RA process is successfully completed, Stop the time window, determining whether the uplink grant can accommodate all data to be sent by the first device, sending the data to the second device based on the uplink grant according to determining that the uplink grant can accommodate all of the data, and The command is executed after stopping the time window or after sending the data.
12. The first device according to claim 11, wherein the first device is caused to: The command is ignored after stopping the time window or after sending a portion of the data based on determining that the uplink grant cannot accommodate all of the data.
13. The first apparatus according to any one of the preceding claims, wherein the time window is defined by at least one of the following: Contention resolution timer, Message B response window, or RA response window.
14. The first apparatus of any preceding claim, wherein ignoring the command comprises monitoring the downlink control channel.
15. A first device, comprising: means for receiving a command from a second device, the command instructing the first device to skip monitoring a downlink control channel between the second device and the first device for a time period; means for initiating a random access (RA) procedure towards the second apparatus, the time period at least partially overlapping with a time window associated with the RA procedure and an end of the time period being after an end of the time window; A component for determining whether the RA process is successfully completed or whether the contention resolution for the RA process is successful; as well as Means for ignoring or executing the command after the end of the time window based on the determination.
16. The first device according to claim 15, further comprising: means for determining said end of said time window based on one of: The time window is stopped, or Expiration of the time window.
17. The first device of claim 16, wherein the means for ignoring or executing the command after the end of the time window comprises: means for ignoring the command after stopping the time window based on determining that the contention resolution is successful or the RA process is successfully completed.
18. The first device according to any one of claims 15 to 17, further comprising: Means for determining that the contention resolution was successful based on determining that a transmission on the downlink control channel was received within the time window, the transmission being addressed to a Cell Radio Network Temporary Identifier (C-RNTI) of the first apparatus.
19. The first device of claim 18, wherein the transmission comprises an uplink grant for a new transmission.
20. The first device according to claim 18 or 19, further comprising: means for stopping the time window based on determining that the transmission on the downlink control channel is received.
21. The first device according to any one of claims 15 to 20, wherein the means for initiating the RA process comprises: Means for initiating said RA procedure in a special cell (SpCell) and ignoring said command after said end of said time window only in said SpCell.
22. The first device according to any one of claims 15 to 20, wherein the means for initiating the RA process comprises: Means for initiating said RA procedure in a special cell (SpCell) and ignoring said command after said end of said time window in a subset of serving cells in a cell group including said SpCell.
23. The first device according to any one of claims 15 to 20, wherein the means for initiating the RA process comprises: Means for initiating said RA procedure in a special cell (SpCell) and ignoring said command after said end of said time window in all serving cells in a cell group including said SpCell.
24. The first device of claim 15, wherein the means for ignoring or executing the command after the end of the time window comprises: Means for executing the command after the end of the time window based on determining that the contention resolution was unsuccessful or the RA process was not successfully completed.
25. The first apparatus of claim 16, further comprising means for performing: performing the following in accordance with determining that a transmission on the downlink control channel is received, the transmission being addressed to a cell radio network temporary identifier (C-RNTI) of the first apparatus and including an uplink grant for a new transmission: Determining that the contention resolution is successful or the RA process is successfully completed, Stop the time window, determining whether the uplink grant can accommodate all data to be sent by the first device, Based on determining that the uplink grant can accommodate all of the data, sending the data to the second device based on the uplink grant, and The means for ignoring or executing the command after the end of the time window comprises: Means for executing said command after stopping said time window or after sending said data.
26. The first device of claim 25, wherein the means for ignoring or executing the command after the end of the time window comprises: means for ignoring said command after stopping said time window or after transmitting a portion of said data based on determining that said uplink grant cannot accommodate all of said data.
27. The first device according to any one of claims 15 to 26, wherein the time window is defined by at least one of the following: Contention resolution timer, Message B response window, or RA response window.
28. The first device of any one of claims 15 to 27, wherein the means for ignoring the command comprises: Means for monitoring said downlink control channel.
29. A method comprising: receiving, at a first device, a command from a second device, the command instructing the first device to skip monitoring a downlink control channel between the second device and the first device for a time period; initiating a random access (RA) procedure to the second apparatus, the time period at least partially overlapping with a time window associated with the RA procedure, and an end of the time period being after an end of the time window; determining whether the RA process is successfully completed or whether contention resolution for the RA process is successful; and Based on the determination, the command is ignored or executed after the end of the time window.
30. A non-transitory computer readable medium comprising a computer program for causing an apparatus to at least perform the method according to claim 11.
