EP3675573B1

EP3675573B1 - Signal transmission method, related device and system

Info

Publication number: EP3675573B1
Application number: EP17924437.1A
Authority: EP
Inventors: Jiafeng SHAO; Sha Ma
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2017-09-08
Filing date: 2017-09-08
Publication date: 2022-03-30
Anticipated expiration: 2037-09-08
Also published as: ES2914273T3; RU2744508C1; AU2017430542A1; US11006438B2; KR20200044959A; WO2019047193A1; AU2017430542B2; BR112020004360A2; JP7189207B2; EP3675573A1; CN109757131A; US20200137781A1; CN110868277A; CN110868277B; CN109757131B; EP3675573A4; JP2020533863A; KR102304385B1

Description

TECHNICAL FIELD

This application relates to the field of wireless communications technologies, and in particular, to a signal transmission method, a related apparatus, and a system.

BACKGROUND

In an LTE-A system, as shown in FIG. 1, a process from a time when a terminal device has no to-be-scheduled resource to a time when the terminal device sends an uplink channel may include: UE waits a time for sending a scheduling request (scheduling request, SR), and sends the SR; an eNB receives the SR and generates a scheduling grant, and sends the scheduling grant; the UE receives the scheduling grant and sends an uplink channel; and if a data volume of the UE is not completely sent, the UE further needs to wait for a next scheduling grant.
In the LTE-A system, as shown in FIG. 2, if a hybrid automatic repeat request (Hybrid Automatic Repeat reQuest, HARQ) subframe in PUCCH format 3/PUCCH format 4/PUCCH format 5 used by the terminal device and an SR subframe configured by a higher layer for the terminal are a same subframe, there is one scheduling request bit. Otherwise, if they are not a same subframe, there are zero scheduling request bit. The one scheduling request bit is added after consecutive HARQ bits. Specifically, when a bit state of the bit is 1, it indicates a positive scheduling request (positive SR), and the positive scheduling request indicates that there is currently uplink data for the terminal, or a network device currently needs to allocate a resource used for transmission to the terminal. When the bit state of the bit is 0, it indicates a negative scheduling request (negative SR), and the negative scheduling request indicates that there is currently no uplink data for the terminal, or there is currently no need to allocate a resource used for transmission to the terminal. In a fifth-generation mobile radio technology (NR) system, there are a plurality of service types, and the plurality of service types correspond to different service requirements. For example, uRLLC requires a short latency and high reliability, to be specific, successful transmission within 1 ms; eMBB requires high spectral efficiency but has no latency requirement; and mMTC requires periodic sending at low power. For different services, the terminal device needs to request for resources of different attributes (Numerology/TTI), to satisfy service requirements of the different services.
However, the one scheduling request bit in LTE-A does not support a multi-service scenario in future 5G, and this problem needs to be urgently resolved currently.
3GPP document R1-1714072 discloses a method for how to convey scheduling request when SR occurs in the same symbol/slot with other UCI. The UE can be configured in NR with multiple SR configurations/processes associated with different logical channels or services such as eMBB and URLLC. Sequence selection is used to indicate SR+HARQ-ACK.

SUMMARY

The present invention is defined by the methods of independent claims 1 or 2, by the apparatus of independent claims 7 or 8, by the computer readable storage medium of independent claim 9, and by the communication system of independent claim 10. Additional features of the invention are presented in the dependent claims. In the following, parts of the description and drawings referring to embodiments, which are not covered by the claims are not presented as embodiments of the invention, but as examples useful for understanding the invention.

BRIEF DESCRIPTION OF DRAWINGS

To describe the technical solutions in the embodiments of this application or in the background more clearly, the following describes the accompanying drawings required for describing the embodiments of this application or the background.

FIG. 1 is a schematic flowchart of an uplink scheduling process in LTE;
FIG. 2 is a schematic diagram of a HARQ bit(s) and an SR bit(s) transmitted together in different PUCCH formats in LTE;
FIG. 3 is a schematic architectural diagram of a wireless communications system according to this application;
FIG. 4 is a schematic hardware architectural diagram of a terminal according to an embodiment of this application;
FIG. 5 is a schematic hardware architectural diagram of a network device according to an embodiment of this application;
FIG. 6 is a schematic diagram of a plurality of SR configurations according to this application;
FIG. 7 is a schematic flowchart of a signal transmission method according to this application;
FIG. 8 is a schematic diagram of a plurality of SR configurations configured by a network device for a terminal device according to an embodiment of this application;
FIG. 9 is a schematic diagram of a plurality of SR configurations configured by a network device for a terminal device according to another embodiment of this application;
FIG. 10 is a schematic diagram of a plurality of SR configurations configured by a network device for a terminal device according to still another embodiment of this application;
FIG. 11 is a schematic diagram of a plurality of SR configurations configured by a network device for a terminal device according to yet another embodiment of this application;
FIG. 12 is a schematic diagram of a plurality of SR configurations configured by a network device for a terminal device according to still yet another embodiment of this application;
FIG. 13A to FIG. 13E are schematic diagrams of several location relationships between a HARQ bit(s) and an SR bit(s) according to this application;
FIG. 14A and FIG. 14B are schematic diagrams of two correspondences between an SR bit and an SR configuration according to this application;
FIG. 15 is a function block diagram of a wireless communications system, a terminal device, and a network device according to this application;
FIG. 16 is a schematic structural diagram of an apparatus according to this application; and
FIG. 17 is a schematic structural diagram of another apparatus according to this application.

DESCRIPTION OF EMBODIMENTS

