WO2025199964A1 - Information sending method and apparatus, information receiving method and apparatus, terminal, network device, and storage medium - Google Patents

Abstract

The present disclosure relates to the technical field of communications, and in particular to an information sending method and apparatus, an information receiving method and apparatus, a terminal, a network device, and a storage medium. The information sending method comprises: sending first request information to a network device, wherein the first request information is used for requesting the network device to send first downlink information. According to the present disclosure, even if the network device stops sending the first downlink information, a terminal can also send the first request information to the network device to request the network device to send the first downlink information, thereby ensuring that the terminal can successfully receive the first downlink information.

Description

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

The present disclosure relates to the field of communication technology, and in particular to an information sending method, an information receiving method, an information sending device, an information receiving device, a terminal, a network device, a communication system, and a storage medium.

Background Art

During the communication process with the terminal, the network device can send downlink information to the terminal, but for some reasons, the network device will stop sending some downlink information to the terminal. In this case, the terminal will not be able to receive the downlink information, which will affect the communication of the terminal.

Summary of the Invention

The embodiments of the present disclosure provide information sending and receiving methods and devices, terminals, network devices, and storage media to solve technical problems in related technologies.

According to a first aspect of an embodiment of the present disclosure, a method for sending information is proposed, which is executed by a terminal. The method includes: sending first request information to a network device, wherein the first request information is used to request the network device to send first downlink information.

According to a second aspect of an embodiment of the present disclosure, an information receiving method is proposed, which is executed by a network device. The method includes: receiving first request information sent by a terminal, wherein the first request information is used to request the network device to send first downlink information.

According to a third aspect of an embodiment of the present disclosure, an information sending device is proposed, which includes: a sending module configured to send first request information to a network device, wherein the first request information is used to request the network device to send first downlink information.

According to a fourth aspect of an embodiment of the present disclosure, an information receiving device is proposed, which includes: a receiving module configured to receive first request information sent by a terminal, wherein the first request information is used to request the network device to send first downlink information.

According to a fifth 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 information sending method described in the first aspect.

According to a sixth 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 information receiving method described in the second aspect.

According to the seventh 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 information sending method described in the first aspect, and the network device is configured to implement the information receiving method described in the second aspect.

According to the eighth aspect of the embodiments of the present disclosure, the embodiments of the present disclosure propose a storage medium, which stores instructions. When the instructions are executed on a communication device, the communication device executes the information sending method described in the first aspect and/or the information receiving method described in the second aspect.

According to the ninth aspect of the embodiments of the present disclosure, the embodiments of the present disclosure propose a program product. When the above program product is executed by a communication device, the above communication device executes the information sending method described in the first aspect and/or the information receiving method described in the second aspect.

According to the tenth aspect of the embodiments of the present disclosure, the embodiments of the present disclosure propose a computer program, which, when running on a computer, enables the computer to execute the information sending method described in the first aspect and/or the information receiving method described in the second aspect.

According to an embodiment of the present disclosure, even if the network device stops sending the first downlink information, the terminal can still request the network device to send the first downlink information by sending the first request information to the network device, which is conducive to ensuring that the terminal can successfully receive the first downlink information.

BRIEF DESCRIPTION OF THE DRAWINGS

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.

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

FIG2 is an interactive schematic diagram showing a method for sending information according to an embodiment of the present disclosure.

FIG3 is a schematic flowchart showing a method for sending information according to an embodiment of the present disclosure.

FIG4 is a schematic flow chart showing a method for receiving information according to an embodiment of the present disclosure.

FIG5 is a schematic block diagram of an information sending device according to an embodiment of the present disclosure.

FIG6 is a schematic block diagram of an information receiving device according to an embodiment of the present disclosure.

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

FIG7B is a schematic diagram of the structure of the chip proposed in an embodiment of the present disclosure.

DETAILED DESCRIPTION

The embodiments of the present disclosure provide information sending and receiving methods and devices, terminals, network devices, and storage media.

In a first aspect, an embodiment of the present disclosure proposes an information sending method, which is executed by a terminal, and the method includes: sending first request information to a network device, wherein the first request information is used to request the network device to send first downlink information.

In the above embodiment, even if the network device stops sending the first downlink information, the terminal can still send the first request information to the network device to request the network device to send the first downlink information, which is conducive to ensuring that the terminal can successfully receive the first downlink information.

In combination with some embodiments of the first aspect, in some embodiments, the first request information includes a preamble; and/or the first request information is carried via a physical uplink shared channel (PUSCH).

In combination with some embodiments of the first aspect, in some embodiments, the preamble includes the preamble in Msg1; and/or the PUSCH includes a PUSCH used to send Msg3.

In combination with some embodiments of the first aspect, in some embodiments, the preamble is a preamble corresponding to a first preamble index, wherein the preamble corresponding to the first preamble index is used to request the network device to send the first downlink information.

In conjunction with some embodiments of the first aspect, in some embodiments, the first preamble index is determined based on one of the following methods:

At least one synchronization signal block (SSB) is associated with a random access opportunity (RO), the first preamble index is equal to the sum of a first preamble start index and a first value, wherein the first preamble index is used to request first downlink information on a beam corresponding to an SSB corresponding to the first value in the at least one SSB;

At least one SSB is associated with one RO, the first preamble index is equal to the sum of the first preamble start index and a first value, wherein the preamble of the first preamble index is used to request the first downlink information;

At least one SSB is associated with one RO, and the first preamble index is the same as the first preamble start index;

One SSB is associated with multiple ROs, and the first preamble index is the same as the first preamble start index.

In combination with some embodiments of the first aspect, in some embodiments, the first value is determined based on an indication of a network device, or the first value is determined based on a predefined method.

In combination with some embodiments of the first aspect, in some embodiments, the first preamble start index is determined based on a first signaling sent by the network device, or the first start preamble index is determined based on a predefined method.

In combination with some embodiments of the first aspect. In some embodiments, the first signaling is independent of the second signaling, wherein the second signaling is used to configure a second preamble starting index for the terminal, and the second preamble starting index is used to request the network device to send other downlink information; or, the predefined method includes determining the first preamble starting index based on the second preamble starting index.

In combination with some embodiments of the first aspect. In some embodiments, the method further includes: determining, based on first configuration information, a first resource for sending the first request information; wherein the first configuration information and the second configuration information are also used by the terminal to determine a second resource for sending a second request information, and the second request information is used to request the network device to send other downlink information.

In combination with some embodiments of the first aspect. In some embodiments, the method further includes: determining a first resource for sending the first request information based on first configuration information, wherein the first resource is used by the network device to determine that the first request information is used to request the network device to send the first downlink information; the first configuration information is independent of second configuration information, and the second configuration information is used by the terminal to determine a second resource for sending a second request information, and the second request information is used to request the network device to send other downlink information.

In combination with some embodiments of the first aspect, in some embodiments, the terminal receives the first configuration information in a second cell other than the first cell, and the terminal expects that the first resource configured by the first configuration information is the same as the resource used to send the first request information in the first cell.

In conjunction with some embodiments of the first aspect, in some embodiments, the first request information is included in: a traditional message carried by Msg3; or a newly defined message carried by Msg3.

In conjunction with some embodiments of the first aspect, in some embodiments, the traditional message carried by Msg3 includes at least one of the following:

Radio resource control setup request RRCSetupRequest message;

Radio resource control recovery request RRCResumeRequest message or RRCResumeRequest1 message;

Radio resource control reestablishment request RRCReestablishmentRequest message;

Media access control layer control unit MAC CE;

Radio resource control configuration completion RRCReconfigurationComplete message;

Radio resource control system information request RRCSystemInfoRequest message.

In combination with some embodiments of the first aspect, in some embodiments, the first request information includes a reserved bit in the message, wherein the value of the reserved bit is used to indicate at least one of the following:

The message is used to implement traditional functions;

The message is used to request the network device to send first downlink information;

The message is used to implement a traditional function and request the network device to send the first downlink information.

In conjunction with some embodiments of the first aspect, in some embodiments, the first request information is further used to indicate at least one of the following:

Requesting the network device to send first downlink information that is downlink information based on beam transmission;

Requesting the network device to send the first downlink information as broadcast downlink information;

Request the network device to send the beam corresponding to the first downlink information.

In combination with some embodiments of the first aspect, in some embodiments, the first downlink information includes at least one of the following: SIB1; SSB.

In a second aspect, an embodiment of the present disclosure proposes an information receiving method, which is executed by a network device, and the method includes: receiving first request information sent by a terminal, wherein the first request information is used to request the network device to send first downlink information.

In conjunction with some embodiments of the second aspect, in some embodiments, the first request information includes a preamble; and/or the first request information is carried via a physical uplink shared channel (PUSCH).

In conjunction with some embodiments of the second aspect, in some embodiments, the preamble includes the preamble in Msg1; and/or the PUSCH includes a PUSCH used to send Msg3.

In combination with some embodiments of the second aspect, in some embodiments, the preamble is a preamble corresponding to a first preamble index, wherein the preamble corresponding to the first preamble index is used to request the network device to send the first downlink information.

In conjunction with some embodiments of the second aspect, in some embodiments, the first preamble index is determined based on one of the following methods:

At least one synchronization signal block (SSB) is associated with a random access opportunity (RO), the first preamble index is equal to the sum of a first preamble start index and a first value, wherein the first preamble index is used to request first downlink information on a beam corresponding to an SSB corresponding to the first value in the at least one SSB;

At least one SSB is associated with one RO, the first preamble index is equal to the sum of the first preamble start index and a first value, wherein the preamble of the first preamble index is used to request the first downlink information;

At least one SSB is associated with one RO, and the first preamble index is the same as the first preamble start index;

One SSB is associated with multiple ROs, and the first preamble index is the same as the first preamble start index.

In combination with some embodiments of the second aspect, in some embodiments, the first value is indicated by the network device, or the first value is determined based on a predefined method.

In combination with some embodiments of the second aspect, in some embodiments, the first preamble starting index is indicated by the network device through a first signaling, or the first starting preamble index is determined based on a predefined method.

In combination with some embodiments of the second aspect. In some embodiments, the first signaling is independent of the second signaling, wherein the second signaling is used to configure a second preamble code starting index for the terminal, and the second preamble code starting index is used to request the network device to send other downlink information; or, the predefined method includes determining the first preamble code starting index based on the second preamble code starting index.

In combination with some embodiments of the second aspect. In some embodiments, the first configuration information is further used by the terminal to determine a first resource for sending the first request information; wherein the first configuration information and the second configuration information are further used by the terminal to determine a second resource for sending a second request information, and the second request information is used to request the network device to send other downlink information.

In combination with some embodiments of the second aspect. In some embodiments, the first configuration information is further used by the terminal to determine a first resource for sending the first request information, wherein the first resource is used by the network device to determine that the first request information is used to request the network device to send the first downlink information; the first configuration information is independent of the second configuration information, and the second configuration information is used by the terminal to determine a second resource for sending the second request information, and the second request information is used to request the network device to send other downlink information.

In combination with some embodiments of the second aspect, in some embodiments, the terminal receives the first configuration information in a second cell other than the first cell, and the terminal expects that the first resource configured by the first configuration information is the same as the resource used to send the first request information in the first cell.

In conjunction with some embodiments of the second aspect, in some embodiments, the first request information is included in: a traditional message carried by Msg3; or a newly defined message carried by Msg3.

