Request information processing method, communication device, and storage medium

Abstract

Embodiments of the present disclosure provide a request information processing method, a communication device, a communication system, and a storage medium. The request information processing method, which is executed by a terminal, may comprise: receiving a first configuration of a configured grant physical uplink shared channel (CG-PUSCH) sent by a network device; and, on the basis of the first configuration, sending request information on the CG-PUSCH to the network device, the request information being used for requesting the network device to send downlink transmission to the terminal.

Description

Request information processing method, communication device and storage medium Technical Field

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

[0002] To reduce network power consumption, related technologies have proposed on-demand signal transmission technology. This on-demand signal can be a synchronization signal broadcast block (SSB) and / or a system information block (SIB). Based on traffic conditions or power consumption, network devices will stop sending these signals for a period of time, thereby achieving energy conservation.

[0003] Summary of the Invention

[0004] Embodiments of the present disclosure provide a request information processing method, a communication device, and a storage medium.

[0005] According to a first aspect of an embodiment of the present disclosure, a request information processing method is provided, which is executed by a terminal, and the method includes: receiving a first configuration of a configured grant-Physical Uplink Shared Channel (CG-PUSCH) sent by a network device; according to the first configuration, sending request information to the network device on the CG-PUSCH; the request information is used to request the network device to send a downlink transmission to the terminal.

[0006] According to a second aspect of an embodiment of the present disclosure, a request information processing method is provided, which is executed by a network device and includes: sending a first configuration of configuring an authorized physical uplink shared channel CG-PUSCH to a terminal; according to the first configuration, receiving request information sent by the terminal on the CG-PUSCH; the request information is used to request the network device to send a downlink transmission to the terminal.

[0007] According to a third aspect of an embodiment of the present disclosure, a terminal is provided, wherein the terminal includes: a receiving module configured to receive a first configuration of a configuration authorization physical uplink shared channel CG-PUSCH sent by a network device; a sending module configured to send request information to the network device on the CG-PUSCH according to the first configuration; the request information is used to request the network device to send a downlink transmission to the terminal.

[0008] According to a fourth aspect of an embodiment of the present disclosure, a network device is provided, wherein the network device includes: a sending module, configured to send a first configuration of configuring an authorized physical uplink shared channel CG-PUSCH to a terminal; a receiving module, configured to receive request information sent by the terminal on the CG-PUSCH according to the first configuration; the request information is used to request the network device to send a downlink transmission to the terminal.

[0009] According to a fifth aspect of an embodiment of the present disclosure, a communication device is provided, wherein the communication device includes: one or more processors; wherein the processor is used to call instructions so that the communication device executes the request information processing method provided by any technical solution of the aforementioned first to second aspects.

[0010] According to the sixth aspect of an embodiment of the present disclosure, a storage medium is provided, wherein the storage medium stores instructions, which, when the instructions are executed on a communication device, enable the communication device to execute the request information processing method provided by any aspect from the first aspect to the second aspect.

[0011] The technical solution provided by the embodiment of the present disclosure allows the terminal to send a request corresponding to the downlink transmission on the CG-PUSCH, so that the network device does not need to provide additional resource configuration for sending the request information, which has the characteristic of simple implementation.

[0012] It should be understood that the foregoing general description and the following detailed description are merely exemplary and explanatory and are not restrictive of the embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the present disclosure and, together with the description, serve to explain the principles of the embodiments of the present disclosure.

[0014] FIG1A is a schematic diagram showing an architecture of a communication system according to an exemplary embodiment;

[0015] FIG1B is a schematic diagram showing time domain transmission of SSB / SIB according to an exemplary embodiment;

[0016] FIG1C is a schematic structural diagram of an SSB according to an exemplary embodiment;

[0017] FIG1D is a frequency domain schematic diagram of SSB according to an exemplary embodiment;

[0018] FIG1E is a frequency domain schematic diagram of SSB according to an exemplary embodiment;

[0019] FIG1F is a schematic diagram showing candidate time-domain positions of an SSB according to an exemplary embodiment;

[0020] FIG1G is a schematic diagram showing a type 1 CG-PUSCH according to an exemplary embodiment;

[0021] FIG1H is a schematic diagram showing a type 2 CG-PUSCH according to an exemplary embodiment;

[0022] FIG1I is a schematic diagram showing a CG-PUSCH-like opportunity according to an exemplary embodiment;

[0023] FIG2A is a flow chart showing a method for processing request information according to an exemplary embodiment;

[0024] FIG2B is a schematic diagram showing a configuration of SIB1 according to an exemplary embodiment;

[0025] FIG2C is a schematic diagram showing a configuration of a physical downlink control channel (PDCCH) according to an exemplary embodiment;

[0026] FIG2D is a schematic diagram showing a configuration of a CG-PUSCH for small data transmission according to an exemplary embodiment;

[0027] FIG2E is a schematic diagram showing another configuration of a CG-PUSCH for small data transmission according to an exemplary embodiment;

[0028] FIG3 is a flow chart showing a method for processing request information according to an exemplary embodiment;

[0029] FIG4 is a flow chart showing a method for processing request information according to an exemplary embodiment;

[0030] FIG5A is a flow chart showing a method for processing request information according to an exemplary embodiment;

[0031] FIG5B is a schematic diagram showing a time domain comparison of the second type CG-PUSCH and the third type CG-PUSCH according to an exemplary embodiment;

[0032] FIG5C is a schematic diagram showing a fourth type of CG-PUSCH according to an exemplary embodiment;

[0033] FIG5D is a schematic diagram of a Media Access Control (MAC) Control Element (CE) for requesting information according to an exemplary embodiment;

[0034] FIG5E is a schematic diagram showing correspondence between CG-PUSCH timing and SSB index according to an exemplary embodiment;

[0035] FIG6A is a schematic structural diagram of a terminal according to an exemplary embodiment;

[0036] FIG6B is a schematic structural diagram of a network device according to an exemplary embodiment;

[0037] FIG7A is a schematic structural diagram of a communication device according to an exemplary embodiment;

[0038] FIG7B is a schematic structural diagram of a chip according to an exemplary embodiment. DETAILED DESCRIPTION

[0039] Embodiments of the present disclosure provide a request information processing method, a communication device, and a storage medium.

[0040] The first aspect provides a request information processing method, which is executed by a terminal, and the method includes: receiving a first configuration of CG-PUSCH sent by a network device; according to the first configuration, sending request information to the network device on CG-PUSCH; the request information is used to request the network device to send downlink transmission to the terminal.

[0041] Based on the above solution, the terminal can send the corresponding downlink transmission request on the CG-PUSCH. This allows the network device to simplify implementation without additional resource configuration for sending the request information. In some embodiments of the first aspect, the request information includes at least one of the following: a first indication for requesting the transmission of a downlink transmission; a second indication for indicating the type of the downlink transmission requested; a third indication for indicating the index of the downlink transmission requested; and a fourth indication for indicating beam information of a desired beam for the downlink transmission.

[0042] Based on the above solution, the terminal can flexibly set the information content of the request information according to its own needs, so that the network device can better send downlink transmission to the terminal according to the request information.

[0043] In some embodiments of the first aspect, any two or more of the first indication, the second indication, the third indication, and the fourth indication share a common indication field; or, the first indication, the second indication, the third indication, and the fourth indication use different indication fields. In some embodiments, the field corresponding to any one of the first to fourth indications can be flexibly defined according to the two aforementioned methods.

[0044] In some embodiments of the first aspect, CG-PUSCH includes at least one of the following: a first type CG-PUSCH, a second type CG-PUSCH, a third type CG-PUSCH and a fourth type CG-PUSCH; at least one of the configuration method, activation method and configuration parameters of the first type CG-PUSCH, the second type CG-PUSCH, the third type CG-PUSCH and the fourth type CG-PUSCH is different.

[0045] Based on the above solution, the CG-PUSCH for sending the request information can be any of the above types, thereby facilitating flexible selection of network devices and / or terminals.

[0046] In some embodiments of the first aspect, the first type CG-PUSCH and the fourth type CG-PUSCH are configured by a radio resource control RRC message; and the CG-PUSCH timing CGO of the fourth type CG-PUSCH is associated with a beam; the second type CG-PUSCH and the third type CG-PUSCH are configured by an RRC message, and the second type CG-PUSCH and the third type CG-PUSCH are activated by different signaling.

[0047] In some embodiments of the first aspect, the second type CG-PUSCH is activated by a first signaling; the first signaling includes specific downlink control information (DCI). The third type CG-PUSCH is activated by a second signaling; the second signaling includes a common DCI and / or notification signaling;

[0048] Notification signaling, used to notify the start or stop of the first transmission; the start of the first transmission corresponds to the deactivation of the third type CG-PUSCH; the stop of the first transmission corresponds to the activation of the third type CG-PUSCH.

[0049] In some embodiments of the first aspect, the first second type CG-PUSCH for sending the request information is determined by the reception time of the first signaling and K2 time units; and / or, the first third type CG-PUSCH for sending the request information is determined by the reception time of the second signaling.

[0050] In some embodiments of the first aspect, the first configuration for the first type of CG-PUSCH indicates at least one of the following: the period of the first type of CG-PUSCH; the time domain offset of the first type of CG-PUSCH, indicating the offset of the first resource position of the first type of CG-PUSCH relative to the reference time; the first configuration for the second type of CG-PUSCH indicates at least: the period of the second type of CG-PUSCH; the first configuration for the third type of CG-PUSCH indicates at least one of the following: the period of the third type of CG-PUSCH; the time domain offset of the third type of CG-PUSCH, indicating the offset of the first resource position of the third type of CG-PUSCH relative to the reference time; the first configuration for the fourth type of CG-PUSCH indicates at least one of the following: the period of the fourth type of CG-PUSCH; the time domain offset of the fourth type of CG-PUSCH, indicating the offset of the first resource position of the fourth type of CG-PUSCH relative to the reference time.

[0051] In some embodiments of the first aspect, the first type CG-PUSCH, the third type CG-PUSCH, and the fourth type CG-PUSCH are all shared by multiple terminals. Different terminals use different demodulation reference signal DMRS ports when using the same CG-PUSCH, that is, different terminals use different demodulation reference signal (DMRS) ports to send request information on the same CG-PUSCH.

[0052] In some embodiments of the first aspect, the second signaling further includes at least one of the following: time domain resource location information of the third type CG-PUSCH; frequency domain resource location information of the third type CG-PUSCH.

[0053] In some embodiments of the first aspect, the first configuration of the third type CG-PUSCH further includes: time domain resource location information of the third type CG-PUSCH; and frequency domain resource location information of the third type CG-PUSCH.

[0054] In some embodiments of the first aspect, according to the first configuration, sending request information to the network device on the CG-PUSCH includes:

[0055] Ignore the second configuration sent by the network device, and send request information to the network device on the CG-PUSCH according to the first configuration; the second configuration is a configuration indicating that the network device is in the network node NES state.

[0056] Based on the above solution, the second configuration sending request information is ignored, so that the terminal can request downlink transmission in time, and the network device can send the downlink transmission requested by the terminal in time.

[0057] In some embodiments of the first aspect, the second configuration includes at least one of the following:

[0058] Cell discontinuous reception (DRX) configuration;

[0059] Cell discontinuous transmission (DTX) DTX configuration.

[0060] In some embodiments of the first aspect, the downlink transmission includes at least:

[0061] SSB;

[0062] SIB.

[0063] A second aspect provides a request information processing method, wherein the method is performed by a network device and includes:

[0064] Sending a first configuration of a configuration grant physical uplink shared channel CG-PUSCH to the terminal;

[0065] According to the first configuration, a request message sent by the terminal is received on the CG-PUSCH; the request message is used to request the network device to send a downlink transmission to the terminal.

[0066] In some embodiments of the second aspect, the request information includes at least one of the following:

[0067] A first indication, used to indicate a request to send a downlink transmission;

[0068] A second indication, used to indicate the type of downlink transmission requested to be sent;

[0069] A third indication is used to indicate the index of the downlink transmission requested to be sent;

[0070] The fourth indication is used to indicate the beam information of downlink transmission.

[0071] In some embodiments of the second aspect, any two or more of the first indication, the second indication, the third indication, and the fourth indication share an indication domain; or, the first indication, the second indication, the third indication, and the fourth indication use different indication domains.

[0072] In some embodiments of the second aspect, the CG-PUSCH includes at least one of the following:

[0073] Type 1 CG-PUSCH, Type 2 CG-PUSCH, Type 3 CG-PUSCH, and Type 4 CG-PUSCH;

[0074] At least one of the configuration method, activation method and configuration parameters of the first type CG-PUSCH, the second type CG-PUSCH, the third type CG-PUSCH and the fourth type CG-PUSCH is different.

[0075] In some embodiments of the second aspect, the first type CG-PUSCH and the fourth type CG-PUSCH are configured by an RRC message; and a CG-PUSCH opportunity CGO of the fourth type CG-PUSCH is associated with a beam;

[0076] The second type CG-PUSCH and the third type CG-PUSCH are configured by an RRC message, and the second type CG-PUSCH and the third type CG-PUSCH are activated by different signaling.

[0077] In some embodiments of the second aspect, the second type CG-PUSCH is activated by first signaling; the first signaling includes specific downlink control information DCI;

