Information processing method, terminal, network device, communication system, and storage medium

Abstract

Embodiments of the present disclosure provide an information processing method, a terminal, a network device, a communication system, and a storage medium. The information processing method is executed by a terminal and comprises: sending request information to a network device, wherein the request information is used for requesting the network device to send first downlink information and requesting events other than the sending of the first downlink information. In this way, other events can be requested while sending the request for the downlink information, thereby saving the signaling overhead, and saving power.

Description

Information processing method, terminal, network device, communication system and storage medium Technical Field

[0001] The present disclosure relates to the field of communication technologies, and in particular to an information processing method, a terminal, a network device, a communication system, and a storage medium. Background Art

[0002] In the field of communication technology, a terminal may request a downlink signal and / or downlink channel from a network device. If a downlink signal and / or downlink channel is requested during a random access process, this may increase the latency of the random access.

[0003] Summary of the Invention

[0004] The embodiments of the present disclosure need to solve the problem of delay caused by requesting downlink information in random access.

[0005] According to the first aspect of an embodiment of the present disclosure, an information processing method is proposed, which is executed by a terminal, including: sending request information to a network device, wherein the request information is used to request the network device to send first downlink information and other events except sending the first downlink information.

[0006] According to the second aspect of an embodiment of the present disclosure, an information processing method is proposed, which is executed by a network device, including: receiving request information sent by a terminal, wherein the request information is used to request the network device to send first downlink information and other events except sending the first downlink information.

[0007] According to the third aspect of an embodiment of the present disclosure, a terminal is proposed, comprising: a first transceiver module, configured to send request information to a network device, wherein the request information is used to request the network device to send first downlink information and other events except sending the first downlink information.

[0008] According to the fourth aspect of an embodiment of the present disclosure, a network device is proposed, comprising: a second transceiver module, configured to receive request information sent by a terminal, wherein the request information is used to request the network device to send first downlink information and other events except sending the first downlink information.

[0009] According to a fifth aspect of an embodiment of the present disclosure, a communication device is proposed, comprising one or more processors; wherein the above-mentioned communication device is used to execute optional implementation methods such as the first aspect, the second aspect, or the first and second aspects.

[0010] According to the sixth aspect of the embodiment of the present disclosure, a communication system is proposed, including: a terminal and a network device; wherein the above-mentioned terminal is configured to execute the method described in the optional implementation manner of the first aspect, and the above-mentioned network device is configured to execute the method described in the optional implementation manner of the second aspect.

[0011] According to the seventh aspect of an embodiment of the present disclosure, a storage medium is proposed, which stores instructions. When the instructions are executed on a communication device, the communication device executes the method described in the first aspect, the second aspect, or the optional implementation of the first and second aspects.

[0012] According to an eighth aspect of an embodiment of the present disclosure, a computer program product is proposed, which includes a computer program or instructions. When the computer program or instructions are executed by a processor, they implement the method described in the first aspect, the second aspect, or the optional implementation of the first and second aspects.

[0013] The embodiments of the present disclosure can reduce the random access delay and save energy when requesting downlink information during the random access process. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following drawings required for describing the embodiments are introduced. The following drawings are merely some embodiments of the present disclosure and do not impose specific limitations on the protection scope of the present disclosure.

[0015] FIG1A is a schematic structural diagram of an information processing system according to an embodiment of the present disclosure.

[0016] FIG1B is a schematic diagram showing on-demand SSB / SIB1 transmission according to an embodiment of the present disclosure.

[0017] FIG1C is a code diagram illustrating a Msg3 request corresponding mechanism according to an embodiment of the present disclosure.

[0018] FIG1D is a schematic diagram of a code of an RRC system message request IE according to an embodiment of the present disclosure.

[0019] FIG1E is a schematic diagram of a code of CCCH1 according to an embodiment of the present disclosure.

[0020] FIG1F is a schematic structural diagram of a MAC PDU according to an embodiment of the present disclosure.

[0021] FIG2 is an interactive schematic diagram illustrating an information processing method according to an embodiment of the present disclosure.

[0022] FIG3A is a flow chart illustrating an information processing method according to an embodiment of the present disclosure.

[0023] FIG3B is a flow chart illustrating an information processing method according to an embodiment of the present disclosure.

[0024] FIG4A is a flow chart illustrating an information processing method according to an embodiment of the present disclosure.

[0025] FIG4B is a flow chart illustrating an information processing method according to an embodiment of the present disclosure.

[0026] FIG5A is a schematic structural diagram of a terminal according to an embodiment of the present disclosure.

[0027] FIG5B is a schematic structural diagram of a network device according to an embodiment of the present disclosure.

[0028] FIG6A is a schematic structural diagram of a communication device provided according to an embodiment of the present disclosure.

[0029] FIG6B is a schematic structural diagram of a chip provided according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0030] The embodiments of the present disclosure provide an information processing method, a terminal, a network device, a communication system, and a storage medium.

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

[0032] In the above embodiment, other events can be requested simultaneously with downlink request information, thereby saving signaling overhead and achieving energy conservation. For example, if a terminal in an embodiment of the present disclosure sends a request message during random access, multiple events can be requested at the same time. This can reduce the latency of multiple event requests and random access latency, thus achieving energy conservation, and effectively reduce the complexity of terminal request operations, enabling the terminal to jointly request multiple events.

[0033] In combination with some embodiments of the first aspect, in some embodiments, the request information includes: first request information; the first request information is used to request first downlink information and other events except sending the first downlink information.

[0034] In the above embodiment, at least two events may be requested through the same request information.

[0035] In combination with some embodiments of the first aspect, in some embodiments, the request information includes: first request information and second request information; wherein, the first request information is used to request first downlink information, and the second request information is used to request other events besides sending the first downlink information.

[0036] In the above embodiment, requests for at least two events may be made through different request information.

[0037] In combination with some embodiments of the first aspect, in some embodiments, other events besides sending the first downlink information include at least one of the following: a radio resource control (RRC) connection establishment request; an RRC recovery establishment request; an RRC recovery establishment request 1; an RRC reconstruction request; and an RRC system message request.

[0038] In the above embodiment, other events other than the event before the first downlink event are exemplified. For example, the terminal may request the network device to send downlink information and establish an RRC connection at the same time.

[0039] In combination with some embodiments of the first aspect, in some embodiments, sending request information to a network device includes at least one of the following: sending request information requesting different events based on different logical channels; sending request information requesting different events based on different Media Access Contro Control Element (MAC CE); sending first request information, the first request information including first indication information indicating the request event; sending second request information, the second request information including first indication information indicating the request event; sending request information requesting different request events based on the second indication information sent by the network device; and sending request information requesting different events based on different preambles and / or physical random access channels (PRACH) resources.

[0040] In the above embodiments, the terminal can send request information for different events in different ways. For example, the terminal can send requests for different events through different logical channels or MAC CEs; or send first request information and / or second request information; or send second indication information sent by a network device; or send requests for different events through different preambles and / or PRACHs. In this way, the terminal can achieve a variety of event requests and adapt to more application scenarios.

[0041] In combination with some embodiments of the first aspect, in some embodiments, different logical channels correspond to different logical channel numbers (Logical Channel Index, LCID), and / or, different logical channels are based on different MAC service data units (Service Data Unit, SDU) carry; and / or, different MAC CEs correspond to different logical channel numbers LCID, and / or, different MAC CEs are based on different MAC sub-protocol data units (subPDU) carry.

[0042] In the above embodiments, the correspondence between the logical channel and the LCID, and the MAC CE and the LCID is defined, and / or the location where the MAC SDU and / or MAC CE is carried is also described.

[0043] In combination with some embodiments of the first aspect, in some embodiments, the first indication information indicating the request event is based on at least one of the following signaling indications: a spare field; a spare bit; a reservation status; an information class extension indication field; and an information type indication field.

[0044] In the above embodiment, multiple event request information can be sent using various signaling instructions or carrying methods, thereby adapting to more application scenarios. For example, if a reserved field, reserved bit, or reserved status is used, the existing signaling structure can be reused, reducing changes to the signaling structure and improving signaling utilization.

[0045] In combination with some embodiments of the first aspect, in some embodiments, the second indication information sent by the network device is based on at least one of the following signaling indications: random access response (Random Access Response, RAR) signaling; system information; and request information configuration.

[0046] In the above embodiment, the network device can indicate multiple events jointly requested by the terminal in multiple ways, which is applicable to more application scenarios.

[0047] With reference to some embodiments of the first aspect, in some embodiments, request information of different request events corresponds to different preambles and / or PRACH resources.

[0048] In the above embodiment, different preamble codes or PRACH resources may be sent so that the network device can be aware of multiple events requested by the terminal, and the terminal does not need to add other indication information for indication, thereby reducing signaling overhead.

[0049] In combination with some embodiments of the first aspect, in some embodiments, the request information includes at least one of the following: message 3 (Msg3); Msg1; MsgA; MAC CE; and Preamble.

[0050] In the above embodiment, request information of multiple events can be sent through multiple messages or signaling, and requests for multiple events can be flexibly implemented in the random result process, which can adapt to more application scenarios.

[0051] In combination with some embodiments of the first aspect, in some embodiments, the method further includes: determining at least one event capable of joint request based on at least one of the following methods: indication signaling; a predefined method; and terminal capability reporting.

[0052] In the above embodiment, the terminal can confirm the joint request event through multiple methods such as indication signaling, predefined methods, and terminal capability reporting. On the one hand, it can realize the diversity of determining the joint request event, and on the other hand, it is convenient for the subsequent terminal to request the network device for these multiple events.

[0053] In a second aspect, an embodiment of the present disclosure proposes an information processing method, which is executed by a network device, including: receiving a request message sent by a terminal, wherein the request message is used to request the network device to send a first downlink message and other events except sending the first downlink message.

[0054] In combination with some embodiments of the second aspect, in some embodiments, the request information includes: first request information; the first request information is used to request first downlink information and other events except sending the first downlink information.

