Uplink information scheduling method and apparatus, terminal, and network side device

Abstract

The present application relates to the technical field of wireless communications, and discloses an uplink information scheduling method and apparatus, a terminal, and a network side device. The uplink information scheduling method in the embodiments of the present application comprises: a terminal receives scheduling information from a network side device, the scheduling information being used for scheduling uplink information transmission of the terminal in a non-connected state; and on the basis of the scheduling information, the terminal sends uplink information to the network side device.

Description

Uplink information scheduling method, device, terminal and network side equipment

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the China Patent Office on December 12, 2023, with application number 202311710219.6 and invention name “Uplink information scheduling method, device, terminal and network side equipment”. The entire contents of the Chinese patent application are incorporated herein by reference. Technical Field

[0003] The present application belongs to the field of wireless communication technology, and specifically relates to an uplink information scheduling method, apparatus, terminal, and network-side equipment. Background Art

[0004] In the prior art, a terminal can be configured to establish a connection with the network, i.e., in a connected state. In the connected state, the terminal can perform data transmission with a network-side device, for example, the terminal sends data to the network-side device, or the terminal receives data sent by the network-side device, thereby achieving uplink or downlink data transmission. Data transmission in a non-connected state is a special transmission mechanism that allows user equipment (UE) to transmit and receive UE-dedicated data with the network without entering a connected state. This avoids excessive signaling overhead and excessive latency caused by the Radio Resource Control (RRC) state transition and the RRC connection establishment process, thereby completing data transmission through a simple signaling process.

[0005] However, how to implement uplink data transmission in a non-connected state is a technical problem that needs to be solved urgently. Summary of the Invention

[0006] The embodiments of the present application provide an uplink information scheduling method, apparatus, terminal, and network-side equipment, which can solve the problem of uplink data transmission in a non-connected state.

[0007] In a first aspect, an uplink information scheduling method is provided, which includes: a terminal receives scheduling information from a network side device, wherein the scheduling information is used to schedule uplink information transmission when the terminal is in a non-connected state; and the terminal sends the uplink information to the network side device based on the scheduling information.

[0008] In a second aspect, an uplink information scheduling method is provided, which includes: a network side device sends scheduling information to a terminal, wherein the scheduling information is used to schedule uplink information transmission when the terminal is in a non-connected state; and the network side device receives the uplink information from the terminal.

[0009] In the third aspect, an uplink information scheduling device is provided, which includes: a first receiving module for receiving scheduling information from a network side device, wherein the scheduling information is used to schedule uplink information transmission when the terminal is in a non-connected state; and a first sending module for sending the uplink information to the network side device based on the scheduling information.

[0010] In a fourth aspect, an uplink information scheduling device is provided, which includes: a second sending module for sending scheduling information to a terminal, wherein the scheduling information is used to schedule uplink information transmission when the terminal is in a non-connected state; and a second receiving module for receiving the uplink information from the terminal.

[0011] In a fifth aspect, a terminal is provided, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented.

[0012] In the sixth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the communication interface is used to: receive scheduling information from a network side device, the scheduling information being used to schedule uplink information transmission when the terminal is in a non-connected state; and send the uplink information to the network side device based on the scheduling information.

[0013] In the seventh aspect, a network side device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the second aspect are implemented.

[0014] In the eighth aspect, a network side device is provided, including a processor and a communication interface, wherein the communication interface is used to: send scheduling information to a terminal, the scheduling information being used to schedule uplink information transmission when the terminal is in a non-connected state; and receive the uplink information from the terminal.

[0015] In the ninth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented.

[0016] In the tenth aspect, a wireless communication system is provided, comprising: a terminal and a network side device, wherein the terminal can be used to execute the steps of the method described in the first aspect, and the network side device can be used to execute the steps of the method described in the second aspect.

[0017] In the eleventh aspect, a chip is provided, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

[0018] In the twelfth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0019] In an embodiment of the present application, scheduling information is received from a network-side device through a terminal, and the scheduling information is used to schedule uplink information transmission when the terminal is in a non-connected state; the terminal sends the uplink information to the network-side device based on the scheduling information, thereby realizing the scheduling of uplink information for the terminal in the non-connected state, reducing signaling overhead, and reducing uplink information transmission delay and terminal power consumption. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] FIG1 shows a block diagram of a wireless communication system to which embodiments of the present application may be applied;

[0021] FIG2 is a flow chart of an uplink information scheduling method according to an embodiment of the present application;

[0022] FIG3 is a second flow chart of the uplink information scheduling method provided in an embodiment of the present application;

[0023] FIG4 is a third flow chart of the uplink information scheduling method provided in an embodiment of the present application;

[0024] FIG5 is a schematic diagram of a structure of an uplink information scheduling device according to an embodiment of the present application;

[0025] FIG6 is a second structural diagram of an uplink information scheduling device according to an embodiment of the present application;

[0026] FIG7 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0027] FIG8 is a schematic diagram of the hardware structure of a terminal provided in an embodiment of the present application;

[0028] FIG9 is a schematic diagram of the hardware structure of the network side device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0029] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0030] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0031] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.

[0032] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for example purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th Generation (6G) communication systems.

[0033] FIG1 is a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device (Wearable Device), an aircraft (Flight Vehicle), a vehicle-mounted device (VUE), a ship-mounted device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), a game console, a personal computer (PC), an ATM, or a self-service machine, or other terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be called a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (WLAN) access point (AP) or a wireless fidelity (WiFi) node, etc.Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home evolved Node B (home evolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the relevant field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0034] In order to facilitate a clearer understanding of the technical solutions provided by the embodiments of the present application, some relevant knowledge is first introduced as follows.

[0035] 1. Paging:

[0036] In NR, paging can be divided into the following types according to the source of the message:

[0037] 5th Generation Mobile Communication Technology Core Network (5GC) paging: paging is initiated by the 5GC. When downlink data arrives for the UE in the RRC idle state (RRC_IDLE), the 5GC notifies the UE through a Paging message.

[0038] RAN paging, that is, paging is initiated by the gNB. When downlink data arrives for a UE in the RRC_INACTIVE state, the gNB notifies the UE through a RAN Paging message.

[0039] The final paging message is sent by the gNB to the UE via the air interface.

[0040] The paging message is carried by the Paging Control Channel (PCCH) logical channel, and the data block of the PCCH logical channel is carried by the Paging Channel (PCH) transport channel, and the data block of the PCH transport channel is carried by the Physical Downlink Shared Channel (PDSCH) physical channel. Since PDSCH is a downlink shared physical channel, it can carry not only the PCH transport channel but also the Downlink Shared Channel (DL-SCH) transport channel. Therefore, before receiving a paging message, the terminal needs to first monitor the Physical Downlink Control Channel (PDCCH) physical channel, and then determine whether the network has sent a paging message to the terminal in this paging cycle based on whether the PDCCH physical channel carries the Paging Radio Network Temporary Identifier (P-RNTI).

[0041] In addition to the paging message, the downlink control information (DCI) for scheduling paging may also carry a short message and indicate whether there are available tracking reference signal (TRS) resources.

[0042] A paging message carries a paging record list (PagingRecordList), which contains at least one and at most maxNrofPageRec paging records (PagingRecord). Each PagingRecord carries the paging identity (ue_Identity) of the paged UE. That is, a paging message can indicate that at most maxNrofPageRec UEs are paged.

[0043] The paged UE has two identifiers: one for paging UEs in idle state, namely ng-5G-S-TMSI; the other for paging UEs in inactive state, namely full-length inactive radio network temporary identifier (full I-RNTI). The UE receiving the paging message is in either idle state or inactive state.

[0044] 2. Paging Frame (PF) and Paging Occasion (PO)

[0045] PF and PO are two important paging related contents. A paging frame (PF) is a radio frame that can contain one or more POs. A PO is a subframe that may contain a paging message.

[0046] If the terminal knows the paging cycle, PF and PO, it can know the exact time to receive the paging message. In order to reduce the power consumption of the UE in the RRC_IDLE / RRC_INACTIVE state, the UE uses discontinuous reception (DRX) to receive paging messages. There are several PFs in a DRX cycle, and one PF corresponds to several POs. The UE only wakes up once in a DRX cycle to monitor one PO. The UE monitors one PO in each DRX cycle. PO is a set of PDCCH monitoring opportunities and can include multiple time slots in which paging DCI can be sent, such as subframes or orthogonal frequency division multiplexing (OFDM) symbols.

[0047] 3. Random Access Process

[0048] In the prior art, the random access procedure may be a contention-based random access procedure or a non-contention-based random access procedure. The random access procedure may be a four-step random access procedure (also called a Type-1 random access procedure) or a two-step random access procedure (also called a Type-2 random access procedure).

[0049] In the contention-based 4-step random access procedure (RACH), the UE first sends Message 1 (Msg1) to the network, which includes a preamble. After the network detects the preamble, it sends a Msg2 / RAR (Random Access Response) message, which includes the number of the preamble detected by the network and the uplink radio resources allocated to the UE to send Msg3. After receiving Msg2, the UE confirms that at least one of the preamble numbers carried in Msg2 is consistent with the number of the preamble it sent, and then sends Msg3 containing contention resolution information based on the resources indicated by the RAR. After receiving Msg3, the network sends Msg4 containing contention resolution information. After receiving Msg4, the UE confirms that the contention resolution information is consistent with the one sent by the terminal itself in Msg3, thus completing the 4-step random access.

