Request transmitting method and apparatus, request receiving method and apparatus, terminal, network device, and storage medium

Abstract

The present disclosure relates to the technical field of communications, and in particular to a request transmitting method and apparatus, a request receiving method and apparatus, a terminal, a network device, and a storage medium. The request transmitting method comprises: determining a first resource used for transmitting request information; and transmitting the request information to a network device on the basis of the first resource, wherein the request information is used for requesting the network device to transmit first information in an on-demand state. According to the present disclosure, the terminal can determine the first resource used for transmitting the request information, and then transmits the request information to the network device over the first resource, so as to request the network device to transmit the first information in the on-demand state, thereby ensuring that the terminal can successfully acquire the first information in the on-demand state.

Description

Request sending and receiving method and device, terminal, network device and storage medium Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a request sending method, a request receiving method, a request sending device, a request receiving device, a terminal, a network device, a communication device, and a storage medium. Background Art

[0002] When communicating with a terminal, a network device can send information to the terminal, and the terminal can receive information sent by the network device. However, in some scenarios, the circumstances under which the network device sends information to the terminal may change, and some technical issues need to be addressed in this scenario.

[0003] Summary of the Invention

[0004] The embodiments of the present disclosure provide a request sending and receiving method and apparatus, a terminal, a network device, and a storage medium to solve technical problems in related technologies.

[0005] According to a first aspect of an embodiment of the present disclosure, a request sending method is proposed, which is executed by a terminal, and the method includes: determining a first resource for sending request information; sending the request information to a network device based on the first resource, wherein the request information is used to request the network device to send first information in an on-demand state.

[0006] According to the second aspect of an embodiment of the present disclosure, a request receiving method is proposed, which is executed by a network device. The method includes: receiving the request information sent by the terminal on a first resource used for the terminal to send request information, wherein the request information is used to request the network device to send first information in an on-demand state.

[0007] According to the third aspect of an embodiment of the present disclosure, a request sending device is proposed, which includes: a processing module, configured to determine a first resource for sending request information; a sending module, configured to send the request information to a network device based on the first resource, wherein the request information is used to request the network device to send first information in an on-demand state.

[0008] According to the fourth aspect of an embodiment of the present disclosure, a request receiving device is proposed, which includes: a receiving module, configured to receive the request information sent by the terminal on a first resource used for the terminal to send request information, wherein the request information is used to request a network device to send first information in an on-demand state.

[0009] According to the fifth aspect of an embodiment of the present disclosure, a request sending method is proposed, including: a terminal sends request information to a network device on a first resource; the network device determines, based on the request information, that the terminal requests the network device to send first information in an on-demand state.

[0010] According to a sixth aspect of an embodiment of the present disclosure, a terminal is proposed, comprising: one or more processors; wherein the terminal is used to execute the request sending method described in the first aspect.

[0011] According to a seventh aspect of an embodiment of the present disclosure, a network device is proposed, comprising: one or more processors; wherein the network device is used to execute the request receiving method described in the second aspect.

[0012] According to the eighth aspect of an embodiment of the present disclosure, a communication system is proposed, comprising a terminal and a network device, wherein the terminal is configured to implement the request sending method described in the first aspect, and the network device is configured to implement the request receiving method described in the second aspect.

[0013] According to the ninth aspect of the embodiment of the present disclosure, a storage medium is proposed, which stores instructions. When the instructions are executed on a communication device, the communication device executes the request sending method described in the first aspect and / or the request receiving method described in the second aspect.

[0014] According to an embodiment of the present disclosure, the terminal can determine the first resource for sending the request information, and then send the request information to the network device on the first resource to request the network device to send the first information in an on-demand state. Accordingly, it is beneficial to ensure that the terminal can smoothly obtain the first information in an on-demand state. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0016] FIG1 is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.

[0017] FIG2 is an interactive diagram illustrating a request sending method according to an embodiment of the present disclosure.

[0018] FIG3 is a schematic flowchart of a request sending method according to an embodiment of the present disclosure.

[0019] FIG4 is a schematic flowchart of a request receiving method according to an embodiment of the present disclosure.

[0020] FIG5 is a schematic block diagram of a request sending apparatus according to an embodiment of the present disclosure.

[0021] FIG6 is a schematic block diagram showing a network device according to an embodiment of the present disclosure.

[0022] FIG7A is a schematic structural diagram of a communication device proposed in an embodiment of the present disclosure.

[0023] FIG7B is a schematic diagram of the structure of the chip proposed in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0024] The embodiments of the present disclosure provide a method and apparatus for sending and receiving a request, a terminal, a network device, and a storage medium.

[0025] In a first aspect, an embodiment of the present disclosure proposes a request sending method, which is executed by a terminal, and the method includes: determining a first resource for sending request information; sending the request information to a network device based on the first resource, wherein the request information is used to request the network device to send first information in an on-demand state.

[0026] In the above embodiment, the terminal can determine the first resource for sending the request information, and then send the request information to the network device on the first resource to request the network device to send the first information in an on-demand state. Accordingly, it is helpful to ensure that the terminal can smoothly obtain the first information in an on-demand state.

[0027] In combination with some embodiments of the first aspect, in some embodiments, the request information is used to request the network device to send at least one first information in an on-demand state.

[0028] In combination with some embodiments of the first aspect. In some embodiments, the request information is associated with the at least one first information in the on-demand state and / or the beam where the at least one first information in the on-demand state is located; or, the first resource is associated with the at least one first information in the on-demand state and / or the beam where the at least one first information in the on-demand state is located; or, the value of the bit in the request information and the first resource are associated with the at least one first information in the on-demand state and / or the beam where the at least one first information in the on-demand state is located.

[0029] In combination with some embodiments of the first aspect. In some embodiments, determining the first resource for sending the request information includes one of the following: determining the first resource according to configuration information in cell-specific signaling; determining the first resource according to configuration information in terminal-specific signaling; or determining the first resource according to a method agreed upon in a protocol.

[0030] In combination with some embodiments of the first aspect, in some embodiments, the first resource includes a physical uplink control channel (PUCCH) resource.

[0031] In combination with some embodiments of the first aspect, in some embodiments, the first resource overlaps with a legacy PUCCH resource used to send legacy information, and the request information or the legacy information is sent on the overlapping resource.

[0032] In conjunction with some embodiments of the first aspect, in some embodiments, the legacy PUCCH resource used to send legacy information includes the first resource, and the first resource determined to be used to send request information includes one of the following:

[0033] receiving indication information sent by a network device, wherein the indication information is used to indicate the first resource in the traditional PUCCH resource;

[0034] The first resource is determined in the traditional PUCCH resources in a manner agreed upon in a protocol.

[0035] In combination with some embodiments of the first aspect, in some embodiments, the first beam where the request information is located and the second beam where the first information is located are quasi-co-located.

[0036] In combination with some embodiments of the first aspect, in some embodiments, the terminal enters a non-connected state and the first resource is not released.

[0037] In combination with some embodiments of the first aspect. In some embodiments, at least one of the network device and the terminal is in a discontinuous reception state or a discontinuous transmission state, and the terminal sends the request information to the network device according to the first resource during an inactive period of the discontinuous reception state or the discontinuous transmission state.

[0038] In combination with some embodiments of the first aspect, in some embodiments, the first information includes at least one of the following: a synchronization broadcast signal block; a system information block 1; a channel state information reference signal; a tracking reference signal; a physical downlink control channel; a physical downlink shared channel; or a newly defined reference signal.

[0039] In the second aspect, an embodiment of the present disclosure proposes a request receiving method, which is executed by a network device, and the method includes: receiving the request information sent by the terminal on a first resource used for the terminal to send request information, wherein the request information is used to request the network device to send first information in an on-demand state.

[0040] In combination with some embodiments of the second aspect. In some embodiments, the request information is associated with the at least one first information in the on-demand state and / or the beam where the at least one first information in the on-demand state is located; or, the first resource is associated with the at least one first information in the on-demand state and / or the beam where the at least one first information in the on-demand state is located; or, the value of the bit in the request information and the first resource are associated with the at least one first information in the on-demand state and / or the beam where the at least one first information in the on-demand state is located.

[0041] In conjunction with some embodiments of the second aspect, in some embodiments, the first resource used to send the request information is determined based on one of the following: configuration information in cell-specific signaling; configuration information in terminal-specific signaling; or a method agreed upon in a protocol.

[0042] In conjunction with some embodiments of the second aspect, in some embodiments, the first resource includes a physical uplink control channel (PUCCH) resource.

[0043] In combination with some embodiments of the second aspect, in some embodiments, the first resource overlaps with a legacy PUCCH resource used to send legacy information, and the request information or the legacy information is sent on the overlapping resource.

[0044] In conjunction with some embodiments of the second aspect, in some embodiments, the traditional PUCCH resource used to send traditional information includes the first resource, and the first resource used for the terminal to send the request information is determined based on at least one of the following:

[0045] The indication information of the network device indicates the first resource in the traditional PUCCH resource;

[0046] The first resource is determined in the traditional PUCCH resources in a manner agreed upon in a protocol.

[0047] In combination with some embodiments of the second aspect, in some embodiments, the first beam where the request information is located and the second beam where the first information is located are quasi-co-located.

[0048] In combination with some embodiments of the second aspect, in some embodiments, the terminal enters a non-connected state, and the first resource is not released.

[0049] In combination with some embodiments of the second aspect. In some embodiments, at least one of the network device and the terminal is in a discontinuous reception state or a discontinuous transmission state, and the terminal sends the request information to the network device according to the first resource during an inactive period of the discontinuous reception state or the discontinuous transmission state.

[0050] In combination with some embodiments of the second aspect, in some embodiments, the first information includes at least one of the following: a synchronization broadcast signal block; a system information block 1; a channel state information reference signal; a tracking reference signal; a physical downlink control channel; a physical downlink shared channel; or a newly defined reference signal.

[0051] In a third aspect, a request sending device is proposed, which includes: a processing module, configured to determine a first resource for sending request information; a sending module, configured to send the request information to a network device based on the first resource, wherein the request information is used to request the network device to send the first information in an on-demand state.

[0052] In a fourth aspect, a request receiving device is proposed, which includes: a receiving module, configured to receive the request information sent by the terminal on a first resource used for the terminal to send request information, wherein the request information is used to request the network device to send first information in an on-demand state.

[0053] In a fifth aspect, a request sending method is proposed, comprising: a terminal sends request information to a network device on a first resource; and the network device determines, based on the request information, that the terminal requests the network device to send first information in an on-demand state.

[0054] In a sixth aspect, a terminal is proposed, comprising: one or more processors; wherein the terminal is used to execute the request sending method described in any one of the first aspect and the optional embodiments of the first aspect.

[0055] In the seventh aspect, a network device is proposed, comprising: one or more processors; wherein the network device is used to execute the request receiving method described in any one of the second aspect and the optional embodiments of the second aspect.

[0056] In the eighth aspect, a communication system is proposed, including a terminal and a network device, wherein the terminal is configured to implement the request sending method described in any one of the first aspect and the optional embodiments of the first aspect, and the network device is configured to implement the request receiving method described in any one of the second aspect and the optional embodiments of the second aspect.

[0057] In the ninth aspect, a storage medium is proposed, which stores instructions. When the instructions are executed on a communication device, the communication device executes the request sending method described in any one of the first aspect and the optional embodiments of the first aspect, and / or the request receiving method described in any one of the second aspect and the optional embodiments of the second aspect.

[0058] In the tenth aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the request sending method described in any one of the first aspect and the optional embodiments of the first aspect, and / or the request receiving method described in any one of the second aspect and the optional embodiments of the second aspect.

[0059] In the eleventh aspect, an embodiment of the present disclosure proposes a computer program, which, when running on a computer, enables the computer to execute the request sending method described in any one of the first aspect and the optional embodiments of the first aspect, and / or the request receiving method described in any one of the second aspect and the optional embodiments of the second aspect.

