Patent Description:
A network side device may preconfigure an uplink resource for a terminal. The uplink resource may be referred to as a preconfigured uplink resource (preconfigured uplink resource, PUR). However, the network side device does not know whether the terminal needs the preconfigured uplink resource, nor does it know content of a preconfigured uplink resource required by the terminal. As a result, an uplink resource configured on a network side device may not satisfy a demand of the terminal.

<CIT> discloses methods, systems, and devices related to digital wireless communication, and more specifically, to techniques related to pre-configure dedicated resources for data transmission. In one exemplary aspect, a method for wireless communication includes receiving a pre-configured transmission resource request from a terminal. The method also includes configuring a pre-configured transmission resource based on the pre-configured transmission resource request. In another exemplary embodiment, a method for wireless communication includes receiving a pre-configured transmission resource request from a terminal, wherein the pre-configured transmission resource request includes a medium access control (MAC) control element. The method also includes configuring a pre-configured transmission resource based on the pre-configured transmission resource request.

R2-<NUM> discloses method regarding improvement of the uplink transmission efficiency and /or UE power consumption by means of transmission in preconfigured resources.

<CIT> discloses a method for a terminal to transmit uplink data, and an apparatus therefor. The method may include: transmitting, to a base station, help information for transmitting uplink data using a pre-configured uplink resource; receiving, from the base station, configuration information for transmitting the uplink data using the pre-configured uplink resource; and transmitting the uplink data through the pre-configured uplink resource on the basis of the configuration information.

Objectives of embodiments of this application are to provide a method for sending auxiliary information, a method for receiving auxiliary information, a terminal, and a network side device, to resolve the problem that an uplink resource configured on a network side device may not satisfy a demand of a terminal.

The terms "first", "second", and the like in the specification and claims of this application are used to distinguish between similar objects instead of describing a specific order or sequence. It should be understood that, data termed in such a way is interchangeable in proper circumstances, so that the embodiments of this application can be implemented in an order other than the order illustrated or described herein. Objects classified by "first" and "second" are usually of a same type, and the quantity of objects is not limited. For example, there may be one or more first objects. In addition, in the specification and the claims, "and/or" represents at least one of connected objects, and a character "/" generally represents an "or" relationship between associated objects.

It should be noted that the technology described in the embodiments of this application is not limited to a long term evolution (Long Term Evolution, LTE)/LTE-Advanced (LTE-Advanced, LTE-A) system, and can also be used in various wireless communications systems, such as code division multiple access (Code Division Multiple Access, CDMA), time division multiple access (Time Division Multiple Access, TDMA), frequency division multiple access (Frequency Division Multiple Access, FDMA), orthogonal frequency division multiple access (Orthogonal Frequency Division Multiple Access, OFDMA), single-carrier frequency-division multiple access (Single-carrier Frequency-Division Multiple Access, SC-FDMA), and other systems. The terms "system" and "network" in the embodiments of this application may be used interchangeably. The technologies described can be applied to both the systems and the radio technologies mentioned above as well as to other systems and radio technologies. However, a new radio (New Radio, NR) system is described below as an example, and the term NR is used in most of the descriptions, although these technologies can also be used in an application other than an application of the NR system, for example, a 6th generation (6th Generation, <NUM>) communications system.

<FIG> is a block diagram of a wireless communications system to which embodiments of this application can be applied. The wireless communications system includes a terminal <NUM> and a network side device <NUM>. The terminal <NUM> may be also referred to as a terminal device or user equipment (User Equipment, UE). The terminal <NUM> may be a terminal side device such as a mobile phone, a tablet personal computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or referred to as a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a palmtop computer, a netbook, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), a wearable device (Wearable Device), vehicle user equipment (vehicle user equipment, VUE), or pedestrian user equipment (pedestrian user equipment, PUE). The wearable device includes a bracelet, a headset, glasses, or the like. It should be noted that a specific type of the terminal <NUM> is not limited in the embodiments of this application. The network side device <NUM> may be a base station or a core network. The base station may be referred to as a Node B, an evolved Node B, an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service set (Basic Service Set, BSS), an extended service set (Extended Service Set, ESS), a Node B, an evolved Node B (evolved Node B, eNB), a home Node B, a home evolved Node B, a wireless local area network (wireless local area network, WLAN) access point, a WiFi (wireless fidelity, WiFi) node, a transmission and reception point (Transmitting Receiving Point, TRP), or other certain appropriate terms in the art. Provided that the same technical effects are achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiments of this application, a base station in the NR system is merely used as an example, but does not limit a specific type of the base station.

With reference to the accompanying drawings, the following describes in detail a method and an apparatus for sending auxiliary information, a method and an apparatus for receiving auxiliary information, a terminal, and a network side device in the embodiments of this application based on specific embodiments and application scenarios thereof.