[0078] The third type CG-PUSCH is activated by the second signaling; the second signaling includes common DCI and / or notification signaling;

[0079] Notification signaling, used to notify the start or stop of the first transmission; the start of the first transmission corresponds to the deactivation of the third type CG-PUSCH; the stop of the first transmission corresponds to the activation of the third type CG-PUSCH.

[0080] In some embodiments of the second aspect, the first second type CG-PUSCH for sending the request information is determined by the reception time of the first signaling and K2 time units; and / or,

[0081] The first third type CG-PUSCH for sending the request information is determined by the reception time of the second signaling.

[0082] In some embodiments of the second aspect, the first configuration for the first type of CG-PUSCH indicates at least one of the following: a period of the first type of CG-PUSCH; a time domain offset of the first type of CG-PUSCH, indicating an offset of a first resource position of the first type of CG-PUSCH relative to a reference time;

[0083] The first configuration indication for the second type CG-PUSCH: a period of the first type CG-PUSCH;

[0084] The first configuration indication for the third type CG-PUSCH indicates at least one of the following: the period of the third type CG-PUSCH; the time domain offset of the third type CG-PUSCH, indicating the offset of the first resource position of the first type CG-PUSCH relative to the reference time.

[0085] In some embodiments of the second aspect, the first type CG-PUSCH, the third type CG-PUSCH, and the fourth type CG-PUSCH are all shared by multiple terminals. Different terminals use different demodulation reference signal DMRS ports when using the same CG-PUSCH, that is, different terminals use different demodulation reference signal (DMRS) ports to send request information on the same CG-PUSCH.

[0086] In some embodiments of the second aspect, the second signaling further includes at least one of the following:

[0087] Time domain resource location information of the third type CG-PUSCH;

[0088] Frequency domain resource location information of the third type CG-PUSCH.

[0089] In some embodiments of the second aspect, the first configuration of the third type CG-PUSCH further includes:

[0090] Time domain resource location information of the third type CG-PUSCH;

[0091] Frequency domain resource location information of the third type CG-PUSCH.

[0092] In some embodiments of the second aspect, according to the first configuration, receiving request information sent by the terminal on the CG-PUSCH includes:

[0093] Ignore the second configuration, and receive the request information sent by the network device on the CG-PUSCH according to the first configuration; the second configuration is a configuration indicating that the network device is in the network node NES state.

[0094] In some embodiments of the second aspect, the second configuration includes at least one of the following:

[0095] Cell discontinuous reception (DRX) configuration;

[0096] Cell discontinuous transmission DTX configuration.

[0097] In some embodiments of the second aspect, the downlink transmission includes at least:

[0098] SSB;

[0099] SIB.

[0100] A third aspect provides a terminal, wherein the terminal includes:

[0101] A receiving module configured to receive a first configuration of a configuration grant physical uplink shared channel CG-PUSCH sent by a network device;

[0102] The sending module is configured to send request information to the network device on the CG-PUSCH according to the first configuration; the request information is used to request the network device to send downlink transmission to the terminal.

[0103] A fourth aspect provides a network device, wherein the network device includes:

[0104] A sending module configured to send a first configuration of a configuration grant physical uplink shared channel CG-PUSCH to the terminal;

[0105] The receiving module is configured to receive a request message sent by the terminal on the CG-PUSCH according to the first configuration; the request message is used to request the network device to send a downlink transmission to the terminal. In a fifth aspect, an embodiment of the present disclosure provides a communication device, the communication device including: one or more processors;

[0106] The processor is used to call instructions to enable the communication device to execute the request information processing method described in the optional implementation of the first aspect to the second aspect.

[0107] In a sixth aspect, an embodiment of the present disclosure provides a storage medium, wherein the storage medium stores instructions, which, when the instructions are executed on a communication device, enable the communication device to execute the request information processing method described in the optional implementation methods of the first to second aspects.

[0108] In a seventh aspect, an embodiment of the present disclosure provides a program product. When the program product is executed by a communication device, the communication device executes the request information processing method described in the optional implementation of the first to fifth aspects.

[0109] In an eighth aspect, an embodiment of the present disclosure provides a computer program, which, when executed on a computer, enables the computer to execute the request information processing method described in the optional implementation manners of the first to fifth aspects.

[0110] It is understandable that the above-mentioned terminals, network devices, communication systems, program products, and computer programs are all used to execute 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.

[0111] The embodiments of the present disclosure propose a request information processing method, communication equipment, communication system and storage medium. The embodiments of the present disclosure are not exhaustive, but are only 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.

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

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

[0114] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "the", "the", etc., can 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 can be understood as a singular expression or a plural expression.

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

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

[0117] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "in one case A, in another case B," or "in one case A, in 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 same applies when there are more branches such as A, B, and C.

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

[0119] 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 category of information" and the "second category of information" can be the same information or different information, and their contents can be the same or different.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0133] As shown in Figure 1A, a communication system 100 includes a terminal 101 and a network device 102. The network device 102 may include an access network device and / or a core network device.

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

[0135] In some embodiments, the terminal is also referred to as User Equipment (UE).

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

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

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

[0139] In some embodiments, the core network device may be a single device including a first network element, or may be a plurality of devices or a group of devices, each including a first network element. 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).

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

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

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

[0143] Figure 1B shows a schematic diagram of the transmission of SSB and SIB between a terminal and a network device. When the network device is in an energy-saving state, it temporarily stops sending SSB and / or SIB. After the network device stops SSB and / or SIB, if the terminal has an urgent need to receive SSB and / or SIB, it can send a wake-up signal (Wake Up Signal, WUS) to the network device. After receiving the WUS, the network device will decide whether to send SSB.

[0144] As shown in FIG1B , the SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH).

[0145] SSB occupies 4 OFDM symbols in the time domain and 240 consecutive subcarriers in the frequency domain.

[0146] Table 1 may be a configuration of SSB.

[0147] Table 1

[0148] In Table 1, "set to 0" indicates that the complex symbol transmitted by the RE determined for l and k is 0. In the table, v is the cell identity (ID) mod 4. According to Table 1, the SSB time-frequency structure can be determined as shown in FIG1C.

[0149] The absolute frequency domain position of SSB can be determined as follows:

[0150] The frequency domain position k occupied by the SSB can be counted starting from 0. However, when k is 0, the starting position of the subcarrier is determined by the SSB subcarrier spacing (Kssb) parameter. The Kssb parameter indicates the position of subcarrier 0 of the SSB relative to the Common Resource Block (CRB). The offset of subcarrier 0. The value of the Kssb parameter is determined by the higher-layer parameter offsetToPointA. The offsetToPointA parameter may be indicated by SIB1. The value of the Kssb parameter may be indicated by the higher-layer parameter ssb-SubcarrierOffset.

[0151] When the terminal is initially connected, it does not have these parameters to determine the frequency domain position of the SSB, but instead attempts to receive the SSB at a predefined synchronization grid.

[0152] FIG. 1D is a schematic diagram showing how to determine the absolute frequency domain position of an SSB.

[0153] The SSB time domain position can be determined by referring to the following method:

[0154] SSB is sent periodically in the time domain, and its period can be given by the high-level parameter (ssb-periodicityServingCell):

[0155] ssb-periodicityServingCell ENUMERATED{ms5, ms10, ms20, ms40, ms80, ms160, spare2, spare1}.

[0156] It can be seen that the period is an integer multiple of half a frame (5ms). If this parameter is not configured, the terminal assumes a period of 5ms. During initial cell selection, the terminal assumes a period of 2 frames.

[0157] As shown in Figure 1E, in a 5ms half-frame, the base station sends multiple SSBs in all directions. These multiple SSBs have different indexes. These SSBs constitute an SB burst set, and then the SS burst set is sent at the same position in the next cycle.

[0158] For an SSB burst, as shown in Figure 1F, the time domain position of the SSB within the half frame has different possibilities, with a total of five candidate time domain positions. The first symbol position of a candidate SSB is determined by the subcarrier spacing SCS of the SSB. For example, for the case of 15KHz. In an SS Burst Set, the first symbol position of a candidate SSB is {2,8}+14·n. For carrier frequencies below 3GHz, n={0,1}, then the position of the SSB in the first slot is 2,8. At this time, there are 2 candidate SSB positions in an SSB burst; for carrier frequencies above 3GHz, n={0,1,2,3}, that is, 2, 8, 16, 22, 30, 36. At this time, there are 6 candidate SSB positions in an SSB burst.

[0159] In some embodiments, the transmission mechanism of SIB1 may be as follows:

[0160] During initial access,

[0161] In order to facilitate the terminal to monitor the PDCCH that schedules SIB1, the MIB carried by the PBCH of the SSB will include the parameter PDCCH-ConfigSIB1, which contains the control resource set #0 (ControlResourceSetZero) and search space #0 (SearchSpaceZero). According to this parameter, the terminal receives DCI 1_0 scrambled by the System Information-Radio Network Temporary Identity (SI-RNTI). This DCI is used to schedule the PDSCH information that sends SIB1 information. The PDCCH configuration for scheduling PDSCH can be shown in Figure 2B.

[0162] After the terminal establishes an RRC connection with the network device, the network device obtains the CORESET configuration of the PDSCH for scheduling transmission of SIB1 through PDCCH-configCommon in the serving cell common configuration (servingCellConfigCommon).

[0163] The common configuration of the serving cell may be as shown in FIG2C .

[0164] Type 1 CG PUSCH can be as follows:

[0165] The CG PUSCH may be shown in Figure 1G. The basic idea of ​​this type of CG PUSCH is that after resources are configured through configuration parameters, the terminal can use the resources to periodically send data.

[0166] Specifically, type 1 CG PUSCH is configured with at least the following information via RRC:

[0167] DMRS information (cg-DMRS-Configuration);

[0168] Periodicity information (periodicity);

[0169] Scheduling resource information (rrc-ConfiguredUplinkGrant).

[0170] The rrc-ConfiguredUplinkGrant includes the offset parameter that determines the absolute position of the CG PUSCH, as well as the timeDomainAllocation and frequencyDomainAllocation parameters that determine its time-frequency resource block. It also includes transmission beam information, path loss reference signal, DMRS sequence initialization parameters, etc.

[0171] Type 2 CG PUSCH is shown in Figure 1H. This type of CG PUSCH is first configured with parameters such as periodicity via RRC messaging. It is then activated via DCI format 0_0, 0_1, or 0_2, which indicates the time-frequency resources. After activation, the terminal periodically transmits data on these resources.

[0172] Specifically, RRC messages are used to configure parameters such as the CG PUSCH period and / or DMRS configuration. However, unlike type 1, there is no rrc-ConfiguredUplinkGrant parameter. Furthermore, there is no offset parameter to determine the absolute time domain position of the CG PUSCH. The specific position is determined by the activation DCI, and the CG PUSCH transmission can begin K2 symbols relative to the activation DCI. In addition, the time-frequency resource blocks of the CG PUSCH are not configured through configuration parameters, but are indicated by the activation DCI.

[0173] CG PUSCH for small data transmission (SDT) of inactive terminals:

[0174] When the terminal enters an inactive state, a CG PUSCH list is configured for the terminal through terminal-specific (UE-specific) configuration parameters, such as an RRC release message, and one or more CG PUSCH Occasions (CGOs) are configured in the CG PUSCH list.

[0175] The configuration of CGO can be shown in Figure 2D.

[0176] In the CG PUSCH list, each CG PUSCH configuration includes period, offset, time-frequency resource configuration parameters, etc. In addition, the CG PUSCH list also includes SDT-specific parameters, such as the number of SSBs and / or the allocated DMRS ports for each SSB.

[0177] The specific content of resource configuration parameters can be shown in Figure 2E.

[0178] The correspondence between CGO and SSB, regarding the beam configuration of the base station and the terminal, adopts a similar relationship between RO and SSB index during random access. However, when a CGO corresponds to multiple SSB indices, the specific SSB index cannot be further determined by the preamble sequence as in the RACH process.

[0179] Figure 1I is a schematic diagram of the correspondence between CGO and SSB indexes.

[0180] To this end, a mapping relationship between CGO and DMRS port and / or DMRS sequence is introduced to further inform the base station terminal of the selected beam (SSB index). That is, an SSB index is mapped to a CGO and the corresponding DMRS resource:

[0181] First, in a CGO, mapping is performed in ascending order by DMRS ID. DMRS IDs are defined as being numbered in ascending order by DMRS port index, then by DMRS sequence index. Then, frequency and time domain mapping of the CGO is performed.

[0182] To ensure that each SSB has resources mapped to it, the CGO introduces an association period. The association period is an integer multiple of the CGO period. Finally, the SSB index is mapped according to the CGO period within the association period.

[0183] If there are any remaining CGOs after SSB mapping is completed, the remaining CGOs are called invalid CGOs.

[0184] As shown in FIG2A , an embodiment of the present disclosure provides a method for processing request information, which is executed by a communication system. The method may include:

[0185] S2101: The network device sends the first configuration of CG-PUSCH to the terminal.

[0186] In some embodiments, the first configuration may include, but is not limited to, at least one of the following:

[0187] Time domain position information, indicating the time domain position of CG-PUSCH;