[0060] It is understandable that the request sending and receiving devices, communication devices, communication systems, storage media, program products, and computer programs are all used to execute the methods proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0061] The present disclosure provides methods and apparatus for sending and receiving requests, terminals, network devices, and storage media. In some embodiments, the terms "request sending and receiving method" and "information processing method" and "communication method" are interchangeable; "request sending and receiving apparatus" and "information processing apparatus" and "communication apparatus" are interchangeable; and "information processing system" and "communication system" are interchangeable.

[0062] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0063] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0064] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0065] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular form, such as "a", "an", "the", "above", "said", "aforementioned", "this", etc., may mean "one and only one", or "one or more", "at least one", etc.

[0066] For example, when using articles such as “a”, “an”, and “the” in English in translation, the noun following the article can be understood as a singular expression or a plural expression.

[0067] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0068] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0069] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0070] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0071] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restrictions on the position, order, priority, quantity or content of the description objects. For the statement of the description objects, please refer to the description in the context of the claims or embodiments, and no unnecessary restrictions should be constituted due to the use of prefixes.

[0072] For example, if the description object is "field," the ordinal number preceding "field" in "first field" and "second field" does not restrict the position or order of the "fields." "First" and "second" do not restrict whether the modified "fields" are in the same message, nor do they restrict the order of the "first field" and "second field." For another example, if the description object is "level," the ordinal number preceding "level" in "first level" and "second level" does not restrict the priority of the "levels." For another example, the number of description objects is not restricted by the ordinal number and can be one or more. For example, in the case of "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the description object is "device," "first device" and "second device" can be the same or different devices, and their types can be the same or different. For another example, if the description object is "information," "first information" and "second information" can be the same or different information, and their content can be the same or different.

[0073] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0074] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0075] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0076] In some embodiments, devices, etc. can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as "device", "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", and "subject" can be used interchangeably.

[0077] In some embodiments, "network" can be interpreted as devices included in the network (eg, access network equipment, core network equipment, etc.).

[0078] In some embodiments, the terms "access network device (AN device)", "radio access network device (RAN device)", "base station (BS)", "radio base station" "fixed station", "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission / reception point (TRP)", "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)" and the like may be used interchangeably.

[0079] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc. can be used interchangeably.

[0080] In some embodiments, the access network device, the core network device, or the network device can be replaced by a terminal. For example, the various embodiments of the present disclosure can also be applied to a structure in which the communication between the access network device, the core network device, or the network device and the terminal is replaced by communication between multiple terminals (for example, device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, it is also possible to set the structure in which the terminal has all or part of the functions of the access network device. In addition, terms such as "uplink" and "downlink" can also be replaced by terms corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. can be replaced by side channels, and uplinks, downlinks, etc. can be replaced by side links.

[0081] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, the core network device, or the network device may have a structure that has all or part of the functions of the terminal.

[0082] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0083] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0084] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0085] FIG1 is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.

[0086] As shown in FIG1 , a communication system 100 includes a terminal 101 and a network device 102 , wherein the network device includes at least one of the following: an access network device and a core network device.

[0087] In some embodiments, the terminal 101 includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and at least one of a wireless terminal device in a smart home, but is not limited thereto.

[0088] In some embodiments, the access network device is, for example, a node or device that accesses a terminal to a wireless network. The access network device may include an evolved NodeB (eNB), a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved nodeB (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open base station (Open RAN), a cloud base station (Cloud RAN), a base station in other communication systems, and at least one of an access node in a Wi-Fi system, but is not limited thereto.

[0089] In some embodiments, a core network device may be a device including one or more network elements, or may be multiple devices or device groups, each including all or part of the one or more network elements. The network element may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

[0090] In some embodiments, the technical solution of the present disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within the access network devices involved in the embodiments of the present disclosure can be transformed into internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0091] In some embodiments, the access network device can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0092] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0093] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1 , or a portion thereof, but are not limited thereto. The entities shown in FIG1 are illustrative only. The communication system may include all or part of the entities shown in FIG1 , or may include other entities outside of FIG1 . The number and form of the entities are arbitrary, and the entities may be physical or virtual. The connection relationships between the entities are illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0094] The embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), future radio access (FRA), new radio access technology (RAT), new radio (NR), new radio access (NX), future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X), systems utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0095] In some embodiments, during the communication process with the terminal, the network device may send first information to the terminal, such as a system information block (SIB), a physical downlink channel, a reference signal, etc.

[0096] During this process, the network device may stop sending the first information to the terminal for some reasons. For example, for the first information that is stopped from being sent, the terminal requests the network device to send the first information, and the network device sends the first information. In this case, the status of the first information can be called on demand.

[0097] Alternatively, the network device stops sending the first information to the terminal based on the cell communication situation. In this case, the state of the first information can be called on demand.

[0098] It should be noted that the meaning of the first information being in an on-demand state is not limited to the network device sending the first information only when the terminal requests the first information.

[0099] In some embodiments, from the perspective of the network device, the first information being in an on-demand state may mean that although the network device has sent the configuration of the first information to the terminal, the network device stops sending the first information to the terminal based on the configuration, and the network device continues to send the first information to the terminal based on the configuration after receiving the request information from the terminal requesting the network device to send the first information; the first information being in a non-on-demand state may mean that the network device has sent the configuration of the first information to the terminal, and sends the first information to the terminal based on the configuration.

[0100] In some embodiments, from the perspective of the terminal, the first information being in an on-demand state may mean that although the network device has sent the configuration of the first information to the terminal, the terminal has not received the first information from the network device based on the configuration. When the terminal needs to obtain the first information, the terminal sends a request message to the network device requesting the network device to send the first information; the first information being in a non-on-demand state may mean that the network device has sent the configuration of the first information to the terminal, and the terminal can receive the first information based on the configuration.

[0101] In some embodiments, based on the difference of the first information, the network device may send the first information to the terminal in different ways. For example, the first information may be sent through broadcast, multicast, groupcast, unicast, etc., and this disclosure does not limit this.

[0102] It can be seen that since the first information can be in both on-demand and non-on-demand states, the network device will stop sending the first information in the on-demand state to the terminal. When the terminal needs to obtain the first information in the on-demand state, it needs to send a request message to the network device to request the network device to send the first information to the terminal.

[0103] FIG2 is an interactive diagram illustrating a request sending method according to an embodiment of the present disclosure.

[0104] As shown in FIG2 , the request sending method may include the following steps:

[0105] In step S201, the terminal may determine a first resource for sending request information.

[0106] In some embodiments, the first resource may be configured by a network device or determined based on a protocol agreement, which will not be expanded here and will be specifically exemplified in subsequent embodiments.

[0107] In step S201, the terminal sends request information to the network device according to the first resource.

[0108] In some embodiments, the request information is used to request the network device to send the first information in an on-demand state.

[0109] According to an embodiment of the present disclosure, the terminal can determine the first resource for sending the request information, and then send the request information to the network device on the first resource to request the network device to send the first information in an on-demand state. Accordingly, it is beneficial to ensure that the terminal can smoothly obtain the first information in an on-demand state.

[0110] It should be noted that, after receiving a request message from a terminal, the network device may send the first information in an on-demand state to the terminal. In this case, the status of the first information changes from on-demand to non-on-demand. Alternatively, after receiving a request message from a terminal, the network device may not send the first information in an on-demand state to the terminal. In this case, the status of the first information remains on-demand. Whether the network device sends the first information in an on-demand state to the terminal based on the request message depends on the network device implementation and is not limited by this disclosure.

[0111] In some embodiments, after sending the request information, the terminal may detect the first information in the first resource of the first information after the first time duration T of sending the request information, so as to allow the terminal sufficient time to switch from the sending operation to the receiving operation. T may be determined by the terminal based on its own processing capabilities, configured by the network device, or determined based on a protocol agreement.

[0112] In some embodiments, after sending a request message, if the terminal does not detect the first information in a first number N of first information resources after a first time duration T of sending the request message, the terminal may continue to send the request message to ensure that the terminal can obtain the first information. T and N may be determined by the terminal based on its own processing capabilities, may be configured by the network device, or may be determined based on a protocol agreement.

[0113] In some embodiments, the first information includes at least one of the following: synchronization broadcast signal block (SS (Synchronization Signal) and PBCH (Physical downlink Broadcast Channel) Block, SSB); system information block (System Information Block) 1; channel state information reference signal (CSI-RS); tracking reference signal (TRS), physical downlink control channel (PDCCH), physical downlink shared channel (PDSCH); newly defined reference signals, such as signals composed of primary synchronization signal and secondary synchronization signal, discovery reference signal (DRS), etc.

[0114] In some embodiments, when the first information includes at least one of SSB and SIB1, the first information is relatively important information. Under normal circumstances, the first information will not enter the on-demand state. However, the network device can still make the first information enter the on-demand state for certain needs. For example, the network device needs to enter the Network Energy Saving (NES) mode. Then, for energy saving considerations, the sending of the first information can be stopped, so that the first information enters the on-demand state.

[0115] Therefore, in some embodiments, the request information sent by the terminal to the network device to request the network device to send the first information may also be referred to as a wake-up signal (WUS), which may be used to wake up the network device from the NES mode. After the network device is woken up from the NES mode, it may continue to send the first information. Of course, in some embodiments, the network device may also send the first information based on the request information when in the NES mode.

[0116] In some embodiments, when the first information includes SIB1, when the terminal has not received SIB1 in the current cell, SIB1 can be received according to the configuration of SIB1; and when the terminal has already received SIB1 in the current cell, SIB1 can be received according to the configuration of SIB1 only when it is determined that SIB1 needs to be updated, and when SIB1 does not need to be updated, the reception of SIB1 can be suspended.

[0117] In some embodiments, determining a first resource for sending the request information includes one of the following:

[0118] determining the first resource according to configuration information in cell-specific signaling;

[0119] Determining the first resource according to configuration information in terminal-dedicated (UE-dedicated) signaling;

[0120] The first resource is determined according to the method agreed upon in the protocol.

[0121] In some embodiments, the first resource may be configured by a network device.

[0122] For example, the network device may send cell-specific signaling to the terminal, where the cell-specific signaling carries configuration information. The terminal may determine the first resource according to the configuration information. The present disclosure does not limit the type of the cell-specific signaling.

[0123] For example, the network device may send UE-dedicated signaling to the terminal, where the UE-dedicated signaling carries configuration information, and the terminal may determine the first resource according to the configuration information, where the UE-dedicated signaling includes but is not limited to Radio Resource Control (RRC) signaling.

[0124] It should be noted that the way in which the network device configures the first resource for the terminal is not limited to the above embodiment. The first resource can be configured for the terminal through downlink control information (DCI), or the first resource can be indicated to the terminal through the media access control layer control element (MAC CE), for example, indicating the first resource among multiple resources pre-configured by RRC signaling.

[0125] In some embodiments, the terminal may determine the first resource based on a protocol agreement.

[0126] For example, when the first information includes SIB1, if the terminal has not received SIB1 in the current cell, the terminal cannot obtain the frequency domain information corresponding to the initial uplink bandwidth part (BandWidth Part, BWP), and the terminal will not be able to be configured with resources for requesting information by the network device in a conventional manner.

[0127] In this case, the resource for the requested information may be determined based on a predefined method, for example, the pattern corresponding to the resource for the requested information is agreed upon by the protocol. For example, the protocol agrees on multiple patterns corresponding to the resource for the requested information. Although the terminal does not receive SIB1, it may receive the Master Information Block (MIB). The terminal may determine one of the multiple patterns as the resource for the requested information based on the information in the MIB (e.g., the PDCCH for scheduling SIB1 in the MIB, i.e., pdcch-ConfigSIB1).

[0128] In some embodiments, the first resource includes a physical uplink control channel (PUCCH) resource.

[0129] That is, the request information sent by the terminal to the network device may also be carried by the PUCCH, where the PUCCH includes at least one of the following: PUCCH format #0, PUCCH format #1, PUCCH format #2, and PUCCH format #3.

[0130] It should be noted that the channel used to carry the request information is not limited to the PUCCH, and can also be carried by other channels, and this disclosure does not limit this. For example, the request information can also be carried by the Physical Random Access Channel (PRACH), that is, the first resource can include a PRACH resource.