[0050] The network includes uplink grant (UL grant) information in the RAR, which indicates the MSG3 Physical Uplink Shared Channel (PUSCH) scheduling information and includes information such as RAPID (RACH preamble ID), Temporary Cell Radio Network Temporary Identifier (TC-RNTI), and Tracking Area (TA). If the network does not receive the MSG3 PUSCH, it can schedule the retransmission of the MSG3 PUSCH in the PDCCH scrambled by the TC-RNTI.

[0051] For the contention random access process, different UEs randomly select preambles for transmission. In this way, different UEs may select the same preamble to send on the same time-frequency radio resources (RO resources). This situation can be understood as a UE preamble conflict. In this case, different UEs will receive the same RAR. At this time, different UEs will transmit MSG.3PUSCH according to the scheduling information in the RAR UL grant. Since the existing technology does not support repeated transmission of MSG.3PUSCH, the network can only decode the PUSCH (including contention resolution information) sent by one UE on one MSG3 PUSCH scheduling resource. Therefore, the network will include the contention resolution information received in MSG3 in MSG4. If the contention resolution information in MSG4 received by the UE matches the contention resolution information sent by the UE in MSG3 PUSCH, the UE considers that the contention resolution is successful. If they do not match, the contention resolution is considered unsuccessful.

[0052] If the contention resolution is unsuccessful, the UE reselects RACH transmission resources, performs PRACH transmission, and makes the next random access attempt.

[0053] In the two-step random access process 2-step RACH, the first step is for the UE to send MsgA to the network side. After receiving MsgA, the network side sends a MsgB message to the UE. If the UE does not receive MsgB within a certain period of time, the UE will increment the counter that counts the number of times MsgA is sent and resend MsgA. If the counter that counts the number of times MsgA is sent reaches a certain threshold, the UE will switch from the 2-step random access process to the 4-step random access process. MsgA includes the MsgA preamble part and the MsgA PUSCH part. The preamble part is sent on the RO used for 2-step RACH, and the PUSCH part is sent on the MsgA PUSCH resources associated with the sending of the MsgA preamble and the RO. MsgA PUSCH resources are a set of PUSCH resources configured relative to each PRACH slot, including time-frequency resources and demodulation reference signal (DMRS) resources.

[0054] 4. PDCCH

[0055] The PDCCH is the only downlink control channel in NR, and the data carried by the PDCCH is the DCI. DCI primarily contains PDSCH or PUSCH transmission resource scheduling information, as well as uplink power control indicators, slot format indicators, and non-data-mapped PRBs and OFDM symbols. After undergoing a series of scrambling, modulation, and coding processes, the DCI is mapped to physical resources in units of Control Channel Elements (CCEs).

[0056] PDCCH involves two important aspects. The first is the resource for transmitting control information, namely the Control Resource Set (CORESET). For each DCI, L = 1, 2, 4, 8 or 16 Control Channel Elements (CCE) can be allocated, where the number of CCEs in the DCI is represented by the aggregation level (AL). DCI with AL = L will be mapped to the CORESET configured on the network side. The other is how the UE obtains control information from the CORESET. The UE obtains control information by monitoring the CORESET at a specified monitoring occasion. This process is achieved by blind decoding the candidate set (PDCCH Candidate) in the configured search space (Search Space).

[0057] The following describes in detail the uplink information scheduling method, apparatus, terminal, and network-side equipment provided in the embodiments of the present application through some embodiments and their application scenarios in conjunction with the accompanying drawings.

[0058] Currently, when a terminal is in a connected state, it can transmit data with network-side devices, for example, sending data to or receiving data from the network-side device, thereby implementing uplink or downlink data transmission. However, there is no solution for transmitting uplink data in a disconnected state. There is also no solution for sending feedback / response information for downlink data in a disconnected state.

[0059] In order to achieve the above-mentioned transmission of uplink information in the non-connected state and reduce latency and power consumption, this application proposes to send scheduling information related to uplink information in the non-connected state (such as uplink data or uplink feedback information) through existing paging PDSCH or paging DCI or other physical layer signaling, and defines the relevant information structure of the scheduling information.

[0060] FIG2 is a flow chart of an uplink information scheduling method according to an embodiment of the present application. The method is applied to a terminal. As shown in FIG2 , the method includes steps 201 and 202.

[0061] Step 201: The terminal receives scheduling information from a network-side device, where the scheduling information is used to schedule uplink information transmission when the terminal is in a non-connected state.

[0062] Step 202: The terminal sends the uplink information to the network side device based on the scheduling information.

[0063] Optionally, the network-side device sends scheduling information to the terminal in the non-connected state, where the scheduling information is used to schedule uplink information transmission by the terminal in the non-connected state. The terminal receives the scheduling information from the network-side device; based on the scheduling information, the terminal sends the uplink information to the network-side device while in the non-connected state; and the network-side device receives the uplink information from the terminal.

[0064] Optionally, the disconnected state includes at least one of the following:

[0065] Radio Resource Connection (RRC) idle state;

[0066] RRC inactive state;

[0067] Standby state;

[0068] Terminal status after RRC release and before random access;

[0069] A specific terminal state before random access.

[0070] Optionally, the uplink information includes at least one of the following:

[0071] In the non-connected state, feedback information or response information to be transmitted by the terminal for downlink data transmission;

[0072] control information to be transmitted by the terminal in the non-connected state;

[0073] The data information to be transmitted by the terminal in the non-connected state;

[0074] When the terminal does not perform random access and is in a non-connected state, feedback information or response information to be transmitted by the terminal for downlink data transmission;

[0075] When the terminal does not perform random access and is in a non-connected state, control information to be transmitted by the terminal;

[0076] When the terminal does not perform random access and is in a non-connected state, the terminal has data information to be transmitted.

[0077] It should be noted that downlink data transmission refers to downlink data transmission by a terminal in a non-connected state. The data information may include small data or normal data. The feedback information or response information may be an acknowledgment (ACK) or a negative acknowledgment (NACK) information.

[0078] Optionally, the type of the scheduling information includes at least one of the following: a medium access control (MAC) control element (CE); RRC; DCI; a specific downlink physical layer message.

[0079] Optionally, the scheduling information includes at least one of the following:

[0080] UE ID supporting the uplink information transmission;

[0081] first indication information, used to indicate whether the terminal is allowed to perform the uplink information transmission;

[0082] The number of bits of the uplink information transmission;

[0083] an upper limit on the number of bits of the uplink information transmission;

[0084] Time domain information of transmission resources of the uplink information;

[0085] Frequency domain information of transmission resources of the uplink information;

[0086] a period of transmission resources for the uplink information;

[0087] The coding and modulation method for uplink information transmission;

[0088] A transport block size quantization coefficient for uplink information transmission;

[0089] Redundancy version number of the uplink information transmission;

[0090] duration of the uplink information transmission;

[0091] The second indication information is used to indicate the encryption algorithm for transmitting the uplink information.

[0092] In an embodiment of the present application, scheduling information is received from a network-side device through a terminal, and the scheduling information is used to schedule uplink information transmission when the terminal is in a non-connected state; the terminal sends the uplink information to the network-side device based on the scheduling information, thereby realizing the scheduling of uplink information for the terminal in the non-connected state, reducing signaling overhead, and reducing uplink information transmission delay and terminal power consumption.

[0093] Optionally, the implementation of the terminal receiving the scheduling information from the network-side device in step 201 may include: the terminal receiving the scheduling information from the network-side device through a target resource, wherein the target resource includes at least one of the following:

[0094] 1) Paging resources, including: paging physical downlink control channel (PDCCH) and / or paging physical downlink shared channel (PDSCH);

[0095] 2) Specific downlink physical layer signaling or channel, the specific downlink physical layer signaling or channel is determined according to the paging resource, the specific downlink physical layer signaling or channel has a first association relationship with the paging resource, or the specific downlink physical layer signaling or channel satisfies a relative position relationship with the paging resource.

[0096] Optionally, the relative position relationship is indicated by a DCI carried by a paging PDCCH.

[0097] Optionally, the scheduling information is associated with a target identification ID of the terminal; or, the scheduling information is associated with a paging message of the terminal.

[0098] Optionally, the order of the scheduling information in the target resource is associated with the order of the target IDs of the terminals; or, the scheduling information is transmitted together with part or all of the target IDs of the terminals.

[0099] Optionally, the target ID is determined according to at least one of the following:

[0100] User equipment UE ID;

[0101] Tracking area index TA index;

[0102] Terminal priority level;

[0103] Terminal type;

[0104] Terminal capability level.

[0105] Optionally, the scheduling information has a second association relationship with the paging message of the terminal, and the second association relationship includes at least one of the following:

[0106] 1) The order of the scheduling information in the target resource is associated with the order of the paging message of the terminal in the corresponding paging PDSCH;

[0107] 2) The scheduling information is transmitted together with the paging message of the terminal;