In conjunction with some embodiments of the second aspect, in some embodiments, the traditional message carried by Msg3 includes at least one of the following:

Radio resource control setup request RRCSetupRequest message;

Radio resource control recovery request RRCResumeRequest message or RRCResumeRequest1 message;

Radio resource control reestablishment request RRCReestablishmentRequest message;

Media access control layer control unit MAC CE;

Radio resource control configuration completion RRCReconfigurationComplete message;

Radio resource control system information request RRCSystemInfoRequest message.

In combination with some embodiments of the second aspect, in some embodiments, the first request information includes a reserved bit in the message, wherein the value of the reserved bit is used to indicate at least one of the following:

The message is used to implement traditional functions;

The message is used to request the network device to send first downlink information;

The message is used to implement a traditional function and request the network device to send the first downlink information.

In conjunction with some embodiments of the second aspect, in some embodiments, the first request information is further used to indicate at least one of the following:

Requesting the network device to send first downlink information that is downlink information based on beam transmission;

Requesting the network device to send the first downlink information as broadcast downlink information;

Request the network device to send the beam corresponding to the first downlink information.

In combination with some embodiments of the second aspect, in some embodiments, the first downlink information includes at least one of the following: SIB1; SSB.

In a third aspect, an embodiment of the present disclosure provides an information sending device, the device comprising: a sending module, The system is configured to send first request information to the network device, wherein the first request information is used to request the network device to send first downlink information.

In a fourth aspect, an embodiment of the present disclosure proposes an information receiving device, which includes: a receiving module configured to receive first request information sent by a terminal, wherein the first request information is used to request the network device to send first downlink information.

In a fifth aspect, an embodiment of the present disclosure proposes a terminal, comprising: one or more processors; wherein the terminal is used to execute the information sending method described in any one of the first aspect and the optional embodiments of the first aspect.

In a sixth aspect, an embodiment of the present disclosure proposes a network device, comprising: one or more processors; wherein the network device is used to execute the information receiving method described in any one of the second aspect and the optional embodiments of the second aspect.

In the seventh aspect, an embodiment of the present disclosure proposes a communication system, including a terminal and a network device, wherein the terminal is configured to implement the information 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 information receiving method described in any one of the second aspect and the optional embodiments of the second aspect.

In the eighth aspect, an embodiment of the present disclosure proposes a storage medium, which stores instructions. When the instructions are executed on a communication device, the communication device executes the information sending method described in any one of the first aspect and the optional embodiments of the first aspect, and/or the information receiving method described in any one of the second aspect and the optional embodiments of the second aspect.

In the ninth 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 information sending method described in any one of the first aspect and the optional embodiments of the first aspect, and/or the information receiving method described in any one of the second aspect and the optional embodiments of the second aspect.

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

It is understandable that the above-mentioned information sending and receiving devices, communication equipment, 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.

The embodiments of the present disclosure provide information sending and receiving methods and devices, terminals, network devices and storage media. In some embodiments, terms such as information sending and receiving methods and information processing methods, communication methods, etc. can be replaced with each other, terms such as information sending and receiving devices and information processing devices, communication devices, etc. can be replaced with each other, and terms such as information processing systems and communication systems can be replaced with each other.

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.

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.

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.

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.

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.

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

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

In some embodiments, the description of "at least one of A and B", "A and/or B", "A in one case, B in another case", "in response to one case A, in response to another case B", etc. may include the following technical solutions according to the circumstances: 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); In some embodiments, A and B (both A and B are executed). When there are more branches such as A, B, C, the same is true as above.

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.

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.

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 request information" and "second information" can be the same or different information, and their content can be the same or different.

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.

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.

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.

In some embodiments, devices and the like may be interpreted as physical or virtual, and their names are not limited to the names described in the embodiments, such as “device”, “equipment”, “device”, “circuit”, “network element”, “node”, “function”, “unit”, “section”, “system”, Terms such as “network,” “chip,” “chip system,” “entity,” and “subject” are interchangeable.

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

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.

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.

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.

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.

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

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

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.

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

As shown in Figure 1, the 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.

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.

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 Node B (eNB), a next generation evolved Node B (ng-eNB), a next generation Node B (gNB), a node B (NB), a home node B (HNB), a home evolved node B (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.

In some embodiments, the core network device may be a device including one or more network elements, or may be a Multiple devices or device groups each include all or part of one or more of the above-mentioned network elements. The network elements can be virtual or physical. The core network, for example, includes at least one of the Evolved Packet Core (EPC), 5G Core Network (5GCN), and Next Generation Core (NGC).

In some embodiments, the technical solution of the present disclosure may be applicable 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 may become internal interfaces of Open RAN, and the processes and information interactions between these internal interfaces may be implemented through software or programs.

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

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.

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.

The embodiments of the present disclosure may 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).

In some embodiments, the network device may send first downlink information to the terminal during communication with the terminal.

For example, the first downlink information may include: system information block SIB1, synchronization advertising signal block (SS (Synchronization Signal) and PBCH (Physical downlink Broadcast Channel) Block, SSB), etc.

It should be noted that the first downlink information is not limited to the above-mentioned SSB and SIB1, but may also include other information, such as master information block (MIB), channel state information reference signal (CSI-RS), tracking reference signal (TRS), physical downlink control channel (PDCCH), physical downlink shared channel (PDSCH), and other newly defined signals, such as signals composed of primary synchronization signal and secondary synchronization signal, discovery reference signal (DRS), etc.

In some embodiments, for some reasons, the network device may stop sending the first downlink information to the terminal. For example, the network device may choose to stop sending the first downlink information based on the network load, the number of resident terminals, the service type, the service period, etc. For example, the network device is about to enter or has entered the Network Energy Saving (NES) mode for energy saving purposes, and the first downlink information may be adjusted to the on-demand mode. Since the network device stops sending the first downlink information, some first downlink information is necessary for the terminal, for example, the terminal needs to access the service cell based on the first downlink information. Therefore, it is necessary to provide a method for the terminal to obtain the first downlink information.

FIG2 is an interactive schematic diagram showing a method for sending information according to an embodiment of the present disclosure.

As shown in FIG2 , the information sending method may include the following steps:

In step S201, the terminal sends first request information to the network device.

In some embodiments, the first request information is used to request the network device to send first downlink information.

In some embodiments, the network device may receive first request information sent by the terminal.

In some embodiments, the first request information is used to request the network device to send the first downlink information.

In some embodiments, the terminal may send the first request information to the network device when it is determined that the first downlink information is in an on-demand state and/or the terminal needs to obtain the first downlink information.

For example, the terminal can determine that the first downlink information is in the on-demand state based on the indication information of the network device, or the terminal can determine that the first downlink information is in the on-demand state based on a predefined method. For example, when the terminal receives the first downlink information based on a predefined period (for example, 20ms), if the terminal does not receive the first downlink information for a first period of time, it can be determined that the first downlink information is in the on-demand state.

In step S202, the network may send first downlink information to the terminal according to the first request information.

According to an embodiment of the present disclosure, even if the network device stops sending the first downlink information, the terminal can still request the network device to send the first downlink information by sending the first request information to the network device, which is conducive to ensuring that the terminal can successfully receive the first downlink information.

In some embodiments, the request information may also be referred to as a wake-up signal (Wake Up Signal, WUS), which may request the network device to send the first request information.

In some embodiments, the first downlink information may include at least one of the following: SSB, SIB.

In some embodiments, an SSB occupies four consecutive orthogonal frequency division multiplexing (OFDM) symbols in the time domain, including a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a PBCH.

In some embodiments, the NR system supports five SSB time domain transmission scenarios (cases), namely case A (SCS = 15KHz, operating in frequency bands above 3GHz), case B (SCS = 30KHz, operating in frequency bands above 3GHz), case C (SCS = 30KHz, TDD and operating in frequency bands above 3GHz), case D (SCS = 120KHz, operating in FR2 frequency band), and case E (SCS = 240KHz, operating in FR2 frequency band). The time domain pattern of the case depends on factors such as the sub-carrier space (SCS) of the SSB, the operating frequency, the time division duplex (TDD) format, and the frequency division duplex (FDD) format. Different SSB cases correspond to the number of SSBs in an SSB burst and the time domain resource positions occupied in the burst. For example, the duration of the SSB burst is 5ms; for example, the transmission period of the SSB is 20ms. Furthermore, the network device can configure the SSB transmission period and time domain pattern through the relevant information carried in the system information block SIB1. The maximum transmission period of SSB is 160ms. For different cases, the SSB pattern can refer to the relevant Technologies, such as the protocol TS38.213 in 3GPP, are not described in detail in this disclosure.

In some embodiments, SIB1 can be scheduled through downlink control information (DCI), for example, through DCI format 1_0 transmitted in the type 0 common search space (Type0-CSS (Common Search Space)).

Among them, the DCI 1_0 related search space (e.g., Type-0 CSS) and time-frequency resource location can be indicated through MIB, or configured through SIB1 or RRC signaling, which is not limited in this disclosure.

The periodicity and time-frequency resource location of SIB1 depend on the indication information carried in the DCI format 1_0 that schedules its transmission. Network devices can periodically transmit SIB1 so that terminals in idle, inactive, and connected states can obtain system information in a timely manner. In addition to the resource overhead caused by the SIB1 transmission itself, the CORESET#0 or other CORESETs used for the PDCCH (which carries DCI format 1_0) that schedules SIB1 transmission also occupy considerable time domain resources. Therefore, when considering NES, network devices can transmit SIB1 on demand or extend the SIB1 transmission period.

It should be noted that, in addition to SSB and SIB1, the first downlink information may also include other downlink information, such as MIB, CSI-RS, TRS, PDCCH, PDSCH, and other newly defined signals (such as signals composed of PSS and SSS, DRS), etc.

In some embodiments, in order to send the first request information to the network device, the terminal may first determine the configuration information of the first request information (for example, the resources and period for sending the first request information may be configured), and then send the first request information according to the configuration information.

In some embodiments, the first request information includes a preamble; and/or the first request information is carried via a physical uplink shared channel PUSCH.

For example, the preamble may be the preamble in Msg1 of 4-step random access, or the preamble in MsgA of 2-step random access. For example, the PUSCH may be the PUSCH used to send the PUSCH in Msg3, or the PUSCH used to send the data in MsgA of 2-step random access.

It should be noted that, when the first request information includes a preamble, the terminal only needs to request the network device to send the first request information without having to perform random access. After sending Msg1 carrying the preamble, it can subsequently send Msg3, or it may not send Msg3. This is not limited in the present disclosure.

In some embodiments, the information sending method further includes: determining a first resource for sending the first request information according to the first configuration information; wherein the first configuration information can also be used by the terminal to determine a first resource for sending the second request information. The second resource, the second request information is used to request the network device to send other downlink information.

In some embodiments, in addition to the first downlink information in the embodiment of the present disclosure, other downlink information may also be in an on-demand state. For example, SIBs other than SIB1 may also be in an on-demand state. SIBs other than SIB1 may be called other system information (OSI).

In some embodiments, when the terminal needs to request the network device to send an OSI (e.g., when the OSI is in an on-demand state), the terminal may send a second request message to the network device for sending second configuration information of the second request message, such as a system information request configuration (SI-RequestConfig). For information about the information element (IE) in the SI-RequestConfig, reference may be made to related technologies and will not be elaborated in this disclosure.