[0055] In combination with some embodiments of the second aspect, in some embodiments, the request information includes: the request information includes: first request information and second request information; wherein, the first request information is used to request first downlink information, and the second request information is used to request other events besides sending the first downlink information.

[0056] In combination with some embodiments of the second aspect, in some embodiments, the request information includes: other events other than sending the first downlink information, including at least one of the following: RRC connection establishment request; RRC recovery establishment request; RRC recovery establishment request 1; RRC reconstruction request; and RRC system message request.

[0057] In combination with some embodiments of the second aspect, in some embodiments, the request information includes: request information sent by the receiving terminal, including at least one of the following: request information sent by the receiving terminal requesting different events based on different logical channels; request information sent by the receiving terminal requesting different events based on different MAC CEs; first request information sent by the receiving terminal, the first request information including first indication information indicating the requested event; second request information sent by the receiving terminal, the second request information including first indication information indicating the requested event; and request information sent by the receiving terminal requesting different events based on different preambles and / or PRACH resources.

[0058] In combination with some embodiments of the second aspect, in some embodiments, the request information includes: different logical channels correspond to different LCIDs, and / or different logical channels are carried based on different MAC SDUs; and / or different MAC CEs correspond to different logical channel numbers LCIDs, and / or different MAC CEs are carried based on different MAC subPDUs.

[0059] In combination with some embodiments of the second aspect, in some embodiments, the request information includes: first indication information indicating a request event, based on at least one of the following signaling indications: reserved spare field; Spare bit; reservation status; information class extension indication field; and information type indication field.

[0060] In combination with some embodiments of the second aspect, in some embodiments, the request information includes: the method also includes: sending second indication information to the terminal, the second indication information is used by the terminal to send request information requesting different events.

[0061] In combination with some embodiments of the second aspect, in some embodiments, the request information includes: second indication information, which is indicated based on one of the following signaling indications: random access response RAR signaling; system information; and request information configuration.

[0062] In combination with some embodiments of the second aspect, in some embodiments, the request information includes: request information of different request events corresponding to different preambles and / or PRACH resources.

[0063] In combination with some embodiments of the second aspect, in some embodiments, the request information includes: request information, including at least one of the following: Msg3; Msg1; MsgA; MAC CE; and Preamble.

[0064] In combination with some embodiments of the second aspect, in some embodiments, the request information includes: the method also includes: determining at least one event that can be jointly requested based on at least one of the following methods: indication signaling; predefined method; and terminal capability reporting.

[0065] In a third aspect, an embodiment of the present disclosure proposes a terminal, comprising: a first transceiver module, configured to send a request message to a network device, wherein the request message is used to request the network device to send a first downlink message and other events except sending the first downlink message.

[0066] In a fourth aspect, an embodiment of the present disclosure proposes a network device, comprising: a second transceiver module, configured to receive request information sent by a terminal, wherein the request information is used to request the network device to send first downlink information and other events except sending the first downlink information.

[0067] In a fifth aspect, an embodiment of the present disclosure proposes a communication device comprising one or more processors; wherein the above-mentioned communication device is used to execute optional implementation methods such as the first aspect, the second aspect, or the first and second aspects.

[0068] In the sixth aspect, an embodiment of the present disclosure proposes a communication system, comprising: a terminal and a network device; wherein the above-mentioned terminal is configured to execute the method described in the optional implementation manner of the first aspect, and the above-mentioned network device is configured to execute the method described in the optional implementation manner of the second aspect.

[0069] In the seventh 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 method described in the first aspect, the second aspect, or the optional implementation of the first and second aspects.

[0070] In an eighth aspect, an embodiment of the present disclosure proposes a computer program product, which includes a computer program or instructions. When the computer program or instructions are executed by a processor, they implement the method described in the first aspect, the second aspect, or the optional implementation of the first and second aspects.

[0071] In a 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 method described in the first aspect, the second aspect, or the optional implementation of the first and second aspects.

[0072] In a tenth aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the information processing method as described in the first aspect, the second aspect, or the optional implementation of the first and second aspects.

[0073] In the eleventh aspect, an embodiment of the present disclosure proposes a chip or a chip system; the chip or chip system includes a processing circuit configured to execute the method described in accordance with the above-mentioned first aspect, second aspect, or optional implementation of the first and second aspects.

[0074] It is understood that the above-mentioned terminals, network devices, communication systems, storage media, program products, computer programs, chips, or chip systems are all used to perform the methods provided by 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.

[0075] The present disclosure provides an information processing method, terminal, network device, communication system, and storage medium. In some embodiments, the terms information processing method and communication method are interchangeable, the terms information processing device and communication device are interchangeable, and the terms information processing system and communication system are interchangeable.

[0076] 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.

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

[0078] 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.

[0079] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

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

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

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

[0083] 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.

[0084] 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 restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0085] 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.

[0086] 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.

[0087] 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.

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

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

[0090] 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", "carrier", "component carrier", "bandwidth part (BWP)" and the like may be used interchangeably.

[0091] 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.

[0092] 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, it can also be called device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, it can also be set as a structure in which the terminal has all or part of the functions of the access network device. In addition, language such as "uplink" and "downlink" can also be replaced by language 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.

[0093] 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.

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

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

[0096] 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.

[0097] FIG1A is a schematic diagram showing the structure of an information processing system 100 according to an embodiment of the present disclosure. As shown in FIG1A , the information processing system 100 may include: a terminal 101 and a network device 102 .

[0098] In some embodiments, the network device 102 may include at least one of an access network device and a core network device.

[0099] In some embodiments, the terminal 101 includes, for example, a mobile phone, a wearable device, an Internet of Things (IOT) device or terminal, a car with communication function, a smart car, a tablet computer (Pad), 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.

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

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

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

[0103] In some embodiments, the core network device may be a device including a first device, a second device, etc., or may be a plurality of devices or a device group, each including all or part of the first device and the second device. The first device and the second device may be network elements; the network element may be virtual or physical. The core network may include, for example, at least one of an evolved packet core (EPC), a 5G core network (5GCN), and a next generation core (NGC).

[0104] It can be understood that the information processing 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 provided by the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of system architecture and the emergence of new business scenarios, the technical solution provided by the embodiment of the present disclosure is also applicable to similar technical problems.

[0105] The following embodiments of the present disclosure may be applied to the information processing system 100 shown in FIG1A , or a portion thereof, but are not limited thereto. The various entities shown in FIG1A are illustrative only. The information processing system may include all or a portion of the entities shown in FIG1A , or may include other entities other than those shown in FIG1A . The number and configuration of the entities may be arbitrary. 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.

[0106] 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), 6th generation mobile communication system (6G), 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, LTE or LTE-A combined with 5G or 6G).

[0107] In some embodiments, in order to reduce energy consumption of network devices, etc., network energy saving (NES) research is introduced; the network energy saving research can fully evaluate and standardize NES technologies in the time domain, frequency domain, space domain and / or power domain.

[0108] In the time domain technology, on-demand system messages (such as on-demand Synchronization Signal Block (SSB) / System Information Block 1 (SIB1)) are one of the important technologies. On-demand SSB / SIB1 technology means that SSB / SIB1 is no longer sent periodically, but is sent according to the needs of the UE. For example, as shown in Figure 1B: the base station stops sending SSB / SIB1 periodically (in the NES state), or uses a more sparse time domain pattern to send SSB / SIB1; when the UE has an SSB / SIB1 demand, it sends a wake-up signal (WUS) to the base station; 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 and / or the time period, after sending one or more SSB bursts, it stops sending SSB / SIB1 (i.e., returns to the NES state).

[0109] Taking on-demand SIB1 as an example, in order to send a WUS signal to trigger SIB1 transmission, the terminal needs to obtain the corresponding WUS configuration and send a WUS based on the WUS configuration to request the corresponding SIB1 transmission.

[0110] For WUSs requesting SIB1, one possible approach is to refer to the on-demand SI mechanism in related technologies and use Msg.1 or Msg.3 during the random access process to request the corresponding SIB1. In addition to on-demand SI and on-demand SIB1 requests, the terminal can implement other requests based on the random access process, such as RRC Setup Request, RRC Resume Request, and RRC Reestablishment Request.

[0111] In order to reduce the delay of random access and simplify the terminal random access request process, if the terminal has multiple requests at the same time; for example, the terminal needs to request SIB1 at the current moment and needs to initiate the RRC connection establishment process at the same time, a possible implementation method is that the terminal sends the above two or more requests based on the same random access process.

[0112] In some embodiments, 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, and the terminal sends the request information on the corresponding resources based on the configuration. The specific mechanism includes:

[0113] Application conditions: If si-BroadcastStatus is configured as notBroadcasting and SI-RequestConfig is configured, the required Msg1 resources are determined based on SI-RequestConfig. Otherwise, the request information is carried in Msg3. If the request is based on Msg3, the corresponding mechanism is shown in Figure 1C.

[0114] If SI-RequestConfig is not configured, the terminal triggers on-demand SI transmission by transmitting the RRCSystemInfoRequest message via Msg3. If, after transmitting the request message, the terminal successfully receives the request message Msg4 transmitted by the base station 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 corresponding RRC system message request information element (RRCSystemInfoRequest IE) is shown in Figure 1D.

[0115] The terminal transmits the above request information based on the uplink common control channel message (UpLink Common Control Channel Message, UL-CCCH1 Message), the UL-CCCH1 Message is carried based on Msg3, the UL-CCCH corresponds to a 48-bit radio resource control (Radio Resource Control, RRC) message, and CCCH1 is based on as shown in Figure 1E.

[0116] In addition to carrying on-demand SI request information, the UL-CCCH Message may also carry other request information, such as RRCSetupRequest, RRCResumeRequest, and / or RRCReestablishmentRequest. After the terminal sends the request information based on the UL-CCCH-Message, the base station determines whether the request is at least one of on-demand SI, RRCSetupRequest, RRCResumeRequest, and RRCReestablishmentRequest based on the indication bit of the UL-CCCH-Message.