[0188] Frequency domain position information, indicating the frequency domain position of CG-PUSCH;

[0189] Period information, indicating the period of CG-PUSCH;

[0190] The offset indicates that the resource position of the first CG-PUSCH is equivalent to the offset relative to the reference position.

[0191] In some embodiments, the first configuration includes at least:

[0192] Time domain position information, indicating the time domain position of CG-PUSCH;

[0193] Frequency domain position information, indicating the frequency domain position of CG-PUSCH;

[0194] Period information, indicating the period of CG-PUSCH;

[0195] The offset indicates that the resource position of the first CG-PUSCH is equivalent to the offset relative to the reference position.

[0196] For example, the offset may be a time domain offset, the reference position may be a reference time, and the reference time may be the start time of system frame 0.

[0197] In some implementations, the CG-PUSCH configured by the first configuration may be used by the terminal to send request information.

[0198] In some embodiments, the request information is used to request the network device to send downlink transmission to the terminal.

[0199] In some embodiments, the request information is used to request the network device to send a common downlink transmission to the terminal.

[0200] In some embodiments, the common downlink transmission may be a downlink transmission that can be used by multiple terminals.

[0201] In some embodiments, the downlink transmission requested by the request information may be a downlink transmission that is originally sent periodically. For example, the downlink transmission may be a downlink transmission that is originally sent periodically based on a semi-static configuration or a dynamic configuration.

[0202] In some embodiments, the downlink transmission may include but is not limited to at least one of the following:

[0203] Downlink reference signal;

[0204] System Information Block (SIB).

[0205] The downlink reference signal may be any signal sent by the network device. For example, the downlink signal may include but is not limited to SSB.

[0206] The SIB may include at least SIB 1. In some embodiments, the SIB may further include other SIBs besides SIB 1.

[0207] In some embodiments, the SIB may be sent via a physical downlink shared information channel (PDSCH).

[0208] In some embodiments, the CG-PUSCH may be divided into multiple types, specifically, a first type to a fourth type, which are a first type CG-PUSCH, a second type CG-PUSCH, a third type CG-PUSCH, and a fourth type CG-PUSCH, respectively;

[0209] At least one of the configuration method, activation method and configuration parameters of the first type CG-PUSCH, the second type CG-PUSCH, the third type CG-PUSCH and the fourth type CG-PUSCH is different.

[0210] In some embodiments, the configuration messages for different configuration modes are different, for example, different message types or the same message type but different messages.

[0211] In some embodiments, different types of CG-PUSCH can be distinguished by whether activation or activation signaling is required. For example, the first type of CG-PUSCH and the fourth type of CG-PUSCH do not require activation. The second type of CG-PUSCH and the third type of CG-PUSCH require activation. The activation signaling for the second type of CG-PUSCH and the third type of CG-PUSCH is different.

[0212] The configuration parameters may be any information content of a specific CG-PUSCH, such as a period parameter indicating a period, a parameter indicating an offset, a parameter indicating whether it is associated with a beam, and / or a parameter indicating a corresponding CG-PUSCH type.

[0213] In some embodiments, the first type CG-PUSCH and the fourth type CG-PUSCH are configured by an RRC message; and the CGO of the fourth type CG-PUSCH is associated with a beam.

[0214] In some embodiments, one CGO of the fourth type CG-PUSCH is associated with one beam.

[0215] In some embodiments, a CGO of the fourth type CG-PUSCH is associated with multiple beams. In this way, the number of CGOs included in the fourth type CG-PUSCH can be less than or equal to the number of beams, which can reduce the number of CGOs included in the fourth type CG-PUSCH and thus reduce the resources occupied by the CGOs.

[0216] In some embodiments, the fourth type of CG-PUSCH is periodically distributed in the time domain, and CGOs of different periods can be associated with different beams.

[0217] In some embodiments, the fourth type of CG-PUSCH is periodically distributed in the time domain, and CGOs of different periods can be associated with the same beam.

[0218] In some embodiments, as shown in FIG. 1I , if a beam can be indicated by an SSB index, the association between the CGO and the beam can be determined using the following mapping method: each SSB index is mapped to a CGO in sequence according to the order of the SSB index. Specifically, frequency domain mapping is performed first, followed by time domain mapping, and finally mapping is performed in sequence according to the period of the CGO, in ascending order of the SSB index.

[0219] In some embodiments, C is less than or equal to A*B, and C is greater than A*(B-1); wherein C is the number of SSB indexes; A is the number of CGOs in one cycle of the fourth type CG-PUSCH; and B is the number of cycles of mapping the fourth type CG-PUSCH to the SSB index.

[0220] In some embodiments, different beams may be associated with different CGOs of the fourth type CG-PUSCH.

[0221] In some embodiments, different beams may be associated with the same CGO of the fourth type CG-PUSCH.

[0222] In some embodiments, different CGOs of the fourth type CG-PUSCH may be associated with different beams.

[0223] In some embodiments, the beam associated with the CGO may be indicated by the SSB index corresponding to the beam. Figure 5E is a schematic diagram of the association between a CGO and an SSB index.

[0224] In some embodiments, the RRC message for configuring the first type CG-PUSCH and the fourth type CG-PUSCH may be any RRC message.

[0225] In some embodiments, the configuration of the first type CG-PUSCH and the fourth type CG-PUSCH may be SIB1.

[0226] In some embodiments, the RRC message may include: a user-specific RRC message and / or a common RRC message. The user-specific RRC message may be a unicast RRC message. The common RRC message may be a broadcast message.

[0227] In some embodiments, the user-specific RRC message may also include an RRC configuration message, an RRC reconfiguration message and / or an RRC release message.

[0228] Exemplarily, the first type CG-PUSCH may be configured by an RRC configuration message or an RRC reconfiguration message.

[0229] In some embodiments, the first configuration for the first type CG-PUSCH indicates at least one of the following: a period of the first type CG-PUSCH; a time domain offset of the first type CG-PUSCH, indicating an offset of the first resource location of the first type CG-PUSCH relative to a reference time. The first type CG-PUSCH may not be associated with a beam.

[0230] In some embodiments, the first configuration for the first type CG-PUSCH may also carry indication information indicating whether the first type CG-PUSCH is specifically used to send request information.

[0231] For example, the specific configuration of the first type CG-PUSCH here can refer to the aforementioned type 1 CG-PUSCH.

[0232] In some implementations, the fourth type of CG-PUSCH may be released by an RRC release message. The fourth type of CG-PUSCH is configured for a terminal entering an RRC inactive state to send request information. Therefore, using an RRC release message to configure the fourth type of CG-PUSCH can reduce signaling overhead. It is worth noting that the fourth type of CG-PUSCH can be used by terminals in any RRC state. For example, the fourth type of CG-PUSCH can be used by RRC connected terminals, RRC idle terminals and / or RRC inactive terminals.

[0233] In some implementations, a period of the fourth type CG-PUSCH may include one or more CGOs. Different CGOs may be associated with different beams. Different beams may have different beam directions. In some embodiments, a beam may be indicated by an SSB index. Thus, association of different CGOs with beams may be understood as association of different beams with SSB indices.

[0234] In some embodiments, the first configuration for the fourth type of CG-PUSCH indicates at least one of the following: the period of the fourth type of CG-PUSCH; the time domain offset of the fourth type of CG-PUSCH, indicating the offset of the first resource position of the fourth type of CG-PUSCH relative to the reference time.

[0235] In some embodiments, the first configuration for the fourth type CG-PUSCH may also carry indication information indicating whether the fourth type CG-PUSCH is used to send request information.

[0236] The second type CG-PUSCH and the third type CG-PUSCH are configured by an RRC message, and the second type CG-PUSCH and the third type CG-PUSCH are activated by different signaling.

[0237] The RRC message for configuring the second type CG-PUSCH and / or the third type CG-PUSCH may be any RRC message.

[0238] The specific configuration of the second type of CG-PUSCH here can refer to the aforementioned type 2 CG-PUSCH.

[0239] The activation signaling of the second type CG-PUSCH and / or the third type CG-PUSCH may be any physical layer signaling and / or higher layer signaling. Exemplarily, the physical layer signaling may include DCI.

[0240] In some embodiments, the second type CG-PUSCH is activated by first signaling; the first signaling includes user-specific downlink control information DCI.

[0241] In some embodiments, the first configuration for the second type CG-PUSCH indicates at least: a period of the second type CG-PUSCH.

[0242] In some embodiments, in some embodiments, the first configuration for the second type CG-PUSCH may also carry indication information indicating whether the second type CG-PUSCH is used to send request information.

[0243] In some embodiments, the activation signaling for the second type of CG-PUSCH is different from the activation signaling for the third type of CG-PUSCH. For example, the activation signaling for the second type of CG-PUSCH may be signaling for a single terminal. The activation signaling for the third type of CG-PUSCH may be signaling for a terminal group or cell.

[0244] In some embodiments, the third type CG-PUSCH is activated by second signaling; the second signaling includes common DCI and / or notification signaling.

[0245] By activating the third type of CG-PUSCH through the public DCI, all terminals configured with the third type of CG-PUSCH can receive the public DCI, and thus know that the third type of CG-PUSCH is activated at the same time. Terminals that need to send request information can send request information through the third type of CG-PUSCH, thereby reducing resource occupancy and signaling overhead on the network side.

[0246] In some embodiments, the notification signaling is used to notify the start or stop of the first transmission; to specify that the third type CG-PUSCH is deactivated when the first transmission is turned on; and to specify that the third type CG-PUSCH is activated when the first transmission is turned off.

[0247] The notification signaling may include but is not limited to DCI and / or MAC signaling, or an implicit notification method, which can save signaling overhead on the network side.

[0248] The first configuration indication for the third type CG-PUSCH indicates at least one of the following: the period of the third type CG-PUSCH; the time domain offset of the third type CG-PUSCH, indicating the offset of the first resource position of the third type CG-PUSCH relative to the reference time.

[0249] The resource location information for the third type of CG-PUSCH may be carried by the first configuration of the third type of CG-PUSCH, or may be carried by activation signaling of the third type of CG-PUSCH. That is, in some embodiments, the second signaling further includes at least one of the following: time domain resource location information for the third type of CG-PUSCH; or frequency domain resource location information for the third type of CG-PUSCH.

[0250] Exemplarily, for example, the time domain resource location information can be used by the terminal to determine the time slot and / or symbol occupied by the third type CG-PUSCH.

[0251] Exemplarily, the frequency domain resource location information of the third type of CG-PUSCH can be used by the terminal to determine the resource blocks (RBs) and / or resource elements (REs) occupied by the third type of CG-PUSCH.

[0252] In some embodiments, the first type CG-PUSCH, the third type CG-PUSCH, and the fourth type CG-PUSCH may be shared by multiple terminals. For example, different terminals may use different DMRS ports to send request information on the same CG-PUSCH.

[0253] In this way, the first type CG-PUSCH, the third type CG-PUSCH and the fourth type CG-PUSCH can all be shared by multiple terminals. In this way, the effective utilization rate of the first type CG-PUSCH, the third type CG-PUSCH and the fourth type CG-PUSCH is improved, the wireless resource occupation is reduced, and in order to facilitate network equipment to know the sending terminal of the request information currently received on these CG-PUSCHs, different terminals use different DMRS ports to send request information using the same CG-PUSCH, that is, by utilizing the correspondence between CG-PUSCH, DRMS ​​port and terminal, the terminal differentiation is achieved while improving the effective utilization rate of CG-PUSCH.

[0254] In some embodiments, the first type CG-PUSCH, the third type CG-PUSCH and the fourth type CG-PUSCH may not be used by multiple terminals.

[0255] In some embodiments, the first type CG-PUSCH, the third type CG-PUSCH, and the fourth type CG-PUSCH are all shared by multiple terminals, but different terminals may use the same DMRS port to send request information on the same CG-PUSCH. For example, if the aforementioned downlink transmission is a public downlink transmission. The public downlink transmission may be a downlink transmission broadcast or multicast by a network device. In this way, the network device receives the request information broadcast downlink transmission, and the terminal requesting the downlink transmission can naturally receive it, and the network device does not need to know the terminal sending the request information.

[0256] In some embodiments, the first second type CG-PUSCH for sending request information is determined by the reception time of the first signaling and K2 time units; and / or, the first third type CG-PUSCH for sending request information is determined by the reception time of the second signaling.

[0257] As shown in FIG5B , the second type CG-PUSCH and the third type CG-PUSCH have different ways of determining the time domain positions at which they can be used to send request information.

[0258] In some embodiments, K2 associated with the second type CG-PUSCH may be carried by the first signaling for activating the second type CG-PUSCH, or may be agreed upon by a protocol.

[0259] In some embodiments, K2 can be any positive integer.

[0260] In some embodiments, the frequency shift amount in FIG5B may be an absolute time domain offset of the third type CG-PUSCH equivalent to radio frame #0 (SFN0).

[0261] S2102: The terminal sends a request message on the CG-PUSCH.

[0262] In some embodiments, the terminal sends the request information on a first type CG-PUSCH.

[0263] In some embodiments, the terminal sends the request information on a second type CG-PUSCH.

[0264] In some embodiments, the terminal sends the request information on a third type CG-PUSCH.