In the case where the first configuration information is also used by the terminal to determine the second resource for sending the second request information, the first resource and the second resource of the terminal may be the same, so that the terminal uses the same resource to send the first request information and the second request information. Then, it will be difficult for the network device to distinguish whether the request information is the first request information or the second request information by the resource where the received request information is located.

Therefore, in this case, the embodiment of the present disclosure can distinguish whether the request information sent by the terminal is the first request information or the second request information through preamble codes with different indexes.

For example, the preamble is a preamble corresponding to a first preamble index, wherein the preamble corresponding to the first preamble index is used to request the network device to send first downlink information. That is, the preamble corresponding to the first preamble index can be specifically used as first request information to request the network device to send first downlink information (e.g., SIB1, SSB, etc.), and the preamble corresponding to the second preamble index can be specifically used as second request information to request the network device to send OSI.

In some embodiments, the first preamble index is determined based on one of the following:

Mode 1: Under the condition that at least one synchronization signal block (SSB) is associated with a random access opportunity (RO), the first preamble index is equal to the sum of the first preamble start index and the first value, where the first preamble index is used to request the first downlink information on the beam corresponding to the SSB corresponding to the first value in the at least one SSB;

Method 2: Under the condition that at least one SSB is associated with one RO, the first preamble code index is equal to the sum of the first preamble code start index and the first value, wherein the preamble code of the first preamble code index is used to request the first downlink information; the first downlink information can be transmitted based on beam or broadcast, and the present invention does not limit this.

Mode 3: Under the condition that at least one SSB is associated with one RO, the first preamble code index is the same as the first preamble code start index; in this case, the terminal does not need to request the beam-based first downlink information, but only needs to request the first downlink information, without distinguishing different beams based on different indexes.

Method 4: One SSB is associated with multiple ROs, and the first preamble index is the same as the first preamble start index. In this case, if the terminal requests beam-based first downlink information, the corresponding beams can be distinguished based on the RO. If beam-based first downlink information is not required, only the first downlink information needs to be requested, without distinguishing different beams based on different indices.

Among them, method 1 and method 4 can be applicable to the scenario where the terminal requests the network device to send the first downlink information based on beam transmission, and method 2, method 3 and method 4 can be applicable to the scenario where the terminal requests the network device to send the first downlink information of broadcast.

In some embodiments, in order to reduce the corresponding system energy overhead and improve NES gain, the terminal may request first downlink information based on beam transmission.

In some embodiments, when the first downlink information is cell-specific downlink information, the terminal may request the first downlink information to be transmitted based on broadcast.

For example, when an SSB is associated with multiple ROs, the network device can determine the associated SSB based on the RO where the preamble is transmitted. Therefore, the terminal can request the first downlink information on the beam corresponding to the SSB associated with the RO based on the preamble, for example, requesting the first downlink information based on the preamble with index i. The method for determining i can refer to the example below.

For example, under the condition that multiple SSBs are associated with one RO, the terminal can determine the first preamble code index corresponding to the preamble code used to request the first downlink information based on any of the above methods 1, 2, and 3.

In some embodiments, the terminal may request the network device to send the first downlink information based on beam transmission. For example, the first preamble start index is called preamblestartindex#i, the first value is b, and the SSB corresponding to b may be the bth SSB in at least one SSB. The first preamble index preambleIndex=i+b, that is, preambleIndex#(i+b), the preamble corresponding to preambleIndex#(i+b) can be used to request the first downlink information (e.g., SIB1, SSB, etc.) on the beam corresponding to the bth SSB.

For example, the beam corresponding to the bth SSB can be the beam for initiating random access by the terminal, or the beam with the best signal instruction, or any beam greater than or equal to the first power (for example, the Reference Signal Receiving Power (RSRP)), or any beam, and the present disclosure does not limit this.

In some embodiments, the terminal may request the network device to send the first downlink information based on broadcast transmission. The terminal may send the preamble corresponding to preambleIndex#(i+b) to the network device to request the network device to send the first downlink information. After receiving the preamble corresponding to preambleIndex#(i+b), the network device determines that the terminal requests to transmit the first downlink information.

For example, the beam corresponding to the bth SSB can be the beam that initiates random access by the terminal, or the beam with the best signal quality (for example, the beam with the highest Reference Signal Receiving Power (RSRP)), or any beam that is greater than or equal to the first power (for example, RSRP), or any beam. The present disclosure does not limit this.

In some embodiments, the terminal may request the network device to transmit first downlink information based on broadcast transmission. The terminal may send a preamble corresponding to preambleIndex#i to the network device to request the network device to transmit the first downlink information. After receiving the preamble corresponding to preambleIndex#i, the network device determines that the terminal requests transmission of the first downlink information.

In some embodiments, the terminal may indicate through explicit signaling whether the requested first downlink information is first downlink information transmitted based on beam.

In some embodiments, the network device may determine, based on a predefined method, whether the first downlink information requested by the terminal is first downlink information transmitted based on a beam. For example, if the terminal sends a preamble corresponding to preambleIndex#i, the network device determines that the terminal requests first downlink information transmitted based on broadcast; if the terminal sends a preamble corresponding to preambleIndex#(i+b), the network device determines that the terminal requests first downlink information transmitted based on a beam.

In some embodiments, the first preamble code index is determined based on the first signaling sent by the network device, or the first preamble code starting index is determined based on a predefined method.

In some embodiments, the first signaling is independent of the second signaling, wherein the second signaling is used to configure a second preamble start index for the terminal, and the second preamble start index is used to request the network device to send other downlink information, for example, the other downlink information may include OSI.

For example, the second preamble code starting index can be called preamblestartindex#j. If N SSBs are associated with one RO and N is greater than or equal to 1, for the above-mentioned OSI of the beam corresponding to the a-th SSB, the terminal can request OSI based on the preamble with index preamblestartindex#(j+a); if N SSBs are associated with one RO and N is less than 1, the terminal can request OSI based on the preamble with index equal to preamblestartindex#j.

Regarding preamblestartindex#j, the terminal may determine it based on the second signaling sent by the network device, for example, the second signaling includes ra-PreambleStartIndex signaling.

As for preamblestartindex#i, the terminal can determine it based on the first signaling sent by the network device. The first signaling is independent of the second signaling. For example, the first signaling can be a signaling dedicated to the first downlink information in the on-demand state. For example, the first downlink information includes SIB1, and the first signaling can be called ra-PreambleStartIndex-SIB1.

In some embodiments, preamblestartindex#i may be determined based on preamblestartindex#j. For example, the first preamble index is determined according to the second preamble start index.

For example, preamblestartindex#i=preamblestartindex#(j+Δ), where the first variable Δ can be indicated by the network device, or can be determined based on a predefined method. When Δ is determined based on a predefined method, for example, Δ can be equal to the number of SSBs in a single SSB burst, or Δ can be equal to the number of SSBs actually sent in a single SSB burst.

In the aforementioned embodiment, the terminal determines the first preamble code index in a manner that uses the same or similar logic as that used to determine the index of the preamble code used to request OSI, or determines the first preamble code index based on a related index of the preamble code used to request OSI (for example, the second preamble code starting index). Accordingly, it is convenient to expand the logic of requesting OSI to obtain the manner in which the first preamble code index is determined in the embodiment of the present disclosure.

In some embodiments, the terminal determines, based on the first configuration information, a first resource for sending the first request information, wherein the first resource is used by the network device to determine that the first request information is used to request the network device to send the first downlink information;

The first configuration information is independent of the second configuration information. The second configuration information is used by the terminal to determine a second resource for sending second request information. The second request information is used to request the network device to send other downlink information.

Based on the previous embodiment, when the first configuration information is also used by the terminal to determine the second resource for sending the second request information, the first resource and the second resource may be the same, so that the terminal uses the same resource to send the first request information and the second request information. In this case, the terminal can request the first downlink information (e.g., SIB1, SSB) and OSI based on different preambles.

In this embodiment, the first configuration information may be independent of the second configuration information, and the first configuration for sending the first request information determined by the terminal based on the first configuration information may be different from the second configuration for sending the second request information determined based on the second configuration information.

Taking the preamble including the preamble in Msg1 as an example, the difference between the first configuration and the second configuration may include at least one of the following: different random access occasion (RO) resources, different preambles. Among them, the different RO resources may include different frequency domain resources, different time domain resources, and different time-frequency domain resources. different.

For example, when the first RO resource and the second RO resource are the same, the terminal can use different preambles to distinguish whether to request the network device to send the first downlink information or the OSI. The specific implementation method can refer to the above embodiment and will not be repeated here.

For example, when the first RO resource and the second RO resource are different, the terminal can distinguish whether it is requesting the network device to send the first downlink information or the OSI by sending preambles on different RO resources (the preambles sent can be the same or different). The network device can then determine whether the terminal specifically requests the network device to send the first downlink information or the OSI based on the RO resource where the received preamble is located.

In some embodiments, the terminal receives the first configuration information in a second cell other than the first cell. In this case, the terminal may expect that the first resources (e.g., RO resources, preamble) configured by the first configuration information are the same as the resources (e.g., RO resources, preamble) used to send the first request information in the first cell. This helps avoid resource fragmentation.

For example, the cell where the terminal is located includes the cell #1 where the terminal resides, the SIB1 in cell #1 is in an on-demand state, and the SIB1 in cell #2 other than cell #1 (for example, a neighboring cell or non-neighboring cell of cell #1) is not in an on-demand state. In this case, the first configuration information can be carried in the SIB1 of cell #2, and the terminal can obtain the first configuration information by receiving the SIB1 of cell #2.

For example, the first configuration information configures a first RO resource for the terminal. The terminal may expect that the first RO resource is the same as the RO resource used to send the first request information in cell #1, so that the terminal may send the first request information to the network device in cell #1 based on the first RO resource configured by the first configuration information.

For example, the first configuration information configures a first preamble for the terminal. The terminal may expect that the first preamble is the same as the preamble used as the first request information in cell #1, so that the terminal may send the first preamble as the first request information to the network device in cell #1.

It should be noted that the RO resources, preamble, etc. configured by the first configuration information, in addition to being used to send the first request information in this embodiment, can also be used for other purposes, such as for initial access and for requesting OSI. The present disclosure does not limit this, and the RO resources, preamble, etc. configured by the first configuration information can also be the same as the RO resources, preamble, etc. for other purposes, so as to avoid resource fragmentation.

In some embodiments, when the first request information is carried by PUSCH, the first request information may specifically be: a traditional message carried by Msg3 (i.e., a traditional message carried by Msg3 sent on PUSCH), for example One or more bits in the traditional message are used as the first request information; or, the newly defined message carried by Msg3 (ie, the newly defined message carried by Msg3 sent on PUSCH), for example, one or more bits in the newly defined message are used as the first request information.

For example, the PUSCH may be included in Msg3 of a 4-step random access, or in MsgA of a 2-step random access. For example, carrying the first request information through Msg3 is beneficial to reducing the overhead and delay of the first request information.

In some embodiments, the traditional message carried by Msg3 includes at least one of the following:

Radio resource control setup request RRCSetupRequest message;

Radio resource control recovery request RRCResumeRequest message or RRCResumeRequest1 message;