[0117] For a random access request, RRCSetupRequest1 may also be included; compared with RRCSetupRequest, RRCSetupRequest1 can be applied to more terminals in an inactive state (for example, RRCSetupRequest1 is based on I-RNTI-Value identification, and RCSetupRequest is based on shortI-RNTI-Value identification). The RRCSetupRequest1 is carried based on the UL-CCCH1-Message, the UL-CCCH1 corresponds to a 64-bit RRC message, and the LCID number corresponding to the UL CCCH is defined based on the definition method of Table 1 and Table 2.

[0118] Table 1

[0119] Table 2

[0120] Optionally, the message carried on the CCCH can be carried based on a media access control (MAC) service data unit (SDU). The MAC SDU is contained in a MAC sub-protocol data unit (subPDU). A MAC PDU contains one or more MAC subPDUs, each of which corresponds to a subheader. The subheader contains a logical channel identity (LCID). The specific structure is shown in Figure 1F. The logical channel identity can also be called the logical channel number.

[0121] Currently, the on-demand SI mechanism is used to request information of other SIBs except SIB 1. The embodiment of the present disclosure mainly requests multiple request information based on the same random access procedure on the basis of considering the SIB1 request information mechanism.

[0122] In some embodiments, the UE may be a terminal, or the terminal may be a UE.

[0123] FIG2 is an interactive diagram of an information processing method according to an embodiment of the present disclosure. As shown in FIG2 , the present disclosure embodiment relates to an information processing method for an information processing system 100, and the method includes:

[0124] Step S2101: The terminal determines at least one event that can be jointly requested. Optionally, the terminal determines at least one event to be requested. Optionally, the terminal determines at least one event to be jointly requested.

[0125] Optionally, the terminal determines at least two events to be jointly requested. Optionally, the terminal determines at least two events that can be jointly requested.

[0126] Optionally, the at least one event of the joint request may include: an event requesting the sending of first downlink information; and / or other events other than the sending of first downlink information. Here, the request to send first downlink information may be considered an event of a terminal request or a joint request. The first downlink information may also refer to a first downlink signal; the first downlink information may refer to any downlink information, and the first downlink signal may refer to any downlink signal.

[0127] Optionally, the at least two events of the joint request may include: an event requesting to send the first downlink information; or other events except sending the first downlink information; or an event requesting to send the first downlink information and other events except sending the first downlink information.

[0128] Optionally, the request to send the first downlink information may be a first type of event or a first type of event request; and the event other than sending the first downlink information may be a second type of event or a second type of event request.

[0129] Optionally, the first downlink information may include at least one of the following: SSB, SI, SIB, SIB1, on-demand SIB1, 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 or predefined signals. Optionally, the first downlink information is not limited; the event of requesting the network device to send the first downlink information is not limited.

[0130] Exemplarily, the other newly defined or predefined signals may be: a signal (PSS+SSS) consisting of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS), or a discovery reference signal (DRS), etc.

[0131] Exemplarily, the event of requesting to send the first downlink information may include at least one of the following: SSB request, SI request, SIB1 request, on demand SIB1 request, MIB request, CSI-RS request, TRS request, PDCCH request, PDSCH request, signal request consisting of PSS and SSS, and DRS request.

[0132] Optionally, the other events other than sending the first downlink information may include at least one of the following: an RRC connection establishment request (RRCSetupRequest), an RRC recovery establishment request (RRCResumeRequest), (RRC recovery establishment request 1RRCResumeRequest1), an RRC reestablishment request (RRCReestablishmentRequest), and other system message (Other SI, OSI) request (RRCSystemInfoRequest). Optionally, the other events other than sending the first downlink information are not limited.

[0133] Exemplarily, the RRC recovery establishment request 1 and the RRC recovery establishment request are based on different information bearers.

[0134] Optionally, other events besides sending the first downlink information may include at least one of the following: handover, scheduling request (SR) failure; explicit request by RRC upon synchronous reconfiguration; time alignment for a primary or a secondary TAG; beam failure recovery; consistent UL LBT failure on SpCell; SDT in RRC_INACTIVE; positioning purpose during RRC_CONNECTED requiring random access procedure (for example, UE positioning requires timing information); early UL synchronization with an LTM candidate cell; and RACH-based LTM cell handover. switch); DL or UL data arrival (during RRC_CONNECTED or during RRC_INACTIVE while SDT procedure is ongoing, when UL synchronisation status is "non-synchronised");and UL data arrival, during RRC_CONNECTED or during RRC_INACTIVE while SDT procedure is ongoing, when there are no PUCCH resources for SR available.

[0135] In the embodiments of the present disclosure, taking into account the possibility of application scenarios and the limitations of the processing complexity of network equipment (such as base stations), it is necessary to define events that can be jointly requested by the terminal; for example, the terminal can determine the events that can be jointly requested through indication signaling, predefined methods and / or terminal capability indication.

[0136] In some embodiments, the terminal determines at least one event that can be jointly requested based on an indication signaling method.

[0137] In an optional embodiment, the network device sends a first signaling to the terminal, wherein the first signaling is used to instruct the terminal to determine at least one event that can be jointly requested. Optionally, the terminal receives the first signaling sent by the network device.

[0138] Optionally, the first signaling may include: SIB, WUS configuration signaling or random access response (Random Access Response, RAR) signaling.

[0139] Optionally, the RAR signaling may include MAC RAR or a newly defined MAC RAR.

[0140] Optionally, the first signaling may include third indication information, and the third indication information is used to indicate at least one event of the joint request. Exemplarily, when the first indication information has different values, it is used to indicate a combination of different joint request events. For example, if the first indication information has a first value, it is used to indicate that at least one event of the joint request is an SI request; or, if the first indication information has a second value, it is used to indicate that at least one event of the joint request is an RRC connection establishment request; or, if the first indication information has a third value, it is used to indicate that at least one event of the joint request is an SI request and an RRC connection establishment request; or, if the first indication information has a fourth value, it is used to indicate that at least one event of the joint request is an SI request, an RRC connection establishment request, and an RRC reestablishment request; and so on. This combination of joint request events is at least one event of the joint request.

[0141] Optionally, the reserved field or reserved bit of the RAR signaling may be used to indicate at least one event of the joint request.

[0142] Optionally, the terminal determines at least one event capable of joint request based on the first signaling.

[0143] In some embodiments, the terminal determines at least one event capable of being jointly requested based on a predefined manner.

[0144] Optionally, the terminal determines at least one event for the joint request based on a predetermined rule. Exemplarily, the predetermined rule may be determined by negotiation between the terminal or the network device; or the predetermined rule may be specified in a communication protocol.

[0145] In some embodiments, the terminal determines at least one event that can be jointly requested based on the manner in which the terminal capabilities are reported.

[0146] In some optional embodiments, the terminal sends capability information to the network device, wherein the capability information is used to indicate at least one event jointly requested by the terminal. Optionally, the network device receives the capability information sent by the terminal.

[0147] Optionally, the terminal sends a preamble to the network device, where the preamble indicates capability information, or the preamble is used to indicate at least one event jointly requested by the terminal.

[0148] Optionally, different preamble codes are used to indicate at least one event of different joint requests.

[0149] Optionally, a reserved field of the preamble is used to indicate at least one event of the joint request. For example, different reserved fields of the preamble are used to indicate different combinations of joint request events.

[0150] Optionally, the newly defined preamble is used to indicate at least one event of the joint request. For example, different newly defined preambles are used to indicate different combinations of joint request events.

[0151] Optionally, the terminal determines a preamble corresponding to a combination of events supporting joint request based on a signaling indication, and determines at least one event capable of joint request based on the preamble.

[0152] Optionally, the name of the capability information is not limited, for example, it is an event joint request indication.

[0153] Step S2102: The terminal sends a request message to the network device.

[0154] Optionally, the request information is used to request the network device to send the first downlink information and other events except sending the first downlink information.

[0155] Optionally, the request information is used to indicate at least two events; the at least two events include at least an event requesting to send the first downlink information and other events except sending the first downlink information.

[0156] In some embodiments, the terminal sends request information to the network device during the random access process.

[0157] In some embodiments, the network device receives request information sent by the terminal during the random access process.

[0158] In some embodiments, after determining the events that can be jointly requested, the terminal selects at least one event from the events that can be jointly requested as an event combination, and uses the event combination as the event to be requested in the request information. Exemplarily, the terminal determines that the events that can be jointly requested include a first event, a second event, and a third event; the terminal uses the first event and the second event as a combined event, and the request information is used to request the combined event.

[0159] Optionally, the terminal may select an event combination from the events that can be jointly requested based on a predefined rule, or the terminal may select an event combination from the events that can be jointly requested based on demand.

[0160] In some embodiments, the request information includes: first request information; the first request information is used to request the first downlink information and other events except sending the first downlink information.

[0161] In some embodiments, the request information includes: first request information and second request information; wherein the first request information is used to request the first downlink information, and the second request information is used to request other events except sending the first downlink information.

[0162] In some embodiments, the request information includes at least one of the following: Msg3, Msg1, MsgA, MAC CE, and Preamble; or the request information is carried or indicated by at least one of the following: Msg3, Msg1, MsgA, MAC CE, and Preamble.

[0163] Optionally, Msg3 is Msg3 in the four-step random access process; Msg1 is Msg1 in the four-step random access process; MsgA is MsgA in the four-step random access process; and Preamble is Preamble in the four-step or two-step random access process.

[0164] Exemplarily, the terminal sends two MAC SDUs based on Msg3, one MAC SDU is used to request sending the first downlink information (such as SI request), and the other MAC SDU is used to request sending other events except sending the first downlink information (such as RRC reconstruction request).

[0165] Exemplarily, the terminal sends two MAC SDUs based on Msg3, one MAC SDU is used to request sending the first downlink information (such as SI request), and the other MAC SDU is used to request sending other events except sending the first downlink information (such as RRC reconstruction request).

[0166] Exemplarily, the terminal sends two MAC CEs based on Msg3, one MAC CE is used to request sending the first downlink information, and the other MAC CE is used to request sending other events except sending the first downlink information.