[0131] In some embodiments, the first resource overlaps with a legacy PUCCH resource used to send legacy information, and the request information or the legacy information is sent on the overlapping resource.

[0132] For example, traditional PUCCH resources include at least one of the following: resources for reporting channel state information (CSI), resources for sending hybrid automatic repeat request (HARQ) information (such as HARQ-ACK, HARQ-NACK), and resources for sending scheduling requests (SR).

[0133] The first resource is a newly defined resource relative to the traditional PUCCH resource. Therefore, the first resource may overlap with the traditional PUCCH resource. In this case, the terminal can choose to send the request information or the traditional information on the overlapping resource. The specific selection can be configured by the network equipment or determined based on the protocol agreement.

[0134] For example, the PUCCH resources used to send request information overlap with the PUCCH resources used to send CSI. The network device configures the terminal to send traditional information on the overlapping resources. Then the terminal can send CSI on the overlapping PUCCH resources instead of sending request information (for example, the request information can be sent on the next first resource).

[0135] For example, the PUCCH resources used to send request information overlap with the PUCCH resources used to send SR. The network device configures the terminal to send request information on the overlapping resources. Then the terminal can send the request information on the overlapping PUCCH resources instead of sending SR (for example, SR can be sent on the next PUCCH resource used to send SR).

[0136] In some embodiments, when the first resource overlaps with a traditional PUCCH resource used to send traditional information, the terminal may also determine whether to request information or send traditional information based on a priority relationship between the traditional information and the first information requested by the request information.

[0137] For example, the priority of the first information is higher than that of the legacy information, and the terminal may send the request information on the overlapping resources instead of sending the legacy information (for example, the legacy information may be sent on the next PUCCH resource used to send the legacy information).

[0138] For example, the priority of the first information is lower than that of the legacy information, and the terminal may send the legacy information on the overlapping resources instead of sending the request information (for example, the request information may be sent on the next first resource).

[0139] The above embodiments describe the case where the first resource is a newly defined resource relative to the traditional PUCCH resource. In addition, the first resource can also be shared with the traditional PUCCH, that is, the traditional PUCCH resource can be used to send request information. This is exemplified by several embodiments below.

[0140] In some embodiments, the legacy PUCCH resource used to send legacy information includes the first resource, and the determining of the first resource used to send the request information includes one of the following:

[0141] receiving indication information sent by a network device, wherein the indication information is used to indicate the first resource in the traditional PUCCH resource;

[0142] The first resource is determined in the traditional PUCCH resources in a manner agreed upon in a protocol.

[0143] In some embodiments, traditional PUCCH resources for sending traditional information may include first resources. For example, at least one of resources used to send resources for reporting CSI, resources used to send HARQ information, and resources used to send SR may also be used to send request information. In this case, the terminal needs to clearly identify which traditional PUCCH resources can be used as the first resource to send request information.

[0144] For example, the network device may indicate a first resource in a traditional PUCCH resource through indication information, so that when the terminal needs to send request information to the network device, it may select the first resource in the traditional PUCCH through the indication information to send the request information. For example, the traditional PUCCH resources constitute a PUCCH resource set (set), each traditional PUCCH resource corresponds to an index (index), and the indication information may indicate one or more indexes in the PUCCH resource set, and the terminal may determine the traditional PUCCH resource corresponding to the index as the first resource.

[0145] For example, the indication of the first resource in the traditional PUCCH resources may be determined based on a protocol agreement. When the terminal needs to send a request to the network device, it may select the first resource in the traditional PUCCH based on the protocol agreement to send the request. For example, the traditional PUCCH resources constitute a PUCCH resource set (set), each of which corresponds to an index (index). The protocol may stipulate that the PUCCH with the smallest or largest index in the set is the first resource.

[0146] In some embodiments, the first beam where the request information is located and the second beam where the first information is located are quasi co-located (QCL).

[0147] In some embodiments, the terminal enters a non-connected state and the first resource is not released. For example, the non-connected state includes at least one of the following: an idle state and an inactive state.

[0148] Since the first resource is used by the terminal to send request information to the network device, and the first information requested by the request information (such as SSB, SIB1) is generally relatively important, the terminal cannot even communicate normally if the first information is not successfully obtained. Therefore, even if the terminal is in a non-connected state, the first resource used to send the request information can remain unreleased, so that when the terminal needs to obtain the first information, it can still send the request information to the network device on the first resource, so as to ensure that the terminal can successfully obtain the first information to achieve normal communication.

[0149] In some embodiments, at least one of the network device and the terminal is in a discontinuous reception (DTX) state or a discontinuous transmission (DRT) state, and the terminal sends the request information to the network device according to the first resource during an inactive period of the discontinuous reception state or the discontinuous transmission state.

[0150] The DRX and / or DTX status may be for a network device or for a terminal.

[0151] For example, when the network device is in the DRX inactive state, the network device suspends the receiving operation, but in an embodiment of the present disclosure, the network device can still receive the first request sent by the terminal on the first resource in the DRX inactive state, so that when the terminal needs to obtain the first information, the network device can receive the request information sent by the terminal on the first resource in a timely manner, so as to ensure that the terminal can smoothly obtain the first information to achieve normal communication.

[0152] For example, when the terminal is in the DTX inactive state, the terminal suspends the sending operation, but in an embodiment of the present disclosure, the terminal can still send a first request to the network device on the first resource in the DTX inactive state, so that when the terminal needs to obtain the first information, it can send the request information to the network device on the first resource in a timely manner to ensure that the terminal can smoothly obtain the first information to achieve normal communication.

[0153] In some embodiments, the request information is used to request the network device to send at least one first information in an on-demand state.

[0154] In this embodiment, after receiving the request information sent by the terminal, the network device may send at least one first information in an on-demand state.

[0155] For example, the at least one on-demand first information requested by the request information may be non-specific first information among all the on-demand first information. The at least one on-demand first information may be all the on-demand first information, or the at least one on-demand first information may be part of the on-demand first information.

[0156] For example, the at least one first information in the on-demand state requested by the request information may be specific first information among all first information in the on-demand state. The following describes how the request information requests specific first information in the on-demand state through several embodiments.

[0157] In some embodiments, the request information is associated with the at least one first information in an on-demand state and / or the beam where the at least one first information in an on-demand state is located; or,

[0158] The first resource is associated with the at least one first information in an on-demand state and / or the beam where the at least one first information in an on-demand state is located; or,

[0159] The value of the bit in the request information and the first resource are associated with the at least one first information in an on-demand state and / or the beam where the at least one first information in an on-demand state is located.

[0160] Among them, the association relationship between the request information and the first information can be configured by the network device or agreed upon by the protocol; the association relationship between the request information and the beam can be configured by the network device or agreed upon by the protocol; the association relationship between the first resource and the first information can be configured by the network device or agreed upon by the protocol; the association relationship between the first resource and the beam can be configured by the network device or agreed upon by the protocol.

[0161] In some embodiments, the request information may be associated with at least one first information in an on-demand state. For example, the request information includes 3 bits and the first information includes SSB. There are 4 SSBs in the system, namely SSB#0, SSB#1, SSB#2, and SSB#3.

[0162] For example, when the request information is 000, the request information is associated with SSB#0 and SSB#1;

[0163] When the request information is 001, the request information is associated with SSB#2 and SSB#3;

[0164] When the request information is 010, the request information is associated with SSB#1 and SSB#2;

[0165] When the request information is 011, the request information is associated with SSB#1, SSB#2, SSB#3, and SSB#4;

[0166] When the request information is 100, the request information is associated with SSB#0;

[0167] When the request information is 101, the request information is associated with SSB#1;

[0168] When the request information is 110, the request information is associated with SSB#2;

[0169] When the request information is 111, the request information is associated with SSB#3.

[0170] For example, when the terminal needs to request SSB#0 in the on-demand state, the request information sent to the network device can be 100. Based on the received request information, the network device can determine that the terminal requests the network device to send SSB#0, and then can choose to send SSB#0.

[0171] In some embodiments, the request information may be associated with the beam in which the first information is located. For example, the request information includes 2 bits, and the beams include beam#1, beam#2, beam#3, and beam#4.

[0172] For example, when the request information is 00, the request information is associated with beam #1;

[0173] When the request information is 01, the request information is associated with beam#2;

[0174] When the request information is 10, the request information is associated with beam#3;

[0175] When the request information is 11, the request information is associated with beam#4.

[0176] For example, when the terminal needs to request the first information on beam#3 that is in an on-demand state, the request information sent to the network device can be 10. Based on the received request information, the network device can determine that the terminal requests the network device to send the first information on beam#3, and then can choose to send the first information on beam#3.

[0177] In some embodiments, the request information may be associated with at least one first information in an on-demand state and the beam in which the first information resides. For example, the request information includes three bits, the first information includes SSB#1, SSB#2, SSB#3, and SSB#4, and the beams include beam#1, beam#2, beam#3, and beam#4.

[0178] For example, when the request information is 000, the request information is associated with beam#1 and SSB#1;

[0179] When the request information is 001, the request information is associated with beam#2 and SSB#2;

[0180] When the request information is 010, the request information is associated with beam#3 and SSB#3;

[0181] When the request information is 011, the request information is associated with beam#4 and SSB#4;

[0182] When the request information is 100, the request information is associated with beam#1 and beam#2, SSB#1 and SSB#2;

[0183] When the request information is 101, the request information is associated with beam#3 and beam#4, SSB#3 and SSB#4;

[0184] When the request information is 110, the request information is associated with beam#1 and beam#3, SSB#1 and SSB#3;

[0185] When the request information is 111, the request information is associated with beam#1, beam#2, beam#3, beam#4, SSB#1, SSB#2, SSB#3, and SSB#4;

[0186] For example, when the terminal needs to request SSB#2 in the on-demand state on beam#2, the request information sent to the network device can be 001. Based on the received request information, the network device can determine that the terminal requests the network device to send SSB#2 on beam#2, and then can choose to send SSB#2 on beam#2.

[0187] In some embodiments, the first resource may be associated with at least one first information in an on-demand state. For example, the first resource includes five resources, namely Resource#1, Resource#2, Resource#3, Resource#4, and Resource#5, and the first information includes an SSB. There are four SSBs in the system, namely SSB#0, SSB#1, SSB#2, and SSB#3.

[0188] For example, when the first resource is Resource#1, the first resource is associated with SSB#0;

[0189] When the first resource is Resource#2, the first resource is associated with SSB#1;

[0190] When the first resource is Resource#3, the first resource is associated with SSB#2;

[0191] When the first resource is Resource#4, the first resource is associated with SSB#3;

[0192] When the first resource is Resource#5, the first resource is associated with SSB#0, SSB#1, SSB#2, and SSB#3.

[0193] For example, when the terminal needs to request SSB#1 in the on-demand state, it can send a request message to the network device on Resource#2. After the network device receives the request message on Resource#2, it can determine that the terminal requests the network device to send SSB#1, and then can choose to send SSB#1.

[0194] In some embodiments, the first resource may be associated with the beam in which the first information is located. For example, the first resource includes four resources, namely Resource#1, Resource#2, Resource#3, and Resource#4, and the beams include beam#1, beam#2, beam#3, and beam#4.

[0195] For example, when the first resource is Resource#1, the first resource is associated with beam#1;

[0196] When the first resource is Resource#2, the first resource is associated with beam#2;

[0197] When the first resource is Resource#3, the first resource is associated with beam#3;

[0198] When the first resource is Resource#4, the first resource is associated with beam#4.

[0199] For example, when the terminal needs to request the first information on beam#3 that is in an on-demand state, it can send the request information to the network device in Resource#3. After the network device receives the request information in Resource#3, it can determine that the terminal requests the network device to send the first information on beam#3, and then it can choose to send the first information on beam#3.

[0200] In some embodiments, the first resource may be associated with the first information and the beam in which the first information is located. For example, the first resource includes eight resources, namely Resource#1 and Resource#2, the first information includes SSB#1 and SSB#2, and the beam includes beam#1 and beam#2.