[0265] In some embodiments, the terminal sends the request information on the fourth type CG-PUSCH.

[0266] In some embodiments, if the terminal sends request information on the second type CG-PUSCH or the third type CG-PUSCH, the resources of the second type CG-PUSCH or the third type CG-PUSCH can only be used after the second type CG-PUSCH or the third type CG-PUSCH is activated.

[0267] In some embodiments, the second type CG-PUSCH or the third type CG-PUSCH may be activated by network signaling sent by a network device.

[0268] In some embodiments, the activation signaling of the second type CG-PUSCH may be the aforementioned first signaling.

[0269] In some embodiments, the activation signaling of the third type CG-PUSCH may be the aforementioned second signaling. Exemplarily, the second signaling may include but is not limited to public DCI and / or notification signaling.

[0270] In some embodiments, when the terminal has a need to obtain downlink transmission, it sends a request message on the CG-PUSCH.

[0271] In some embodiments, the terminal resides in a cell in a power saving state and when there is a need to obtain downlink transmission of the cell in the power saving state, the terminal may send a request message on the CG-PUSCH of the cell or a neighboring cell of the cell.

[0272] In some embodiments, the power saving state may include but is not limited to at least one of the following: the cell no longer periodically sends the downlink transmission, but sends the downlink transmission on demand. Exemplarily, the cell in the power saving state may also send the downlink transmission based on a request from a terminal.

[0273] In some embodiments, the terminal is within the coverage of a first cell and a second cell. The terminal may send a request message on the CG-PUSCH of the first cell. The request message may request downlink transmission of the first cell or may be used to request downlink transmission of the second cell. In some embodiments, the first cell and the second cell may be neighboring cells.

[0274] In some embodiments, the first cell and the cell may have overlapping coverage.

[0275] In some embodiments, if the terminal supports carrier aggregation or dual connectivity, the first cell is a primary cell and the second cell is a secondary cell; or, the first cell is a secondary cell and the second cell is a primary cell.

[0276] In some embodiments, the first cell may be a primary cell and the second cell may be a secondary cell, or the first cell may be a secondary cell and the second cell may be a primary cell.

[0277] In some embodiments, the description related to the downlink transmission requested by the terminal's request information can be found in the corresponding position of S2101, and will not be repeated here.

[0278] In some embodiments, the request information may be a wake-up signal (WUS) requesting downlink transmission.

[0279] In some embodiments, when the request information is a physical layer signal, the physical layer signal may not carry any information, but the physical layer signal represents the terminal's request for downlink transmission.

[0280] In some embodiments, the request information may include at least one of the following:

[0281] A first indication is used to request sending a downlink transmission;

[0282] A second indication, used to indicate the type of downlink transmission requested to be sent;

[0283] A third indication is used to indicate the index of the downlink transmission requested to be sent;

[0284] The fourth indication is used to indicate beam information of the desired beam for downlink transmission.

[0285] In some embodiments, the first indication may include one or more bits. For example, if the bit corresponding to the first indication has a first value, it indicates that downlink transmission is requested, otherwise it may be considered that downlink transmission is not requested.

[0286] In some embodiments, the downlink transmission may include SSBs and / or SIBs. For example, the second indication may indicate whether an SSB or SIB is requested. For another example, if SSBs are of different types, the second indication may indicate the type of SSB requested to be transmitted.

[0287] In some embodiments, taking SIB as an example, whether the terminal requests SIB1, SIB2 or SIBn may be carried by the third indication.

[0288] In some embodiments, the fourth indication may indicate the beam that the terminal desires to receive downlink transmission. The beam information may include a beam identifier, a beam direction, or a beam index. In some embodiments, the beam information may also be an SSB index that is bound to the beam.

[0289] In some embodiments, the desired beam may be the optimal transmission beam at the terminal and the base station.

[0290] In some embodiments, the desired beam may be the optimal beam measured by the terminal at a previous moment.

[0291] In some embodiments, the request message may carry the first indication alone.

[0292] In some embodiments, the request message may carry the second indication alone.

[0293] In some embodiments, the request message may carry the third indication alone.

[0294] In some embodiments, the request message may carry the fourth indication alone.

[0295] In some embodiments, the request information may include any two or more combinations of the first indication, the second indication, the third indication, and the fourth indication.

[0296] In some embodiments, any two or more of the first indication, the second indication, the third indication, and the fourth indication share an indication field.

[0297] In some embodiments, when any two or more of the first to fourth indications share an indication field, different bits of the indication field may carry the first indication, the second indication, the third indication, and the fourth indication, respectively.

[0298] In some embodiments, when any two or more of the first to fourth indications share a common indication field, the indication bits of the indication field are jointly encoded, and the different bit values ​​corresponding to the joint encoding of the indication field may correspond to the first indication, the second indication, the third indication, and the fourth indication. In this way, the network device can determine the content corresponding to the first indication, the second indication, the third indication, and the fourth indication based on this correspondence and the value indicated by the indication field.

[0299] In some embodiments, the first indication, the second indication, the third indication, and the fourth indication use different indication fields.

[0300] In some embodiments, the request information is not limited to the first to fourth indications described above. For example, the request information may also carry a fifth indication. The fifth indication may indicate a time range within which the terminal expects to receive downlink transmissions.

[0301] In some embodiments, the terminals may include a first type of terminal and a second type of terminal.

[0302] The first type of terminal supports the energy-saving mechanism of the network device. The second type of terminal may not support the energy-saving mechanism of the network device. When the network device implements the energy-saving mechanism, the terminal needs to send a request message to the network device to request the above-mentioned downlink transmission.

[0303] In some embodiments, when the terminal is a first type terminal, request information is sent to the network device via CG-PUSCH.

[0304] In some embodiments, when the terminal is a second type terminal and determines that it needs to request downlink transmission from the corresponding cell, it can select other cells for access through a cell switching and / or cell reselection mechanism.

[0305] In some embodiments, the terminal may receive a second configuration of the network device, where the second configuration indicates that the network device is in a network node NES state.

[0306] In some embodiments, the second configuration includes at least one of the following:

[0307] Cell DRX configuration;

[0308] Cell DTX configuration.

[0309] The cell DRX configuration may be used by a network device to perform discontinuous reception.

[0310] In some embodiments, if the network device is configured with cell DRX, the terminal can send request information during the activation time of cell DRX, so that the network device can maintain a low power consumption state during the inactivation time of cell DRX, thereby improving the energy-saving cell of the network device.

[0311] In some embodiments, if the network device is configured with cell DRX, the terminal may send request information during the activation time and inactivation time of the cell DRX, so that the terminal may request the downlink transmission required by itself in a timely manner.

[0312] In some embodiments, a cell DTX configuration is configured for performing DTX in the cell. After the network device receives the request information, when the cell performs DTX, the cell sends the terminal the downlink transmission requested by the terminal during the activation time of the cell DTX. This allows the network device to maintain a low power consumption state during the inactive time of the cell DTX, thereby improving energy conservation of the network device. The network device sends the terminal the requested downlink transmission during the inactive and active time of the cell DTX cycle.

[0313] In some embodiments, if the second cell is in an energy-saving state and does not send SSB and / or SIB, in this case, the terminal may request the first cell to send an SSB and / or SIB request message for the second cell on the CG-PUSCH of the first cell. At this time, the request information sent by the terminal may carry the cell identifier or index of the second cell to facilitate confirmation by the first cell. After receiving the request information, the network device of the first cell transmits the request information to the second cell, and the second cell sends the requested downlink transmission. In some embodiments, the terminal may ignore the second configuration sent by the network device and send the request information to the network device on the CG-PUSCH according to the first configuration.

[0314] In some embodiments, the terminal may send request information to the network device on the CG-PUSCH within the activation time of the cell DRX according to the second configuration and the first configuration.

[0315] In some embodiments, when cell DRX is performed in the second cell, the terminal may send request information to the first cell according to the first configuration of the first cell. The request information may be transmitted by the first cell to the second cell via an inter-cell interface or tunnel to trigger the second cell to send downlink transmission.

[0316] In some embodiments, when cell DTX is performed in the second cell, the terminal may send a request message to the first cell and monitor downlink transmission sent by the second cell within the activation time of DTX of the second cell.

[0317] In some embodiments, the network device receives the request information when performing cell DTX, and then sends the downlink transmission to the terminal within the activation time of the cell DTX.

[0318] In some embodiments, the network device receives the request information when performing cell DTX and can send downlink transmission to the terminal during the inactive time and active time of the cell DTX.

[0319] In some embodiments, after receiving the request information, the network device may send a downlink transmission based on the request information, or may not send the requested downlink transmission. For example, the network device is in an energy-saving state in which it does not send a downlink transmission or sends a downlink transmission on demand. In order to maximize energy saving, the network device may choose not to send the downlink transmission. However, in order to promptly respond to the needs of the terminal, the network device may also respond to the request information and send the downlink transmission requested by the terminal. For another example, when the terminal receives the request information, the network device is in an energy-saving state in which it does not send a downlink transmission or sends a downlink transmission on demand. However, based on its own configuration, the network device determines that it will soon exit the energy-saving state. After exiting the energy-saving state, the network device will send downlink transmission normally. At this time, the network device may also choose not to respond to the request information.

[0320] In some embodiments, when the network device sends a downlink transmission based on the request information, it may send the downlink transmission according to the request information, for example, sending the downlink transmission on the desired beam and / or desired time range of the terminal.

[0321] As shown in FIG3 , an embodiment of the present disclosure provides a method for processing request information, which is executed by a terminal. The method may include:

[0322] S3101: Receive the first configuration of CG-PUSCH.

[0323] In some embodiments, the terminal receives a first configuration of the CG-PUSCH sent by the network device.

[0324] The CG-PUCSH may be any one of the aforementioned first type CG-PUSCH, second type CG-PUSCH, third type CG-PUSCH and fourth type CG-PUSCH.

[0325] In some embodiments, the description of the first configuration and / or CG-PUSCH can be found in S2101 of the corresponding embodiment of Figure 2A.

[0326] S3102: Send request information on CG-PUSCH.

[0327] In some embodiments, the optional real-time method of S3102 can refer to S2102 of the corresponding embodiment of Figure 2A.

[0328] As shown in FIG3 , an embodiment of the present disclosure provides a method for processing request information, which is executed by a network device. The method may include:

[0329] S4101: Send the first configuration of CG-PUSCH.

[0330] In some embodiments, the network device sends the first configuration of the CG-PUSCH to the terminal in a broadcast, multicast, or unicast manner.

[0331] The CG-PUCSH may be any one of the aforementioned first type CG-PUSCH, second type CG-PUSCH, third type CG-PUSCH and fourth type CG-PUSCH.

[0332] In some embodiments, the description of the first configuration and / or CG-PUSCH can be found in S2101 of the corresponding embodiment of Figure 2A.

[0333] S4102: Receive request information on CG-PUSCH.

[0334] In some embodiments, the request information is received on a second type CG-PUSCH.

[0335] In some embodiments, the request information is received on a second type CG-PUSCH.

[0336] In some embodiments, the request information is received on a third type CG-PUSCH.

[0337] In some embodiments, the request information is received on a fourth type CG-PUSCH.

[0338] In some embodiments, the request information is used by the terminal to request the network device to send a downlink transmission.

[0339] In some embodiments, the downlink transmission may be a public downlink transmission.

[0340] In some embodiments, the downlink transmission may be an SSB and / or a SIB.

[0341] In some embodiments, the relevant description of the request information can be found in S2102 of the embodiment corresponding to FIG. 2A .

[0342] In some embodiments, the request message may be used to request the cell sending the first position to send a downlink transmission, or may be used to request other cells to send a downlink transmission. If the request message requests other cells to send a downlink transmission, the cell receiving the request message may transmit the request message to the corresponding cell via an inter-cell interface or tunnel, so that the corresponding cell sends the downlink transmission.

[0343] In some embodiments, if the requested cell itself responds to the request information, there is no need to forward the request information to other cells.

[0344] In some embodiments, after receiving the request information, the network device may send a downlink transmission based on the request information, or may not send the requested downlink transmission. For example, the network device is in an energy-saving state in which it does not send a downlink transmission or sends a downlink transmission on demand. In order to maximize energy saving, the network device may choose not to send the downlink transmission. However, in order to promptly respond to the needs of the terminal, the network device may also respond to the request information and send the downlink transmission requested by the terminal. For another example, when the terminal receives the request information, the network device is in an energy-saving state in which it does not send a downlink transmission or sends a downlink transmission on demand. However, based on its own configuration, the network device determines that it will soon exit the energy-saving state. After exiting the energy-saving state, the network device will send downlink transmission normally. At this time, the network device may also choose not to respond to the request information.

[0345] In some embodiments, when sending a downlink transmission based on the request information, the network device may send the downlink transmission according to the request information, for example, sending the downlink transmission on a desired beam and / or desired time range of the terminal.

[0346] An embodiment of the present invention proposes a WUS design scheme for waking up a cell-specific signal or channel to support terminal users with relevant capabilities in the cell to send SSB and / or SIB1 wake-up signals to the network as needed, so that the base station decides whether to send relevant signals / signaling based on the actual needs of the terminal.