[0167] Exemplarily, the terminal sends different preambles based on Msg1, and different preambles (Preambles) are used to indicate requests for different events; for example, Preamble1 is used to indicate an SI request and an RRC re-establishment request.

[0168] Exemplarily, the terminal sends a preamble based on Msg1, for example, sends Preamble2, where Preamble2 is used to indicate an SI request; and the terminal sends a MAC SDU based on Msg3, where the MAC SDU is used to request an RRC re-establishment request.

[0169] Exemplarily, the terminal sends a preamble based on MsgA, such as Preamble3, where Preamble2 is used to indicate an on demand SIB1 request; and the terminal sends a Physical Uplink Shared Channel (PUSCH) based on MsgA, where PUSCH includes indication information indicating an RRC reestablishment request.

[0170] In some embodiments, the terminal sends request information requesting different events to the network device based on different logical channels.

[0171] In some embodiments, the network device receives request information of different events sent by the terminal based on different logical channels.

[0172] Optionally, the terminal sends different CCCH messages based on different logical channels, and different CCCH messages are used to carry request information for requesting different events, or different CCCH messages are used to indicate requests for different events.

[0173] Optionally, the CCCH message may be a first-type CCCH message. The LCID index corresponding to the first-type CCCH message may be 52 or 35, etc. For example, the first-type CCCH message may be a UL-CCCH message. For example, the first-type CCCH message may be a UL-CCCH Message or a UL-CCCH1-Message.

[0174] Optionally, the first-type CCCH message may include a first CCCH message or a second CCCH message; the second CCCH message occupies more bits than the first CCCH message. For example, the first CCCH message is 48 bits, and the second CCCH message is 64 bits. For example, the first CCCH message may be a UL-CCCH message, and the second CCCH message may be a UL-CCCH1-Message.

[0175] Optionally, the CCCH message may be a second-type CCCH message. The LCID index corresponding to the second-type CCCH message may be any one of 37 to 42, or may be any one of 64 to 292 of an extended logical channel identifier (eLCID) index. For example, the second-type CCCH message may be a UL-CCCH1 message. For example, the second-type CCCH message may be a UL-CCCH2 message.

[0176] Optionally, the CCCH message may be a predetermined CCCH message. For example, the predetermined CCCH message is used to request the network device to send the first downlink information.

[0177] In some embodiments, different logical channels correspond to different logical channel numbers (LCIDs), and / or different logical channels are carried based on different MAC SDUs.

[0178] Optionally, the terminal sends request information for different events based on different MAC SDUs carried by different MAC subPDUs.

[0179] Optionally, the terminal sends request information for different events based on different MAC SDUs carried by the same MAC subPDU.

[0180] In some embodiments, the terminal sends request information requesting different events based on different MAC CEs.

[0181] In some embodiments, based on different MAC CEs, request information for requesting different events sent by the terminal is received.

[0182] In some embodiments, different MAC CEs correspond to different logical channel numbers (LCIDs), and / or different MAC CEs are carried based on different MAC subPDUs.

[0183] Optionally, the terminal sends request information for different events based on different MAC CEs carried by different MAC subPDUs.

[0184] Optionally, the terminal sends request information for different events based on different MAC CEs carried by the same MAC subPDU.

[0185] Optionally, a MAC PDU may include one or more MAC subPDUs. In the above embodiments, different MAC subPDUs are included in different MAC PDUs, or different MAC subPDUs may be included in the same MAC PDU.

[0186] In some embodiments, the terminal sends first request information to the network device, where the first request information includes first indication information indicating a request event.

[0187] In some embodiments, the network device receives first request information sent by the terminal, where the first request information includes first indication information indicating a request event.

[0188] In some embodiments, the terminal sends a second request message to the network device, where the second request message includes first indication information indicating a request event;

[0189] In some embodiments, the network device receives second request information sent by the terminal, where the second request information includes first indication information indicating a request event.

[0190] Optionally, the first indication information included in the first request information may be the same as the first indication information included in the second request information, or the first indication information included in the first request information may be the same as the second indication information included in the second request information.

[0191] Optionally, the reserved field, reserved bit, reserved status, information class extension indication field, and / or information type indication field may be carried by different CCCHs; or, the reserved field, reserved bit, reserved status, information class extension indication field, and / or information type indication field may be carried by the same CCCH. Here, when the reserved field, reserved bit, reserved status, information class extension indication field, and / or information type indication field may be carried by the same CCCH, different combinations of request events cannot be distinguished based on the LCID. Therefore, they may be indicated by the above-mentioned information field.

[0192] Optionally, the first indication information indicating the request event is based on at least one of the following signaling indications: a spare field; a spare bit; a reservation status; a message class extension indication field (messageClassExtension); and an information type indication field.

[0193] Exemplarily, the information type indication field may be: the UL-CCCH-MessageType field of UL-CCCH1-Message or UL-CCCH1-Message1, or the c1 field of the UL-CCCH-MessageType field of UL-CCCH1-Message or UL-CCCH1-Message1.

[0194] Optionally, the reserved field, reserved bit, reserved status, information type extension indication field and information type indication may all be a combination (or combination) of different events for indicating requests when they have different values.

[0195] Exemplarily, when the reserved field has a first value, it indicates a request to send the first downlink information; or, when the reserved field has a second value, it indicates an event other than sending the first downlink information. For example, when the reserved field is 0, it indicates an SI request; or, when the reserved field is 1, it indicates an RRC reestablishment request. Here, the reserved bit, reservation status, information class extension indication field, and information type indication may be indicated in a manner similar to that of the reserved field.

[0196] Exemplarily, when the reserved field has a first value, it is used to simultaneously transmit at least the first downlink information and other events other than the first downlink information. For example, when the reserved field is 0, it is used to indicate an SI request and an RRC reestablishment request. Here, the reserved bit, reservation status, information class extension indication field, and information type indication can be indicated in a manner similar to that of the reserved field.

[0197] Optionally, the reserved field, reserved bit, reserved status, information class extension indication field and information type indication can all be: when different reserved fields, reserved bits, reserved status, information class extension indication field and / or information type indication are used to indicate different requested events, or a combination (or combination) of different events.

[0198] Exemplarily, the reserved field includes a first reserved field and a second reserved field; wherein the first reserved field is used to indicate a request to send the first downlink information, and the second reserved field is used to indicate other events besides sending the first downlink information. For example, the first reserved field is used to indicate an SI request, and the second reserved field is used to request an RRC reestablishment request. Here, the reserved bit, reservation status, information class extension indication field, and information type indication can be indicated in a similar manner to the reserved field.

[0199] Exemplarily, the reserved field includes a first reserved field and a second reserved field; wherein the first reserved field is used to indicate at least one event in a request to send first downlink information and at least one first event among other events other than sending the first downlink; and the second reserved field is used to indicate at least one second event among other events other than sending the first downlink. For example, the first reserved field indicates an SI request and an RRC reestablishment request, and the second reserved field indicates a handover request. Here, the reserved bit, reservation status, information class extension indication field, and information type indication can be indicated in a similar manner to the reserved field.

[0200] In some embodiments, the terminal sends request information requesting a different request event based on the second indication information sent by the network device.

[0201] In some optional embodiments, the network device sends the second indication information to the terminal. Optionally, the terminal receives the second indication information sent by the network device.

[0202] Optionally, the second indication information sent by the network device is based on at least one of the following signaling indications: RAR signaling, system information and request information configuration.

[0203] Optionally, the second indication information is used to indicate whether the terminal is allowed to send a request for at least one event, and / or to indicate the time-frequency domain resources and / or CCCH for the terminal to initiate the request for at least one event. Accordingly, the terminal may send the request for at least one event based on the time-frequency domain resources and / or CCCH.

[0204] Illustratively, the RAR signaling may be existing signaling or newly defined RAR signaling.

[0205] Exemplarily, the RAR signaling may be MAC RAR.

[0206] Exemplarily, the second indication information may be based on an indication in RAR signaling, or an indication in the R field of RAR signaling. Alternatively, the second indication information may be based on an indication in other fields or bits reserved in RAR signaling.

[0207] Exemplarily, the system information may be SIB1 or other system messages.

[0208] Exemplarily, the request information configuration may be WUS configuration, etc.

[0209] In some embodiments, the terminal sends request information for different events based on different preambles and / or RACH resources. Optionally, the RACH resource may be a PRACH resource.

[0210] In some embodiments, the network device receives request information for different events sent by the terminal based on different preambles and / or RACH resources.

[0211] Optionally, the request information of different request events corresponds to different preambles and / or RACH resources. Optionally, the RACH resources are PRACH resources.

[0212] Optionally, the PRACH resource may include a random access channel occasion (RACH occasion, RO).

[0213] Exemplarily, the preamble includes a first preamble and a second preamble; an event requesting to send the first downlink information corresponds to the first preamble, and an event other than sending the first downlink information corresponds to the second preamble.

[0214] Exemplarily, the PRACH resources include a first PRACH resource and a second PRACH resource; an event requesting to send the first downlink information corresponds to the first PRACH resource, and an event other than sending the first downlink information corresponds to the second PRACH resource.

[0215] Step S2103: The network device determines at least one event that can be jointly requested. Optionally, the network device determines at least one event requested by the terminal.

[0216] In some embodiments, step S2103 may precede step S2101. Thus, the network device may determine at least one event that the terminal can jointly request through indication signaling, predefined methods, or the like; or, the network device may learn at least one event that the terminal needs to request through terminal capability reporting.

[0217] Optionally, the network device determines the at least one event for the terminal's joint request using a signaling method. Optionally, the network device sends a first signaling to the terminal, the first signaling being used for the at least one event for the terminal's joint request. Optionally, the network device determines the at least one event for the terminal's joint request based on a predefined method.

[0218] Optionally, the network device determines at least one event of the terminal joint request based on the terminal capability reporting method. Optionally, the network device determines at least one event of the terminal joint request based on the terminal capability reporting method, which may also be before the network device sends the first signaling to the terminal via indication signaling.