[0201] For example, when the first resource is Resource#1, the first resource is associated with beam#1 and SSB#1;

[0202] When the first resource is Resource#2, the first resource is associated with beam#2 and SSB#2.

[0203] For example, when the terminal needs to request SSB#2 on beam#2 which is in an on-demand state, it can send a request message to the network device on Resource#2. After the network device receives the request message on Resource#2, it can determine that the terminal requests the network device to send SSB#2 on beam#2, and then it can choose to send SSB#2 on beam#2.

[0204] In some embodiments, the request information and the first resource may be associated with the first information and the beam in which the first information resides. For example, the request information includes one bit, the first resource includes two resources, Resource#1 and Resource#2, the first information includes SSB#1, SSB#2, SSB#3, and SSB#4, and the beams include beam#1, beam#2, beam#3, and beam#4.

[0205] For example, when the request information is 0 and the first resource is Resource#1, the request information and the first resource are associated with beam#1 and SSB#1;

[0206] The request information is 1, the first resource is Resource#1, and the request information and the first resource are associated with beam#2 and SSB#2;

[0207] The request information is 0, the first resource is Resource#2, and the request information and the first resource are associated with beam#3 and SSB#3;

[0208] The request information is 1, the first resource is Resource#2, and the request information and the first resource are associated with beam#4 and SSB#4.

[0209] For example, when the terminal needs to request SSB#2 in the on-demand state on beam#2, it can send request information 1 to the network device on Resource#1. After the network device receives the request information on Resource#1 and determines that the request information is 1, it can be determined that the terminal requests the network device to send SSB#2 on beam#2, and then it can choose to send SSB#2 on beam#2.

[0210] The above embodiments mainly describe that the granularity of the terminal requesting the first information may include the beam where the first information is located.

[0211] In the embodiments of the present disclosure, the granularity of the terminal requesting the first information is not limited to the beam where the first information is located, but may also include other granularities, which are not limited by the present disclosure. For example, it may also include the cell where the first information is located, the BWP where the first information is located, the SSB index corresponding to the first information (e.g., SIB1), etc.

[0212] The technical solution of the present disclosure is exemplarily described below through several embodiments, taking the example that the granularity of the terminal requesting the first information includes the cell where the first information is located.

[0213] In some embodiments, when the network device configures the first resource for the terminal, the operation of the terminal sending the request information to the network device can be performed in one of the following scenarios:

[0214] Scenario 1: A terminal receives configuration information sent by a first network device corresponding to the first cell in a first cell, and subsequently switches to a second cell through a cell switching operation. When the terminal needs to obtain first information in an on-demand state in the second cell, the terminal can switch back to the first cell and send a request information to the first network device based on the configuration information in the first cell.

[0215] In this case, for example, the first cell may be referred to as an anchor cell, and the second cell may be referred to as a non-anchor cell.

[0216] The network device can configure resources for the terminal on the anchor cell, which is used for the terminal to send request information, where the request information is used to request one or more other cells (such as non-anchor cells) to send the first information, and can also receive request information for requesting other cells to send the first information on the anchor cell.

[0217] For example, after switching back to the first cell, the terminal can send a request message to the first network device on the resources configured by the configuration information. After receiving the request message, the first network device can send the request message to the second network device corresponding to the second cell. After receiving the request message, the second network device can determine whether to send the first message in the second cell.

[0218] In some embodiments, the request information sent by the terminal and / or the resource where the request information is located may be associated with a cell (the association may be determined based on a network device indication or may be determined based on a protocol agreement). For example, when the terminal needs to obtain first information in an on-demand state in a second cell, it may send request information associated with the second cell to the first network device in the first cell, and / or send request information to the first network device on the resource associated with the second cell. Based on this, the first network device may determine that the request information sent by the terminal is for requesting the first information in the second cell.

[0219] Scenario 2: A terminal in a first cell receives configuration information sent by a first network device corresponding to the first cell, and subsequently switches to a second cell through a cell switching operation. When the terminal needs to obtain first information in an on-demand state in the second cell, the terminal can send a request information based on the configuration information in the second cell. In this case, the configuration information may be known to the second cell.

[0220] In this case, for example, the first cell may be referred to as an anchor cell, and the second cell may be referred to as a non-anchor cell.

[0221] The network device can configure resources for the terminal on the anchor cell, which is used for the terminal to send request information, where the request information is used to request one or more other cells (such as non-anchor cells) to send the first information, and can also receive request information for requesting other cells to send the first information on the anchor cell.

[0222] For example, the terminal in the second cell can send request information to the second network device corresponding to the second cell on the resources configured by the configuration information. After receiving the request information, the second network device can determine whether to send the first information in the second cell.

[0223] Scenario 3: After the terminal switches from the first cell to the second cell, it can determine the resources used to send the request information based on the configuration information sent by the second network device corresponding to the second cell. When the terminal needs to obtain the first information in the on-demand state in the second cell, the terminal can send the request information to the second network device on the first resource.

[0224] In some embodiments, the first information includes SIB1, and the SIB1 in the second cell is in an on-demand state. Then, after the terminal switches to the second cell, it has not yet received SIB1. In this case, the terminal can obtain configuration information from the SSB (e.g., the MIB in the SSB), or it is necessary to determine the resources for sending the request information based on other methods. For example, at least one pattern corresponding to the resource can be determined based on the protocol agreement. The terminal can determine a pattern from multiple patterns as the resource for the request information based on the information in the MIB (e.g., the PDCCH in the MIB used to schedule SIB1, i.e., pdcch-ConfigSIB1).

[0225] In some embodiments, when the first information includes SIB1, the SIB1 in the second cell is in an on-demand state, then the terminal has not received SIB1 after switching to the second cell. In this case, the terminal has not yet learned the frequency domain information of the initial uplink bandwidth part (initial UL BWP), but can receive SSB. Therefore, in order to determine the frequency domain information corresponding to the resource of the requested information, the frequency domain information of SSB can be used as a reference position. Moreover, in this case, the terminal has not yet learned the time division duplexing (TDD) related configuration, but can receive SSB. Therefore, in order to determine the time domain position corresponding to the resource of the requested information, the time domain information of SSB can be used as a reference position. That is, in this embodiment, the frequency domain information and time domain information of SSB can be used as configuration information.

[0226] Scenario 4: After the terminal switches from the first cell to the second cell, when the terminal needs to obtain the first information in the second cell in an on-demand state, the terminal determines the configuration information of the request information based on the protocol agreement, and based on the configuration information, it can determine the resources used to send the request information.

[0227] In some embodiments, the first information includes SIB1, and the SIB1 in the second cell is in an on-demand state. Therefore, after the terminal switches to the second cell, it has not yet received SIB1. In this case, the terminal may first determine at least one pattern corresponding to the resource based on the protocol agreement, and the terminal may determine a pattern from multiple patterns as the resource for requesting information based on information in the MIB (for example, the PDCCH used to schedule SIB1 in the MIB, i.e., pdcch-ConfigSIB1).

[0228] In some embodiments, if the first information includes SIB1, and SIB1 in the second cell is in an on-demand state, the terminal has not yet received SIB1 after switching to the second cell. In this case, the terminal has not yet learned the frequency domain information of the initial UL BWP, but can receive the SSB. Therefore, to determine the frequency domain information corresponding to the resource for the requested information, the frequency domain information of the SSB can be used as a reference position. Exemplarily, the resource for the requested information can be the same as the number of RBs occupied by the SSB, or can be the lowest / highest M RBs of the SSB. The M can be determined based on a predefined method or based on signaling.

[0229] Moreover, in this case, the terminal has not yet learned the TDD-related configuration, but can receive SSB. Therefore, in order to determine the time domain position corresponding to the resource of the requested information, the time domain information of SSB can be used as a reference position.

[0230] Exemplarily, the time domain position of the request information may be a time domain position starting from the first OFDM (Orthogonal Frequency Division Multiplexing) symbol of the first SSB corresponding to the SSB burst and spaced by M time units, and the time unit may be an OFDM symbol, an OFDM time slot, a subframe, a frame, etc., which will not be described in detail in the present invention;

[0231] For example, the time domain position of the request information may be a time domain position starting from the last OFDM symbol of the last SSB corresponding to the SSB burst and spaced by M time units, and the time unit may be an OFDM symbol, an OFDM time slot, a subframe, a frame, etc., which will not be described in detail in the present invention;

[0232] The M may be determined based on a predefined or signaling configuration, for example, 5 time slots or 2 OFDM symbols.

[0233] The communication method involved in the embodiments of the present disclosure may include at least one of steps S201 and S202. For example, step S201 may be implemented as an independent embodiment, step S202 may be implemented as an independent embodiment, and steps S201+S202 may be implemented as independent embodiments, but are not limited thereto.

[0234] In some embodiments, steps S201 and S202 may be executed in an exchanged order or simultaneously, and steps xx and xx may be executed in an exchanged order or simultaneously.

[0235] In some embodiments, step S201 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0236] In some embodiments, step S202 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0237] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 2 .

[0238] In a first aspect, an embodiment of the present disclosure proposes a request sending method. Figure 3 is a schematic flow chart illustrating a request sending method according to an embodiment of the present disclosure. The request sending method illustrated in this embodiment can be executed by a terminal.

[0239] As shown in FIG3 , the request sending method may include the following steps:

[0240] In step S301, a first resource for sending request information is determined;

[0241] In step S302, the request information is sent to the network device according to the first resource, wherein the request information is used to request the network device to send first information in an on-demand state.

[0242] It should be noted that the embodiment shown in FIG. 3 can be implemented independently or in combination with at least one other embodiment in the present disclosure. The specific selection can be made as needed and the present disclosure does not limit it.

[0243] In some embodiments, the request information is used to request the network device to send at least one first information in an on-demand state.

[0244] In some embodiments, the request information is associated with the at least one first information in an on-demand state and / or the beam where the at least one first information in an on-demand state is located; or,

[0245] The first resource is associated with the at least one first information in an on-demand state and / or the beam where the at least one first information in an on-demand state is located; or,

[0246] The value of the bit in the request information and the first resource are associated with the at least one first information in an on-demand state and / or the beam where the at least one first information in an on-demand state is located.

[0247] In some embodiments, determining the first resource for sending the request information includes one of the following:

[0248] determining the first resource according to configuration information in cell-specific signaling;

[0249] Determining the first resource according to configuration information in the terminal-specific signaling;

[0250] The first resource is determined according to the method agreed upon in the protocol.

[0251] In some embodiments, the first resource includes a physical uplink control channel (PUCCH) resource.

[0252] In some embodiments, the first resource overlaps with a legacy PUCCH resource used to send legacy information, and the request information or the legacy information is sent on the overlapping resource.

[0253] In some embodiments, the legacy PUCCH resource used to send legacy information includes the first resource, and the determining of the first resource used to send the request information includes one of the following:

[0254] receiving indication information sent by a network device, wherein the indication information is used to indicate the first resource in the traditional PUCCH resource;

[0255] The first resource is determined in the traditional PUCCH resources in a manner agreed upon in a protocol.

[0256] In some embodiments, the first beam containing the request information and the second beam containing the first information are quasi-co-located.

[0257] In some embodiments, the terminal enters a non-connected state and the first resource is not released.

[0258] In some embodiments, at least one of the network device and the terminal is in a discontinuous reception state or a discontinuous transmission state, and the terminal sends the request information to the network device according to the first resource during an inactive period of the discontinuous reception state or the discontinuous transmission state.

[0259] In some embodiments, the first information includes at least one of the following: a synchronization broadcast signal block; a system information block 1; a channel state information reference signal; a tracking reference signal; a physical downlink control channel; a physical downlink shared channel; or a newly defined reference signal.

[0260] For the first aspect and the optional implementation of the optional embodiment of the first aspect, reference can be made to the optional implementation in the embodiment shown in FIG2 and other related parts in the embodiment involved in FIG2 , which will not be described in detail here.

[0261] In a second aspect, an embodiment of the present disclosure provides a request receiving method. Figure 4 is a schematic flow chart illustrating a request receiving method according to an embodiment of the present disclosure. The request receiving method illustrated in this embodiment can be executed by a network device.