<FIG> is a flowchart of a method for sending auxiliary information according to an embodiment of this application. As shown in <FIG>, the method for sending auxiliary information is applied to a terminal and includes the following steps:.

Step <NUM>: Send auxiliary information for a target configuration to a network side device, where the target configuration is a configuration related to transmission of a preconfigured physical uplink shared channel PUSCH resource.

In this embodiment of this application, the target configuration may be understood as a configuration related to transmission of an uplink resource preconfigured by the network side device. Specifically, the target configuration may be a configuration related to transmission of a preconfigured physical uplink shared channel (Physical Uplink Shared Channel, PUSCH) resource. For example, the target configuration may be similar to PUR-Config in LTE. For another example, the target configuration may be a configuration related to a transmission mode of a preconfigured PUSCH resource for small data transmission (Small Data Transmission, SDT) in NR. In addition to the above target configuration, there may be another target configuration. This is not limited in this embodiment of this application.

The following briefly describes an NR SDT data service.

The NR SDT data service may be understood as a service of small and infrequent data. For example, an NR SDT data service in an application of a smartphone may include data of an instant messaging service, heart-beat/keep-alive data of an instant messaging (Instant Messaging, IM)/email client and another application, push notifications of various applications, and the like. For another example, an NR SDT data service in an application of a dumbphone may include periodic positioning messages of a wearable device, data of a sensor, data of a smart water meter, and the like. The NR SDT data service may alternatively be sporadic low-throughput short data and the like.

In this embodiment of this application, the terminal sends the auxiliary information to the network side device, so that the network side device can configure an uplink resource according to the auxiliary information. Therefore, the auxiliary information can assist the network side device in better configuring the uplink resource, thereby enabling the uplink resource configured by the network side device to better satisfy a demand of the terminal.

Optionally, before the sending auxiliary information for a target configuration to a network side device, the method further includes:.

In this embodiment of this application, the network side device may send the configuration information to the terminal. The configuration information may be used to indicate whether the terminal is allowed to report the auxiliary information. In this way, in a case that the terminal receives the configuration information sent by the network side device and used to indicate that the terminal is allowed to report the auxiliary information, the terminal can send the auxiliary information to the network side device on an appropriate occasion. However, if the terminal receives the configuration information sent by the network side device and used to indicate that the terminal is not allowed to report the auxiliary information, the terminal may not send the auxiliary information to the network side device.

It should be noted that the above configuration information may directly indicate whether the terminal is allowed to report the auxiliary information, or indirectly indicate whether the terminal is allowed to report the auxiliary information.

Optionally, the configuration information includes a target bit, where the target bit is used to indicate whether the terminal is allowed to report the auxiliary information; and/or
the configuration information includes information about a target timer, where the target timer is configured to indicate whether the terminal is allowed to report the auxiliary information.

The target bit may be one bit, and may directly indicate whether the terminal is allowed to report the auxiliary information, or indirectly indicate whether the terminal is allowed to report the auxiliary information. The target timer may be one timer, and may directly indicate whether the terminal is allowed to report the auxiliary information.

Optionally, the sending auxiliary information for a target configuration to a network side device includes:
sending the auxiliary information for the target configuration to the network side device in a case that an initiation condition is satisfied.

Optionally, the initiation condition includes at least one of the following:.

The first transmission mode is a transmission mode related to the target configuration. For example, the first transmission mode may be an LTE PUR transmission mode; or may be a transmission mode of a preconfigured PUSCH resource for SDT in NR. This is not limited in this embodiment of this application.

In the above initiation condition, that the target configuration does not match a service feature of the terminal may be understood as follows: At least one configuration in the target configuration does not match the service feature of the terminal. In other words, that the target configuration does not match a service feature of the terminal may include the following two cases: Some configurations in the target configuration do not match the service feature of the terminal; and all configurations in the target configuration do not match the service feature of the terminal.

In the above initiation condition, the target state in which the terminal reports the auxiliary information may be preconfigured by the network side device, or may be specified in a protocol. If the target state is merely the RRC connected state, the terminal may report the auxiliary information to the network side device only when in the RRC connected state, but cannot report the auxiliary information to the network side device when in the non-RRC connected state. If the target state is merely the non-RRC connected state, the terminal may report the auxiliary information to the network side device only when in the non-RRC connected state, but cannot report the auxiliary information to the network side device when in the RRC connected state. If the target state is the RRC connected state or the non-RRC connected state, the terminal may report the auxiliary information to the network side device when in either the RRC connected state or the non-RRC connected state.

As an example, the initiation condition may be that the terminal is interested in a configuration of the preconfigured PUSCH resource, or that the terminal is interested in a transmission mode of the preconfigured PUSCH resource. As another example, the initiation condition may be that the terminal is not interested in or is no longer interested in a configuration of the preconfigured PUSCH resource, or that the terminal is not interested in or is no longer interested in a transmission mode of the preconfigured PUSCH resource for SDT. As still another example, the initiation condition may be that a configuration of an existing preconfigured PUSCH resource does not match or is not suitable for a service of the terminal, that is, at least one configuration in the target configuration does not match the service feature of the terminal.