[0219] In some embodiments, the network device determines at least one event of a terminal joint request based on at least one of indication signaling, a predefined method, and terminal capability reporting, which is similar to the terminal determining at least one event that can be jointly requested based on at least one of indication signaling, a predefined method, and terminal capability reporting, and will not be repeated here.

[0220] In some embodiments, the network device sends second indication information to the terminal, where the second indication information is used by the terminal to send request information requesting a different event.

[0221] In some embodiments, step S2103 may be performed after step S2101. In this way, the network device may determine at least one event jointly requested by the terminal based on the request information sent by the terminal.

[0222] In some embodiments, the network device determines at least one event of the terminal joint request based on the request information sent by the terminal.

[0223] Optionally, the network device determines at least one event jointly requested by the terminal based on the first request information and / or second request information sent by the terminal; wherein the first request information includes first indication information indicating the requested event, and / or the second request information includes first indication information indicating the requested event.

[0224] Optionally, the network device determines at least one event jointly requested by the terminals based on a logical channel through which the terminals send request information requesting different events.

[0225] Optionally, the network device determines at least one event jointly requested by the terminal based on a MAC CE in which the terminal sends request information requesting different events.

[0226] Optionally, the network device determines at least one event jointly requested by the terminal based on a preamble and / or a PRACH resource used by the terminal to send request information for different events.

[0227] Optionally, the network device determines at least one event of the terminal joint request based on second indication information sent by the network device to the terminal.

[0228] 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.

[0229] 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.

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

[0231] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "some", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "some 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, some A, any A, or first A, etc., but not limited to this.

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

[0233] The information processing method involved in the embodiments of the present disclosure may include at least one of steps S2101 to S2103. For example, step S2101 can be implemented as an independent embodiment; step S2102 can be implemented as an independent embodiment; step S2103 can be implemented as an independent embodiment; the combination of step S2101 and step S2102 can be implemented as an independent embodiment; the combination of step S2102 and step S2103 can be implemented as an independent embodiment; and the combination of steps S2101 and S2103 can be implemented as an independent embodiment.

[0234] In some embodiments, step S2102 and step S2103 may be optional, and one or more of these steps may be omitted or replaced in different embodiments.

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

[0236] In the embodiments of the present disclosure, each embodiment can be implemented individually or in combination with each other, and the steps in each embodiment can be distinguished in order.

[0237] FIG3A is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG3A , the present disclosure embodiment relates to an information processing method, which is executed by a terminal. The method includes:

[0238] Step S3101: Determine at least one event that can be jointly requested.

[0239] The optional implementation of step S3101 can refer to the optional implementation of step S2101 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0240] Optionally, the terminal determines at least one event that can be jointly requested based on indication signaling, a predefined method, and a method of reporting terminal capabilities.

[0241] Optionally, the terminal receives first signaling sent by the network device, where the first signaling is used to indicate at least one event of the joint request.

[0242] Step S3102, sending request information.

[0243] The optional implementation of step S3102 can refer to the optional implementation of step S2102 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0244] In some embodiments, the terminal may send request information to a network device, but is not limited thereto and may also send request information to other entities.

[0245] Optionally, the terminal sends request information of different events based on different preamble codes and / or PRACH resources.

[0246] Optionally, the terminal sends request information of different events based on different logical channels.

[0247] Optionally, the terminal sends request information of different events based on different MAC CEs.

[0248] Optionally, the terminal sends request information requesting a different event based on the second indication information sent by the network device.

[0249] The information processing method involved in the embodiments of the present disclosure may include at least one of steps S3101 and S3102. For example, step S3101 may be implemented as an independent embodiment; step S3102 may be implemented as an independent embodiment; or a combination of step S3101 and step S3102 may be implemented as an independent embodiment.

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

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

[0252] In the embodiments of the present disclosure, each embodiment can be implemented individually or in combination with each other, and the steps in each embodiment can be distinguished in order.

[0253] FIG3B is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG3B , the present disclosure embodiment relates to an information processing method, which is executed by a terminal and includes:

[0254] Step S3201: Send a request message to a network device, wherein the request message is used to request the network device to send first downlink information and other events except sending the first downlink information.

[0255] The optional implementation of step S3201 can be found in step S2102 in FIG. 2 , or the optional implementation of step S3102 in FIG. 3A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0256] In some embodiments, the request information includes: first request information; the first request information is used to request the first downlink information and other events except sending the first downlink information.

[0257] In some embodiments, the request information includes: first request information and second request information; wherein the first request information is used to request the first downlink information, and the second request information is used to request other events except sending the first downlink information.

[0258] In some embodiments, other events besides sending the first downlink information include at least one of the following: a radio resource control RRC connection establishment request; an RRC recovery establishment request; an RRC recovery establishment request 1; an RRC reconstruction request; and an RRC system message request.

[0259] In some embodiments, sending request information to a network device includes at least one of the following: sending request information requesting different events based on different logical channels; sending request information requesting different events based on different MAC CEs; sending first request information, the first request information including first indication information indicating the request event; sending second request information, the second request information including first indication information indicating the request event; sending request information requesting different request events based on the second indication information sent by the network device; and sending request information requesting different events based on different preambles and / or physical random access channel PRACH resources.

[0260] In some embodiments, different logical channels correspond to different logical channel numbers LCID, and / or, different logical channels are carried based on different MAC service data units SDU; and / or, different MAC CEs correspond to different logical channel numbers LCID, and / or, different MAC CEs are carried based on different MAC SubPDUs.

[0261] In some embodiments, the first indication information indicating the request event is based on at least one of the following signaling indications: a reserved spare field; a spare bit; a reservation status; an information class extension indication field; and an information type indication field.

[0262] In some embodiments, the second indication information sent by the network device is based on at least one of the following signaling indications: random access response RAR signaling; system information; and request information configuration.

[0263] In some embodiments, request information of different request events corresponds to different preambles and / or PRACH resources.

[0264] In some embodiments, the request information includes at least one of the following: Msg3; Msg1; MsgA; MAC CE; and Preamble.

[0265] In some embodiments, the method further comprises: determining at least one event capable of joint request based on at least one of the following ways: indication signaling; a predefined way; and terminal capability reporting.

[0266] The above embodiments may be implemented individually or in combination with each other. For optional implementations, please refer to the optional implementations of the steps in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0267] FIG4A is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG4A , the present disclosure embodiment relates to an information processing method, which is executed by a network device. The method includes:

[0268] Step S4101, obtain request information.

[0269] The optional implementation of step S4101 can refer to the optional implementation of step S2102 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0270] In some embodiments, the network device receives request information sent by the terminal, but is not limited thereto and may also receive request information sent by other entities.

[0271] In some embodiments, the network device obtains request information specified by the protocol.

[0272] In some embodiments, the network device obtains the request information from upper layer(s).

[0273] In some embodiments, the network device performs processing to obtain the requested information.

[0274] In some embodiments, step S4101 is omitted, and the network device autonomously implements the function indicated by the request information, or the above function is default or by default.

[0275] Step S4102: Determine at least one event that can be jointly requested. Optionally, the network device determines at least one event that the terminal can jointly request. Optionally, the network device determines at least one event that can be jointly requested.

[0276] The optional implementation of step S4102 can refer to the optional implementation of step S2103 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0277] Optionally, in step S4102, before step S4101, the network device determines at least one event that the terminal can jointly request based on one of a predefined method, indication signaling, and terminal capability reporting. For example, the network device may determine at least one event that the terminal jointly requests through a predefined method and an indication signaling method, and send signaling indicating the at least one event that the terminal has determined to be capable of jointly requesting to the terminal, so that the terminal is aware of the at least one event that requires a joint request. For another example, the network device may know in advance the at least one event that the terminal expects to jointly request through terminal capability reporting, so that the network device can know or determine whether to allow the event to be reported.

[0278] Optionally, after step S4101, the network device determines at least one event jointly requested by the terminal based on the request information after receiving the request information.

[0279] The information processing method involved in the embodiments of the present disclosure may include at least one of steps S4101 and S4102. For example, step S4101 may be implemented as an independent embodiment; step S4102 may be implemented as an independent embodiment; or a combination of step S4101 and step S4102 may be implemented as an independent embodiment.

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

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

[0282] In the embodiments of the present disclosure, each embodiment can be implemented individually or in combination with each other, and the steps in each embodiment can be distinguished in order.

[0283] FIG4B is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG4B , the embodiment of the present disclosure relates to an information processing method, which is executed by a network device and includes:

[0284] Step S4201: Receive request information sent by a terminal, wherein the request information is used to request a network device to send first downlink information and other events except sending the first downlink information.

[0285] The optional implementation of step S4201 can be found in step S2102 in FIG. 2 , or the optional implementation of step S4101 in FIG. 4A , and other related parts in the embodiments involved in FIG. 2 and FIG. 4A , which will not be described in detail here.

[0286] In some embodiments, the request information includes: first request information; the first request information is used to request the first downlink information and other events except sending the first downlink information.

[0287] In some embodiments, the request information includes: the request information includes: first request information and second request information; wherein the first request information is used to request the first downlink information, and the second request information is used to request other events except sending the first downlink information.

[0288] In some embodiments, the request information includes: other events other than sending the first downlink information, including at least one of the following: radio resource control RRC connection establishment request; RRC recovery establishment request; RRC recovery establishment request 1; RRC reconstruction request; and RRC system message request.

[0289] In some embodiments, the request information includes: request information sent by the receiving terminal, including at least one of the following: request information sent by the receiving terminal requesting different events based on different logical channels; request information sent by the receiving terminal requesting different events based on different MAC CEs; first request information sent by the receiving terminal, the first request information including first indication information indicating the requested event; second request information sent by the receiving terminal, the second request information including first indication information indicating the requested event; and request information sent by the receiving terminal requesting different events based on different preambles and / or physical random access channel PRACH resources.

[0290] In some embodiments, the request information includes: different logical channels correspond to different logical channel numbers LCID, and / or, different logical channels are carried based on different MAC service data units SDU; and / or, different MAC CEs correspond to different logical channel numbers LCID, and / or, different MAC CEs are carried based on different MAC SDU.