[0262] As shown in FIG4 , the request receiving method may include the following steps:

[0263] In step S401, the request information sent by the terminal is received on a first resource used for the terminal to send request information, wherein the request information is used to request the network device to send first information in an on-demand state.

[0264] It should be noted that the embodiment shown in FIG. 4 can be implemented independently or in combination with at least one other embodiment in the present disclosure. The specific selection can be made as needed and the present disclosure does not limit it.

[0265] In some embodiments, the request information is used to request the network device to send at least one first information in an on-demand state.

[0266] In some embodiments, the request information is associated with the at least one first information in an on-demand state and / or the beam where the at least one first information in an on-demand state is located; or,

[0267] The first resource is associated with the at least one first information in an on-demand state and / or the beam where the at least one first information in an on-demand state is located; or,

[0268] The value of the bit in the request information and the first resource are associated with the at least one first information in an on-demand state and / or the beam where the at least one first information in an on-demand state is located.

[0269] In some embodiments, the first resource used to send the request information is determined based on one of the following: configuration information in cell-specific signaling; configuration information in terminal-specific signaling; or a method agreed upon in a protocol.

[0270] In some embodiments, the first resource includes a physical uplink control channel (PUCCH) resource.

[0271] In some embodiments, the first resource overlaps with a legacy PUCCH resource used to send legacy information, and the request information or the legacy information is sent on the overlapping resource.

[0272] In some embodiments, the legacy PUCCH resource used to send legacy information includes the first resource, and the first resource used for the terminal to send request information is determined based on at least one of the following:

[0273] The indication information of the network device indicates the first resource in the traditional PUCCH resource;

[0274] The first resource is determined in the traditional PUCCH resources in a manner agreed upon in a protocol.

[0275] In some embodiments, the first beam containing the request information and the second beam containing the first information are quasi-co-located.

[0276] In some embodiments, the terminal enters a non-connected state and the first resource is not released.

[0277] In some embodiments, at least one of the network device and the terminal is in a discontinuous reception state or a discontinuous transmission state, and the terminal sends the request information to the network device according to the first resource during an inactive period of the discontinuous reception state or the discontinuous transmission state.

[0278] In some embodiments, the first information includes at least one of the following: a synchronization broadcast signal block; a system information block 1; a channel state information reference signal; a tracking reference signal; a physical downlink control channel; a physical downlink shared channel; or a newly defined reference signal.

[0279] The second aspect and the optional implementation of the optional embodiment of the second aspect can be referred to the optional implementation in the embodiment shown in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0280] The technical solution of the present disclosure is exemplified below through several embodiments.

[0281] Example 1: For example, a base station (for example, a network device includes a base station) is a base station that supports network energy-saving technology. The base station can choose to stop sending part of the downlink signals or channels according to the network load, the number of resident terminals, the service type, the service period, etc. Of course, the present disclosure does not impose any restrictions on the decision-making process and strategy of whether the base station sends the part of the downlink signal or channel. After the base station receives the indication information sent by the terminal, it can choose to resume sending the downlink signal or channel according to the request information of the terminal. In this embodiment, according to the request of the terminal, the base station determines to send any one or any combination of the following downlink signals or channels: SSB, SIB1, TRS, PDCCH, PDSCH, CSI-RS, other newly defined downlink reference signals, such as PSS+SSS, DRS, etc.

[0282] In this embodiment, the terminal sends a PUCCH channel to the base station, and requests the base station to send the downlink signal and / or signal through the indication information carried on the PUCCH channel. In this embodiment, the terminal carries the request information through PUCCH format#2, which is referred to as a wake-up signal WUS (wake-up signal) in the subsequent description. In this embodiment, the terminal sends specific PUCCH format#2 information on the periodically appearing WUS resources, and the PUCCH format#2 information is used to request the base station to send downlink signals and / or channels. The WUS resources are used for the terminal to send PUCCH format#2, and the PUCCH format#2 carries the PUCCH format#2 information for requesting the base station to send downlink signals / channels. In this embodiment, the terminal determines the time-frequency resources occupied by the PUCCH format#2 used to request the base station to send downlink signals by the following method:

[0283] This disclosure does not make any provisions for the state of the terminal. For example, this disclosure can be applied to terminals in connected state, IDLE state, or INACTIVE state. This disclosure also does not impose any restrictions on the base station from which the configuration of the time-frequency resources for sending the WUS signal comes. For example, the relevant configuration information in this disclosure can be sent by the base station from which the terminal requests downlink transmission, or by other base stations.

[0284] The configuration information in the cell-specific signaling sent by the base station is determined. The present disclosure does not limit the type of the cell-specific signaling, such as SIB1 or other SIBs.

[0285] Alternatively, it is determined according to the configuration information in the UE-dedicated RRC signalling sent by the base station.

[0286] Alternatively, it is determined in a manner predefined in the protocol, that is, the terminal sends PUCCH format #2 on a default resource specified in the protocol to request the base station to send a downlink message.

[0287] Because the PUCCH format #2 resource used to request the base station to send a downlink transmission may conflict with other PUCCH format #2 resources used to send CSI, HARQ confirmation information, or SR information, in this scenario, this disclosure assumes that the terminal sends CSI, HARQ confirmation information, or SR information on the resource as needed. Alternatively, in this scenario, this disclosure assumes that the terminal sends WUS information on the resource.

[0288] As for the PUCCH resource used to send PUCCH format #2, it is an additional PUCCH resource configured or determined by any of the aforementioned methods. That is, it is different from the traditional PUCCH resource used to carry CSI or HARQ confirmation information or SR resources. Alternatively, the PUCCH resource used to send PUCCH format #2 is shared with the legacy PUCCH resource, that is, through any of the aforementioned methods, one or more PUCCH resources are selected in the PUCCH resource set to send indication information requesting the base station to transmit downlink. Under this assumption, the base station needs to inform the terminal of the PUCCH resource identifier used to send the indication information requesting the base station to transmit downlink, and the PUCCH resource cannot be used to send PUCCH format #2 carrying CSI or HARQ confirmation information or SR. Alternatively, the terminal needs to determine the PUCCH resource identifier used to send downlink transmission indication information in a predefined manner, for example, the PUCCH resource that identifies the minimum or represents the maximum in the set.

[0289] Based on the above assumptions and configurations, the terminal sends PUCCH format #2 on the WUS resource, carrying the downlink transmission indication information requesting the base station when it needs to request the base station to send the corresponding downlink signal or channel. In this embodiment, it is assumed that the terminal sends any allowed bit information PUCCH format #2 information on the resource to request the base station to send a downlink channel or signal. The PUCCH format #2 information is used to request the base station to send SSB, or SIB1, or SSB and SIB1, or SSB corresponding to a specific beam, SIB1 corresponding to a specific beam, or SSB or SIB1 corresponding to a specific beam, or any other combination of downlink channels and / or signals, as described above.

[0290] When the terminal is in the IDLE / INACTIVE state, the configuration information is not released, and the terminal can still send PUCCH format #2 on the corresponding time-frequency resources according to the configuration information to request the base station to send the corresponding downlink signal or channel.

[0291] Furthermore, after the terminal sends the WUS signal, the terminal detects and receives the corresponding downlink channel and / or signal at the time domain resource location of the first downlink channel and / or signal transmission requested after T. The T is determined according to the terminal capability, or is determined in a predefined manner, or is determined through configuration information sent by the base station.

[0292] Furthermore, after the terminal fails to detect and receive the corresponding downlink channel and / or signal in the N requested downlink channel and / or signal transmission time domain resource locations after T, the terminal may continue to send a WUS signal request. The N is determined according to the terminal capability, or is determined in a predefined manner, or is determined through configuration information sent by the base station.

[0293] After detecting and receiving the WUS signal sent by the terminal, the base station sends the downlink signal or channel requested by the terminal.

[0294] Based on this, the following figure is a schematic diagram of requesting the base station to send SSB through the WUS signal carried by PUCCH format #2. Of course, the downlink channel can be any one or any combination of the aforementioned channels or signals, and this disclosure does not impose any restrictions. In addition, taking SSB as an example, during the SSB OFF period, the base station can selectively send other signals or signals, and this disclosure does not impose any restrictions.

[0295] Example 2: For example, a base station (for example, a network device includes a base station) is a base station that supports network energy-saving technology. The base station can choose to stop sending part of the downlink signals or channels according to the network load, the number of resident terminals, the service type, the service period, etc. Of course, the present disclosure does not impose any restrictions on the decision-making process and strategy of whether the base station sends the said part of the downlink signal or channel. After the base station receives the indication information sent by the terminal, it can choose to resume sending the downlink signal or channel according to the request information of the terminal. In this embodiment, according to the request of the terminal, the base station determines to send any one or any combination of the following downlink signals or channels: SSB, SIB1, TRS, PDCCH, PDSCH, CSI-RS, other newly defined downlink reference signals, such as PSS+SSS, DRS, etc.

[0296] In this embodiment, the terminal sends a PUCCH channel to the base station, and requests the base station to send the downlink signal and / or signal through the indication information carried on the PUCCH channel. In this embodiment, the terminal carries the request information through PUCCH format#2, which is referred to as wake-up signal in the subsequent description. In this embodiment, the terminal sends specific PUCCH format#2 information on the periodically appearing WUS resources, and the PUCCH format#2 information is used to request the base station to send downlink signals and / or channels. The WUS resources are used for the terminal to send PUCCH format#2, and the PUCCH format#2 carries the PUCCH format#2 information for requesting the base station to send downlink signals / channels. In this embodiment, the terminal determines the time-frequency resources occupied by the PUCCH format#2 used to request the base station to send downlink signals by the following method:

[0297] Determined according to configuration information in the cell-specific signaling sent by the base station. The present disclosure does not limit the type of the cell-specific signaling, such as SIB1 or other SIBs;

[0298] Alternatively, it is determined according to configuration information in UE-dedicated RRC signaling sent by the base station;

[0299] Alternatively, it is determined in a manner predefined in the protocol, that is, the terminal sends PUCCH format #2 on a default resource specified in the protocol to request the base station to send a downlink message.

[0300] This disclosure does not make any provisions for the state of the terminal. For example, this disclosure can be applied to terminals in connected state, IDLE state, or INACTIVE state. This disclosure also does not impose any restrictions on the base station from which the configuration of the time-frequency resources for sending the WUS signal comes. For example, the relevant configuration information in this disclosure can be sent by the base station from which the terminal requests downlink transmission, or by other base stations.

[0301] Because the PUCCH format #2 resource used to request the base station to send a downlink transmission may conflict with other PUCCH format #2 resources used to send CSI, HARQ acknowledgment information, or SR information, in this scenario, this disclosure assumes that the terminal sends CSI, HARQ acknowledgment information, or SR information on the resource as needed. Alternatively, in this scenario, this disclosure assumes that the terminal sends WUS information on the resource.

[0302] As for the PUCCH resource used to send PUCCH format #2, it is an additional PUCCH resource configured or determined by any of the aforementioned methods. That is, it is different from the traditional PUCCH resource used to carry ACK / NAK or SR resources. Alternatively, the PUCCH resource used to send PUCCH format #2 is shared with the legacy PUCCH resource, that is, through any of the aforementioned methods, one or more PUCCH resources are selected in the PUCCH resource set to send indication information requesting the base station to transmit downlink. Under this assumption, the base station needs to inform the terminal of the PUCCH resource identifier used to send the indication information requesting the base station to transmit downlink, and the PUCCH resource cannot be used to send CSI or HARQ confirmation information or SR PUCCH format #2. Alternatively, the terminal needs to determine the PUCCH resource identifier used to send downlink transmission indication information in a predefined manner, for example, the PUCCH resource that identifies the minimum or represents the maximum in the set.