[0347] In view of this, network equipment can turn off the transmission of SSB / SIB1 according to business load, number of residents, etc. to achieve energy saving. At the same time, the network can turn on SSB / SIB1 according to user needs to ensure normal communication between users and the network and avoid a decline in network service quality.

[0348] As shown in FIG5A , the method provided by the embodiment of the present disclosure may include:

[0349] The network side (ie, the network device) sends the CG-PUSCH configuration to the terminal. For example, the network side sends the CG-PUSCH configuration to terminal 1 and / or terminal 2. This configuration may be the first configuration described above.

[0350] If the CG-PUSCH configured by the network side for the terminal needs to be activated, the CG-PUSCH can be activated through explicit or implicit instructions. For example, the aforementioned dedicated DCI and / or public DCI can explicitly activate the CG-PUSCH. Notification instructions can implicitly activate the CG-PUSCH.

[0351] If the terminal determines that the downlink (DL) of the corresponding cell is closed, it can send a WUS to the network. The WUS can request the network to open the DL channel or signal. If the DL channel or signal is opened, the network will send the corresponding DL signal or channel.

[0352] The terminal uses the CG PUSCH resource to send a request to the network. This request can be used to request downlink transmission from the base station. The base station receives the request on the corresponding resource. The terminal sends the request via a Type 1 Configured Grant (CG) Physical Uplink Shared Channel (PUSCH).

[0353] The terminal sends the request information on the newly defined CG PUSCH.

[0354] The terminal selects an appropriate (CG PUSCH Occasion, CGO) to send a request message to the network, and the base station receives the request message accordingly.

[0355] For terminals that support network energy saving, a request message (WUS) is sent to the network using the following method.

[0356] Downlink transmission may be a combination of one or more signals or information.

[0357] For example, the downlink transmission may be a combination of SSB and SIB1, a combination of SIB1 and SIB2, and a combination of SSB and SIB2.

[0358] For example, the downlink transmission may include at least one of the following:

[0359] SSB;

[0360] SIB1;

[0361] SIBn, n>1.

[0362] Specifically, the implementation of the first step may include but is not limited to at least one of the following:

[0363] Method 1: The terminal sends the request information via type 1 CG PUSCH.

[0364] The terminal sends a request message on a CG PUSCH resource of type 1 configured by the network. The request message is a MAC control element (CE), RRC information, or other information, which is not limited in the embodiment of the present invention.

[0365] The request information includes a first indication field. The first indication field is used by the terminal to request downlink transmission from the network device.

[0366] The request information includes a second indication field. The second indication field is used to indicate the downlink signal or channel type requested by the terminal, such as SSB, SIB1, or SSB and SIB1.

[0367] The first indication domain and the second indication domain may be the same domain.

[0368] The request information also includes a third indication field, which is used to indicate the desired beam of one or more transmission SSBs and / or SIBs of the downlink signal or channel that the terminal expects to receive. Specifically, the desired beam can be indexed by one or more SSBs. Different SSB indices can correspond to different desired beams.

[0369] The terminal receives a first configuration of a CG PUSCH from the network.

[0370] The CG PUSCH may be a multiplexed existing CG PUSCH.

[0371] The CG PUSCH may also be used exclusively for the CG PUSCH transmitted by the WUS.

[0372] The CG PUSCH resource can be configured for one or more terminals. The configured resource is configured by a UE-specific RRC message or through SIB1.

[0373] When the same CG PUSCH resource is configured for multiple terminals simultaneously, these terminals reuse the same resource to send request information. To distinguish the WUSs of different terminals, different DMRS ports need to be allocated to different terminals when configuring the CG PUSCH resource for different terminals. In this case, the maximum number of terminals that can be reused is 12 / 24.

[0374] If the network configures cell DTX or downlink DRX for the terminal at the same time, the CG PUSCH for sending WUS is not affected by cell discontinuous reception and / or cell discontinuous transmission.

[0375] Method 2: The terminal sends a request message on the newly defined CG PUSCH.

[0376] For convenience, the newly defined CG PUSCH is called Type 3 CG PUSCH, and the Type 3 CG PUSCH can be shown in (b) of FIG5B .

[0377] A first configuration of the network is received, where the first configuration is parameters for a CG PUSCH of terminal configuration type 3. The parameters may include at least a period and an offset. Optionally, the configuration parameters further include a first configuration of time-frequency resources. The parameters may be configured via terminal-specific configuration parameters or via SIB1. The resources may be configured for one or more terminals.

[0378] When multiple terminals are allocated the same CG PUSCH resource to send WUS, in order to distinguish the WUS of each terminal, different DMRS ports need to be allocated to different terminals.

[0379] Receive activation signaling sent by the network device, where the activation signaling is terminal activation type 3 CG PUSCH.

[0380] In one embodiment, dedicated activation signaling is introduced, such as common DCI.

[0381] The activation signaling includes at least a first indication field, indicating that a predetermined value activates the CG-PUSCH.

[0382] If RRC does not configure the time-frequency resources of CG-PUSCH, the activation signaling also includes a second indication field for indicating the time-frequency resources of CG-PUSCH.

[0383] In another embodiment, no dedicated activation signaling is introduced.

[0384] If there is network signaling notifying each terminal that the signal or channel is closed, the CG-PUSCH activation signaling can be carried on the signaling notifying the terminal that the signal or channel is closed.

[0385] If there is no network signaling to notify each terminal that SSB is closed, when the terminal cannot detect the channel or signal, it is considered that SSB is closed and CG-PUSCH is activated by default.

[0386] This method requires that the CG-PUSCH time-frequency resources need to be configured through configuration parameters. The configuration parameters can be RRC parameters carried by RRC messages.

[0387] After CG-PUSCH is activated, the terminal sends request information on CG-PUSCH.

[0388] The request information is MAC CE, RRC information or other information, which is not limited in the embodiment of the present invention.

[0389] The content and method of the request information are the same.

[0390] Receive the CG-PUSCH deactivation signaling sent by the network side.

[0391] Solution 1: Set the first indication field in the introduced activation signaling to a predetermined value to deactivate CG-PUSCH.

[0392] Solution 2: If there is a network signaling to inform each terminal that SSB is turned on, the CG-PUSCH can be activated through this signaling.

[0393] If there is no network signaling to inform the terminal that SSB is turned on, the terminal will consider CG-PUSCH deactivated after detecting SSB. For the network, after turning on SSB, it defaults to CG-PUSCH deactivation and no longer attempts to receive WUS.

[0394] If the network configures cell discontinuous reception and / or cell discontinuous transmission for the terminal at the same time, the network needs to receive the CG-PUSCH that may send WUS.

[0395] As shown in Figure 5B (b), the CG-PUSCH is the third type of CG-PUSCH. The third type of CG-PUSCH can also be called type 3 CG-PUSCH. Figure 5B is a timing comparison diagram of the second type of CG-PUSCH and the third type of CG-PUSCH. The second type of CG-PUSCH can also be called type 2 CG-PUSCH, as shown in Figure 5B (a).

[0396] The time domain location of the Type 3 CG-PUSCH is determined by the configured period and offset. For the first CG-PUSCH, the CG-PUSCH corresponding to the grid line filled square is not valid because no activation signaling has been received. The second CG-PUSCH is located in the time domain after the public DCI is received, so the second CG-PUSCH is valid. The valid CG-PUSCH can be used to send request information.

[0397] Method 3: The terminal selects the appropriate CGO (CG-PUSCH Occasion) and sends a request message to the network.

[0398] A first configuration of the receiving network is configured, where the first configuration configures multiple CG-PUSCH Occasions (CGOs) for the terminal, corresponding to different SSB indices, as shown in Figure 5C. The configuration resource can be configured by a UE-specific RRC message or through SIB1. The SSB index can be used to indicate a beam.

[0399] Different CGOs correspond to different SSBs, where the correspondence between CGO and SSB can be mapped in ascending order of CGO frequency domain, then ascending order of time domain, and finally CGO period.

[0400] These CGOs can be configured for one terminal or multiple terminals. In order to allow multiple terminals to reuse CG-PUSCH, different DMRS ports are allocated to different terminals.

[0401] For the mapping of CGO to different SSBs, since DMRS is already used for multi-terminal multiplexing, DMRS resources can no longer be used to distinguish them. It can be considered to indicate directly in the request information. The specific number of SSB indexes that each CGO can map is determined by the number of bits in the indication field used to indicate the specific SSB index in the request information. In this case, the multiple SSB indexes corresponding to each CGO are configured by the network.

[0402] The terminal sends a request message on the CG-PUSCH configured by the network. The request message can be MAC CE or RRC, which is not limited in the embodiment of the present invention.

[0403] The terminal selects a suitable transmission beam and selects CGO to send WUS according to the corresponding SSB index.

[0404] To prevent the terminal from initially selecting an appropriate transmission beam, the network indicates an initial transmission beam to the terminal when configuring CG-PUSCH for the terminal. Specifically, it may indicate an SSB index. If the terminal fails to select an appropriate transmission beam, it uses the optimal transmission beam with the indicated SSB index and selects CGO to send the request information.

[0405] The request message includes a first indication field, which is used to initiate a request to the network. The request message also includes a second indication field, which indicates the type of downlink signal or channel requested by the terminal, such as SSB, SIB1, or both SSB and SIB1. The first indication field and the second indication field can be the same field, meaning that indicating the required signal or channel also initiates the request.

[0406] When a CGO corresponds to multiple SSB indexes, it also includes a third indication field. The third indication field sends the CGO request information, and specifically indicates which SSB index among the corresponding multiple SSB indexes is used.

[0407] The request information also includes a fourth indication field, which is used to indicate one or more transmission beams for receiving downlink signals or channels that the terminal expects. Specifically, one or more SSB indexes (index) can be indicated. If the fourth indication field is missing, the one or more transmission beams (SSB indexes (index)) corresponding to the CGO can be defaulted to the one or more transmission beams for receiving downlink signals or channels that are expected.

[0408] If the network configures cell discontinuous reception and / or cell discontinuous transmission for the terminal at the same time, the network needs to receive the CG-PUSCH that may send WUS.

[0409] Base station side: For base stations that support network energy saving, after the downlink signal or channel is closed, the downlink signal or channel request information sent by the terminal is received through the following method.

[0410] Mode 1: The base station receives the request information on a type 1 CG-PUSCH configured for the terminal.

[0411] The CG-PUSCH is configured for terminals supporting network energy saving through UE-specific RRC message configuration or SIB1. The CG PUSCH resource is a CG-PUSCH dedicated to WUS transmission or an existing CG-PUSCH. The CG-PUSCH can be configured for one or more terminals.

[0412] In order to allow multiple terminals to multiplex the resource to send request information, different DMRS ports need to be allocated to different terminals when configuring the CG-PUSCH for different terminals.

[0413] The request information sent by the terminal is received on the configured CG-PUSCH. The request information is MAC CE, RRC information, or other information, which is not limited in the embodiment of the present invention.

[0414] The request message includes a first indication field, which is used to initiate a request to the network; the request message also includes a second indication field, which indicates the downlink signal or channel type requested by the terminal, such as SSB, SIB1, or both SSB and SIB1. The first indication field and the second indication field can be the same field, meaning that indicating the required signal or channel also initiates the request.

[0415] The request information also includes a third indication field, which is used to indicate one or more transmission beams for receiving downlink signals or channels that the terminal expects to receive. Specifically, it can indicate one or more SSB indexes.

[0416] If the network configures cell discontinuous reception and / or cell discontinuous transmission for the terminal at the same time, it still needs to receive request information in the cell DRX inactive state.

[0417] Mode 2: The base station receives a downlink signal or channel request information sent by the terminal in a newly defined CG-PUSCH configured for the terminal.

[0418] The CG-PUSCH parameters are configured for the terminal through UE-specific RRC or SIB1, including at least the period and offset. Optionally, the first configuration of time-frequency resources is also included. The CG-PUSCH can be configured for one or more terminals.

[0419] In order to allow different terminals to reuse the resource, different DMRS ports are allocated to different terminals.

[0420] Send CG-PUSCH activation signaling to activate the configured CG-PUSCH for the terminal.

[0421] The request information sent by the terminal is received on the configured CG-PUSCH. The request information is MAC CE, RRC information, or other information, which is not limited in the embodiment of the present invention.

[0422] The message and method are the same.

[0423] Send CG-PUSCH deactivation signaling to deactivate CG-PUSCH.

[0424] If the network configures cell discontinuous reception and / or cell discontinuous transmission for the terminal at the same time, it still needs to receive request information in the cell DRX inactive state.

[0425] Method 3: The network attempts to receive the downlink signal or channel request signal sent by the terminal using the corresponding beam on multiple CGOs configured for the terminal.

[0426] Multiple CG-PUSCH Occasion (CGO) resources are configured for the terminal, corresponding to different SSB indices (beams). The configuration resources can be configured by UE-specific RRC messages or through SIB1. These CGO resources can be configured for one or more terminals.

[0427] When the same CGO is allocated to multiple terminals, different DMRS ports are allocated to different terminals.

[0428] The network receives the request information sent by the terminal. The request information can be MAC CE or RRC, which is not limited in the embodiment of the present invention.

[0429] The request information includes a first indication field, which is used to initiate a request to the network.