[0291] In some embodiments, the request information includes: first indication information indicating a request event, based on at least one of the following signaling indications: a reserved spare field; a Spare bit; a reservation status; an information class extension indication field; and an information type indication field.

[0292] In some embodiments, the request information includes: The method further includes: sending second indication information to the terminal, the second indication information is used by the terminal to send request information requesting different events.

[0293] In some embodiments, the request information includes: second indication information, indicated based on one of the following signaling indications: random access response RAR signaling; system information; and request information configuration.

[0294] In some embodiments, the request information includes: request information of different request events corresponding to different preambles and / or PRACH resources.

[0295] In some embodiments, the request information includes: request information including at least one of the following: Msg3; Msg1; MsgA; MAC CE; and Preamble.

[0296] In some embodiments, the request information includes: the method further includes: determining at least one event capable of joint request based on at least one of the following methods: indication signaling; a predefined method; and terminal capability reporting.

[0297] The above embodiments may be implemented individually or in combination with each other. For optional implementations, please refer to the optional implementations of the steps in FIG. 2 and FIG. 4A , which will not be described in detail here.

[0298] The present disclosure relates to an information processing method, which includes:

[0299] In some embodiments, a terminal supporting network energy saving initiates multiple event requests including on-demand SIB1 based on at least one of the following methods to request corresponding SIB1 transmission and other event requests:

[0300] The terminal sends different event requests based on different CCCHs; CCCHs are carried on different MAC SDUs. Optionally, different CCCHs correspond to different LCIDs, or different CCCHs correspond to the same LCID. Optionally, the CCCH can be the logical channel in the previous embodiment, or the CCCH message corresponding to the logical channel.

[0301] The terminal determines, based on at least one of the following methods, an event request that can be jointly requested with the on-demand SIB1. Optionally, the method includes at least one of the following: predefinition, signaling configuration, and terminal capability indication. Optionally, the event request that can be jointly requested with the on-demand SIB1 includes at least one of the following: RRC connection establishment request (RRCSetupRequest), RRC recovery establishment request (RRCResumeRequest), RRC recovery establishment request 1 (RRCResumeRequest1), RRC reestablishment request (RRCReestablishmentRequest), and OSI request (RRCSystemInfoRequest).

[0302] The terminal distinguishes multiple event requests carried by CCCH based on at least one of the following methods: CCCH corresponding LCID, CCCH indication signaling, RACH resource and RAR indication signal. Exemplarily, different event request combinations are associated with different RACH resources.

[0303] In some embodiments, a base station supporting network energy saving receives multiple event requests including on-demand SIB1 based on at least one of the following methods:

[0304] The base station receives different event requests based on different CCCHs, which are carried by different MAC SDUs. Optionally, different CCCHs correspond to different LCID numbers, or different CCCHs correspond to the same LCID number.

[0305] The base station determines an event request that can be jointly requested with the on-demand SIB1 and sends an indication signaling. Exemplarily, the indication signaling is RAR.

[0306] The base station determines, based on at least one of the following methods, an event request that can be jointly requested with the on-demand SIB1. Optionally, the method includes at least one of the following: predefinition, signaling configuration, and terminal capability indication. Optionally, the event request that can be jointly requested with the on-demand SIB1 includes at least one of the following: RRC Connection Setup Request (RRCSetupRequest), RRC Resume Setup Request (RRCResumeRequest), RRC Resume Setup Request 1 (RRCResumeRequest1), RRC Reestablishment Request (RRCReestablishmentRequest), and OSI Request (RRCSystemInfoRequest).

[0307] The base station distinguishes the event requests carried by multiple CCCHs based on at least one of the following methods: CCCH corresponding LCID, CCCH indication signaling, and RACH resources. Exemplarily, different event request combinations are associated with different RACH resources.

[0308] In some embodiments, the terminal sends Msg3 to the base station and requests the corresponding downlink signal and / or downlink channel through the request information carried by Msg3.

[0309] Optionally, assuming that the base station supports network energy-saving technologies, the base station can choose to stop transmitting some downlink signals and / or downlink channels based on network load, the number of resident terminals, service type, and / or service period. The base station's decision-making process and strategy for whether to transmit some downlink signals and / or downlink channels are not limited. Upon receiving the indication information sent by the terminal, the base station can choose to resume transmitting downlink signals or channels based on the terminal's request information.

[0310] Optionally, based on the terminal request, the base station determines to send at least one of the following downlink signals and / or downlink channels: SSB; IB1, TRS, PDCCH, PDSCH; CSI-RS; and other newly defined downlink reference signals, such as PSS+SSS, DRS, etc.

[0311] Optionally, taking the downlink signal requested by the terminal as SIB1 as an example, in addition to the above-mentioned on demand SIB1 information, the terminal may also initiate request information of other events based on the request information carried by Msg3, and the request information of other events includes at least one of the following: RRC connection establishment request (RRCSetupRequest); RRC connection establishment request (RRCSetupRequest), RRC recovery establishment request (RRCResumeRequest), (RRC recovery establishment request 1RRCResumeRequest1), RRC reestablishment request (RRCReestablishmentRequest), other system message (Other SI, OSI) request (RRCSystemInfoRequest); DL or UL data arrival (when the UL synchronization status is "asynchronous", during the RRC connected state or during the inactive state, and small data packet transmission (SDT) transmission is in progress) (i.e. DL or UL data arrival, during RRC_CONNECTED or during RRC_INACTIVE while SDT procedure is ongoing, when UL synchronisation status is "non-synchronised"); UL data arrival, during RRC_CONNECTED or during RRC_INACTIVE while SDT procedure is ongoing, when there are no PUCCH resources for SR scheduling; Handover; Scheduling request (SR) failure; Explicit request by RRC upon synchronous reconfiguration; To establish time alignment for a primary or a secondary TAG; Beam failure recovery;Consistent UL LBT failure on SpCell; SDT in RRC_INACTIVE; Positioning purpose during RRC_CONNECTED requiring random access procedure (e.g., UE positioning requires timing information); Early UL synchronization with an LTM candidate cell; and RACH-based LTM cell switch.

[0312] Optionally, the terminal mainly considers sending the above request information based on Msg3. In addition to Msg3, the terminal can also send the request information based on other uplink channels and / or uplink signals, for example, the above information can be sent through a preamble, PUSCH and / or PUCCH, which is not limited here.

[0313] Optionally, Msg3 may be information transmitted via a Cell Radio Network Temporary Identifier (C-RNTI) MAC CE or CCCH SDU carried over the UL-SCH. This information is sent by the terminal to the base station and is related to the UE Contention Resolution Identity. The process of sending Msg3 is part of the random access process. The CCCH SDU may be a MAC SDU.

[0314] Optionally, the request information for the event carried by Msg.3 may refer to the request information for the event carried by the terminal based on the MAC CE or CCCH SDU carried by the UL-SCH. To simplify the description, the CCCH SDU is used as an example to illustrate the solution of the embodiment of the present disclosure; it is worth noting that other logical channels or MAC CEs are also within the scope of protection of the embodiment of the present disclosure.

[0315] 1. Example 1 (Example 1 includes Example 1-1, Example 1-2, Example 1-3, Example 1-4 and / or Example 1-5):

[0316] To enable the transmission of request information for multiple events, including on-demand SIB1, the terminal can carry the request information for each of these events using different CCCH SDUs carried by different MAC subPDUs. The CCCH SDUs correspond one-to-one with the event request information. Alternatively, different MAC subPDUs can be carried by the same MAC PDU. For example, as shown in Figure 1F, a MAC subPDU can include: a MAC SDU, a MAC CE, or padding.

[0317] Exemplarily, the UL-CCCH corresponds to only one specific LCID, and request information of multiple events can be carried based on the UL-CCCH corresponding to the same LCID.

[0318] For example, considering that CCCH may carry request information of different events, CCCH may correspond to different LCID numbers, and different LCIDs correspond to request information of different events.

[0319] 1. Example 1-1. Example 1-1 includes at least one of the following:

[0320] The terminal carries the on-demand SIB1 based on the UL-CCCH-Message. The LCID corresponding to the UL-CCCH-Message is the same as the existing CCCH channel; for example, LCID index = 52, or LCID index = 35. The UL-CCCH-Message carries 48 bits of RRC signaling. For details about the UL-CCCH-Message, please refer to the relevant technology.

[0321] (1) Implementation method 1: The terminal indicates the corresponding on-demand SIB1 request based on the message class extension indication (messageClassExtension) field of the UL-CCCH message.

[0322] Correspondingly, if the base station receives two UL-CCCH Messages based on different MAC SDUs, one of which is an rrcsetuprequest and the other is an on demand SIB1 request corresponding to the messageClassExtension field, the base station determines that two event requests are received.

[0323] (2) Implementation method 2: The terminal indicates the corresponding on demand SIB1 request based on the reserved (spare) bit and / or spare status of the UL-CCCH Message. The spare bit and / or spare status can be configured based on one or more of the following information fields: RRC connection establishment request (RRCSetupRequest), RRC recovery establishment request (RRCResumeRequest), (RRC recovery establishment request 1RRCResumeRequest1), RRC re-establishment request (RRCReestablishmentRequest) and other system message (Other SI, OSI) request (RRCSystemInfoRequest).

[0324] Taking RRCSetupRequest as an example, on demand SIB1 can be indicated based on the spare bit (such as spare field) of RRCSetupRequest, or based on the spare status (such as spare1, spare2, ..., or spare6, etc.) of RRCSetupRequest.

[0325] Taking RRCSetupRequest as an example, if the spare bit or spare status indicator is 0, the base station determines that the terminal initiates an RRC connection establishment request. If the spare bit or spare status indicator is 1, the base station determines that the terminal initiates an on-demand SIB1 request.