The auxiliary information includes first auxiliary information and/or second auxiliary information in a case that the terminal needs the target configuration. The first auxiliary information is used to indicate a tendentious configuration of the terminal for the target configuration, and the second auxiliary information is used to indicate service status of the terminal.

In this implementation, that the terminal needs the target configuration may include a case that the terminal actively needs the target configuration. For example, the terminal is interested in the target configuration. For another example, the terminal is interested in the transmission mode (namely, the first transmission mode) related to the target configuration. Alternatively, the terminal may passively need or be forced to need the target configuration. In other words, the network side device considers that the terminal needs the target configuration. For example, the terminal is not interested in the target configuration or the transmission mode related to the target configuration, but the network side device considers that the terminal needs the target configuration.

Both the first auxiliary information and the second auxiliary information may be understood as content of the auxiliary information. When the terminal initiates reporting of the auxiliary information, the content of the auxiliary information may be specified through an RRC layer of the terminal, and then the auxiliary information may be submitted to an underlying protocol entity for transmission.

In this implementation, the first auxiliary information is used to indicate the tendentious configuration (or referred to as a preferred configuration) of the terminal for the target configuration. The tendentious configuration may be understood as a result of the target configuration. In other words, the terminal expects the network side device to configure the target configuration according to the tendentious configuration, and enables, by sending the first auxiliary information to the network side device, the network side device to be aware of the terminal's tendentious configuration for the target configuration. Therefore, the network side device is enabled to configure the target configuration according to the first auxiliary information.

The second auxiliary information is used to indicate the service status of the terminal. The network side device is enabled to be aware of the service status of the terminal after the second auxiliary information is sent to the network side device, so that the network side device can reasonably configure the target configuration according to the service status of the terminal.

A quantity of pieces of each of the first auxiliary information and the second auxiliary information may be one or more.

Specific content of the first auxiliary information and the second auxiliary information is described below respectively.

Optionally, the first auxiliary information includes at least one of a target configuration identifier, a service identifier, a service pattern identifier, a configuration parameter, and first transmission bearer information.

This embodiment provides the content of the first auxiliary information.

The target configuration identifier may be, for example, PUSCH configuration <NUM>.

The service identifier may be, for example, service <NUM>.

The service pattern identifier may be, for example, traffic pattern <NUM>.

It should be noted that both the service identifier and the service pattern identifier are used to indicate a specific service type or service pattern, and have the same or similar meanings. Therefore, the first auxiliary information may include both the service identifier and the service pattern identifier, or only any one of the service identifier and the service pattern identifier.

Optionally, the configuration parameter includes at least one of a TBS, a quantity of PUSCH occasions (PUSCH occasions), a period of a PUSCH occasion, time offset for the first PUSCH occasion, a bandwidth part (bandwidth Part, BWP) identifier, and a quantity of hybrid automatic repeat requests (Hybrid Automatic Repeat reQuest, HARQ).

The unit of the period of the PUSCH occasion may be any case. The unit of the time offset for the first PUSCH occasion (time offset for the first PUSCH occasion) may also be any case. The BWP identifier may be, for example, activated BWP <NUM>.

The first transmission bearer information includes at least one of a radio bearer identifier, a logical channel identifier, a data flow identifier, a session identifier, and a cell group identifier.

The radio bearer identifier may be, for example, data radio bearer <NUM> (Data Radio bearer <NUM>, DRB1). The logical channel identifier may be, for example, logical channel identifier <NUM> (Logical Channel ID <NUM>, LCID <NUM>). The data flow identifier may be, for example, QoS flow <NUM>. The session identifier may be, for example, PDU session <NUM>. The cell group identifier may be, for example, master cell group (Master Cell Group, MCG) or secondary cell group (Secondary Cell Group, SCG).

The second auxiliary information includes at least one of Quality of Service (Quality of Service, QoS) requirement information and service status information.

A quantity of pieces of each of the QoS requirement information and the service status information may be one or more.

The QoS requirement information includes at least one of a service identifier, a service pattern identifier, QoS description information, and second transmission bearer information; and
the second transmission bearer information is used to indirectly indicate a QoS requirement of the terminal.

The service identifier may be, for example, service identifier (identifier, ID) <NUM>. The service pattern identifier may be, for example, traffic pattern <NUM>. The QoS description information (QoS profile) may be, for example, description information such as low delay and high reliability.

Optionally, the second transmission bearer information includes at least one of a radio bearer identifier, a data flow identifier, a session identifier, and a logical channel identifier.