Radio resource control reestablishment request RRCReestablishmentRequest message;

Media Access Control Element (MAC CE); for example, the MAC CE may be used to indicate the Cell-Radio Network Temporary Identifier (C-RNTI);

Radio resource control configuration completion RRCReconfigurationComplete message;

Radio resource control system information request RRCSystemInfoRequest message.

In some embodiments, the first request information includes a reserved bit in the message, wherein a value of the reserved bit is used to indicate at least one of the following:

Messages are used to implement traditional functions;

The message is used to request the network device to send first downlink information;

The message is used to implement traditional functions and request the network device to send the first downlink information

The following embodiments mainly illustrate the technical solution of the present disclosure with reference to the RRCSetupRequest message and the RRCSystemInfoRequest message.

In some embodiments, the traditional message carried by Msg3 includes an RRCSetupRequest message, and the reserved (spare) bit or the newly added information field in the RRCSetupRequest message can be used as the first request information to request the network device to send the first downlink information.

Take one of the reserved bits in the RRCSetupRequest message (the first bit, the last bit, or any bit) as the first request information as an example. For example, if the reserved bit indication value is 1, it means that the first request information is used to request the network device to send the first downlink information. For example, if the reserved bit indication value is 0, it means that the first request information is used to request the network device to send the first downlink information. The information is not used to request the network device to send the first downlink information.

After the network device receives the RRCSetupRequest message, if the first request information indication value is 1, the network device determines that the terminal requests the network device to send the first downlink information and requests to establish an RRC connection (the traditional function of the RRCSetupRequest message).

After the network device receives the RRCSetupRequest message, if the first request information indication value is 0, the network device determines that the terminal does not request the network device to send the first downlink information, but only requests to establish an RRC connection (the traditional function of the RRCSetupRequest message).

Exemplarily, when the RRCSetupRequest message requests the network device to send the first downlink information and requests to establish an RRC connection, after the network device receives the RRCSetupRequest information in Msg3, it can instruct the terminal to respond to the first request information based on Msg4, and after sending Msg4 to the terminal, send the first downlink information requested by the terminal (such as SIB1, SSB), and perform the subsequent RRC connection establishment process.

When the RRCSetupRequest message requests the network device to send the first downlink information and requests to establish an RRC connection, if the terminal determines that the network device responds to the first request information based on the successful reception of Msg4, the terminal can try to receive the requested first downlink information (such as SIB1, SSB) after receiving Msg4, and perform the subsequent RRC connection establishment process.

For example, the process may include the following steps:

Once Msg3 is transmitted, the MAC entity shall:

1>monitor the PDCCH while the ra-ContentionResolutionTimer is running regardless of the possible occurrence of a measurement gap (monitor the PDCCH while the ra-ContentionResolutionTimer is running regardless of the possible occurrence of a measurement gap);

1>if notification of a reception of a PDCCH transmission of the SpCell is received from lower layers (if a reception notification of a PDCCH transmission of the SpCell (e.g., primary cell, primary and secondary cell) is received from lower layers):

2>if the CCCH SDU was included in Msg3 and the PDCCH transmission is addressed to its TEMPORARY_C-RNTI:

3>if the MAC PDU is successfully decoded (if the MAC protocol data unit (PDU) is successfully decoded):

4>stop ra-ContentionResolutionTimer (stop timer ra-ContentionResolutionTimer);

4>if the MAC PDU contains a UE Contention Resolution Identity MAC CE (if the MAC PDU contains a UE Contention Resolution Identity MAC CE); and

4>if the UE Contention Resolution Identity in the MAC CE matches the CCCH SDU transmitted in Msg3:

5>consider this contention resolution successful and finish the disassembly and demultiplexing of the MAC PDU;

5>if this Random Access procedure was initiated for SI request (If this Random Access procedure was initiated for SI request):

6>indicate the reception of an acknowledgment for SI request to upper layers (indicates the receipt of an acknowledgment for SI request to upper layers).

5>if this Random Access procedure was initiated both for SI request and RRC setup request (if this Random Access procedure was initiated for SI (e.g. SIB1) request and RRC setup request):

6>indicate the reception of an acknowledgment for SI request to upper layers:

6>set the C-RNTI to the value of the TEMPORARY_C-RNTI (set the C-RNTI to the value of TEMPORARY_C-RNTI);

5>else (otherwise):

6>set the C-RNTI to the value of the TEMPORARY_C-RNTI (set the C-RNTI to the value of TEMPORARY_C-RNTI);

5>discard the TEMPORARY_C-RNTI(discard temporary_C-RNTI);

5>consider this Random Access procedure successfully completed.

In some embodiments, the legacy message carried by Msg3 includes an RRCSystemInfoRequest message. The reserved (spare) bit or the newly added information field in the RRCSystemInfoRequest message can be used as the first request information to request the network device to send the first downlink information.

Taking one of the reserved bits in the RRCSystemInfoRequest message (the first bit, the last bit, or any bit) as the first request information as an example, for example, the reserved bit indication value is 1, indicating that the first request information is used to request the network device to send the first downlink information. For example, the reserved bit indication value is 1, indicating that the first request information is not used to request the network device to send the first downlink information.

After the network device receives the RRCSystemInfoRequest message, if the first request information indication value is 1, the network device determines that the terminal requests the network device to send the first downlink information, and requests the network device to send OSI (the traditional function of the RRCSystemInfoRequest message).

After the network device receives the RRCSystemInfoRequest message, if the first request information indication value is 0, the network device determines that the terminal does not request the network device to send the first downlink information, and only requests the network device to send OSI (the traditional function of the RRCSystemInfoRequest message).

In some embodiments, a requestable system information list (SI list), such as a schedulingInfoList, may be introduced in the PUSCH. The first request information may include a list of requested system information (such as a requested-SI-List), indicating at least one first downlink information requested by the terminal.

For example, if a terminal needs to request a network device to send SIB1, the requested-SI-List of the RRCSystemInfoRequest can carry the SIB1 identifier. Based on this, after receiving the PUSCH, the network device can determine that the requested-SI-List sent by the terminal is for requesting SIB1 in the schedulingInfoList. This embodiment can be applied to both traditional messages included in the PUSCH and newly defined messages included in the PUSCH.

In some embodiments, taking the PUSCH including the PUSCH for sending Msg3 as an example, the terminal may request the network device to send the first downlink information based on the message carried by the traditional Msg3 in the PUSCH as the first request information.

For example, a new message can be defined in a traditional Msg3. After receiving the Msg3, the network device can determine whether the Msg3 carries the newly defined information to distinguish whether the Msg3 sent by the terminal is used to request the network device to send the first downlink information. For example, if the Msg3 carries the newly defined information, the network device can determine that the Msg3 sent by the terminal is used to request the network device to send the first downlink information; if the Msg3 does not carry the newly defined information, the network device can determine that the Msg3 sent by the terminal is not used to request the network device to send the first downlink information, and is only used as the Msg3 in the random access process.

For example, there is no need to define a new message in the traditional Msg3, and the traditional Msg3 can be reused. The network device can configure specific configuration information (such as the first configuration information) for the terminal, or the protocol can agree on specific configuration information. The specific configuration information (such as the on-demand SIB1 specific configuration information) can be used by the terminal to determine the specific RO resource and/or the specific preamble. After receiving Msg3, the network device can distinguish whether the terminal requests the network device to send the first downlink information based on whether the RO resource sent by the terminal in Msg1 is a specific RO resource and/or whether the preamble in Msg1 is a specific preamble. If the RO resource sent by the terminal in Msg1 is a specific RO resource and/or the preamble in Msg1 is a specific preamble, it can be determined that the terminal requests the network device to send the first downlink information; if the RO resource sent by the terminal in Msg1 is not a specific RO resource and/or the preamble in Msg1 is not a specific preamble, it can be determined that the terminal does not request the network device to send the first downlink information.

In some embodiments, the newly defined message carried by Msg3 may be called, for example, RRCSIB1Request, and RRCSIB1Request may carry at least one of the following information:

A request for requesting a network device to send first downlink information;

Type of the requested first downlink information (e.g., beam-based first downlink information, e.g., broadcast first downlink information);

The beam corresponding to the first downlink information requested.

Exemplarily, the newly defined message in PUSCH can be carried based on an uplink logical channel (Uplink logical channel), for example, the logical channel includes a CCCH logical channel or a CCCH1 logical channel.

In some embodiments, the first request information is further used to indicate at least one of the following:

Requesting the network device to send first downlink information that is downlink information based on beam transmission;

Requesting the network device to send the first downlink information as broadcast downlink information;

Request the network device to send the beam corresponding to the first downlink information.

For example, the network device can determine, based on the first request information, whether the first downlink information requested by the terminal to be sent by the network device is downlink information based on beam transmission or broadcast downlink information. The network device can also determine the beam corresponding to the first downlink information requested by the terminal to be sent by the network device.

For example, the first request information is used to indicate that the first downlink information is SIB1 transmitted by beam, and the beam corresponding to the first downlink information is beam#1. Based on the first request information, SIB1 based on beam transmission can be sent in beam#1.

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

In some embodiments, steps S201 and S202 may be performed in an interchangeable order or simultaneously.

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

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

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

In a first aspect, embodiments of the present disclosure provide a method for sending information. Figure 3 is a schematic flow chart illustrating a method for sending information according to an embodiment of the present disclosure. The method for sending information illustrated in this embodiment can be executed by a terminal.

As shown in FIG3 , the information sending method may include the following steps:

In step S301, first request information is sent to a network device, wherein the first request information is used to request the network device to send first downlink information.

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.

In some embodiments, the first request information includes a preamble; and/or the first request information is carried via a physical uplink shared channel PUSCH.

In some embodiments, the preamble includes the preamble in Msg1; and/or the PUSCH includes a PUSCH used to send Msg3.

In some embodiments, the preamble code is a preamble code corresponding to a first preamble code index, wherein the preamble code corresponding to the first preamble code index is used to request the network device to send the first downlink information.

In some embodiments, the first preamble index is determined based on one of the following:

At least one synchronization signal block (SSB) is associated with a random access opportunity (RO), and a first preamble index is equal to the sum of a first preamble start index and a first value, wherein the first preamble index is used to request first downlink information on a beam corresponding to an SSB corresponding to the first value in the at least one SSB;

At least one SSB is associated with one RO, a first preamble index is equal to a sum of a first preamble start index and a first value, wherein a preamble of the first preamble index is used to request first downlink information;

At least one SSB is associated with one RO, and the first preamble index is the same as the first preamble start index;

One SSB is associated with multiple ROs, and the first preamble index is the same as the first preamble start index.

In some embodiments, the first value is determined based on an indication of the network device, or the first value is determined based on a predefined manner.

In some embodiments, the first preamble code starting index is determined based on the first signaling sent by the network device, or the first starting preamble code index is determined based on a predefined method.

In some embodiments, the first signaling is independent of the second signaling, wherein the second signaling is used to configure a second preamble code starting index for the terminal, and the second preamble code starting index is used to request the network device to send other downlink information; or, the predefined method includes determining the first preamble code starting index based on the second preamble code starting index.

In some embodiments, the method further includes: determining a first resource for sending a first request information based on the first configuration information; wherein the first configuration information is also used by the terminal to determine a second resource for sending a second request information, and the second request information is used to request the network device to send other downlink information.