[0326] Correspondingly, if the base station receives two UL-CCCH Messages based on different MAC SDUs; one of them is rrcsetuprequest and the corresponding spare bit or spare status indicator is 0; the other is rrcsetuprequest and the corresponding spare bit or spare status indicator is 1; the base station determines that both the RRC connection establishment request and the on demand SIB1 request are received;

[0327] Taking RRCSetupRequest as an example, if the spare bit or spare status indication is 0, the base station determines that the terminal initiates an RRC connection establishment request; or, if the spare bit or spare status indication is 1, the base station determines that the terminal initiates an RRC connection establishment request and an on demand SIB1 request at the same time.

[0328] For information fields such as RRCResumeRequest, RRCReestablishmentRequest, and RRCSystemInfoRequest, the rules are similar to those for RRCSetupRequest and will not be repeated here.

[0329] (3) Implementation method 3: defining an on-demand SIB1 specific message, for example, defining an RRC SIB1 request message (RRCSIB1Request Message); the defined on-demand SIB1 specific message is carried based on a UL-CCCH-Message bearer, for example, based on a c1 bearer of a UL-CCCH-MessageType.

[0330] Correspondingly, the base station receives Msg3, and if it is determined that the corresponding UL-CCCH-Message corresponding to c1 indicates that the MessageType type is a SIB1 corresponding message, the base station determines that the terminal initiates an on-demand SIB1 request.

[0331] For example, the percentage of messages corresponding to on demand SIB1 request is 45.

[0332] 2. Example 1-2:

[0333] The terminal carries the on-demand SIB1 based on a UL-CCCH message (e.g., a UL-CCCH2 message). The LCID corresponding to the UL-CCCH2 message is different from that of the existing CCCH channel. For example, the LCID index corresponding to the UL-CCCH2 message is any one from 37 to 42, such as LCID index = 37. Another example is that the UL-CCCH2 message is defined based on an eLCID, such as any one from 64 to 292, such as eLCID index = 64.

[0334] Exemplarily, the number of bits occupied by the UL-CCCH2 message is 48 bits. Exemplarily, the number of bits occupied by the UL-CCCH2 message is 64 bits.

[0335] Correspondingly, the base station receives the MAC SDU. If the MAC SDU corresponds to an LCID index corresponding to a UL-CCCH2 message, the base station determines that the UL-CCCH2 message carries the on-demand SIB1 in response.

[0336] 3. Embodiments 1-3. Embodiments 1-3 include at least one of the following:

[0337] The terminal carries the on-demand SIB1 request based on the UL-CCCH1-Message. The LCID corresponding to the UL-CCCH1-Message is the same as the existing CCCH1 channel; for example, LCID index = 0, or LCID index = 36. The UL-CCCH1-Message carries 64 bits of RRC signaling. For details about the UL-CCCH1-Message, please refer to the relevant technology.

[0338] (1) Implementation method 1: The terminal indicates the corresponding on-demand SIB1 request based on the message class extension indication (messageClassExtension) field of the UL-CCCH1 message.

[0339] Correspondingly, if the base station receives two UL-CCCH1 Messages based on different MAC SDUs, one of which is rrcResuemeRequest1 and the other is an on demand SIB1 request corresponding to the messageClassExtension field; the base station determines that two event requests are received.

[0340] (2) Implementation 2: The terminal indicates the corresponding on-demand SIB1 request based on the spare field of the UL-CCCH1 Message. The spare field may be the spare1, spare2, or spare3 field in the UL-CCCH1-Message.

[0341] Exemplarily, if the spare field indicates 1, it indicates that the terminal initiates an on demand SIB1 request.

[0342] Exemplarily, an on-demand SIB1 specific message is defined, for example, an RRC SIB1 request message is defined; the defined on-demand SIB1 specific message is based on a UL-CCCH1-Message bearer, for example, based on a c1 bearer of a UL-CCCH1-MessageType.

[0343] Correspondingly, the base station receives Msg3, and if it is determined that the corresponding UL-CCCH1-Message corresponding to c1 indicates that the MessageType type is a SIB1 corresponding message, the base station determines that the terminal initiates an on demand SIB1 request.

[0344] For example, the percentage of messages corresponding to on-demand SIB1 requests is 61.

[0345] 4. Examples 1-4:

[0346] Define on-demand SIB1 specific RACH resources. RACH resources include the RO where the preamble is sent and one or more preamble sending channels.

[0347] Exemplarily, when the terminal sends the corresponding on-demand SIB1 request based on Msg3 and / or UL-CCCH, the terminal first sends Msg1 based on the on-demand SIB1 specific RACH resources.

[0348] Correspondingly, if the base station receives Msg3 and / or UL-CCCH and determines that the Msg3 and / or UL-CCCH correspond to the on-demand SIB1-specific RACH resources, the base station determines to receive the on-demand SIB1 request.

[0349] 5. Examples 1-5:

[0350] The base station indicates, based on the RAR signaling, whether to allow initiation of the on-demand SIB1 request, and / or indicates the time-frequency domain resources and / or CCCH for which initiation of the on-demand SIB1 request is allowed.

[0351] Exemplarily, taking CCCH as an example, the base station indicates based on RAR signaling that the CCCH for on-demand SIB1 is allowed to be initiated; for example, the LCID number of the CCCH for on-demand SIB1 is indicated.

[0352] Exemplarily, the CCCH that allows initiation of the on-demand SIB1 request is predefined. For example, the LCID index of the CCCH that allows initiation of the on-demand SIB1 request is predefined as 37.

[0353] Exemplarily, the RAR signaling indication may be based on the R field indication of the MAC RAR. For example, if the corresponding R field indication is 1, the terminal may initiate an on-demand SIB1 request based on the CCCH.

[0354] For example, a newly defined MAC RAR is introduced. Based on the MAC RAR, the base station indicates one or more CCCHs that allow the terminal to initiate an on-demand SIB1 request. For example, the LCID index of the CCCH that allows the terminal to initiate an on-demand SIB1 request is 37 and / or 38. If the terminal sends a request based on this CCCH, the base station confirms receipt of the on-demand SIB1 request.

[0355] 2. Example 2:

[0356] To implement the sending of request information for multiple events, including on-demand SIB1, the terminal can carry the above request information based on the same MAC subPDU, which can include a CCCH SDU (i.e., MAC SDU) or a MAC CE. Alternatively, the terminal can carry the above request information based on different MAC subPDUs, which can include a CCCH SDU or a MAC CE.

[0357] In a possible implementation, the terminal may carry the on-demand SIB1 request based on the spare bit of the existing information field. The specific implementation is similar to the implementation 2 of the above embodiment 1-1 and will not be repeated here.

[0358] In one possible implementation, a RACH resource specific to on-demand SIB1 is defined. If the terminal wants to initiate an on-demand SIB1 request, the terminal sends Msg1 based on the RACH resource. The specific implementation is similar to that of the above embodiments 1-4 and will not be described again here.

[0359] In a possible implementation, the terminal determines whether to initiate an on-demand SIB1 request and / or initiate a CCCH for an on-demand SIB1 request based on an RAR signaling indication. The specific implementation is similar to that of the above embodiments 1-5 and will not be described again here.

[0360] 3. Example 3. Example 3 includes at least one of the following:

[0361] To reduce request latency, in addition to the aforementioned on-demand SIB1 request, the terminal can also initiate other event requests based on request information carried by CCCH or MAC CE. The event requests that can be jointly requested with the on-demand SIB1 can be based on the event requests in the aforementioned embodiments and will not be further described here.

[0362] For example, considering the possibility of application scenarios and the limitations of base station processing complexity, it is necessary to define events that the terminal can jointly request; for example, it is possible to define an event that can be jointly requested with on demand SIB1 based on one or more of the following methods: a predefined method, a signaling configuration (i.e., the indication signaling method in the above embodiment), and a terminal capability indication.

[0363] (1) Implementation 1: The terminal determines, based on signaling configuration, events that can be jointly requested with SIB1. This signaling may be SIB1 or configured based on WUS configuration. Alternatively, this signaling may be RAR signaling; for example, the events that can be jointly requested may be indicated based on an existing MAC RAR or a newly defined MAC RAR.

[0364] (2) Implementation 2: Define the terminal's capabilities based on the events of the joint request. The terminal reports the supported combinations of events for the joint request based on its capability report (e.g., the capability information reported in the previous embodiment). Correspondingly, the base station determines the combinations of events that can be jointly requested based on the terminal's capability report.

[0365] Exemplarily, the terminal reports the supported capabilities based on different preambles; Exemplarily, the base station indicates the preamble corresponding to the event that can be jointly requested based on existing signaling, for example, based on the spare field of the feature combination (FeatureCombination) or newly defined signaling to indicate the event of the joint request; based on the feature combination preamble list (FeatureCombinationPreambles) signaling or newly defined signaling to indicate the preamble resources corresponding to the event combination. The terminal determines the preamble resources corresponding to the combination of supported events based on the signaling indication, and requests the corresponding event combination based on the above preamble resources.

[0366] Correspondingly, the base station receives a combination of corresponding events based on the preamble resources.

[0367] (3) Implementation 3: The terminal determines a combination of one or more events that can be jointly requested based on predefined rules, and requests the required events based on needs and the method in the embodiment of the present disclosure.

[0368] For example, taking on-demand SIB1 as an application scenario, the embodiments of the present disclosure can implement terminal joint request for on-demand SIB1 and other event requests, which can effectively reduce the complexity of terminal request operations and reduce request latency.

[0369] In some embodiments, a terminal supporting network energy conservation initiates multiple event requests, including on-demand SIB1, during a random access process to request SIB1 transmission and other events. A base station supporting network energy conservation receives multiple event requests, including on-demand SIB1. Optionally, the base station may determine multiple event requests, including demand SIB1.

[0370] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, and may also be arbitrarily combined with the optional implementations of other embodiments.

[0371] 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.

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

