Methods for stimulating link-based reception, terminals, and network-side devices.
Patent Information
- Application Number
- TH2201006913
- Authority / Receiving Office
- TH · TH
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2021-04-25
- Publication Date
- 2026-10-05
AI Technical Summary
In the mobile communication system, when the terminal performs downlink reception according to the dynamic scheduling of the network-side device, the flexibility and efficiency are low, and it cannot meet the business needs of extended reality (XR) terminals.
The terminal sends an uplink signal to trigger downlink reception, and directly configures the time-frequency domain resources and duration of downlink reception to avoid relying on the scheduling process of network-side equipment.
It improves the flexibility and efficiency of terminal downlink reception, saves resource consumption, and can better meet the business needs of XR terminals.
Smart Images

Figure 00000001_0000
Abstract
Description
Downlink reception triggering method, terminal and network side device
[0001] Cross-reference to Related Applications
[0002] This application claims priority to Chinese Patent Application No. 202010367082.9, filed on April 30, 2020, the contents of which are incorporated herein by reference in its entirety. TECHNICAL FIELD
[0003] The present application relates to the field of communication technology, and in particular to a downlink reception triggering method, a terminal and a network side device. BACKGROUND
[0004] In a mobile communication system, the conventional transmission mode is a scheduling-based transmission mode, for example, a terminal first acquires the time-frequency domain resources for its own downlink reception allocated by a network side device by listening to a physical downlink control channel (PDCCH), and then performs downlink reception on the corresponding resources.
[0005] In actual application scenarios, the scheduling-based transmission mode is not necessarily the most efficient. Taking extended reality (XR) as an example, XR refers to a combined environment of reality and virtuality and human-computer interaction generated by computer technology and wearable devices. In the XR application scenario, the data resources required by the user can be predicted according to the user's actions. However, the flexibility of the terminal to perform downlink reception according to dynamic scheduling by the network side device is poor and the efficiency is low, which cannot well meet the service requirements of the XR terminal and is not suitable for the XR service model.
[0006] SUMMARY
[0007] Embodiments of the present application provide a downlink reception triggering method, a terminal and a network side device to solve the problem of poor flexibility and low efficiency of the terminal to perform downlink reception according to dynamic scheduling by the network side device in the prior art.
[0008] To solve the above problems, the present application is implemented as follows:
[0009] In a first aspect, embodiments of the present application provide a downlink reception triggering method applied to a terminal, the method comprising:
[0010] sending a first uplink signal, the first uplink signal being used to trigger a first downlink reception.
[0011] In a second aspect, embodiments of the present application provide a downlink reception triggering method applied to a network side device, the method comprising:
[0012] receive the first uplink signal sent by the terminal, the first uplink signal being used for triggering the first downlink reception.
[0013] In a third aspect, an embodiment of the present application provides a terminal, comprising:
[0014] The sending module is configured to send a first uplink signal, the first uplink signal being used for triggering the first downlink reception.
[0015] In a fourth aspect, an embodiment of the present application provides a network side device, comprising:
[0016] The receiving module is configured to receive a first uplink signal sent by the terminal, the first uplink signal being used for triggering the first downlink reception.
[0017] In a fifth aspect, an embodiment of the present application provides a terminal, comprising a memory, a processor, and instructions or programs stored in the memory and executable on the processor, and when the instructions or programs are executed by the processor, the steps in the downlink reception triggering method provided in the first aspect of the present application are implemented.
[0018] In a sixth aspect, an embodiment of the present application provides a network side device, comprising a memory, a processor, and instructions or programs stored in the memory and executable on the processor, and when the instructions or programs are executed by the processor, the steps in the downlink reception triggering method provided in the second aspect of the present application are implemented.
[0019] In a seventh aspect, an embodiment of the present application provides a readable storage medium, and the readable storage medium stores instructions or programs, and when the instructions or programs are executed by a processor, the steps in the downlink reception triggering method provided in the first aspect of the present application are implemented.
[0020] In an eighth aspect, an embodiment of the present application provides a readable storage medium, and the readable storage medium stores instructions or programs, and when the instructions or programs are executed by a processor, the steps in the downlink reception triggering method provided in the second aspect of the present application are implemented.
[0021] In a ninth aspect, an embodiment of the present application provides a chip, and the chip comprises a processor and a communication interface, the communication interface is coupled with the processor, and the processor is configured to run programs or instructions to implement the downlink reception triggering method as described in the first aspect.
[0022] In a tenth aspect, an embodiment of the present application provides a chip, and the chip comprises a processor and a communication interface, the communication interface is coupled with the processor, and the processor is configured to run programs or instructions to implement the downlink reception triggering method as described in the second aspect.
[0023] In a first aspect, an embodiment of the present application provides a downlink reception triggering method. The method comprises: receiving, by a terminal, a downlink signal from a network device; and triggering, by the terminal, a downlink reception based on the downlink signal.
[0024] In a twelfth aspect, an embodiment of the present application provides a terminal. The terminal is configured to perform the downlink reception triggering method according to the first aspect.
[0025] In a thirteenth aspect, an embodiment of the present application provides a network device. The network device is configured to perform the downlink reception triggering method according to the second aspect.
[0026] In the embodiment of the present application, the terminal can trigger a corresponding downlink reception by sending an uplink signal. In this way, not only the resource consumption of the terminal can be saved, but also the flexibility and efficiency of the downlink reception of the terminal can be improved. The embodiment of the present application can be applied to, but is not limited to, an XR application scenario. When the embodiment of the present application is applied to the XR application scenario, the service requirement of the XR terminal can be better met, and the requirement of the XR user can be better met. BRIEF DESCRIPTION OF DRAWINGS
[0027] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed in the description of the embodiments of the present application will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without any creative labor on the basis of these drawings.
[0028] FIG. 1 is a structural diagram of a network system provided by an embodiment of the present application;
[0029] FIG. 2 is a schematic diagram of a DRX cycle provided by an embodiment of the present application;
[0030] FIG. 3 is a flowchart of a downlink reception triggering method provided by an embodiment of the present application;
[0031] FIGS. 4 to 9 are example diagrams provided by an embodiment of the present application;
[0032] FIG. 10 is a flowchart of another downlink reception triggering method provided by an embodiment of the present application;
[0033] FIG. 11 is a structural schematic diagram of a terminal provided by an embodiment of the present application;
[0034] FIG. 12 is a structural schematic diagram of a network device provided by an embodiment of the present application;
[0035] FIG. 13 is a hardware structural schematic diagram of a terminal provided by an embodiment of the present application;
[0036] FIG. 14 is a schematic diagram of a hardware structure of a network-side device according to an embodiment of the present application. DETAILED DESCRIPTION
[0037] The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, rather than all the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts should fall within the scope of the present application.
[0038] The term "comprising" and any variation thereof when used in the specification and claims of the present application shall be understood to encompass the inclusion of a stated step or element but not to the exclusion of any additional, unrecited, or inherent steps or elements. Further, the use of "and / or" in the specification and claims of the present application shall be understood to encompass both the conjunctive and disjunctive sense, e.g., A and / or B shall be understood to mean at least one of A, B, and both A and B.
[0039] In the embodiments of the present application, the word "exemplary" or "for example" is used to mean serving as an example, instance, or illustration. Any implementation described as "exemplary" or "for example" in the embodiments of the present application is not necessarily to be construed as preferred or advantageous over other implementations. Rather, the implementations described as "exemplary" or "for example" are intended to deliver a clear conception of the relative scope of the features in question.
[0040] Embodiments of the present application are described below with reference to the accompanying drawings. The embodiments provided by the present application can be applied to a wireless communication system. The wireless communication system can be a 5G system, or an evolved long term evolution (eLTE) system, or a subsequent evolved communication system.
[0041] Fig. 1 is a structural diagram of a network system provided by an embodiment of the present application, as shown in Fig. 1, which includes a terminal 11 and a network-side device 12, wherein the terminal 11 can be a mobile communication device, for example, a mobile phone, a tablet personal computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a personal digital assistant (personal digital assistant, PDA), a mobile internet device (Mobile Internet Device, MID), or a wearable device, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network-side device 12 can be a 5G network-side device (for example, gNB, 5G NR NB), or a 4G network-side device (for example, eNB), or a 3G network-side device (for example, NB), or a network-side device in a subsequent evolved communication system, etc. It should be noted that the specific type of the network-side device 12 is not limited in the embodiment of the present application.
[0042] In order to more appropriately understand the technical solutions of the embodiments of the present application, before the technical solutions of the embodiments of the present application are described, the related technologies of the embodiments of the present application are introduced generally.
[0043] I. XR service
[0044] XR refers to all real and virtual combined environments and human-computer interactions generated by computer technology and wearable devices, which includes Augmented Reality (AR), Mediated Reality (MR), Virtual Reality (VR), and other representative forms, as well as the interpolation areas between them. The level of the virtual world ranges from partial sensory input to fully immersive virtual reality. One key aspect of XR is the extension of human experience, especially the experience related to presence (represented by VR) and cognitive acquisition (represented by AR).
[0045] In the application scenario of XR, the user can obtain information of a new visual angle in a virtual reality experience through head turning and other actions. At this time, the head turning action of the XR user can be sent to the network-side device through an uplink signal, and the network-side device will schedule the required downlink data for the XR user after receiving the uplink signal.
[0046] For XR (not excluding NR light) application scenarios, there will be a process triggered by uplink signals to trigger certain downlink reception. The existing technology does not support the mechanism of triggering downlink reception by uplink signals, which makes the resource consumption of the terminal large, and the flexibility of the terminal to perform downlink reception poor, and cannot well meet the service requirements of XR terminals, thereby cannot well meet the service requirements of XR users.
[0047] II. CDRX (Discontinuous Reception (DRX) in Radio Resource Control (RRC) connected state)
[0048] As shown in FIG. 2, the DRX cycle is composed of “On Duration” and “Opportunity for DRX”: in the time of “On Duration”, the terminal listens and receives PDCCH; in the time of “Opportunity for DRX”, the terminal does not listen to PDCCH to save power consumption. If a new PDCCH is received in onduration, an inactivity timer will be started or restarted to extend the time for the terminal to listen to PDCCH.
[0049] It should be noted that the “timer” involved in the present application can also be referred to as “timer”, that is, the meaning expressed by the “timer” involved in the present application is the same as or similar to the meaning expressed by the “timer”.
[0050] The system can configure the terminal with a short DRX cycle or a long DRX cycle according to different service scenarios. If both short and long cycles are configured, switching between the two long and short cycles can be performed in some way.
[0051] Therefore, the embodiment of the present application provides a method of triggering downlink reception by uplink signals, that is, the downlink reception triggering method provided by the embodiment of the present application.
[0052] FIG. 3 is a flowchart of the downlink reception triggering method provided by the embodiment of the present application. As shown in FIG. 3, the downlink reception triggering method is applied to a terminal, and the method comprises the following steps:
[0053] Step 201: a first uplink signal is sent, and the first uplink signal is used to trigger a first downlink reception.
[0054] In the embodiment of the present application, the terminal can directly trigger the first downlink reception by sending the first uplink signal, without the need for processes such as network side device configuring the first downlink reception, and therefore, triggering the first downlink reception by sending the first uplink signal is different from the existing downlink scheduling and downlink reception mode.
[0055] Triggering the first downlink reception by sending the first uplink signal is different from triggering the downlink reception in the existing scheduling transmission mode. In the existing scheduling transmission mode, for example, the terminal acquires the time-frequency domain resources of the downlink reception allocated by the network side device for itself by listening to the PDCCH, and then the terminal performs the downlink reception on the corresponding resources. In the embodiment of the present application, the terminal triggers the first downlink reception by sending the first uplink signal. The time-frequency domain resources of the first downlink reception and the configuration parameters such as the duration of the first downlink reception can be configured in advance by the network side device or carried by the first uplink signal, and the downlink reception can be triggered without the scheduling process. Therefore, triggering the first downlink reception by sending the first uplink signal can improve the flexibility and efficiency of the downlink reception.
[0056] The first uplink signal is used to trigger the first downlink reception, and it can be understood that there is an association relationship between the first uplink signal and the first downlink reception. After the terminal sends the first uplink signal, it can listen to or receive the first downlink reception according to the association relationship between the first uplink signal and the first downlink reception.
[0057] The association relationship between the first uplink signal and the first downlink reception may, for example, be an association relationship in terms of resource configuration parameters between the first uplink signal and the first downlink reception. Here, the resource configuration parameters may, for example, be time domain configuration parameters, frequency domain configuration parameters, or time-frequency domain configuration parameters, and the like.
[0058] In one embodiment, the first downlink reception is explicitly configured by the resource configuration parameters carried in the first uplink signal, and the network side device sends the first downlink reception according to the configuration parameters indicated by the received first uplink signal. For example, after the terminal sends the first uplink signal, it listens to the first downlink reception in a discontinuous reception manner. In addition, the first downlink reception can include multiple downlink receptions. In other words, the resource configuration parameters corresponding to the first downlink reception are different from the downlink reception resource configuration parameters configured by the network side device according to the RACH or BFR uplink signals sent by the terminal.
[0059] The association relationship between the first uplink signal and the first downlink reception can be established in advance, for example, the association relationship between the first uplink signal and the first downlink reception can be configured in advance by the network side device, or the association relationship between the first uplink signal and the first downlink reception can be agreed in advance by the protocol.
[0060] On the basis of the pre-established association between the first uplink signal and the first downlink reception, the first uplink signal is used to trigger the first downlink reception. It can be understood that the first uplink signal is used to activate the first downlink reception associated with the first uplink signal. More specifically, the first uplink signal is used to activate the first downlink reception under the corresponding resource configuration parameters.
[0061] The first downlink reception can include one or more (including two) downlink receptions. When the first downlink reception includes multiple downlink receptions, each downlink reception can correspond to a downlink reception type. When the first downlink reception includes one downlink reception, the downlink reception can correspond to a downlink reception type or not correspond to a specific type.
[0062] The first downlink reception can include at least one of downlink scheduling information reception, downlink signal reception, downlink data information reception, and downlink channel monitoring.
[0063] That is, the type of the first downlink reception can include at least one of downlink scheduling information, downlink signal, downlink data transmission information, and downlink channel monitoring. Among them, the downlink scheduling information can be, for example, a PDCCH, and downlink control information (DCI) in the PDCCH can be scrambled by a specific radio network temporary identifier, such as a cell radio network temporary identifier I (C-RNT) or a configurable scheduling RNTI (CS-RNTI). The DCI format of the PDCCH can be, for example, DCI 1-1, DCI 0-1, DCI 0-0, DCI 1-0, DCI 1-2, DCI 0-2, etc. The downlink signal can be, for example, a channel state information reference signal (CSI-RS), a CSI interference measurement (CSI-IM), a time reference signal (TRS), a phase-tracking reference signal (PTRS), a positioning reference signal (PRS), a synchronization signal block (SSB), etc. The downlink data transmission information can be, for example, a physical downlink shared channel (PDSCH) reception of semi-persistent scheduling (SPS). The downlink channel monitoring can be, for example, an unscheduled PDCCH, a group common PDCCH, etc. Other downlink channels or downlink signals are not excluded.
[0064] The type of the first uplink signal can include at least one of a type of an uplink channel and a signaling or signal type carried on the uplink channel. The type of the uplink channel can be a physical uplink control channel (PUCCH), a PUSCH (e.g., a PUSCH of a configured grant), a physical random access channel (PRACH) (e.g., Msg1, MsgA PRACH, MsgA PUSCH, Msg3). The periodicity of the uplink channel can be periodic, aperiodic, or semi-persistent. The signaling type or signal type carried on the uplink channel can be uplink control information (UCI), a scheduling request (SR), channel state information (CSI), a hybrid automatic repeat request (HARQ), a media access control (MAC) CE, a sounding reference signal (SRS), or the like. Other uplink channels or uplink signals are not excluded.
[0065] Optionally, the first uplink signal and the first downlink reception have a time-domain association relationship.
[0066] That is, when the association relationship between the first uplink signal and the first downlink reception includes a time-domain association relationship between the first uplink signal and the first downlink reception, the terminal can trigger the first downlink reception under the corresponding time-domain configuration parameter by sending the first uplink signal.
[0067] In the embodiments of the application, the first uplink signal can trigger the first downlink reception in an implicit indication manner, or the first uplink signal can trigger the first downlink reception in an explicit indication manner.
[0068] The following describes the implicit indication manner.
[0069] Optionally, the association relationship between the first uplink signal and the first downlink reception is configured by a network side device or agreed by a protocol.
[0070] In a case that the association relationship between the first uplink signal and the first downlink reception includes an association relationship in time domain between the first uplink signal and the first downlink reception, the association relationship in time domain between the first uplink signal and the first downlink reception can be configured by a network side device or agreed by a protocol.
[0071] Optionally, the method further includes:
[0072] The first downlink reception associated with the first uplink signal is triggered according to at least one of a type of the first uplink signal, a logical channel in which the first uplink signal is located, and a service priority of the first uplink signal.
[0073] In this embodiment, different downlink receptions can be associated by different uplink signal types, different downlink receptions can be associated by different service types of uplink signals, and different downlink receptions can be associated by logical channels in which uplink signals are located.
[0074] For example, when a logical channel in which an uplink signal is located is logical channel 1, the uplink signal is associated with downlink reception 1, that is, the uplink signal corresponding to logical channel 1 can trigger or activate downlink reception 1, so that as long as the terminal sends the first uplink signal corresponding to logical channel 1, the downlink reception 1 is implicitly triggered or activated. In this example, the first uplink signal is the uplink signal corresponding to logical channel 1, and the first downlink reception is downlink reception 1.
[0075] The above is an embodiment in which the first downlink reception is triggered by the first uplink signal in an implicit indication manner.
[0076] The following is described in an explicit indication manner.
[0077] Optionally, the first uplink signal includes first indication information, and the first indication information is used to trigger the first downlink reception.
[0078] The first indication information can include an identifier of the first downlink reception, can include a time domain configuration parameter of the first downlink reception, or can include the identifier and the time domain configuration parameter of the first downlink reception. For example, the terminal can send uplink control signaling (such as MAC CE, UCI, etc.), and the uplink control signaling can explicitly indicate the first downlink reception triggered or activated by the uplink control signaling.
[0079] The first downlink reception triggered by the first indication information can be pre-configured by a network side device or pre-agreed by a protocol. For example, the first downlink reception triggered by the first indication information can be configured by RRC. The first downlink reception triggered by the first indication information can include one or more downlink receptions, or the first indication information can trigger multiple first downlink receptions.
[0080] Optionally, the first indication information is used to trigger M first downlink receptions in N downlink receptions, the N downlink receptions are configured by a network side device or agreed by a protocol, and the N and M are integers greater than or equal to 1.
[0081] For example, the RRC configures N downlink receptions, the first indication information is contained in the first uplink signal, and the first indication information is used to trigger or activate M downlink receptions in the N downlink receptions. The M downlink receptions are the first downlink receptions, or the M downlink receptions are M first downlink receptions respectively.
[0082] Optionally, if the M is greater than 1, the method further includes:
[0083] After the first uplink signal is sent, a first downlink control information (DCI) is received.
[0084] K downlink receptions in the M downlink receptions are triggered by the first DCI, the first downlink receptions include the K downlink receptions, and the K is an integer greater than or equal to 1.
[0085] For example, the RRC configures N downlink receptions, the first indication information is contained in the first uplink signal, and the first indication information is used to trigger or activate M downlink receptions in the N downlink receptions. In the downlink receptions, K downlink receptions in the M downlink receptions are dynamically triggered or activated by receiving a DCI.
[0086] The above is an implementation of triggering the first downlink reception by the first uplink signal in an explicit indication manner.
[0087] Optionally, time domain configuration parameters of the first downlink reception are configured by a network side device or agreed by a protocol.
[0088] In the embodiment of the application, the association relationship between the first uplink signal and the first downlink reception can be configured by a network side device or agreed by a protocol. Further, the association relationship between the first uplink signal and the first downlink reception in the time domain can be configured by a network side device or agreed by a protocol. Still further, time domain configuration parameters of the first downlink reception can be configured by a network side device or agreed by a protocol.
[0089] The following describes related implementations of time domain configuration parameters of the first downlink reception.
[0090] Optionally, the time domain configuration parameters of the first downlink reception include at least one of the following:
[0091] A time domain starting moment of the first downlink reception;
[0092] a time domain starting moment of the first downlink reception;
[0093] a duration of the first downlink reception;
[0094] a first periodicity parameter of the first downlink reception, the first periodicity parameter comprising at least one of a first periodicity length, an activation time length of the first periodicity, and an activation time starting position offset of the first periodicity.
[0095] optionally, the time domain starting moment of the first downlink reception is any one of:
[0096] a reference moment, the reference moment being an ending moment of a time domain resource where the first uplink signal is located;
[0097] a first moment, the first moment being a moment that is spaced apart from the reference moment by a first time interval;
[0098] a starting moment of a first available downlink time domain resource after the reference moment;
[0099] a starting moment of a time domain resource after a first timer expires, the first timer being started at the reference moment;
[0100] a starting moment of a first available downlink time domain resource after the first moment;
[0101] a starting moment of a first available downlink time domain resource after the first timer expires.
[0102] The time domain starting moment of the first downlink reception can be an ending moment of a time domain resource where the first uplink signal is located, that is, the terminal can start the first downlink reception immediately after the first uplink signal is sent.
[0103] The time domain starting moment of the first downlink reception can also be the first moment, and a time interval between the first moment and an ending moment of a time domain resource where the first uplink signal is located is the first time interval, that is, the terminal can start the first downlink reception after a first time interval after the first uplink signal is sent, and the first time interval can be configured by a network side device or agreed by a protocol. Further, the network side device can configure multiple first time interval parameters, and the terminal can carry an indication about the first time interval in the first uplink signal. For example, the first time interval can be equal to a time interval K1 of a PDSCH and a HARQ-ACK feedback thereof, and a value set of the K1 is pre-configured by the network side device; or the first time interval can be equal to a time interval between sending a BFRQ (beam failure recovery request) and receiving a BFRR (beam failure recovery response); or the first time interval can be equal to a time interval between sending a RACH and receiving a RAR response.
[0104] The time-domain starting moment of the first downlink reception can also be the starting moment of the first available downlink time-domain resource after the ending moment of the time-domain resource where the first uplink signal is located, that is, the terminal can start the first downlink reception at the first available downlink time-domain resource after the first uplink signal is sent, and the downlink time-domain resource can be a DL subframe, a DL slot, a DL slot containing a CORESET, and the like.
[0105] The time-domain starting moment of the first downlink reception can also be the time-domain resource starting moment after the expiration of the first timer triggered at the ending moment of the time-domain resource where the first uplink signal is located, that is, the terminal triggers the first timer immediately after the first uplink signal is sent, and starts the first downlink reception after the expiration of the first timer.
[0106] The time-domain starting moment of the first downlink reception can also be the starting moment of the first available downlink time-domain resource after the first time interval, that is, the terminal can start the first downlink reception at the first available downlink time-domain resource after the first time interval after the first uplink signal is sent.
[0107] The time-domain starting moment of the first downlink reception can also be the starting moment of the first available downlink time-domain resource after the expiration of the first timer triggered immediately after the first uplink signal is sent, that is, the terminal starts the first downlink reception at the first available downlink time-domain resource after the expiration of the first timer.
[0108] The first time interval can be reported by the terminal according to the capability, or the size of the first time interval can be agreed according to different subcarrier space (SCS) levels, or the terminal can report the first time interval, and the value of the first time interval is not specifically limited.
[0109] In addition, in addition to the above-mentioned time-domain starting moment, the first uplink signal can also include position information (such as a given offset) of the starting moment, and the time-domain starting moment of the first downlink reception is determined according to the starting moment information.
[0110] Optionally, the duration of the first downlink reception includes any one of the first time length and the second timer length.
[0111] In this embodiment, the duration of the first downlink reception can be represented by a first time length, which can be configured by the network side device or agreed by the protocol. The duration of the first downlink reception can also be represented by a second timer length, which can be configured by the network side device or agreed by the protocol.
[0112] Optionally, the time domain monitoring manner of the first downlink reception comprises any one of the following:
[0113] monitoring the first downlink reception within the duration of the first downlink reception;
[0114] monitoring the first downlink reception within the active time of each first cycle within the duration of the first downlink reception;
[0115] monitoring the first downlink reception within the active time of each first cycle within the duration of the first downlink reception.
[0116] If the duration of the first downlink reception is configured, the terminal can monitor the first downlink reception within the duration of the first downlink reception, or in other words, the terminal can uninterruptedly perform the first downlink reception within the duration of the first downlink reception. For example, if the duration of the first downlink reception is a first time length, the terminal can monitor the first downlink reception within the first time length. For another example, if the duration of the first downlink reception is a second timer length, the terminal can monitor the first downlink reception within the second timer length, or in other words, the terminal can uninterruptedly perform the first downlink reception within the second timer length. After the second timer expires, the terminal can exit the first downlink reception triggered by the first uplink signal, and if the terminal receives downlink scheduling information and / or downlink data sending information within the second timer length, the terminal can restart the second timer.
[0117] The terminal can also monitor the first downlink reception in a discontinuous reception manner, i.e., in a periodic time domain monitoring manner. For example, the terminal can monitor the first downlink reception within the active time of each first cycle. The first cycle includes an active time and an inactive time, and the terminal only needs to receive or monitor the first downlink reception within the active time, and does not need to receive or monitor the first downlink reception within the inactive time. The discontinuous reception given in this embodiment can further save the power of the terminal, and is a preferred time domain monitoring manner of the first downlink reception. The first cycle can be a long DRX cycle or a short DRX cycle. If the first cycle is configured as a DRX cycle, the related timers and parameters of the DRX cycle can be further applied to the downlink reception. For example, a DRX-inactivity timer in the DRX cycle.
[0118] The two time-domain monitoring manners can also be combined. For example, the terminal can monitor the first downlink reception in the active time of each first period within the duration of the first downlink reception. In this manner, if the duration of the first downlink reception is a first time length, the monitoring manner is that the terminal can monitor the first downlink reception in the active time of each first period within the first time length of the first downlink reception; if the duration of the first downlink reception is a second timer time length, the monitoring manner is that the terminal can monitor the first downlink reception in the active time of each first period within the running time of the second timer of the first downlink reception. Further, after the duration of the first downlink reception ends, the terminal can no longer use the periodic downlink reception manner.
[0119] In addition, the duration of the first downlink reception can also be carried by the first uplink signal.
[0120] Optionally, the method further comprises:
[0121] If the terminal does not receive Q downlink receptions in the first downlink reception in the active time of L consecutive first periods, the terminal stops monitoring the first downlink reception, where 1≤Q≤L, and L and Q are integers greater than or equal to 1.
[0122] In this embodiment, for the case that the terminal periodically receives the first downlink reception, the time-domain monitoring manner of discontinuous reception is used. If the terminal does not receive downlink scheduling and / or downlink data in the active time of L consecutive first periods, the terminal can exit the first downlink reception, or in other words, the terminal can exit the first downlink reception triggered by the first uplink signal.
[0123] For example, the terminal monitors the first downlink reception in the active time of each first period. If the terminal does not receive any one or more downlink receptions or all downlink receptions in the first downlink reception in the active time of 3 consecutive first periods, the terminal stops monitoring the first downlink reception. For another example, the terminal monitors the first downlink reception in the active time of each first period within the duration of the first downlink reception. If the terminal does not receive all downlink receptions in the first downlink reception in the active time of 3 first periods within the duration of the first downlink reception, the terminal stops monitoring the first downlink reception.
[0124] This embodiment can achieve energy saving of the terminal.
[0125] Optionally, the active time of the first period is indicated by a bitmap method.
[0126] For the active time of the first period described above, the duration can also be indicated.
[0127] For example, "11000" represents a first period, wherein each bit represents 2 ms, the length of the whole first period is 10 ms, and the first 2 bits of 1 represent the active time of the first period and the length of the active time is 4 ms, and the last 3 bits represent the inactive time of the first period and the length of the inactive time is 6 ms.
[0128] Optionally, if the first downlink reception contains the reception of a PDCCH, the time domain configuration parameter of the first downlink reception comprises at least one of the following:
[0129] a blind detection parameter of the PDCCH;
[0130] a monitoring period of the PDCCH;
[0131] a monitoring offset of the PDCCH;
[0132] a monitoring duration of the PDCCH;
[0133] a control resource set (CORESET);
[0134] a search space group;
[0135] a search space;
[0136] a DCI format;
[0137] an RNTI (Radio Network Temporary Identity);
[0138] a time interval between the PDCCH and a physical downlink shared channel (PDSCH) scheduled by the PDCCH;
[0139] a time interval between the PDSCH and a hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback of the PDSCH;
[0140] a time interval between the PDCCH and a physical uplink shared channel (PUSCH) scheduled by the PDCCH;
[0141] a processing delay of the PDSCH;
[0142] a preparation delay of the PUSCH.
[0143] The time interval related to the PDCCH can include K0, K1, and K2, all of which are in units of slots. K0 is the time interval between the slot in which the DCI (or the PDCCH corresponding to the DCI) is located and the slot in which the PDSCH scheduled by the DCI is located. K2 is the time interval between the slot in which the DCI (or the PDCCH corresponding to the DCI) is located and the slot in which the PUSCH scheduled by the DCI is located. For example, K0 = 0 indicates that the PDCCH and the PDSCH scheduled thereby are in one slot. K1 is the time interval between the slot in which the PDSCH is located and the slot in which the HARQ-ACK feedback is located, that is, the offset in slots.
[0144] The processing delay of the PDSCH refers to the time interval from when the PDCCH schedules the PDSCH to when the HARQ-ACK feedback corresponding to the PDSCH is ready to be sent. The processing delay of the PDSCH is different from K1, which determines the slot in which the HARQ-ACK feedback is performed. However, the processing delay of the PDSCH refers to the time interval that the terminal needs to process after receiving the PDSCH before the HARQ-ACK feedback is ready. That is, K1 must be greater than or equal to the processing delay of the PDSCH.
[0145] The preparation delay of the PUSCH refers to the time interval that the terminal needs to prepare the transmission of the PUSCH scheduled by the PDCCH after receiving the PDCCH. The preparation delay of the PUSCH is different from K2, which determines the slot in which the PUSCH is transmitted. However, the preparation delay of the PUSCH refers to the time interval that the terminal needs to prepare after receiving the PDCCH before the PUSCH is ready to be transmitted. That is, K2 must be greater than or equal to the processing delay of the PUSCH.
[0146] It should be noted that any one or more or all of the time domain configuration parameters of the first downlink reception can be configured by the network side or agreed by the protocol together with other time domain configuration parameters, for example, any one or more or all of the time domain configuration parameters of the first downlink reception can be configured together with any one or more or all of the time domain starting time, the time domain monitoring manner, the time domain duration, and the first periodicity parameter of the first downlink reception. In addition, any one or more or all of the time domain configuration parameters of the first downlink reception can be carried by the first uplink signal together with other time domain configuration parameters.
[0147] Optionally, the association relationship is configured for at least one of a specific terminal, a specific media access control (Media Access Control, MAC) entity, a specific service type, and a specific frequency range.
[0148] Alternatively, the mechanism of triggering the first downlink reception by the first uplink signal can be configured for use by a specific terminal, or for use by a specific MAC entity (such as a MAC entity of an SCG, a MAC entity of an MCG), or for use by a specific service type (such as a specific logical channel (such as logical channel 1)), or for use by a specific frequency range (such as cell 1, BWP 1). The frequency range can be a BWP, a serving cell, or a component carrier. In addition, the association between the uplink signal and the downlink reception for each service type can be configured, which means that the configuration parameters of the mechanism of triggering the first downlink reception by the first uplink signal can be the same or different. The association between the uplink signal and the downlink reception for each BWP of the terminal can also be configured, which means that the configuration parameters of the mechanism of triggering the first downlink reception by the first uplink signal can be the same or different.
[0149] In this embodiment, the mechanism of triggering the first downlink reception by the first uplink signal can be flexibly configured according to specific requirements, which can improve the flexibility of downlink reception of the terminal.
[0150] Optionally, the method further comprises:
[0151] receiving a first message sent by the network side device, the first message being used to instruct the terminal to stop receiving at least one downlink reception in the first downlink reception.
[0152] In this embodiment, the network side device can configure a stop mechanism of the first downlink reception triggered by the first uplink signal, for example, the network side device configures a stop command (such as a MAC CE command, a DCI) for stopping any one or more downlink receptions or all downlink receptions in the first downlink reception currently performed by the terminal. After receiving the first message sent by the network side device, the terminal can stop any one or more downlink receptions or all downlink receptions in the first downlink reception according to the instruction of the first message.
[0153] In this embodiment, the terminal can stop the downlink reception triggered by the uplink signal according to the instruction of the network side device, which is beneficial to improve the working performance and efficiency of the communication system.
[0154] Optionally, the method further comprises:
[0155] receiving a second message sent by the network side device, the second message being used to instruct the terminal to switch the reception period of the first downlink reception from the first period to a second period; the second period being different from the first period in at least one of the period length, the active time length of the period, and the active time starting position offset of the period.
[0156] In this embodiment, the network-side device can configure a dual-cycle switching mechanism for the first downlink reception triggered by the first uplink signal, which is similar to a short DRX cycle and a long DRX cycle switching mechanism. For example, the network-side device can issue a switching command (such as a MAC CE command or a DCI) to instruct the terminal to switch the cycle of the discontinuous reception of the first downlink reception.
[0157] After receiving the second message sent by the network-side device, the terminal can switch the cycle of the first downlink reception to the second cycle according to the indication of the second message. In this way, the flexibility of the first downlink reception can be improved, and the performance of the communication system can be improved.
[0158] Optionally, if the terminal sends a second uplink signal in the duration of the first downlink reception, the second uplink signal is used to trigger a second downlink reception, and the method further includes:
[0159] performing the first downlink reception and the second downlink reception in parallel; or
[0160] only performing the second downlink reception.
[0161] In this embodiment, if the terminal sends another uplink signal (i.e., a second uplink signal) for triggering a second downlink reception in the duration of the first downlink reception triggered by the first uplink signal (i.e., the first downlink reception has not ended), the downlink reception time configuration for this case can include any of the following.
[0162] First, the terminal performs multiple downlink receptions triggered by uplink signals in parallel, or the terminal performs parallel monitoring of the first downlink reception and the second downlink reception. Each uplink signal triggers a monitoring configuration of a downlink reception, for example, a new timer is triggered each time an uplink signal is sent, and the terminal needs to meet the monitoring configuration of the downlink reception triggered by any uplink signal.
[0163] Second, the terminal only performs the downlink reception triggered by a certain uplink signal, or the terminal can only maintain the monitoring configuration of a certain downlink reception. Each time the terminal sends a new uplink signal, the terminal can stop the currently ongoing downlink reception and start a new downlink reception in the monitoring configuration of the new downlink reception. Of course, it is also possible that the terminal continues the currently ongoing downlink reception each time a new uplink signal is sent.
[0164] Optionally, in the case of performing the first downlink reception and the second downlink reception in parallel, if the first downlink reception and the second downlink reception have one or more resource conflicts, the method further includes:
[0165] perform the second downlink reception on the conflicting resources and abandon the first downlink reception; or
[0166] perform the first downlink reception on the conflicting resources and abandon the second downlink reception; or
[0167] determine, according to at least one of a type, a logical channel, and a service priority of the first uplink signal and the second uplink signal, the downlink reception to be performed from the first downlink reception and the second downlink reception on the conflicting resources.
[0168] The resource conflict includes at least one of a time domain resource conflict and a frequency domain resource conflict.
[0169] The embodiment can also be expressed as follows:
[0170] In a case where the first downlink reception and the second downlink reception are performed in parallel, if the first downlink reception and the second downlink reception have one or more resource conflicts, the method further includes:
[0171] receiving a downlink signal in the second downlink reception that conflicts with the first downlink reception and abandoning receiving a downlink signal in the first downlink reception that conflicts with the second downlink reception; or
[0172] receiving a downlink signal in the first downlink reception that conflicts with the second downlink reception and abandoning receiving a downlink signal in the second downlink reception that conflicts with the first downlink reception; or
[0173] determining, according to at least one of a type, a logical channel, and a service priority of the first uplink signal and the second uplink signal, a downlink signal to be received from a downlink signal that conflicts between the first downlink reception and the second downlink reception.
[0174] In the embodiment, when the two downlink receptions have one or more resource conflicts, the terminal can preferentially receive a downlink signal of a downlink reception triggered later and abandon a downlink signal of a downlink reception triggered earlier; the terminal can also preferentially receive a downlink signal of a downlink reception triggered earlier and abandon a downlink signal of a downlink reception triggered later; the terminal can also determine a downlink signal to be received or a downlink signal to be abandoned according to at least one of a type, a logical channel, and a service priority of an uplink signal.
[0175] In this embodiment, the resource conflict can be a time-domain resource conflict only, a frequency-domain resource conflict only, or a time-frequency-domain resource conflict.
[0176] It should be noted that the various optional embodiments in the embodiments of the present application can be combined with each other to implement, or can be implemented independently, and the embodiments of the present application do not limit this.
[0177] In order to better understand the technical solutions of the embodiments of the present application, three specific embodiments are provided below.
[0178] Embodiment one
[0179] As shown in FIGS. 4 to 6, in this embodiment, the network side device pre-configures the association relationship between the uplink signal and the downlink reception, and completes the process of triggering the downlink reception by the uplink signal through implicit indication. The uplink signal triggering downlink reception mechanism is configured for each logical channel. The uplink signal is PUSCH triggering of configurable scheduling (CG), and the time-domain monitoring mode of the downlink reception adopts the discontinuous reception mode of the short DRX cycle. The network configures the first timer of the starting time of the related downlink reception as the length of the waiting monitoring timer and the duration of the downlink reception = delay budget; the set of waiting monitoring timers and the retransmission timers related to the HARQ process in the DRX configured by the DRX can be used at the same time; a MAC CE command is agreed to forcibly stop all ongoing downlink receptions triggered by the uplink signal.
[0180] The network side device pre-configures the association relationship between the uplink signal and the downlink reception. For example, logical channel 1 is mapped to the PUSCH of CG1, and is associated with downlink reception 1 and downlink reception 2; logical channel 2 is mapped to the PUSCH of CG2, and is associated with downlink reception 3.
[0181] The configuration information corresponding to the downlink reception 1 and the downlink reception 2 is basically the same: the same downlink reception time-domain starting time, downlink reception monitoring configuration (using a short DRX cycle, a set of downlink reception waiting monitoring timers and duration delay budget). Among them, the downlink reception types of the two are different, the downlink reception 1 is a semi-persistent SPS PDSCH reception. The downlink reception 2 is a DCI format 1-2 and 0-2 scrambled by C-RNTI.
[0182] The terminal waits for the listening timer to determine the time-domain starting moment of the downlink reception. The duration timer (valid duration) of the downlink reception is set as the delay budget, and after the expiration, the uplink CG triggered by this time is immediately stopped. The downlink reception related listening timer, duration, DRX-HARQ-RTT-TimerDL (downlink DRX-HARQ round trip time timer) and DRX-RetransmissionTimerDL (downlink DRX retransmission timer) in the DRX can coexist.
[0183] In this embodiment, the terminal is configured with a long DRX cycle before receiving the uplink signal triggered downlink reception.
[0184] After the terminal sends the PUSCH of the uplink CG1, the "listening timer" is triggered immediately, and after the expiration of the timer, the short DRX cycle is started immediately, and the downlink scheduling (downlink reception 2) and the reception of the SPS downlink data (downlink reception 1) are performed. In this embodiment, the downlink reception of CG1 uses the configuration related to the short DRX cycle: for example, DRX-ondurationtimer (DRX duration timer) and DRX-inactivitytimer (DRX inactivity timer).
[0185] The configuration information corresponding to the downlink reception 3 is the periodic CSI-RS. The same set of downlink reception listening timer and duration delay budget as the downlink reception 1 and the downlink reception 2. In addition, according to the configured listening period (the period is a newly defined period configuration, not a DRX period), the downlink reception is performed in the active time of each period: the active time position and the duration length are indicated by the bitmap in two slots "11000", indicating that the first 4 slots are active time and the last 6 slots are inactive time.
[0186] The terminal is originally configured with a long DRX cycle. The terminal sends the uplink CG1 PUSCH (data of logical channel 1) and / or CG2 PUSCH (data of logical channel 2) to the network side device, and combines the related configuration in this scheme to give a typical example of the uplink signal triggered downlink reception scheme:
[0187] Example 1: As shown in FIG. 4, only one CG1 PUSCH triggers the downlink reception process, that is, the configuration of the single CG1 PUSCH triggering the downlink reception.
[0188] In FIG. 4, the dashed arrow represents the downlink reception 1: SPS PDSCH reception; and the solid arrow represents the downlink reception 2: PDCCH scheduling.
[0189] Example 2: As shown in FIG. 5, if another uplink CG2 is sent within the duration of the downlink reception triggered by the uplink CG1 (i.e. before the current downlink reception ends), the method of configuring multiple downlink receptions in parallel triggered by multiple uplink signals is selected; the network side device configures a MAC CE command to stop the downlink reception currently being performed. That is, multiple CG PUSCHs overlap, multiple sets of downlink reception configurations need to be met, and a MAC CE command is configured.
[0190] In FIG. 5, the dashed arrow represents downlink reception 1: SPS PDSCH reception; the solid arrow represents downlink reception 2: PDCCH scheduling; and the dotted arrow represents downlink reception 3: CSI-RS.
[0191] Example 3: As shown in FIG. 6, if another uplink CG2 is sent within the duration of the downlink reception triggered by the uplink CG1 (i.e. before the current downlink reception ends), the method of configuring only one downlink reception triggered by one uplink signal is selected, and the network side device does not configure a MAC CE command. That is, multiple CG PUSCHs overlap, the previous downlink reception is stopped, a new downlink reception is started, and no MAC CE command is configured.
[0192] In FIG. 6, the dashed arrow represents downlink reception 1: SPS PDSCH reception; the solid arrow represents downlink reception 2: PDCCH scheduling; and the dotted arrow represents downlink reception 3: CSI-RS.
[0193] Embodiment Two
[0194] This embodiment focuses on the association between uplink signals and downlink receptions and the explicit indication method.
[0195] In this embodiment, the terminal is not configured with a DRX mechanism before receiving the downlink reception triggered by the uplink signal. The terminal sends a MAC CE to the network side device, and the ID of the activated downlink reception is carried in the MAC CE.
[0196] Example 1: As shown in FIG. 7, 5 downlink receptions are configured by RRC, and the 5 uplink receptions are numbered. The terminal sends an uplink control signaling MAC CE to explicitly activate one of the downlink receptions: downlink reception 2.
[0197] Example 2: As shown in FIG. 8, 5 downlink receptions are configured by RRC, and the 5 uplink receptions are numbered. The terminal sends an uplink control signaling MAC CE to explicitly activate 3 of the downlink receptions: downlink receptions 2, 3, and 4. After starting the downlink receptions, a DCI is used to dynamically indicate the activation of one of the 3 downlink receptions: downlink reception 2.
[0198] The configuration information of the downlink reception 2 is that the downlink reception type is a group common PDCCH (PDCCH) scrambled by a C-RNTI, and a set of downlink reception waiting listening N and a time duration timer. After the terminal sends an uplink SR, after N symbols or N ms or N slots, the time duration timer is started and the downlink scheduling reception is started. If the unit of N is a symbol or a slot, the value of N is related to the configuration of SCS. In this example, N is set to 5 ms. The timer is restarted after receiving the downlink scheduling PDCCH in the time duration timer. After the timer expires, the downlink reception in this example is exited.
[0199] Embodiment three
[0200] This embodiment focuses on the method of triggering downlink reception by uplink signal. The downlink reception triggered by the uplink signal is configured to a specific BWP1.
[0201] In this embodiment, the terminal is configured with a long DRX cycle before receiving the downlink reception triggered by the uplink signal. The terminal sends uplink signaling UCI on BWP1, and explicitly carries the configuration information of the downlink reception triggered by the UCI: the time domain starting time of the downlink reception, the listening configuration of the downlink reception, the duration of the downlink reception, and the type of the downlink reception.
[0202] As shown in FIG. 9, the time domain starting time of the downlink reception is the start of the first DL slot containing the CORESET after the UCI. The listening configuration of the downlink reception is a short DRX cycle with a period of 2 ms and an offset of 0. The type of the downlink reception is a periodic PTRS. The duration of the downlink reception is 10 ms.
[0203] The above three embodiments are only exemplary and do not limit the embodiments of the present application.
[0204] In the embodiments of the present application, the terminal can trigger the corresponding downlink reception by sending an uplink signal, which not only saves the resource consumption of the terminal and is beneficial to the energy saving of the terminal, but also improves the flexibility and efficiency of the downlink reception of the terminal. The embodiments of the present application can be applied to but not limited to XR application scenarios, and when the embodiments of the present application are applied to XR application scenarios, the business needs of XR terminals can be better met, and the needs of XR users can be better met.
[0205] FIG. 10 is a flowchart of a downlink reception triggering method according to an embodiment of the present application. As shown in FIG. 10, the downlink reception triggering method is applied to a network side device, and the method comprises the following steps:
[0206] Step 301: receiving a first uplink signal sent by a terminal, the first uplink signal being used to trigger a first downlink reception.
[0207] Optionally, the first uplink signal and the first downlink reception have a time-domain association relationship.
[0208] Optionally, the association relationship is configured by a network-side device or agreed by a protocol.
[0209] Optionally, the first uplink signal includes first indication information, the first indication information being used to trigger M first downlink receptions in N downlink receptions, the N downlink receptions being configured by a network-side device or agreed by a protocol, and the N and M are integers greater than or equal to 1.
[0210] Optionally, the first indication information includes at least one of an identifier of the first downlink reception and a time-domain configuration parameter of the first downlink reception.
[0211] Optionally, the time-domain configuration parameter of the first downlink reception is configured by a network-side device or agreed by a protocol.
[0212] Optionally, the time-domain configuration parameter of the first downlink reception includes at least one of:
[0213] a time-domain starting moment of the first downlink reception;
[0214] a time-domain monitoring manner of the first downlink reception;
[0215] a duration of the first downlink reception;
[0216] a first periodicity parameter of the first downlink reception, the first periodicity parameter including at least one of a first periodicity length, an active time length of a first periodicity, and an active time starting position offset amount of the first periodicity.
[0217] Optionally, the time-domain starting moment of the first downlink reception is any one of:
[0218] a reference moment, the reference moment being an ending moment of a time-domain resource where the first uplink signal is located;
[0219] a first moment, the first moment being a moment that is spaced apart from the reference moment by a first time interval;
[0220] a starting moment of a first available downlink time-domain resource after the reference moment;
[0221] a time-domain resource starting moment after a first timer expires, the first timer being started at the reference moment;
[0222] a starting moment of a first available downlink time domain resource after the first moment;
[0223] a starting moment of a first available downlink time domain resource after the first timer expires.
[0224] Optionally, the duration of the first downlink reception comprises any one of a first time length and a second timer length.
[0225] Optionally, the time domain monitoring manner of the first downlink reception comprises any one of:
[0226] monitoring the first downlink reception within the duration of the first downlink reception;
[0227] monitoring the first downlink reception within an activation time of each of the first periodicities;
[0228] monitoring the first downlink reception within an activation time of each of the first periodicities within the duration of the first downlink reception.
[0229] Optionally, the activation time of the first periodicity is indicated by a bitmap.
[0230] Optionally, if the first downlink reception comprises a reception of a physical downlink control channel (PDCCH), the time domain configuration parameter of the first downlink reception comprises at least one of:
[0231] a blind detection parameter of the PDCCH;
[0232] a monitoring periodicity of the PDCCH;
[0233] a monitoring offset of the PDCCH;
[0234] a monitoring duration of the PDCCH;
[0235] a control resource set (CORESET);
[0236] a search space group;
[0237] a search space;
[0238] a DCI format;
[0239] a radio network temporary identifier (RNTI);
[0240] a time interval between the PDCCH and a physical downlink shared channel (PDSCH) scheduled by the PDCCH;
[0241] a time interval between the PDSCH and a HARQ-ACK feedback of the PDSCH;
[0242] a time interval between the PDCCH and a physical uplink shared channel (PUSCH) scheduled by the PDCCH;
[0243] a processing delay of the PDSCH;
[0244] a preparation delay of the PUSCH.
[0245] Optionally, the association relationship is configured for at least one of a specific terminal, a specific medium access control (MAC) entity, a specific service type, and a specific frequency range.
[0246] Optionally, the type of the first uplink signal comprises at least one of a type of an uplink channel and a type of a signal carried on the uplink channel.
[0247] Optionally, the first downlink reception comprises at least one of downlink scheduling information reception, downlink signal reception, downlink data information reception, and downlink channel listening.
[0248] Optionally, the method further comprises:
[0249] sending a first message to the terminal, the first message being used to instruct the terminal to stop receiving at least one of the first downlink reception.
[0250] Optionally, the method further comprises:
[0251] sending a second message to the terminal, the second message being used to instruct the terminal to switch a receiving period of the first downlink reception from the first period to a second period; the second period being different from the first period in at least one of a period length, an active time length of a period, and a starting position offset of an active time of a period.
[0252] Optionally, the first downlink reception comprises a plurality of downlink receptions, each downlink reception corresponding to a type of downlink reception.
[0253] It should be noted that the embodiment of the present application as the embodiment of the network side device corresponding to the foregoing embodiment can refer to the related description of the foregoing embodiment and achieve the same beneficial effects. To avoid repeated description, details are not described here.
[0254] FIG. 11 is a structure diagram of a terminal according to an embodiment of the present application. As shown in FIG. 11, the terminal 400 comprises:
[0255] a sending module 401 configured to send a first uplink signal, the first uplink signal being used to trigger a first downlink reception.
[0256] Optionally, the first uplink signal and the first downlink reception have an association relationship in a time domain.
[0257] Optionally, the association relationship is configured by a network side device or is agreed by a protocol.
[0258] Optionally, the terminal 400 further comprises:
[0259] a first triggering module, configured to trigger the first downlink reception associated with the first uplink signal according to at least one of a type of the first uplink signal, a logical channel where the first uplink signal is located, and a service priority of the first uplink signal.
[0260] Optionally, the first uplink signal comprises first indication information, and the first indication information is used to trigger M first downlink receptions in N downlink receptions, the N downlink receptions are configured by a network side device or are agreed by a protocol, and the N and the M are integers greater than or equal to 1.
[0261] Optionally, if the M is greater than 1, the terminal 400 further comprises:
[0262] a first receiving module, configured to receive first downlink control information DCI after the first uplink signal is sent;
[0263] a second triggering module, configured to trigger K first downlink receptions in the M first downlink receptions by the first DCI, the K being an integer greater than or equal to 1.
[0264] Optionally, the first indication information comprises at least one of an identifier of the first downlink reception and a time domain configuration parameter of the first downlink reception.
[0265] Optionally, the time domain configuration parameter of the first downlink reception is configured by a network side device or is agreed by a protocol.
[0266] Optionally, the time domain configuration parameter of the first downlink reception comprises at least one of:
[0267] a time domain starting moment of the first downlink reception;
[0268] a time domain monitoring manner of the first downlink reception;
[0269] a time duration of the first downlink reception;
[0270] a first period parameter of the first downlink reception, the first period parameter comprising at least one of a first period length, an activation time length of the first period, and an activation time starting position offset amount of the first period.
[0271] Optionally, the time domain starting moment of the first downlink reception is any one of:
[0272] a reference time, the reference time being an ending time of a time domain resource where the first uplink signal is located;
[0273] a first time, the first time being a time that is separated from the reference time by a first time interval;
[0274] a starting time of a first available downlink time domain resource after the reference time;
[0275] a starting time of a time domain resource after a first timer expires, the first timer being started at the reference time;
[0276] a starting time of a first available downlink time domain resource after the first time;
[0277] a starting time of a first available downlink time domain resource after the first timer expires.
[0278] Optionally, the duration of the first downlink reception comprises any one of a first time length and a second timer length.
[0279] Optionally, the time domain monitoring manner of the first downlink reception comprises any one of the following:
[0280] monitoring the first downlink reception within the duration of the first downlink reception;
[0281] monitoring the first downlink reception within an active time of each of the first periods;
[0282] monitoring the first downlink reception within an active time of each of the first periods within the duration of the first downlink reception.
[0283] Optionally, the terminal 400 further comprises:
[0284] a stopping monitoring module, configured to stop monitoring the first downlink reception if Q downlink receptions in the first downlink reception are not received within active times of L consecutive first periods, wherein 1≤Q≤L, and L and Q are integers greater than or equal to 1.
[0285] Optionally, the active time of the first period is indicated by a bitmap.
[0286] Optionally, if the first downlink reception comprises a reception of a physical downlink control channel (PDCCH), the time domain configuration parameter of the first downlink reception comprises at least one of the following:
[0287] a blind detection parameter of the PDCCH;
[0288] a monitoring period of the PDCCH;
[0289] a monitoring offset of the PDCCH.
[0290] monitoring duration of the PDCCH;
[0291] control resource set (CORESET);
[0292] search space group;
[0293] search space;
[0294] DCI format;
[0295] radio network temporary identifier (RNTI);
[0296] time interval between the PDCCH and a physical downlink shared channel (PDSCH) scheduled by the PDCCH;
[0297] time interval between the PDSCH and a HARQ-ACK feedback of the PDSCH;
[0298] time interval between the PDCCH and a physical uplink shared channel (PUSCH) scheduled by the PDCCH;
[0299] processing delay of the PDSCH;
[0300] preparation delay of the PUSCH.
[0301] Optionally, the association relationship is configured for at least one of a specific terminal, a specific medium access control (MAC) entity, a specific service type, and a specific frequency range.
[0302] Optionally, the first downlink reception includes at least one of downlink scheduling information reception, downlink signal reception, downlink data information reception, and downlink channel monitoring.
[0303] Optionally, the type of the first downlink reception includes at least one of downlink scheduling information, downlink signal, downlink data transmission information, and downlink channel monitoring.
[0304] Optionally, the terminal 400 further includes:
[0305] a second receiving module, configured to receive a first message sent by a network side device, the first message being used to instruct the terminal to stop receiving at least one of the first downlink reception.
[0306] Optionally, the terminal 400 further includes:
[0307] The third receiving module is configured to receive a second message sent by the network-side device, the second message being used to instruct the terminal to switch the receiving period of the first downlink reception from the first period to a second period, wherein the second period is different from the first period in at least one of the period length, the length of the active time of the period, and the starting position offset of the active time of the period.
[0308] Optionally, if the terminal sends a second uplink signal in the duration of the first downlink reception, the second uplink signal being used to trigger a second downlink reception, the terminal 400 further comprises:
[0309] The first downlink reception module is configured to perform the first downlink reception and the second downlink reception in parallel, or
[0310] The second downlink reception module is configured to perform only the second downlink reception.
[0311] Optionally, in the case of performing the first downlink reception and the second downlink reception in parallel, if the first downlink reception and the second downlink reception occur one or more resource conflicts, the terminal further comprises:
[0312] The third downlink reception module is configured to perform the second downlink reception on the conflicting resources and abandon the first downlink reception, or
[0313] The fourth downlink reception module is configured to perform the first downlink reception on the conflicting resources and abandon the second downlink reception, or
[0314] The determining module is configured to determine the downlink reception to be performed from the first downlink reception and the second downlink reception according to at least one of the type of the first uplink signal and the second uplink signal, the logical channel where the first uplink signal and the second uplink signal are located, and the service priority on the conflicting resources.
[0315] Optionally, the first downlink reception comprises a plurality of downlink receptions, each downlink reception corresponding to a downlink reception type.
[0316] It should be noted that the terminal 400 described above in the embodiments of the present application can be the terminal of any implementation manner in the method embodiments, and any implementation manner of the terminal in the method embodiments can be realized by the terminal 400 described above in the embodiments of the present application and achieve the same beneficial effects, and thus details are not described herein again.
[0317] FIG. 12 is a structural diagram of a network-side device according to an embodiment of the present application, as shown in FIG. 12, the network-side device 500 comprises:
[0318] The receiving module 501 is configured to receive a first uplink signal sent by a terminal, wherein the first uplink signal is used to trigger a first downlink reception.
[0319] Optionally, the first uplink signal and the first downlink reception have a time-domain association relationship.
[0320] Optionally, the association relationship is configured by the network side device or is agreed by a protocol.
[0321] Optionally, the first uplink signal comprises first indication information, wherein the first indication information is used to trigger M first downlink receptions in N downlink receptions, the N downlink receptions are configured by the network side device or are agreed by a protocol, and N and M are integers greater than or equal to 1.
[0322] Optionally, the first indication information comprises at least one of an identifier of the first downlink reception and a time-domain configuration parameter of the first downlink reception.
[0323] Optionally, the time-domain configuration parameter of the first downlink reception is configured by the network side device or is agreed by a protocol.
[0324] Optionally, the time-domain configuration parameter of the first downlink reception comprises at least one of:
[0325] a time-domain starting moment of the first downlink reception;
[0326] a time-domain monitoring manner of the first downlink reception;
[0327] a duration of the first downlink reception;
[0328] a first periodicity parameter of the first downlink reception, wherein the first periodicity parameter comprises at least one of a first periodicity length, an active time length of a first periodicity, and an active time starting position offset amount of the first periodicity.
[0329] Optionally, the time-domain starting moment of the first downlink reception is any one of:
[0330] a reference moment, wherein the reference moment is an ending moment of a time-domain resource where the first uplink signal is located;
[0331] a first moment, wherein the first moment is a moment that is spaced apart from the reference moment by a first time interval;
[0332] a starting moment of a first available downlink time-domain resource after the reference moment;
[0333] a starting moment of a time-domain resource after a first timer expires, wherein the first timer is started at the reference moment.
[0334] a starting moment of a first available downlink time domain resource after the first moment;
[0335] a starting moment of a first available downlink time domain resource after the first timer expires.
[0336] Optionally, the duration of the first downlink reception comprises any one of a first time length and a second timer length.
[0337] Optionally, the time domain monitoring manner of the first downlink reception comprises any one of:
[0338] monitoring the first downlink reception within the duration of the first downlink reception;
[0339] monitoring the first downlink reception within an active time of each of the first periodicities;
[0340] monitoring the first downlink reception within an active time of each of the first periodicities within the duration of the first downlink reception.
[0341] Optionally, the active time of the first periodicity is indicated by a bitmap.
[0342] Optionally, if the first downlink reception comprises a reception of a physical downlink control channel (PDCCH), the time domain configuration parameter of the first downlink reception comprises at least one of:
[0343] a blind detection parameter of the PDCCH;
[0344] a monitoring periodicity of the PDCCH;
[0345] a monitoring offset of the PDCCH;
[0346] a monitoring duration of the PDCCH;
[0347] a control resource set (CORESET);
[0348] a search space group;
[0349] a search space;
[0350] a DCI format;
[0351] a radio network temporary identifier (RNTI);
[0352] a time interval between the PDCCH and a physical downlink shared channel (PDSCH) scheduled by the PDCCH;
[0353] a time interval between the PDSCH and a HARQ-ACK feedback of the PDSCH;
[0354] a time interval between the PDCCH and a physical uplink shared channel (PUSCH) scheduled by the PDCCH;
[0355] a processing delay of the PDSCH;
[0356] a preparation delay of the PUSCH.
[0357] Optionally, the association relationship is configured for at least one of a specific terminal, a specific medium access control (MAC) entity, a specific service type, and a specific frequency range.
[0358] Optionally, the type of the first uplink signal includes at least one of a type of an uplink channel and a type of a signal carried on the uplink channel.
[0359] Optionally, the first downlink reception includes at least one of downlink scheduling information reception, downlink signal reception, downlink data information reception, and downlink channel listening.
[0360] Optionally, the network-side device 500 further includes:
[0361] a first sending module configured to send a first message to the terminal, the first message being used to instruct the terminal to stop receiving at least one of the first downlink reception.
[0362] Optionally, the network-side device 500 further includes:
[0363] a second sending module configured to send a second message to the terminal, the second message being used to instruct the terminal to switch a receiving period of the first downlink reception from a first period to a second period; the second period being different from the first period in at least one of a period length, an active time length of a period, and a starting position offset of an active time of a period.
[0364] Optionally, the first downlink reception includes a plurality of downlink receptions, each downlink reception corresponding to a type of downlink reception.
[0365] It should be noted that the network-side device 500 described above in the embodiments of the present application can be the network-side device of any implementation manner in the method embodiments, and any implementation manner of the network-side device in the method embodiments can be implemented by the network-side device 500 described above in the embodiments of the present application, and achieve the same beneficial effects. To avoid repetition, details are not described herein.
[0366] Fig. 13 is a schematic diagram of a hardware structure of a terminal implementing various embodiments of the present application. The terminal 900 includes, but is not limited to, a radio frequency unit 901, a network module 902, an audio output unit 903, an input unit 904, a sensor 905, a display unit 906, a user input unit 907, an interface unit 908, a storage 909, a processor 910, and a power supply 911, etc. Those skilled in the art can understand that the terminal structure shown in Fig. 13 does not constitute a limitation on the terminal, and the terminal can include more or fewer components than shown, or combine certain components, or different component arrangements. In embodiments of the present application, the terminal includes, but is not limited to, a mobile phone, a tablet computer, a notebook computer, a palm computer, a vehicle-mounted terminal, a wearable device, and a pedometer, etc.
[0367] The radio frequency unit 901 is configured to:
[0368] transmit a first uplink signal, the first uplink signal being used to trigger a first downlink reception.
[0369] Optionally, the first uplink signal and the first downlink reception have a time-domain association relationship.
[0370] Optionally, the association relationship is configured by a network side device or a protocol.
[0371] Optionally, the radio frequency unit 901 or the processor 910 is further configured to:
[0372] trigger the first downlink reception associated with the first uplink signal according to at least one of a type of the first uplink signal, a logical channel in which the first uplink signal is located, and a service priority of the first uplink signal.
[0373] Optionally, the first uplink signal includes first indication information, the first indication information being used to trigger M first downlink receptions in N downlink receptions, the N downlink receptions being configured by a network side device or a protocol, and the N and M are integers greater than or equal to 1.
[0374] Optionally, if the M is greater than 1, the radio frequency unit 901 is further configured to:
[0375] after transmitting the first uplink signal, receive a first downlink control information DCI;
[0376] The radio frequency unit 901 or the processor 910 is further configured to:
[0377] trigger K first downlink receptions in the M first downlink receptions through the first DCI, the K being an integer greater than or equal to 1.
[0378] Optionally, the first indication information comprises at least one of an identifier of the first downlink reception and a time domain configuration parameter of the first downlink reception.
[0379] Optionally, the time domain configuration parameter of the first downlink reception is configured by a network side device or agreed by a protocol.
[0380] Optionally, the time domain configuration parameter of the first downlink reception comprises at least one of:
[0381] a time domain starting moment of the first downlink reception;
[0382] a time domain monitoring manner of the first downlink reception;
[0383] a duration of the first downlink reception;
[0384] a first periodicity parameter of the first downlink reception, the first periodicity parameter comprising at least one of a first periodicity length, an activation time length of a first periodicity and an activation time starting position offset of the first periodicity.
[0385] Optionally, the time domain starting moment of the first downlink reception is any one of:
[0386] a reference moment, the reference moment being an ending moment of a time domain resource where the first uplink signal is located;
[0387] a first moment, the first moment being a moment that is spaced apart from the reference moment by a first time interval;
[0388] a starting moment of a first available downlink time domain resource after the reference moment;
[0389] a time domain resource starting moment after a first timer expires, the first timer being started at the reference moment;
[0390] a starting moment of a first available downlink time domain resource after the first moment;
[0391] a starting moment of a first available downlink time domain resource after the first timer expires.
[0392] Optionally, the duration of the first downlink reception comprises any one of a first time length and a second timer length.
[0393] Optionally, the time domain monitoring manner of the first downlink reception comprises any one of:
[0394] monitoring the first downlink reception within the duration of the first downlink reception;
[0395] monitoring the first downlink reception within an activation time of each of the first periodicity;
[0396] listening to the first downlink reception in an active time of each of the first periods within a duration of the first downlink reception.
[0397] Optionally, the radio frequency unit 901 or the processor 910 is further configured to:
[0398] stopping listening to the first downlink reception if Q downlink receptions in the first downlink reception are not received in the active time of the L consecutive first periods, wherein 1≤Q≤L, and L and Q are integers greater than or equal to 1.
[0399] Optionally, the active time of the first period is indicated by a bitmap.
[0400] Optionally, if the first downlink reception includes reception of a physical downlink control channel (PDCCH), the time domain configuration parameter of the first downlink reception includes at least one of:
[0401] a blind detection parameter of the PDCCH;
[0402] a listening period of the PDCCH;
[0403] a listening offset of the PDCCH;
[0404] a listening duration of the PDCCH;
[0405] a control resource set (CORESET);
[0406] a search space group;
[0407] a search space;
[0408] a DCI format;
[0409] a radio network temporary identifier (RNTI);
[0410] a time interval between the PDCCH and a physical downlink shared channel (PDSCH) scheduled by the PDCCH;
[0411] a time interval between the PDSCH and a HARQ-ACK feedback of the PDSCH;
[0412] a time interval between the PDCCH and a physical uplink shared channel (PUSCH) scheduled by the PDCCH;
[0413] a processing delay of the PDSCH;
[0414] a preparation delay of the PUSCH.
[0415] Optionally, the association relationship is configured for at least one of a specific terminal, a specific medium access control (MAC) entity, a specific service type, and a specific frequency range.
[0416] Optionally, the type of the first uplink signal comprises at least one of a type of an uplink channel and a type of a signal carried on the uplink channel.
[0417] Optionally, the first downlink reception comprises at least one of downlink scheduling information reception, downlink signal reception, downlink data information reception, and downlink channel listening.
[0418] Optionally, the radio frequency unit 901 is further configured to:
[0419] receive a first message sent by the network-side device, the first message being used to instruct the terminal to stop receiving at least one of the first downlink reception.
[0420] Optionally, the radio frequency unit 901 is further configured to:
[0421] receive a second message sent by the network-side device, the second message being used to instruct the terminal to switch a reception period of the first downlink reception from the first period to a second period; the second period being different from the first period in at least one of a period length, an active time length of a period, and a start position offset of an active time of a period.
[0422] Optionally, if the terminal sends a second uplink signal within a duration of the first downlink reception, the second uplink signal being used to trigger a second downlink reception, the radio frequency unit 901 or the processor 910 is further configured to:
[0423] perform the first downlink reception and the second downlink reception in parallel; or,
[0424] perform only the second downlink reception.
[0425] Optionally, in a case where the first downlink reception and the second downlink reception are performed in parallel, if the first downlink reception and the second downlink reception have one or more resource conflicts, the radio frequency unit 901 or the processor 910 is further configured to:
[0426] perform the second downlink reception and abandon the first downlink reception on the conflicting resources; or,
[0427] perform the first downlink reception and abandon the second downlink reception on the conflicting resources; or,
[0428] determine, from the first downlink reception and the second downlink reception, a downlink reception to be performed on the conflicting resources according to at least one of a type of the first uplink signal and the second uplink signal, a logical channel where the first uplink signal and the second uplink signal are located, and a service priority.
[0429] Optionally, the first downlink reception comprises a plurality of downlink receptions, each downlink reception corresponding to a downlink reception type.
[0430] It should be noted that the terminal 900 in the embodiment can be the terminal in any of the embodiments of the method of the present application, and any of the embodiments of the terminal in the embodiments of the method of the present application can be implemented by the terminal 900 in the embodiment, and the same beneficial effects are achieved, which will not be described herein.
[0431] It should be understood that in the embodiments of the present application, the radio frequency unit 901 can be used for receiving and sending signals in the process of transmitting and receiving information or calls. Specifically, after receiving the downlink data from the base station, the radio frequency unit 901 processes the data for the processor 910. In addition, the radio frequency unit 901 sends the uplink data to the base station. Generally, the radio frequency unit 901 includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc. In addition, the radio frequency unit 901 can also communicate with the network and other devices through a wireless communication system.
[0432] The terminal provides the user with wireless broadband Internet access through the network module 902, such as helping the user to send and receive e-mails, browse web pages, and access streaming media, etc.
[0433] The audio output unit 903 can convert audio data received by the radio frequency unit 901 or the network module 902 or stored in the memory 909 into an audio signal and output as a sound. Moreover, the audio output unit 903 can also provide audio output related to a specific function performed by the terminal 900 (e.g., a call signal reception sound, a message reception sound, etc.). The audio output unit 903 includes a speaker, a buzzer, and a receiver, etc.
[0434] The input unit 904 is used to receive audio or video signals. The input unit 904 can include a graphics processor (GPU) 9041 and a microphone 9042. The graphics processor 9041 processes image data of a still picture or a video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The processed image frame can be displayed on the display unit 906. The image frame processed by the graphics processor 9041 can be stored in the memory 909 (or other storage medium) or transmitted via the radio frequency unit 901 or the network module 902. The microphone 9042 can receive sound and can process such sound into audio data. The processed audio data can be converted into a format that can be transmitted to a mobile communication base station via the radio frequency unit 901 in the case of a telephone call mode.
[0435] The terminal 900 further includes at least one sensor 905, such as an optical sensor, a motion sensor, and other sensors. Specifically, the optical sensor includes an ambient light sensor and a proximity sensor, wherein the ambient light sensor can adjust the brightness of the display panel 9061 according to the brightness of ambient light, and the proximity sensor can turn off the display panel 9061 and the backlight when the terminal 900 is moved to the ear. As one of the motion sensors, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally three axes), and when at rest, can detect the magnitude and direction of gravity, and can be used to identify the terminal posture (such as screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, knocking), and the like. The sensor 905 can also include a fingerprint sensor, a pressure sensor, an iris sensor, a molecular sensor, a gyroscope, a barometer, a hygrometer, a thermometer, an infrared sensor, and the like, which will not be described here.
[0436] The display unit 906 is used to display information input by the user or information provided to the user. The display unit 906 can include a display panel 9061, which can be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.
[0437] The user input unit 907 can be used to receive input digital or character information, and to generate key signal inputs related to the user settings and function control of the terminal. Specifically, the user input unit 907 includes a touch panel 9071 and other input devices 9072. The touch panel 9071, also known as a touch screen, can collect user touch operations (such as user operations using a finger, a stylus, or any suitable object or accessory on or near the touch panel 9071) on or near it. The touch panel 9071 can include two parts, a touch detection device and a touch controller. The touch detection device detects the user's touch position and detects the signals generated by the touch operation, and transmits the signals to the touch controller; the touch controller receives touch information from the touch detection device, and converts it into touch coordinates, and sends it to the processor 910, receives commands from the processor 910 and executes them. In addition, the touch panel 9071 can be implemented in various types such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the touch panel 9071, the user input unit 907 can also include other input devices 9072. Specifically, the other input devices 9072 can include, but are not limited to, a physical keyboard, function keys (such as volume control buttons, on-off buttons, etc.), trackballs, mice, joysticks, and the like, which will not be described here.
[0438] Further, the touch panel 9071 can be overlaid on the display panel 9061, and when the touch panel 9071 detects a touch operation thereon or thereabout, it transmits the touch event to the processor 910 to determine the type of the touch event, and then the processor 910 provides a corresponding visual output on the display panel 9061 according to the type of the touch event. Although in FIG. 13, the touch panel 9071 and the display panel 9061 are implemented as two independent components to realize the input and output functions of the terminal, in some embodiments, the touch panel 9071 and the display panel 9061 can be integrated to realize the input and output functions of the terminal, which is not limited here.
[0439] The interface unit 908 is an interface for connecting external devices with the terminal 900. For example, the external devices can include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input / output (I / O) port, a video I / O port, a headphone port, and the like. The interface unit 908 can be used to receive input (e.g., data information, power, and the like) from external devices and transmit the received input to one or more elements within the terminal 900, or can be used to transmit data between the terminal 900 and external devices.
[0440] The memory 909 can be used to store software programs and various data. The memory 909 can mainly include a storage program area and a storage data area, wherein the storage program area can store operating systems, application programs (such as sound playing functions, image playing functions, and the like) required by at least one function, and the like; the storage data area can store data (such as audio data, phone books, and the like) created according to the use of the mobile phone, and the like. In addition, the memory 909 can include a high-speed random access memory, and can also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other volatile solid-state memory device.
[0441] The processor 910 is the control center of the terminal, which connects all parts of the terminal through various interfaces and lines, executes various functions of the terminal and processes data by running or executing software programs and modules stored in the memory 909, and calling data stored in the memory 909, and thus monitors the terminal as a whole. The processor 910 can include one or more processing units; preferably, the processor 910 can integrate an application processor and a modem processor, wherein the application processor mainly processes operating systems, user interfaces, and application programs, and the like, and the modem processor mainly processes wireless communication. It can be understood that the above-mentioned modem processor can also not be integrated into the processor 910.
[0442] The terminal 900 can further include a power supply 911 (such as a battery) for supplying electrical power to each component. Preferably, the power supply 911 can be logically connected to the processor 910 through a power management system, so that the power management system can realize functions such as management of charging, discharging, and power consumption management.
[0443] In addition, the terminal 900 includes some functional modules that are not shown here and will not be described herein.
[0444] Preferably, the embodiment of the present application further provides a terminal, which includes a processor 910, a memory 909, instructions or programs stored in the memory 909 and executable on the processor 910, the instructions or programs are executed by the processor 910 to realize each process of the above-mentioned downlink reception triggering method embodiment and achieve the same technical effects. To avoid repetition, they will not be described here.
[0445] It should be noted that the above-mentioned terminal 900 in the embodiment can be the terminal of any implementation manner of the method embodiment of the present application, and any implementation manner of the terminal in the method embodiment of the present application can be realized by the above-mentioned terminal 900 in the embodiment and achieve the same beneficial effects, which will not be described here.
[0446] FIG. 14 is a structure diagram of a network side device provided by an embodiment of the present application. As shown in FIG. 14, the network side device 700 includes a processor 701, a transceiver 702, a memory 703, and a bus interface, wherein:
[0447] The transceiver 702 is configured to:
[0448] receive a first uplink signal sent by a terminal, the first uplink signal being used for triggering a first downlink reception.
[0449] Optionally, the first uplink signal and the first downlink reception have a time domain association relationship.
[0450] Optionally, the association relationship is configured by the network side device or is agreed by a protocol.
[0451] Optionally, the first uplink signal includes first indication information, the first indication information being used for triggering M first downlink receptions in N downlink receptions, the N downlink receptions being configured by the network side device or being agreed by a protocol, and the N and M are integers greater than or equal to 1.
[0452] Optionally, the first indication information includes at least one of an identifier of the first downlink reception and a time domain configuration parameter of the first downlink reception.
[0453] Optionally, the time domain configuration parameter of the first downlink reception is configured by the network side device or is agreed by a protocol.
[0454] Optionally, the time domain configuration parameter of the first downlink reception comprises at least one of:
[0455] a time domain starting moment of the first downlink reception;
[0456] a time domain monitoring manner of the first downlink reception;
[0457] a time duration of the first downlink reception;
[0458] a first periodicity parameter of the first downlink reception, the first periodicity parameter comprising at least one of a first periodicity length, an activation time length of the first periodicity, and an activation time starting position offset of the first periodicity.
[0459] Optionally, the time domain starting moment of the first downlink reception is any one of:
[0460] a reference moment, the reference moment being an ending moment of a time domain resource where the first uplink signal is located;
[0461] a first moment, the first moment being a moment that is spaced apart from the reference moment by a first time interval;
[0462] a starting moment of a first available downlink time domain resource after the reference moment;
[0463] a time domain resource starting moment after a first timer expires, the first timer being started at the reference moment;
[0464] a starting moment of a first available downlink time domain resource after the first moment;
[0465] a starting moment of a first available downlink time domain resource after the first timer expires.
[0466] Optionally, the time duration of the first downlink reception comprises any one of a first time length and a second timer length.
[0467] Optionally, the time domain monitoring manner of the first downlink reception comprises any one of:
[0468] monitoring the first downlink reception within the time duration of the first downlink reception;
[0469] monitoring the first downlink reception within an activation time of each of the first periodicity;
[0470] monitoring the first downlink reception within an activation time of each of the first periodicity within the time duration of the first downlink reception.
[0471] Optionally, the activation time of the first periodicity is indicated by a bitmap.
[0472] Optionally, if the first downlink reception comprises a reception of a physical downlink control channel (PDCCH), the time domain configuration parameter of the first downlink reception comprises at least one of:
[0473] a blind detection parameter of the PDCCH;
[0474] a monitoring periodicity of the PDCCH;
[0475] a monitoring offset of the PDCCH;
[0476] a monitoring duration of the PDCCH;
[0477] a control resource set (CORESET);
[0478] a search space group;
[0479] a search space;
[0480] a DCI format;
[0481] a radio network temporary identifier (RNTI);
[0482] a time interval between the PDCCH and a physical downlink shared channel (PDSCH) scheduled by the PDCCH;
[0483] a time interval between the PDSCH and a HARQ-ACK feedback of the PDSCH;
[0484] a time interval between the PDCCH and a physical uplink shared channel (PUSCH) scheduled by the PDCCH;
[0485] a processing delay of the PDSCH;
[0486] a preparation delay of the PUSCH.
[0487] Optionally, the association relationship is configured for at least one of a specific terminal, a specific medium access control (MAC) entity, a specific service type, and a specific frequency range.
[0488] Optionally, the type of the first uplink signal comprises at least one of a type of an uplink channel and a type of a signal carried on the uplink channel.
[0489] Optionally, the first downlink reception comprises at least one of a downlink scheduling information reception, a downlink signal reception, a downlink data information reception, and a downlink channel monitoring.
[0490] Optionally, the transceiver 702 is further configured to:
[0491] send, to the terminal, a first message, the first message being used to instruct the terminal to stop receiving at least one of the first downlink receptions.
[0492] Optionally, the transceiver 702 is further configured to:
[0493] send a second message to the terminal, the second message being used to instruct the terminal to switch a receiving period of the first downlink reception from a first period to a second period, the second period being different from the first period in at least one of a period length, an active time length of the period and a start position offset of the active time of the period.
[0494] Optionally, the first downlink reception comprises a plurality of downlink receptions, each downlink reception corresponding to a downlink reception type.
[0495] In Figure 14, the bus architecture can include any number of interconnected buses and bridges, which link various circuits, including the one or more processors represented by the processor 701 and the memory represented by the memory 703. The bus architecture can also link various other circuits, such as peripheral devices, voltage stabilizers and power management circuits, which are well known in the art, and thus, are not further described herein. The bus interface provides an interface. The transceiver 702 can be a plurality of elements, i.e., including a transmitter and a receiver, which provide units for communicating with various other devices on a transmission medium.
[0496] The processor 701 is responsible for managing the bus architecture and general processing, and the memory 703 can store data used by the processor 701 in performing operations.
[0497] It should be noted that the network side device 700 described above in the embodiment can be the network side device of any implementation manner of the method embodiments of the present application, and any implementation manner of the network side device in the method embodiments of the present application can be implemented by the network side device 700 described above in the embodiment, and achieve the same beneficial effects, which will not be described herein.
[0498] The embodiment of the present application further provides a readable storage medium, and the readable storage medium stores instructions or programs, the instructions or programs are executed by a processor to implement various processes of the above-mentioned embodiments corresponding to the terminal or the network side, and can achieve the same technical effects, and to avoid repetition, which will not be described herein. The readable storage medium is, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.
[0499] The embodiment of the present application further provides a chip, which comprises a processor and a communication interface, the communication interface is coupled with the processor, the processor is used for running programs or instructions, realizes each process of the downlink receiving triggering method embodiment, and can achieve the same technical effects, to avoid repetition, which will not be described here.
[0500] It should be understood that the chip mentioned in the embodiment of the present application can also be referred to as a system chip, a system chip, a chip system or a system on chip, etc.
[0501] It should be noted that in this paper, the term "including", "containing" or any other variant thereof is intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements not only includes those elements, but also includes other elements not explicitly listed, or includes elements inherent to such process, method, article or device. Without more limitations, the element defined by the statement "including a" does not exclude the presence of other identical elements in the process, method, article or device including the element.
[0502] From the above description of the embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment method can be realized by means of software and necessary general hardware platform, of course, it can also be realized by hardware, but in many cases, the former is a better embodiment. Based on such understanding, the technical solutions of the present application can be embodied in the form of software products, which are stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), including a plurality of instructions for making a terminal (which can be a mobile phone, computer, server, air conditioner or network equipment, etc.) execute the method described in each embodiment of the present application.
[0503] The above is only a specific embodiment of the present application, but the protection scope of the present application is not limited thereto, any skilled person in the art can easily think of changes or replacements within the technical range disclosed by the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.
Claims
1. The method of triggering a link-down reception, applied to the terminal and comprising: link-first transmission, where the link-first signal is used to trigger the link-down reception.
2. The method according to claim 1, where there is a time-domain link-first relationship between the link-first signal and the link-down reception.
3. The method according to claim 2, where the link-first relationship is shaped by the network-side device or determined by a protocol.
4. The method according to claim 3, which further comprising: triggering, based on at least one type of link-first signal, the logical channel to which the link-first signal is a part, and the service priority of the link-first signal, the link-down reception associated with the link-first signal.
5. The method according to claim 1, where the link-first signal contains the first identification information.The first identification information is used to trigger the first downlink input M among the first downlink inputs N. The first downlink input N is formatted by the network-side device or determined by the protocol, and both N and M are integers greater than or equal to 16. Method according to claim 5, where if M is greater than 1, the method includes: receiving the first downlink control (DC) information after the first uplink signal has been transmitted; and triggering the first downlink input K in the first downlink input M by using the first DCI, where K is an integer greater than or equal to 17. Method according to claim 5, where the first identification information includes at least one of the first downlink input identifiers and the first downlink input time domain formatting parameters.
8. Method according to claim 1, where the first downlink input time domain formatting parameters are formatted by the network-side device or determined by the protocol.
9. Method according to claim 7 or 8,Where the time domain formatting parameters of the first-up link-down input include at least one of the following: the time domain start time of the first-up link-down input; the time domain traceability method for the first-up link-down input; the duration of the first-up link-down input; and the parameters of the first round of the first-up input, where the parameters of the first round include at least one of the intervals of the first round, the interval in the duration of the first round, and the initial offset of the duration of the first round.
10. The method according to claim 9, where the time domain start time of the first-up link-down input is one of the following: the reference time, where the reference time is the end time of the time domain resource that carries the first-up link signal; the initial time, where the initial time is the time interval outside of the reference time; the start time of the first-up link-down time domain resource after the reference time; the start time of the time domain resource after the first timer timeout.Where the first timer is set to start at the reference time: the start time of the first available downlink time domain resource after the initial time: and the start time of the first available downlink time domain resource after the first timer timeout.
11. Method according to claim 9, where the period of the first downlink admission consists of one of the initial time period and the period of the second timer.
12. Method according to claim 9, where the time domain monitoring method for the first downlink admission consists of one of the following: monitoring of the first downlink admission within the period of the first downlink admission; monitoring of the first downlink admission within the period of each first round; and monitoring of the first downlink admission within the period of each first round in the period of the first downlink admission.
13. Method according to claim 12,This includes the following additional conditions: Stopping the tracking of the first-place link-down reception if the first-place link-down reception Q is not received within the period of the first consecutive cycle L, where 1 is less than or equal to Q is less than or equal to L and both L and Q are integers greater than or equal to 114. Method according to claim 9, where the period of the first cycle is indicated by bitmap 1r. Method according to claim 7 or 8, where if the first-place link-down reception includes the reception of a physical link-down control channel (PDCCH),The time-domain formatting parameters of first-line down-link reception include at least one of the following: PDCCH blind decoding parameters; PDCCH monitoring state; PDCCH monitoring offset; PDCCH monitoring duration; CORESET; search region group; search region; DCI format; RNTI transient identifier; time interval between the PDCCH and the physically allocated down-link channel (PDSCH) scheduled by the PDCCH; interval; The time interval between PDSCH and the HARQ-ACK feedback for PDSCH; the time interval between PDCCH and the physical link-assigned channel (PUSCH) scheduled by PDCCH; the PDSCH processing delay; and the PUSCH preparation delay.
16. Method according to claim 2, whereby a mutual link relationship has been established for at least one of the defined terminals, defined intermediate access control (MAC) entities, defined service types, and defined frequency ranges.
17. Method according to claim 1 or 4,Where the first-level uplink signal type comprises at least one of the uplink channel types and the type of signal being transmitted on the uplink channel.
18. Method of Claim 1. Where the first-level downlink reception comprises at least one of the downlink scheduling information receptions, downlink signal receptions, downlink data information receptions, and downlink channel monitoring.
19. Method of Claim 1, which includes additionally: reception of the first message from the network-side device, where the first message is used to indicate to the terminal to stop receiving at least one of the first-level downlink receptions.
20. Method of Claim 9, which includes additionally: reception of the second message from the network-side device,Where the second message is used to indicate to the terminal to switch the receiving round for the first downlink receive from the first round to the second round: and the second round differs from the first round by at least one time interval. Time interval, and initial offset of time interval 21. Method according to claim 1, where if the terminal transmits a second uplink signal within the time interval of the first downlink receive and a second uplink signal is used to trigger the second downlink receive, the additional method is: performing the first downlink receive and the second downlink receive in parallel; or performing only the second downlink receive.
22. Method according to claim 21, where in the case of performing the first downlink receive and the second downlink receive in parallel, if the first downlink and the second downlink receive compete on one or more resources,The additional assembly methods include: on the competing resource, performing the second-rank downlink incoming operation and terminating the first-rank downlink incoming operation; or on the competing resource, performing the first-rank downlink incoming operation and terminating the second-rank downlink incoming operation; or on the competing resource, determining, based on at least one type of first-rank uplink and second-rank uplink signal, the logical channel of which the first-rank uplink and second-rank uplink signals are a part, and the service priority of the first-rank uplink and second-rank uplink signals, the downlink incoming operation to be executed from the first-rank downlink incoming and the second-rank downlink incoming operation.
23. The downlink incoming activation method, which is applied to the network-side device and includes: receiving the first-rank uplink signal from the terminal,24. Method according to claim 23, where there is a time-domain mutual link relationship between the first-as-as-as-as-a-link signal and the first-as-a-down link entry.
25. Method according to claim 24, where the mutual link relationship is formatted by the network-side device or determined by the protocol.
26. Method according to claim 23, where the first-as-as-as-a-link signal incorporates first-identification information, first-identification information is used to trigger the first-as-a-down link entry M among the first-a-down link entries N, the first-a-down link entry N is formatted by the network-side device or determined by the protocol, and both N and M are integers greater than or equal to 1.
7. Method according to claim 23, which includes: first-message transmission to the terminal.Where the first message is used to instruct the terminal to stop receiving at least one Link-Up First (LST) entry in Link-Down First (LST) entry.
28. The method under claim 23, which includes additionally: the transmission of a second message to the terminal, where the second message is used to instruct the terminal to switch the receiving cycle for Link-Down First (LST) entry from the first cycle to the second cycle: and the second cycle differs from the first cycle by at least one time interval. Time interval, and initial offset of time interval.
29. The terminal, which includes: a transmission module, formatted to transmit a Link-Up First (LST) signal, where the Link-Up First (LST) signal is used to trigger a Link-Down First (LST) entry.
30. The terminal under claim 29, where there is a time domain mutual link relationship between the Link-Up First (LST) signal and the Link-Down First (LST) entry.
31. The terminal under claim 30,Where the mutual link relationship is formatted by the network-side device or determined by the protocol.
32. The terminal under claim 29, where the first-link up signal comprises the first-link identification information, the first-link identification information is used to trigger the first-link down-link input M in the first-link down-link input N, the first-link down-link input N is formatted by the network-side device or determined by the protocol, and both N and M are integers greater than or equal to 1.
33. The network-side device, which comprises: the receiver module, which is formatted to receive the first-link up signal from the terminal, where the first-link up signal is used to trigger the first-link down-link input.
34. The network-side device under claim 33, where there is a time-domain mutual link relationship between the first-link up signal and the first-link down-link input.
35. The network-side device under claim 34,Where the link-to-first relationship is formatted by the network-side device or determined by the protocol.
36. Network-side device according to claim 33, where the first-up link signal contains first-priority identification information, the first-priority identification information is used to trigger the first-down link input M among the down link inputs N, the down link input N is formatted by the network-side device or determined by the protocol, and both N and M are integers greater than or equal to 1.
37. Terminal, which includes memory, processor, and instructions or programs stored in memory and capable of execution on the processor, where, when the instructions or program are executed by the processor, one of the down link triggering procedures according to claims 1 through 22 is executed.
38. Network-side device, which includes memory, processor, and instructions or programs stored in memory and capable of execution on the processor,39. A readable storage medium where an instruction or program is executed by the processor, and when the instruction or program is executed by the processor, any of the link-down activation procedures under Rights 23 through 28 are executed.
40. A chip, which contains a processor and a communication interface, where the communication interface is connected to the processor, and the processor is formatted to execute a program or instruction to execute any of the link-down activation procedures under Rights 1 through 22, or to execute any of the link-down activation procedures under Rights 23 through 28.
41. A computer program product, stored on a readable storage medium.Where the computer program product is executed by at least one processor to perform any of the Link Down Access Procedures under Rights 1 through 22 or any of the Link Down Access Procedures under Rights 23 through 28; 42. Terminal, where the terminal is formatted to execute any of the Link Down Access Procedures under Rights 1 through 22; 43. Network device, where the network device is formatted to execute any of the Link Down Access Procedures under Rights 23 through 28;