[0303] Based on the above assumptions and configurations, the terminal sends PUCCH format #2 carrying downlink transmission indication information requesting the base station on the WUS resource when it needs to request the base station to send the corresponding downlink signal or channel. In this embodiment, it is assumed that the terminal sends specific PUCCH format #2 information on the resource to request the base station to send a downlink channel or signal. The PUCCH format #2 information is used to request the base station to send SSB, or SIB1, or SSB and SIB1, or SSB corresponding to a specific beam, SIB1 corresponding to a specific beam, or SSB or SIB1 corresponding to a specific beam, or any other combination of downlink channels and / or signals, as described above.

[0304] The specific information PUCCH format#2 information used to request the base station to send a downlink signal or channel is determined in a protocol predefined manner, such as information composed of a specific length and specific bit information, e.g., '00000000000'; it can also be configured by the base station, that is, the base station specifies which bit indicates the corresponding information to be used as the WUS signal. Furthermore, the specific PUCCH format#2 information may correspond to the transmission beam of the downlink signal and / or channel, such as the corresponding one or more SSB indices. The correspondence between the aforementioned PUCCH format#2 information and the signal and / or channel requested by the terminal is configured through high-layer signaling or determined in a protocol predefined manner. Furthermore, the specific information can be used to request the SSB and / or SIB1 of a specific beam, and the beam is quasi-co-located with the beam corresponding to PUCCH format#2, and the present disclosure does not impose any limitation.

[0305] When the terminal is in the IDLE / INACTIVE state, the configuration information is not released, and the terminal can still send PUCCH format #2 on the corresponding time-frequency resources according to the configuration information to request the base station to send the corresponding downlink signal or channel.

[0306] Furthermore, after the terminal sends the WUS signal, the terminal detects and receives the corresponding downlink channel and / or signal at the time domain resource location of the first downlink channel and / or signal transmission requested after T. The T is determined according to the terminal capability or by configuration information sent by the base station.

[0307] Furthermore, after the terminal fails to detect and receive the corresponding downlink channel and / or signal in the N requested downlink channel and / or signal transmission time domain resource locations after T, the terminal may continue to send a WUS signal request. The N is determined according to the terminal capability, or is determined in a predefined manner, or is determined through configuration information sent by the base station.

[0308] After detecting and receiving the WUS signal sent by the terminal, the base station sends the downlink signal or channel requested by the terminal.

[0309] Based on this, the following figure is a schematic diagram of requesting the base station to send SSB through the WUS signal carried by PUCCH format #2. Of course, the downlink channel can be any one or any combination of the aforementioned channels or signals, and the present disclosure does not impose any restrictions. In addition, taking SSB as an example, during the SSB OFF period, the base station may selectively send other signals or signals, and the present disclosure does not impose any restrictions. In the following example, it is assumed that the terminal can request the base station to send SSB through seven different types of information PUCCH format #2 information. Exemplarily, the proportion of the information is equal to 3 bits. Exemplarily, it is assumed that the transmission pattern of SSB at this time is case A, and it is below 3GHz, so there are 4 SSBs in the system. In this example, it is assumed that the terminal sends PUCCH format #2 information. The correspondence between PUCCH format #2 information and SSB is as follows, and the correspondence is determined by any of the aforementioned methods:

[0310] 000 corresponds to SSB#0 and SSB#1

[0311] 001 corresponds to SSB#2 and SSB#3

[0312] 010 corresponds to SSB#0, SSB#1, SSB#2, and SSB#3

[0313] 011 corresponds to SSB#0

[0314] 100 corresponds to SSB#1

[0315] 101 corresponds to SSB#2

[0316] 110 corresponds to SSB#3

[0317] To fully illustrate the solution of this embodiment, it is assumed that the terminal sends different PUCCH format #2 information PUCCH format #2 information at three different WUS transmission positions. As can be seen from the figure, when the base station does not receive any WUS signal sent by any terminal, the base station does not need to send SSB. When the base station receives PUCCH format #2 information corresponding to '000' sent by the terminal, it sends SSB #0 and SSB #1; when the base station receives PUCCH format #2 information corresponding to '001' sent by the terminal, it sends SSB #2 and SSB #3; when the base station receives PUCCH format #2 information corresponding to '010' sent by the terminal, it sends SSB #0, SSB #1, SSB #2 and SSB #4. Other indication information is similar and will not be repeated here.

[0318] Of course, as mentioned above, the method described in the present disclosure is not limited to SSB, nor is it limited to the correspondence between WUS signals and downlink signals. For example, in this example, it is assumed that the correspondence between the terminal sending PUCCH format #2 information and SIB1 is as follows, and the correspondence is determined by any of the above methods:

[0319] 000 corresponds to SIB1 sent by beam#1;

[0320] 001 corresponds to SIB1 sent by beam#2;

[0321] 010 corresponds to SIB1 sent by beam#3;

[0322] 011 corresponds to SIB1 sent by beam#4;

[0323] 100 corresponds to SIB1 sent in full beam.

[0324] Example 3: For example, a base station (for example, a network device includes a base station) is a base station that supports network energy-saving technology. The base station can choose to stop sending part of the downlink signals or channels according to the network load, the number of resident terminals, the service type, the service period, etc. Of course, the present disclosure does not impose any restrictions on the decision-making process and strategy of whether the base station sends the said part of the downlink signal or channel. After the base station receives the indication information sent by the terminal, it can choose to resume sending the downlink signal or channel according to the request information of the terminal. In this embodiment, according to the request of the terminal, the base station determines to send any one or any combination of the following downlink signals or channels: SSB, SIB1, TRS, PDCCH, PDSCH, CSI-RS, other newly defined downlink reference signals, such as PSS+SSS, DRS, etc.

[0325] In this embodiment, the terminal sends a PUCCH channel to the base station, and requests the base station to send the downlink signal and / or signal through the indication information carried on the PUCCH channel. In this embodiment, the terminal carries the request information through PUCCH format #2, which is referred to as a wake-up signal in the subsequent description. In this embodiment, the terminal sends specific PUCCH format #2 information on the periodically appearing WUS resource, and the PUCCH format #2 information is used to request the base station to send downlink signals and / or channels. The WUS resource is used by the terminal to send PUCCH format #2, and the PUCCH format #2 carries the PUCCH format #2 information used to request the base station to send downlink signals / channels.

[0326] In this embodiment, the terminal determines the time-frequency resources occupied by the PUCCH format #2 used to request the base station to send downlink signals by the following method:

[0327] Determined according to configuration information in the cell-specific signaling sent by the base station. The present disclosure does not limit the type of the cell-specific signaling, such as SIB1 or other SIBs;

[0328] Alternatively, it is determined according to configuration information in UE-dedicated RRC signaling sent by the base station;

[0329] Alternatively, it is determined in a manner predefined in the protocol, that is, the terminal sends PUCCH format #2 on a default resource specified in the protocol to request the base station to send a downlink message.

[0330] This disclosure does not make any provisions for the state of the terminal. For example, this disclosure can be applied to terminals in connected state, IDLE state, or INACTIVE state. This disclosure also does not impose any restrictions on the base station from which the configuration of the time-frequency resources for sending the WUS signal comes. For example, the relevant configuration information in this disclosure can be sent by the base station from which the terminal requests downlink transmission, or by other base stations.

[0331] Because the PUCCH format #2 resource used to request the base station to send a downlink transmission may conflict with other PUCCH format #2 resources used to send CSI, HARQ confirmation information, or SR information, in this scenario, this disclosure assumes that the terminal sends CSI, HARQ confirmation information, or SR information on the resource as needed. Alternatively, in this scenario, this disclosure assumes that the terminal sends WUS information on the resource.

[0332] The PUCCH resource used to send PUCCH format #2 is an additional PUCCH resource configured or determined by any of the aforementioned methods. That is, it is different from the traditional PUCCH resource used to carry CSI or HARQ confirmation or SR resources. Alternatively, the PUCCH resource used to send PUCCH format #2 is shared with the legacy PUCCH resource, that is, one or more PUCCH resources are selected in the PUCCH resource set through any of the aforementioned methods to send indication information requesting the base station downlink transmission.

[0333] Under this assumption, the base station needs to inform the terminal of the PUCCH resource identifier used to send downlink transmission indication information requesting the base station, and the PUCCH resource cannot be used to send PUCCH format #2 carrying CSI or HARQ confirmation information or SR. Alternatively, the terminal needs to determine the PUCCH resource identifier used to send downlink transmission indication information in a predefined manner, for example, the PUCCH resource that identifies the minimum or represents the maximum in the set. Based on the above assumptions and configurations, the terminal sends PUCCH format #2 that carries downlink transmission indication information requesting the base station on the WUS resource when it needs to request the base station side to send the corresponding downlink signal or channel.

[0334] In this embodiment, it is assumed that the terminal sends specific PUCCH format #2 information on one of the multiple WUS resources to request the base station to send a downlink channel or signal. The PUCCH format #2 information is used to request the base station to send an SSB, or SIB1, or SSB and SIB1, or SSB corresponding to a specific beam, SIB1 corresponding to a specific beam, or SSB or SIB1 corresponding to a specific beam, or any other combination of downlink channels and / or signals, as described above.

[0335] The specific PUCCH format#2 information used to request the base station to send a downlink signal or channel is determined in a protocol predefined manner, such as information composed of a specific length and specific bit information, e.g., '00000000000'; it can also be configured by the base station, that is, the base station specifies which cyclic shift is used as the WUS signal. Of course, the PUCCH format#2 information may not be distinguished, and the terminal may send any PUCCH format#2 information on one of the multiple WUS resources to request the base station to send the corresponding downlink signal or channel. The different resources may correspond to the transmission beams of the downlink signal and / or channel, such as one or more corresponding SSB indices. The correspondence between the aforementioned PUCCH format#2 information and the signal and / or channel requested by the terminal is configured through high-layer signaling or determined in a protocol predefined manner. Furthermore, the specific information can be used to request the SSB and / or SIB1 of a specific beam, and the beam is quasi-co-located with the beam corresponding to the PUCCH format#2, and the present disclosure does not impose any limitations thereon.

[0336] As a more flexible indication method, the method of this embodiment also supports the transmission beam corresponding to the downlink signal and / or channel through PUCCH format#2 information on different resources, such as the corresponding one or more SSB indices.

[0337] When the terminal is in the IDLE / INACTIVE state, the configuration information is not released, and the terminal can still send PUCCH format #2 on the corresponding time-frequency resources according to the configuration information to request the base station to send the corresponding downlink signal or channel.

[0338] Furthermore, after the terminal sends the WUS signal, the terminal detects and receives the corresponding downlink channel and / or signal at the time domain resource location of the first downlink channel and / or signal transmission requested after T. The T is determined according to the terminal capability or by configuration information sent by the base station.

[0339] Furthermore, after the terminal fails to detect and receive the corresponding downlink channel and / or signal in the N requested downlink channel and / or signal transmission time domain resource locations after T, the terminal may continue to send a WUS signal request. The N is determined according to the terminal capability, or is determined in a predefined manner, or is determined through configuration information sent by the base station.

[0340] After detecting and receiving the WUS signal sent by the terminal, the base station sends the downlink signal or channel requested by the terminal.

[0341] Based on this, the following figure is a schematic diagram of requesting the base station to send SSB through the WUS signal carried by PUCCH format #2. Of course, the downlink channel can be any one or any combination of the aforementioned channels or signals, and this disclosure does not impose any restrictions. In addition, taking SSB as an example, during the SSB OFF period, the base station may selectively send other signals or signals, and this disclosure does not impose any restrictions. In the following example, it is assumed that the terminal can request the base station to send SSB through five different PUCCH resources. Assume that the transmission pattern of SSB at this time is case A, and it is below 3GHz, so there are 4 SSBs in the system. In this example, it is assumed that the correspondence between the PUCCH format #2 information sent by the terminal and the SSB is as follows, and the correspondence is determined by any of the aforementioned methods:

[0342] PUCCH format#2 information on Resource#1 corresponds to SSB#0

[0343] PUCCH format#2 information on Resource#2 corresponds to SSB#1

[0344] The PUCCH format#2 information on Resource#3 corresponds to SSB#2

[0345] PUCCH format#2 information on Resource#4 corresponds to SSB#3

[0346] The PUCCH format#2 information on Resource#5 corresponds to SSB#0, SSB#1, SSB#2 and SSB#3