[0373] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP); in another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit, and the logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable, such as a hardware circuit implemented by a processor as 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 a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0374] Figure 5A is a structural diagram of a terminal 5100 provided in an embodiment of the present disclosure. As shown in Figure 5A, the terminal 5100 includes: a first transceiver module 5101 and a first processing module 5102. In some embodiments, the first transceiver module 5101 is used to send request information. Optionally, the above-mentioned first transceiver module 5101 is used to execute at least one of the steps of receiving and / or sending (such as step S2102, but not limited to this) executed by the terminal in any of the above methods, which will not be repeated here. In some embodiments, the first processing module 5102 is used to determine at least one event that can be jointly requested. Optionally, the above-mentioned first processing module 5102 is used to execute at least one of the steps of processing (such as step S2101, but not limited to this) executed by the terminal in any of the above methods, which will not be repeated here.

[0375] Figure 5B is a schematic structural diagram of a network device 5200 provided in an embodiment of the present disclosure. As shown in Figure 5B, the network device 5200 includes: a second transceiver module 5201 and a second processing module 5202. Optionally, the second transceiver module 5201 is used to receive request information. Optionally, the second transceiver module 5201 is used to perform at least one of the steps of sending and / or receiving (such as step S2102, but not limited to this) performed by the network device 5200 in any of the above methods, which will not be repeated here. In some embodiments, the second processing module 5202 is used to determine at least one event that can be jointly requested. Optionally, the second processing module is used to perform at least one of the steps of processing (such as step S2101, but not limited to this) performed by the network device 5200 in any of the above methods, which will not be repeated here.

[0376] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module. The transmitting module and the receiving module may be separate or integrated. Optionally, the transceiver module and the transceiver may be interchangeable. Exemplarily, the first transceiver module includes a first transmitting module and / or a first receiving module. Exemplarily, the second transceiver module includes a second transmitting module and / or a second receiving module.

[0377] In some embodiments, the processing module can be a single module or can include multiple submodules. Optionally, the multiple submodules respectively execute all or part of the steps required to be executed by the processing module. Optionally, the processing module can be interchangeable with the processor.

[0378] Figure 6A is a schematic diagram of the structure of a communication device 6100 proposed in an embodiment of the present disclosure. Communication device 6100 can be a network device (e.g., an access network device, a core network device, etc.), a terminal, etc., or a chip, chip system, or processor that supports a network device in implementing any of the above methods. It can also be a chip, chip system, or processor that supports a terminal in implementing any of the above methods. Communication device 6100 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.

[0379] As shown in Figure 6A, the communication device 6100 includes one or more processors 6101. The processor 6101 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 6100 is used to perform any of the above methods. Optionally, one or more processors 6101 are used to call instructions to enable the communication device 6100 to perform any of the above methods.

[0380] In some embodiments, the communication device 6100 further includes one or more transceivers 6102. When the communication device 6100 includes one or more transceivers 6102, the transceiver 6102 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps S2102 and / or step S2103 and / or step S2104, but not limited thereto), and the processor 6101 performs at least one of the other steps (e.g., steps S2101 and / or step S2103, 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.

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

[0382] The communication device 6100 described in the above embodiment may be a network device or a terminal, but the scope of the communication device 6100 described in the present disclosure is not limited thereto, and the structure of the communication device 6100 may not be limited to FIG6A. 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 and 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.

[0383] 6B is a schematic diagram of the structure of a chip 6200 according to an embodiment of the present disclosure. If the communication device 6100 can be a chip or a chip system, reference can be made to the schematic diagram of the structure of the chip 6200 shown in FIG6B , but the present disclosure is not limited thereto.

[0384] The chip 6200 includes one or more processors 6201. The chip 6200 is configured to execute any of the above methods.

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

[0386] In some embodiments, the interface circuit 6202 performs at least one of the communication steps, such as sending and / or receiving, in the above-described method (e.g., steps S2101 and / or S2103, but not limited thereto). The interface circuit 6202 performing the communication steps, such as sending and / or receiving, in the above-described method, for example, means that the interface circuit 6202 performs data exchange between the processor 6201, the chip 6200, the memory 6203, or the transceiver device. In some embodiments, the processor 6201 performs at least one of the other steps (e.g., steps S2102, but not limited thereto).

[0387] 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.

[0388] The present disclosure also proposes a storage medium having instructions stored thereon. When the instructions are executed on the communication device 6100, the communication device 6100 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 transient storage medium.

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

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

Claims

1. An information processing method, characterized in that: Executed by the terminal, including: Sending request information to the network device, wherein the request information is used to request the network device to send the first downlink information and other events except sending the first downlink information.

2. The method according to claim 1, characterized in that The request information includes: first request information; the first request information is used to request the first downlink information and other events except sending the first downlink information.

3. The method according to claim 1, characterized in that The request information includes: first request information and second request information; wherein the first request information is used to request the first downlink information, and the second request information is used to request other events except sending the first downlink information.

4. The method according to any one of claims 1 to 3, characterized in that The other events other than sending the first downlink information include at least one of the following: Radio Resource Control RRC connection establishment request; RRC recovery establishment request; RRC recovery establishment request 1; RRC re-establishment request; RRC system message request.

5. The method according to any one of claims 1 to 4, characterized in that The sending of the request information to the network device includes at least one of the following: Sending request information for different events based on different logical channels; Sending request information for different events based on different media access control information elements MAC CE; Sending first request information, where the first request information includes first indication information indicating a request event; Sending second request information, where the second request information includes first indication information indicating a request event; Sending request information requesting a different request event based on the second indication information sent by the network device; Based on different preambles and / or physical random access channel (PRACH) resources, request information requesting different events is sent.

6. The method according to claim 5, characterized in that The different logical channels correspond to different logical channel numbers LCID, and / or the different logical channels are carried based on different MAC service data units SDU; and / or, The different MAC CEs correspond to different logical channel numbers LCID, and / or the different MAC CEs are carried based on different MAC subPDUs.

7. The method according to claim 5, characterized in that The first indication information indicating the request event is based on at least one of the following signaling indications: Reserve spare area; Spare bits; Reserved status; Information type extended indication field; Information type indicator field.

8. The method according to claim 5, characterized in that The second indication information sent by the network device is based on at least one of the following signaling indications: Random access response RAR signaling; System information; Request information configuration.

9. The method according to claim 5, characterized in that The request information of different request events corresponds to different preambles and / or PRACH resources.

10. The method according to any one of claims 1 to 9, characterized in that The request information includes at least one of the following: Msg3; Msg1; MsgA; MAC CE; Preamble.

11. The method according to any one of claims 1 to 10, characterized in that The method further includes determining at least one event capable of being combined with the request based on at least one of the following methods: Indication signaling; Predefined method; Terminal capability reporting.

12. An information processing method, characterized in that: Performed by network devices, including: Receive request information sent by the terminal, wherein the request information is used to request the network device to send the first downlink information and other events except sending the first downlink information.

13. The method according to claim 12, characterized in that The request information includes: first request information; the first request information is used to request the first downlink information and other events except sending the first downlink information.

14. The method according to claim 12, characterized in that The request information includes: first request information and second request information; wherein the first request information is used to request the first downlink information, and the second request information is used to request other events except sending the first downlink information.

15. The method according to any one of claims 12 to 14, characterized in that The other events other than sending the first downlink information include at least one of the following: Radio Resource Control RRC connection establishment request; RRC recovery establishment request; RRC recovery establishment request 1; RRC re-establishment request; RRC system message request.

16. The method according to any one of claims 12 to 15, characterized in that The request information sent by the receiving terminal includes at least one of the following: Based on different logical channels, receiving request information for different events sent by the terminal; receiving, based on different media access control information elements MAC CE, request information for different events sent by the terminal; receiving first request information sent by a terminal, where the first request information includes first indication information indicating a request event; receiving second request information sent by the terminal, where the second request information includes first indication information indicating a request event; The receiving terminal sends request information for different events based on different preambles and / or physical random access channel PRACH resources.

17. The method according to claim 16, characterized in that The different logical channels correspond to different logical channel numbers LCID, and / or the different logical channels are carried based on different MAC service data units SDU; and / or, The different MAC CEs correspond to different logical channel numbers LCID, and / or the different MAC CEs are carried based on different MAC subPDUs.

18. The method according to claim 16, characterized in that The first indication information indicating the request event is based on at least one of the following signaling indications: Reserve spare area; Spare bits; Reserved status; Information type extended indication field; Information type indicator field.

19. The method according to claim 16, wherein The method further includes: sending second indication information to the terminal, where the second indication information is used by the terminal to send request information requesting a different event.

20. The method according to claim 19, characterized in that The second indication information is based on at least one of the following signaling indications: Random access response RAR signaling; System information; Request information configuration.

21. The method according to claim 16, wherein The request information of different request events corresponds to different preambles and / or PRACH resources.

22. The method according to any one of claims 12 to 21, characterized in that The request information includes at least one of the following: Msg3; Msg1; MsgA; MAC CE; Preamble.

23. The method according to any one of claims 12 to 21, characterized in that The method further includes determining at least one event capable of being combined with the request based on at least one of the following methods: Indication signaling; Predefined method; Terminal capability reporting.

24. A terminal, characterized in that: include: The first transceiver module is configured to send request information to the network device, wherein the request information is used to request the network device to send the first downlink information and other events except sending the first downlink information.

25. A network device, characterized in that: include: The second transceiver module is configured to receive request information sent by the terminal, wherein the request information is used to request the network device to send the first downlink information and other events except sending the first downlink information.

26. A communication device, characterized in that: include: one or more processors; The communication device is used to execute the information processing method according to any one of claims 1 to 11 or claims 12 to 23.

27. A communication system, characterized in that: include: A terminal and a network device; wherein the terminal is configured to implement the information processing method according to any one of claims 1 to 11, and the network device is configured to implement the information processing method according to any one of claims 12 to 23.

28. A storage medium storing instructions, characterized in that: When the instruction is executed on a communication device, the communication device is caused to execute the information processing method according to any one of claims 1 to 11 or claims 12 to 23.

29. A computer program product, comprising a computer program or instructions, characterized in that: When the computer program or instruction is executed by a processor, the information processing method according to any one of claims 1 to 11 or claims 12 to 23 is implemented.

Images