[0108] 3) The scheduling information and the paging message of the terminal are located on different PDSCHs, and the PDSCH corresponding to the scheduling information and the PDSCH corresponding to the paging message of the terminal share part of the same scheduling information.

[0109] For example, the PDSCH corresponding to the scheduling information and the PDSCH corresponding to the paging message of the terminal share the FDRA related field in the scheduling information (this field is used to indicate the location of frequency domain resources), that is, the PDSCH corresponding to the scheduling information and the PDSCH corresponding to the paging message of the terminal have the same frequency domain resource position, and differ by a certain offset in the time domain.

[0110] For example, a certain offset in the time domain can be achieved based on at least one of the following:

[0111] (1) predefined by the offset protocol;

[0112] (2) The offset is additionally configured by the network through any one of RRC, MAC-CE, or DCI;

[0113] (3) The time domain position of the PDSCH corresponding to the scheduling information is indicated separately.

[0114] Optionally, the scheduling information satisfies at least one of the following:

[0115] (a) The scheduling information is carried in the paging DCI or the paging PDCCH;

[0116] The paging DCI is carried by the corresponding paging PDCCH.

[0117] (b) The scheduling information is carried in the paging PDSCH;

[0118] (c) a portion of the scheduling information is carried in the paging PDSCH, and the remaining portion of the scheduling information is carried in the paging DCI or the paging PDCCH;

[0119] That is, at least part of the scheduling information is carried in the paging PDSCH, and the rest of the scheduling information is carried in the paging PDCCH.

[0120] (d) the scheduling information is carried in a paging message of the terminal;

[0121] (e) The scheduling information is carried in a specific downlink physical layer signaling or channel.

[0122] Optionally, the scheduling information is carried in the paging DCI and includes at least one of the following:

[0123] Reusing or multiplexing at least one bit in the paging DCI to carry the scheduling information;

[0124] Use a paging DCI scrambled by a specific radio network temporary identifier RNTI to carry the scheduling information;

[0125] The scheduling information is carried in the short message field in the paging DCI;

[0126] The scheduling information is carried in the paging DCI and includes at least bits of the short message domain.

[0127] Optionally, the scheduling information is carried in the paging PDSCH and includes at least one of the following:

[0128] (1) The scheduling information and the paging message of the terminal are located in the same transport block (TB) on the paging PDSCH, wherein the MAC service data unit (SDU) containing the paging message of the terminal and the MAC SDU containing the scheduling information constitute a MAC protocol data unit (PDU);

[0129] Optionally, the MAC PDU satisfies at least one of the following:

[0130] A MAC SDU containing a paging message of the terminal, located at a first specific position of the MAC PDU;

[0131] The MAC SDU containing the scheduling information is located at the second specific position of the MAC PDU.

[0132] (2) The scheduling information and the paging message of the terminal are located in different TBs on the paging PDSCH.

[0133] Optionally, the scheduling information is carried in a paging message of the terminal, and includes at least one of the following:

[0134] (a) The paging message of the terminal includes a paging record list and a first record list; the first record list includes at least one first record, and the first record includes at least one of a UE ID and corresponding scheduling information;

[0135] The first record list is, for example, an uplink grant information record list (uplinkgrant Record List), and the first record is, for example, an uplink grant information record (uplinkgrant Record), and the uplinkgrant Record includes at least one of the UE ID and the scheduling information corresponding to the UE ID.

[0136] (b) The paging message of the terminal includes a paging record list; each paging record in the paging record list includes at least one of a UE ID and corresponding scheduling information. Optionally, the paging message does not include the first record list.

[0137] The paging record (pagingRecord) includes scheduling information corresponding to the UE ID, that is, uplinkgrant information.

[0138] Optionally, the order of the paging records of different terminals in the paging record list is the same as the order of the corresponding first records in the first record list.

[0139] Optionally, when the first record does not include a UE ID, the UE ID corresponding to the scheduling information carried in the first record is a UE ID included in the paging record in the paging record list in the same order as the first record in the first record list.

[0140] Optionally, the scheduling information is carried in a specific downlink physical layer signaling or channel, and includes at least one of the following:

[0141] (1) The scheduling information is carried in a specific DCI; the specific DCI has a specific DCI format or is scrambled by a specific RNTI;

[0142] Specific DCI, such as DCI newly introduced in the protocol, is used to carry the scheduling information.

[0143] (2) The scheduling information is carried in a specific RRC message; the specific RRC message includes a first record list; the first record list includes at least one first record, and the first record includes at least one of the UE ID and the corresponding scheduling information.

[0144] For example, the protocol introduces a new RRC message: Uplinkgrant message.

[0145] FIG3 is a second flow diagram of an uplink information scheduling method provided in an embodiment of the present application. The method is applied to a network-side device. As shown in FIG3 , the method includes steps 301 and 302:

[0146] Step 301: A network-side device sends scheduling information to a terminal, where the scheduling information is used to schedule uplink information transmission when the terminal is in a non-connected state.

[0147] Step 302: The network-side device receives the uplink information from the terminal.

[0148] Optionally, the network-side device sends scheduling information to the terminal in the non-connected state, where the scheduling information is used to schedule uplink information transmission by the terminal in the non-connected state. The terminal receives the scheduling information from the network-side device; based on the scheduling information, the terminal sends the uplink information to the network-side device; and the network-side device receives the uplink information from the terminal.

[0149] In an embodiment of the present application, scheduling information is sent to a terminal in a non-connected state by a network-side device, and the uplink information transmission of the terminal in a non-connected state is scheduled. Then, the network-side device receives the uplink information from the terminal, thereby realizing the scheduling of uplink information for the terminal in the non-connected state, reducing signaling overhead, and reducing uplink information transmission delay and terminal power consumption.

[0150] Optionally, the implementation of the network-side device sending the scheduling information to the terminal in step 301 may include: the network-side device sending the scheduling information to the terminal through a target resource, wherein the target resource includes at least one of the following:

[0151] 1) Paging resources, including: paging physical downlink control channel (PDCCH) and / or paging physical downlink shared channel (PDSCH);

[0152] 2) Specific downlink physical layer signaling or channel, the specific downlink physical layer signaling or channel is determined according to the paging resource, the specific downlink physical layer signaling or channel has a first association relationship with the paging resource, or the specific downlink physical layer signaling or channel satisfies a relative position relationship with the paging resource.

[0153] Optionally, the relative position relationship is indicated by a DCI carried by a paging PDCCH.

[0154] Optionally, the disconnected state includes at least one of the following:

[0155] Radio resource connection RRC idle state;

[0156] RRC inactive state;

[0157] Standby state;

[0158] Terminal status after RRC release and before random access;

[0159] A specific terminal state before random access.

[0160] Optionally, the uplink information includes at least one of the following:

[0161] In the non-connected state, feedback information or response information to be transmitted by the terminal for downlink data transmission;

[0162] control information to be transmitted by the terminal in the non-connected state;

[0163] The terminal is in the non-connected state and has data to transmit.

[0164] Optionally, the specific downlink physical layer signaling or channel is determined by a paging resource and a first association relationship between the specific downlink physical layer signaling or channel and the paging resource;

[0165] The specific downlink physical layer signaling or channel is indicated by the network side device through paging DCI.

[0166] Optionally, the scheduling information is associated with a target identification ID of the terminal; or, the scheduling information is associated with a paging message of the terminal.

[0167] Optionally, the order of the scheduling information in the target resource is associated with the order of the target IDs of the terminals; or, the scheduling information is transmitted together with part or all of the target IDs of the terminals.

[0168] Optionally, the target ID is determined according to at least one of the following:

[0169] User equipment UE ID;

[0170] Tracking area index TA index;

[0171] Terminal priority level;

[0172] Terminal type;

[0173] Terminal capability level.

[0174] Optionally, the scheduling information has a second association relationship with the paging message of the terminal, and the second association relationship includes at least one of the following:

[0175] The order of the scheduling information in the target resource is associated with the order of the paging messages of the terminal in the corresponding paging PDSCH;

[0176] The scheduling information is transmitted together with the paging message of the terminal;

[0177] The scheduling information and the paging message of the terminal are located on different PDSCHs, and the PDSCH corresponding to the scheduling information and the PDSCH corresponding to the paging message of the terminal share the same portion of the scheduling information.

[0178] Optionally, the scheduling information satisfies at least one of the following:

[0179] The scheduling information is carried in the paging DCI or the paging PDCCH;

[0180] The scheduling information is carried in the paging PDSCH;

[0181] Part of the scheduling information is carried in the paging PDSCH, and the rest of the scheduling information is carried in the paging DCI or the paging PDCCH;

[0182] The scheduling information is carried in a paging message of the terminal;

[0183] The scheduling information is carried in a specific downlink physical layer signaling or channel.

[0184] Optionally, the scheduling information is carried in the paging DCI and includes at least one of the following:

[0185] Reusing or multiplexing at least one bit in the paging DCI to carry the scheduling information;

[0186] Use a paging DCI scrambled by a specific radio network temporary identifier RNTI to carry the scheduling information;

[0187] The scheduling information is carried in the short message field in the paging DCI;

[0188] The scheduling information is carried in the paging DCI and includes at least bits of the short message domain.