Terms used in the embodiments of this application are only intended to explain specific embodiments of this application, but not intended to limit this application.
FIG. 3 shows a wireless communications system in this application. The wireless communications system may be a global system for mobile communications (Global System of Mobile communication, GSM) system, a code division multiple access (Code Division Multiple Access, CDMA) system, a wideband code division multiple access (Wideband Code Division Multiple Access Wireless, WCDMA) system, a general packet radio service (General Packet Radio Service, GPRS) system, a universal mobile telecommunications system (Universal Mobile Telecommunications System, UMTS), or a long term evolution (Long Term Evolution, LTE) system; or may be a fifth-generation mobile communications (the 5th Generation, 5G) system, a new radio (NR) system, a machine-to-machine (Machine to Machine, M2M) communications system, or the like. As shown in FIG. 3, the wireless communications system 100 may include: one or more network devices 101, one or more terminal devices 103, and a core network 115.
The terminal device 103 may also be referred to as user equipment (User Equipment, UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communications device, a user agent, or a user apparatus. The terminal device 103 may be a station (STATION, ST) in a wireless local area network (Wireless Local Area Network, WLAN), a cellular phone, a cordless phone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital assistant (Personal Digital Assistant, PDA) device, a handheld device or a computing device having a wireless communications function, another processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device 103 in a next-generation communications system such as a fifth-generation (fifth-generation, 5G) communications network, a terminal device 103 in a public land mobile network (Public Land Mobile Network, PLMN) network, a terminal device 103 in a new radio (New Radio, NR) communications system, or the like.
By way of example but not limitation, in this embodiment of the present invention, the terminal device 103 may be a wearable device. The wearable device may also be referred to as a wearable intelligent device. The wearable intelligent device is a collective name of wearable devices, such as glasses, gloves, watches, clothes, and shoes, obtained by performing intelligent design and development on daily wearables by using a wearable technology. The wearable device is a portable device that is directly worn on a human body or is integrated into a user's clothes or ornaments. The wearable device is not merely a hardware device, but further implements a powerful function through software support, data exchange, and cloud-based interaction. In a broad sense, the wearable intelligent device includes a device that provides a complete function, has a large size, and can implement all or some functions without relying on a smartphone, for example, a smartwatch or smart glasses; and includes a device that focuses only on a specific type of application and needs to be used in combination with another device such as a smartphone, for example, various smart bands and smart jewelry used for vital sign monitoring. In addition, the network device 101 may be a device, configured to communicate with a mobile device, in a network. The network device 101 may be an access point (Access Point, AP) in a WLAN, a base transceiver station (Base Transceiver Station, BTS) in a GSM or CDMA system, a NodeB (NodeB, NB) in a WCDMA system, an evolved NodeB (Evolutional NodeB, eNB or eNodeB) in an LTE system, a relay station or an access point, a vehicle-mounted device, a wearable device, a network device 101 in a 5G network, a network device 101 in a PLMN network, a new-generation NodeB (new generation NodeB, gNodeB) in an NR system, or the like.
In addition, in this embodiment of the present invention, the network device 101 provides a cell with a service, and the terminal device 103 communicates with the network device 101 by using a transmission resource (for example, a frequency domain resource, or referred to as a frequency spectrum resource) used by the cell. The cell may be a cell corresponding to the network device 101 (for example, a base station). The cell may belong to a macro base station, or a base station corresponding to a small cell (small cell). The small cell herein may include: a metro cell (Metro cell), a micro cell (Micro cell), a pico cell (Pico cell), a femto cell (Femto cell), or the like. These small cells feature a small coverage area and low transmitting power, and are suitable for providing a high-rate data transmission service.
Furthermore, in an LTE system or an NR system, a plurality of cells may simultaneously work at a same frequency on a carrier, and it may be considered that the concept "carrier" is equivalent to the concept "cell" in some special scenarios. For example, in a carrier aggregation (Carrier Aggregation, CA) scenario, when a secondary carrier is configured for UE, configuration information carries both a carrier index of the secondary carrier and a cell identity (Cell Identity, Cell ID) of a secondary cell working on the secondary carrier. In this case, it may be considered that the concept "carrier" is equivalent to the concept "cell". For example, UE's access to a carrier is equivalent to the UE's access to a cell.
In this embodiment of the present invention, the network device 101 (or the terminal 103) may work on a licensed frequency band or a license-free frequency band.
It should be noted that, the wireless communications system 100 shown in FIG. 3 is merely intended to describe the technical solutions in this application more clearly, but shall not be construed as any limitation on this application. A person of ordinary skill in the art may be aware that, with evolution of network architectures and emergence of new service scenarios, the technical solutions provided in this application are also applicable to similar technical problems. FIG. 4 shows a terminal device 200 according to some embodiments of this application. As shown in FIG. 4, the terminal device 200 may include: one or more terminal processors 201, a memory 202, a communications interface 203, a receiver 205, a transmitter 206, a coupler 207, an antenna 208, a user interface 209, and an input/output module (including an audio input/output module 210, a button input module 211, a display 212, and the like). These components may be connected by using a bus 204 or in another manner, and are connected, for example, by using a bus in FIG. 4.
The communications interface 203 may be used by the terminal device 200 to communicate with another communications device, for example, a network device. Specifically, the network device may be a network device 300 shown in FIG. 5. Specifically, the communications interface 203 may be a long term evolution (LTE) (4G) communications interface, or may be a 5G communications interface or a new radio communications interface. The communications interface 203 is not limited to a wireless communications interface. The terminal device 200 may be further equipped with a wired communications interface 203, for example, a local access network (Local Access Network, LAN) interface.
The transmitter 206 may be configured to perform transmitting processing, for example, signal modulation, on a signal output by the terminal processor 201. The receiver 205 may be configured to perform reception processing, for example, signal demodulation, on a mobile communications signal received by the antenna 208. In some embodiments of this application, the transmitter 206 and the receiver 205 may be considered as a wireless modem. In the terminal device 200, there may be one or more transmitters 206 and one or more receivers 205. The antenna 208 may be configured to convert electromagnetic energy in a transmission line into an electromagnetic wave in free space, or convert an electromagnetic wave in free space into electromagnetic energy in a transmission line. The coupler 207 is configured to split a mobile communications signal received by the antenna 208 into a plurality of signals, and allocate the signals to a plurality of receivers 205.
The terminal device 200 may further include other communications components, such as a GPS module, a Bluetooth (Bluetooth) module, and a wireless fidelity (Wireless Fidelity, Wi-Fi) module, in addition to the transmitter 206 and the receiver 205 shown in FIG. 4. The terminal device 200 may further support other wireless communications signals, such as a satellite signal and a short-wave signal, in addition to the foregoing described wireless communications signal. The terminal device 200 may be further equipped with a wired network interface (for example, a LAN interface) to support wired communication, in addition to wireless communication.
The input/output module may be configured to implement interaction between the terminal device 200 and a user/an external environment, and may mainly include the audio input/output module 210, the button input module 211, the display 212, and the like. Specifically, the input/output module may further include: a camera, a touchscreen, a sensor, or the like. The input/output module communicates with the terminal process 201 only by using the user interface 209.
The memory 202 is coupled to the terminal processor 201, and is configured to store various software programs and/or a plurality of sets of instructions. Specifically, the memory 202 may include a high-speed random access memory, and may also include a non- transitory memory, for example, one or more disk storage devices, a flash memory, or another non-transitory solid state storage device. The memory 202 may store an operating system (briefly referred to as a system below), for example, an embedded operating system such as Android, IoS, Windows, or Linux. The memory 202 may further store a network communications program. The network communications program may be used to communicate with one or more additional devices, one or more terminal devices, and one or more network devices. The memory 202 may further store a user interface program. The user interface program may vividly display content of an application program by using a graphical operation interface; and receive, by using input controls such as a menu, a dialog box, and a button, a control operation performed by a user on the application program.
In some embodiments of this application, the memory 202 may be configured to store a program for implementing, on the terminal device 200 side, a signal transmission method provided in one or more embodiments of this application. For implementation of the signal transmission method provided in one or more embodiments of this application, refer to a subsequent embodiment. The terminal processor 201 may be configured to read and execute a computer readable instruction. Specifically, the terminal processor 201 may be configured to invoke a program stored in the memory 202, for example, a program for implementing, on the terminal device 200 side, a signal transmission method provided in one or more embodiments of this application, and execute an instruction included in this program.
It may be understood that, the terminal device 200 may be the terminal 103 in the wireless communications system 100 shown in FIG. 3, and may be implemented as a mobile device, a mobile station (mobile station), a mobile unit (mobile unit), a radio unit, a remote unit, a user agent, a mobile client, or the like.
It should be noted that, the terminal device 200 shown in FIG. 4 is merely an implementation of an embodiment of this application. During practical application, the terminal device 200 may further include more or fewer components, and this is not limited herein.
FIG. 5 shows a network device 300 according to some embodiments of this application. As shown in FIG. 5, the network device 300 may include: one or more network device processors 301, one or more memories 302, one or more communications interfaces 303, one or more transmitters 305, one or more receivers 306, one or more couplers 307, and one or more antennas 308. These components may be connected by using a bus 304 or connected in another manner. FIG. 5 is an example by using a bus.
The communications interface 303 may be used by the network device 300 to communicate with another communications device, for example, a terminal device or another network device. Specifically, the terminal device may be the terminal device 200 shown in FIG. 4. Specifically, the communications interface 303 may be a long term evolution (LTE) (4G) communications interface, or may be a 5G communications interface or a new radio communications interface. The communications interface 303 is not limited to a wireless communications interface. The network device 300 may be further equipped with a wired communications interface 303 to support wired communication. For example, a backhaul link between one network device 300 and another network device 300 may be a wired communications connection.
The transmitter 305 may be configured to perform transmit processing, for example, signal modulation, on a signal output by the network device processor 301. The receiver 306 may be configured to perform reception processing, for example, signal demodulation, on a mobile communications signal received by the antenna 308. In some embodiments of this application, the transmitter 305 and the receiver 306 may be considered as a wireless modem. In the network device 300, there may be one or more transmitters 305 and one or more receivers 306. The antenna 308 may be configured to convert electromagnetic energy in a transmission line into an electromagnetic wave in free space, or convert an electromagnetic wave in free space into electromagnetic energy in a transmission line. The coupler 307 may be configured to split a mobile communications signal into a plurality of signals, and allocate the signals to a plurality of receivers 306.
The memory 302 is coupled to the network device processor 301, and is configured to store various software programs and/or a plurality of sets of instructions. Specifically, the memory 302 may include a high-speed random access memory, and may also include a non-transitory memory, for example, one or more disk storage devices, a flash memory, or another non- transitory solid state storage device. The memory 302 may store an operating system (briefly referred to as a system below), for example, an embedded operating system such as uCOS, VxWorks, or RTLinux. The memory 302 may further store a network communications program. The network communications program may be used to communicate with one or more additional devices, one or more terminal devices, and one or more network devices.
The network device processor 301 may be configured to perform radio channel management, implement establishment and disconnection of a call or a communication link, and provide a user in a current control area with cell handover control and the like. Specifically, the network device processor 301 may include: an administration module/communication module (Administration Module/Communication Module, AM/CM) (a center configured to perform speech channel switching and information exchange), a basic module (Basic Module, BM) (configured to implement call processing, signaling processing, radio resource management, radio link management, and a circuit maintenance function), a transcoder and submultiplexer (Transcoder and SubMultiplexer, TCSM) unit (configured to implement multiplexing, demultiplexing, and a transcoding function), and the like.
In this embodiment of this application, the network device processor 301 may be configured to read and execute a computer readable instruction. Specifically, the network device processor 301 may be configured to invoke a program stored in the memory 302, for example, a program for implementing, on the network device 300 side, a signal transmission method provided in one or more embodiments of this application, and execute an instruction included in this program.
It may be understood that, the network device 300 may be the base station 101 in the wireless communications system 100 shown in FIG. 3, and may be implemented as a base transceiver station, a wireless transceiver, a basic service set (BSS), an extended service set (ESS), a NodeB, an eNodeB, an access point or a TRP, or the like.
It should be noted that, the network device 300 shown in FIG. 5 is merely an implementation of an embodiment of this application. During practical application, the network device 300 may further include more or fewer components, and this is not limited herein.
Based on the embodiments respectively corresponding to the foregoing wireless communications system 100, terminal device 200, and network device 300, this application provides a signal transmission method, as described in detail below.
First, to help understand this application, the following describes basic concepts in this application.

(1) Scheduling request configuration (scheduling request configuration, briefly referred to as an SR configuration below)

An SR configuration may be dynamically configured by a network device for a terminal, or may be configured by a network device for a terminal by using higher layer signaling. The higher layer signaling may be signaling sent by a higher protocol layer. The higher protocol layer is at least one protocol layer in all protocol layers above a physical layer. Specifically, the higher protocol layer may be at least one of the following protocol layers: a medium access control (Medium Access Control, MAC) layer, a radio link control (Radio Link Control, RLC) layer, a packet data convergence protocol (Packet Data Convergence Protocol, PDCP) layer, a radio resource control (Radio Resource Control, RRC) layer, a non-access stratum (Non-Access Stratum, NAS) layer, and the like.

It may be understood that an SR configuration is associated with a first scheduling request(s) in at least one of the following manners:
1. The SR configuration may be used to indicate a time-domain location and/or a frequency-domain location of the first scheduling request(s). For example, the SR configuration indicates a time period in which the first scheduling request(s) can be sent, in other words, a time-domain location corresponding to the time period is a time-domain location at which the first scheduling request(s) can be sent. The SR configuration indicates a subcarrier spacing on which the first scheduling request(s) can be sent, in other words, a subcarrier size corresponding to the subcarrier spacing is a subcarrier on which the first scheduling request(s) can be sent. Table 1-1, Table 1-2, and Table 1-3 show examples of three SR configurations.

Table 1-1

SR configuration index number	Time-domain location
SR configuration #0	Once every 2 ms
SR configuration #1	Once every seven symbols
SR configuration #2	Once every slot

Table 1-2

SR configuration index number	Frequency-domain location
SR configuration #0	Physical resource block 1
SR configuration #1	Physical resource block 2
SR configuration #2	Physical resource block 1

Table 1-3

SR configuration index number	Time-domain location	Frequency-domain location
SR configuration #0	Once every 2 ms	Physical resource block 1
SR configuration #1	Once every seven symbols	Physical resource block 2
SR configuration #2	Once every symbol	Physical resource block 3

It can be learned that, a plurality of SR configurations may indicate a same time-domain location, or may indicate different time-domain locations; and a plurality of SR configurations may indicate a same frequency-domain location, or may indicate different frequency-domain locations.
2. The SR configuration may be used to indicate a length of a time unit occupied by an uplink control channel that carries the first scheduling request(s) and/or a size of a subcarrier spacing occupied by an uplink control channel that carries the first scheduling request(s). For example, the SR configuration indicates that a length of a time unit occupied by an uplink control channel that carries the first scheduling request(s) is two symbols, in other words, the first scheduling request(s) can be sent on a two-symbol uplink control channel.
Table 2-1, Table 2-2, and Table 2-3 show examples of three SR configurations.

Table 2-1

SR configuration index number	Length of a time unit occupied by an uplink control channel
SR configuration #0	1-ms subframe
SR configuration #1	7 symbols
SR configuration #2	1 slot

Table 2-2

SR configuration index number	Size of a subcarrier spacing occupied by an uplink control channel
SR configuration #0	15 kHz
SR configuration #1	60 kHz
SR configuration #2	30 kHz

Table 2-3

SR configuration index number	Length of a time unit occupied by an uplink control channel	Size of a subcarrier spacing occupied by an uplink control channel
SR configuration #0	1-ms subframe	15 kHz
SR configuration #1	7 symbols	60 kHz
SR configuration #2	1 symbol	30 kHz

It can be learned that, a plurality of SR configurations may indicate a same length of a time unit occupied by an uplink control channel, or may indicate different lengths of a time unit occupied by an uplink control channel; and a plurality of SR configurations may indicate a same size of a subcarrier spacing occupied by an uplink control channel, or may indicate different sizes of a subcarrier spacing occupied by an uplink control channel.
3. The SR configuration may be used to indicate an attribute (Numerology/TTI/logical channel) of a resource requested in the first scheduling request(s). Different SR configurations are for different services, because a requirement for an attribute of a resource varies according to different services. Specifically, an attribute of a frequency-domain resource requested in the first scheduling request(s) is a first numerology (for example, a first subcarrier spacing (subcarrier spacing, SCS)), and/or an attribute of a time-domain resource requested in the first scheduling request(s) is a first time unit, and/or a logical channel requested in the first scheduling request(s) is a first logical channel, and/or a priority of a logical channel requested in the first scheduling request(s) is a second priority.
Table 3-1, Table 3-2, Table 3-3, and Table 3-4 show examples of three SR configurations.

Table 3-1

SR configuration index number	Attribute of a requested time-domain resource (time unit)
SR configuration #0	1 ms
SR configuration #1	2 symbols
SR configuration #2	1 slot

Table 3-2

SR configuration index number	Attribute of a requested time-domain resource (time unit)	Service
SR configuration #0	1 ms	Service #	0
SR configuration #1	2 symbols	Service #	1
SR configuration #2	1 slot	Service #	2

Table 3-3

SR configuration index number	Attribute of a requested time-domain resource (time unit)	Attribute (Numerology) of a requested frequency-domain resource
SR configuration #0	1 ms	15 kHz
SR configuration #1	2 symbols	60 kHz
SR configuration #2	1 slot	30 kHz

Table 3-4

It can be learned that, a plurality of SR configurations may indicate a same attribute of a requested time-domain resource, or may indicate different attributes of a requested time-domain resource; and a plurality of SR configurations may indicate a same attribute of a requested frequency-domain resource, or may indicate different attributes of a requested frequency-domain resource.
It should be noted that the foregoing three SR configurations respectively correspond to requirements for different services. It can be learned that, if a service requires a relatively short time, an SR configuration whose requested time unit is relatively small may be configured for a terminal; or if a service requires a relatively long time, an SR configuration whose requested time unit is relatively large may be configured for a terminal.
The foregoing examples are merely used to explain the invention principles of this application, and shall not be construed as any limitation.

(2) Scheduling request bit (scheduling request bit, briefly referred to as an SR bit(s) below)

The SR bit(s) is used to indicate an SR(s) reported by a terminal device, and specifically indicate an SR(s) associated with a specific SR configuration(s) and indicate whether the reported SR(s) associated with the SR configuration(s) is a positive SR(s) or a negative SR(s).
There may be one or more SR bits. In this application, a quantity of SR bits is greater than or equal to 2. The quantity of SR bits may be related to a quantity of SR configurations.
Optionally, in this application, an SR bit(s) and a HARQ bit(s) are carried on a same uplink control channel.
Specifically, a terminal may determine a quantity of SR bits based on a quantity of SR configurations. Optionally, the quantity of SR bits may be equal to the quantity of SR configurations. According to the invention, the quantity of SR bits is equal to: ceil(log₂ (1+N_{configuration})), where N_{configuration} represents the quantity of SR configurations, and ceil represents rounding up to a next integer. For a correlation between the quantity of SR bits and the quantity of SR configurations, refer to the subsequent Embodiment 1 and Embodiment 2. Details are not described herein again.
For example, it is assumed that an SR configuration #0 and an SR configuration #1 in Table 3-4 are SR configurations in a slot #0.
When the slot #0 arrives, the terminal may indicate, by using two bits, SRs associated with the SR configurations in the slot #0 that are configured for the terminal. One bit (for example, a most significant bit) is used to indicate whether an SR associated with the SR configuration #0 is a positive SR or a negative SR. The other bit (for example, a least significant bit) is used to indicate whether an SR associated with the SR configuration #1 is a positive SR or a negative SR. In other words, the two bits are SR bits, and one bit corresponds to one SR configuration.
When the slot #0 arrives, the terminal may indicate, still by using two bits, SRs associated with the SR configurations in the slot #0 that are configured for the terminal. When the two bits are "01", it indicates that the terminal device reports, in the slot #0, only a positive SR associated with the SR configuration #1 and does not report an SR associated with the SR configuration #0; or when the two bits are "10", it indicates that the terminal device reports, in the slot #0, only a positive SR associated with the SR configuration #0 and does not report an SR associated with the SR configuration #1; or when the two bits are "00", it indicates that the terminal device reports, in the slot #0, both a negative SR associated with the SR configuration #0 and a negative SR associated with the SR configuration #1.

(3) Time unit

In this application, a length of one time unit may be set to any value, and is not limited herein.
For example, one time unit may include one or more subframes.
Alternatively, one time unit may include one or more slots.
Alternatively, one time unit may include one or more mini-slots.
Alternatively, one time unit may include one or more symbols.
Alternatively, one time unit may include one or more transmission time intervals (Transmission Time Interval, TTI).
Alternatively, one time unit may include one or more short transmission time intervals (short Transmission Time Interval, sTTI).
Alternatively, one time unit may correspond to a time mode. For example, a first time mode is a two-symbol or three-symbol transmission time interval, and a second time mode is a seven-symbol transmission time interval.
The mini-slot includes one or more symbols, and is less than or equal to a slot. Herein, the mini-slot may be a mini-slot in a system with a 60 kHz subcarrier spacing, or may be a mini-slot in a system with a 15 kHz subcarrier spacing, and this is not limited in the embodiments of the present invention.
The slot includes one or more symbols. Herein, the slot may be a slot in a system with a 60 kHz subcarrier spacing, or may be a slot in a system with a 15 kHz subcarrier spacing, and this is not limited in the embodiments of the present invention.
The TTI is a parameter commonly used in a current communications system (for example, an LTE system), and is a scheduling unit used for data transmission scheduling on a radio link. In the prior art, generally it is considered that 1 TTI = 1 ms. In other words, one TTI is one subframe (subframe), or a size of two slots (slot). The TTI is a basic unit of time managed in radio resource management (for example, scheduling).

(4) Hybrid automatic repeat request (Hybrid Automatic Repeat reQuest, HARQ) bit, briefly referred to as a HARQ bit below

A HARQ bit is used to feed back a result of decoding one or more downlink data blocks by a terminal, and may be a positive acknowledgment ACK or a negative acknowledgment ACK. The ACK indicates that the terminal has correctly performed the decoding. The NACK indicates that an error has occurred during the decoding by the terminal. Specifically, the terminal may feed back the HARQ bit to a network device, or the terminal may feed back the HARQ bit to another terminal. Further, if the terminal feeds back a negative acknowledgment, a device that receives the HARQ bit retransmits data for which an error has occurred during the decoding by the terminal, to help the terminal correctly receive downlink data.
The foregoing example is merely used to explain this application, and shall not be construed as any limitation. Correlation between a quantity of SR bits and a quantity of SR configurations configured for a terminal is described in detail in a subsequent embodiment, and details are not described herein again.
Second, main invention principles of this application may include: selecting, by a terminal device, at least one SR configuration from a plurality of SR configurations; and then sending, by the terminal, a hybrid automatic repeat request bit(s) and an SR bit(s) in one time unit, where the SR bit(s) is used to indicate each SR(s) associated with each SR configuration of the at least one SR configuration. Correspondingly, a network device may receive the HARQ bit(s) and the SR bit(s) from the terminal, and determine, based on the SR bit(s), an SR reported by the terminal. In this way, the terminal device may indicate which SR configuration reported by the terminal device is associated with a positive SR and/or which SR configuration reported by the terminal device is associated with a negative SR. In this application, a plurality of SR configurations can be supported, so as to adapt to a multi-service scenario in 5G.
In this application, the SR bit(s) may be referred to as a first bit(s), and the foregoing at least one SR configuration may be referred to as a first SR configuration(s). The foregoing at least one SR configuration may be an SR configuration(s), configured by the network device for the terminal device, in a current time unit (namely, one time unit). Herein, the current time unit may be a time unit in which the terminal device is ready to send the HARQ bit(s) and the SR bit(s). In this application, a positive SR indicates, to the terminal device, that there is currently uplink data for the terminal, or the network device currently needs to allocate a resource used for transmission to the terminal. The resource used for transmission may be scheduled by the network device or may be predefined. A negative SR indicates, to the terminal device, that there is currently no uplink data for the terminal device, or there is currently no need to allocate a resource used for transmission to the terminal. It may be understood that, if a receiving device receives only a positive SR associated with an SR configuration, the receiving device may consider that SR configurations other than this SR configuration in the at least one SR configuration are all negative SRs. The receiving device may be a network device or a terminal.
In this application, the network device may further configure a time unit in which the plurality of SR configurations are located. Herein, a time unit in which an SR configuration is located is a time unit in which the terminal device can report an SR associated with the SR configuration. In other words, if an SR configuration exists in one time unit, it indicates that the terminal device can report, in this time unit, an SR associated with this SR configuration. It may be understood that an SR configuration configured for the terminal may indicate the time unit.
FIG. 6 shows an example of a time unit in which three SR configurations (an SR configuration #0, an SR configuration #1, and an SR configuration #2) configured by the network device are located. As shown in FIG. 6, a time unit in which the SR configuration #0 is located is a symbol #0, a symbol #2, a symbol #4, and a symbol #6. This indicates that the terminal device can send, on the four symbols, an SR associated with the SR configuration #0. The example is merely used to explain the embodiments of this application, and shall not be construed as any limitation.
It may be understood that, although a time unit in which the terminal device reports an SR is configured by the network device, or configured by using higher layer signaling, or configured by the terminal device, generating an SR is behavior of the terminal device; therefore, the network device knows only that an SR associated with a specific SR configuration may exist in a specific time unit, but does not know which SR associated with SR configuration is actually reported by the terminal device in this specific time unit. To make the network device know which SR configuration actually reported by the terminal device in this specific time unit is associated with the SR, the terminal device needs to send an SR bit to the network device.
For example, in the example shown in FIG. 6, the terminal device may determine, according to an actual requirement, to report, on the symbol #0, only the SR associated with the SR configuration #0 and not to report an SR associated with the SR configuration #1. The terminal device sends two SR bits " 10" to the network device, so that the network device can know, based on the two SR bits "10", that the terminal device actually reports, on the symbol #0, only the SR associated with the SR configuration #0 and does not report the SR associated with the SR configuration #1.
For example, in the example shown in FIG. 6, the terminal device may determine, according to an actual requirement, to report, on the symbol #0, the SR associated with the SR configuration #0 and an SR associated with the SR configuration #1. A most significant bit "1" is used to indicate whether the SR associated with the SR configuration #0 is a positive SR or a negative SR, and a least significant bit "0" is used to indicate whether the SR associated with the SR configuration #1 is a positive SR or a negative SR. In this way, the network device can know, based on the two SR bits "10", that the terminal device actually reports the SR associated with the SR configuration #0 and the SR associated with the SR configuration #1 on the symbol #0. The example is merely used to explain this application, and shall not be construed as any limitation.
In this application, there may be a correlation between a quantity of SR bits and a quantity of the plurality of SR configurations configured by the network device for the terminal device. This correlation is specifically described in a subsequent embodiment, and details are not described herein again. Optionally, the quantity of the plurality of SR configurations is greater than or equal to 2. First, the following describes several manners in which the quantity of the plurality of SR configurations are defined.
(1) In manner 1, the quantity of the plurality of SR configurations is equal to a quantity of all SR configurations. In other words, the plurality of SR configurations may be all SR configurations dynamically configured by the network device for the terminal, or may be all SR configurations configured by the network device for the terminal by using higher layer signaling, or may be all SR configurations configured by another terminal device for the terminal.
For example, as shown in FIG. 8, all SR configurations configured by the network device for the terminal device are: an SR configuration #0, an SR configuration #1, and an SR configuration #2. In other words, a quantity of all the SR configurations configured by the network device for the terminal is 3. It can be learned, from FIG. 8, that some SR configurations in all the SR configurations may be separately used in each time unit (symbol). A first bit(s) is used to indicate an SR(s) associated with at least one SR configuration in all the SR configurations. For example, the SR configuration #0 and the SR configuration #1 are used on a symbol #0, and the first bit(s) is used to indicate an SR associated with the SR configuration #0 and/or the SR configuration #1 in all the SR configurations; and the SR configuration #2 is used on a symbol #1, and the first bit(s) is used to indicate an SR associated with the SR configuration #2 in all the SR configurations. The example is merely used to explain this application, and shall not be construed as any limitation.
In manner 1, efficiency in reporting, by the terminal device, SRs associated with all the SR configurations can be improved. For example, as shown in FIG. 8, even if a time unit corresponding to the SR configuration #2 is on the symbol #1 but not on the symbol #0, the terminal device can notify, on the symbol #0, the network device of the SR associated with the SR configuration #2, instead of notifying, until the symbol #1, the network device of the SR associated with the SR configuration #2, thereby improving efficiency. The example is merely used to explain this application, and shall not be construed as any limitation. (2) In manner 2, the quantity of the plurality of SR configurations is equal to a quantity of SR configurations in the time unit. To be specific, the plurality of SR configurations may be SR configurations in the time unit that are dynamically configured by the network device for the terminal, or may be SR configurations in the time unit that are configured by the network device for the terminal by using higher layer signaling, or may be SR configurations in the time unit that are configured by another terminal for the terminal.
For example, as shown in FIG. 9, SR configurations on a symbol #0 that are configured by the network device for the terminal device are: an SR configuration #0 and an SR configuration #1. In other words, a quantity of SR configurations on the symbol #0 that are configured by the network device for the terminal is 2, and a first bit(s) is used to indicate an SR(s) associated with at least one SR configuration in the SR configuration #0 and the SR configuration #1. For another example, as shown in FIG. 9, an SR configuration that is configured by the network device for the terminal device and that is on a symbol #1 is an SR configuration #2. In other words, a quantity of SR configurations on the symbol #1 that are configured by the network device for the terminal is 1, and a first bit(s) is used to indicate an SR(s) associated with an SR configuration #2. The examples are merely used to explain this application, and shall not be construed as any limitation.
In manner 2, SR configurations in one time unit that are configured for the terminal may include SR configurations associated with different uplink control channel attributes. For details about an uplink control channel attribute associated with an SR configuration, refer to description of a subsequent manner 4. Explanation is not given herein.
In manner 2, only SRs associated with SR configurations in the time unit that are actually configured for the terminal are reported, to reduce SR bit overheads. For example, as shown in FIG. 8, there is an SR configuration #0 and an SR configuration #1 on a symbol #0, and the terminal device can notify, by using only two bits, an SR associated with the SR configuration #0 and an SR associated with the SR configuration #1; and there is only an SR configuration #2 on a symbol #1, and the terminal device can notify, by using only one bit, an SR associated with the SR configuration #2. The example is merely used to explain this application, and shall not be construed as any limitation. (3) In manner 3, the quantity of the plurality of SR configurations is equal to a quantity of SR configurations in a plurality of time units. In other words, the plurality of SR configurations may be SR configurations that are dynamically configured by the network device for the terminal and that are in a plurality of time units, or may be SR configurations that are configured by the network device for the terminal by using higher layer signaling and that are in a plurality of time units, or may be SR configurations that are configured by another terminal for the terminal and that are in a plurality of time units. The plurality of time units include one time unit in which the terminal sends the hybrid automatic repeat request bit(s) and the first bit(s).
For example, as shown in FIG. 10, SR configurations on a symbol #0 that are configured by the network device for the terminal device are: an SR configuration #0 and an SR configuration #1; and an SR configuration that is configured by the network device for the terminal device and that is on a symbol #1 is an SR configuration #2. In other words, total SR configurations that are configured by the network device for the terminal and that are on the symbol #0 and a symbol #1: the SR configuration #0, the SR configuration #1, and the SR configuration #2. A quantity of SR configurations that are configured by the network device for the terminal and that are on the symbol #0 and the symbol #1 is 3, and a first bit(s) is used to indicate an SR(s) associated with at least one SR configuration in the SR configuration #0, the SR configuration #1, and the SR configuration #2. The example is merely used to explain this application, and shall not be construed as any limitation.
In the example shown in FIG. 10, the plurality of time units are consecutive. This application is not limited thereto, and the plurality of time units may alternatively be inconsecutive. For example, as shown in FIG. 11, SR configurations on a symbol #0 that are configured by the network device for the terminal device are: an SR configuration #0 and an SR configuration #1; and an SR configuration that is configured by the network device for the terminal device and that is on a symbol #2 is an SR configuration #0. In other words, total SR configurations that are configured by the network device for the terminal on the symbol #0 and the symbol #2 are: the SR configuration #0 and the SR configuration #1. A quantity of SR configurations that are configured by the network device for the terminal and that are on the symbol #0 and the symbol #2 is 2, and a first bit(s) is used to indicate an SR associated with at least one SR configuration in the SR configuration #0 and the SR configuration #1. The example is merely used to explain this application, and shall not be construed as any limitation.
In manner 3, SR configurations that are configured for the terminal and that are in a plurality of time units may include SR configurations associated with different uplink control channel attributes. For details about an uplink control channel attribute associated with an SR configuration, refer to description of a subsequent manner 4. Explanation is not given herein.
In manner 3, which is similar to manner 2, only SRs associated with SR configurations that are actually configured for the terminal and that are in a plurality of time units are reported, to reduce SR bit overheads. (4) In manner 4, the quantity of the plurality of SR configurations is equal to a quantity of SR configurations that are associated with a same uplink control channel attribute and that are in one or more time units. To be specific, the plurality of SR configurations may be SR configurations that are dynamically configured by the network device for the terminal and that are in one or more time units and associated with a same uplink control channel attribute, or may be SR configurations that are configured by the network device for the terminal by using higher layer signaling and that are in one or more time units and associated with a same uplink control channel attribute, or may be SR configurations that are configured by another terminal for the terminal and that are in one or more time units and associated with a same uplink control channel attribute.
Herein, an uplink control channel attribute associated with an SR configuration is an attribute of an uplink control channel that carries an SR. An attribute of an uplink control channel may include at least one of the following: a length of a time unit occupied by the uplink control channel, or a quantity of time units occupied by the uplink control channel, or a format of the uplink control channel, or a minimum quantity or a maximum quantity of bits carried by the uplink control channel.
First, a single time unit (for example, one time unit is one symbol) is used as an example.
For example, as shown in FIG. 12, SR configurations on a symbol #0 that are configured by the network device for the terminal device are: an SR configuration #0, an SR configuration #1, and an SR configuration #3. The SR configuration #0 and the SR configuration #1 are associated with a same uplink control channel attribute, and the same uplink control channel attribute is one symbol. In other words, a length of a time unit that carries an SR associated with the SR configuration #0 is one symbol, and a length of a time unit that carries an SR associated with the SR configuration #1 is also one symbol. An uplink control channel attribute associated with the SR configuration #3 is one mini-slot (mini-slot) (namely, four symbols). In other words, a length of a time unit that carries an SR associated with the SR configuration #3 is four symbols or one mini-slot.
In the example shown in FIG. 12, from a perspective of the one-symbol uplink control channel attribute, SR configurations on the symbol #0 that are configured by the network device for the terminal device are the SR configuration #0 and the SR configuration #1, and do not include the SR configuration #3. In other words, a quantity of SR configurations that are configured by the network device for the terminal and that are on the symbol #0 and associated with the one-symbol uplink control channel attribute is 2, and in this case, a first bit(s) is used to indicate an SR(s) associated with at least one SR configuration in the SR configuration #0 and the SR configuration #1.
In the example shown in FIG. 12, from a perspective of the one-mini-slot uplink control channel attribute, an SR configuration that is configured by the network device for the terminal device and that is on the symbol #0 is the SR configuration #3, and does not include the SR configuration #0 or the SR configuration #1. In other words, a quantity of SR configurations on the symbol #0 that are configured by the network device for the terminal and that are associated with the one-mini-slot uplink control channel attribute is 1, and in this case, a first bit(s) is used to indicate an SR(s) associated with the SR configuration #3.
The foregoing example is merely used to explain this application, and shall not be construed as any limitation.
Second, a plurality of time units (for example, one time unit is one symbol) are used as an example.
For another example, as shown in FIG. 12, SR configurations that are configured by the network device for the terminal device and that are on a symbol #0 to a symbol #3 are: an SR configuration #0, an SR configuration #1, an SR configuration #2, and an SR configuration #3. The SR configuration #0, the SR configuration #1, and the SR configuration #2 are associated with a same uplink control channel attribute, and the same uplink control channel attribute is one symbol. An uplink control channel attribute associated with the SR configuration #3 is one mini-slot (mini-slot) (namely, four symbols).
In the example shown in FIG. 12, from a perspective of the one-symbol uplink control channel attribute, SR configurations that are configured by the network device for the terminal device and that are on the symbol #0 to the symbol #3 are the SR configuration #0, the SR configuration #1, and the SR configuration #2, and do not include the SR configuration #3. In other words, a quantity of SR configurations that are configured by the network device for the terminal and that are on the symbol #0 to the symbol #3 and associated with the one-symbol uplink control channel attribute is 3, and in this case, a first bit(s) is used to indicate an SR associated with at least one SR configuration in the SR configuration #0, the SR configuration #1, and the SR configuration #2.
In the example shown in FIG. 12, from a perspective of the one-mini-slot uplink control channel attribute, an SR configuration that is configured by the network device for the terminal device and that is on the symbol #0 to the symbol #4 is the SR configuration #3, and does not include the SR configuration #0, the SR configuration #1, and the SR configuration #2. In other words, a quantity of SR configurations that are configured by the network device for the terminal and that are on the symbol #0 to the symbol #4 and associated with the one-mini-slot uplink control channel attribute is 1, and in this case, a first bit(s) is used to indicate an SR(s) associated with the SR configuration #3.
The foregoing example is merely used to explain this application, and shall not be construed as any limitation. In manner 4, the plurality of time units may be consecutive, or may be inconsecutive.
Manner 4 is described merely by using an example in which an uplink control channel attribute is a length of a time unit occupied by an uplink control channel. For another uplink control channel attribute, similar processing applies.
If a quantity of time units occupied by an uplink control channel is the same as a quantity of time units occupied by another uplink control channel, for example, both are two time units, it is considered that attributes of the uplink control channels are the same. Otherwise, the attributes are different.
If a format of an uplink control channel is the same as that of another uplink control channel, for example, both are uplink control channels in a first format, it is considered that attributes of the uplink control channels are the same. Otherwise, the attributes are different.
If a minimum quantity of bits that can be carried by an uplink control channel is the same as a minimum quantity of bits that can be carried by another uplink control channel, for example, both are two bits, it is considered that attributes of the uplink control channels are the same. Otherwise, the attributes are different.
If a maximum quantity of bits that can be carried by an uplink control channel is the same as a maximum quantity of bits that can be carried by another uplink control channel, for example, both are two bits, it is considered that attributes of the uplink control channels are the same. Otherwise, the attributes are different.
An operation manner applicable when the attributes are the same or different is similar to a manner for a length of a time unit occupied by an uplink control channel. In other words, a quantity of SR configurations is a quantity of SR configurations associated with a same attribute. Therefore, details are not described herein again.
In manner 4, SR configurations associated with different uplink control channel attributes can be reported distinctively, with higher flexibility.
In this application, a location relationship between an SR bit(s) and a HARQ bit(s) in a bit sequence may include but is not limited to the following:

(1) First location relationship: As shown in FIG. 13A, an SR bit(s) is adjacent to a HARQ bit(s), and the SR bit(s) is added after the HARQ bit(s).
(2) Second location relationship: As shown in FIG. 13B, an SR bit(s) is adjacent to a HARQ bit(s), and the HARQ bit(s) is added after the SR bit(s). Because a capacity of an uplink control channel is limited, when a total amount of information to be transmitted is greater than a maximum capacity, information at the tail needs to be discarded, so that information arranged first can be protected. Therefore, when the SR bit(s) is more important, the SR bit(s) is arranged first, to protect the SR bit(s).
(3) Third location relationship: As shown in FIG. 13C, there is another bit between an SR bit(s) and a HARQ bit(s), and the SR bit(s) is added after the HARQ bit(s). When importance of some information is higher than importance of the SR bit(s) but lower than or equal to importance of the HARQ bit(s), the information may be arranged in this place. A beneficial effect of the arrangement is equivalent to (2), where important information is arranged first.
(4) Fourth location relationship: As shown in FIG. 13D, there is another bit between an SR bit(s) and a HARQ bit(s), and the HARQ bit(s) is added after the SR bit(s). When importance of some information is higher than importance of the HARQ bit(s) but lower than or equal to importance of the SR bit(s), the information may be arranged in this place. A beneficial effect of the arrangement is equivalent to (2), where important information is arranged first.
(5) Fifth location relationship: As shown in FIG. 13E, an SR bit(s) is added after a first part of HARQ bits, and a second part of HARQ bits are added after the SR bit(s). An advantage of this manner is as follows: When a frequency-domain resource occupied by an uplink control channel on which HARQ bits and SR bits are carried is allowed to change, for example, when the uplink control channel on a first symbol is on a first frequency-domain resource and the uplink control channel on a second symbol is on a second frequency-domain resource, some HARQ bits and some SR bits are placed on one of the frequency-domain resources, and the rest HARQ bits and rest SR bits are placed on the other frequency-domain resource, thereby improving accuracy in receiving partial information.

FIG. 13A to FIG. 13 E show only a concatenation relationship between an SR bit(s) and a HARQ bit(s) in an original bit sequence prior to coding. Herein, this application does not impose any particular limitation on other bits in (3) and (4), which may be any other bits prior to coding.
In this application, a time unit may be a symbol (symbol), a slot (slot), a mini-slot (mini-slot), or a subframe (subframe). For definitions of these time units, refer to LTE standards. However, the definitions of these time units are not limited to the LTE standards. The definitions of these time units in a different communications standard may differ.
Based on the foregoing main invention principles, the following describes an overall procedure of a signal transmission method provided in this application. As shown in FIG. 7, the signal transmission method provided in this application may include the following steps.
S101. A terminal device generates a first bit(s). Herein, the first bit(s) is the foregoing SR bit(s), and may be used to indicate a scheduling request(s) associated with a first scheduling request configuration(s). The first scheduling request configuration(s) may be at least one of a plurality of scheduling request configurations configured by a network device for the terminal device. Specifically, the generating, by a terminal device, a first bit(s) may include at least one of the following actions: (1) determining a quantity of first bit(s), and perform channel coding on the first bit(s); and (2) determining a bit state of the first bit(s), and determine the first bit(s) based on an attribute of a resource that needs to be requested.
The at least one scheduling request configuration in the plurality of scheduling request configurations may be dynamically configured by the network device, or configured by the network device by using higher layer signaling. Herein, the higher layer signaling may be media access control (Media Access Control, MAC) layer signaling or radio resource control (Radio Resource Control, RRC) layer signaling. The at least one scheduling request configuration may be at least one of a plurality of scheduling request configurations dynamically configured by the network device for the terminal device, or the at least one scheduling request configuration may be at least one of a plurality of scheduling request configurations configured by the network device for the terminal by using higher layer signaling.
For description of the at least one scheduling request configuration and the plurality of scheduling request configurations, refer to the foregoing section about the invention principles. Details are not described herein again.
S102. The terminal device generates a hybrid automatic repeat request bit(s). The hybrid automatic repeat request bit(s) is used to feed back a result of decoding one or more downlink data blocks by the terminal device, and the result may be a positive acknowledgment ACK or a negative acknowledgment ACK. The ACK indicates that the terminal has correctly performed the decoding. The NACK indicates that an error has occurred during the decoding by the terminal. It may be understood that, if the terminal feeds back a negative acknowledgment, the network device retransmits data for which an error has occurred during the decoding by the terminal.
Specifically, the generating, by the terminal device, a HARQ bit(s) may include at least one of the following actions: determining a quantity of HARQ bit(s), and performing channel coding on the HARQ bit(s); and determining a bit state of the HARQ bit(s), and determining the HARQ bit(s) based on a downlink data reception status.
S103. The terminal device sends the hybrid automatic repeat request bit(s) and the first bit(s) in one time unit. Correspondingly, the network device may receive the hybrid automatic repeat request bit(s) and the first bit(s) from the terminal device in the time unit.
S104. The network device may determine, based on the first bit(s), the scheduling request(s) associated with the first scheduling request configuration(s).
In an implementation, with reference to an SR bit(s) design solution provided in the subsequent Embodiment 1, the network device may determine, based on a state of each bit in the first bit(s), an SR (a positive SR or a negative SR) associated with an SR configuration corresponding to each bit.
For example, it is assumed that a possible state of each bit in the first bit(s) and a possible SR configuration corresponding to each bit are shown in Table 5. If the first bits actually transmitted are "0XXX", the network device may determine that the scheduling request associated with the first scheduling request configuration(s) is a negative SR associated with an SR configuration #0. If the first bits actually transmitted are "X1XX", the network device may determine that the scheduling request associated with the first scheduling request configuration is a positive SR associated with an SR configuration #1. The example is merely used to explain this application, and shall not be construed as any limitation.
In another implementation, with reference to an SR bit design solution provided in the subsequent Embodiment 1, the network device may determine, based on a state of a first bit(s), an SR (a positive SR or a negative SR) corresponding to the state.
For example, it is assumed that a possible state of each bit in the first bit(s) and a possible SR configuration corresponding to each bit are shown in Table 6-1. If first bits actually transmitted are "001", the network device may determine that the scheduling request associated with the first scheduling request configuration(s) is a positive SR associated with an SR configuration #0. If the first bits actually transmitted are "000", the network device may determine that the scheduling request associated with the first scheduling request configuration(s) is: negative SRs associated with SR configurations #0, #1, #2, and #3, in other words, SRs associated with all the SR configurations are negative SRs.
Not limited to a case shown in FIG. 7, there may be another time sequence of S101 and S102. For example, S102 is performed before S101. This is not limited in this application.
The following describes, in detail with reference to a plurality of embodiments, how to design the SR bit(s).

(1) Embodiment 1

In this embodiment, one bit in the SR bit(s) (namely, the first bit(s)) is used to indicate a scheduling request(s) associated with one SR configuration in the at least one SR configuration (namely, first SR configuration(s)). It may be understood that a first SR configuration(s) corresponds to a bit(s) in the SR bit(s). Specifically, one SR configuration corresponds to one bit in the SR bit(s). In this case, a quantity O^SR of the SR bits is equal to a quantity of the plurality of SR configurations (namely, the plurality of SR configurations mentioned in the foregoing invention principles) configured for the terminal. This is a manner in which the quantity O^SR of the SR bits is related to the quantity of the plurality of SR configurations. For a definition of the quantity of the plurality of SR configurations mentioned in the foregoing invention principles, refer to the foregoing section about the invention principles. Details are not described herein again.

One bit in the SR bit(s) is used to indicate whether an SR associated with one SR configuration in the first SR configuration(s) is a positive SR or a negative SR. Specifically, one bit in the SR bit(s) is used to indicate whether an SR associated with one SR configuration corresponding to the bit is a positive SR or a negative SR. For example, it is assumed that one bit in the SR bit(s) corresponds to an SR configuration #0. Table 4 shows the bit and an indication meaning of the bit.

Table 4

Bit state	Indication meaning of a bit (a corresponding SR configuration, and an SR associated with the SR configuration)
0	Negative SR associated with an SR configuration #0
1	Positive SR associated with an SR configuration #0

The left column in Table 4 represents a state ("0" or "1") of the bit, and the right column in Table 4 represents an SR indicated by the bit. When the state of the bit is "0", it indicates that the SR indicated by the bit is a negative SR associated with the SR configuration #0; or when the state of the bit is "1", it indicates that the SR indicated by the bit is a positive SR associated with the SR configuration #0. Table 4 is merely intended to explain this application. In practical application, a correspondence between the state of the bit and the SR indicated by the bit may be contrary to that shown in Table 4, and this is not limited herein.
The following describes Embodiment 1 in detail by using an example in which there are four SR bits (O^SR= 4).
It is assumed that the four SR bits respectively correspond to four different SR configurations: an SR configuration #3, an SR configuration #2, an SR configuration #1, and an SR configuration #0.
Optionally, as shown in FIG. 14A, the four SR bits may respectively correspond, in an order from a most significant bit to a least significant bit, to an SR configuration #3, an SR configuration #2, an SR configuration #1, and an SR configuration #0. Optionally, as shown in FIG. 14B, the four SR bits may respectively correspond, in an order from a least significant bit to a most significant bit, to an SR configuration #3, an SR configuration #2, an SR configuration #1, and an SR configuration #0.
Not limited to the manners shown in FIG. 14A and FIG. 14B, the four SR bits may correspond to four different SR configurations in another manner, and this is not limited herein.
Specifically, a correspondence similar to a correspondence that is shown in FIG. 14A or FIG. 14B and that is between an SR configuration and a bit in the SR bits may be dynamically configured by a network device, or may be configured by a network device by using higher layer signaling. The correspondence may include B SR configurations, and B bits respectively corresponding to the B SR configurations. In this way, a terminal device may determine, based on the correspondence, each bit corresponding to each SR configuration of the at least one SR configuration (namely, first SR configuration(s)) in the SR bits. Herein, B is a positive integer. In this application, the correspondence configured by the network device or configured by using higher layer signaling may be referred to as a first correspondence.

It is assumed that the correspondence shown in FIG. 14A is used as for the four SR bits and the four SR configurations. Table 5 shows an example of an indication meaning of each bit in the SR bits.

Table 5

State	Indication meaning of bits
0XXX	Negative SR associated with an SR configuration #0
1XXX	Positive SR associated with an SR configuration #0
X0XX	Negative SR associated with an SR configuration #1
X1XX	Positive SR associated with an SR configuration #1
XX0X	Negative SR associated with an SR configuration #2
XX1X	Positive SR associated with an SR configuration #2
XXX0	Negative SR associated with an SR configuration #3
XXX1	Positive SR associated with an SR configuration #3

In Table 5, row 1 and row 2 represent the first most significant bit of the SR bits and a meaning of the bit. When a state of the bit is "0", it indicates that an SR indicated by the bit is a negative SR associated with an SR configuration #0, in other words, an SR associated with an SR configuration #0 reported by a terminal is a negative scheduling request; or when a state of the bit is "1", it indicates that an SR indicated by the bit is a positive SR associated with an SR configuration #0, in other words, an SR associated with an SR configuration #0 reported by a terminal is a positive scheduling request. In this case, "X" in row 1 and row 2 means that, whether a state of any other bit is 0 or 1 does not affect a correspondence between the first bit and the SR configuration #0, and does not affect indication, by the first bit, of whether the SR associated with the SR configuration #0 is a positive SR or a negative SR. Similarly, every two rows of the rest rows in Table 5 represent a bit in the SR bits and an indication meaning of the bit, and details are not described herein again.
In the example shown in Table 5, if a bit state of the SR bits is "0011", it indicates that indicated SRs are: a negative SR associated with an SR configuration #0, a negative SR associated with an SR configuration #1, a positive SR associated with an SR configuration #2, and a positive SR associated with an SR configuration #3. In other words, the terminal device actually reports two positive SRs: a positive SR associated with an SR configuration #2, and a positive SR associated with an SR configuration #3. Similarly, when values of a plurality of other bits in the SR bits are "1", it indicates that the terminal device actually reports positive SRs associated with a plurality of other SR configurations. In particular, when the bit state of the SR bits is "1111", it indicates that the SR bits allow the terminal device to simultaneously report positive SRs associated with a maximum of four different SR configurations.
This application is not limited to that one SR configuration corresponds to one bit in the SR bits. In Embodiment 1, one SR configuration may alternatively correspond to a plurality of bits in the SR bits. In other words, a plurality of bits may be used to indicate an SR associated with one SR configuration. In this case, a quantity O^SR of the SR bits is equal to an integer multiple of a quantity of SR configurations (namely, the plurality of SR configurations mentioned in the foregoing invention principles) configured by the network device for the terminal. This is another manner in which the quantity O^SR of the SR bits is related to the quantity of the SR configurations configured by the network device for the terminal. For a definition of the quantity of the plurality of SR configurations mentioned in the foregoing invention principles, refer to the foregoing section about the invention principles. Details are not described herein again.
For example, in the example shown in Table 5, two most significant bits of the SR bits are used to indicate an SR associated with an SR configuration #0. When a state of the two bits is "00", it indicates that the SR indicated by the two bits is a negative SR associated with the SR configuration #0; or when a state of the two bits is a non-zero state ("01", or "10", or "11"), it indicates that the SR indicated by the two bits is a positive SR associated with the SR configuration #0. The example is merely an implementation provided in this application and shall not be construed as any limitation, and the implementation may vary in practical application. In this way, a plurality of non-zero states may be used to indicate a plurality of available attributes (for example, a TTI) of an uplink control channel that carries an SR, so as to instruct the network device to select one attribute from the plurality of attributes, thereby adapting to a scenario of a plurality of uplink control channel attributes in SR management.
It can be learned from the foregoing description that, in the SR bit design solution provided in Embodiment 1, a plurality of SRs can be reported, and SRs associated with a plurality of different SR configurations can be flexibly reported.

(2) Embodiment 2

In this embodiment, a bit state of an SR bit(s) (namely, a first bit(s)) is used to indicate a scheduling request(s) associated with the at least one SR configuration (namely, first SR configuration(s)). The SR (positive SR or negative SR) associated with the first SR configuration(s) corresponds to the state of the SR bit(s).
Optionally, a first state of the SR bit(s) is used to indicate that the SR(s) associated with the first SR configuration(s) is a negative SR(s).
Optionally, at least one state of the SR bit(s) other than the first state is used to indicate that the SR(s) associated with the first SR configuration(s) is a positive SR(s).
Optionally, no state of the SR bit(s) other than the first state is used to indicate that any one of the SR(s) associated with the first SR configuration(s) is a negative SR.
Specifically, in a plurality of states of the SR bits, only one state (for example, a zero state) corresponds to a negative SR associated with the first SR configuration(s). In other words, the only one state is used to indicate that the SRs associated with the first SR configuration(s) are all negative SRs. It may be understood that, at least one state other than the only state is not used to indicate that any one of the SRs associated with the first SR configuration(s) is a negative SR. The at least one state other than the only one state corresponds to a positive SR(s) associated with at least one SR configuration in the first SR configuration(s). In other words, the at least one state other than the only one state is used to indicate a positive SR(s) associated with at least one SR configuration. In this application, the only state may be referred to as a first state.

It is assumed that the SR bits have three bits, and states of the three bits are used to indicate SRs associated with four different SR configurations. Table 6-1 and Table 6-2 show examples of an indication meaning of each state of the SR bits.

Table 6-1

Bit state	Indication meaning of bits
000	Negative SRs associated with SR configurations #0, #1, #2, and #3
001	Positive SR associated with an SR configuration #0
010	Positive SR associated with an SR configuration #1
011	Positive SR associated with an SR configuration #2

Bit state	Indication meaning of bits
100	Positive SR associated with an SR configuration #3
101	Reserved
110	Reserved
111	Reserved

Table 6-2

Bit state	Indication meaning of bits
000	Negative SRs associated with SR configurations #0, #1, #2, and #3
001	Positive SR associated with an SR configuration #0
010	Positive SR associated with an SR configuration #1
011	Positive SR associated with an SR configuration #2
100	Positive SR associated with an SR configuration #3
101	Positive SRs associated with an SR configuration #0 and an SR configuration #1
110	Positive SRs associated with an SR configuration #2 and an SR configuration #3
111	Positive SRs associated with SR configurations #0, #1, #2, and #3

When the state of the SR bits is "000", it indicates that SRs associated with SR configurations #0, #1, #2, and #3 are all negative SRs. In other states of the SR bits, at least one state represents a positive SR associated with at least one SR configuration. For details, refer to Table 6-1 and Table 6-2.
It can be learned from the foregoing description that, in the SR bit design solution provided in Embodiment 2, an amount of information carried by an uplink control channel may be reduced by indicating, by using a relatively small quantity of bits, each SR associated with the at least one SR configuration (namely, first SR configuration(s)), thereby improving a transmission success rate of the uplink control channel.
Specifically, a correspondence similar to a correspondence that is shown in Table 6-1 or Table 6-2 and that is between an SR and a state of the SR bits may be dynamically configured by a network device, or may be configured by a network device by using higher layer signaling. The correspondence may include SRs associated with P SR configurations, and Q states corresponding to the SRs associated with the P SR configurations. In this way, a terminal may determine, based on the correspondence, a state corresponding to an SR associated with the at least one SR configuration (namely, first SR configuration(s)). Herein, Q ≥ 3, Q is a positive integer, P ≥ 2, and P is a positive integer. In this application, the correspondence may be referred to as a second correspondence.
In Embodiment 2, a quantity O^SR of the SR bits may be: O^SR = ceil(log₂ (1+N_{configuration})), where N_{configuration} represents a quantity of SR configurations (namely, the plurality of SR configurations mentioned in the foregoing invention principles) configured for the terminal, and ceil represents rounding up to a next integer. This is another manner in which the quantity O^SR of the SR bits is related to the quantity of the SR configurations configured by the network device for the terminal. For a definition of the quantity of the plurality of SR configurations mentioned in the foregoing invention principles, refer to the foregoing section about the invention principles. Details are not described herein again.
In Embodiment 2, a state of the SR bits may alternatively be used to indicate SRs associated with a plurality of SR configurations.
For example, a state "101" in Table 6-2 is used to indicate a positive SR associated with an SR configuration #0 and a positive SR associated with an SR configuration #1. In other words, when the SR bits are "101", the terminal device reports a positive SR associated with an SR configuration #0 and a positive SR associated with an SR configuration #1. In this case, it may be understood that this is equivalent to reporting of a negative SR associated with an SR configuration #2 and a negative SR associated with an SR configuration #3. Similarly, a state "110" in Table 6-2 may be used to indicate a positive SR associated with an SR configuration #3 and a positive SR associated with an SR configuration #2; and a state "111" in Table 6-2 may be used to indicate a positive SR associated with an SR configuration #3, a positive SR associated with an SR configuration #2, a positive SR associated with an SR configuration #1, and a positive SR associated with an SR configuration #0. The example is merely used to explain this application, and shall not be construed as any limitation.
Optionally, an index of an SR configuration associated with one positive SR may be used as a maximum value, and SRs associated with SR configurations whose indices are less than the maximum value are all positive SRs. In this way, the terminal device can indicate, based on only a state of an SR bit corresponding to this positive SR, positive SRs associated with a plurality of SR configurations.
For example, it is assumed that a state of the SR bits is "100", used to indicate a positive SR associated with an SR configuration #3. In this case, the index "3" of the SR configuration #3 is used as a maximum value, and SRs respectively associated with an SR configuration #2, an SR configuration #1, and an SR configuration #0 whose indices are less than "3" are all positive SRs. The example is merely used to explain this application, and shall not be construed as any limitation.
Optionally, an index of an SR configuration associated with one positive SR may be used as a minimum value, and SRs associated with SR configurations whose indices are greater than the minimum value are all positive SRs. In this way, the terminal device can indicate, based on only a state of an SR bit corresponding to the positive SR, positive SRs associated with a plurality of SR configurations.
For example, it is assumed that a state of the SR bits is "001", used to indicate a positive SR associated with an SR configuration #1. In this case, the index "1" of the SR configuration #1 is used as a minimum value, and SRs respectively associated with an SR configuration #2 and an SR configuration #3 whose indices are greater than "1" are all positive SRs. The example is merely used to explain this application, and shall not be construed as any limitation.
With reference to Embodiment 1 or Embodiment 2, in some optional implementations, a quantity of HARQ bits sent along with the SR bit(s) is greater than or equal to X, X ≥ 2, and X is a positive integer. This prevents affecting a transmission success rate for a small quantity of HARQ bits. This is because reliability of HARQ transmission design increases as the quantity of HARQ bits increases. In other words, when the quantity of HARQ bits is relatively small, it is not suitable to add a plurality of SR bits after a HARQ bit.
With reference to Embodiment 1 or Embodiment 2, in some optional implementations, a length of a current time unit is greater than or equal to Y symbols, Y ≥ 1, and Y is a positive integer. This prevents affecting a transmission success rate of an uplink control channel in a time unit of a short length. This is because transmit power of an uplink control channel in a current time unit increases as a time length of a current time-domain resource increases, bringing higher reliability. In other words, when the time length of the current time unit is relatively small, it is not suitable for the uplink control channel in the current time unit to carry a plurality of SR bits.
FIG. 15 shows a wireless communications system, a terminal, and a network device according to this application. The wireless communications system 10 includes: a terminal 400 and a network device 500. The terminal 400 may be the terminal 200 in the embodiment in FIG. 4, the network device 500 may be the network device 300 in the embodiment in FIG. 5, and the wireless communications system 10 may be the wireless communications system 100 described in FIG. 3, as separately described below.
As shown in FIG. 15, the terminal 400 may include: a generation unit 401 and a sending unit 403.
The generation unit 401 may be configured to generate a first bit(s). The first bit(s) may be used to indicate a scheduling request(s) associated with a first scheduling request configuration(s), and the first scheduling request configuration(s) may be at least one of a plurality of scheduling request configurations.
The generation unit 401 may be further configured to generate a hybrid automatic repeat request bit(s).
The sending unit 403 may be configured to send the hybrid automatic repeat request bit(s) and the first bit(s) in one time unit.
In this application, a quantity of the plurality of scheduling request configurations may be equal to a quantity of scheduling request configurations in the time unit, or a quantity of the plurality of scheduling request configurations may be equal to a quantity of all scheduling request configurations.
Specifically, the first bit(s) may indicate, in the following manners, the scheduling request(s) associated with the first scheduling request configuration(s):
In a first manner, one bit in the first bit(s) may be used to indicate a scheduling request(s) associated with one scheduling request configuration in first scheduling request configuration(s). For details about the first manner, refer to Embodiment 1. Details are not described herein again. In a second manner, a first state of the first bit(s) may be used to indicate that the scheduling request(s) associated with the first scheduling request configuration(s) is a negative scheduling request(s), at least one state of the first bit(s) other than the first state may be used to indicate that the scheduling request(s) associated with the first scheduling request configuration(s) is a positive scheduling request(s), and no state of the first bit(s) other than the first state is used to indicate that any one of the scheduling request(s) associated with the first scheduling request configuration(s) is a negative scheduling request.
For details about the second manner, refer to Embodiment 2. Details are not described herein again.
Specifically, a quantity of the first bit(s) may be related to the quantity of the plurality of scheduling request configurations, specifically in the following manners:
In a correlation manner, when the design solution in Embodiment 1 is used for the SR bits, a quantity O^SR of the SR bits may be equal to the quantity of the plurality of scheduling request configurations.
In another correlation manner, when the design solution in Embodiment 2 is used for the SR bits, a quantity O^SR of the SR bits may be: O^SR = ceil(log2 (1+N_{configuration})), where N_{configuration} represents a quantity of SR configurations (namely, the plurality of SR configurations mentioned in the foregoing invention principles) configured for the terminal, and ceil represents rounding up to a next integer.
Technical advantages of the correlation between the quantity of the first bit(s) and the quantity of the plurality of scheduling request configurations are as follows: In such a predefinition manner, the network device and the terminal device can determine the quantity of the first bit(s) before the first bit(s) is sent, so that the network device and the terminal device do not have different understandings of the quantity of the first bit(s), thereby avoiding a case in which the first bit(s) fails to be received due to the different understandings.
In some optional implementations, a quantity of HARQ bits sent along with the SR bit(s) is greater than or equal to X, X ≥ 2, and X is a positive integer. This prevents affecting a transmission success rate for a small quantity of HARQ bits. This is because reliability of HARQ transmission design increases as the quantity of HARQ bits increases. In other words, when the quantity of HARQ bits is relatively small, it is not suitable to add a plurality of SR bits after a HARQ bit.
In some optional implementations, a length of the time unit is greater than or equal to Y symbols, Y ≥ 1, and Y is a positive integer. This prevents affecting a transmission success rate of an uplink control channel in a time unit of a short length. This is because transmit power of an uplink control channel in a current time unit increases as a time length of a current time-domain resource increases, bringing higher reliability. In other words, when the time length of the current time unit is relatively small, it is not suitable for the uplink control channel in the current time unit to carry a plurality of SR bits.
It may be understood that, for specific implementation of each functional unit included in the terminal 400, refer to the foregoing embodiments. Details are not described herein again.
As shown in FIG. 15, the network device 500 may include: a receiving unit 501 and a determining unit 503.
The receiving unit 501 may be configured to receive, in one time unit, a hybrid automatic repeat request bit(s) and a first bit(s) that are sent by a terminal device. The first bit(s) may be used to indicate a scheduling request(s) associated with a first scheduling request configuration(s), and the first scheduling request configuration(s) may be at least one of a plurality of scheduling request configurations.
The determining unit 503 may be configured to determine, based on the first bit(s), the scheduling request(s) associated with the first scheduling request configuration(s).
In this application, a quantity of the plurality of scheduling request configurations may be equal to a quantity of scheduling request configurations in the time unit, or a quantity of the plurality of scheduling request configurations may be equal to a quantity of all scheduling request configurations.
Specifically, the first bit(s) may indicate, in the following manners, the scheduling requests associated with the first scheduling request configuration(s):
In a first manner, one bit in the first bit(s) may be used to indicate a scheduling request(s) associated with one scheduling request configuration in first scheduling request configuration(s). In this way, the determining unit 503 may be configured to determine, based on a state of each bit in the first bit(s), an SR (a positive SR or a negative SR) associated with an SR configuration corresponding to each bit.
For details about the first manner, refer to Embodiment 1. Details are not described herein again.
In a second manner, a first state of the first bit(s) may be used to indicate that the scheduling request(s) associated with the first scheduling request configuration(s) is a negative scheduling request(s), at least one state of the first bit(s) other than the first state may be used to indicate that the scheduling request(s) associated with the first scheduling request configuration(s) is a positive scheduling request(s), and no state of the first bit(s) other than the first state is used to indicate that any one of the scheduling request(s) associated with the first scheduling request configuration(s) is a negative scheduling request. In this way, the determining unit 503 may be configured to determine, based on a state of the first bit(s), an SR (a positive SR or a negative SR) corresponding to the state.
For details about the second manner, refer to Embodiment 2. Details are not described herein again.
Specifically, a quantity of the first bit(s) may be related to the quantity of the plurality of scheduling request configurations, specifically in the following manners:
In a correlation manner, when the design solution in Embodiment 1 is used for the SR bits, a quantity O^SR of the SR bits may be equal to the quantity of the plurality of SR configurations.
In another correlation manner, when the design solution in Embodiment 2 is used for the SR bits, a quantity O^SR of the SR bits may be: O^SR = ceil(log2 (1+N_{configuration})), where N_{configuration} represents a quantity of SR configurations (namely, the plurality of SR configurations mentioned in the foregoing invention principles) configured for the terminal, and ceil represents rounding up to a next integer.
In some optional implementations, a quantity of HARQ bits sent along with the SR bit(s) is greater than or equal to X, X ≥ 2, and X is a positive integer. This prevents affecting a transmission success rate for a small quantity of HARQ bits. This is because reliability of HARQ transmission design increases as the quantity of HARQ bits increases. In other words, when the quantity of HARQ bits is relatively small, it is not suitable to add a plurality of SR bits after a HARQ bit.
In some optional implementations, a length of the time unit is greater than or equal to Y symbols, Y ≥ 1, and Y is a positive integer. This prevents affecting a transmission success rate of an uplink control channel in a time unit of a short length. This is because transmit power of an uplink control channel in a current time unit increases as a time length of a current time-domain resource increases, bringing higher reliability. In other words, when the time length of the current time unit is relatively small, it is not suitable for the uplink control channel in the current time unit to carry a plurality of SR bits.
It may be understood that, for specific implementation of each functional unit included in the network device 500, refer to the foregoing embodiments. Details are not described herein again.
FIG. 16 is a schematic structural diagram of an apparatus according to this application. As shown in FIG. 16, the apparatus 50 may include: a processor 501, and one or more interfaces 502 coupled to the processor 501. Optionally, the apparatus 50 may further include a memory 503. Optionally, the apparatus 50 may be a chip.
The processor 501 may be configured to read and execute a computer readable instruction. In specific implementation, the processor 501 may mainly include a controller, an arithmetic unit, and a register. The controller is mainly responsible for decoding an instruction, and sending a control signal for an operation that corresponds to the instruction. The arithmetic unit is mainly responsible for performing a fixed-point or floating-point arithmetic operation, a shift operation, a logic operation, and the like; and may also perform address calculation and conversion. The register is mainly responsible for storing a register operand and an intermediate operation result to be temporarily stored in a process of executing an instruction, and the like. In specific implementation, a hardware architecture of the processor 501 may be an application-specific integrated circuit (Application-Specific Integrated Circuit, ASIC) architecture, a MIPS architecture, an ARM architecture, an NP architecture, or the like. The processor 501 may be a single-core processor, or may be a multi-core processor.
The memory 503 may be configured to store program code including a computer-accessible instruction, and may be further configured to store input/output data of the processor 501.
The input/output interface 502 may be configured to input to-be-processed data to the processor 501, and may output a processing result of the processor 501. In specific implementation, the interface 502 may be a general purpose input/output (General Purpose Input/Output, GPIO) interface, and may be connected to a plurality of peripheral devices (for example, a display (LCD), a camera, and a radio frequency module). The interface 502 may further include a plurality of independent interfaces, for example, an Ethernet interface, an LCD interface, and a camera interface, which are respectively responsible for communication between different peripheral devices and the processor 501.
In this application, the processor 501 may be configured to invoke, from the memory, a program for implementing, on a terminal side, a signal transmission method provided in one or more embodiments of this application, and execute an instruction included in the program. The interface 502 may be configured to output an execution result of the processor 501. In this application, the interface 502 may be specifically configured to output a processing result of the processor 501. Specifically, the processor 501 may be configured to generate a first bit(s) and a hybrid automatic repeat request bit(s), and the interface 502 may be configured to output the first bit(s) and the hybrid automatic repeat request bit(s). For description related to the first bit(s), refer to the foregoing embodiments. Details are not described herein again. For the signal transmission method provided in one or more embodiments of this application, refer to the foregoing embodiments. Details are not described herein again.
It should be noted that, functions respectively corresponding to the processor 501 and the interface 502 may be implemented by using hardware design, or may be implemented by using software design, or may be implemented by combining software and hardware, and this is not limited herein.
FIG. 17 is a schematic structural diagram of an apparatus according to this application. As shown in FIG. 17, the apparatus 60 may include: a processor 601, and one or more interfaces 601 coupled to the processor 602. Optionally, the apparatus 60 may further include a memory 603. Optionally, the apparatus 60 may be a chip.
The processor 601 may be configured to read and execute a computer readable instruction. In specific implementation, the processor 601 may mainly include a controller, an arithmetic unit, and a register. The controller is mainly responsible for decoding the instruction, and sending a control signal for an operation that corresponds to the instruction. The arithmetic unit is mainly responsible for performing a fixed-point or floating-point arithmetic operation, a shift operation, a logic operation, and the like; and may also perform address calculation and conversion. The register is mainly responsible for storing a register operand and an intermediate operation result to be temporarily stored in a process of executing the instruction, and the like. In specific implementation, a hardware architecture of the processor 601 may be an application-specific integrated circuit (Application-Specific Integrated Circuit, ASIC) architecture, or the like. The processor 601 may be a single-core processor, or may be a multi-core processor.
The memory 603 may be configured to store program code including a computer-accessible instruction, and may be further configured to store input/output data of the processor 601.
The input/output interface 602 may be configured to input data to be processed to the processor 601, and may output a processing result of the processor 601.
In this application, the processor 601 may be configured to: invoke, from the memory, a program for implementing, on a network device side, a signal transmission method provided in one or more embodiments of this application, and execute an instruction included in the program. The interface 602 may be configured to output an execution result of the processor 601. Specifically, the processor 601 may be configured to determine, based on a first bit(s) from a terminal device, a scheduling request(s) associated with a first scheduling request configuration(s), and the interface 602 may be configured to output the scheduling request(s) that is determined by the processor 601 and that is associated with the first scheduling request configuration(s). For description related to the first bit(s), the first scheduling request configuration(s), and the like, refer to the foregoing embodiments. Details are not described herein again. For the signal transmission method provided in one or more embodiments of this application, refer to the foregoing embodiments. Details are not described herein again.
It should be noted that, functions respectively corresponding to the processor 601 and the interface 602 may be implemented by using hardware design, or may be implemented by using software design, or may be implemented by combining software and hardware, and this is not limited herein.
In summary, a plurality of scheduling request configurations can be supported by implementing the foregoing solutions provided in this application, so as to adapt to a multi-service scenario in a communications system.
A person of ordinary skill in the art may understand that all or some of the processes of the methods in the foregoing embodiments may be implemented by a computer program instructing related hardware. The program may be stored in a computer readable storage medium. When the program runs, the processes of the methods in the foregoing embodiments are performed. The foregoing storage medium includes: any medium that can store program code, such as a ROM, a random access memory RAM, a magnetic disk, or an optical disc.

Claims

A signal transmission method performed in a terminal device, comprising:
generating (S101) a first scheduling request, SR, bit sequence, wherein a quantity of bits of the first SR bit sequence is equal to ceil(log₂(1+N)), wherein ceil represents an operation of rounding up to a next integer, and N is a quantity of a plurality of SR configurations, an SR configuration indicates at least one of the following:
a time-domain location of an SR, and

a frequency-domain location of an SR;

wherein a first state of the first SR bit sequence indicates that all of a plurality of SRs are negative SRs;

wherein a second state of the first SR bit sequence indicates that a first SR is a positive SR, and the second state is different from the first state;

wherein the first SR is one SR of a plurality of SRs, the first SR is associated with a first SR configuration, and the first SR configuration is one of the plurality of SR configurations ;

generating (S102) a hybrid automatic repeat request, HARQ, ACK/NACK bit sequence; and

sending (S103) the HARQ ACK/NACK bit sequence and the first SR bit sequence through an uplink control channel.
A signal transmission method performed in a network device, comprising:
receiving (S103) a hybrid automatic repeat request, HARQ, ACK/NACK bit sequence and a first scheduling request, SR, bit sequence through an uplink control channel, wherein a quantity of bits of the first SR bit sequence is equal to ceil(log₂(1+N)), wherein ceil represents an operation of rounding up to a next integer, and N is a quantity of a plurality of SR configurations, an SR configuration indicates at least one of the following:
a time-domain location of an SR, and

a frequency-domain location of an SR;

wherein a first state of the first SR bit sequence indicates that all of a plurality of SRs are negative SRs,

wherein a second state of the first SR bit sequence indicates that a first SR is a positive SR, and the second state is different from the first state,

wherein the first SR is one of a plurality of SRs, the first SR is associated with a first SR configuration, and the first SR configuration is one of the plurality of SR configurations; and

determining (S014), based on the first SR bit sequence, the first SR associated with the first SR configuration.
The method according to claim 1 or 2, wherein a channel state information, CSI, bit sequence is appended at an end of the first SR bit sequence, and the first SR bit sequence is appended at an end of the HARQ bit sequence.
The method according to any one of claims 1 to 3, wherein the first state is an all-zero state for all bits of the first SR bit sequence.
The method according to any one of claims 1 to 4, wherein no state of the first SR bit sequence other than the first state indicates that any one of the plurality of SRs is a negative SR.
The method according to claim 5, wherein the second state is '001', a third state of the first SR bit sequence is '010', a fourth state of the first SR bit sequence is '011', and a fifth state of the first SR bit sequence is '100',
wherein the third state indicates a second SR associated with a second SR configuration is a positive SR, the fourth state indicates a third SR associated with a third SR configuration is a positive SR, the fifth state indicates a fourth SR associated with a fourth SR configuration is a positive SR, and the second SR configuration, the third SR configuration and the fourth SR configuration are three SR configurations of the plurality of SR configurations,

and wherein index numbers of the first SR configuration, the second SR configuration, the third SR configuration and the fourth SR configuration are in ascending order.
An apparatus (50), the apparatus being configured to carry out a method according to any one of claims 1 and 3 to 6.
An apparatus (60), the apparatus being configured to carry out a method according to any one of claims 2 and 3 to 6.
A computer readable storage medium comprising instructions which, when executed by a computer, cause the computer to carry out the method according to any one of claims 1 to 6.
A communication system, comprising:
an apparatus according to claim 7 and an apparatus according to claim 8.