The radio bearer identifier may be, for example, data radio bearer <NUM> (Data Radio bearer <NUM>, DRB1). The data flow identifier may be, for example, QoS flow <NUM>. The session identifier may be, for example, PDU session <NUM>. The logical channel identifier may be, for example, logical channel identifier <NUM> (Logical Channel ID <NUM>, LCID <NUM>).

Optionally, the service status information includes at least one of a service identifier, a service pattern identifier, a service period (periodicity), a service starting time (starting time), a service ending time (ending time), a service duration time (duration time), and a service size (packet size).

The service identifier may be, for example, service ID <NUM>. The service pattern identifier may be, for example, traffic pattern <NUM>. The service period (or a period of the service pattern) may be any value and any time unit, for example, <NUM> hours.

A quantity of the service starting time (or a starting time of the service pattern) may be one or more. A quantity of the service ending time (or an ending time of the service pattern) may also be one or more. A quantity of the service duration time (or a duration time of the service pattern) may also be one or more. A quantity of the service size (or a size of the service pattern) may also be one or more.

Optionally, a quantity of each of the service starting time, the service ending time, the service duration time, and the service size is one or more.

When the quantity of the service starting time is a complex number, the quantity of the service ending time and/or the service duration time is also a complex number, and a mapping relationship between the service starting time and the service ending time and/or the service duration time is required. For example, service starting time <NUM> corresponds to service ending time <NUM> and/or service duration time <NUM>, and service starting time <NUM> corresponds to service ending time <NUM> and/or service duration time <NUM>.

A time value of the service starting time may be represented in at least one of the following manners:
The time value of the service starting time is represented by an absolute time, for example, <NUM>:<NUM> China Standard Time (CST).

The time value of the service starting time is represented by a relative time, and a reference time thereof may be any time, for example, <NUM>:<NUM> CST.

When the quantity of the service ending time is a complex number, the quantity of the service starting time and/or the service duration time is also a complex number, and a mapping relationship between the service ending time and the service starting time and/or the service duration time is required. For example, service ending time <NUM> corresponds to service starting time <NUM> and/or service duration time <NUM>, and service ending time <NUM> corresponds to service starting time <NUM> and/or service duration time <NUM>.

A time value of the service ending time may be represented in at least one of the following manners:
The time value of the service ending time is represented by an absolute time, for example, <NUM>:<NUM> CST.

The time value of the service ending time is represented by a relative time, and a reference time thereof may be any time, for example, <NUM>:<NUM> CST, or a corresponding service starting time.

When the quantity of the service duration time is a complex number, the quantity of the service starting time and/or the service ending time is also a complex number, and a mapping relationship between the service duration time and the service starting time and/or the service ending time is required. For example, service duration time <NUM> corresponds to service starting time <NUM> and/or service ending time <NUM>, and service duration time <NUM> corresponds to service starting time <NUM> and/or service ending time <NUM>.

A value of the service duration time may be any value and any time unit, for example, <NUM> minutes.

A value of the service size may be any value, and a unit of the service size may be any unit. For example, the service size is <NUM> bits.

The above describes the specific content of the first auxiliary information and the second auxiliary information. Because the auxiliary information includes the above content, for example, the auxiliary information includes content such as the terminal's tendentious configuration for the target configuration, QoS requirement information, service status information, and the like, the network side device can be assisted in better configuring the target resource.

Optionally, the auxiliary information includes third auxiliary information in a case that the terminal does not need the target configuration, and the third auxiliary information is used to indicate that the target configuration needs to be released.

The third auxiliary information may be an identifier used to indicate that an identifier configured for the preconfigured PUSCH resource needs to be released, for example, may be pur-ReleaseRequest.

In a case that the terminal does not need the target configuration, the terminal can enable, by sending the third auxiliary information to the network side device, the network side device to be aware that the terminal does not need the target configuration. Therefore, the network side device does not need to configure the target configuration for the terminal, thereby reducing resource overheads of the network side device in configuring the target configuration.

As an example, two specific embodiments are provided below by taking the target configuration as a configuration related to the transmission of preconfigured PUSCH resource.

As shown in <FIG>, the service pattern of the terminal is burstdata (several data packets are sent at one time, and each interval between the data packets is very short). <FIG> shows that three data packets are sent at one time. These three packets are St1-Et1, St2-Et2, and St3-Et3 respectively.

The network side device uses one bit (bit) in system information to indicate that the terminal is allowed to report the auxiliary information. In a case that the initiation condition of the auxiliary information is satisfied (for example, the terminal is interested in the configuration of the preconfigured PUSCH resource), the terminal sends the auxiliary information to the network side device.

The content of the auxiliary information includes the tendentious configuration related to the configuration of the preconfigured PUSCH resource, the QoS requirement information, and the service status information.

The tendentious configuration related to the configuration of the preconfigured PUSCH resource includes three preferred configurations.