[0189] Optionally, the scheduling information is carried in the paging PDSCH and includes at least one of the following:

[0190] The scheduling information and the paging message of the terminal are located in the same transport block TB on the paging PDSCH, wherein the MAC service data unit SDU containing the paging message of the terminal and the MAC SDU containing the scheduling information constitute a MAC protocol data unit PDU;

[0191] The scheduling information and the paging message of the terminal are located in different TBs on the paging PDSCH.

[0192] Optionally, the scheduling information is carried in a paging message of the terminal, and includes at least one of the following:

[0193] The paging message of the terminal includes a paging record list and a first record list; the first record list includes at least one first record, and the first record includes at least one of a UE ID and corresponding scheduling information;

[0194] The paging message of the terminal includes only a paging record list; each paging record in the paging record list includes at least one of a UE ID and corresponding scheduling information.

[0195] Optionally, the order of the paging records of different terminals in the paging record list is the same as the order of the corresponding first records in the first record list.

[0196] Optionally, when the first record does not include a UE ID, the UE ID corresponding to the scheduling information carried in the first record is a UE ID included in the paging record in the paging record list in the same order as the first record in the first record list.

[0197] Optionally, the scheduling information is carried in a specific downlink physical layer signaling or channel, and includes at least one of the following:

[0198] The scheduling information is carried in a specific DCI; the specific DCI has a specific DCI format or is scrambled by a specific RNTI;

[0199] The scheduling information is carried in a specific RRC message; the specific RRC message includes a first record list; the first record list includes at least one first record, and the first record includes at least one of a UE ID and corresponding scheduling information.

[0200] Optionally, the scheduling information includes at least one of the following:

[0201] UE ID supporting the uplink information transmission;

[0202] first indication information, used to indicate whether the terminal is allowed to perform the uplink information transmission;

[0203] The number of bits of the uplink information transmission;

[0204] an upper limit on the number of bits of the uplink information transmission;

[0205] Time domain information of transmission resources of the uplink information;

[0206] Frequency domain information of transmission resources of the uplink information;

[0207] a period of transmission resources for the uplink information;

[0208] The coding and modulation method for uplink information transmission;

[0209] A transport block size quantization coefficient for uplink information transmission;

[0210] Redundancy version number of the uplink information transmission;

[0211] duration of the uplink information transmission;

[0212] The second indication information is used to indicate the encryption algorithm for transmitting the uplink information.

[0213] FIG4 is a third flow chart of an uplink information scheduling method provided in an embodiment of the present application. The method is executed by a terminal and a network-side device in cooperation. As shown in FIG4 , the method includes steps 401 and 402:

[0214] Step 401: The network-side device sends scheduling information to the terminal, where the scheduling information is used to schedule uplink information transmission when the terminal is in a non-connected state.

[0215] Step 402: After receiving the scheduling information from the network-side device, the terminal sends the uplink information to the network-side device based on the scheduling information.

[0216] In an embodiment of the present application, scheduling information is sent to the terminal through the network side device, and the scheduling information is used to schedule the uplink information transmission of the terminal in a non-connected state; after the terminal receives the scheduling information from the network side device, the terminal sends the uplink information to the network side device based on the scheduling information, thereby realizing the scheduling of uplink information for the terminal in the non-connected state, which can reduce signaling overhead, reduce uplink information transmission delay and terminal power consumption.

[0217] The purpose of the embodiment of the present application is to enable the UE to send uplink feedback information or data information before random access in the non-connected state. To achieve the uplink information transmission in the non-connected state, it is necessary to first determine the scheduling information and scheduling resources related to the uplink information transmission.

[0218] The embodiments of the present application propose multiple scheduling methods for uplink information of a terminal in a non-connected state, which mainly include the following three aspects:

[0219] 1. Determining scheduling resources for uplink transmission;

[0220] 2. The relationship between uplink transmission scheduling information and other information;

[0221] 3. Message structure of scheduling information for uplink transmission.

[0222] The uplink information transmission described in the embodiment of the present application is the transmission of feedback / response information, and / or control information, and / or small data, and / or normal data for a terminal in a non-connected state.

[0223] The feedback / response information mainly includes response / feedback information for downlink data transmission in a non-connected state before the terminal performs random access, such as acknowledgment (ACK) or negative acknowledgment (NACK) information.

[0224] The control information / small data / normal data mainly include uplink control information or data information in a non-connected state before the terminal performs random access.

[0225] The scheduling information described in the embodiment of the present application is the resource scheduling information related to the above-mentioned uplink information transmission.

[0226] The non-connected state in the embodiment of the present application may include at least one of the following: RRC-idle state; RRC-inactive state; standby state; state after RRC release and before random access; other non-connected states before random access.

[0227] The standby state may be a terminal standby state or a terminal inactive state introduced in the sixth generation mobile communication technology (6G) or a future mobile communication system.

[0228] Here, based on the uplink information scheduling method provided in the embodiment of the present application, the above three aspects are respectively illustrated.

[0229] 1. Determination of Scheduling Resources for Uplink Transmission

[0230] Some uplink information transmission resources in the non-connected state are obtained through scheduling, and the resources for scheduling uplink information transmission may be paging PDCCH or paging PDSCH or other downlink physical layer signaling.

[0231] In some embodiments, the resource for scheduling uplink information transmission is a paging PDCCH or a paging PDSCH.

[0232] This method can avoid additional configuration of new resources specifically for scheduling uplink information transmission, although it will increase the size of the message carried by the paging PDCCH or Paging PDSCH.

[0233] As a first sub-embodiment of the above embodiment, the resource used for scheduling uplink information transmission is the paging PDCCH.

[0234] Optionally, at least part of the bits in the existing paging DCI is multiplexed / reused, such as at least part of the scheduling information for scheduling the paging PDSCH.

[0235] Optionally, a new RNTI is used to scramble the paging DCI. For example, the new RNTI may be generated based on the UE ID so that the corresponding UE can decode the DCI.

[0236] As a second sub-embodiment of the above embodiment, the resource used for scheduling uplink information transmission is the paging PDSCH.

[0237] Optionally, scheduling information for scheduling uplink information transmission is all transmitted in the paging PDSCH.

[0238] In some embodiments, at least part of the scheduling information for scheduling uplink information transmission is transmitted in the paging PDSCH, and the rest is transmitted in the paging PDCCH.

[0239] In some embodiments, the resources used for scheduling uplink information transmission are physical layer signaling or channels (such as the newly introduced DCI / PDCCH / PDSCH) specifically used for scheduling uplink information transmission resources.

[0240] For example, a DCI format specifically used for scheduling uplink information transmission or a unique RNTI corresponding to the DCI format is introduced to schedule uplink information transmission.

[0241] In some embodiments, dedicated physical layer signaling or channels for scheduling uplink information transmission may be determined by paging DCI resources.

[0242] Optionally, an association relationship between a dedicated physical layer signaling or channel and a paging DCI resource is introduced, for example, the dedicated physical layer signaling or channel is a PDCCH monitoring occasion adjacent to the paging PDCCH monitoring occasion in the same search space.

[0243] Optionally, the network configures dedicated physical layer signaling or channels relative to the paging DCI resources or paging PDSCH resources. For example, the network indicates in the paging DCI the location of the search space or PDCCH monitoring occasion where the dedicated physical layer signaling or channel is located relative to the PDCCH monitoring occasion where the paging is located.

[0244] 2. Relationship between Uplink Scheduling Information and Other Information

[0245] In some embodiments, an association relationship between scheduling information and corresponding terminal information is introduced.

[0246] Optionally, the scheduling information is associated with the target ID of the terminal.

[0247] For example, the location of the terminal's scheduling information in the corresponding channel is placed from small to large according to the terminal's target ID.

[0248] For example, assuming that the target ID of UE1 is 1, the target ID of UE2 is 3, and the target ID of UE3 is 2, the location of the scheduling information of each terminal in the corresponding channel is as follows:

[0249] Scheduling information of UE1, scheduling information of UE3, scheduling information of UE2.

[0250] Optionally, the scheduling information of each terminal is transmitted together with part or all of the target ID of the terminal.

[0251] For example, the scheduling information is placed after, before, or at a predetermined position of the target ID of the corresponding UE in the corresponding channel.

[0252] For example, assuming that the target ID of UE1 is 1, the target ID of UE2 is 3, and the target ID of UE3 is 2, the information in the corresponding channels is composed as follows:

[0253] UE1's target ID + UE1's scheduling information, UE2's target ID + UE2's scheduling information, UE3's target ID + UE3's scheduling information.

[0254] In some embodiments, an association relationship between scheduling information and corresponding terminal paging messages is introduced.

[0255] Optionally, the scheduling information order is associated with the paging message order of the terminal.

[0256] For example, the order of the scheduling information of different terminals in the corresponding signaling is consistent with the order of the paging information of different terminals in the corresponding signaling.

[0257] For another example, the order of the scheduling information of different terminals in the corresponding channel is opposite to the order of the paging information of different terminals in the corresponding channel.

[0258] Optionally, the scheduling information of each terminal is transmitted together with the paging message of the terminal.

[0259] For example, the scheduling information is placed before or after the paging message of the corresponding terminal or is regarded as a part of the paging message.