In some embodiments, the method also includes: determining a first resource for sending a first request information based on the first configuration information, wherein the first resource is used by the network device to determine that the first request information is used to request the network device to send a first downlink information; the first configuration information is independent of the second configuration information, and the second configuration information is used by the terminal to determine a second resource for sending a second request information, and the second request information is used to request the network device to send other downlink information.

In some embodiments, the terminal receives the first configuration information in a second cell other than the first cell, and the terminal expects that the first resource configured by the first configuration information is the same as the resource used to send the first request information in the first cell.

In some embodiments, the first request information is included in: a traditional message carried by Msg3; or a newly defined message carried by Msg3.

In some embodiments, the traditional message carried by Msg3 includes at least one of the following:

Radio resource control setup request RRCSetupRequest message;

Radio resource control recovery request RRCResumeRequest message or RRCResumeRequest1 message;

Radio resource control reestablishment request RRCReestablishmentRequest message;

Media access control layer control unit MAC CE;

Radio resource control configuration completion RRCReconfigurationComplete message;

Radio resource control system information request RRCSystemInfoRequest message.

In some embodiments, the first request information includes a reserved bit in the message, wherein a value of the reserved bit is used to indicate at least one of the following:

Messages are used to implement traditional functions;

The message is used to request the network device to send first downlink information;

The message is used to implement traditional functions and request the network device to send first downlink information.

In some embodiments, the first request information is further used to indicate at least one of the following:

Requesting the network device to send first downlink information that is downlink information based on beam transmission;

Requesting the network device to send the first downlink information as broadcast downlink information;

Request the network device to send the beam corresponding to the first downlink information.

In some embodiments, the first downlink information includes at least one of the following: SIB1; SSB.

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.

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

As shown in FIG4 , the information receiving method may include the following steps:

In step S401, first request information sent by a terminal is received, wherein the first request information is used to request a network device to send first downlink information.

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.

In some embodiments, the first request information includes a preamble; and/or the first request information is carried via a physical uplink shared channel PUSCH.

In some embodiments, the preamble includes the preamble in Msg1; and/or the PUSCH includes a PUSCH used to send Msg3.

In some embodiments, the preamble is a preamble corresponding to a first preamble index, wherein the first preamble index The corresponding preamble code is used to request the network device to send the first downlink information.

In some embodiments, the first preamble index is determined based on one of the following:

At least one synchronization signal block (SSB) is associated with a random access opportunity (RO), and a first preamble index is equal to the sum of a first preamble start index and a first value, wherein the first preamble index is used to request first downlink information on a beam corresponding to an SSB corresponding to the first value in the at least one SSB;

At least one SSB is associated with one RO, a first preamble index is equal to a sum of a first preamble start index and a first value, wherein a preamble of the first preamble index is used to request first downlink information;

At least one SSB is associated with one RO, and the first preamble index is the same as the first preamble start index;

One SSB is associated with multiple ROs, and the first preamble index is the same as the first preamble start index.

In some embodiments, the first value is indicated by the network device, or the first value is determined based on a predefined method.

In some embodiments, the first preamble code starting index is indicated by the network device through a first signaling, or the first starting preamble code index is determined based on a predefined method.

In some embodiments, the first signaling is independent of the second signaling, wherein the second signaling is used to configure a second preamble code starting index for the terminal, and the second preamble code starting index is used to request the network device to send other downlink information; or, the predefined method includes determining the first preamble code starting index based on the second preamble code starting index.

In some embodiments, the first configuration information is also used by the terminal to determine a first resource for sending a first request information; wherein the first configuration information is also used by the terminal to determine a second resource for sending a second request information, and the second request information is used to request the network device to send other downlink information.

In some embodiments, the first configuration information is also used by the terminal to determine the first resource for sending the first request information, wherein the first resource is used by the network device to determine that the first request information is used to request the network device to send the first downlink information; the first configuration information is independent of the second configuration information, and the second configuration information is used by the terminal to determine the second resource for sending the second request information, and the second request information is used to request the network device to send other downlink information.

In some embodiments, the terminal receives the first configuration information in a second cell other than the first cell, and the terminal expects that the first resource configured by the first configuration information is the same as the resource used to send the first request information in the first cell.

In some embodiments, the first request information is included in:

Msg3 carries traditional messages;

Msg3 carries the newly defined message.

In some embodiments, the traditional message carried by Msg3 includes at least one of the following:

Radio resource control setup request RRCSetupRequest message;

Radio resource control recovery request RRCResumeRequest message or RRCResumeRequest1 message;

Radio resource control reestablishment request RRCReestablishmentRequest message;

Media access control layer control unit MAC CE;

Radio resource control configuration completion RRCReconfigurationComplete message;

Radio resource control system information request RRCSystemInfoRequest message.

In some embodiments, the first request information includes a reserved bit in the message, wherein a value of the reserved bit is used to indicate at least one of the following:

Messages are used to implement traditional functions;

The message is used to request the network device to send first downlink information;

The message is used to implement traditional functions and request the network device to send first downlink information.

In some embodiments, the first request information is further used to indicate at least one of the following:

Requesting the network device to send first downlink information that is downlink information based on beam transmission;

Requesting the network device to send the first downlink information as broadcast downlink information;

Request the network device to send the beam corresponding to the first downlink information.

In some embodiments, the first downlink information includes at least one of the following: SIB1; SSB.

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.

To reduce energy consumption in base stations and the network, the Network Energy Saving (NES) topic of Rel-18 has been researched in some implementations. During the research phase of Rel-18, NES technologies in the time, frequency, spatial, and power domains were thoroughly evaluated. During the standards phase, some technologies in the time, spatial, and power domains were standardized. Given the time constraints of Rel-18, some technologies will continue to be standardized in Rel-19.

In NR, the time domain position of SSB/SIB1 transmission opportunity is semi-statically configured, and the periodic transmission of common signals (SSB/SIB1/cell common PDCCH) will limit the base station to use (deeper) sleep mode to save energy. The technology achieves energy conservation by limiting the transmission/reception of public signals and increasing the sleep time of base stations. In the current protocol, SSB and SIB1 are periodically transmitted at a certain time-frequency resource location according to a period predefined by the protocol and/or configured by the network.

About SSB: An SSB occupies 4 consecutive OFDM symbols in the time domain, including PSS, SSS and PBCH. The NR system supports 5 SSB time domain transmission cases, namely case A-case E. The time domain pattern of the case depends on factors such as the SCS of the SSB, operating frequency, TDD/FDD standard, etc. Different SSB cases correspond to the number of SSBs in an SSB burst and the time domain resource position occupied in the burst. The duration of the SSB burst is 5ms. Typically, the transmission period of SSB is 20ms. Furthermore, the base station can configure the transmission period and time domain pattern of the SSB through the relevant information carried in SIB1. The maximum transmission period of SSB is 160ms.

About SIB1: SIB1 is scheduled through DCI format 1-0 transmitted in Type0-CSS. The SS related to Type-0 CSS and the corresponding time-frequency resource location can be indicated by MIB, or configured through SIB1 or RRC signaling. Its transmission period and time-frequency resource location depend on the SSB/SIB1 multiplexing pattern and the indication information carried in the DCI format 1-0 that schedules its transmission. The base station must send SIB1 periodically so that IDLE/INACTIVE UE and CONNECTED UE can obtain system information in a timely manner. In addition to the resource overhead caused by the SIB1 transmission itself, the CORESET#0 or other CORESET used for the PDCCH transmission that schedules the SIB1 transmission also occupies considerable time domain resources in the time domain.

On-demand SSB/SIB1 technology, a time-domain technology, is a key candidate for standardization research in Rel-19. In on-demand SSB/SIB1 technology, SSB/SIB1 is no longer sent periodically, but instead is sent based on UE demand.

The base station stops periodically sending SSB/SIB1 (is in the NES state), or uses a sparser time domain pattern to send SSB/SIB1.

When the UE has SSB/SIB1 requirements, it will send a wake-up signal (WUS) to the base station, which is the first request information in the previous embodiment.

After receiving the WUS signal, the base station sends SSB/SIB1 (enters the non-NES state), and according to the network service load, the number of resident terminals, the service type, the time period, etc., after sending one or more SSB bursts (SSB burst), it stops sending SSB/SIB1 (returns to the NES state).

Taking on-demand SIB1 as an example, in order to send the WUS signal that triggers SIB1 transmission, the terminal needs to obtain the corresponding WUS configuration. The WUS configuration contains the time-frequency domain information required by the terminal to send the WUS signal and the WUS signal related information. During the Rel-19 discussion, the terminal obtains the WUS configuration in the following ways:

The terminal obtains the WUS configuration of the current cell in other cells, which are cells that periodically transmit SIB1. The terminal obtains the WUS-related configuration based on system information or RRC signaling.

The terminal obtains the WUS configuration of the current cell. If the current cell is in the SIB1 on state, the terminal can obtain the WUS-related configuration based on system information or RRC signaling. If the current cell is in the SIB1 off state, the terminal can obtain the relevant WUS configuration based on pre-configuration.

The embodiments of the present invention are mainly based on the manner in which the terminal obtains relevant WUS configuration based on system information or indication signaling, and design a specific indication manner for the terminal to obtain the WUS configuration based on the indication signaling.

In related technologies, an on-demand SI mechanism for requesting SIBn (n>1) on demand is defined. The base station configures the time-frequency domain resources and request information for on-demand requests. Based on the configuration, the terminal sends the request information on the corresponding resources. The specific mechanism includes:

Application conditions: When si-BroadcastStatus is configured as notBroadcasting and SI-RequestConfig is configured, the demand Msg1 resources are determined based on SI-RequestConfig; otherwise, the request information is carried in Msg 3, and the request information is based on the following RRCSystemInfoRequest definition;

Motivation for introduction: The concept of beam is introduced in NR. To support full coverage of a cell, the base station needs to broadcast system messages in different slots for beams in different directions.

At high frequencies, the maximum number of beams is 64. Therefore, using a non-broadcast approach can save base station power consumption. On the other hand, if broadcasting is used, PDCCH resources must be reserved to schedule system messages; these resources cannot be used for scheduling other PDSCHs.

The request methods mainly include the following:

Msg 1based: The specified preamble index is allocated through SI-RequestConfig, and the UE sends the corresponding PRACH to request the base station to send system information. The base station responds to the UE by sending MSG2. As long as the RAPID in MSG2 is consistent with the preamble index sent by the UE, it is considered that the base station has received the UE's request.

Specific SI-RequestConfig configurations may include one or more of the following:

si-RequestPeriod (request period): with association period as the granularity. If the indication is M, the request period is equal to M association periods.

Association period: Starts at 0 and has a length of N times the PRACH configuration period, which is determined based on the prach-ConfigurationIndex in RACH-ConfigGeneric. N is the PRACH in 38.213/Table 8.1-1 that meets condition 1. The minimum value in the set corresponding to the configuration period.

Condition 1: During the association period, Each SSB in the SSBs is mapped to RO at least once

Get the number of SSBs according to the configuration in ssb-PositionsInBurst in SIB1or in ServingCellConfigCommon. Mapping each SSB in the SSBs to the RO once can be called a round-robin mapping.

si-RequestResources: Request resources, configure one or more request SI requestResource; the resource contains the following parameters:

ra-PreambleStartIndex (SI request information index): If N SSBs are associated with one RO (N>=1), for the i-th SSB, the terminal requests SI based on the preamble with index ra-PreambleStartIndex+i; if N<1, the terminal requests SI based on the preamble with index equal to ra-PreambleStartIndex;

ra-AssociationPeriodIndex: association period used for SI request within the request period;

ra-ssb-OccasionMaskIndex: related to RA resource selection;

About RO Resources:

ssb-perRACH-Occasion: The mapping between SSB and RO. The terminal selects the optimal SSB based on RSRP and sends the preamble on the RO corresponding to the optimal SSB. The base station determines the optimal downlink beam for the terminal based on the received RO.

RACH-ConfigGeneric: SI requests corresponding time-frequency domain resources and transmission power:

Mark: This IE is optional. If not configured, the terminal determines it based on the RACH-ConfigGeneric configuration parameter in the initial UL BWP. This means it shares the same configuration as random access.

Msg3 based: If SI-RequestConfig is not configured, the terminal transmits the RRCSystemInfoRequest message via Msg3 to trigger on-demand SI transmission. If the terminal successfully receives the Msg4 request message transmitted by the base station after transmitting the request message and successfully completes the random access response, the base station is considered to have responded to the user request. Otherwise, the base station is considered to have not responded to the user request.

The terminal transmits the above request information based on the UL-CCCH Message, and the UL-CCCH Message is carried based on Msg.3.

Exemplarily, the process of sending WUS (first request information) may be as follows:

The UE shall, while SDT procedure is not ongoing (When the Small Data Transmission (SDT) process is not in progress, the UE shall):

1>if the UE is not a RedCap UE and if SIB1 includes si-SchedulingInfo containing si-RequestConfig and criteria to select normal uplink;

2>trigger the lower layer to initiate the Random Access procedure on normal uplink using the PRACH preamble(s) and PRACH resource(s) in si-RequestConfig corresponding to the SI message(s) that the UE requires to operate within the cell, and for which si-BroadcastStatus is set to notBroadcasting;

2>if acknowledgement for SI request is received from lower layers (if acknowledgement for SI request is received from lower layers):

3>acquire the requested SI message(s) immediately (immediately obtain the requested SI message);

1>else (otherwise):

2>apply the default L1 parameter values as specified in the corresponding physical layer specifications except for the parameters for which values are provided in SIB1;

2>apply the default MAC Cell Group configuration (apply the default MAC cell group configuration);

2>apply the timeAlignmentTimerCommon included in SIB1 (apply the time in SIB1 to its timer common);

2>apply the CCCH configuration (apply CCCH configuration);

2>initiate transmission of the RRCSystemInfoRequest message with rrcSystemInfoRequest (initiate transmission of the RRCSystemInfoRequest message using RRCSystemInfoRequest);

2>if acknowledgement for RRCSystemInfoRequest message with rrcSystemInfoRequest is received from lower layers:

3>acquire the requested SI message(s) immediately.

The core idea of the embodiments of the present disclosure is as follows: a terminal supporting network skill technology obtains WUS configuration based on the corresponding solution of the patent of the present invention, and sends a WUS signal based on the WUS configuration to request corresponding SIB1 transmission; a base station supporting network energy-saving technology obtains WUS configuration based on the corresponding solution of this application, and monitors WUS signals on the time-frequency domain resources corresponding to the WUS configuration.

In the disclosed embodiment, the terminal sends a WUS to the base station, and requests the base station to send the downlink signal and/or signal using the indication information carried by the WUS. In this embodiment, the terminal carries the request information through WUS signaling. For example, the downlink signal/channel is SSB/SIB1.

The disclosed embodiments consider WUS configuration based on system information or signaling bearer conditions, and the corresponding WUS configuration methods. It is worth noting that the WUS configuration corresponding to an NES cell can be based on other cell bearers or the current NES cell bearer, and this invention does not impose any restrictions on this.

In the solution of the present invention, it is assumed that the 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, this patent 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.

Taking the example of a terminal requesting a downlink signal as SIB1, in this embodiment, the terminal determines WUS-related information through indication information, which includes the resources and/or WUS signals for transmitting the WUS. Based on this information, the terminal transmits the corresponding WUS signal on the corresponding time-frequency domain resources, requesting SIB1 transmission. Correspondingly, the base station indicates the WUS-related information based on the indication information and, based on this information, monitors the corresponding WUS signal on the corresponding time-frequency domain resources. If the base station successfully receives the corresponding WUS signal, the base station transmits the corresponding SIB1 information based on the request.

In the embodiment of the present disclosure, the terminal uses at least one of the following signals/information as a WUS requesting SIB1 transmission: Msg1, Msg3.

In this embodiment, the terminal uses at least one of the following signaling as the WUS for requesting SIB1 transmission: On-demand SI; On-demand SIB1 specific signaling; Msg.3 related configuration signaling.

Based on the above information, the present invention is described in detail in the following three examples.

Example 1:

The terminal uses Msg1 as a WUS request for SIB1, and the terminal determines the WUS configuration based on SI-RequestConfig carried by SIB1.

In the related art, the SI-RequestConfig is used to configure the relevant configuration of the on-demand SI request based on Msg1, and the SI corresponds to OSI, which is other SIB information except SIB1.

To better distinguish, the solution of the present invention will use on demand OSI to represent the traditional on demand SI request mechanism.

If the terminal still determines the WUS configuration for SIB1 requests based on SI-RequestConfig, the terminal must make SIB1 requests and on-demand SI (OSI) requests based on different preamble resources. Accordingly, the base station can differentiate between SIB1 requests and on-demand SI (OSI) requests based on different preamble resources. On-demand SI (OSI) requests can be determined based on traditional mechanisms. For NES terminals, illustratively, the terminal can determine the preamble resources for SIB1 requests based on at least one of the following methods.

The terminal determines the preamblestartindex j of the on demand OSI request based on traditional signaling. For example, the signaling is ra-PreambleStartIndex.

Example 1-1: A terminal determines a preamblestartindex i for an on-demand OSI request based on on-demand SIB1-specific signaling, where the signaling is independent of ra-PreambleStartIndex. Exemplarily, the signaling is ra-PreambleStartIndex-SIB1.

Example 1-2: A terminal determines a preamblestartindex i for an on-demand OSI request based on a predefined method, where illustratively, i = j + Δ. Δ is determined based on a predefined method or a signaling instruction. For example, if Δ is determined based on a predefined method, Δ may be equal to the number of SSBs included in an SSB burst, or may be equal to the number of SSBs actually transmitted in the SSB burst.

As a possible implementation, in order to reduce the corresponding system energy overhead and improve NES gain (disputed), the terminal can request beam-based SIB1 transmission.

Another possible implementation method is that, considering that SIB1 is cell-specific system information, the terminal can request broadcast transmission of SIB1.

Under the condition that one SSB is associated with multiple ROs, the base station can determine the associated SSB based on the RO where the preamble is transmitted. Therefore, the terminal can request the corresponding SIB1 based on Preamble i, where i is based on the above definition. I will not go into details here.

When multiple SSBs are associated with one RO, the terminal may determine the preamble for requesting SIB1 based on at least one of the following methods:

Example 1-3: If the terminal requests SIB1 based on beam transmission, the terminal can request SIB1 of the beam corresponding to the b-th SSB based on the preamble corresponding to preambleIndex=i+b; illustratively, the beam corresponding to the b SSBs can be the beam for initiating random access by the terminal, or the beam corresponding to the highest RSRP.

Example 1-4: If a terminal requests broadcast transmission of SIB1, the terminal may also request SIB1 based on the preamble corresponding to preambleIndex = i + b. After receiving the preamble corresponding to preambleIndex, the base station determines the SIB1 transmission request. For example, the beam corresponding to the b SSBs may be the beam on which the terminal initiates random access, or the beam corresponding to the highest RSRP. Alternatively, any beam may be used, and this is not limited in the present invention.

Embodiment 1-5: If the terminal requests broadcast transmission of SIB1, the terminal may request SIB1 based on the preamble corresponding to preambleIndex=i; after receiving the preamble corresponding to preambleIndex, the base station determines the request for SIB1 transmission.

Exemplarily, the terminal may determine whether to request SIB1 based on beam transmission based on display signaling;

Exemplarily, the base station may determine whether to request SIB1 based on beam transmission based on a predefined method; exemplarily, if the terminal sends a preamble corresponding to preambleIndex=i, the base station determines that the terminal requests SIB1 for broadcast transmission; if the terminal sends a preamble corresponding to preambleIndex=i+b, the base station determines that the terminal requests SIB1 for beam transmission;

Example 2:

The terminal requests the WUS of SIB1 based on Msg1, and the terminal determines the WUS configuration based on the configuration of SIB1 specific.

Exemplarily, the WUS configuration is independent of the on-demand OSI configuration. The RO resources corresponding to the WUS configuration and the on-demand OSI may be the same or different.

If the corresponding RO resources are the same, the terminal requests SIB1 or OSI based on different preambles. The specific mechanism is determined based on embodiment 1 and will not be described in detail in the present invention.

If the corresponding RO resources are different, the terminal can distinguish different RO/preamble resources for SIB1 request and on-demand SI (OSI) request based on different signaling configurations. Correspondingly, the base station can distinguish one of the SIB1 request and on-demand SI (OSI) request based on different RO/preamble resources.

Exemplarily, to avoid resource fragmentation, if the RO resources corresponding to the WUS are configured based on cells other than the current NES cell, the terminal expects that the RO/preamble resources corresponding to the WUS are the same as the RO/preamble resources configured in this cell.

Illustratively, the RO/preamble resources configured in this cell can be used for one or more of initial access, on-demand OSI, on-demand SIB1, and capability reporting, and the present invention does not impose any restrictions on this.

Example 3:

The terminal uses Msg.3 as the WUS to request SIB1. For example, if the WUS configuration corresponding to embodiment 1 and/or embodiment 2 is not configured, the terminal determines to request SIB1 information based on Msg.3;

Example 3-1:

In one possible implementation, to reduce WUS request overhead and request delay, the terminal can request the corresponding SIB1 by adding a corresponding SIB1 request to the traditional message carried by the traditional Msg3. Correspondingly, upon receiving the message and determining that the message carries the SIB1 request information, the base station can determine that a request for SIB1 from the terminal has been received. Exemplarily, the message includes one or more of the following:

RRCSetupRequest;

RRCResumeRequest or RRCResumeRequest1;

RRCReestablishmentRequest;

C-RNTI MAC CE;

RRCReconfigurationComplete;

RRCSystemInfoRequest.

Take RRCSetupRequest as an example:

If the terminal requests SIB1 transmission, it can request SIB1 based on the spare bit of RRCSetupRequest or the newly added information field.

Taking the spare bit as an example, if the bit indication is 1, it indicates a request for corresponding SIB1 transmission, and if it is 0, it indicates no request for corresponding SIB1 transmission.

After the base station receives the RRCSetupRequest information, if the corresponding spare bit is 1, the base station determines that the terminal requests SIB transmission and initiates an RRC connection establishment request.

After the base station receives the RRCSetupRequest information, if the corresponding spare bit is 0, the base station determines that the terminal only initiates an RRC connection establishment request.