The first preferred configuration includes the following content:
The identifier of the PUSCH configuration is <NUM>.

The configuration parameter includes: the TBS being <NUM> bits, the quantity of the PUSCH occasion being infinite, the period of the PUSCH occasion being <NUM> subframes (subframes), the time offset for the first PUSCH occasion being <NUM> slots (slots), and the identifier of the BWP being activated BWP <NUM>.

The transport bearer is a radio bearer. The radio bearer identifier is DRB1.

The second preferred configuration includes the following content:
The identifier of the PUSCH configuration is <NUM>.

The configuration parameter includes: the TBS being <NUM> bits, the quantity of the PUSCH occasion being infinite, the period of the PUSCH occasion being <NUM> subframes, the time offset for the first PUSCH occasion being <NUM> slots, and the identifier of the BWP being activated BWP <NUM>.

The third preferred configuration includes the following content:
The identifier of the PUSCH configuration is <NUM>.

The QoS requirement information includes one QoS requirement. The QoS requirement is indirectly informed through the transport bearer. The transport bearer is a radio bearer. The radio bearer identifier is DRB1.

The service status information includes the following content:
The period (Periodicity) of the service pattern is <NUM> minutes (60mins).

A quantity of the starting time of the service pattern is <NUM>, namely, St1=<NUM>:<NUM>, St2=<NUM>:<NUM>, and St3=<NUM>:<NUM>.

A quantity of the ending time of the service pattern is <NUM>, namely, Et1=<NUM>:<NUM>, Et2=<NUM>:<NUM>, and Et3=<NUM>:<NUM>.

A quantity of the size of the service pattern is three. Packet <NUM> is <NUM> bits (corresponding to St1 and Et1), Packet <NUM> is <NUM> bits (corresponds to St2 and Et2), and Packet <NUM> is <NUM> bits (corresponds to St3 and Et3).

As shown in <FIG>, when the service pattern of the terminal changes, the configuration of the preconfigured PUSCH resource needs to be updated.

The network side device uses one timer to indicate that the terminal is allowed to report the auxiliary information. In a case that the initiation condition of the auxiliary information is satisfied (for example, the terminal is interested in the transmission mode of the preconfigured PUSCH resource), the terminal sends the auxiliary information to the network side device.

The tendentious configuration related to the configuration of the preconfigured PUSCH resource includes two preferred configurations.

The identifier of the service pattern is <NUM>.

The transport bearer is a radio bearer. The radio bearer identifier is DRB2.

The transport bearer is a radio bearer. The radio bearer identifier is DRB3.

The QoS requirement information includes two QoS requirements. A first QoS requirement is the identifier of the service pattern being <NUM>. The QoS requirement is indirectly informed through the transport bearer. The transport bearer is a radio bearer. The radio bearer identifier is DRB2. A second QoS requirement is the identifier of the service pattern being <NUM>. The QoS requirement is indirectly informed through the transport bearer. The transport bearer is a radio bearer. The radio bearer identifier is DRB3.

The service status information includes information about two service patterns. Information about a first service pattern is: the identifier of the service pattern being <NUM>, the period (Periodicity) of the service pattern being <NUM> minutes (<NUM> mins), the starting time (St) of the service pattern being <NUM>:<NUM> CST, the ending time (Et) of the service pattern being <NUM>:<NUM> CST, and the size of the service pattern being <NUM> bits. Information about a second service pattern is: the identifier of the service pattern being <NUM>, the period (Periodicity) of the service pattern being <NUM> minutes (<NUM> mins), the starting time (St) of the service pattern being <NUM>:<NUM> CST, the ending time (Et) of the service pattern being <NUM>:<NUM> CST, and the size of the service pattern being <NUM> bits.

In this embodiment of this application, a terminal sends auxiliary information for a target configuration to a network side device, where the target configuration is a configuration related to transmission of an uplink resource preconfigured by the network side device. In this way, the terminal can assist, by sending the auxiliary information, the network side device in better configuring the uplink resource. Therefore, the uplink resource configured by the network side device can better satisfy a demand of the terminal.

It should be noted that, the method for sending auxiliary information provided in this embodiment of this application may be performed by an apparatus for sending auxiliary information, or by a control module that is in the apparatus for sending auxiliary information and that is configured to perform the method for sending auxiliary information. In this embodiment of this application, that the apparatus for sending auxiliary information performs the method for sending auxiliary information is used as an example to describe an apparatus for sending auxiliary information provided in an embodiment of this application.

<FIG> is a structural diagram of an apparatus for sending auxiliary information according to an embodiment of this application. As shown in <FIG>, the apparatus <NUM> for sending auxiliary information is applied to a terminal and includes:
a sending module <NUM>, configured to send auxiliary information for a target configuration to a network side device, where the target configuration is a configuration related to transmission of a preconfigured physical uplink shared channel PUSCH resource.