[0260] Optionally, the scheduling information of the uplink information and the paging message of the terminal are located on different PDSCHs, and the two PDSCHs share some of the same scheduling information, such as having the same frequency domain resources but a certain offset in the time domain.

[0261] In the above embodiment, the target ID is determined by one or more of the following:

[0262] UE ID;

[0263] Tracking area TA index;

[0264] Terminal priority level;

[0265] Terminal type;

[0266] Terminal capability level.

[0267] The UE ID can be part or all of the bits of one of the following: International Mobile Equipment Identity (IMEI), International Mobile Subscriber Identity (IMSI), Temporary Mobile Subscriber Identity (TMSI), S-TMSI, P-TMSI, temporary index or Radio Network Temporary Identifier (RNTI).

[0268] 3. Message Structure of Scheduling Information for Uplink Transmission

[0269] For uplink information transmission in a non-connected state, it can be transmitted through resources scheduled by specific scheduling information, and it is necessary to determine how to transmit the specific scheduling information.

[0270] In some embodiments, the type of the scheduling information of the uplink information may be one of MAC-CE, RRC, DCI, or other physical layer messages.

[0271] In some embodiments, the scheduling information of the uplink information is transmitted in a paging DCI and includes at least one of the following:

[0272] 1) Carrying by reusing existing bits in the paging DCI.

[0273] For example, the 'Reserved' field in the paging DCI is used to carry scheduling information for uplink information.

[0274] For example, the existing paging scheduling information-related fields (such as 'FDRA' and 'TDRA' fields) in the paging DCI are reused to indicate the transmission resources of the uplink information.

[0275] 2) Carried through the short message field in the paging DCI (such as the Short Messages field in 5G).

[0276] For example, different values ​​in the short message indicator field in the paging DCI (such as the Short Messages indicator field in 5G) are used to indicate whether the short message field in the paging DCI carries scheduling information for uplink information.

[0277] 3) Use the bits in the paging DCI that at least contain the short message field to carry it.

[0278] 4) Use all / part of the bits in the paging DCI to carry the information.

[0279] In some embodiments, the scheduling information of the uplink information is carried using paging PDSCH.

[0280] Optionally, the scheduling information of the uplink information and the paging message are located in the same TB. The MAC SDU containing the paging message and the MAC SDU containing the scheduling information of the uplink information constitute a MAC PDU. The MAC PDU packaging rule includes at least one of the following:

[0281] a) The MAC SDU containing the paging message is located at a specific position in the MAC PDU, such as the front, back, or a specific position.

[0282] b) The MAC SDU containing scheduling information for uplink information is located at a specific position of the MAC PDU, such as the front, back, or a specific position.

[0283] Optionally, the scheduling information and paging message of the uplink information are located in different TBs.

[0284] As a sub-embodiment of the above embodiment, the scheduling information of the uplink information may be one of MAC-CE and RRC.

[0285] In some embodiments, part of the scheduling information of the uplink information is carried in the paging PDCCH, and the other part is carried in the paging PDSCH.

[0286] In some embodiments, the scheduling information of the uplink information is carried by a newly introduced DCI. The scheduling information of the uplink information in the new DCI includes at least one of the following:

[0287] Terminal ID that can transmit uplink information;

[0288] Whether the terminal can transmit small / normal uplink data;

[0289] The number of bits transmitted in uplink information;

[0290] The upper limit of the number of bits for uplink information transmission;

[0291] Time domain information of uplink information transmission resources;

[0292] Frequency domain information of uplink information transmission resources;

[0293] The period of uplink information transmission resources;

[0294] Coding and modulation method for uplink information transmission;

[0295] Uplink information transmission block size quantization coefficient;

[0296] Redundancy version number for uplink information transmission;

[0297] Duration of uplink information transmission;

[0298] Indicates the encryption algorithm used for uplink information transmission.

[0299] In some embodiments, the scheduling information of the uplink information is an RRC message, and a new list is introduced in the paging message: the uplink grant record list (uplinkgrantRecordList), which is used to store the scheduling information of different UEs. That is, there are two lists in the paging message, one pagingRecordList and one uplinkgrantRecordList.

[0300] The uplinkgrantRecordList includes at least one uplinkgrantRecord; the uplinkgrant Record includes at least one item of the UE ID and the scheduling information corresponding to the UE ID.

[0301] Here, the following example illustrates the existence of scheduling information:

[0302] Example 1:

[0303] The uplinkgrant Record includes at least one of a UE ID and an uplinkgrant; wherein the uplinkgrant includes specific scheduling information, such as TDRA and / or FDRA.

[0304] For example:

[0305] Example 2:

[0306] The uplinkgrant Record includes at least one of a UE ID and scheduling information; wherein the scheduling information includes, for example, TDRA and / or FDRA.

[0307] For example:

[0308] Optionally, the order of UEs in uplinkgrantRecordList is the same as that in pagingRecordList;

[0309] Example 1: The ue-Identity in UplinkgrantRecord is the same as the ue-Identity in PagingRecord.

[0310] Example 2: The UplinkgrantRecord does not contain / does not need to carry the UE-Identity, and by default it is the same as the UE-Identity in the PagingRecord. That is, the order of the Records of different UEs in the UplinkgrantRecordList is the same as that in the PagingRecordList. The UEID in the PagingRecord can be used to determine which UE's scheduling information the corresponding UplinkgrantRecord belongs to.

[0311] In some embodiments, the scheduling information of the uplink information is an RRC message, and optional uplinkgrant information is introduced in pagingRecord. Based on this solution, the paging message includes pagingRecordList, and scheduling information is added to each paging record in the pagingRecordList.

[0312] Here, the following example illustrates the existence of scheduling information:

[0313] Example 1:

[0314] The paging record includes at least one of a UE ID and an uplink grant; wherein the uplink grant includes specific scheduling information, such as TDRA and / or FDRA.

[0315] For example:

[0316] Example 2:

[0317] The paging record includes at least one of a UE ID and scheduling information; wherein the scheduling information includes, for example, TDRA and / or FDRA.

[0318] For example:

[0319] In some embodiments, the scheduling information of the uplink information is an RRC message, and a specific RRC message is introduced, for example, a new RRC message: Uplinkgrant message. The Uplinkgrant message includes a first record list (e.g., uplinkgrantRecordList); the first record list includes at least one first record (e.g., uplinkgrantRecord), and the first record includes a UE ID and at least one item of scheduling information corresponding to the UE ID.

[0320] Here, the following example illustrates the existence of scheduling information:

[0321] Example 1:

[0322] The uplinkgrant Record includes at least one of a UE ID and an uplinkgrant; wherein the uplinkgrant includes specific scheduling information, such as TDRA and / or FDRA.

[0323] For example:

[0324] Example 2:

[0325] The uplinkgrant Record includes at least one of a UE ID and scheduling information; wherein the scheduling information includes, for example, TDRA and / or FDRA.

[0326] For example:

[0327] The embodiments of the present application provide a variety of uplink information scheduling methods for terminals in a non-connected state, which are applicable to 5G, 6G and future evolved mobile communication systems, and implement scheduling of uplink resources in a non-connected state to allow the UE to transmit uplink feedback / response signals or UE-specific data to the NW side without entering a connected state, further reducing the data transmission delay and reducing the power consumption of the UE.

[0328] The uplink information scheduling method provided in the embodiment of the present application can be executed by an uplink information scheduling device. In the embodiment of the present application, the uplink information scheduling device provided in the embodiment of the present application is described by taking the uplink information scheduling method performed by the uplink information scheduling device as an example.

[0329] FIG5 is a schematic diagram of the structure of an uplink information scheduling device provided in an embodiment of the present application. As shown in FIG5 , the uplink information scheduling device 500 is applied to a terminal. The uplink information scheduling device 500 includes:

[0330] A first receiving module 501 is configured to receive scheduling information from a network-side device, where the scheduling information is used to schedule uplink information transmission when the terminal is in a non-connected state;

[0331] The first sending module 502 is configured to send the uplink information to the network side device based on the scheduling information.

[0332] In an embodiment of the present application, by receiving scheduling information from a network side device, the scheduling information is used to schedule the uplink information transmission of the terminal in a non-connected state; based on the scheduling information, the uplink information is sent to the network side device, thereby realizing the scheduling of uplink information for the terminal in the non-connected state, which can reduce signaling overhead, reduce uplink information transmission delay and terminal power consumption.

[0333] Optionally, the first receiving module 501 is specifically configured to receive the scheduling information from the network-side device through a target resource, wherein the target resource includes at least one of the following:

[0334] Paging resources, the paging resources including: paging physical downlink control channel paging PDCCH and / or paging physical downlink shared channel PDSCH;

[0335] Specific downlink physical layer signaling or channel, the specific downlink physical layer signaling or channel is determined according to the paging resource, the specific downlink physical layer signaling or channel has a first association relationship with the paging resource, or the specific downlink physical layer signaling or channel satisfies a relative position relationship with the paging resource.

[0336] Optionally, the relative position relationship is indicated by a DCI carried by a paging PDCCH.

[0337] Optionally, the order of the scheduling information in the target resource is associated with the order of the target IDs of the terminals;