[0347] To fully illustrate the solution of this embodiment, it is assumed that the terminal sends different PUCCH format #2 information at five different WUS transmission locations. As can be seen from the figure, when the base station does not receive any WUS signal sent by any terminal, the base station does not need to send SSB. When the base station receives PUCCH format #2 information sent by the terminal on resource #1, it sends SSB #0; when the base station receives PUCCH format #2 information sent by the terminal on resource #2, it sends SSB #1; when the base station receives PUCCH format #2 information sent by the terminal on resource #3, it sends SSB #2; when the base station receives PUCCH format #2 information sent by the terminal on resource #4, it sends SSB #3; when the base station receives PUCCH format #2 information sent by the terminal on resource #5, it sends SSB #0, SSB #1, SSB #2, and SSB #3.

[0348] Of course, as mentioned above, the method disclosed in the present invention is not limited to SSB, nor is it limited to the correspondence between the WUS signal and the downlink signal.

[0349] Of course, as mentioned above, the method described in the present disclosure is not limited to SSB, nor is it limited to the correspondence between WUS signals and downlink signals. For example, in this example, it is assumed that the correspondence between different resources corresponding to the terminal sending PUCCH format #2 information and SIB1 is as follows, and the correspondence is determined by any of the above methods:

[0350] The PUCCH format #2 information on Resource #1 corresponds to SIB1 sent by beam #1;

[0351] The PUCCH format#2 information on Resource#2 corresponds to the SIB1 sent by beam#2;

[0352] The PUCCH format #2 information on Resource #3 corresponds to the SIB1 sent by beam #3;

[0353] The PUCCH format #2 information on Resource #4 corresponds to the SIB1 sent by beam #4

[0354] The PUCCH format #2 information on Resource #5 corresponds to the SIB1 sent by the full beam

[0355] As a more flexible indication method, the method of this embodiment also supports different PUCCH format #2 information on different resources corresponding to the transmission beam of the downlink signal and / or channel, such as the corresponding one or more SSB indices.

[0356] When the terminal is in the IDLE / INACTIVE state, the configuration information is not released, and the terminal can still send PUCCH format #2 on the corresponding time-frequency resources according to the configuration information to request the base station to send the corresponding downlink signal or channel.

[0357] Furthermore, after the terminal sends the WUS signal, the terminal detects and receives the corresponding downlink channel and / or signal at the time domain resource location of the first downlink channel and / or signal transmission requested after T. The T is determined according to the terminal capability or by configuration information sent by the base station.

[0358] After detecting and receiving the WUS signal sent by the terminal, the base station sends the downlink signal or channel requested by the terminal.

[0359] Based on this, the following figure is a schematic diagram of requesting the base station to send SSB through the WUS signal carried by PUCCH format #2. Of course, the downlink channel can be any one or any combination of the aforementioned channels or signals, and this disclosure does not impose any restrictions. In addition, taking SSB as an example, during the SSB OFF period, the base station may selectively send other signals or signals, and this disclosure does not impose any restrictions. In the following example, it is assumed that the terminal can request the base station to send SSB through five different PUCCH resources and PUCCH format #2 information combinations. Assume that the SSB transmission pattern is case A at this time, and it is below 3GHz, so there are 4 SSBs in the system. In this example, it is assumed that the correspondence between the PUCCH format #2 information sent by the terminal and the SSB is as follows, and the correspondence is determined by any of the aforementioned methods:

[0360] PUCCH format #2 information '00' on Resource #1 corresponds to SSB #0;

[0361] PUCCH format #2 information '01' on Resource #1 corresponds to SSB #1;

[0362] PUCCH format#2 information '00' on Resource#2 corresponds to SSB#2;

[0363] PUCCH format #2 information '01' on Resource #2 corresponds to SSB #3;

[0364] The PUCCH format#2 information on Resource#3 corresponds to SSB#0, SSB#1, SSB#2, and SSB#3

[0365] For example, in this example, it is assumed that the correspondence between the terminal sending five different PUCCH resources, PUCCH format #2 information combinations, and SIB1 is as follows, and the correspondence is determined by any of the aforementioned methods:

[0366] The PUCCH format #2 information '00' on Resource #1 corresponds to SIB1 transmitted by beam #1;

[0367] The PUCCH format #2 information '01' on Resource #1 corresponds to SIB1 transmitted in beam #2;

[0368] The PUCCH format #2 information '00' on Resource #2 corresponds to the SIB1 transmitted by beam #3;

[0369] The PUCCH format #2 information '01' on Resource #2 corresponds to SIB1 transmitted by beam #4;

[0370] PUCCH format#2 information on Resource#3 corresponds to SSB#0, SSB#1, SSB#2, and SSB#3.

[0371] Embodiment 4: In this embodiment, the method in which the terminal sends a WUS signal and the base station receives the WUS signal and determines to send a downlink signal or signals may be any method in Embodiment 1 to Embodiment 3.

[0372] In this embodiment, the above method is combined with cell-specific DTX / DRX. That is, when cell-specific DTX / DRX is configured and activated on the network side, regardless of whether the WUS resource configured by the base station or pre-defined by the protocol is in the active duration, the terminal can send a WUS signal on the corresponding resource according to its needs to request the base station to send the corresponding downlink signal or channel.

[0373] Example 5: Like any method in Example 1 to Example 4, the embodiments of the present disclosure can be applied to UEs in any state, such as CONNECTED UE, IDLE UE, and INACTIVE UE.

[0374] When the WUS-related configuration is determined through RRC signaling, when the terminal enters the IDLE state or INACTIVE state, the relevant configuration is retained, and the terminal can still send WUS signals according to the configuration. Correspondingly, the base station needs to detect and receive the WUS signal at the corresponding resource location according to the configuration and perform the corresponding action.

[0375] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codeword", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0376] In some embodiments, the terms "codebook," "codeword," and "precoding matrix" may be used interchangeably. For example, a codebook may be a collection of one or more codewords / precoding matrices.

[0377] In some embodiments, terms such as "uplink", "uplink", "physical uplink" can be interchangeable with each other, and terms such as "downlink", "downlink", "physical downlink" can be interchangeable with each other, and terms such as "side", "sidelink", "side communication", "sidelink communication", "direct connection", "direct link", "direct communication", "direct link communication" can be interchangeable with each other.

[0378] In some embodiments, the terms "downlink control information (DCI)", "downlink (DL) assignment", "DL DCI", "uplink (UL) grant", "UL DCI" and the like may be used interchangeably.

[0379] In some embodiments, terms such as "physical downlink shared channel (PDSCH)" and "DL data" can be used interchangeably, and terms such as "physical uplink shared channel (PUSCH)" and "UL data" can be used interchangeably.

[0380] In some embodiments, the terms "radio", "wireless", "radio access network (RAN)", "access network (AN)", "RAN-based" and the like may be used interchangeably.

[0381] In some embodiments, the terms "search space", "search space set", "search space configuration", "search space set configuration", "control resource set (CORESET)", "CORESET configuration" and the like may be used interchangeably.

[0382] In some embodiments, terms such as "synchronization signal (SS)", "synchronization signal block (SSB)", "reference signal (RS)", "pilot", and "pilot signal" can be used interchangeably.

[0383] In some embodiments, terms such as "moment", "time point", "time", and "time position" can be replaced with each other, and terms such as "duration", "period", "time window", "window", and "time" can be replaced with each other.

[0384] In some embodiments, the terms "component carrier (CC)", "cell", "frequency carrier", "carrier frequency" and the like can be used interchangeably.

[0385] In some embodiments, terms such as "resource block (RB)", "physical resource block (PRB)", "sub-carrier group (SCG)", "resource element group (REG)", "PRB pair", "RB pair", "resource element (RE)", and "sub-carrier" can be used interchangeably.

[0386] In some embodiments, terms such as wireless access scheme and waveform may be used interchangeably.

[0387] In some embodiments, the terms "precoding", "precoder", "weight", "precoding weight", "quasi-co-location (QCL)", "transmission configuration indication (TCI) state", "spatial relation", "spatial domain filter", "transmission power", "phase rotation", "antenna port", "antenna port group", "layer", "the number of layers", "rank", "resource", "resource set", "resource group", "beam", "beam width", "beam angular degree", "antenna", "antenna element", "panel" and the like can be used interchangeably.

[0388] In some embodiments, terms such as "frame", "radio frame", "subframe", "slot", "sub-slot", "mini-slot", "symbol", "symbol", and "transmission time interval (TTI)" can be used interchangeably.

[0389] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

[0390] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0391] In some embodiments, the terms "certain", "preset", "preset", "set", "indicate", "a certain", "arbitrary", "first" and the like can be used interchangeably, and "certain A", "preset A", "set A", "indicate A", ...

[0392] "A certain A", "any A", "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or instruction, etc., or as specific A, a certain A, any A, or the first A, etc., but not limited to this.

[0393] In some embodiments, the determination or judgment can be performed by a value represented by 1 bit (0 or 1), or by a true or false value (Boolean value) represented by true or false, or by comparison of numerical values ​​(for example, comparison with a predetermined value), but is not limited thereto.

[0394] In some embodiments, "not expecting to receive" can be interpreted as not receiving on time domain resources and / or frequency domain resources, or as not performing subsequent processing on the data after receiving it; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the recipient to respond to the content sent.

[0395] Corresponding to the aforementioned embodiments of the request sending method and the request receiving method, the present disclosure also provides embodiments of a request sending device and a request receiving device.

[0396] FIG5 is a schematic block diagram of a request sending device according to an embodiment of the present disclosure. As shown in FIG5 , the request sending device includes: a processing module 501 and a sending module 502 .

[0397] In some embodiments, the processing module is configured to determine a first resource for sending request information; the sending module is configured to send the request information to the network device based on the first resource, wherein the request information is used to request the network device to send the first information in an on-demand state.

[0398] In some embodiments, the request information is used to request the network device to send at least one first information in an on-demand state.

[0399] In some embodiments, the request information is associated with the at least one first information in the on-demand state and / or the beam where the at least one first information in the on-demand state is located; or, the first resource is associated with the at least one first information in the on-demand state and / or the beam where the at least one first information in the on-demand state is located; or, the value of the bit in the request information and the first resource are associated with the at least one first information in the on-demand state and / or the beam where the at least one first information in the on-demand state is located.

[0400] In some embodiments, determining the first resource for sending the request information includes one of the following: determining the first resource according to the configuration information in the cell-specific signaling; determining the first resource according to the configuration information in the terminal-exclusive signaling; determining the first resource according to the method agreed upon in the protocol.

[0401] In some embodiments, the first resource includes a physical uplink control channel (PUCCH) resource.

[0402] In some embodiments, the first resource overlaps with a legacy PUCCH resource used to send legacy information, and the request information or the legacy information is sent on the overlapping resource.

[0403] In some embodiments, the legacy PUCCH resource used to send legacy information includes the first resource, and the processing module is configured to do one of the following:

[0404] Determine the first resource in the traditional PUCCH resource according to the indication information sent by the network device;

[0405] The first resource is determined in the traditional PUCCH resources in a manner agreed upon in a protocol.

[0406] In some embodiments, the first beam containing the request information and the second beam containing the first information are quasi-co-located.

[0407] In some embodiments, the terminal enters a non-connected state and the first resource is not released.

[0408] In some embodiments, at least one of the network device and the terminal is in a discontinuous reception state or a discontinuous transmission state, and the terminal sends the request information to the network device according to the first resource during an inactive period of the discontinuous reception state or the discontinuous transmission state.

[0409] In some embodiments, the first information includes at least one of the following: a synchronization broadcast signal block; a system information block 1; a channel state information reference signal; a tracking reference signal; a physical downlink control channel; a physical downlink shared channel; or a newly defined reference signal.

[0410] FIG6 is a schematic block diagram of a request receiving device according to an embodiment of the present disclosure. As shown in FIG6 , the request receiving device includes: a receiving module 601 .

[0411] In some embodiments, the receiving module is configured to receive the request information sent by the terminal on a first resource used for the terminal to send request information, wherein the request information is used to request the network device to send first information in an on-demand state.