Exemplarily, when the RRCSetupRequest message requests the network device to send the first downlink information and requests to establish an RRC connection, after the network device receives the RRCSetupRequest information in Msg3, it can instruct the terminal to respond to the first request information based on Msg4, and after sending Msg4 to the terminal, send the first downlink information requested by the terminal (such as SIB1, SSB), and perform the subsequent RRC connection establishment process.

In the case where the RRCSetupRequest message requests the network device to send the first downlink information and requests to establish an RRC connection, if the terminal determines that the network device responds to the first request information based on the successful reception of Msg4, the terminal can attempt to receive the requested first downlink information (such as SIB1, SSB) after receiving Msg4, and perform the subsequent RRC connection establishment process (the specific process can refer to the steps that the MAC entity should perform once Msg3 is sent in the previous embodiment).

Take RRCSystemInfoRequest as an example:

Sub-embodiment 1:

In one possible implementation, if the terminal requests SIB1 transmission, SIB1 may be requested based on the spare bit of RRCSystemInfoRequest or a newly added information field.

Taking the first bit of the spare field as an example, if the bit indication is 1, it indicates a request for corresponding SIB1 transmission, and if it is 0, it indicates no request for corresponding SIB1 transmission.

After the base station receives the RRCSystemInfoRequest information, if the corresponding spare bit is 1, the base station determines that the terminal requests SIB1 transmission and requests OSI.

After the base station receives the RRCSystemInfoRequest information, if the corresponding spare bit is 0, the base station determines that the terminal only requests the OSI.

Sub-embodiment 2:

In one possible implementation, if the terminal requests SIB1 transmission, SIB1 may be requested based on the requested-SI-List of RRCSystemInfoRequest.

One possible implementation method is to introduce a requestable SI list including SIB1 for users supporting NES, e.g., schedulingInfoList. The requested-SI-List indicates one or more SIs requested by the terminal.

For example, if the terminal wants to request SIB1 transmission, the request signal can be based on the requested-SI-List indication. SIB1.

The embodiment of the present invention takes RRCSetupRequest as an example to illustrate the solution of the present invention. It is worth noting that other messages follow similar mechanisms, which will not be described in detail in the present invention.

Example 3-2:

In a possible implementation, the terminal may request corresponding SIB1 transmission based on a message carried by a traditional Msg.3.

In Example 3-1, based on the traditional Msg.3Message, request information corresponding to SIB1 is added. The base station can distinguish whether the terminal initiates the SIB1 request information based on whether the Msg.3Message carries the SIB1 request information.

In another possible implementation, the base station can distinguish whether the terminal initiates SIB1 request information based on a specific preamble/RO. Example 3-2 configures SIB1 request specific RO time-frequency resources and/or preamble resources through signaling configuration or a predefined method. On the basis of the terminal sending a preamble based on the SIB1 request specific RO time-frequency resources and/or preamble resources, if the terminal sends information carried by a traditional Msg.3Message, the base station determines that the terminal sends SIB1 request information.

Unlike Example 3-1, Example 3-2 fully reuses the design of the traditional Msg.3 corresponding message. There is no need to carry additional SIB1 requests based on the Msg.3 corresponding message. The base station distinguishes whether the terminal initiates the SIB1 request information based on the preamble/RO. For example, the message includes one or more of the following:

RRCSetupRequest;

RRCResumeRequest or RRCResumeRequest1;

RRCReestablishmentRequest;

C-RNTI MAC CE;

RRCReconfigurationComplete;

RRCSystemInfoRequest.

Example 3-3:

One possible implementation method is to follow the traditional on-demand SI design process and improve the flexibility of WUS requests. The terminal sends the corresponding WUS request based on the newly defined signaling Message.

For example, the message is independent of the message corresponding to Example 1-1. The base station receives the newly defined message, confirm the terminal SIB1 transmission request.

For example, the IE corresponding to the newly defined message may be RRCSIB1Request. The IE includes one or more of the following information:

Beam-based SIB1 requests;

Request SIB1 to transmit the corresponding beam;

Broadcasting SIB1 request;

SIB1 transfer request.

Exemplarily, the message can be carried based on the uplink CCCH logical channel.

The embodiment of the present disclosure determines the signaling method of WUS configuration and the corresponding WUS signal transmission method, which is beneficial to improving WUS request performance while improving NES gain.

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.

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.

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.

In some embodiments, the terms "downlink control information (DCI)", "downlink (DL) assignment (assignment)", "DL DCI", "uplink (UL) grant (grant)", "UL DCI" and so on can be used interchangeably.

In some embodiments, a "physical downlink shared channel" The terms “PDSCH”, “DL data” and the like can be used interchangeably, and the terms “physical uplink shared channel (PUSCH)”, “UL data” and the like can be used interchangeably.

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

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 can be used interchangeably.

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

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.

In some embodiments, terms such as "component carrier (CC)", "cell", "frequency carrier", and "carrier frequency" can be used interchangeably.

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.

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

In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "a certain", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, a certain A, any A, or first A, etc., but not limited to this.

Corresponding to the aforementioned embodiments of the information sending method and the information receiving method, the present disclosure also provides embodiments of an information sending device and an information receiving device.

FIG5 is a schematic block diagram of an information sending device according to an embodiment of the present disclosure. In some embodiments, the information sending device may be provided in a terminal. As shown in FIG5 , the information sending device includes: a sending module 501 and a processing module 502.

In some embodiments, the sending module is configured to send first request information to the network device, wherein the first request information is used to request the network device to send first downlink information.

In some embodiments, the first request information includes a preamble; and/or the first request information is carried via a physical uplink shared channel PUSCH.

In some embodiments, the preamble includes the preamble in Msg1; and/or, the PUSCH includes a PUSCH used to send Msg3.

In some embodiments, the preamble code is a preamble code corresponding to a first preamble code index, wherein the preamble code corresponding to the first preamble code index is used to request the network device to send the first downlink information.

In some embodiments, the first preamble index is determined based on one of the following methods:

At least one synchronization signal block (SSB) is associated with a random access opportunity (RO), the first preamble index is equal to the sum of a first preamble start index and a first value, wherein the first preamble index is used to request first downlink information on a beam corresponding to an SSB corresponding to the first value in the at least one SSB;

At least one SSB is associated with one RO, the first preamble index is equal to the sum of the first preamble start index and a first value, wherein the preamble of the first preamble index is used to request the first downlink information;

At least one SSB is associated with one RO, and the first preamble index is the same as the first preamble start index;

One SSB is associated with multiple ROs, and the first preamble index is the same as the first preamble start index.

In some embodiments, the first value is determined based on a network device indication, or the first value is determined based on a predefined manner.

In some embodiments, the first preamble code starting index is determined based on the first signaling sent by the network device, or the first starting preamble code index is determined based on a predefined method.

In some embodiments, the first signaling is independent of the second signaling, wherein the second signaling is used to configure a second preamble code starting index for the terminal, and the second preamble code starting index is used to request the network device to send other downlink information; or, the predefined method includes determining the first preamble code starting index based on the second preamble code starting index.

In some embodiments, the device also includes: a processing module, configured to determine a first resource for sending the first request information based on first configuration information; wherein, the first configuration information is also used by the terminal to determine a second resource for sending a second request information, and the second request information is used to request the network device to send other downlink information.

In some embodiments, the processing module is configured to determine a first resource for sending the first request information based on first configuration information, wherein the first resource is used by the network device to determine that the first request information is used to request the network device to send the first downlink information; the first configuration information is independent of the second configuration information, and the second configuration information is used by the terminal to determine a second resource for sending the second request information, and the second request information is used to request the network device to send other downlink information.

In some embodiments, the terminal receives the first configuration information in a second cell other than the first cell, and the terminal expects that the first resource configured by the first configuration information is the same as the resource used to send the first request information in the first cell.

In some embodiments, the first request information is included in: a traditional message carried by Msg3; or a newly defined message carried by Msg3.

In some embodiments, the traditional message carried by Msg3 includes at least one of the following:

Radio resource control setup request RRCSetupRequest message;

Radio resource control recovery request RRCResumeRequest message or RRCResumeRequest1 message;

Radio resource control reestablishment request RRCReestablishmentRequest message;

Media access control layer control unit MAC CE;

Radio resource control configuration completion RRCReconfigurationComplete message;

Radio resource control system information request RRCSystemInfoRequest message.

In some embodiments, the first request information includes a reserved bit in the message, wherein a value of the reserved bit is used to indicate at least one of the following:

The message is used to implement traditional functions;

The message is used to request the network device to send first downlink information;

The message is used to implement a traditional function and request the network device to send the first downlink information.

In some embodiments, the first request information is further used to indicate at least one of the following:

Requesting the network device to send first downlink information that is downlink information based on beam transmission;

Requesting the network device to send the first downlink information as broadcast downlink information;

Request the network device to send the beam corresponding to the first downlink information.

In some embodiments, the first downlink information includes at least one of the following: SIB1; SSB.

FIG6 is a schematic block diagram of an information receiving device according to an embodiment of the present disclosure. In some embodiments, the information receiving device may be provided in a network device. As shown in FIG6 , the information receiving device includes: a receiving module 601.

In some embodiments, the receiving module is configured to receive first request information sent by a terminal, wherein the first request information is used to request the network device to send first downlink information.

In some embodiments, the first request information includes a preamble; and/or the first request information is carried via a physical uplink shared channel PUSCH.

In some embodiments, the preamble includes the preamble in Msg1; and/or, the PUSCH includes a PUSCH used to send Msg3.

In some embodiments, the preamble code is a preamble code corresponding to a first preamble code index, wherein the preamble code corresponding to the first preamble code index is used to request the network device to send the first downlink information.

In some embodiments, the first preamble index is determined based on one of the following methods:

At least one synchronization signal block (SSB) is associated with a random access opportunity (RO), the first preamble index is equal to the sum of a first preamble start index and a first value, wherein the first preamble index is used to request first downlink information on a beam corresponding to an SSB corresponding to the first value in the at least one SSB;

At least one SSB is associated with one RO, the first preamble index is equal to the sum of the first preamble start index and a first value, wherein the preamble of the first preamble index is used to request the first downlink information;

At least one SSB is associated with one RO, and the first preamble index is associated with the first preamble start index. Same as

One SSB is associated with multiple ROs, and the first preamble index is the same as the first preamble start index.

In some embodiments, the first value is indicated by the network device, or the first value is determined based on a predefined method.

In some embodiments, the first preamble code starting index is indicated by the network device through a first signaling, or the first starting preamble code index is determined based on a predefined method.

In some embodiments, the first signaling is independent of the second signaling, wherein the second signaling is used to configure a second preamble code starting index for the terminal, and the second preamble code starting index is used to request the network device to send other downlink information; or, the predefined method includes determining the first preamble code starting index based on the second preamble code starting index.

In some embodiments, the first configuration information is also used by the terminal to determine a first resource for sending the first request information; wherein, the first configuration information is also used by the terminal to determine a second resource for sending a second request information, and the second request information is used to request the network device to send other downlink information.

In some embodiments, the first configuration information is also used by the terminal to determine a first resource for sending the first request information, wherein the first resource is used by the network device to determine that the first request information is used to request the network device to send the first downlink information; the first configuration information is independent of the second configuration information, and the second configuration information is used by the terminal to determine a second resource for sending the second request information, and the second request information is used to request the network device to send other downlink information.