[0338] Alternatively, the scheduling information is transmitted together with part or all of the target IDs of the terminals.

[0339] Optionally, the target ID is determined according to at least one of the following:

[0340] User equipment UE ID;

[0341] Tracking area index TA index;

[0342] Terminal priority level;

[0343] Terminal type;

[0344] Terminal capability level.

[0345] Optionally, the scheduling information has a second association relationship with the paging message of the terminal, and the second association relationship includes at least one of the following:

[0346] The order of the scheduling information in the target resource is associated with the order of the paging messages of the terminal in the corresponding paging PDSCH;

[0347] The scheduling information is transmitted together with the paging message of the terminal;

[0348] The scheduling information and the paging message of the terminal are located on different PDSCHs, and the PDSCH corresponding to the scheduling information and the PDSCH corresponding to the paging message of the terminal share the same portion of the scheduling information.

[0349] Optionally, the scheduling information satisfies at least one of the following:

[0350] The scheduling information is carried in the paging DCI or the paging PDCCH;

[0351] The scheduling information is carried in the paging PDSCH;

[0352] Part of the scheduling information is carried in the paging PDSCH, and the rest of the scheduling information is carried in the paging DCI or the paging PDCCH;

[0353] The scheduling information is carried in a paging message of the terminal;

[0354] The scheduling information is carried in a specific downlink physical layer signaling or channel.

[0355] Optionally, the scheduling information is carried in the paging DCI and includes at least one of the following:

[0356] Reusing or multiplexing at least one bit in the paging DCI to carry the scheduling information;

[0357] Use a paging DCI scrambled by a specific radio network temporary identifier RNTI to carry the scheduling information;

[0358] The scheduling information is carried in the short message field in the paging DCI;

[0359] The scheduling information is carried in the paging DCI and includes at least bits of the short message domain.

[0360] Optionally, the scheduling information is carried in the paging PDSCH and includes at least one of the following:

[0361] The scheduling information and the paging message of the terminal are located in the same transport block TB on the paging PDSCH, wherein the MAC service data unit SDU containing the paging message of the terminal and the MAC SDU containing the scheduling information constitute a MAC protocol data unit PDU;

[0362] The scheduling information and the paging message of the terminal are located in different TBs on the paging PDSCH.

[0363] Optionally, the scheduling information is carried in a paging message of the terminal, and includes at least one of the following:

[0364] The paging message of the terminal includes a paging record list and a first record list; the first record list includes at least one first record, and the first record includes at least one of a UE ID and corresponding scheduling information;

[0365] The paging message of the terminal includes only a paging record list; each paging record in the paging record list includes at least one of a UE ID and corresponding scheduling information.

[0366] Optionally, the order of the paging records of different terminals in the paging record list is the same as the order of the corresponding first records in the first record list.

[0367] Optionally, when the first record does not include a UE ID, the UE ID corresponding to the scheduling information carried in the first record is a UE ID included in the paging record in the paging record list in the same order as the first record in the first record list.

[0368] Optionally, the scheduling information is carried in a specific downlink physical layer signaling or channel, and includes at least one of the following:

[0369] The scheduling information is carried in a specific DCI; the specific DCI has a specific DCI format or is scrambled by a specific RNTI;

[0370] The scheduling information is carried in a specific RRC message; the specific RRC message includes a first record list; the first record list includes at least one first record, and the first record includes at least one of a UE ID and corresponding scheduling information.

[0371] Optionally, the scheduling information includes at least one of the following:

[0372] UE ID supporting the uplink information transmission;

[0373] first indication information, used to indicate whether the terminal is allowed to perform the uplink information transmission;

[0374] The number of bits of the uplink information transmission;

[0375] an upper limit on the number of bits of the uplink information transmission;

[0376] Time domain information of transmission resources of the uplink information;

[0377] Frequency domain information of transmission resources of the uplink information;

[0378] a period of transmission resources for the uplink information;

[0379] The coding and modulation method for uplink information transmission;

[0380] A transport block size quantization coefficient for uplink information transmission;

[0381] Redundancy version number of the uplink information transmission;

[0382] duration of the uplink information transmission;

[0383] The second indication information is used to indicate the encryption algorithm for transmitting the uplink information.

[0384] The uplink information scheduling device 500 in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or chip. The electronic device can be a terminal or other device other than a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and the other device can be a server, a network attached storage (NAS), etc., which is not specifically limited in the embodiment of the present application.

[0385] The uplink information scheduling device 500 provided in the embodiment of the present application can implement each process implemented in the method embodiment of Figure 2 and achieve the same technical effect. To avoid repetition, it will not be described here.

[0386] FIG6 is a second structural diagram of an uplink information scheduling device provided in an embodiment of the present application. As shown in FIG6 , the uplink information scheduling device 600 is applied to a network-side device. The uplink information scheduling device 600 includes:

[0387] The second sending module 601 is used to send scheduling information to the terminal, where the scheduling information is used to schedule uplink information transmission when the terminal is in a non-connected state;

[0388] The second receiving module 602 is configured to receive the uplink information from the terminal.

[0389] In an embodiment of the present application, by sending scheduling information to the terminal, scheduling the uplink information transmission of the terminal in a non-connected state, and then receiving the uplink information from the terminal, scheduling of uplink information for the terminal in the non-connected state is achieved, which can reduce signaling overhead, reduce uplink information transmission delay and terminal power consumption.

[0390] Optionally, the second sending module 601 is specifically configured to send the scheduling information to the terminal through a target resource, where the target resource includes at least one of the following:

[0391] Paging resources, the paging resources including: paging physical downlink control channel paging PDCCH and / or paging physical downlink shared channel PDSCH;

[0392] Specific downlink physical layer signaling or channel, the specific downlink physical layer signaling or channel is determined according to the paging resource, the specific downlink physical layer signaling or channel has a first association relationship with the paging resource, or the specific downlink physical layer signaling or channel satisfies a relative position relationship with the paging resource.

[0393] Optionally, the relative position relationship is indicated by a DCI carried by a paging PDCCH.

[0394] Optionally, the order of the scheduling information in the target resource is associated with the order of the target IDs of the terminals;

[0395] Alternatively, the scheduling information is transmitted together with part or all of the target IDs of the terminals.

[0396] Optionally, the target ID is determined according to at least one of the following:

[0397] User equipment UE ID;

[0398] Tracking area index TA index;

[0399] Terminal priority level;

[0400] Terminal type;

[0401] Terminal capability level.

[0402] Optionally, the scheduling information has a second association relationship with the paging message of the terminal, and the second association relationship includes at least one of the following:

[0403] The order of the scheduling information in the target resource is associated with the order of the paging messages of the terminal in the corresponding paging PDSCH;

[0404] The scheduling information is transmitted together with the paging message of the terminal;

[0405] The scheduling information and the paging message of the terminal are located on different PDSCHs, and the PDSCH corresponding to the scheduling information and the PDSCH corresponding to the paging message of the terminal share the same portion of the scheduling information.

[0406] Optionally, the scheduling information satisfies at least one of the following:

[0407] The scheduling information is carried in the paging DCI or the paging PDCCH;

[0408] The scheduling information is carried in the paging PDSCH;

[0409] Part of the scheduling information is carried in the paging PDSCH, and the rest of the scheduling information is carried in the paging DCI or the paging PDCCH;

[0410] The scheduling information is carried in a paging message of the terminal;

[0411] The scheduling information is carried in a specific downlink physical layer signaling or channel.

[0412] Optionally, the scheduling information is carried in the paging DCI and includes at least one of the following:

[0413] Reusing or multiplexing at least one bit in the paging DCI to carry the scheduling information;

[0414] Use a paging DCI scrambled by a specific radio network temporary identifier RNTI to carry the scheduling information;

[0415] The scheduling information is carried in the short message field in the paging DCI;

[0416] The scheduling information is carried in the paging DCI and includes at least bits of the short message domain.

[0417] Optionally, the scheduling information is carried in the paging PDSCH and includes at least one of the following:

[0418] The scheduling information and the paging message of the terminal are located in the same transport block TB on the paging PDSCH, wherein the MAC service data unit SDU containing the paging message of the terminal and the MAC SDU containing the scheduling information constitute a MAC protocol data unit PDU;

[0419] The scheduling information and the paging message of the terminal are located in different TBs on the paging PDSCH.

[0420] Optionally, the scheduling information is carried in a paging message of the terminal, and includes at least one of the following:

[0421] The paging message of the terminal includes a paging record list and a first record list; the first record list includes at least one first record, and the first record includes at least one of a UE ID and corresponding scheduling information;

[0422] The paging message of the terminal includes only a paging record list; each paging record in the paging record list includes at least one of a UE ID and corresponding scheduling information.

[0423] Optionally, the order of the paging records of different terminals in the paging record list is the same as the order of the corresponding first records in the first record list.

[0424] Optionally, when the first record does not include a UE ID, the UE ID corresponding to the scheduling information carried in the first record is a UE ID included in the paging record in the paging record list in the same order as the first record in the first record list.

[0425] Optionally, the scheduling information is carried in a specific downlink physical layer signaling or channel, and includes at least one of the following:

[0426] The scheduling information is carried in a specific DCI; the specific DCI has a specific DCI format or is scrambled by a specific RNTI;

[0427] The scheduling information is carried in a specific RRC message; the specific RRC message includes a first record list; the first record list includes at least one first record, and the first record includes at least one of a UE ID and corresponding scheduling information.

[0428] Optionally, the scheduling information includes at least one of the following:

[0429] UE ID supporting the uplink information transmission;

[0430] first indication information, used to indicate whether the terminal is allowed to perform the uplink information transmission;

[0431] The number of bits of the uplink information transmission;

[0432] an upper limit on the number of bits of the uplink information transmission;

[0433] Time domain information of transmission resources of the uplink information;

[0434] Frequency domain information of transmission resources of the uplink information;

[0435] a period of transmission resources for the uplink information;

[0436] The coding and modulation method for uplink information transmission;

[0437] A transport block size quantization coefficient for uplink information transmission;

[0438] Redundancy version number of the uplink information transmission;

[0439] duration of the uplink information transmission;

[0440] The second indication information is used to indicate the encryption algorithm for transmitting the uplink information.

[0441] The uplink information scheduling device 600 in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component of an electronic device, such as an integrated circuit or chip. The electronic device can be a network-side device or other device other than a network-side device. For example, the network-side device can include, but is not limited to, the types of network-side devices 12 listed above, and is not specifically limited in the embodiment of the present application.

[0442] The uplink information scheduling device 600 provided in the embodiment of the present application can implement each process implemented in the method embodiment of Figure 3 and achieve the same technical effect. To avoid repetition, it will not be described here.

[0443] FIG7 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. As shown in FIG7 , an embodiment of the present application further provides a communication device 700, including a processor 701 and a memory 702. The memory 702 stores a program or instruction that can be run on the processor 701. For example, when the communication device 700 is a terminal, the program or instruction, when executed by the processor 701, implements the various steps of the embodiment of the uplink information scheduling method shown in FIG2 above, and can achieve the same technical effect. When the communication device 700 is a network-side device, the program or instruction, when executed by the processor 701, implements the various steps of the embodiment of the uplink information scheduling method shown in FIG3 above, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0444] The present application also provides a terminal including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps in the method embodiment shown in FIG2 . This terminal embodiment corresponds to the above-mentioned terminal-side method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment are applicable to this terminal embodiment and can achieve the same technical effects.

[0445] The present application also provides a terminal. FIG8 is a schematic diagram of the hardware structure of the terminal provided in the present application. The terminal 800 includes, but is not limited to, at least some of the components including a radio frequency unit 801, a network module 802, an audio output unit 803, an input unit 804, a sensor 805, a display unit 806, a user input unit 807, an interface unit 808, a memory 809, and a processor 810.

[0446] Those skilled in the art will appreciate that the terminal 800 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to the processor 810 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The terminal structure shown in FIG8 does not limit the terminal. The terminal may include more or fewer components than shown, or may combine certain components, or have different component arrangements, which will not be described in detail here.

[0447] It should be understood that in an embodiment of the present application, the input unit 804 may include a graphics processing unit (GPU) 8041 and a microphone 8042, and the graphics processing unit 8041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 806 may include a display panel 8061, and the display panel 8061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 807 includes a touch panel 8071 and at least one of other input devices 8072. The touch panel 8071 is also called a touch screen. The touch panel 8071 may include two parts: a touch detection device and a touch controller. Other input devices 8072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0448] In the embodiment of the present application, after receiving downlink data from a network-side device, the radio frequency unit 801 may transmit the data to the processor 810 for processing. Furthermore, the radio frequency unit 801 may send uplink data to the network-side device. Typically, the radio frequency unit 801 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.

[0449] The memory 809 can be used to store software programs or instructions and various data. The memory 809 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 809 may include a volatile memory or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DRRAM). The memory 809 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0450] Processor 810 may include one or more processing units. Optionally, processor 810 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 810.

[0451] The radio frequency unit 801 is configured to: receive scheduling information from a network side device, where the scheduling information is used to schedule uplink information transmission when the terminal is in a non-connected state; and send the uplink information to the network side device based on the scheduling information.

[0452] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiment shown in Figure 2, and achieve the same or corresponding technical effects. To avoid repetition, it will not be repeated here.

[0453] The present application also provides a network-side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiment shown in FIG3 . This network-side device embodiment corresponds to the aforementioned network-side device method embodiment, and each implementation process and implementation method of the aforementioned method embodiment are applicable to this network-side device embodiment and can achieve the same technical effects.

[0454] The embodiment of the present application also provides a network-side device. FIG9 is a schematic diagram of the hardware structure of the network-side device provided in the embodiment of the present application. As shown in FIG9 , the network-side device 900 includes: an antenna 91, a radio frequency device 92, a baseband device 93, a processor 94, and a memory 95. The antenna 91 is connected to the radio frequency device 92. In the uplink direction, the radio frequency device 92 receives information through the antenna 91 and sends the received information to the baseband device 93 for processing. In the downlink direction, the baseband device 93 processes the information to be sent and sends it to the radio frequency device 92. The radio frequency device 92 processes the received information and sends it through the antenna 91.

[0455] The method executed by the network-side device in the above embodiment may be implemented in the baseband device 93 , which includes a baseband processor.

[0456] The baseband device 93 may include, for example, at least one baseband board, on which multiple chips are arranged, as shown in Figure 9, one of the chips is, for example, a baseband processor, which is connected to the memory 95 through a bus interface to call the program in the memory 95 and execute the network device operations shown in the above method embodiment.

[0457] The network side device may further include a network interface 96, which is, for example, a Common Public Radio Interface (CPRI).

[0458] Specifically, the network side device 900 of the embodiment of the present application also includes: instructions or programs stored in the memory 95 and can be run on the processor 94. The processor 94 calls the instructions or programs in the memory 95 to execute the steps of the method embodiment shown in Figure 3 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0459] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned uplink information scheduling method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0460] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0461] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned uplink information scheduling method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0462] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0463] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the above-mentioned uplink information scheduling method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0464] An embodiment of the present application further provides an uplink information scheduling system, including: a terminal and a network-side device, wherein the terminal can be used to execute the steps of the method embodiment shown in FIG2 , and the network-side device can be used to execute the steps of the method embodiment shown in FIG3 .

[0465] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0466] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general-purpose hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for enabling a terminal or network-side device to execute the methods described in each embodiment of the present application.

[0467] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. A method for scheduling uplink information, comprising: The terminal receives scheduling information from a network side device, where the scheduling information is used to schedule uplink information transmission when the terminal is in a non-connected state; The terminal sends the uplink information to the network side device based on the scheduling information.

2. The uplink information scheduling method according to claim 1, wherein: The terminal receiving scheduling information from the network side device includes: The terminal receives the scheduling information from the network side device through a target resource, wherein the target resource includes at least one of the following: Paging resources, the paging resources include: paging physical downlink control channel paging PDCCH and / or paging physical downlink shared channel PDSCH; A specific downlink physical layer signaling or channel, wherein the specific downlink physical layer signaling or channel is determined according to the paging resource, the specific downlink physical layer signaling or channel has a first association relationship with the paging resource, or the specific downlink physical layer signaling or channel satisfies a relative position relationship with the paging resource.

3. The uplink information scheduling method according to claim 2, wherein: The relative position relationship is indicated by the DCI carried by the paging PDCCH.

4. The uplink information scheduling method according to claim 2, wherein: The order of the scheduling information in the target resource is associated with the order of the target IDs of the terminals; Alternatively, the scheduling information is transmitted together with a part or all of the target ID of the terminal.

5. The uplink information scheduling method according to claim 4, wherein: The target ID is determined according to at least one of the following: User equipment UE ID; Tracking area index TA index; Terminal priority level; Terminal type; Terminal capability level.

6. The uplink information scheduling method according to claim 2, wherein: The scheduling information has a second association relationship with the paging message of the terminal, and the second association relationship includes at least one of the following: The order of the scheduling information in the target resource is associated with the order of the paging message of the terminal in the corresponding paging PDSCH; The scheduling information is transmitted together with a paging message of the terminal; The scheduling information and the paging message of the terminal are located on different PDSCHs, and the PDSCH corresponding to the scheduling information and the PDSCH corresponding to the paging message of the terminal share part of the same scheduling information.

7. The uplink information scheduling method according to any one of claims 1 to 6, wherein: The scheduling information satisfies at least one of the following: The scheduling information is carried in the paging DCI or the paging PDCCH; The scheduling information is carried in the paging PDSCH; A part of the scheduling information is carried in a paging PDSCH, and the rest of the scheduling information is carried in a paging DCI or a paging PDCCH; The scheduling information is carried in a paging message of the terminal; The scheduling information is carried in a specific downlink physical layer signaling or channel.

8. The uplink information scheduling method according to claim 7, wherein: The scheduling information is carried in the paging DCI, including at least one of the following: Reusing or multiplexing at least one bit in the paging DCI to carry the scheduling information; Use a paging DCI scrambled by a specific radio network temporary identifier RNTI to carry the scheduling information; The scheduling information is carried in the short message field in the paging DCI; The scheduling information is carried in the paging DCI and includes at least bits of the short message domain.