[0412] In some embodiments, the request information is used to request the network device to send at least one first information in an on-demand state.

[0413] In some embodiments, the request information is associated with the at least one first information in the on-demand state and / or the beam where the at least one first information in the on-demand state is located; or, the first resource is associated with the at least one first information in the on-demand state and / or the beam where the at least one first information in the on-demand state is located; or, the value of the bit in the request information and the first resource are associated with the at least one first information in the on-demand state and / or the beam where the at least one first information in the on-demand state is located.

[0414] In some embodiments, the first resource used to send the request information is determined based on one of the following: configuration information in cell-specific signaling; configuration information in terminal-specific signaling; or a method agreed upon in a protocol.

[0415] In some embodiments, the first resource includes a physical uplink control channel (PUCCH) resource.

[0416] In some embodiments, the first resource overlaps with a legacy PUCCH resource used to send legacy information, and the request information or the legacy information is sent on the overlapping resource.

[0417] In some embodiments, the legacy PUCCH resource used to send legacy information includes the first resource, and the first resource used for the terminal to send request information is determined based on at least one of the following:

[0418] The indication information of the network device indicates the first resource in the traditional PUCCH resource;

[0419] The first resource is determined in the traditional PUCCH resources in a manner agreed upon in a protocol.

[0420] In some embodiments, the first beam containing the request information and the second beam containing the first information are quasi-co-located.

[0421] In some embodiments, the terminal enters a non-connected state and the first resource is not released.

[0422] In some embodiments, at least one of the network device and the terminal is in a discontinuous reception state or a discontinuous transmission state, and the terminal sends the request information to the network device according to the first resource during an inactive period of the discontinuous reception state or the discontinuous transmission state.

[0423] In some embodiments, the first information includes at least one of the following: a synchronization broadcast signal block; a system information block 1; a channel state information reference signal; a tracking reference signal; a physical downlink control channel; a physical downlink shared channel; or a newly defined reference signal.

[0424] For the device embodiment, since it basically corresponds to the method embodiment, the relevant parts can be referred to the partial description of the method embodiment. The device embodiment described above is merely illustrative, wherein the modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network modules. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Those of ordinary skill in the art can understand and implement it without paying any creative work.

[0425] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0426] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0427] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0428] Figure 7A is a schematic diagram of the structure of a communication device 7100 proposed in an embodiment of the present disclosure. Communication device 7100 can be a network device (e.g., an access network device, a core network device, etc.), a terminal (e.g., a user equipment, etc.), a chip, a chip system, or a processor that supports a network device to implement any of the above methods, or a chip, a chip system, or a processor that supports a terminal to implement any of the above methods. Communication device 7100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0429] As shown in Figure 7A, the communication device 7100 includes one or more processors 7101. The processor 7101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process the communication protocol and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. Optionally, the communication device 7100 is used to perform any of the above methods. Optionally, one or more processors 7101 are used to call instructions to enable the communication device 7100 to perform any of the above methods.

[0430] In some embodiments, the communication device 7100 further includes one or more transceivers 7102. When the communication device 7100 includes one or more transceivers 7102, the transceiver 7102 performs at least one of the communication steps such as sending and / or receiving in the above method (for example, steps S201 and S202, but not limited thereto), and the processor 7101 performs at least one of the other steps (for example, steps S201 and S202, but not limited thereto). In an optional embodiment, the transceiver may include a receiver and / or a transmitter, and the receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface may be interchangeable, the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be interchangeable, and the terms receiver, receiving unit, receiver, and receiving circuit may be interchangeable.

[0431] In some embodiments, the communication device 7100 further includes one or more memories 7103 for storing data. Alternatively, all or part of the memories 7103 may be located outside the communication device 7100. In alternative embodiments, the communication device 7100 may include one or more interface circuits 7104. Optionally, the interface circuits 7104 are connected to the memory 7102 and may be configured to receive data from the memory 7102 or other devices, or to send data to the memory 7102 or other devices. For example, the interface circuits 7104 may read data stored in the memory 7102 and send the data to the processor 7101.

[0432] The communication device 7100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 7100 described in the present disclosure is not limited thereto, and the structure of the communication device 7100 may not be limited by FIG. 7A . The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0433] 7B is a schematic diagram of the structure of a chip 7200 proposed in an embodiment of the present disclosure. If the communication device 7100 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 7200 shown in FIG7B , but the present disclosure is not limited thereto.

[0434] The chip 7200 includes one or more processors 7201. The chip 7200 is configured to execute any of the above methods.

[0435] In some embodiments, chip 7200 further includes one or more interface circuits 7202. Alternatively, terms such as interface circuit, interface, and transceiver pins may be used interchangeably. In some embodiments, chip 7200 further includes one or more memories 7203 for storing data. Alternatively, all or part of memory 7203 may be located external to chip 7200. Optionally, interface circuit 7202 is connected to memory 7203 and may be used to receive data from memory 7203 or other devices, or may be used to send data to memory 7203 or other devices. For example, interface circuit 7202 may read data stored in memory 7203 and send the data to processor 7201.

[0436] In some embodiments, the interface circuit 7202 performs at least one of the communication steps (e.g., steps S201 and S202, but not limited thereto) of the aforementioned method. For example, the interface circuit 7202 performing the communication steps (e.g., steps S201 and S202) of the aforementioned method means that the interface circuit 7202 performs data exchange between the processor 7201, chip 7200, memory 7203, or a transceiver device. In some embodiments, the processor 7201 performs at least one of the other steps (e.g., steps S201 and S202, but not limited thereto).

[0437] The modules and / or devices described in various embodiments, such as virtual devices, physical devices, and chips, can be arbitrarily combined or separated according to circumstances. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0438] The present disclosure also proposes a storage medium having instructions stored thereon. When the instructions are executed on the communication device 7100, the communication device 7100 executes any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a temporary storage medium.

[0439] The present disclosure also provides a program product, which, when executed by the communication device 7100, enables the communication device 7100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0440] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

Claims

1. A request sending method, characterized in that, Executed by a terminal, the method includes: Determine a first resource for sending request information; Send the request information to a network device according to the first resource, where the request information is used to request the network device to send first information in an on-demand state.

2. The method according to claim 1, wherein The request information is used to request the network device to send at least one first information in an on-demand state.

3. The method according to claim 2, wherein, The request information is associated with the at least one first information in an on-demand state and / or the beam where the at least one first information in an on-demand state is located; Or, The first resource is associated with the at least one first information in an on-demand state and / or the beam where the at least one first information in an on-demand state is located; Or, The value of the bit in the request information and the first resource are associated with the at least one first information in an on-demand state and / or the beam where the at least one first information in an on-demand state is located.

4. The method according to any one of claims 1 to 3, characterized in that, The determining of the first resource for sending request information includes one of the following: Determine the first resource according to the configuration information in the cell-specific signaling; Determine the first resource according to the configuration information in the terminal-specific signaling; Determine the first resource according to the manner agreed upon by the protocol.

5. The method according to any one of claims 1 to 4, characterized in that, The first resource includes a Physical Uplink Control Channel (PUCCH) resource.

6. The method according to claim 5, characterized in that The first resource overlaps with a traditional PUCCH resource for sending traditional information, and the request information or the traditional information is sent on the overlapping resource.

7. The method according to claim 5, characterized in that, The traditional PUCCH resource for sending traditional information includes the first resource. The determining of the first resource for sending request information includes one of the following: Receive indication information sent by the network device, where the indication information is used to indicate the first resource in the traditional PUCCH resource; Determine the first resource in the traditional PUCCH resource according to the manner agreed upon by the protocol.

8. The method according to any one of claims 1 to 7, characterized in that, The first beam where the request information is located is quasi-co-located with the second beam where the first information is located.

9. The method according to any one of claims 1 to 8, characterized in that When the terminal enters the non-connected state, the first resource is not released.

10. The method according to any one of claims 1 to 9, characterized in that At least one of the network device and the terminal is in a discontinuous reception state or a discontinuous transmission state. The terminal sends the request information to the network device according to the first resource during the inactive period of the discontinuous reception state or the discontinuous transmission state.

11. The method according to any one of claims 1 to 10, characterized in that, The first information includes at least one of the following: Synchronization broadcast signal block; System Information Block 1; Channel State Information Reference Signal; Tracking Reference Signal; Physical Downlink Control Channel; Physical Downlink Shared Channel; Newly defined reference signal.

12. A request receiving method, characterized in that, Executed by a network device, the method includes: Receive the request information sent by the terminal on a first resource for the terminal to send request information, where The request information is used to request the network device to send first information in an on-demand state.

13. The method according to claim 12, wherein The request information is used to request the network device to send at least one first information in an on-demand state.

14. The method according to claim 13, wherein The request information is associated with the at least one first information in an on-demand state and / or the beam where the at least one first information in an on-demand state is located; Or, The first resource is associated with the at least one first piece of information in the on-demand state and / or the beam where the at least one first piece of information in the on-demand state is located; Alternatively, The value of the bit in the request information and the first resource are associated with the at least one first piece of information in the on-demand state and / or the beam where the at least one first piece of information in the on-demand state is located.

15. The method according to any one of claims 12 to 14, characterized in that, The first resource for sending the request information is determined based on one of the following: Configuration information in cell-specific signaling; Configuration information in UE-specific signaling; In a manner agreed upon by the protocol.

16. The method according to any one of claims 12 to 15, characterized in that, The first resource includes a Physical Uplink Control Channel (PUCCH) resource.

17. The method according to claim 16, wherein The first resource overlaps with a traditional PUCCH resource for sending traditional information, and the request information or the traditional information is sent on the overlapping resource.

18. The method according to claim 16, wherein The traditional PUCCH resource for sending traditional information includes the first resource, and the first resource for the UE to send the request information is determined based on at least one of the following: Indication information of the network device indicates the first resource in the traditional PUCCH resource; The first resource is determined in the traditional PUCCH resource in a manner agreed upon by the protocol.

19. The method according to any one of claims 12 to 18, characterized in that The first beam where the request information is located is quasi-co-located with the second beam where the first information is located.

20. The method according to any one of claims 12 to 19, characterized in that When the UE enters the disconnected state, the first resource is not released.

21. The method according to any one of claims 12 to 20, characterized in that At least one of the network device and the UE is in a discontinuous reception state or a discontinuous transmission state, and the UE sends the request information to the network device according to the first resource during the inactive period of the discontinuous reception state or the discontinuous transmission state.

22. The method according to any one of claims 12 to 21, characterized in that The first information includes at least one of the following: Synchronization broadcast signal block; System Information Block 1; Channel State Information Reference Signal; Tracking Reference Signal; Physical Downlink Control Channel; Physical Downlink Shared Channel; Newly defined reference signal.

23. A request sending device, characterized in that, The apparatus includes: A processing module, configured to determine a first resource for sending request information; A sending module, configured to send the request information to a network device according to the first resource, where the request information is used to request the network device to send the first information in the on-demand state.

24. A request receiving device, characterized in that, The apparatus includes: A receiving module, configured to receive the request information sent by the UE on the first resource for the UE to send the request information, where the request information is used to request the network device to send the first information in the on-demand state.

25. A request sending method, characterized in that, Includes: The UE sends request information to the network device on the first resource; The network device determines according to the request information that the UE requests the network device to send the first information in the on-demand state.

26. A terminal, characterized in that, Includes: One or more processors; Wherein, the UE is configured to execute the request sending method according to any one of claims 1 to 11.

27. A network device, characterized in that, Includes: One or more processors; Wherein, the network device is configured to execute the request receiving method according to any one of claims 12 to 22.

28. A communication system, characterized in that, It includes a terminal and a network device. Among them, the terminal is configured to implement the request sending method described in any one of claims 1 to 11, and the network device is configured to implement the request receiving method described in any one of claims 12 to 22.

29. A storage medium storing instructions, characterized in that, When the instruction runs on the communication device, it causes the communication device to execute the request sending method described in any one of claims 1 to 11, and / or the request receiving method described in any one of claims 12 to 22.

Images