In some embodiments, the terminal receives the first configuration information in a second cell other than the first cell, and the terminal expects that the first resource configured by the first configuration information is the same as the resource used to send the first request information in the first cell.

In some embodiments, the first request information is included in: a traditional message carried by Msg3; or a newly defined message carried by Msg3.

In some embodiments, the traditional message carried by Msg3 includes at least one of the following:

Radio resource control setup request RRCSetupRequest message;

Radio resource control recovery request RRCResumeRequest message or RRCResumeRequest1 message;

Radio resource control reestablishment request RRCReestablishmentRequest message;

Media access control layer control unit MAC CE;

Radio resource control configuration completion RRCReconfigurationComplete message;

Radio resource control system information request RRCSystemInfoRequest message.

In some embodiments, the first request information includes a reserved bit in the message, wherein a value of the reserved bit is used to indicate at least one of the following:

The message is used to implement traditional functions;

The message is used to request the network device to send first downlink information;

The message is used to implement a traditional function and request the network device to send the first downlink information.

In some embodiments, the first request information is further used to indicate at least one of the following:

Requesting the network device to send first downlink information that is downlink information based on beam transmission;

Requesting the network device to send the first downlink information as broadcast downlink information;

Request the network device to send the beam corresponding to the first downlink information.

In some embodiments, the first downlink information includes at least one of the following: SIB1; SSB.

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.

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.

It should be understood that the division of the units or modules in the above device is only a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated. In addition, the units or modules in the device can 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 The memory stores instructions, and 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-mentioned 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 implemented 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), and the functions of some or all of the above units or modules are implemented by designing the logical relationship of the components within the circuit; for example, in another implementation, the above-mentioned hardware circuit can be implemented by a programmable logic device (PLD), taking a field programmable gate array (FPGA) as an example, which can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by a configuration file, thereby implementing the functions of some or all of the above units or modules. All units or modules of the above devices may be implemented entirely in the form of software called by a processor, or entirely in the form of hardware circuits, or partially in the form of software called by a processor and the rest in the form of hardware circuits.

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 a 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 to implement 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 ASIC, such as the Neural Network Processing Unit (NPU), the Tensor Processing Unit (TPU), the Deep Learning Processing Unit (DPU), etc.

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.

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.

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.

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.

The communication device 7100 described in the above embodiment 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.

FIG7B is a schematic diagram of the structure of a chip 7200 proposed in an embodiment of the present disclosure. In the case of a chip or a chip system, reference may be made to the structural diagram of a chip 7200 shown in FIG7B , but the present invention is not limited thereto.

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

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.

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).

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.

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.

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.

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 (39)

A method for sending information, characterized in that it is executed by a terminal, the method comprising: Sending first request information to the network device, wherein the first request information is used to request the network device to send first downlink information. The method according to claim 1 is characterized in that the first request information includes a preamble; and/or the first request information is carried by a physical uplink shared channel PUSCH. The method according to claim 2, characterized in that the preamble code includes the preamble code in Msg1; and/or the PUSCH includes a PUSCH used to send Msg3. The method according to claim 2 or 3 is characterized in that the preamble code is a preamble code corresponding to a first preamble code index, wherein the preamble code corresponding to the first preamble code index is used to request the network device to send the first downlink information. The method according to claim 4, wherein the first preamble index is determined based on one of the following methods: At least one synchronization signal block (SSB) is associated with a random access opportunity (RO), the first preamble index is equal to the sum of a first preamble start index and a first value, wherein the first preamble index is used to request first downlink information on a beam corresponding to an SSB corresponding to the first value in the at least one SSB; At least one SSB is associated with one RO, the first preamble index is equal to the sum of the first preamble start index and a first value, wherein the preamble of the first preamble index is used to request the first downlink information; At least one SSB is associated with one RO, and the first preamble index is the same as the first preamble start index; One SSB is associated with multiple ROs, and the first preamble index is the same as the first preamble start index. The method according to claim 5 is characterized in that the first value is determined based on an indication of a network device, or the first value is determined based on a predefined method. The method according to claim 5 is characterized in that the first preamble code starting index is determined based on the first signaling sent by the network device, or the first preamble code starting index is determined based on a predefined method. The method according to claim 7, wherein the first signaling is independent of the second signaling, wherein the second signaling is used to configure a second preamble start index for the terminal, and the second preamble start index is used to request the network device to send other downlink information; or The predefined manner includes determining the first preamble start index according to the second preamble start index. The method according to any one of claims 3 to 8, further comprising: Determine, according to the first configuration information, a first resource for sending the first request information; The first configuration information is further used by the terminal to determine a second resource for sending second request information, and the second request information is used to request the network device to send other downlink information. The method according to claim 2 or 3, characterized in that the method further comprises: Determining, according to the first configuration information, a first resource for sending the first request information, wherein the first resource is used by the network device to determine that the first request information is used to request the network device to send the first downlink information; The first configuration information is independent of the second configuration information. The second configuration information is used by the terminal to determine a second resource for sending second request information. The second request information is used to request the network device to send other downlink information. The method according to claim 9 or 10 is characterized in that the terminal receives the first configuration information in a second cell other than the first cell, and the terminal expects that the first resource configured by the first configuration information is the same as the resource used to send the first request information in the first cell. The method according to claim 3, wherein the first request information is included in: Msg3 carries the traditional message; or, Msg3 carries the newly defined message. The method according to claim 12, wherein the traditional message carried by Msg3 includes at least one of the following: Radio resource control setup request RRCSetupRequest message; Radio resource control recovery request RRCResumeRequest message or RRCResumeRequest1 message; Radio resource control reestablishment request RRCReestablishmentRequest message; Media access control layer control unit MAC CE; Radio resource control configuration completion RRCReconfigurationComplete message; Radio resource control system information request RRCSystemInfoRequest message. The method according to claim 13, wherein the first request information includes a reserved bit in the message, wherein a value of the reserved bit is used to indicate at least one of the following: The message is used to implement traditional functions; The message is used to request the network device to send first downlink information; The message is used to implement a traditional function and request the network device to send first downlink information. The method according to any one of claims 1 to 14, characterized in that the first request information further Used to indicate at least one of the following: Requesting the network device to send first downlink information that is downlink information based on beam transmission; Requesting the network device to send the first downlink information as broadcast downlink information; Request the network device to send the beam corresponding to the first downlink information. The method according to any one of claims 1 to 15, wherein the first downlink information includes at least one of the following: SIB1; SSB. An information receiving method, characterized in that it is executed by a network device, the method comprising: A first request message sent by a receiving terminal is received, wherein the first request message is used to request the network device to send first downlink information. The method according to claim 17 is characterized in that the first request information includes a preamble; and/or the first request information is carried by a physical uplink shared channel PUSCH. The method according to claim 18, characterized in that the preamble code includes the preamble code in Msg1; and/or the PUSCH includes a PUSCH used to send Msg3. The method according to claim 18 or 19 is characterized in that the preamble code is a preamble code corresponding to a first preamble code index, wherein the preamble code corresponding to the first preamble code index is used to request the network device to send the first downlink information. The method according to claim 20, wherein the first preamble index is determined based on one of the following methods: At least one synchronization signal block (SSB) is associated with a random access opportunity (RO), the first preamble index is equal to the sum of a first preamble start index and a first value, wherein the first preamble index is used to request first downlink information on a beam corresponding to an SSB corresponding to the first value in the at least one SSB; At least one SSB is associated with one RO, the first preamble index is equal to the sum of the first preamble start index and a first value, wherein the preamble of the first preamble index is used to request the first downlink information; At least one SSB is associated with one RO, and the first preamble index is the same as the first preamble start index; One SSB is associated with multiple ROs, and the first preamble index is the same as the first preamble start index. The method according to claim 21 is characterized in that the first value is indicated by the network device, or the first value is determined based on a predefined method. The method according to claim 21 is characterized in that the first preamble code starting index is indicated by the network device through a first signaling, or the first starting preamble code index is determined based on a predefined method. The method according to claim 23, wherein the first signaling is independent of the second signaling, wherein the second signaling is used to configure a second preamble start index for the terminal, and the second preamble start index is used to request the network device to send other downlink information; or The predefined manner includes determining the first preamble start index according to the second preamble start index. The method according to any one of claims 19 to 24, wherein the first configuration information is further used by the terminal to determine a first resource for sending the first request information; The first configuration information is further used by the terminal to determine a second resource for sending second request information, and the second request information is used to request the network device to send other downlink information. The method according to claim 18 or 19, characterized in that the first configuration information is further used by the terminal to determine a first resource for sending the first request information, wherein the first resource is used by the network device to determine that the first request information is used to request the network device to send the first downlink information; The first configuration information is independent of the second configuration information. The second configuration information is used by the terminal to determine a second resource for sending second request information. The second request information is used to request the network device to send other downlink information. The method according to claim 25 or 26 is characterized in that the terminal receives the first configuration information in a second cell other than the first cell, and the terminal expects that the first resource configured by the first configuration information is the same as the resource used to send the first request information in the first cell. The method according to claim 19, wherein the first request information is included in: Msg3 carries the traditional message; or, Msg3 carries the newly defined message. The method according to claim 28, wherein the traditional message carried by Msg3 includes at least one of the following: Radio resource control setup request RRCSetupRequest message; Radio resource control recovery request RRCResumeRequest message or RRCResumeRequest1 message; Radio resource control reestablishment request RRCReestablishmentRequest message; Media access control layer control unit MAC CE; Radio resource control configuration completion RRCReconfigurationComplete message; Radio resource control system information request RRCSystemInfoRequest message. The method according to claim 29, wherein the first request information includes a reserved bit in the message, wherein a value of the reserved bit is used to indicate at least one of the following: The message is used to implement traditional functions; The message is used to request the network device to send first downlink information; The message is used to implement a traditional function and request the network device to send the first downlink information. The method according to any one of claims 17 to 30, wherein the first request information is further used to indicate at least one of the following: Requesting the network device to send first downlink information that is downlink information based on beam transmission; Requesting the network device to send the first downlink information as broadcast downlink information; Request the network device to send the beam corresponding to the first downlink information. The method according to any one of claims 17 to 31, wherein the first downlink information includes at least one of the following: SIB1; SSB. An information sending device, characterized in that the device comprises: The sending module is configured to send first request information to the network device, wherein the first request information is used to request the network device to send first downlink information. An information receiving device, characterized in that the device comprises: The receiving module is configured to receive first request information sent by the terminal, wherein the first request information is used to request the network device to send first downlink information. A terminal, comprising: one or more processors; The terminal is configured to execute the information sending method according to any one of claims 1 to 16. A network device, comprising: one or more processors; Wherein, the network device is used to execute the information receiving method according to any one of claims 17 to 32. A communication system, characterized in that it includes a terminal and a network device, wherein the terminal is configured to implement the information sending method described in any one of claims 1 to 16, and the network device is configured to implement the information receiving method described in any one of claims 17 to 32. A storage medium storing instructions, wherein the instructions are stored in a communication device. When the communication device is operated, the communication device executes the information sending method according to any one of claims 1 to 16, and/or the information receiving method according to any one of claims 17 to 32. A program product, characterized in that when the program product is executed by a communication device, the communication device executes the information sending method according to any one of claims 1 to 16, and/or the information receiving method according to any one of claims 17 to 32.