9. The uplink information scheduling method according to claim 7, wherein: The scheduling information is carried in the paging PDSCH and includes at least one of the following: The scheduling information and the paging message of the terminal are located in the same transmission block TB on the paging PDSCH, wherein the MAC service data unit SDU containing the paging message of the terminal and the MAC SDU containing the scheduling information constitute a MAC protocol data unit PDU; The scheduling information and the paging message of the terminal are located in different TBs on the paging PDSCH.

10. The uplink information scheduling method according to claim 7, wherein: The scheduling information is carried in the paging message of the terminal, including at least one of the following: The paging message of the terminal includes a paging record list and a first record list; the first record list includes at least one first record, and the first record includes at least one of a UE ID and corresponding scheduling information; The paging message of the terminal includes a paging record list; each paging record in the paging record list includes at least one of a UE ID and corresponding scheduling information.

11. The uplink information scheduling method according to claim 10, wherein: The order of the paging records of different terminals in the paging record list is the same as the order of the corresponding first records in the first record list.

12. The uplink information scheduling method according to claim 10 or 11, wherein: In the case that the first record does not include a UE ID, the UE ID corresponding to the scheduling information carried in the first record is a UE ID included in a paging record in the paging record list that has the same order as the first record in the first record list.

13. The uplink information scheduling method according to claim 7, wherein: The scheduling information is carried in a specific downlink physical layer signaling or channel, including at least one of the following: The scheduling information is carried in a specific DCI; the specific DCI has a specific DCI format or is scrambled by a specific RNTI; The scheduling information is carried in a specific RRC message; the specific RRC message includes a first record list; the first record list includes at least one first record, and the first record includes at least one of a UE ID and corresponding scheduling information.

14. The uplink information scheduling method according to any one of claims 1 to 13, wherein: The scheduling information includes at least one of the following: UE ID supporting the uplink information transmission; first indication information, used to indicate whether the terminal is allowed to perform the uplink information transmission; The number of bits of the uplink information transmission; An upper limit on the number of bits of the uplink information transmission; Time domain information of transmission resources of the uplink information; Frequency domain information of transmission resources of the uplink information; A period of transmission resources of the uplink information; The coding and modulation method for uplink information transmission; A transmission block size quantization coefficient for uplink information transmission; The redundant version number of the uplink information transmission; Duration of the uplink information transmission; The second indication information is used to indicate the encryption algorithm for transmitting the uplink information.

15. A method for scheduling uplink information, comprising: The network side device sends scheduling information to the terminal, where the scheduling information is used to schedule uplink information transmission when the terminal is in a non-connected state; The network side device receives the uplink information from the terminal.

16. The uplink information scheduling method according to claim 15, wherein: The network side device sending scheduling information to the terminal includes: The network side device sends the scheduling information to the terminal through a target resource, wherein the target resource includes at least one of the following: Paging resources, the paging resources include: paging physical downlink control channel paging PDCCH and / or paging physical downlink shared channel PDSCH; A specific downlink physical layer signaling or channel, wherein the specific downlink physical layer signaling or channel is determined according to the paging resource, the specific downlink physical layer signaling or channel has a first association relationship with the paging resource, or the specific downlink physical layer signaling or channel satisfies a relative position relationship with the paging resource.

17. The uplink information scheduling method according to claim 16, wherein: The relative position relationship is indicated by the DCI carried by the paging PDCCH.

18. The uplink information scheduling method according to claim 16, wherein: The order of the scheduling information in the target resource is associated with the order of the target IDs of the terminals; Alternatively, the scheduling information is transmitted together with a part or all of the target ID of the terminal.

19. The uplink information scheduling method according to claim 18, wherein: The target ID is determined according to at least one of the following: User equipment UE ID; Tracking area index TA index; Terminal priority level; Terminal type; Terminal capability level.

20. The uplink information scheduling method according to claim 16, wherein: The scheduling information has a second association relationship with the paging message of the terminal, and the second association relationship includes at least one of the following: The order of the scheduling information in the target resource is associated with the order of the paging message of the terminal in the corresponding paging PDSCH; The scheduling information is transmitted together with a paging message of the terminal; The scheduling information and the paging message of the terminal are located on different PDSCHs, and the PDSCH corresponding to the scheduling information and the PDSCH corresponding to the paging message of the terminal share part of the same scheduling information.

21. The uplink information scheduling method according to any one of claims 15 to 20, wherein: The scheduling information satisfies at least one of the following: The scheduling information is carried in the paging DCI or the paging PDCCH; The scheduling information is carried in the paging PDSCH; A part of the scheduling information is carried in a paging PDSCH, and the rest of the scheduling information is carried in a paging DCI or a paging PDCCH; The scheduling information is carried in a paging message of the terminal; The scheduling information is carried in a specific downlink physical layer signaling or channel.

22. The uplink information scheduling method according to claim 21, wherein: The scheduling information is carried in the paging DCI, including at least one of the following: Reusing or multiplexing at least one bit in the paging DCI to carry the scheduling information; Use a paging DCI scrambled by a specific radio network temporary identifier RNTI to carry the scheduling information; The scheduling information is carried in the short message field in the paging DCI; The scheduling information is carried in the paging DCI and includes at least bits of the short message domain.

23. The uplink information scheduling method according to claim 21, wherein: The scheduling information is carried in the paging PDSCH and includes at least one of the following: The scheduling information and the paging message of the terminal are located in the same transmission block TB on the paging PDSCH, wherein the MAC service data unit SDU containing the paging message of the terminal and the MAC SDU containing the scheduling information constitute a MAC protocol data unit PDU; The scheduling information and the paging message of the terminal are located in different TBs on the paging PDSCH.

24. The uplink information scheduling method according to claim 21, wherein: The scheduling information is carried in the paging message of the terminal, including at least one of the following: The paging message of the terminal includes a paging record list and a first record list; the first record list includes at least one first record, and the first record includes at least one of a UE ID and corresponding scheduling information; The paging message of the terminal includes only a paging record list; each paging record in the paging record list includes at least one of a UE ID and corresponding scheduling information.

25. The uplink information scheduling method according to claim 24, wherein: The order of the paging records of different terminals in the paging record list is the same as the order of the corresponding first records in the first record list.

26. The uplink information scheduling method according to claim 24 or 25, wherein: In the case that the first record does not include a UE ID, the UE ID corresponding to the scheduling information carried in the first record is a UE ID included in a paging record in the paging record list that has the same order as the first record in the first record list.

27. The uplink information scheduling method according to claim 21, wherein: The scheduling information is carried in a specific downlink physical layer signaling or channel, including at least one of the following: The scheduling information is carried in a specific DCI; the specific DCI has a specific DCI format or is scrambled by a specific RNTI; The scheduling information is carried in a specific RRC message; the specific RRC message includes a first record list; the first record list includes at least one first record, and the first record includes at least one of a UE ID and corresponding scheduling information.

28. An uplink information scheduling device, comprising: A first receiving module, used to receive scheduling information from a network side device, where the scheduling information is used to schedule uplink information transmission of a terminal in a non-connected state; The first sending module is used to send the uplink information to the network side device based on the scheduling information.

29. The uplink information scheduling device according to claim 28, wherein: The first receiving module is specifically configured to receive the scheduling information from the network side device through a target resource, wherein the target resource includes at least one of the following: Paging resources, the paging resources include: paging physical downlink control channel paging PDCCH and / or paging physical downlink shared channel PDSCH; A specific downlink physical layer signaling or channel, wherein the specific downlink physical layer signaling or channel is determined according to the paging resource, the specific downlink physical layer signaling or channel has a first association relationship with the paging resource, or the specific downlink physical layer signaling or channel satisfies a relative position relationship with the paging resource.

30. The uplink information scheduling device according to claim 29, wherein: The order of the scheduling information in the target resource is associated with the order of the target IDs of the terminals; Alternatively, the scheduling information is transmitted together with a part or all of the target ID of the terminal.

31. The uplink information scheduling device according to claim 29, wherein: The scheduling information has a second association relationship with the paging message of the terminal, and the second association relationship includes at least one of the following: The order of the scheduling information in the target resource is associated with the order of the paging message of the terminal in the corresponding paging PDSCH; The scheduling information is transmitted together with a paging message of the terminal; The scheduling information and the paging message of the terminal are located on different PDSCHs, and the PDSCH corresponding to the scheduling information and the PDSCH corresponding to the paging message of the terminal share part of the same scheduling information.

32. An uplink information scheduling device, comprising: A second sending module, used to send scheduling information to the terminal, where the scheduling information is used to schedule uplink information transmission of the terminal in a non-connected state; The second receiving module is used to receive the uplink information from the terminal.

33. A terminal comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the uplink information scheduling method as described in any one of claims 1 to 14 are implemented.

34. A network side device, comprising a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the programs or instructions are executed by the processor, the steps of the uplink information scheduling method as described in any one of claims 15 to 27 are implemented.

35. A readable storage medium storing a program or instruction, wherein the program or instruction, when executed by a processor, implements the uplink information scheduling method as described in any one of claims 1 to 14, or implements the steps of the uplink information scheduling method as described in any one of claims 15 to 27.

Images