[0430] The request information includes a second indication field, which is used to indicate the downlink signal or channel type requested by the terminal, such as SSB, SIB1, or SSB and SIB1.

[0431] The first indication field and the second indication field may be the same field, that is, when the required signal or channel is indicated, a request is also initiated.

[0432] When a CGO corresponds to multiple SSB indexes, it also includes a third indication field. The third indication field sends the CGO request information, and specifically indicates which SSB index among the corresponding multiple SSB indexes is used.

[0433] The request information also includes a fourth indication field, which is used to indicate one or more transmission beams for receiving downlink signals or channels that the terminal expects to receive. Specifically, one or more SSB indexes (index) can be indicated. If the fourth indication field is correct, the one or more SSBs corresponding to the CGO can be defaulted to one or more transmission beams for receiving downlink signals or channels that are expected to receive.

[0434] Example 1:

[0435] In wireless communication systems, the network may suspend the transmission of downlink signals or channels, such as SSB / SIB1, to save energy. However, this may prevent the terminal from properly receiving SSB / SIB1 for downlink synchronization, RRM measurements, L1 measurements, or updating system messages. To ensure normal communication between the network and the terminal, it is considered to allow the terminal to initiate a downlink signal or channel request message (WUS) to the network as needed. The network decides whether to enable the downlink signal or channel based on the received WUS.

[0436] In this embodiment, as shown in FIG1B , each terminal is a terminal supporting Network Energy Saving (NES), and the network device is a device supporting Network Energy Saving.

[0437] This embodiment proposes a method for sending downlink signal or channel request information through type (type) 1 CG-PUSCH to support the network to shut down the downlink signal or channel to achieve energy saving, while ensuring that the terminal can request information to ensure normal communication with the network and avoid degradation of network service quality.

[0438] Downlink signals or channels include the following signals or channels, or any combination of the following channels or signals:

[0439] SSB

[0440] SIB1

[0441] SIBn, n>1.

[0442] For example, SSB and SIB1, SIB1 and SIB2, SSB and SIB2. The following method description will not be repeated.

[0443] In this embodiment, the terminal sends request information on the configured CG-PUSCH as needed. The message may be MAC CE, RRC or other messages, which is not limited in this embodiment.

[0444] The request information includes a first indication field, which is used to initiate a request to the network; the request information includes a second indication field, which indicates the type of downlink signal or channel requested by the terminal, such as SSB or SIB1, or SSB and SIB1, etc. The first indication field and the second indication field can be the same field, that is, when indicating the required signal or channel, a request is also initiated at the same time, or there may be no first indication field. It is used to request a downlink signal or channel from the network. The request information also includes a third indication field, which is used to indicate one or more transmission beams for the terminal to receive the downlink signal or channel. Specifically, one or more SSB indexes (index) can be indicated.

[0445] Exemplarily, the request information may be carried in a Media Access Control Control Element (MAC CE), which may be referred to as a WUS MAC CE.

[0446] As shown in FIG5D , the WUS MAC CE may include a first indication field.

[0447] The first indication field may carry a 'WUS' identifier. The first configuration is used to identify that the terminal requests an SSB and / or SIB1.

[0448] The WUS MAC CE may further include a second indication field. The second indication field indicates the requested downlink signal or channel. Specifically,

[0449] The second indication field may include 1 bit indicating whether SSB is requested. The first indication field here may carry the aforementioned first indication.

[0450] The second indication field may include 1 bit indicating whether SIB1 is requested. The second indication field here may carry the aforementioned second indication and / or third indication.

[0451] The second indication field may include one or more bits indicating whether SIBn is requested. For example, the second indication field includes a bit indicating whether SIBn is requested. If the bit in the second indication field is a specified value, it indicates that the terminal requests SIB2, SIB3, and other SIBn.

[0452] In some embodiments, the importance of SIB1 may be higher than that of SIBn, and therefore there may be a dedicated indication bit in the second indication field.

[0453] In some embodiments, a bit indication is set corresponding to each SIB in the WUS MAC CE for the terminal to indicate whether to request the corresponding SIB.

[0454] The first indication field and the second indication field are the same field, that is, if there is a request for a downlink signal channel, there is corresponding indication of request information.

[0455] In some embodiments, in some embodiments, a third indication field is further included.

[0456] The third indication field includes one or more bits indicating the desired beam of the terminal. The desired beam may be indicated by an SSB index. The third indication field may carry the aforementioned fourth indication.

[0457] For example, the third indication field indicates one or more SSB indices, indicating one or more transmission beams of a downlink signal or channel that the terminal desires to receive. The signaling is only for exemplary purposes.

[0458] Figure 5D is a schematic diagram of a WUS MAC CE, wherein the first indication field and the second indication field are located in the same octet (Ocelet, Oct). The fourth indication field may correspond to one or more octets and be located in a different octet than the first indication field and the second indication field.

[0459] In this embodiment, the terminal receives the first configuration of the network, and the first configuration is a CG-PUSCH for the terminal to transmit a downlink signal or channel request information. In this embodiment, the CG-PUSCH is a CG-PUSCH configured by the terminal specifically for requesting information, or a CG-PUSCH that reuses an existing protocol. The network can configure the same CG-PUSCH for one or more terminals. In order for multiple terminals to reuse the resource to send their respective WUS, different DMRS ports need to be allocated to different terminals. In this embodiment, the first configuration can be configured by UE-specific RRC information or signaling such as SIB1.

[0460] Exemplarily, the configuration signaling is configured to the terminal by a terminal-specific RRC message, specifically, by a ConfiguredGrantConfig IE. Optionally, an explicit identifier, such as cg-NES-SSBWUS, is introduced therein to indicate that the CG-PUSCH is specifically used for sending WUS.

[0461] Exemplarily, the first configuration may be configured to the terminal via SIB 1. Specifically, a nes-ConfigCommon may be introduced in SIB 1 to configure the terminal with a CG-PUSCH for sending a WUS.

[0462] The signaling names cg-NES-SSBWUS and nes-ConfigCommo are only used as examples.

[0463] In this embodiment, the terminal may send a WUS only once and then start to determine whether the network has enabled SSB. Alternatively, the terminal may send a WUS continuously or continuously until SSB is determined to be enabled, which is not limited in this embodiment.

[0464] If the network configures cell discontinuous reception and / or cell discontinuous transmission for the terminal at the same time, the CG-PUSCH for sending WUS is not affected by cell discontinuous reception and / or cell discontinuous transmission.

[0465] Example 2:

[0466] Similar to the first embodiment, in this embodiment, each terminal is a terminal supporting NES, and the network device will temporarily shut down the transmission of downlink signals or channels according to energy saving needs.

[0467] Consider using a CG-PUSCH similar to type 2 to send WUS. After SSB is enabled, there is no need to send WUS, and the corresponding resources can be deactivated. However, unlike type 2 CG-PUSCH, type 3 CG-PUSCH can be multiplexed by multiple terminals. The timing cannot be determined according to the previous dedicated DCI.

[0468] To this end, this embodiment proposes a new CG PSUCH type (referred to as type 3 for convenience) for sending downlink signal or channel request information. This allows the network to shut down downlink signals or channels for energy saving while ensuring that terminals can request downlink signals or channels to maintain normal communication with the network, while also reducing resource usage.

[0469] The terminal receives a second configuration of the network, which is a terminal configuration type (type) 3 CG-PUSCH. The second configuration includes at least the period and offset of the CG-PUSCH. This parameter is configured through terminal-specific configuration parameters, and the same CG-PUSCH can be configured for multiple terminals. In order for the multiple terminals to reuse the resource to send their own WUS, different DMRS ports are allocated to different terminals.

[0470] The activation signaling is used to activate the configured type 3 CG-PUSCH for one or more terminals.

[0471] In some embodiments, the activation signaling includes at least a first indication field indicating that a predetermined value activates the CG-PUSCH.

[0472] In some embodiments, the activation signaling further includes a second indication field for indicating the time-frequency resources of the CG-PUSCH.

[0473] The activation signaling may be a specially introduced common DCI.

[0474] If the network device has explicit signaling to notify each terminal that the signal or channel is closed, the CG-PUSCH activation signaling can be carried on the signaling notifying the terminal that the signal or channel is closed.

[0475] In this embodiment, after receiving the activation signaling, the terminal sends an information signal or channel request information on the configured CG-PUSCH. The message may be a MAC CE, RRC or other message. This embodiment does not limit this.

[0476] The request information content is the same as that in Example 1.

[0477] In this embodiment, the terminal also needs to receive the CG-PUSCH deactivation signaling sent by the network side, and set the first indication field in the activation signaling to a predetermined value to indicate that the CG-PUSCH is deactivated.

[0478] If the network configures cell discontinuous reception and / or cell discontinuous transmission for the terminal at the same time, the CG-PUSCH for sending WUS is not affected by cell discontinuous reception and / or cell discontinuous transmission.

[0479] Example 3:

[0480] A new CG-PUSCH type is introduced for terminals to send signals or channel request information (WUS).

[0481] The network device configures a type 3 CG-PUSCH for the terminal, which includes at least a period, an offset, and time-frequency resources of the CG-PUSCH.

[0482] The terminal receives activation signaling of CG-PUSCH from the network.

[0483] The activation signaling is used to activate the configured type 3 CG-PUSCH for one or more terminals.

[0484] The activation signaling is a specially introduced common DCI.

[0485] The common DCI includes a first indication field. The first indication field indicates that a predetermined value activates the CG-PUSCH.

[0486] In some cases, it is stipulated that when the terminal determines that there is a downlink signal or the channel is closed, the CG-PUSCH is activated by default.

[0487] For example, if there is a displayed signaling to notify each terminal that the signal or channel is closed, the CG-PUSCH is activated; if there is no displayed signaling to notify each terminal that the signal or channel is closed, the terminal considers that the CG-PUSCH is activated after detecting that the SSB is closed.

[0488] The terminal receives CG-PUSCH deactivation signaling from the network.

[0489] The deactivation signaling is used to deactivate the configured type 3 CG-PUSCH for one or more terminals.

[0490] The first indication field of the deactivation signaling is set to a specific value for deactivation; or it is stipulated that when the terminal determines that there is a downlink signal or the channel is turned on, the CG-PUSCH is deactivated by default.

[0491] In some embodiments, the second signaling may also be used to deactivate the third type CG-PUSCH. The second signaling to deactivate the third type CG-PUSCH may be a common DCI and / or the aforementioned notification signaling.

[0492] For example, if there is a displayed signaling to notify each terminal that the signal or channel is turned on, the CG-PUSCH is deactivated; if there is no displayed signaling to notify each terminal that the signal or channel is turned on, the terminal considers that the CG-PUSCH is deactivated after detecting that the SSB is turned on.

[0493] In this embodiment, other contents are the same as those in embodiment 1.

[0494] The difference from embodiment 2 is that the activation signaling of the embodiment of the present disclosure does not include the time-frequency domain resource parameters of the third type CG-PUSCH.

[0495] Example 4:

[0496] Assuming that the terminal is a terminal that supports NES and the network is the above-mentioned network that supports energy saving, the network device will suspend the transmission of downlink signals or channels within a certain period of time.

[0497] The network device configures multiple CGOs for the terminal. Different CGOs correspond to different SSBs.

[0498] As shown in Figure 5C, the correspondence between CGO and SSB can be mapped in the ascending order of SSB index, first in the frequency domain and then in the time domain, and finally mapped according to the CGO period within the mapping period. The mapping period is an integer multiple of the CGO period, and the specific value is determined by the number of CGOs and the SSB index, ensuring the minimum number of CGO periods required to map all SSB indices once.

[0499] These CGOs can be configured for one terminal or multiple terminals. In order to allow multiple terminals to reuse CG-PUSCH, different DMRS ports are allocated to different terminals.

[0500] In this embodiment, the fourth first configuration may be configured by terminal-specific RRC messages or SIB1 signaling. The first configuration is included in terminal-specific signaling or information elements, such as a ConfiguredGrantConfig information element (IE) or an RRC release message.

[0501] In this embodiment, the terminal sends a request message to the network as needed. Specifically, the terminal selects an appropriate transmission beam and selects a CGO based on its corresponding SSB index, and sends the request message through the CGO. The message can be a MAC CE, RRC, or other message.

[0502] Similar to embodiment 1, the request information includes a first indication field, a second indication field and / or a third indication field.

[0503] In this embodiment, the request information may not include the third indication field, and at this time, the beam (SSB index (index)) corresponding to the CGO that sends the request information is defaulted to be the transmission beam for receiving the desired downlink signal or channel.

[0504] In this embodiment, the selection of the transmission beam of the terminal and the base station can be determined by the terminal implementation, and the SSB can be used to perform beam measurement to select a suitable transmission beam. If the channel and signal are SSB, the beam can be updated by measurement each time the SSB is turned on; or the SSB as the root source of the CSI-RS can be selected based on the beam measurement result of the Channel State Information-Reference Signal (CSI-CS). This is not limited in this embodiment. SSB is turned on, indicating that the network device sends SSB. SSB is turned off, indicating that the network device does not send SSB.