Optionally, the apparatus <NUM> for sending auxiliary information further includes:.

Optionally, the sending module <NUM> is specifically configured to:
send the auxiliary information for the target configuration to the network side device in a case that an initiation condition is satisfied.

Optionally, the auxiliary information includes first auxiliary information and/or second auxiliary information in a case that the terminal needs the target configuration, where the first auxiliary information is used to indicate a tendentious configuration of the terminal for the target configuration, and the second auxiliary information is used to indicate service status of the terminal.

Optionally, the configuration parameter includes at least one of a TBS, a quantity of PUSCH occasions, a period of a PUSCH occasion, time offset for the first PUSCH occasion, a bandwidth part BWP identifier, and a quantity of hybrid automatic repeat requests HARQs.

Optionally, the first transmission bearer information includes at least one of a radio bearer identifier, a logical channel identifier, a data flow identifier, a session identifier, and a cell group identifier.

Optionally, the second auxiliary information includes at least one of Quality of Service QoS requirement information and service status information.

Optionally, the QoS requirement information includes at least one of a service identifier, a service pattern identifier, QoS description information, and second transmission bearer information; and
the second transmission bearer information is used to indirectly indicate a QoS requirement of the terminal.

Optionally, the service status information includes at least one of a service identifier, a service pattern identifier, a service period, a service starting time, a service ending time, a service duration time, and a service size.

Optionally, the service starting time is represented by an absolute time and/or a relative time; and
the service ending time is represented by an absolute time and/or a relative time.

The apparatus for sending auxiliary information in this embodiment of this application may be an apparatus, or may be a component, an integrated circuit, or a chip in a terminal. The apparatus may be a mobile terminal, or a non-mobile terminal. For example, the mobile device may include but is not limited to the types of the terminal <NUM> listed above, and the non-mobile terminal may be a server, a network attached storage (Network Attached Storage, NAS), a personal computer (personal computer, PC), a television (television, TV), an automated teller machine, or a self-service machine. This is not specifically limited in the embodiments of this application.

The apparatus for sending auxiliary information in this embodiment of this application may be an apparatus with an operating system. The operating system may be an Android (Android) operating system, an iOS operating system, or another possible operating system, which is not specifically limited in this embodiment of this application.

The apparatus for sending auxiliary information provided in this embodiment of this application can implement the processes implemented in the method embodiments in <FIG>, and achieve a same technical effect. To avoid repetition, details are not described herein again.

<FIG> is a flowchart of a method for receiving auxiliary information according to an embodiment of this application. As shown in <FIG>, the method for receiving auxiliary information is applied to a network side device and includes the following steps.

Step <NUM>: Receive auxiliary information sent by a terminal for a target configuration, where the target configuration is a configuration related to transmission of a preconfigured physical uplink shared channel PUSCH resource.

Optionally, before the receiving auxiliary information sent by a terminal for a target configuration, the method further includes:.

Optionally, an initiation condition for the auxiliary information includes at least one of the following:.

It should be noted that, related implementations and related descriptions in the method embodiments of <FIG> are all applicable to the embodiments of this application, with the same technical effects achieved. To avoid repetition, details are not described herein again.

It should be noted that, the method for receiving auxiliary information provided in this embodiment of this application may be performed by an apparatus for receiving auxiliary information, or by a control module that is in the apparatus for receiving auxiliary information and that is configured to perform the method for receiving auxiliary information. In this embodiment of this application, that the apparatus for receiving auxiliary information performs the method for receiving auxiliary information is used as an example to describe an apparatus for receiving auxiliary information provided in an embodiment of this application.

<FIG> is a structural diagram of an apparatus for receiving auxiliary information according to an embodiment of this application. As shown in <FIG>, the apparatus <NUM> for receiving auxiliary information is applied to a network side device and includes:
a receiving module <NUM>, configured to receive auxiliary information sent by a terminal for a target configuration, where the target configuration is a configuration related to transmission of a preconfigured physical uplink shared channel PUSCH resource.

Optionally, the apparatus <NUM> for receiving auxiliary information further includes:.

As shown in <FIG>, an embodiment of this application further provides a communications device <NUM>, including a processor <NUM>, a memory <NUM>, and a program or an instruction stored in the memory <NUM> and executable by the processor <NUM>. For example, in a case that the communications device <NUM> is a terminal, the program or instruction, when executed by the processor <NUM>, implements the processes of the embodiment of the method for sending auxiliary information and achieves a same technical effect. In a case that the communications device <NUM> is a network side device, the program or instruction, when executed by the processor <NUM>, implements the processes of the embodiment of the method for receiving auxiliary information and achieves a same technical effect. To avoid repetition, details are not described herein again.