[0505] In this embodiment, when the signal channel or channel is SSB, in order to prevent the terminal from initially failing to select a transmission beam through the beam measurement result when SSB is turned on. An initial transmission beam can be configured for the terminal through the fifth first configuration, specifically, an SSB index (index) can be indicated. When there is no optimal beam measurement result, the terminal uses the indicated SSB index (index) to select the best transmission beam, and then selects the corresponding CGO to send WUS. In subsequent transmissions, the transmission beam is updated according to the beam measurement when SSB is turned on.

[0506] Example 5:

[0507] In the embodiment of the present disclosure, a relationship between multiple CGOs and different beams is introduced. The terminal can select a CGO to send a downlink channel or signal request information based on the currently selected beam.

[0508] In this embodiment, considering that the base station may have many beams (SSB indices), many CGOs may need to be configured to correspond to these SSB indices, which may result in excessive CGO resources. In order to reduce resource usage, it is considered to allow further improvements to the mapping relationship between the SSB index and the CGO. One CGO is allowed to correspond to multiple SSB indices, and a method is introduced to indicate a specific SSB index to the network.

[0509] The network device configures multiple CGOs for the terminal.

[0510] When CGO and SSB correspond one to one, one CGO can correspond to one SSB index.

[0511] When CGO and SSB are one-to-many, multiple different CGOs can correspond to one SSB index.

[0512] For a CGO associated with multiple SSB indexes, the correspondence (or association) between the CGO and SSB indexes can be determined as follows:

[0513] Method 1:

[0514] The specific SSB index corresponding to each CGO is configured by the network through configuration parameters. For example, the SSB index corresponding to each CGO is configured through the configuration parameter associated SSB index list.

[0515] Method 2:

[0516] The network device is configured with a common parameter M or a common parameter M is agreed upon by the protocol. The M is used to determine the SSB index corresponding to each CGO.

[0517] For example, M can represent the number of SSB indices that each CGO can use in ascending order of SSB indices. For example, if M = 2, then CGO1 uses SSB indices 0 and 1. CGO2 corresponds to SSB indices 2 and 3, and so on. This is the mapping method within each CGO. When performing CGO mapping, the frequency domain can be used first, then the time domain, and finally the CGO period can be mapped within the mapping period.

[0518] For another example, M may be the modulus of mod. The remainder of the SSB index MOD M corresponds to the index of CGO.

[0519] In this embodiment, the terminal sends SSB / SIB1 request information to the network as needed. The request information may also include the first indication field and / or the second indication field.

[0520] In some embodiments, the request information further includes a third indication field.

[0521] The third indication field can be used to indicate one of multiple SSB indexes corresponding to the CGO that sends the request information.

[0522] In some embodiments, the request information further includes a fourth indication field.

[0523] In some embodiments, the fourth indication field is used to indicate one or more transmission beams for receiving downlink signals or channels that the terminal expects to receive. If the fourth indication field is missing, the multiple transmission beams (SSB indexes) corresponding to the CGO may be defaulted to the multiple transmission beams for receiving downlink signals or channels; or the specific SSB index indicated by the third indication field may be defaulted to the transmission beam for receiving downlink signals or channels.

[0524] The embodiments of the present invention propose a WUS design for waking up cell-specific signals or channels. This allows capable terminals within the cell to send SSB and / or SIB1 wake-up signals to the network as needed, allowing the base station to decide whether to send relevant signals / signaling based on the actual needs of the terminals. Based on this, the network can disable SSB / SIB1 to achieve energy savings based on traffic load, the number of resident devices, and so on. At the same time, the network can enable SSB / SIB1 based on terminal needs to ensure normal communication between the terminal and the network, thereby avoiding a decrease in network service quality.

[0525] 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, or may be arbitrarily combined with the optional implementations of other embodiments.

[0526] 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, or may be arbitrarily combined with the optional implementations of other embodiments.

[0527] The embodiments of the present disclosure also 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 or a core network device) in any of the above methods.

[0528] It should be understood that the division of the various units or modules in the above devices 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 devices, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0529] 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 an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0530] As shown in FIG6A , an embodiment of the present disclosure provides a terminal, wherein the terminal includes:

[0531] The receiving module 5101 is configured to receive a first configuration of a configuration grant physical uplink shared channel CG-PUSCH sent by a network device;

[0532] The sending module 5102 is configured to send request information to the network device on the CG-PUSCH according to the first configuration; the request information is used to request the network device to send downlink transmission to the terminal.

[0533] In some embodiments, the terminal further includes a processing module.

[0534] In some embodiments, the processing module can be used for the terminal to execute information processing related steps in any request information processing method.

[0535] In some embodiments, the terminal may further include: a sending module and / or a receiving module.

[0536] In some embodiments, the sending module and / or the receiving module may correspond to a network interface and / or a transceiver antenna of the terminal.

[0537] In some embodiments, the sending module can be used by the terminal to execute steps related to information sending in any request information processing method.

[0538] In some embodiments, the receiving module may be used by the terminal to execute steps related to information sending in any one of the request information processing methods.

[0539] In some embodiments, the request information includes at least one of the following:

[0540] A first indication is used to request sending a downlink transmission;

[0541] A second indication, used to indicate the type of downlink transmission requested to be sent;

[0542] A third indication is used to indicate the index of the downlink transmission requested to be sent;

[0543] The fourth indication is used to indicate beam information of the desired beam for downlink transmission.

[0544] In some embodiments, any two or more of the first indication, the second indication, the third indication, and the fourth indication share an indication field; or,

[0545] The first indication, the second indication, the third indication, and the fourth indication use different indication fields.

[0546] In some embodiments, the CG-PUSCH includes at least one of the following: a first type CG-PUSCH, a second type CG-PUSCH, a third type CG-PUSCH, and a fourth type CG-PUSCH;

[0547] At least one of the configuration method, activation method and configuration parameters of the first type CG-PUSCH, the second type CG-PUSCH, the third type CG-PUSCH and the fourth type CG-PUSCH is different.

[0548] In some embodiments, the first type CG-PUSCH and the fourth type CG-PUSCH are configured by a radio resource control RRC message; and a CG-PUSCH opportunity CGO of the fourth type CG-PUSCH is associated with a beam;

[0549] The second type CG-PUSCH and the third type CG-PUSCH are configured by an RRC message, and the second type CG-PUSCH and the third type CG-PUSCH are activated by different signaling.

[0550] In some embodiments, the second type CG-PUSCH is activated by first signaling; the first signaling includes specific downlink control information DCI;

[0551] The third type CG-PUSCH is activated by the second signaling; the second signaling includes common DCI and / or notification signaling;

[0552] Notification signaling, used to notify the start or stop of the first transmission; the start of the first transmission corresponds to the deactivation of the third type CG-PUSCH; the stop of the first transmission corresponds to the activation of the third type CG-PUSCH.

[0553] In some embodiments, the first second type CG-PUSCH for sending the request information is determined by the reception time of the first signaling and K2 time units; and / or,

[0554] The first third type CG-PUSCH for sending the request information is determined by the reception time of the second signaling.

[0555] In some embodiments, the first configuration for the first type of CG-PUSCH indicates at least one of the following: a period of the first type of CG-PUSCH; a time domain offset of the first type of CG-PUSCH, indicating an offset of a first resource position of the first type of CG-PUSCH relative to a reference time;

[0556] The first configuration for the second type CG-PUSCH indicates at least: a period of the second type CG-PUSCH;

[0557] The first configuration for the third type CG-PUSCH indicates at least one of the following: a period of the third type CG-PUSCH; a time domain offset of the third type CG-PUSCH, indicating an offset of a first resource position of the third type CG-PUSCH relative to a reference time;

[0558] The first configuration indication for the fourth type of CG-PUSCH indicates at least one of the following: the period of the fourth type of CG-PUSCH; the time domain offset of the fourth type of CG-PUSCH, indicating the offset of the first resource position of the fourth type of CG-PUSCH relative to the reference time.

[0559] In some embodiments, the first type CG-PUSCH, the third type CG-PUSCH and the fourth type CG-PUSCH are all shared by multiple terminals, and different terminals use different DMRS ports to send request information on the same CG-PUSCH.

[0560] In some embodiments, the second signaling further includes at least one of the following:

[0561] Time domain resource location information of the third type CG-PUSCH;

[0562] Frequency domain resource location information of the third type CG-PUSCH.

[0563] In some embodiments, the first configuration of the third type CG-PUSCH further includes:

[0564] Time domain resource location information of the third type CG-PUSCH;

[0565] Frequency domain resource location information of the third type CG-PUSCH.

[0566] In some embodiments, according to the first configuration, sending request information to the network device on the CG-PUSCH includes:

[0567] Ignore the second configuration sent by the network device, and send request information to the network device on the CG-PUSCH according to the first configuration; the second configuration is a configuration indicating that the network device is in the network node NES state.

[0568] In some embodiments, the second configuration includes at least one of the following:

[0569] Cell discontinuous reception (DRX) configuration;

[0570] Cell discontinuous transmission DTX configuration.

[0571] In some embodiments, downlink transmission includes at least:

[0572] Synchronization signal broadcast block SSB;

[0573] System Information Block SIB.

[0574] FIG6B is a network device provided by an embodiment of the present disclosure, wherein the network device includes:

[0575] The sending module 5201 is configured to send a first configuration of a configuration grant physical uplink shared channel CG-PUSCH to the terminal;

[0576] The receiving module 5202 is configured to receive request information sent by the terminal on the CG-PUSCH according to the first configuration; the request information is used to request the network device to send downlink transmission to the terminal.

[0577] Any step related to information processing in the request information processing method executed by the device.

[0578] In some embodiments, the network device may further include: a sending module and / or a receiving module.

[0579] In some embodiments, the sending module and / or the receiving module may correspond to a network interface and / or a transceiver antenna of a network device.

[0580] In some embodiments, the request information includes at least one of the following:

[0581] A first indication, used to indicate a request to send a downlink transmission;

[0582] A second indication, used to indicate the type of downlink transmission requested to be sent;

[0583] A third indication is used to indicate the index of the downlink transmission requested to be sent;

[0584] The fourth indication is used to indicate the beam information of downlink transmission.

[0585] In some embodiments, any two or more of the first indication, the second indication, the third indication, and the fourth indication share an indication field; or,

[0586] The first indication, the second indication, the third indication, and the fourth indication use different indication fields.

[0587] In some embodiments, the CG-PUSCH includes at least one of the following:

[0588] Type 1 CG-PUSCH, Type 2 CG-PUSCH, Type 3 CG-PUSCH, and Type 4 CG-PUSCH;

[0589] At least one of the configuration method, activation method and configuration parameters of the first type CG-PUSCH, the second type CG-PUSCH, the third type CG-PUSCH and the fourth type CG-PUSCH is different.

[0590] In some embodiments, the first type CG-PUSCH and the fourth type CG-PUSCH are configured by an RRC message; and a CG-PUSCH opportunity CGO of the fourth type CG-PUSCH is associated with a beam;

[0591] The second type CG-PUSCH and the third type CG-PUSCH are configured by an RRC message, and the second type CG-PUSCH and the third type CG-PUSCH are activated by different signaling.

[0592] In some embodiments, the second type CG-PUSCH is activated by first signaling; the first signaling includes specific downlink control information DCI;

[0593] The third type CG-PUSCH is activated by the second signaling; the second signaling includes common DCI and / or notification signaling;

[0594] Notification signaling, used to notify the start or stop of the first transmission; the start of the first transmission corresponds to the deactivation of the third type CG-PUSCH; the stop of the first transmission corresponds to the activation of the third type CG-PUSCH.

[0595] In some embodiments, the first second type CG-PUSCH for sending the request information is determined by the reception time of the first signaling and K2 time units; and / or,

[0596] The first third type CG-PUSCH for sending the request information is determined by the reception time of the second signaling.

[0597] In some embodiments, the first configuration for the first type of CG-PUSCH indicates at least one of the following: a period of the first type of CG-PUSCH; a time domain offset of the first type of CG-PUSCH, indicating an offset of a first resource position of the first type of CG-PUSCH relative to a reference time;

[0598] The first configuration indication for the second type CG-PUSCH: a period of the first type CG-PUSCH;

[0599] The first configuration indication for the third type CG-PUSCH indicates at least one of the following: the period of the third type CG-PUSCH; the time domain offset of the third type CG-PUSCH, indicating the offset of the first resource position of the first type CG-PUSCH relative to the reference time.

[0600] In some embodiments, the first type CG-PUSCH, the third type CG-PUSCH and the fourth type CG-PUSCH are all shared by multiple terminals, and different terminals use different DMRS ports to send request information on the same CG-PUSCH.

[0601] In some embodiments, the second signaling further includes at least one of the following:

[0602] Time domain resource location information of the third type CG-PUSCH;

[0603] Frequency domain resource location information of the third type CG-PUSCH.

[0604] In some embodiments, the first configuration of the third type CG-PUSCH further includes:

[0605] Time domain resource location information of the third type CG-PUSCH;

[0606] Frequency domain resource location information of the third type CG-PUSCH.

[0607] In some embodiments, the receiving module is configured to ignore the second configuration sent by the network device and send request information to the network device on CG-PUSCH according to the first configuration; the second configuration is a configuration indicating that the network device is in the network node NES state.

[0608] In some embodiments, the second configuration includes at least one of the following:

[0609] Cell discontinuous reception (DRX) configuration;

[0610] Cell discontinuous transmission DTX configuration.

[0611] In some embodiments, downlink transmission includes at least:

[0612] SSB;

[0613] SIB.

[0614] An embodiment of the present disclosure further provides a communication device, which may include: one or more processors; wherein the processor is used to call instructions to enable the communication device to execute the request information processing method that can be implemented in any of the aforementioned embodiments.

[0615] 7A and / or 7B , the communication device 8100 further includes one or more memories 8102 for storing instructions. Alternatively, all or part of the memories 8102 may be located outside the communication device 8100.

[0616] The communication device may be the aforementioned terminal and network device. In some embodiments, the network device may be a master node and / or an auxiliary node.

[0617] In some embodiments, the communication device 8100 further includes one or more transceivers 8103. When the communication device 8100 includes one or more transceivers 8103, the communication steps such as sending and receiving in the above method are performed by the transceiver 8103, and the other steps are performed by the processor 8101.

[0618] In some embodiments, a transceiver may include a receiver and a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0619] Optionally, the communication device 8100 further includes one or more interface circuits 8104, which are connected to the memory 8102. The interface circuits 8104 can be used to receive signals from the memory 8102 or other devices, and can be used to send signals to the memory 8102 or other devices. For example, the interface circuits 8104 can read instructions stored in the memory 8102 and send the instructions to the processor 8101.

[0620] The communication device 8100 described in the above embodiment may be a network device or a terminal, but the scope of the communication device 8100 described in the present disclosure is not limited thereto, and the structure of the communication device 8100 may not be limited by FIG. 7A. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: (1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data 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.

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

[0622] The chip 8200 includes one or more processors 8201 , and the processor 8201 is used to call instructions so that the chip 8200 executes any of the above request information processing methods.

[0623] In some embodiments, chip 8200 further includes one or more interface circuits 8202, which are connected to memory 8203. Interface circuit 8202 can be used to receive signals from memory 8203 or other devices, and can be used to send signals to memory 8203 or other devices. For example, interface circuit 8202 can read instructions stored in memory 8203 and send the instructions to processor 8201. Optionally, the terms interface circuit, interface, transceiver pin, and transceiver are interchangeable.

[0624] In some embodiments, the chip 8200 further includes one or more memories 8203 for storing instructions. Alternatively, all or part of the memories 8203 may be outside the chip 8200.

[0625] The present disclosure also provides a storage medium having instructions stored thereon, which, when executed on the communication device 8100, causes the communication device 8100 to execute 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 may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but may also be a transient storage medium.

[0626] The present disclosure further provides a program product, which, when executed by the communication device 8100, enables the communication device 8100 to execute any of the above request information processing methods. Optionally, the program product is a computer program product.

[0627] The present disclosure also provides a computer program, which, when executed on a computer, enables the computer to execute any one of the above request information processing methods.

[0628] Other embodiments of the present invention will readily occur to those skilled in the art after considering the specification and practicing the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the present invention that follow the general principles of the present invention and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered as exemplary only, with the true scope and spirit of the present invention being indicated by the following claims.

[0629] It should be understood that the embodiments of the present disclosure are not limited to the precise structures described above and shown in the drawings, and various modifications and changes can be made without departing from the scope thereof. The scope of the embodiments of the present disclosure is limited only by the appended claims.

Claims

1. A method for processing request information, wherein, Executed by a terminal, the method includes: Receiving a first configuration for configuring an authorized physical uplink shared channel CG-PUSCH sent by a network device; Sending request information to the network device on the CG-PUSCH according to the first configuration; the request information is used to request the network device to send downlink transmission to the terminal.

2. The method according to claim 1, wherein The request information includes at least one of the following: A first indication for requesting to send the downlink transmission; A second indication for indicating the type of the downlink transmission for which the request is sent; A third indication for indicating the index of the downlink transmission for which the request is sent; A fourth indication for indicating the beam information of the desired beam of the downlink transmission.

3. The method according to claim 2, wherein Any two or more of the first indication, the second indication, the third indication, and the fourth indication share one indication field; or, The first indication, the second indication, the third indication, and the fourth indication use different indication fields.

4. The method according to any one of claims 1 to 3, wherein, The CG-PUSCH includes at least one of the following: a first type of CG-PUSCH, a second type of CG-PUSCH, a third type of CG-PUSCH, and a fourth type of CG-PUSCH; At least one of the configuration method, activation method, and configuration parameters of the first type of CG-PUSCH, the second type of CG-PUSCH, the third type of CG-PUSCH, and the fourth type of CG-PUSCH is different.

5. The method according to claim 4, wherein, The first type of CG-PUSCH and the fourth type of CG-PUSCH are configured by a radio resource control RRC message; and the CG-PUSCH occasion CGO of the fourth type of CG-PUSCH is associated with a beam; The second type of CG-PUSCH and the third type of CG-PUSCH are configured by an RRC message, and the second type of CG-PUSCH and the third type of CG-PUSCH are activated by different signaling.

6. The method according to claim 5, wherein, The second type of CG-PUSCH is activated by a first signaling; the first signaling includes specific downlink control information DCI; The third type of CG-PUSCH is activated by a second signaling; the second signaling includes common DCI and / or a notification signaling; The notification signaling is used to notify the start or stop of a first transmission; the start of the first transmission corresponds to the deactivation of the third type of CG-PUSCH; the stop of the first transmission corresponds to the activation of the third type of CG-PUSCH.

7. The method according to claim 6, wherein, The first second type of CG-PUSCH for sending the request information is determined by the reception time of the first signaling and K2 time units; or, The first third type of CG-PUSCH for sending the request information is determined by the reception time of the second signaling.

8. The method according to claim 4, wherein, The first configuration for the first type of CG-PUSCH indicates at least one of the following: the period of the first type of CG-PUSCH and the time-domain offset of the first type of CG-PUSCH; the time-domain offset of the first type of CG-PUSCH indicates the offset of the first resource position of the first type of CG-PUSCH relative to the reference time. The first configuration for the second type of CG-PUSCH indicates at least: the period of the second type of CG-PUSCH. The first configuration for the third type of CG-PUSCH indicates at least one of the following: the period of the third type of CG-PUSCH and the time-domain offset of the third type of CG-PUSCH; the time-domain offset of the third type of CG-PUSCH indicates the offset of the first resource position of the third type of CG-PUSCH relative to the reference time. The first configuration for the fourth type of CG-PUSCH indicates at least one of the following: the period of the fourth type of CG-PUSCH and the time-domain offset of the fourth type of CG-PUSCH; the time-domain offset of the fourth type of CG-PUSCH indicates the offset of the first resource position of the fourth type of CG-PUSCH relative to the reference time.

9. The method according to any one of claims 4 to 8, wherein, The first type of CG-PUSCH, the third type of CG-PUSCH, and the fourth type of CG-PUSCH are shared by multiple terminals, and different terminals use different demodulation reference signal DMRS ports when using the same CG-PUSCH.

10. The method according to claim 6, wherein, The second signaling further includes at least one of the following: The time-domain resource position information of the third type of CG-PUSCH; The frequency-domain resource position information of the third type of CG-PUSCH.

11. The method according to any one of claims 4 to 9, wherein The first configuration of the third type of CG-PUSCH further includes at least one of the following: The time-domain resource position information of the third type of CG-PUSCH; The frequency-domain resource position information of the third type of CG-PUSCH.

12. The method according to any one of claims 1 to 10, wherein, According to the first configuration, sending a request message to the network device on the CG-PUSCH includes: Ignoring the second configuration sent by the network device and sending a request message to the network device on the CG-PUSCH according to the first configuration; the second configuration is a configuration indicating that the network device is in the network node NES state.

13. The method according to claim 12, wherein, The second configuration includes at least one of the following: Cell discontinuous reception DRX configuration; Cell discontinuous transmission DTX configuration.

14. The method according to any one of claims 1 to 13, wherein The downlink transmission at least includes: Synchronization signal broadcast block SSB; System information block SIB.

15. A method for processing request information, wherein, Executed by the network device, the method includes: Sending a first configuration for configuring the physical uplink shared channel CG-PUSCH to the terminal; Receiving, on the CG-PUSCH, a request message sent by the terminal according to the first configuration; the request message is used to request the network device to send downlink transmission to the terminal.

16. The method according to claim 15, wherein, The request message includes at least one of the following: A first indication for indicating a request to send the downlink transmission; A second indication for indicating the type of the downlink transmission requested to be sent. A third indication for indicating an index of the downlink transmission for which the request is sent; A fourth indication for indicating beam information of the downlink transmission.

17. The method according to claim 16, wherein Any two or more of the first indication, the second indication, the third indication, and the fourth indication share an indication field; or The first indication, the second indication, the third indication, and the fourth indication use different indication fields.

18. The method according to any one of claims 15 to 17, wherein, The CG-PUSCH includes at least one of the following: A first type of CG-PUSCH, a second type of CG-PUSCH, a third type of CG-PUSCH, and a fourth type of CG-PUSCH; At least one of the configuration method, activation method, and configuration parameters of the first type of CG-PUSCH, the second type of CG-PUSCH, the third type of CG-PUSCH, and the fourth type of CG-PUSCH is different.

19. The method according to claim 18, wherein The first type of CG-PUSCH and the fourth type of CG-PUSCH are configured by an RRC message; and the CGO of the CG-PUSCH timing of the fourth type of CG-PUSCH is associated with a beam; The second type of CG-PUSCH and the third type of CG-PUSCH are configured by an RRC message, and the second type of CG-PUSCH and the third type of CG-PUSCH are activated by different signaling.

20. The method according to claim 19, wherein The second type of CG-PUSCH is activated by a first signaling; the first signaling includes specific downlink control information DCI; The third type of CG-PUSCH is activated by a second signaling; the second signaling includes common DCI and / or a notification signaling; The notification signaling is used to notify the start or stop of a first transmission; the start of the first transmission corresponds to the deactivation of the third type of CG-PUSCH; the stop of the first transmission corresponds to the activation of the third type of CG-PUSCH.

21. The method according to claim 20, wherein The first second type of CG-PUSCH for sending the request information is determined by the reception time of the first signaling and K2 time units; and / or The first third type of CG-PUSCH for sending the request information is determined by the reception time of the second signaling.

22. The method according to claim 20, wherein, A first configuration for the first type of CG-PUSCH indicates at least one of the following: the period of the first type of CG-PUSCH and the time domain offset of the first type of CG-PUSCH; the time domain offset of the first type of CG-PUSCH indicates the offset of the first resource position of the first type of CG-PUSCH relative to a reference time; A first configuration for the second type of CG-PUSCH indicates: the period of the first type of CG-PUSCH; The first configuration for the third type of CG-PUSCH indicates at least one of the following: the period of the third type of CG-PUSCH and the time-domain offset of the third type of CG-PUSCH; the time-domain offset of the third type of CG-PUSCH indicates the offset of the first resource position of the first type of CG-PUSCH relative to the reference time.

23. The method according to any one of claims 20 to 22, wherein The first type of CG-PUSCH, the third type of CG-PUSCH, and the fourth type of CG-PUSCH are shared by multiple terminals. When different terminals use the same CG-PUSCH, they use different demodulation reference signal DMRS ports.

24. The method according to claim 20, wherein, The second signaling further includes at least one of the following: The time-domain resource position information of the third type of CG-PUSCH; The frequency-domain resource position information of the third type of CG-PUSCH.

25. The method according to any one of claims 18 to 23, wherein The first configuration of the third type of CG-PUSCH further includes: The time-domain resource position information of the third type of CG-PUSCH; The frequency-domain resource position information of the third type of CG-PUSCH.

26. The method according to any one of claims 18 to 23, wherein Receiving, according to the first configuration, request information sent by a terminal on the CG-PUSCH includes: Ignoring the second configuration and receiving, according to the first configuration, request information sent by a terminal on the CG-PUSCH; the second configuration is a configuration indicating that the network device is in the network node NES state.

27. The method according to claim 26, wherein The second configuration includes at least one of the following: Cell discontinuous reception DRX configuration; Cell discontinuous transmission DTX configuration.

28. The method according to any one of claims 15 to 27, wherein The downlink transmission at least includes: Synchronization signal broadcast block SSB; System information block SIB.

29. A terminal, wherein, The terminal includes: A receiving module, configured to receive the first configuration of the configured grant physical uplink shared channel CG-PUSCH sent by the network device; A transmitting module, configured to send, according to the first configuration, request information to the network device on the CG-PUSCH; the request information is used to request the network device to send downlink transmission to the terminal.

30. A network device, wherein, The network device includes: A transmitting module, configured to send the first configuration of the configured grant physical uplink shared channel CG-PUSCH to the terminal; A receiving module, configured to receive, according to the first configuration, request information sent by the terminal on the CG-PUSCH; the request information is used to request the network device to send downlink transmission to the terminal.

31. A communication device, wherein, The communication device includes: One or more processors; Wherein, the processor is used to call instructions to enable the communication device to execute the method described in any one of claims 1 to 14 and / or claims 15 to 28.

32. A storage medium, wherein, The storage medium stores instructions that, when running on the communication device, enable the communication device to execute the method described in any one of claims 1 to 14 and / or claims 15 to 28.

Images