An embodiment of this application further provides a network side device. As shown in <FIG>, the network side device <NUM> includes an antenna <NUM>, a radio frequency apparatus <NUM>, and a baseband apparatus <NUM>. The antenna <NUM> is connected to the radio frequency apparatus <NUM>. In an uplink direction, the radio frequency apparatus <NUM> receives information by using the antenna <NUM>, and sends the received information to the baseband apparatus <NUM> for processing. In a downlink direction, the baseband apparatus <NUM> processes to-be-sent information, and sends the to-be-sent information to the radio frequency apparatus <NUM>. After processing the received information, the radio frequency apparatus <NUM> sends the information by using the antenna <NUM>.

The frequency band processing apparatus may be located in the baseband apparatus <NUM>. The method performed by the network side device in the above embodiment may be implemented in the baseband apparatus <NUM>. The baseband apparatus <NUM> includes a processor <NUM> and a memory <NUM>.

The baseband apparatus <NUM> may include, for example, at least one baseband board, where a plurality of chips are disposed on the baseband board. As shown in <FIG>, one chip is, for example, the processor <NUM>, which is connected to the memory <NUM>, so as to invoke a program in the memory <NUM> to perform operations of the network device shown in the above method embodiment.

The baseband apparatus <NUM> may further include a network interface <NUM> for exchanging information with the radio frequency apparatus <NUM>. The interface is, for example, a common public radio interface (common public radio interface, CPRI).

Specifically, the network side device in this embodiment of the present disclosure further includes an instruction or a program stored in the memory <NUM> and executable by the processor <NUM>. The processor <NUM> invokes the instruction or the program in the memory <NUM> to perform the method performed by the modules shown in <FIG>, and a same technical effect can be achieved. To avoid repetition, details are not described herein again.

<FIG> is a schematic diagram of a hardware structure of a terminal according to an embodiment of this application.

The terminal <NUM> includes but is not limited to components such as a radio frequency unit <NUM>, a network module <NUM>, an audio output unit <NUM>, an input unit <NUM>, a sensor <NUM>, a display unit <NUM>, a user input unit <NUM>, an interface unit <NUM>, a memory <NUM>, and a processor <NUM>.

A person skilled in the art can understand that the terminal <NUM> may further include a power supply (for example, a battery) that supplies power to the components. The power supply may be logically connected to the processor <NUM> by using a power management system, so as to implement functions such as charging management, discharging management, and power consumption management by using the power management system. The terminal structure shown in <FIG> constitutes no limitation on the terminal, and the terminal may include more or fewer components than those shown in the figure, or combine some components, or have different component arrangements.

It should be understood that, in the embodiments of this application, the input unit <NUM> may include a graphics processing unit (Graphics Processing Unit, GPU) <NUM> and a microphone <NUM>, and the graphics processing unit <NUM> processes image data of a still picture or video obtained by an image capture apparatus (such as a camera) in a video capture mode or an image capture mode. The display unit <NUM> may include a display panel <NUM>, and the display panel <NUM> may be configured in a form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit <NUM> includes a touch panel <NUM> and another input device <NUM>. The touch panel <NUM> is also referred to as a touchscreen. The touch panel <NUM> may include two parts: a touch detection apparatus and a touch controller. The another input device <NUM> may include but is not limited to a physical keyboard, a functional button (such as a volume control button or a power on/off button), a trackball, a mouse, and a joystick.

In this embodiment of this application, the radio frequency unit <NUM> receives downlink data from a network side device and then sends the downlink data to the processor <NUM> for processing; and sends uplink data to the network side device. Usually, the radio frequency unit <NUM> includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.

The memory <NUM> may be configured to store a software program or an instruction and various data. The memory <NUM> may mainly include a program or instruction storage area and a data storage area. The program or instruction storage area may store an operating system, and an application or an instruction required by at least one function (for example, a sound playing function or an image playing function). In addition, the memory <NUM> may include a high-speed random access memory, and may further include a non-volatile memory. The non-volatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically erasable programmable read-only memory (Electrically EPROM, EEPROM), or a flash memory. For example, at least one disk storage component, a flash memory component, or another non-volatile solid-state storage component.

The processor <NUM> may include one or more processing units. Optionally, an application processor and a modem processor may be integrated into the processor <NUM>. The application processor mainly processes an operating system, a user interface, an application, an instruction, or the like. The modem processor mainly processes wireless communications, for example, a baseband processor. It can be understood that, alternatively, the modem processor may not be integrated into the processor <NUM>.

The radio frequency unit <NUM> is configured to:
send auxiliary information for a target configuration to a network side device, where the target configuration is a configuration related to transmission of a preconfigured physical uplink shared channel PUSCH resource.

Optionally, the radio frequency unit <NUM> is further configured to:.

Optionally, the radio frequency unit <NUM> is further configured to:
send the auxiliary information for the target configuration to the network side device in a case that an initiation condition is satisfied.

Optionally, the target configuration is a configuration related to transmission of a preconfigured physical uplink shared channel PUSCH resource.

An embodiment of this application further provides a readable storage medium. The readable storage medium stores a program or an instruction. The program or instruction, when executed by a processor, implements the processes of the method for sending auxiliary information according to the above embodiment or implements the processes of the method for receiving auxiliary information according to the above embodiment, with the same technical effects achieved. To avoid repetition, details are not described herein again.

The processor is a processor in the terminal in the above embodiment. The readable storage medium includes a computer-readable storage medium such as a read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk, an optical disc, or the like.

An embodiment of this application further provides a chip. The chip includes a processor and a communications interface. The communications interface is coupled to the processor. The processor is configured to run a program or an instruction, to implement the processes of the method for sending auxiliary information according to the above embodiment or implement the processes of the method for receiving auxiliary information according to the above embodiment, with the same technical effects achieved. To avoid repetition, details are not described herein again.

It should be understood that the chip mentioned in the embodiment of this application can also be called a system-level chip, a system chip, a chip system, or a system on chip.

It should be noted that, in this specification, the terms "include", "comprise", or their any other variant is intended to cover a non-exclusive inclusion, so that a process, a method, an article, or an apparatus that includes a list of elements not only includes those elements but also includes other elements which are not expressly listed, or further includes elements inherent to such process, method, article, or apparatus. In the absence of more restrictions, an element defined by the statement "including a. " does not preclude the presence of other identical elements in the process, method, article, or apparatus that includes the element. In addition, it should be noted that the scope of the method and the apparatus in the embodiments of this application is not limited to performing functions in an illustrated or discussed sequence, and may further include performing functions in a basically simultaneous manner or in a reverse sequence according to the functions concerned. For example, the described method may be performed in an order different from that described, and the steps may be added, omitted, or combined. In addition, features described with reference to some examples may be combined in other examples.

A person of ordinary skill in the art may recognize that, with reference to the examples described in the embodiments disclosed herein, units and algorithm steps may be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether these functions are implemented by using hardware or software depends on the specific application and design constraints of the technical solution. A person skilled in the art may use different methods to implement the described functions for each particular application, but it should not be considered that the implementation goes beyond the scope of the present disclosure.

It may be clearly understood by a person skilled in the art that, for convenience and brevity of description, for a specific working process of the above described system, apparatus, and unit, reference may be made to a corresponding process in the above method embodiments, and details are not described herein again.

In the embodiments provided in this application, it should be understood that the disclosed apparatus and method may be implemented in another manner. For example, the unit division is merely logical function division. In actual implementation, there may be another division manner. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not performed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections may be implemented through some interfaces.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected based on an actual requirement to implement the objectives of the solutions in the embodiments.

In addition, functional units in the embodiments of the present disclosure may be integrated into one processing unit, or each of the units may exist alone physically, or two or more units are integrated into one unit.

Based on the descriptions of the above implementations, a person skilled in the art may clearly understand that the method in the above embodiment may be implemented by software in addition to a necessary universal hardware platform or by hardware only. In most circumstances, the former is a preferred implementation. Based on such understanding, the technical solutions of this application essentially, or the part contributing to the prior art may be implemented in a form of a software product. The computer software product is stored in a storage medium (for example, a ROM/RAM, a magnetic disk, or a compact disc), and includes several instructions for instructing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, a network device, or the like) to perform the method described in the embodiments of this application.

It can be understood that the embodiments described in the present disclosure may be implemented by hardware, software, firmware, middleware, microcode, or a combination thereof. For implementation with hardware, the module, unit, and subunit can be implemented in one or more application specific integrated circuits (Application Specific Integrated Circuits, ASIC), a digital signal processor (Digital Signal Processor, DSP), a DSP device (DSP Device, DSPD), a programmable logic device (Programmable Logic Device, PLD), a field-programmable gate array (Field-Programmable Gate Array, FPGA), a general-purpose processor, a controller, a micro-controller, a micro-processor, and other electronic units for implementing the functions of the present disclosure, or a combination thereof.

Claim 1:
A method for sending auxiliary information performed by a terminal, the method comprising:
sending auxiliary information for a target configuration to a network side device, wherein the target configuration is a configuration related to transmission of a preconfigured physical uplink shared channel, PUSCH, resource (<NUM>);
the method characterised in that,
the auxiliary information comprises second auxiliary information in a case that the terminal needs the target configuration, wherein the second auxiliary information is used to indicate service status of the terminal, and the second auxiliary information comprises Quality of Service, QoS, requirement information;
wherein the QoS requirement information comprises at least one of a service identifier, a service pattern identifier, QoS description information, and second transmission bearer information; and
the second transmission bearer information is used to indirectly indicate a QoS requirement of the terminal, wherein the second transmission bearer information comprises at least one of a radio bearer identifier, a data flow identifier, a session identifier, or a logical channel identifier.